idnits 2.17.1 draft-jeong-ipwave-problem-statement-00.txt: 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. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (June 8, 2017) is 2514 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2460 (Obsoleted by RFC 8200) ** Obsolete normative reference: RFC 3315 (Obsoleted by RFC 8415) ** Obsolete normative reference: RFC 3736 (Obsoleted by RFC 8415) ** Downref: Normative reference to an Informational RFC: RFC 7333 ** Downref: Normative reference to an Informational RFC: RFC 7429 == Outdated reference: A later version (-17) exists of draft-jeong-ipwave-iot-dns-autoconf-00 == Outdated reference: A later version (-17) exists of draft-jeong-ipwave-vehicular-neighbor-discovery-00 -- Obsolete informational reference (is this intentional?): RFC 4941 (Obsoleted by RFC 8981) Summary: 6 errors (**), 0 flaws (~~), 4 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Jeong 3 Internet-Draft Sungkyunkwan University 4 Intended status: Standards Track A. Petrescu 5 Expires: December 10, 2017 CEA, LIST 6 T. Oh 7 Rochester Institute of Technology 8 D. Liu 9 Alibaba 10 C. Perkins 11 Futurewei Inc. 12 June 8, 2017 14 Problem Statement for IP Wireless Access in Vehicular Environments 15 draft-jeong-ipwave-problem-statement-00 17 Abstract 19 This document provides a problem statement for IP Wireless Access in 20 Vehicular Environments (IPWAVE), that is, vehicular networks. This 21 document addresses the extension of IPv6 as the network layer 22 protocol in vehicular networks. It deals with networking issues in 23 one-hop communication between a Road-Side Unit (RSU) and a vehicle, 24 that is, "vehicle-to-infrastructure" (V2I) communication. It also 25 deals with one-hop communication between two neighboring vehicles, 26 that is, "vehicle-to-vehicle" (V2V) communication. Major issues 27 about IPv6 in vehicular networks include neighbor discovery protocol, 28 stateless address autoconfiguration, and DNS configuration for 29 Internet connectivity. When a vehicle and an RSU have an internal 30 network (respectively), the document discusses internetworking issues 31 between two internal networks through either V2I or V2V 32 communication. Those issues include prefix discovery, prefix 33 exchange, service discovery, security, and privacy. 35 Status of This Memo 37 This Internet-Draft is submitted to IETF in full conformance with the 38 provisions of BCP 78 and BCP 79. 40 Internet-Drafts are working documents of the Internet Engineering 41 Task Force (IETF), its areas, and its working groups. Note that 42 other groups may also distribute working documents as Internet- 43 Drafts. 45 Internet-Drafts are draft documents valid for a maximum of six months 46 and may be updated, replaced, or obsoleted by other documents at any 47 time. It is inappropriate to use Internet-Drafts as reference 48 material or to cite them other than as "work in progress." 49 The list of current Internet-Drafts can be accessed at 50 http://www.ietf.org/ietf/1id-abstracts.txt. 52 The list of Internet-Draft Shadow Directories can be accessed at 53 http://www.ietf.org/shadow.html. 55 This Internet-Draft will expire on December 10, 2017. 57 Copyright Notice 59 Copyright (c) 2017 IETF Trust and the persons identified as the 60 document authors. All rights reserved. 62 This document is subject to BCP 78 and the IETF Trust's Legal 63 Provisions Relating to IETF Documents 64 (http://trustee.ietf.org/license-info) in effect on the date of 65 publication of this document. Please review these documents 66 carefully, as they describe your rights and restrictions with respect 67 to this document. Code Components extracted from this document must 68 include Simplified BSD License text as described in Section 4.e of 69 the Trust Legal Provisions and are provided without warranty as 70 described in the Simplified BSD License. 72 Table of Contents 74 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 75 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4 76 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 77 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 78 5. Internetworking between Vehicle Network and RSU Network . . . 6 79 5.1. V2I-Based Internetworking . . . . . . . . . . . . . . . . 6 80 5.2. The Use Cases of V2I-Based Internetworking . . . . . . . . 8 81 6. Internetworking between Two Vehicle Networks . . . . . . . . . 8 82 6.1. V2V-Based Internetworking . . . . . . . . . . . . . . . . 8 83 6.2. The Use Cases of V2V-Based Internetworking . . . . . . . . 9 84 7. IPv6 Addressing . . . . . . . . . . . . . . . . . . . . . . . 10 85 8. Neighbor Discovery . . . . . . . . . . . . . . . . . . . . . . 10 86 9. IP Address Autoconfiguration . . . . . . . . . . . . . . . . . 11 87 10. DNS Naming Service . . . . . . . . . . . . . . . . . . . . . . 11 88 11. IP Mobility Management . . . . . . . . . . . . . . . . . . . . 12 89 12. Service Discovery . . . . . . . . . . . . . . . . . . . . . . 12 90 13. Security Considerations . . . . . . . . . . . . . . . . . . . 13 91 14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 13 92 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13 93 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 94 16.1. Normative References . . . . . . . . . . . . . . . . . . . 14 95 16.2. Informative References . . . . . . . . . . . . . . . . . . 15 97 1. Introduction 99 Recently, Vehicular Ad Hoc Networks (VANET) have been focusing on 100 intelligent services in road networks, such as driving safety, 101 efficient driving, and entertainment. For VANET, Dedicated Short- 102 Range Communications (DSRC) [DSRC-WAVE] was standardized as Wireless 103 Access in Vehicular Environments (WAVE) standards by IEEE. The WAVE 104 standards include IEEE 802.11p [IEEE-802.11p] for WAVE Media Access 105 Control (MAC) and Physical Layer (PHY), IEEE 1609.0 for WAVE 106 architecture [WAVE-1609.0], IEEE 1609.2 for WAVE security services 107 [WAVE-1609.2], IEEE 1609.3 for WAVE networking services 108 [WAVE-1609.3], and IEEE 1609.4 for WAVE multi-channel operation 109 [WAVE-1609.4]. 802.11p extends IEEE 802.11a [IEEE-802.11a] by 110 consideration of vehicular characteristics such as a vehicle's 111 velocity and collision avoidance. IEEE 802.11p has been published as 112 IEEE 802.11 Outside the Context of a Basic Service Set (OCB) 113 [IEEE-802.11-OCB] in 2012. 115 Now the deployment of VANET is indicated in real road environments 116 along with the popularity of smart devices (e.g., smartphone and 117 tablet). Many automobile vendors (e.g., Benz, BMW, Ford, Honda, and 118 Toyota) now consider automobiles as computer systems instead of 119 mechanical machines, since many current vehicles are operating with 120 many sensors and software. Google has advanced self-driving vehicles 121 with many special software modules and hardware devices to support 122 computer-vision-based object recognition, machine-learning-based 123 decision-making, and GPS navigation. 125 Vehicular networking research is enabling vehicles to communicate 126 with each other and infrastructure nodes in the Internet by using 127 TCP/IP, IP address autoconfiguration, routing, handover, and mobility 128 management [ID-VN-Survey]. IPv6 [RFC2460] is suitable for vehicular 129 networks since the protocol has abundant address space and 130 autoconfiguration features, and can be extended by way of new 131 protocol headers. 133 This document identifies issues of IPv6-based vehicle-to- 134 infrastructure (V2I) networking and vehicle-to-vehicle (V2V) 135 networking, such as IPv6 addressing [RFC4291], neighbor discovery 136 [RFC4861], address autoconfiguration [RFC4862], and DNS naming 137 service [RFC8106][RFC3646][ID-DNSNA]. This document also identifies 138 issues of internetworking between two internal networks when a 139 vehicle and/or an RSU have an internal network. Those issues include 140 prefix discovery, prefix exchange, and service discovery in the 141 inter-connected internal networks. In addition, the document 142 analyzes the characteristics of vehicular networks to consider the 143 design of V2I or V2V networking. 145 2. Requirements Language 147 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 148 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 149 document are to be interpreted as described in RFC 2119 [RFC2119]. 151 3. Terminology 153 This document uses the terminology described in [RFC4861] and 154 [RFC4862]. In addition, five new terms are defined below: 156 o Road-Side Unit (RSU): A node that has a wireless communication 157 device (e.g., DSRC) to communicate with vehicles and is connected 158 to the Internet as a router. An RSU is deployed either at an 159 intersection or in a road segment. 161 o On-Board Unit (OBU): A node that has a wireless communication 162 device (e.g., DSRC) to communicate with other OBUs and RSUs. An 163 OBU is mounted on a vehicle. It is assumed that a Global 164 Positioning System (GPS) is included in a vehicle with an OBU for 165 efficient navigation. 167 o Fixed Network: An RSU can have an internal network consisting of 168 multiple subnets. This internal network is a fixed network since 169 the RSU is fixed in the road network. 171 o Moving Network: A vehicle can have an internal network consisting 172 of multiple subnets. This internal network is called a moving 173 network since the vehicle is moving in the road network. 175 o Traffic Control Center (TCC): A node that maintains road 176 infrastructure information (e.g., RSUs and traffic signals), 177 vehicular traffic statistics (e.g., average vehicle speed and 178 vehicle inter-arrival time per road segment), and vehicle 179 information (e.g., a vehicle's identifier, position, direction, 180 speed, and trajectory as a navigation path). TCC is included in a 181 vehicular cloud for vehicular networks. Exemplary functions of 182 TCC include the management of evacuation routes, the monitoring of 183 pedestrians and bike traffic, the monitoring of real-time transit 184 operations, and real-time responsive traffic signal systems. 185 Thus, TCC is the nerve center of most freeway management sytems 186 such that data is collected, processed, and fused with other 187 operational and control data, and is also synthesized to produce 188 "information" distributed to stakeholders, other agencies, and 189 traveling public. TCC is called Traffic Management Center (TMC) 190 in the US. 192 4. Overview 194 This document provides a problem statement of IPv6-based V2I and V2V 195 networking. The main focus is one-hop networking between a vehicle 196 and an RSU or between two neighboring vehicles. However, this 197 document does not address all multi-hop networking scenarios of 198 vehicles and RSUs. Also, the problems focus on the network layer 199 (i.e., IPv6 protocol stack) rather than the MAC layer and the 200 transport layer (e.g., TCP, UDP, and SCTP). 202 Figure 1 shows a network configuration for V2I and V2V networking in 203 a road network. The two RSUs (RSU1 and RSU2) are deployed in the 204 road network and are connected to a Vehicular Cloud through the 205 Internet. TCC is connected to the Vehicular Cloud and the two 206 vehicles (Vehicle1 and Vehicle2) are wirelessly connected to RSU1, 207 and the last vehicle (Vehicle3) is wirelessly connected to RSU2. 208 Vehicle1 can communicate with Vehicle2 via V2V communication, and 209 Vehicle2 can communicate with Vehicle3 via V2V communication. 210 Vehicle1 can communicate with Vehicle3 via RSU1 and RSU2 via V2I 211 communication. 213 *-------------* 214 * * .-------. 215 * Vehicular Cloud *<------>| TCC | 216 * * ._______. 217 *-------------* 218 ^ ^ 219 | | 220 | | 221 v v 222 .--------. .--------. 223 | RSU1 |<----------->| RSU2 | 224 .________. .________. 225 ^ ^ ^ 226 : : : 227 : : : 228 v v v 229 .--------. .--------. .--------. 230 |Vehicle1|=> |Vehicle2|=> |Vehicle3|=> 231 | |<....>| |<....>| | 232 .________. .________. .________. 234 <----> Wired Link <....> Wireless Link => Moving Direction 236 Figure 1: The Network Configuration for Vehicular Networking 238 5. Internetworking between Vehicle Network and RSU Network 240 This section discusses the internetworking between a vehicle's moving 241 network and an RSU's fixed network. 243 5.1. V2I-Based Internetworking 245 As shown in Figure 2, the vehicle's moving network and the RSU's 246 fixed network are internal networks having multiple subnets and 247 having an edge router for the communication with another vehicle or 248 RSU. The method of prefix assignment for each subnet inside the 249 vehicle's mobile network and the RSU's fixed network is out of scope 250 for this document. The internetworking between two internal networks 251 via either V2I or V2V communication requires an exchange of network 252 prefix and other parameters. 254 The network parameter discovery collects networking information for 255 an IP communication between a vehicle and an RSU or between two 256 neighboring vehicles, such as link layer, MAC layer, and IP layer 257 information. The link layer information includes wireless link layer 258 parameters, such as wireless media (e.g., IEEE 802.11 OCB, LTE D2D, 259 Bluetooth, and LiFi) and a transmission power level. The MAC layer 260 information includes the MAC address of an external network interface 261 for the internetworking with another vehicle or RSU. The IP layer 262 information includes the IP address and prefix of an external network 263 interface for the internetworking with another vehicle or RSU. 265 Once the network parameter discovery and prefix exchange operations 266 are performed, unicast of packets can be supported between the 267 vehicle's moving network and the RSU's fixed network. The DNS naming 268 service should be supported for the DNS name resolution for hosts or 269 servers residing either in the vehicle's moving network or the RSU's 270 fixed network. 272 (*)<..........>(*) 273 | | 2001:DB8:1:1::/64 274 .------------------------------. .---------------------------------. 275 | | | | | | 276 | .-------. .------. .-------. | | .-------. .------. .-------. | 277 | | Host1 | |RDNSS1| |Router1| | | |Router3| |RDNSS2| | Host3 | | 278 | ._______. .______. ._______. | | ._______. .______. ._______. | 279 | ^ ^ ^ | | ^ ^ ^ | 280 | | | | | | | | | | 281 | v v v | | v v v | 282 | ---------------------------- | | ------------------------------- | 283 | 2001:DB8:10:1::/64 ^ | | ^ 2001:DB8:20:1::/64 | 284 | | | | | | 285 | v | | v | 286 | .-------. .-------. | | .-------. .-------. .-------. | 287 | | Host2 | |Router2| | | |Router4| |Server1|...|ServerN| | 288 | ._______. ._______. | | ._______. ._______. ._______. | 289 | ^ ^ | | ^ ^ ^ | 290 | | | | | | | | | 291 | v v | | v v v | 292 | ---------------------------- | | ------------------------------- | 293 | 2001:DB8:10:2::/64 | | 2001:DB8:20:2::/64 | 294 .______________________________. ._________________________________. 295 Vehicle1 (Moving Network1) RSU1 (Fixed Network1) 297 <----> Wired Link <....> Wireless Link (*) Antenna 299 Figure 2: Internetworking between Vehicle Network and RSU Network 301 Figure 2 shows internetworking between the vehicle's moving network 302 and the RSU's fixed network. There exists an internal network 303 (Moving Network1) inside Vehicle1. Vehicle1 has the DNS Server 304 (RDNSS1), the two hosts (Host1 and Host2), and the two routers 305 (Router1 and Router2). There exists another internal network (Fixed 306 Network1) inside RSU1. RSU1 has the DNS Server (RDNSS2), one host 307 (Host3), the two routers (Router3 and Router4), and the collection of 308 servers (Server1 to ServerN) for various services in the road 309 networks, such as the emergency notification and navigation. 310 Vehicle1's Router1 and RSU1's Router3 use 2001:DB8:1:1::/64 for an 311 external link (e.g., DSRC) for I2V networking. 313 This document addresses the internetworking between the vehicle's 314 moving network and the RSU's fixed network in Figure 2 and the 315 required enhancement of IPv6 protocol suite for the V2I networking 316 service. 318 5.2. The Use Cases of V2I-Based Internetworking 320 The use cases for V2I networking include navigation service, fuel- 321 efficient speed recommendation service, and accident notification 322 service. 324 A navigation service, such as Self-Adaptive Interactive Navigation 325 Tool [SAINT], using V2I networking interacts with TCC for the global 326 road traffic optimization and can guide individual vehicles for 327 appropriate navigation paths in real time. 329 A pedestrian protection service, such as Safety-Aware Navigation 330 Application [SANA], using V2I networking can reduce the collision of 331 a pedestrian and a vehicle, which have a smartphone, in a road 332 network. 334 6. Internetworking between Two Vehicle Networks 336 This section discusses the internetworking between the moving 337 networks of two neighboring vehicles. 339 6.1. V2V-Based Internetworking 341 In Figure 3, the prefix assignment for each subnet inside each 342 vehicle's mobile network is done through a prefix delegation 343 protocol. 345 (*)<..........>(*) 346 | | 2001:DB8:1:1::/64 347 .------------------------------. .---------------------------------. 348 | | | | | | 349 | .-------. .------. .-------. | | .-------. .------. .-------. | 350 | | Host1 | |RDNSS1| |Router1| | | |Router3| |RDNSS2| | Host3 | | 351 | ._______. .______. ._______. | | ._______. .______. ._______. | 352 | ^ ^ ^ | | ^ ^ ^ | 353 | | | | | | | | | | 354 | v v v | | v v v | 355 | ---------------------------- | | ------------------------------- | 356 | 2001:DB8:10:1::/64 ^ | | ^ 2001:DB8:30:1::/64 | 357 | | | | | | 358 | v | | v | 359 | .-------. .-------. | | .-------. .-------. | 360 | | Host2 | |Router2| | | |Router4| | Host4 | | 361 | ._______. ._______. | | ._______. ._______. | 362 | ^ ^ | | ^ ^ | 363 | | | | | | | | 364 | v v | | v v | 365 | ---------------------------- | | ------------------------------- | 366 | 2001:DB8:10:2::/64 | | 2001:DB8:30:2::/64 | 367 .______________________________. ._________________________________. 368 Vehicle1 (Moving Network1) Vehicle2 (Moving Network2) 370 <----> Wired Link <....> Wireless Link (*) Antenna 372 Figure 3: Internetworking between Two Vehicle Networks 374 Figure 3 shows internetworking between the moving networks of two 375 neighboring vehicles. There exists an internal network (Moving 376 Network1) inside Vehicle1. Vehicle1 has the DNS Server (RDNSS1), the 377 two hosts (Host1 and Host2), and the two routers (Router1 and 378 Router2). There exists another internal network (Moving Network2) 379 inside Vehicle2. Vehicle2 has the DNS Server (RDNSS2), the two hosts 380 (Host3 and Host4), and the two routers (Router3 and Router4). 381 Vehicle1's Router1 and Vehicle2's Router3 use 2001:DB8:1:1::/64 for 382 an external link (e.g., DSRC) for V2V networking. 384 This document describes the internetworking between the moving 385 networks of two neighboring vehicles in Figure 3 and the required 386 enhancement of IPv6 protocol suite for the V2V networking service. 388 6.2. The Use Cases of V2V-Based Internetworking 390 The use cases for V2V networking include context-aware navigator for 391 driving safety, cooperative adaptive cruise control in an urban 392 roadway, and platooning in a highway. These are three techniques 393 that will be important elements for self-driving. 395 Context-aware navigator can help drivers to drive safely by letting 396 the drivers recognize dangerous obstacles and situations, including 397 neighboring vehicles that might cause a collision [CASD]. 399 Cooperative adaptive cruise control helps vehicles to adapt their 400 speed autonomously according to the mobility of their predecessor and 401 successor vehicles in an urban roadway. 403 Platooning allows a series of vehicles (e.g., trucks) to move 404 together with a very short inter-distance. This platooning can 405 maximize the throughput of vehicular traffic in a highway. 407 7. IPv6 Addressing 409 This section discusses IP addressing for the V2I and V2V networking. 410 There are two approaches for IPv6 addressing in vehicular networks. 411 The first is to use unique local IPv6 unicast addresses (ULAs) for 412 vehicular networks [RFC4193]. The other is to use global IPv6 413 addresses for the interoperability with the Internet [RFC4291]. The 414 former approach is often used by Mobile Ad Hoc Networks (MANET) for 415 an isolated subnet. This approach can support the emergency 416 notification service and navigation service in road networks. 417 However, for general Internet services (e.g., email access, web 418 surfing and entertainment services), the latter approach is required. 420 For global IP addresses, there are two choices: a multi-link subnet 421 approach for multiple RSUs and a single subnet approach per RSU. In 422 the multi-link subnet approach, which is similar to ULA for MANET, 423 RSUs play a role of layer-2 (L2) switches and the router 424 interconnected with the RSUs is required. The router maintains the 425 location of each vehicle belonging to an RSU for L2 switching. In 426 the single subnet approach per RSU, which is similar to the legacy 427 subnet in the Internet, each RSU plays the role of a (layer-3) 428 router. 430 8. Neighbor Discovery 432 Neighbor Discovery (ND) is a core part of IPv6 protocol suite 433 [RFC4861]. This section discusses an extension of ND for V2I 434 networking. The vehicles are moving fast within the communication 435 coverage of an RSU. The external link between the vehicle and the 436 RSU can be used for V2I networking, as shown in Figure 2. 438 ND time-related parameters such as router lifetime and Neighbor 439 Advertisement (NA) interval should be adjusted for high-speed 440 vehicles and vehicle density. As vehicles move faster, the NA 441 interval should decrease for the NA messages to reach the neighboring 442 vehicles promptly. Also, as vehicle density is higher, the NA 443 interval should increase for the NA messages to collide with other NA 444 messages with lower collision probability. 446 9. IP Address Autoconfiguration 448 This section discusses IP address autoconfiguration for V2I 449 networking. For IP address autoconfiguration, high-speed vehicles 450 should also be considered. The legacy IPv6 stateless address 451 autoconfiguration [RFC4862], as shown in Figure 1, may not perform 452 well. This is because vehicles can travel through the communication 453 coverage of the RSU faster than the completion of address 454 autoconfiguration (with Router Advertisement and Duplicate Address 455 Detection (DAD) procedures). 457 To mitigate the impact of vehicle speed on address configuration, the 458 RSU can perform IP address autoconfiguration including the DAD 459 proactively as an ND proxy on behalf of the vehicles. If vehicles 460 periodically report their movement information (e.g., position, 461 trajectory, speed, and direction) to TCC, TCC can coordinate the RSUs 462 under its control for the proactive IP address configuration of the 463 vehicles with the mobility information of the vehicles. DHCPv6 (or 464 Stateless DHCPv6) can be used for the IP address autoconfiguration 465 [RFC3315][RFC3736]. 467 In the case of a single subnet per RSU, the delay to change IPv6 468 address through DHCPv6 procedure is not suitable since vehicles move 469 fast. Some modifications are required for the high-speed vehicles 470 that quickly crosses the communication coverages of multiple RSUs. 471 Some modifications are required for both stateless address 472 autoconfiguration and DHCPv6. Mobile IPv6 (MIPv6) can be used for 473 the fast update of a vehicle's care-of address for the current RSU to 474 communicate with the vehicle [RFC6275]. 476 10. DNS Naming Service 478 This section suggests a DNS naming service for V2I networking. The 479 DNS naming service consists of the DNS name resolution and DNS name 480 autoconfiguration. 482 The DNS name resolution translates a DNS name into the corresponding 483 IPv6 address through a recursive DNS server (RDNSS) within the 484 vehicle's moving network and DNS servers in the Internet 485 [RFC1034][RFC1035], which are located outside the VANET. The RDNSSes 486 can be advertised by RA DNS Option or DHCP DNS Option into the 487 subnets within the vehicle's moving network. 489 The DNS name autoconfiguration makes a unique DNS name for hosts 490 within a vehicle's moving network and registers it into a DNS server 491 within the vehicle's moving network [ID-DNSNA]. With Vehicle 492 Identification Number (VIN), a unique DNS suffix can be constructed 493 as a DNS domain for the vehicle's moving network. Each host can 494 generate its DNS name and register it into the local RDNSS in the 495 vehicle's moving network. 497 11. IP Mobility Management 499 This section discusses an IP mobility support in V2I networking. In 500 a single subnet per RSU, vehicles continually cross the communication 501 coverages of adjacent RSUs. During this crossing, TCP/UDP sessions 502 can be maintained through IP mobility support, such as MIPv6 503 [RFC6275], Proxy MIPv6 [RFC5213][RFC5949], and Distributed Mobility 504 Management (DMM) [RFC7333][RFC7429]. Since vehicles move fast along 505 roadways, high speed should be enabled by the parameter configuration 506 in the IP mobility management. With the periodic reports of the 507 movement information from the vehicles, TCC can coordinate RSUs and 508 other network compoments under its control for the proactive mobility 509 management of the vehicles along the movement of the vehicles. 511 To support the mobility of a vehicle's moving network, Network 512 Mobility Basic Support Protocol (NEMO) can be used [RFC3963]. Like 513 MIPv6, the high speed of vehicles should be considered for a 514 parameter configuration in NEMO. 516 12. Service Discovery 518 Vehicles need to discover services (e.g., road condition 519 notification, navigation service, and entertainment) provided by 520 infrastructure nodes in a fixed network via RSU, as shown in 521 Figure 2. During the passing of an intersection or road segment with 522 an RSU, vehicles should perform this service discovery quickly. 524 Since with the existing service discovery protocols, such as DNS- 525 based Service Discovery (DNS-SD) [RFC6763] and Multicast DNS (mDNS) 526 [RFC6762], the service discovery will be performed with message 527 exchanges, the discovery delay may hinder the prompt service usage of 528 the vehicles from the fixed network via RSU. One feasible approach 529 is a piggyback service discovery during the prefix exchange of 530 network prefixes for the networking between a vehicle's moving 531 network and an RSU's fixed network. That is, the message of the 532 prefix exchange can include service information, such as each 533 service's IP address, transport layer protocol, and port number. 535 IPv6 ND can be extended for the prefix and service discovery 536 [ID-Vehicular-ND]. Vehicles and RSUs can announce the network 537 prefixes and services in their internal network via ND messages 538 containing ND options with the prefix and service information. Since 539 it does not need any additional service discovery protocol in the 540 application layer, this ND-based approach can provide vehicles and 541 RSUs with the rapid discovery of the network prefixes and services. 543 13. Security Considerations 545 Security and privacy are paramount in the V2I and V2V networking in 546 VANET. Only authorized vehicles should be allowed to use the V2I and 547 V2V networking in VANET. A Vehicle Identification Number (VIN) and a 548 user certificate along with in-vehicle device's identifier generation 549 can be used to authenticate a vehicle and the user through a road 550 infrastructure node, such as an RSU connected to an authentication 551 server in TCC. Transport Layer Security (TLS) certificates can also 552 be used for secure vehicle communications. 554 A security scheme providing authentication and access control should 555 be provided in vehicular networks [VN-Security]. With this scheme, 556 the security and privacy can be supported for safe and reliable data 557 services in vehicular networks. 559 To prevent an adversary from tracking a vehicle by with its MAC 560 address or IPv6 address, each vehicle should periodically update its 561 MAC address and the corresponding IPv6 address as suggested in 562 [RFC4086][RFC4941]. Such an update of the MAC and IPv6 addresses 563 should not interrupt the communications between a vehicle and an RSU. 565 To protect packets exchanged between a vehicle and an RSU, packets 566 should be encrypted. To assure confidentiality, efficient encryption 567 and decryption algorithms can be used along with a key management 568 scheme such as Internet Key Exchange version 2 (IKEv2) and Internet 569 Protocol Security (IPsec) [Securing-VCOMM]. 571 14. Contributors 573 IPWAVE is a group effort. The following people actively contributed 574 to the problem statement text: Nabil Benamar (Moulay Ismail 575 University), Sandra Cespedes (Universidad de Chile), Thierry Ernst 576 (YoGoKo), Jerome Haerri (Eurecom), Richard Roy (MIT), and Francois 577 Simon (Pilot). 579 15. Acknowledgments 581 This work was supported by Basic Science Research Program through the 582 National Research Foundation of Korea (NRF) funded by the Ministry of 583 Education (No. 2017R1B1A1B03035885). This work was supported in part 584 by ICT R&D program of MSIP/IITP (14-824-09-013, Resilient Cyber- 585 Physical Systems Research) and the DGIST Research and Development 586 Program (CPS Global Center) funded by the Ministry of Science, ICT & 587 Future Planning. 589 16. References 591 16.1. Normative References 593 [RFC2119] Bradner, S., "Key words for use in RFCs to 594 Indicate Requirement Levels", BCP 14, RFC 2119, 595 March 1997. 597 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, 598 Version 6 (IPv6) Specification", RFC 2460, 599 December 1998. 601 [RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 602 Unicast Addresses", RFC 4193, October 2005. 604 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 605 Addressing Architecture", RFC 4291, February 2006. 607 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. 608 Soliman, "Neighbor Discovery for IP Version 6 609 (IPv6)", RFC 4861, September 2007. 611 [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 612 Stateless Address Autoconfiguration", RFC 4862, 613 September 2007. 615 [RFC8106] Jeong, J., Park, S., Beloeil, L., and S. 616 Madanapalli, "IPv6 Router Advertisement Options 617 for DNS Configuration", RFC 8106, March 2017. 619 [RFC3646] Droms, R., Ed., "DNS Configuration options for 620 Dynamic Host Configuration Protocol for IPv6 621 (DHCPv6)", RFC 3646, December 2003. 623 [RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., 624 Perkins, C., and M. Carney, "Dynamic Host 625 Configuration Protocol for IPv6 (DHCPv6)", 626 RFC 3315, July 2003. 628 [RFC3736] Droms, R., "Stateless Dynamic Host Configuration 629 Protocol (DHCP) Service for IPv6", RFC 3736, 630 April 2004. 632 [RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, 633 "Mobility Support in IPv6", RFC 6275, July 2011. 635 [RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., 636 Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", 637 RFC 5213, August 2008. 639 [RFC5949] Yokota, H., Chowdhury, K., Koodli, R., Patil, B., 640 and F. Xia, "Fast Handovers for Proxy Mobile 641 IPv6", RFC 5949, September 2010. 643 [RFC3963] Devarapalli, V., Wakikawa, R., Petrescu, A., and 644 P. Thubert, "Network Mobility (NEMO) Basic Support 645 Protocol", RFC 3963, January 2005. 647 [RFC7333] Chan, H., Liu, D., Seite, P., Yokota, H., and J. 648 Korhonen, "Requirements for Distributed Mobility 649 Management", RFC 7333, August 2014. 651 [RFC7429] Liu, D., Zuniga, JC., Seite, P., Chan, H., and CJ. 652 Bernardos, "Distributed Mobility Management: 653 Current Practices and Gap Analysis", RFC 7429, 654 January 2015. 656 [RFC1034] Mockapetris, P., "Domain Names - Concepts and 657 Facilities", RFC 1034, November 1987. 659 [RFC1035] Mockapetris, P., "Domain Names - Implementation 660 and Specification", RFC 1035, November 1987. 662 [RFC6763] Cheshire, S. and M. Krochmal, "DNS-Based Service 663 Discovery", RFC 6763, February 2013. 665 [RFC6762] Cheshire, S. and M. Krochmal, "Multicast DNS", 666 RFC 6762, February 2013. 668 16.2. Informative References 670 [DSRC-WAVE] Morgan, Y., "Notes on DSRC & WAVE Standards Suite: 671 Its Architecture, Design, and Characteristics", 672 IEEE Communications Surveys & Tutorials, 12(4), 673 2012. 675 [IEEE-802.11p] IEEE Std 802.11p, "Part 11: Wireless LAN Medium 676 Access Control (MAC) and Physical Layer (PHY) 677 Specifications Amendment 6: Wireless Access in 678 Vehicular Environments", June 2010. 680 [IEEE-802.11a] IEEE Std 802.11a, "Part 11: Wireless LAN Medium 681 Access Control (MAC) and Physical Layer (PHY) 682 specifications: High-speed Physical Layer in the 5 683 GHZ Band", September 1999. 685 [IEEE-802.11-OCB] IEEE Std 802.11, "Part 11: Wireless LAN Medium 686 Access Control (MAC) and Physical Layer (PHY) 687 Specifications", February 2012. 689 [WAVE-1609.0] IEEE 1609 Working Group, "IEEE Guide for Wireless 690 Access in Vehicular Environments (WAVE) - 691 Architecture", IEEE Std 1609.0-2013, March 2014. 693 [WAVE-1609.2] IEEE 1609.2 Working Group, "IEEE Standard for 694 Wireless Access in Vehicular Environments - 695 Security Services for Applications and Management 696 Messages", IEEE Std 1609.2-2016, March 2016. 698 [WAVE-1609.3] IEEE 1609.3 Working Group, "IEEE Standard for 699 Wireless Access in Vehicular Environments (WAVE) - 700 Networking Services", IEEE Std 1609.3-2016, 701 April 2016. 703 [WAVE-1609.4] IEEE 1609.4 Working Group, "IEEE Standard for 704 Wireless Access in Vehicular Environments (WAVE) - 705 Multi-Channel Operation", IEEE Std 1609.4-2016, 706 March 2016. 708 [ID-VN-Survey] Jeong, J., Ed., Cespedes, S., Benamar, N., Haerri, 709 J., and M. Wetterwald, "Survey on IP-based 710 Vehicular Networking for Intelligent 711 Transportation Systems", 712 draft-jeong-ipwave-vehicular-networking-survey-03 713 (work in progress), June 2017. 715 [ID-DNSNA] Jeong, J., Ed., Lee, S., and J. Park, "DNS Name 716 Autoconfiguration for Internet of Things Devices", 717 draft-jeong-ipwave-iot-dns-autoconf-00 (work in 718 progress), March 2017. 720 [ID-Vehicular-ND] Jeong, J., Ed., Shen, Y., Jo, Y., Jeong, J., and 721 J. Lee, "IPv6 Neighbor Discovery for Prefix and 722 Service Discovery in Vehicular Networks", 723 draft-jeong-ipwave-vehicular-neighbor-discovery-00 724 (work in progress), March 2017. 726 [VN-Security] Moustafa, H., Bourdon, G., and Y. Gourhant, 727 "Providing Authentication and Access Control in 728 Vehicular Network Environment", IFIP TC- 729 11 International Information Security Conference, 730 May 2006. 732 [Securing-VCOMM] Fernandez, P., Santa, J., Bernal, F., and A. 733 Skarmeta, "Securing Vehicular IPv6 734 Communications", IEEE Transactions on Dependable 735 and Secure Computing, January 2016. 737 [RFC4086] Eastlake 3rd, D., Schiller, J., and S. Crocker, 738 "Randomness Requirements for Security", RFC 4086, 739 June 2005. 741 [RFC4941] Narten, T., Draves, R., and S. Krishnan, "Privacy 742 Extensions for Stateless Address Autoconfiguration 743 in IPv6", RFC 4941, September 2007. 745 [SAINT] Jeong, J., Jeong, H., Lee, E., Oh, T., and D. Du, 746 "SAINT: Self-Adaptive Interactive Navigation Tool 747 for Cloud-Based Vehicular Traffic Optimization", 748 IEEE Transactions on Vehicular Technology, Vol. 749 65, No. 6, June 2016. 751 [SANA] Hwang, T. and J. Jeong, "SANA: Safety-Aware 752 Navigation Application for Pedestrian Protection 753 in Vehicular Networks", Springer Lecture Notes in 754 Computer Science (LNCS), Vol. 9502, December 2015. 756 [CASD] Shen, Y., Jeong, J., Oh, T., and S. Son, "CASD: A 757 Framework of Context-Awareness Safety Driving in 758 Vehicular Networks", International Workshop on 759 Device Centric Cloud (DC2), March 2016. 761 Authors' Addresses 763 Jaehoon Paul Jeong 764 Department of Software 765 Sungkyunkwan University 766 2066 Seobu-Ro, Jangan-Gu 767 Suwon, Gyeonggi-Do 440-746 768 Republic of Korea 770 Phone: +82 31 299 4957 771 Fax: +82 31 290 7996 772 EMail: pauljeong@skku.edu 773 URI: http://iotlab.skku.edu/people-jaehoon-jeong.php 774 Alex 775 CEA, LIST 776 CEA Saclay 777 Gif-sur-Yvette, Ile-de-France 91190 778 France 780 Phone: +33169089223 781 EMail: Alexandre.Petrescu@cea.fr 783 Tae (Tom) Oh 784 Department of Information Sciences and Technologies 785 Rochester Institute of Technology 786 One Lomb Memorial Drive 787 Rochester, NY 14623-5603 788 USA 790 Phone: +1 585 475 7642 791 EMail: Tom.Oh@rit.edu 793 Dapeng Liu 794 Alibaba 795 Beijing, Beijing 100022 796 China 798 Phone: +86 13911788933 799 EMail: max.ldp@alibaba-inc.com 801 Charles E. Perkins 802 Futurewei Inc. 803 2330 Central Expressway 804 Santa Clara, CA 95050 805 USA 807 Phone: +1 408 330 4586 808 EMail: charliep@computer.org