draft-ietf-ipwave-vehicular-networking-01.txt   draft-ietf-ipwave-vehicular-networking-02.txt 
Network Working Group J. Jeong, Ed. Network Working Group J. Jeong, Ed.
Internet-Draft Sungkyunkwan University Internet-Draft Sungkyunkwan University
Intended status: Informational November 13, 2017 Intended status: Informational March 5, 2018
Expires: May 17, 2018 Expires: September 6, 2018
IP-based Vehicular Networking: Use Cases, Survey and Problem Statement IP-based Vehicular Networking: Use Cases, Survey and Problem Statement
draft-ietf-ipwave-vehicular-networking-01 draft-ietf-ipwave-vehicular-networking-02
Abstract Abstract
This document discusses use cases, survey, and problem statement on This document discusses use cases, survey, and problem statement on
IP-based vehicular networks, which are considered a key component of IP-based vehicular networks, which are considered a key component of
Intelligent Transportation Systems (ITS). The main topics of Intelligent Transportation Systems (ITS). The main topics of
vehicular networking are vehicle-to-vehicle (V2V), vehicle-to- vehicular networking are vehicle-to-vehicle (V2V), vehicle-to-
infrastructure (V2I), and infrastructure-to-vehicle (I2V) networking. infrastructure (V2I), and infrastructure-to-vehicle (I2V) networking.
First, this document surveys use cases using V2V and V2I networking. First, this document surveys use cases using V2V and V2I networking.
Second, this document deals with some critical aspects in vehicular Second, this document deals with some critical aspects in vehicular
skipping to change at page 1, line 44 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 17, 2018. This Internet-Draft will expire on September 6, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 32 skipping to change at page 2, line 32
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. V2I Use Cases . . . . . . . . . . . . . . . . . . . . . . 5 3.1. V2I Use Cases . . . . . . . . . . . . . . . . . . . . . . 5
3.2. V2V Use Cases . . . . . . . . . . . . . . . . . . . . . . 6 3.2. V2V Use Cases . . . . . . . . . . . . . . . . . . . . . . 6
4. Vehicular Network Architectures . . . . . . . . . . . . . . . 7 4. Vehicular Network Architectures . . . . . . . . . . . . . . . 7
4.1. Existing Architectures . . . . . . . . . . . . . . . . . 7 4.1. Existing Architectures . . . . . . . . . . . . . . . . . 7
4.1.1. VIP-WAVE: IP in 802.11p Vehicular Networks . . . . . 7 4.1.1. VIP-WAVE: IP in 802.11p Vehicular Networks . . . . . 7
4.1.2. IPv6 Operation for WAVE . . . . . . . . . . . . . . . 8 4.1.2. IPv6 Operation for WAVE . . . . . . . . . . . . . . . 8
4.1.3. Multicast Framework for Vehicular Networks . . . . . 9 4.1.3. Multicast Framework for Vehicular Networks . . . . . 9
4.1.4. Joint IP Networking and Radio Architecture . . . . . 9 4.1.4. Joint IP Networking and Radio Architecture . . . . . 10
4.1.5. Mobile Internet Access in FleetNet . . . . . . . . . 10 4.1.5. Mobile Internet Access in FleetNet . . . . . . . . . 11
4.1.6. A Layered Architecture for Vehicular DTNs . . . . . . 11 4.1.6. A Layered Architecture for Vehicular DTNs . . . . . . 12
4.2. V2I and V2V Internetworking Problem Statement . . . . . . 12 4.2. V2I and V2V Internetworking Problem Statement . . . . . . 12
4.2.1. V2I-based Internetworking . . . . . . . . . . . . . . 13 4.2.1. V2I-based Internetworking . . . . . . . . . . . . . . 14
4.2.2. V2V-based Internetworking . . . . . . . . . . . . . . 16 4.2.2. V2V-based Internetworking . . . . . . . . . . . . . . 16
5. Standardization Activities . . . . . . . . . . . . . . . . . 16 5. Standardization Activities . . . . . . . . . . . . . . . . . 17
5.1. IEEE Guide for WAVE - Architecture . . . . . . . . . . . 16 5.1. IEEE Guide for WAVE - Architecture . . . . . . . . . . . 17
5.2. IEEE Standard for WAVE - Networking Services . . . . . . 17 5.2. IEEE Standard for WAVE - Networking Services . . . . . . 18
5.3. ETSI Intelligent Transport Systems: GeoNetwork-IPv6 . . . 18 5.3. ETSI Intelligent Transport Systems: GeoNetwork-IPv6 . . . 18
5.4. ISO Intelligent Transport Systems: IPv6 over CALM . . . . 18 5.4. ISO Intelligent Transport Systems: IPv6 over CALM . . . . 19
6. IP Address Autoconfiguration . . . . . . . . . . . . . . . . 19 6. IP Address Autoconfiguration . . . . . . . . . . . . . . . . 20
6.1. Existing Protocols for Address Autoconfiguration . . . . 19 6.1. Existing Protocols for Address Autoconfiguration . . . . 20
6.1.1. Automatic IP Address Configuration in VANETs . . . . 19 6.1.1. Automatic IP Address Configuration in VANETs . . . . 20
6.1.2. Using Lane/Position Information . . . . . . . . . . . 20 6.1.2. Using Lane/Position Information . . . . . . . . . . . 20
6.1.3. GeoSAC: Scalable Address Autoconfiguration . . . . . 20 6.1.3. GeoSAC: Scalable Address Autoconfiguration . . . . . 21
6.1.4. Cross-layer Identities Management in ITS Stations . . 21 6.1.4. Cross-layer Identities Management in ITS Stations . . 22
6.2. Problem Statement for IP Address Autoconfiguration . . . 22 6.2. Problem Statement for IP Address Autoconfiguration . . . 22
6.2.1. Neighbor Discovery . . . . . . . . . . . . . . . . . 22 6.2.1. Neighbor Discovery . . . . . . . . . . . . . . . . . 23
6.2.2. IP Address Autoconfiguration . . . . . . . . . . . . 22 6.2.2. IP Address Autoconfiguration . . . . . . . . . . . . 23
7. Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 7. Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
7.1. Existing Routing Protocols . . . . . . . . . . . . . . . 24 7.1. Existing Routing Protocols . . . . . . . . . . . . . . . 24
7.1.1. Experimental Evaluation for IPv6 over GeoNet . . . . 24 7.1.1. Experimental Evaluation for IPv6 over GeoNet . . . . 24
7.1.2. Location-Aided Gateway Advertisement and Discovery . 24 7.1.2. Location-Aided Gateway Advertisement and Discovery . 25
7.2. Routing Problem Statement . . . . . . . . . . . . . . . . 25 7.2. Routing Problem Statement . . . . . . . . . . . . . . . . 26
8. Mobility Management . . . . . . . . . . . . . . . . . . . . . 25 8. Mobility Management . . . . . . . . . . . . . . . . . . . . . 26
8.1. Existing Protocols . . . . . . . . . . . . . . . . . . . 25 8.1. Existing Protocols . . . . . . . . . . . . . . . . . . . 26
8.1.1. Vehicular Ad Hoc Networks with Network Fragmentation 25 8.1.1. Vehicular Ad Hoc Networks with Network Fragmentation 26
8.1.2. Hybrid Centralized-Distributed Mobility Management . 26 8.1.2. Hybrid Centralized-Distributed Mobility Management . 27
8.1.3. Hybrid Architecture for Network Mobility Management . 27 8.1.3. Hybrid Architecture for Network Mobility Management . 28
8.1.4. NEMO-Enabled Localized Mobility Support . . . . . . . 28 8.1.4. NEMO-Enabled Localized Mobility Support . . . . . . . 29
8.1.5. Network Mobility for Vehicular Ad Hoc Networks . . . 29 8.1.5. Network Mobility for Vehicular Ad Hoc Networks . . . 29
8.1.6. Performance Analysis of P-NEMO for ITS . . . . . . . 29 8.1.6. Performance Analysis of P-NEMO for ITS . . . . . . . 30
8.1.7. Integration of VANets and Fixed IP Networks . . . . . 30 8.1.7. Integration of VANets and Fixed IP Networks . . . . . 30
8.1.8. SDN-based Mobility Management for 5G Networks . . . . 30 8.1.8. SDN-based Mobility Management for 5G Networks . . . . 31
8.1.9. IP Mobility for VANETs: Challenges and Solutions . . 31 8.1.9. IP Mobility for VANETs: Challenges and Solutions . . 32
8.2. Problem Statement for Mobility-Management . . . . . . . . 32 8.2. Problem Statement for Mobility-Management . . . . . . . . 33
9. DNS Naming Service . . . . . . . . . . . . . . . . . . . . . 33 9. DNS Naming Service . . . . . . . . . . . . . . . . . . . . . 34
9.1. Existing Protocols . . . . . . . . . . . . . . . . . . . 33 9.1. Existing Protocols . . . . . . . . . . . . . . . . . . . 34
9.1.1. Multicast DNS . . . . . . . . . . . . . . . . . . . . 33 9.1.1. Multicast DNS . . . . . . . . . . . . . . . . . . . . 34
9.1.2. DNS Name Autoconfiguration for IoT Devices . . . . . 33 9.1.2. DNS Name Autoconfiguration for IoT Devices . . . . . 34
9.2. Problem Statement . . . . . . . . . . . . . . . . . . . . 34 9.2. Problem Statement . . . . . . . . . . . . . . . . . . . . 35
10. Service Discovery . . . . . . . . . . . . . . . . . . . . . . 35 10. Service Discovery . . . . . . . . . . . . . . . . . . . . . . 35
10.1. Existing Protocols . . . . . . . . . . . . . . . . . . . 35 10.1. Existing Protocols . . . . . . . . . . . . . . . . . . . 35
10.1.1. mDNS-based Service Discovery . . . . . . . . . . . . 35 10.1.1. mDNS-based Service Discovery . . . . . . . . . . . . 36
10.1.2. ND-based Service Discovery . . . . . . . . . . . . . 35 10.1.2. ND-based Service Discovery . . . . . . . . . . . . . 36
10.2. Problem Statement . . . . . . . . . . . . . . . . . . . 35 10.2. Problem Statement . . . . . . . . . . . . . . . . . . . 36
11. Security and Privacy . . . . . . . . . . . . . . . . . . . . 36 11. Security and Privacy . . . . . . . . . . . . . . . . . . . . 37
11.1. Existing Protocols . . . . . . . . . . . . . . . . . . . 36 11.1. Existing Protocols . . . . . . . . . . . . . . . . . . . 37
11.1.1. Securing Vehicular IPv6 Communications . . . . . . . 36 11.1.1. Securing Vehicular IPv6 Communications . . . . . . . 37
11.1.2. Authentication and Access Control . . . . . . . . . 37 11.1.2. Authentication and Access Control . . . . . . . . . 38
11.2. Problem Statement . . . . . . . . . . . . . . . . . . . 37 11.2. Problem Statement . . . . . . . . . . . . . . . . . . . 38
12. Discussions . . . . . . . . . . . . . . . . . . . . . . . . . 38 12. Discussions . . . . . . . . . . . . . . . . . . . . . . . . . 39
12.1. Summary and Analysis . . . . . . . . . . . . . . . . . . 38 12.1. Summary and Analysis . . . . . . . . . . . . . . . . . . 39
12.2. Deployment Issues . . . . . . . . . . . . . . . . . . . 39 12.2. Deployment Issues . . . . . . . . . . . . . . . . . . . 40
13. Security Considerations . . . . . . . . . . . . . . . . . . . 39 13. Security Considerations . . . . . . . . . . . . . . . . . . . 40
14. Informative References . . . . . . . . . . . . . . . . . . . 40 14. Informative References . . . . . . . . . . . . . . . . . . . 40
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 47 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 49
Appendix B. Contributors . . . . . . . . . . . . . . . . . . . . 47 Appendix B. Contributors . . . . . . . . . . . . . . . . . . . . 49
Appendix C. Changes from draft-ietf-ipwave-vehicular- Appendix C. Changes from draft-ietf-ipwave-vehicular-
networking-00 . . . . . . . . . . . . . . . . . . . 49 networking-01 . . . . . . . . . . . . . . . . . . . 51
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 49 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 52
1. Introduction 1. Introduction
Vehicular networks have been focused on the driving safety, driving Vehicular networks have been focused on the driving safety, driving
efficiency, and entertainment in road networks. The Federal efficiency, and entertainment in road networks. The Federal
Communications Commission (FCC) in the US allocated wireless channels Communications Commission (FCC) in the US allocated wireless channels
for Dedicated Short-Range Communications (DSRC) service in the for Dedicated Short-Range Communications (DSRC) [DSRC], service in
Intelligent Transportation Systems (ITS) Radio Service in the the Intelligent Transportation Systems (ITS) Radio Service in the
5.850-5.925 GHz band (5.9 GHz band). DSRC-based wireless 5.850 - 5.925 GHz band (5.9 GHz band). DSRC-based wireless
communications can support vehicle-to-vehicle (V2V), vehicle-to- communications can support vehicle-to-vehicle (V2V), vehicle-to-
infrastructure (V2I), and infrastructure-to-vehicle (I2V) networking. infrastructure (V2I), and infrastructure-to-vehicle (I2V) networking.
For driving safety services based on the DSRC, IEEE has standardized For driving safety services based on the DSRC, IEEE has standardized
Wireless Access in Vehicular Environments (WAVE) standards, such as Wireless Access in Vehicular Environments (WAVE) standards, such as
IEEE 802.11p [IEEE-802.11p], IEEE 1609.2 [WAVE-1609.2], IEEE 1609.3 IEEE 802.11p [IEEE-802.11p], IEEE 1609.2 [WAVE-1609.2], IEEE 1609.3
[WAVE-1609.3], and IEEE 1609.4 [WAVE-1609.4]. Note that IEEE 802.11p [WAVE-1609.3], and IEEE 1609.4 [WAVE-1609.4]. Note that IEEE 802.11p
has been published as IEEE 802.11 Outside the Context of a Basic has been published as IEEE 802.11 Outside the Context of a Basic
Service Set (OCB) [IEEE-802.11-OCB] in 2012. Along with these WAVE Service Set (OCB) [IEEE-802.11-OCB] in 2012. Along with these WAVE
standards, IPv6 and Mobile IP protocols (e.g., MIPv4 and MIPv6) can standards, IPv6 and Mobile IP protocols (e.g., MIPv4 and MIPv6) can
skipping to change at page 4, line 43 skipping to change at page 4, line 43
document, we can specify the requirements for vehicular networks for document, we can specify the requirements for vehicular networks for
the intended purposes, such as the driving safety, driving the intended purposes, such as the driving safety, driving
efficiency, and entertainment. As a consequence, this will make it efficiency, and entertainment. As a consequence, this will make it
possible to design a network architecture and protocols for vehicular possible to design a network architecture and protocols for vehicular
networking. networking.
2. Terminology 2. Terminology
This document uses the following definitions: This document uses the following definitions:
o Road-Side Unit (RSU): A node that has Dedicated Short-Range o Road-Side Unit (RSU): A node that has physical communication
Communications (DSRC) device for wireless communications with devices (e.g., DSRC, Visible Light Communication, 802.15.4, etc.)
vehicles and is also connected to the Internet as a router or for wireless communication with vehicles and is also connected to
switch for packet forwarding. An RSU is deployed either at an the Internet as a router or switch for packet forwarding. An RSU
intersection or in a road segment. is deployed either at an intersection or in a road segment.
o On-Board Unit (OBU): A node that has a DSRC device for wireless o On-Board Unit (OBU): A node that has a DSRC device for wireless
communications with other OBUs and RSUs. An OBU is mounted on a communications with other OBUs and RSUs. An OBU is mounted on a
vehicle. It is assumed that a radio navigation receiver (e.g., vehicle. It is assumed that a radio navigation receiver (e.g.,
Global Positioning System (GPS)) is included in a vehicle with an Global Positioning System (GPS)) is included in a vehicle with an
OBU for efficient navigation. OBU for efficient navigation.
o Vehicle Detection Loop (or Loop Detector): An inductive device o Vehicle Detection Loop (or Loop Detector): An inductive device
used for detecting vehicles passing or arriving at a certain used for detecting vehicles passing or arriving at a certain
point, for instance approaching a traffic light or in motorway point, for instance approaching a traffic light or in motorway
skipping to change at page 5, line 34 skipping to change at page 5, line 34
of most freeway management sytems such that data is collected, of most freeway management sytems such that data is collected,
processed, and fused with other operational and control data, and processed, and fused with other operational and control data, and
is also synthesized to produce "information" distributed to is also synthesized to produce "information" distributed to
stakeholders, other agencies, and traveling public. TCC is called stakeholders, other agencies, and traveling public. TCC is called
Traffic Management Center (TMC) in the US. TCC can communicate Traffic Management Center (TMC) in the US. TCC can communicate
with road infrastructure nodes (e.g., RSUs, traffic signals, and with road infrastructure nodes (e.g., RSUs, traffic signals, and
loop detectors) to share measurement data and management loop detectors) to share measurement data and management
information by an application-layer protocol. information by an application-layer protocol.
o WAVE: Acronym for "Wireless Access in Vehicular Environments" o WAVE: Acronym for "Wireless Access in Vehicular Environments"
[WAVE-1609.0].
o DMM: Acronym for "Distributed Mobility Management" [DMM].
3. Use Cases 3. Use Cases
This section provides use cases of V2V and V2I networking. This section provides use cases of V2V and V2I networking.
3.1. V2I Use Cases 3.1. V2I Use Cases
The use cases of V2I networking include navigation service, fuel- The use cases of V2I networking include navigation service, fuel-
efficient speed recommendation service, and accident notification efficient speed recommendation service, and accident notification
service. service.
skipping to change at page 6, line 15 skipping to change at page 6, line 17
efficient detour paths. efficient detour paths.
The emergency communication between accident vehicles (or emergency The emergency communication between accident vehicles (or emergency
vehicles) and TCC can be performed via either RSU or 4G-LTE networks. vehicles) and TCC can be performed via either RSU or 4G-LTE networks.
The First Responder Network Authority (FirstNet) [FirstNet] is The First Responder Network Authority (FirstNet) [FirstNet] is
provided by the US government to establish, operate, and maintain an provided by the US government to establish, operate, and maintain an
interoperable public safety broadband network for safety and security interoperable public safety broadband network for safety and security
network services, such as emergency calls. The construction of the network services, such as emergency calls. The construction of the
nationwide FirstNet network requires each state in the US to have a nationwide FirstNet network requires each state in the US to have a
Radio Access Network (RAN) that will connect to FirstNet's network Radio Access Network (RAN) that will connect to FirstNet's network
core. The current RAN is mainly constructed by 4G-LTE, but DSRC- core. The current RAN is mainly constructed by 4G-LTE for the
based vehicular networks can be used in near future. communication between a vehicle and an infrastructure node (i.e.,
V2I) [FirstNet-Annual-Report-2017], but DSRC-based vehicular networks
can be used for V2I in near future [DSRC].
A pedestrian protection service, such as Safety-Aware Navigation A pedestrian protection service, such as Safety-Aware Navigation
Application (called SANA) [SANA], using V2I networking can reduce the Application (called SANA) [SANA], using V2I networking can reduce the
collision of a pedestrian and a vehicle, which have a smartphone, in collision of a pedestrian and a vehicle, which have a smartphone, in
a road network. Vehicles and pedestrians can communicate with each a road network. Vehicles and pedestrians can communicate with each
other via an RSU that delivers scheduling information for wireless other via an RSU that delivers scheduling information for wireless
communication to save the smartphones' battery. communication to save the smartphones' battery.
3.2. V2V Use Cases 3.2. V2V Use Cases
skipping to change at page 7, line 24 skipping to change at page 7, line 28
statement for a vehicular network architecture for IP-based vehicular statement for a vehicular network architecture for IP-based vehicular
networking. networking.
4.1. Existing Architectures 4.1. Existing Architectures
4.1.1. VIP-WAVE: IP in 802.11p Vehicular Networks 4.1.1. VIP-WAVE: IP in 802.11p Vehicular Networks
Cespedes et al. proposed a vehicular IP in WAVE called VIP-WAVE for Cespedes et al. proposed a vehicular IP in WAVE called VIP-WAVE for
I2V and V2I networking [VIP-WAVE]. IEEE 1609.3 specified a WAVE I2V and V2I networking [VIP-WAVE]. IEEE 1609.3 specified a WAVE
stack of protocols and includes IPv6 as a network layer protocol in stack of protocols and includes IPv6 as a network layer protocol in
data plane [WAVE-1609.3]. The standard WAVE does not support data plane [WAVE-1609.3]. The standard WAVE [WAVE-1609.0]
Duplicate Address Detection (DAD) of IPv6 Stateless Address [WAVE-1609.3] does not support Duplicate Address Detection (DAD) of
Autoconfiguration (SLAAC) [RFC4862] due to its own efficient IP IPv6 Stateless Address Autoconfiguration (SLAAC) [RFC4862] by having
address configuration based on a WAVE Service Advertisement (WSA) its own efficient IP address configuration mechanism based on a WAVE
management frame [WAVE-1609.3], seamless communications for Internet Service Advertisement (WSA) management frame [WAVE-1609.3]. It does
services, and multi-hop communications between a vehicle and an not support both seamless communications for Internet services and
infrastructure node (e.g., RSU). To overcome these limitations of multi-hop communications between a vehicle and an infrastructure node
the standard WAVE for IP-based networking, VIP-WAVE enhances the (e.g., RSU), either. To overcome these limitations of the standard
standard WAVE by the following three schemes: (i) an efficient WAVE for IP-based networking, VIP-WAVE enhances the standard WAVE by
mechanism for the IPv6 address assignment and DAD, (ii) on-demand IP the following three schemes: (i) an efficient mechanism for the IPv6
mobility based on Proxy Mobile IPv6 (PMIPv6), and (iii) one-hop and address assignment and DAD, (ii) on-demand IP mobility based on Proxy
two-hop communications for I2V and V2I networking. Mobile IPv6 (PMIPv6), and (iii) one-hop and two-hop communications
for I2V and V2I networking.
In WAVE, IPv6 Neighbor Discovery (ND) protocol is not recommended due In WAVE, IPv6 Neighbor Discovery (ND) protocol is not recommended due
to the overhead of ND against the timely and prompt communications in to the overhead of ND against the timely and prompt communications in
vehicular networking. By WAVE service advertisement (WAS) management vehicular networking. By WAVE service advertisement (WAS) management
frame, an RSU can provide vehicles with IP configuration information frame, an RSU can provide vehicles with IP configuration information
(e.g., IPv6 prefix, prefix length, gateway, router lifetime, and DNS (e.g., IPv6 prefix, prefix length, gateway, router lifetime, and DNS
server) without using ND. However, WAVE devices may support server) without using ND. However, WAVE devices may support
readdressing to provide pseudonymity, so a MAC address of a vehicle readdressing to provide pseudonymity, so a MAC address of a vehicle
may be changed or randomly generated. This update of the MAC address may be changed or randomly generated. This update of the MAC address
may lead to the collision of an IPv6 address based on a MAC address, may lead to the collision of an IPv6 address based on a MAC address,
skipping to change at page 40, line 35 skipping to change at page 41, line 29
Available: Available:
http://www.path.berkeley.edu/research/automated-and- http://www.path.berkeley.edu/research/automated-and-
connected-vehicles/cooperative-adaptive-cruise-control, connected-vehicles/cooperative-adaptive-cruise-control,
2017. 2017.
[CASD] Shen, Y., Jeong, J., Oh, T., and S. Son, "CASD: A [CASD] Shen, Y., Jeong, J., Oh, T., and S. Son, "CASD: A
Framework of Context-Awareness Safety Driving in Vehicular Framework of Context-Awareness Safety Driving in Vehicular
Networks", International Workshop on Device Centric Cloud Networks", International Workshop on Device Centric Cloud
(DC2), March 2016. (DC2), March 2016.
[DMM] Chan, H., "Requirements for Distributed Mobility
Management", RFC 7333, August 2014.
[DSRC] ASTM International, "Standard Specification for
Telecommunications and Information Exchange Between
Roadside and Vehicle Systems - 5 GHz Band Dedicated Short
Range Communications (DSRC) Medium Access Control (MAC)
and Physical Layer (PHY) Specifications",
ASTM E2213-03(2010), October 2010.
[ETSI-GeoNetwork-IP] [ETSI-GeoNetwork-IP]
ETSI Technical Committee Intelligent Transport Systems, ETSI Technical Committee Intelligent Transport Systems,
"Intelligent Transport Systems (ITS); Vehicular "Intelligent Transport Systems (ITS); Vehicular
Communications; GeoNetworking; Part 6: Internet Communications; GeoNetworking; Part 6: Internet
Integration; Sub-part 1: Transmission of IPv6 Packets over Integration; Sub-part 1: Transmission of IPv6 Packets over
GeoNetworking Protocols", ETSI EN 302 636-6-1, October GeoNetworking Protocols", ETSI EN 302 636-6-1, October
2013. 2013.
[ETSI-GeoNetworking] [ETSI-GeoNetworking]
ETSI Technical Committee Intelligent Transport Systems, ETSI Technical Committee Intelligent Transport Systems,
skipping to change at page 41, line 11 skipping to change at page 42, line 19
addressing and forwarding for point-to-point and point-to- addressing and forwarding for point-to-point and point-to-
multipoint communications; Sub-part 1: Media-Independent multipoint communications; Sub-part 1: Media-Independent
Functionality", ETSI EN 302 636-4-1, May 2014. Functionality", ETSI EN 302 636-4-1, May 2014.
[FirstNet] [FirstNet]
U.S. National Telecommunications and Information U.S. National Telecommunications and Information
Administration (NTIA), "First Responder Network Authority Administration (NTIA), "First Responder Network Authority
(FirstNet)", [Online] (FirstNet)", [Online]
Available: https://www.firstnet.gov/, 2012. Available: https://www.firstnet.gov/, 2012.
[FirstNet-Annual-Report-2017]
First Responder Network Authority, "FY 2017: ANNUAL REPORT
TO CONGRESS, Advancing Public Safety Broadband
Communications", FirstNet FY 2017, December 2017.
[FleetNet] [FleetNet]
Bechler, M., Franz, W., and L. Wolf, "Mobile Internet Bechler, M., Franz, W., and L. Wolf, "Mobile Internet
Access in FleetNet", 13th Fachtagung Kommunikation in Access in FleetNet", 13th Fachtagung Kommunikation in
verteilten Systemen, February 2001. verteilten Systemen, February 2001.
[GeoSAC] Baldessari, R., Bernardos, C., and M. Calderon, "GeoSAC - [GeoSAC] Baldessari, R., Bernardos, C., and M. Calderon, "GeoSAC -
Scalable Address Autoconfiguration for VANET Using Scalable Address Autoconfiguration for VANET Using
Geographic Networking Concepts", IEEE International Geographic Networking Concepts", IEEE International
Symposium on Personal, Indoor and Mobile Radio Symposium on Personal, Indoor and Mobile Radio
Communications, September 2008. Communications, September 2008.
skipping to change at page 41, line 35 skipping to change at page 42, line 48
Communications, June 2015. Communications, June 2015.
[H-NEMO] Nguyen, T. and C. Bonnet, "A Hybrid Centralized- [H-NEMO] Nguyen, T. and C. Bonnet, "A Hybrid Centralized-
Distributed Mobility Management Architecture for Network Distributed Mobility Management Architecture for Network
Mobility", IEEE International Symposium on a World of Mobility", IEEE International Symposium on a World of
Wireless, Mobile and Multimedia Networks, June 2015. Wireless, Mobile and Multimedia Networks, June 2015.
[ID-DNSNA] [ID-DNSNA]
Jeong, J., Ed., Lee, S., and J. Park, "DNS Name Jeong, J., Ed., Lee, S., and J. Park, "DNS Name
Autoconfiguration for Internet of Things Devices", draft- Autoconfiguration for Internet of Things Devices", draft-
jeong-ipwave-iot-dns-autoconf-01 (work in progress), jeong-ipwave-iot-dns-autoconf-02 (work in progress), March
October 2017. 2018.
[ID-Vehicular-ND] [ID-Vehicular-ND]
Jeong, J., Ed., Shen, Y., Jo, Y., Jeong, J., and J. Lee, Jeong, J., Ed., Shen, Y., Jo, Y., Jeong, J., and J. Lee,
"IPv6 Neighbor Discovery for Prefix and Service Discovery "IPv6 Neighbor Discovery for Prefix and Service Discovery
in Vehicular Networks", draft-jeong-ipwave-vehicular- in Vehicular Networks", draft-jeong-ipwave-vehicular-
neighbor-discovery-01 (work in progress), October 2017. neighbor-discovery-02 (work in progress), March 2018.
[Identity-Management] [Identity-Management]
Wetterwald, M., Hrizi, F., and P. Cataldi, "Cross-layer Wetterwald, M., Hrizi, F., and P. Cataldi, "Cross-layer
Identities Management in ITS Stations", The 10th Identities Management in ITS Stations", The 10th
International Conference on ITS Telecommunications, International Conference on ITS Telecommunications,
November 2010. November 2010.
[IEEE-802.11-OCB] [IEEE-802.11-OCB]
IEEE 802.11 Working Group, "Part 11: Wireless LAN Medium IEEE 802.11 Working Group, "Part 11: Wireless LAN Medium
Access Control (MAC) and Physical Layer (PHY) Access Control (MAC) and Physical Layer (PHY)
skipping to change at page 47, line 7 skipping to change at page 49, line 7
Access in Vehicular Environments (WAVE) - Networking Access in Vehicular Environments (WAVE) - Networking
Services", IEEE Std 1609.3-2016, April 2016. Services", IEEE Std 1609.3-2016, April 2016.
[WAVE-1609.4] [WAVE-1609.4]
IEEE 1609 Working Group, "IEEE Standard for Wireless IEEE 1609 Working Group, "IEEE Standard for Wireless
Access in Vehicular Environments (WAVE) - Multi-Channel Access in Vehicular Environments (WAVE) - Multi-Channel
Operation", IEEE Std 1609.4-2016, March 2016. Operation", IEEE Std 1609.4-2016, March 2016.
Appendix A. Acknowledgments Appendix A. Acknowledgments
This work was supported by Basic Science Research Program through the This work was supported by Next-Generation Information Computing
National Research Foundation of Korea (NRF) funded by the Ministry of Development Program through the National Research Foundation of Korea
Education (2017R1D1A1B03035885). This work was supported in part by (NRF) funded by the Ministry of Science and ICT (2017M3C4A7065980).
the Global Research Laboratory Program (2013K1A1A2A02078326) through This work was supported in part by the Global Research Laboratory
NRF and the DGIST Research and Development Program (CPS Global Program (2013K1A1A2A02078326) through NRF and the DGIST Research and
Center) funded by the Ministry of Science and ICT. This work was Development Program (CPS Global Center) funded by the Ministry of
supported in part by the French research project DataTweet (ANR-13- Science and ICT. This work was supported in part by the French
INFR-0008) and in part by the HIGHTS project funded by the European research project DataTweet (ANR-13-INFR-0008) and in part by the
Commission I (636537-H2020). HIGHTS project funded by the European Commission I (636537-H2020).
Appendix B. Contributors Appendix B. Contributors
This document is a group work of IPWAVE working group, greatly This document is a group work of IPWAVE working group, greatly
benefiting from inputs and texts by Rex Buddenberg (Naval benefiting from inputs and texts by Rex Buddenberg (Naval
Postgraduate School), Thierry Ernst (YoGoKo), Bokor Laszlo (Budapest Postgraduate School), Thierry Ernst (YoGoKo), Bokor Laszlo (Budapest
University of Technology and Economics), Jose Santa Lozanoi University of Technology and Economics), Jose Santa Lozanoi
(Universidad of Murcia), Richard Roy (MIT), and Francois Simon (Universidad of Murcia), Richard Roy (MIT), and Francois Simon
(Pilot). The authors sincerely appreciate their contributions. (Pilot). The authors sincerely appreciate their contributions.
skipping to change at page 48, line 37 skipping to change at page 50, line 37
Charles E. Perkins Charles E. Perkins
Futurewei Inc. Futurewei Inc.
2330 Central Expressway 2330 Central Expressway
Santa Clara, CA 95050 Santa Clara, CA 95050
USA USA
Phone: +1 408 330 4586 Phone: +1 408 330 4586
EMail: charliep@computer.org EMail: charliep@computer.org
Alex Petrescu Alexandre Petrescu
CEA, LIST CEA, LIST
CEA Saclay CEA Saclay
Gif-sur-Yvette, Ile-de-France 91190 Gif-sur-Yvette, Ile-de-France 91190
France France
Phone: +33169089223 Phone: +33169089223
EMail: Alexandre.Petrescu@cea.fr EMail: Alexandre.Petrescu@cea.fr
Yiwen Chris Shen Yiwen Chris Shen
Department of Computer Science & Engineering Department of Computer Science & Engineering
skipping to change at page 49, line 23 skipping to change at page 51, line 23
URI: http://iotlab.skku.edu/people-chris-shen.php URI: http://iotlab.skku.edu/people-chris-shen.php
Michelle Wetterwald Michelle Wetterwald
FBConsulting FBConsulting
21, Route de Luxembourg 21, Route de Luxembourg
Wasserbillig, Luxembourg L-6633 Wasserbillig, Luxembourg L-6633
Luxembourg Luxembourg
EMail: Michelle.Wetterwald@gmail.com EMail: Michelle.Wetterwald@gmail.com
Appendix C. Changes from draft-ietf-ipwave-vehicular-networking-00 Appendix C. Changes from draft-ietf-ipwave-vehicular-networking-01
The following changes are made from draft-ietf-ipwave-vehicular- The following changes are made from draft-ietf-ipwave-vehicular-
networking-00: networking-01:
o In Section 4.2, The mobility information of a mobile device (e.g., o In Section 1, the following sentence is added: The Federal
vehicle) can be used by the mobile device and infrastructure nodes Communications Commission (FCC) in the US allocated wireless
(e.g., TCC and RSU) for enhancing protocol performance. channels for Dedicated Short-Range Communications (DSRC) [DSRC],
service in the Intelligent Transportation Systems (ITS Radio
Service in the 5.850 - 5.925 GHz band (5.9 GHz band).
o In Section 4.2, Vehicles can use the TCC as its Home Network, so o In Section 2, the definition of Road-Side Unit (RSU) is modified
the TCC maintains the mobility information of vehicles for as a node that has physical communication devices (e.g., DSRC,
location management. Visible Light Communication, 802.15.4, etc.) for wireless
communication with vehicles and is also connected to the Internet
as a router or switch for packet forwarding.
o In Section 2, DMM is defined as the acronym for "Distributed
Mobility Management" [DMM].
o In Section 3.1, the following sentence is clarified along with
relevant references: The current RAN is mainly constructed by 4G-
LTE for the communication between a vehicle and an infrastructure
node (i.e., V2I) [FirstNet-Annual-Report-2017], but DSRC-based
vehicular networks can be used for V2I in near future [DSRC].
o In Section 4.1.1, the following sentences are clarified along with
relevant references: The standard WAVE [WAVE-1609.0][WAVE-1609.3]
does not support Duplicate Address Detection (DAD) of IPv6
Stateless Address Autoconfiguration (SLAAC) [RFC4862] by having
its own efficient IP address configuration mechanism based on a
WAVE Service Advertisement (WSA) management frame [WAVE-1609.3].
It does not support both seamless communications for Internet
services and multi-hop communications between a vehicle and an
infrastructure node (e.g., RSU), either.
o The contents are clarified with typo corrections and rephrasing. o The contents are clarified with typo corrections and rephrasing.
Author's Address Author's Address
Jaehoon Paul Jeong (editor) Jaehoon Paul Jeong (editor)
Department of Software Department of Software
Sungkyunkwan University Sungkyunkwan University
2066 Seobu-Ro, Jangan-Gu 2066 Seobu-Ro, Jangan-Gu
Suwon, Gyeonggi-Do 16419 Suwon, Gyeonggi-Do 16419
Republic of Korea Republic of Korea
Phone: +82 31 299 4957 Phone: +82 31 299 4957
Fax: +82 31 290 7996 Fax: +82 31 290 7996
EMail: pauljeong@skku.edu EMail: pauljeong@skku.edu
 End of changes. 32 change blocks. 
96 lines changed or deleted 141 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/