Enrollment over Secure Transport
draft-ietf-pkix-est-03

The information below is for an old version of the document
Document Type Active Internet-Draft (pkix WG)
Last updated 2012-10-22
Replaces draft-pritikin-est
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
PKIX                                                    M. Pritikin, Ed.
Internet-Draft                                       Cisco Systems, Inc.
Intended status: Standards Track                             P. Yee, Ed.
Expires: April 25, 2013                                     AKAYLA, Inc.
                                                         D. Harkins, Ed.
                                                          Aruba Networks
                                                        October 22, 2012

                    Enrollment over Secure Transport
                         draft-ietf-pkix-est-03

Abstract

   This document profiles certificate enrollment for clients using
   Certificate Management over CMS (CMC) messages over a secure
   transport.  This profile, called Enrollment over Secure Transport
   (EST), describes a simple yet functional certificate management
   protocol targeting Public Key Infrastructure (PKI) clients that need
   to acquire client certificate(s) and associated Certification
   Authority (CA) certificate(s).

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 April 25, 2013.

Copyright Notice

   Copyright (c) 2012 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
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Pritikin, et al.         Expires April 25, 2013                 [Page 1]
Internet-Draft                     EST                      October 2012

   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 . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  5
   2.  Operational Scenario Overviews . . . . . . . . . . . . . . . .  5
     2.1.  Obtaining CA Certificates  . . . . . . . . . . . . . . . .  6
     2.2.  Initial Enrollment . . . . . . . . . . . . . . . . . . . .  7
       2.2.1.  Previously Installed Client Certificate  . . . . . . .  7
       2.2.2.  Username/Password Distributed Out-of-Band  . . . . . .  7
     2.3.  Client Certificate Re-issuance . . . . . . . . . . . . . .  8
       2.3.1.  Re-issuance of Signature Certificates  . . . . . . . .  8
       2.3.2.  Re-issuance of Key Exchange Certificates . . . . . . .  8
     2.4.  Server Key Generation  . . . . . . . . . . . . . . . . . .  8
     2.5.  Full PKI Request messages  . . . . . . . . . . . . . . . .  8
     2.6.  CSR (Certificate Signing Request) Attributes Request . . .  8
   3.  Protocol Design and Layering . . . . . . . . . . . . . . . . .  9
     3.1.  Application Layer Design . . . . . . . . . . . . . . . . . 12
     3.2.  HTTP Layer Design  . . . . . . . . . . . . . . . . . . . . 12
       3.2.1.  HTTP headers for control . . . . . . . . . . . . . . . 12
       3.2.2.  HTTP URIs for control  . . . . . . . . . . . . . . . . 13
       3.2.3.  HTTP-Based Client Authentication . . . . . . . . . . . 14
       3.2.4.  Message types  . . . . . . . . . . . . . . . . . . . . 15
     3.3.  TLS Layer Design . . . . . . . . . . . . . . . . . . . . . 16
       3.3.1.  TLS for transport security . . . . . . . . . . . . . . 17
         3.3.1.1.  TLS-Based Server Authentication  . . . . . . . . . 17
         3.3.1.2.  TLS-Based Client Authentication  . . . . . . . . . 17
         3.3.1.3.  Certificate-less TLS Mutual Authentication . . . . 18
     3.4.  Proof-of-Possession  . . . . . . . . . . . . . . . . . . . 18
     3.5.  Linking Identity and POP information . . . . . . . . . . . 18
   4.  Protocol Exchange Details  . . . . . . . . . . . . . . . . . . 20
     4.1.  Server Authorization . . . . . . . . . . . . . . . . . . . 20
     4.2.  Client Authorization . . . . . . . . . . . . . . . . . . . 20
Show full document text