Re: ROID how useful?
Francisco Obispo <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <[email protected]> |
Thank you all for your comments. I'm wondering whether: (from rfc5731) When an <info> command has been processed successfully, the EPP <resData> element MUST contain a child <domain:infData> element that identifies the domain namespace. Elements that are not OPTIONAL MUST be returned; OPTIONAL elements are returned based on client authorization and server policy. The <domain:infData> element contains the following child elements: contains an error, since I believe we should be referencing the contact by its ID in this case and not by its ROID. On Dec 7, 2012, at 6:30 PM, Francisco Obispo <[email protected]> wrote: > C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> > C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> > C: <command> > C: <transfer op="query"> > C: <domain:transfer > C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> > C: <domain:name>example.com</domain:name> > C: <domain:authInfo> > C: <domain:pw roid="JD1234-REP">2fooBAR</domain:pw> > C: </domain:authInfo> > C: </domain:transfer> > C: </transfer> > C: <clTRID>ABC-12345</clTRID> > C: </command> > C:</epp> It could mean that previous versions of the protocol did in fact use ROIDs as contact identifiers but it seems strange that this is the _only_ place where ROIDs are referenced as part of a query, everywhere else the contact:id is used. How are others implementing it? 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