RFC 2280: Routing Policy Specification Language (RPSL)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2622.
Current version: RFC 2622 — Routing Policy Specification Language (RPSL)
In plain English — editorial summary, not part of the RFC
This memo is the reference document for the Routing Policy Specification Language (RPSL). 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]
Document record
- Document ID
- RFC2280
- Published
- January 1998
- Authors
- C. Alaettinoglu; T. Bates; E. Gerich; D. Karrenberg; D. Meyer; M. Terpstra; C. Villamizar
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 53
- Also known as
- —
- Obsoleted by:
- RFC 2622
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2725Routing Policy System SecurityUpdated
December 1999
- RFC 3138Extended Assignments in 233/8Obsoleted
June 2001
- RFC 2178OSPF Version 2Obsoleted
July 1997
- RFC 2769Routing Policy System ReplicationCurrent
February 2000
- RFC 2270Using a Dedicated AS for Sites Homed to a Single ProviderCurrent
January 1998
- RFC 1966BGP Route Reflection An alternative to full mesh IBGPObsoleted
June 1996
- RFC 2624NFS Version 4 Design ConsiderationsCurrent
June 1999
- RFC 1665Definitions of Managed Objects for SNA NAUs using SMIv2Obsoleted
July 1994
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?