Re: [regext] Benjamin Kaduk's Discuss on draft-ietf-regext-org-ext-09: (with DISCUSS and COMMENT)

"Linlin Zhou" <zhoulinlin@cnnic.cn> Wed, 14 November 2018 02:30 UTC

Return-Path: <zhoulinlin@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 5EDF8130E10; Tue, 13 Nov 2018 18:30:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 PgitYnFSI1f1; Tue, 13 Nov 2018 18:30:51 -0800 (PST)
Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13]) by ietfa.amsl.com (Postfix) with ESMTP id 49E4A130DE0; Tue, 13 Nov 2018 18:30:47 -0800 (PST)
Received: from zll (unknown [218.241.111.73]) by ocmail02.zx.nicx.cn (Coremail) with SMTP id AQAAf0BJUKDNiOtbGxUDAA--.2127S2; Wed, 14 Nov 2018 10:30:37 +0800 (CST)
Date: Wed, 14 Nov 2018 10:32:11 +0800
From: "Linlin Zhou" <zhoulinlin@cnnic.cn>
To: "Benjamin Kaduk" <kaduk@mit.edu>
Cc: regext-chairs <regext-chairs@ietf.org>, "Pieter Vandepitte" <pieter.vandepitte@dnsbelgium.be>, iesg <iesg@ietf.org>, regext <regext@ietf.org>, draft-ietf-regext-org-ext <draft-ietf-regext-org-ext@ietf.org>
References: <20181031010506.GY45914@kduck.kaduk.org>, <20181031141945204989108@cnnic.cn>, <20181031124321.GH45914@kduck.kaduk.org>, <2018110111280976085295@cnnic.cn>, <20181101222859.GH45914@kduck.kaduk.org>, <B567C9E4-BF56-4BB0-8081-27264947C1F7@verisign.com>, <201811060918110034890@cnnic.cn>, <2018111211152341848066@cnnic.cn>, <20181112194852.GE99562@kduck.kaduk.org>, <2018111309283308613641@cnnic.cn>, <20181113150617.GI99562@kduck.kaduk.org>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 5, 136[cn]
Mime-Version: 1.0
Message-ID: <201811141032104571327@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart284022640753_=----"
X-CM-TRANSID: AQAAf0BJUKDNiOtbGxUDAA--.2127S2
X-Coremail-Antispam: 1UD129KBjvAXoWfJr17AFyfArykGr13ury3Arb_yoW8Jr4DXo WfXwsxArs3tw1rAr4qka1DKa4DXa48uw1rJF4IqryDGwsIqwsFkw1rZ3Wqq3y3JrZ7W34U Jas8J3yDZ39Fq3Wfn29KB7ZKAUJUUUUU529EdanIXcx71UUUUU7v73VFW2AGmfu7bjvjm3 AaLaJ3UjIYCTnIWjp_UUUYX7k0a2IF6w4xM7kC6x804xWl14x267AKxVWUJVW8JwAFc2x0 x2IEx4CE42xK8VAvwI8IcIk0rVWrJVCq3wAFIxvE14AKwVWUJVWUGwA2ocxC64kIII0Yj4 1l84x0c7CEw4AK67xGY2AK021l84ACjcxK6xIIjxv20xvE14v26ryj6F1UM28EF7xvwVC0 I7IYx2IY6xkF7I0E14v26F4j6r4UJwA2z4x0Y4vEx4A2jsIE14v26r4UJVWxJr1l84ACjc xK6I8E87Iv6xkF7I0E14v26F4UJVW0owAS0I0E0xvYzxvE52x082IY62kv0487Mc02F40E 42I26xC2a48xMcIj6xIIjxv20xvE14v26r1j6r18McIj6I8E87Iv67AKxVWUJVW8JwAm72 CE4IkC6x0Yz7v_Jr0_Gr1lF7xvr2IYc2Ij64vIr41lFcxC0VAYjxAxZF0Ew4CEw7xC0wAC Y4xI67k04243AVC20s07MxkIecxEwVAFwVW8JwCF04k20xvY0x0EwIxGrwCFx2IqxVCFs4 IE7xkEbVWUJVW8JwC20s026c02F40E14v26r106r1rMI8I3I0E7480Y4vE14v26r106r1r MI8E67AF67kF1VAFwI0_JF0_Jw1lIxkGc2Ij64vIr41lIxAIcVC0I7IYx2IY67AKxVWUJV WUCwCI42IY6xIIjxv20xvEc7CjxVAFwI0_Jr0_Gr1lIxAIcVCF04k26cxKx2IYs7xG6rW3 Jr0E3s1lIxAIcVC2z280aVAFwI0_Jr0_Gr1lIxAIcVC2z280aVCY1x0267AKxVWUJVW8Jw CE64xvF2IEb7IF0Fy7YxBIdaVFxhVjvjDU0xZFpf9x07jnl19UUUUU=
X-CM-SenderInfo: p2kr3zplqox0w6fq0xffof0/
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/-4q1mvx0lKPbSA6Mv4bTsQ5iq8Y>
Subject: Re: [regext] Benjamin Kaduk's Discuss on draft-ietf-regext-org-ext-09: (with DISCUSS and COMMENT)
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: Wed, 14 Nov 2018 02:30:56 -0000

Hi Benjamin,
I think the last issue was clarified as well. I will settle down to update the drafts to address all the comments. Thanks for your review and comments.

Regards,
Linlin


Linlin Zhou
 
From: Benjamin Kaduk
Date: 2018-11-13 23:06
To: Linlin Zhou
CC: regext-chairs; Pieter Vandepitte; iesg; regext; draft-ietf-regext-org-ext
Subject: Re: [regext] Benjamin Kaduk's Discuss on draft-ietf-regext-org-ext-09: (with DISCUSS and COMMENT)
Hi Linlin,
 
I likewise forgot to look at the list archives for the HTML version.
The proposed changes (from
https://www.ietf.org/mail-archive/web/regext/current/msg01984.html) look
good to me.
 
Thanks,
 
Benjamin
 
On Tue, Nov 13, 2018 at 09:28:34AM +0800, Linlin Zhou wrote:
> Hi Benjamin,
> Sorry that I forgot your email is text/plain.
> Since we'v e already define "one or more <orgext:id> elements" in each <orgext:add>, <orgext:rem> and <orgext:chg> element. So the following text seems a little duplicated and will be removed. I add the text strikethrough and you may not find that.
> 
> The <orgext:add>, <orgext:rem> and <orgext:chg> elements contain the following child element:
>  o One or more <orgext:id> elements that contain the identifier of the organization. The "role" attribute is used to represent the relationship that the organization has to the object. See Section 7.3 in [ID.draft-ietf-regext-org] for a list of values.
> 
> This bullet will be removed from section 4.2.5. (May last email add one more sentence "Any given object MUST have at most one associated organization ID for any given role value" by mistake and this should not exist). How about changing like this?
> 
> Regards,
> Linlin
> 
> 
> Linlin Zhou
>  
> From: Benjamin Kaduk
> Date: 2018-11-13 03:48
> To: Linlin Zhou
> CC: regext-chairs; Pieter Vandepitte; iesg; regext; draft-ietf-regext-org-ext
> Subject: Re: [regext] Benjamin Kaduk's Discuss on draft-ietf-regext-org-ext-09: (with DISCUSS and COMMENT)
> Hi Linlin,
>  
> On Mon, Nov 12, 2018 at 11:15:24AM +0800, Linlin Zhou wrote:
> > Dear Benjamin,
> > James provided his suggestions and I'd like to include them in the updated text. I think this is the last issue we have and please see if these changes workable for you.
>  
> I think this looks good, thank you!  Just one minor thing (in the same vein
> as my comment just now on the companion document)...
>  
> > 1. In section 3.1 Organization Identifier, add sentences at the end of this paragraph. 
> > A "role" attribute is used to represent the relationship that the organization has to the EPP object. Any given object MUST have at most one associated organization ID for any given role value. 
> > 
> > 2. In section 4.1.2,
> > Zero or more <orgext:id> elements are allowed that contain the identifier of the organization, as defined in [section 3.1]. The "role" attribute is used to represent the relationship that the organization has to the object. See Section 7.3 in [ID.draft-ietf-regext-org] for a list of values.
> > 
> > 3. In section 4.2.1, 
> > One or more <orgext:id> elements that contain the identifier of the organization, as defined in [section 3.1]. The "role" attribute is used to represent the relationship that the organization has to the object. See Section 7.3 in [ID.draft-ietf-regext-org] for a list of values. 
> > 
> > 4. In section 4.2.5,
> >  o  An OPTIONAL <orgext:add> element that contains one or more <orgext:id> elements, as defined in [section 3.1], that add non-existent organization roles to the object. The <orgext:id> element MUST have a non-empty organization identifier value.  The server SHOULD validate that the <orgext:id> element role does not exist. 
> >  
> >    o  An OPTIONAL <orgext:rem> element that contains one or more <orgext:id> elements, as defined in [section 3.1], that remove organization roles from the object. The <orgext:id> element MAY have an empty organization identifier value.  The server SHOULD validate the existence of the <orgext:id> element role and the organization identifier if provided. 
> >  
> >    o  An OPTIONAL <orgext:chg> element that one or more <orgext:id> elements, as defined in [section 3.1], that change organization role identifiers for the object. The existing organization identifier value will be replaced for the defined role.  The server SHOULD validate the existence of the <orgext:id> element role. 
> > 
> > At least one <orgext:add>, <orgext:rem> or <orgext:chg> element MUST be provided. The <orgext:add>, <orgext:rem> and <orgext:chg> elements contain the following child element:
> > 
> > o One or more <orgext:id> elements that contain the identifier of the organization. The "role" attribute is used to represent the relationship that the organization has to the object. Any given object MUST have at most one associated organization ID for any given role value. See Section 7.3 in [ID.draft-ietf-regext-org] for a list of values.
>  
> ... this MUST duplicates the requirement from Section 3.1; it could instead
> be "Any given object has at most one [...]", optionally with a reference up
> to Section 3.1.
>  
> -Benjamin
>  
> > Regards,
> > Linlin
> > 
> > 
> > Linlin Zhou
> >  
> > From: Linlin Zhou
> > Date: 2018-11-06 09:18
> > To: jgould; kaduk@mit.edu
> > CC: regext-chairs; Pieter Vandepitte; iesg; regext; draft-ietf-regext-org-ext
> > Subject: Re: [regext] Benjamin Kaduk's Discuss on draft-ietf-regext-org-ext-09: (with DISCUSS and COMMENT)
> > Hi James,
> > Thanks for your further suggestions. I'll include them in the updated version.
> > 
> > Regards,
> > Linlin
> > 
> > 
> > zhoulinlin@cnnic.cn
> >  
> > From: Gould, James
> > Date: 2018-11-02 20:25
> > To: kaduk@mit.edu; zhoulinlin@cnnic.cn
> > CC: regext-chairs@ietf.org; pieter.vandepitte@dnsbelgium.be; iesg@ietf.org; regext@ietf.org; draft-ietf-regext-org-ext@ietf.org
> > Subject: Re: [regext] Benjamin Kaduk's Discuss on draft-ietf-regext-org-ext-09: (with DISCUSS and COMMENT)
> > I believe that we need to ensure that the 1-on-1 organization role mapping is consistently defined in the draft.  The definition of the "role" attribute, the possible value can be referenced in section 7.3, and the relationship between the organization id and the role should certainly be defined in section 3.1.  The definition in 3.1 can be referenced in the create (4.2.1) and info (4.1.2), as in "One or more <orgext:id> elements that contain the identifier of the organization, as defined in [section 3.1]."  The update (4.2.5) is a little bit more complex to provide clarity on the behavior of the <orgext:add>, <orgext:rem> and the <orgext:chg>.  The following bullet could be removed from the update (4.2.5):
> >  
> > One or more <orgext:id> elements that contain the identifier of
> > the organization.  The "role" attribute is used to represent the
> > relationship that the organization has to the object.  See
> > Section 7.3 in [ID.draft-ietf-regext-org] for a list of values.
> >  
> > The reference to the <orgext:id> child elements and the expected behavior can be embedded under the definition of the <orgext:add>, <orgext:rem>, and <orgext:chg> elements, such as:
> >  
> >    o  An OPTIONAL <orgext:add> element that contains one or more <orgext:id> elements, as defined in [section 3.1], that add non-existent organization roles to the object.  The <orgext:id> element MUST have a non-empty organization identifier value.  The server SHOULD validate that the <orgext:id> element role does not exist.  
> >  
> >    o  An OPTIONAL <orgext:rem> element that contains one or more <orgext:id> elements, as defined in [section 3.1], that remove organization roles from the object.  The <orgext:id> element MAY have an empty organization identifier value.  The server SHOULD validate the existence of the <orgext:id> element role and the organization identifier if provided.  
> >  
> >    o  An OPTIONAL <orgext:chg> element that one or more <orgext:id> elements, as defined in [section 3.1], that change organization role identifiers for the object.  The existing organization identifier value will be replaced for the defined role.  The server SHOULD validate the existence of the <orgext:id> element role.     
> >   
> > —
> > JG
> >  
> >  
> >  
> > James Gould
> > Distinguished Engineer
> > jgould@Verisign.com
> >  
> > 703-948-3271
> > 12061 Bluemont Way
> > Reston, VA 20190
> >  
> > Verisign.com <http://verisigninc.com/> 
> >  
> > On 11/1/18, 6:29 PM, "regext on behalf of Benjamin Kaduk" <regext-bounces@ietf.org on behalf of kaduk@mit.edu>; wrote:
> >  
> >     On Thu, Nov 01, 2018 at 11:28:10AM +0800, Linlin Zhou wrote:
> >     > Dear Benjamin,
> >     > I found that following sections may be the proper place to restrict the 1-to-1 mapping. I think we can have restrictions in section 3.1 only or in 3.1&4.2.1&4.2.5. I've not decided which one is better and hope to have others' suggestions.
> >     
> >     I'd be happy to hear others' suggestions as well.  I don't have a strong
> >     preference, but if forced to choose would put text in all three places.
> >     (That is, others should feel free to choose "just section 3.1" and not
> >     force me to choose, if they want.)
> >     
> >     Thanks for putting together the proposals,
> >     
> >     Benjamin
> >     
> >     > 1. In section 3.1 Organization Identifier, add sentences at the end of this paragraph.
> >     > A "role" attribute is used to represent the relationship that the organization has to the EPP object. Any given object MUST have at most one associated organization ID for any given role value.
> >     > 
> >     > 2. In section 4.2.1,
> >     > One or more <orgext:id> elements that contain the identifier of the organization. The "role" attribute is used to represent the relationship that the organization has to the object. Any given object MUST have at most one associated organization ID for any given role value. See Section 7.3 in [ID.draft-ietf-regext-org] for a list of values.
> >     > 
> >     > 3. In section 4.2.5
> >     > One or more <orgext:id> elements that contain the identifier of the organization. The "role" attribute is used to represent the relationship that the organization has to the object. Any given object MUST have at most one associated organization ID for any given role value. See Section 7.3 in [ID.draft-ietf-regext-org] for a list of values. 
> >     > 
> >     > If we have the restrictions, the 1-to-multiple mapping cases are not necessary to be specified in this document.
> >     > 
> >     > Regards,
> >     > Linlin
> >     > 
> >     > 
> >     > Linlin Zhou
> >     >  
> >     > From: Benjamin Kaduk
> >     > Date: 2018-10-31 20:43
> >     > To: Linlin Zhou
> >     > CC: regext-chairs; Pieter Vandepitte; iesg; regext; draft-ietf-regext-org-ext
> >     > Subject: Re: [regext] Benjamin Kaduk's Discuss on draft-ietf-regext-org-ext-09: (with DISCUSS and COMMENT)
> >     > Dear Linlin,
> >     >  
> >     > On Wed, Oct 31, 2018 at 02:19:45PM +0800, Linlin Zhou wrote:
> >     > > Dear Benjamin,
> >     > > Thanks for your input. We believe that relationship between an object and an organization should be 1-to-1, one organization ID with just one role. 1-to-many is an exception for the organization extension. Indeed that is our concern, "the multiple examples may be overkill". Many thanks.
> >     >  
> >     > I won't object to requiring the 1-to-1 mapping, as the impact of the
> >     > restriction seems minor.  I am not entirely sure where the best place to
> >     > add some text that clarifies this restriction would be; perhaps in Section
> >     > 4.2.1 where we describe the <orgext:id> elements in <create>?  (I assume
> >     > that the formal syntax does not provide for a maxOccurs that applies
> >     > per-type.)  It may also be worth a (non-normative) reminder in the <update>
> >     > description that the semantics of <orgext:chg> are well-defined because
> >     > there is only one entry per role value, but I'm not sure about that.
> >     >  
> >     > Thanks,
> >     >  
> >     > Benjamin
> >     >  
> >     > _______________________________________________
> >     > regext mailing list
> >     > regext@ietf.org
> >     > https://www.ietf.org/mailman/listinfo/regext
> >     
> >     _______________________________________________
> >     regext mailing list
> >     regext@ietf.org
> >     https://www.ietf.org/mailman/listinfo/regext
> >     
>  
> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext
 
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext