RFC 4249 on Implementer-Friendly Specification of Message and MIME-Part Header Fields and Field Components
rfc-editor@rfc-editor.org Thu, 19 January 2006 01:18 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 1EzORM-0007v8-O5; Wed, 18 Jan 2006 20:18:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EzORL-0007uv-2r for ietf-announce@megatron.ietf.org; Wed, 18 Jan 2006 20:18:15 -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 UAA28379 for <ietf-announce@ietf.org>; Wed, 18 Jan 2006 20:16:48 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EzOZl-0007Wf-Rr for ietf-announce@ietf.org; Wed, 18 Jan 2006 20:26:58 -0500
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 k0J1HJi10036; Wed, 18 Jan 2006 17:17:19 -0800 (PST)
Message-Id: <200601190117.k0J1HJi10036@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: Wed, 18 Jan 2006 17:17:19 -0800
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: rfc-editor@rfc-editor.org
Subject: RFC 4249 on Implementer-Friendly Specification of Message and MIME-Part Header Fields and Field Components
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.
RFC 4249
Title: Implementer-Friendly Specification of Message and
MIME-Part Header Fields and Field Components
Author(s): B. Lilly
Status: Informational
Date: January 2006
Mailbox: blilly@erols.com
Pages: 14
Characters: 28731
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-lilly-field-specification-04.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc4249.txt
Implementation of generators and parsers of header fields requires
certain information about those fields. Interoperability is most
likely when all such information is explicitly provided by the
technical specification of the fields. Lacking such explicit
information, implementers may guess, and interoperability may suffer.
This memo identifies information useful to implementers of header
field generators and parsers.
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. 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