List-Id: A Structured Field and Namespace for the Identification of Mailing Lists
draft-moonesamy-rfc2919bis-04

Document Type Expired Internet-Draft (individual in app area)
Authors S Moonesamy  , Geoffrey Wenger  , Ravinder Chandhok 
Last updated 2015-10-14 (latest revision 2012-02-19)
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state Expired (IESG: Dead)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Pete Resnick
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-moonesamy-rfc2919bis-04.txt

Abstract

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 header fields, it has become even more important to provide a unique identifier for a mailing list regardless of the particular host that runs the mailing list manager at any given time. The List-Id header field provides a standard location for such an identifier. In addition, a namespace for mailing 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, mailing list managers can make it easier for mail user agents to provide automated tools for users to perform mailing list functions. The mailing list identifier can serve as a key for automated processing tasks

Authors

S Moonesamy (sm+ietf@elandsys.com)
Geoffrey Wenger (gwenger@qualcomm.com)
Ravinder Chandhok (chandhok@qualcomm.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)