Protocol Action: MHS-DS Documents to Experimental

IESG Secretary <iesg-secretary@CNRI.Reston.VA.US> Mon, 28 November 1994 22:52 UTC

Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa13921; 28 Nov 94 17:52 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa17592; 28 Nov 94 17:52 EST
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13897; 28 Nov 94 17:52 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa13823; 28 Nov 94 17:49 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa17510; 28 Nov 94 17:49 EST
Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa13817; 28 Nov 94 17:49 EST
To: IETF-Announce: ;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: mhs-ds@mercury.udev.cdc.com
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: IESG Secretary <iesg-secretary@CNRI.Reston.VA.US>
Subject: Protocol Action: MHS-DS Documents to Experimental
Date: Mon, 28 Nov 94 17:49:15 -0500
X-Orig-Sender: scoya@CNRI.Reston.VA.US
Message-ID: <9411281749.aa13817@IETF.CNRI.Reston.VA.US>

The IESG has reviewed the Internet-Drafts:

    o "Representing the O/R Address hierarchy in the X.500 Directory
      Information Tree" <draft-ietf-mhsds-infotree-06.txt, .ps>

    o "Representing Tables and Subtrees in the X.500 Directory"
      <draft-ietf-mhsds-subtrees-06.txt, .ps>

    o "Use of the X.500 Directory to support mapping between X.400
      and RFC 822 Addresses" <draft-ietf-mhsds-supmapping-06.txt, .ps>

and recommends to the RFC Editor that they be published as
Experimental RFCs.

These documents are the product of the MHS-DS Working Group.  The
IESG contact persons are John Klensin and Erik Huizer.


Technical Summary

  These documents specify uses of the X.500 directory structure to
  facilitate use of X.400 mail and the associated formal names and
  descriptors in the Internet context.  They also specify how to
  facilitate distribution of mapping rules for gatewaying between
  X.400 mail and RFC 822/MIME, as required by RFC 1327.