clTRID element clarification
Aaron Roberts <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <0E7B3A96BAA7334CB6D338433C5E61B93E93E6E33B@LISA.internal.domicilium.com> |
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. I'd be very interested to know what everybody is doing in this regard? Regards, Aaron Domicilium (IOM) Limited | The Isle of Man Datacentre Ronaldsway Industrial Estate | Ballasalla | Isle of Man |IM9 2RS Tel +44 (0) 1624 825278 www.domicilium.com www.ipv6.domicilium.com This e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient. If you have received it in error, please contact the sender immediately by return e-mail. Please then delete the e-mail and do not disclose its contents to any person. _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg