Re: [Ietf-message-headers] Re: HTTP header registration question

On Sat, 29 Sep 2007 12:31:54 +0200, Martin Duerst <duerst@it.aoyama.ac.jp>  
wrote:
> At 18:58 07/09/29, Anne van Kesteren wrote:
> I suggest that you look at the IDNA RFCs if you want to get a definition
> of a label including non-ASCII characters. IDNA definitely deals with
> individual labels, because that's where punicode and the xn-- prefix
> and all that stuff happen.

Ah, it seems RFC 3490 defines "internationalized domain name" which can  
replace "subdomain" above. "internationalized label" can replace "label".  
Not sure why I didn't use those from the start. However, for HTTP it seems  
the ToASCII variant should be required (not just allowed) as HTTP doesn't  
do Unicode.

Thanks. Also thanks to Frank Ellerman for pointing out the limitation of  
HTTP that has escaped me (and the rest of the people reviewing; I begin to  
wonder how many there are...).

-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>

_______________________________________________
Ietf-message-headers mailing list
Ietf-message-headers@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-message-headers