[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[idn] other suggestions for req



mostly clarifications.

------------
rewrite this:

[12] This document RECOMMENDS Unicode only. If multiple charsets are
allowed, each charset MUST be tagged and conform to [RFC2277].

to:

[12] codepoints SHOULD be from the Universal Set as defined in ISO-10646 or 
Unicode. The specifics of versions MUST be defined in the proposed 
solution.  If multiple charsets are allowed, each charset
MUST be tagged and conform to [RFC2277].
------------

rewrite this:

[15] The protocol SHOULD NOT make any assumptions about the location in
a domain name where internationalization might appear. In other words,
it SHOULD NOT differentiate between any part of a domain name because
this MAY impose restrictions on future internationalization efforts.

to:

[15] The protocol SHOULD NOT make any assumptions about the location in
a domain name where internationalization might appear. In other words,
it SHOULD NOT differentiate between any part of a domain name because
this MAY impose restrictions on future internationalization efforts. For
example, the TLDs can be internationalized.

Marc Blanchet
Viagénie inc.
tel: 418-656-9254
http://www.viagenie.qc.ca

----------------------------------------------------------
Normos (http://www.normos.org): Internet standards portal:
IETF RFC, drafts, IANA, W3C, ATMForum, ISO, ... all in one place.