TEAP Update and Extensions for Bootstrapping
draft-lear-eap-teap-brski-05

Document Type Active Internet-Draft (individual)
Last updated 2019-11-03
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
On Agenda emu at IETF-106
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                            E. Lear
Internet-Draft                                                  O. Friel
Updates: RFC7170 (if approved)                             N. Cam-Winget
Intended status: Standards Track                           Cisco Systems
Expires: May 4, 2020                                          D. Harkins
                                                           HP Enterprise
                                                       November 01, 2019

              TEAP Update and Extensions for Bootstrapping
                      draft-lear-eap-teap-brski-05

Abstract

   In certain environments, in order for a device to establish any layer
   three communications, it is necessary for that device to be properly
   credentialed.  This is a relatively easy problem to solve when a
   device is associated with a human being and has both input and
   display functions.  It is less easy when the human, input, and
   display functions are not present.  To address this case, this memo
   specifies extensions to the Tunnel Extensible Authentication Protocol
   (TEAP) method that leverages Bootstrapping Remote Secure Key
   Infrastructures (BRSKI) in order to provide a credential to a device
   at layer two.  The basis of this work is that a manufacturer will
   introduce the device and the local deployment through cryptographic
   means.  In this sense the same trust model as BRSKI is used.

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 May 4, 2020.

Lear, et al.               Expires May 4, 2020                  [Page 1]
Internet-Draft         TEAP Update and Extensions          November 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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  TEAP BRSKI Architecture . . . . . . . . . . . . . . . . . . .   4
   3.  BRSKI Bootstrap and Enroll Operation  . . . . . . . . . . . .   4
     3.1.  Discovery of Trusted MASA . . . . . . . . . . . . . . . .   5
     3.2.  Executing BRSKI in a TEAP Tunnel  . . . . . . . . . . . .   5
   4.  PKI Certificate Considerations  . . . . . . . . . . . . . . .   9
     4.1.  TEAP Tunnel Establishment . . . . . . . . . . . . . . . .   9
     4.2.  BRSKI Trust Establishment . . . . . . . . . . . . . . . .  11
     4.3.  Certificate Expiration Times  . . . . . . . . . . . . . .  12
     4.4.  LDevID Subject and Subject Alternative Names  . . . . . .  12
     4.5.  PKCS#10 Retry Handling  . . . . . . . . . . . . . . . . .  13
   5.  Peer Identity . . . . . . . . . . . . . . . . . . . . . . . .  13
   6.  Channel and Crypto Binding  . . . . . . . . . . . . . . . . .  14
   7.  Protocol Flows  . . . . . . . . . . . . . . . . . . . . . . .  14
     7.1.  TEAP Server Grants Access . . . . . . . . . . . . . . . .  14
     7.2.  TEAP Server Instructs Client to Perform BRSKI Flow  . . .  16
     7.3.  TEAP Server Instructs Client to Reenroll  . . . . . . . .  20
     7.4.  Out of Band Reenroll  . . . . . . . . . . . . . . . . . .  22
   8.  TEAP TLV Formats  . . . . . . . . . . . . . . . . . . . . . .  22
     8.1.  New TLVs  . . . . . . . . . . . . . . . . . . . . . . . .  22
       8.1.1.  BRSKI-RequestVoucher TLV  . . . . . . . . . . . . . .  23
       8.1.2.  BRSKI-Voucher TLV . . . . . . . . . . . . . . . . . .  23
       8.1.3.  CSR-Attributes TLV  . . . . . . . . . . . . . . . . .  24
       8.1.4.  Retry-After TLV . . . . . . . . . . . . . . . . . . .  25
       8.1.5.  NAI TLV . . . . . . . . . . . . . . . . . . . . . . .  25
     8.2.  Existing TEAP TLV Specifications  . . . . . . . . . . . .  26
Show full document text