DMARC verification without record definitions
draft-akagiri-dmarc-virtual-verification-01
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
---|---|---|---|
Authors | Genki Yasutaka , Takehito Akagiri , Masaki Kase , Kouji Okada , Kaoru Maeda | ||
Last updated | 2017-03-27 (Latest revision 2016-09-21) | ||
RFC stream | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
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
While DMARC is a powerful architecture to protect email users from malicious email activities, its deployment is still a work in progress. To encourage further adoption of DMARC, in this draft we propose an incremental deployment procedure.
Authors
Genki Yasutaka
Takehito Akagiri
Masaki Kase
Kouji Okada
Kaoru Maeda
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)