TLS Authentication using IEEE 1609.2 certificate
draft-msahli-ise-ieee1609-03

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Authors Mounira Msahli  , Nancy Cam-Winget  , Ahmed Serhrouchni  , Houda Labiod  , William Whyte 
Last updated 2020-01-19 (latest revision 2019-11-17)
Replaces draft-msahli-ipwave-extension-ieee1609
Stream ISE
Intended RFC status Experimental
Formats pdf htmlized (tools) htmlized bibtex
IETF conflict review conflict-review-msahli-ise-ieee1609
Stream ISE state Response to Review Needed
Consensus Boilerplate Unknown
Document shepherd Adrian Farrel
Shepherd write-up Show (last changed 2019-11-24)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to Adrian Farrel <rfc-ise@rfc-editor.org>
IANA IANA review state IANA OK - Actions Needed
IANA expert review state Expert Reviews OK
Network Working Group                                     M. Msahli, Ed.
Internet-Draft                                             Telecom Paris
Intended status: Experimental                         N. Cam-Winget, Ed.
Expires: May 20, 2020                                              Cisco
                                                     A. Serhrouchni, Ed.
                                                        H.  Labiod , Ed.
                                                           Telecom Paris
                                                           W. Whyte, Ed.
                                                                Qualcomm
                                                       November 17, 2019

            TLS Authentication using IEEE 1609.2 certificate
                      draft-msahli-ise-ieee1609-03

Abstract

   The IEEE and ETSI have specified end-entity certificates.  This
   docment defines an experimental change to TLS to support IEEE/ETSI
   certificate types to authenticate TLS entities.

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 20, 2020.

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

Msahli, et al.            Expires May 20, 2020                  [Page 1]
Internet-Draft   IEEE and ETSI Certificate Types for TLS   November 2019

   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.  Experiment Overview . . . . . . . . . . . . . . . . . . .   4
   2.  Requirements Terminology  . . . . . . . . . . . . . . . . . .   4
   3.  Extension Overview  . . . . . . . . . . . . . . . . . . . . .   4
   4.  TLS Client and Server Handshake . . . . . . . . . . . . . . .   5
     4.1.  Client Hello  . . . . . . . . . . . . . . . . . . . . . .   7
     4.2.  Server Hello  . . . . . . . . . . . . . . . . . . . . . .   7
   5.  Certificate Verification  . . . . . . . . . . . . . . . . . .   8
   6.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   9
     6.1.  TLS Server and TLS Client use the 1609Dot2 Certificate  .   9
     6.2.  TLS Client uses the IEEE 1609.2 certificate and TLS
           Server uses the X.509 certificate . . . . . . . . . . . .  10
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
     7.1.  Securely Obtaining Certificates from an Online Repository  11
     7.2.  Expiry of Certificates  . . . . . . . . . . . . . . . . .  11
     7.3.  Algorithms and Cryptographic Strength . . . . . . . . . .  11
     7.4.  Interpreting ITS Certificate Permissions  . . . . . . . .  11
     7.5.  Psid and Pdufunctionaltype in Certificateverify . . . . .  12
   8.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  13
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  13
   11. Normative References  . . . . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

   The TLS protocol [RFC8446] [RFC5246] uses X.509 certificates and Raw
   Public Key in order to authenticate servers and clients.  This
   document describes an experimental extension following the [RFC7250]
   to support use of the certificate format specified by the IEEE in
   [IEEE1609.2] and profiled by the European Telecommunications
   Standards Institute (ETSI) in [TS103097].  These standards specify
   secure communications in vehicular environments.  These certificates
   are referred to in this document as Intelligent Transportation
   Systems (ITS) Certificates.

   The certificate types are optimized for bandwidth and processing time
   to support delay-sensitive applications, and also to provide both
Show full document text