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.
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 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 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 element that contains one or more
elements, as defined in [section 3.1], that add non-existent organization roles
to the object. The element MUST have a non-empty organization
identifier value. The server SHOULD validate that the element role
does not exist.
o An OPTIONAL element that contains one or more
elements, as defined in [section 3.1], that remove organization roles from the
object. The element MAY have an empty organization identifier
value. The server SHOULD validate the existence of the element
role and the organization identifier if provided.
o An OPTIONAL element that one or more 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
element role.
At least one , or element MUST be
provided. The , and elements contain the
following child element:
o One or more 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.
Regards,
Linlin
Linlin Zhou
From: Linlin Zhou
Date: 2018-11-06 09:18
To: jgould; ka...@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
zhoulin...@cnnic.cn
From: Gould, James
Date: 2018-11-02 20:25
To: ka...@mit.edu; zhoulin...@cnnic.cn
CC: regext-cha...@ietf.org; pieter.vandepi...@dnsbelgium.be; i...@ietf.org;
regext@ietf.org; draft-ietf-regext-org-...@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 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 ,
and the . The following bullet could be removed from
the update (4.2.5):
One or more 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 child elements and the expected behavior can
be embedded under the definition of the , , and
elements, such as:
o An OPTIONAL element that contains one or more
elements, as defined in [section 3.1], that add non-existent organization roles
to the object. The element MUST have a non-empty organization
identifier value. The server SHOULD validate that the element role
does not exist.
o An OPTIONAL element that contains one or more
elements, as defined in [section 3.1], that remove organization roles from the
object. The element MAY have an empty organization identifier
value. The server SHOULD validate the existence of the element
role and the organization identifier if provided.
o An OPTIONAL element that one or more elements,
as defined in [section 3.1], that change organization role identifiers for the
object. The ex
