[ipv6-wg@ripe.net] Call for agenda items RIPE49 & draft agenda (v1)
Please see below for the first version of the draft agenda. As usual, we don't have enough interesting topics (yet). That is bad news and good news: I need your help in finding interesting topics but the good news is that we will have time to accommodate your suggestions. Let me know if you want to volunteer for an agenda topic, but also feel free to suggest a topic that I or the list might know volunteers for. Thanks, David Kessens --- Updated agenda for the IPv6 Working Group Meeting RIPE49 When: 14:00 - 18:00, Wednesday September 22, 2004 Where: Medici Room, Renaissance Hotel, Manchester, UK A. Administrative stuff - appointment of scribe - agenda bashing (David Kessens) B. Global IPv6 routing table status (Gert Doering) C. Report(s) about *actual* v6 traffic volume as compared to v4? *what's real* out there, not what's on powerpoint? (input from the audience) D. What are the deployment plans behind the larger ipv6 allocations ? o TeliaSonera (Mikael Lind) E. Developments/initiatives regarding IPv6 in the RIPE region and beyond (input from the audience) F. Input for the RIPE NCC Activity Plan (input from the audience) Z. AOB ---
On 2-sep-04, at 3:14, David Kessens wrote:
Please see below for the first version of the draft agenda. As usual, we don't have enough interesting topics (yet). That is bad news and good news: I need your help in finding interesting topics but the good news is that we will have time to accommodate your suggestions. Let me know if you want to volunteer for an agenda topic, but also feel free to suggest a topic that I or the list might know volunteers for.
A topic that's near and dear to my heart is how an IPv6 host finds IPv6 addresses for resolving nameservers. The IETF doesn't seem to be able to reach consensus on doing this by having well known addresses, by advertising the addresses in the DNS or by doing this using some form of DHCP. And having more than one solution is also blocked. So what do we, as people who actually run IPv6, feel about this, and what can we do other than editing resolv.conf by hand every time we move to another IPv6 network? I'd be happy to summerize the issue (but be warned that I'm biased) but the real value in having this as an agenda item would be a discussion. I'll also be happy to talk about by IPv6 counter ( http://countipv6.bgpexpert.com/ ) but there isn't THAT much to tell. :-)
participants (2)
-
David Kessens
-
Iljitsch van Beijnum