Op 22 aug. 2016, om 16:02 heeft Gould, James <jgo...@verisign.com> het volgende geschreven:
> Your response made me think a little bit more around the problem that is > being solved. I see 2 problems that could be solved by formally defining the > reseller and linking the reseller with objects in the registry: > > Displaying the Reseller information in RDDS (RDAP). Right now it is the > reseller name that needs to be displayed, but what if more information is > needed later like E-mail, URL, Address, Contacts, etc.? > Enable registrars to set security, policy, and reporting options for > reseller’s at the registry level. I can see many different use cases here > that we’ve not yet fully discussed. > > Thoughts? > Hi James, I fully agree with your use cases. Thank you for clarifying them. In addition this was actually my main question that has not been answered yet thinking ahead. Looking from a registration/registry perspective I think that a registrant/registrar/reseller/dns-operator is only a role an entity has for a specific registration. It is NOT a tag to the entity itself. You cannot say an entity IS a reseller, only that he performs a role as a reseller for a specific registration. It’s the relationship that is tagged, not the entity. Outside the registry relationship, an entity is appointed or "tagged” as a reseller by a registrar, but that contract is not what a registry administers. What happens if an entity is a registrant for one registration, a dns-operator for another one, a registrar for some others, and a reseller for yet another group? Will he be in the registry 4 times in 4 different tables, or only once? What if he is a reseller for multiple registrars? What happens when he changes emailadress/phone number/address? What happens when a reseller becomes a registrar for a new set of domains but remains reseller for the existing ones? Will his identifier and credentials change? In my humble thought experiment, I think we should register a reseller the same as we do a registrar. As long as he does not have a registrar role for any registration, but only a reseller role, far less data is required, but the entity will need to get an identifier and credentials that do not change once he will get an additional role. So it’s business logic to determine how much data is required and displayed depending on the role the entity has in a specific registration. But a phone number is a phone number, an emailaddress is an emailaddress, and there is no difference in definition in emailaddress requirements of a reseller compared to that of a registrant or any other entity that needs to be administered. Once the local registry policy determines the emailaddress field is mandatory for an entity in a reseller role, the definition of an emailaddress is still the same.. Can this be done, especially looking at the way registrar and registrant entities are treated different now? The question of authoritative data versus informational is an interesting one. We need to know why the data needs to be in the registry in the first place. If the data is to be used later for limited access rights to the database, like a dns-operator allowed to change an NS-set or a reseller allowed to change a registrant’s emailaddress, then it needs to be authoritative data from the registry perspective. Do we think that will never happen, or do we leave that decision to the business case of each individual registrar? I can imagine some registrars want to delegate some specific access rights and reporting, and others don’t. Should we provision for both, or only one use case? Thoughts? - -- Antoin Verschuren Tweevoren 6, 5672 SB Nuenen, NL M: +31 6 37682392
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
