peering-toolbox:the_internet_routing_registry
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| peering-toolbox:the_internet_routing_registry [2023/04/30 15:38] – [Background] philip | peering-toolbox:the_internet_routing_registry [2023/04/30 15:39] (current) – [Route Object] philip | ||
|---|---|---|---|
| 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: | ||
peering-toolbox/the_internet_routing_registry.1682833128.txt.gz · Last modified: 2023/04/30 15:38 by philip