Tennessee Gas Pipeline Company

FIFTH REVISED VOLUME NO. 1

 Contents / Previous / Next / Main Tariff Index

 

 

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

Second Revised Sheet No. 661 Second Revised Sheet No. 661 : Effective

Superseding: First Revised Sheet No. 661

 

 

ELECTRONIC DATA INTERCHANGE

TRADING PARTNER AGREEMENT (Continued)

 

 

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.

 

2.1.2 The "Receipt Computer" shall be defined in the Exhibit(s) as the

receiving party's Uniform Resource Locator ("URL"), which describes the protocols which

are needed to access the resources and point to the appropriate Internet locations.

Where the parties employ the services of Providers to transmit and receive Documents, the

Receipt Computer shall be defined in the Exhibit(s) as the receiving party's URL provided

by the receiving party's Provider.

 

2.2 Digital Signature Verification and Decryption. Upon proper receipt of any

Document, the receiving party shall attempt to decrypt the Document and verify the

digital signature of the sending party. If the Document is verified and the decryption

is successful, the receiving party shall transmit a Functional Acknowledgment in return.

If the Document is verified and the decryption is unsuccessful, the receiving party shall

send the applicable error message to the sending party. The sending party shall attempt

to correct the error and promptly retransmit the Document or otherwise contact the

receiving party.