Authenticated Received Chain (ARC)
draft-andersen-arc-05

Document Type Replaced Internet-Draft (individual)
Last updated 2016-05-23
Replaced by draft-ietf-dmarc-arc-protocol
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-dmarc-arc-protocol
Telechat date
Responsible AD (None)
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-andersen-arc-05.txt

Abstract

Authenticated Received Chain (ARC) permits an organization which is creating or handling email to indicate its involvement with the handling process. It defines a set of cryptographically signed header fields in a manner analagous to that of DKIM. Assertion of responsibility is validated through a cryptographic signature and by querying the Signer's domain directly to retrieve the appropriate public key. Changes in the message that might break DKIM can be identified through the ARC set of header fields.

Authors

None (arc-discuss@dmarc.org)
Kurt Andersen (kurta@linkedin.com)
John Rae-Grant (johnrg@google.com)
Brandon Long (blong@google.com)
J. Adams (trent.adams@paypal.com)
Steven Jones (smj@crash.com)

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