RFC 2654: A Tagged Index Object for use in the Common Indexing Protocol
In plain English — editorial summary, not part of the RFC
This document defines a mechanism by which information servers can exchange indices of information from their databases by making use of the Common Indexing Protocol (CIP). This document defines the structure of the index information being exchanged, as well as the appropriate meanings for the headers that are defined in the Common Indexing Protocol. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC2654
- Published
- August 1999
- Authors
- R. Hedberg; B. Greenblatt; R. Moats; M. Wahl
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- app
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2651The Architecture of the Common Indexing Protocol (CIP)Current
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 2653CIP Transport ProtocolsCurrent
August 1999
- RFC 2657LDAPv2 Client vs. the Index MeshCurrent
August 1999
- RFC 1625WAIS over Z39.50-1988Current
June 1994
- RFC 2707Job Monitoring MIB - V1.0Current
November 1999
- RFC 2708Job Submission Protocol Mapping Recommendations for the Job Monitoring MIBCurrent
November 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?