idnits 2.17.1 draft-jeong-ipwave-context-aware-navigator-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 date (November 4, 2019) is 1632 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 216, but no explicit reference was found in the text == Unused Reference: 'IEEE-802.11-OCB' is defined on line 240, but no explicit reference was found in the text == Outdated reference: A later version (-30) exists of draft-ietf-ipwave-vehicular-networking-12 ** 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-08 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: May 7, 2020 Y. Shen 6 Sungkyunkwan University 7 November 4, 2019 9 Context-Aware Navigator Protocol for IP-Based Vehicular Networks 10 draft-jeong-ipwave-context-aware-navigator-00 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 May 7, 2020. 40 Copyright Notice 42 Copyright (c) 2019 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. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 63 6.1. Normative References . . . . . . . . . . . . . . . . . . 5 64 6.2. Informative References . . . . . . . . . . . . . . . . . 5 65 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 7 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 68 1. Introduction 70 The enhancement of driving safety is one of objectives in cooperative 71 driving in vehicular networks. Dedicated Short-Range Communications 72 (DSRC) is for vehicular communications [DSRC]. IEEE has standardized 73 a family standard suite of Wireless Access in Vehicular Environments 74 (WAVE) [WAVE]. Also, IETF has standardized an IPv6 packet delivery 75 protocol over IEEE 802.11-OCB (Outside the Context of a Basic Service 76 Set) [ID-IPv6-802.11-OCB], which is a MAC protocol for vehicles in 77 WAVE. 79 A vehicle equipped with various sensors and the a DSRC device can 80 sense its surrounding environment including its neighboring vehicles, 81 and share the sensed data and its mobility information (e.g., 82 position, speed, acceleration/deceleration, and direction) with its 83 neighboring vehicles. This information sharing allows vehicles to 84 assess the collision risk and make their maneuver change to avoid an 85 accident in a prompt way. That is, the capability of sensing, 86 computing, and communication of vehicles enables them to understand 87 the driving environment and situation (i.e., context), and cooperate 88 with each other during their navigation. 90 The driving information sharing enables Context-Aware Navigator (CAN) 91 where each vehicle can display its neighboring vehicles, pedestrians, 92 and obstacles in its navigation system [CASD]. With this CAN, a 93 driver can make a better decision on driving to avoid an accident, 94 and an autonomous vehicle can control its maneuver to escape from a 95 possible fatality in advance. 97 For this CAN service, this document proposes a light-weight data 98 sharing protocol using a new IPv6 Neighbor Discovery (ND) option for 99 Vehicle Mobility Information, which is called Vehicle Mobility 100 Information (VMI) option. This VMI option can be included by a 101 Neighbor Advertisement (NA) message in Vehicular Neighbor Discovery 102 (VND) [ID-Vehicular-ND]. 104 There are two messages for the CAN service with the VMI option such 105 as Cooperation Context Message (CCM) and Emergency Context Message 106 (ECM). The CCM is a message to deliver a vehicle's motion 107 information (e.g., position, speed, acceleration/deceleration, 108 direction) and a driver's driving action (e.g., braking and 109 accelerating) to its neighboring vehicles for cooperative driving. 110 The ECM is a message to notify a vehicle's neighboring vehicles of an 111 emergency situation (e.g., an accident and dangerous situation). The 112 ECM has a higher priority than the CCM such that the ECM needs to be 113 disseminated faster than the CCM in vehicular networks. 115 2. Requirements Language 117 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 118 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 119 document are to be interpreted as described in RFC 2119 [RFC2119]. 121 3. Terminology 123 This document uses the terminology described in [ID-IPWAVE-PS]. 125 4. Vehicle Mobility Information Option 127 Vehicle Mobility Information (VMI) option is an IPv6 ND option to 128 convey either a CCM or ECM. Figure 1 shows the format of the VMI 129 option. 131 0 1 2 3 132 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 133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 134 | Type | Length | Message | Reserved1 | 135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 136 | Reserved2 | 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 | | 139 : Mobility Information : 140 | | 141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 143 Figure 1: Vehicle Mobility Information (VMI) Option Format 145 Fields: 146 Type 8-bit identifier of the VMI option type as assigned 147 by the IANA: TBD 149 Length 8-bit unsigned integer. The length of the option 150 (including the Type and Length fields) is in units of 151 8 octets. The value is 3. 153 Message 8-bit identifier of the VMI message type as CCM (0) 154 and ECM (1). 156 Reserved1 This field is unused. It MUST be initialized to 157 zero by the sender and MUST be ignored by the 158 receiver. 160 Reserved2 This field is unused. It MUST be initialized to 161 zero by the sender and MUST be ignored by the 162 receiver. 164 Mobility Information 165 128-bit mobility information. It contains a vehicle's 166 motion information (e.g., position, speed, 167 acceleration/deceleration, direction) and a driver's 168 driving action (e.g., braking and accelerating) for 169 CCM. Also, it contains a vehicle's emergency 170 information (e.g., obstacle information and accident 171 information). 173 A CCM in a VMI option can be included in an NA message that a vehicle 174 transmits periodically to announce its existence and routing 175 information to its one-hop neighboring vehicles [ID-Vehicular-ND]. 177 An ECM in a VMI option can be included in an NA message that a 178 vehicle transmits to immediately announce an emergency situation to 179 its one-hop neighboring vehicles [ID-Vehicular-ND]. 181 To let the vehicles take an immediate action on an emergency 182 situation, the ECM has a higher priority than the CCM. Thus, if a 183 vehicle has an ECM and a CCM to send, it SHOULD transmit the ECM 184 earlier than the CCM. 186 5. Security Considerations 188 This document shares all the security issues of the IPv6 ND protocol. 189 This document can get benefits from Secure Neighbor Discovery (SEND) 190 [RFC3971] in order to protect exchanged messages from possible 191 security attacks. 193 6. References 195 6.1. Normative References 197 [ID-IPv6-802.11-OCB] 198 Benamar, N., Haerri, J., Lee, J., and T. Ernst, "Basic 199 Support for IPv6 over IEEE Std 802.11 Networks Operating 200 Outside the Context of a Basic Service Set (IPv6-over- 201 80211-OCB)", draft-ietf-ipwave-ipv6-over-80211ocb-52 (work 202 in progress), August 2019. 204 [ID-IPWAVE-PS] 205 Jeong, J., "IP Wireless Access in Vehicular Environments 206 (IPWAVE): Problem Statement and Use Cases", draft-ietf- 207 ipwave-vehicular-networking-12 (work in progress), October 208 2019. 210 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 211 Requirement Levels", BCP 14, RFC 2119, March 1997. 213 [RFC3971] Arkko, J., "SEcure Neighbor Discovery (SEND)", RFC 3971, 214 March 2005. 216 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 217 "Neighbor Discovery for IP Version 6 (IPv6)", RFC 4861, 218 September 2007. 220 6.2. Informative References 222 [CASD] Shen, Y., Jeong, J., Oh, T., and S. Son, "CASD: A 223 Framework of Context-Awareness Safety Driving in Vehicular 224 Networks", International Workshop on Device Centric Cloud 225 (DC2), March 2016. 227 [DSRC] ASTM International, "Standard Specification for 228 Telecommunications and Information Exchange Between 229 Roadside and Vehicle Systems - 5 GHz Band Dedicated Short 230 Range Communications (DSRC) Medium Access Control (MAC) 231 and Physical Layer (PHY) Specifications", 232 ASTM E2213-03(2010), October 2010. 234 [ID-Vehicular-ND] 235 Jeong, J., Ed., Shen, Y., and Z. Xiang, "Vehicular 236 Neighbor Discovery for IP-Based Vehicular Networks", 237 draft-jeong-ipwave-vehicular-neighbor-discovery-08 (work 238 in progress), November 2019. 240 [IEEE-802.11-OCB] 241 "Part 11: Wireless LAN Medium Access Control (MAC) and 242 Physical Layer (PHY) Specifications", IEEE Std 243 802.11-2016, December 2016. 245 [WAVE] IEEE 1609 Working Group, "IEEE Guide for Wireless Access 246 in Vehicular Environments (WAVE) - Architecture", IEEE Std 247 1609.0-2013, March 2014. 249 Appendix A. Acknowledgments 251 This work was supported by Basic Science Research Program through the 252 National Research Foundation of Korea (NRF) funded by the Ministry of 253 Education (2017R1D1A1B03035885). 255 This work was supported in part by Institute of Information & 256 Communications Technology Planning & Evaluation (IITP) grant funded 257 by the Korea MSIT (Ministry of Science and ICT) (R-20160222-002755, 258 Cloud based Security Intelligence Technology Development for the 259 Customized Security Service Provisioning). 261 This work was supported in part by the MSIT under the ITRC 262 (Information Technology Research Center) support program (IITP- 263 2019-2017-0-01633) supervised by the IITP. 265 Authors' Addresses 267 Jaehoon Paul Jeong 268 Department of Computer Science and Engineering 269 Sungkyunkwan University 270 2066 Seobu-Ro, Jangan-Gu 271 Suwon, Gyeonggi-Do 16419 272 Republic of Korea 274 Phone: +82 31 299 4957 275 Fax: +82 31 290 7996 276 EMail: pauljeong@skku.edu 277 URI: http://iotlab.skku.edu/people-jaehoon-jeong.php 279 Bien Aime Mugabarigira 280 Department of Electrical and Computer Engineering 281 Sungkyunkwan University 282 2066 Seobu-Ro, Jangan-Gu 283 Suwon, Gyeonggi-Do 16419 284 Republic of Korea 286 Phone: +82 10 5964 8794 287 Fax: +82 31 290 7996 288 EMail: bienaime@skku.edu 289 Zhong Xiang 290 Department of Electrical and Computer Engineering 291 Sungkyunkwan University 292 2066 Seobu-Ro, Jangan-Gu 293 Suwon, Gyeonggi-Do 16419 294 Republic of Korea 296 Phone: +82 10 9895 1211 297 Fax: +82 31 290 7996 298 EMail: xz618@skku.edu 300 Yiwen Chris Shen 301 Department of Electrical and Computer Engineering 302 Sungkyunkwan University 303 2066 Seobu-Ro, Jangan-Gu 304 Suwon, Gyeonggi-Do 16419 305 Republic of Korea 307 Phone: +82 31 299 4106 308 Fax: +82 31 290 7996 309 EMail: chrisshen@skku.edu