Internet vulnerabilities
Marshall Eubanks
tme at multicasttech.com
Fri Jul 5 12:45:37 UTC 2002
On Fri, 5 Jul 2002 05:22:29 -0700
"Barry Raveendran Greene" <bgreene at cisco.com> 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
>
Thanks - and the AS112 project seems to use static BGP spoofing, where
different locations announce the address via different paths :
"As a way to distribute the load for RFC1918-related queries, we use IPv4
anycast addressing. The address block is 192.175.48.0/24 and its origin AS is
112. This address block is advertised from multiple points around the Internet,
and these distributed servers coordinate their responses and back end
statistical analyses."
Marshall
> > -----Original Message-----
> > From: owner-nanog at merit.edu [mailto:owner-nanog at merit.edu]On Behalf Of
> > Bill Woodcock
> > Sent: Friday, July 05, 2002 4:56 AM
> > To: Marshall Eubanks
> > Cc: nanog at 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
> >
> >
> >
>
More information about the NANOG
mailing list