- ipv6-wg - mailman.ripe.net

Status update replacing ripe-501
by Marco Hogewoning 23 May '12

23 May '12

Dear working group, In case anybody is wondering what happened to this. The working group chairs and authors are pretty confident that all issues have been addressed and the document in its current form is the one that will published. At the moment we are in the process of doing a final review for spelling and grammar, after which we will ask the RIPE NCC to assign a number and publish the document. Grtx, Marco

1 0

New article on RIPE Labs: Measuring IPv6 at Network and Customer Level
by Mirjam Kuehne 16 May '12

16 May '12

Dear all, Please find a new article "Measuring IPv6 at the Network and the Customer Level" on RIPE Labs. It has been contributed by George Michaelson from APNIC: https://labs.ripe.net/Members/ggm/measuring-ipv6-at-the-network-and-the-cus… Kind regards, Mirjam Kuehne RIPE Labs

1 0

6to4 and teredo pingables?
by Aleksi Suhonen 13 May '12

13 May '12

Hi, We run 6to4 and Teredo relay routers and in order to monitor the service our network monitoring system has been pinging a handful of 6to4 and Teredo addresses elsewhere. If more than one of those addresses fail to answer pings, an alarm is raised. Now I'm looking for a few more addresses I could ping, so I could raise the alert threshold a bit. Any volunteers? And in case anyone else wants to ping some of our hosts, here's a couple of candidates: (sorry, no Teredo hosts) ns.trex.fi. IN AAAA 2002:c38c:c38c:15::35 mail.trex.fi. IN AAAA 2002:c38c:c38c:14:203:baff:fe0f:d68b Yours sincerely, -- Aleksi Suhonen / TREX

1 0

New on RIPE Labs: Test your IPv6 Reachability by Using RIPE Atlas
by Mirjam Kuehne 09 May '12

09 May '12

[apologies for duplicate mails] Dear colleagues, You can now use RIPE Atlas to test your IPv6 reachability. This also works if you do not host a RIPE Atlas probe yourself. However, please note that this is only available to RIPE NCC members. Please find the details on RIPE Labs: https://labs.ripe.net/Members/becha/test-your-ipv6-reachability-using-ripe-… If you have any comments or questions, please let us know. Kind Regards, Mirjam Kuehne RIPE NCC

1 0

IETF I-D: Security Implications of IPv6 on IPv4 Networks
by Fernando Gont 02 May '12

02 May '12

Folks, A couple of weeks ago we published a new IETF I-D entitled "Security Implications of IPv6 on IPv4 networks". The I-D is available at: <http://tools.ietf.org/html/draft-gont-opsec-ipv6-implications-on-ipv4-nets> The Abstract of the I-D is: ---- cut here ---- This document discusses the security implications of native IPv6 support and IPv6 transition/co-existence technologies on "IPv4-only" networks, and describes possible mitigations for the aforementioned issues. ---- cut here ---- We're currently working on a revision of the document, so any comments will be really appreciated. Thanks! Best regards, -- Fernando Gont SI6 Networks e-mail: fgont(a)si6networks.com PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

1 0

New on RIPE Labs: Update on IPv6 Address Distribution
by Mirjam Kuehne 02 May '12

02 May '12

Dear colleagues, At the recent RIPE Meeting we presented some IPv6 address distribution statistics. In this RIPE Labs article, you can find statistics on IPv6 allocations and assignments. In particular, the article details what affect the removal of the requirement to be multihomed had on the number of assignments and the relationship between the age of an LIR and the number of IPv6 addresses they have received. https://labs.ripe.net/Members/mirjam/update-on-ipv6-address-distribution Kind regards, Mirjam Kuehne RIPE NCC

1 0

Last Call for publication of RIPE-501bis (reply by 20120426)
by David Kessens 02 May '12

02 May '12

In the IPv6 working session at the RIPE meeting in Slovenia, we discussed: http://go6.si/docs/Requirements-for-IPv6-in-ICT-equipment-v.9.pdf The meeting participants felt that the document is now ready for publication. Therefore, I would like to give everybody a final chance to bring up major issues that must be resolved before publication. Please comment by Thu 20120426 if you have major issues that require a delay in publication. We will ask the RIPE NCC to publish the document after the Last Call ends if no serious issues are uncovered by that date. The RIPE NCC will do an editorial pass for spelling, grammar and minor issues before it will publish the document. Feel free to contact the working group chairs directly <ipv6-wg-chairs(a)ripe.net> if you find anything minor that doesn't need working group review and we will make sure that it gets fixed in the final document. Thanks, David, Shane & Marco ---

3 3

RIPE 64 Working Group session
by Marco Hogewoning 18 Apr '12

18 Apr '12

Hi all, This is to remind you that the IPv6 Working Group will meet here in Ljubljana, tomorrow Thursday the 19th. We have 2 sessions, starting at 11:00 after the first coffee break in the main room. With a lunch break in between we continue at 14:00 in the same room for the second half. The agenda is posted to the website and available via https://ripe64.ripe.net/programme/meeting-plan/ipv6-wg/ We hope to see you all there. In case you couldn't make it to Slovenia, as always these sessions will be broadcasted and recorded for the archives. For remote participants feedback channels using IRC/Jabber will be available. More information can be found on the RIPE 64 meeting website, the stream is available via https://ripe64.ripe.net/live/ (Grant Union Hall). In case you want to join remote, Slovenian local time is UTC +0200. See you tomorrow, Marco, David and Shane

1 0

Fw: WG Review: sunset4 (sunset4)
by Shane Kerr 18 Apr '12

18 Apr '12

All, FYI, the IETF may be starting some (more) work of interest to IPv6 folks. Perhaps this will inspire us to change the IPv6 working group to the IPv4 CGN/NAT working group. ;) Cheers, -- Shane Begin forwarded message: Date: Tue, 17 Apr 2012 09:41:57 -0700 From: IESG Secretary <iesg-secretary(a)ietf.org> To: IETF Announcement List <ietf-announce(a)ietf.org> Subject: WG Review: sunset4 (sunset4) A new IETF working group has been proposed in the Internet Area. The IESG has not made any determination as yet. The following draft charter was submitted, and is provided for informational purposes only. Please send your comments to the IESG mailing list (iesg(a)ietf.org) by Tuesday, April 24, 2012. sunset4 (sunset4) ----------------------------------------- Status: Proposed Working Group Last Updated: 2012-04-13 Chairs: TBD Internet Area Directors: Ralph Droms <rdroms.ietf(a)gmail.com> Brian Haberman <brian(a)innovationslab.net> <TBD> Internet Area Advisor: <TBD> Area Advisors: OPS: <TBD> TSV: <TBD> RTG: <TBD> Mailing Lists: <TBD, pending final WG name> Description of Working Group: The IETF is committed to the deployment of IPv6 to ensure the evolution of the Internet. However, the IPv4-only components of the Internet must continue to operate as much as possible during the transition from IPv4 to IPv6. The Working Group will standardize technologies that facilitate the graceful sunsetting of the IPv4 Internet in the context of the exhaustion of IPv4 address space while IPv6 is deployed. These technologies will likely be less optimal than equivalent technologies for IPv6-only and dual-stack networks. The Working Group works only on IPv4 protocols to facilitate IPv4 sunsetting. The Working Group may work on fixing security bugs in existing IPv4-specific protocols but is not chartered to add new security functionality to those protocols. The working group will provide a single venue for the consideration of IPv4 sunsetting, while ensuring that any such technologies do not impede the deployment of IPv6 and do not duplicate functions and capabilities already available in existing technologies. Therefore, along the lines of draft-george-ipv6-support, before the working group adopts any technology, it must: 1) describe the problem to be solved and show that there is widespread demand for a solution 2) demonstrate that the problem can not be solved with existing technologies 3) provide a description of the proposed solution along with the impact on current IPv4-only use and its ability to promote the deployment of IPv6 These steps will likely be described in the form of a use case and requirements document. Only after the above mentioned steps have been completed and the results accepted by the community will the IETF consider adding new work items to the Working Group charter. This new work may include protocol specifications. The work spans over multiple IETF areas including as Internet, Operations, Transport and Routing. Therefore, cross-area coordination and support is essential and required. Any work on IPv4 to IPv6 transition methods is out of scope. The initial work items are: * Review current CGN documents, including requirements for standardization, and determine is CGN is a suitable sunsetting technology to become a work item * Gap analysis of IPv4 features to facilitate IPv4 sunsetting Milestones 2012-09 Complete review of CGN and, if necessary, propose CGN work items 2013-06 Send gap analysis on IPv4 sunsetting to IESG

1 0

Slides for "Recent Advances in IPv6 Security" at Hackito Ergo Sum 2012
by Fernando Gont 16 Apr '12

16 Apr '12

Folks, The slides for my presentation entitled "Recent Advances in IPv6 Security" at Hackito Ergo Sum 2012 (http://2012.hackitoergosum.org/) are available at: <http://www.si6networks.com/presentations/HES2012/fgont-hes2012-recent-advan…> The same slides are available in other formats at: <http://www.si6networks.com/presentations/index.html> Thanks! Best regards, -- Fernando Gont SI6 Networks e-mail: fgont(a)si6networks.com PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

1 0