idnits 2.17.1 draft-jeong-ipwave-vehicular-mobility-management-06.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 (21 August 2021) is 972 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) == Missing Reference: 'VMI' is mentioned on line 486, but not defined ** Obsolete normative reference: RFC 3775 (Obsoleted by RFC 6275) ** Downref: Normative reference to an Informational RFC: RFC 7333 ** Downref: Normative reference to an Informational RFC: RFC 7429 ** Downref: Normative reference to an Experimental RFC: RFC 8885 == Outdated reference: A later version (-30) exists of draft-ietf-ipwave-vehicular-networking-20 ** Downref: Normative reference to an Informational draft: draft-ietf-ipwave-vehicular-networking (ref. 'ID-IPWAVE-PS') == Outdated reference: A later version (-17) exists of draft-jeong-ipwave-vehicular-neighbor-discovery-12 Summary: 6 errors (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IPWAVE Working Group J. Jeong 3 Internet-Draft B. Mugabarigira 4 Intended status: Standards Track Y. Shen 5 Expires: 22 February 2022 Z. Xiang 6 Sungkyunkwan University 7 21 August 2021 9 Vehicular Mobility Management for IP-Based Vehicular Networks 10 draft-jeong-ipwave-vehicular-mobility-management-06 12 Abstract 14 This document specifies a Vehicular Mobility Management (VMM) scheme 15 for IP-based vehicular networks. The VMM scheme takes advantage of a 16 vehicular link model based on a multi-link subnet. With a vehicle's 17 mobility information (e.g., position, speed, acceleration/ 18 deceleration, and direction) and navigation path (i.e., trajectory), 19 it can provide a moving vehicle with proactive and seamless handoff 20 along with its trajectory. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at https://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on 22 February 2022. 39 Copyright Notice 41 Copyright (c) 2021 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 46 license-info) in effect on the date of publication of this document. 47 Please review these documents carefully, as they describe your rights 48 and restrictions with respect to this document. Code Components 49 extracted from this document must include Simplified BSD License text 50 as described in Section 4.e of the Trust Legal Provisions and are 51 provided without warranty as described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 56 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 57 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 4. Vehicular Network Architecture . . . . . . . . . . . . . . . 4 59 4.1. Vehicular Network . . . . . . . . . . . . . . . . . . . . 4 60 5. Mobility Management . . . . . . . . . . . . . . . . . . . . . 6 61 5.1. Network Attachment of a Vehicle . . . . . . . . . . . . . 6 62 5.2. Handoff within One Prefix Domain . . . . . . . . . . . . 8 63 5.3. Handoff between Multiple Prefix Domains . . . . . . . . . 10 64 6. Security Considerations . . . . . . . . . . . . . . . . . . . 12 65 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 66 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 67 8.1. Normative References . . . . . . . . . . . . . . . . . . 12 68 8.2. Informative References . . . . . . . . . . . . . . . . . 13 69 Appendix A. Changes from 70 draft-jeong-ipwave-vehicular-mobility-management-05 . . . 14 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 73 1. Introduction 75 This document proposes a mobility management scheme for IP-based 76 vehicular networks, called Vehicular Mobility Management (VMM). The 77 VMM is tailored for a vehicular network architecture and a vehicular 78 link model described in the IPWAVE problem statement document 79 [ID-IPWAVE-PS]. 81 Vehicle Neighbor Discovery (VND) is proposed as Extended IPv6 82 Neighbor Discovery (ND) for IP-based vehicle networks [ID-IPWAVE-VND] 83 to support the vehicle-to-vehicle or the vehicle to Road-Side Unit 84 (RSU) interactions. For an efficient IPv6 Stateless Address 85 Autoconfiguration (SLAAC) [RFC4862], VND adopts an optimized Address 86 Registration using a multihop Duplicate Address Detection (DAD). 87 This multihop DAD enables a vehicle to have a unique IP address in a 88 multi-link subnet consisting of multiple wireless subnets with the 89 same IP prefix, which corresponds to wireless coverage of multiple 90 RSUs. VND also supports IP packet routing over a connected Vehicular 91 Ad Hoc Network (VANET) by allowing vehicles to exchange the prefixes 92 of their internal networks through their external wireless interface. 94 The mobility management in this multi-link subnet needs a new 95 approach from the legacy mobility management schemes. This document 96 aims at an efficient mobility management scheme called VMM to support 97 efficient V2V, V2I, and V2X communications in a road network. The 98 VMM takes advantage of the mobility information (e.g.,a vehicle's 99 speed, direction, and position) and trajectory (i.e., navigation 100 path) of each vehicle registered in the Traffic Control Center (TCC) 101 of the vehicular cloud. 103 2. Requirements Language 105 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 106 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 107 document are to be interpreted as described in RFC 2119 [RFC2119]. 109 3. Terminology 111 This document uses the terminology described in [RFC4861] and 112 [RFC4862]. In addition, the following new terms are defined as 113 below: 115 * DMM: Acronym for "Distributed Mobility Management" 116 [RFC7333][RFC7429]. 118 * Mobility Anchor (MA): A node that maintains the IP addresses and 119 mobility information of vehicles in a road network to support 120 their address autoconfiguration and mobility management with a 121 binding table. It has end-to-end connections with RSUs under its 122 control. 124 * On-Board Unit (OBU): A node that with a network interface (e.g., 125 IEEE 802.11-OCB and Cellular V2X (C-V2X) [TS-23.285-3GPP]) for 126 wireless communications with other OBUs and RSUs, and may be 127 connected to in-vehicle devices or networks. An OBU is mounted on 128 a vehicle. It is assumed that a radio navigation receiver (e.g., 129 Global Positioning System (GPS)) is included in a vehicle with an 130 OBU for efficient navigation. 132 * OCB: Acronym for "Outside the Context of a Basic Service Set" 133 [IEEE-802.11-OCB]. 135 * Road-Side Unit (RSU): A node that has physical communication 136 devices (e.g., IEEE 802.11-OCB and C-V2X) for wireless 137 communication with vehicles and is also connected to the Internet 138 as a router or switch for packet forwarding. An RSU is typically 139 deployed on the road infrastructure, either at an intersection or 140 in a road segment, but may also be located in cars parking areas. 142 * Traffic Control Center (TCC): A node that maintains road 143 infrastructure information (e.g., RSUs, traffic signals, and loop 144 detectors), vehicular traffic statistics (e.g., average vehicle 145 speed and vehicle inter-arrival time per road segment), and 146 vehicle information (e.g., a vehicle's identifier, position, 147 direction, speed, and trajectory as a navigation path). TCC is 148 included in a vehicular cloud for vehicular networks. 150 * Vehicular Cloud: A cloud infrastructure for vehicular networks, 151 having compute nodes, storage nodes, and network nodes. 153 * WAVE: Acronym for "Wireless Access in Vehicular Environments" 154 [WAVE-1609.0]. 156 4. Vehicular Network Architecture 158 This section describes a vehicular network architecture for V2V and 159 V2I communication. A vehicle and an RSU have their internal networks 160 including in-vehicle devices or servers, respectively. 162 4.1. Vehicular Network 164 A vehicular network architecture for V2I and V2V is illustrated in 165 Figure 1. In this figure, there is a vehicular cloud containing a 166 TCC. The TCC has Mobility Anchors (MAs) responsible for the vehicles 167 mobility management. Each MA is in charge of the mobility management 168 of vehicles under its prefix domain, which is a multi-link subnet of 169 RSUs sharing the same prefix [ID-IPWAVE-PS]. A vehicular network is 170 a wireless network consisting of RSUs and vehicles. The RSUs are 171 interconnected via a wired network, allowing vehicles to build VANETs 172 via V2V and V2I communications. 174 *-----------------------------------------* 175 * TCC in Vehicular Cloud * 176 * +-------------------------------------+ * 177 +--------+ * | +---------+ +---------+ | * 178 | CN1 |<---->* | | MA1 |<------->| MA2 | | * 179 +--------+ * | +---------+ +---------+ | * 180 * +-------------------------------------+ * 181 * ^ ^ * 182 * | INTERNET | * 183 *---------v--------------------v----------* 184 ^ ^ ^ 185 | Ethernet | | 186 | | | 187 v v v 188 +--------+ Ethernet +--------+ Ethernet +--------+ 189 | RSU1 |<-------->| RSU2 |<-------->| RSU3 | 190 +--------+ +--------+ +--------+ 191 ^ ^ ^ 192 : : : 193 +-----------------------------------+ +-----------------+ 194 | : V2I V2I : | | V2I : | 195 | v v | | v | 196 +--------+ | +--------+ +--------+ | | +--------+ | 197 |Vehicle1|===> |Vehicle2|===> |Vehicle3|===> | | |Vehicle4|===> | 198 | |<.....>| |<.....>| | | | | | | 199 +--------+ V2V +--------+ V2V +--------+ | | +--------+ | 200 | | | | 201 +-----------------------------------+ +-----------------+ 202 Subnet1 Subnet2 204 <----> Wired Link <....> Wireless Link ===> Moving Direction 206 Figure 1: A Vehicular Network Architecture for V2I and V2V Networking 208 In Figure 1, three RSUs are deployed either at intersections or along 209 roadways. They are connected to an MA through wired networks. The 210 vehicular network has two subnets, such as Subnet1 and Subnet2. 211 Subnet1 is a multi-link subnet consisting of multiple wireless 212 coverage areas of multiple RSUs, which share the same IPv6 prefix to 213 construct a single logical subnet [ID-IPWAVE-PS]. That is, the RSU1 214 and RSU2 wireless links belong to Subnet1. Thus, since Vehicle2 and 215 Vehicle3 use the same prefix for Subnet1 and they are within the 216 wireless communication range, they can communicate directly with each 217 other. Note that in a multi-link subnet, a vehicle (e.g., Vehicle2 218 and Vehicle3 in Figure 1) can configure its global IPv6 address 219 through an address registration procedure that includes the multihop 220 DAD specified in VND [ID-IPWAVE-VND]. 222 Subnet2 on the other hand, uses a different prefix than Subnet1. 223 Vehicle4 residing in Subnet2 cannot communicate directly to Vehicle3 224 because it belongs to a different subnet. Vehicles can construct a 225 connected VANET so they can communicate with each other without the 226 relaying on RSU, but the forwarding over the VANET. In the case 227 where two vehicles belong to the same multi-link subnet, but they are 228 not connected in the same VANET, they can use RSUs. In Figure 1, 229 even though Vehicle1 is disconnected from Vehicle3, they can 230 communicate indirectly with each other through RSUs such as RSU1 and 231 RSU2. 233 This document specifies a mobility management scheme for the 234 vehicular network architecture, as shown in Figure 1. Vehicle2 is 235 supposed to communicates with the corresponding node denoted as CN1, 236 and Vehicle2 is moving in the wireless coverage of RSU1. When 237 Vehicle2 moves out of the coverage of RSU1 and moves into the 238 coverage of RSU2 where RSU1 and RSU2 share the same prefix, packets 239 sent by CN1 should be routed through RSU2 to Vehicle2. Also, when 240 Vehicle2 moves out of the coverage of RSU2 and moves into the 241 coverage of RSU3 where RSU2 and RSU3 use two different prefixes, the 242 CN1 packets should be delivered to Vehicle2 via RSU3. A handoff 243 procedure allows a sender's packets to be delivered to a destination 244 vehicle which is moving within the wireless coverage areas. 246 5. Mobility Management 248 This section explains the detailed procedure of mobility management 249 of a vehicle in a road network as shown in Figure 1. 251 5.1. Network Attachment of a Vehicle 253 A mobility management is required for the seamless communication of 254 vehicles moving between the RSUs. When a vehicle moves into the 255 coverage of another RSU, a different IP address is assigned to the 256 vehicle, the transport-layersession information (i.e., an end-point's 257 IP address) is reconfigured to avoid service disruption. Considering 258 this issue, this document proposes a handoff mechanism for seamless 259 communication. 261 In [VIP-WAVE], the authors constructed a network-based mobility 262 management scheme using Proxy Mobile IPv6 (PMIPv6) [RFC5213], which 263 is highly suitable for vehicular networks. This document uses a 264 mobility management procedure similar to PMIPv6, but uses a newly 265 proposed Shared-Prefix model in which vehicles in the same subnet 266 share the same prefix. 268 Vehicle RSU MA 269 | | | 270 |-RS with Mobility Info->| | 271 | [VMI] | | 272 | | | 273 | |--------PBU------>| 274 | | | 275 | | | 276 | |<-------PBA-------| 277 | | | 278 | | | 279 | |===Bi-Dir Tunnel==| 280 | | | 281 | | | 282 |<----RA with prefix-----| | 283 | | | 285 Figure 2: Message Interaction for a Vehicle's Network Attachment 287 Figure 2 shows the binding update flow when a vehicle entered the RSU 288 subnet. The RSUs act as Mobility Anchor Gateway (MAG) defined in 289 [VIP-WAVE]. When it receives an RS message from a vehicle containing 290 its mobility information (e.g., position, speed, and direction), an 291 RSU sends a Proxy Binding Update (PBU) message to its MA 292 [RFC5213][RFC3775]. This contains a Mobility Option including the 293 vehicle's mobility information. The MA receives the PBU and sets up 294 a Binding Cache Entry (BCE) as well as a bi-directional tunnel 295 (denoted as Bi-Dir Tunnel in Figure 2) between the serving RSU and 296 itself. Through this tunnel, all traffic packets to the vehicle are 297 encapsulated toward the RSU. Simultaneously, the MA sends back a 298 Proxy Binding Acknowledgment (PBA) message to the serving RSU. This 299 serving RSU receives the PBA and sets up a bi-directional tunnel with 300 the MA. After this binding update, the RSU sends back an RA message 301 to the vehicle. This message includes the RSU's prefix for the 302 address autoconfiguration of the vehicle. 304 When the vehicle receives the RA message, it performs the address 305 registration procedure including a multihop DAD for its global IP 306 address based on the prefix announced by the RA message according to 307 the VND [ID-IPWAVE-VND]. 309 In PMIPv6, an MA (i.e., LMA) allocates a unique prefix to each 310 vehicle to guarantee the uniqueness of each address, but in this 311 document, an MA allocates in its domain a unique IP address to each 312 vehicle with the same prefix through the multihop-DAD-based address 313 registration. This unique IP address allocation ensures that 314 vehicles own unique IP addresses in a multi-link subnet and can 315 reduce the waste of IP prefixes in legacy PMIPv6. 317 5.2. Handoff within One Prefix Domain 319 When the vehicle changes its location and its current RSU (denoted as 320 c-RSU) detects that the vehicle is moving out of its coverage, the 321 c-RSU reports the leaving of the vehicle to the MA and de-register 322 the binding via PBU. 324 Vehicle c-RSU MA n-RSU 325 | | | | 326 | |===Bi-Dir Tunnel==| | 327 | | | | 328 | | | | 329 | |----DeReg PBU---->| | 330 | | | | 331 | | | | 332 | |<-------PBA-------| | 333 | | | | 334 | | | | 335 | | | | 336 | | | | 337 | | | | 338 |(------------------RS with Mobility Info-------------->)| 339 | [VMI] | | 340 | |<-------PBU-------| 341 | | | 342 | | | 343 | |--------PBA------>| 344 | | | 345 | | | 346 | |===Bi-Dir Tunnel==| 347 | | | 348 | | | 349 |<--------------------RA with prefix---------------------| 350 | | 352 Figure 3: Handoff of a Vehicle within One Prefix Domain with PMIPv6 354 With this report, the MA will send back a PBA to notice the de- 355 register to c-RSU, and get ready to detect new binding requests. If 356 MA can figure out the new RSU (denoted as n-RSU) based on the 357 vehicle's trajectory, it will directly change the end-point of the 358 tunnel into n-RSU's IP address for the vehicle. 360 Figure 3 shows the handoff of a vehicle within one prefix domain 361 (i.e., a multi-link subnet) with PMIPv6. As shown in the figure, 362 when the MA receives a new PBU from the n-RSU, it changes the 363 tunnel's end-point from the c-RSU to n-RSU. If there are ongoing IP 364 packets toward the vehicle, the MA encapsulates the packets and then 365 forwards them towards n-RSU. Through this network-based mobility 366 management, the vehicle is not aware of any changes at its network 367 layer and can maintain its transport-layer sessions without any 368 disruption. 370 Vehicle c-RSU n-RSU 371 | | | 372 |---------------------| | 373 |c-RSU detects leaving| | 374 |---------------------| | 375 | |--------PBU------>| 376 | | | 377 | |===Bi-Dir Tunnel==| 378 | | | 379 | |<-------PBA-------| 380 | | | 381 | | | 382 |(--------RS with Mobility Info-------->)| 383 | [VMI] | 384 | | 385 |<------------RA with prefix-------------| 386 | | 388 Figure 4: Handoff of a Vehicle within One Prefix Domain with DMM 390 If c-RSU and n-RSU are adjacent, that is, vehicles are moving in 391 specified routes with fixed RSU allocation, the procedure can be 392 simplified by constructing the bidirectional tunnel directly between 393 them (cancel the intervention of MA) to alleviate the traffic flow in 394 MA as well as reduce handoff delay. 396 Figure 4 shows a vehicle handoff within one prefix domain (as a 397 multi-link subnet) with DMM [RFC8885]. The RSUs are in charge of 398 detecting when a node joins or moves to its domain. If the c-RSU 399 detects that the vehicle is going to leave its coverage and to enter 400 the area of an adjacent RSU, it sends a PBU message to inform n-RSU 401 of the vehicle's handoff. If n-RSU receives the PBU message, it 402 constructs a bidirectional tunnel between c-RSU and itself, and then 403 sends back a PBA message as an acknowledgment to c-RSU. If there are 404 ongoing IP packets toward the vehicle, c-RSU encapsulates the packets 405 and then forwards them to n-RSU. When n-RSU detects the entrance of 406 the vehicle, it directly sends an RA message to the vehicle so that 407 the vehicle can assure that it is still connected to a router with 408 its current prefix. If the vehicle sends an RS message to n-RSU, 409 n-RSU responds to the RS message by replying to the vehicle with an 410 RA . 412 5.3. Handoff between Multiple Prefix Domains 414 When the vehicle moves from a prefix domain to another prefix domain, 415 a handoff between multiple prefix domains is required. As shown in 416 Figure 1, when Vehicle3 moves from the subnet of RSU2 (i.e., Subnet1) 417 to the subnet of RSU3 (i.e., Subnet2), a multiple domain handoff is 418 performed through the cooperation of RSU2, RSU3, MA1 and MA2. 420 Vehicle c-RSU MA1 MA2 n-RSU 421 | | | | | 422 | |==Bi-Dir Tunnel==| | | 423 | | | | | 424 | | | | | 425 | |---DeReg PBU---->| | | 426 | | |-------PBU----->| | 427 | | | | | 428 | |<------PBA-------| |-------PBA------>| 429 | | | | | 430 | | | |==Bi-Dir Tunnel==| 431 | | | | | 432 | | | | | 433 |(----------------------RS with Mobility Info------------------->)| 434 | | [VMI] | | 435 | | | | | 436 | | | | | 437 |<----------------------RA with prefix1 (c-RSU)-------------------| 438 | | | | | 439 |<----------------------RA with prefix2 (n-RSU)-------------------| 440 | | | | | 442 Figure 5: Handoff of a Vehicle between Multiple Prefix Domains 443 with PMIPv6 445 Figure 5 shows the handoff of a vehicle between two prefix domains 446 (i.e., two multi-link subnets) with PMIPv6. When the vehicle moves 447 out of its c-RSU belonging to Subnet1, and moves into the n-RSU 448 belonging to Subnet2, c-RSU detects the vehicle's leaving and reports 449 it to MA1. MA1 figures out that the vehicle will get into the 450 coverage of the n-RSU based on its trajectory and sends MA2 a PBU 451 message to inform MA2 that the vehicle will enter the coverage of 452 n-RSU belonging to MA2. MA2 sends a PBA message to n-RSU to inform 453 that the vehicle will enter the coverage of n-RSU along with handoff 454 context such as c-RSU's context information (e.g., c-RSU's link-local 455 address and prefix called prefix1), and the vehicle's context 456 information (e.g., the vehicle's global IP address and MAC address). 457 After n-RSU receives the PBA message including the handoff context 458 from MA2, it sets up a bi-directional tunnel with MA2, and generates 459 RA messages with c-RSU's context information. That is, n-RSU 460 pretends to be a router belonging to Subnet1. When the vehicle 461 receives RA from n-RSU, it can maintain its connection with its 462 corresponding node (i.e., CN1). Note that n-RSU also sends RA 463 messages with its domain prefix called prefix2. The vehicle 464 configures another global IP address with prefix2, and can use it for 465 communication with neighboring vehicles under the coverage of n-RSU. 467 If c-RSU and n-RSU are adjacent, that is, vehicles are moving in 468 specified routes with fixed RSU allocation, the procedure can be 469 simplified by constructing the bidirectional tunnel directly between 470 them (cancel the intervention of MAs) to alleviate the traffic flow 471 in MA as well as reduce handoff delay. 473 Vehicle c-RSU n-RSU 474 | | | 475 |---------------------| | 476 |c-RSU detects leaving| | 477 |---------------------| | 478 | |--------PBU------>| 479 | | | 480 | |===Bi-Dir Tunnel==| 481 | | | 482 | |<-------PBA-------| 483 | | | 484 | | | 485 |(--------RS with Mobility Info-------->)| 486 | [VMI] | 487 | | 488 |<--------RA with prefix1 (c-RSU)--------| 489 | | 490 |<--------RA with prefix2 (n-RSU)--------| 491 | | 493 Figure 6: Handoff of a Vehicle within Multiple Prefix Domains 494 with DMM 496 Figure 6 shows the vehicle handoff within two prefix domains (as two 497 multi-link subnets) with DMM [RFC8885]. If c-RSU detects that the 498 vehicle is going to leave its coverage and to enter the area of an 499 adjacent RSU (n-RSU) belonging to a different prefix domain, it sends 500 a PBU message to inform n-RSU that the vehicle will enter the 501 coverage of n-RSU along with handoff context such as c-RSU's context 502 information (e.g., c-RSU's link-local address and prefix called 503 prefix1), and the vehicle's context information (e.g., the vehicle's 504 global IP address and MAC address). After n-RSU receives the PBA 505 message including the handoff context from c-RSU, it sets up a bi- 506 directional tunnel with c-RSU, and generates RA messages with c-RSU's 507 context information. That is, n-RSU pretends to be a router 508 belonging to Subnet1. When the vehicle receives RA from n-RSU, it 509 can maintain its connection with its corresponding node (i.e., CN1). 510 Note that n-RSU also sends RA messages with its domain prefix called 511 prefix2. The vehicle configures another global IP address with 512 prefix2, and can use it for communication with neighboring vehicles 513 under the coverage of n-RSU. 515 6. Security Considerations 517 This document shares all the security issues of Vehicular ND 518 [ID-IPWAVE-VND], Proxy MIPv6 [RFC5213], and DMM 519 [RFC7333][RFC7429][RFC8885]. 521 7. Acknowledgments 523 This work was supported by the National Research Foundation of Korea 524 (NRF) grant funded by the Korea government, Ministry of Science and 525 ICT (MSIT) (No. 2020R1F1A1048263). 527 This work was supported in part by Institute of Information & 528 Communications Technology Planning & Evaluation (IITP) grant funded 529 by the Korea MSIT (Ministry of Science and ICT) (R-20160222-002755, 530 Cloud based Security Intelligence Technology Development for the 531 Customized Security Service Provisioning). 533 This work was supported in part by the MSIT under the ITRC 534 (Information Technology Research Center) support program (IITP- 535 2021-2017-0-01633) supervised by the IITP. 537 8. References 539 8.1. Normative References 541 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 542 Requirement Levels", BCP 14, RFC 2119, March 1997, 543 . 545 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 546 "Neighbor Discovery for IP Version 6 (IPv6)", RFC 4861, 547 September 2007, . 549 [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless 550 Address Autoconfiguration", RFC 4862, September 2007, 551 . 553 [RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., and K. 554 Chowdhury, "Proxy Mobile IPv6", RFC 5213, August 2008, 555 . 557 [RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support 558 in IPv6", RFC 3775, June 2004, 559 . 561 [RFC7333] Chan, H., Liu, D., Seite, P., Yokota, H., and J. Korhonen, 562 "Requirements for Distributed Mobility Management", 563 RFC 7333, August 2014, 564 . 566 [RFC7429] Liu, D., Zuniga, JC., Seite, P., Chan, H., and CJ. 567 Bernardos, "Distributed Mobility Management: Current 568 Practices and Gap Analysis", RFC 7429, January 2015, 569 . 571 [RFC8885] Bernardos, CJ., Oliva, A. de la., Giust, F., Zuniga, JC., 572 and A. Mourad, "Proxy Mobile IPv6 Extensions for 573 Distributed Mobility Management", RFC 8885, October 2020, 574 . 576 [ID-IPWAVE-PS] 577 Jeong, J., Ed., "IPv6 Wireless Access in Vehicular 578 Environments (IPWAVE): Problem Statement and Use Cases", 579 Work in Progress, Internet-Draft, draft-ietf-ipwave- 580 vehicular-networking-20, March 2021, 581 . 584 8.2. Informative References 586 [ID-IPWAVE-VND] 587 Jeong, J., Ed., Shen, Y., Xiang, Z., and S. Cespedes, 588 "Vehicular Neighbor Discovery for IP-Based Vehicular 589 Networks", Work in Progress, Internet-Draft, draft-jeong- 590 ipwave-vehicular-neighbor-discovery-12, August 2021, 591 . 594 [VIP-WAVE] Cespedes, S., Lu, N., and X. Shen, "VIP-WAVE: On the 595 Feasibility of IP Communications in 802.11p Vehicular 596 Networks", IEEE Transactions on Intelligent Transportation 597 Systems, vol. 14, no. 1, March 2013. 599 [IEEE-802.11-OCB] 600 "Part 11: Wireless LAN Medium Access Control (MAC) and 601 Physical Layer (PHY) Specifications", IEEE Std 602 802.11-2016, December 2016. 604 [WAVE-1609.0] 605 IEEE 1609 Working Group, "IEEE Guide for Wireless Access 606 in Vehicular Environments (WAVE) - Architecture", IEEE Std 607 1609.0-2013, March 2014. 609 [TS-23.285-3GPP] 610 3GPP, "Architecture Enhancements for V2X Services", 3GPP 611 TS 23.285, June 2018. 613 Appendix A. Changes from draft-jeong-ipwave-vehicular-mobility- 614 management-05 616 The following changes are made from draft-jeong-ipwave-vehicular- 617 mobility-management-05: 619 * This version has a submission date update to maintain the active 620 status of the document. 622 Authors' Addresses 624 Jaehoon (Paul) Jeong 625 Department of Computer Science and Engineering 626 Sungkyunkwan University 627 2066 Seobu-Ro, Jangan-Gu 628 Suwon 629 Gyeonggi-Do 630 16419 631 Republic of Korea 633 Phone: +82 31 299 4957 634 Email: pauljeong@skku.edu 635 URI: http://iotlab.skku.edu/people-jaehoon-jeong.php 637 Bien Aime Mugabarigira 638 Department of Electrical and Computer Engineering 639 Sungkyunkwan University 640 2066 Seobu-Ro, Jangan-Gu 641 Suwon 642 Gyeonggi-Do 643 16419 644 Republic of Korea 646 Phone: +82 10 5964 8794 647 Email: bienaime@skku.edu 649 Yiwen (Chris) Shen 650 Department of Electrical and Computer Engineering 651 Sungkyunkwan University 652 2066 Seobu-Ro, Jangan-Gu 653 Suwon 654 Gyeonggi-Do 655 16419 656 Republic of Korea 658 Phone: +82 31 299 4106 659 Email: chrisshen@skku.edu 661 Zhong Xiang 662 Department of Electrical and Computer Engineering 663 Sungkyunkwan University 664 2066 Seobu-Ro, Jangan-Gu 665 Suwon 666 Gyeonggi-Do 667 16419 668 Republic of Korea 670 Phone: +82 10 9895 1211 671 Email: xz618@skku.edu