RFC 2968: Mesh of Multiple DAG servers - Results from TISDAG
In plain English — editorial summary, not part of the RFC
This document defines the basic principle for establishing a mesh, that interoperating services should exchange index objects, according to the architecture of the mesh (e.g., hierarchical, or graph-like, preferably without loops!). The Common Indexing Protocol (CIP) is designed to facilitate the creation not only of query referral indexes, but also of meshes of (loosely) affiliated referral indexes. The purpose of such a mesh of servers is to implement some kind of distributed sharing of indexing and/or searching tasks across different servers. So far, the TISDAG (Technical Infrastructure for Swedish Directory Access Gateways) project has focused on creating a single referral index; the obvious next step is to integrate that into a larger set of interoperating services. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2968
- Published
- October 2000
- Authors
- L. Daigle; T. Eklof
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2969Wide Area Directory Deployment - Experiences from TISDAGCurrent
October 2000
- RFC 2970Architecture for Integrated Directory Services - Result from TISDAGCurrent
October 2000
- RFC 2985PKCS #9: Selected Object Classes and Attribute Types Version 2.0Current
November 2000
- RFC 3045Storing Vendor Information in the LDAP root DSECurrent
January 2001
- RFC 3112LDAP Authentication Password SchemaCurrent
May 2001
- RFC 2798Definition of the inetOrgPerson LDAP Object ClassUpdated
April 2000
- RFC 2714Schema for Representing CORBA Object References in an LDAP DirectoryCurrent
October 1999
- RFC 2713Schema for Representing Java(tm) Objects in an LDAP DirectoryCurrent
October 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?