idnits 2.17.1 draft-jeong-ipwave-context-aware-navigator-05.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 date (21 February 2022) is 794 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) == Unused Reference: 'RFC4861' is defined on line 219, but no explicit reference was found in the text == Unused Reference: 'IEEE-802.11-OCB' is defined on line 260, but no explicit reference was found in the text == Outdated reference: A later version (-30) exists of draft-ietf-ipwave-vehicular-networking-26 ** 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-13 Summary: 2 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: 25 August 2022 Z. Xiang 6 Sungkyunkwan University 7 Z. Kim 8 Hyundai Motor 9 21 February 2022 11 Context-Aware Navigation Protocol for IP-Based Vehicular Networks 12 draft-jeong-ipwave-context-aware-navigator-05 14 Abstract 16 This document proposes a Context-Aware Navigation Protocol (CNP) for 17 IP-based vehicular networks for cooperative navigation among vehicles 18 in road networks. This CNP aims at the enhancement of driving safety 19 through a light-weight driving information sharing method. The CNP 20 protocol uses an IPv6 Neighbor Discovery (ND) option to convey 21 driving information such as a vehicle's position, speed, 22 acceleration/deceleration, and direction, and a driver's driving 23 action (e.g., braking and accelerating). 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at https://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on 25 August 2022. 42 Copyright Notice 44 Copyright (c) 2022 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 49 license-info) in effect on the date of publication of this document. 50 Please review these documents carefully, as they describe your rights 51 and restrictions with respect to this document. Code Components 52 extracted from this document must include Revised BSD License text as 53 described in Section 4.e of the Trust Legal Provisions and are 54 provided without warranty as described in the Revised BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 60 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 4. Vehicle Mobility Information Option . . . . . . . . . . . . . 3 62 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 63 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5 64 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 65 7.1. Normative References . . . . . . . . . . . . . . . . . . 5 66 7.2. Informative References . . . . . . . . . . . . . . . . . 6 67 Appendix A. Changes from 68 draft-jeong-ipwave-context-aware-navigator-04 . . . . . . 6 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 71 1. Introduction 73 The enhancement of driving safety is one of objectives of cooperative 74 driving in vehicular networks. Dedicated Short-Range Communications 75 (DSRC) is for vehicular communications [DSRC]. IEEE has standardized 76 a family standard suite of Wireless Access in Vehicular Environments 77 (WAVE) [WAVE]. Also, IETF has standardized an IPv6 packet delivery 78 protocol over IEEE 802.11-OCB (Outside the Context of a Basic Service 79 Set) [RFC8691], which is a MAC protocol for vehicles in WAVE. 81 A vehicle equipped with various sensors and a DSRC device can sense 82 its surrounding environment including its neighboring vehicles, and 83 share the sensed data and its mobility information (e.g., position, 84 speed, acceleration/deceleration, and direction) with its neighboring 85 vehicles. This information sharing allows vehicles to assess the 86 collision risk and make their maneuvers to avoid an accident in a 87 prompt way. That is, the capability of sensing, computing, and 88 communication of vehicles enables them to understand the driving 89 environment and situation (i.e., context), and cooperate with each 90 other during their navigation. 92 The driving information sharing enables context-aware navigation 93 where each vehicle can display its neighboring vehicles, pedestrians, 94 and obstacles in its navigation system [CASD]. With this CNP, a 95 driver can make a better decision on driving to avoid an accident, 96 and an autonomous vehicle can control its maneuver to escape from a 97 possible fatality in advance. 99 For this CNP service, this document proposes a light-weight data 100 sharing protocol using a new IPv6 Neighbor Discovery (ND) option for 101 Vehicle Mobility Information, which is called Vehicle Mobility 102 Information (VMI) option. This VMI option can be included by a 103 Neighbor Advertisement (NA) message in Vehicular Neighbor Discovery 104 (VND) [ID-Vehicular-ND]. 106 There are two messages for the CNP services with the VMI option such 107 as Cooperation Context Message (CCM) and Emergency Context Message 108 (ECM). The CCM is a message to deliver a vehicle's motion 109 information (e.g., position, speed, acceleration/deceleration, 110 direction) and a driver's driving action (e.g., braking and 111 accelerating) to its neighboring vehicles for cooperative driving. 112 The ECM is a message to notify a vehicle's neighboring vehicles of an 113 emergency situation (e.g., an accident and dangerous situation). The 114 ECM has a higher priority than the CCM such that the ECM needs to be 115 disseminated faster than the CCM in vehicular networks. 117 2. Requirements Language 119 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 120 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 121 document are to be interpreted as described in RFC 2119 [RFC2119]. 123 3. Terminology 125 This document uses the terminology described in [ID-IPWAVE-PS]. 127 4. Vehicle Mobility Information Option 129 Vehicle Mobility Information (VMI) option is an IPv6 ND option to 130 convey either a CCM or ECM. Figure 1 shows the format of the VMI 131 option. 133 0 1 2 3 134 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 136 | Type | Length | Message | Reserved1 | 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 | Reserved2 | 139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 140 | | 141 : Mobility Information : 142 | | 143 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 145 Figure 1: Vehicle Mobility Information (VMI) Option Format 147 Fields: 148 Type 8-bit identifier of the VMI option type as assigned 149 by the IANA: TBD 151 Length 8-bit unsigned integer. The length of the option 152 (including the Type and Length fields) is in units of 153 8 octets. The value is 3. 155 Message 8-bit identifier of the VMI message type as CCM (0) 156 and ECM (1). 158 Reserved1 This field is unused. It MUST be initialized to 159 zero by the sender and MUST be ignored by the 160 receiver. 162 Reserved2 This field is unused. It MUST be initialized to 163 zero by the sender and MUST be ignored by the 164 receiver. 166 Mobility Information 167 128-bit mobility information. It contains a vehicle's 168 motion information (e.g., position, speed, 169 acceleration/deceleration, direction) and a driver's 170 driving action (e.g., braking and accelerating) for 171 CCM. Also, it contains a vehicle's emergency 172 information (e.g., obstacle information and accident 173 information). 175 A CCM in a VMI option can be included in an NA message that a vehicle 176 transmits periodically to announce its existence and routing 177 information to its one-hop neighboring vehicles [ID-Vehicular-ND]. 179 An ECM in a VMI option can be included in an NA message that a 180 vehicle transmits to immediately announce an emergency situation to 181 its one-hop neighboring vehicles [ID-Vehicular-ND]. 183 To let the vehicles take an immediate action on an emergency 184 situation, the ECM has a higher priority than the CCM. Thus, if a 185 vehicle has an ECM and a CCM to send, it SHOULD transmit the ECM 186 earlier than the CCM. 188 5. Security Considerations 190 This document shares all the security issues of the IPv6 ND protocol. 191 This document can get benefits from Secure Neighbor Discovery (SEND) 192 [RFC3971] in order to protect exchanged messages from possible 193 security attacks. 195 6. Acknowledgments 197 This work was supported by the National Research Foundation of Korea 198 (NRF) grant funded by the Korea government, Ministry of Science and 199 ICT (MSIT) (No. 2020R1F1A1048263). 201 This work was supported in part by Institute of Information & 202 Communications Technology Planning & Evaluation (IITP) grant funded 203 by the Korea MSIT (Ministry of Science and ICT) (R-20160222-002755, 204 Cloud based Security Intelligence Technology Development for the 205 Customized Security Service Provisioning). 207 This work was supported in part by the MSIT under the ITRC 208 (Information Technology Research Center) support program (IITP- 209 2022-2017-0-01633) supervised by the IITP. 211 7. References 213 7.1. Normative References 215 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 216 Requirement Levels", BCP 14, RFC 2119, March 1997, 217 . 219 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 220 "Neighbor Discovery for IP Version 6 (IPv6)", RFC 4861, 221 September 2007, . 223 [RFC3971] Arkko, J., "SEcure Neighbor Discovery (SEND)", RFC 3971, 224 March 2005, . 226 [RFC8691] Benamar, N., Haerri, J., Lee, J., and T. Ernst, "Basic 227 Support for IPv6 Networks Operating Outside the Context of 228 a Basic Service Set over IEEE Std 802.11", RFC 8691, 229 December 2019, . 231 [ID-IPWAVE-PS] 232 Jeong, J., "IPv6 Wireless Access in Vehicular Environments 233 (IPWAVE): Problem Statement and Use Cases", Work in 234 Progress, Internet-Draft, draft-ietf-ipwave-vehicular- 235 networking-26, February 2022, 236 . 239 7.2. Informative References 241 [ID-Vehicular-ND] 242 Jeong, J., Ed., Shen, Y., Xiang, Z., and S. Cespedes, 243 "Vehicular Neighbor Discovery for IP-Based Vehicular 244 Networks", Work in Progress, Internet-Draft, draft-jeong- 245 ipwave-vehicular-neighbor-discovery-13, February 2022, 246 . 249 [DSRC] ASTM International, "Standard Specification for 250 Telecommunications and Information Exchange Between 251 Roadside and Vehicle Systems - 5 GHz Band Dedicated Short 252 Range Communications (DSRC) Medium Access Control (MAC) 253 and Physical Layer (PHY) Specifications", 254 ASTM E2213-03(2010), October 2010. 256 [WAVE] IEEE 1609 Working Group, "IEEE Guide for Wireless Access 257 in Vehicular Environments (WAVE) - Architecture", IEEE Std 258 1609.0-2013, March 2014. 260 [IEEE-802.11-OCB] 261 "Part 11: Wireless LAN Medium Access Control (MAC) and 262 Physical Layer (PHY) Specifications", IEEE Std 263 802.11-2016, December 2016. 265 [CASD] Shen, Y., Jeong, J., Oh, T., and S. Son, "CASD: A 266 Framework of Context-Awareness Safety Driving in Vehicular 267 Networks", International Workshop on Device Centric Cloud 268 (DC2), March 2016. 270 Appendix A. Changes from draft-jeong-ipwave-context-aware-navigator-04 272 The following changes are made from draft-jeong-ipwave-context-aware- 273 navigator-04: 275 * This version has fixed typos from the preveous version to maintain 276 the active status of the document. 278 Authors' Addresses 280 Jaehoon (Paul) Jeong 281 Department of Computer Science and Engineering 282 Sungkyunkwan University 283 2066 Seobu-Ro, Jangan-Gu 284 Suwon 285 Gyeonggi-Do 286 16419 287 Republic of Korea 288 Phone: +82 31 299 4957 289 Email: pauljeong@skku.edu 290 URI: http://iotlab.skku.edu/people-jaehoon-jeong.php 292 Bien Aime Mugabarigira 293 Department of Electrical and Computer Engineering 294 Sungkyunkwan University 295 2066 Seobu-Ro, Jangan-Gu 296 Suwon 297 Gyeonggi-Do 298 16419 299 Republic of Korea 300 Phone: +82 10 5964 8794 301 Email: bienaime@skku.edu 303 Yiwen (Chris) Shen 304 Department of Electrical and Computer Engineering 305 Sungkyunkwan University 306 2066 Seobu-Ro, Jangan-Gu 307 Suwon 308 Gyeonggi-Do 309 16419 310 Republic of Korea 311 Phone: +82 31 299 4106 312 Email: chrisshen@skku.edu 313 Zhong Xiang 314 Department of Electrical and Computer Engineering 315 Sungkyunkwan University 316 2066 Seobu-Ro, Jangan-Gu 317 Suwon 318 Gyeonggi-Do 319 16419 320 Republic of Korea 321 Phone: +82 10 9895 1211 322 Email: xz618@skku.edu 324 Zeung Il (Ben) Kim 325 Electric Energy Control Test Team 326 Hyundai Motor 327 150 Hyundaiyeonguso-ro, Namyang-eup 328 Hwaseong 329 Gyeonggi-Do 330 18280 331 Republic of Korea 332 Phone: +82-10-8805-3810 333 Email: ben.kim@hyundai.com