RFC 2653: CIP Transport Protocols
In plain English — editorial summary, not part of the RFC
This document specifies three protocols for transporting CIP requests, responses and index objects, utilizing TCP, mail, and HTTP. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2653
- Published
- August 1999
- Authors
- J. Allen; P. Leach; R. Hedberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2654A Tagged Index Object for use in the Common Indexing ProtocolCurrent
August 1999
- RFC 2652MIME Object Definitions for the Common Indexing Protocol (CIP)Current
August 1999
- RFC 2655CIP Index Object Format for SOIF ObjectsCurrent
August 1999
- RFC 2651The Architecture of the Common Indexing Protocol (CIP)Current
August 1999
- RFC 2657LDAPv2 Client vs. the Index MeshCurrent
August 1999
- RFC 2049Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and ExamplesCurrent
November 1996
- RFC 2533A Syntax for Describing Media Feature SetsUpdated
March 1999
- RFC 2506Media Feature Tag Registration ProcedureCurrent
March 1999
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?