Allan Cargille <> Thu, 07 April 1994 19:34 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa12071; 7 Apr 94 15:34 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa12067; 7 Apr 94 15:34 EDT
Received: from by CNRI.Reston.VA.US id aa22515; 7 Apr 94 15:34 EDT
Received: by; Thu, 7 Apr 94 13:13:37 -0500
X-From: Thu Apr 7 13:13 CDT 1994
Received: from by; Thu, 7 Apr 94 13:11:52 -0500
Received: from by id SMTP-0012da44cdb003491; Thu, 7 Apr 94 13:11:40 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Allan Cargille <>
Message-Id: <>
Received: by; Thu, 7 Apr 94 13:11:37 -0500
Subject: comments.supmapping-04.txt
Date: Thu, 7 Apr 1994 13:11:37 -0500 (CDT)
Organization: Univ of Wisconsin
Phone: +1 608 262-5084
Fax: +1 608 262-9777
X-Mailer: ELM [version 2.4 PL23]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1911


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

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
>>> blank line


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


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.