Re: Proposal: A standard EPP OT&E test suite for each object type and extension type
Patrik Fältström <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <[email protected]> |
On 17 jun 2011, at 18.03, Jim Reid wrote: > However with 200+ countries in the world, that pretty much means 200+ different business models because there are 200+ different registry policies or national laws.... :-( Well, not really. Let me take an example: When you do transfer of a domain, what happens with the host and contact objects that are bound to the domain? What notifications are sent, and what actions have to be taken? I think, even though we have 200+ different business models, I claim those can be implemented with only say 3-5 different ways of doing transfer. > It might be better to approach this from a different direction. How about defining a standard set of registry transactions -- create/delete/modify objects, renew and transfer a domain name, etc -- and writing this up as a BCP? Once that's done, the BCP could be encoded in a standard test suite. In other words, document what it is that's to be tested before developing a test suite. Some tests might be optional (for instance IDN and DNSSEC might not be deployed in places) while others are mandatory. I fully support this. And is implicitly what I am asking for. That registries try to, before they invent their own epp architecture, look carefully at if they can not reuse what someone else is doing. I do not see that happening today. Not as much as I as an implementor in the registrar side would like to see. Patrik _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg