[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] I-D ACTION:draft-ietf-idn-vidn-00.txt
- To: <email@example.com>,"Paul Hoffman / IMC" <firstname.lastname@example.org>
- Subject: Re: [idn] I-D ACTION:draft-ietf-idn-vidn-00.txt
- From: "Mark Davis" <email@example.com>
- Date: Thu, 16 Nov 2000 21:37:18 -0800
- Delivery-date: Thu, 16 Nov 2000 21:41:02 -0800
- Envelope-to: firstname.lastname@example.org
I agree completely.
a. There is no accepted set of rules for romanizations of all languages.
b. Moreover, to be useful according to the proposal, the romanization would
have to provide a "round-trip" mapping.
c. Furthermore, the romanizations will be subject to accidental collisions
between different scripts.
d. And finally, the mechanisms for doing romanization need to be fairly
sophisticated. Look at ICU's, for example:
(I'm replying to a slightly broader list on this message).
----- Original Message -----
From: "Paul Hoffman / IMC" <email@example.com>
Sent: Thursday, November 16, 2000 09:57
Subject: Re: [idn] I-D ACTION:draft-ietf-idn-vidn-00.txt
> This document has a patent statement at the end of the document, but
> nothing appears in the IETF IPR directory for it. If they haven't
> already done so, it would be a good first gesture for the authors to
> follow RFC 2026 and put their statement in the IETF repository.
> As a second comment, please note that there is wide disagreement
> about any single method for phonemic transformations from other
> languages to English. This document specifically covers Korean, for
> which there are at least two different romanization schemes in
> current use. For a perfect example of this, one of the contributors
> to this working group offers two different romanized spellings of his
> last and first names:
> GIM Gyeongseog
> KIM Kyongsok
> The draft proposes that every possible romanization using each
> possible phoneme be kept by the authoritative DNS server, and only
> one combined romanization can be returned. This assumes that the
> complete set of romanization tables is known today, and that the set
> will never grow. Both of these assumptions may be incorrect.
> Further, there is the legacy problem. For example, both kim.com and
> gim.com exist today. Even if the romanizaiton table problem can be
> solved, the names returned would have to be different than current
> names. Maybe the authors could use a prefix hack similar to the ones
> the ACE authors have saddled ourselves with.
> --Paul Hoffman, Director
> --Internet Mail Consortium
----- Original Message -----
Sent: Thursday, November 16, 2000 07:14
Subject: [idn] I-D ACTION:draft-ietf-idn-vidn-00.txt
> A New Internet-Draft is available from the on-line Internet-Drafts
> This draft is a work item of the Internationalized Domain Name Working
Group of the IETF.
> Title : Virtually Internationalized Domain Names (VIDN)
> Author(s) : S. Shim
> Filename : draft-ietf-idn-vidn-00.txt
> Pages : 9
> Date : 15-Nov-00
> This document describes a method that internationalizes existing as
> well as future domain names in English, not making any change to the
> current DNS, not requiring separate name server or resolver, and not
> creating domain names in non-English languages. Based upon the
> knowledge of transliteration between a local language and English,
> the method allows a user to use virtual domain names in the user's
> preferred local language by converting them into the corresponding
> actual domain names in English that comply with the current DNS. The
> conversion takes place automatically and transparently in the user's
> applications before DNS queries are sent. The method uses the current
> DNS as it is and meets all the requirements of internationalized
> domain names as described in Wenzel and Seng .
> A URL for this Internet-Draft is:
> Internet-Drafts are also available by anonymous FTP. Login with the
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> "get draft-ietf-idn-vidn-00.txt".
> A list of Internet-Drafts directories can be found in
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> Internet-Drafts can also be obtained by e-mail.
> Send a message to:
> In the body type:
> "FILE /internet-drafts/draft-ietf-idn-vidn-00.txt".
> NOTE: The mail server at ietf.org can return the document in
> MIME-encoded form by using the "mpack" utility. To use this
> feature, insert the command "ENCODING mime" before the "FILE"
> command. To decode the response(s), you will need "munpack" or
> a MIME-compliant mail reader. Different MIME-compliant mail readers
> exhibit different behavior, especially when dealing with
> "multipart" MIME messages (i.e. documents which have been split
> up into multiple messages), so check your local documentation on
> how to manipulate these messages.
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the