Re: [Gen-art] [regext] Genart last call review of draft-ietf-regext-bundling-registration-09

"Jiankang Yao" <> Fri, 15 March 2019 03:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 302341277CD; Thu, 14 Mar 2019 20:17:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id OTrF87WVq4oh; Thu, 14 Mar 2019 20:17:00 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id B28C7129524; Thu, 14 Mar 2019 20:16:58 -0700 (PDT)
Received: by (Coremail) ; Fri, 15 Mar 2019 11:16:54 +0800 (GMT+08:00)
X-Originating-IP: []
Date: Fri, 15 Mar 2019 11:16:54 +0800 (GMT+08:00)
X-CM-HeaderCharset: UTF-8
From: "Jiankang Yao" <>
To: "Joel Halpern via Datatracker" <>
X-Priority: 3
X-Mailer: Coremail Webmail Server Version XT3.0.8 dev build 20171117(fcd8b4ed) Copyright (c) 2002-2019 cnnic
In-Reply-To: <>
References: <>
X-SendMailWithSms: false
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset=UTF-8
MIME-Version: 1.0
Message-ID: <>
X-Coremail-Locale: zh_CN
X-CM-SenderInfo: x1dryyw6fq0xffof0/1tbiAQAKDSVCN5NS4gABs0
X-Coremail-Antispam: 1Ur529EdanIXcx71UUUUU7IcSsGvfJ3iIAIbVAYjsxI4VW3Jw CS07vEb4IE77IF4wCS07vE1I0E4x80FVAKz4kxMIAIbVAFxVCaYxvI4VCIwcAKzIAtYxBI daVFxhVjvjDU=
Archived-At: <>
Subject: Re: [Gen-art] [regext] Genart last call review of draft-ietf-regext-bundling-registration-09
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 15 Mar 2019 03:17:03 -0000

> -----原始邮件-----
> 发件人: "Joel Halpern via Datatracker" <>
> 发送时间: 2019-03-08 07:33:32 (星期五)
> 收件人:
> 抄送:,,
> 主题: [regext] Genart last call review of draft-ietf-regext-bundling-registration-09
> Reviewer: Joel Halpern
> Review result: Almost Ready
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
> For more information, please see the FAQ at
> <>.
> Document: draft-ietf-regext-bundling-registration-09
> Reviewer: Joel Halpern
> Review Date: 2019-03-07
> IETF LC End Date: 2019-03-15
> IESG Telechat date: Not scheduled for a telechat
> Summary: This document is almost ready for publication as some form of RFC

Thanks for your kind review.

> Major issues:
>     This document defines protocol extensions and mandatory procedures to go
>     with them.  As such, it seems it is either Experimental or Proposed
>     Standard, but not Informational.

This document was originally for proposed standard. After WG's discussion, the WG decides to move it as informational.

> Minor issues:
>     Section 5 consists of a list of behavioral requirements that appear
>     normative, but do not use RFC 2119 language.  If these are indeed normative
>     behavioral requirements, the document should use RFC 2119 language to be
>     clear.  (And therefore, should also include the text explaining and citing
>     RFC 2119.)

Yes, will update it.

>    The description in 7.2.1 of the EPP <create> command seems lacking.  After
>    saying that it needs an extension element, it says:
>         The <extension> element SHOULD contain a child <b-dn:create> element
>         that identifies the bundle namespace and the location of the bundle
>         name schema.
> It is unclear when it is reasonable to omit this <b-dn:create> element.  (We
> normally include with "SHOULD" explanations of this sort.) It is unspecified
> what format of the information in the <b-dn:create> element has.  I suspect
> that it is assumed to be the same as some other piece of EPP information, but
> it does not say so.  The only child element for <b-dn:create> given in the
> schema is the <b-dn:rdn> which is neither a namespace identifier nor a location
> of the bundle name schema.

Thanks. We will consider to update it.

>     Again in 7.2.2 on the EPP <delete> command, when discussing the addition to
>     the response, it is a SHOULD with no explanation of when it is okay to omit
>     it.  The same applies to the 7.2.3 EPP <renew> command, the 7.2.4 EPP
>     <transfer> command, and the 7.2.5 EPP <update> command.

Thanks. We will consider to change it to "MUST" or add some explanations.

Best Regards.

Jiankang Yao
> Nits/editorial comments:
> _______________________________________________
> regext mailing list