Re: 6bone space used still in the free (www.ietf.org over IPv6 broken) (Was: why same names, was Re: NANOG 40 agenda posted)

2007-06-04 Thread Mike Leber
On Wed, 30 May 2007, Jeroen Massar wrote: > [let me whine again about this one more time... *sigh*] > [guilty parties in cc + public ml's so that every body sees again that > this is being sent to you so that you can't deny it... *sigh again*] Actually appreciated, as the only sessions with 3ffe

Re: 6bone space used still in the free (www.ietf.org over IPv6 broken) (Was: why same names, was Re: NANOG 40 agenda posted)

2007-05-31 Thread Jeroen Massar
The IPv6 connectivity problems, at least the ones that I and some others encountered, where resolved yesterday. Thanks to all the folks involved who made that happen! Mike Leber wrote: [..] > Would you similarly disconnect a nonresponsive customer because they used > a /30 from RFC1918 space on

Re: 6bone space used still in the free (www.ietf.org over IPv6 broken) (Was: why same names, was Re: NANOG 40 agenda posted)

2007-05-30 Thread bmanning
> And what do we see: 6bone space and still in use. > > As a lot of places correctly filter it out, the PMTU's get dropped, as > they are supposed to be dropped. > > The whois.6bone.net registry is fun of course: > > inet6num: 3FFE:800::/24 > netname: ISI-LAP > descr:Harry Try I

RE: 6bone space used still in the free (www.ietf.org over IPv6 broken) (Was: why same names, was Re: NANOG 40 agenda posted)

2007-05-30 Thread James Jun
> > I think what's going on is that packets from www.ietf.org don't make it > > back to my ISP. A ping6 or traceroute6 doesn't show any ICMP errors and > > TCP sessions don't connect so it's not a PMTUD problem. So it's an > > actual timeout. > > I also just started noticing this, that is, that it

Re: [ipv6] 6bone space used still in the free (www.ietf.org over IPv6 broken) (Was: why same names, was Re: NANOG 40 agenda posted)

2007-05-30 Thread Steve Powell
Greetings. I do not believe 6bone space has anything to do with it. 3ffe:80a::/64 is still being used by PAIX in Palo Alto. However, we should be filtering 6bone space. So were only using it until all peers are moved off of 6bone space. Unfortunately, moving those peers and getting rid of our

Re: [ipv6] 6bone space used still in the free (www.ietf.org over IPv6 broken) (Was: why same names, was Re: NANOG 40 agenda posted)

2007-05-30 Thread Jeroen Massar
Steve Powell wrote: > Greetings. Thanks for the quick response. That is always appreciated. Some networks don't even take that decency to respond, and for the record, those are the ones that the previous mail is targeted at, in the hope that they at least maybe acknowledge that there is a problem

6bone space used still in the free (www.ietf.org over IPv6 broken) (Was: why same names, was Re: NANOG 40 agenda posted)

2007-05-30 Thread Jeroen Massar
[let me whine again about this one more time... *sigh*] [guilty parties in cc + public ml's so that every body sees again that this is being sent to you so that you can't deny it... *sigh again*] Iljitsch van Beijnum wrote: > > On 30-mei-2007, at 13:23, Nathan Ward wrote: > >>> I can't seem to r