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

Document Type Active Internet-Draft (sidrops WG)
Last updated 2020-01-15
Replaces draft-tbruijnzeels-sidrops-signed-tal
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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                                        C. Martinez
Internet-Draft                                                    LACNIC
Intended status: Standards Track                           G. Michaelson
Expires: July 19, 2020                                       T. Harrison
                                                                   APNIC
                                                          T. Bruijnzeels
                                                              NLnet Labs
                                                              R. Austein
                                                    Dragon Research Labs
                                                        January 16, 2020

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

Abstract

   A Trust Anchor Locator (TAL) [I-D.ietf-sidrops-https-tal] is used by
   Relying Parties (RP) in the RPKI to locate and validate a Trust
   Anchor (TA) CA certificate used in RPKI validation.  This document
   defines an RPKI signed object for a set of Trust Anchor Keys (TAK),
   that can be used by TA creators and publishers to signal their set of
   current keys and the location(s) of the accompanying CA certificates
   to RPs, 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 July 19, 2020.

Martinez, et al.          Expires July 19, 2020                 [Page 1]
Internet-Draft         RPKI signed object for TAL           January 2020

Copyright Notice

   Copyright (c) 2020 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.  Requirements notation . . . . . . . . . . . . . . . . . . . .   3
   2.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  TAK Object definition . . . . . . . . . . . . . . . . . . . .   4
     3.1.  The TAK Object Content Type . . . . . . . . . . . . . . .   4
     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.  TAK Object Generation and Publication . . . . . . . . . . . .   6
   5.  Relying Party Use . . . . . . . . . . . . . . . . . . . . . .   8
   6.  Maintaining multiple TA keys  . . . . . . . . . . . . . . . .   9
   7.  Performing TA Key Rolls . . . . . . . . . . . . . . . . . . .  10
     7.1.  Phase 1: Add a TAK for Key 'A'  . . . . . . . . . . . . .  10
     7.2.  Phase 2: Add a Key 'B'  . . . . . . . . . . . . . . . . .  11
     7.3.  Phase 3: Roll to Key 'C'  . . . . . . . . . . . . . . . .  11
       7.3.1.  Planned Direction Roll  . . . . . . . . . . . . . . .  11
       7.3.2.  Unplanned Direction Roll  . . . . . . . . . . . . . .  12
     7.4.  Phase X: Roll to Key 'D', 'E', .. . . . . . . . . . . . .  12
   8.  Deployment Considerations . . . . . . . . . . . . . . . . . .  12
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
     10.1.  OID  . . . . . . . . . . . . . . . . . . . . . . . . . .  13
     10.2.  File Extension . . . . . . . . . . . . . . . . . . . . .  13
   11. Security Considerations . . . . . . . . . . . . . . . . . . .  13
   12. Revision History  . . . . . . . . . . . . . . . . . . . . . .  13
   13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  14
Show full document text