RFC 2653 (rfc2653) - Page 2 of 11

CIP Transport Protocols

Alternative Format: Original Text Document

< Previous

Next >

RFC 2653                CIP Transport Protocols              August 1999


   building. It should also stand as an example of a simple way to
   leverage existing Internet technologies to easily implement new
   application-level services.

1.2  Conventions

   The key words "MUST" and "MAY" in this document are to be interpreted
   as described in "Key words for use in RFCs to Indicate Requirement
   Levels" [KEYWORDS].

   Formal syntax is defined using ABNF [ABNF].

   In examples octets sent by the sender-CIP are preceded by ">>> " and
   those sent by the receiver-CIP by "". On existing Whois++
   servers implementing version 1 and 2 of CIP, this results in a 500-
   series response code, and the server terminates the connection.  If



Allen, et al.               Standards Track

< Previous

Next >