Re: Standard Extensions
"Gould, James" <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <CB4412A1.1683A%[email protected]> |
We haven't had the need for an extension for result codes or status values for root, .com, .net, .edu, .cc, .tv, .jobs and our additional services (name suggestion, whowas, etc.). For .name we only needed to include a sub-result code of 2305 "Object association prohibits operation" on the create response of domain and emailfwd for providing more clarity on which object prohibits the operation (1 "Corresponding service exists" or 2 "Conflicting defensive registration exists"). I'm not sure if any of the Registrars for .name are utilizing this feature of the "Personal Registration" extension to drive their client-side logic. In general we stick with the result codes and status values defined in the RFC's. -- JG James Gould Principal Software Engineer [email protected] 703-948-3271 (Office) 12061 Bluemont Way Reston, VA 20190 VerisignInc.com On 1/24/12 6:59 AM, "Hollenbeck, Scott" <[email protected]> wrote: >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] On >> Behalf Of Patrick Mevzek >> Sent: Monday, January 23, 2012 6:59 PM >> To: [email protected] >> Subject: Re: [provreg] Standard Extensions >> >> Hollenbeck, Scott <[email protected]> 2012-01-19 13:18 >> > Having said that, maybe it makes sense to create a standard extension >> for additional result codes and status values. >> >> I believe so. >> >> And then, if you make it happen that everyone switch from their >> current homegrown version to this extension, you may find out that all >> registries or almost all of them need this extension, which in a way >> shows that the feature should be in the core protocol. >> But things will technically work out the same way while in an >> extension. >> >> *If* everyone switches to it. >> >> Which I'm far to believe. > >I'm with you on the switching part, but I'm not convinced that there >really is significant demand. How many registries are using custom result >codes and status values? > >Scott >_______________________________________________ >provreg mailing list >[email protected] >https://www.ietf.org/mailman/listinfo/provreg _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg