< draft-ietf-ipwave-vehicular-networking-26.txt   draft-ietf-ipwave-vehicular-networking-27.txt >
IPWAVE Working Group J. Jeong, Ed. IPWAVE Working Group J. Jeong, Ed.
Internet-Draft Sungkyunkwan University Internet-Draft Sungkyunkwan University
Intended status: Informational 21 February 2022 Intended status: Informational 22 February 2022
Expires: 25 August 2022 Expires: 26 August 2022
IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem
Statement and Use Cases Statement and Use Cases
draft-ietf-ipwave-vehicular-networking-26 draft-ietf-ipwave-vehicular-networking-27
Abstract Abstract
This document discusses the problem statement and use cases of This document discusses the problem statement and use cases of
IPv6-based vehicular networking for Intelligent Transportation IPv6-based vehicular networking for Intelligent Transportation
Systems (ITS). The main scenarios of vehicular communications are Systems (ITS). The main scenarios of vehicular communications are
vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and
vehicle-to-everything (V2X) communications. First, this document vehicle-to-everything (V2X) communications. First, this document
explains use cases using V2V, V2I, and V2X networking. Next, for explains use cases using V2V, V2I, and V2X networking. Next, for
IPv6-based vehicular networks, it makes a gap analysis of current IPv6-based vehicular networks, it makes a gap analysis of current
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 25 August 2022. This Internet-Draft will expire on 26 August 2022.
Copyright Notice Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the Copyright (c) 2022 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 25 skipping to change at page 2, line 25
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1. V2V . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.1. V2V . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2. V2I . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 3.2. V2I . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.3. V2X . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.3. V2X . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4. Vehicular Networks . . . . . . . . . . . . . . . . . . . . . 12 4. Vehicular Networks . . . . . . . . . . . . . . . . . . . . . 12
4.1. Vehicular Network Architecture . . . . . . . . . . . . . 13 4.1. Vehicular Network Architecture . . . . . . . . . . . . . 13
4.2. V2I-based Internetworking . . . . . . . . . . . . . . . . 15 4.2. V2I-based Internetworking . . . . . . . . . . . . . . . . 15
4.3. V2V-based Internetworking . . . . . . . . . . . . . . . . 17 4.3. V2V-based Internetworking . . . . . . . . . . . . . . . . 18
5. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 21 5. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 22
5.1. Neighbor Discovery . . . . . . . . . . . . . . . . . . . 22 5.1. Neighbor Discovery . . . . . . . . . . . . . . . . . . . 23
5.1.1. Link Model . . . . . . . . . . . . . . . . . . . . . 24 5.1.1. Link Model . . . . . . . . . . . . . . . . . . . . . 25
5.1.2. MAC Address Pseudonym . . . . . . . . . . . . . . . . 26 5.1.2. MAC Address Pseudonym . . . . . . . . . . . . . . . . 27
5.1.3. Routing . . . . . . . . . . . . . . . . . . . . . . . 26 5.1.3. Routing . . . . . . . . . . . . . . . . . . . . . . . 27
5.2. Mobility Management . . . . . . . . . . . . . . . . . . . 28 5.2. Mobility Management . . . . . . . . . . . . . . . . . . . 29
6. Security Considerations . . . . . . . . . . . . . . . . . . . 30 6. Security Considerations . . . . . . . . . . . . . . . . . . . 31
6.1. Security Threats in Neighbor Discovery . . . . . . . . . 31 6.1. Security Threats in Neighbor Discovery . . . . . . . . . 32
6.2. Security Threats in Mobility Management . . . . . . . . . 32 6.2. Security Threats in Mobility Management . . . . . . . . . 33
6.3. Other Threats . . . . . . . . . . . . . . . . . . . . . . 32 6.3. Other Threats . . . . . . . . . . . . . . . . . . . . . . 33
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 33 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 34
8.1. Normative References . . . . . . . . . . . . . . . . . . 34 8.1. Normative References . . . . . . . . . . . . . . . . . . 35
8.2. Informative References . . . . . . . . . . . . . . . . . 39 8.2. Informative References . . . . . . . . . . . . . . . . . 40
Appendix A. Support of Multiple Radio Technologies for V2V . . . 44 Appendix A. Support of Multiple Radio Technologies for V2V . . . 45
Appendix B. Support of Multihop V2X Networking . . . . . . . . . 44 Appendix B. Support of Multihop V2X Networking . . . . . . . . . 45
Appendix C. Support of Mobility Management for V2I . . . . . . . 46 Appendix C. Support of Mobility Management for V2I . . . . . . . 47
Appendix D. Acknowledgments . . . . . . . . . . . . . . . . . . 47 Appendix D. Acknowledgments . . . . . . . . . . . . . . . . . . 48
Appendix E. Contributors . . . . . . . . . . . . . . . . . . . . 48 Appendix E. Contributors . . . . . . . . . . . . . . . . . . . . 49
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 49 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 50
1. Introduction 1. Introduction
Vehicular networking studies have mainly focused on improving safety Vehicular networking studies have mainly focused on improving safety
and efficiency, and also enabling entertainment in vehicular and efficiency, and also enabling entertainment in vehicular
networks. The Federal Communications Commission (FCC) in the US networks. The Federal Communications Commission (FCC) in the US
allocated wireless channels for Dedicated Short-Range Communications allocated wireless channels for Dedicated Short-Range Communications
(DSRC) [DSRC] in the Intelligent Transportation Systems (ITS) with (DSRC) [DSRC] in the Intelligent Transportation Systems (ITS) with
the frequency band of 5.850 - 5.925 GHz (i.e., 5.9 GHz band). DSRC- the frequency band of 5.850 - 5.925 GHz (i.e., 5.9 GHz band). DSRC-
based wireless communications can support vehicle-to-vehicle (V2V), based wireless communications can support vehicle-to-vehicle (V2V),
skipping to change at page 3, line 46 skipping to change at page 3, line 46
[TR-22.886-3GPP][TS-23.287-3GPP]. With C-V2X, vehicles can directly [TR-22.886-3GPP][TS-23.287-3GPP]. With C-V2X, vehicles can directly
communicate with each other without relay nodes (e.g., eNodeB in LTE communicate with each other without relay nodes (e.g., eNodeB in LTE
and gNodeB in 5G). and gNodeB in 5G).
Along with these WAVE standards and C-V2X standards, regardless of a Along with these WAVE standards and C-V2X standards, regardless of a
wireless access technology under the IP stack of a vehicle, vehicular wireless access technology under the IP stack of a vehicle, vehicular
networks can operate IP mobility with IPv6 [RFC8200] and Mobile IPv6 networks can operate IP mobility with IPv6 [RFC8200] and Mobile IPv6
protocols (e.g., Mobile IPv6 (MIPv6) [RFC6275], Proxy MIPv6 (PMIPv6) protocols (e.g., Mobile IPv6 (MIPv6) [RFC6275], Proxy MIPv6 (PMIPv6)
[RFC5213], Distributed Mobility Management (DMM) [RFC7333], Network [RFC5213], Distributed Mobility Management (DMM) [RFC7333], Network
Mobility (NEMO) [RFC3963], Locator/ID Separation Protocol (LISP) Mobility (NEMO) [RFC3963], Locator/ID Separation Protocol (LISP)
[I-D.ietf-lisp-rfc6830bis], and Asymmetric Extended Route [I-D.ietf-lisp-rfc6830bis], and Automatic Extended Route Optimization
Optimization (AERO) [I-D.templin-6man-aero]). In addition, ISO has (AERO) [I-D.templin-6man-aero]). In addition, ISO has approved a
approved a standard specifying the IPv6 network protocols and standard specifying the IPv6 network protocols and services to be
services to be used for Communications Access for Land Mobiles (CALM) used for Communications Access for Land Mobiles (CALM)
[ISO-ITS-IPv6][ISO-ITS-IPv6-AMD1]. [ISO-ITS-IPv6][ISO-ITS-IPv6-AMD1].
This document describes use cases and a problem statement about This document describes use cases and a problem statement about
IPv6-based vehicular networking for ITS, which is named IPv6 Wireless IPv6-based vehicular networking for ITS, which is named IPv6 Wireless
Access in Vehicular Environments (IPWAVE). First, it introduces the Access in Vehicular Environments (IPWAVE). First, it introduces the
use cases for using V2V, V2I, and V2X networking in ITS. Next, for use cases for using V2V, V2I, and V2X networking in ITS. Next, for
IPv6-based vehicular networks, it makes a gap analysis of current IPv6-based vehicular networks, it makes a gap analysis of current
IPv6 protocols (e.g., IPv6 Neighbor Discovery, Mobility Management, IPv6 protocols (e.g., IPv6 Neighbor Discovery, Mobility Management,
and Security & Privacy), and then enumerates requirements for the and Security & Privacy), and then enumerates requirements for the
extensions of those IPv6 protocols, which are tailored to IPv6-based extensions of those IPv6 protocols, which are tailored to IPv6-based
skipping to change at page 10, line 6 skipping to change at page 10, line 6
* Energy-efficient speed recommendation service; * Energy-efficient speed recommendation service;
* Accident notification service; * Accident notification service;
* Electric vehicle (EV) charging service; * Electric vehicle (EV) charging service;
* UAM navigation service with efficient battery charging. * UAM navigation service with efficient battery charging.
A navigation service, for example, the Self-Adaptive Interactive A navigation service, for example, the Self-Adaptive Interactive
Navigation Tool(SAINT) [SAINT], using V2I networking interacts with a Navigation Tool (SAINT) [SAINT], using V2I networking interacts with
TCC for the large-scale/long-range road traffic optimization and can a TCC for the large-scale/long-range road traffic optimization and
guide individual vehicles along appropriate navigation paths in real can guide individual vehicles along appropriate navigation paths in
time. The enhanced version of SAINT [SAINTplus] can give fast moving real time. The enhanced version of SAINT [SAINTplus] can give fast
paths to emergency vehicles (e.g., ambulance and fire engine) to let moving paths to emergency vehicles (e.g., ambulance and fire engine)
them reach an accident spot while redirecting other vehicles near the to let them reach an accident spot while redirecting other vehicles
accident spot into efficient detour paths. near the accident spot into efficient detour paths.
Either a TCC or an ECD can recommend an energy-efficient speed to a Either a TCC or an ECD can recommend an energy-efficient speed to a
vehicle that depends on its traffic environment and traffic signal vehicle that depends on its traffic environment and traffic signal
scheduling [SignalGuru]. For example, when a vehicle approaches an scheduling [SignalGuru]. For example, when a vehicle approaches an
intersection area and a red traffic light for the vehicle becomes intersection area and a red traffic light for the vehicle becomes
turned on, it needs to reduce its speed to save fuel consumption. In turned on, it needs to reduce its speed to save fuel consumption. In
this case, either a TCC or an ECD, which has the up-to-date this case, either a TCC or an ECD, which has the up-to-date
trajectory of the vehicle and the traffic light schedule, can notify trajectory of the vehicle and the traffic light schedule, can notify
the vehicle of an appropriate speed for fuel efficiency. the vehicle of an appropriate speed for fuel efficiency.
[Fuel-Efficient] studies fuel-efficient route and speed plans for [Fuel-Efficient] studies fuel-efficient route and speed plans for
skipping to change at page 14, line 12 skipping to change at page 14, line 12
in various ways. Some of them (e.g., Mobility Anchor, Traffic in various ways. Some of them (e.g., Mobility Anchor, Traffic
Control Center, and Vehicular Cloud) may not be needed for the Control Center, and Vehicular Cloud) may not be needed for the
vehicular networks according to target use cases in Section 3. vehicular networks according to target use cases in Section 3.
Existing network architectures, such as the network architectures of Existing network architectures, such as the network architectures of
PMIPv6 [RFC5213], RPL (IPv6 Routing Protocol for Low-Power and Lossy PMIPv6 [RFC5213], RPL (IPv6 Routing Protocol for Low-Power and Lossy
Networks) [RFC6550], and OMNI (Overlay Multilink Network Interface) Networks) [RFC6550], and OMNI (Overlay Multilink Network Interface)
[I-D.templin-6man-omni], can be extended to a vehicular network [I-D.templin-6man-omni], can be extended to a vehicular network
architecture for multihop V2V, V2I, and V2X, as shown in Figure 1. architecture for multihop V2V, V2I, and V2X, as shown in Figure 1.
Refer to Appendix B for the detailed discussion on multihop V2X Refer to Appendix B for the detailed discussion on multihop V2X
networking by RPL and OMNI. networking by RPL and OMNI. Also, refer to Appendix A for the
description of how OMNI can support the use of multiple radio
technologies in V2X.
As shown in this figure, IP-RSUs as routers and vehicles with IP-OBU As shown in this figure, IP-RSUs as routers and vehicles with IP-OBU
have wireless media interfaces for VANET. Furthermore, the wireless have wireless media interfaces for VANET. Furthermore, the wireless
media interfaces are autoconfigured with a global IPv6 prefix (e.g., media interfaces are autoconfigured with a global IPv6 prefix (e.g.,
2001:DB8:1:1::/64) to support both V2V and V2I networking. Note that 2001:DB8:1:1::/64) to support both V2V and V2I networking. Note that
2001:DB8::/32 is a documentation prefix [RFC3849] for example 2001:DB8::/32 is a documentation prefix [RFC3849] for example
prefixes in this document, and also that any routable IPv6 address prefixes in this document, and also that any routable IPv6 address
needs to be routable in a VANET and a vehicular network including IP- needs to be routable in a VANET and a vehicular network including IP-
RSUs. RSUs.
 End of changes. 7 change blocks. 
37 lines changed or deleted 39 lines changed or added

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