<?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-ahn-nmrg-5g-security-i2nsf-framework-01">

<front>
    <title abbrev="An 5G Integrated Security Service System">
    An Integrated Security Service System for 5G Networks using an I2NSF Framework
    </title>

    <author role="editor" initials="Y." surname="Ahn" fullname="Yoseop Ahn">
        <organization abbrev="Sungkyunkwan University">
        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>
    </author>

    <author role="editor" initials="J." surname="Jeong" fullname="Jaehoon Paul Jeong">
        <organization abbrev="Sungkyunkwan University">
        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 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="Kim" fullname="Younghan Kim">
        <organization abbrev="Soongsil University">
        School of Electronic Engineering
        </organization>
		<address>
            <postal>
                <extaddr>Soongsil University</extaddr>
                <street>369, Sangdo-ro, Dongjak-gu</street>
                <city>Seoul</city>
                <code>06978</code>
                <country>Republic of Korea</country>
            </postal>
            <phone></phone>
            <email>younghak@ssu.ac.kr</email>
		</address>
    </author>
    
    <date month="February" day="25" year="2026" />

    <area>Network Management</area>
    
    <workgroup>Internet Research Task Force</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 presents an integrated framework for automated security management in 5G edge networks using
        the Interface to Network Security Functions (I2NSF) architecture. The proposed system leverages Intent-Based
        Networking (IBN) to allow users or administrators to declare high-level security intents, which are translated
        into enforceable network and application policies. Network-level policies are delivered to 5G core components via the
        Network Exposure Function (NEF), while application-level policies are enforced directly on a User Equipment (UE)
        through distributed IBN Controllers. This architecture supports adaptive, context-aware, and distributed policy enforcement,
        enabling real-time response to dynamic edge conditions and user mobility scenarios such as handovers. By integrating
        closed-loop monitoring and analytics, the system ensures consistent and autonomous security across heterogeneous 5G environments.
        </t>
    </abstract>
</front>


<middle>

<section anchor="section:Introduction" title="Introduction">
    <t>
    Network softwarization has become a fundamental approach for delivering network services across various infrastructures, 
    including 5G mobile networks <xref target="TS-23.501" />, cloud computing platforms, and edge computing environments. 
    This paradigm is enabled through key technologies such as Network Functions Virtualization (NFV) 
    <xref target="ETSI-NFV" /> and Software-Defined Networking (SDN) <xref target="RFC7149" />.
    In addition, Intent-Based Networking (IBN) <xref target="RFC9315" /> <xref target="Survey-IBN-CST-2023" /> serves as
    a foundation for implementing intelligent behaviors in both network-level and application-level services. 
    As networks continue to evolve in this software-driven direction, the emergence of 5G introduces new challenges, 
    particularly in the realm of security.
    </t>

    <t>
    As mobile networks evolve toward 5G, the increasing complexity of network functions
    and the widespread deployment of edge devices such as IoT nodes, user equipment (UE),
    and application functions (AFs) <xref target="TS-23.501" /> introduce significant challenges to existing security models.
    These environments are inherently dynamic, heterogeneous, and latency-sensitive, making it
    difficult for traditional rule-based configurations, which are typically static and manually
    managed, to respond effectively to changing conditions. In particular, security operations at
    the edge require more contextual awareness, automation, and adaptability than ever before.
    </t>

    <t>
    Intent-Based Networking (IBN) provides a promising paradigm to meet these requirements.
    It enables operators or users to declare high-level goals, or intents, which the system can
    automatically translate into enforceable security and network policies <xref target="TS-28.312" />.
    These policies may range from abstract service-level objectives to fine-grained access control rules.
    By automating this translation and enforcement process, the network gains the ability to respond autonomously
    to operational demands without requiring manual intervention. This model supports closed-loop
    control, where real-time feedback mechanisms continuously refine and adapt system behavior based
    on evolving context and intent.
    </t>

    <t>
    This document defines an intent-based framework for edge security management in the context of
    5G systems. The framework builds upon the service-based architecture (SBA) defined in 3GPP 5G and
    beyond, and introduces a layered approach that includes intent translation, policy generation,
    enforcement, and monitoring. It integrates seamlessly with existing 3GPP network functions such as
    the Policy Control Function (PCF) <xref target="TS-29.520" />, Access and Mobility Management Function (AMF),
    Session Management Function (SMF), and Network Data Analytics Function (NWDAF) <xref target="TS-23.288" />.
    The aim is to deliver scalable and adaptive security control across heterogeneous edge domains through 
    policy-driven orchestration.
    </t>

    <t>
    Furthermore, the framework is designed to support mobility scenarios, including handovers between
    gNBs and session migration across multiple User Plane Functions (UPFs). By dynamically enforcing
    intents on the edge, the system maintains consistent and context-aware security postures even in
    the presence of mobility events. This capability improves network resilience and responsiveness
    and provides a foundation for secure, automated, and intelligent 5G services. The proposed
    framework also aligns with long-term goals of zero-touch security, AI-driven orchestration, and
    intent-based policy automation within future mobile network infrastructures.
    </t>
</section>



<section anchor="section:Terminology" title="Terminology">
    <t> 
    This section provides definitions of the key terms and concepts used throughout this document.
    The terminology is intended to establish a common understanding of the architectural elements,
    interfaces, and operational principles discussed in the context of intent-based security management
    in 5G networks. These terms are used to describe 5G Network automation based on the Intent-Based
    Networking (IBN) and Interface to Network Security Functions (I2NSF) framework.
    </t>

    <t>
    <list style="symbols">

      <t>
        Intent: It refers to a set of operational objectives and expected outcomes that a network is expected to fulfill, 
        expressed in a declarative manner without specifying the implementation details or the exact procedures 
        to achieve them <xref target="RFC9315" />. Intents can be represented using XML 
        <xref target="RFC6020" /> <xref target="RFC7950" /> or YAML <xref target="YAML" /> formats, and 
        may be delivered to the target components through protocols such as NETCONF <xref target="RFC6241" />, 
        RESTCONF <xref target="RFC8040" />, or via standard REST APIs <xref target="REST" />.
      </t>
      
      <t>
        IBN User Function (IUF): The IUF is typically accessed via a web-browser interface, which allows Mobile Object
        administrators to input network intents for the IBN Control Function (ICF). These intents serve as strategic
        objectives that guide the generation of security and network policies within the system.
      </t>

      <t>
        IBN Control Function (ICF): The ICF operates as a core component of the I2NSF architecture
        deployed within the 5G network. It is responsible for managing and orchestrating security enforcement
        functions by both translating the intents from the IUF into actionable policies, and selecting appropriate
        5G Network Functions (NFs) for their execution.
      </t>

      <t>
        Developer's Management Function (DMF): The DMF is a component within the Interface to Network Security Functions
        (I2NSF) framework that acts as a provider of Network Security Functions (NSFs). It is responsible for
        registering the capabilities of these NSFs with the Security Controller, essentially making them available
        for use in enforcing security policies. 
      </t>

      <t>
        Security Control Function (SCF): The SCF strengthens network security by generating low-level policies to modify
        and supplement the network configuration based on the delivered network policy and delivering them
        to the relevant individual NFs.
      </t>

      <t>
        Security Data Analytics Function (SDAF): THE SDAF collects and analyzes monitoring data to verify whether 
        the policies generated based on intents have been properly enforced by the network security functions,
        and to evaluate the performance and functionality of the security services.
      </t>

      <t>
        Network Security Function (NSF): The NSF is a network security function that provides actual security services
        based on policies generated based on the user's intent. It actually executes security tasks such as blocking
        or allowing traffic based on the policy delivered from ICF.
      </t>
    
    </list>
    </t>

</section>


<section title="An I2NSF-Based Architecture for 5G Edge Security Management">
    <t>
    This section defines a comprehensive framework for 5G security management automation by introducing
    its essential components and explaining how each of them is designed to interconnect with functions
    in the 5G core networks <xref target="TS-23.501" />. The framework is grounded in intent-based networking principles,
    which enable high-level user or application intents to be automatically translated into actionable policies.
    These policies are then enforced and monitored across both the core and edge domains without requiring
    manual intervention.
    </t>

    <t>
    As 5G networks become more distributed and support a growing number of latency-sensitive services and heterogeneous devices,
    traditional static security mechanisms struggle to cope with the dynamic nature of threats and the scale of real-time traffic.
    Manual configuration is no longer feasible in such environments, making automated security orchestration essential to maintain
    consistent protection, reduce response time, and minimize human error.
    </t>
    
    <t>
    To realize this, the framework leverages a set of I2NSF-based functional modules that
    collectively support policy translation, enforcement, and real-time monitoring. By integrating these components
    into the 5G architecture, the system enables scalable, adaptive, and context-aware security operations
    tailored to the needs of dynamic and heterogeneous edge environments.
    </t>

      <figure anchor="figure:5G-Edge-Security-Management-Automation" align="center"
          title="I2NSF-Based Security Management Framework for 5G Edge Networks">
          <artwork align="left"><![CDATA[
+------------------------------------+ +-----------------------------+
| 5G Core NFs                        | |                             |
| +-----+  +-----+  +-----+  +-----+ | | +-----+  +-----+  +------+  |
| |NSSF |  | UDM |  | NRF |  | PCF | | | | IUF |  | ICF |  | SDAF |  |
| +---+-+  +---+-+  +---+-+  +---+-+ | | +--+--+  +--+--+  +--+---+  |
|     |        |        |        |   | |    |        |        |      |
| --+-+------+-+------+-+---+--+-+---+-+----+---+----+----+---+----- |
|   |        |        |        |     | |        |         |          |
| +-+---+  +-+---+  +-+---+  +-+---+ | |     +-----+   +-----+       |
| | AUSF|  | AMF |  | SMF |  | NEF | | |     | DMF |   | SCF |       |
| +-----+  +-+-+-+  +--+--+  +-----+ | |     +-----+   +-----+       |
|            | |       |             | |                             |
|      +-----+ +--+    +------+      | |  AFs for Security Services  |
+------+----------+-----------+------+ +-----------------------------+
       |          |           |                         
    +--+--+   +---+---+    +--+---+   +--+---+   +--------------+
    | UE  +---+ (R)AN +----+ UPFs +---+ NSFs +---+ Data Network |
    +-----+   +-------+    +--+---+   +------+   +--------------+
]]></artwork>
      </figure>


<t>
<xref target="figure:5G-Edge-Security-Management-Automation" /> illustrates a 5G edge security service architecture based on
the I2NSF framework <xref target="RFC8329" />, implemented as an Intent-Based System (IBS). An intent-based management strategy
is required between the 5G Core network and distributed edge domains to enable the autonomous configuration and security
enforcement of edge functions such as User Equipment (UEs), as described in the IETF draft on intent-based network management automation.
</t>

<t>
On the right side of the architecture, the AFs for Security Services represent application-layer functions that initiate
and manage high-level security intents. These functions serve as the interface between external users or applications and
the intent-based security system. This service is composed of several key modules, including the Intent-Based Use Function (IUF),
the Intent Control Function (ICF), the Security Control Function (SCF), the Developer's Management Function (DMF), and the
Security Data Analytics Function (SDAF), which collectively support intent interpretation, policy translation, enforcement,
and monitoring across the network.
</t>

<t>
The security intent generated by the Intent-Based Network Use Function (IUF) is first interpreted
as a high-level objective reflecting the desired behavior of the network or specific applications. This intent is then
processed by the Intent-Based Network Control Function (ICF), which plays a central role in translating the abstract intent
into concrete policies. Through this translation process, two distinct types of policies are created: a network policy,
which governs how the underlying network should behave (e.g., traffic routing, filtering, or QoS enforcement), and an application
policy, which defines how specific applications or devices should operate under given security constraints.
</t>

<t>
Once these policies are generated, they are delivered to the 5G Core Network via the Network Exposure Function (NEF). The NEF serves
as the gateway between external application functions and the internal control plane of the 5G Core. To support flexible deployment and
orchestration, these components can be implemented as containerized microservices and managed using Kubernetes<xref target="Kubernetes" />.
By passing the policies through the NEF, the system enables relevant 5G Core components such as the Policy Control Function (PCF), Session 
Management Function (SMF), and Access and Mobility Management Function (AMF) to enforce the translated policies in real time. This ensures 
that the original user or service intent is consistently and dynamically applied throughout the network.
</t>
</section>



<section title="The Procedure for I2NSF-Based 5G Edge Security Management">
<t>
This testbed demonstrates a use case where high-level user intents are automatically translated into enforceable network and application policies.
Leveraging the I2NSF (Interface to Network Security Functions) framework <xref target="RFC8329" /> and deployed on
the free5GC platform, this architecture enables automated, intent-driven security management that reduces
the reliance on manual configuration and static rule sets.
</t>

<t>
The system is designed to support distributed policy enforcement by integrating key I2NSF components such as
the Intent-Based Networking Use Function (IUF), Intent Control Function (ICF), Security Control Function (SCF),
and Security Data Analytics Function (SDAF). These components work collaboratively to process intents, generate
appropriate policies, and enforce them dynamically across both the core network and the edge.
</t>

    <figure anchor="figure:Intent-Based-Policy-Generation-and-Delivery"
     title="The Procedure of Policy Generation and Delivery for 5G Edge Network">
            <artwork><![CDATA[    
                 +--------------+ 
                 |User Equipment|
                 +--------------+ 
                        ^  Appplication Policy
                        |    (Configuration)     
                        |          +-------------------+ 
+-----+             +--------+     |    IBN Control    |         +----------+
| NEF |<------------+ Router |<----+      Function     |<--------+ IBN Use  |
+-----+   Network   +--------+     |(Intent Translator)|  Intent | Function |
5G Core   Policy                   +-------------------+         +----------+
Network (Firewall& WebFilter) 
]]></artwork>
    </figure>

<t>
<xref target="figure:Intent-Based-Policy-Generation-and-Delivery" /> shows the procedure for 5G Edge Security 
Management Automation, specifically illustrating the creation of user intents and the generation of corresponding network policies
and application policies. The process begins when a user or administrator expresses a security-related intent via the IBN Use Function (IUF).
This intent, representing a high-level goal such as restricting access to certain websites or monitoring device behavior,
is passed to the IBN Control Function (ICF). The ICF, equipped with an Intent Translator, converts this intent into both
network-level and application-level policies. The translated network-level policies are forwarded through the router to the 5G Core's Network Exposure Function (NEF) <xref target="TS-29.503" />,
while the application-level policies are delivered directly to the User Equipment (UE). 
This enables consistent policy enforcement from the core network to the device edge.
</t>

    <figure anchor="figure:5G-security-management-automation-framework-procedure"
     title="The Procedure within an I2NSF-Based Framework for 5G Edge Security Management">
            <artwork><![CDATA[   
           User Equipment 1 (SmartPhone)  User Equipment 2 (IoT Device)   
              +---------------------+        +---------------------+
              | +-----------------+ |        | +-----------------+ |
              | |Service Functions| |        | |Service Functions| |
              | |      (SFs)      | |        | |      (SFs)      | |
              | +-----------------+ |        | +-----------------+ |
              |          ^ |        |        |          ^ |        |
              |Monitoring| |  API   |        |Monitoring| |  API   |
              |   Data   | |Command |        |   Data   | |Command |
              |          | V        |        |          | V        |
              |   +--------------+  |        |   +--------------+  |
              |   |IBN Controller|  |        |   |IBN Controller|  |
              |   +--------------+  |        |   +--------------+  |
              |          ^  |       |        |        ^       |    |
              +----------+--+-------+        +--------+-------+----+
                         |  |                         |       | 
                         |  +---------------------------------+
                         |                            |       |   
                         +--------------+-----+-------+----+  +
                   Application Policy   |     |            |  |
                    (Configuration)     |     |            |  |
                                        |     |            |  |
            +---------------------------+-----+-----+      |  |
            |                           |     |     |      |  |
+--------+  |   +------+   +-----+   +--+--+  |     |      |  |
|  Data  +--|---+ NSFs +---+ UPF +---+ gNB |  |     |      |  |
| Network|  |   +------+   +--+--+   +--+--+  |     |      |  |
+--------+  |                 |         |     |     |      |  |
            |              +--+--+   +--+--+  |     |      |  |
            |              | SMF |   | AMF +--+     |      |  |
            |              +--+--+   +--+--+        |      |  |
            |                 |         |           |    +-+--+---+
            |  ------------+--+-----+---+----+---   |    | Router +---+
            |              |        |        |      |    +---+----+   | 
            |           +--+--+  +--+--+  +--+--+   |        |        |
            |           | DMF |  | SCF |  | NEF |<--+--------+        |
            |           +--+--+  +--+--+  +--+--+   | Network         |
            |                                       | Policy          |
            |                                       | (Firewall       |
            +---------------------------------------+ & Web Filter)   |
                          5G Core Network                             |
                                                           Monitoring |
                                                             Report   |
                                                                      V
                                                        +-------------------+
                                                        |   Security Data   |
                                                        | Analytics Function|
                                                        +---------+---------+
                                                                  |
                                                  +---------------+---------+
                                                  | Monitoring Data Storage |
                                                  +-------------------------+  
]]></artwork>
   </figure>

    <t>
    <xref target="figure:5G-security-management-automation-framework-procedure" /> illustrates the procedure of how the intent-driven network
    policies and application policies are applied across both the 5G core network and user equipment. These policies are then propagated throughout
    the 5G network to support coordinated and consistent security enforcement. Network-level policies are distributed to core network
    functions <xref target="TS-23.501" />, where they help guide the overall behavior and resource allocation of the system in alignment 
    with the user's intent. At the same time, application-level policies are delivered to various user devices, such as smartphones and IoT nodes,
    which have embedded controllers capable of interpreting and enforcing the received policies locally. 
    </t>

    <t>
    This allows each device to autonomously adjust its behavior according to the defined security or operational requirements. 
    In parallel, network-based security functions are also engaged to apply the necessary controls, such as access restrictions or traffic
    filtering, ensuring that both the core and the edge of the network operate securely and in harmony with the original intent. 
    This distributed approach enables flexible, scalable, and adaptive policy enforcement across the entire mobile network environment <xref target="TS-23.288" />. 
    </t>

    <t>
    To support adaptive security validation, each user equipment's IBN Controller periodically generates monitoring reports based on local
    policy enforcement status. These reports are sent to the Security Data Analytics Function (SDAF), which analyzes the monitoring data to
    evaluate whether the applied policies are effectively enforced. All collected data is stored in a centralized Monitoring Data Storage module,
    enabling real-time policy validation and historical auditing. The related steps are as follows:

    <list style="symbols">
        <t>
        Steps 1-2: An intent is sent from an application within the 5G Core to the IBN Control Function (ICF),
        where it is translated into network and application policies. This marks the beginning of intent-driven
        automation for security management.
        </t>

        <t>
        Step 3: The network policy is delivered via the NEF to relevant 5G Core functions and connected security components.
        These components then prepare for the enforcement of the policy.
        </t>

        <t>
        Step 4: The application policy is sent to the IBN Controllers on target user devices.
        This allows the devices to receive instructions without direct user intervention.
        </t>

        <t>
        Step 5: Each device applies the policy to adjust its settings and behavior.
        The changes take effect locally to reflect the system-wide intent.
        </t>

        <t>
        Step 6: Devices monitor their own status and send relevant data back to their IBN Controllers.
        This ensures continuous awareness of policy impact at the device level.
        </t>

        <t>
        Step 7: The IBN Controllers compile and forward the data as monitoring reports.
        These reports provide a basis for evaluating the effectiveness of the applied policies.
        </t>

        <t>
        Step 8: The reports are analyzed to check if the policies are working as intended, and the results
        are stored for future use. This completes the feedback loop that enables adaptive policy refinement.
        </t>
    </list>
    </t>

    <t>
    Through this process, the system enables intent-driven security management that spans from core network
    functions to individual user devices. By translating high-level intents into enforceable policies and continuously
    monitoring their effects, the architecture supports real-time adaptation to network conditions and user behaviors.
    This ensures that security enforcement remains consistent, context-aware, and autonomous throughout distributed edge environments.
    Moreover, the closed-loop structure provides a foundation for scalable and self-optimizing
    policy management, which is essential for future 5G edge-native networks.
    </t>

    <t>
    Also, the proposed system extends the core components such as the Intent-Based Networking Use Function (IUF),
    Intent Control Function (ICF), and distributed enforcement modules to operate in tandem with the handover procedures defined
    in 3GPP specifications. This helps keep security consistent and smart across the edge network where quick response and local
    control are especially important. This approach can also be applied to mobility scenarios where intent-driven security policies
    need to dynamically migrate and be re-enforced as User Equipment (UE) transitions between gNBs.
    </t>

</section>


<section title="Security Considerations Sections">
  <t>
  In the context of intent-based edge security management in 5G networks, several important security aspects
  must be considered to ensure robust and trustworthy system behavior. One key concern involves the potential for malicious manipulation 
  of user intents. Since intents are high-level expressions of user goals that drive the automated generation of network and application policies, any unauthorized
  alteration could lead to unintended or insecure outcomes. Ensuring that each intent originates from a trusted source
  and is protected by integrity validation mechanisms is therefore essential.
  </t>

  <t>
  Another important consideration is the accuracy and reliability of the policy translation and enforcement process.
  When translating abstract intents into concrete policies, the system must preserve the user's original intent without
  introducing misconfigurations or inconsistencies. Incorporating validation checks and feedback mechanisms helps to ensure
  that policies are correctly interpreted and consistently applied across the network. To further enhance this process,
  deep learning techniques <xref target="Deep-Learning" /> can be employed to detect anomalies, learn from past policy
  enforcement outcomes, and adaptively improve the translation logic based on contextual patterns and historical data.
  </t>
</section>



<section anchor="section:IANA-Considerations" title="IANA Considerations">
  <t>
    This document does not require any IANA actions.
  </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.7149"?>
    <?rfc include="reference.RFC.7950"?>
    <?rfc include="reference.RFC.8040"?> 
    <?rfc include="reference.RFC.8329"?> 
    <?rfc include="reference.RFC.9315"?> 
    
</references>
<!-- END: Normative References -->


<!-- START: Informative References -->
<references title="Informative References">

    <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="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.503">
        <front>
            <title>Service-Based Interface Specifications for the Network Exposure Function (NEF)</title>
            <author surname="3GPP TS 29.503 V18.3.0" />
            <date month="September" year="2023" />
        </front>
        <seriesInfo name="Available:" value="https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3342" />
    </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="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="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="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="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>

    <reference anchor="Survey-IBN-CST-2023">
        <front>
            <title>A Survey on Intent-Based Networking</title>
            <author initials="A." surname="Leivadeas" />
            <author initials="M." surname="Falkner" />
            <date month="March" year="2023" />
        </front>
        <seriesInfo name="Available:" value="https://ieeexplore.ieee.org/document/9925251" />    
    </reference>

    <reference anchor="ClickINC-Sigcomm-2023">
        <front>
            <title>ClickINC: In-network Computing as a Service in Heterogeneous Programmable Data-center Networks</title>
            <author initials="W." surname="Xu" />
            <author initials="Z." surname="Zhang" />
            <author initials="Y." surname="Feng" />
            <author initials="H." surname="Song" />
            <author initials="Z." surname="Chen" />
            <author initials="W." surname="Wu" />
            <author initials="G." surname="Liu" />
            <author initials="Y." surname="Zhang" />
            <author initials="S." surname="Liu" />
            <author initials="Z." surname="Tian" />
            <author initials="B." surname="Liu" />
            <date month="September" year="2023" />
        </front>
        <seriesInfo name="Publisher:" value="ACM SIGCOMM" />
        <seriesInfo name="Available:" value="https://dl.acm.org/doi/10.1145/3603269.3604835" />    
    </reference>

</references>
<!-- END: Informative References -->


<!-- START: Acknowledgments -->
<section anchor="section:Acknowledgments" numbered="false" title="Acknowledgments">
    <t indent="0" pn="section-appendix.a-1">
    This work was supported by Institute of Information &amp; Communications
    Technology Planning &amp; Evaluation (IITP) grant funded by the Korea
    Ministry of Science and ICT (MSIT) (No. RS-2024-00398199 and
    RS-2022-II221015).
    </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. IITP-2025-RS-2022-II221199,
    Regional strategic industry convergence security core talent training
    business).
    </t>

</section>
<!-- END: Acknowledgments -->



<!-- START: Contributors -->
<section anchor="section:Contributors" numbered="false" title="Contributors">
    <t indent="0" pn="section-appendix.b-1">
    This document is made by the group effort of NMRG, 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 is the coauthor of this document:
    </t>   
      <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>
<!-- END: Contributors -->

</back>

<!-- <vspace blankLines="100"/> -->
<!-- page break to put addresses onto one page-->

</rfc>