[6bone] non-global address space for IXs (was: 2001:478:: as /48)

[Chris Liljenstolpe]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have to disagree here.  Having globally routable address space for each 
hop on a network path is really, really useful for troubleshooting.  We've 
run into issues where folks have used private address space in the v4 
world for "private" portions of the public Internet, and it make 
troubleshooting and operational support very painful.  Please do not go 
down this road in v6.

        Chris

>
> Date: Fri, 05 Sep 2003 00:34:43 +0900 (JST)
> To: bmanning@ISI.EDU
> Cc: 6bone@ISI.EDU
> Subject: Re: [6bone] 2001:478:: as /48
> From: Akira Kato <kato@wide.ad.jp>
>
>
>> this prefix has/is being carved up into /48 and /64 subnets for
>> use at exchange points and other infrastructure support services.
>
>> Do not expect to see it aggregated.
>
> I have a question: do we need to make such a prefix assigned to
> an exchange point reachable globally?
>
> Provided if every ISP uses "next-hop-self" to their I-BGP peering, the
> addresses on an IX is used only for E-BGP peering. What we loose if
> nobody advertises the IX prefix globally (or even locally)?
>
> If the address is not globally reachable, it is impossible to send
> packets to the routers on the IX and this will be a measure for the
> remote DoS attack if not perfect.
>
> In order to make traceroute happy we may need to establish a DNS zone
> for reverse lookup. But such a DNS server does not have to be on the
> IX.
>
> Akira Kato, WIDE Project
> P.S.
> This discussion is also applicable to IPv4...
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (Darwin)

iD8DBQE/V8vFS7vf0lGnolIRAvlkAJ9Ny2z+9EZ1AS72kNkCrMuLITHwKgCeIen/
x0drb783a7AHCpEAm4NAwrE=
=QxdI
-----END PGP SIGNATURE-----