I-D ACTION:draft-chandhok-listid-04.txt
Internet-Drafts@ietf.org Wed, 24 March 1999 23:25 UTC
Received: by ietf.org (8.9.1a/8.9.1a) id SAA04216 for ietf-123-outbound.10@ietf.org; Wed, 24 Mar 1999 18:25:03 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01135 for <all-ietf@ietf.org>; Wed, 24 Mar 1999 17:02:46 -0500 (EST)
Message-Id: <199903242202.RAA01135@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-chandhok-listid-04.txt
Date: Wed, 24 Mar 1999 17:02:46 -0500
Sender: cclark@ns.cnri.reston.va.us
A New Internet-Draft is available from the on-line Internet-Drafts directories. Note: This revision reflects comments received during the last call period. Title : List-Id: A Structured Field and Namespace for the Identification of Mailing Lists Author(s) : R. Chandhok, G. Wenger Filename : draft-chandhok-listid-04.txt Pages : 6 Date : 23-Mar-99 Software that handles electronic mailing list messages (servers and user agents) needs a way to reliably identify messages that belong to a particular mailing list. With the advent of list management headers [RFC2369] it has become even more important to provide a unique identifier for a mailing list regardless of the particular host that serves as the list processor at any given time. The List-Id header provides a standard location for such an identifier. In addition, a namespace for list identifiers based on fully qualified domain names is described. This namespace is intended to guarantee uniqueness for list owners who require it, while allowing for a less rigorous namespace for experimental and personal use. By including the List-Id field, list servers can make it easier for mail clients to provide automated tools for users to perform list functions. The list identifier can serve as a key to make many automated processing tasks easier, and hence more widely available. The key words ''MUST'', ''MUST NOT'', ''REQUIRED'', ''SHALL'', ''SHALL NOT'', ''SHOULD'', ''SHOULD NOT'', ''RECOMMENDED'', ''MAY'', and ''OPTIONAL'' in this document are to be interpreted as described in RFC 2119. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-chandhok-listid-04.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-chandhok-listid-04.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-chandhok-listid-04.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.
- I-D ACTION:draft-chandhok-listid-04.txt Internet-Drafts