idnits 2.17.1 draft-jeong-ipwave-context-aware-navigator-02.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 (November 2, 2020) is 1269 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 228, but no explicit reference was found in the text == Unused Reference: 'IEEE-802.11-OCB' is defined on line 257, but no explicit reference was found in the text == Outdated reference: A later version (-30) exists of draft-ietf-ipwave-vehicular-networking-19 ** 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-10 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: May 6, 2021 Z. Xiang 6 Sungkyunkwan University 7 Z. Zeung 8 Hyundai Motor 9 November 2, 2020 11 Context-Aware Navigation Protocol for IP-Based Vehicular Networks 12 draft-jeong-ipwave-context-aware-navigator-02 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 May 6, 2021. 42 Copyright Notice 44 Copyright (c) 2020 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 49 (https://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 60 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 61 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 4. Vehicle Mobility Information Option . . . . . . . . . . . . . 3 63 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 64 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5 65 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 66 7.1. Normative References . . . . . . . . . . . . . . . . . . 5 67 7.2. Informative References . . . . . . . . . . . . . . . . . 6 68 Appendix A. Changes from draft-jeong-ipwave-context-aware- 69 navigator-01 . . . . . . . . . . . . . . . . . . . . 7 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 72 1. Introduction 74 The enhancement of driving safety is one of objectives of cooperative 75 driving in vehicular networks. Dedicated Short-Range Communications 76 (DSRC) is for vehicular communications [DSRC]. IEEE has standardized 77 a family standard suite of Wireless Access in Vehicular Environments 78 (WAVE) [WAVE]. Also, IETF has standardized an IPv6 packet delivery 79 protocol over IEEE 802.11-OCB (Outside the Context of a Basic Service 80 Set) [RFC8691], which is a MAC protocol for vehicles in WAVE. 82 A vehicle equipped with various sensors and the a DSRC device can 83 sense its surrounding environment including its neighboring vehicles, 84 and share the sensed data and its mobility information (e.g., 85 position, speed, acceleration/deceleration, and direction) with its 86 neighboring vehicles. This information sharing allows vehicles to 87 assess the collision risk and make their maneuvers to avoid an 88 accident in a prompt way. That is, the capability of sensing, 89 computing, and communication of vehicles enables them to understand 90 the driving environment and situation (i.e., context), and cooperate 91 with each other during their navigation. 93 The driving information sharing enables context-aware navigation 94 where each vehicle can display its neighboring vehicles, pedestrians, 95 and obstacles in its navigation system [CASD]. With this CNP, a 96 driver can make a better decision on driving to avoid an accident, 97 and an autonomous vehicle can control its maneuver to escape from a 98 possible fatality in advance. 100 For this CNP service, this document proposes a light-weight data 101 sharing protocol using a new IPv6 Neighbor Discovery (ND) option for 102 Vehicle Mobility Information, which is called Vehicle Mobility 103 Information (VMI) option. This VMI option can be included by a 104 Neighbor Advertisement (NA) message in Vehicular Neighbor Discovery 105 (VND) [ID-Vehicular-ND]. 107 There are two messages for the CNP service with the VMI option such 108 as Cooperation Context Message (CCM) and Emergency Context Message 109 (ECM). The CCM is a message to deliver a vehicle's motion 110 information (e.g., position, speed, acceleration/deceleration, 111 direction) and a driver's driving action (e.g., braking and 112 accelerating) to its neighboring vehicles for cooperative driving. 113 The ECM is a message to notify a vehicle's neighboring vehicles of an 114 emergency situation (e.g., an accident and dangerous situation). The 115 ECM has a higher priority than the CCM such that the ECM needs to be 116 disseminated faster than the CCM in vehicular networks. 118 2. Requirements Language 120 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 121 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 122 document are to be interpreted as described in RFC 2119 [RFC2119]. 124 3. Terminology 126 This document uses the terminology described in [ID-IPWAVE-PS]. 128 4. Vehicle Mobility Information Option 130 Vehicle Mobility Information (VMI) option is an IPv6 ND option to 131 convey either a CCM or ECM. Figure 1 shows the format of the VMI 132 option. 134 0 1 2 3 135 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 136 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 137 | Type | Length | Message | Reserved1 | 138 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 139 | Reserved2 | 140 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 141 | | 142 : Mobility Information : 143 | | 144 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 146 Figure 1: Vehicle Mobility Information (VMI) Option Format 148 Fields: 149 Type 8-bit identifier of the VMI option type as assigned 150 by the IANA: TBD 152 Length 8-bit unsigned integer. The length of the option 153 (including the Type and Length fields) is in units of 154 8 octets. The value is 3. 156 Message 8-bit identifier of the VMI message type as CCM (0) 157 and ECM (1). 159 Reserved1 This field is unused. It MUST be initialized to 160 zero by the sender and MUST be ignored by the 161 receiver. 163 Reserved2 This field is unused. It MUST be initialized to 164 zero by the sender and MUST be ignored by the 165 receiver. 167 Mobility Information 168 128-bit mobility information. It contains a vehicle's 169 motion information (e.g., position, speed, 170 acceleration/deceleration, direction) and a driver's 171 driving action (e.g., braking and accelerating) for 172 CCM. Also, it contains a vehicle's emergency 173 information (e.g., obstacle information and accident 174 information). 176 A CCM in a VMI option can be included in an NA message that a vehicle 177 transmits periodically to announce its existence and routing 178 information to its one-hop neighboring vehicles [ID-Vehicular-ND]. 180 An ECM in a VMI option can be included in an NA message that a 181 vehicle transmits to immediately announce an emergency situation to 182 its one-hop neighboring vehicles [ID-Vehicular-ND]. 184 To let the vehicles take an immediate action on an emergency 185 situation, the ECM has a higher priority than the CCM. Thus, if a 186 vehicle has an ECM and a CCM to send, it SHOULD transmit the ECM 187 earlier than the CCM. 189 5. Security Considerations 191 This document shares all the security issues of the IPv6 ND protocol. 192 This document can get benefits from Secure Neighbor Discovery (SEND) 193 [RFC3971] in order to protect exchanged messages from possible 194 security attacks. 196 6. Acknowledgments 198 This work was supported by Basic Science Research Program through the 199 National Research Foundation of Korea (NRF) funded by the Ministry of 200 Education (2017R1D1A1B03035885). 202 This work was supported in part by Institute of Information & 203 Communications Technology Planning & Evaluation (IITP) grant funded 204 by the Korea MSIT (Ministry of Science and ICT) (R-20160222-002755, 205 Cloud based Security Intelligence Technology Development for the 206 Customized Security Service Provisioning). 208 This work was supported in part by the MSIT under the ITRC 209 (Information Technology Research Center) support program (IITP- 210 2020-2017-0-01633) supervised by the IITP. 212 7. References 214 7.1. Normative References 216 [ID-IPWAVE-PS] 217 Jeong, J., "IPv6 Wireless Access in Vehicular Environments 218 (IPWAVE): Problem Statement and Use Cases", draft-ietf- 219 ipwave-vehicular-networking-19 (work in progress), July 220 2020. 222 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 223 Requirement Levels", BCP 14, RFC 2119, March 1997. 225 [RFC3971] Arkko, J., "SEcure Neighbor Discovery (SEND)", RFC 3971, 226 March 2005. 228 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 229 "Neighbor Discovery for IP Version 6 (IPv6)", RFC 4861, 230 September 2007. 232 [RFC8691] Benamar, N., Haerri, J., Lee, J., and T. Ernst, "Basic 233 Support for IPv6 Networks Operating Outside the Context of 234 a Basic Service Set over IEEE Std 802.11", RFC 8691, 235 December 2019. 237 7.2. Informative References 239 [CASD] Shen, Y., Jeong, J., Oh, T., and S. Son, "CASD: A 240 Framework of Context-Awareness Safety Driving in Vehicular 241 Networks", International Workshop on Device Centric Cloud 242 (DC2), March 2016. 244 [DSRC] ASTM International, "Standard Specification for 245 Telecommunications and Information Exchange Between 246 Roadside and Vehicle Systems - 5 GHz Band Dedicated Short 247 Range Communications (DSRC) Medium Access Control (MAC) 248 and Physical Layer (PHY) Specifications", 249 ASTM E2213-03(2010), October 2010. 251 [ID-Vehicular-ND] 252 Jeong, J., Ed., Shen, Y., and Z. Xiang, "Vehicular 253 Neighbor Discovery for IP-Based Vehicular Networks", 254 draft-jeong-ipwave-vehicular-neighbor-discovery-10 (work 255 in progress), November 2020. 257 [IEEE-802.11-OCB] 258 "Part 11: Wireless LAN Medium Access Control (MAC) and 259 Physical Layer (PHY) Specifications", IEEE Std 260 802.11-2016, December 2016. 262 [WAVE] IEEE 1609 Working Group, "IEEE Guide for Wireless Access 263 in Vehicular Environments (WAVE) - Architecture", IEEE Std 264 1609.0-2013, March 2014. 266 Appendix A. Changes from draft-jeong-ipwave-context-aware-navigator-01 268 The following changes are made from draft-jeong-ipwave-context-aware- 269 navigator-01: 271 o This version updates the title from Context-Aware Navigator 272 Protocol to Context-Aware Navigation Protocol. 274 o This version updates the author list by having Zeung Il Kim as a 275 co-author. 277 o This version updates the version numbers of the referenced drafts. 279 Authors' Addresses 281 Jaehoon Paul Jeong 282 Department of Computer Science and Engineering 283 Sungkyunkwan University 284 2066 Seobu-Ro, Jangan-Gu 285 Suwon, Gyeonggi-Do 16419 286 Republic of Korea 288 Phone: +82 31 299 4957 289 Fax: +82 31 290 7996 290 EMail: pauljeong@skku.edu 291 URI: http://iotlab.skku.edu/people-jaehoon-jeong.php 293 Bien Aime Mugabarigira 294 Department of Electrical and Computer Engineering 295 Sungkyunkwan University 296 2066 Seobu-Ro, Jangan-Gu 297 Suwon, Gyeonggi-Do 16419 298 Republic of Korea 300 Phone: +82 10 5964 8794 301 Fax: +82 31 290 7996 302 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, Gyeonggi-Do 16419 308 Republic of Korea 310 Phone: +82 31 299 4106 311 Fax: +82 31 290 7996 312 EMail: chrisshen@skku.edu 314 Zhong Xiang 315 Department of Electrical and Computer Engineering 316 Sungkyunkwan University 317 2066 Seobu-Ro, Jangan-Gu 318 Suwon, Gyeonggi-Do 16419 319 Republic of Korea 321 Phone: +82 10 9895 1211 322 Fax: +82 31 290 7996 323 EMail: xz618@skku.edu 325 Zeung Il Kim 326 Electric Energy Control Test Team 327 Hyundai Motor 328 150 Hyundaiyeonguso-ro, Namyang-eup 329 Hwaseong, Gyeonggi-Do 18280 330 Republic of Korea 332 Phone: +82-10-8805-3810 333 Fax: +82-31-5172-3134 334 EMail: ben.kim@hyundai.com