RFC 2164 (rfc2164) - Page 2 of 10
Use of an X
Alternative Format: Original Text Document
RFC 2164 X.500/LDAP Directory to Support MIXER January 1998 o It is the "natural" location, and will also help to ensure correct administrative authority for a mapping definition. o The tree will usually be accessed for routing, and so it will be efficient for addresses which are being routed. This is not done, as the benefits of the approach proposed are greater. MCGAMs are global. A MIXER gateway may use any set of MCGAMs. A key use of the directory is to enable MIXER gateways to share MCGAMs and to share the effort of maintaining and publishing MCGAMs. This specification and MIXER also recognise that there is not a single unique location for publication of all MCGAMs. This specification allows for multiple sets of MCGAMs to be published. Each set of MCGAMs is published under a single part of the directory. There are four mappings, which are represented by two subtrees located under any part of the DIT. For the examples the location defined below is used: OU=MIXER MCGAMs, O=Zydeco Plc, C=GB These subtree roots are of object class subtree, and use the mechanism for representing subtrees defined in [1]. X.400 to RFC 822 This table gives the equivalence mapping from X.400 to RFC 822. There is an OR Address tree under this. An example entry is: PRMD=Isode, ADMD=Mailnet, C=FI, CN=X.400 to RFC 822, OU=MIXER MCGAMs, O=Zydeco Plc, C=GB RFC 822 to X.400 There is a domain tree under this. This table holds the equivalence mapping from RFC 822 to X.400, and the gateway mapping defined in RFC 1327. An example entry is: DomainComponent=ISODE, DomainComponent=COM, CN=RFC 822 to X.400, OU=MIXER MCGAMs, O=Zydeco Plc, C=GB The values of the table mapping are defined by use of two new object classes, as specified in Figure 1. The objects give pointers to the mapped components. Kille Standards Track
