[49581] in North American Network Operators' Group
RE: Internet vulnerabilities
daemon@ATHENA.MIT.EDU (Stephen J. Wilcox)
Fri Jul 5 08:37:41 2002
Date: Fri, 5 Jul 2002 13:36:49 +0100 (BST)
From: "Stephen J. Wilcox" <steve@opaltelecom.co.uk>
To: Barry Raveendran Greene <bgreene@cisco.com>
Cc: Bill Woodcock <woody@zocalo.net>,
Marshall Eubanks <tme@multicasttech.com>, nanog@merit.edu
In-Reply-To: <LNEHJBNJAPFNLEGJHCPECEOBHHAA.bgreene@cisco.com>
Errors-To: owner-nanog-outgoing@merit.edu
Doesnt announcing the same routing prefix into BGP from multiple locations do
the same thing without needing a new range or enhancement in IGMP etc ?
We do this in IGP currently..
Steve
On Fri, 5 Jul 2002, Barry Raveendran Greene wrote:
>
>
> FYI - for those scratching their heads on "anycast" .....
>
> I just pushed out a paper on anycast by Chris Metz. Good foundation
> material.
>
> http://www.cisco.com/public/cons/isp/essentials/ip-anycast-cmetz-03.pdf
>
> > -----Original Message-----
> > From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of
> > Bill Woodcock
> > Sent: Friday, July 05, 2002 4:56 AM
> > To: Marshall Eubanks
> > Cc: nanog@merit.edu
> > Subject: Re: Internet vulnerabilities
> >
> >
> >
> > > But the only IPv4 anycast
> > > that I know of does use MSDP :
> > >
> > http://www.ietf.org/internet-drafts/draft-ietf-mboned-anycast-rp-08.txt
> > > Is there a different proposal ? What's the RFC / I-D name ?
> >
> > You seem to be confusing anycast with something complicated. It's not a
> > protocol, it's a method of assigning and routing addresses.
> >
> > -Bill
> >
> >
> >
>
>
