One document matched: draft-ietf-sidr-rpki-rtr-impl-05.xml
<?xml version="1.0"?>
<!-- $Id: draft-ietf-sidr-rpki-rtr-impl.xml 2695 2013-12-11 21:20:07Z sra $ -->
<?rfc comments="yes"?><?rfc compact="yes"?><?rfc inline="yes"?><?rfc sortrefs="yes"?><?rfc subcompact="no"?><?rfc symrefs="yes"?><?rfc toc="yes"?><?rfc tocdepth="3"?><?rfc tocindent="yes"?><?rfc tocompact="yes"?><rfc category="info" docName="draft-ietf-sidr-rpki-rtr-impl-05" ipr="trust200902" obsoletes="" updates="" submissionType="IETF" xml:lang="en">
<front>
<title>RPKI Router Implementation Report</title>
<author fullname="Randy Bush " initials="R" surname="Bush">
<organization>Internet Initiative Japan</organization>
<address>
<postal>
<street>5147 Crystal Springs</street>
<city>Bainbridge Island</city>
<region>Washington</region>
<code>98110</code>
<country>US</country>
</postal>
<email>randy@psg.com</email>
</address>
</author>
<author fullname="Rob Austein " initials="R" surname="Austein">
<organization>Dragon Research Labs</organization>
<address>
<email>sra@hactrn.net</email>
</address>
</author>
<author fullname="Keyur Patel " initials="K" surname="Patel">
<organization>Cisco Systems</organization>
<address>
<postal>
<street>170 West Tasman Drive</street>
<city>San Jose</city>
<region>CA</region>
<code>95134</code>
<country>US</country>
</postal>
<email>keyupate@cisco.com</email>
</address>
</author>
<author fullname="Hannes Gredler" initials="H." surname="Gredler">
<organization>Juniper Networks, Inc.</organization>
<address>
<postal>
<street>1194 N. Mathilda Ave.</street>
<city>Sunnyvale</city>
<region>CA</region>
<code>94089</code>
<country>US</country>
</postal>
<email>hannes@juniper.net</email>
</address>
</author>
<author fullname="Matthias Waehlisch" initials="M." surname="Waehlisch">
<organization>FU Berlin</organization>
<address>
<postal>
<street>Takustr. 9</street>
<city>Berlin</city>
<code>14195</code>
<country>Germany</country>
</postal>
<email>waehlisch@ieee.org</email>
<uri>http://www.inf.fu-berlin.de/~waehl</uri>
</address>
</author>
<!-- <date month="December" year="2013"/> -->
<date/>
<abstract>
<t>
This document is an implementation report for the RPKI Router
protocol as defined in <xref target="RFC6810" pageno="false" format="default"/>. The
editor did not verify the accuracy of the information provided
by respondents. The respondents are experts with the
implementations they reported on, and their responses are
considered authoritative for the implementations for which their
responses represent. Respondents were asked to only use the YES
answer if the feature had at least been tested in the lab.</t>
</abstract>
</front>
<middle>
<section title="Introduction" toc="default">
<t>
In order to formally validate the origin Autonomous Systems
(ASs) of BGP announcements, routers need a simple but reliable
mechanism to receive Resource Public Key Infrastructure
(RPKI) <xref target="RFC6810" pageno="false" format="default"/> prefix origin data from a
trusted cache. The RPKI Router protocol defined
in <xref target="RFC6810" pageno="false" format="default"/> provides a mechanism to
deliver validated prefix origin data to routers.
</t>
<t>
This document provides an implementation report for the RPKI
Router protocol as defined in <xref target="RFC6810" pageno="false" format="default">RFC 6810</xref>.
</t>
<t>
The editor did not verify the accuracy of the information
provided by respondents or by any alternative means. The
respondents are experts with the implementations they reported
on, and their responses are considered authoritative for the
implementations for which their responses represent.
Respondents were asked to only use the YES answer if the
feature had at least been tested in the lab.
</t>
</section>
<section title="Implementation Forms" toc="default">
<t>
Contact and implementation information for person filling out this
form:
</t>
<t><list style="hanging">
<t hangText="IOS"> <vspace blankLines="0"/>
Name: Keyur Patel <vspace blankLines="0"/>
Email: keyupate@cisco.com <vspace blankLines="0"/>
Vendor: Cisco Systems, Inc. <vspace blankLines="0"/>
Release: IOS <vspace blankLines="0"/>
Protocol Role: Client
</t>
</list></t>
<t><list style="hanging">
<t hangText="XR "> <vspace blankLines="0"/>
Name: Forhad Ahmed <vspace blankLines="0"/>
Email:foahmed@cisco.com <vspace blankLines="0"/>
Vendor: Cisco Systems, Inc. <vspace blankLines="0"/>
Release: IOS-XR <vspace blankLines="0"/>
Protocol Role: Client
</t>
</list></t>
<t><list style="hanging">
<t hangText="JUNOS"> <vspace blankLines="0"/>
Name: Hannes Gredler <vspace blankLines="0"/>
Email: hannes@juniper.net <vspace blankLines="0"/>
Vendor: Juniper Networks, Inc. <vspace blankLines="0"/>
Release: JUNOS <vspace blankLines="0"/>
Protocol Role: Client
</t>
</list></t>
<t><list style="hanging">
<t hangText="rpki.net"> <vspace blankLines="0"/>
Name: Rob Austein <vspace blankLines="0"/>
Email: sra@hactrn.net <vspace blankLines="0"/>
Vendor: rpki.net project <vspace blankLines="0"/>
Release: http://subvert-rpki.hactrn.net/trunk/ <vspace blankLines="0"/>
Protocol Role: Client, Server
</t>
</list></t>
<t><list style="hanging">
<t hangText="NCC"> <vspace blankLines="0"/>
Name: Tim Bruijnzeels <vspace blankLines="0"/>
Email: tim@ripe.net <vspace blankLines="0"/>
Vendor: RIPE NCC <vspace blankLines="0"/>
Release: RIPE NCC validator-app 2.0.0
https://github.com/RIPE-NCC/rpki-validator <vspace blankLines="0"/>
Protocol Role: Server
</t>
</list></t>
<t><list style="hanging">
<t hangText="RTRlib"> <vspace blankLines="0"/>
Name: Fabian Holler, Matthias Waehlisch <vspace blankLines="0"/>
Email: waehlisch@ieee.org <vspace blankLines="0"/>
Vendor: HAW Hamburg, FU Berlin, RTRlib project <vspace blankLines="0"/>
Release: RTRlib 0.2
http://rpki.realmv6.org/ <vspace blankLines="0"/>
Protocol Role: Client
</t>
</list></t>
<t><list style="hanging">
<t hangText="BBN"> <vspace blankLines="0"/>
Name: David Mandelberg, Andrew Chi <vspace blankLines="0"/>
Email: dmandelb@bbn.com <vspace blankLines="0"/>
Vendor: Raytheon/BBN Technologies <vspace blankLines="0"/>
Release: RPSTIR 0.2
http://sourceforge.net/projects/rpstir/ <vspace blankLines="0"/>
Protocol Role: Server
</t>
</list></t>
<!-- RFC 2629's odd way of requesting a page break after this section -->
<t><vspace blankLines="100"/></t>
</section>
<section title="Protocol Data Units" toc="default">
<t>
Does the implementation support Protocol Data Units (PDUs) as
described in Section 5 of <xref target="RFC6810" pageno="false" format="default"/>?
</t>
<t>
<list style="hanging">
<t hangText="P0:">Serial Notify</t>
<t hangText="P1:">Serial Query</t>
<t hangText="P2:">Reset Query</t>
<t hangText="P3:">Cache Response</t>
<t hangText="P4:">IPv4 Prefix</t>
<t hangText="P6:">IPv6 Prefix</t>
<t hangText="P7:">End of Data</t>
<t hangText="P8:">Cache Reset</t>
<t hangText="P10:">Error Report</t>
</list>
</t>
<texttable title="" suppress-title="false" align="center" style="full">
<ttcol align="left"/>
<ttcol align="center">IOS</ttcol>
<ttcol align="center">XR</ttcol>
<ttcol align="center">JUNOS</ttcol>
<ttcol align="center">rpki .net clnt</ttcol>
<ttcol align="center">rpki .net srvr</ttcol>
<ttcol align="center">NCC</ttcol>
<ttcol align="center">RTR- lib</ttcol>
<ttcol align="center">BBN</ttcol>
<!-- IOS XR JUNOS rpki.net-C rpki.net-S NCC RTR-lib BBN -->
<c>Rcv.P0</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>---</c> <c>---</c> <c>YES</c> <c>---</c>
<c>Snd.P0</c> <c>---</c> <c>---</c> <c>---</c> <c>---</c> <c>YES</c> <c>YES</c> <c>---</c> <c>YES</c>
<c>Rcv.P1</c> <c>---</c> <c>---</c> <c>---</c> <c>---</c> <c>YES</c> <c>YES</c> <c>---</c> <c>YES</c>
<c>Snd.P1</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>---</c> <c>---</c> <c>YES</c> <c>---</c>
<c>Rcv.P2</c> <c>---</c> <c>---</c> <c>---</c> <c>---</c> <c>YES</c> <c>YES</c> <c>---</c> <c>YES</c>
<c>Snd.P2</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>---</c> <c>---</c> <c>YES</c> <c>---</c>
<c>Rcv.P3</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>---</c> <c>---</c> <c>YES</c> <c>---</c>
<c>Snd.P3</c> <c>---</c> <c>---</c> <c>---</c> <c>---</c> <c>YES</c> <c>YES</c> <c>---</c> <c>YES</c>
<c>Rcv.P4</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>---</c> <c>---</c> <c>YES</c> <c>---</c>
<c>Snd.P4</c> <c>---</c> <c>---</c> <c>---</c> <c>---</c> <c>YES</c> <c>YES</c> <c>---</c> <c>YES</c>
<c>Rcv.P6</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>---</c> <c>---</c> <c>YES</c> <c>---</c>
<c>Snd.P6</c> <c>---</c> <c>---</c> <c>---</c> <c>---</c> <c>YES</c> <c>YES</c> <c>---</c> <c>YES</c>
<c>Rcv.P7</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>---</c> <c>---</c> <c>YES</c> <c>---</c>
<c>Snd.P7</c> <c>---</c> <c>---</c> <c>---</c> <c>---</c> <c>YES</c> <c>YES</c> <c>---</c> <c>YES</c>
<c>Rcv.P8</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>---</c> <c>---</c> <c>YES</c> <c>---</c>
<c>Snd.P8</c> <c>---</c> <c>---</c> <c>---</c> <c>---</c> <c>YES</c> <c>YES</c> <c>---</c> <c>YES</c>
<c>Rcv.P10</c> <c>YES</c> <c>YES</c> <c>NO~1</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c>
<c>Snd.P10</c> <c>YES</c> <c>NO</c> <c>NO</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c>
</texttable>
<t>
<list style="format Note %d:">
<t>
No, Error PDU gets silently ignored.
</t>
</list>
</t>
</section>
<section title="Protocol Sequence" toc="default">
<t>
Does RPKI Router protocol implementation follow the four protocol
sequences as outlined in Section 6 of <xref target="RFC6810" pageno="false" format="default"/>?
</t>
<t>
<list style="format S%d:">
<t>Start or Restart</t>
<t>Typical Exchange</t>
<t>No Incremental Update Available</t>
<t>Cache Has No Data Available</t>
</list>
</t>
<texttable title="" suppress-title="false" align="center" style="full">
<ttcol align="left"/>
<ttcol align="center">IOS</ttcol>
<ttcol align="center">XR</ttcol>
<ttcol align="center">JUNOS</ttcol>
<ttcol align="center">rpki .net clnt</ttcol>
<ttcol align="center">rpki .net srvr</ttcol>
<ttcol align="center">NCC</ttcol>
<ttcol align="center">RTRlib</ttcol>
<ttcol align="center">BBN</ttcol>
<!-- IOS XR JUNOS rpki.net-C rpki.net-S NCC RTR-lib BBN -->
<c>S1</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c>
<c>S2</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>NO~1</c> <c>YES</c> <c>YES</c>
<c>S3</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c>
<c>S4</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES~2</c>
</texttable>
<t>
<list style="format Note %d:">
<t>
Does not implement Serial Query, thus Incremental Update
is never available, so responds to Serial Query with Cache
Reset as described in Section 6.3 of <xref target="RFC6810" pageno="false" format="default"/>
</t>
<t>
Sends Cache Reset in response to Serial Query when no data;
sends Error Report PDU in response to Reset Query when no data.
</t>
</list>
</t>
</section>
<section title="Protocol Transport" toc="default">
<t>
Does RPKI Router protocol implementation support different
protocol transport mechanism outlined in Section 7
of <xref target="RFC6810" pageno="false" format="default"/>?
</t>
<texttable title="" suppress-title="false" align="center" style="full">
<ttcol align="left"/>
<ttcol align="center">IOS</ttcol>
<ttcol align="center">XR</ttcol>
<ttcol align="center">JUNOS</ttcol>
<ttcol align="center">rpki .net clnt</ttcol>
<ttcol align="center">rpki .net srvr</ttcol>
<ttcol align="center">NCC</ttcol>
<ttcol align="center">RTRlib</ttcol>
<ttcol align="center">BBN</ttcol>
<!-- IOS XR JUNOS rpki.net-C rpki.net-S NCC RTR-lib BBN -->
<c>SSH</c> <c>NO</c> <c>YES</c> <c>NO</c> <c>YES</c> <c>YES</c> <c>NO</c> <c>YES</c> <c>YES</c>
<c>TLS</c> <c>NO</c> <c>NO</c> <c>NO</c> <c>NO</c> <c>NO</c> <c>NO</c> <c>NO</c> <c>NO</c>
<c>TCP</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c>
<c>TCP-MD5</c> <c>NO</c> <c>NO</c> <c>NO</c> <c>NO</c> <c>NO</c> <c>NO</c> <c>NO</c> <c>NO</c>
<c>TCP-AO</c> <c>NO</c> <c>NO</c> <c>NO</c> <c>NO</c> <c>NO</c> <c>NO</c> <c>NO</c> <c>NO</c>
<c>IPsec</c> <c>NO</c> <c>NO</c> <c>NO</c> <c>NO</c> <c>NO</c> <c>NO</c> <c>NO</c> <c>NO</c>
</texttable>
</section>
<section title="Error Codes" toc="default">
<t>
Does RPKI Router protocol implementation support different protocol
error codes outlined in Section 10 of <xref target="RFC6810" pageno="false" format="default"/>?
</t>
<texttable title="" suppress-title="false" align="center" style="full">
<ttcol align="left"/>
<ttcol align="center">IOS</ttcol>
<ttcol align="center">XR</ttcol>
<ttcol align="center">JUNOS</ttcol>
<ttcol align="center">rpki .net clnt</ttcol>
<ttcol align="center">rpki .net srvr</ttcol>
<ttcol align="center">NCC</ttcol>
<ttcol align="center">RTRlib</ttcol>
<ttcol align="center">BBN</ttcol>
<!-- IOS XR JUNOS rpki.net-C rpki.net-S NCC RTR-lib BBN -->
<!-- Either -->
<c>Rcv.0</c> <c>YES</c> <c>YES</c> <c>NO</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c>
<c>Snd.0</c> <c>YES</c> <c>YES</c> <c>NO</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c>
<!-- Either -->
<c>Rcv.1</c> <c>YES</c> <c>YES</c> <c>NO</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c>
<c>Snd.1</c> <c>YES</c> <c>YES</c> <c>NO</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c>
<!-- Cache to router -->
<c>Rcv.2</c> <c>YES</c> <c>YES</c> <c>NO</c> <c>YES</c> <c>---</c> <c>---</c> <c>YES</c> <c>---</c>
<c>Snd.2</c> <c>---</c> <c>---</c> <c>---</c><c>---</c> <c>YES</c> <c>YES</c> <c>---</c> <c>YES</c>
<!-- Cache to router -->
<c>Rcv.3</c> <c>YES</c> <c>YES</c> <c>NO</c> <c>YES</c> <c>---</c> <c>---</c> <c>YES</c> <c>---</c>
<c>Snd.3</c> <c>---</c> <c>---</c> <c>---</c><c>---</c> <c>YES</c> <c>YES</c> <c>---</c> <c>YES</c>
<!-- Either -->
<c>Rcv.4</c> <c>YES</c> <c>YES</c> <c>NO</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c>
<c>Snd.4</c> <c>YES</c> <c>YES</c> <c>NO</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c>
<!-- Either -->
<c>Rcv.5</c> <c>YES</c> <c>YES</c> <c>NO</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c>
<c>Snd.5</c> <c>YES</c> <c>YES</c> <c>NO</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c>
<!-- Router to cache -->
<c>Rcv.6</c> <c>---</c> <c>---</c> <c>---</c><c>---</c> <c>YES</c> <c>YES~1</c> <c>---</c> <c>YES</c>
<c>Snd.6</c> <c>YES</c> <c>YES</c> <c>NO</c> <c>NO</c> <c>---</c> <c>---</c> <c>YES</c> <c>---</c>
<!-- Router to cache -->
<c>Rcv.7</c> <c>---</c> <c>---</c> <c>---</c><c>---</c> <c>YES</c> <c>YES~1</c> <c>---</c> <c>YES</c>
<c>Snd.7</c> <c>YES</c> <c>YES</c> <c>NO</c> <c>NO</c> <c>---</c> <c>---</c> <c>YES</c> <c>---</c>
</texttable>
<t>
<list style="format Note %d:">
<t>
YES, but... fatal, so connection is dropped, but cache does not conclude it's inconsistent.
</t>
</list>
</t>
</section>
<section title="Incremental Updates Support" toc="default">
<t>
Does the RPKI Router implementation support Incremental Updates as
defined in Section 4 of <xref target="RFC6810" pageno="false" format="default"/>?
</t>
<texttable title="" suppress-title="false" align="center" style="full">
<ttcol align="center">IOS</ttcol>
<ttcol align="center">XR</ttcol>
<ttcol align="center">JUNOS</ttcol>
<ttcol align="center">rpki.net clnt</ttcol>
<ttcol align="center">rpki.net srvr</ttcol>
<ttcol align="center">NCC</ttcol>
<ttcol align="center">RTRlib</ttcol>
<ttcol align="center">BBN</ttcol>
<!-- IOS XR JUNOS rpki.net-C rpki.net-S NCC RTR-lib BBN -->
<c>NO</c> <c>NO</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>NO</c> <c>YES</c> <c>YES</c>
</texttable>
</section>
<section title="Session ID Support" toc="default">
<t>
Session ID is used to indicate that the cache server may have
restarted and that the incremental restart may not be
possible.
</t>
<t>
Does RPKI Router protocol implementation support Session ID
procedures outlined in Section 5.1
of <xref target="RFC6810" pageno="false" format="default"/>?
</t>
<texttable title="" suppress-title="false" align="center" style="full">
<ttcol align="center">IOS</ttcol>
<ttcol align="center">XR</ttcol>
<ttcol align="center">JUNOS</ttcol>
<ttcol align="center">rpki.net clnt</ttcol>
<ttcol align="center">rpki.net srvr</ttcol>
<ttcol align="center">NCC</ttcol>
<ttcol align="center">RTRlib</ttcol>
<ttcol align="center">BBN</ttcol>
<!-- IOS XR JUNOS rpki.net-C rpki.net-S NCC RTR-lib BBN -->
<c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>NO~1</c> <c>YES</c> <c>YES</c>
</texttable>
<t>
<list style="format Note %d:">
<t>
NO, using random, but will FIX
</t>
</list>
</t>
</section>
<section title="Incremental Session Startup Support" toc="default">
<t>
Does the RPKI Router protocol implementation support
Incremental session startups with Serial Number and Session ID
as defined in section 5.3 of <xref target="RFC6810" pageno="false" format="default"/>?
</t>
<texttable title="" suppress-title="false" align="center" style="full">
<ttcol align="center">IOS</ttcol>
<ttcol align="center">XR</ttcol>
<ttcol align="center">JUNOS</ttcol>
<ttcol align="center">rpki.net clnt</ttcol>
<ttcol align="center">rpki.net srvr</ttcol>
<ttcol align="center">NCC</ttcol>
<ttcol align="center">RTRlib</ttcol>
<ttcol align="center">BBN</ttcol>
<!-- IOS XR JUNOS rpki.net-C rpki.net-S NCC RTR-lib BBN -->
<c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>YES</c> <c>NO</c> <c>YES</c> <c>YES</c>
</texttable>
</section>
<section title="Interoperable Implementations" toc="default">
<t>
List other implementations that you have tested interoperability of
RPKI Router Implementation.
</t>
<section title="Cisco Implementation" toc="default">
<t>
Cisco: The Cisco IOS and IOS-XR implementation should be
interoperable with other vendor RPKI Router Protocol
implementations. In particular we have tested our
interoperability with rpki.net's RPKI Router
implementation.
</t>
</section>
<section title="Juniper Implementation" toc="default">
<t>
Juniper: The Juniper Networks, Inc. JUNOS implementation
should be interoperable with other vendor RPKI Router Protocol
implementations. In particular we have tested our
interoperability with rpki.net's and NCC's RPKI Router Cache
implementation.
</t>
</section>
<section title="rpki.net Implementation" toc="default">
<t>
rpki.net: The rpki.net implementation should operate with
other rpki-rtr implementations. In particular, we have tested
our rpki-rtr server's interoperability with Cisco IOS, Cisco IOS-XR,
and Juniper.
</t>
</section>
<section title="RIPE NCC Implementation" toc="default">
<t>
RIPE NCC: The RIPE NCC validator has been tested by us with other
rpki-rtr implementations. In particular we have tested with RTRLib and
CISCO IOS. We received positive feedback from close contacts testing our
validator with JUNOS and Quagga.
</t>
</section>
<section title="RTRlib Implementation" toc="default">
<t>
RTRlib: The RTRlib has been tested by us with other rpki-rtr
implementations. In particular, we have tested with rtr-origin from
rpki.net and RIPE NCC Validator.
</t>
</section>
<section title="BBN RPSTIR Implementation" toc="default">
<t>
BBN RPSTIR: We have not yet tested with any other implementations.
</t>
</section>
</section>
<section anchor="IANA" title="IANA Considerations" toc="default">
<t>
This document makes no request of IANA.
</t>
<t>
Note to RFC Editor: The IANA has requested that this section
remain in the document upon publication as an RFC. This note
to the RFC Editor, however, may be removed.
</t>
</section>
<section title="Security considerations" toc="default">
<t>
No new security issues are introduced to the RPKI Router
protocol defined in <xref target="RFC6810" pageno="false" format="default"/>.
</t>
</section>
<section anchor="Acknowledgements" title="Acknowledgements" toc="default">
<t>
The authors would like to thank Andrew Chi, David Mandelberg,
Fabian Holler, Forhad Ahmed, and Tim Bruijnzeels for their
contributions to this document.
</t>
</section>
</middle>
<back>
<references title="Normative References">
<!-- Begin inclusion: reference.RFC.6810.xml --><reference anchor="RFC6810">
<front>
<title>The Resource Public Key Infrastructure (RPKI) to Router Protocol</title>
<author fullname="R. Bush" initials="R." surname="Bush">
<organization/>
</author>
<author fullname="R. Austein" initials="R." surname="Austein">
<organization/>
</author>
<date month="January" year="2013"/>
<abstract>
<t>In order to verifiably validate the origin Autonomous Systems of BGP announcements, routers need a simple but reliable mechanism to receive Resource Public Key Infrastructure (RFC 6480) prefix origin data from a trusted cache. This document describes a protocol to deliver validated prefix origin data to routers. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="6810"/>
<format type="TXT" octets="59714" target="http://www.rfc-editor.org/rfc/rfc6810.txt"/>
<!-- current-status PROPOSED STANDARD -->
<!-- publication-status PROPOSED STANDARD -->
</reference><!-- End inclusion: reference.RFC.6810.xml -->
</references>
</back>
</rfc><!--
- Local Variables:
- mode:sgml
- indent-tabs-mode: nil
- End:
-->
| PAFTECH AB 2003-2026 | 2026-04-22 21:01:42 |