peering-toolbox:the_internet_routing_registry
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| peering-toolbox:the_internet_routing_registry [2022/08/26 07:11] – [AS Set] philip | peering-toolbox:the_internet_routing_registry [2023/04/30 05:39] (current) – [Route Object] philip | ||
|---|---|---|---|
| Line 13: | 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 | + | * 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 |
| 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' | 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' | ||
| Line 23: | Line 23: | ||
| ===== 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 80: | 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/the_internet_routing_registry.1661497896.txt.gz · Last modified: by philip