Use of the Directory to support routing for RFC 822 and related protocols
draft-ietf-mhsds-822dir-03
Document | Type |
Expired Internet-Draft
(mhsds WG)
Expired & archived
|
|
---|---|---|---|
Author | Steve Kille | ||
Last updated | 1993-07-08 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | mercury.udev.cdc.com%3A~/pub/archives/mhs-ds-archive | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document defines a mechanism to route RFC 822 using the OSI Directory. The basic mechanisms are being developed for routing X.400. These offer a number of benefits relative to the the current mechanisms available for RFC 822 routing. The prime goal of this specification is to provide integrated routing management for sites using both RFC 822 and X.400. This draft document will be submitted to the RFC editor as a protocol standard. Distribution of this memo is unlimited. Please send comments to the author or to the discussion group <mhs-ds@mercury.udev.cdc.com>.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)