[49653] in North American Network Operators' Group

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

RE: Internet vulnerabilities

daemon@ATHENA.MIT.EDU (Daniel Golding)
Mon Jul 8 11:33:03 2002

From: "Daniel Golding" <dgolding@sockeye.com>
To: "Marshall Eubanks" <tme@multicasttech.com>,
	"Bill Woodcock" <woody@zocalo.net>
Cc: <nanog@merit.edu>
Date: Mon, 8 Jul 2002 11:31:32 -0400
In-Reply-To: <web-1389886@multicasttech.com>
Errors-To: owner-nanog-outgoing@merit.edu


RFC1546.

Really, anycast is a bad name for it. "nearcast" or "closecast" might be
better. Anycast just has a nice ring...

- Daniel Golding

> -----Original Message-----
> From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of
> Marshall Eubanks
> Sent: Friday, July 05, 2002 7:44 AM
> To: Bill Woodcock; Marshall Eubanks
> Cc: nanog@merit.edu
> Subject: Re: Internet vulnerabilities
>
>
>
> On Thu, 4 Jul 2002 18:43:44 -0700 (PDT)
>  Bill Woodcock <woody@zocalo.net> wrote:
> >
> >       On Thu, 4 Jul 2002, Marshall Eubanks wrote:
> >     > Is this the anycast based on MSDP ?
> >
> > Anycast, not multicast.
> >
> >                                 -Bill
> >
> >
>
> 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 ?
>
> Regards
> Marshall
>


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