Using Multiple Signing Algorithms with the ARC (Authenticated Received Chain) Protocol
draft-ietf-dmarc-arc-multi-03
| Document | Type | Expired Internet-Draft (dmarc WG) | |
|---|---|---|---|
| Last updated | 2019-09-08 (latest revision 2019-03-07) | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | Parked WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-dmarc-arc-multi-03.txt
Abstract
The Authenticated Received Chain (ARC) protocol creates a mechanism whereby a series of handlers of an email message can conduct authentication of the email message as it passes among them on the way to its destination. Initial development of ARC has been done with a single allowed signing algorithm, but parallel work in the DCRUP working group (https://datatracker.ietf.org/wg/dcrup/about/) is expanding the supported algorithms. This specification defines how to extend ARC for multiple signing algorithms.
Authors
Kurt Andersen
(kurta@linkedin.com)
Seth Blank
(seth@valimail.com)
John Levine
(standards@taugh.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)