Dear IPv6-wg list members and RIPE community.
In the upcoming RIPE meeting (RIPE87) we will select a new co-chair, who will fill the gap, since Benedikt Stockebrand has decided to step down and not run for another term.
The selection process will be done at the IPv6-wg session, via the meeting system "Meetecho". There will be a poll on who do you want to select.
This system is available for all onsite and online.
You will all get a link from the meeting organization to the Meetecho website, keep it near...
You can still register for the meeting online or onsite: https://ripe87.ripe.net/attend/register/
In response to our request on the list we are glad to announce that we have 2 interested candidates:
Christian Seitz
Paolo Volpato
They will send in their personal motivations and backgrounds to this list soon.
We would like the members of this list to show their support for their preferred candidate, or send questions to the candidates, so we can discuss this even before the meeting. The decision however will be made at the meeting as said before.
Best regards,
The IPv6 WG chairs.
For Internal Use Only
Some very nice visuals, enjoy !
Subject: [118attendees] Animation showing IPv6 growth over time.
Date: Mon, 06 Nov 2023 07:16:53 -0600
From: Nick Buraglio <buraglio(a)forwardingplane.net>
Reply-To: Nick Buraglio <buraglio(a)forwardingplane.net>
To: 118attendees(a)ietf.org
This set of animations have made the rounds within some of the IPv6
groups at IETF and it was thought that the 118 participants may find it
encouraging and interesting.
These animations showing both the growth of IPv6 over time were compiled
by a researcher named Barrett Lyon using data from RouteViews* data.
The animation of v6 starts on May 9th, 2003, as that is when RouteViews
began compiling their IPv6 data.
Enjoy!
IPv4 vs IPv6
Full: https://www.youtube.com/watch?v=vo5glK9czIE
1m social media: https://www.youtube.com/watch?v=tMyFRGGGWOQ
IPv6 with labels
Full: https://www.youtube.com/watch?v=jj9RjUtZ54o
1m social media: https://www.youtube.com/watch?v=jj9RjUtZ54o
* https://www.routeviews.org/routeviews/
For Internal Use Only
Hi all,
On behalf of the University of Liege (Belgium), we've been doing
measurements on IPv6 Extension Headers over the last two years. More
specifically, we're trying to evaluate how they are processed by routers
along the path, and so from the edge. Now, we would like to compare our
observations with the reality of operators. For that, we propose this
very short survey [1] to operators and would really appreciate if you
could complete it. Note that we guarantee anonymity of your answers by
not sharing any data.
Looking forward to your input.
Thanks,
Justin
[1]
https://docs.google.com/forms/d/e/1FAIpQLSeHgEWVQMrAbB9-pRf-T-mDHXxRxw-mAqO…
Hi all,
Some folks in this WG may not know that I maintain a web page that shows
accessibility to web, mail and DNS services via IPv6 across a number of
domains. As I have just rewritten the script that generates it I thought
I would take that opportunity to promote it a little.
Back in 2007 at an Internet2 Joint Techs meeting Ron Broersma of DREN
presented a talk on IPv6 adoption that included a coloured chart that
showed a small number of Internet2 related domains and if they had IPv6
accessible web, mail and DNS. Basically the argument was that it was
fine to have IPv6 plumbing but what were you doing with it (and the
answer was not a lot). After chatting with Ron I decided to code up
something and create a web page so I could report back any changes.
Early in the piece the updates were ad hoc (probably driven by meeting
deadlines) but eventually it was run by cron. Now it runs daily and
works though a largish list of domains seeing if there are web, mail
(smtp, submission and imap/pop), DNS, NTP, XMPP and SIP services
available via IPv6. Also there is DNSSEC because something has to have
worse deployment than IPv6 :-)
Originally research and education domains dominated the list but over
time I have added ISP/telcos and other commercial companies. There are
probably zombie domains in the list too.
Anyway that's enough of a background. If you are interested then have a
look at <https://www.mrp.net/ipv6_survey/>.
I am happy to add more domains if you want to suggest them.
Regards,
Mark.
Dear IPv6 Working Group,
Benedikt Stockebrand, who has been one of the co-chairs of the IPv6 Working Group since RIPE 69
has announced he wishes to step down at the RIPE 87 meeting in Rome, at the end of his term.
Thus, we have a call for candidates.
The term of a IPv6 WG co-chair is three years. A current co-chair may stand for
re-selection at the end of their term or may resign voluntarily at any time.
What is the IPv6 WG doing:
The working group activities may be anything useful in helping people to deploy IPv6,
and to manage IPv4/IPv6 co-existence. These activities include:
Outreach
Education
Sharing deployment experiences
Discussing and fixing operational issues
The co-chairs also prepare the program for the IPv6 WG session at the ripe meetings.
The working group will cooperate with operators and others, both inside and outside the
networking industry, to share resources and combine efforts.
The tasks and expectations of a WG co-chair are described here:
https://www.ripe.net/publications/docs/ripe-692
A WG co-chair must comply with the Code of Conduct:
https://www.ripe.net/publications/docs/ripe-766
If you feel you are interested in this or have any questions on this, you can drop the current
co-chairs a note ipv6-wg-chair(a)ripe.net<mailto:ipv6-wg-chair@ripe.net>
We kindly request you to respond at latest Friday 10-November-2023 midday CET (Amsterdam),
when the call for candidates will be closed.
After this we will announce the candidates on the list, and you can express your support.
The official selection will take place at the RIPE 87 Meeting in Rome during the IPv6 Working Group session.
On behalf of the IPv6 WG co-chairs,
Ray
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
