Re: [regext] New-AD review of draft-ietf-regext-bundling-registration-09

Jiankang Yao <yaojk@cnnic.cn> Mon, 24 June 2019 10:17 UTC

Return-Path: <yaojk@cnnic.cn>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 003A1120114; Mon, 24 Jun 2019 03:17:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3P9T9snoBj5i; Mon, 24 Jun 2019 03:17:38 -0700 (PDT)
Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13]) by ietfa.amsl.com (Postfix) with ESMTP id A3B3E120090; Mon, 24 Jun 2019 03:17:37 -0700 (PDT)
Received: from [172.16.255.5] (unknown [159.226.7.2]) by ocmail02.zx.nicx.cn (Coremail) with SMTP id AQAAf0ApVq02oxBdgqJ2AA--.4381S2; Mon, 24 Jun 2019 18:17:30 +0800 (CST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: Jiankang Yao <yaojk@cnnic.cn>
X-Mailer: iPhone Mail (15G77)
In-Reply-To: <CALaySJK1PSK_O0CKSVGqk2PzXyYKhLm81fKv+5_Oago8Npu9ig@mail.gmail.com>
Date: Mon, 24 Jun 2019 11:17:23 +0100
Cc: draft-ietf-regext-bundling-registration.all@ietf.org, regext@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <62169347-F8F6-45FC-B368-5E6169CDE91D@cnnic.cn>
References: <CALaySJK1PSK_O0CKSVGqk2PzXyYKhLm81fKv+5_Oago8Npu9ig@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-CM-TRANSID: AQAAf0ApVq02oxBdgqJ2AA--.4381S2
X-Coremail-Antispam: 1UD129KBjvJXoW7WFykGw47tw47tF4DKF13CFg_yoW8AFWUp3 yaywsFkFnYyFn3Aws29a18ZFyjkrs7C3y5Zw1kGryUZa45W34xKFyFgFWjvFy7A395Za4q qr4FvrZY9r4UZaDanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUkYb7Iv0xC_KF4lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_JFI_Gr1l84ACjcxK6xII jxv20xvEc7CjxVAFwI0_Gr0_Cr1l84ACjcxK6I8E87Iv67AKxVW0oVCq3wA2z4x0Y4vEx4 A2jsIEc7CjxVAFwI0_GcCE3s1le2I262IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG64xvF2IE w4CE5I8CrVC2j2WlYx0E2Ix0cI8IcVAFwI0_Jr0_Jr4lYx0Ex4A2jsIE14v26r1j6r4UMc vjeVCFs4IE7xkEbVWUJVW8JwACjcxG0xvY0x0EwIxGrwCY02Avz4vE14v_Gw1l42xK82IY c2Ij64vIr41l4I8I3I0E4IkC6x0Yz7v_Jr0_Gr1lx2IqxVAqx4xG67AKxVWUJVWUGwC20s 026x8GjcxK67AKxVWUGVWUWwC2zVAF1VAY17CE14v26r1Y6r17MIIYrxkI7VAKI48JMIIF 0xvE2Ix0cI8IcVAFwI0_Jr0_JF4lIxAIcVC0I7IYx2IY6xkF7I0E14v26r1j6r4UMIIF0x vE42xK8VAvwI8IcIk0rVWrZr1j6s0DMIIF0xvEx4A2jsIE14v26r1j6r4UMIIF0xvEx4A2 jsIEc7CjxVAFwI0_Jr0_GrUvcSsGvfC2KfnxnUUI43ZEXa7IU8PPE3UUUUU==
X-CM-SenderInfo: x1dryyw6fq0xffof0/
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/zYPFC7rv-LVoC1ZckBrVr1EKnbo>
Subject: Re: [regext] New-AD review of draft-ietf-regext-bundling-registration-09
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2019 10:17:40 -0000

Dear Barry,

      Thanks a lot. We will update a new version based on your guidance.

Best Regards 
Jiankang Yao 

From my phone

> 在 2019年6月22日,02:28,Barry Leiba <barryleiba@computer.org> 写道:
> 
> Hey, regext folks,
> 
> This document had an AD review from Adam, a Gen-ART review from Joel,
> and a SecDir review from Russ, and went through IETF last call.  All
> three reviews were responded to on the regext mailing list (by
> Jiankang and by Antoine), but there has been no revision of the draft
> to address the issues raised.  That has to happen.
> 
> While we're there, there's the issue of the Informational status and
> the registrant contact for the namespace:
> 
> It's my understanding that this isn't specifying a standard, but,
> rather, is documenting an existing non-standard extension that is not
> expected to be a standard nor widely implemented.  Is that correct?
> 
> If so, the document should make that clear in the Abstract (briefly)
> and in the Introduction (somewhat less briefly).
> 
> Also, the shepherd writeup doesn't help me understand why this is
> Informational, and it should: (from the writeup text, emphasis mine)
> "Explain briefly what the intent of the document is (the document's
> abstract is usually good for this), and WHY THE WORKING GROUP HAS
> CHOSEN THE REQUESTED PUBLICATION TYPE".  You say the working group
> decided, but you don't say why.
> 
> So:
> Please revise the draft to address the last call reviews, and also
> please add something to the Introduction (and possibly the Abstract)
> to explain the status of the document, making clear what the standards
> or non-standards status is and what applicability we expect for it.
> 
> I'm putting this into a "Revised I-D Needed" substate, awaiting such revision.
> 
> Thanks,
> Barry