Yes, usually something like "accept r/n" iff "there is a route object 'covering' r/n and the 'origin AS' of r/n is in the AS-set of the neighbor AS. mh -----Message d'origine----- De:Mike Simkins Envoyé: 17/08/2012, 18:04 A: jlewis@lewis.org; rs@seastrom.com Cc: nanog@nanog.org Objet:Re: IRR-clueful person at 3356? That's the sort of thing we have in Europe, downstream customer need to be in your AS-SET for filtering purposes ----- Original Message ----- From: Jon Lewis [mailto:jlewis@lewis.org] Sent: Friday, August 17, 2012 11:29 AM To: Robert E. Seastrom <rs@seastrom.com> Cc: nanog@nanog.org <nanog@nanog.org> Subject: Re: IRR-clueful person at 3356? On Fri, 17 Aug 2012, Robert E. Seastrom wrote:
The telemetry I'm getting (thirdhand and believed to originate from first line support) suggests that both Level(3)'s direct customer and any downstreams of that customer need to be in the same IRR component.
Can't say for sure if it's true, but I've been told the same thing by Level3 support. ---------------------------------------------------------------------- Jon Lewis, MCP :) | I route Senior Network Engineer | therefore you are Atlantic Net | _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________