Resource Public Key Infrastructure (RPKI) Trust Anchor Locator
draft-ietf-sidrops-https-tal-08
Network Working Group G. Huston
Internet-Draft APNIC
Obsoletes: 7730 (if approved) S. Weiler
Intended status: Standards Track W3C/MIT
Expires: November 1, 2019 G. Michaelson
APNIC
S. Kent
Unaffiliated
T. Bruijnzeels
NLnet Labs
April 30, 2019
Resource Public Key Infrastructure (RPKI) Trust Anchor Locator
draft-ietf-sidrops-https-tal-08
Abstract
This document defines a Trust Anchor Locator (TAL) for the Resource
Public Key Infrastructure (RPKI). TALs allow Relying Parties in the
RPKI to download the current Trust Anchor (TA) CA certificate from
one or more locations, and verify that the key of this self-signed
certificate matches the key on the TAL. Thus, Relying Parties can be
configured with TA keys, but allow these TAs to change the content of
their CA certificate. In particular it allows TAs to change the set
of IP Address Delegations and/or Autonomous System Identifier
Delegations included in the RFC3779 extension of their certificate.
This document obsoletes the previous definition of Trust Anchor
Locators in RFC 7730 by adding support for RFC3986 Uniform Resource
Identifiers (URIs) that use HTTPS as the scheme.
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 https://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 November 1, 2019.
Huston, et al. Expires November 1, 2019 [Page 1]
Internet-Draft https-tals April 2019
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://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. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Changes from RFC7730 . . . . . . . . . . . . . . . . . . 3
2. Trust Anchor Locator . . . . . . . . . . . . . . . . . . . . 3
2.1. Trust Anchor Locator Motivation . . . . . . . . . . . . . 3
2.2. Trust Anchor Locator File Format . . . . . . . . . . . . 4
2.3. TAL and Trust Anchor Certificate Considerations . . . . . 4
2.4. Example . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Relying Party Use . . . . . . . . . . . . . . . . . . . . . . 6
4. URI Scheme Considerations . . . . . . . . . . . . . . . . . . 7
5. Security Considerations . . . . . . . . . . . . . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
8.1. Normative References . . . . . . . . . . . . . . . . . . 9
8.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
This document defines a Trust Anchor Locator (TAL) for the Resource
Public Key Infrastructure (RPKI) [RFC6480]. This format may be used
to distribute trust anchor material using a mix of out-of-band and
online means. Procedures used by Relying Parties (RPs) to verify
RPKI signed objects SHOULD support this format to facilitate
interoperability between creators of trust anchor material and RPs.
Show full document text