I quickly read this surprising one. <br>Can somebody point me where the proposed changes are? May be replace 2008 by 2009 too?<br>Does this affect the current WG/LC?<br>Thank you !<br>Potrzamparc.<br><br><div class="gmail_quote">
2009/8/18 IESG Secretary <span dir="ltr"><<a href="mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
A modified charter has been submitted for the Internationalized Domain<br>
Names in Applications, Revised (idnabis) working group in the Applications<br>
Area of the IETF. The IESG has not made any determination as yet. The<br>
modified charter is provided below for informational purposes only.<br>
Please send your comments to the IESG mailing list (<a href="mailto:iesg@ietf.org">iesg@ietf.org</a>) by<br>
Tuesday, August 25, 2009.<br>
<br>
Internationalized Domain Names in Applications, Revised (idnabis)<br>
-------------------------------<br>
Last Modified: 2009-08-10<br>
<br>
Additional information is available at <a href="http://tools.ietf.org/wg/idnabis" target="_blank">tools.ietf.org/wg/idnabis</a><br>
<br>
Chair(s):<br>
- Vinton Cerf <<a href="mailto:vint@google.com">vint@google.com</a>><br>
<br>
Applications Area Director(s):<br>
- Lisa Dusseault <<a href="mailto:lisa.dusseault@gmail.com">lisa.dusseault@gmail.com</a>><br>
- Alexey Melnikov <<a href="mailto:alexey.melnikov@isode.com">alexey.melnikov@isode.com</a>><br>
<br>
Applications Area Advisor:<br>
- Lisa Dusseault <<a href="mailto:lisa.dusseault@gmail.com">lisa.dusseault@gmail.com</a>><br>
<br>
Mailing Lists:<br>
General Discussion: <a href="mailto:idna-update@alvestrand.no">idna-update@alvestrand.no</a><br>
To Subscribe: <a href="http://www.alvestrand.no/mailman/listinfo/idna-update" target="_blank">http://www.alvestrand.no/mailman/listinfo/idna-update</a><br>
Archive: <a href="http://www.alvestrand.no/pipermail/idna-update/" target="_blank">http://www.alvestrand.no/pipermail/idna-update/</a><br>
<br>
Description of Working Group:<br>
The original Internationalized Domain Name (IDN) WG specified rules for<br>
the use of characters other than Latin A(a)-Z(z), digits 0-9 and the<br>
hyphen (-) in domain names in RFC3490, RFC3491 and RFC3492 in 2002<br>
(published in 2003 and often referenced collectively as "IDNA2003").<br>
<br>
These documents depend on RFC 3454 and were tied to Unicode version<br>
3.2. An update to the current version (5.x) is required to accommodate<br>
additional scripts. In addition, experience has shown that significant<br>
improvements could be made in the protocol as presently specified.<br>
<br>
This WG is chartered to decouple IDNA from specific versions of Unicode<br>
using algorithms that define validity based on Unicode properties. It<br>
is recognized that some explicit exceptions may be necessary in any<br>
case, but attempts will be made to minimize these exceptions.<br>
<br>
Additional goals:<br>
<br>
- Separate requirements for valid IDNs at registration time (insertion<br>
of names into DNS zone files), vs. at resolution time (looking up those<br>
names)<br>
- Review, and if necessary revise, the algorithms and rules for<br>
handling right to left character sequences in an IDN context to allow<br>
labels based on additional scripts and languages and to make presentation<br>
as predictable as reasonably possible.<br>
- Permit use of some scripts that were inadvertently excluded by the<br>
original protocols.<br>
- Ensure practical stability of validity algorithms for IDNs.<br>
<br>
The constraints of the original IDN WG still apply to IDNABIS, namely<br>
to avoid disturbing the current use and operation of the domain name<br>
system, and for the DNS to continue to allow any system to resolve any<br>
domain name in a consistent way. The client-based approach of the<br>
original IDN work will be maintained -- substantially new protocols or<br>
mechanisms are not in scope. In particular, IDNs continue to use the<br>
"xn--" prefix and the same ASCII-compatible encoding, and the<br>
bidirectional algorithm follows the same basic design.<br>
<br>
The specifications are initially organized as four documents: overview<br>
and rationale, protocol, table algorithm, and improvements to the<br>
bidirectional algorithm. These documents are to be used as the basis<br>
for the discussion of the general direction of the work.<br>
<br>
This working group will be providing extended public review of the<br>
output of a design team that has been working on improvement of the<br>
IDNA specifications.<br>
<br>
This review-based approach is being used in part because of the way the<br>
work was undertaken by the team; in particular, the design team has<br>
been working with IETF visibility and has solicited and received<br>
significant amounts of technical review already from IETF participants<br>
and from others including experts in the Unicode specifications and the<br>
use of scripts in languages. If the public review provided by this<br>
Working Group confirms the basic method outlined in the input documents,<br>
it is expected that the working group will be able to respond with any<br>
needed changes and close in a short period of time. If technical issues<br>
arise that indicate a fundamentally different approach must be taken<br>
from the one outlined above, it is anticipated that this working group<br>
would close, and a new one with an appropriate charter would be<br>
considered.<br>
<br>
This work is intended to specify an improved means to produce and use<br>
stable and unambiguous IDN identifiers.<br>
<br>
There are a variety of generally unsolvable problems, notably the<br>
problem of characters that are confusingly similar in appearance (often<br>
known as the "phishing" problem) that are not specifically part of the<br>
scope of the WG although some of the preliminary results of the design<br>
team suggest that the improvements contemplated in the specifications<br>
might mitigate some of the ways in which the current IDNA specifications<br>
can be abused for phishing purposes.<br>
<br>
While it is referenced from the original IDNA2003 package, the original<br>
Stringprep specification, RFC 3454, is not formally part of the IDNA<br>
package and will not be altered by this work.<br>
<br>
The work will update or obsolete RFC 3490. It is not expected to<br>
continue to use Nameprep (RFC 3491). Nameprep is used by other<br>
specifications; determining how (or whether) to update those<br>
specifications and, consequently, the long-term status of Nameprep,<br>
are not part of this effort. The method for ASCII-compatible ("ACE")<br>
encoding of IDNs, "Punycode" (RFC 3492) will not be revised by this WG.<br>
<br>
Subject to the more general constraints described above, the WG is<br>
permitted to consider changes that are not strictly backwards-<br>
compatible. For any such change that is recommended, it is expected to<br>
document the reasons for the change, the characters affected, and<br>
possible transition strategies.<br>
<br>
The assumptions outlined above are considered critical to the WG<br>
constituted by this charter. The WG will stop work and recommend that<br>
a new charter be generated if it concludes that any of the following are<br>
necessary to meet its goals:<br>
<br>
(i) A change to the "punycode" algorithm or to the ACE approach to<br>
encoding names in the DNS.<br>
(ii) A change to the ACE prefix from "xn--"<br>
(iii) A change to the basic approach taken in the design team<br>
documents (Namely: independence from Unicode version and reduction of<br>
dependency on character mapping )<br>
<br>
Goals and Milestones:<br>
Apr 2008 WG formation<br>
May 2008 Decision on form and structure of the WG document set<br>
Sep 2008 WG Last Call on WG document set<br>
Nov 2008 IETF Last Call on WG document set<br>
_______________________________________________<br>
Idna-update mailing list<br>
<a href="mailto:Idna-update@alvestrand.no">Idna-update@alvestrand.no</a><br>
<a href="http://www.alvestrand.no/mailman/listinfo/idna-update" target="_blank">http://www.alvestrand.no/mailman/listinfo/idna-update</a><br>
</blockquote></div><br>