- ripe-list - mailman.ripe.net

RIPE 58: Registration is Now Open
by RIPE NCC Meeting Coordinator 17 Feb '09

17 Feb '09

Dear Colleagues, Online registration for the RIPE 58 Meeting is now open. RIPE 58 will be held from 4-8 May, 2009, at the NH Hotel Krasnapolsky, in Amsterdam, the Netherlands. Registration ---------------- You can register online for RIPE 58 at: https://lirportal.ripe.net/lirportal/meeting/register/61 Meeting Fee ----------------- The registration fee for the meeting is EUR 400. This covers the full RIPE Meeting week. You will receive a EUR 50 discount if your payment is received before 17:00 UTC on Friday, 1 May 2009. Day Tickets ----------------- Day tickets are also available online and cost EUR 125 per day. Day tickets can also be purchased at the Registration Desk during the meeting. Student Discount ----------------- Tickets for students costs EUR 175. You must show a valid international student card upon arrival at the meeting. This discount does not apply to day tickets or to RIPE Dinner tickets. Attend RIPE 58 for Free ---------------------- If you are a *new* Local Internet Registry (LIR), you are entitled to *two* free RIPE Meeting tickets as part of your membership. You can find out more about how to use your RIPE Meeting tickets at: http://www.ripe.net/ripe/meetings/new-lir.html Travel Visa for the Netherlands ------------------------------ If you require a visa to enter the Netherlands, please request one as soon as possible. We are happy to provide you with an invitation letter upon request after you have completed the meeting registration. Sponsorships -------------- Sponsorship opportunities are available. For more information please contact <meeting(a)ripe.net>. Meeting Agenda ---------------- The meeting agenda will be published shortly at: http://www.ripe.net/ripe/meetings/ripe-58/ More Information ------------------ If you have questions, please contact <meeting(a)ripe.net>. Please also check the meeting homepage regularly for updated information: http://www.ripe.net/ripe/meetings/ripe-58/ Regards, Camilla Meidell Conference Coordinator RIPE NCC

1 0

Final Call For Support Statements on Nominees to ICANN Board
by Axel Pawlik 11 Feb '09

11 Feb '09

[Apologies for duplicate e-mails.] Forwarded on behalf of the Address Supporting Organization (ASO): ----------------------------------------------------------------------------------------- Dear Colleagues, This is a final reminder that the comment period for nominees to the ASO's ICANN Board seat closes at 18:00 UTC on 20 April 2007. Following a public nomination period, the ASO Address Council (ASO AC) selected the final set of candidates to fill the ASO seat on the ICANN Board currently held by Raimundo Beca, whose term expires in June 2007. The candidates are: - Al-Din J. Kadhem Al-Radhi - Smain Aouissi - Raimundo Beca - Vikram Gupta - Jordi Palet Martinez - Remco Van Mook - Shahmeet Singh - Kuo-Wei Wu In May 2007, the ASO AC will make its final selection to appoint one of these individuals to fill the ASO Board seat. To aid them in making their final selection, the ASO AC members request your comments and statements of support for these candidates. If you would like to add a statement of support for any candidate, please send it to the ASO AC Nominations Committee at: board-nomms(a)aso.icann.org All comments received are being published on the ASO website. To view them, follow the links for each candidate at: http://www.aso.icann.org/elections Kind Regards, ASO Secretariat ---------------------- Axel Pawlik Managing Director RIPE NCC

2 1

RIPE NCC Supporter Agreement
by Axel Pawlik 26 Jan '09

26 Jan '09

Dear Colleagues, During the RIPE NCC's General Meeting in October 2008, members accepted the proposed "RIPE NCC Supporter Agreement" enabling non-members to show their support for the RIPE NCC. Any organisation or individual can become a RIPE NCC supporter. You do not have to be a member of the RIPE NCC to show your support. Supporters can attend General Meetings but do not have any voting rights and cannot request Internet number resources or related member services from the RIPE NCC. For more information about becoming a supporter, the fees involved and for the application form, please see: http://www.ripe.net/info/ncc/supporters/ If you have questions about the RIPE NCC Supporter Agreement, please email <ncc(a)ripe.net>. Regards, Axel Pawlik Managing Director RIPE NCC

1 0

NRO Executive Council Roles for 2009
by Adiel A. Akplogan 20 Jan '09

20 Jan '09

[Apologies for duplicate emails] Dear Colleagues, As of 1 January, 2009, the Number Resource Organization's (NRO) Executive Council (EC) positions have rotated. This is in line with the NRO procedure. The EC roles for 2009 are: Chairman: Adiel Akplogan (AfriNIC) Secretary: Axel Pawlik (RIPE NCC) Treasurer: Raul Echeberria (LACNIC) Members: Paul Wilson (APNIC) and John Curran (ARIN) For more information about the NRO please see: http://www.nro.net The Address Supporting Organization (ASO) ----------------------------------------------------- As the secretariat of the NRO, the RIPE NCC will also support ASO Address Council (AC) operations during 2009. For more information about the ASO please see: http://aso.icann.org/ If you have any questions about the NRO or the ASO, please contact nro(a)nro.net <mailto:nro@nro.net>. Regards, Adiel A. Akplogan Chairman NRO

1 0

RIPE NCC offices closed on 25-26 December 2008 and 1 January 2009
by Saskia van Gorp 22 Dec '08

22 Dec '08

Dear Colleagues, Our offices will be closed on Thursday 25 December (Christmas Day), Friday 26 December (Boxing Day) and Thursday 1 January (New Year's Day). Normal office hours will resume on respectively Monday 29 December 2008 and Friday 2 January 2009. The RIPE NCC wishes you a Merry Christmas and a Happy New Year. Regards, Saskia van Gorp Front Office Manager RIPE NCC

1 0

RIPE NCC service outage update, 17 December 2008
by Andrei Robachevsky 17 Dec '08

17 Dec '08

Dear Colleagues, Due to a loop problem in out layer 2 infrastructure starting from 11:20 UTC we experienced a high volume of traffic flooding the RIPE NCC network. That caused intermittent high packet loss and affected all our online services. The issue was resolved at 15:00 UTC. All services are back to normal. We apologise for the inconvenience. Best Regards, Andrei Robachevsky

1 0

Consensus on RIPE message to the NTIA on signing the root
by Rob Blokzijl 23 Nov '08

23 Nov '08

Dear Colleagues, we have received close to 40 responses to the proposed RIPE statement on signing the root. All of them were in favour of the statement, so we can safely conclude that we have consensus. The statement will therefore be submitted to the NTIA as the RIPE position on signing the root. Thanks to all who contributed in reaching this outcome. Regards, Rob Blokzijl

1 0

Call for Support: RIPE response to the US NTIA's NoI
by Peter Koch 21 Nov '08

21 Nov '08

Dear RIPE Community, as mentioned in my email sent on Monday, the DNS working group has come up with a response to the US NTIA's Notice of Inquiry (NoI) regarding the introduction of DNSSEC for the DNS root zone (for details see <http://www.ntia.doc.gov/DNS/DNSSEC.html>). The text below reflects the consensus of the DNS working group. As a follow up to our earlier efforts (see below), the DNS WG suggests that the response to the NTIA come from the broader RIPE community. So, this is the DNS WG's request for your support and endorsement of the proposal. Please read the text and voice your support or opposition. As mentioned earlier, we will have to meet an external deadline. Therefore, we are not looking for editorial suggestions. Regrettably, it is impractical to further refine or reword the text, since that would require more editing cycles and new consensus calls, which time won't permit. The WG chairs' collective and the RIPE Chair have agreed that it needs a binary decision on the proposal as presented here. It is possible that the text doesn't represent the optimum for everyone. Still, please consider whether you can support it as a community statement. In any case, the NoI is open for anybody, so you might want to send your individual response and/or contribute to other group efforts, as well. Clarifying questions are welcome, probably best asked on the DNS WG mailing list or to the DNS WG co-chairs <http://www.ripe.net/ripe/wg/dns/index.html>. Given the 24 Nov deadline and to allow some time for the evalutaion of the list traffic, you are kindly asked to send your explicit statements to this list no later than Friday, 21 Nov 2008 12:00 UTC. Thanks in advance for your consideration! -Peter Koch [DNS WG co-chair] ----------------------------------------------------------------------------- # # $Id: ntia-draft,v 1.9 2008/11/13 20:20:41 jim Exp $ # The RIPE community thanks the NTIA for its consultation on proposals to sign the root and is pleased to offer the following response to that consultation. We urge the adoption of a solution that leads to the prompt introduction of a signed root zone. Our community considers the introduction of a signed root zone to be an essential enabling step towards widespread deployment of Secure DNS, DNSSEC. This view is supported by the letter from the RIPE community to ICANN as an outcome of discussions at the May 2007 RIPE meeting in Tallinn: http://www.ripe.net/ripe/wg/dns/icann-root-signing.pdf. It is to be expected that a community as diverse as RIPE cannot have a unified set of detailed answers to the NTIA questionnaire. However several members of the RIPE community will be individually responding to that questionnaire. We present the following statement as the consensus view of our community about the principles that should form the basis of the introduction of a signed DNS root. 1. Secure DNS, DNSSEC, is about data authenticity and integrity and not about control. 2. The introduction of DNSSEC to the root zone must be made in such a way that it is accepted as a global initiative. 3. Addition of DNSSEC to the root zone must be done in a way that does not compromise the security and stability of the Domain Name System. 4. When balancing the various concerns about signing the root zone, the approach must provide an appropriate level of trust and confidence by offering an optimally secure solution. 5. Deployment of a signed root should be done in a timely but not hasty manner. 6. Updates from TLD operators relating to DNSSEC should be aligned with the operational mechanisms for co-ordinating changes to the root zone. 7. If any procedural changes are introduced by the deployment of DNSSEC they should provide sufficient flexibility to allow for the roles and processes as well as the entities holding those roles to be changed after suitable consultations have taken place. 8. Policies and processes for signing the root zone must be transparent and trustworthy, making it straightforward for TLDs to supply keys and credentials so the delegations for those TLDs can benefit from a common DNSSEC trust anchor, the signed root. 9. There is no technical justification to create a new organisation to oversee the process of signing of the root. 10. No data should be moved between organisations without appropriate authenticity and integrity checking, particularly the flow of keying material between a TLD operator and the entity that signs the root. 11. The public part of the key signing key must be distributed as widely as possible. 12. The organisation that generates the root zone file must sign the file and therefore hold the private part of the zone signing key. 13. Changes to the entities and roles in the signing process must not necessarily require a change of keys. -----------------------------------------------------------------------------

22 21

Re: Call for Support: RIPE response to the US NTIA's NoI
by Daniele Vannozzi 20 Nov '08

20 Nov '08

Dear Peter, I support this document. > # > # $Id: ntia-draft,v 1.9 2008/11/13 20:20:41 jim Exp $ > # Best regards, Daniele Vannozzi Registry ID: it.cnr

1 0

>>: [regional-russia] RIPE statement to NTIA - need your action - corrected]
by Natalya V Romashova 20 Nov '08

20 Nov '08

We agree with the RIPE letter and proposals on designing of signing the DNS root zone. We wait with impatience for DNSSEC testing activities. Best regards, Head of Operators' VAS department OAO "VimpelCom" Nataliya V. Romashova loc. 09 53395 tel. +7 495-961-31-86 #53395 tel. +7(495)743-01-70 fax. +7(495)985-95-55 e-mail: rom(a)beeline.ru Subject: Call for Support: RIPE response to the US NTIA's NoI From: Peter Koch <pk(a)DENIC.DE> Date: Fri, 14 Nov 2008 23:59:09 +0100 To: ripe-list(a)ripe.net Dear RIPE Community, as mentioned in my email sent on Monday, the DNS working group has come up with a response to the US NTIA's Notice of Inquiry (NoI) regarding the introduction of DNSSEC for the DNS root zone (for details see <http://www.ntia.doc.gov/DNS/DNSSEC.html>). The text below reflects the consensus of the DNS working group. As a follow up to our earlier efforts (see below), the DNS WG suggests that the response to the NTIA come from the broader RIPE community. So, this is the DNS WG's request for your support and endorsement of the proposal. Please read the text and voice your support or opposition. As mentioned earlier, we will have to meet an external deadline. Therefore, we are not looking for editorial suggestions. Regrettably, it is impractical to further refine or reword the text, since that would require more editing cycles and new consensus calls, which time won't permit. The WG chairs' collective and the RIPE Chair have agreed that it needs a binary decision on the proposal as presented here. It is possible that the text doesn't represent the optimum for everyone. Still, please consider whether you can support it as a community statement. In any case, the NoI is open for anybody, so you might want to send your individual response and/or contribute to other group efforts, as well. Clarifying questions are welcome, probably best asked on the DNS WG mailing list or to the DNS WG co-chairs <http://www.ripe.net/ripe/wg/dns/index.html>. Given the 24 Nov deadline and to allow some time for the evalutaion of the list traffic, you are kindly asked to send your explicit statements to this list no later than Friday, 21 Nov 2008 12:00 UTC. Thanks in advance for your consideration! -Peter Koch [DNS WG co-chair] ----------------------------------------------------------------------------- # # $Id: ntia-draft,v 1.9 2008/11/13 20:20:41 jim Exp $ # The RIPE community thanks the NTIA for its consultation on proposals to sign the root and is pleased to offer the following response to that consultation. We urge the adoption of a solution that leads to the prompt introduction of a signed root zone. Our community considers the introduction of a signed root zone to be an essential enabling step towards widespread deployment of Secure DNS, DNSSEC. This view is supported by the letter from the RIPE community to ICANN as an outcome of discussions at the May 2007 RIPE meeting in Tallinn: http://www.ripe.net/ripe/wg/dns/icann-root-signing.pdf. It is to be expected that a community as diverse as RIPE cannot have a unified set of detailed answers to the NTIA questionnaire. However several members of the RIPE community will be individually responding to that questionnaire. We present the following statement as the consensus view of our community about the principles that should form the basis of the introduction of a signed DNS root. 1. Secure DNS, DNSSEC, is about data authenticity and integrity and not about control. 2. The introduction of DNSSEC to the root zone must be made in such a way that it is accepted as a global initiative. 3. Addition of DNSSEC to the root zone must be done in a way that does not compromise the security and stability of the Domain Name System. 4. When balancing the various concerns about signing the root zone, the approach must provide an appropriate level of trust and confidence by offering an optimally secure solution. 5. Deployment of a signed root should be done in a timely but not hasty manner. 6. Updates from TLD operators relating to DNSSEC should be aligned with the operational mechanisms for co-ordinating changes to the root zone. 7. If any procedural changes are introduced by the deployment of DNSSEC they should provide sufficient flexibility to allow for the roles and processes as well as the entities holding those roles to be changed after suitable consultations have taken place. 8. Policies and processes for signing the root zone must be transparent and trustworthy, making it straightforward for TLDs to supply keys and credentials so the delegations for those TLDs can benefit from a common DNSSEC trust anchor, the signed root. 9. There is no technical justification to create a new organisation to oversee the process of signing of the root. 10. No data should be moved between organisations without appropriate authenticity and integrity checking, particularly the flow of keying material between a TLD operator and the entity that signs the root. 11. The public part of the key signing key must be distributed as widely as possible. 12. The organisation that generates the root zone file must sign the file and therefore hold the private part of the zone signing key. 13. Changes to the entities and roles in the signing process must not necessarily require a change of keys. -----------------------------------------

1 0