Patrick, The role applies to both the object (Organization) as well as the links (Domain to Organization). In the data model, a generic Organization may have multiple roles (“registrar”, “reseller”, “privacyproxy”, etc.), each with an optional external identifier like the IANA ID for the registrar, and each with its own server defined status. The Organization identifier is server defined and will most likely not match an external identifier like the IANA ID for the registrar, thus you need support for an optional identifier at the level of the Organization role. The status defines whether new links can be made or whether there are existing links. An Organization can provide multiple services (roles) and therefore the Organization has a status and each of the roles can have a status. The link role is needed to easily identify was service the organization provides to the object. The server defines the possible set of Organization roles via an out-of-band mechanism and the link roles to the organization can be server or client specified. The links from the provisioning objects (e.g., Domain) and the Organization is a many-to-many relationship, which can be called Provider or Service Provider, that has a Role attribute that needs to be match up with one of the Roles defined for the Organization. The Provider Role and the Organization Roles are linked to ensure that there are no orphaned links and to provide visibility into what links exist and what new links can be created. The roles in both draft-ietf-regext-org and draft-ietf-regext-org-ext enable the definition of a generic Organization with an extensible set or service roles that are consistent.
Thanks, — JG James Gould Distinguished Engineer jgo...@verisign.com 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com <http://verisigninc.com/> On 12/30/17, 6:56 PM, "regext on behalf of Patrick Mevzek" <regext-boun...@ietf.org on behalf of p...@dotandco.com> wrote: Hello Linlin, I will wait on next versions of your draft to see how they got changed, but I still have one major point: On Thu, Dec 28, 2017, at 10:58, Linlin Zhou wrote: > I am more than a little fuzy about your "role" uses. > When you create an organization you specify a role, > and then when you create/update a domain to add an organization you > again specifcy a role. > Are they the same or different? Why do they need to be repeated? > > This whole idea of "role" will need to be seriously improved in both documents. > > [Linlin] Actually the two role have the same value referring to section > 7.3 in draft-ietf-regext-org. I think we need add some words in the org- > ext draft to explain that you should go to org draft to find the role > values. > S: <org:role> > S: <org:type roleStatus="ok">registrar</org:type> > S: <org:roleid>1362</org:roleid> > S: </org:role> > > S: <orgext:id role="reseller">myreseller</orgext:id> Even with your reply I think I still do not understand enough what you are trying to do with the whole role/roleid/rolestatus things and the fact that it is both an attribute of the organization object and an attribute of the link between the organization object and the domain object. If it is the same value, then one of them is redundant and should be removed I think. I hope to understand this more in your later versions. Do not hesitate to add more text and examples. -- Patrick Mevzek _______________________________________________ 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
