rfc2164.txt

RFC 的详细文档！


RFC 2164         X.500/LDAP Directory to Support MIXER      January 1998


   1.  Derive a directory name from the domain part of the RFC 822
       address.

   2.  Look up this name in the RFC 822 to X.400 subtree to find the
       mapped value (either associatedORAddress or
       associatedX400Gateway.).  If the lookup fails, the error will
       indicate the longest match, which can then be looked up.

   If associatedORAddress is found, this will define the mapped OR
   Address.  The mapping can always be achieved with two lookups.  If an
   associatedX400Gateway is present, the address in question will be
   encoded as a domain defined attribute, relative to the OR Address
   defined by this attribute.  If multiple associatedX400Gateway
   attributes are found, the MTA may select the one it chooses to use.

   Because of the availability of aliases, some of the table mappings
   may be simplified.  In addition, the directory can support mapping
   from addresses using the numeric country codes.

5  Gateway Selection of MCGAMs

   The directory information to support identification of MCGAMs is
   given in Figure 3.  A MIXER gateway simply identifies the an ordered
   lists of MCGAM collections that it will use for lookup.  These are
   referenced by name.  A gateway is not required to use any MCGAMs.
   Where MCGAMs are accessed from multiple sources, it is recommended
   that all of the sources be accessed in order to determine the MCGAM
   which gives the


mixerGateway OBJECT-CLASS ::=
        KIND auxiliary
        SUBCLASS OF {mhs-message-transfer-agent}
        MUST Contain {
                mcgamTables
        }
        ID oc-mixer-gateway}


mcgamTables ATTRIBUTE ::= {                                         10
        WITH SYNTAX SEQUENCE OF DistinguishedName
        SINGLE VALUE
        ID at-mcgam-tables}

             Figure 3:  Object Classes for MCGAM selection


best match.



Kille                       Standards Track                     [Page 6]

RFC 2164         X.500/LDAP Directory to Support MIXER      January 1998


6  Acknowledgements

   Acknowledgements for work on this document are given in [3].

References

   [1] Kille, S., "Representing tables and subtrees in the X.500
       directory", RFC 1837, August 1995.

   [2] Kille, S., "Representing the O/R Address hierarchy in the X.500
       directory information tree," RFC 1836, August 1995.

   [3] Kille, S., " X.400-MHS use of the X.500 directory to support
       X.400-MHS routing," RFC 1801, June 1995.

   [4] Kille, S., "MIXER (Mime Internet X.400 Enhanced Relay):
       Mapping between X.400 and RFC 822/MIME," RFC 2156, January 1998.

   [5] Kille, S., Wahl, M., Grimsatd, A., Huber, R., and S. Sataluri,
       "Using Domains in LDAP/X.500 Distinguished Names", RFC 2247,
       January 1998.

7  Security Considerations

   This document specifies a means by which the X.500/LDAP directory
   service can direct the translation between X.400 and Internet mail
   addresses.  This can indirectly affect the routing of messages across
   a gateway between X.400 and Internet Mail.  A succesful attack on
   this service could cause incorrect translation of an originator
   address (thus "forging" the originator address), or incorrect
   translation of a recipient address (thus directing the mail to an
   unauthorized recipient, or making it appear to an authorized
   recipient, that the message was intended for recipients other than
   those chosen by the originator).  When cryptographic authentication
   is available for directory responses, clients shall employ those
   mechanisms to verify the authenticity and integrity of those
   responses.














Kille                       Standards Track                     [Page 7]

RFC 2164         X.500/LDAP Directory to Support MIXER      January 1998


8  Author's Address

   Steve Kille
   Isode Ltd.
   The Dome
   The Square
   Richmond
   TW9 1DT
   England

   Phone:  [phone]
   Internet EMail:  [e-mail]







































Kille                       Standards Track                     [Page 8]

RFC 2164         X.500/LDAP Directory to Support MIXER      January 1998


A  Object Identifier Assignment


mhs-ds OBJECT IDENTIFIER ::= {iso(1) org(3) dod(6) internet(1) private(4)
          enterprises(1) isode-consortium (453) mhs-ds (7)}

mapping OBJECT IDENTIFIER ::= {mhs-ds 4}

oc OBJECT IDENTIFIER ::= {mapping 1}
at OBJECT IDENTIFIER ::= {mapping 2}


oc-rfc822-to-x400-mapping OBJECT IDENTIFIER ::= {oc 1}              10
oc-x400-to-rfc822-mapping OBJECT IDENTIFIER ::= {oc 2}
oc-omitted-or-address-component OBJECT IDENTIFIER ::= {oc 3}
oc-mixer-gateway ::= {oc 4}

at-associated-or-address OBJECT IDENTIFIER ::= {at 6}
at-associated-x400-gateway OBJECT IDENTIFIER ::= {at 3}
at-associated-domain OBJECT IDENTIFIER ::= {at 4}
at-or-address-component-type OBJECT IDENTIFIER ::= {at 7}
at-associated-internet-gateway OBJECT IDENTIFIER ::= {at 8}
at-mcgam-tables ::= {at 9}                                          20


                Figure 4:  Object Identifier Assignment

























Kille                       Standards Track                     [Page 9]

RFC 2164         X.500/LDAP Directory to Support MIXER      January 1998


Full Copyright Statement

   Copyright (C) The Internet Society (1998).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
























Kille                       Standards Track                    [Page 10]