[33414] in North American Network Operators' Group
RE: multiple origin ASes
daemon@ATHENA.MIT.EDU (Dmitri Krioukov)
Tue Jan 9 23:20:15 2001
From: "Dmitri Krioukov" <dima@krioukov.net>
To: "abha" <ahuja@wibh.net>
Cc: <nanog@merit.edu>
Date: Tue, 9 Jan 2001 23:12:22 -0500
Message-ID: <NCBBIKACLKNMKDHKKKNFCEDOFEAA.dima@krioukov.net>
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <Pine.BSI.4.30.0101091557001.45983-100000@dipsy.tch.org>
Errors-To: owner-nanog-outgoing@merit.edu
Abha,
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 :)
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 ;)
>
