Internet DRAFT - draft-moonesamy-list-sequence-header
draft-moonesamy-list-sequence-header
Individual Submission S. Moonesamy
Internet-Draft February 20, 2012
Intended status: Standards Track
Expires: August 23, 2012
List-Sequence header field for mailing lists
draft-moonesamy-list-sequence-header-00
Abstract
The List-Sequence header field provides a standard location for
identifying the sequence position of an individual message for a
mailing list.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 23, 2012.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Moonesamy Expires August 23, 2012 [Page 1]
Internet-Draft List-Sequence header field February 2012
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Syntax Notation . . . . . . . . . . . . . . . . . . . . . . 3
1.3. Note . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. List-Sequence Header Field . . . . . . . . . . . . . . . . . . 3
3. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
6. Normative References . . . . . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5
Moonesamy Expires August 23, 2012 [Page 2]
Internet-Draft List-Sequence header field February 2012
1. Introduction
The List-Sequence header field provides a standard location for a
sequence identifier identifying the sequence position of an
individual message for a mailing list.
1.1. Terminology
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 [RFC2119].
1.2. Syntax Notation
This specification uses the Augmented Backus-Naur Form (ABNF)
[RFC5234] notation for the formal definitions of the syntax of list
header fields.
1.3. Note
This Internet-Draft can be discussed on the apps-discuss@ietf.org
mailing list. [RFC-Editor: please remove this paragraph]
2. List-Sequence Header Field
The List-Sequence header field provides a Sequence Identifier for
each message sent to a mailing list. While this is often expressed
as an integer, it is not constrained to be so. Nor is it constrained
to fit into a 31- or 32-bit integer when it is an integral value.
The Sequence Identifier SHOULD be unique within a mailing list.
There MUST NOT be more than one List-Sequence header field in any
given message.
Syntax:
seq-id = 1*atext
list-sequence = "List-Sequence:" seq-id CRLF
Examples:
List-Sequence: 5
Moonesamy Expires August 23, 2012 [Page 3]
Internet-Draft List-Sequence header field February 2012
List-Sequence: S25
3. Security Considerations
If a mailing list manager encounters a List-Sequence header fields
from any unexpected source it SHOULD NOT pass them through to the
mailing list.
4. IANA Considerations
The following is the registration template to add the List-Sequence
header field to the Permanent Message Header Field Names registry:
Header field name: List-Sequence
Applicable protocol: mail ([RFC5322])
Status: Standard
Author/Change controller: IETF
Specification document(s): RFC XXXX [RFC Editor: please replace
XXXX with this RFC number]
5. Acknowledgements
Tony Hansen suggested standardizing the List-Sequence header field
and contributed to this document.
6. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322,
October 2008.
Moonesamy Expires August 23, 2012 [Page 4]
Internet-Draft List-Sequence header field February 2012
Author's Address
S. Moonesamy
76, Ylang Ylang Avenue
Quatre Bornes
Mauritius
Email: sm+ietf@elandsys.com
Moonesamy Expires August 23, 2012 [Page 5]
