Hi Patrick, I think the "role" of S: <orgext:id role="reseller">myreseller</orgext:id> is the same thing with "roletype" in S: <org:type roleStatus="ok">registrar</org:type>. If we change the name "role" to "roleType", is it better to help readers to understand?
Regards, zhoulin...@cnnic.cn From: Patrick Mevzek Date: 2017-12-31 07:56 To: regext Subject: Re: [regext] My review of draft-ietf-regext-org and draft-ietf-regext-org-ext 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. -- 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
