document progression

"Kevin E. Jordan" <Kevin.E.Jordan@cdc.com> Thu, 12 May 1994 13:40 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04755; 12 May 94 9:40 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa04751; 12 May 94 9:40 EDT
Received: from [129.179.91.44] by CNRI.Reston.VA.US id aa06803; 12 May 94 9:40 EDT
Received: from mercury91.udev.cdc.com by sequoia.udev.cdc.com; Thu, 12 May 94 08:39:40 -0600
Received: by mercury.udev.cdc.com; Thu, 12 May 94 08:20:54 -0500
X-From: kej@mercury.udev.cdc.com Thu May 12 08:20 CDT 1994
Received: from localhost by mercury.udev.cdc.com; Thu, 12 May 94 08:20:52 -0500
To: s.kille@isode.com
cc: mhs-ds@mercury.udev.cdc.com
Subject: document progression
Date: Thu, 12 May 94 08:20:51 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Kevin E. Jordan" <Kevin.E.Jordan@cdc.com>
Message-Id: <2dd22d340956002@mercury.udev.cdc.com>

Steve,

In order to continue making progress on the MHS-DS documents, I recommend
that you apply the editorial changes you've received up to this point and
put the documents out for a two week review period.  If no significant comments
are received by the end of the review period, we should then submit the
documents as RFC's.  The specific documents to be updated and progressed
are:

   - Representing the O/R Address hierarchy in the Directory Information Tree
           last draft: draft-ietf-mhsds-infotree-04
       recommendation: progress as Proposed Internet Standard

   - Representing Tables and Subtrees in the Directory
           last draft: draft-ietf-mhsds-subtrees-04
       recommendation: progress as Proposed Internet Standard

   - MHS use of Directory to support MHS Routing
           last draft: draft-ietf-mhsds-routdirectory-04
       recommendation: progress as Proposed Internet Standard

   - Use of the Directory to support mapping between X.400 and RFC 822 Addresses
           last draft: draft-ietf-mhsds-supmapping-04
       recommendation: progress as Proposed Internet Standard

Is it possible for you to revise and put these documents out for review by
May 27?  If so, we can target June 10 as the date for submitting the documents
as proposed standards.  We can then start working on the remaining three
documents (MHS-DS support of RFC822, MHS-DS support of distribution lists,
and MHS-DS support of content conversion).