Document status

"Kevin E. Jordan" <Kevin.E.Jordan@cdc.com> Wed, 13 July 1994 23:03 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13351; 13 Jul 94 19:03 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa13347; 13 Jul 94 19:03 EDT
Received: from mercury91.udev.cdc.com by CNRI.Reston.VA.US id aa21762; 13 Jul 94 19:03 EDT
Received: by mercury.udev.cdc.com; Wed, 13 Jul 94 18:03:13 -0500
X-From: kej@mercury.udev.cdc.com Wed Jul 13 18:03 CDT 1994
Received: from localhost by mercury.udev.cdc.com; Wed, 13 Jul 94 18:03:11 -0500
To: mhs-ds@mercury.udev.cdc.com
Subject: Document status
Date: Wed, 13 Jul 94 18:03:10 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Kevin E. Jordan" <Kevin.E.Jordan@cdc.com>
Message-Id: <2e2472af4527002@mercury.udev.cdc.com>

All,

The core MHS-DS protocol specification documents have been installed in
the usual internet-drafts directories, and I have also placed copies in
the MHS-DS archive on host ftp.css.cdc.com.  The core files are:

    pub/mhs-ds/internet-drafts/draft-ietf-mhsds-infotree-05.ps
    pub/mhs-ds/internet-drafts/draft-ietf-mhsds-infotree-05.txt

    pub/mhs-ds/internet-drafts/draft-ietf-mhsds-routdirectory-05.ps
    pub/mhs-ds/internet-drafts/draft-ietf-mhsds-routdirectory-05.txt

    pub/mhs-ds/internet-drafts/draft-ietf-mhsds-subtrees-05.ps
    pub/mhs-ds/internet-drafts/draft-ietf-mhsds-subtrees-05.txt

    pub/mhs-ds/internet-drafts/draft-ietf-mhsds-supmapping-05.ps
    pub/mhs-ds/internet-drafts/draft-ietf-mhsds-supmapping-05.txt

Please review these documents before the upcoming IETF meeting.  Unless there
are significant comments against them, the documents will be progressed as
RFC's following the meeting.

Also, please review the "Intro to Project Long Bud" draft.  This can also
be obtained from the normal internet-draft sites and from ftp.css.cdc.com.
The pathname on ftp.css.cdc.com is:

    pub/mhs-ds/internet-drafts/draft-ietf-mhsds-long-bud-intro-01.txt

This document defines the Long Bud pilot project and specifies how to
participate in it.  The infrastructure for the pilot project is already
under construction.  Two of the proposed four core DSA's which will support
the pilot are in operation.  One of the DSA's is located in the US, and the
other is located in the UK.  The US DSA is named "cn=Long Bud, c=US", and the
UK DSA is named "cn=Ornate Hawk Eagle, c=GB".  At the present time, these
DSA's are replicating all X.400 routing information for all ADMD's and PRMD's
currently registered in the Internet directory under c=GB and c=US.  Support
for fail-over has also been established by configuring slaveDSA attributes in
nonleaf ADMD and PRMD entries.

We hope to bring a second core European DSA into operation before the
upcoming IETF meeting (Sylvain, are you listening?), and a second core US
DSA may become available in August.  Going forward, we need to establish
agreements with Internet DSA managers in other countries such that the
core DSA's can replicate all ADMD and PRMD levels of the Open Community
routing tree.  We must also start verifying that the routing information
registered in the directory is accurate and that the guidelines defined in
the "Long Bud Introduction" Internet Draft are followed.