Re: [ietf-dkim] Comments on draft-ietf-dkim-rfc4871bis-02

> > RFC 3490 is obsolete, replaced by 5890 and 5891. When they rewrote it 
> > they made the language descriptive rather than prescriptive, and an 
> > A-label is the new name for what was the output of ToASCII.
> My understanding is that they actually changed the behavior of the 
> 'subroutine'.  Nothing in the switch to 5322 from 2822 changes any behaviors 
> for DKIM.
Of course it does.  The message syntax in 5322 is ever so slightly 
different from 2822, so the set of valid messages over which DKIM is 
defined is slightly different, too.  It didn't change very much, but 5890 
didn't change very much either.  It mostly tightened up rules for 
rejecting invalid input, got rid of dependencies on a particular version 
of Unicode, and fixed a few arcane bugs.
> The toAscii routine still works for us.
Sort of.  IDN2008 handles more recent versions of Unicode than IDN2003 
does and allows some joiner characters that IDN2003 ignored, so ToAscii 
willl fail on some valid current IDNs.
I see that on the IDNA list they're arguing about this exact issue for a 
revision of http cookies, so I guess that whatever they do, we can do.
Regards,
John Levine, johnl(_at_)iecc(_dot_)com, Primary Perpetrator of "The Internet for 
Dummies",
Please consider the environment before reading this e-mail. http://jl.ly

smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
NOTE WELL: This list operates according to 
http://mipassoc.org/dkim/ietf-list-rules.html