- ipv6-wg - mailman.ripe.net

New document available: RIPE-501 Requirements For IPv6 in ICT Equipment
by Marco Hogewoning 25 Nov '10

25 Nov '10

Dear community, A new ripe document, RIPE-501, has been published "Requirements For IPv6 in ICT Equipment". This document aims to be a guide of what to ask for exactly when IPv6 is a requirement in a tender or some contract and lists the various applicable RFCs for specific kinds of ICT equipment. The document is available on http://www.ripe.net/ripe/docs/ripe-501.html Please note that when using this document as a reference, as with any RIPE document, it might get superseded by new versions in the future. Many thanks to the authors and everybody who helped with proof reading, translation and feedback. Marco, David & Shane, co-chairs of the IPv6 working group

2 1

AUTO: Nicht erreichbar bis 29.11.2010 / Out of Office until 29.11.2010
by Joachim Strohbach 25 Nov '10

25 Nov '10

Ich bin abwesend und kehre am 29.11.2010 zurück. Danke für Ihre E-Mail-Nachricht. Ich bin bis 29. November 2010 nicht im Büro. In dringenden Angelegenheiten kontaktieren Sie bitte DENIC IT-Services (E-Mail: its(a)denic.de, Tel: (069) 27235-160 oder -250). ----- Thank you for your email message. I am not in the office until 29 November 2010. In urgent cases please contact DENIC IT-Services (e-mail: its(a)denic.de, Tel: +49 69 27235-160 or -250). -- Joachim Strohbach Leiter IT-Services / Head of IT-Services DENIC eG Kaiserstraße 75-77 60329 Frankfurt am Main GERMANY E-Mail: strohbach(a)denic.de Fon: +49 69 27235-123 Fon: +49 69 27235-160 (Assistance) Fon: +49 69 27235-250 (IT-Services) Fax: +49 69 27235-239 SIP-URI: sip:123@denic.de http://www.denic.de PGP-KeyID: 0x7A8A00FF, Fingerprint: 30AB 0F15 17D3 995F CA50 F0A8 EA30 B915 7A8A 00FF Angaben nach § 25a Absatz 1 GenG: DENIC Domain Verwaltungs- und Betriebsgesellschaft eG (Sitz: Frankfurt am Main) Vorstand: Sabine Dolderer, Helga Krüger, Carsten Schiefner, Dr. Jörg Schweiger Vorsitzender des Aufsichtsrats: Elmar Knipp Eingetragen unter Nr. 770 im Genossenschaftsregister, Amtsgericht Frankfurt am Main Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht "New document available: RIPE-501 Requirements For IPv6 in ICT Equipment" gesendet am 24.11.10 20:48:45. Diese ist die einzige Benachrichtigung, die Sie empfangen werden, während diese Person abwesend ist.

1 0

Last Call (20101117): Requirements For IPv6 in ICT Equipment
by David Kessens 24 Nov '10

24 Nov '10

Working Group, The "Requirements For IPv6 in ICT Equipment" draft seems to have reached a level of maturity that is enough to issue a formal Last Call to determine whether it is ready for publication as a RIPE document. The latest version is available here: http://www.ripe.net/ripe/draft-documents/ipv6-ict-requirements.html We would appreciate if you let us know by the end of November 17, 2010 if you have read the document and whether you support the publication of the document. As long as we get at least 8 statements of support and no significant issues are raised, we will ask the RIPE NCC to publish the document after fixing minor editorial issues (if found). David, Marco & Shane ---

11 30

Re: [ipv6-wg] Last Call (20101117): Requirements For IPv6 in ICT Equipment
by Marco Hogewoning 23 Nov '10

23 Nov '10

Please for the process, as this is a last call, be very clear wether you are making comments about future versions or if you are objecting against publication of the current document. So far I consider this future improvements and we will go forward with publishing the current text as final. If anybody objects, please state this clearly and we will back out. The authors already agreed to do a second version together with some help from others, at the same time we have stakeholders who would like to get this draft label removed. Groet, MarcoH ----- Reply message ----- From: "Isacco Fontana" <isacco.fontana(a)trentinonetwork.it> Date: Tue, Nov 23, 2010 18:18 Subject: [ipv6-wg] Last Call (20101117): Requirements For IPv6 in ICT Equipment To: <mtinka(a)globaltransit.net> Cc: <ipv6-wg(a)ripe.net>, "Ivan Pepelnjak" <ipepelnjak(a)gmail.com>

2 1

Re: [ipv6-wg] Last Call (20101117): Requirements For IPv6 in ICT Equipment
by Ivan Pepelnjak 23 Nov '10

23 Nov '10

Dear all, As I'm one of the original authors of this document (now nicely hidden behind the "Slovenian IPv6 working group" blob ;) and had a bit to do with MPLS in the past, please allow me to comment on the MPLS-related requirements. 6PE/6VPE ========= Unfortunately, the only way to combine IPv6 with MPLS features like MPLS-TE or FRR today (and in the next few years) is to run IPv4 MPLS core and 6PE/6VPE. The requirement to support 6PE/6VPE is thus MANDATORY, but has to be conditioned the same way mobile IPv6 is. I would therefore suggest that we add the following two bullets to the "Mandatory support" part of the "Router or Layer 3 switch" equipment: * If MPLS functionality (for example, BGP-free core, MPLS TE, MPLS FRR) is requested, the PE-routers and route reflectors MUST support "Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE)" [RFC 4798] * If layer-3 VPN functionality is requested, the PE-routers and route reflectors MUST support "BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN" [RFC 4659] MT IS-IS & MPLS =============== There's another gotcha that we totally missed: MT for IS-IS (RFC 5120) should be mentioned and it should be MANDATORY in combination with MPLS (otherwise you might experience some weird symptoms if you decide to run some IPv6 natively). The "Router or Layer 3 switch" equipment section thus needs two more items: MANDATORY --------- * If MPLS Traffic Engineering is used in combination with IS-IS routing protocol, the equipment MUST support "M-ISIS: Multi Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs)" [RFC 5120] OPTIONAL -------- * When IS-IS routing protocol is requested, the equipment SHOULD support "M-ISIS: Multi Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs)" [RFC 5120] (this support is highly recommended) Best, Ivan Pepelnjak www.ioshints.info

4 4

New draft document available: Requirements For IPv6 in ICT Equipment
by Marco Hogewoning 17 Nov '10

17 Nov '10

(apologies for any duplicate emails) Dear Colleagues, Jan Zorz and Sander Steffan have prepared a document to serve as a guide what the requirements should be when asking for IPv6 in a tender or contract. It is our intention to publish this document as a RIPE document BCP so people can use this as an external reference. The draft version of this document is available at http://www.ripe.net/ripe/draft-documents/ipv6-ict-requirements.html Your comments and feedback can be sent to the IPv6 working group mailing-list on ipv6-wg(a)ripe.net. Regards, Marco Hogewoning IPv6 WG co-chair

7 17

Interactive Graph on RIPE Labs: Networks with IPv6 over Time
by Mirjam Kuehne 16 Nov '10

16 Nov '10

Dear colleagues, On RIPE Labs you can now find an interactive graph (provided by Emile Aben) that shows the percentage of networks (ASes) that announce one or more IPv6 prefixes in the global routing table. You can specify countries and compare the IPv6 deployment by region: https://labs.ripe.net/Members/emileaben/interesting-graph-networks-with-ipv… Kind Regards, Mirjam Kuehne RIPE NCC

5 6

Announcement: RIPE NCC Training Courses
by Training Mailbox 16 Nov '10

16 Nov '10

[Apologies for duplicate e-mails] Dear Colleagues, The RIPE NCC invites you to register for one of our upcoming training courses: - The LIR Training Course This course teaches LIRs how to request Internet number resources and interact with the RIPE NCC. A course outline is available at: http://www.ripe.net/training/lir/outline.html - The Routing Registry Training Course This course teaches LIRs how to use the RIPE Database for routing. A course outline is available at: http://www.ripe.net/training/rr/outline.html - The IPv6 Training Course This course teaches LIRs about the need for IPv6 and includes basic information on how to plan your deployment. A course outline is available at: http://www.ripe.net/training/ipv6/outline.html To see the location of upcoming courses and to register, please use the LIR Portal or complete the registration form on our website at: RIPE NCC Upcoming Courses List & Registration https://lirportal.ripe.net/lirportal/training/course-list.html If you have any questions, please do not hesitate to contact us at <training(a)ripe.net>. Kind regards, Rumy Kanis Training Services Manager RIPE NCC

1 0

Draft agenda RIPE-61: Tuesday November 16th 16:00 - 18:00 CET
by Marco Hogewoning 16 Nov '10

16 Nov '10

Hello, Sorry for beng a bit late. This is the draft agenda for the IPv6 WG sesison in Rome. We have a pretty full programme with lots of interesting examples of what happens when you deploy IPv6 in the real world. 1 opening/administrativa 2 "Experiences from an IPv6-only world" - Jari Arkko/Ari Keranen 3 "Detecting (and fixing!), IPv6 dualstack brokenness" - Tore Aderson 4 "The results on introducing native IPv6 at XS4ALL - Marco Hogewoning 5 "RIPE NCC stats" - Emile Aben 6 "Native IPv6 via xDSL - How to tweak your LNS" - Emanuel Kleindienst 7 "Requirements For IPv6 in ICT Equipment" - Jan Zorz/Sander Steffan 8 "Update on policy proposal 2010-06" - Marco Hogewoning/Remco van Mook See you all in Rome and for those of you who can't make it, this session will be live broadcasted. See http://ripe61.ripe.net/programme/remote-participation/ for more information. On behalf of the IPv6 WG chairs, Marco Hogewoning

2 2

Re: [ipv6-wg] Last Call (20101117): Requirements For IPv6 in ICT Equipment
by Ivan Pepelnjak 10 Nov '10

10 Nov '10

Dear all, As I'm one of the original authors of this document (now nicely hidden behind the "Slovenian IPv6 working group" blob ;) and had a bit to do with MPLS in the past, please allow me to comment on the MPLS-related requirements. 6PE/6VPE ========= Unfortunately, the only way to combine IPv6 with MPLS features like MPLS-TE or FRR today (and in the next few years) is to run IPv4 MPLS core and 6PE/6VPE. The requirement to support 6PE/6VPE is thus MANDATORY, but has to be conditioned the same way mobile IPv6 is. I would therefore suggest that we add the following two bullets to the "Mandatory support" part of the "Router or Layer 3 switch" equipment: * If MPLS functionality (for example, BGP-free core, MPLS TE, MPLS FRR) is requested, the PE-routers and route reflectors MUST support "Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE)" [RFC 4798] * If layer-3 VPN functionality is requested, the PE-routers and route reflectors MUST support "BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN" [RFC 4659] MT IS-IS & MPLS =============== There's another gotcha that we totally missed: MT for IS-IS (RFC 5120) should be mentioned and it should be MANDATORY in combination with MPLS (otherwise you might experience some weird symptoms if you decide to run some IPv6 natively). The "Router or Layer 3 switch" equipment section thus needs two more items: MANDATORY --------- * If MPLS Traffic Engineering is used in combination with IS-IS routing protocol, the equipment MUST support "M-ISIS: Multi Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs)" [RFC 5120] OPTIONAL -------- * When IS-IS routing protocol is requested, the equipment SHOULD support "M-ISIS: Multi Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs)" [RFC 5120] (this support is highly recommended) Best, Ivan Pepelnjak www.ioshints.info

1 0