TLS Authentication using IEEE 1609.2 certificates
draft-msahli-ipwave-extension-ieee1609-00

Document Type Active Internet-Draft (individual)
Last updated 2019-04-02
Replaces draft-tls-certieee1609
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)
IPWAVE                                                    M. Msahli, Ed.
Internet-Draft                                         Telecom ParisTech
Intended status: Informational                        P. Kampanakis, Ed.
Expires: September 29, 2019                                        Cisco
                                                          March 28, 2019

           TLS Authentication using IEEE 1609.2 certificates
             draft-msahli-ipwave-extension-ieee1609-03.txt

Abstract

   This document specifies the use of a new certificate type to
   authenticate TLS entities.  The first type enables the use of a
   certificate specified by the IEEE and the European Telecommunications
   Standards Institute (ETSI).

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 September 29, 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.

Msahli & Kampanakis    Expires September 29, 2019               [Page 1]
Internet-Draft   IEEE and ETSI Certificate Types for TLS      March 2019

Table of Contents

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

1.  Introduction

   The TLS protocol [RFC8446] [RFC5246] uses X509 and Raw Public Key in
   order to authenticate servers and clients.  This document describes
   the use of the certificate 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.  The certificate types are optimized for
   bandwidth and processing time to support delay-sensitive
   applications, and also provide both authentication and authorization
   information to enable fast access control decisions in ad hoc
   networks such as are found in Intelligent Transportation System
   (ITS).  The extension is following the [RFC6066].

2.  Requirements Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

3.  Extension Overview

   This specification extends the Client Hello and Server Hello
   messages, by using the "extension_data" field of the ClientCertType
   Extension and the ServerCertType Extension structures defined in
Show full document text