Vector Pipeline L.P.

Original Volume No. 1

Effective Date: 10/01/2002, Docket: RP02-479-000, Status: Effective

First Revised Sheet No. 247 First Revised Sheet No. 247 : Effective

Vector Pipeline L.P. First Revised Sheet No. 247

FERC Gas Tariff Superseding

Original Volume No. 1 Original Sheet No. 247

1.2.2 Notwithstanding the acts or omissions of its Provider, for purposes of this

Agreement, each party is responsible for transmitting, receiving, storing or handling

Data Communications to the extent required to effectuate transactions pursuant to

Section 2.

1.3 System Operations. Each party, at its own expense, shall provide and maintain the

equipment, software, services and testing necessary to transmit Data Communications to,

and receive Data Communications from the parties' respective Receipt Computers.

1.4 Security Procedures

1.4.1 Each party shall use those security procedures specified in the North

American Energy Standards Board ("NAESB") standards and the Exhibit(s). The manner in

which public encryption keys are to be changed and/or exchanged will be specified in the

Exhibit(s).

Security Key Exchanges. The parties shall maintain a public key used to facilitate

secure electronic communication. The parties shall change their public key as set forth

in the Exhibit(s). However, in emergency situations in which it is necessary to change a

key immediately, each party shall provide the other party with immediate notice of the

change. Each party shall provide to the other its public key by either: (a) a certified

or receipt mail service using a diskette with the public key contained in an ASCII text

file; or, (b) an electronic simple mail transfer protocol ("SMTP") mail message with the

public key contained in the body. The public key shall be verified by the party to whom

it is sent by validating the fingerprint of the public key by phone or by other

comparable means.

1.5 Signatures. Each party shall adopt as its signature private keys which shall be

applied to each document transmitted by such party ("Digital Signature"). Such Digital

Signature, when decrypted by the receiving party, will be used to authenticate the

identity of the sender.

Section 2. Transmissions

2.1 Proper Receipt

2.1.1 Documents shall not be deemed to have been properly received, and no

Document shall give rise to any obligation, until accessible to the receiving party at

such party's Receipt Computer designated in the Exhibit(s), as evidenced by the receipt

by sending party of the HTTP response initiated by receiving party. The HTTP response

shall specify the date and time of receipt of a Document at the receiving Internet

server (also called "time-c"). No Document shall have any effect if the HTTP response is

not received by sending party, or if the HTTP response indicates an error.