{"id":5329,"date":"2016-08-16T14:06:30","date_gmt":"2016-08-16T20:06:30","guid":{"rendered":"http:\/\/gregsowell.com\/?p=5329"},"modified":"2019-02-07T13:46:37","modified_gmt":"2019-02-07T19:46:37","slug":"arins-route-registry-why-you-need-as-set","status":"publish","type":"post","link":"https:\/\/gregsowell.com\/?p=5329","title":{"rendered":"ARIN’s Route Registry – Why You Need AS-SET"},"content":{"rendered":"

Believe it or not, I’m just now having to create entries in ARIN’s RRs<\/a>…and I’ve been doing this thing for ages hehehe. A RR is a searchable database of route policy information. There are some that are easy to use with web interfaces, but these are generally pay to play. If you stick with ARIN, it’s free…which means I’m going with ARIN.<\/p>\n

Ultimately, what’s the point? When you are peering with other BGP ASNs, they will often seek to verify what information they will allow you to advertise to them. One easy way for them to lookup what to expect from you is to connect to an RR. I can also dictate some more advanced policies inside of special records.<\/p>\n

Getting started, ARIN has a very complete list<\/a> of information on how\/what you should submit to them. The problem is, it’s pretty complex. I did a lot of googling, but I eventually happened on Theodore’s blog entry <\/a>on the subject. This guy is kind enough to explain the basics which will guide you through most of the process. It looks like his page is dead for now(hopefully it will be back).<\/p>\n

The most important part for me were the AS-SET entries. In simple terms, this is a list of autonomous systems that peer with you. Since I’m a service provider, this will be all of my customers(not my upstream ISPs) that I’ll be sending traffic sourced from. More and more upstream ISPs have started requiring an AS-SET entry that contains your downstream customer AS’s. I’ve noticed that just because you have this entry, doesn’t mean you don’t need to also tell them all of the subnets to expect as well as the source AS’, because they will. I’ve also noticed that I don’t have to create an RR record including customer subnets, I just need their AS# in my AS-SET list.<\/p>\n

Here’s an example of my AS-SET:<\/p>\n

as-set: AS-MNS-1
\npassword: MyPassword
\ndescr: Managed Network Solutions AS-SET-1
\nmembers: AS19366, AS13701, AS16903, AS29808, AS46724, AS32768, AS55291
\nmbrs-by-ref: ANY
\nnotify: somepeople@gregsowell.com
\nadmin-c: SOWEL6-ARIN
\ntech-c: SOWEL6-ARIN
\nmnt-by: MNT-MNSL
\nchanged: somepeople@gregsowell.com 20160519
\nsource: ARIN<\/p>\n

aut-num: AS19366
\npassword: MyPassword
\nas-name: MNS-AS19366
\ndescr: Managed Network Solutions AUT-NUM-1
\nmember-of: AS-MNS-1
\nnotify: somepeople@gregsowell.com
\nadmin-c: SOWEL6-ARIN
\ntech-c: SOWEL6-ARIN
\nmnt-by: MNT-MNSL
\nchanged: somepeople@gregsowell.com 20160519
\nsource: ARIN<\/p><\/blockquote>\n

As you can see my AS-SET simply lists all of my downstream customers. Keeps it pretty simple.<\/p>\n

If you plan to simply update an entry, just submit the same information with the modification, and the entry will be overridden in the IRR entry.<\/p>\n

Once you have it submitted and would like to verify it, use the IRRExplorer online portal<\/a>!<\/p>\n

**Line wrap warning**<\/strong><\/p>\n

If you get errors described as:
\nmembers: AS19366, AS13701, AS16903, AS29808, AS46724, AS32768, AS55291, AS12345
\n***Error: Syntax error in “”
\n:
\n***Error: Attribute missing colon, ‘:’ <\/p>\n

You likely have a line that is too long.
\nBreak the errored line into two like this:
\nmembers: AS19366, AS13701, AS16903, AS29808
\nmembers: AS46724, AS32768, AS55291, AS12345<\/p>\n

**End of warning**<\/strong><\/p>\n

I know there is a lot more you can do with it, and I’m sure some of you kind fellows will be happy to leave me comments on best practices \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"

Believe it or not, I’m just now having to create entries in ARIN’s RRs…and I’ve been doing this thing for ages hehehe. A RR\u2026<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[],"class_list":["post-5329","post","type-post","status-publish","format-standard","hentry","category-networking"],"_links":{"self":[{"href":"https:\/\/gregsowell.com\/index.php?rest_route=\/wp\/v2\/posts\/5329","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/gregsowell.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/gregsowell.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/gregsowell.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/gregsowell.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=5329"}],"version-history":[{"count":4,"href":"https:\/\/gregsowell.com\/index.php?rest_route=\/wp\/v2\/posts\/5329\/revisions"}],"predecessor-version":[{"id":5952,"href":"https:\/\/gregsowell.com\/index.php?rest_route=\/wp\/v2\/posts\/5329\/revisions\/5952"}],"wp:attachment":[{"href":"https:\/\/gregsowell.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=5329"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/gregsowell.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=5329"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/gregsowell.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=5329"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}