- ipv6-wg - mailman.ripe.net

Short report on Saudi IPv6 Task Force meeting
by Marco Hogewoning 25 Nov '14

25 Nov '14

Hello, As part of my day job I was close by in the region and the opportunity to visit the 16th meeting of the Saudi Arabian IPv6 Task Force. Still a lot of nice stuff going on down there with a steady progress towards deployment of IPv6. Not only in the more traditional telecoms and connectivity sector, but also with a strong focus on getting the users in other sectors on board such as the banks and the oil industry. A short report can be found on RIPE Labs https://labs.ripe.net/Members/marco_hogewoning/16th-meeting-of-the-saudi-ar… Cheers, Marco (who still has an interest in the topic)

1 0

Re: [ipv6-wg] [address-policy-wg] [Merging ipv6 and address policy mailing lists]
by Yannis Nikolopoulos 24 Nov '14

24 Nov '14

hello, a rather late reply On 11/12/2014 11:26 AM, Wilhelm Boeddinghaus wrote: > Am 12.11.2014 um 08:32 schrieb Aleksi Suhonen: >> Hello, >> >> On 11/09/2014 06:06 PM, Lu wrote: >>> Should we put address policy wh together with IPv6 wg? Why we need >>> two different wg for addressing?the day we start treat IPv6 as normal >>> IP address is the day we really in a world of v6. >> >> In theory, the IPv6 working group and mailing lists are not only about >> address policy. In practice, I do think that a separate mailing list >> for IPv6 at RIPE has outlived its usefulness. In essence, I support >> this proposal. sorry, but this just doesn't make sense. RIPE's IPv6 WG is about promoting IPv6 adoption and there's definitely a long way to go... http://www.ripe.net/ripe/groups/wg/ipv6 > Hi, > > But > please let the forum for technical discussion about IPv6 untouched. We > will need that for the next 10 years until we all have as much > experience with IPv6 as we have with IPv4 today. +1 regards, Yannis > Regards, > > Wilhelm

1 0

Re: [ipv6-wg] [address-policy-wg] [Merging ipv6 and address policy mailing lists]
by Alex Saroyan 13 Nov '14

13 Nov '14

+1 don't merge. Regards /Alex Saroyan Gert Doering <gert(a)space.net> wrote: >Hi, > >On Thu, Nov 13, 2014 at 01:53:21PM +0100, Wilfried Woeber wrote: >> [...] >> > That said, if I was more involved with the address policy WG, I'd also >> > expect to get involved if someone proposed to dump some other WG >> > discussions into "my" mailing list. >> >> Also donning my (past) DB-WG hat for a minute, there's always the possibility >> to include an item like "input from other WGs or TFs" into the WG Meeting's >> draft agenda. I have done that for years, and it worked quite OK (for the >> most recent time in London, receiving input from Routing. So, *that*is no >> reason in my books to talk about dismantling a useful and active WG. >> >> No rocket science here, just a tad of looking across the fence :-) > >Fully agree. And, to come back to where this whole thread started - while >IPv6 WG doesn't *do* policy by charter, there are people in the IPv6 WG >who are interested in IPv6 address policy, but do not regularily follow >the AP WG list. Which is why Erik threw the ball over the fence "you >might be interested in this, so here's a notification so you don't miss it". > > >And, speaking as a member of the IPv6 community, I do not think the idea >to dismantle the IPv6 WG (or it's list) has much merit - there are still >operational technical challenges to IPv6, and it's thus useful to have >a WG focusing on these. AP will take care of addressing challenges (and >if AP does policy things that do not work out operationally, they listen). > >Gert Doering > -- some relevant hats >-- >have you enabled IPv6 on something today...? > >SpaceNet AG Vorstand: Sebastian v. Bomhard >Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann >D-80807 Muenchen HRB: 136055 (AG Muenchen) >Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279

2 1

Re: [ipv6-wg] [address-policy-wg] [Merging ipv6 and address policy mailing lists]
by Jen Linkova 13 Nov '14

13 Nov '14

On Wed, Nov 12, 2014 at 8:32 AM, Aleksi Suhonen <ripe-ml-2012(a)ssd.axu.tm> wrote: >> Should we put address policy wh together with IPv6 wg? Why we need >> two different wg for addressing? Because IPv6 WG is not for addressing. IPv6 is not 'IPv4 with bigger address space'. >the day we start treat IPv6 as normal >> IP address is the day we really in a world of v6. I have no objection to *this* statement, so I'd expect that all discussions related to IPv[4,6] address policy are happening in this mailing list, while IPv6 WG discusses technical aspects of IPv6 deployment. > In theory, the IPv6 working group and mailing lists are not only about > address policy. Exactly. >In practice, I do think that a separate mailing list for > IPv6 at RIPE has outlived its usefulness. I strongly disagree. Shall I read it as a proposal to shut down IPv6 WG as well? I'd object to say the least. There are a lot of topics to discuss on IPv6 WG which do not belong to address policy. Anyway, I'm surprised to see a discussion about shutting down a mailing list happening in *another* mailing list. If community feels like 'there is nothing to discuss in IPv6 WG mailing list anymore' (which does not seem to be a case as I can see from the replies to your message), it should be discussed there. I'm adding ipv6-wg@ to Cc: so people are aware of this discussion, however from my point of view we've seen enough support to keep IPv6 list untouched. -- SY, Jen Linkova aka Furry

6 5

FW: [policy-announce] 2014-12 New Policy Proposal (Allow IPv6 Transfers)
by Erik Bais 11 Nov '14

11 Nov '14

Hi, This email is to inform the people who are subscribed on the IPv6 WG list but not on the Address Policy WG list. There is a policy proposal currently in discussion phase to Allow IPv6 Transfers. > You can find the full proposal at: > https://www.ripe.net/ripe/policies/proposals/2014-12 > We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 28 November 2014. Regards, Erik Bais -----Oorspronkelijk bericht----- Van: policy-announce-bounces(a)ripe.net [mailto:policy-announce-bounces@ripe.net] Namens Marco Schmidt Verzonden: donderdag 30 oktober 2014 13:43 Aan: policy-announce(a)ripe.net CC: address-policy-wg(a)ripe.net Onderwerp: [policy-announce] 2014-12 New Policy Proposal (Allow IPv6 Transfers) Dear colleagues, A proposed change to RIPE Document ripe-589, "IPv6 Address Allocation and Assignment Policy" is now available for discussion. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2014-12 We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 28 November 2014. Regards Marco Schmidt Policy Development Officer RIPE NCC

3 3

[training] RIPE NCC Training Courses January-March 2015
by Training Services 10 Nov '14

10 Nov '14

Dear colleagues, Our training team travels the RIPE NCC service region to deliver training courses to our members without any additional cost. Over the next few months, we'll be in Milan, Madrid, Munich, Podgorica, Prague, Moscow, Riga, Ramallah, Edinburgh, Copenhagen, Amsterdam. Visit the following page to register and to check which training courses we are giving in your area: https://lirportal.ripe.net/training/courses The RIPE NCC delivers the following training courses: - LIR Training Course - RIPE Database Training Course - Basic IPv6 Training Course - Advanced IPv6 Training Course - Routing Security Training Course - DNSSEC Training Course The RIPE NCC delivers the following tailor-made workshops: - Measurements Tools Workshop - Introduction to BGP For more information visit: http://www.ripe.net/lir-services/training/courses With kind regards, Rumy Spratley-Kanis Training Services Manager

1 0

RIPE 69: Test your gear and software without IPv4!
by Marco Hogewoning 03 Nov '14

03 Nov '14

Hello and welcome to London, This message probably only has relevance if you are visiting the RIPE 69 Meeting, But feel free to continue reading even when you are not. As you are setting up wireless you may have noticed a network called ‘IPV6ONLYEXP’. This network is once again setup so you can see if your applications hold up in an environment that only provides you with an IPv6 address. The password is in the bottom of this email. Please note: This network is provided as-is and on a BEST EFFORT basis, the RIPE NCC will NOT PROVIDE SUPPORT. Of course the main functionality will be monitored and acted upon when things go wrong, but ops will be unable to help you with devices or software configuration and/or troubleshooting. The network has a NAT64 gateway attached, which means that you should be able to connect to the whole Internet, even when the service does not support IPv6 yet. This also means that some applications will be confused and complain there is no connectivity, even when there is. This is exactly why we have this setup running, you can find out for yourself what works and what doesn’t. If you find an issue, please feel free to share it on this list. Even more important however, please also file a bug report or send a notification to the creators, so they are aware and hopefully can make it work in the next release. Of course, since we have done this before, we have a few know problems: - For NAT64 to work you must make use of the resolvers as advertised by the network, these are patched to do the translations - A wide variety of Android devices will not be able to pick up the advertised DNS servers and while connected, will fail to work properly - Skype does not work! - A number of IOS apps will complain there is no network, while they actually do work, please try what happens if you ignore those pop-ups So good luck and enjoy the meeting. If you do have questions or want to chat about it, please use this list or find me or Andrew Yourtchenko on site. I would like to thank RIPE NCC, especially Menno, Razvan and Marco v T for helping out and making this possible. The password is “iknowbesteffort”, this is different from the main meeting password :) See you in a bit in London, Marco Hogewoning

1 0

New Document: "IPv6 Troubleshooting for Residential ISP Helpdesks"
by Marco Hogewoning 26 Oct '14

26 Oct '14

Dear colleagues, Collaborative efforts in the BCOP TF have led to the following document, detailing how to troubleshoot IPv6 connectivity. The author(s) have asked us to forward this to the IPv6 Working Group for review, with the intend of publishing this as RIPE Document. To clarify the procedure, any document, when there is consensus within the working group can receive a number and be published as part of the RIPE Document series. As it does not specify any RIPE policy or changes existing policy, we are comfortable in not invoking the formal PDP for this. Please review this document and leave any comments regarding the contents on this list. Also we would like to receive some feedback wether you think this document should be published as a RIPE Document. Please leave your initial comments before Monday 7 November COB, we will carve out some time in the RIPE 69 agenda to talk about this and to decide on the workflow. Regards, Marco Hogewoning co-chair of the IPv6 Working Group

3 9

Draft RIPE 69 Agenda (version 2)
by Marco Hogewoning 26 Oct '14

26 Oct '14

Dear colleagues, Here is an updated agenda for our upcoming session in London, please note that in the previous process we briefly communicated the wrong time and date. Our session will take place on Thursday, 6 November from 09:00 – 10:30 GMT(!). Of course as with all sessions, if you are unable to join us in London, webcast and remote participation will be available via http://ripe69.ripe.net. A. Welcome and Administrativa B. IPv6 Extension Headers Jen Linkova, Google This is a follow up to a presentation at an earlier meeting, presenting some new results C. IPv6 experiences - a RIPE Atlas Anchor project perspective Nathalie Trenaman, RIPE NCC In this presentation Nathalie will present on the IPv6 specific network issues Atlas anchors experienced and how this affected the user measurements. D. Progress and results of implementing IPv6 at the German government Tahar Schaa, Cassini Consulting Another follow up in which Tahar will present some of the results of this project and and report on the progress being made E. Document: "IPv6 Troubleshooting for Residential ISP Helpdesks” Jan Zorz (on behalf of the BCOP TF) We will review the feedback received and discuss how to move forward on publishing this new RIPE Document. D. Transfer of IPv6 Chair Duties Shane and I will formally hand over our duties to the new team: Dave, Jen and Benedikt E. Establishing a Procedure to Elect Chairs There is requirement to document the procedure to re-affirm and replace the working group chairs. This discussion will be led by the new chairs. X. Closing Regards. Marco Hogewoning on behalf of the team: Shane, Jen, Benedikt and Dave

1 0

IPv6 & Android & Facebook
by Daniel Baeza (Red y Sistemas TVT) 21 Oct '14

21 Oct '14

Hi all, I'm writting here since I didnt really know how or where to check whats happening to us. Is any of you experiencing problems loading photos/images from facebook/twitter/instagram/whatever via Android devices with Dual-Stack IPv4/IPv6? Thanks in advance. -- Daniel Baeza

2 1

RIPE69 draft agenda
by MarcoH 21 Oct '14

21 Oct '14

Hello, Our initial draft agenda for the London meeting is online. Our session will be on Thursday 09 November, 11:00. We hope to see you all there and as usual remote participation will be available for those who can't make it to London. We welcome suggestions for any additional topics or talks. Thursday, 9 November 09:00 – 10:30 A. Welcome and Administrativa B. IPv6 Extension Headers Jen Linkova, Google C. Nathalie Trenaman, RIPE NCC IPv6 Program Manager D. Transfer of IPv6 Chair Duties E. Establishing a Procedure to Elect Chairs X. Closing See you in London, MarcoH -- Sent from mobile, sorry for the typos

2 1

Re: [ipv6-wg] RIPE69 draft agenda
by MarcoH 02 Oct '14

02 Oct '14

Goed point, that is why we have drafts :) Should be 6 :) I'll ask my colleagues to change the website if needed. We are on Thursday folk, that is the important bit. But of course you don't want to mis out on any of the other great RIPE 69 days either. Apologies, MarcoH -- Sent from mobile, sorry for the typos > On 2 okt. 2014, at 09:41, "Gunter Van de Velde (gvandeve)" <gvandeve(a)cisco.com> wrote: > > 9 November 2014 is a Sunday? > > Something went wrong in agenda browsing I guess…. J > > G/ > > From: ipv6-wg-bounces(a)ripe.net [mailto:ipv6-wg-bounces@ripe.net] On Behalf Of MarcoH > Sent: 02 October 2014 09:07 > To: ipv6-wg(a)ripe.net IPv6 > Subject: [ipv6-wg] RIPE69 draft agenda > > Hello, > > Our initial draft agenda for the London meeting is online. > > Our session will be on Thursday 09 November, 11:00. We hope to see you all there and as usual remote participation will be available for those who can't make it to London. > > We welcome suggestions for any additional topics or talks. > Thursday, 9 November 09:00 – 10:30 > A. Welcome and Administrativa > > B. IPv6 Extension Headers > Jen Linkova, Google > > C. Nathalie Trenaman, RIPE NCC IPv6 Program Manager > > D. Transfer of IPv6 Chair Duties > > E. Establishing a Procedure to Elect Chairs > > X. Closing > > See you in London, > > MarcoH > -- > Sent from mobile, sorry for the typos

1 0

Replacing the IPv6 Working Group chairs
by Marco Hogewoning 01 Oct '14

01 Oct '14

Dear Colleagues, As announced during the meeting in Warsaw, after David’s decision to step down, Shane and I decided to also make place for some fresh new people. Over the past months we have been working with the candidates, who volunteered during the session and on this mailing list, on how to exactly make this change happen. And how to do that in as light weight a way as possible, while still have it based on the principles of transparency and rough consensus. As you may already have seen on other lists, there is an open action point to all working group chairs to, together with the working group, document the procedure by which chairs are selected, replaced and on a regular basis re-affirmed by the working group. As we already decided to step down, Shane and I feel slightly uncomfortable in our final act being to document how to replace ourselves. We would rather have the newly selected group of volunteers to take the lead in this process. Discussing this with Hans Petter, the RIPE Chair, he agreed to this approach. Talks and email exchanges amongst those people who nominated themselves or who’s name was brought forward has left three remaining candidates for the open positions: - Jen Linkova - Benedikt Stokebrand - Dave Wilson We, as acting working group chairs, would suggest the following: - The IPv6 Working Group, via this mailing list, to affirm the appointment of Jen, Dave and Benedikt as the new chairs of the IPv6 Working Group - Have the new chairs, together with the working group, draft the selection process with the aim of reaching consensus and publishing this document prior to RIPE 70 which will be in Amsterdam in May 2015. - Take the 70th RIPE meeting as an opportunity to execute the new process for the first time and have the working group re-affirm the new chairs under the new procedure. Shane and I, together with the new people, will continue to work on creating an inspiring agenda for the upcoming meeting in London and to prepare the new chairs for the upcoming change and of course, after the hand over, will be available for advice and assistance to ensure continuity of this working group in the transitioning phase. We would like to invite you all to provide us with your feedback on this proposed plan and to reach consensus on this matter, Regards, Marco Hogewoning Shane Kerr co-chairs of the RIPE IPv6 Working Group

27 27

Replacing the IPv6 Working Group chairs
by Timothy Roy 24 Sep '14

24 Sep '14

I am in support of these decisions as well. It is good to have new perspectives and some fresh blood now and then. Cheers Tim -----Original Message----- From: ipv6-wg-bounces(a)ripe.net [mailto:ipv6-wg-bounces@ripe.net] On Behalf Of ipv6-wg-request(a)ripe.net Sent: 24 September 2014 00:52 To: ipv6-wg(a)ripe.net Subject: ipv6-wg Digest, Vol 36, Issue 4 Send ipv6-wg mailing list submissions to ipv6-wg(a)ripe.net To subscribe or unsubscribe via the World Wide Web, visit https://www.ripe.net/mailman/listinfo/ipv6-wg or, via email, send a message with subject or body 'help' to ipv6-wg-request(a)ripe.net You can reach the person managing the list at ipv6-wg-owner(a)ripe.net When replying, please edit your Subject line so it is more specific than "Re: Contents of ipv6-wg digest..." Today's Topics: 1. Re: Replacing the IPv6 Working Group chairs (Daniel Baeza (Red y Sistemas TVT)) 2. Re: Replacing the IPv6 Working Group chairs (Roger J?rgensen) 3. Re: Replacing the IPv6 Working Group chairs (Elvis Velea) 4. Re: Replacing the IPv6 Working Group chairs (Andrew ? Yourtchenko) 5. Re: Replacing the IPv6 Working Group chairs (Tim Kleefass) 6. Re: Replacing the IPv6 Working Group chairs (George Giannousopoulos) 7. Re: Replacing the IPv6 Working Group chairs (Olivier MJ Crepin-Leblond) ---------------------------------------------------------------------- Message: 1 Date: Tue, 23 Sep 2014 17:10:51 +0200 From: "Daniel Baeza (Red y Sistemas TVT)" <d.baeza(a)tvt-datos.es> Subject: Re: [ipv6-wg] Replacing the IPv6 Working Group chairs To: ipv6-wg(a)ripe.net Message-ID: <54218D7B.20702(a)tvt-datos.es> Content-Type: text/plain; charset=windows-1252; format=flowed > - The IPv6 Working Group, via this mailing list, to affirm the > appointment of Jen, Dave and Benedikt as the new chairs of the IPv6 > Working Group I support this. -- Daniel Baeza Centro de Observaci?n de Red Dpto. Red y Sistemas Television Costa Blanca S.L. Telf. 966.190.847 | Fax. 965.074.390 http://www.tvt.es | http://www.tvt-datos.es Correo: d.baeza(a)tvt-datos.es -- [Atenci?n] La informaci?n contenida en este e-mail es confidencial, privilegiada y est? dirigida exclusivamente a su destinatario. Cualquier revisi?n, difusi?n, distribuci?n o copiado de este mensaje sin autorizaci?n del propietario est? prohibido. Si ha recibido este e-mail por error por favor b?rrelo y env?e un mensaje al remitente. [Disclaimer] The information contained in this e-mail is privileged and confidential and is intended only for its addressee. Any review, dissemination, distribution or copying of this e-mail is prohibited. If you have received it in error please delete the original message and e-mail us. (!) El medio ambiente es responsabilidad de todos. Imprime este mail si es absolutamente necesario. ------------------------------ Message: 2 Date: Tue, 23 Sep 2014 17:16:31 +0200 From: Roger J?rgensen <rogerj(a)gmail.com> Subject: Re: [ipv6-wg] Replacing the IPv6 Working Group chairs To: "ipv6-wg(a)ripe.net IPv6" <ipv6-wg(a)ripe.net> Message-ID: <CAKFn1SF1mq3ktYnwjYg1C3V67PUfxQjt=Ws_9aa9yp6H33NB8A(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 On Tue, Sep 23, 2014 at 1:40 PM, Marco Hogewoning <marcoh(a)marcoh.net> wrote: > Dear Colleagues, <snip> > Talks and email exchanges amongst those people who nominated themselves or who?s name was brought forward has left three remaining candidates for the open positions: > > - Jen Linkova > - Benedikt Stokebrand > - Dave Wilson supported -- Roger Jorgensen | ROJO9-RIPE rogerj(a)gmail.com | - IPv6 is The Key! http://www.jorgensen.no | roger(a)jorgensen.no ------------------------------ Message: 3 Date: Tue, 23 Sep 2014 17:25:45 +0200 From: Elvis Velea <elvis(a)velea.eu> Subject: Re: [ipv6-wg] Replacing the IPv6 Working Group chairs To: ipv6-wg(a)ripe.net Message-ID: <542190F9.6060408(a)velea.eu> Content-Type: text/plain; charset=UTF-8; format=flowed On 23/09/14 17:16, Roger J?rgensen wrote: > On Tue, Sep 23, 2014 at 1:40 PM, Marco Hogewoning <marcoh(a)marcoh.net> wrote: >> Dear Colleagues, > <snip> >> Talks and email exchanges amongst those people who nominated themselves or who?s name was brought forward has left three remaining candidates for the open positions: >> >> - Jen Linkova >> - Benedikt Stokebrand >> - Dave Wilson > supported > +1 cheers, elvis ------------------------------ Message: 4 Date: Tue, 23 Sep 2014 17:32:33 +0200 From: Andrew ? Yourtchenko <ayourtch(a)gmail.com> Subject: Re: [ipv6-wg] Replacing the IPv6 Working Group chairs To: "ipv6-wg(a)ripe.net IPv6" <ipv6-wg(a)ripe.net> Message-ID: <CAPi140NVynqgwG-Z7u6FGJ-d0VCXLQaywWhx_F2jsvmpFPVZdg(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Marco, Shane, On 9/23/14, Marco Hogewoning <marcoh(a)marcoh.net> wrote: > - The IPv6 Working Group, via this mailing list, to affirm the > appointment of Jen, Dave and Benedikt as the new chairs of the IPv6 > Working Group support! --a ------------------------------ Message: 5 Date: Tue, 23 Sep 2014 19:28:12 +0200 From: Tim Kleefass <tim(a)haitabu.net> Subject: Re: [ipv6-wg] Replacing the IPv6 Working Group chairs To: ipv6-wg(a)ripe.net Message-ID: <5421ADAC.4010904(a)haitabu.net> Content-Type: text/plain; charset=windows-1252 On 23.09.2014 1:40 PM, Marco Hogewoning wrote: > We, as acting working group chairs, would suggest the following: > > - The IPv6 Working Group, via this mailing list, to affirm the > appointment of Jen, Dave and Benedikt as the new chairs of the IPv6 > Working Group Support! -Tim ------------------------------ Message: 6 Date: Tue, 23 Sep 2014 20:37:40 +0300 From: George Giannousopoulos <ggiannou(a)gmail.com> Subject: Re: [ipv6-wg] Replacing the IPv6 Working Group chairs To: Marco Hogewoning <marcoh(a)marcoh.net> Cc: "ipv6-wg(a)ripe.net IPv6" <ipv6-wg(a)ripe.net> Message-ID: <CAFotJgvfhmisz7rO5-g6cv5puyWskLeyowpnaDW8S7vOS1Yt4w(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi, > Talks and email exchanges amongst those people who nominated > themselves or who?s name was brought forward has left three remaining > candidates for the open positions: > - Jen Linkova > - Benedikt Stokebrand > - Dave Wilson > We, as acting working group chairs, would suggest the following: > - The IPv6 Working Group, via this mailing list, to affirm the > appointment of Jen, Dave and Benedikt as the new chairs of the IPv6 > Working Group > - Have the new chairs, together with the working group, draft the > selection process with the aim of reaching consensus and publishing > this document prior to RIPE 70 which will be in Amsterdam in May 2015. > - Take the 70th RIPE meeting as an opportunity to execute the new > process for the first time and have the working group re-affirm the > new chairs under the new procedure. I support too. George On Tue, Sep 23, 2014 at 2:40 PM, Marco Hogewoning <marcoh(a)marcoh.net> wrote: > Dear Colleagues, > > As announced during the meeting in Warsaw, after David?s decision to > step down, Shane and I decided to also make place for some fresh new people. > Over the past months we have been working with the candidates, who > volunteered during the session and on this mailing list, on how to > exactly make this change happen. And how to do that in as light weight > a way as possible, while still have it based on the principles of > transparency and rough consensus. > > As you may already have seen on other lists, there is an open action > point to all working group chairs to, together with the working group, > document the procedure by which chairs are selected, replaced and on a > regular basis re-affirmed by the working group. > > As we already decided to step down, Shane and I feel slightly > uncomfortable in our final act being to document how to replace ourselves. > We would rather have the newly selected group of volunteers to take > the lead in this process. Discussing this with Hans Petter, the RIPE > Chair, he agreed to this approach. > > Talks and email exchanges amongst those people who nominated > themselves or who?s name was brought forward has left three remaining > candidates for the open positions: > > - Jen Linkova > - Benedikt Stokebrand > - Dave Wilson > > We, as acting working group chairs, would suggest the following: > > - The IPv6 Working Group, via this mailing list, to affirm the > appointment of Jen, Dave and Benedikt as the new chairs of the IPv6 > Working Group > - Have the new chairs, together with the working group, draft the > selection process with the aim of reaching consensus and publishing > this document prior to RIPE 70 which will be in Amsterdam in May 2015. > - Take the 70th RIPE meeting as an opportunity to execute the new > process for the first time and have the working group re-affirm the > new chairs under the new procedure. > > Shane and I, together with the new people, will continue to work on > creating an inspiring agenda for the upcoming meeting in London and to > prepare the new chairs for the upcoming change and of course, after > the hand over, will be available for advice and assistance to ensure > continuity of this working group in the transitioning phase. > > We would like to invite you all to provide us with your feedback on > this proposed plan and to reach consensus on this matter, > > Regards, > > Marco Hogewoning > Shane Kerr > > co-chairs of the RIPE IPv6 Working Group > >

1 0

[training] RIPE NCC Webinars - new dates
by Training Services 11 Sep '14

11 Sep '14

Dear colleagues, We are pleased to announce the launch of new dates for our Webinars. The RIPE NCC Webinars are live and take only one hour. You can interact with our trainers without leaving your desk. We focus on the topics and issues most important for LIRs. Register now at https://www.ripe.net/lir-services/training/e-learning/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have questions, please email <training(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Services

1 0

IPv6 troubleshooting for helpdesks - draft v.01
by Jan Zorz ＠ go6.si 09 Sep '14

09 Sep '14

Dear IPv6 WG, Just to let you know, the co-authors of "IPv6 troubleshooting for helpdesks" document published the next version of the document with some new and also a bit more fine tuned old content and revised structure. Please find the latest version in attach and also at following URLs: http://go6.si/ipv6-troubleshooting-for-helpdesks/ http://go6.si/docs/IPv6-troubleshooting-for-helpdesks-v01.pdf (direct download) I would like to ask IPv6 WG community to read the document and check the technical and procedural validity of the content. All ideas, comments and suggestions also welcome on this list. This document is now in the works for quite long time, so I hope that we might be approaching the final version soon ;) Cheers and thnx, Jan Zorz

1 0

IP Address Space Course this November in London
by Training Services 26 Aug '14

26 Aug '14

Dear Colleagues, We are happy to announce a new RIPE NCC training course that will take place on the Sunday before the RIPE 69 Meeting in London this November. This new course will focus on how to obtain, transfer, manage and protect your IP address space. The course is free of charge and is open to anyone interested. The course will cover the most frequently asked questions the RIPE NCC receives about IP address space. Course title: RIPE NCC Presents: IP Address Space Basics How to obtain, transfer, manage and protect your IP addresses Goals: By the end of this course, you will be able to: - Manage your IPv4 and IPv6 addresses according to current RIPE Policies - Understand how to obtain IPv4 addresses through transfers - Protect your address space from hijacking Target audience: Anyone interested in the policies and procedures around address space in the RIPE NCC service region, and companies looking at address space transfers, mergers and acquisitions. No prior knowledge of the topic is necessary. Time: Sunday, 2 November, 10:00–16:00 Outline: - Becoming a RIPE NCC member (why and how) - Obtaining IP addresses (IPv4 and IPv6) - IP address space transfers, mergers and acquisitions - IPv6 basics - Address space hijacking - Resource Certification (RPKI) Cost: Free of charge. Coffee and lunch will be provided. The course will be delivered by representatives from the RIPE NCC’s Training Services and Registration Services departments. If you are interested in attending this course, please let us know asap by sending an email to training(a)ripe.net. Be quick - we only have 40 seats available on a first come, first served basis! If there is enough interest, we will continue to offer courses on different topics of interest alongside future RIPE Meetings. Kind regards, Training Services

1 0

RIPE 69 Agenda items?
by Marco Hogewoning 20 Aug '14

20 Aug '14

Dear Colleagues, The next RIPE Meeting will be held in London from 3-7 November. As always this working group has been given a slot to meet, which is on Thursday the 6th of November at 09:00 local time. For now we only have 90 minutes, but if we have enough content that we feel is worth discussing, we can put in a request for additional time. We expect some of the time to be taken by a discussion on replacing Shane and me as chairs of this working group, but there should be more than enough left to focus on the tasks at hand. If you have a topic that is related to the deployment of IPv6, that you think is worth showing, discussing by this working group or you have any proposal for specific work items for this group, please make yourself known either via this list or an email to ipv6-wg-chairs at ripe dot net. And keep in mind our charter is not limited to IPv6 address management, we equally welcome any other topics that relate to the adoption and implementation of IPv6 that would be of benefit to the RIPE community or the global Internet community. More information about RIPE 69 and registration is available via http://ripe69.ripe.net Cheers and see you in London, Marco and Shane IPv6 WG chairs

1 0

Re: [ipv6-wg] IPv6 Addressing Plan (Daniel Baeza (Red y Sistemas TVT))
by Sonderegger Olaf ABRAXAS INFORMATIK AG 20 Aug '14

20 Aug '14

Hi Daniel >From my point of view, an IP Addressing Plan has to be done by its user. It doesn't exist an one-fits-all solution, there will be always something which is unique within your environment/your country/your service. I think, a good starting point is following SURFnet paper about "Preparing an IPv6 Adressing Plan": https://labs.ripe.net/Members/steffann/preparing-an-ipv6-addressing-plan Best regards, Olaf

3 2

[training] RIPE NCC Training Courses October-December 2014
by Training Services 19 Aug '14

19 Aug '14

Dear Colleagues, Our training team travels the RIPE NCC service region to deliver training courses to our members without any additional cost. Over the next few months, we'll be in Ljubljana, Norway, Tbilisi, Berlin, Bratislava, Amman, Lyon, Athens, London, Amsterdam. Visit the following page to register and to check which training courses we are giving in your area: https://lirportal.ripe.net/training/courses The RIPE NCC delivers the following training courses: - LIR Training Course - RIPE Database Training Course - Basic IPv6 Training Course - Advanced IPv6 Training Course - Routing Security Training Course - DNSSEC Training Course For more information visit: http://www.ripe.net/lir-services/training/courses With kind regards, Rumy Spratley-Kanis Training Services Manager

1 0

IPv6 Addressing Plan
by Daniel Baeza (Red y Sistemas TVT) 29 Jul '14

29 Jul '14

Hi all, Im new to this list and dont know if im doing right asking that here but, Can anyone help us a little bit on making an addressing plan? We are a Local ISP provider and we work with Coaxial(HFC), FTTH and WiFi. We have allocated a /29 but It have been split into 8 /32. We are planning to use 1 /32 for our own infraestructure and for client lease (dhcpv6) in both ways, Direct Access and PD. Thanks in advance! Best Regards, -- Daniel Baeza Centro de Observación de Red Dpto. Red y Sistemas Television Costa Blanca S.L. Telf. 966.190.847 | Fax. 965.074.390 http://www.tvt.es | http://www.tvt-datos.es Correo: d.baeza(a)tvt-datos.es -- [Atención] La información contenida en este e-mail es confidencial, privilegiada y está dirigida exclusivamente a su destinatario. Cualquier revisión, difusión, distribución o copiado de este mensaje sin autorización del propietario está prohibido. Si ha recibido este e-mail por error por favor bórrelo y envíe un mensaje al remitente. [Disclaimer] The information contained in this e-mail is privileged and confidential and is intended only for its addressee. Any review, dissemination, distribution or copying of this e-mail is prohibited. If you have received it in error please delete the original message and e-mail us. (!) El medio ambiente es responsabilidad de todos. Imprime este mail si es absolutamente necesario.

2 2

RIPE 68 Minutes
by Marco Hogewoning 14 Jul '14

14 Jul '14

Dear colleagues, Please find attached a copy of the minutes of our last meeting. Once again we like to thank the RIPE NCC for providing these and invite the community to review and report back any errors or omissions. Please send any feedback before September 1st, 2014 (allowing for holidays) after which we will publish the final version. Cheers, Marco RIPE 68 WG Chairs: Shane Kerr, Marco Hogewoning Session I: 15 May 2014, 9:00- 10:30 Scribe: Mirjam Kuehne A. Welcome and Housekeeping Shane Kerr, IPv6 Working Group Chair, opened the first session. He briefly described the IPv6-only wireless network and encouraged everyone to use it. B. IPv6 Campus Deployment Experience - Niall O’Reilly[FM1] , University College Dublin The presentation is available at: https://ripe68.ripe.net/presentations/261-RIPE68_Deploying_IPv6.pdf Jen Linkova, Google, asked how many users or devices Niall expects for the wireless network. Niall said that he expects a couple of tens of thousands. Jen added that this large number of devices on the network may have an effect on the battery life of the devices. Niall thanked Jen for the warning and said that this would be an interesting user experiment. However, he agreed that, when adding a large number of customers, the noise level on the network goes up, which may be mitigated by the access control they're using. Wilfried Wöber, Univie/ACOnet/VIX, said that they had been “playing with” IPv6 for a while at the NREN in Austria and that he was surprised to see in the most recent Akamai report that 43% of traffic with Akamai from Vienna University was IPv6 traffic, much higher than he had expected. Niall responded that this very much depends on the applications used. Benedikt Stockebrandt, Stepladder IT, referred to a document from a university in South Africa. They turned on IPv6 on the campus and observed that 56% of the traffic was IPv6 and most of it was YouTube traffic. He expected that something like this will also happen at the Dublin campus and wondered what the traceability requirements are. Niall answered that part of the agreement with Eduroam requires keeping radius and DHCP logs for six months. Jen Linkova said that, before using tools to conform that a user is using a certain IP address which was assigned by DHCP (and not statically configured), one needs to consider that DHCP doesn't necessarily give you the malicious user that was using that address. Niall responded that he is sure that they don't have complete proof against malicious attacks but that the majority of users want to use the network and the set-up, and the existing tools seem to be adequate for this purpose (logs from wireless controllers and access lists). C. IPv6 Penetration in Hungary - Janos Zsako The presentation is available at: https://ripe68.ripe.net/presentations/330-IPv6_measurements_in_Hungary.pdf Shane Kerr, Dyn, said that he was surprised to see that mail has such low penetration because it seems an easy thing to turn on. He asked Janos if he had any ideas why this is the case. Janos responded that he doesn't know and that he didn't have the opportunity to talk to the providers to find out why this is the case. He added that it might be caused by the fact that it is not yet widely spread so the servers in the backbone or in the core could have IPv6 but that it doesn't help much yet. Ondrej Calatka, CESNET, reported that he is operating automated responder tests, where you can send mail and take a reply over IPv6 and see if you are able to send to, and receive from, an IPv6-only mail server. He said that he observed some interesting things: 30% of MX records with IPv6 address don’t respond to SMTP to connect to the port. Furthermore, when you are lucky enough to connect to the SMTP service, some IPv6-only host names respond with an invalid host name. There is also other anti-spam, anti-malware and other measures that are IPv4 only. So, even if you are communicating over IPv6 with the SMTP server, it means that you can only deliver mail with IPv6, therefore it's somewhat “horrible”. Janos agreed and said that he also looked at common errors in MX records. Often, he saw local hosts or there are IP addresses inside or many other bugs. Alex, participating via chat, asked whether the percentages shown are of MX, NS, WEB servers, or percentages of .hu domains with working service. Alex also asked, “Who are the champions of turning IPv6 on in .hu?” Janos clarified that the percentage of servers that we see is much lower than the percentage of domains serving those servers. In response to Alex’s second question, he stated that the academic network was one of the pioneers many years ago but he wanted to concentrate on the current situation. Sebastian Castro, .nz Registry Services, reported that he sees similar numbers: higher level of adoption on name servers compared to adoption on mail and web servers. He added that they are scanning all domain names for A and AAAA records, that they are happy to share the data and that the IPv6 task force in New Zealand also has interesting numbers. Jan Zorz said that he also sees the same issues with mail servers and suggested that people use protocols that work over IPv6 (such as DKIM). He referred to a recent article published by Frank Martin on RIPE Labs: https://labs.ripe.net/Members/mirjam/sending-and-receiving-emails-over-ipv6 George Michaelson, APNIC, said that the different numbers Janos presented are because different people are measuring different things (mostly quantitative measurements). George commented that Janos is performing more qualitative measurements to assess capacity and capability, and it is common knowledge that that the centre is better than the edge. Therefore, it may not be surprising to see that the edge measurements Janos is performing are lower. Finally, he added that he was struggling to send traceroutes into IPv6 space in Hungary- the richness of the peering narrows pretty quickly. Andrea Cima, RIPE NCC, referred to the quality of registration data in IPv6 as opposed to IPv4 data, as Janos mentioned in his presentation. The RIPE NCC has also been thinking about this: for IPv4 there was a much closer feedback loop between the RIPE NCC and the LIRs, especially when LIRs come back for more resources. For IPv6, that is not the case. Most LIRs will never come back for an additional allocation. Also, before 2011, LIRs were not required to register End User assignments in the RIPE Database. Recently, it was decided to create a new auditing process that is much more lightweight and focused on advice and support (the Assisted Registry Check, which has been very successful so far). The plan is to contact 3,000 LIRs every year and the RIPE NCC wants to make it easy for LIRs to maintain their resources. An unnamed speaker from Romania said that they are running the biggest IPv6 network in the country. However, he added that they could not expand into Hungary, because the Hungarian regulator did not authorise lawful interception. D. Painting by Numbers (Visualisation of Structured IPv6-Addressing) - Helge Holz, Dataport The presentation is available at: https://ripe68.ripe.net/presentations/344-Painting_by_Numbers.pdf Jen Linkova congratulated Helge on this work and asked if it can also be used for other environments. She suggested making it public so that others can also use it. Helge said that, currently, it is not very stable but added that he certainly wants to make it public, which why he is presenting it at the RIPE Meeting. Geoff Huston, APNIC, asked what would happen if the libraries would want to connect separately from all the schools. Helge clarified that In Germany that won't be the case. Niall stated that this algorithm has properties that he needs for his operations and that he couldn't work it out by himself. Therefore, he is very happy about Helge's algorithm and thanked him for it. E. What the Future Holds Ondrej Sury, CZ.NIC Ondrej showed some slides from his presentation that was presented in full at the Open Source Working Group about Knot DNS. The full presentation is available at: https://ripe68.ripe.net/presentations/262-KNOT-20140514-RIPE68.pdf Wilfried Woeber asked for confirmation: if one has a particular entry for the 4-bit zone, you cannot automatically give the answer if queried for the reverse. Ondrej answered that it is the case and that it doesn't match the zones together. It just creates a pattern that will generate “on the fly” if somebody asks for the name. Session II: 15 May 2014, 11:00- 12:30 Scribe: Emile Aben At the beginning of the session, Working Group Chair Marco Hogewoning mentioned the availability of an IPv6-only WiFi network. F. RIPE IPv6 Analyser Alex Band, RIPE NCC The presentation is available at https://ripe68.ripe.net/presentations/338-IPv6_Analyser.pdf There were no questions for this presentation. G. BCOP Document: “IPv6 troubleshooting procedures for helpdesks” - Jan Zorz, ISOC The presentation is available online: https://ripe68.ripe.net/presentations/343-Jan_Zorz_IPv6_helpdesk.pdf Ragnar Anfinsen, Altibox, said that he had received positive feedback on this from his helpdesk. He asked for additional text for expert users on the website, so that they can fix problems themselves. Jan clarified that this is the plan. Jen Linkova said that it's a great idea, and added that she had already given detailed comments by email. She wondered about the procedure and indicated that there are too many places to track and comment on this work and that it needs one place where discussion can take place. After a discussion, it was agreed that technical comments should go to the IPv6 Working Group mailing list. H. IETF document: “Balanced Security for IPv6 Residential CPE” - Ragnar Anfinsen, Altibox The presentation is available online at: https://ripe68.ripe.net/presentations/358-Balanced_Security_-_IPv6_Security… Sander Steffann, SJM Steffann, said that this effort is heading in the right direction that it's very important to both show advice and experiences from people who have already done this. Jan Zorz said that his suggestion at the IETF was to verify the document with the operational community, and mentioned BCOP as a means to do this. Jan asked if the CPE (Customer Premises Equipment) vendors showed interest in this. Ragnar said that they didn't show interest. This is mainly for service providers that manage the CPE and it is quite complex for retail CPE. Jan suggested taking this to the openCPE project, or to Terrastream's version of that. Benedikt Stockebrandt indicated that there are cultural differences on what approaches to adopt and it would be good to account for these. Mathew Moyle-Croft, Amazon, suggested offering customers the ability to do upstream filtering, as an alternative to filtering on the CPE, as it's easier to manage and reduces traffic. Ragnar said that the draft is about filtering as a service, and is therefore not necessarily specific to CPE. I. RIPE_554bis - Sander Steffann, RIPE NCC The presentation is available at: https://ripe68.ripe.net/presentations/340-RIPE-554bis.pdf Shane Kerr stated that this document is one of the success stories of this working group, but things need to be updated continuously. Benedikt Stockebrandt said that the size of the document scares people off. He suggested to split it up in different documents addressing different areas, and indicated choosing connectivity as one of these. Wilhelm Boeddinghaus, BCIX/Iubari, warned against setting the scope too wide and suggested keeping the focus with hardware, and not to engage in cloud or software-defined networking (SDN) because this will result in discussions. These, and connectivity need new documents. Marco Hogewoning agreed with previous comments, and indicated that the document is widely used. He suggested adding text to the document on how updates to the document are handled. He argued to not obsolete ripe-554, “Requirements for IPv6 in ICT Equipment”, but make a new document that is referenced everywhere, to help people who are not familiar with the processes. He proposed keeping both ripe-554 and the new document alive. Sander agreed, and considered different wording might help, and to not call it obsoleted. Shane said that it wasn't clear to him how that would work. Sander pointed out that ripe-501, “Requirements for IPv6 in ICT Equipment”, is called obsoleted and much downloaded, and called for careful communication regarding this. Jan Zorz called for language polishing by native speakers. He added that, for the connectivity part, he is maintaining that list, and, due to an error, it wasn't in ripe-554. He volunteered to work on the connectivity part. Sander said that he wants to do ripe-554 first, and later take the extra parts to the mailing list. Mirjam Kuehne, RIPE NCC, indicated that the RIPE NCC is always happy to do language review of these documents. J. IPv6 deployment at CERN - Edoardo Martelli, CERN The presentation is available at: https://ripe68.ripe.net/presentations/294-cern-ipv6-deployment.pdf Jen Linkova asked about the plans for IPv6 on external services, because they are not dual-stacked. Edoardo said that, internally, services are IPv6-ready, but are not externally ready for various reasons- for mail, due to lack of IPv6 support in their anti-spam software and for web server because they didn't dare to. Shane Kerr wondered if they saw more questions coming into their customer support, because that was a concern for IPv6 World Day. Edoardo said that most questions were about how to use it, not about problems. Shane mentioned that there are people working to eliminate the need for Router Advertisement (RA), so to be able to use only DHCPv6. Lionel Hoffmann, Bouygues Telecom, asked if the tools mentioned in the presentation were all homemade. Eduardo confirmed that most of it is homemade. Lionel also asked about experiences with specific applications having problems with IPv6, and CERN's plans for applications that only support IPv4. Eduardo explained that they test whether applications keep working on dual-stacked machines, even if the application doesn't use IPv6. For some legacy applications, like AFS, he expected never to get IPv6 support, so they cannot phase out IPv4 at the moment. Lionel asked if dual-stack is a step towards IPv6-only. Eduardo answered that, currently, they expect to be dual-stacked forever. K. Selection of a New Working Group Chair Marco and Shane discussed David Kessens stepping down as one of the chairs of the IPv6 Working Group and how to fill the vacancy. Marco and Shane also intend to be gradually replaced. Working group chairs are replaced by consensus of the working group. They said that they would take the process to the mailing list. They then invited people to comment on this and to step forward as potential IPv6 Working Group Chairs. Jan Zorz thanked David Kessens for his service and was willing to step forward as a candidate, but would need to work out how to combine that with chairing the BCOP Task Force. Jen, Dave Wilson, HEAnet, and Dmitry Kohmanyuk, Hostmaster, also stepped forward as candidates. Rob Evans, JANET, indicated that this is really good in the light of periodic reaffirmation of working group chairs. He was disappointed that Marco and Shane won't stand again. The IPv6 Working Group chairs thanked participants for attending and stated that they hope that they would see the participants in London at the next RIPE Meeting. Marco Hogewoning urged participants to try the IPv6-only network and closed the session. [FM1]Org?

1 0

IPv6 only network at RIPE 68
by MarcoH 12 Jul '14

12 Jul '14

Hello, First of all let me use this opportunity to say thank you to Andrew Yourtchenko and the RIPE NCC staff for all their support and work in making this available. Statistics show that again quite a lot of people have used or at least tried this network. A few issues bubbled up, but they were all related to issues with 3rd party software and one minor incident with the layer 2 infrastructure that was not related to our specific setup. Please feel free to give feedback about this experiment on this list. But also please consider relaying it back to the developers or companies and compliment with a nice job done or ask them to fix any bugs you may have encountered. Thanks, MarcoH -- Sent from mobile, sorry for the typos

23 65

is use of IF-ID 0 "clean"
by Wilfried Woeber 27 Jun '14

27 Jun '14

Dear WG-folks, out of curiosity and because I got asked this question, here we go: Is the use of "0" as the interface ID in an IPv6 network "clean"? I haven't found any indication that "0" is reserved (as in IPv4), or should not be used, but there's a lingering feeling that it may cause trouble, somewhere, somehow. Any input appreciated, tia, Wilfried.

5 5

[training] RIPE NCC Webinars - new dates
by Training Services 24 Jun '14

24 Jun '14

Dear colleagues, We are pleased to announce the launch of new dates for our Webinars. The RIPE NCC Webinars are live and take only one hour. You can interact with our trainers without leaving your desk. We focus on the topics and issues most important for LIRs. Register now at https://www.ripe.net/lir-services/training/e-learning/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have questions, please email <training(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Services

1 0