- ripe-list - mailman.ripe.net

Reminder - RIPE NCC Regional Meeting, Moscow 16-18 June 2004
by Membership Liaison Officer 19 May '04

19 May '04

[Apologies for duplicate emails] Dear Colleague, We would like to remind you that the RIPE NCC Regional Meeting in Moscow will be held 16 - 18 June 2004 at the Hotel Metropol, Moscow, Russia. Attendance to the RIPE NCC Regional Meeting is open and free of charge. However, attendees are responsible to cover their own travel and accommodation costs. REGISTRATION To register, please see: http://www.ripe.net/cgi-bin/moscow-reg Please note that registration closes on 7 June 2004. AGENDA The Regional Meeting draft agenda has been updated and can be found at: http://www.ripe.net/ripencc/regional-meetings/moscow-2004/agenda.html MORE INFORMATION More information about the RIPE NCC Regional Meeting, Moscow is available from: http://www.ripe.net/ripencc/regional-meetings/moscow-2004/ Any further questions can be sent directly to: <contact(a)ripe.net>. Regards, Nathalie Dougall Membership Liaison Officer RIPE NCC http://www.ripe.net

1 0

RIRs and IPv6 Groups Pledge Support of Global IPv6 Deployment
by Paul Rendek 12 May '04

12 May '04

Dear Colleagues, The RIRs, the IPv6 Task Forces, and the IPv6 Forum have issued a joint press release detailing co-operative efforts in support of global IPv6 deployment. The press release is available on the RIPE NCC website at: http://www.ripe.net/ipv6/ipv6-support-20040512.html Regards, Paul Rendek Head of Member Services and Communications RIPE NCC

1 0

Call for volunteers for Policy Development Process
by Hans Petter Holen 11 May '04

11 May '04

Dear Address Policy Working Group, At recent RIPE meetings we have discussed how to better document the RIPE policy development process. This will not only improve openness and transparency, but may also encourage participation from a wide audience, including those that are not able to attend RIPE meetings. At the Address Policy working group meeting last week, I called for volunteers to help writing the documentation for this process. I further proposed a timeline for the task to result in drafts to be delveopled before the next wg meeting. A mailing list has been set up, to discuss the process. It is open to everyone. You can subscribe at the URL below. http://www.ripe.net/mailman/listinfo/ripe-pdp The list is publicly archived at: http://www.ripe.net/ripe/mail-archives/ripe-pdp/ We'd like to start the discussion from 17 May[1], to continue over the summer. Our goal is to have completed work by mid November. The proposed timeline and more information can be found in last week's presentation to the Address Policy WG, available from: http://www.ripe.net/ripe/meetings/ripe-48/presentations/ripe48-ap- policy-dev.pdf Webcasts of last week' Address Policy WG sessions can be found on the web site at: mms://webcast.ripe.net/ripe-48/ap-1.wmv mms://webcast.ripe.net/ripe-48/ap-2.wmv Looking forward to your participation, Hans Petter [1]Norway's Independence Day

1 0

RIPE-48 overall agenda in vcalendar format
by Patrik Fältström 02 May '04

02 May '04

This is created on a Mac using iCalendar, and I have not verified how compliant it _really_ is to the vcalendar standard. But, if you are lucky, you might be able to import it into whatever you might use. paf

1 0

RIPE 48 meeting reminder
by RIPE NCC Meeting Registration 29 Apr '04

29 Apr '04

Dear Colleagues, The RIPE 48 meeting is less than one week away. RIPE 48 will be held from 3 - 7 May 2004 at the NH Grand Hotel Krasnapolsky in Amsterdam, the Netherlands. AGENDAS HAVE BEEN UPDATED For the latest RIPE 48 agendas please see: http://www.ripe.net/ripe/meetings/ripe-48/meeting-plan.html REGISTRATION To register for RIPE 48 please see: https://www.ripe.net/cgi-bin/mtgreg ASO GENERAL ASSEMBLY On Wednesday, 5 May 2004, the fifth Address Supporting Organization (ASO) General Assembly meeting will be held from 6pm. This meeting will be hosted alongside the RIPE 48 Meeting at the Grand Hotel Krasnapolsky, Amsterdam, and is open to all parties with an interest in the activities of the ASO. The ASO General Assembly is free of charge and you do not need to be registered at the RIPE Meeting to attend. More information about the ASO General Assembly is available at: http://www.aso.icann.org/index.html RIPE 48 INFORMATION For further information on RIPE 48 please see: http://www.ripe.net/ripe/meetings/ripe-48/index.html Should you have any further questions, please do not hesitate to contact us at: <meeting(a)ripe.net> Regards Nick Hyrka Communications Manager RIPE NCC

1 0

RIPE 48 meeting is less than two weeks away, 3- 7 May 2004
by RIPE NCC meeting coordinator 21 Apr '04

21 Apr '04

Dear Colleagues, RIPE 48 commences less than two weeks from now, 3 - 7 May 2004 at the NH Grand Hotel Krasnapolsky in Amsterdam, the Netherlands. REGISTRATION IS OPEN! To register for RIPE 48 please see: https://www.ripe.net/cgi-bin/mtgreg MEETING FEE The registration fee for this meeting is EUR 400. However, if payment is received before 1 May at 16:00 (CET) you will receive a prepayment discount of EUR 50. The registration form and more information can be found at: https://www.ripe.net/cgi-bin/mtgreg AGENDA For more information about the agenda for RIPE 48 please see: http://www.ripe.net/ripe/meetings/ripe-48/meeting-plan.html ACCOMMODATION Rooms are still available at special rates for meeting attendees at the NH Grand Hotel Krasnapolsky. For further information please see: http://www.ripe.net/ripe/meetings/ripe-48/hotel-information.html TRAVEL VISA FOR THE NETHERLANDS Participants requiring a visa to enter the Netherlands are advised to begin the required procedures as soon as possible. The RIPE NCC Conference Co-ordinator is pleased to provide letters of invitation to those attendees requiring them. RIPE 48 INFORMATION For further information on RIPE 48 please see: http://www.ripe.net/ripe/meetings/ripe-48/index.html Should you have any further questions, please do not hesitate to contact us at: <meeting(a)ripe.net> Regards Camilla Meidell Conference Coordinator RIPE NCC

1 0

RIPE NCC Regional Meeting, Moscow, 16-18 June 2004
by Membership Liaison Officer 19 Apr '04

19 Apr '04

[Apologies for duplicate emails] Dear Colleagues, The RIPE NCC is pleased to announce the RIPE NCC Regional Meeting, Moscow, to be held 16 - 18 June 2004 at the Hotel Metropol, Moscow, Russia. Registration for the Regional Meeting opens 19 April 2004. Attendance to the RIPE NCC Regional Meeting is open and free of charge. However, attendees are responsible to cover their own travel and accommodation costs. To register, please see: http://www.ripe.net/cgi-bin/moscow-reg The RIPE NCC Regional Meeting will focus on Internet resource allocation and Internet management issues including: - How to participate in and influence IP address management policy-making; - The industry self-regulatory open structures and processes used by the RIPE NCC and the global Internet community; - Are we running out of IPv4 address space?; - An update on IPv6; - Local, Regional and Global Internet Working and Routing; - Domain Name management on the Internet; - Root Server Operations The Regional Meeting draft agenda can be found at: http://www.ripe.net/ripencc/regional-meetings/moscow-2004/agenda.html RIPE and the RIPE NCC will explain their roles in the administration of the Internet infrastructure as well as specific aspects in managing and operating the Internet infrastructure. The discussions will be directly related to the particular needs and concerns surrounding these issues in the region. The current draft meeting agenda reflects our intentions. However, it requires active participation from the local community to discuss specific issues of the region. The RIPE NCC has reserved several presentation opportunities for those with local knowledge of Internet management and operational issues affecting the region. If your organisation wishes to provide a presentation or suggest a relevant topic, please send your proposal by e-mail to: <contact(a)ripe.net> The RIPE NCC is one of four Regional Internet Registries (RIRs) that provide Internet resource allocation, registration services and co-ordination activities that support the operation of the Internet globally. The RIPE NCC is an independent, not-for-profit membership organisation that provides services to members in its service region currently covering Europe, the Middle East, Central Asia and African countries located north of the equator. Further information about the RIPE NCC and RIPE can be found at: http://www.ripe.net More information about the RIPE NCC Regional Meeting, Moscow is available from: http://www.ripe.net/ripencc/regional-meetings/moscow-2004/ Any further questions can be sent directly to: <contact(a)ripe.net>. Regards, Nathalie Dougall Membership Liaison Officer RIPE NCC

1 0

RIPE 48: Updated Agenda Available
by RIPE NCC Meeting Registration 07 Apr '04

07 Apr '04

Dear Colleagues, RIPE 48 will be held from 3 - 7 May 2004 at the NH Grand Hotel Krasnapolsky in Amsterdam, the Netherlands. Please note that the EOF draft agenda has been updated: http://www.ripe.net/ripe/meetings/ripe-48/eof.html REGISTRATION IS OPEN! To register for RIPE 48 please see: https://www.ripe.net/cgi-bin/mtgreg MEETING FEE The registration fee for this meeting is EUR 400. However, if payment is received before 1 May at 16:00 (CET) you will receive a prepayment discount of EUR 50. The registration form and more information can be found at: https://www.ripe.net/cgi-bin/mtgreg AGENDA For more information about the agenda for RIPE 48 please see: http://www.ripe.net/ripe/meetings/ripe-48/meeting-plan.html ACCOMMODATION Rooms are still available at special rates for meeting attendees at the NH Grand Hotel Krasnapolsky. For further information please see: http://www.ripe.net/ripe/meetings/ripe-48/hotel-information.html TRAVEL VISA FOR THE NETHERLANDS Participants requiring a visa to enter the Netherlands are advised to begin the required procedures as soon as possible. The RIPE NCC Conference Co-ordinator is pleased to provide letters of invitation to those attendees requiring them. RIPE 48 INFORMATION For further information on RIPE 48 please see: http://www.ripe.net/ripe/meetings/ripe-48/index.html Should you have any further questions, please do not hesitate to contact us at: <meeting(a)ripe.net> Regards Camilla Meidell Conference Coordinator RIPE NCC

1 0

Program for EOF @ RIPE-48
by Daniel Karrenberg 07 Apr '04

07 Apr '04

** The EOF will start only after Lunch. ** There will be *no* morning sessions on Monday! Watch http://www.ripe.net/ripe/meetings/ripe-48/eof.html for possible updates. Monday, May 3rd 2004 1400 - 1530 Tutorial: Practical Strategies for IP Traffic Engineering and Enhancing Core network Availability Presenters: John Evans (Cisco), Arman Maghbouleh (Cariden) 1530 - 1600 C o f f e e 1600 - 1730 Tutorial Part 2 Tuesday, May 4th 2004 0900 - 1030 Applications of Bidirectional Forwarding Detection (BFD) Presenter: Rahul Aggarwal (Juniper) Nemecis: A tool to analyze the IRR registries Presenter: Georgos Siganos (UC Riverside) To be Announced NN 1030 - 1100 C o f f e e 1100 - 1230 Address Space Hijacking How Operators Can Protect Themselves & Their Customers Presenters: Leslie Nobile (ARIN), Leo Vegoda (RIPE NCC) Rob Thomas (Team Cymru/Cisco) (Tentative) ---- "Practical Strategies for IP Traffic Engineering and Enhancing Core network Availability" John Evans (Cisco) Arman Maghbouleh (Cariden) MPLS traffic engineering (TE) is often considered as synonymous with making more efficient use of network bandwidth and/or improving network availability via the capabilities of TE Fast Re-route (FRR). This session considers the theory behind traffic engineering in general, together with the benefits, limitations, and deployment considerations of MPLS TE in the context of IP traffic engineering and engineering core network availability. Consideration is also given to alternative technologies such as IGP metric based traffic engineering and IGP fast convergence, and to how quatitive decisions can be made on the relative benefits of the different approaches. http://www.cariden.com/apricot/TE_Beyond_MPLS_apricot_04.pdf ------ "Applications of Bidirectional Forwarding Detection (BFD)" Rahul Aggarwal (Juniper) This presentation describes various applications of BFD in service provider networks. BFD is emerging as a widely applicable forwarding detection tool. It can be used to reduce failure detection times, improve convergence and aid operations. Several service providers are looking at deploying it. BFD makes it possible to support SLAs of applications such as voice over IP, by allowing end to end sub-second failure detection. It is an ubiquitous OAM tool and can be used for IGP adjacencies, static IP routes, E-BGP peers, MPLS LSPs and IP/GRE tunnels. The talk will start with an overview of BFD to establish the context of the presentation. The application of BFD in the access network will be stressed as a means to achieve edge availability. Particularly BFD between a router and a host will be discussed as a means to fill the last mile failure detection void. Usage of BFD for IGP fast convergence will be described, where its particularly useful on ethernet links. The relevance of BFD for static IP routes and E-BGP peers will be described. This is relevant between a router and hosts eg. web servers and VoIP media gateways. BFD over ethernet will be introduced for fault detection between a router and a switch. BFD can also be used as an OAM tool on IP/GRE tunnels and for MPLS LSPs. The relevant mechanisms for this will be discussed. Voice over IP will be used as a case study to describe how BFD can be used to achieve end to end sub-second failure detection. - Bidirectional Forwarding Detection, D. Katz, D. Ward, draft-katz-ward-bfd-00.txt - BFD for MPLS LSPs: Rahul Aggarwal and Kireeti Kompella draft-raggarwa-mpls-bfd-00.txt - BFD for IPv4 and IPv6 (Single Hop), D. Katz, D. Ward, draft-katz-ward-bfd-v4v6-1hop-00.txt ----- "Nemecis: A tool to analyze the IRR registries" Georgos Siganos (University of California Riverside) In this talk, we will present a brief analysis on the IRR and the quality of information they contain. The IRR effort provides a voluntary detailed repository of BGP policy information that has not reached its full potential for three reasons: a) ISPs have limited incentives to maintain their policy, b) extracting useful information is far from trivial, and c) the accuracy of the data is uncertain. Using our tool Nemecis we try to address the last two issues. First, we can check the registered policies for correctness and then for freshness against BGP routing tables. We found that even though RIPE is the most accurate registry, only 34% (for June 22 2003) of the ASes pass all our tests. Our tool consists of two parts: first we have an easy to query relational database, where the policies are stored in tables and not as simple text. Second, we have a web based front end so that ISPs can easily check the result of our analysis. A demo of the tool exists at the following location: http://ira.cs.ucr.edu:8080/Nemecis http://www.nanog.org/mtg-0402/pdf/siganos.pdf http://www.cs.ucr.edu/~siganos/papers/Nemecis.pdf ----- "Address Space and AS Number Hijacking How Operators Can Protect Themselves & Their Customers " Leslie Nobile (ARIN) Leo Vegoda (RIPE NCC) Rob Thomas (Team Cymru/Cisco) (Tentative) 1. Definition and scope of the hijacking problem: Over the last year to 18 months we have seen the rise of address space hijacking. Addresses are re-registered from their legitimate users to third parties without proper authority. The networks are often used to send spam and host pornography. All four RIRs have "ask and ye shall receive" like policies. However, the groups hijacking address space rarely want to use them because their activities are unpopular. The address space they use is quickly placed on blacklists by network administrators. Consequently, the need a regular supply of fresh address space. 3. Historical perspective: An explanation of the "Cheers" legacy. The world has changed since the early days of the Internet. The networking community has grown and people no longer know everyone's name or nic-hdl. Instead, they rely on the registration information published in the RIR databases and various Routing Registries. However, one legacy of the early days is the 'bitty' security on many early registrations. 4. Examples of recent hijackings (in the RIPE NCC region) We might describe some tuypical examples from 2004. We can show the kind of modus operandi used by hijackers. 5. Actions taken by the RIRs to combat this problem We'll describe changes in ARIN and RIPE NCC procedures. We'll also describe new roles people can contact and registration hints they can watch for e.g. whois -ipn RR-RIPE Network operators need to be aware of recent changes in database security mechanisms, such as the deprecation of NONE in the APNIC and RIPE databases, the introduction of the more secure MD5-PW and the introduction of X.509 as an auth scheme for the RIPE database. They also need to know about the introduction of "Org" objects in the RIPE database and how these "Org" objects can be used when accepting new customers and their routes. 6. Actions that the operator community could take to protect themselves and their customers' registrations and networks A look at how the miscreants make use of the addresses and AS Numbers they hijack in the registry databases.

1 0

New IPv4 blocks allocated to RIPE NCC
by RIPE NCC Announcement 05 Apr '04

05 Apr '04

[Apologies for duplicate mails] Dear Colleagues, The RIPE NCC received the IPv4 address ranges 85.0.0.0/8, 86.0.0.0/8, 87.0.0.0/8 and 88.0.0.0/8 from the IANA in April 2004. We will begin allocating from these ranges in the near future. The minimum allocation size for these four /8s has been set at /21. You may wish to adjust any filters you have in place accordingly. More information on the IP space administered by the RIPE NCC can be found on our web site at: <http://www.ripe.net/ripe/docs/smallest-alloc-sizes.html> Additionally, please note that two "pilot" prefixes are being announced from each /8. The prefixes are: 85.192.0.0/16 & 85.255.248.0/21 86.192.0.0/16 & 86.255.248.0/21 87.192.0.0/16 & 87.255.248.0/21 88.192.0.0/16 & 88.255.248.0/21 They all originate in AS12654. More information on this "pilot" activity is available in the draft document "De-Bogonising New Address Blocks" which can be found at: <http://www.ripe.net/ripe/draft-documents/deboganising-draft.html> Best regards, -- leo vegoda Registration Services Manager RIPE NCC

1 0