RPKI Multiple "All Resources" Trust Anchors Applicability Statement
draft-rir-rpki-allres-ta-app-statement-02
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-09-13
(latest revision 2017-07-18)
|
|
Replaces |
|
draft-nro-rpki-ta-app-statement
|
|
Stream |
|
ISE
|
|
Intended RFC status |
|
Informational
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
ISE state
|
|
Response to Review Needed
Awaiting Reviews, Revised I-D Needed
|
|
Consensus Boilerplate |
|
Unknown
|
|
Document shepherd |
|
No shepherd assigned
|
|
Shepherd write-up |
|
Show
(last changed 2017-09-04)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
Nevil Brownlee <rfc-ise@rfc-editor.org>
|
Internet Engineering Task Force A. Newton, Ed.
Internet-Draft ARIN
Intended status: Informational C. Martinez-Cagnazzo, Ed.
Expires: January 19, 2018 LACNIC
D. Shaw
AFRINIC
T. Bruijnzeels
RIPE NCC
B. Ellacott
APNIC
July 18, 2017
RPKI Multiple "All Resources" Trust Anchors Applicability Statement
draft-rir-rpki-allres-ta-app-statement-02
Abstract
This document provides an applicability statement for the use of
multiple, over-claiming 'all resources' (0/0) RPKI certificate
authorities (CA) certificates used as trust anchors (TAs) operated by
the Regional Internet Registry community to help mitigate the risk of
massive downstream invalidation in the case of transient registry
inconsistencies.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 19, 2018.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
Newton, et al. Expires January 19, 2018 [Page 1]
Internet-Draft RPKI 0/0 TA Applicability Statement July 2017
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Requirements Language . . . . . . . . . . . . . . . . . . . . 2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Applicability to reduce overclaiming possibilities . . . . . 3
4. Normative References . . . . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
2. Introduction
The RPKI is a hierarchical cryptologic system that uses X.509
certificates to match and validate holdership of Internet number
resources. This validation follows the allocation change from IANA
to an RIR, to an NIR or LIR, and ending with end users who make use
of the address block. Since these allocations can be
cryptographically validated, this can then be tied to assertions made
by the holder of those number resources. As an improvement of this
system, the RPKI was updated to add validation of origin routing
announcements via ROAs. These ROAs can then be independently and
cryptographically validated by third parties to assure themselves
that the origin of the announcement as seen in the actual routing
system is valid.
Since this system is envisioned to be used by network operators and
ISPs to determine their routing decisions, there is a goal to be 100%
correct 100% of the time. This goal could be achieved if the system
was contained in a static environment where there is little or no
movement of holdership changes from one organization to another of
number resources. Unfortunately, this state cannot be achieved
Show full document text