[rfc-dist] BCP 13, RFC 4289 on Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures
rfc-editor at rfc-editor.org
Mon Dec 12 11:40:30 PST 2005
A new Request for Comments is now available in online RFC libraries.
Title: Multipurpose Internet Mail Extensions (MIME)
Part Four: Registration Procedures
Author(s): N. Freed, J. Klensin
Status: Best Current Practice
Date: December 2005
Mailbox: ned.freed at mrochek.com, klensin+ietf at jck.com
See Also: BCP0013
I-D Tag: draft-freed-mime-p4-07.txt
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. Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
More information about the rfc-dist