peering-toolbox:route_origin_authorisation
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
peering-toolbox:route_origin_authorisation [2022/05/06 15:29] – [Route Origin Authorisation] philip | peering-toolbox:route_origin_authorisation [2022/08/26 17:15] (current) – [Legacy address space] philip | ||
---|---|---|---|
Line 34: | Line 34: | ||
Holders of legacy (InterNIC assigned) address space are encouraged to create ROAs to assist with ensuring greater integrity of the global routing system. | Holders of legacy (InterNIC assigned) address space are encouraged to create ROAs to assist with ensuring greater integrity of the global routing system. | ||
- | Some (but not all) RIRs have a mechanism allowing legacy address holders whose IP address space is now managed by the RIR under the ERX project to create and maintain a ROA for a small annual fee. | + | Some (but not all) RIRs have a mechanism allowing legacy address holders whose IP address space is now managed by the RIR under the ERX project to create and maintain a ROA for a small annual fee. These operators are encouraged to contact the RIR holding these legacy addresses to find out how to create ROAs. |
- | [[: | + | [[: |
peering-toolbox/route_origin_authorisation.1651814991.txt.gz · Last modified: 2022/05/06 15:29 by philip