Representation of IP Routing Policies in a Routing Registry (ripe-81++)
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 83
- Abstract
- 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.
- Publication Date
- 1995-03-01
- Status Note
- Informational
- DOI
10.17487/RFC1786- Link
- https://doi.org/10.17487/RFC1786
- Author(s)
- T. BatesE. GerichL. JoncherayJ-M. JouanigotD. KarrenbergM. TerpstraJ. Yu
Latest version of IETF RFC 1786
Document Versions — IETF RFC 1786
-
▶ IETF RFC 1786 (1995-03-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- Karrenberg, D., "Authorisation and Notification of Changes in the RIPE Database", RIPE-120, October 1994. EXTERNAL
- Merit Network Inc.,"Representation of Complex Routing Policies of an Autonomous System", Work in Progress, March 1994. EXTERNAL
- Bates, T., "Specifying an `Internet Router' in the Routing Registry", RIPE-122, October 1994. EXTERNAL
- Merit Inc. RRDB Tools. See rrdb.merit.edu:pub/meritrr/* EXTERNAL
- Karrenberg, D., "RIPE Database Template for Domains", RIPE-49, April 1992. EXTERNAL
- Estrin, D., Li, T., Rekhter, Y., Varadhan, K., Zappala, D., "Source Demand Routing: Packet Format and Forwarding Specification (Version 1)", Work in Progress, March 1994. EXTERNAL
- Bates, T., Karrenberg, D., Terpstra, M., "RIPE Database Transition Plan", RIPE-123, October 1994. EXTERNAL
- Bates, T., Jouanigot, J-M., Karrenberg, D., Lothberg, P., Terpstra, M., "Representation of IP Routing Policies in the RIPE Database", RIPE-81, February 1993. EXTERNAL
- Joncheray, L., "Experimental Objects and attributes for the Routing Registry", RIPE-182, October1994. EXTERNAL
- Lord, A., Terpstra, M., "RIPE Database Template for Networks and Persons", RIPE-119, October 1994. EXTERNAL
- Bates, T., "Support of Guarded fields within the RIPE Database", ripe-117, July 1994. EXTERNAL
- Bates, T., Karrenberg, D., Terpstra, M., "Support for Classless Internet Addresses in the RIPE Database", RIPE-121, October 1994. EXTERNAL
- PRIDE Tools Release 1. See ftp.ripe.net:pride/tools/pride-tools-1.tar.Z. EXTERNAL
- The Network List Compiler. See dxcoms.cern.ch:pub/ripe-routing-wg/nlc-2.2d.tar EXTERNAL
- IETF RFC 1267 [Active*]
- IETF RFC 1654 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC1786.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 1786, Representation of IP Routing Policies in a Routing Registry (ripe-81++). Available at https://doi.org/10.17487/RFC1786
Snippet:
IETF RFC 1786, Representation of IP Routing Policies in a Routing Registry (ripe-81++). Available at https://doi.org/10.17487/RFC1786
HTML (ISO 690 compliant)
Preview:
IETF RFC 1786, Representation of IP Routing Policies in a Routing Registry (ripe-81++). Available at https://doi.org/10.17487/RFC1786
Snippet:
<span class="citation"><cite>IETF RFC 1786</cite>, Representation of IP Routing Policies in a Routing Registry (ripe-81++). Available at <a href="https://doi.org/10.17487/RFC1786" target="_blank" rel="noopener">https://doi.org/10.17487/RFC1786</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 1786, Representation of IP Routing Policies in a Routing Registry (ripe-81++)
doi: 10.17487/RFC1786
url: https://doi.org/10.17487/RFC1786
doi: 10.17487/RFC1786
url: https://doi.org/10.17487/RFC1786
Snippet:
<li> <cite id="bib-rfc1786">IETF RFC 1786</cite>, Representation of IP Routing Policies in a Routing Registry (ripe-81++) <span class="doi">10.17487/RFC1786</span> </li>
Referenced By
- IETF RFC 2270 [Active*]
- IETF RFC 2280 [Superseded*]
- IETF RFC 2622 [Active*]
- IETF RFC 2725 [Active*]
- IETF RFC 3013 [Active*]