RFC 1786: Representation of IP Routing Policies in a Routing Registry (ripe-81++)
In plain English — editorial summary, not part of the RFC
This document is an update to the original `ripe-81' proposal for representing and storing routing polices within the RIPE database. It incorporates several extensions proposed by Merit Inc. and gives details of a generalized IP routing policy representation to be used by all Internet routing registries. It acts as both tutorial and provides details of database objects and attributes that use and make up a routing registry. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1786
- Published
- March 1995
- Authors
- T. Bates; E. Gerich; L. Joncheray; J-M. Jouanigot; D. Karrenberg; M. Terpstra; J. Yu
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 83
- Also known as
- —
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?