December 2023 - ipv6-wg - mailman.ripe.net

Question about how I handle web sites in my IPv6 survey
by Mark Prior 02 Jan '24

02 Jan '24

Hi there, I'm seeking some views on how I should report some web failures on my IPv6 survey page <https://www.mrp.net/ipv6_survey/>. If a site has both A and AAAA records for a web site I will try to connect to the IPv6 address and see if there is a web site listening there. It will start at tcp port 80 and then follow any redirects until hopefully it finds a 200 response. The cases where it gets to a 200 are fine as that's "success" but there are some failure modes that I can't really make my mind up on so having some feedback would be potentially useful. In all these cases I see a site with A and AAAA records so I connect on port 80 of the IPv6 address(es). 1. If the connection fails should I just report that or should I do anything more? For example see if the site responds via IPv4. 2. If the connection succeeds (so I assume there should be a working IPv6 based web server) but after querying it with a HTTP/1.1 message sees the site resets the connection (or fails in some other manner). 3. The connection succeeds as does the query and I get a 301 redirect to a location that fails to connect (typically it's the https port but could be another domain name). Again is this enough or should it do something else? The difference is in how they are reported on the main survey page. If there is a problem then the cell will be blue but if I stop at the error then some indication of the error will appear in the cell. If after the failure I check if IPv4 works then the cell will still be blue but the indication in the cell will be the IPv4 status (more often than not this is success and so the indicator is type of connection (HTTP, HTTPS, HSTS, H2, etc) with a link to the web page. At the moment I'm not consistent and I probably should be :-) but what type of indication is more helpful? Finally in some cases I'll get a HTTP status code such as 403, 429 or 503 rather than 200 and these are reported with a background of either light green or light red depending on whether it occurred on an IPv6 or IPv4 connection. Should these be blue rather than a different green/red? Thanks, Mark.

3 4

Allocating a /16 to a large enterprise ?
by Eric Vyncke (evyncke) 12 Dec '23

12 Dec '23

[This is about ARIN, but curious to see if anybody has any insight...] A colleague of mine showed me https://whois.arin.net/rest/net/NET6-2630-2, i.e., a /16 allocated by ARIN to Capital One (AFAIK a US bank). Of course, this may be a tool bug, or a human encoding mistake, else I will start to fear an IPv6 addresses exhaustion in the future (only 2**13 of /16 out of 2000::/3). If anyone has any insight, then I will welcome this insight in this specific case. Regards -éric

6 5

follow up on the IPv6-wg session at RIPE 87
by Raymond Jetten 07 Dec '23

07 Dec '23

Dear list Members, During RIPE 87 Benedikt Stockebrand has stepped down as IPv6 WG Co-Chair. Again Benedikt, on behalf of Jen and me thanks for the many years of having you. Jen and I decided to give Benedikt a small present after stepping down. A bottle of quality Italian wine, a wine bottle opener, a glass to drink from, and bag of popcorn. We had 2 candidates to fill Benedikt's place. Christian Seitz, and Paolo Volpato. We used Meetecho's poll as a platform where participants on site and remote could show their preference. The result was that Christian is now our new co-chair, Welcome Christian. We hope to see you all again in Krakow Poland next may. On behalf of Jen and Christian, Raymond Jetten RIPE IPv6 Working Group co-Chair To the co Chairs: ipv6-wg-chair(a)ripe.net<mailto:ipv6-wg-chair@ripe.net> To the mailing list: ipv6-wg(a)ripe.net<mailto:ipv6-wg@ripe.net> For Internal Use Only

1 0