<?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="info" docName="draft-jeong-opsawg-intent-based-sdv-framework-00">

<front>
    <title abbrev="An Intent-Based SDV Framework">
    An Intent-Based Management Framework for Software-Defined Vehicles in Intelligent Transportation Systems
    </title>

    <author role="editor" 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="Y." surname="Shen" fullname="Yiwen Shen">
        <organization abbrev="Sungkyunkwan University">
        Department of Computer Science and Engineering
        </organization>	

		    <address>
			      <postal>
			          <extaddr>Sungkyunkwan University</extaddr>
  			        <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>
			      <email>chrisshen@skku.edu</email>
			      <uri>https://chrisshen.github.io</uri>
		    </address>
    </author>

    <date month="March" day="4" year="2024" />

    <area>Operations and Management Area</area>
    
    <workgroup>Operations and Management Area 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>
        Software-Defined Vehicle (SDV) is a new player towards 
        autonomous vehicles in Intelligent Transportation Systems (ITS). 
        An SDV is constructed by a software platform like a cloud-native
        system like Kubernetes and  has its internal network. To 
        facilitate the easy and efficient configuration of networks in
        the SDV, an intent-based management is an appropriate direction.
        This document proposes a framework of intent-based management
        for networks, security, and applications in SDVs so that they
        can communicate with other SDVs and infrastructure nodes for
        safe driving and infotainment services in the road networks.
        </t>
    </abstract>
</front>

<middle>

<section anchor="section:Introduction" title="Introduction">
    <t>
    Software-Defined Vehicle (SDV) is a new paradigm in Intelligent Transportation Systems (ITS).
    The SDVs interact with each other and infrastructure (e.g., edge servers) for safe driving and 
    infotainment services through vehicular networks, as shown in <xref target="figure:Vehicular-Networks-for-SDVs" />.
    SDVs can communicates with each other via Vehicle-to-Vehicle (V2V) communications. They can communicate with infrastructure nodes
    (e.g., gNodeB in 5G <xref target="TS-23.501" />) via Vehicle-to-Infrastructure (V2I) communications.
    </t>
    
      <figure anchor="figure:Vehicular-Networks-for-SDVs">
        <name>Vehicular Networks for Software-Defined Vehicles</name>
        <artwork name="" type="" align="left" alt=""><![CDATA[
                              Vehicular Cloud
               *******************************************
             *                                             *
            *              +------------------+             *
           *               | Cloud Controller |              *
           *               +------------------+              *
           *                         ^                       *
            *                        |                      *
             *                       v                     *
               *******************************************
                 ^ +------------+   ^ +------------+   ^ +------------+
                 | |Edge-Server1|   | |Edge-Server2|   | |Edge-Server3|
                 | +------------+   | +------------+   | +------------+
                 |   ^              |   ^              |   ^
                 |   |              |   |              |   |
                 v   V              v   V              v   V
               +---------+         +---------+        +---------+
               | IP-RSU1 |<------->| IP-RSU2 |<------>| IP-RSU3 |
               +---------+         +---------+        +---------+
                    ^                   ^                    ^
                    :                   :                    :
           +-----------------+ +-----------------+   +-----------------+
           |        : V2I    | |        : V2I    |   |       : V2I     |
           |        v        | |        v        |   |       v         |
+--------+ |   +--------+    | |   +--------+    |   |   +--------+    |
|  SDV1  |===> |  SDV2  |===>| |   |  SDV3  |===>|   |   |  SDV4  |===>|
+--------+<...>+--------+<........>+--------+    |   |   +--------+    |
           V2V     ^         V2V        ^        |   |        ^        |
           |       : V2V     | |        : V2V    |   |        : V2V    |
           |       v         | |        v        |   |        v        |
           |  +--------+     | |   +--------+    |   |    +--------+   |
           |  |  SDV5  |===> | |   |  SDV6  |===>|   |    |  SDV7  |==>|
           |  +--------+     | |   +--------+    |   |    +--------+   |
           +-----------------+ +-----------------+   +-----------------+
                 Subnet1              Subnet2              Subnet3
                (Prefix1)            (Prefix2)            (Prefix3)

        <----> Wired Link   <....> Wireless Link   ===> Moving Direction
]]></artwork>
      </figure>

    <t>     
    SDV is regarded as a future platform for autonomous vehicles and electric vehicles. 
    Many automotive-related companies are developing the platform of SDVs, such as  AUTOSAR <xref target="AUTOSAR-SDV" /> and Eclipse SDV <xref target="Eclipse-SDV" />.
    An SDV consists of computing devices, operating systems, and a cloud-native platform (e.g., Kubernetes <xref target="Kubernetes" />).
    Kubernetes is an open-source platform for managing containerized workloads and services with portability and extendibility.
    It can  facilitate intent-based management with both declarative configuration and automation.  
    </t>
  
    <t>
    An SDV needs an intent-based management for networks and security inside its in-vehicle networks. 
    An intent is a declarative command  to request a configuration for a network or security function <xref target="TS-28.312" /><xref target="TR-28.812" />. 
    It emphasizes more on ``What'' is needed (i.e., declarative command) to be accomplished than 
    ``How'' it should be accomplished (i.e., imperative command).
    Since there are a huge number of vehicles produced by each automotive company, the networks and security for the SDV
    needs to be remotely configured and monitored by a control center of each automotive company.
    The in-vehicle networks are based on Gigabit Ethernet and can be configured as multiple subnets including
    Electric Control Units (ECU) and infotainment devices. It requires huge overhead for an operator to configure and monitor
    networks and security for those in-vehicle networks.
    </t>

    <t>
    This document proposes a framework of intent-based management for networks, security, and applications in SDVs that are Service Functions (SFs). Such SFs can be contructed and managed by Software-Defined Networking (SDN) <xref target="RFC7149" />, Network Functions Virtualization (NFV) <xref target="ETSI-NFV" /><xref target="ETSI-NFV-Release-2" />, and Cloud Native Computing Platform (e.g., Kubernetes <xref target="Kubernetes" />).
    This framework automates the configuration and monitoring for the networks and security in each SDV through
    a vehicular cloud and the SDV's mobile network. An SDV User (i.e., administrator) for the management of SDVs
    can configure and monitor the networks and security through an intent. 
    The intent from the SDV User is delivered to a Cloud Controller in charge of a vehicular cloud for SDVs.
    The Cloud Controller translates the intent into the corresponding high-level policy, and delivers 
    the high-level policy to an SDV Controller in charge of an SDV. The SDV translates the high-level policy
    into the corresponding low-level policy and delivered it to an appropriate Network Function (NF)
    for a specific service (e.g., router, firewall, and navigator) in the SDV.
    </t>
</section>

<section anchor="section:Terminology" title="Terminology">
    <t>
      This document uses the terminology described in <xref target="RFC8329" />, 
      <xref target="I-D.ietf-i2nsf-applicability" />,  
      <xref target="I-D.jeong-i2nsf-security-management-automation"/>, <xref target="I-D.jeong-nmrg-ibn-network-management-automation"/>, and <xref target="I-D.yang-i2nsf-security-policy-translation"/>.
      In addition, the following terms are defined below:
    </t>

    <t>
    <list style="symbols">
      <t>
        Intent: A set of operational goals (that a network should meet) and
        outcomes (that a network is supposed to deliver) defined in a
        declarative manner without specifying how to achieve or implement
        them <xref target="RFC9315" />.
      </t>

      <t>
        Intent-Based Management (IBM): It enforces an intent from a user 
        (or administrator) into a target system (e.g., SDV).
        An intent can be expressed as a Natural Language (e.g., English)
        and can be translated into a high-level policy by a Natural Language
        Processing (NLP) <xref target="USENIX-ATC-Lumi" /><xref target="BERT" />
        <xref target="Deep-Learning" />. 
        In this document, the intent can be translated into the corresponding high-level
        policy by an intent translator <xref target="I-D.jeong-i2nsf-security-management-automation"/>.
        The high-level policy can also be translated into the corresponding
        low-level policy by a policy translator <xref target="I-D.yang-i2nsf-security-policy-translation"/>. 
        The low-level policy is dispatched to appropriate Service Functions (SFs).
        Through the monitoring of the SFs, the activity and performace of
        the SFs is monitored and analyzed. If needed, the rules of the 
        high-level or low-level network policy are augmented or new rules 
        are generated and configured to appropriate SFs.
      </t>
    </list>
    </t>

</section>

<section anchor="section:Intent-Based-Management-Framework-for-SDVs" title="Intent-Based Management Framework for Software-Defined Vehicles">

    <t>
    SDVs are managed and monitored by the vehicular cloud. They get help for software updates as well as 
    the configuration of their networks and security from the vehicular cloud.
    <xref target="figure:Vehicular-Networks-for-SDVs" /> shows a vehicular network architecture for SDVs.
    SDVs as vehicles can communicate with each other via V2V and with infrastructure nodes such as 
    IP Road-Side Unit (IP-RSU), for example, gNodeB in 5G networks, respectively.
    Edge servers can help SDVs to perform their safe driving by processing environmental data collected by
    the SDVs and giving maneuver guidance to the SDVs.  
    </t>

        <figure anchor="figure:In-Vehicle-Network-and-Edge-Network">
          <name>In-Vehicle Network and Edge Network</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[
                                                 +-----------------+
                        (*)<........>(*)  +----->| Vehicular Cloud |
     (2001:db8:1:1::/64) |            |   |      +-----------------+
+------------------------------+  +---------------------------------+
|                        v     |  |   v   v                         |
| +---------+        +-------+ |  | +-------+         +---------+   |
| |Navigator|        |IP-OBU1| |  | |IP-RSU1|         |Navigator|   |
| +---------+        +-------+ |  | +-------+         +---------+   |
|     ^                  ^     |  |     ^                  ^        |
|     |                  |     |  |     |                  |        |
|     v                  v     |  |     v                  v        |
| ---------------------------- |  | ------------------------------- |
| 2001:db8:10:1::/64 ^         |  |     ^ 2001:db8:20:1::/64        |
|                    |         |  |     |                           |
|                    v         |  |     v                           |
| +---------+    +-------+     |  | +-------+ +-------+   +-------+ |
| |Firewall |    |Router1|     |  | |Router2| |Server1|...|ServerN| |
| +---------+    +-------+     |  | +-------+ +-------+   +-------+ |
|     ^              ^         |  |     ^         ^           ^     |
|     |              |         |  |     |         |           |     |
|     v              v         |  |     v         v           v     |
| ---------------------------- |  | ------------------------------- |
|      2001:db8:10:2::/64      |  |       2001:db8:20:2::/64        |
+------------------------------+  +---------------------------------+
     SDV1 (Mobile Network1)              EN1 (Fixed Network1)

   <----> Wired Link   <....> Wireless Link   (*) Antenna
]]></artwork>
        </figure>

    <t>
    An SDV has its own internal networks (called in-vehicle networks), as shown in <xref target="figure:In-Vehicle-Network-and-Edge-Network" />. The in-vehicle networks consist of multiple subnets connected with each other through routers.
    IP On-Board Unit (IP-OBU) is a network device in an SDV that has a basic processing ability and can be driven by a low-power CPU (e.g., ARM) with 5G Vehicle-to-Everything (V2X) communication device <xref target="RFC9365" />.
    IP Road-Side Unit (IP-RSU) is a network device situated along the road as an infrastructure node. It has at least two distinct IP-enabled interfaces where one is for 5G V2X and the other is for the wired network connected to the vehicular cloud <xref target="RFC9365" />.
    An Edge Network (EN) is a radio access network which has an IP-RSU for wireless communication with other SDVs having an IP-OBU and wired communication with other network devices (e.g., routers, IP-RSUs, and edge servers) <xref target="RFC9365" />.
    As shown in <xref target="figure:In-Vehicle-Network-and-Edge-Network" />, the IPv6 prefixes should be configured for the in-vehicle network (called mobile network) and Edge Network (called EN). Also, for V2X IP networking, the wireless interfaces of IP-OBU and IP-RSU should be configured with appropriate IPv6 network prefixes and default gateways towards the infrastructure network connected to the vehicular cloud.  
    </t>

    <figure anchor="figure:Intent-Based-SDV-Management-Framework"
     title="Intent-Based Management Framework for Software-Defined Vehicles">
            <artwork><![CDATA[   
                        <Vehicular Cloud (VC)>            
+---------------------------------------------------------------------+
| +------------------+                      +--------------------+    |
| |     SDV User     |          +---------->|    SDV Database    |    |
| +------------------+          |           +--------------------+    |
|          ^                    |                     ^               |
|          | Consumer-Facing    | Management          | Analytics     |
|          | Interface (Intent) | Interface           | Interface     |
|          V                    |                     V               |
| +------------------+<---------+           +--------------------+    |
| |Cloud  Controller |                      |Vendor's Mgmt System|<-+ |
| +------------------+<-------------------->+--------------------+  | |
|          ^           Analytics Interface                          | |
|          |                                                        | |
+----------|--------------------------------------------------------|-+
           | Controller-Facing Interface                  Analytics |
           |     (High-level Policy)                      Interface |
+----------|--------------------------------------------------------|-+
|          |                                                        | |
|          v                                                        | |
| +------------------+     Registration     +--------------------+  | |
| |  SDV Controller  |<-------------------->|Vendor's Mgmt System|  | |
| +------------------+      Interface       +--------------------+  | |
|          ^      ^                                                 | |
|          |      |                                                 | |
|          |      |   Analytics Interface   +--------------------+  | |
|          |      +------------------------>|    SDV Analyzer    |<-+ |
|          |                                +--------------------+    |
|          | Service-Facing Interface          ^       ^       ^      |
|          |   (Low-level Policy)              |       |       |      |
|          |                                   |       |       |      |
|          |    +------------------------------+       |       |      |
|          |    |              +-----------------------+       |      |
|          |    |              |   Monitoring Interface        |      |
|          v    v              v                               v      |
|   +---------------+  +---------------+        +---------------+     |
|   |     SF-1      |--|     SF-2      |........|     SF-n      |     |
|   |   (Router)    |  |  (Firewall)   |        |  (Navigator)  |     |
|   +---------------+  +---------------+        +---------------+     |
+---------------------------------------------------------------------+
                  <Software-Defined Vehicle (SDV)>
            ]]></artwork>
    </figure>

    <t>
    For the automatic network configuration of SDVs, an intent-based management is required between the vehicular cloud and SDVs <xref target="I-D.jeong-nmrg-ibn-network-management-automation"/>. 
    <xref target="figure:Intent-Based-SDV-Management-Framework" /> shows a framework of intent-based management for SDVs. The framework consists of a vehicular cloud and SDVs.
    The vehicular cloud consists of SDV User (as network administrator), Cloud Controller (as an orchestrator for a vehicular cloud), SDV Database (as a main repository for SDV management and monitoring), and Cloud Analyzer (as a monitoring data analyzer for SDVs) such as Network Data Analytics Function (NWDAF) in 5G networks <xref target="TS-23.288" /><xref target="TS-29.520" />.
    The SDV is composed of SDV Controller (as a manager for an SDV), SDV Analyzer (as a monitoring data analyzer for an SDV) <xref target="I-D.jeong-nmrg-ibn-network-management-automation"/>, Vendor's Management System (as a vendor system to provide cloud-native containers) <xref target="RFC8329" /><xref target="I-D.ietf-i2nsf-applicability" />, and Network Functions (NF) such as router, DNS server, and firewall <xref target="I-D.jeong-nmrg-ibn-network-management-automation"/>.
    In this figure, interfaces are defined between a pair of system components in the vehicular cloud and SDV. The intent, high-level policy, and low-level policy can be either XML documents <xref target="RFC6020" /><xref target="RFC7950" /> or YAML documents <xref target="YAML" />. They can be delivered to the destination components via NETCONF <xref target="RFC6241" />, RESTCONF <xref target="RFC8040" />, or REST API <xref target="REST" />.  
    </t>

    <t>
    As shown in <xref target="figure:Intent-Based-SDV-Management-Framework" />,
    the Intent-Based Management SDV Framework enforces an intent from an SDV User,
    which as a user (or administrator), into a target system such as SDV. 
    The intent from the SDV User can be translated into the corresponding high-level
    policy by an intent translator in the Cloud Controller of the Vehicular Cloud <xref target="I-D.jeong-i2nsf-security-management-automation"/>.
    The high-level policy can also be translated into the corresponding
    low-level policy by a policy translator in the SDV Controller of the SDV <xref target="I-D.yang-i2nsf-security-policy-translation"/>. 
    The low-level policy is dispatched from the SDV Controller to appropriate Service Functions (SFs) in the SDV, such as Router, Firewall, and Navigator, as shown in the figure.
    Through the monitoring of the SFs, the activity and performace of
    the SFs in the SDV is monitored and analyzed by the SDV Analyzer in the SDV. 
    If needed, the rules of the high-level or low-level network policy can be augmented
    by the SDV Analyzer. Also, new rules can be automatically generated and configured to
    appropriate SFs by the SDV Analyzer.
    </t>

    <t>
    Therefore, this document proposes a framework of intent-based management for networks in a Software-Defined Vehicle (called SDV). 
    Through this intent-based management, SDVs can communicate with other SDVs and infrastructure nodes (e.g., IP-RSU) via V2X communications
    for safe driving and infotainment services in vehicular networks.
    As future work, we will design and implement YANG data models for the system components and interfaces in the intent-based management framework for SDVs.      
    </t>
</section>

<section anchor="section:IANA-Considerations" title="IANA Considerations">
  <t>
    This document does not require any IANA actions.
  </t>
</section>

<section anchor="section:Security-Considerations" title="Security Considerations">
  <t>
    The same security considerations for the Interface to Network Security Functions (I2NSF)  Framework <xref target="RFC8329" /> are applicable to the intent-based management framework this document.
  </t>

</section>

</middle>

<back>

<!-- START: Normative References -->
<references title="Normative References">

    <?rfc include="reference.RFC.6020"?>
    <?rfc include="reference.RFC.6241"?>
    <?rfc include="reference.RFC.7950"?>
    <?rfc include="reference.RFC.8040"?>    
    <?rfc include="reference.RFC.8329"?>
    <?rfc include="reference.RFC.9315"?>
    <?rfc include="reference.RFC.9365"?>
    
</references>
<!-- END: Normative References -->

<!-- START: Informative References -->
<references title="Informative References">

    <?rfc include='reference.I-D.ietf-i2nsf-applicability'?>
    <?rfc include='reference.I-D.jeong-i2nsf-security-management-automation'?>
    <?rfc include='reference.I-D.jeong-nmrg-ibn-network-management-automation'?>
    <?rfc include='reference.I-D.yang-i2nsf-security-policy-translation'?>

    <reference anchor="YAML">
        <front>
            <title>Yet Another Markup Language (YAML) 1.0</title>
            <author initials="B." surname="Ingerson" />
            <author initials="C." surname="Evans" />
            <author initials="O." surname="Ben-Kiki" />
            <date month="October" year="2023" />
        </front>
        <seriesInfo name="Available:" value="https://yaml.org/spec/history/2001-05-26.html" />
    </reference>

    <reference anchor="TS-23.501">
        <front>
            <title>System Architecture for the 5G System (5GS)</title>
            <author surname="3GPP TS 23.501 V18.3.0" />
            <date month="September" year="2023" />
        </front>
        <seriesInfo name="Available:" value="https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3144" />
    </reference>

    <reference anchor="TS-28.312">
        <front>
            <title>Intent Driven Management Services for Mobile Networks</title>
            <author surname="3GPP TS 28.312 V18.1.1" />
            <date month="September" year="2023" />
        </front>
        <seriesInfo name="Available:" value="https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3554" />
    </reference>

    <reference anchor="TR-28.812">
        <front>
            <title>Study on Scenarios for Intent Driven Management Services for Mobile Networks</title>
            <author surname="3GPP TR 28.812 V17.1.0" />
            <date month="December" year="2020" />
        </front>
        <seriesInfo name="Available:" value="https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3553" />
    </reference>

    <reference anchor="TS-23.288">
        <front>
            <title>Architecture Enhancements for 5G System (5GS) to Support Network Data Analytics Services</title>
            <author surname="3GPP TS 23.288 V18.3.0" />
            <date month="September" year="2023" />
        </front>
        <seriesInfo name="Available:" value="https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3579" />
    </reference>

    <reference anchor="TS-29.520">
        <front>
            <title>Network Data Analytics Services</title>
            <author surname="3GPP TS 29.520 V18.3.0" />
            <date month="September" year="2023" />
        </front>
        <seriesInfo name="Available:" value="https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3355" />
    </reference>

    <reference anchor="RFC7149">
        <front>
            <title>Software-Defined Networking: A Perspective from within a Service Provider Environment</title>
            <author initials="M." surname="Boucadair" />
            <author initials="C." surname="Jacquenet" />
            <date month="March" year="2014" />
        </front>
        <seriesInfo name="RFC" value="7149" />
    </reference>

    <reference anchor="ETSI-NFV">
        <front>
            <title>Network Functions Virtualisation (NFV); Architectural Framework</title>
            <author surname="ETSI GS NFV 002 V1.2.1" />
            <date month="December" year="2014" />
        </front>
        <seriesInfo name="Available:" value="https://www.etsi.org/deliver/etsi_gs/nfv/001_099/002/01.02.01_60/gs_nfv002v010201p.pdf" />
    </reference>

    <reference anchor="ETSI-NFV-Release-2">
        <front>
            <title>Network Functions Virtualisation (NFV) Release 2; 
            Management and Orchestration; Architectural Framework Specification</title>
            <author surname="ETSI GS NFV 006 V2.1.1" />
            <date month="January" year="2021" />
        </front>
        <seriesInfo name="Available:" value="https://www.etsi.org/deliver/etsi_gs/nfv/001_099/006/02.01.01_60/gs_nfv006v020101p.pdf" />
    </reference>

    <reference anchor="REST">
        <front>
            <title>Principled Design of the Modern Web Architecture</title>
            <author initials="R." surname="Fielding" />
            <author initials="R." surname="Taylor" />
            <date month="May" year="2002" />
        </front>
        <seriesInfo name="ACM" value="Transactions on Internet Technology, Vol. 2, Issue 2," />
    <seriesInfo name="Available:" value="https://dl.acm.org/doi/10.1145/514183.514185" />
    </reference>

    <reference anchor="USENIX-ATC-Lumi">
        <front>
            <title>Hey, Lumi! Using Natural Language for Intent-Based Network Management</title>
            <author initials="A." surname="Jacobs" />
            <author initials="R." surname="Pfitscher" />
            <author initials="R." surname="Ribeiro" />
            <author initials="R." surname="Ferreira" />
            <author initials="L." surname="Granville" />
            <author initials="W." surname="Willinger" />
            <author initials="S." surname="Rao" />
            <date month="July" year="2021" />
        </front>
        <seriesInfo name="USENIX" value="Annual Technical Conference" />
    <seriesInfo name="Available:" value="https://www.usenix.org/conference/atc21/presentation/jacobs" />
    </reference>

    <reference anchor="BERT">
        <front>
            <title>BERT: Pre-training of Deep Bidirectional Transformers for Language Understanding</title>
            <author initials="J." surname="Devlin" />
            <author initials="M." surname="Chang" />
            <author initials="K." surname="Lee" />
            <author initials="K." surname="Toutanova" />
            <date month="June" year="2019" />
        </front>
        <seriesInfo name="NAACL-HLT" value="Conference" />
    <seriesInfo name="Available:" value="https://aclanthology.org/N19-1423.pdf" />
    </reference>


    <reference anchor="Deep-Learning">
        <front>
            <title>Deep Learning</title>
            <author initials="I." surname="Goodfellow" />
            <author initials="Y." surname="Bengio" />
            <author initials="A." surname="Courville" />
            <date month="November" year="2016" />
        </front>
        <seriesInfo name="Publisher:" value="The MIT Press" />
    <seriesInfo name="Available:" value="https://www.deeplearningbook.org/" />
    </reference>

    <reference anchor="AUTOSAR-SDV">
        <front>
            <title>AUTOSAR Adaptive Platform</title>
            <author surname="AUTOSAR" />
            <date month="March" year="2024" />
        </front>
        <seriesInfo name="Available:" value="https://www.autosar.org/standards/adaptive-platform" />    
    </reference>

    <reference anchor="Eclipse-SDV">
        <front>
            <title>Eclipse Software Defined Vehicle Working Group Charter</title>
            <author surname="Eclipse" />
            <date month="March" year="2024" />
        </front>
        <seriesInfo name="Available:" value="https://www.eclipse.org/org/workinggroups/sdv-charter.php" />    
    </reference>
    
    <reference anchor="Kubernetes">
        <front>
            <title>Kubernetes: Cloud Native Computing Platform</title>
            <author surname="Kubernetes" />
            <date month="March" year="2024" />
        </front>
        <seriesInfo name="Available:" value="https://kubernetes.io/" />    
    </reference>

</references>
<!-- END: Informative References -->

<section title="Acknowledgments">
    <t indent="0" pn="section-appendix.a-1">
    This work was supported in part by Institute of Information &amp; Communications
    Technology Planning &amp; Evaluation (IITP) grant funded by the Korea
    Ministry of Science and ICT (MSIT)(No. 2022-0-01015, Development of
    Candidate Element Technology for Intelligent 6G Mobile Core Network).
    </t>

    <t indent="0" pn="section-appendix.a-2">    
    This work was supported in part by Institute of Information &amp;
    Communications Technology Planning &amp; Evaluation (IITP) grant
    funded by the Korea Ministry of Science and ICT (MSIT) (No. 2022-0-01199,
    Regional strategic industry convergence security core talent training
    business).
    </t>
</section>

<section anchor="section:Contributors" title="Contributors">
    <t indent="0" pn="section-appendix.b-1">
    This document is made by the group effort of OPWAWG, greatly benefiting 
    from inputs and texts by <contact fullname="Linda Dunbar"/> (Futurewei)
    <contact fullname="Yong-Geun Hong"/> (Daejeon University), and
    <contact fullname="Joo-Sang Youn"/> (Dong-Eui University).
    The authors sincerely appreciate their contributions.
    </t>

    <t indent="0" pn="section-appendix.b-2">  
    The following are coauthors of this document:
    </t>   

      <contact fullname="Yoseop Ahn">
        <organization showOnFrontPage="true">Department of Computer Science &amp; Engineering</organization>
        <address>
          <postal>
            <extaddr>Sungkyunkwan University</extaddr>
            <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>
          <email>ahnjs124@skku.edu</email>
          <uri>http://iotlab.skku.edu/people-Ahn-Yoseop.php</uri>
        </address>
      </contact>
      <contact fullname="Mose Gu">
        <organization showOnFrontPage="true">Department of Computer Science &amp; Engineering</organization>
        <address>
          <postal>
            <extaddr>Sungkyunkwan University</extaddr>
            <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>
          <email>rna0415@skku.edu</email>
          <uri>http://iotlab.skku.edu/people-Moses-Gu.php</uri>
        </address>
      </contact>
</section>

</back>

<!-- <vspace blankLines="100"/> -->
<!-- page break to put addresses onto one page-->

</rfc>
