[49580] in North American Network Operators' Group
RE: Internet vulnerabilities
daemon@ATHENA.MIT.EDU (Barry Raveendran Greene)
Fri Jul 5 08:25:44 2002
From: "Barry Raveendran Greene" <bgreene@cisco.com>
To: "Bill Woodcock" <woody@zocalo.net>,
"Marshall Eubanks" <tme@multicasttech.com>
Cc: <nanog@merit.edu>
Date: Fri, 5 Jul 2002 05:22:29 -0700
In-Reply-To: <Pine.NEB.4.33.0207050454420.18820-100000@woody.zocalo.net>
Errors-To: owner-nanog-outgoing@merit.edu
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
>
>
>