From pim at ipng.nl Mon Jun 5 12:47:45 2006 From: pim at ipng.nl (Pim van Pelt) Date: Mon, 5 Jun 2006 21:47:45 +0200 Subject: [6bone] 6bone phaseout countdown notification - 1 months until phaseout In-Reply-To: <2a8350a60605062324h368a1658xf4ba9bfffa466087@mail.gmail.com> References: <2a8350a60605062324h368a1658xf4ba9bfffa466087@mail.gmail.com> Message-ID: <20060605194745.GA22619@bfib.ipng.nl> Hoi, | After June 6, 2006 no 6bone 3FFE prefixes, of any size/length, are to | be used on the Internet in any form. I have added BGP filtering at BIT (as12859) to prohibit 6BONE prefixes from entering our routing tables. SixXS has also turned off routing to these destinations. Where appropriate, we have collaborated with our participating ISPs to enable BGP filtering for all 3ffe::/16 routes. For all 20+ tunnelservers, we have disabled forwarding to 6BONE space by adding a route for 3ffe::/16 to lo0 and having them send ICMP unreachables for SixXS users trying to reach those destinations. 6BONE becomes 6GONE! -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pim at ipng.nl http://www.ipng.nl/ IPv6 Deployment ----------------------------------------------- From bob at thefinks.com Mon Jun 5 12:53:37 2006 From: bob at thefinks.com (Robert Fink) Date: Mon, 5 Jun 2006 12:53:37 -0700 Subject: [6bone] 6bone phaseout countdown notification - 1 months until phaseout In-Reply-To: <20060605194745.GA22619@bfib.ipng.nl> References: <2a8350a60605062324h368a1658xf4ba9bfffa466087@mail.gmail.com> <20060605194745.GA22619@bfib.ipng.nl> Message-ID: <2a8350a60606051253u2e20ec3ta4ea7b37905a9b2c@mail.gmail.com> Pim, Thanks for the note. Good luck! Bob On 6/5/06, Pim van Pelt wrote: > Hoi, > > | After June 6, 2006 no 6bone 3FFE prefixes, of any size/length, are to > | be used on the Internet in any form. > I have added BGP filtering at BIT (as12859) to prohibit 6BONE prefixes > from entering our routing tables. > > SixXS has also turned off routing to these destinations. Where > appropriate, we have collaborated with our participating ISPs to enable > BGP filtering for all 3ffe::/16 routes. For all 20+ tunnelservers, we > have disabled forwarding to 6BONE space by adding a route for 3ffe::/16 > to lo0 and having them send ICMP unreachables for SixXS users trying to > reach those destinations. > > 6BONE becomes 6GONE! > > -- > ---------- - - - - -+- - - - - ---------- > Pim van Pelt Email: pim at ipng.nl > http://www.ipng.nl/ IPv6 Deployment > ----------------------------------------------- > From bob at thefinks.com Mon Jun 5 12:55:21 2006 From: bob at thefinks.com (Robert Fink) Date: Mon, 5 Jun 2006 12:55:21 -0700 Subject: [6bone] 6bone phaseout is tomorrow, 6 June 2006... be ready! Message-ID: <2a8350a60606051255mc8ac318t80de07d051012785@mail.gmail.com> 6bone Operators & Users, Per RFC 3701, "6bone (IPv6 Testing Address Allocation) Phaseout ", 3FFE prefixes only remain valid until June 6, 2006. After June 6, 2006 no 6bone 3FFE prefixes, of any size/length, are to be used on the Internet in any form. Note that on June 6, 2006 3FFE prefixes do not actively need to be returned to the 6bone registry; 3FFE prefixes will simply be invalid after that date and assumed to be totally under the control of the IANA. Network operators may filter 3FFE prefixes on their borders to ensure these prefixes are not misused. Because of this, it is highly recommend that all 6Bone participants take early measures to find alternative IPv6 services, instead of waiting until the last minute, in order to avoid service disruption. Please take appropriate action now. Regards, Bob Fink From jeroen at unfix.org Mon Jun 5 15:48:51 2006 From: jeroen at unfix.org (Jeroen Massar) Date: Tue, 06 Jun 2006 00:48:51 +0200 Subject: [6bone] 6/6/6 06:06:06 - Farewell 6bone Message-ID: <1149547731.13412.31.camel@firenze.zurich.ibm.com> Dear 6bone, On this sad date of 6/6/6 when the clock has struck 00:00 in most countries on the European continent, it is time for your demise. When the clock strikes 06:06:06 here it will also be 6/6/6 in the US and thus globally the final hours will have chimed in. At the moment of writing this sad letter I also have to conclude that some people didn't abide by the 6bone rules, even though the clock has chimed into the phaseout day, still 57 of the 144 assigned networks are announcing 6bone space, another 52 didn't even take the small moment of time to return the prefix to the registry when they where asked to, they clearly didn't read the mailinglist either nor where they subscribed. It is too bad that your demise seems to have been also on a note of neglect and due to people who initially wanted to use you for experimentation and advance based on what they learned from you, they forgot all about you. We will not forget you and abandon you in disgrace as that is not what you have deserved. We will remember the 6bone as the start of the IPv6 capable internet, the network that was used to experiment with, where the first IPv6 implementations saw it's light and where a large number of problems where found, debugged and resolved. We will remember you as the network that started the freedom of having enough IP addresses for everybody around the world and maybe even one day beyond. Thanks for your kindness and thanks for your time. Let the 6bone rest in piece and not in pieces and apply filters where needed. Results of filtering can be seen at: http://www.sixxs.net/tools/grh/dfp/6bone/ Further IPv6 operational content can be found at: http://lists.cluenet.de/mailman/listinfo/ipv6-ops nibbles to nibbles, bits to bits. Greets, Jeroen -- A few example filters, do remind to remove these one day ;) Juniper (BGP): policy-statement ipv6-from-customer { from { family inet6; route-filter 3ffe::/16 orlonger next policy; } then reject; } Linux: ip -6 ro add 3ffe::/16 dev lo Free/Net/OpenBSD: route add -inet6 3ffe:: -prefixlen 16 lo0 Cisco (BGP): ipv6 prefix-list ipv6-from-customer deny 3ffe:::/16 le 128 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 313 bytes Desc: This is a digitally signed message part Url : http://mailman.isi.edu/pipermail/6bone/attachments/20060606/f4a4bfd1/attachment.bin From jordi.palet at consulintel.es Mon Jun 5 16:39:15 2006 From: jordi.palet at consulintel.es (JORDI PALET MARTINEZ) Date: Tue, 06 Jun 2006 01:39:15 +0200 Subject: [6bone] The IPv6 Day: Bye 6Bone. Hi, IPv6 ! Message-ID: Today 6Bone Operators & Users say bye to the experimental network which allowed, already some years ago, to turn IPv6 into the production space. With the occasion of this virtual celebration, we have a couple of quotes from two key people on this subject: * Bob Fink (6Bone Project): ?After more than ten years of planning, development and experience with IPv6, with efforts from all around the world, it is gratifying for me to see the 6Bone phase-out on the 6th of June 2006, having served it's purpose to stimulate IPv6 deployment and experience, leaving IPv6 a healthy ongoing component of the future of the Internet!? * Brian Carpenter (IBM, co-author of multiple IPv6 RFCs and IETF chair): ?It's very encouraging to see IPv6 moving forward both technically and commercially, with its address assignments now routinely managed by the same registries that look after the rapidly diminishing IPv4 address pool. I look forward to the day the Internet reaches ten billion active nodes with public addresses, which will only be possible with IPv6.? Users can learn how to enable IPv6, enjoy free IPv6 production connectivity and use some trial services at the IPv6 Day web site (http://www.ipv6day.org) (in several languages). http://www.ipv6tf.org/news/newsroom.php?id=2037 ********************************************** The IPv6 Portal: http://www.ipv6tf.org Barcelona 2005 Global IPv6 Summit Slides available at: http://www.ipv6-es.com This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited. From bob at thefinks.com Tue Jun 6 08:42:56 2006 From: bob at thefinks.com (Robert Fink) Date: Tue, 6 Jun 2006 08:42:56 -0700 Subject: [6bone] 6bone is PHASED OUT !! Thanks to all who have worked on the 6bone. Message-ID: <2a8350a60606060842x27209bb8w749c51f59eeb6e54@mail.gmail.com> 6bone Operators & Users, Today is the day! The 6bone is phased out. I would like to thank everyone who has participated in the 6bone during the last 10 years. === Per RFC 3701, "6bone (IPv6 Testing Address Allocation) Phaseout ", 3FFE prefixes only remains valid until TODAY, June 6, 2006. After TODAY, June 6, 2006, no 6bone 3FFE prefixes, of any size/length, are to be used on the Internet in any form. Note that on June 6, 2006 3FFE prefixes do not actively need to be returned to the 6bone registry; 3FFE prefixes will simply be invalid after that date and assumed to be totally under the control of the IANA. Network operators may filter 3FFE prefixes on their borders to ensure these prefixes are not misused. Please take appropriate action now. Again, thanks to everyone who has been involved with the 6bone; you are great! Regards, Bob Fink From jordi.palet at consulintel.es Tue Jun 6 11:39:22 2006 From: jordi.palet at consulintel.es (JORDI PALET MARTINEZ) Date: Tue, 06 Jun 2006 20:39:22 +0200 Subject: [6bone] Good signs Message-ID: http://slashdot.org/comments.pl?sid=187606&threshold=1&commentsort=0&mode=th read&cid=15478052 Regards, Jordi ********************************************** The IPv6 Portal: http://www.ipv6tf.org Barcelona 2005 Global IPv6 Summit Slides available at: http://www.ipv6-es.com This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited. From dr at cluenet.de Tue Jun 6 12:22:17 2006 From: dr at cluenet.de (Daniel Roesen) Date: Tue, 6 Jun 2006 21:22:17 +0200 Subject: [6bone] Good signs In-Reply-To: References: Message-ID: <20060606192217.GA15923@srv01.cluenet.de> On Tue, Jun 06, 2006 at 08:39:22PM +0200, JORDI PALET MARTINEZ wrote: > http://slashdot.org/comments.pl?sid=187606&threshold=1&commentsort=0&mode=thread&cid=15478052 What is good about routing changing to a less optimal path? trace #1 shows a direct Abilene<->WIDE peering, where trace #2 shows a detour via ES.net. The hop #15 in trace #1 is just the peering LAN of LAAP (which is still in 6bone space, they don't get it that they should have renumbered long ago). So in this example, routing got worse, and I seriously doubt it is because the LAAP was running on 6bone IP address space. Regards, Daniel -- CLUE-RIPE -- Jabber: dr at cluenet.de -- dr at IRCnet -- PGP: 0xA85C8AA0 From kato at wide.ad.jp Tue Jun 6 13:33:15 2006 From: kato at wide.ad.jp (Akira Kato) Date: Wed, 07 Jun 2006 05:33:15 +0900 (JST) Subject: [6bone] Good signs In-Reply-To: <20060606192217.GA15923@srv01.cluenet.de> References: <20060606192217.GA15923@srv01.cluenet.de> Message-ID: <20060607.053315.08320661.kato@wide.ad.jp> > The hop #15 in trace #1 is just the peering LAN of LAAP (which is still > in 6bone space, they don't get it that they should have renumbered long > ago). For honor of LAAP, it has already provided production address for the IX fabric since many months ago. The 3ffe:80a::/32 still in use is PAIX/Palo Alto. Mark Prior from AARNET wrote at least a couple of times to PAIX to provide non-6bone space but I don't think he got a response. The peering with Abilene over PAIX/Palo Alto has been established for more than 10 days. So the main reason of the route change was not due to a fact that the peering still uses 6bone space. A couple of Abilene routers (SNVA and DNVR) still uses the route via PAIX/Palo Alto to reach us while other routers pick routes based on their own preferences. While the number of the hops increased, the RTT doesn't change a lot (313ms vs 309ms -- average of the three measurements). -- Akira Kato, WIDE Project From hank at efes.iucc.ac.il Tue Jun 6 14:29:01 2006 From: hank at efes.iucc.ac.il (Hank Nussbacher) Date: Wed, 7 Jun 2006 00:29:01 +0300 (IDT) Subject: [6bone] A list of 3FFEs still in the routing tables Message-ID: http://www.cidr-report.org/v6/#Bogons -Hank From pim at ipng.nl Tue Jun 6 14:42:48 2006 From: pim at ipng.nl (Pim van Pelt) Date: Tue, 6 Jun 2006 23:42:48 +0200 Subject: [6bone] A list of 3FFEs still in the routing tables In-Reply-To: References: Message-ID: <20060606214248.GL22619@bfib.ipng.nl> Hoi Hank, On Wed, Jun 07, 2006 at 12:29:01AM +0300, Hank Nussbacher wrote: | http://www.cidr-report.org/v6/#Bogons Thanks for the link. Another view can be found from SixXS' GRH project: http://www.sixxs.net/tools/grh/dfp/6bone/ -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pim at ipng.nl http://www.ipng.nl/ IPv6 Deployment ----------------------------------------------- From dr at cluenet.de Tue Jun 6 15:14:35 2006 From: dr at cluenet.de (Daniel Roesen) Date: Wed, 7 Jun 2006 00:14:35 +0200 Subject: [6bone] A list of 3FFEs still in the routing tables In-Reply-To: References: Message-ID: <20060606221435.GA18078@srv01.cluenet.de> On Wed, Jun 07, 2006 at 12:29:01AM +0300, Hank Nussbacher wrote: > http://www.cidr-report.org/v6/#Bogons A more complete picture: http://www.sixxs.net/tools/grh/lg/?prefix=3ffe::/16&show=best Best regards, Daniel -- CLUE-RIPE -- Jabber: dr at cluenet.de -- dr at IRCnet -- PGP: 0xA85C8AA0 From jkintree at swbell.net Wed Jun 7 08:11:36 2006 From: jkintree at swbell.net (John Kintree) Date: Wed, 7 Jun 2006 10:11:36 -0500 Subject: [6bone] Good signs In-Reply-To: References: Message-ID: <200606071011.36755.jkintree@swbell.net> On Tuesday 06 June 2006 01:39 pm, JORDI PALET MARTINEZ wrote: > http://slashdot.org/comments.pl?sid=187606&threshold=1&commentsort=0&mode=t >h read&cid=15478052 Another good sign is that the Developers Program page at the $100 laptop web site includes as one of its goals: * IPv6 support, and service discovery, which are very important to us. http://wiki.laptop.org/index.php/Developers_Program John From henk at ripe.net Wed Jun 7 10:08:24 2006 From: henk at ripe.net (Henk Uijterwaal) Date: Wed, 07 Jun 2006 19:08:24 +0200 Subject: [6bone] A list of 3FFEs still in the routing tables In-Reply-To: <20060606214248.GL22619@bfib.ipng.nl> References: <20060606214248.GL22619@bfib.ipng.nl> Message-ID: <7.0.1.0.2.20060607190613.033ff680@ripe.net> At 23:42 06/06/2006, Pim van Pelt wrote: >Hoi Hank, > >On Wed, Jun 07, 2006 at 12:29:01AM +0300, Hank Nussbacher wrote: >| http://www.cidr-report.org/v6/#Bogons >Thanks for the link. Another view can be found from SixXS' GRH project: > >http://www.sixxs.net/tools/grh/dfp/6bone/ Our view, from the RIB's: AS Prefix #peers 4555 3ffe::/24 22 29216 3ffe:3::/48 19 16838 3ffe:4::/48 5 3263 3ffe:100::/24 22 2527 3ffe:50f::/32 5 293 3ffe:700::/24 22 4555 3ffe:800::/24 8 5609 3ffe:1000::/24 22 33 3ffe:1200::/24 22 3582 3ffe:1500::/24 22 7610 3ffe:1600::/24 22 3 3ffe:1ce1::/32 5 3322 3ffe:1f80::/32 19 145 3ffe:2800::/24 22 195 3ffe:2807::/32 2 6175 3ffe:2900::/24 21 6175 3ffe:290a::/32 5 3748 3ffe:2e00::/24 22 17715 3ffe:3600::/24 22 3597 3ffe:8070:1019::/48 5 12199 3ffe:8090::/28 23 25336 3ffe:80e0::/28 17 8954 3ffe:8110::/28 23 7660 3ffe:8140::/28 22 10013 3ffe:8200::/28 26 7671 3ffe:8250::/28 23 20834 3ffe:8270::/28 30 17965 3ffe:8330::/28 22 This list is available with a whois client and whois -h riswhois.ripe.net -F -M 3ffe::/16 For a longer list, use whois -h riswhois.ripe.net -M 3ffe::/16 Henk ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ 1160438400. Watch this space... From Bradley at NorthTech.US Thu Jun 8 17:28:33 2006 From: Bradley at NorthTech.US (Bradley D. Thornton) Date: Thu, 08 Jun 2006 17:28:33 -0700 Subject: [6bone] 6bone is PHASED OUT !! Thanks to all who have worked on the 6bone. In-Reply-To: <2a8350a60606060842x27209bb8w749c51f59eeb6e54@mail.gmail.com> References: <2a8350a60606060842x27209bb8w749c51f59eeb6e54@mail.gmail.com> Message-ID: <4488C0B1.6040301@NorthTech.US> And thank you Bob :) It's been a great ten years, watching my daughter go from conception to 4th grade, if that puts any perspective on things. Hope you and your wife are lovin' your new home in the hills Bob! Kindest regards, Bradley. Robert Fink wrote: > 6bone Operators & Users, > > Today is the day! The 6bone is phased out. > > I would like to thank everyone who has participated in the 6bone > during the last 10 years. > > === > Per RFC 3701, "6bone (IPv6 Testing Address Allocation) Phaseout ", 3FFE > prefixes only remains valid until TODAY, June 6, 2006. > > After TODAY, June 6, 2006, no 6bone 3FFE prefixes, of any size/length, are to > be used on the Internet in any form. > > Note that on June 6, 2006 3FFE prefixes do not actively need to be > returned to the 6bone registry; 3FFE prefixes will simply be invalid > after that date and assumed to be totally under the control of the > IANA. > > Network operators may filter 3FFE prefixes on their borders to ensure > these prefixes are not misused. > > Please take appropriate action now. > > Again, thanks to everyone who has been involved with the 6bone; you are great! > > > Regards, > > Bob Fink > _______________________________________________ > 6bone mailing list > 6bone at mailman.isi.edu > http://mailman.isi.edu/mailman/listinfo/6bone > > > > -- Kindest regards, Bradley D. Thornton Manager Network Services NorthTech Computer +1.949.310.3505 http://NorthTech.US mailto:Bradley at NorthTech.US From bob at thefinks.com Thu Jun 8 17:35:08 2006 From: bob at thefinks.com (Robert Fink) Date: Thu, 8 Jun 2006 17:35:08 -0700 Subject: [6bone] return of 3FFE IPv6 address block per RFC 3701 Message-ID: <2a8350a60606081735i325ab8e5p794547d643936702@mail.gmail.com> Dear IANA, Per RFC 3701, "6bone (IPv6 Testing Address Allocation) Phaseout", the 6bone IPv6 Testbed network has been phased out as of the 6th of June 2006. Therefore, also per RFC 3701, the 3FFE::/16 prefix allocated by RFC 2471 for IPv6 testing, can now be reclaimed by the IANA. To the best of my knowledge, 6bone operators are making active efforts to stop further usage of the 3FFE prefix, and to filter where relevant and necessary. Let us hope they are successful. I hope we have honored our commitments to Jon Postel, who helped to make the 6bone possible. Long may his memory live! Regards, Bob Fink past project lead for the 6bone === >From RFC 3701: 6. IANA Considerations This document defines a phaseout plan for the usage of the IPv6 Testing Address Allocation [TEST-NEW]. The IANA MUST reclaim the 3FFE::/16 prefix upon the date specified in section 2.0. When the 6bone Testing Address Allocation is reclaimed by the IANA, it is expected that many network operators will filter it on their borders to ensure these prefixes are not misused. There is experience from the IPv4 world that such filters may not be removed promptly should this address space be reallocated, and it is recommended that the IANA bears this in mind before reallocating it in a manner that would require it to be routed globally within the current Internet. -end From henk at ripe.net Mon Jun 12 01:49:01 2006 From: henk at ripe.net (Henk Uijterwaal) Date: Mon, 12 Jun 2006 10:49:01 +0200 Subject: [6bone] A list of 3FFEs still in the routing tables In-Reply-To: <7.0.1.0.2.20060607190613.033ff680@ripe.net> References: <20060606214248.GL22619@bfib.ipng.nl> <7.0.1.0.2.20060607190613.033ff680@ripe.net> Message-ID: <7.0.1.0.2.20060612104631.00adb2a8@ripe.net> At 19:08 07/06/2006, Henk Uijterwaal wrote: >At 23:42 06/06/2006, Pim van Pelt wrote: >>Hoi Hank, >> >>On Wed, Jun 07, 2006 at 12:29:01AM +0300, Hank Nussbacher wrote: >>| http://www.cidr-report.org/v6/#Bogons >>Thanks for the link. Another view can be found from SixXS' GRH project: >> >>http://www.sixxs.net/tools/grh/dfp/6bone/ > >Our view, from the RIB's: 6 prefixes have disappeared but we still see 23 of them: 7/6/2006 12/6/2006 AS Prefix # peers # peers 4555 3ffe::/24 22 10 29216 3ffe:3::/48 19 18 16838 3ffe:4::/48 5 5 3263 3ffe:100::/24 22 10 2527 3ffe:50f::/32 5 5 293 3ffe:700::/24 22 10 4555 3ffe:800::/24 8 9 5609 3ffe:1000::/24 22 -- (GONE) 33 3ffe:1200::/24 22 -- (GONE) 3582 3ffe:1500::/24 22 10 7610 3ffe:1600::/24 22 10 3 3ffe:1ce1::/32 5 5 3322 3ffe:1f80::/32 19 18 145 3ffe:2800::/24 22 -- (GONE) 195 3ffe:2807::/32 2 2 6175 3ffe:2900::/24 21 -- (GONE) 6175 3ffe:290a::/32 5 5 3748 3ffe:2e00::/24 22 10 17715 3ffe:3600::/24 22 10 3597 3ffe:8070:1019::/48 5 5 12199 3ffe:8090::/28 23 -- (GONE) 25336 3ffe:80e0::/28 17 14 8954 3ffe:8110::/28 23 17 7660 3ffe:8140::/28 22 10 10013 3ffe:8200::/28 26 19 6342 3ffe:8240::/28 -- 10 7671 3ffe:8250::/28 23 -- (GONE) 20834 3ffe:8270::/28 30 27 17965 3ffe:8330::/28 22 10 Henk ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ 1160438400. Watch this space... From pim at ipng.nl Mon Jun 12 01:56:38 2006 From: pim at ipng.nl (Pim van Pelt) Date: Mon, 12 Jun 2006 10:56:38 +0200 Subject: [6bone] A list of 3FFEs still in the routing tables In-Reply-To: <7.0.1.0.2.20060612104631.00adb2a8@ripe.net> References: <20060606214248.GL22619@bfib.ipng.nl> <7.0.1.0.2.20060607190613.033ff680@ripe.net> <7.0.1.0.2.20060612104631.00adb2a8@ripe.net> Message-ID: <20060612085637.GD25568@bfib.ipng.nl> On Mon, Jun 12, 2006 at 10:49:01AM +0200, Henk Uijterwaal wrote: | 6 prefixes have disappeared but we still see 23 of them: | SixXS sees 19 prefixes today. Note that this was approximately 80 just before 6/6/2006, so I think we are making good progress. I have been asking my IPv6 transitprovider (GLBX) to update their filtering, because they are still sending us 3ffe::/16 prefixes. If there are any other GLBX IPv6 customers on this list, it would help if you could contact them with a similar request. I have contact details if you need them (contact me offlist in that case). -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pim at ipng.nl http://www.ipng.nl/ IPv6 Deployment ----------------------------------------------- From hank at efes.iucc.ac.il Mon Jun 12 02:37:33 2006 From: hank at efes.iucc.ac.il (Hank Nussbacher) Date: Mon, 12 Jun 2006 12:37:33 +0300 Subject: [6bone] A list of 3FFEs still in the routing tables In-Reply-To: <20060612085637.GD25568@bfib.ipng.nl> References: <7.0.1.0.2.20060612104631.00adb2a8@ripe.net> <20060606214248.GL22619@bfib.ipng.nl> <7.0.1.0.2.20060607190613.033ff680@ripe.net> <7.0.1.0.2.20060612104631.00adb2a8@ripe.net> Message-ID: <5.1.0.14.2.20060612123522.00ad3588@efes.iucc.ac.il> At 10:56 AM 12-06-06 +0200, Pim van Pelt wrote: >On Mon, Jun 12, 2006 at 10:49:01AM +0200, Henk Uijterwaal wrote: >| 6 prefixes have disappeared but we still see 23 of them: >| >SixXS sees 19 prefixes today. Note that this was approximately 80 just >before 6/6/2006, so I think we are making good progress. I have sent out another 7 targetted notices today for ASNs: 3582, 4555, 29216, 16838, 3263, 3, and 293. -Hank >I have been asking my IPv6 transitprovider (GLBX) to update their >filtering, because they are still sending us 3ffe::/16 prefixes. If there >are any other GLBX IPv6 customers on this list, it would help if you could >contact them with a similar request. I have contact details if you need >them (contact me offlist in that case). >-- >---------- - - - - -+- - - - - ---------- >Pim van Pelt Email: pim at ipng.nl >http://www.ipng.nl/ IPv6 Deployment >----------------------------------------------- > > +++++++++++++++++++++++++++++++++++++++++++ > This Mail Was Scanned By Mail-seCure System > at the Tel-Aviv University CC. From dr at cluenet.de Mon Jun 12 05:05:42 2006 From: dr at cluenet.de (Daniel Roesen) Date: Mon, 12 Jun 2006 14:05:42 +0200 Subject: [6bone] A list of 3FFEs still in the routing tables In-Reply-To: <5.1.0.14.2.20060612123522.00ad3588@efes.iucc.ac.il> References: <7.0.1.0.2.20060612104631.00adb2a8@ripe.net> <20060606214248.GL22619@bfib.ipng.nl> <7.0.1.0.2.20060607190613.033ff680@ripe.net> <7.0.1.0.2.20060612104631.00adb2a8@ripe.net> <5.1.0.14.2.20060612123522.00ad3588@efes.iucc.ac.il> Message-ID: <20060612120542.GA1633@srv01.cluenet.de> On Mon, Jun 12, 2006 at 12:37:33PM +0300, Hank Nussbacher wrote: > I have sent out another 7 targetted notices today for ASNs: > 3582, 4555, 29216, 16838, 3263, 3, and 293. 4555 has already announced to continue advertising the (now bogon) route. He can't let go. Could someone finally remove ip6.int now so we don't have to further suffer from this 4555 show? The opinion of the ops community at large is crystal-clear. Hank, thanks for your efforts! Regards, Daniel -- CLUE-RIPE -- Jabber: dr at cluenet.de -- dr at IRCnet -- PGP: 0xA85C8AA0 From tvo at enterzone.net Mon Jun 12 05:05:47 2006 From: tvo at enterzone.net (John Fraizer) Date: Mon, 12 Jun 2006 08:05:47 -0400 Subject: [6bone] A list of 3FFEs still in the routing tables In-Reply-To: <20060612085637.GD25568@bfib.ipng.nl> References: <20060606214248.GL22619@bfib.ipng.nl> <7.0.1.0.2.20060607190613.033ff680@ripe.net> <7.0.1.0.2.20060612104631.00adb2a8@ripe.net> <20060612085637.GD25568@bfib.ipng.nl> Message-ID: <448D589B.3010404@enterzone.net> Pim van Pelt wrote: > On Mon, Jun 12, 2006 at 10:49:01AM +0200, Henk Uijterwaal wrote: > | 6 prefixes have disappeared but we still see 23 of them: > | > SixXS sees 19 prefixes today. Note that this was approximately 80 just > before 6/6/2006, so I think we are making good progress. > > I have been asking my IPv6 transitprovider (GLBX) to update their > filtering, because they are still sending us 3ffe::/16 prefixes. If there > are any other GLBX IPv6 customers on this list, it would help if you could > contact them with a similar request. I have contact details if you need > them (contact me offlist in that case). Do you really want your provider to filter the 3ffe::/16 prefixes right now? It will make the offending prefixes dissappear from YOUR view but, it won't make them go away. Unless EVERYONE filters 3ffe::/16 as BOGON prefixes, we need to be able to see who is actually announcing those prefixes. We're seeing 15 prefixes right now: Border2-BGP> sh bgp 3ffe::/16 longer-prefixes BGP table version is 0, local router ID is 66.35.95.2 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 3ffe::/24 2001:4f0:1001:1::2 0 0 4555 i *> 3ffe:100::/24 2001:4f0:1001:1::2 0 4555 6939 6939 3263 i *> 3ffe:700::/24 2001:4f0:1001:1::2 0 4555 6939 4725 2915 2713 293 i *> 3ffe:800::/24 2001:4f0:1001:1::2 0 0 4555 i *> 3ffe:1500::/24 2001:4f0:1001:1::2 0 4555 3582 i *> 3ffe:1600::/24 2001:4f0:1001:1::2 0 4555 6939 6939 2042 7610 i *> 3ffe:2e00::/24 2001:4f0:1001:1::2 0 4555 6939 6939 3748 i *> 3ffe:3600::/24 2001:4f0:1001:1::2 0 4555 6939 4725 17715 i *> 3ffe:80e0::/28 2001:4f0:1001:1::2 0 4555 6939 2516 7660 7684 18084 3257 25336 i *> 3ffe:8110::/28 2001:4f0:1001:1::2 0 4555 6939 2516 7660 7684 18084 3257 8954 i *> 3ffe:8140::/28 2001:4f0:1001:1::2 0 4555 6939 2516 7660 i *> 3ffe:8200::/28 2001:4f0:1001:1::2 0 4555 6939 4716 10013 i *> 3ffe:8240::/28 2001:4f0:1001:1::2 0 4555 6939 6939 278 6342 i *> 3ffe:8270::/28 2001:4f0:1001:1::2 0 4555 6939 3257 20834 i *> 3ffe:8330::/28 2001:4f0:1001:1::2 0 4555 6939 6939 2042 17965 i Total number of prefixes 15 On a different note, I've attempted to contact the following ASNs to move our peering sessions over to RIR address space. No reply thus far: 6175 - SPRINT 8002 - Stealth Communications 6939 - Hurricane Electric If you have enable on one of those ASNs, please contact me off-list so we can move the peering session and get the 3ffe::/16 addresses out of the path. John Fraizer AS13944 From kloch at hotnic.net Mon Jun 12 07:06:06 2006 From: kloch at hotnic.net (Kevin Loch) Date: Mon, 12 Jun 2006 10:06:06 -0400 Subject: [6bone] A list of 3FFEs still in the routing tables In-Reply-To: <20060612120542.GA1633@srv01.cluenet.de> References: <7.0.1.0.2.20060612104631.00adb2a8@ripe.net> <20060606214248.GL22619@bfib.ipng.nl> <7.0.1.0.2.20060607190613.033ff680@ripe.net> <7.0.1.0.2.20060612104631.00adb2a8@ripe.net> <5.1.0.14.2.20060612123522.00ad3588@efes.iucc.ac.il> <20060612120542.GA1633@srv01.cluenet.de> Message-ID: <448D74CE.4060502@hotnic.net> Daniel Roesen wrote: > On Mon, Jun 12, 2006 at 12:37:33PM +0300, Hank Nussbacher wrote: > >>I have sent out another 7 targetted notices today for ASNs: >>3582, 4555, 29216, 16838, 3263, 3, and 293. Here is a list of AS's appearing one space to the left of those still announcing 3ffe::/16 prefixes from my view: #routes AS 6 3257 3 6939 2 9009 2 8674 2 4725 2 4555 2 278 2 2042 1 4716 1 4275 1 2713 1 2516 1 18084 1 145 1 13944 I think Alexander (3257) said he would wait a short time to give folks who weren't paying attention time to migrate. Hopefully that time will come soon. - Kevin From kloch at hotnic.net Mon Jun 12 07:18:54 2006 From: kloch at hotnic.net (Kevin Loch) Date: Mon, 12 Jun 2006 10:18:54 -0400 Subject: [6bone] return of 3FFE IPv6 address block per RFC 3701 In-Reply-To: <2a8350a60606081735i325ab8e5p794547d643936702@mail.gmail.com> References: <2a8350a60606081735i325ab8e5p794547d643936702@mail.gmail.com> Message-ID: <448D77CE.6010705@hotnic.net> Robert Fink wrote: > Dear IANA, > > Per RFC 3701, "6bone (IPv6 Testing Address Allocation) Phaseout", the > 6bone IPv6 Testbed network has been phased out as of the 6th of June > 2006. > > Therefore, also per RFC 3701, the 3FFE::/16 prefix allocated by RFC > 2471 for IPv6 testing, can now be reclaimed by the IANA. > > To the best of my knowledge, 6bone operators are making active efforts > to stop further usage of the 3FFE prefix, and to filter where relevant > and necessary. Let us hope they are successful. Robert, Thank you for following through on winding this up after many years of operation. I don't know if you are still associated with ESnet, but they are still announcing 3ffe:700::/24. Can you or anyone you know there fix that? All of the paths visible from sixxs are going through 2713, if that helps. - Kevin From bob at thefinks.com Mon Jun 12 08:34:24 2006 From: bob at thefinks.com (Robert Fink) Date: Mon, 12 Jun 2006 08:34:24 -0700 Subject: [6bone] return of 3FFE IPv6 address block per RFC 3701 In-Reply-To: <448D77CE.6010705@hotnic.net> References: <2a8350a60606081735i325ab8e5p794547d643936702@mail.gmail.com> <448D77CE.6010705@hotnic.net> Message-ID: <2a8350a60606120834p14c2ee03p65b4a867a88b127a@mail.gmail.com> Kevin, On 6/12/06, Kevin Loch wrote: > Robert Fink wrote: > > Dear IANA, > > > > Per RFC 3701, "6bone (IPv6 Testing Address Allocation) Phaseout", the > > 6bone IPv6 Testbed network has been phased out as of the 6th of June > > 2006. > > > > Therefore, also per RFC 3701, the 3FFE::/16 prefix allocated by RFC > > 2471 for IPv6 testing, can now be reclaimed by the IANA. > > > > To the best of my knowledge, 6bone operators are making active efforts > > to stop further usage of the 3FFE prefix, and to filter where relevant > > and necessary. Let us hope they are successful. > > Robert, > > Thank you for following through on winding this up after many years of > operation. I don't know if you are still associated with ESnet, > but they are still announcing 3ffe:700::/24. Can you or anyone > you know there fix that? > > All of the paths visible from sixxs are going through 2713, if that > helps. I'll get in touch with the ESnet folk and get them to take it down. Thanks, Bob From yhines at es.net Mon Jun 12 09:14:24 2006 From: yhines at es.net (Yvonne Hines) Date: Mon, 12 Jun 2006 09:14:24 -0700 Subject: [6bone] return of 3FFE IPv6 address block per RFC 3701 In-Reply-To: <448D77CE.6010705@hotnic.net> References: <2a8350a60606081735i325ab8e5p794547d643936702@mail.gmail.com> <448D77CE.6010705@hotnic.net> Message-ID: <20060612161424.B09AE3F5B6@blueskies.es.net> Hello Kevin, All though it may look as if ESnet is announcing 3FFE:700::/24 to as2713. ESnet is only announcing 2001:400::/32. I will be contacting as2713 to work with them to remove the 3ffe:700::/24 announcment. The SixXS Ghost Route Hunter is identifying 3FFE:700::/24 as a ghost route since 2006 06 07 22:17 https://noc.sixxs.net/tools/grh/ghosts/ Regards, Yvonne Hines ESnet > Robert Fink wrote: > > Dear IANA, > > > > Per RFC 3701, "6bone (IPv6 Testing Address Allocation) Phaseout", the > > 6bone IPv6 Testbed network has been phased out as of the 6th of June > > 2006. > > > > Therefore, also per RFC 3701, the 3FFE::/16 prefix allocated by RFC > > 2471 for IPv6 testing, can now be reclaimed by the IANA. > > > > To the best of my knowledge, 6bone operators are making active efforts > > to stop further usage of the 3FFE prefix, and to filter where relevant > > and necessary. Let us hope they are successful. > > Robert, > > Thank you for following through on winding this up after many years of > operation. I don't know if you are still associated with ESnet, > but they are still announcing 3ffe:700::/24. Can you or anyone > you know there fix that? > > All of the paths visible from sixxs are going through 2713, if that > helps. > > - Kevin > _______________________________________________ > 6bone mailing list > 6bone at mailman.isi.edu > http://mailman.isi.edu/mailman/listinfo/6bone > From dr at cluenet.de Mon Jun 12 10:42:06 2006 From: dr at cluenet.de (Daniel Roesen) Date: Mon, 12 Jun 2006 19:42:06 +0200 Subject: [6bone] return of 3FFE IPv6 address block per RFC 3701 In-Reply-To: <20060612161424.B09AE3F5B6@blueskies.es.net> References: <2a8350a60606081735i325ab8e5p794547d643936702@mail.gmail.com> <448D77CE.6010705@hotnic.net> <20060612161424.B09AE3F5B6@blueskies.es.net> Message-ID: <20060612174206.GA8180@srv01.cluenet.de> On Mon, Jun 12, 2006 at 09:14:24AM -0700, Yvonne Hines wrote: > All though it may look as if ESnet is announcing 3FFE:700::/24 to as2713. > ESnet is only announcing 2001:400::/32. I will be contacting as2713 to > work with them to remove the 3ffe:700::/24 announcment. > > The SixXS Ghost Route Hunter is identifying > 3FFE:700::/24 as a ghost route since 2006 06 07 22:17 Jup, it's one of those ASses ghosting the route: 2713 AT&T Jens 2915 AT&T Jens 4725 Japan Telecom/ODN Best regards, Daniel -- CLUE-RIPE -- Jabber: dr at cluenet.de -- dr at IRCnet -- PGP: 0xA85C8AA0 From raeburn at MIT.EDU Mon Jun 12 12:31:40 2006 From: raeburn at MIT.EDU (Ken Raeburn) Date: Mon, 12 Jun 2006 15:31:40 -0400 Subject: [6bone] A list of 3FFEs still in the routing tables In-Reply-To: <5.1.0.14.2.20060612123522.00ad3588@efes.iucc.ac.il> References: <7.0.1.0.2.20060612104631.00adb2a8@ripe.net> <20060606214248.GL22619@bfib.ipng.nl> <7.0.1.0.2.20060607190613.033ff680@ripe.net> <7.0.1.0.2.20060612104631.00adb2a8@ripe.net> <5.1.0.14.2.20060612123522.00ad3588@efes.iucc.ac.il> Message-ID: <02389E9A-B75F-4F7B-8AB3-656056F0EACF@mit.edu> On Jun 12, 2006, at 05:37, Hank Nussbacher wrote: > At 10:56 AM 12-06-06 +0200, Pim van Pelt wrote: >> On Mon, Jun 12, 2006 at 10:49:01AM +0200, Henk Uijterwaal wrote: >> | 6 prefixes have disappeared but we still see 23 of them: >> | >> SixXS sees 19 prefixes today. Note that this was approximately 80 >> just >> before 6/6/2006, so I think we are making good progress. > > I have sent out another 7 targetted notices today for ASNs: > 3582, 4555, 29216, 16838, 3263, 3, and 293. > > -Hank By "targetted notices" I assume you mean email directly to responsible people listed for the ASN, not those in the 6bone registry? In MIT's case, that's two non-overlapping sets of people, and I'm in the latter set. As far as I can tell, we at MIT (AS 3) have stopped advertising 3ffe: 1ce1::/32 as of a few days ago (not 6/6/6, but soon after). Just to be sure, I took down our end of our old 6bone tunnel to MCI and the BGP association about nine hours ago, in case they're still accepting and passing 6bone routes and I'm misreading my config file. Yet the looking glass at sixxs is still showing me it's receiving a path via Hurricane Electric and MCI (and a bunch of sites in between), directly from HE and via other sites. I'll track down the MCI contact address and ask if maybe they're advertising a route for us rather than passing on our advertisement if/when we send it to them... Ken From gert at space.net Mon Jun 12 13:50:37 2006 From: gert at space.net (Gert Doering) Date: Mon, 12 Jun 2006 22:50:37 +0200 Subject: [6bone] A list of 3FFEs still in the routing tables In-Reply-To: <02389E9A-B75F-4F7B-8AB3-656056F0EACF@mit.edu> References: <7.0.1.0.2.20060612104631.00adb2a8@ripe.net> <20060606214248.GL22619@bfib.ipng.nl> <7.0.1.0.2.20060607190613.033ff680@ripe.net> <7.0.1.0.2.20060612104631.00adb2a8@ripe.net> <5.1.0.14.2.20060612123522.00ad3588@efes.iucc.ac.il> <02389E9A-B75F-4F7B-8AB3-656056F0EACF@mit.edu> Message-ID: <20060612205037.GF53070@Space.Net> Hi, On Mon, Jun 12, 2006 at 03:31:40PM -0400, Ken Raeburn wrote: > As far as I can tell, we at MIT (AS 3) have stopped advertising 3ffe: > 1ce1::/32 as of a few days ago (not 6/6/6, but soon after). Just to > be sure, I took down our end of our old 6bone tunnel to MCI and the > BGP association about nine hours ago, in case they're still accepting > and passing 6bone routes and I'm misreading my config file. Yet the > looking glass at sixxs is still showing me it's receiving a path via > Hurricane Electric and MCI (and a bunch of sites in between), > directly from HE and via other sites. Chances are that this is a so-called "ghost route" - the originator has withdrawn it, but somewhere on the path, there's a buggy BGP speaker that has removed it from its own tables, but omitted to actually send out the withdrawal. Nobody currently seems to really *know* what's triggering it, which is why it's sort of hard to make the offending vendor fix it. Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 92315 SpaceNet AG Mail: netmaster at Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 D- 80807 Muenchen Fax : +49-89-32356-234 From hank at efes.iucc.ac.il Mon Jun 12 21:30:18 2006 From: hank at efes.iucc.ac.il (Hank Nussbacher) Date: Tue, 13 Jun 2006 07:30:18 +0300 (IDT) Subject: [6bone] A list of 3FFEs still in the routing tables In-Reply-To: <02389E9A-B75F-4F7B-8AB3-656056F0EACF@mit.edu> References: <7.0.1.0.2.20060612104631.00adb2a8@ripe.net> <20060606214248.GL22619@bfib.ipng.nl> <7.0.1.0.2.20060607190613.033ff680@ripe.net> <7.0.1.0.2.20060612104631.00adb2a8@ripe.net> <5.1.0.14.2.20060612123522.00ad3588@efes.iucc.ac.il> <02389E9A-B75F-4F7B-8AB3-656056F0EACF@mit.edu> Message-ID: On Mon, 12 Jun 2006, Ken Raeburn wrote: > > I have sent out another 7 targetted notices today for ASNs: > > 3582, 4555, 29216, 16838, 3263, 3, and 293. > > > > -Hank > > By "targetted notices" I assume you mean email directly to > responsible people listed for the ASN, not those in the 6bone > registry? In MIT's case, that's two non-overlapping sets of people, > and I'm in the latter set. I sent out an email yesterday to the 2 ARIN whois people for AS3. Thanks for your help as well. -Hank From henk at ripe.net Mon Jun 19 02:39:36 2006 From: henk at ripe.net (Henk Uijterwaal) Date: Mon, 19 Jun 2006 11:39:36 +0200 Subject: [6bone] A list of 3FFEs still in the routing tables In-Reply-To: <7.0.1.0.2.20060612104631.00adb2a8@ripe.net> References: <20060606214248.GL22619@bfib.ipng.nl> <7.0.1.0.2.20060607190613.033ff680@ripe.net> <7.0.1.0.2.20060612104631.00adb2a8@ripe.net> Message-ID: <7.0.1.0.2.20060619113357.03488590@ripe.net> Today's view: > 7/6/2006 12/6/2006 18/6/2006 >AS Prefix # peers # peers #peers >4555 3ffe::/24 22 10 9 >29216 3ffe:3::/48 19 18 -- GONE >16838 3ffe:4::/48 5 5 -- GONE >3263 3ffe:100::/24 22 10 9 >2527 3ffe:50f::/32 5 5 5 >293 3ffe:700::/24 22 10 9 >4555 3ffe:800::/24 8 9 6 >5609 3ffe:1000::/24 22 -- -- >33 3ffe:1200::/24 22 -- -- >3582 3ffe:1500::/24 22 10 -- GONE >7610 3ffe:1600::/24 22 10 -- GONE >3 3ffe:1ce1::/32 5 5 -- GONE >3322 3ffe:1f80::/32 19 18 -- GONE >145 3ffe:2800::/24 22 -- -- >195 3ffe:2807::/32 2 2 2 >6175 3ffe:2900::/24 21 -- -- >6175 3ffe:290a::/32 5 5 -- GONE >3748 3ffe:2e00::/24 22 10 9 >17715 3ffe:3600::/24 22 10 9 >3597 3ffe:8070:1019::/48 5 5 -- GONE >12199 3ffe:8090::/28 23 -- -- >25336 3ffe:80e0::/28 17 14 -- GONE >8954 3ffe:8110::/28 23 17 14 >7660 3ffe:8140::/28 22 10 10 >10013 3ffe:8200::/28 26 19 -- GONE >6342 3ffe:8240::/28 -- 10 9 >7671 3ffe:8250::/28 23 -- -- >20834 3ffe:8270::/28 30 27 26 >17965 3ffe:8330::/28 22 10 -- GONE Henk ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ 1160438400. Watch this space...