draft-ietf-appsawg-received-state-02.txt   draft-ietf-appsawg-received-state-03.txt 
Individual submission D. Crocker Individual submission D. Crocker
Internet-Draft Brandenburg InternetWorking Internet-Draft Brandenburg InternetWorking
Intended status: Standards Track M. Kucherawy Intended status: Standards Track M. Kucherawy
Expires: December 23, 2012 Cloudmark, Inc. Expires: December 25, 2012 Cloudmark, Inc.
June 21, 2012 June 23, 2012
Indicating Email Handling States in Trace Fields Indicating Email Handling States in Trace Fields
draft-ietf-appsawg-received-state-02 draft-ietf-appsawg-received-state-03
Abstract Abstract
This memo registers a trace field clause for use in indicating This memo registers a trace field clause for use in indicating
transitions between handling queues or processing states, including transitions between handling queues or processing states, including
enacting inter- and intra-host message transitions. This might enacting inter- and intra-host message transitions. This might
include message quarantining, mailing list moderation, timed include message quarantining, mailing list moderation, timed
delivery, queueing for further analysis, content conversion, or other delivery, queueing for further analysis, content conversion, or other
similar causes, as well as optionally identifying normal handling similar causes, as well as optionally identifying normal handling
queues. queues.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 23, 2012. This Internet-Draft will expire on December 25, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 4, line 44 skipping to change at page 4, line 44
outbound: The message entered a queue for outbound relaying. This outbound: The message entered a queue for outbound relaying. This
is typically the last case added for a single host, and the next is typically the last case added for a single host, and the next
Received header field is expected to be added by some other host. Received header field is expected to be added by some other host.
quarantine: The message entered a hold in an isolation queue pending quarantine: The message entered a hold in an isolation queue pending
operator action for local policy reasons. operator action for local policy reasons.
timed: The message entered a hold in order to meet a requested timed: The message entered a hold in order to meet a requested
delivery window, such as is defined in [FUTURERELEASE]. delivery window, such as is defined in [FUTURERELEASE].
The ABNF for this clause: The "state" clause is added in Section 6 to the Additional-
Registered-Clauses IANA sub-registry. The ABNF for this clause is:
State = CFWS "state" FWS queue-state-keyword *( "/" value ) State = CFWS "state" FWS queue-state-keyword *( "/" value )
queue-state-keyword = ( reg-state-keyword / unreg-state-keyword ) queue-state-keyword = ( reg-state-keyword / unreg-state-keyword )
reg-state-keyword = ( "auth" / "content" / "convert" / reg-state-keyword = ( "auth" / "content" / "convert" /
"moderation" / "normal" / "other" / "moderation" / "normal" / "other" /
"outbound" / "quarantine" / "timed" / "outbound" / "quarantine" / "timed" /
additional-state-keyword ) additional-state-keyword )
additional-state-keyword = unstructured additional-state-keyword = unstructured
; see "IANA Considerations" below ; see "IANA Considerations" below
value = unstructured value = token
unreg-state-keyword = unstructured unreg-state-keyword = token
"unstructured", "FWS" and "CFWS" are defined in [MAIL] "FWS" and "CFWS" are defined in [MAIL]. "token" is defined in [MIME].
A transfer agent making use of this extension MAY also include header A transfer agent making use of this extension MAY also include header
field comments to provide additional information. field comments to provide additional information.
The "value" is available for providing additional labels as The "value" is available for providing additional labels as
explanation for the state transition. Examples could include: explanation for the state transition. Examples could include:
o convert/unicode2ascii o convert/unicode2ascii
o moderation/not-subscribed o moderation/not-subscribed
skipping to change at page 9, line 12 skipping to change at page 9, line 12
[IANA] Narten, T. and H. Alvestrand, "Guidelines for [IANA] Narten, T. and H. Alvestrand, "Guidelines for
Writing an IANA Considerations Section in RFCs", Writing an IANA Considerations Section in RFCs",
BCP 26, RFC 5226, May 2008. BCP 26, RFC 5226, May 2008.
[KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate [KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[MAIL] Resnick, P., "Internet Message Format", RFC 5322, [MAIL] Resnick, P., "Internet Message Format", RFC 5322,
October 2008. October 2008.
[MIME] Freed, N. and N. Borenstein, "Simple Mail Transfer
Protocol", RFC 2045, November 1996.
[SMTP] Klensin, J., "Simple Mail Transfer Protocol", [SMTP] Klensin, J., "Simple Mail Transfer Protocol",
RFC 5321, October 2008. RFC 5321, October 2008.
8.2. Informative References 8.2. Informative References
[FUTURERELEASE] White, G. and G. Vaudreuil, "SMTP Submission Service [FUTURERELEASE] White, G. and G. Vaudreuil, "SMTP Submission Service
Extension for Future Message Release", RFC 4865, Extension for Future Message Release", RFC 4865,
May 2007. May 2007.
Appendix A. Trace Field Examples Appendix A. Trace Field Examples
 End of changes. 8 change blocks. 
8 lines changed or deleted 12 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/