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

Barry Leiba <barryleiba@computer.org> Fri, 13 September 2019 01:21 UTC

Return-Path: <barryleiba@gmail.com>
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 E0E7F1200E3; Thu, 12 Sep 2019 18:21:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level:
X-Spam-Status: No, score=-1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.026, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 Gq5nx25_202J; Thu, 12 Sep 2019 18:21:18 -0700 (PDT)
Received: from mail-io1-f47.google.com (mail-io1-f47.google.com [209.85.166.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39DA312002E; Thu, 12 Sep 2019 18:21:15 -0700 (PDT)
Received: by mail-io1-f47.google.com with SMTP id f4so58718891ion.2; Thu, 12 Sep 2019 18:21:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=XUuX9n5L0TOCqgY3EL9zJ2QQ2BysLU/hv97jy4KWBHQ=; b=IcxURQpA4IO4kj1ua8B+nnMqqJiULavFsXJ/DvvNtIlwvj/FetH/pk+wUCL13zWouf n6JiUXkQcqg5Ln1JG1gleZ/tV76Ru6zuvhAg9uyHNJadjvFBxLIMPFGsYIZxi33DbM2N 0xmnql5hLb/dZNbMkdaRt0Ppa6TLHFhw9OnhzN9k/B34KroCCoqPGg3/jawIp+fancwj VzBdmAh4P4X7EO71kxdIUOlAPk2mtF28PjEPb0DU1l+kzUhJpp9QFxhT7eKTbEmKMu/S ddonnvNKmzdPc47RMAu4PefQrJZwpPbH8/1p3dnjtgRqn751KuZniOxTjNR5D54DplEj IT5w==
X-Gm-Message-State: APjAAAUkS9PO6J5CQ1mRr47hZmhBdbWb+krMmDLQhtQasmgkXMGDXDlp b6hqIVIqqJ/V3OhpYqg4vs/U1VfpY4KWqhiowbOgvA==
X-Google-Smtp-Source: APXvYqwUq4J6w/AkyyJ6/Pz8MZQ56FN9JWe1rxZTLaMkMeGoduRB5KhN7Ue2FjRLt7KaifwQc/184Pw8vexslhyLyDw=
X-Received: by 2002:a6b:1787:: with SMTP id 129mr8513931iox.140.1568337674291; Thu, 12 Sep 2019 18:21:14 -0700 (PDT)
MIME-Version: 1.0
References: <CALaySJK1PSK_O0CKSVGqk2PzXyYKhLm81fKv+5_Oago8Npu9ig@mail.gmail.com> <62169347-F8F6-45FC-B368-5E6169CDE91D@cnnic.cn>
In-Reply-To: <62169347-F8F6-45FC-B368-5E6169CDE91D@cnnic.cn>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 12 Sep 2019 21:21:02 -0400
Message-ID: <CALaySJLhY3K5QPFPtPM_h0zzGTG2bKqZR7Hjq-UG-M5Dmbc7Pg@mail.gmail.com>
To: Jiankang Yao <yaojk@cnnic.cn>
Cc: draft-ietf-regext-bundling-registration.all@ietf.org, regext@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/zfwGikLu6Br6-xNtw0cc1aHzZCo>
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: Fri, 13 Sep 2019 01:21:20 -0000

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

It's been almost 12 weeks.  Is a new version forthcoming?  When can we
expect it?

Barry

> > 在 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