Routing Policy Specification Language: Difference between revisions
Jump to navigation
Jump to search
imported>Howard C. Berkowitz (New page: Developed by the Internet Engineering Task Force, the '''Routing Policy Specification Language (RPSL)''' is a means of describing abstract routing policy among [[aut...) |
imported>Howard C. Berkowitz No edit summary |
||
| Line 5: | Line 5: | ||
While it is not a programming language, it can describe relationships among sets of AS, individual AS, and among routers inside an AS. It is object-oriented. | While it is not a programming language, it can describe relationships among sets of AS, individual AS, and among routers inside an AS. It is object-oriented. | ||
==References== | |||
{{reflist}} | |||
Revision as of 04:08, 28 March 2009
Developed by the Internet Engineering Task Force, the Routing Policy Specification Language (RPSL) is a means of describing abstract routing policy among autonomous systems (AS), the basic building block of global Internet routing. It allows both the definition of policies for the carrying out of business or other goals, but it also has sufficiently fine detail to allow the automatic generation of router configuration language from RPSL descriptions. [1]
While it is not a programming language, it can describe relationships among sets of AS, individual AS, and among routers inside an AS. It is object-oriented.
References
- ↑ C. Alaettinoglu et al. (June 1999), Routing Policy Specification Language (RPSL)