[28921] in North American Network Operators' Group
Re: That pesky AS path corruption bug...
daemon@ATHENA.MIT.EDU (Jeff Haas)
Wed May 24 10:28:47 2000
Date: Wed, 24 May 2000 10:26:41 -0400
From: Jeff Haas <jeffhaas@merit.edu>
To: NANOG <nanog@merit.edu>
Message-ID: <20000524102641.C981@vorlon.merit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <Pine.LNX.3.96.1000524001813.17089A-100000@Overkill.EnterZone.Net>; from John Fraizer on Wed, May 24, 2000 at 12:23:05AM -0400
Errors-To: owner-nanog-outgoing@merit.edu
On Wed, May 24, 2000 at 12:23:05AM -0400, John Fraizer wrote:
> Come on people. It's VERY easy to do one of the following:
>
> (1) NOT implement AS-path filtering on route-server connections
AS-path filtering is a perfectly reasonable thing to do.
The route server software can either prepend the RS AS, or not.
RSng peers have full control over this via their registered inet-rtr
policy.
http://www.rsng.net/peering.html#rs-in
options: aspath-trans
> Am I the only RA that notifies the peering contacts of all other RS peers
> when someone new joins? I certainly hope not.
Unless your policy (not specifically you, John) is promiscuous,
its necessary for both "the new guy" and existing RS peers to
update their aut-num policy (and possibly import() policy in
their inet-rtr:rs-in) in order for the new routes to be proxied via
the route servers.
> John Fraizer
> EnterZone, Inc
--
Jeffrey Haas - Merit RSng project - jeffhaas@merit.edu
