Re: The same prefix originated within two different ASs

Alan Barrett <barrett@daisy.ee.und.ac.za> Wed, 12 July 1995 08:05 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00570; 12 Jul 95 4:05 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa00566; 12 Jul 95 4:05 EDT
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa00897; 12 Jul 95 4:05 EDT
Received: by interlock.ans.net id AA26777 (InterLock SMTP Gateway 3.0 for iwg-out@ans.net); Wed, 12 Jul 1995 03:58:20 -0400
Message-Id: <199507120758.AA26777@interlock.ans.net>
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-2); Wed, 12 Jul 1995 03:58:20 -0400
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-1); Wed, 12 Jul 1995 03:58:20 -0400
Date: Wed, 12 Jul 1995 09:57:53 +0200 (GMT+0200)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Alan Barrett <barrett@daisy.ee.und.ac.za>
To: Vadim Antonov <avg@sprint.net>
Cc: bgp@ans.net, bgpd@merit.edu
Subject: Re: The same prefix originated within two different ASs
In-Reply-To: <199507111933.PAA10350@titan.sprintlink.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

> >Can someone please reiterate to me, from experience, reasons why a prefix
> >shouldn't be advertised as originating from two separate ASs?
> 
> Because it breaks underlying assumption after AS-path based policies that
> all prefixes are split into groups by originating AS-es.

But an AS is a set of routers, not a set of prefixes.

> I.e. if you
> do that somebody's preferences or filters based on originating AS-es
> may behave incoherently, potentially creating persistent routing loops.

Can you give an example?  I don't immediately see a way for persistent
routing loops to arise from a prefix being originated by several ASes.  

--apb (Alan Barrett)