[DNSOP] summary of the discussion of draft-yao-dnsop-idntld-implementation-01.txt

"YAO Jiankang" <yaojk@cnnic.cn> Mon, 09 November 2009 00:56 UTC

Return-Path: <yaojk@cnnic.cn>
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8764F3A635F for <dnsop@core3.amsl.com>; Sun, 8 Nov 2009 16:56:57 -0800 (PST)
X-Quarantine-ID: <HIey7R8IRRQc>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: 1.955
X-Spam-Level: *
X-Spam-Status: No, score=1.955 tagged_above=-999 required=5 tests=[AWL=-0.603, BAYES_50=0.001, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MSGID_FROM_MTA_HEADER=0.803]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HIey7R8IRRQc for <dnsop@core3.amsl.com>; Sun, 8 Nov 2009 16:56:56 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id 8D7DC3A68E7 for <dnsop@ietf.org>; Sun, 8 Nov 2009 16:56:55 -0800 (PST)
Received: (eyou send program); Mon, 09 Nov 2009 08:57:21 +0800
Message-ID: <457728241.11384@cnnic.cn>
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown (HELO whatisfuture) (127.0.0.1) by 127.0.0.1 with SMTP; Mon, 09 Nov 2009 08:57:21 +0800
Message-ID: <028e01ca60d7$96af33a0$01125d85@whatisfuture>
From: YAO Jiankang <yaojk@cnnic.cn>
To: IETF DNSOP WG <dnsop@ietf.org>
Date: Mon, 09 Nov 2009 08:57:18 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_028B_01CA611A.A3F4BDD0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3598
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Subject: [DNSOP] summary of the discussion of draft-yao-dnsop-idntld-implementation-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Nov 2009 00:56:57 -0000

Dear all,

      the 01 version of draft (draft-yao-dnsop-idntld-implementation-01.txt)
introduces the problem of IDN TLD variants and 4 possible solutions to this problem:
1. put the dname into the root directly for the IDN TLD variant
2. Put the NS into the root for IDN TLD variant and apply the DNAME to All names in the Apex of delegated IDN TLD variant zone.
   there has only one DNAME record in the Apex of delegated IDN TLD variant zone in the form of "IDN TLD variant DNAME original IDN TLD".
3. Put the NS into the root for IDN TLD variant and apply the DNAME to some names which want to be dnamed.
4. Put the NS into the root for IDN TLD variant and apply the NS to some names which want to use NS.
this draft also introduces some policies related to the above solutions.

through the discussion in the DNSOP wg list and DNS-OARC meeting, many think that we should separate the technical issues from the 
policy issues in this draft. Many prefer the solution 1 (put the dname into the root directly for the IDN TLD variant); many can accept the solution 2 ( Put the NS into the root for IDN TLD variant and apply the DNAME to All names in the Apex of delegated IDN TLD variant zone.).
solution 3 and solution 4 may cause the potential data inconsistencies  in the IDN TLD variant zone since the policy can not be granted in all the levels.

thanks a lot to all for the kind comments from DNSOP and DNS-oarc.

the aim of this draft is to identify the problem and find the possible solutions.

based on my understanding, the WG seems to agree the following updatings to the draft if we hope it to be an item of WG:
1. suggest to use the solution 1 and 2 and analyze these 2 solutions.
  (the results of solution 1 and 2 are almost same. both apply dname to all names)
2. remove the solution 3 and 4
3. remove most contents about the policy


Yao Jiankang
CNNIC