Philip Smith's Internet Development Site

User Tools

Site Tools

Trace:
peering-toolbox:the_internet_routing_registry

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
peering-toolbox:the_internet_routing_registry [2022/05/06 04:22] – [AS Set] philippeering-toolbox:the_internet_routing_registry [2023/04/30 05:39] (current) – [Route Object] philip
Line 1: Line 1:
-===== The Internet Routing Registry =====+====== The Internet Routing Registry ======
  
-The Internet Routing Registry (IRR) is used to document policy of autonomous networks taking part in the global Internet.+The Internet Routing Registry (IRR) is used to document policy of autonomous networks taking part in the global Internet. The IRR has been around since the early days of the Internet, starting off as the Routing Arbiter project operated by Merit Network when the Internet was mostly made up of University and Research institution networks. 
 + 
 +===== Background =====
  
 There is no one system that is the IRR, but is made up of several components. Each of the 5 Regional Internet Registries ([[https://www.afrinic.net/|AfriNIC]], [[https://apnic.net|APNIC]], [[https://www.arin.net/|ARIN]], [[https://www.lacnic.net/|LACNIC]], [[https://www.ripe.net/|RIPE NCC]]) runs their own component of the IRR, and this is done as a service to their members. There is no one system that is the IRR, but is made up of several components. Each of the 5 Regional Internet Registries ([[https://www.afrinic.net/|AfriNIC]], [[https://apnic.net|APNIC]], [[https://www.arin.net/|ARIN]], [[https://www.lacnic.net/|LACNIC]], [[https://www.ripe.net/|RIPE NCC]]) runs their own component of the IRR, and this is done as a service to their members.
Line 11: Line 13:
 Our advice is as follows: Our advice is as follows:
   * Network Operators holding IP address distributed by an RIR should only use their RIR's instance of the Internet Routing Registry   * Network Operators holding IP address distributed by an RIR should only use their RIR's instance of the Internet Routing Registry
-  * Network Operators holding IP address distributed by InterNIC (pre-existing the RIRs) means the Network Operator has to use RADB unless their RIR has a policy permiting them to use the RIR's intance of the IRR.+  * Network Operators holding IP address distributed by InterNIC (pre-existing the RIRs) means the Network Operator has to use RADB unless their RIR has a policy permitting them to use the RIR's instance of the IRR.
  
 It is beyond the scope of the Peering Toolbox to provide a detailed tutorial about the operation of the Internet Routing Registry. However, we have to highlight the three key objects that all network operators need to be aware of, and one that is more or less mandatory in today's Internet. The following sections describe: It is beyond the scope of the Peering Toolbox to provide a detailed tutorial about the operation of the Internet Routing Registry. However, we have to highlight the three key objects that all network operators need to be aware of, and one that is more or less mandatory in today's Internet. The following sections describe:
  
-  * the [[peering-toolbox:how-to-peer#route_object|Route Object]] +  * the [[the_internet_routing_registry#route_object|Route Object]] - needed by all network operators 
-  * the [[peering-toolbox:how-to-peer#as_object|AS Object]] +  * the [[the_internet_routing_registry#as_object|AS Object]] 
-  * the [[peering-toolbox:how-to-peer#as_set|AS Set]]+  * the [[the_internet_routing_registry#as_set|AS Set]]
  
-==== Route Object ====+===== Route Object =====
  
-The Route Object documents which Autonomous System is originating the route listed. It is required by many major transit providers because they build their customer and peer filter based on the route- +The Route Object documents which Autonomous System is originating the route listed. It is required by many major transit providers because they build their customer and peer filter based on the route-objects listed in the IRR. Operators will refer to at least the 5 RIR routing registries and the RADB to check for route-objects. Those who run their own IRR instance will generally check there first before consulting with the IRR instances run elsewhere.
-objects listed in the IRR. Operators will refer to at least the 5 RIR routing registries and the RADB to check for route-objects. Those who run their own IRR instance will generally check there first before consulting with the IRR instances run elsewhere.+
  
 A typical IPv4 route object may look like this: A typical IPv4 route object may look like this:
Line 33: Line 34:
  
 The key ingredients of a route-object are: The key ingredients of a route-object are:
-  * route/route6: identifying the IP address block +  * **route/route6**: identifying the IP address block 
-  * descr: describing what the block is about (useful but not essential) +  * **descr**: describing what the block is about (useful but not essential) 
-  * country: which country it is used in (can help with geolocation) +  * **country**: which country it is used in (can help with geolocation) 
-  * notify: who to notify if anything with the object changes +  * **notify**: who to notify if anything with the object changes 
-  * maint-by: who the maintainer of the object is +  * **maint-by**: who the maintainer of the object is 
-  * origin: the ASN which is originating this address block +  * **origin**: the ASN which is originating this address block 
-  * last-modified: when the object was last changed +  * **last-modified**: when the object was last changed 
-  * source: which instance of the IRR provided the data+  * **source**: which instance of the IRR provided the data
  
 Operators who build their BGP filters based on the contents of the IRR will search all route-objects for their peer ASNs, and only accepte BGP announcements from peers (and customers) which have matching and correct route-objects. No route-object or an incorrect route-object, and the BGP announcement will not be accepted. Operators who build their BGP filters based on the contents of the IRR will search all route-objects for their peer ASNs, and only accepte BGP announcements from peers (and customers) which have matching and correct route-objects. No route-object or an incorrect route-object, and the BGP announcement will not be accepted.
Line 47: Line 48:
  
 Creation of a Route Object can be done via the RIR's member portal - consult the relevant RIR for more information. Creation of a Route Object can be done via the RIR's member portal - consult the relevant RIR for more information.
-==== AS Object ====+ 
 +===== AS Object =====
  
 The AS Object documents a Network Operator's peering policy with other Autonomous Systems. The AS Object lists network information, contact information, routes announced to neighbouring autonomous systems, and routes accepted from neighbouring autonomous systems. The AS Object documents a Network Operator's peering policy with other Autonomous Systems. The AS Object lists network information, contact information, routes announced to neighbouring autonomous systems, and routes accepted from neighbouring autonomous systems.
Line 65: Line 67:
 Creation of an AS Object can be done via the RIR's member portal - consult the relevant RIR for more information. Creation of an AS Object can be done via the RIR's member portal - consult the relevant RIR for more information.
  
-==== AS Set ====+===== AS Set =====
  
 The AS-Set is used by network operators to group AS numbers they provide transit for in an easier to manage form. It is very convenient for more complicated policy declarations and is used mostly by network operators who build their EBGP filters from their IRR entries. It is also commonly used at Internet Exchange Points to handle a large numbers of peers. The AS-Set is used by network operators to group AS numbers they provide transit for in an easier to manage form. It is very convenient for more complicated policy declarations and is used mostly by network operators who build their EBGP filters from their IRR entries. It is also commonly used at Internet Exchange Points to handle a large numbers of peers.
Line 77: Line 79:
 Then when the Network Operator needs to refer to outbound policy for its customers, rather than an entry for each customer ASN (and its own), it simply refers to its AS-set instead. Then when the Network Operator needs to refer to outbound policy for its customers, rather than an entry for each customer ASN (and its own), it simply refers to its AS-set instead.
  
-[[:peering-toolbox/how-to-peer| Back to How To Peer page]]+[[:peering-toolbox/how-to-peer| Back to "What is required for Peering" page]] 
peering-toolbox/the_internet_routing_registry.1651810959.txt.gz · Last modified: by philip