Rationale and updated issues list
yone at jprs.co.jp
Mon Jul 28 20:24:23 CEST 2008
Dear John and all,
I think rationale issues list is good summary. Among them, I think
R.23 and R.24 are issues dealing with variety of contexts, languages
and/or scripts, and TLDs. And, the definitions of such mappings should
be defined and referred to by related entities who deals with IDNs.
Even though I admit the definitions reside outside of the protocol,
the protocol document should define appropriate repository for those
definitions as well as context registry, and make entities such as
application developers and registries to comply with them.
That is, protocol document should treat such definitions as its
complement. Otherwise, without clear definition, application
developers and registries can't implement appropriate handling such as
mappings, which I think it will cause incompatibility with IDNA2003
Yoshiro YONEYA <yone at jprs.co.jp>
On Mon, 28 Jul 2008 01:38:30 -0400 John C Klensin <klensin at jck.com> wrote:
> I'm attaching an updated version of the Rationale issues list
> and will be using it in this week's meetings. It is changed
> much less than the Protocol one was.
> I'm going to ask that the agenda be adjusted as needed to defer
> most discussion of Rationale until tomorrow in the hope that I
> can get a complete response to Marcos's comments and possible an
> interim document revision posted later today or tonight. Even
> if I do that, the draft will be very much interim -- it isn't
> possible to make much more progress on Rationale until we decide
> whether we are going to keep it (Issue R.1) or make it a major
> objective to move a lot of material out (part of Issue R.2).
More information about the Idna-update