I think overall, there are two concerns I have:
1) The over estimated use of the idea for "rewriting" and
2) the word or term "common" is used for mitigation methods.
Common means most and its not the case. Rewriting is a major industry
taboo, in all mail or communications concept. Just because one or two
renegade MLM wrote a kludge for their site, puts it on a wiki, does
not make it legit at all, not one iota.
The doc infers that RFC6377 provides guidance, and it immediate jumps
to a Rewriting "common mitigation policy." Thats not right. In fact,
RFC6377 preaches ADSP or in general the DKIM Policy framework. I
don't support Rewriting, its not common, its not a BCP. It reeks with
IETF appeal problems. I don't think the doc should legitimize any
idea of rewriting.
Other comments...
The doc should make a note that DMARC is an informational status
domain. It is not a proposed standard nor a BCP. It is very
incomplete and it is missing lots of considerations. The 3rd party
issues was intentionally in an attempt to avoid a complex design
issue, but that it could not avoid.
The doc fails to mention technical history with SSP ADSP, ATPS, or any
of the RFC documents products such as:
rfc4686 Analysis of Threats Motivating DKIM
rfc5016 Requirements for a DKIM Signing Practices Protocol
rfc5518 Vouch By Reference
rfc5863 DKIM Development, Deployment, and Operations
and possibly others.
The docs should explain why ADSP was abandoned and why its "Super
ADSP" [sic] version called DMARC replaced it.
--
HLS
On 4/28/2015 7:49 PM, Franck Martin wrote:
FYI
Please post more reviews...
-----------------
A new version of I-D, draft-ietf-dmarc-interoperability-02.txt
has been successfully submitted by Franck Martin and posted to the
IETF repository.
Name: draft-ietf-dmarc-interoperability
Revision: 02
Title: Interoperability Issues Between DMARC and Indirect Email Flows
Document date: 2015-04-28
Group: dmarc
Pages: 20
URL:
https://www.ietf.org/internet-drafts/draft-ietf-dmarc-interoperability-02.txt
Status: https://datatracker.ietf.org/doc/draft-ietf-dmarc-interoperability/
Htmlized: https://tools.ietf.org/html/draft-ietf-dmarc-interoperability-02
Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-dmarc-interoperability-02
Abstract:
DMARC introduces a mechanism for expressing domain-level policies and
preferences for email message validation, disposition, and reporting.
The DMARC mechanism can encounter interoperability issues when
messages do not flow directly from the author's administrative domain
to the final recipients. Collectively these email flows are referred
to as indirect email flows. This document describes interoperability
issues between DMARC and indirect email flows. Possible methods for
addressing interoperability issues are presented.
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
The IETF Secretariat
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc
