Authenticated Received Chain (ARC)
draft-andersen-arc-05
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | None , Kurt Andersen , John Rae-Grant , Brandon Long , J. Trent Adams , Steven M Jones | ||
| Last updated | 2016-05-23 | ||
| Replaced by | draft-ietf-dmarc-arc-protocol | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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 | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Kurt Andersen
John Rae-Grant
Brandon Long
J. Trent Adams
Steven M Jones
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)