Re: clTRID element clarification

"Hollenbeck, Scott" <[email protected]>
Newsgroups gmane.ietf.provreg
Message-ID <831693C2CDA2E849A7D7A712B24E257F0D5B7647@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On
> Behalf Of Aaron Roberts
> Sent: Wednesday, February 29, 2012 10:24 AM
> To: [email protected]
> Subject: [provreg] clTRID element clarification
> 
> Hi all,
> 	I'm looking to gauge domain registries' interpretation and use of
> the clTRID EPP command element in their EPP server implementations.
> 
> It seems that some registry EPP servers (namely .za and .im) use a kind
> of "cache/lookup" mechanism, based on the clTRID and (hopefully) scoped
> to individual registrars.  Where a command is received from a registrar
> with a clTRID which has been previously used by the same registrar, the
> cached server response is returned to the client, instead of the
> command being executed a second time.  The intention is to provide
> idempotency at the server level, when commands are issued multiple
> times.
> 
> My interpretation of the RFCs is that the clTRID is just a handy
> identifier for debugging etc.. managed by the client end and that EPP
> commands are designed to be idempotent by nature so can be safely
> executed multiple times without any considerations given to previous
> executions.

Your interpretation is correct. Servers should not make *any* assumptions about clTRIDs.

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.