File formats:

Status:

PROPOSED STANDARD

Obsoletes:

RFC 2280

Updated by:

RFC 4012, RFC 7909

Authors:

C. Alaettinoglu
C. Villamizar
E. Gerich
D. Kessens
D. Meyer
T. Bates
D. Karrenberg
M. Terpstra

Stream:

IETF

Source:

rps (ops)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC2622

Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org

Other actions: View Errata  |  Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 2622

Abstract

RPSL allows a network operator to be able to specify routing policies at various levels in the Internet hierarchy; for example at the Autonomous System (AS) level. At the same time, policies can be specified with sufficient detail in RPSL so that low level router configurations can be generated from them. RPSL is extensible; new routing protocols and new protocol features can be introduced at any time. [STANDARDS-TRACK]

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.