So let's have a look at some of the objects that we need to use. The first one is the Route Object and this one documents which autonomous system number is originating the route that's listed. This is required by many major transit providers today they build their customer and peer filter based on the route objects listed in the IRR referring to at least the registry based routing registries and the radb some operators run their own instance of the irr as well and they may require the customers to place the route object there if the customer is not using any of the registry hosted ones or the radb the slide shows you some examples these are taken from a network operator it shows a route object with the address space and the origin as one example is for ipv4 the other example is for ipv6 the next object is the air subject the as object documents the peering policy used by this as with other autonomous systems it lists network information it lists contact information and it lists routes announced to and accepted from neighboring autonomous systems some operators pay close attention to what is contained in the air subject and some will configure the border route of bgp so that the policy is based on what is listed in the as object the screen shows you a typical as object example again taken from publicly available information for a network operator it lists some import statements which autonomous system it's importing prefixes from and how and some export statements which again lists what they're going to export to the different autonomous systems the final one we're going to look at is the air set the air set is referenced in the as object and is used by network operators to group as numbers they provide transit for in an easier to manage form it's convenient for more complicated policy declarations and is used mostly by network operators who build the ebgp filters from the irr entries in fact it's commonly used at internet exchange points to handle large numbers of peers if you look at the example on this slide in front of you you'll see again a typically available air set by a transit provider and the transit provider is listing the as members in other words the autonomous systems that it is providing transit to so when somebody else needs to set up policy or they need to set up policy they can refer to the air set rather than having to list all the members individually if they get a new end user or new customers AS that they need to announce, they simply add it to the AR set and no other object in the internet routing registry needs to be changed.

© Produced by Philip Smith and the Network Startup Resource Center, through the University of Oregon.

Attribution-NonCommercial 4.0 International (CC BY-NC 4.0)
This is a human-readable summary of (and not a substitute for) the license. Disclaimer. You are free to: Share — copy and redistribute the material in any medium or format Adapt — remix, transform, and build upon the material The licensor cannot revoke these freedoms as long as you follow the license terms. Under the following terms: Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. NonCommercial — You may not use the material for commercial purposes. No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.