Routing Policy Specification Language: Difference between revisions
Created page with "'''Routing Policy Specification Language''' (RPSL) allows global routing policy to be in a single distributed database. Despite its name, RPSL is not a router configuration la..." |
Christiane (talk | contribs) m Christiane moved page RPSL to Routing Policy Specification Language: Standardize |
||
(No difference)
| |||
Latest revision as of 20:25, 24 June 2024
Routing Policy Specification Language (RPSL) allows global routing policy to be in a single distributed database. Despite its name, RPSL is not a router configuration language. RPSL is oriented toward objects, which contain policy and administrative information that is registered in Internet Routing Registries (IRRs).
Overview edit
RFC 2622 explains that RPSL allows network operators to specify routing policies at various levels in the Internet hierarchy with enough detail that low-level router configurations can be generated. RPSL is extensible, meaning new protocols and features can be introduced at any time. RPSL replaces RIPE-181 (RFC 1786), which replaced RIPE-81 in October 1994.[1]
RPSL, which is case insensitive, describes aspects of routing policy, such as prefixes, Autonomous System Numbers, relationships between BGP peers, management responsibilities.[2]
Other RPSL specifications edit
- – RFC-2650: Using RPSL in Practice
- – RFC-2726: PGP Authentication for RIPE Database Updates
- – RFC-2725: Routing Policy System Security
- – RFC-2769: Routing Policy System Replication
- – RFC-4012: Routing Policy System Replication next generation