[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] Comments on protocol drafts
- To: C C Magnus Gustavsson <mag@lysator.liu.se>, idn@ops.ietf.org
- Subject: Re: [idn] Comments on protocol drafts
- From: James Seng <jseng@pobox.org.sg>
- Date: Tue, 08 Feb 2000 13:41:39 +0800
- Delivery-date: Mon, 07 Feb 2000 21:43:39 -0800
- Envelope-to: idn-data@psg.com
I agreed with the requirement on the guidence part.
But I do not think restricting character set or encoding is a good idea. We
never know what other people are doing out there and we do not want to isolate
them. Every implementation and proposal we get is a valuable lesson we can
learn (from their experience and their problem) which will be useful should
IETF decide to do a standard track in future.
I do not believe having a requirement to deny them to even propose their
solution to the IETF is fair and in the interest of the WG. Denying them a
chance to work with IETF will only make them shun away and go on their own
path.
-James Seng
C C Magnus Gustavsson wrote:
>
> > Does the WG wants to specify and restrict the character set (or the
> > behavior of the encodig) of the possible implementation of IDN in the
> > requirement?
>
> "1. An Informational RFC specifying the requirements for providing
> Internationalized access to domain names. The document
> should provide guidance for development solutions to this problem,
> taking localized (e.g. writing order) and related operational issues
> into consideration."
>
> If you agree on the requirement itself, don't you think it's a pretty
> important and relevant guidance?
>
> /Magnus