Re: [idn] WG last call documents

["Eric A. Hall" <ehall@ehsco.com>]

"Adam M. Costello" wrote:
> 
> "Eric A. Hall" <ehall@ehsco.com> wrote:
> 
> > Please list the RFC822 header fields that IDNA should be
> > transliterated versus the header fields that should not be
> > transliterated.
> 
> When an application is displaying header fields to the user, it should
> apply ToUnicode to domain labels found in domain name slots.  RFC 822
> defines the syntax of every header field, and some of those fields have
> <domain> in their definition.  Those <domain>s are the domain name
> slots.  Anything else in the header is not a domain name slot.

Are you SURE you want to do this with Received? or rather, are you SURE
you want to mandate this behavior with Received on behalf of the other
communities, even though copy-and-paste with transliterated Received
headers will get ugly.

Does your list include all of those data-types which have domain names as
a subordinate element? I will assume that your list also includes "slots"
that hold email addresses since that is one of your other religious
doctrines, and since those hold domain names they are candidates.

Are URLs in header fields therefore also candidates? Are you SURE you want
to do this with List-* and Content-Location header fields?

Are message identifiers also candidates, since they are structured the
same as email addresses? Are you SURE you want to do this with Message-ID?

Sweeping rules that affect every instance of every domain name across
every network service in use on the Internet are absurd.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/