draft-ietf-sidr-origin-ops-14.txt   draft-ietf-sidr-origin-ops-15.txt 
Network Working Group R. Bush Network Working Group R. Bush
Internet-Draft Internet Initiative Japan Internet-Draft Internet Initiative Japan
Intended status: BCP March 8, 2012 Intended status: BCP March 10, 2012
Expires: September 9, 2012 Expires: September 11, 2012
RPKI-Based Origin Validation Operation RPKI-Based Origin Validation Operation
draft-ietf-sidr-origin-ops-14 draft-ietf-sidr-origin-ops-15
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 them. considerations. This document attempts to collect and present them.
It is expected to evolve as RPKI-based origin validation is deployed It is expected to evolve as RPKI-based origin validation is deployed
and the dynamics are better understood. and the dynamics are better understood.
Requirements Language Requirements Language
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 September 9, 2012. This Internet-Draft will expire on September 11, 2012.
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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 6, line 9 skipping to change at page 6, line 9
the work to manage the relevant certificates and ROAs. Operators the work to manage the relevant certificates and ROAs. Operators
SHOULD offer to provision the RPKI data for these customers just as SHOULD offer to provision the RPKI data for these customers just as
they provision many other things for them. they provision many other things for them.
While an operator using RPKI data MAY choose any polling frequency While an operator using RPKI data MAY choose any polling frequency
they wish for ensuring they have a fresh RPKI cache. However, if they wish for ensuring they have a fresh RPKI cache. However, if
they use RPKI data as an input to operational routing decisions, they they use RPKI data as an input to operational routing decisions, they
SHOULD ensure local caches inside their AS are synchronized with each SHOULD ensure local caches inside their AS are synchronized with each
other at least every four to six hours. other at least every four to six hours.
Operators should use tools which warn them of any impending ROA or
certificate expiry which could affect the validity of their own data.
Ghostbuster Records, see [RFC6493], can be used to facilitate contact
with upstream CAs to effect repair.
4. Within a Network 4. Within a Network
Origin validation need only be done by edge routers in a network, Origin validation need only be done by edge routers in a network,
those which border other networks/ASs. those which border other networks/ASs.
A validating router will use the result of origin validation to A validating router will use the result of origin validation to
influence local policy within its network, see Section 5. In influence local policy within its network, see Section 5. In
deployment this policy should fit into the AS's existing policy, deployment this policy should fit into the AS's existing policy,
preferences, etc. This allows a network to incrementally deploy preferences, etc. This allows a network to incrementally deploy
validation-capable border routers. validation-capable border routers.
 End of changes. 4 change blocks. 
4 lines changed or deleted 9 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/