[33418] in North American Network Operators' Group
RE: multiple origin ASes
daemon@ATHENA.MIT.EDU (abha)
Wed Jan 10 03:12:23 2001
Date: Wed, 10 Jan 2001 00:06:52 -0800 (PST)
From: abha <ahuja@wibh.net>
To: Dmitri Krioukov <dima@krioukov.net>
Cc: <nanog@merit.edu>
In-Reply-To: <NCBBIKACLKNMKDHKKKNFCEDOFEAA.dima@krioukov.net>
Message-ID: <Pine.BSI.4.30.0101092331280.52007-100000@dipsy.tch.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
Hi Dima...
> One of the origins :) of inconsistent routes is improper multihoming --
> a network is multihomed but no public ASN is assigned to it; some private
> ASN is used and stripped off (by remove-private-as) at the edges of
> the both (or many) ISPs, which results in multiple origin ASs for the
> network prefix. I don't know how intentional this practice is, though :)
Yeah. I know about that origin of inconsistent ASes. I'm more curious
about other creative occurences...
Thanks!
-abha ;)
> The question about how bad inconsistent routes are was also addressed
> on this list.
> --
> dima.
>
> > -----Original Message-----
> > From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of
> > abha
> > Sent: Tuesday, January 09, 2001 7:02 PM
> > To: nanog@merit.edu
> > Subject: multiple origin ASes
> >
> >
> >
> >
> > Hi All!
> >
> > I'm trying to get a feeling for how often ISPs announce a prefix from
> > different origin ASes intentionally.... (and why...)
> >
> > I asked this question on my peering survey (*grin*), but I thought i'd hit
> > a wider audience...
> >
> > Thanks.
> >
> > -abha ;)
> >
>
>
>
