Re: [dnsext] [apps-discuss] APPSDIR review of draft-ietf-dnsext-dnssec-bis-updates-18

"Jiankang YAO" <yaojk@cnnic.cn> Thu, 21 June 2012 12:45 UTC

Return-Path: <yaojk@cnnic.cn>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03EDE21F85D9 for <dnsext@ietfa.amsl.com>; Thu, 21 Jun 2012 05:45:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.615
X-Spam-Level:
X-Spam-Status: No, score=-98.615 tagged_above=-999 required=5 tests=[AWL=-0.183, BAYES_40=-0.185, MIME_BASE64_TEXT=1.753, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qAAuo6jSq9yx for <dnsext@ietfa.amsl.com>; Thu, 21 Jun 2012 05:45:50 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by ietfa.amsl.com (Postfix) with SMTP id C468621F85DD for <dnsext@ietf.org>; Thu, 21 Jun 2012 05:45:48 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown127.0.0.1 (HELO lenovo47e041cf) (127.0.0.1) by 127.0.0.1 with SMTP; Thu, 21 Jun 2012 20:45:41 +0800
Message-ID: <9D782E7B4A4F42D5AB5B85C5D391B752@LENOVO47E041CF>
From: Jiankang YAO <yaojk@cnnic.cn>
To: Andrew Sullivan <ajs@crankycanuck.ca>, S Moonesamy <sm+ietf@elandsys.com>
References: <6.2.5.6.2.20120522092115.0900a4a0@elandnews.com> <20120619023034.GJ32683@crankycanuck.ca>
Date: Thu, 21 Jun 2012 20:45:36 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
Cc: iesg@ietf.org, apps-discuss@ietf.org, dnsext@ietf.org
Subject: Re: [dnsext] [apps-discuss] APPSDIR review of draft-ietf-dnsext-dnssec-bis-updates-18
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 12:45:51 -0000

----- Original Message ----- 
From: "Andrew Sullivan" <ajs@crankycanuck.ca>
To: "S Moonesamy" <sm+ietf@elandsys.com>
Cc: <iesg@ietf.org>; <draft-ietf-dnsext-dnssec-bis-updates.all@tools.ietf.org>; <apps-discuss@ietf.org>; <dnsext@ietf.org>
Sent: Tuesday, June 19, 2012 10:30 AM
Subject: Re: [apps-discuss] APPSDIR review of draft-ietf-dnsext-dnssec-bis-updates-18


> ......
>> There was an announcement that the DNSEXT WG would be shut down.
>> The rush to publish these clarifications raises questions about
>> whether the DNSSECbis documents will ever be advanced in the near
>> future from Proposed Standard to Internet Standard.
> 
> It is hard to see how there is a rush here.  The earliest version of
> this draft was submitted in 2005.  I know things have slowed down
> around the IETF, but I can't think of seven years as a rush.
> 

 SM does not mean seven years is a rush.
He mean that this draft survives almost 7 years and the draft has not clear clue of being ready to be published before announcement of DNSEXT WG shutting down.
Only after the announcement, someone said that this draft is ready for publication.
Many readers,  I think it is not only SM,  feel that there is a little surprise or unexpected.

From 0 month to 6 year and 11 month, there is no sign of ready.
From 6 year and 11 month to 6 year and 12 month, suddently say that "it is ready to go"

This is a rush, not 7 years as a rush.


If I understand SM correctly, I think That is why there is a rush.

Jiankang Yao