- ncc-services-wg - mailman.ripe.net

New RIPE NCC PGP Key
by Alex Le Heux 17 Dec '07

17 Dec '07

[Apologies for duplicate e-mails] Dear Colleagues, We are approaching the new year and so we will start to use a new PGP key for signing e-mail sent from our ticketing system. On Wednesday 2nd January 2008 we will start using our 2008 key to sign e-mail. The new key has been signed by the old key as described in the key-management policy on our web site: https://www.ripe.net/rs/pgp/index.html The old key remains valid until 7th February 2008. If you have any questions, please contact <lir-help(a)ripe.net>. Kind Regards, Alex Le Heux RIPE NCC

1 0

Unscheduled LIR Portal outage
by Pedro da Silva Vaz 22 Nov '07

22 Nov '07

Dear Colleagues The LIR Portal and related services have experienced several short outages in recent days. This was due to an unsuccessful upgrade of our production servers. All LIR Portal services were down for approximately one hour from 16:00 (UTC) on Wednesday, 21 November, and from 10:00 - 15:00 (UTC) on Thursday, 22 November. The New LIR Registration Wizard remained unavailable until approximately 16:30 (UTC) on Thursday, due to some extra maintenance tasks. We apologise for any inconvenience this may have caused. If you have any questions regarding this event, please send an email to <sw-bugs(a)ripe.net>. -- Pedro Vaz Software Engineer Phone: +31 20 535 4490 ------------------ Business Applications Department RIPE NCC

1 0

New Document available: ripe-423
by RIPE NCC Document Announcement Service 15 Nov '07

15 Nov '07

Dear Colleagues We have published a new RIPE Document - ripe-423 'RIPE NCC Audit Activity'. It replaces ripe-170 'RIPE NCC Consistency & Auditing Activity'. We have also published ripe-424, as it contained references to ripe-170. The publication of these documents do not represent any change to policy in the RIPE NCC Service Region. The new documents are available at: http://www.ripe.net/ripe/docs/ripe-423.html http://www.ripe.net/ripe/docs/ripe-424.html Regards Adrian Bedford Web Services Team Leader RIPE NCC

1 0

Announcing new RIS de-bogon prefixes
by Ruben van Staveren 13 Nov '07

13 Nov '07

[Apologies for duplicate messages] Dear Colleagues As part of our effort to de-bogonise new address blocks, we are now announcing the following prefixes on RRC03: 114.0.0.0/24 114.50.0.0/21 114.200.0.0/19 114.255.0.0/16 115.0.0.0/24 115.50.0.0/21 115.200.0.0/19 115.255.0.0/16 More information regarding the RIS de-bogon project can be found at: http://www.ris.ripe.net/debogon/index.shtml Kind regards, Ruben van Staveren, RIPE NCC

1 0

RIPE NCC General Meeting October 2007 - Final Reminder to Register
by Axel Pawlik 23 Oct '07

23 Oct '07

[Apologies for duplicate e-mails] Dear RIPE NCC member, The RIPE NCC Executive Board is pleased to invite you to the RIPE NCC General Meeting (GM). The meeting will be held at 17:45 on Wednesday, 24 October 2007 during the RIPE 55 meeting in Amsterdam, the Netherlands. You can register online at: https://lirportal.ripe.net/lirportal/meeting/registration-general/meeting.h… You will also be able to register at the GM registration desk until 15:00 on Wednesday, 24 October 2006. After this time, registration for the GM will close. Please bring the appropriate identification to the GM registration desk. Once registered you will be given your meeting folder (containing your membership status and details of your voting rights) and your GM badge. More information on the GM can be found at: http://www.ripe.net/membership/gm/gm-october2007/ The GM agenda is available at: http://www.ripe.net/membership/gm/gm-october2007/agenda.html The GM supporting documents can be downloaded at: http://www.ripe.net/ripe/draft-documents/gm-october2007/ If you have any questions about the GM, please e-mail us at: agm(a)ripe.net Regards, Axel Pawlik Managing Director RIPE NCC

1 0

Re: Allow DNSMON services to monitor ENUM domains
by Jim Reid 18 Oct '07

18 Oct '07

Ondrej, I raised a number of issues about this proposal when you first presented this to the ENUM WG. To the best of my knowledge these have still not been resolved. Wearing no hats, my concerns are as follows: 1 DNS Monitoring is not a core NCC service. It should not be doing this IMO. It's OK for the NCC to monitor its own name servers, but that's all. 2 By offering a commercial DNS Monitoring service, the NCC is distorting the market. Its presence presents other organisations from offering similar services because the barrier to entry has been artificially increased. And on top of that the NCC has cherry-picked the best customers. 3 The costs of the NCC's DNS monitoring service are not clear. Which raises the prospect of complaints about monopoly membership fees cross-subsidising non-core commercial activities. This is a particular worry of mine given that the NCC's initial investment in name server monitoring was met from its membership fees. 4 If any monitoring of ENUM delegations was to be done by the NCC, it must only be at the request of the Administration concerned. This avoids issues about national sovereignty. I accept this is unlikely to be a concern for many countries. But that will not be the case in the parts of the world that are hostile to Internet governance in its broadest sense being outside an international treaty organisation. It would not be wise IMO to open another window for those sorts of complaints and attacks. Issues 1-3 have parallels with the historical situation of the NCC providing DNS service for ccTLDs. That situation is beginning to get untangled. And for the same reasons outlined above: non-core service, competition concerns, cross-subsidy, etc. It seems unwise to be opening up the same can of worms all over again just as an earlier one is starting to get cleared up.

14 39

New RIPE Database document
by Denis Walker 11 Oct '07

11 Oct '07

[Apologies for duplicates] Dear Colleagues, During the Database Working Group (DB WG) session at RIPE 54, it was decided to review the status of those RIPE Documents relating to the RIPE Database. Following discussion on the DB WG Mailing List, a proposal to address this issue was produced, which can be viewed at: http://ripe.net/ripe/maillists/archives/db-wg/2007/msg00162.html No concerns were raised and this proposal has now been implemented. This implementation has resulted in a new RIPE Document, ripe-419 "RIPE Database Reference Manual". This provides a brief introduction to the RIPE Database and references the new RIPE Database Document Library, which can be viewed at: http://www.ripe.net/db/docs.html This library references all the available documents concerning the RIPE Database and associated services. These documents will, in future, be kept up-to-date with all changes to database software and procedures. If you have any questions or concerns, please send an e-mail to <ripe-dbm(a)ripe.net>. Regards Denis Walker RIPE NCC

1 0

Announcing new RIS de-bogon prefixes
by Ruben van Staveren 11 Oct '07

11 Oct '07

[Apologies for duplicate messages] Dear Colleagues As part of our effort to de-bogonise new address blocks, we are now announcing prefixes from 186.127.248/21 and 186.128/16 on RRC03. Kind regards, Ruben van Staveren, RIPE NCC -- Ruben van Staveren RIPE Network Coordination Center Information Services Singel 258 Amsterdam NL http://www.ripe.net +31 20 535 4444 PGP finger print 6501 4389 A675 477E DCE5 53D8 9108 49E2 DAFC 271B

1 0

(no subject)
by Daniel Karrenberg 11 Oct '07

11 Oct '07

Subject Excursion to NSD history. Was: Allow DNSMON services to monitor ENUM domains Reply-To: In-Reply-To: <3678E9F7-3B2E-44EC-83B8-F0A5BAA5845F(a)rfc1035.com> On 08.10 14:33, Jim Reid wrote: > ... And as a former employee of an LIR who saw their > membership fees being used by the NCC to nurture DNS software that > undermined that company's products. ... Jim, I assume you mean NSD. I'll react to the dnsmon side of this separately. The intention of this message is to put the record straight and voice some opinions on the NSD side. Full disclosure: I am a long standing member of the (European) Internet community and speak as such. But be informed of these other things: My personal view is that the RIPE NCC needs to be much more than a number "factory". I am on record with this view consistently over time and from far before the NCC was actually established. [Ref: RIPE meeting minutes, ripe-019, ...] I am the founding CEO of the RIPE NCC and currently serve as is in the role of Chief Scientist. I am one of the instigators of what became NSD; some have said I am *the* instigator but I feel that is not quite right. The gestation of ideas like this is always very hard to pin down. John Crain, Ted Lindgreen and Alexis Yushin and possibly others instigated as much as I did. Facts: NSD was developed by NLnet Labs http://www.nlnetlabs.nl/ and not the RIPE NCC. When development of NSD started we were not aware of anyone developing something similar, neither proprietary nor open source. If someone had offered a realistic alternative at the time the RIPE NCC would have taken it and I doubt if NLnet labs had undertaken to develop a "me too". Development of NSD was above board from before it started. Both NLnet Labs and RIPE NCC told the community what we were up to; we actively solicited feedback about our plans and received nothing but encouragement and good suggestions. The NCC resources that went into NSD were at the *very most* 3 months of my time. It is very difficult to account for that since I do not work on a single thing at a time; neither do I work 9-5 and creative work does mostly happen outside these hours anyway. I was the only NCC staff involved with the project. I fully participated in the design of NSD 1 as part of my NCC duties. Since NSD 2 my involvment is reduced to very sporadic advice. I developed the DISTEL test lab and performed regression and performance testing of NSD 1 as part of my NCC duties. See http://www.ripe.net/ripe/meetings/ripe-42/presentations/ripe42-dns-distel/i… After the first versions of NSD 1 were released I have done no furhter work on this. NLnet Labs is operating a test lab now that is built on the foundations of DISTEL. Opinions: The main reason for the creation of NSD were massive concerns that erupted (post 9/11) about the lack of diversity in major widely deployed DNS software. These concerns came from both the technical community but more importantly from layer 9 and above. Those who are not sympathetic to industry self regulation in general and to organisations like ICANN and the RIPE NCC in particular were creating all sorts of FUD in this area with the intention to harm us. Something needed to be done. Any mishaps with the operation of k.root-servers.net are a considerable danger for the RIPE NCC's reputation as a professional organisation, and more importantly in the light of the "Internet Governance" discussions. So hardening this operation is necessary and in the interest of the RIPE NCC. The use NSD has indeed hardened this operation in more than one way. Any performance increase of DNS software on RIPE NCC operated authoritative DNS name servers saves money for additional hardware that would otherwise be required. One could easily defend the level of our involvment in the development of NSD by direct RIPE NCC operational needs: direct involvement in the design made sure that our requirements were met by the product. Thorough regression testing was a prerequisite for us to deploy the software on k.root-servers.net anyway; doing it as part of the NSD effort rather than post-factum product testing was a much more efficient. I believe strongly that the RIPE NCC should help along open source efforts that meet its operational needs and that also meet operational needs of the RIPE community. So even without the very valid defense above it would have been fully appropriate to participate. The NCC should not just be a number factory but also be a place where the membership can place activities that further their common goals and that need a professional and neutral organisation to do them. This is our strength. Letting the RIPE NCC degenerate to a number factory would very likely weaken it to the point where it could be taken over by others, such as governments. We actively communicated to the RIPE community and beyond what we were planning and doing at all times. As far as I remember noone objected at the time. Certainly there were no significant objections from either the RIPE community or the RIPE NCC membership. I find it aggrevating to be critisised about this *long* after the fact when indeed the channels were wide open at the time, as they always are. Daniel

1 2

DNS Maintenance on ns.ripe.net, 10 Okt
by Sjoerd Oostdijck 08 Oct '07

08 Oct '07

[Apologies for duplicate e-mails.] Dear Colleagues, On Wednesday, 10 Oktober 2007, we will update our DNS server ns.ripe.net between 17:00 and 18:00 (UTC). During this period, it will not be able to answer DNS queries. We apologise for any inconvenience this may cause. If you have any questions or concerns about this, please send an e-mail to <dns-help(a)ripe.net>. Regards, Sjoerd Oostdijck, DNS Services RIPE NCC

1 0