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