Recommended Usage of the Authenticated Received Chain (ARC)
draft-jones-arc-usage-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | None , Steven M Jones , John Rae-Grant , J. Trent Adams , Kurt Andersen | ||
| Last updated | 2016-04-04 | ||
| Replaced by | draft-ietf-dmarc-arc-usage | ||
| 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-usage | |
| 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
The Authentication Received Chain (ARC) provides a means to preserve email authentication results and verify the identity of email message handlers, each of which participates by inserting certain header fields before passing the message on. But the specification does not indicate how intermediaries and receivers should interpret or utilize ARC. This document will provide guidance in these areas.
Authors
None
Steven M Jones
John Rae-Grant
J. Trent Adams
Kurt Andersen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)