comments.supmapping-04.txt

[Allan Cargille <[e-mail]>]

                                 draft-ietf-mhsds-supmapping-04.txt,ps

  Use of the Directory to support mapping between X.400 and RFC 822
                              Addresses

Status of this Memo
>>> blank line
This document is an Internet Draft.  Internet Drafts are working
documents of the Internet Engineering Task Force (IETF), its Areas,
and its Working Groups.  Note that other groups may also distribute
working documents as Internet Drafts.
>>> Break, indent, or wrap text. 
Internet Drafts are draft documents valid for a maximum of six months.
Internet Drafts may be updated, replaced, or obsoleted by other
documents at any time.  It is not appropriate to use Internet Drafts
as reference material or to cite them other than as a ``working
draft'' or ``work in progress.''

Please check the I-D abstract listing contained in each Internet Draft
directory to learn the current status of this or any other Internet
Draft.
>>> blank line
Abstract

....

In RFC 1327, it is possible to have omitted components in O/R
Addresses on either side of the mapping.  A mechanism to represent
such omitted components is defined in Figure 2.
>>> Break, indent, or wrap text. 
The attribute at-or-address-component-type is set to the X.500
attribute type associated with the omitted component (e.g.,

....

at-prmd-name).  This mechanism is for use only withing the
>>> typo "within"
X.400 to RFC 822 subtree and for the at-associated-or-address
attribute.

....

and return the mapping from the associatedDomain attribute, which
gives the domain which this O/R address maps to.  This attribute is
used to define authoritative mappings, which are placed in the open
community tree.  The manager of an RFC 1327 mapping should make the
appropriate entry.
>>> Break, indent, or wrap text. 
Functionally, mapping takes place exactly according to RFC 1327.  The
longest match is found by the following algorithm.