Network Working Group R. Gagliano
Internet-Draft Cisco Systems
Updates: RFC 6490 (if approved) T. Manderson
Intended status: Standards Track ICANN
Expires: August 29, 2013 C. Martinez
LACNIC
February 25, 2013
Multiple Repository Publication Points support in the Resource Public
Key Infrastructure (RPKI)
draft-rogaglia-sidr-multiple-publication-points-02
Abstract
The Resource Public Key Infrastructure (RPKI) depends on Relying
Parties (RP) ability to access its Trust Anchors' certificate
specified in the different "Trust Anchor Locator (TAL)" files and the
Repository Objects located at the Certificate Authorities (CA)
repositories hosted in its respective publication point. This
document updates [RFC6490] by allowing multiple URI associated to a
single public key in a TAL file and introduces the concept of
multiple repository publication point operators for every CA in the
RPKI. This document provides also recommendation for the RP behavior
when analyzing signed objects that include multiple publications
points.
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 August 29, 2013.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
Gagliano, et al. Expires August 29, 2013 [Page 1]
Internet-Draft RPKI Multiple Operators February 2013
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 notation . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Multiple Operators support in TAL files . . . . . . . . . . . 6
3.1. Update to RFC 6490 Section 2.1 . . . . . . . . . . . . . . 6
3.2. Rules for Relying Parties (RP) . . . . . . . . . . . . . . 7
4. Multiple Operators support in Certificates . . . . . . . . . . 8
4.1. Rules for Relying Parties (RP) . . . . . . . . . . . . . . 8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
8. Normative References . . . . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13
Gagliano, et al. Expires August 29, 2013 [Page 2]
Internet-Draft RPKI Multiple Operators February 2013
1. Requirements notation
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 [RFC2119].
Gagliano, et al. Expires August 29, 2013 [Page 3]
Internet-Draft RPKI Multiple Operators February 2013
2. Introduction
The RPKI repository system described in [RFC6481] requires
scalability and diversity in order to address challenges such as
Distributed Denial of Service (DDoS) attacks, to secure the
datatracker.ietf.org