Re: WG Review: Domain-based Message Authentication, Reporting & Conformance (dmarc)

[Hector Santos <hsantos@xxxxxxxx>]

  References

  ----------

  DMARC - http://dmarc.org

  SPF - RFC7208

  DKIM - RFC6376

  Internet Message Format - RFC5322

  OAR / Original Authentication Results -

     draft-kucherawy-original-authres

  Using DMARC -  draft-crocker-dmarc-bcp-03

This is missing two citations that I thought were supposed to be
included, since they touch on indirect email flows:

  Delegating DKIM Signing Authority - draft-kucherawy-dkim-delegate-00
  DKIM Third-Party Authorization Label - draft-otis-dkim-tpa-label-03

Why not ATPS RFC6541 production?

http://tools.ietf.org/html/rfc6541

Consider ATPS the "lite version" of Doug's TPA. The same lookup hashing algorithm is used in both.  Further, there is real high quality commercial "running code" implementations supporting rfc6541.  All of our installations have DKIM+ADSP+ATPS out of the box with their primary domain used for automated first time setup plug and play readiness.

--

Hector Santos

http://www.santronics.com