link-local addresses are traversing

[Bao Phan]

> The following is the result of "traceroute6" from the University of
> New Hampshire to WIDE project.
> 
> lobster# traceroute6 bravo.v6.wide.ad.jp
> traceroute to bravo.v6.wide.ad.jp (5f09:c400:a3dd:ca00::f801:5df5), 30 hops ma
x, 60 byte packets
>  1  5f02:3000:84b1:7e80:: (5f02:3000:84b1:7e80::)  1.908 ms  1.824 ms  1.772 m
s
>  2  fe80::cc7b:2ec (fe80::cc7b:2ec)  103.54 ms  99.682 ms  120.378 ms
>  3  6bone-router.cisco.inner.net (5f00:6d00:c01f:700:1:60:3e11:6770)  347.197 
ms *  274.7 ms
>  4  esnet-v6r1.es.net (::198.128.2.27)  281.609 ms  251.368 ms  253.379 ms
>  5  6bone-router.cisco.inner.net (5f00:6d00:c01f:700:1:60:3e11:6770)  248.65 m
s
> 
> First, I would like to ask each maintainer to make your router not to
> select a link-local source address for a global destination. According
> to the 6bone map, fe80::cc7b:2ec is NRL/US(one between UNH/US and
> IBM/US).
 
fe80::cc7b:2ec does not belong to NRL/US.  This link-local address appears to
be from DIGITAL-CA/US (pax-6bone.pa-x.dec.com/204.123.2.236).  A traceroute
to the host yields:

# ./traceroute ::204.123.2.236
traceroute to ::204.123.2.236 (::204.123.2.236), 30 hops max, 16 byte packets
 1  fe80::cc7b:2ec (fe80::cc7b:2ec)  222.196 ms  78.362 ms  84.14 ms

I have seen packets with link-local source address forwarded on the 6bone
on a number of occasions.  Do most implementations forward such packets
despite what the specs say?