Recommended Usage of the Authenticated Received Chain (ARC)
draft-ietf-dmarc-arc-usage-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Steven M Jones , John Rae-Grant , J. Trent Adams , Kurt Andersen | ||
| Last updated | 2016-12-27 (Latest revision 2016-06-25) | ||
| Replaces | draft-jones-arc-usage | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
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.)