From fgont at si6networks.com Wed Jul 1 22:37:05 2015 From: fgont at si6networks.com (Fernando Gont) Date: Wed, 01 Jul 2015 17:37:05 -0300 Subject: [ipv6-wg] Fwd: Operational Implications of IPv6 Packets with Extension (Fwd: New Version Notification for draft-gont-v6ops-ipv6-ehs-packet-drops-00.txt) In-Reply-To: <55944EFF.8020207@si6networks.com> References: <55944EFF.8020207@si6networks.com> Message-ID: <55944F71.5010502@si6networks.com> FYI To the extent that it's possible, please discuss the I-D on the IETF v6ops mailing-list. But feel free to discuss it here anyway (I'll monitor the list for comments). Thanks! Best regards, Fernando -------- Forwarded Message -------- Subject: Operational Implications of IPv6 Packets with Extension (Fwd: New Version Notification for draft-gont-v6ops-ipv6-ehs-packet-drops-00.txt) Date: Wed, 01 Jul 2015 17:35:11 -0300 From: Fernando Gont To: v6ops at ops.ietf.org CC: draft-gont-v6ops-ipv6-ehs-packet-drops at tools.ietf.org Folks, A group of us published a new I-D trying to summarize the operational and security implications. It is meant to summarize the reasons for which operators may intentionally drop IPv6 packets containing IPv6 extension headers. The I-D is available at: As far as this I-D is concerned, think of us co-authors as the messengers. The I-D doesn't argue itself whether you should (or should not) drop packets with EHs, but simply discusses the challenge they represent in some scenarios. Comments will be more than welcome. Thanks! Best regards, Fernando -------- Forwarded Message -------- Subject: New Version Notification for draft-gont-v6ops-ipv6-ehs-packet-drops-00.txt Date: Wed, 01 Jul 2015 13:29:21 -0700 From: internet-drafts at ietf.org To: Gert Doering , Nick Hilliard , Shucheng LIU (Will) , Gert Doering , Warren Kumari , Will Liu (Shucheng) , Fernando Gont , Nick Hilliard , Fernando Gont , Warren Kumari A new version of I-D, draft-gont-v6ops-ipv6-ehs-packet-drops-00.txt has been successfully submitted by Fernando Gont and posted to the IETF repository. Name: draft-gont-v6ops-ipv6-ehs-packet-drops Revision: 00 Title: Operational Implications of IPv6 Packets with Extension Headers Document date: 2015-07-01 Group: Individual Submission Pages: 13 URL: https://www.ietf.org/internet-drafts/draft-gont-v6ops-ipv6-ehs-packet-drops-00.txt Status: https://datatracker.ietf.org/doc/draft-gont-v6ops-ipv6-ehs-packet-drops/ Htmlized: https://tools.ietf.org/html/draft-gont-v6ops-ipv6-ehs-packet-drops-00 Abstract: This document summarizes the security and operational implications of IPv6 extension headers, and attempts to analyze reasons why packets with IPv6 extension headers may be dropped in the public Internet. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat From furry13 at gmail.com Tue Jul 7 11:04:51 2015 From: furry13 at gmail.com (Jen Linkova) Date: Tue, 7 Jul 2015 11:04:51 +0200 Subject: [ipv6-wg] RIPE71 IPv6 WG: call for presentations Message-ID: Dear IPv6 Enthusiasts, RIPE71 is just 4 months away and it's time to start thinking about IPv6 WG session agenda! If you would like to present, or just have any suggestions on what we should discuss) - please email ipv6-wg-chairs at ripe.net. If you would like to present, we need the following information: - a tentative title of your talk; - short summary - how much time you need (I'd recommend allowing 5 mins for questions). Thank you! -- SY, Jen Linkova aka Furry on behalf of IPv6 WG chairs. From dez at otenet.gr Thu Jul 9 13:23:15 2015 From: dez at otenet.gr (Yannis Nikolopoulos) Date: Thu, 9 Jul 2015 14:23:15 +0300 Subject: [ipv6-wg] IPv6 martian filter-set Message-ID: <559E59A3.8090608@otenet.gr> Hello, I'm not sure if people are using the fltr-martian-v6 filter set maintained by Job Snijders: filter-set: fltr-martian-v6 descr: Current IPv6 martians mp-filter: { 0000::/8^+, # loopback, unspecified, v4-mapped 0200::/7^+, # Reserved by IETF [RFC4048] 2001::/32^-, # Teredo prefix [RFC4380] 2001:db8::/32^+, # NON-ROUTABLE range to be used for documentation purpose [RFC3849] 2002::/16^-, # 6to4 prefix [RFC3068] 3ffe::/16^+, # used for the 6bone but was returned [RFC5156] 5f00::/8^+, # used for the 6bone but was returned [RFC5156] fc00::/7^+, # Unique Local Unicast [RFC4193] fe80::/10^+, # Link Local Unicast [RFC4291] fec0::/10^+, # Reserved by IETF [RFC3879] ff00::/8^+ # Multicast [RFC4291] } I'm trying to figure out why prefixes like 0200::/7 or 0400::/6 are not included in this list Any ideas? cheers, Yannis From job at instituut.net Thu Jul 9 13:38:03 2015 From: job at instituut.net (Job Snijders) Date: Thu, 9 Jul 2015 13:38:03 +0200 Subject: [ipv6-wg] IPv6 martian filter-set In-Reply-To: <559E59A3.8090608@otenet.gr> References: <559E59A3.8090608@otenet.gr> Message-ID: <20150709113803.GH9225@Vurt.local> On Thu, Jul 09, 2015 at 02:23:15PM +0300, Yannis Nikolopoulos wrote: > I'm not sure if people are using the fltr-martian-v6 filter set > maintained by Job Snijders: > > filter-set: fltr-martian-v6 > descr: Current IPv6 martians > mp-filter: { > 0000::/8^+, # loopback, unspecified, v4-mapped > 0200::/7^+, # Reserved by IETF [RFC4048] > 2001::/32^-, # Teredo prefix [RFC4380] > 2001:db8::/32^+, # NON-ROUTABLE range to be used for > documentation purpose [RFC3849] > 2002::/16^-, # 6to4 prefix [RFC3068] > 3ffe::/16^+, # used for the 6bone but was returned > [RFC5156] > 5f00::/8^+, # used for the 6bone but was returned > [RFC5156] > fc00::/7^+, # Unique Local Unicast [RFC4193] > fe80::/10^+, # Link Local Unicast [RFC4291] > fec0::/10^+, # Reserved by IETF [RFC3879] > ff00::/8^+ # Multicast [RFC4291] > } > > I'm trying to figure out why prefixes like 0200::/7 or 0400::/6 are not > included in this list 0200::/7 was already there. > Any ideas? The answer is simple: Vurt:~ job$ whois fltr-martian-v6 | grep manual remarks: this object is manually maintained I've just updated it, manually :-) Kind regards, Job From dez at otenet.gr Thu Jul 9 15:17:31 2015 From: dez at otenet.gr (Yannis Nikolopoulos) Date: Thu, 9 Jul 2015 16:17:31 +0300 Subject: [ipv6-wg] IPv6 martian filter-set In-Reply-To: <20150709113803.GH9225@Vurt.local> References: <559E59A3.8090608@otenet.gr> <20150709113803.GH9225@Vurt.local> Message-ID: <559E746B.4020203@otenet.gr> hello Job, thanks for the update :) On 07/09/2015 02:38 PM, Job Snijders wrote: > On Thu, Jul 09, 2015 at 02:23:15PM +0300, Yannis Nikolopoulos wrote: >> I'm not sure if people are using the fltr-martian-v6 filter set >> maintained by Job Snijders: >> >> filter-set: fltr-martian-v6 >> descr: Current IPv6 martians >> mp-filter: { >> 0000::/8^+, # loopback, unspecified, v4-mapped >> 0200::/7^+, # Reserved by IETF [RFC4048] >> 2001::/32^-, # Teredo prefix [RFC4380] >> 2001:db8::/32^+, # NON-ROUTABLE range to be used for >> documentation purpose [RFC3849] >> 2002::/16^-, # 6to4 prefix [RFC3068] >> 3ffe::/16^+, # used for the 6bone but was returned >> [RFC5156] >> 5f00::/8^+, # used for the 6bone but was returned >> [RFC5156] >> fc00::/7^+, # Unique Local Unicast [RFC4193] >> fe80::/10^+, # Link Local Unicast [RFC4291] >> fec0::/10^+, # Reserved by IETF [RFC3879] >> ff00::/8^+ # Multicast [RFC4291] >> } >> >> I'm trying to figure out why prefixes like 0200::/7 or 0400::/6 are not >> included in this list > > 0200::/7 was already there. > >> Any ideas? > > The answer is simple: > > Vurt:~ job$ whois fltr-martian-v6 | grep manual > remarks: this object is manually maintained > > I've just updated it, manually :-) > > Kind regards, > > Job > From pedrovaz at ripe.net Mon Jul 27 10:50:23 2015 From: pedrovaz at ripe.net (Pedro Vaz) Date: Mon, 27 Jul 2015 10:50:23 +0200 Subject: [ipv6-wg] New IPv6 Tutorials Available Online Message-ID: <55B5F0CF.70307@ripe.net> Dear colleagues, We are pleased to announce that two new IPv6 videos are now available as part of our growing collection of E-Learning Tutorials. You can find these here: Neighbor Discovery Protocol: https://www.ripe.net/support/training/learn-online/videos/ipv6/ipv6-fundamentals 464XLAT: https://www.ripe.net/support/training/learn-online/videos/ipv6/transition-mechanisms These videos also form part of the "Introduction to IPv6" online course that is available through the RIPE NCC Academy. If you want to join this course, you can register here: academy.ripe.net. The RIPE NCC Academy and RIPE NCC E-Learning Tutorials are a free service available to everyone. We plan to announce even more exciting E-Learning news in the coming months, so stay tuned! If you have any questions or comments, feel free to contact us at. Happy learning! Kind regards Pedro Vaz Trainer/Graphics Animator RIPE NCC