RFC 1499 (rfc1499) - Page 2 of 21
Summary of 1400-1499
Alternative Format: Original Text Document
RFC 1499 Summary of 1400-1499 January 1997
1497 Reynolds Aug 93 BOOTP Vendor Information Extensions
This RFC is a slight revision and extension of RFC-1048 by Philip
Prindeville, who should be credited with the original work in this memo.
This memo is a status report on the vendor information extensions used
in the Bootstrap Protocol (BOOTP).
1496 Alverstrand Aug 93 Rules for Downgrading Messages from
X.400/88 to X.400/84 When MIME
Content-Types are Present in the
Messages
This document describes how RFC-1328 must be modified in order to
provide adequate support for the scenarios:
SMTP(MIME) -> X.400(84)
X.400(84) -> SMTP(MIME)
It replaces chapter 6 of RFC-1328. The rest of RFC-1328 is NOT
obsoleted. [STANDARDS-TRACK]
1495 Alverstrand Aug 93 Mapping between X.400 and RFC-822
Message Bodies
Since the introduction of X.400(84), there has been work ongoing for
defining mappings between MHS and RFC-822. The most recent work in this
area is RFC-1327 [3], which focuses primarily on translation of envelope
and headers. This document is complimentary to RFC-1327 as it focuses
on translation of the message body. [STANDARDS-TRACK]
1494 Alverstrand Aug 93 Equivalences between 1988 X.400 and
RFC-822 Message Bodies
This document describes the content of the "IANA MHS/MIME Equivalence
table", and defines the initial configuration of this table. Mappings
for new MIME content-types and/or X.400 body part types should be
registered with the IANA to minimize redundancy and promote
interoperability. [STANDARDS-TRACK]
Elliott Informational