[28081] in North American Network Operators' Group
Re: Policies: Routing a subset of another ISP's address block
daemon@ATHENA.MIT.EDU (Niels Chr. Bank-Pedersen)
Sat Apr 8 18:22:46 2000
Date: Sun, 9 Apr 2000 00:20:45 +0200
From: "Niels Chr. Bank-Pedersen" <ncbp@bank-pedersen.dk>
To: nanog@merit.edu
Message-ID: <20000409002045.A91314@bank-pedersen.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <3.0.5.32.20000408195926.007f4100@max.ibm.net.il>; from hank@att.net.il on Sat, Apr 08, 2000 at 07:59:26PM +0200
Errors-To: owner-nanog-outgoing@merit.edu
On Sat, Apr 08, 2000 at 07:59:26PM +0200, Hank Nussbacher wrote:
>
> At 21:04 07/04/00 -0400, Dmitri Krioukov wrote:
>
> The route object described in http://www.ripe.net/ripe/docs/ripe-189.html
> states that origin AS is a single occurence. RIPE-189 should then be
> updated to allow multiple occurences of the origin tag.
Actually, some additions to that effect has allready been made:
http://www.ripe.net/ripe/docs/ripe-189.html#sec:crossnot
It doesn't specifically allow originating routes from more than
one AS, but it does mention that this can be done in multihoming
scenarions.
> -Hank
/Niels Chr.
> >
> >it does generate inconsistent origin as'es and it does break
> >path filters, but not only. it breaks all the tools/methods
> >based on the uniqueness of the route->origin-as mapping. i'm
> >looking for a more or less complete list of these tools/methods.
> >
> >it seems, though, that the inconsistent-as list is growing and
> >this doesn't produce too much panic.
> >
> >and if you examine this list more closely, you'll notice that it
> >looks like the major part of it is generated by the isps doing
> >the aforementioned trick.
> >--
> >dima.
[...]
--
Niels Christian Bank-Pedersen, NCB1-RIPE.
Network Manager, Tele Danmark NET, IP-section.
"Hey, are any of you guys out there actually *using* RFC 2549?"
