On 5/7/2015 11:05 PM, Scott Kitterman wrote:
On Thursday, May 07, 2015 09:51:43 PM Hector Santos wrote:
On 5/7/2015 7:46 PM, Scott Kitterman wrote:
ATPS is assigned in the registry {1] as dkim-atps.
As stated already, the work predated what Murray did after ATPS rev04.
But its good to know that is this is the case and this is yet another
good reason to continue with ATPS work.
I'm really not sure what you're talking about (and equally not sure I need
to), but in version -00 of the ATPS draft it already had:
Method dkim-atps
Defined In [THIS MEMO]
ptype header
property from
If you want to document a ATPS result in an A-R header, there's a way to do it
and that's how it should be done.
Thanks for the "bug" report.
I should of stated it predated all of the ATPS work. Before ATPS,
there was Doug's TPA and my ASL (Allowed Signer List) which came from
the DSAP 2006 I-D. ATPS is a simpler version of TPA, uses the similar
base32(sha1()) hashing function logic for the sub-domain signer domain
label. ASL is a ADSP "asl=resigner-list" tag for the smaller scale
that can fit into a single UDP byte limit.
I should note this was all done when RFC5451 AUTH-RES was written.
Only DKIM and SPF recorded by this moving target specification. I
only recorded DKIM since SPF already had Received-SPF and DKIM was
still working on ADSP. AUTH-RES and I meant RFC5451, was still
incomplete and still a moving target. It was noted (a post/comment)
that it didn't cover the needs required.
It was all experimental and still early exploration. In any case,
thanks for the bug report.
--
HLS
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc
