Dear colleagues, Following on from Alain’s email, I would like to note a couple of items relating to discussions of the IANA oversight transition in the RIPE community.
The Eurasian Network Operators' Group (ENOG) held its seventh meeting in Moscow on 26-27 May, the week after RIPE 68. There was a discussion of the IANA oversight transition at that meeting, and a brief summary of that discussion is provided below: > ENOG 7, 27 May 2014 > Attendance: Approximately 150 > > Major points coming out of the discussion: > - Additional ways in which the RIPE NCC interacts with the IANA include > reverse DNS and running the K-root name server. > - It is important to note that the oversight function will not transition to > a government-based body. > - The technical community has not had any issues with the U.S. government's > conduct of its oversight of these functions for the past 20+ years - any new > model should not complicate the current system and processes. > - The RIPE NCC is not interested in DNS operations and should not be put > under that umbrella. > - The community should ensure that operators are protected from possible > commercial interests, given that some of ICANN’s activities, such as the > registration of domain names, are profit-making. As noted in the RIPE 68 session, the RIPE Cooperation Working Group is the official venue for community discussion of this issue. For this reason, the RIPE NCC will ensure that any discussion in other RIPE community forums is fed back to this list. Summaries of these discussions will also be posted on the RIPE website: http://ripe.net/iana-discussions Any comments or responses to this process or on the substance of the summaries should be posted to this mailing list. Best regards, Chris Buckridge Senior External Relations Officer, RIPE NCC
smime.p7s
Description: S/MIME cryptographic signature
