RFC 2919: List-Id: A Structured Field and Namespace for the Identification of Mailing Lists
In plain English — editorial summary, not part of the RFC
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, 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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2919
- Published
- March 2001
- Authors
- R. Chandhok; G. Wenger
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 28775250 Telnet EnhancementsObsoleted
July 2000
- RFC 2869RADIUS ExtensionsUpdated
June 2000
- RFC 2868RADIUS Attributes for Tunnel Protocol SupportUpdated
June 2000
- RFC 2847LIPKEY - A Low Infrastructure Public Key Mechanism Using SPKMCurrent
June 2000
- RFC 2730Multicast Address Dynamic Client Allocation Protocol (MADCAP)Current
December 1999
- RFC 2701Nortel Networks Multi-link Multi-node PPP Bundle Discovery ProtocolCurrent
September 1999
- RFC 2696LDAP Control Extension for Simple Paged Results ManipulationCurrent
September 1999
- RFC 2649An LDAP Control and Schema for Holding Operation SignaturesCurrent
August 1999
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?