> Of course there are actually 2 different registry backends > as I recall
Many different back-ends, many different protocols. OpenSRS/HRS, on the back-end, don't differentiate between a gTLD registry and a ccTLD registry, it just knows that someone requested a transaction that it needs to fulfill. Outside of the gTLD world, there is literally a different protocol for each registry that needs to be implemented if you want to get registrations in that namespace. Couple that with the fact that each registry also has their own business rules and you end up with a pretty complex mess pretty quickly. Consider for instance the similarities and differences between .us and .kids.us. Both use the same protocols and registry back-end, but the business rules overlay make for a completely different registration and support experience. They are far from being "the same". Anyways, we're probably getting a little bit off-topic, but hopefully this sheds some light on some of the decisions that we make and why we make them. Things might appear to be simple on the front-end, but there are a million competing issues on the back-end that we need to rationalize before we can move forward. Its not as simple as plugging a protocol adapter into a registry proxy and crossing your fingers ;) Thankfully, exposing and documenting transport and security *is* pretty straightforward :) -rwr
