[dmarc-ietf] RFC 8617 on The Authenticated Received Chain (ARC) Protocol

rfc-editor@rfc-editor.org Wed, 10 July 2019 00:13 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 686411200C3; Tue, 9 Jul 2019 17:13:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id UkMl65av3t-e; Tue, 9 Jul 2019 17:13:19 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49F1C120098; Tue, 9 Jul 2019 17:13:19 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 939E6B8154E; Tue, 9 Jul 2019 17:13:16 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dmarc@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20190710001316.939E6B8154E@rfc-editor.org>
Date: Tue, 9 Jul 2019 17:13:16 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/-TJEAjrHEHyGSD3QMeUvZV5u-Uo>
Subject: [dmarc-ietf] =?utf-8?q?RFC_8617_on_The_Authenticated_Received_Ch?= =?utf-8?q?ain_=28ARC=29_Protocol?=
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jul 2019 00:13:22 -0000

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

        RFC 8617

        Title:      The Authenticated Received Chain (ARC) Protocol
        Author:     K. Andersen, 
                    B. Long, Ed., 
                    S. Blank, Ed., 
                    M. Kucherawy, Ed.
        Status:     Experimental
        Stream:     IETF
        Date:       July 2019
        Mailbox:    kurt+ietf@drkurt.com, 
        Pages:      35
        Characters: 70573
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dmarc-arc-protocol-23.txt

        URL:        https://www.rfc-editor.org/info/rfc8617

        DOI:        10.17487/RFC8617

The Authenticated Received Chain (ARC) protocol provides an
authenticated "chain of custody" for a message, allowing each entity
that handles the message to see what entities handled it before and
what the message's authentication assessment was at each step in the

ARC allows Internet Mail Handlers to attach assertions of message
authentication assessment to individual messages.  As messages
traverse ARC-enabled Internet Mail Handlers, additional ARC assertions
can be attached to messages to form ordered sets of ARC assertions
that represent the authentication assessment at each step of the
message-handling paths.

ARC-enabled Internet Mail Handlers can process sets of ARC assertions
to inform message disposition decisions, identify Internet Mail
Handlers that might break existing authentication mechanisms, and
convey original authentication assessments across trust boundaries.

This document is a product of the Domain-based Message Authentication, Reporting & Conformance Working Group of the IETF.

EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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