RFC 2657: LDAPv2 Client vs. the Index Mesh
In plain English — editorial summary, not part of the RFC
LDAPv2 clients as implemented according to RFC 1777 have no notion on referral. The integration between such a client and an Index Mesh, as defined by the Common Indexing Protocol, heavily depends on referrals and therefore needs to be handled in a special way. This document defines one possible way of doing this. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC2657
- Published
- August 1999
- Authors
- R. Hedberg
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- app
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2655CIP Index Object Format for SOIF ObjectsCurrent
August 1999
- RFC 2654A Tagged Index Object for use in the Common Indexing ProtocolCurrent
August 1999
- RFC 2653CIP Transport ProtocolsCurrent
August 1999
- RFC 2652MIME Object Definitions for the Common Indexing Protocol (CIP)Current
August 1999
- RFC 2651The Architecture of the Common Indexing Protocol (CIP)Current
August 1999
- RFC 2656Registration Procedures for SOIF Template TypesCurrent
August 1999
- RFC 2649An LDAP Control and Schema for Holding Operation SignaturesCurrent
August 1999
- RFC 2648A URN Namespace for IETF DocumentsUpdated
August 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?