Internet-Draft submission

idnits 2.16.02 

/a/www/www6s/staging/draft-msahli-tls-extension-ieee1609-02.txt:

  Showing Errors (**), Flaws (~~), Warnings (==), and Comments (--).
  Errors MUST be fixed before draft submission.  Flaws SHOULD be fixed before draft submission.

  Checking boilerplate required by RFC 5378 and the IETF Trust (see
  https://trustee.ietf.org/license-info):
  ----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
  ----------------------------------------------------------------------------

     No issues found here.

  Running in submission checking mode -- *not* checking nits according to
  https://www.ietf.org/id-info/checklist .
  ----------------------------------------------------------------------------


     No nits found.

TLS Working Group                                         M. Msahli, Ed.
Internet-Draft                                         Telecom ParisTech
Intended status: Informational                        P. Kampanakis, Ed.
Expires: August 24, 2019                                           Cisco
                                                          H. Labiod, Ed.
                                                       Telecom ParisTech
                                                      N. Cam-Winget, Ed.
                                                                   Cisco
                                                     A. Serhrouchni, Ed.
                                                       Telecom ParisTech
                                                           W. Whyte, Ed.
                                                        Onboard Security
                                                       February 20, 2019


 TLS Authentication using ETSI TS 103 097 and IEEE 1609.2 certificates
               draft-msahli-tls-extension-ieee1609-02.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 August 24, 2019.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.





Msahli, et al.           Expires August 24, 2019                [Page 1]
Internet-Draft   IEEE and ETSI Certificate Types for TLS   February 2019


   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Terminology  . . . . . . . . . . . . . . . . . .   3
   3.  Extension Overview  . . . . . . . . . . . . . . . . . . . . .   3
   4.  TLS Client and Server Handshake . . . . . . . . . . . . . . .   4
     4.1.  Client Hello  . . . . . . . . . . . . . . . . . . . . . .   5
     4.2.  Server Hello  . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Certificate Verification  . . . . . . . . . . . . . . . . . .   7
   6.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  TLS Server and TLS Client use the 1609Dot2 Certificate  .   7
     6.2.  TLS Client uses the IEEE 1609.2 certificate and TLS
           Server uses the X 509 certificate . . . . . . . . . . . .   8
   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
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

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].






Msahli, et al.           Expires August 24, 2019                [Page 2]