draft-ietf-sidr-origin-ops-18.txt   draft-ietf-sidr-origin-ops-19.txt 
Network Working Group R. Bush Network Working Group R. Bush
Internet-Draft Internet Initiative Japan Internet-Draft Internet Initiative Japan
Intended status: Best Current Practice July 2012 Intended status: Best Current Practice August 2012
Expires: December 31, 2012 Expires: January 31, 2013
RPKI-Based Origin Validation Operation RPKI-Based Origin Validation Operation
draft-ietf-sidr-origin-ops-18 draft-ietf-sidr-origin-ops-19
Abstract Abstract
Deployment of RPKI-based BGP origin validation has many operational Deployment of RPKI-based BGP origin validation has many operational
considerations. This document attempts to collect and present the considerations. This document attempts to collect and present the
most critical. It is expected to evolve as RPKI-based origin most critical. It is expected to evolve as RPKI-based origin
validation is deployed and the dynamics are better understood. validation is deployed and the dynamics are better understood.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to
document are to be interpreted as described in RFC 2119 [RFC2119]. be interpreted as described in RFC 2119 [RFC2119] only when they
appear in all upper case. They may also appear in lower or mixed
case as English words, without any normative meaning.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 31, 2012. This Internet-Draft will expire on January 31, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (http://trustee.ietf.org/ Provisions Relating to IETF Documents (http://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text extracted from this document must include Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License. provided without warranty as described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Suggested Reading . . . . . . . . . . . . . . . . . . . . . . 2 2. Suggested Reading . . . . . . . . . . . . . . . . . . . . . . 3
3. RPKI Distribution and Maintenance . . . . . . . . . . . . . . 3 3. RPKI Distribution and Maintenance . . . . . . . . . . . . . . 3
4. Within a Network . . . . . . . . . . . . . . . . . . . . . . . 5 4. Within a Network . . . . . . . . . . . . . . . . . . . . . . . 5
5. Routing Policy . . . . . . . . . . . . . . . . . . . . . . . . 5 5. Routing Policy . . . . . . . . . . . . . . . . . . . . . . . . 5
6. Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 6. Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 8 7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
10.1. Normative References . . . . . . . . . . . . . . . . . . 8 10.1. Normative References . . . . . . . . . . . . . . . . . . 8
10.2. Informative References . . . . . . . . . . . . . . . . . 9 10.2. Informative References . . . . . . . . . . . . . . . . . 9
skipping to change at page 2, line 55 skipping to change at page 3, line 14
edge networks. edge networks.
RPKI-based origin validation has been designed so that, with prudent RPKI-based origin validation has been designed so that, with prudent
local routing policies, there is little risk that what is seen as local routing policies, there is little risk that what is seen as
today's normal Internet routing is threatened by imprudent deployment today's normal Internet routing is threatened by imprudent deployment
of the global RPKI, see Section 5. of the global RPKI, see Section 5.
2. Suggested Reading 2. Suggested Reading
It is assumed that the reader understands BGP, [RFC4271], the RPKI, It is assumed that the reader understands BGP, [RFC4271], the RPKI,
see [RFC6480], the RPKI Repository Structure, see [RFC6481], ROAs, see [RFC6480], the RPKI Repository Structure, see [RFC6481], Route
see [RFC6482], the RPKI to Router Protocol, see [I-D.ietf-sidr-rpki- Origin Authorizations (ROAs), see [RFC6482], the RPKI to Router
rtr], RPKI-based Prefix Validation, see [I-D.ietf-sidr-pfx-validate], Protocol, see [I-D.ietf-sidr-rpki-rtr], RPKI-based Prefix Validation,
and Ghostbusters Records, see [RFC6493]. see [I-D.ietf-sidr-pfx-validate], and Ghostbusters Records, see
[RFC6493].
3. RPKI Distribution and Maintenance 3. RPKI Distribution and Maintenance
The RPKI is a distributed database containing certificates, CRLs, The RPKI is a distributed database containing certificates, CRLs,
manifests, ROAs, and Ghostbusters Records as described in [RFC6481]. manifests, ROAs, and Ghostbusters Records as described in [RFC6481].
Policies and considerations for RPKI object generation and Policies and considerations for RPKI object generation and
maintenance are discussed elsewhere. maintenance are discussed elsewhere.
The RPKI repository design [RFC6481] anticipated a hierarchic The RPKI repository design [RFC6481] anticipated an hierarchic
organization of repositories as this seriously affects the organization of repositories, as this seriously affects the
performance of the relying parties gathering data. Publishing performance of relying parties gathering data. Publishing parties
parties SHOULD implement hierarchic directory structures. SHOULD implement hierarchic directory structures.
A local relying party valid cache containing all RPKI data may be A local relying party valid cache containing all RPKI data may be
gathered from the global distributed database using the rsync gathered from the global distributed database using the rsync
protocol, [RFC5781], and a validation tool such as rcynic [rcynic]. protocol, [RFC5781], and a validation tool such as rcynic [rcynic].
Validated caches may also be created and maintained from other Validated caches may also be created and maintained from other
validated caches. Network operators SHOULD take maximum advantage of validated caches. Network operators SHOULD take maximum advantage of
this feature to minimize load on the global distributed RPKI this feature to minimize load on the global distributed RPKI
database. Of course, the recipient relying parties SHOULD re- database. Of course, the recipient relying parties SHOULD re-
validate the data. validate the data.
skipping to change at page 10, line 10 skipping to change at page 10, line 10
[rcynic] "rcynic read-me", , <http://subvert-rpki.hactrn.net/rcynic [rcynic] "rcynic read-me", , <http://subvert-rpki.hactrn.net/rcynic
/README>. /README>.
Author's Address Author's Address
Randy Bush Randy Bush
Internet Initiative Japan Internet Initiative Japan
5147 Crystal Springs 5147 Crystal Springs
Bainbridge Island, Washington 98110 Bainbridge Island, Washington 98110
US US
Phone: +1 206 780 0431 x1
Email: randy@psg.com Email: randy@psg.com
 End of changes. 8 change blocks. 
16 lines changed or deleted 18 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/