<?xml version="1.0" encoding="US-ASCII"?>
<!-- <?xml version="1.0" encoding="UTF-8"?> -->
<!-- edited with XMLSPY v5 rel. 3 U (http://www.xmlspy.com)
     by Daniel M Kohn (private)
-->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">

<?rfc toc="yes"?>
<?rfc rfcedstyle="yes"?>
<?rfc subcompact="no"?>
<?rfc symrefs="yes"?>

<rfc ipr="trust200902" category="std" docName="draft-jeong-ipwave-context-aware-navigator-02">

<front>
    <title abbrev="Context-Aware Navigation Protocol">
    Context-Aware Navigation Protocol for IP-Based Vehicular Networks 
    </title>

	<author initials="J." surname="Jeong" fullname="Jaehoon Paul Jeong">
        <organization abbrev="Sungkyunkwan University">
           Department of Computer Science and Engineering
        </organization>

        <address>
            <postal>
                <street>Sungkyunkwan University</street>
                <street>2066 Seobu-Ro, Jangan-Gu</street>
                <city>Suwon</city> <region>Gyeonggi-Do</region>
                <code>16419</code>
                <country>Republic of Korea</country>
            </postal>
            <phone>+82 31 299 4957</phone>
            <facsimile>+82 31 290 7996</facsimile>
            <email>pauljeong@skku.edu</email>
            <uri>http://iotlab.skku.edu/people-jaehoon-jeong.php</uri>
        </address>
	</author>

 	<author initials="B." surname="Mugabarigira" fullname="Bien Aime Mugabarigira">
        <organization abbrev="Sungkyunkwan University">
           Department of Electrical and Computer Engineering
        </organization>

        <address>
            <postal>
                <street>Sungkyunkwan University</street>
                <street>2066 Seobu-Ro, Jangan-Gu</street>
                <city>Suwon</city> <region>Gyeonggi-Do</region>
                <code>16419</code>
                <country>Republic of Korea</country>
            </postal>
            <phone>+82 10 5964 8794</phone>
            <facsimile>+82 31 290 7996</facsimile>
            <email>bienaime@skku.edu</email>
        </address>
	</author>
	
    <author initials="Y." surname="Shen" fullname="Yiwen Chris Shen">
        <organization abbrev="Sungkyunkwan University">
           Department of Electrical and Computer Engineering
        </organization>

        <address>
            <postal>
                <street>Sungkyunkwan University</street>
                <street>2066 Seobu-Ro, Jangan-Gu</street>
                <city>Suwon</city> <region>Gyeonggi-Do</region>
                <code>16419</code>
                <country>Republic of Korea</country>
            </postal>
            <phone>+82 31 299 4106</phone>
            <facsimile>+82 31 290 7996</facsimile>
            <email>chrisshen@skku.edu</email>
        </address>
    </author>

    <author initials="Z." surname="Xiang" fullname="Zhong Xiang">
        <organization abbrev="Sungkyunkwan University">
           Department of Electrical and Computer Engineering
        </organization>

        <address>
            <postal>
                <street>Sungkyunkwan University</street>
                <street>2066 Seobu-Ro, Jangan-Gu</street>
                <city>Suwon</city> <region>Gyeonggi-Do</region>
                <code>16419</code>
                <country>Republic of Korea</country>
            </postal>
            <phone>+82 10 9895 1211</phone>
            <facsimile>+82 31 290 7996</facsimile>
            <email>xz618@skku.edu</email>
        </address>
    </author>

    <author initials="Z." surname="Zeung" fullname="Zeung Il Kim">
        <organization abbrev="Hyundai Motor">
           Electric Energy Control Test Team
        </organization>

        <address>
            <postal>
                <street>Hyundai Motor</street>
                <street>150 Hyundaiyeonguso-ro, Namyang-eup</street>
                <city>Hwaseong</city> <region>Gyeonggi-Do</region>
                <code>18280</code>
                <country>Republic of Korea</country>
            </postal>
            <phone>+82-10-8805-3810</phone>
            <facsimile>+82-31-5172-3134</facsimile>
            <email>ben.kim@hyundai.com</email>
        </address>
    </author>

    <date month="November" day="2" year="2020" />

    <area>Internet</area>

    <workgroup>IPWAVE Working Group</workgroup>


<!-- [rfced] Please insert any keywords (beyond those that appear in
the title) for use on http://www.rfc-editor.org/rfcsearch.html. -->

<keyword>Internet-Draft</keyword>       

    <abstract>
    <t>
    This document proposes a Context-Aware Navigation Protocol (CNP) for IP-based 
    vehicular networks for cooperative navigation among vehicles in road networks.
    This CNP aims at the enhancement of driving safety through a light-weight driving 
    information sharing method. The CNP protocol uses an IPv6 Neighbor Discovery (ND) 
    option to convey driving information such as a vehicle's position, speed, 
    acceleration/deceleration, and direction, and a driver's driving action (e.g., braking and 
    accelerating). 
    </t>
    </abstract>
</front>

<middle>

<section anchor="section:Introduction" title="Introduction"> 
    <t>
    The enhancement of driving safety is one of objectives of cooperative driving  in vehicular networks. 
	Dedicated Short-Range Communications (DSRC) is for vehicular communications <xref target="DSRC" />. 
	IEEE has standardized a family standard suite of Wireless Access in Vehicular Environments (WAVE)
	<xref target="WAVE" />. Also, IETF has standardized an IPv6 packet delivery protocol over 
	IEEE 802.11-OCB (Outside the Context of a Basic Service Set) <xref target="RFC8691" />, 
	which is a MAC protocol for vehicles in WAVE.
	</t>
	
	<t>
    A vehicle equipped with various sensors and the a DSRC device can sense its surrounding environment 
	including its neighboring vehicles, and share the sensed data and its mobility information (e.g., 
	position, speed, acceleration/deceleration, and direction) with its neighboring vehicles. This 
	information sharing allows vehicles to assess the collision risk and make their maneuvers to 
	avoid an accident in a prompt way. 
    That is, the capability of sensing, computing, and communication of vehicles enables them to understand 
    the driving environment and situation (i.e., context), and cooperate with each other during their navigation.
     </t>
	
    <t>
    The driving information sharing enables context-aware navigation where each vehicle can display
    its neighboring vehicles, pedestrians, and obstacles in its navigation system <xref target="CASD" />. 
	With this CNP, a driver can make a better decision on driving to avoid an accident, and an autonomous 
	vehicle can control its maneuver to escape from a possible fatality in advance.
    </t>

    <t>
    For this CNP service, this document proposes a light-weight data sharing protocol using a new IPv6 Neighbor
    Discovery (ND) option for Vehicle Mobility Information, which is called Vehicle Mobility Information (VMI) option.
    This VMI option can be included by a Neighbor Advertisement (NA) message in Vehicular Neighbor Discovery (VND)
	<xref target="ID-Vehicular-ND" />.
    </t>

    <t>	
    There are two messages for the CNP service with the VMI option such as Cooperation Context Message 
    (CCM) and Emergency Context Message (ECM). The CCM is a message to deliver a vehicle's motion information 
	(e.g., position, speed, acceleration/deceleration, direction) and a driver's driving action (e.g., braking and 
	accelerating) to its neighboring vehicles for cooperative driving. The ECM is a message to notify a vehicle's 
	neighboring vehicles of an emergency situation (e.g., an accident and dangerous situation). The ECM has a higher 
	priority than the CCM such that the ECM needs to be disseminated faster than the CCM in vehicular networks.
    </t>

</section> 

<section anchor="section:Requirements-Language" title="Requirements Language">
    <t>
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", 
	"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be 
	interpreted as described in RFC 2119 <xref target="RFC2119" />.
    </t>
</section>

<section anchor="Terminology" title="Terminology">
    <t>
	This document uses the terminology described in <xref target="ID-IPWAVE-PS" />.
    </t>
</section>

<section anchor="subsection:Vehicle-Mobility-Information-Option" 
         title="Vehicle Mobility Information Option">
  <t>
  Vehicle Mobility Information (VMI) option is an IPv6 ND option to convey 
  either a CCM or ECM.  
  <xref target="fig:vehicle-mobility-information-option-format" /> shows 
  the format of the VMI option.
  </t>

        <figure anchor="fig:vehicle-mobility-information-option-format" 
		        title="Vehicle Mobility Information (VMI) Option Format">
            <artwork><![CDATA[
   0                   1                   2                   3  
   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  
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |     Type      |    Length     |    Message    |  Reserved1    |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                           Reserved2                           |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                                                               |
  :                      Mobility Information                     :
  |                                                               |   
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
            ]]></artwork>
        </figure>

    <!-- <t>Fields:</t> -->
    <figure>
            <artwork><![CDATA[
Fields:
 Type           8-bit identifier of the VMI option type as assigned
                by the IANA: TBD

 Length         8-bit unsigned integer.  The length of the option
                (including the Type and Length fields) is in units of
                8 octets.  The value is 3.
				
 Message        8-bit identifier of the VMI message type as CCM (0) 
                and ECM (1). 
 
 Reserved1      This field is unused.  It MUST be initialized to
                zero by the sender and MUST be ignored by the
                receiver.

 Reserved2      This field is unused.  It MUST be initialized to
                zero by the sender and MUST be ignored by the
                receiver.

 Mobility Information
                128-bit mobility information.  It contains a vehicle's
                motion information (e.g., position, speed, 
                acceleration/deceleration, direction) and a driver's 
                driving action (e.g., braking and accelerating) for 
                CCM.  Also, it contains a vehicle's emergency 
                information (e.g., obstacle information and accident
                information).                  					
            ]]></artwork>
     </figure>

    <t>
    A CCM in a VMI option can be included in an NA message that a vehicle transmits 
	periodically to announce its existence and routing information to its one-hop 
	neighboring vehicles <xref target="ID-Vehicular-ND" />.
    </t>	
	
	<t>
	An ECM in a VMI option can be included in an NA message that a vehicle transmits 
	to immediately announce an emergency situation	to its one-hop neighboring 
	vehicles <xref target="ID-Vehicular-ND" />.
	</t>
  
    <t>
	To let the vehicles take an immediate action on an emergency situation, the ECM has a 
	higher priority than the CCM. Thus, if a vehicle has an ECM and a CCM to send, it 
	SHOULD transmit the ECM earlier than the CCM.
	</t>
</section>


<section anchor="section:Security-Considerations" title="Security Considerations">
	<t>
	This document shares all the security issues of the IPv6 ND protocol. 
	This document can get benefits from Secure Neighbor Discovery (SEND) 
	<xref target="RFC3971" /> in order to protect exchanged messages from 
	possible security attacks.
	</t>
</section>

	
<section title="Acknowledgments">
    <t>
    This work was supported by Basic Science Research Program through the 
    National Research Foundation of Korea (NRF) funded by the Ministry of 
    Education (2017R1D1A1B03035885).
    </t>

	<t>
    This work was supported in part by Institute of Information &amp; Communications 
	Technology Planning &amp; Evaluation (IITP) grant funded by the Korea MSIT 
	(Ministry of Science and ICT) (R-20160222-002755, Cloud based Security 
	Intelligence Technology Development for the Customized Security Service 
	Provisioning).
    </t>

    <t>
	This work was supported in part by the MSIT under the ITRC (Information Technology 
	Research Center) support program (IITP-2020-2017-0-01633) supervised by the IITP.
    </t>	
</section>


</middle>

<back>

 
<references title="Normative References">

    <reference anchor="RFC2119">
        <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author initials="S." surname="Bradner" />
            <date month="March" year="1997" />
        </front>
        <seriesInfo name="BCP" value="14" />
        <seriesInfo name="RFC" value="2119" />
    </reference>   

    <reference anchor="RFC4861">
        <front>
            <title>Neighbor Discovery for IP Version 6 (IPv6)</title>
            <author initials="T." surname="Narten" />
            <author initials="E." surname="Nordmark" />
            <author initials="W." surname="Simpson" />
			<author initials="H." surname="Soliman" />
            <date month="September" year="2007" />
        </front>
        <seriesInfo name="RFC" value="4861" />
    </reference>  

	<reference anchor="RFC3971">
        <front>
            <title>SEcure Neighbor Discovery (SEND)</title>
            <author  initials="J." surname="Arkko" />
            <date month="March" year="2005" />
        </front>
        <seriesInfo name="RFC" value="3971" />
    </reference>  

    <reference anchor="RFC8691">
        <front>
            <title>Basic Support for IPv6 Networks Operating Outside the Context of a Basic Service Set over IEEE Std 802.11						
			</title>
            <author initials="N." surname="Benamar" />
            <author initials="J." surname="Haerri" />
            <author initials="J." surname="Lee" />
            <author initials="T." surname="Ernst" />
            <date month="December" year="2019" />
        </front>
        <seriesInfo name="RFC" value="8691" />
    </reference> 

    <reference anchor="ID-IPWAVE-PS">
        <front>
            <title>IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem Statement and Use Cases</title>
            <author initials="J." surname="Jeong" />
            <date month="July" year="2020" />
        </front>
		<seriesInfo name="Internet-Draft" value="draft-ietf-ipwave-vehicular-networking-19" />
    </reference>  

</references>
    
<references title="Informative References">

    <reference anchor="ID-Vehicular-ND">
        <front>
            <title>Vehicular Neighbor Discovery for IP-Based Vehicular Networks</title>
			<author role='editor' initials="J." surname="Jeong" />
            <author initials="Y." surname="Shen" />
            <author initials="Z." surname="Xiang" />	
            <date month="November" year="2020" />
        </front>
        <seriesInfo name="Internet-Draft" value="draft-jeong-ipwave-vehicular-neighbor-discovery-10" />
    </reference>  

    <reference anchor="DSRC">
        <front>
            <title>Standard Specification for Telecommunications and Information Exchange Between Roadside and Vehicle Systems - 5 GHz Band Dedicated Short Range Communications (DSRC) Medium Access Control (MAC) and Physical Layer (PHY) Specifications</title>
            <author>
                <organization>
                ASTM International
                </organization>
            </author>
            <date month="October" year="2010" />
        </front>
        <seriesInfo name="ASTM" value="E2213-03(2010)" />
    </reference> 

    <reference anchor="WAVE">
        <front>
            <title>IEEE Guide for Wireless Access in Vehicular Environments (WAVE) - Architecture</title>
            <author initials="" surname="IEEE 1609 Working Group" />
            <date month="March" year="2014" />
        </front>
        <seriesInfo name="IEEE" value="Std 1609.0-2013" />
    </reference>

    <reference anchor="IEEE-802.11-OCB">
        <front>
            <title>Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications</title>
    		<author surname="IEEE 802.11 Working Group" />
            <date month="December" year="2016" />
        </front>
    	<seriesInfo name="IEEE" value="Std 802.11-2016" />
    </reference>

    <reference anchor="CASD">
        <front>
            <title>CASD: A Framework of Context-Awareness Safety Driving in Vehicular Networks</title>
            <author initials="Y." surname="Shen" />
            <author initials="J." surname="Jeong" />
            <author initials="T." surname="Oh" />
            <author initials="S." surname="Son" />
            <date month="March" year="2016" />
        </front>
        <seriesInfo name="International Workshop" value="on Device Centric Cloud (DC2)" />
    </reference>
	
</references>
			

<!-- START: Changes from the previous version -->
<section title="Changes from draft-jeong-ipwave-context-aware-navigator-01">   
<t>
The following changes are made from draft-jeong-ipwave-context-aware-navigator-01:
<list style="symbols">
  <t>
  This version updates the title from Context-Aware Navigator
  Protocol to Context-Aware Navigation Protocol.
  </t>
  <t>
  This version updates the author list by having Zeung Il Kim as a co-author.
  </t>
  <t>
  This version updates the version numbers of the referenced drafts.
  </t>  
</list>
</t>
</section> 
<!-- END: Changes from the previous version -->


</back>

<!-- <vspace blankLines="100"/> -->
<!-- page break to put addresses onto one page-->

</rfc>
