IETF temporary v6 block?

[Bernhard Schmidt]

Hi Iljitsch,

> Trying to work IPv6-only in Philadelphia, but it's not going stellar. 
> Can someone check if this block makes it everywhere? I'm especially 
> having problem with the SixXS pop in DC.
> 
> inet6num:     2001:0DF8::/32
> netname:      IETF-CONFERENCE-20070223
> descr:        Temporary address allocation for conference connectivity
> country:      AP
> admin-c:      DK501-AP
> tech-c:       DK501-AP
> status:       ALLOCATED PORTABLE
> remarks:      Temporary allocation
> 

According to http://www.sixxs.net/tools/grh/lg/?&find=2001:0df8::/32 the 
connectivity looks mostly fine. There is a C&-"I take everything from my 
downstream Telia and announce it to peerings"W and a Tel"I take a 
fulltable from my downstream CESNET2"ia issue again:

15456 8489 1273 1299 2852 2852 2852 2852 2852 2852 6939 1280 7922 290
15744 13293 1299 2852 2852 2852 2852 2852 2852 6939 1280 7922 290

not that great, but most networks should be unaffected by this.

usqas01 does not seem to use 30071 for their output path though, 
according to 
http://www.sixxs.net/tools/traceroute/?pop=usqas01-6&dpop=other&dest=2001:df8::16:21b:63ff:fe02:3c13 
they go NTT -> Comcast -> IETF. Trace goes quite a distance through 
Comcast network and then dies at 2001:558:0:f707::2, which is the exact 
same result I get from home.

Can you show some more traces which show your exact problem?

Bernhard