idnits 2.17.1 draft-chandhok-listid-04.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 2919 5 Title: List-Id: A Structured Field and Namespace for the 6 Identification of Mailing Lists 7 Author(s): R. Chandhok, G. Wenger 8 Status: Standards Track 9 Date: March 2001 10 Mailbox: chandhok@within.com, wenger@within.com 11 Pages: 9 12 Characters: 18480 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-chandhok-listid-04.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc2919.txt 19 Software that handles electronic mailing list messages (servers 20 and user agents) needs a way to reliably identify messages that 21 belong to a particular mailing list. With the advent of list 22 management headers, it has become even more important 23 to provide a unique identifier for a mailing list regardless of 24 the particular host that serves as the list processor at any 25 given time. 27 The List-Id header provides a standard location for such an 28 identifier. In addition, a namespace for list identifiers 29 based on fully qualified domain names is described. This 30 namespace is intended to guarantee uniqueness for list owners 31 who require it, while allowing for a less rigorous namespace 32 for experimental and personal use. 34 By including the List-Id field, list servers can make it easier 35 for mail clients to provide automated tools for users to 36 perform list functions. The list identifier can serve as a key 37 to make many automated processing tasks easier, and hence more 38 widely available. 40 This is now a Proposed Standard Protocol. 42 This document specifies an Internet standards track protocol for 43 the Internet community, and requests discussion and suggestions 44 for improvements. Please refer to the current edition of the 45 "Internet Official Protocol Standards" (STD 1) for the 46 standardization state and status of this protocol. Distribution 47 of this memo is unlimited. 49 This announcement is sent to the IETF list and the RFC-DIST list. 50 Requests to be added to or deleted from the IETF distribution list 51 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 52 added to or deleted from the RFC-DIST distribution list should 53 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 55 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 56 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 57 help: ways_to_get_rfcs. For example: 59 To: rfc-info@RFC-EDITOR.ORG 60 Subject: getting rfcs 62 help: ways_to_get_rfcs 64 Requests for special distribution should be addressed to either the 65 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 66 specifically noted otherwise on the RFC itself, all RFCs are for 67 unlimited distribution.echo 68 Submissions for Requests for Comments should be sent to 69 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 70 Authors, for further information.