<?xml version='1.0'?>

<reference anchor='RFC2769'>

<front>
<title>Routing Policy System Replication</title>
<author initials='C.' surname='Villamizar' fullname='Curtis Villamizar'>
<organization>Avici Systems</organization>
<address>
<email>curtis@avici.com</email></address></author>
<author initials='C.' surname='Alaettinoglu' fullname='Cengiz Alaettinoglu'>
<organization>ISI</organization>
<address>
<email>cengiz@ISI.EDU</email></address></author>
<author initials='R.' surname='Govindan' fullname='Ramesh Govindan'>
<organization>ISI</organization>
<address>
<email>govindan@ISI.EDU</email></address></author>
<author initials='D.M.' surname='Meyer' fullname='David M. Meyer'>
<organization>Cisco</organization>
<address>
<email>dmm@cisco.com</email></address></author>
<date month='February' year='2000' />
<abstract>
<t>The RIPE database specifications and RPSL define languages used as the basis for representing information in a routing policy system.  A repository for routing policy system information is known as a routing registry.  A routing registry provides a means of exchanging information needed to address many issues of importance to the operation of the Internet.  The implementation and deployment of a routing policy system must maintain some degree of integrity to be of any use.  The Routing Policy System Security RFCaddresses the need to assure integrity of the data by proposing an authentication and authorization model.  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.</t></abstract></front>

<seriesInfo name='RFC' value='2769' />
</reference>
