home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1997 December
/
Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso
/
ietf
/
mhsds
/
mhsds-charter.txt
< prev
next >
Wrap
Text File
|
1997-10-08
|
5KB
|
116 lines
MHS-DS (mhsds)
--------------
Charter
Last Modified: 26-Mar-95
Current Status: Concluded Working Group
Chair(s):
Kevin Jordan <Kevin.E.Jordan@cdc.com>
Harald Alvestrand <Harald.T.Alvestrand@uninett.no>
Applications Area Director(s):
Keith Moore <moore+iesg@cs.utk.edu>
Harald Alvestrand <Harald.T.Alvestrand@uninett.no>
Applications Area Advisor:
Keith Moore <moore+iesg@cs.utk.edu>
Mailing Lists:
General Discussion:mhs-ds@mercury.udev.cdc.com
To Subscribe: mhs-ds-request@mercury.udev.cdc.com
Archive: mercury.udev.cdc.com:~/pub/archives/mhs-ds-archive
Description of Working Group:
The MHS-DS Working Group works on issues relating to Message Handling
Services use of Directory Services. The message handling services are
primarily X.400, but issues relating to RFC 822 use of Directory and
Directory support for RFC 822 and X.400 interworking are in the scope of
the group. Directory and Directory Services refer to the services
based upon the CCITT X.500 recommendations and additional ISO
standards, stable implementation agreements, and RFCs, as specified by
the OSI-DS Working Group. The major aims of the MHS-DS Working Group
are:
1. Define a set of specifications to enable effective, large-scale
deployment of X.400.
2. Study issues associated with supporting X.400 communities which lack
access to X.500 Directory, and define requirements for tools which: (a)
extract information from the X.500 Directory for use by non-X.500
applications, and (b) upload information into the X.500 Directory.
3. Coordinate a pilot project which deploys MHS information into the
X.500 Directory and uses it to facilitate mail routing and address
mapping. The results of this pilot will be documented, and experience
gained from the project will be fed back into the Internet
specifications created by the working group.
Goals and Milestones:
Jan 92 Establish and maintain liaison relationships with similar
groups working on X.400 and X.500, e.g., RRE Mail and Messaging
Group, IETF OSI-DS Working Group, IETF X.400 Operations Working
Group and the IETF MIME-MHS Working Group.
Jan 92 Provide a forum to discuss Directory support of Message
Handling Services including the operational aspects of X.500
based routing in the Internet community and issues of migration
from non-X.500 to X.500 based routing.
Done Post a document on representing tables and subtees in the
directory as an Internet-Draft.
Done Post an overview of MHS use of Directory as an Internet-Draft.
Done Post an Internet-Draft on MHS use of Directory to support MHS
Routing.
Done Post as an Internet-Draft a document on the use of the
directory to support mapping between X.400 and RFC822
addresses.
Done Post an Internet-Draft on representing the O/R Address
hierarchy in the Directory Information Tree.
Done Submit as an Internet-Draft a document on MHS use of Directory
to support MHS Context Conversion.
Done Post as an Internet-Draft a document on the use of the
Directory to support routing for RFC822 and related protocols.
Done Post as an Internet-Draft a document describing a simple
profile for MHS use of Directory.
Done Post as an Internet-Draft a document describing the use of the
Directory to support distribution lists.
Done Submit the set of MHS-DS documents to the IESG for
consideration as Experimental and Informational documents.
Internet-Drafts:
No Current Internet-Drafts.
Request For Comments:
RFC Stat Published Title
------- -- ---------- -----------------------------------------
RFC1801 E Jun 95 MHS use of the X.500 Directory to support MHS Routing
RFC1802 Jun 95 Introducing Project Long Bud: Internet Pilot Project
for the Deployment of X.500 Directory Information in
Support of X.400 Routing
RFC1837 E Aug 95 Representing Tables and Subtrees in the X.500 Directory
RFC1836 E Aug 95 Representing the O/R Address hierarchy in the X.500
Directory Information Tree
RFC1838 E Aug 95 Use of the X.500 Directory to support mapping between
X.400 and RFC 822 Addresses