Proposed Charter for the IDNAbis Working Group
Vint Cerf <vint@google.com> Wed, 26 March 2008 11:09 UTC
Return-Path: <vint@google.com>
X-Original-To: idna-update@alvestrand.no
Delivered-To: idna-update@alvestrand.no
Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 9E919259753 for <idna-update@alvestrand.no>; Wed, 26 Mar 2008 12:09:48 +0100 (CET)
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03321-04 for <idna-update@alvestrand.no>; Wed, 26 Mar 2008 12:09:33 +0100 (CET)
X-Greylist: domain auto-whitelisted by SQLgrey-1.6.7
Received: from smtp-out.google.com (smtp-out.google.com [216.239.33.17]) by eikenes.alvestrand.no (Postfix) with ESMTP id 637CA25974F for <idna-update@alvestrand.no>; Wed, 26 Mar 2008 12:09:33 +0100 (CET)
Received: from zps78.corp.google.com (zps78.corp.google.com [172.25.146.78]) by smtp-out.google.com with ESMTP id m2QB9R4N027480 for <idna-update@alvestrand.no>; Wed, 26 Mar 2008 11:09:28 GMT
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1206529768; bh=XhX4RirvuLzFZ5DXtEWsANepCqw=; h=DomainKey-Signature:Mime-Version:Content-Transfer-Encoding: Message-Id:Content-Type:To:From:Subject:Date:X-Mailer; b=vtV+xdSPx Tq6o8EuTrP5VFVvC9AdLWQegj7qBeCUtM2iJY2LtXzxSYDT8WSCZPhHiBfu19fah92O xAWj1jeAlA==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=received:mime-version: content-transfer-encoding:message-id:content-type:to:from:subject:date:x-mailer; b=dnLzY7gUxlo3OYTitLvRbD+8z0SoWldKAKoQGXh/4o1aqHFu2BfM3/QETJ5PSz9Pg RyLzN9rTZbR3hLc89XIsg==
Received: from smtp.corp.google.com (spacemonkey1.corp.google.com [192.168.120.115]) by zps78.corp.google.com with ESMTP id m2QB9OUP031266 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <idna-update@alvestrand.no>; Wed, 26 Mar 2008 04:09:26 -0700
Received: from [172.30.9.199] ([212.99.101.200]) (authenticated bits=0) by smtp.corp.google.com (8.13.8/8.13.8) with ESMTP id m2QB9LXA011788 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <idna-update@alvestrand.no>; Wed, 26 Mar 2008 03:09:23 -0800
Mime-Version: 1.0 (Apple Message framework v753)
Content-Transfer-Encoding: quoted-printable
Message-Id: <5C5BF097-5507-4B0E-A752-367AE060FD39@google.com>
Content-Type: text/plain; charset="ISO-8859-1"; delsp="yes"; format="flowed"
To: idna-update@alvestrand.no
From: Vint Cerf <vint@google.com>
Date: Wed, 26 Mar 2008 07:08:52 -0400
X-Mailer: Apple Mail (2.753)
X-Virus-Scanned: by amavisd-new at alvestrand.no
Subject: Proposed Charter for the IDNAbis Working Group
X-BeenThere: idna-update@alvestrand.no
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IDNA update work <idna-update.alvestrand.no>
List-Unsubscribe: <http://www.alvestrand.no/mailman/listinfo/idna-update>, <mailto:idna-update-request@alvestrand.no?subject=unsubscribe>
List-Archive: <http://www.alvestrand.no/pipermail/idna-update>
List-Post: <mailto:idna-update@alvestrand.no>
List-Help: <mailto:idna-update-request@alvestrand.no?subject=help>
List-Subscribe: <http://www.alvestrand.no/mailman/listinfo/idna-update>, <mailto:idna-update-request@alvestrand.no?subject=subscribe>
X-List-Received-Date: Wed, 26 Mar 2008 11:09:49 -0000
Ladies and gentlemen, on the basis of the several weeks of exchanges on this list, a draft charter for the IDNAbis Working Group has emerged. It is enclosed below and as the proposed chair, I ask the participants in the IDNA- update distribution list to confirm adoption of the charter. If there are no strong objections, I request that Area Directors Lisa Dusseault and Chris Newman put the charter forward to the IESG for its approval. Needless to say, I am grateful to all of you who have contributed to the production of this charter in the past several weeks, most particularly john klensin, paul hoffman, martin duerst, patrik fältström, mark davis, harald alvestrand, stephane bortzmeyer, erik van der poel, jefsey morfin, simon josefsson, lisa dusseault, among many others. Apologies if I missed adding your name to the list - it was starting to get kind of long. I look forward to what I hope will be rapid progress of this working group towards the production of RFCs documenting improvements to the IDNA protocols. Vint Cerf ------------- IDNABIS Charter Chair(s): Vinton G. Cerf Applications Area Directors: Lisa Dusseault (ldusseault@commerce.net) Chris Newman (Chris.Newman@sun.com) Applications Area Advisor: Lisa Dusseault (ldusseault@commerce.net) Mailing List: General Discussion: idna-update@alvestrand.no To Subscribe: http://www.alvestrand.no/mailman/listinfo/idna-update Archive: http://www.alvestrand.no/pipermail/idna-update/ Description: The original Internationalized Domain Name (IDN) WG set the requirements for international characters in domain names in RFC3490, RFC3491 and RFC3492 in 2002 (published in 2003). These documents depend on RFC 3454 and were tied to Unicode version 3.2. An update to the current version (5.x) is required to accommodate additional scripts. In addition, experience has shown a number of real or perceived defects or inadequacies with the protocol. This WG is chartered to untie IDNA from specific versions of Unicode using algorithms that define validity based on Unicode properties. It is recognized that some explicit exceptions may be necessary in any case, but attempts would be made to minimize these exceptions. Additional goals: - Separate requirements for valid IDNs at registration time (insertion of names into DNS zone files), vs. at resolution time (looking up those names) - Review, and, as necessary revise, the algorithms and rules for handling right to left character sequences in an IDN context to allow labels based on additional scripts and languages and to make presentation as predictable as reasonably possible. - Permit effective use of some scripts that were inadvertently excluded by the original protocols. - Ensure practical stability of validity algorithms for IDNs. The constraints of the original IDN WG still apply to IDNABIS, namely to avoid disturbing the current use and operation of the domain name system, and for the DNS to continue to allow any system to resolve any domain name in a consistent way. The basic approach of the original IDN work will be maintained -- substantially new protocols or mechanisms are not in scope. In particular, IDNs continue to use the "xn--" prefix and the same ASCII-compatible encoding, and the bidirectional algorithm follows the same basic design. The work is initially organized as four documents: overview and rationale, protocol, table algorithm, and changes to the bidirectional algorithm. These documents are to be used as the basis for the discussion of the general direction of the work. This working group will be providing extended public review of the output of a design team that has been working on the issues described below. This review-based approach is being used in part because of the way the work was undertaken by the team; in particular, the design team has been working with IETF visibility and has solicited and received significant amounts of technical review already. If the public review provided by this Working Group confirms the basic method outlined in the input documents, it is expected that the working group will be able to provide any needed changes and close in a short period of time. If technical issues arise that indicate a fundamentally different approach must be taken, it is anticipated that this working group would close, and a new one with an appropriate charter would be considered. This work will address stable and unambiguous IDN identifiers. There are a variety of unsolvable problems, notably the problem of characters that are confusingly similar in appearance (often known as the "phishing" problem) that are not part of the scope of the WG. While it is referenced from the original IDNA package, the original Stringprep specification, RFC 3454, is not formally part of the IDNA package and will not be altered by this work. The work will update or obsolete RFC 3490. It is not expected to continue to use Nameprep (RFC 3491). Nameprep is used by other specifications; determining how (or whether) to update those specifications and, consequently, the long-term status of Nameprep, are not part of this effort. The method for ASCII-compatible ("ACE") encoding of IDNs, "Punycode" (RFC 3492) will not be revised by this WG. Subject to the more general constraints described above, the WG is permitted to consider changes that are not strictly backwards-compatible. For any such change that is recommended, it is expected to document the reasons for the change, the characters affected, and possible transition strategies. The assumptions outlined above are considered critical to the WG constituted this charter. The WG will stop, close, and recommend that a new charter be generated if it concludes that any of the following are necessary to meet its goals: (i) A change to the "punycode" algorithm or to the ACE approach to encoding names in the DNS. (ii) A change to the ACE prefix from "xn--" (iii) A change to the basic approach taken in the design team documents (Namely: a protocol that is independent of Unicode versions, that removes any character mapping in the protocol, and that has improvements to the bidi algorithm). Goals and milestones: Apr 08: WG formation May 08: Decision on form and structure of the WG document set Sep 08: WG Last Call on WG document set Nov 08: IETF Last Call on WG document set Documents: http://tools.ietf.org/html/draft-klensin-idnabis-issues http://tools.ietf.org/html/draft-klensin-idnabis-protocol http://tools.ietf.org/html/draft-faltstrom-idnabis-tables http://tools.ietf.org/html/draft-alvestrand-idna-bidi ---------------------
- Re: Proposed Charter for the IDNAbis Working Group Simon Josefsson
- Re: Proposed Charter for the IDNAbis Working Group Vint Cerf
- Proposed Charter for the IDNAbis Working Group Vint Cerf
- Re: Proposed Charter for the IDNAbis Working Group Gervase Markham
- Re: Proposed Charter for the IDNAbis Working Group Vint Cerf
- Re: Proposed Charter for the IDNAbis Working Group Gervase Markham
- Re: Proposed Charter for the IDNAbis Working Group Vint Cerf
- Re: Proposed Charter for the IDNAbis Working Group John C Klensin
- Re: Proposed Charter for the IDNAbis Working Group Andrew Sullivan
- Re: Proposed Charter for the IDNAbis Working Group Mark Davis
- Re: Proposed Charter for the IDNAbis Working Group Paul Hoffman
- Re: Proposed Charter for the IDNAbis Working Group Shawn Steele
- Re: Proposed Charter for the IDNAbis Working Group Martin Duerst
- Re: Proposed Charter for the IDNAbis Working Group Martin Duerst
- Re: Proposed Charter for the IDNAbis Working Group Martin Duerst
- Re: Proposed Charter for the IDNAbis Working Group Gervase Markham
- Re: Proposed Charter for the IDNAbis Working Group John C Klensin
- Re: Proposed Charter for the IDNAbis Working Group Paul Hoffman
- Symbols and Line-drawing (was: Re: Proposed Chart… John C Klensin
- Re: Proposed Charter for the IDNAbis Working Group Paul Hoffman
- Re: Proposed Charter for the IDNAbis Working Group John C Klensin
- Re: Proposed Charter for the IDNAbis Working Group Vint Cerf
- Re: Proposed Charter for the IDNAbis Working Group John C Klensin
- Re: Proposed Charter for the IDNAbis Working Group Paul Hoffman
- Re: Proposed Charter for the IDNAbis Working Group Mark Davis
- Re: Proposed Charter for the IDNAbis Working Group John C Klensin
- Re: Proposed Charter for the IDNAbis Working Group Vint Cerf
- Re: Proposed Charter for the IDNAbis Working Group John C Klensin
- RE: Proposed Charter for the IDNAbis Working Group Shawn Steele
- Re: Proposed Charter for the IDNAbis Working Group Vint Cerf
- Removing symbols (was: RE: Proposed Charter for t… John C Klensin
- Re: Proposed Charter for the IDNAbis Working Group Martin Duerst
- Re: Symbols and Line-drawing (was: Re: Proposed C… Martin Duerst
- Re: Proposed Charter for the IDNAbis Working Group Leslie Daigle
- Re: Proposed Charter for the IDNAbis Working Group Martin Duerst