Re: I speak too quickly, so here it is in writing.
Jeffrey Haas <jhaas@nexthop.com> Thu, 22 March 2001 04:34 UTC
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id XAA04050 for <idr-archive@nic.merit.edu>; Wed, 21 Mar 2001 23:34:34 -0500 (EST)
Received: by segue.merit.edu (Postfix) id D9E075DDFF; Wed, 21 Mar 2001 23:31:21 -0500 (EST)
Delivered-To: idr-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56) id BC0545DDFA; Wed, 21 Mar 2001 23:31:21 -0500 (EST)
Received: from presque.djinesys.com (presque.djinesys.com [198.108.88.2]) by segue.merit.edu (Postfix) with ESMTP id 7B3735DD95 for <idr@merit.edu>; Wed, 21 Mar 2001 23:31:20 -0500 (EST)
Received: from jhaas.nexthop.com ([141.211.130.148]) by presque.djinesys.com (8.9.3/8.9.3) with ESMTP id XAA93833; Wed, 21 Mar 2001 23:30:19 -0500 (EST) (envelope-from jhaas@nexthop.com)
Received: (from jhaas@localhost) by jhaas.nexthop.com (8.11.0/8.11.0) id f2M4VFW25171; Wed, 21 Mar 2001 23:31:15 -0500 (EST)
Date: Wed, 21 Mar 2001 23:31:15 -0500
From: Jeffrey Haas <jhaas@nexthop.com>
To: smd@ebone.net
Cc: idr@merit.edu
Subject: Re: I speak too quickly, so here it is in writing.
Message-ID: <20010321233115.A25161@nexthop.com>
References: <20010321223700.A16828A3@sean.ebone.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010321223700.A16828A3@sean.ebone.net>; from smd@ebone.net on Wed, Mar 21, 2001 at 11:37:00PM +0100
Sender: owner-idr@merit.edu
Precedence: bulk
On Wed, Mar 21, 2001 at 11:37:00PM +0100, smd@ebone.net wrote: > I refer everyone to the following command line: > > whois -h whois.ripe.net AS1755 Thanks for the suggestion. > As Rudiger notes, there is more to it than supporting simple > prepend, as one engages in increasingly significant multihoming, Although these are rather fine examples of using communities to shape your traffic, the coarse-grained control of "add <n> to my aspath length" isn't there. Any particular reason? > I do not think that there are any situations which really call > for a protocol change to BGP4, especially one that is dangerous > if there is any forgetful-filtering. If you have the impression that the suggested ASE draft was "dangerous" to anyone but the customer in a misconfiguration, you may wish to review http://www.nexthop.com/standards/drafts/draft-jhaas-ase-01.txt And it is only "dangerous" in the sense of installing routes to yourself. This already can happen as a result of other misconfigurations and is no more dangerous than installing an aggregate containing your address space. As mentioned, this didn't make it out before the deadline and fixed the issue of requiring filtering. > Anyone who wishes to turn this and similar examples into a BCP > is more than welcome to poll me for help. I'll probably take you up on this. > Sean. -- Jeff Haas NextHop Technologies