Re: EPP Poll 'msgid' attribute

"Hollenbeck, Scott" <[email protected]>
Newsgroups gmane.ietf.provreg
Message-ID <831693C2CDA2E849A7D7A712B24E257F0D54671F@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On
> Behalf Of Mike O'Connell
> Sent: Monday, October 31, 2011 5:33 AM
> To: [email protected]
> Subject: [provreg] EPP Poll 'msgid' attribute
> 
> Hi All
> 
> 
> We're currently implementing an EPP based registry.
> 
> One of our test registrars pointed out something of interest which I
> thought should be mentioned in the spec.
> 
> The EPP schema element for 'poll' requests allows for two attributes
> 'op' and 'msgid'. The spec states that when op='req' is used the server
> should return an unacked item from the FIFO queue, and that when
> op='ack' is used you need to specify the 'msgid' to acknowledge.
> 
> We're looking at implementing a selectable poll message process where
> the op='req' can specify the clTRID as the 'msgid' attribute to
> retrieve any unacked responses associated with that client identifier.
> 
> Has anyone implemented anything like this? What are the thoughts
> regarding this?

I personally think you're better off following the spec. One-off deviations make it more difficult for registrars to develop software systems that work across registries. You might want to check with your other registrar partners to see what they think.

Having said that, if you do it be sure to change the URIs for the namespace and schema identifiers. Once you change the schema you're (as you described above) EPP-based, not EPP.

Scott
_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.