Lutz, On Nov 18, 2014, at 1:38 PM, Lutz Donnerhacke <l...@iks-jena.de> wrote: >> If ICANN has concerns about the delegation, then they should raise them >> formally with the RIPE NCC. > I second that.
As mentioned previously, AFAIK, ICANN doesn't have any concerns with ripe.int -- I doubt anyone who isn't on this mailing list from ICANN is even aware it exists. The question is about what happens in the future since .INT registry services is officially (rightly or wrongly) a service provided via the IANA Functions contract, it is likely ICANN won't be providing .INT registry services in the future (since ICANN's section II.2 of own bylaws state: "ICANN shall not act as a Domain Name System Registry [...]" so I'll be surprised if .INT is continued after the stewardship of the IANA functions contract is transitioned), and RIPE is not a treaty organization. This isn't a question for ICANN: it's a question for RIPE (or, if you prefer, RIPE-NCC) and whoever will be running .INT after the transition. I'm just suggesting that if RIPE (or, if you prefer, RIPE-NCC) see no significant value in RIPE.INT, to simply ask it be dropped prior to (I'm perhaps overly cynically guessing here) political silliness associated with the .INT zone. Regards, -drc (ICANN CTO, but speaking only for myself. Really.)
signature.asc
Description: Message signed with OpenPGP using GPGMail
