[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[idn] IDN refocus, v4
- To: IDN <idn@ops.ietf.org>
- Subject: [idn] IDN refocus, v4
- From: "Eric A. Hall" <ehall@ehsco.com>
- Date: Mon, 19 Nov 2001 15:52:19 -0600
- Organization: EHS Company
There is a stated need for a clearer focus on WG output. Although text was
requested, it seems that in order to effectively define the output goals,
we should come up with a set of core objectives that we can reach basic
agreement on. However, the objectives should be specified as practical
tangible results, rather than restrictions on implementation targets that
result in unintended consequences.
The list of objectives that I would start with are as follows (note that
this is not a vote, but a list of possible ballot items for a vote):
1) Define an internationalized domain name and host name syntax
for compliant protocols and applications to use.
[ ] yes
[ ] no
2) Define a seven-bit label encoding that legacy protocols and
applications can use to store and represent i18n domain names
as defined data.
[ ] yes
[ ] no
3) Define an UTF-8 label encoding that BCP18-compliant protocols
and applications can use to store and represent i18n domain
names as defined data.
[ ] yes
[ ] no
4) Provide proposals to DNSEXT for handling these label encodings
in the DNS service.
[ ] yes
[ ] no
5) Provide guidelines for the protocol and data-formatting groups
to use when they extend their services to tag, store, decipher
and/or display (as necessary) these encodings.
[ ] yes
[ ] no
n) others...?
We should be able to come to immediate agreement on 1 and 2. If the
existing proposals are not modified, items 4 and 5 will also have to be
done (item 4 is already done actually), even if it is not entirely obvious
to all of their advocates.
I would also suggest that any further attempts by interested third parties
to redefine the charter without a vote be summarily rejected.
--
Eric A. Hall http://www.ehsco.com/
Internet Core Protocols http://www.oreilly.com/catalog/coreprot/