[22800] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: aads renumbering rumor and implications

daemon@ATHENA.MIT.EDU (Michael P. Lyle)
Mon Jan 25 01:01:46 1999

Date: Sun, 24 Jan 1999 21:48:14 -0800
From: "Michael P. Lyle" <icee@phoenix.lyle.org>
To: Randy Bush <rbush@bainbridge.verio.net>, nanog@merit.edu
In-Reply-To: <m104eg5-0008G4C@rip.psg.com>; from Randy Bush on Sun, Jan 24, 1999 at 09:35:13PM -0800

On Sun, Jan 24, 1999 at 09:35:13PM -0800, Randy Bush wrote:
> >>  o does anyone see why the exchange address space needs to be globally
> >>    routable?
> > Traceroute.
> 
> as the fabric is used for peering under bi-lats, if we each announce the
> mesh to our customers and not to our peers, then i believe you will have
> your tracroutes and yet the prefix does not have to be globally routable,
> e.g. could be 209.666.42/24.
> 
> randy

Holdon, i don't even see the need for that;  if you traceroute out, the
packets will cross the exchange irregardless of whether you're announcing
it to your customers, and a message of TTL exceeded will be generated
from the exchange's address..  The important question is, should they
be globally UNIQUE for troubleshooting purposes?  I think so.

Mike

-- 
Michael P. Lyle
Security Architect
Exodus Communications

home help back first fref pref prev next nref lref last post