RFC 2164: Use of an X.500/LDAP directory to support MIXER address mapping
In plain English — editorial summary, not part of the RFC
This specification defines how to represent and maintain these mappings (MIXER Conformant Global Address Mappings of MCGAMs) in an X.500 or LDAP directory. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2164
- Published
- January 1998
- Authors
- S. Kille
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 10
- Also known as
- —
- Obsoletes:
- RFC 1838
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2927MIME Directory Profile for LDAP SchemaCurrent
September 2000
- RFC 2163Using the Internet DNS to Distribute MIXER Conformant Global Address Mapping (MCGAM)Updated
January 1998
- RFC 2255The LDAP URL FormatObsoleted
December 1997
- RFC 2256A Summary of the X.500(96) User Schema for use with LDAPv3Obsoleted
December 1997
- RFC 1960A String Representation of LDAP Search FiltersObsoleted
June 1996
- RFC 1959An LDAP URL FormatObsoleted
June 1996
- RFC 2596Use of Language Codes in LDAPObsoleted
May 1999
- RFC 2696LDAP Control Extension for Simple Paged Results ManipulationCurrent
September 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?