I discovered today as I attempted to submit the ARC protocol update that I've been working on, that the submission system closed about 40 hours earlier - sigh.
Since I'm headed to Ecuador for a three week vacation with unknown and/or unlikely Internet access, I have created a git repo and posted the source (kramdown) and rendered xml, txt, html versions for both the protocol and usage documents at https://github.com/kurta/arc-docs Once the submissions system opens and I have internet access, I will get the official submission completed; but until then, you can see the updates at: http://tools.ietf.org/rfcdiff?url1=https://tools.ietf.org/id/draft-ietf-dmarc-arc-protocol-01.txt&url2=https://raw.githubusercontent.com/kurta/arc-docs/master/dmarc-arc-protocol-02.txt (obviously the date will have to change further) Here are the key changes I added (based on input from the list and discussion during the interop in February): 1) Removed the attempts to repair any problems in the ARC chain beyond simple ordering problems, added cv=invalid 2) Added section 5.4 to discuss phases for transitioning signature algorithms 3) Updated length of chain? (section 5.1.1.1.1) at least 10, may be up to 50; may mark invalid above that Also as discussed in the interop, I did not add any additional requirements in ARC regarding key lengths. I will be submitting an update to the DKIM spec itself to fork both the key length and signing algorithms into a registry which can then be managed without requiring further spec updates. --Kurt
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
