Re: Has the EPP world really changed?
"Jiankang YAO" <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <71C99AB5811B4D9EA76F0D7B61F09E95@LENOVO47E041CF> |
a.. From: Patrik Fältström <patrik at frobbit.se> b.. To: Edward Lewis <Ed.Lewis at neustar.biz> c.. Cc: IETF Provreg Mailing List <provreg at ietf.org> d.. Date: Fri, 24 Aug 2012 16:50:07 +0200 e.. In-reply-to: <a06240801cc5d3fc5e1b5 at [10.33.203.101]> f.. References: <alpine.DEB.2.00.1208241025280.16452 at softronics.hoeneisen.ch> <a06240800cc5d39505e3a at [10.33.203.101]> <1E021559-D8A8-41DA-BDAC-B6DF57A6C0D6 at frobbit.se> <a06240801cc5d3fc5e1b5 at [10.33.203.101]> g.. List-id: EPP discussion list <provreg.ietf.org> -------------------------------------------------------------------------------- >>On 24 aug 2012, at 16:31, Edward Lewis <Ed.Lewis at neustar.biz> wrote: ...>> In some cases, the registrars weren't implementing anything, so the number of extensions didn't matter. They just got the code and put it in place. >>CNNIC'registrars use different clients for different registries. For .CN, the registrar uses the EPP client (source code) provided by CNNIC to connect CNNIC's EPP server.The registrar also uses the .HK's client to connect to .HK.Based on my estimate, most registrars will use different clients to connect different registries. They will be unlikely to use the same client to connect to the different registries evenif those registries run the EPP protocols.Jiankang Yao >Of course, if you are lucky! > Patrik _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg