Security Problem statement for IP Wireless Access in Vehicular Environments
draft-qi-its-v2vauth-01

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
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)
IPwave Working Group                                          Minpeng Qi
Internet-Draft                                              China Mobile
Intended Status: Informational
Expires: April 30, 2017                                 October 31, 2016 
                                                            

  Security Problem statement for IP Wireless Access in Vehicular Environments
                      draft-qi-its-v2vauth-01

Abstract

   This document specifies security problem about IP wireless access in 
   vehicular environment. It also analyses the authentication part in 
   IPsec/TLS. It proposes a new solution to make IPsec/TLS more fit for
   vehicular environment.

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

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

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright and License Notice

   Copyright (c) 2014 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
   (http://trustee.ietf.org/license-info) in effect on the date of

Minpeng Qi                 Expires April 30, 2017               [Page 1]

Internet-Draft  Security Problem Statement for IPwave    October 31, 2016

   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  IPsec/TLS with Pre-shared key . . . . . . . . . . . . . . . . .  3
   3  IPsec/TLS with certificate  . . . . . . . . . . . . . . . . . .  3
   4  Possible Solution   . . . . . . . . . . . . . . . . . . . . . .  4
   5  Security Consideration  . . . . . . . . . . . . . . . . . . . .  5
   6. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . .  5
   7  References  . . . . . . . . . . . . . . . . . . . . . . . . . .  5
   Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . .  5

   

   

   

   

Minpeng Qi                 Expires April 30, 2017                [Page 2]

Internet-Draft  Security Problem Statement for IPwave     October 31, 2016

1  Introduction

   Under IPwave scenario, a vehicle node usually connects other nodes by 
   using an IP address. The other node could be another vehicle, or a 
   server/infrastructure node with IP address. In this case, communication
   data could be eavesdropped, modified or forged by the attacker as same 
   as attacks happened in other IP connection. Therefore, security channel
   between two nodes like IPsec/TLS are also needed in IPwave to ensure 
   the safety of data transmission. As a result, pre-shared key or 
   certificate are involved when IPsec/TLS tunnel are established.
   However, some issues are raised due to vehicular environment. This 
   document analyzes such issue and will propose security considerations 
   for IPwave.

1.1  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 RFC 2119 [RFC2119].

2  IPsec/TLS with Pre-shared key 

   When a pre-shared key is used in IPsec/TLS tunnel establishment, it 
   implies that there are agreements between nodes in order to configure 
   same key before connection. However, in the case of V2I/V2V, at least 
   one node is vehicular node, which means that it probably has no 
   agreement with the other peer, and result in no pre-shared key could 
   be applied.

3  IPsec/TLS with certificate 

   When using certificate in IPsec/TLS establishment, each node who need 
   to be authenticated should own a certificate. In IPwave, if the node 
Show full document text