% Datatracker information for RFCs on the Legacy Stream is unfortunately often % incorrect. Please correct the bibtex below based on the information in the % actual RFC at https://rfc-editor.org/rfc/rfc2968.txt @misc{rfc2968, series = {Request for Comments}, number = 2968, howpublished = {RFC 2968}, publisher = {RFC Editor}, doi = {10.17487/RFC2968}, url = {https://www.rfc-editor.org/info/rfc2968}, author = {Thommy Eklof and Leslie Daigle}, title = {{Mesh of Multiple DAG servers - Results from TISDAG}}, pagetotal = 9, year = 2000, month = oct, abstract = {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.}, }