| CARVIEW |
Select Language
HTTP/2 200
date: Tue, 15 Jul 2025 19:30:50 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 95fbad35eaad860e-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 1026 » RFC Editor
Search RFCs
RFC 1026
Addendum to RFC 987: (Mapping between X.400 and RFC-822), September 1987
- File formats:
- Status:
- UNKNOWN
- Obsoleted by:
- RFC 2156, RFC 1327
- Updates:
- RFC 987
- Updated by:
- RFC 1138, RFC 1148
- Author:
- S.E. Kille
- Stream:
- [Legacy]
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC1026
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 1026
Abstract
This memo suggest a proposed protocol for the Internet community, and request discussion and suggestions for improvements.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us