TLS 1.3 Authentication using ETSI TS 103 097 and IEEE 1609.2 certificates
draft-tls-certieee1609-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2018-08-20 (latest revision 2018-03-21)
Replaces draft-serhrouchni-tls-certieee1609
Stream (None)
Intended RFC status (None)
Formats plain text 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)
TLS Working Group                                     P. Kampanakis, Ed.
Internet-Draft                                                     Cisco
Intended status: Informational                            M. Msahli, Ed.
Expires: February 19, 2019                             Telecom ParisTech
                                                         August 18, 2018

      TLS 1.3 Authentication using ETSI TS 103 097 and IEEE 1609.2
                              certificates
                     draft-tls-certieee1609-01.txt

Abstract

   This document specifies the use of two new certificate types to
   authenticate TLS entities.  The first type enables the use of a
   certificate specified by the Institute of Electrical and Electronics
   Engineers (IEEE) [IEEE1609.2] and the second by the European
   Telecommunications Standards Institute (ETSI) [TS103097].

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 February 19, 2019.

Copyright Notice

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

Kampanakis & Msahli     Expires February 19, 2019               [Page 1]
Internet-Draft   IEEE and ETSI Certificate Types for TLS     August 2018

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Terminology  . . . . . . . . . . . . . . . . . .   3
   3.  Extension Overview  . . . . . . . . . . . . . . . . . . . . .   3
   4.  Message Flow  . . . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Client Hello  . . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  Server Hello  . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Certificate Verification  . . . . . . . . . . . . . . . . . .   6
     5.1.  IEEE 1609.2 certificates  . . . . . . . . . . . . . . . .   6
     5.2.  ETSI TS 103 097 certificates  . . . . . . . . . . . . . .   6
   6.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  TLS Server and TLS Client use the 1609Dot2 Certificate  .   7
     6.2.  TLS Server uses the IEEE 1609.2 certificate and TLS
           Client uses the X 509 certificate . . . . . . . . . . . .   7
     6.3.  TLS Server uses the IEEE 1609.2 certificate and TLS
           Client uses the ETSI TS 103097 certificate  . . . . . . .   8
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   8.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   9
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     11.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Appendix A.  Co-Authors . . . . . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   At present, TLS 1.3 protocol [RFC8446] uses X509 and Raw Public Key
   in order to authenticate servers and clients.  This document
   describes the use of certificates specified either by the Institute
   of Electrical and Electronics Engineers (IEEE) [IEEE1609.2] or the
   European Telecommunications Standards Institute (ETSI) [TS103097].
   These standards are defined in order to secure communications in
   vehicular environments.  Existing authentication methods, such as
   X509 and Raw Public Key, are designed for Internet use, particularly
   for flexibility and extensibility, and are not optimized for
   bandwidth and processing time to support delay-sensitive
   applications.  This is why size-optimized certificates that meet the
   ITS requirements were designed and standardized.
Show full document text