RPKI Signed Object for Trust Anchor Keys
draft-ietf-sidrops-signed-tal-02

Document Type Active Internet-Draft (sidrops WG)
Last updated 2018-11-05 (latest revision 2018-10-19)
Replaces draft-tbruijnzeels-sidrops-signed-tal
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state In WG Last Call
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                     T. Bruijnzeels
Internet-Draft                                                NLnet Labs
Intended status: Standards Track                             C. Martinez
Expires: April 19, 2019                                           LACNIC
                                                              R. Austein
                                                    Dragon Research Labs
                                                        October 16, 2018

                RPKI Signed Object for Trust Anchor Keys
                    draft-ietf-sidrops-signed-tal-02

Abstract

   Trust Anchor Locators (TALs) [I-D.ietf-sidrops-https-tal] are used by
   Relying Parties in the RPKI to locate and validate Trust Anchor
   certificates used in RPKI validation.  This document defines an RPKI
   signed object for Trust Anchor Keys (TAK), that can be used by Trust
   Anchors to signal their set of current keys and the location(s) of
   the accompanying CA certiifcates to Relying Parties, as well as
   changes to this set in the form of revoked keys and new keys, in
   order to support both planned and unplanned key rolls without
   impacting RPKI validation.

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 April 19, 2019.

Copyright Notice

   Copyright (c) 2018 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

Bruijnzeels, et al.      Expires April 19, 2019                 [Page 1]
Internet-Draft         RPKI signed object for TAL           October 2018

   (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.  Requirements notation . . . . . . . . . . . . . . . . . . . .   3
   2.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  TAK Object definition . . . . . . . . . . . . . . . . . . . .   4
     3.1.  The TAK Object Content Type . . . . . . . . . . . . . . .   5
     3.2.  The TAK Object eContent . . . . . . . . . . . . . . . . .   5
       3.2.1.  version . . . . . . . . . . . . . . . . . . . . . . .   5
       3.2.2.  current . . . . . . . . . . . . . . . . . . . . . . .   5
       3.2.3.  revoked . . . . . . . . . . . . . . . . . . . . . . .   6
     3.3.  TAK Object Validation . . . . . . . . . . . . . . . . . .   6
   4.  Maintaining multiple TA keys  . . . . . . . . . . . . . . . .   7
     4.1.  Prepare a new TA key  . . . . . . . . . . . . . . . . . .   7
     4.2.  Publishing for Multiple TA Keys . . . . . . . . . . . . .   7
   5.  TAK Object Generation and Publication . . . . . . . . . . . .   8
   6.  Performing TA Key Rolls . . . . . . . . . . . . . . . . . . .   9
     6.1.  Opting in to Key Rolls  . . . . . . . . . . . . . . . . .  10
       6.1.1.  Trust Anchor  . . . . . . . . . . . . . . . . . . . .  10
       6.1.2.  Relying Parties . . . . . . . . . . . . . . . . . . .  12
     6.2.  Pre-stage a New Key . . . . . . . . . . . . . . . . . . .  12
       6.2.1.  Trust Anchor  . . . . . . . . . . . . . . . . . . . .  12
       6.2.2.  Relying Parties . . . . . . . . . . . . . . . . . . .  14
     6.3.  Planned Key Revocation  . . . . . . . . . . . . . . . . .  14
       6.3.1.  Trust Anchor  . . . . . . . . . . . . . . . . . . . .  14
       6.3.2.  Relying Parties . . . . . . . . . . . . . . . . . . .  17
     6.4.  Unplanned revocation  . . . . . . . . . . . . . . . . . .  17
       6.4.1.  Trust Anchor  . . . . . . . . . . . . . . . . . . . .  17
   7.  Deployment Considerations . . . . . . . . . . . . . . . . . .  18
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
     8.1.  OID . . . . . . . . . . . . . . . . . . . . . . . . . . .  18
     8.2.  File Extension  . . . . . . . . . . . . . . . . . . . . .  19
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  19
Show full document text