[OCCAID] routing

[Jeroen Massar]

R Dicaire wrote:
> Hi folks...my IPv6 tunnel's been down for a while, is there an ongoing
> issue?
> My remote IPv4 endpoint is 69.72.192.235, thanks in advance.

It's traceable over IPv4, but not over IPv6. Can you ping6 the endpoint
of the tunnel or is it already broken on IPv4?

IPv6 trace seems to indicate that the network behind it is not
reachable. But I assume that you normally announce it per BGP and then
that would make sense.


Which leads me to ask a general question on this subject. I dunno if it
could be done and what OCCAID folks would think of it, it is their
network after all, but:

What if the various SixXS PoPs would have a BGP listener&speaker. Folks
could then request one or multiple tunnels to the various PoPs, as
OCCAID has multiple, and then announce their own prefix toward the PoP.
If tunnel fails, one fails over their prefix automagically to another
tunnel. The PoP would only announce a single default route though, maybe
more specifics could be done also optionally.

The PoP speaks BGP upstream to the OCCAID backbone, announcing the
prefixes from the endusers.

Of course only OCCAID prefixes under 2001:4830::/32 would be accepted
for this to keep aggregation easy. Altough, it could be used to also
accept other /48's etc, but mark them no-export towards the rest of the
world.

Note, that I propose this only for PoPs participating in OCCAID, as
those PoPs all fall under the same 30071 ASN. It can't work for other
SixXS PoPs as that would mean that the PoPs would have to backhaul
traffic amongst them, which is inefficient and doesn't solve the case
where the PoP goes down or becomes unreachable in another way.

Anybody comments on this?

Greets,
 Jeroen


--

IPv6 trace to 2001:4830:20D0:0:0:0:0:4 (www.ardynet.com):
...
 5  so-4-0-0-dcr1.tsd.cw.net (2001:5000:0:20::2)  10.219 ms  10.301 ms
9.732 ms
 6  as0-dcr2.tsd.cw.net (2001:5000:0:1d::2)  10.4 ms  16.998 ms  10.141 ms
 7  so-1-0-0-zcr2.lnt.cw.net (2001:5000:0:63::2)  29.419 ms  11.252 ms
9.718 ms
 8  2001:7f8:4:1::31f9:2 (2001:7f8:4:1::31f9:2)  10.585 ms !N  10.626 ms
!N  10.452 ms !N

IPv4 trace:
...
 9  po1.ar1.nyc3.us.nlayer.net (69.31.95.130)  95 ms  94 ms  92 ms
10  tge1-4.ar1.ewr1.us.nlayer.net (69.31.95.157)  95 ms  90 ms  94 ms
11  fortressitx.ge3-23.ar1.ewr1.us.nlayer.net (69.31.95.86)  95 ms  95
ms  94 ms
12  65.98.0.212 (65.98.0.212)  93 ms  92 ms  92 ms
13  69.72.192.235 (69.72.192.235)  96 ms  94 ms  93 ms


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 311 bytes
Desc: OpenPGP digital signature
Url : http://mailman.twdx.net/pipermail/occaid/attachments/20070123/e020ed54/signature.bin