Standardizing on IDNA 2003 in the URL Standard
Shawn.Steele at microsoft.com
Thu Aug 22 18:28:38 CEST 2013
> 2 [stay on 2003] as deployed is not stuck on an archaic Unicode version
I'm a tad confused there, there's no defined behavior for post 4.2 code points. So of those are mapped in 2008, so just passing them through doesn't really enable those users/scripts.
> Overall though I feel compatibility is downplayed way too much. It's very bad to break deployed content.
That's part of what TR46 tries to address.
More information about the Idna-update