broken routing from ietf due to stale routes..

Bill Sommerfeld sommerfeld@orchard.arlington.ma.us
Wed, 29 Mar 2000 19:35:16 +0930


Pardon the scattershot nature of this..

I was able to get "home" to 3ffe:1ce1::/32 from IETF earlier in the
week but it appears that it's broken at the moment..  

I'm seeing an apparent routing loop:

% traceroute6 hydra.hamachi.org.
traceroute to hydra.hamachi.org (3ffe:1ce1:0:fe01:2a0:ccff:fe3d:86d), 30 hops max, 12 byte packets
 1  2001:210:1:2:2d0:baff:fe0e:5df0  97.407 ms  98.844 ms *
 2  3ffe:b00:c18:502::1  427.993 ms  510.237 ms  507.608 ms
 3  3ffe:b00:c18::11  819.231 ms * *
 4  * * 3ffe:31ff:0:ffff::11  1397.85 ms
 5  * * 3ffe:3600::b  1370.59 ms
 6  3ffe:2100:1:9:0:c46:b898:e  1518.53 ms *  1553.94 ms
 7  pao-6r1-if.6r1.cambridge.ip6.pipex.net  1637.93 ms  1841.65 ms  1640.81 ms
 8  * cisco-if.6r1.paloalto.ip6.pipex.net  1663.44 ms  1636.38 ms
 9  * * *
10  * * *
11  3ffe:b00:c18::11  1882.54 ms *  1743.73 ms
12  3ffe:31ff:0:ffff::11  2349.23 ms * pao-6r1-if.6r1.cambridge.ip6.pipex.net  1972.6 ms
13  * cisco-if.6r1.paloalto.ip6.pipex.net  1956.88 ms *
14  * * *
15  * * 3ffe:1b00:0:ffff::f004  2759.76 ms
16  * * *
17  * * *
18  3ffe:3600::b  3055.94 ms * *
19  3ffe:2100:1:9:0:c46:b898:e  3204.05 ms  2972.77 ms  2872.28 ms
20  * * pao-6r1-if.6r1.cambridge.ip6.pipex.net  2809.26 ms
21  cisco-if.6r1.paloalto.ip6.pipex.net  2784.63 ms * *

3ffe:1ce1::/32 is announced from MIT (AS3) only to MERIT.    

There appear to be a few dozen stale more-specific routes from MERIT
listed in http://carmen.cselt.it/ipv6/bgp/odd-routes2.html,
3ffe:1ce1::/32 being one of them..

The AS path shown in that web page:

	UUNET-UK - UL - RCCN - RNP - CISCO - ISI-LAP - SPACENET-D - SMS -
	AS2839 - TELEBIT - CHTTL-TW - ETRI - JOIN - IPF - CAIRN - MERIT

Anyone in a position to clear these up?  Thanks..

					- Bill