Common Indexing Protocol
The Common Indexing Protocol (CIP) was an attempt in the IETF working group FIND during the mid-1990s to define a protocol for exchanging index information between directory services. In the X.500 Directory model, searches scoped near the root of the tree (e.g. at a particular country) were problematic to implement, as potentially hundreds or thousands of directory servers would need to be contactedin order to handle that query. The protocol evolved from earlier work developing WHOIS++, and was intended to be capable of interconnectingservices from both the evolving WHOIS and LDAP activities.
- Comment
- enThe Common Indexing Protocol (CIP) was an attempt in the IETF working group FIND during the mid-1990s to define a protocol for exchanging index information between directory services. In the X.500 Directory model, searches scoped near the root of the tree (e.g. at a particular country) were problematic to implement, as potentially hundreds or thousands of directory servers would need to be contactedin order to handle that query. The protocol evolved from earlier work developing WHOIS++, and was intended to be capable of interconnectingservices from both the evolving WHOIS and LDAP activities.
- Has abstract
- enThe Common Indexing Protocol (CIP) was an attempt in the IETF working group FIND during the mid-1990s to define a protocol for exchanging index information between directory services. In the X.500 Directory model, searches scoped near the root of the tree (e.g. at a particular country) were problematic to implement, as potentially hundreds or thousands of directory servers would need to be contactedin order to handle that query. The indexes contained summaries or subsets of information about individuals and organizations represented ina white pages schema. By merging subsets of information from multiple sources, it was hoped that an index server holding that subset could be able to process a query more efficiently by chaining it only to some of the sources: those sources which did not hold information would not be contacted. For example, if a server holding the base entry for a particular country were provided with a list of names of all the people in all the entries in that country subtree, then that server would be able to process a query searching for a person witha particular name by only chaining it to those servers which held data about such a person. The protocol evolved from earlier work developing WHOIS++, and was intended to be capable of interconnectingservices from both the evolving WHOIS and LDAP activities. This protocol has not seen much recent deployment, as WHOIS and LDAP environments have followed separate evolution paths. WHOIS deployments are typically in domain name registrars, and its data management issues have been addressed through specifications for domain name registry interconnection such as CRISP. In contrast, enterprises that manage employee, customeror student identity data in an LDAP directory have looked to federation protocols for interconnection between organizations.
- Hypernym
- Attempt
- Is primary topic of
- Common Indexing Protocol
- Label
- enCommon Indexing Protocol
- Link from a Wikipage to an external page
- www.articleworld.org/index.php/Common_Indexing_Protocol
- Link from a Wikipage to another Wikipage
- Category:Identity management
- Category:Internet protocols
- Cross Registry Information Service Protocol
- IETF
- Lightweight Directory Access Protocol
- White pages schema
- WHOIS
- X.500
- SameAs
- 4iDeq
- Common Indexing Protocol
- m.06fdmy
- Q5153395
- Subject
- Category:Identity management
- Category:Internet protocols
- WasDerivedFrom
- Common Indexing Protocol?oldid=1037761502&ns=0
- WikiPageLength
- 2704
- Wikipage page ID
- 2017525
- Wikipage revision ID
- 1037761502
- WikiPageUsesTemplate
- Template:IETF RFC