Dear IPv6 working group,
we found some great presenters for our next IPv6 WG session in Krakow and
built an agenda. Our session will take place on Thursday 23 May 2024 from
11:00 - 12:30 CEST. The agenda will also be published in the RIPE88 meeting
plan [1] soon.
1. Welcome ([5 min]
* Opening and Welcome
* Approval of RIPE 87 Minutes
* Microphone Etiquette
2. Co-Chair-Change [10 min]
3. Operational issues discovered during IPv6-mostly migration [30 min incl. Q&A]
Jen Linkova
4. IPv4-with-IPv6 Next-Hop [20 min incl. Q&A]
Tobias Fiebig
5. IPv4-mapped IPv6 addresses [20 min incl. Q&A]
Ondřej Caletka
6. Thanks, Wrap Up and Rate the Talks [5 min]
If there are any changes to this agenda we will send an update and also update
the meeting plan on the website [1].
[1] https://ripe88.ripe.net/programme/meeting-plan/
On behalf of the IPv6 WG co-chairs,
Jen, Ray and Chris
Hello!
I want to share some experience and ask if other people here also
noticed that behavior.
I operate an IPv6 torrent client (qbittorrent/libtorrent) and I noticed
various things:
The client itself sometimes uses non-GUA source addresses when
connecting to GUA addresses in the default setting. When binding to the
GUA address only, it uses only them.
https://github.com/qbittorrent/qBittorrent/issues/19618
This seems to be not yet fixed.
I also notice a reasonable amount of incoming traffic with non-GUA
addresses like from 63ed:b73b::/32 or 485f:1207::/32, ac11:1::/32 etc.
This also shows that some ISPs don't seem to prohibit their
customers from sending such packages.
Does anybody here also experienced that?
Is there any monitoring at exchange points to find the source?
--
kind regards
Marco
Send unsolicited bulk mail to 1711396344muell(a)cartoonies.org
Dear IPv6 Working Group,
We are still looking for candidates to be a IPv6-WG co- chair.
Are you interested? Drop us (the current chairs) a mail. ipv6-wg-chair(a)ripe.net<mailto:ipv6-wg-chair@ripe.net>
Please do not send it to the list.
Or do you know anyone who could be suitable and interested?
Ask them to stand up and drop the co-chairs an email.
Below is a copy of the earlier request:
Jen Linkova, who has been one of the co-chairs of the IPv6 Working Group since RIPE 69
has announced she wishes to step down at the RIPE 88 meeting in Kraków, at the end of her 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 at ripe.net
We kindly request you to respond at latest Friday 3-May-2024 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 or concerns.
However the official selection will take place at the RIPE 88 Meeting in Kraków during the IPv6 Working Group session.
On behalf of the IPv6 WG co-chairs,
Jen, Christian & Ray
RIPE IPv6 Working Group co-Chair
To the co Chairs: ipv6-wg-chair at ripe.netmailto:ipv6-wg-chair at ripe.net<mailto:ipv6-wg-chair%20at%20ripe.net>
To the mailing list: ipv6-wg at ripe.netmailto:ipv6-wg at ripe.net<mailto:ipv6-wg%20at%20ripe.net>
For Internal Use Only
