Re: Domain check in draft-obispo-epp-idn-00.txt
Patrik Fältström <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <[email protected]> |
On 4 jan 2012, at 21:37, Michael Young wrote: > What can I say, it would be great if the registrar put that kind of intelligence in their storefront and didn't send domain creates that violate a given language table. Regardless of whether they do or not, the registry is what finally says yes or no to a registration, right? > Most registrars aren't making that extensive of an effort. Why? What if the registrar messes up on their filter and denies the registrant a registration the registry actually allows. Ooops starts to sound like a lawsuit, better the registrar makes the registry say no. It's cheaper to say no in domain check than a create. However I think there's room here to satisfy both concerns. > > Adjust the domain check ext so the language tag element is optional. No language tag and it assumes a straight ASCII registration. Yes, check should of course have the same argument(s) etc as create. > Then those registrars that want to validate their own work can and registrars that aren't sure can test a punycode string against the extended domain check. This seems like a compromise that works, thoughts? Makes sense of course but why do a check and not create directly, that might fail? You are absolutely correct that a registrar might do a create if they believe they MIGHT have a success. Specifically if you have a race in the form of backorder you do, and you are limited in the number of commands per time unit you are allowed to do. And as you say, a registrar can not risk rejecting a domain registration for a registrant that might in fact work. If all registries, and I mean all and not only the gTLD registries that the accredited registrars run against, had a few fewer extensions, and used similar rules for things like transfer and whatever else... So, can you please explain what the problem is with having the registries get some creates that will fail? Then I will understand better. Patrik _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg