- ipv6-wg - mailman.ripe.net

Re: [ipv6-wg] IPv6 WG co-chair selection
by Kennedy, James 02 Oct '19

02 Oct '19

+1 support for Ray Regards, James From: ipv6-wg [mailto:ipv6-wg-bounces@ripe.net] On Behalf Of Jetten Raymond Sent: 13 September 2019 12:04 To: RIPE IPv6 WG <ipv6-wg(a)ripe.net> Cc: ipv6-wg-chairs(a)ripe.net Subject: [ipv6-wg] IPv6 WG co-chair selection Hello again, Apologies for the previously incomplete and spelling mistakes email. I hope below is a better version : -- Hello All, Its almost 3 years ago that I started as a IPv6-WG co-chair, so as per our current policy it's time to step down. However, I'm very willing to stand for re-selection, and serve another term as IPv6 WG co-chair, which I hope you all find a good idea. The full process is described here: https://www.ripe.net/participate/ripe/wg/ipv6/ipv6-wg-chair-selection-proce… See you all in Rotterdam! Rgds, Ray

1 0

IPv6 WG co-chair selection
by Jetten Raymond 01 Oct '19

01 Oct '19

Hello again, Apologies for the previously incomplete and spelling mistakes email. I hope below is a better version : -- Hello All, Its almost 3 years ago that I started as a IPv6-WG co-chair, so as per our current policy it's time to step down. However, I'm very willing to stand for re-selection, and serve another term as IPv6 WG co-chair, which I hope you all find a good idea. The full process is described here: https://www.ripe.net/participate/ripe/wg/ipv6/ipv6-wg-chair-selection-proce… See you all in Rotterdam! Rgds, Ray

6 5

IPv6 WG agenda
by Jen Linkova 30 Sep '19

30 Sep '19

Hello, The agenda for IPv6 WG session at RIPE79 has been published: https://ripe79.ripe.net/programme/meeting-plan/ipv6-wg/ See you all in Rotterdam! -- SY, Jen Linkova aka Furry on behalf of IPv6 WG chairs.

1 0

IPv6 WG chair election
by Jetten Raymond 19 Sep '19

19 Sep '19

Hello All, Its almost 3 years ago that I started as a IPv6-WG co-chair, so as per our current policy it's time to step down. However, I'm very willing to stand for re-election, and serve another term as IPv6 WG co-chair, which I hope you all find a good idea. See you all in Rotterdam! Rgds, Ray

14 13

Re: [ipv6-wg] IPv6 WG co-chair selection
by Janos Zsako 18 Sep '19

18 Sep '19

Dear Ray, > Its almost 3 years ago that I started as a IPv6-WG co-chair, I think you did a very good job, thank you. > so as per our current policy it's time to step down. > > However, I'm very willing to stand for re-selection, and serve another term as IPv6 WG co-chair, which I hope you all find a good idea. I am glad to hear this. I strongly support your re-election. Best regards, Janos > Rgds, > Ray

1 0

RIPE 78 Minutes
by Jetten Raymond 14 Sep '19

14 Sep '19

Hello all, The minutes from RIPE 78 are now available: https://www.ripe.net/participate/ripe/wg/ipv6/minutes/ipv6-working-group-mi… Please let us know if you have any comments. Cheers, Jen, Benedikt and Ray

1 0

RIPE 79 IPv6 Working group
by Jetten Raymond 30 Jul '19

30 Jul '19

Hello All, The RIPE 79 meeting will take place will take place in Rotterdam Netherlands from 14-18 October 2019. https://ripe79.ripe.net/ The IPv6 WG session will most likely be on Thursday Morning. (still subject to change). Would you like to present at our WG session, and have a subject that would be of interest on IPv6, or develop IPv6 related RIPE policies, have useful recommendations, or plan other documents that will help the deployment of IPv6 ? We, the IPv6 WG co-chairs, would like to invite you to submit your presentation proposals, including a brief description of the content and the time you would need. Please send them directly to us: ipv6-wg-chairs at ripe.net<https://lists.ripe.net/mailman/listinfo/ipv6-wg> . Once we start to make the final agenda, we will let you know if you are selected or not. Please be aware of the following: Due to potential technical issues, presenters/panelists should be physically present at the RIPE Meeting. RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. All sessions will be recorded and broadcasted, and will be publicly available afterwards, so make sure you own the copyrights of all content. See you in Rotterdam, Jen, Benedikt, Ray

1 0

IPv6 SLAAC renum/problems IETF I-D (Fwd: New Version Notification for draft-gont-v6ops-slaac-renum-00.txt)
by Fernando Gont 07 Jul '19

07 Jul '19

Folks, To make the story short: Based on the recent discussion we had on our IETF I-D draft-gont-6man-slaac-renum, we have posted this new I-D which focuses on discussing the problem, and describing operational mitigations. The document is available at: https://www.ietf.org/internet-drafts/draft-gont-v6ops-slaac-renum-00.txt Comments are welcome. It is being discussed on the IETF v6ops wg mailing-list: https://mailarchive.ietf.org/arch/msg/v6ops/5D2hdpB6QHRm9u-MUj6erQaLZY0 If possible, post your comments on the v6ops wg list. But comments are welcome, whether there, here, or even unicast to us (co-authors) ;-) Thanks! Cheers, Fernando -------- Forwarded Message -------- Subject: New Version Notification for draft-gont-v6ops-slaac-renum-00.txt Date: Sat, 06 Jul 2019 08:59:12 -0700 From: internet-drafts(a)ietf.org To: Fernando Gont <fgont(a)si6networks.com>, Jan Zorz <jan(a)go6.si>, Richard Patterson <richard.patterson(a)sky.uk> A new version of I-D, draft-gont-v6ops-slaac-renum-00.txt has been successfully submitted by Fernando Gont and posted to the IETF repository. Name: draft-gont-v6ops-slaac-renum Revision: 00 Title: Reaction of Stateless Address Autoconfiguration (SLAAC) to Renumbering Events Document date: 2019-07-06 Group: Individual Submission Pages: 14 URL: https://www.ietf.org/internet-drafts/draft-gont-v6ops-slaac-renum-00.txt Status: https://datatracker.ietf.org/doc/draft-gont-v6ops-slaac-renum/ Htmlized: https://tools.ietf.org/html/draft-gont-v6ops-slaac-renum-00 Htmlized: https://datatracker.ietf.org/doc/html/draft-gont-v6ops-slaac-renum Abstract: In scenarios where network configuration information related to IPv6 prefixes becomes invalid without any explicit signaling of that condition (such as when a CPE crashes and reboots without knowledge of the previously-employed prefixes), nodes on the local network will continue using stale prefixes for an unacceptably long period of time, thus resulting in connectivity problems. This document analyzes these problem scenarios, and discusses operational workarounds to improve network robustness. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat

1 0

IPv6 faster than IPv4 (also with 464XLAT)
by JORDI PALET MARTINEZ 26 Jun '19

26 Jun '19

We already knew that from previous measurements, however the nice thing from this article is that it is analyzing many different providers worldwide: https://teamarin.net/2019/06/25/why-is-ipv6-faster/ Regards, Jordi @jordipalet ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

1 0

RIPE NCC Receives Additional /12 IPv6 Allocation from IANA
by Nikolas Pediaditis 07 Jun '19

07 Jun '19

Dear colleagues, On 5 June 2019, the RIPE NCC received the following IPv6 allocation from IANA: 2a10:0000::/12 All allocations of IPv6 unicast address space made by IANA to RIRs are listed here: https://www.iana.org/assignments/ipv6-unicast-address-assignments/ipv6-unic… We received our previous /12 allocation (2a00:0000::/12) on 3 October 2006. The conditions under which we qualified for an additional allocation are described in the IANA Policy For Allocation of IPv6 Blocks to RIRs: https://www.icann.org/resources/pages/allocation-ipv6-rirs-2012-02-25-en The RIPE NCC is the first RIR to receive an additional /12 IPv6 block. As today is also the seventh anniversary of World IPv6 Launch Day, we took the opportunity to look at some of the history of IPv6 and how it has been distributed in our service region: https://labs.ripe.net/Members/riccardo_stagni/we-re-running-out-of-ipv6 Kind regards, Nikolas Pediaditis Registration Services & Policy Development Assistant Manager RIPE NCC

6 6