draft-ietf-sidr-rpki-rtr-03.txt   draft-ietf-sidr-rpki-rtr-04.txt 
Network Working Group R. Bush Network Working Group R. Bush
Internet-Draft IIJ Internet-Draft IIJ
Intended status: Standards Track R. Austein Intended status: Standards Track R. Austein
Expires: May 23, 2011 ISC Expires: May 26, 2011 ISC
November 19, 2010 November 22, 2010
The RPKI/Router Protocol The RPKI/Router Protocol
draft-ietf-sidr-rpki-rtr-03 draft-ietf-sidr-rpki-rtr-04
Abstract Abstract
In order to formally validate the origin ASes of BGP announcements, In order to formally validate the origin ASes of BGP announcements,
routers need a simple but reliable mechanism to receive RPKI routers need a simple but reliable mechanism to receive RPKI
[I-D.ietf-sidr-arch] or analogous prefix origin data from a trusted [I-D.ietf-sidr-arch] or analogous prefix origin data from a trusted
cache. This document describes a protocol to deliver validated cache. This document describes a protocol to deliver validated
prefix origin data to routers over ssh. prefix origin data to routers over ssh.
Requirements Language Requirements Language
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 May 23, 2011. This Internet-Draft will expire on May 26, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 2, line 39 skipping to change at page 2, line 39
5.1. Start or Restart . . . . . . . . . . . . . . . . . . . . . 11 5.1. Start or Restart . . . . . . . . . . . . . . . . . . . . . 11
5.2. Typical Exchange . . . . . . . . . . . . . . . . . . . . . 12 5.2. Typical Exchange . . . . . . . . . . . . . . . . . . . . . 12
5.3. No Incremental Update Available . . . . . . . . . . . . . 13 5.3. No Incremental Update Available . . . . . . . . . . . . . 13
5.4. Cache has No Data Available . . . . . . . . . . . . . . . 13 5.4. Cache has No Data Available . . . . . . . . . . . . . . . 13
6. SSH Transport . . . . . . . . . . . . . . . . . . . . . . . . 14 6. SSH Transport . . . . . . . . . . . . . . . . . . . . . . . . 14
7. Router-Cache Set-Up . . . . . . . . . . . . . . . . . . . . . 14 7. Router-Cache Set-Up . . . . . . . . . . . . . . . . . . . . . 14
8. Deployment Scenarios . . . . . . . . . . . . . . . . . . . . . 16 8. Deployment Scenarios . . . . . . . . . . . . . . . . . . . . . 16
9. Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . 16 9. Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . 16
10. Security Considerations . . . . . . . . . . . . . . . . . . . 17 10. Security Considerations . . . . . . . . . . . . . . . . . . . 17
11. Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 11. Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
14.1. Normative References . . . . . . . . . . . . . . . . . . . 19 14.1. Normative References . . . . . . . . . . . . . . . . . . . 19
14.2. Informative References . . . . . . . . . . . . . . . . . . 19 14.2. Informative References . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
In order to formally validate the origin ASes of BGP announcements, In order to formally validate the origin ASes of BGP announcements,
routers need a simple but reliable mechanism to receive RPKI routers need a simple but reliable mechanism to receive RPKI
skipping to change at page 17, line 18 skipping to change at page 17, line 18
2: No Data Available: The cache believes itself to be in good 2: No Data Available: The cache believes itself to be in good
working order, but is unable to answer either a Serial Query or a working order, but is unable to answer either a Serial Query or a
Reset Query because it has no useful data available at this time. Reset Query because it has no useful data available at this time.
This is likely to be a temporary error, and most likely indicates This is likely to be a temporary error, and most likely indicates
that the cache has not yet completed pulling down an initial that the cache has not yet completed pulling down an initial
current data set from the global RPKI system after some kind of current data set from the global RPKI system after some kind of
event that invalidated whatever data it might have previously held event that invalidated whatever data it might have previously held
(reboot, network partition, etcetera). (reboot, network partition, etcetera).
3: Invalid Request: The cache server believes the client's request
to be invalid.
10. Security Considerations 10. Security Considerations
As this document describes a security protocol, many aspects of As this document describes a security protocol, many aspects of
security interest are described in the relevant sections. This security interest are described in the relevant sections. This
section points out issues which may not be obvious in other sections. section points out issues which may not be obvious in other sections.
Cache Validation: In order for a collection of caches as described Cache Validation: In order for a collection of caches as described
in Section 8 to guarantee a consistent view, they need to be given in Section 8 to guarantee a consistent view, they need to be given
consistent trust anchors to use in their internal validation consistent trust anchors to use in their internal validation
process. Distribution of a consistent trust anchor is assumed to process. Distribution of a consistent trust anchor is assumed to
 End of changes. 5 change blocks. 
5 lines changed or deleted 8 lines changed or added

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