Re: Changes we'd make to EPP, was Re: Domain check in draft-obispo-epp-idn-00.txt
"Gould, James" <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <CB3AE925.C55A%[email protected]> |
Ulrich, Can you provide a reference to the extension created by .SE for registry changes for review? Using a command (obj:delete) in response to a command (poll) would not meet RFC 5730. Use of obj:creData I don't believe would match the context. Use of obj:infData could work since it's the most generic to cover any changes, but it wouldn't provide any specific information on a garbage collection delete except for maybe text in the <msgQ><msg> element (e.g. "deleted - orphaned" or something like that). This is not clean but it wouldn¹t require any new extensions or mappings. -- JG James Gould Principal Software Engineer [email protected] <http://[email protected]> 703-948-3271 (Office) 12061 Bluemont Way Reston, VA 20190 VerisignInc.com On 1/17/12 3:12 AM, "Ulrich Wisser" <[email protected]> wrote: >Hi, > >here at .Se we have done some extension to notify registrars of database >changes done by the registry. Today I believe that we do not even need >an extension for that. > >To notify the registrar of changes we could use > obj:creData > obj:infData > obj:delete >for the respective change. I realize that obj:delete is actually used as >command but there is nothing in the xsd file that prevents reusing it as >response. The absence of clTRID would indicate that the command was >initiated by the registry. > >/Ulrich > >_______________________________________________ >provreg mailing list >[email protected] >https://www.ietf.org/mailman/listinfo/provreg _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg