Browse Prior Art Database

CIP Transport Protocols (RFC2653)

IP.com Disclosure Number: IPCOM000003242D
Original Publication Date: 1999-Aug-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 9 page(s) / 21K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Allen: AUTHOR [+3]

Abstract

This document specifies three protocols for transporting CIP requests, responses and index objects, utilizing TCP, mail, and HTTP. The objects themselves are defined in [CIP-MIME] and the overall CIP architecture is defined in [CIP-ARCH].

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 13% of the total text.

Network Working Group J. Allen

Request for Comments: 2653 WebTV Networks, Inc.

Category: Standards Track P. Leach

Microsoft

R. Hedberg

Catalogix

August 1999

CIP Transport Protocols

Status of this Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1999). All Rights Reserved.

Abstract

This document specifies three protocols for transporting CIP

requests, responses and index objects, utilizing TCP, mail, and HTTP.

The objects themselves are defined in [CIP-MIME] and the overall CIP

architecture is defined in [CIP-ARCH].

1. Protocol

In this section, the actual protocol for transmitting CIP index

objects and maintaining the mesh is presented. While companion

documents ([CIP-ARCH] and [CIP-MIME]) describe the concepts involved

and the formats of the CIP MIME objects, this document is the

authoritative definition of the message formats and transfer

mechanisms of CIP used over TCP, HTTP and mail.

1.1 Philosophy

The philosophy of the CIP protocol design is one of building-block

design. Instead of relying on bulky protocol definition tools, or

ad-hoc text encodings, CIP draws on existing, well understood

Internet technologies like MIME, RFC-822, Whois++, FTP, and SMTP.

Hopefully this will serve to ease implementation and consensus

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 "<<< ".

2 MIME message exchange mechanisms

CIP relies on interchange of standard MIME messages for all requests

and replies. These messages are passe...