Considerations For Using Short Term Certificates
draft-nir-saag-star-00

Document Type Active Internet-Draft (individual)
Last updated 2017-10-15
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
SAAG                                                              Y. Nir
Internet-Draft                                                  Dell EMC
Intended status: Informational                                T. Fossati
Expires: April 17, 2018                                            Nokia
                                                              Y. Sheffer
                                                                  Intuit
                                                        October 14, 2017

            Considerations For Using Short Term Certificates
                         draft-nir-saag-star-00

Abstract

   Recently there has been renewed interest in an old idea: Issue
   certificates with short validity periods and forego revocation
   processing, reasoning that expiration is a sufficient replacement for
   revocation as long as that expiration is not too far off.

   This document covers considerations, both security and operational,
   for using such Short Term Auto Renewed (STAR) certificates for
   various scenarios where Using a revocation protocol is considered
   inappropriate.

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 17, 2018.

Copyright Notice

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

Nir, et al.              Expires April 17, 2018                 [Page 1]
Internet-Draft              STAR Certificates               October 2017

   (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.  Conventions Used in This Document . . . . . . . . . . . .   3
   2.  Short Term Auto Renewed Certificates  . . . . . . . . . . . .   4
     2.1.  Alternative Design: OCSP Stapling . . . . . . . . . . . .   5
   3.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Data Center Network Hosts . . . . . . . . . . . . . . . .   5
     3.2.  Distributed System Installed in One Or More Data Centers    5
       3.2.1.  Distributed Network Security Functions  . . . . . . .   5
     3.3.  Certificate Delegation for Content Delivery Networks  . .   6
   4.  Operational Considerations  . . . . . . . . . . . . . . . . .   6
     4.1.  Certificate Lifetime and Renewal Schedule . . . . . . . .   6
     4.2.  Availability of the Certificate Authority . . . . . . . .   7
     4.3.  Clock Skew and the notBefore Field  . . . . . . . . . . .   7
     4.4.  Automatic Renewal . . . . . . . . . . . . . . . . . . . .   8
     4.5.  Certificate Transparency  . . . . . . . . . . . . . . . .   9
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
     5.1.  Reasons for Revocation  . . . . . . . . . . . . . . . . .  10
     5.2.  Longevity and Revocation  . . . . . . . . . . . . . . . .  10
     5.3.  Clock Skew and Security . . . . . . . . . . . . . . . . .  11
     5.4.  CA availability . . . . . . . . . . . . . . . . . . . . .  11
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   Certificates ([RFC5280]) are used in multiple protocols such as the
   Internet Key Exchange (IKEv2-[RFC7296]) and the Transport Layer
   Security protocol (TLS-[RFC5246]).  Certificates are used to
   authenticate communicating parties to each other.  Certificates are
   issued by Certificate Authorities (CAs) to End Entities (EE) to be
   used to authenticate them to Relying Parties (RPs) in security
   protocols.  Systems that use secure communications typically include
Show full document text