| CARVIEW |
Select Language
HTTP/2 200
date: Wed, 16 Jul 2025 13:46:16 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: 9601f1d6e9452e4c-BOM
alt-svc: h3=":443"; ma=86400
Information on RFC 4289 » RFC Editor
Search RFCs
BCP 13
RFC 4289
Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures, December 2005
- File formats:
- Status:
- BEST CURRENT PRACTICE
- Obsoletes:
- RFC 2048
- Authors:
- N. Freed
J. Klensin - Stream:
- IETF
- Source:
- NON WORKING GROUP
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC4289
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 4289
Abstract
This document specifies IANA registration procedures for MIME external body access types and content-transfer-encodings. This document specifies an Internet Best Current Practices for the Internet Community, and requests 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