Confirming Consensus IETF 74

Vint Cerf vint at google.com
Fri Mar 27 22:42:45 CET 2009


I don't need more confirmation on line, really. But it is important to know if there is any disagreement with this apparent consensus. V

----- Original Message -----
From: idna-update-bounces at alvestrand.no <idna-update-bounces at alvestrand.no>
To: idna-update at alvestrand.no <idna-update at alvestrand.no>
Sent: Fri Mar 27 12:30:51 2009
Subject: RE: Confirming Consensus IETF 74

I'd just like to state that I agree with this direction.  I have a comment about a point, but I'll disambiguate that from the "confirming consensus" thread :)

This is the 2nd mail asking for confirmation of this direction, but there's been very little discussion.  What is needed to enshrine this as the planned direction?

-Shawn

-----Original Message-----
Date: Wed, 25 Mar 2009 08:22:30 -0400
From: Vint Cerf <vint at google.com>
Subject: Confirming Consensus IETF 74
To: idna-update at alvestrand.no

Mark Davis has already sent out a brief note outlining a consensus
reached in the IETF 74 meeting.

In rough terms, the idea is to continue to revise and finalize the
IDNA2008 documents and to add to them a mapping function for look up
only:

1. Use the IDNA2008 document set as the base
2. Do NO MAPPING in the registration phase of IDNs
3. Apply an IDNA2003-like mapping function on lookup for compatibility
with IDNs previously registered under IDNA2003 rules

The WG now needs to specify:

1. what set of characters will be mapped and into what?
2. When will this mapping function be applied

The current protocol spec has an appendix in which a two-lookup method
is suggested. If an non-mapping look up fails, then the IDNA2003-like
mapping function would be applied and another look up attempted. there
are other possible implementations, of course.

This note is to confirm online the consensus reached at IETF74 to move
along these lines.

WG members and document editors are encouraged to elaborate on this
proposal and to attempt to reach closure expeditiously.

vint


Vint Cerf
Google
1818 Library Street, Suite 400
Reston, VA 20190
202-370-5637
vint at google.com


_______________________________________________
Idna-update mailing list
Idna-update at alvestrand.no
http://www.alvestrand.no/mailman/listinfo/idna-update


More information about the Idna-update mailing list