October 2020 - ipv6-wg - mailman.ripe.net

Re: [ipv6-wg] RIPE554-bis
by Eric Vyncke (evyncke) 31 Oct '20

31 Oct '20

Trying to reply to all previous email messages in one email ;-) Look for EV> -éric-happy-to-see-this-initiative -----Original Message----- From: ipv6-wg <ipv6-wg-bounces(a)ripe.net> on behalf of Tim Chown via ipv6-wg <ipv6-wg(a)ripe.net> Reply-To: Tim Chown <Tim.Chown(a)jisc.ac.uk> Date: Wednesday, 28 October 2020 at 18:19 To: "ipv6-wg(a)ripe.net" <ipv6-wg(a)ripe.net> Subject: [ipv6-wg] RIPE554-bis Hi, I’m posting here as a heads-up that an effort has begun to revise RIPE-554, involving the original authors, myself and Tim Winters. We have a 5 min slot tomorrow in the 1pm CET IPv6 WG session to flag the work, to solicit input. The original publication was back in November 2010 with RIPE-501, which was updated in June 2012 with RIPE-554. There’s many references that have been obsoleted, and potentially much to add or remove. References to 2G cellular date the document. We’d like to begin by addressing the more strategic / structural questions. Such high level questions include: - Is there agreement to progress a –bis version now? Eight years have passed, people ask for guidance… EV> YES, please do ! knowing that RIPE554 was already a -bis, I would prefer a 501-ter though ;-) - Should we keep the scope to (largely) enterprise or expand it? If so, to what? EV> large/medium enterprise should indeed be the focus, consumer do not care and (wishful thinking ?) providers know better. Although, that I would love to see the IPv6 check-list for a smart TV ;-) - Is the linkage to the IPv6 Ready Logo programme still desired? EV> a couple of months ago, I check with several end-users and vendors, and, yes, it is still important (to be surprise to be honest, sorry Tim W) - Are there new classes of equipment to add, e.g. IoT/low power, WiFi controllers, …? EV> perhaps extend to applications? Cloud providers ? Perhaps remove consumer switch, load balancer, and network security ? - Are specific sections outdated, or are there significant new sections to add? EV> many "recents" RFC (including RFC 8200), focus on RA extensions - Should we add guidance on applying the content to different use cases? As separate docs? Appendices? We’ve currently working on the -bis as a Google doc, for which there’s a PDF of the current snapshot available from: https://go6.si/wp-content/uploads/2020/10/RIPE554-bis-v_01.pdf For now, please comment to the list, and maybe start a new thread for new topics. Tim

1 0

ip address pricing and protocol selection
by Wolfgang Zenker 30 Oct '20

30 Oct '20

Hello WG, I have a question for those of you that offer some kind of hosting. Do you charge your customers extra for IPv4 or IPv6 addresses? And if you have changed your policy on that recently, did that change your customers behaviour regarding their choice on ordering and publishing IPv4 / IPv6 addresses for the hosted services? Reason for asking: At our own hosting services we started out offering dual stack by default some 6 years ago, moved to ipv6-only by default about 2 years ago and since about one year we are charging extra for IPv4 addresses. This has led to a change in behaviour in our customer base, and I want to see if others are seeing similar changes or a different situation. You can reply off-list and I will summarize the results to the group. Please state if I should mention your name in the summary. Greetings, Wolfgang Zenker -- punkt.de GmbH Tel. +49 721 9109-500 Fax: -100 .infrastructure info(a)punkt.de https://infrastructure.punkt.de/ Kaiserallee 13a CEO: Jürgen Egeling, Daniel Lienert, Fabian Stein D-76133 Karlsruhe AG Mannheim HRB 108285

2 1

RIPE554-bis
by Tim Chown 30 Oct '20

30 Oct '20

Hi, I’m posting here as a heads-up that an effort has begun to revise RIPE-554, involving the original authors, myself and Tim Winters. We have a 5 min slot tomorrow in the 1pm CET IPv6 WG session to flag the work, to solicit input. The original publication was back in November 2010 with RIPE-501, which was updated in June 2012 with RIPE-554. There’s many references that have been obsoleted, and potentially much to add or remove. References to 2G cellular date the document. We’d like to begin by addressing the more strategic / structural questions. Such high level questions include: - Is there agreement to progress a –bis version now? Eight years have passed, people ask for guidance… - Should we keep the scope to (largely) enterprise or expand it? If so, to what? - Is the linkage to the IPv6 Ready Logo programme still desired? - Are there new classes of equipment to add, e.g. IoT/low power, WiFi controllers, …? - Are specific sections outdated, or are there significant new sections to add? - Should we add guidance on applying the content to different use cases? As separate docs? Appendices? We’ve currently working on the -bis as a Google doc, for which there’s a PDF of the current snapshot available from: https://go6.si/wp-content/uploads/2020/10/RIPE554-bis-v_01.pdf For now, please comment to the list, and maybe start a new thread for new topics. Tim

7 9

Rquirements for VPN
by christian bretterhofer 29 Oct '20

29 Oct '20

After reading https://go6.si/wp-content/uploads/2020/10/RIPE554-bis-v_01.pdf I see VPNs as part of the Network Security Equipment. But in my opinium there is not enough definition to be a VPN quality criteria. VPN external Protocol Must support IPv6 clients to IPv6 servers (6-to-6) ( Ipv6 Only) VPN external Protocol Must support IPv4 clients to IPv4 servers (4-to-4) (Ipv4 only) Transport inside of VPN VPN inner Protocol Must support IPv6 clients to IPv6 servers (6-to-6) VPN inner Protocol Must support IPv4 clients to IPv4 servers (4-to-4) VPN inner Protocol should support Dual stack. VPN inner Protocol should support 4in6 6in4 (transition protocols) The Idea from wireguard is maybe also a should the external protocol switch from Ipv6 to Ipv4 or Ipv4 to Ipv6 then the inner protocol should stay connected. Protocols with DNS64/NAT64 support would also help. maybe it fist into this recommendation document. -- --- best regards Christian Bretterhofer Enterprise User:

3 2

Minutes from ripe 80
by Jetten Raymond 28 Oct '20

28 Oct '20

Hi, We have published the RIPE 80 minutes as draft here: https://www.ripe.net/participate/ripe/wg/active-wg/ipv6/minutes/ipv6-workin… Let me know if these need any changes or corrections. Rgds, Ray

1 0

IPv6 WG @ RIPE81 Agenda
by Jen Linkova 07 Oct '20

07 Oct '20

The agenda for the IPv6 WG session at RIPE81 has been published: https://ripe81.ripe.net/programme/meeting-plan/ipv6-wg/ Thanks to everyone who submitted a talk - this time we got really overbooked so my apologies if your talk was not accepted! See you in 3 weeks! -- SY, Jen Linkova aka Furry

1 0

New on RIPE Labs: A Look Into the Tor Network Work on Supporting IPv6
by Alun Davies 01 Oct '20

01 Oct '20

Dear colleagues, With support from the RIPE NCC Community Projects Fund 2019, the Tor project has implemented IPv6 support across its network. Read how the work they've done will help make sure users across the RIPE NCC service region will have a more reliable experience on the Tor network: https://labs.ripe.net/Members/tor_grants/a-look-into-the-tor-network-work-o… Kind regards, Alun Davies RIPE NCC

1 0