BCP 13, RFC 4289 on Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures

RFC Editor <rfc-editor@rfc-editor.org> Mon, 12 December 2005 19:42 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EltZ0-0007wU-HW; Mon, 12 Dec 2005 14:42:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EltYy-0007vl-Ec for ietf-announce@megatron.ietf.org; Mon, 12 Dec 2005 14:42:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09270 for <ietf-announce@ietf.org>; Mon, 12 Dec 2005 14:41:23 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EltZl-0001Be-4f for ietf-announce@ietf.org; Mon, 12 Dec 2005 14:43:10 -0500
Received: from adma.isi.edu (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id jBCJev012525; Mon, 12 Dec 2005 11:40:57 -0800 (PST)
Received: (from rfc-ed@localhost) by adma.isi.edu (8.8.7/8.8.6) id TAA26903; Mon, 12 Dec 2005 19:40:57 GMT
Date: Mon, 12 Dec 2005 11:40:57 -0800
From: RFC Editor <rfc-editor@rfc-editor.org>
To: ietf-announce@ietf.org
Message-ID: <20051212194057.GF26290@isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: RFC Editor <rfc-editor@rfc-editor.org>
Subject: BCP 13, RFC 4289 on Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

A new Request for Comments is now available in online RFC libraries.


        BCP 13
        RFC 4289

        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@mrochek.com, klensin+ietf@jck.com
        Pages:      11
        Characters: 21502
        Obsoletes:  2048
        See Also:   BCP0013

        I-D Tag:    draft-freed-mime-p4-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4289.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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@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.

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce