RFC 2650: Using RPSL in Practice
In plain English — editorial summary, not part of the RFC
This document is a tutorial on using the Routing Policy Specification Language (RPSL) to describe routing policies in the Internet Routing Registry (IRR). This memo provides information for the Internet community.
Document record
- Document ID
- RFC2650
- Published
- August 1999
- Authors
- D. Meyer; J. Schmitz; C. Orange; M. Prior; C. Alaettinoglu
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 26
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2725Routing Policy System SecurityUpdated
December 1999
- RFC 6382Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted ServicesCurrent
October 2011
- RFC 7594A Framework for Large-Scale Measurement of Broadband Performance (LMAP)Current
September 2015
- RFC 7682Considerations for Internet Routing Registries (IRRs) and Routing Policy ConfigurationCurrent
December 2015
- RFC 8909Registry Data Escrow SpecificationCurrent
November 2020
- RFC 9022Domain Name Registration Data (DNRD) Objects MappingCurrent
May 2021
- RFC 4725ENUM Validation ArchitectureCurrent
November 2006
- RFC 5645Update to the Language Subtag RegistryCurrent
September 2009
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?