RFC 1137 (rfc1137) - Page 1 of 3
Mapping between full RFC 822 and RFC 822 with restricted encoding
Alternative Format: Original Text Document
Network Working Group S. Kille
Request for Comments: 1137 University College London
Updates: RFC 976 December 1989
Mapping Between Full RFC 822 and RFC 822 with
Restricted Encoding
Status of this Memo
This RFC suggests an electronic mail protocol mapping for the
Internet community and UK Academic Community, and requests discussion
and suggestions for improvements. This memo does not specify an
Internet standard. Distribution of this memo is unlimited.
This document describes a set of address mappings which will enable
interworking between systems operating RFC 822 protocols in a general
manner, and those environments where transfer of RFC 822 messages
restricts the character set which can be used in addresses. UUCP
transfer of RFC 822 messages is an important case of this
[Crocker82a, Horton86a].
Specification
This document specifies a mapping between two protocols. This
specification should be used when this mapping is performed on the
Internet or in the UK Academic Community. This specification may be
modified in the light of implementation experience, but no
substantial changes are expected.
1. Introduction
Some mail networks which use RFC 822 cannot support the full
character set required by all aspects of RFC 822. This document
describes a symmetrical mapping between full RFC 822 addressing, and
a form for use on these networks. Any addresses within the networks
will not use the full RFC 822 addressing, and so any addresses
encoded according to this standard will always represent remote
addresses. This document derives from a mapping originally specified
in RFC 987 [Kille86a], where the domain of application was more
restricted. Two terms are now defined:
Full RFC 822
This implies full support for transfer to and from any legal RFC
822 address. In particular, the quoted-string form of local-part
must be supported (e.g., ).
Kille