RFC 6729 on Indicating Email Handling States in Trace Fields

rfc-editor@rfc-editor.org Wed, 05 September 2012 21:24 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 843D321F86F6; Wed, 5 Sep 2012 14:24:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.985
X-Spam-Level:
X-Spam-Status: No, score=-101.985 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EsgZ5utyTC+v; Wed, 5 Sep 2012 14:24:46 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 2665C21F86F5; Wed, 5 Sep 2012 14:24:46 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B3E78B1E007; Wed, 5 Sep 2012 14:22:00 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6729 on Indicating Email Handling States in Trace Fields
From: rfc-editor@rfc-editor.org
Message-Id: <20120905212200.B3E78B1E007@rfc-editor.org>
Date: Wed, 5 Sep 2012 14:22:00 -0700 (PDT)
Cc: apps-discuss@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Sep 2012 21:24:46 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6729

        Title:      Indicating Email Handling States in 
                    Trace Fields 
        Author:     D. Crocker, M. Kucherawy
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2012
        Mailbox:    dcrocker@bbiw.net, 
                    superuser@gmail.com
        Pages:      12
        Characters: 24665
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-appsawg-received-state-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6729.txt

This document registers a trace field clause for use in indicating
transitions between handling queues or processing states, including
enacting inter- and intra-host message transitions.  This might
include message quarantining, mailing list moderation, timed
delivery, queuing for further analysis, content conversion, or other
similar causes, as well as optionally identifying normal handling
queues.  [STANDARDS-TRACK]

This document is a product of the Applications Area Working Group Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC