Browse Prior Art Database

Mapping between full RFC 822 and RFC 822 with restricted encoding (RFC1137)

IP.com Disclosure Number: IPCOM000001948D
Original Publication Date: 1989-Dec-01
Included in the Prior Art Database: 2000-Sep-12
Document File: 3 page(s) / 6K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Kille: AUTHOR

Abstract

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:

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 46% of the total text.

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., <"Joe Soap"@foo.bar>).

Restricted RFC 822

This implies a subset of RFC 822 addressing. The quoted-string

form of local-part need not be supported. Standard UUCP mail

transfer falls into this category. Restricted RFC 822 is

undesirable, but in practice it exists in many places.

When a message is transferred from full RFC 822 to restricted RFC

822, and address forms used in full RFC 822 are involved, message

loss may occur (e.g., it may not be possible to return an error

message). This RFC describes a quoting mechanism which may be