BCP 90, RFC 3864 on Registration Procedures for Message Header Fields
rfc-editor@rfc-editor.org Sat, 18 September 2004 01:05 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23699; Fri, 17 Sep 2004 21:05:42 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C8TkU-0001mS-Sa; Fri, 17 Sep 2004 21:11:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C8TU6-0006GS-WA; Fri, 17 Sep 2004 20:53:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C8TOr-0004xA-3o for ietf-announce@megatron.ietf.org; Fri, 17 Sep 2004 20:48:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22599 for <ietf-announce@ietf.org>; Fri, 17 Sep 2004 20:48:23 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C8TTw-0001Pj-Mw for ietf-announce@ietf.org; Fri, 17 Sep 2004 20:54:05 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i8I0jJJ11121; Fri, 17 Sep 2004 17:45:19 -0700 (PDT)
Message-Id: <200409180045.i8I0jJJ11121@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 17 Sep 2004 17:45:19 -0700
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Cc: rfc-editor@rfc-editor.org
Subject: BCP 90, RFC 3864 on Registration Procedures for Message Header Fields
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
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
A new Request for Comments is now available in online RFC libraries.
BCP 90
RFC 3864
Title: Registration Procedures for Message Header Fields
Author(s): G. Klyne, M. Nottingham, J. Mogul
Status: Best Current Practice
Date: September 2004
Mailbox: GK-IETF@ninebynine.org, mnot@pobox.com,
JeffMogul@acm.org
Pages: 17
Characters: 36231
SeeAlso: BCP 90
I-D Tag: draft-klyne-msghdr-registry-07.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3864.txt
This specification defines registration procedures for the message
header fields used by Internet mail, HTTP, Netnews and other
applications.
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