RFC 2769: Routing Policy System Replication
In plain English — editorial summary, not part of the RFC
This document addresses the need to distribute data over multiple repositories and delegate authority for data subsets to other repositories without compromising the authorization model established in Routing Policy System Security RFC. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2769
- Published
- February 2000
- Authors
- C. Villamizar; C. Alaettinoglu; R. Govindan; D. Meyer
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 42
- 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 2622Routing Policy Specification Language (RPSL)Updated
June 1999
- RFC 2280Routing Policy Specification Language (RPSL)Obsoleted
January 1998
- RFC 7682Considerations for Internet Routing Registries (IRRs) and Routing Policy ConfigurationCurrent
December 2015
- RFC 9632Finding and Using Geofeed DataCurrent
August 2024
- RFC 9977Publishing End-Site Prefix LengthsCurrent
May 2026
- RFC 2654A Tagged Index Object for use in the Common Indexing ProtocolCurrent
August 1999
- RFC 2652MIME Object Definitions for the Common Indexing Protocol (CIP)Current
August 1999
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?