Why is draft-ietf-dmarc-eaiauth-03 on the Standards Track?
Because it updates RFCs 6376 and 7208, which are draft standards.
RFC 6376 is an Internet Standard. It may make matters complicated in future
if that specification has to be revised. I'll comment about RFC 7208 below.
In this case I defer to the AD and the IESG. If they want to put it on a
different track, it's OK with me, but it seems fairly obvious that you
update standards track documents with other standards track documents.
Yes. Sorry, I missed that. The local-part is imported from RFC 5321. There
was some discussion about the issue in 2012. The "updates" does not seem EAI
specific.
It refers to "non-ASCII characters"? If you have non-ASCII characters and
purport to be following IETF standards, it's EAI.
Because it does. See the second paragraph of section 6. The existing 7489
language in several places that says "the domain name must be converted to
an A-label" is wrong since mail addresses don't contain single label
domains.
There are other (reported) technical issues with that RFC. I gather that the
DMARC working group is not interested in fixing that specification.
That horse left the barn several years ago. I am not crazy about DMARC
but the current spec is very widely implemented and isn't going to change
in any way that isn't backward compatible.
Regards,
John Levine, johnl@xxxxxxxxx, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly
