Re: ROID how useful?
"Gould, James" <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <[email protected]> |
Francisco, I'm really not sure what you are proposing. The contact ID is unique within an individual registry while a roid is unique across all registries. Referencing a contact roid with it's auth info that resides elsewhere is the only advantage that I can see over the use of the contact ID. In both cases they are unique for supporting authorization of the domain info and transfer commands, so I don't believe there is a true issue with referencing the roid as the RFC is defined. There are uses of roid for dealing with objects whose names can change like hosts and even custom object mappings like for DotName. JG James F. Gould Principal Engineer Verisign [email protected] On Dec 11, 2012, at 6:45 PM, "Francisco Obispo" <[email protected]> wrote: > contact:info doesn't include a "roid" option, > > Only domain:[transfer/info] > > info: > - An OPTIONAL <domain:authInfo> element that contains authorization > information associated with the domain object or authorization > information associated with the domain object's registrant or > associated contacts. An OPTIONAL "roid" attribute MUST be used to > identify the registrant or contact object if and only if the given > authInfo is associated with a registrant or contact object, and > not the domain object itself. If this element is not provided or > if the authorization information is invalid, server policy > determines if the command is rejected or if response information > will be returned to the client. > > transfer: > - A <domain:authInfo> element that contains authorization > information associated with the domain object or authorization > information associated with the domain object's registrant or > associated contacts. An OPTIONAL "roid" attribute MUST be used to > identify the registrant or contact object if and only if the given > authInfo is associated with a registrant or contact object, and > not the domain object itself. > > > On Dec 11, 2012, at 3:23 PM, Francisco Obispo <[email protected]> wrote: > >> For what I can see, any command querying the server that references the ROID, including: domain:info, domain:transfer, and contact:info > > Francisco Obispo > Director of Applications and Services - ISC > email: [email protected] > Phone: +1 650 423 1374 || INOC-DBA *3557* NOC > PGP KeyID = B38DB1BE > _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg