Ozark Gas Transmission System

First Revised Volume No. 1

 Contents / Previous / Next / Main Tariff Index



Effective Date: 08/01/1998, Docket: RP98-283-000, Status: Effective

Second Revised Sheet No. 43A Second Revised Sheet No. 43A : Superseded

Superseding: First Revised Sheet No. 43A



Standard 4.3.9: There is a time stamp (HTTP Time-stamp) that

designates the time that a file is received at the

designated site. The receiving parity should generate a

time-stamp upon successful receipt of the complete file and

send as an immediate response to the sending party. The

time-stamp should be generated by Common Gateway Interface

(CGI) of the receiving party, prior to further processing by

the CGI.


Standard 4.3.10: The time-stamp should be included in the

HTTP response back to the sender of the original HTTP

transaction. It is recommended that the server clock

generating the time-stamp be synchronized with the National

Institute of Standards and Technology (NIST) time in order

to mitigate discrepancies between the clocks of the sender

and receiver.


Standard 4.3.11: The HTTP response should be sent to the

sending Ineternet Protocol (IP) address. Other response

documents should be returned to the official designated site

defined in the Trading Partner Agreement.


Standard 4.3.12: As a minimum, within a trading partner

agreement, one designated site should be identified by a

specific Uniform Resource Locator (URL). This does not

preclude multiple designated sites being mutually agreed to

between trading partners.


Standard 4.3.13: The sender should make three attempts to

complete a unit of work. After three failed attempts, it

should be considered a failure.

Standard 4.3.14: The roles of sender and receiver are

defined in following table. The entire table defines a unit

of work. (A unit of work consists of one complete HTTP

transaction as defined the technical specifications of the

HTTP protocol (Internet Engineering Task Force RFC 1945)

The roles of sender and receiver are also defined in that



Client (Sender) Server (Receiver) CGI (Receiver)

Connect Accept Connection

Write Read Start of Receipt

Write Read

EOF (send) Read End of Receipt

Read (HTTP response) Write (HTTP response)


EOF (HTTP response)


Standard 4.3.15: Trading partners should implement all

security features (secure authentification, integrity,

privacy, and non-repudiation) using a file-based approach

via a commercially available implementation of PGP 2.6 or

greater (or compatible with PGP 2.6). Trading partners

should also implement basic authentification. This should

be regarded as an interim solution since this technology is

not an open standard. This technology supports all of the

above security features while providing independence of

choice of Web servers and browsers. Encryption keys should

be self-certified and the means of exchange should be

specified in the trading partner agreement.


Standard 4.3.16: The documents identified in GISB Standard

4.3.6 will be made available in HTML or RTF format.