Re: IRR Upstream\Downstream

[Owen DeLong via NANOG <nanog () nanog org>]

Generally, you’ll need an export and import policy for each peer AS.

Export should describe what you send to them.
Import should describe what you will accept from them.

In the case of upstreams, that’s usually “to X export MYAS[+customer_AS list]” and “from X import ANY”.

In the case of downstream customers, that’s usually “to Y export ANY” and “from Y import Y”.

Obviously, if your customer has downstream ASs, that import policy will expand.

Owen


> On Sep 20, 2021, at 17:06 , Mike Hammett <nanog () ics-il net> wrote:
>
> I'm trying to firm up my grasp of how I define my neighbor ASes in my IRR entries.
>
> https://bgp.he.net/AS40764#_irr <https://bgp.he.net/AS40764#_irr>
>
> In my aut-num, I've defined my two upstreams (Intercarrier and Cogent). I've used their AS-Set or just their AS and 
> used that in the export lines.
>
> I'd assume I'd do the reverse in the import fields for any downstream customers.
>
> I realized after looking at this that I need to add an export to IX and other peering connections.
>
> What else do I need to change?
>
>
>
>
> Yes, I realized that I just asked NANOG to criticize me. Hopefully, I get more help than flames.  ;-)
>
>
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com <http://www.ics-il.com/>
>
> Midwest-IX
> http://www.midwest-ix.com <http://www.midwest-ix.com/>