Re: large multi-site enterprises and PI prefix [Re: who gets a /32 [Re: IPV6 renumbering painless?]]

[Owen DeLong <owen () delong com>]

Pekka,
        All of the examples I referenced (which I unfortunately cannot name
due to NDA) fit exactly the model you are referring to.  They advertise a 
small
number of prefixes from a small number of sites to cover a very large and
diverse number of sites.  They advertise the same set of prefixes from the
same ASN in each of those sites.  In cases where they are using VPN for
backbone, they use PA space for the VPN terminators and do not advertise
more specifics to accommodate this.

Hope that helps.

Owen


--On Monday, November 22, 2004 9:11 PM +0200 Pekka Savola 
<pekkas () netcore fi> wrote:

> On Mon, 22 Nov 2004 bmanning () vacation karoshi com wrote:
> > > While I would never argue there are companies who do not push internal
> > > data over the Internet, I am surprised you think that proves no company
> > > pushes internal data over the Internet.
> >
> >         i don't.   my assertion is that there are significant networks
> >         that don't ever touch what we think of as the "internet" but
> >         still use IP to push datagrams around...  and attempting to
> >         marginalize them as "fringe" networks that must use non-global
> >         addresses is, imho, arrogent at best.
>
> I'm not sure anyone is marginalizing them.
>
> The point just is that are those very big, international networks
> advertising the same aggregate in all the places they (publicly) connect
> to the net, and no more specifics anywhere?
>
> I.e., what I'd like to see is a couple of example of international big
> enterprises which would not need to advertise the more specifics to
> Internet anywhere.  How rare is this?
>
> --
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings



--
If it wasn't crypto-signed, it probably didn't come from me.

Attachment: _bin
Description: