<?xml version='1.0' encoding='utf-8'?> version="1.0" encoding="UTF-8"?>

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
  <!ENTITY I-D.irtf-nmrg-ibn-concepts-definitions SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.irtf-nmrg-ibn-concepts-definitions.xml"> nbsp    "&#160;">
  <!ENTITY RFC2119 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"> zwsp   "&#8203;">
  <!ENTITY RFC7575 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7575.xml"> nbhy   "&#8209;">
  <!ENTITY RFC8328 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8328.xml">
<!ENTITY RFC3198 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3198.xml">
<!ENTITY RFC6020 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6020.xml">
<!ENTITY RFC7285 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7285.xml">
<!ENTITY I-D.du-anima-an-intent SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.du-anima-an-intent.xml">
<!ENTITY I-D.ietf-supa-generic-policy-info-model SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-supa-generic-policy-info-model.xml">
<!ENTITY I-D.ietf-anima-prefix-management SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-anima-prefix-management-07.xml">
<!ENTITY I-D.ietf-anima-prefix-management SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-anima-prefix-management.xml"> wj     "&#8288;">
]>

<rfc submissionType="IETF" docName="draft-irtf-nmrg-ibn-intent-classification-08" xmlns:xi="http://www.w3.org/2001/XInclude" submissionType="IRTF" category="info" ipr="trust200902">
	<!-- Generated by id2xml 1.5.0 on 2022-06-23T22:24:54Z -->
	<?rfc strict="yes"?>
	<?rfc compact="yes"?>
	<?rfc subcompact="no"?>
	<?rfc symrefs="yes"?>
	<?rfc sortrefs="no"?>
	<?rfc text-list-symbols="oo*+-"?>
	<?rfc toc="yes"?> consensus="true" docName="draft-irtf-nmrg-ibn-intent-classification-08" number="9316" ipr="trust200902" obsoletes="" updates="" xml:lang="en" symRefs="true" sortRefs="true" tocInclude="true" version="3">

	<front>
    <title>Intent Classification</title>
    <seriesInfo name="RFC" value="9316"/>
    <author initials="C." surname="Li" fullname="Chen Li">
      <organization>China Telecom</organization>
	<address><postal><street>No.118
      <address>
        <postal>
	  <extaddr>Xicheng District</extaddr>
          <street>No.118 Xizhimennei street, Xicheng District</street> street</street>
          <city>Beijing</city>
          <code>100035</code>
	<country>P.R. China</country>
          <country>China</country>
        </postal>
	<email>lichen.bri@chinatelecom.cn</email>
        <email>lichen6@chinatelecom.cn</email>
      </address>
    </author>
    <author initials="O." surname="Havel" fullname="Olga Havel">
      <organization>Huawei Technologies</organization>
	<address><postal>
	  <street></street>
      <address>
        <postal>
          <street/>
          <country>Ireland</country>
        </postal>
        <email>olga.havel@huawei.com</email>
      </address>
    </author>
    <author initials="A." surname="Olariu" fullname="Adriana Olariu">
      <organization>Huawei Technologies</organization>
	<address><postal>
  	  <street></street>
      <address>
        <postal>
          <street/>
          <country>Ireland</country>
        </postal>
        <email>adriana.olariu@huawei.com</email>
      </address>
    </author>
    <author initials="P." surname="Martinez-Julia" fullname="Pedro Martinez-Julia">
      <organization>NICT</organization>
	<address><postal>
	  <street></street>
      <address>
        <postal>
          <street/>
          <country>Japan</country>
        </postal>
        <email>pedro@nict.go.jp</email>
      </address>
    </author>
    <author initials="J." surname="Nobre" fullname="Jeferson Campos Nobre">
      <organization abbrev="UFRGS">Federal University of Rio Grande do Sul</organization>
	<address><postal>
	  <street></street> Sul (UFRGS)</organization>
      <address>
        <postal>
          <street/>
          <city>Porto Alegre</city>
	  <region>RS</region>
          <country>Brazil</country>
        </postal>
        <email>jcnobre@inf.ufrgs.br</email>
      </address>
    </author>
    <author initials="D." surname="Lopez" fullname="Diego R. Lopez">
      <organization abbrev="Telefonica, I+D">Telefonica I+D</organization>
	<address><postal><street>Don
      <address>
        <postal>
          <street>Don Ramon de la Cruz, 82</street>
          <city>Madrid</city>
          <code>28006</code>
          <country>Spain</country>
        </postal>
        <email>diego.r.lopez@telefonica.com</email>
      </address>
    </author>
    <date year="2022" month="June"/> month="October"/>
    <workgroup>Network Management</workgroup>

<!-- [rfced] Please insert any keywords (beyond those that appear in the title) for use on https://www.rfc-editor.org/search. -->

<keyword>example</keyword>

	<abstract><t>

    <keyword>intent taxonomy</keyword>
    <keyword>intent-based network</keyword>
    <keyword>intent users</keyword>
    <keyword>intent categories</keyword>
    <keyword>intent types</keyword>
    <keyword>network management</keyword>
    <keyword>network automation</keyword>
    <keyword>network intent</keyword>
    <keyword>network service</keyword>
    <keyword>network orchestration</keyword>
    <keyword>intent translation</keyword>

<abstract>

  <t>

   Intent is an abstract, high-level policy used to operate the a network.
   Intent-based
   An intent-based management system includes an interface for users to
   input requests and an engine to translate the intents into the
   network configuration and manage their life-cycle.</t> life cycle.</t>
      <t>
   This document discusses mostly discusses the concept of network intents, but
   other types of intents are also being considered. Specifically, it this document
   highlights stakeholder perspectives of intent, methods to classify
   and encode intent, and the associated intent taxonomy, and taxonomy; it also defines
   relevant intent terms where necessary. This document necessary, provides a
   foundation for intent related research intent-related research, and facilitates solution
   development.</t>
      <t>
   This document is a product of the IRTF Network Management Research
   Group (NMRG).</t>
    </abstract>
  </front>
  <middle>
    <section title="Introduction" anchor="sect-1"><t> anchor="sect-1" numbered="true" toc="default">
      <name>Introduction</name>

      <t>
   The vision of intent-based networks has attracted a lot of attention,
   as attention
   because it promises to simplify the management of networks by human
   operators. This is done by simply specifying what should happen on
   the network, network without giving any instructions on how to do it. This
   promise led caused many researcher-led activities and telecom companies to
   start researching this new vision, vision and many Standards Development
   Organization
   Organizations (SDOs) to propose different intent frameworks.</t>
      <t>
   This draft document proposes an intent classification methodology and an
   intent taxonomy. The scope of these proposals is to ensure a common
   understanding in the research community in terms of what are the
   intent users, intent types, or intent solutions, etc. etc., are for specific
   scenarios that are being considered.</t>
      <t>
   The document represents the consensus of the Network Management
   Research Group (NMRG). It has been reviewed extensively by the
   Research Group (RG) members who are actively involved in the research
   and development of the technology covered by this document. It is not
   an IETF product and is not a standard.</t>
      <section title="Research activities" anchor="sect-1.1"><t> anchor="sect-1.1" numbered="true" toc="default">
        <name>Research Activities</name>
        <t>
   Intent-based networking is an active research topic which spans spanning
   across different areas that could benefit from an intent
   classification and taxonomy.</t>

	<t>
   One such area is

 <t>Some examples include:
 </t>

 <ul>
   <li>
     intent expression and recognition ([Bezahaf21],
   [Bezahaf19]), NILE [Jacobs18]). (<xref
   target="Bezahaf21" format="default"/>, <xref target="Bezahaf19"
   format="default"/>, <xref target="Jacobs18" format="default"/>).
The use of a common classification
   can could provide consistency in the
understanding of the various forms of intent expressions being proposed and investigated.</t>

	<t>
   Another area where this intent classification could contribute is
investigated.

       </li>

       <li>
the orchestration of cognitive autonomous RANs [Banerjee21] radio access networks (RANs) <xref
target="Banerjee21" format="default"/> where intents are
classified based on their content.</t>

	<t>
   The work carried in content.

	  </li>

	  <li>
	    intent network verification <xref target="Tian19"/> target="Tian19"
	    format="default"/>, where the authors are proposing working to propose new
	    intent language is another candidate where
   intent classification could be used advantageously.</t> language.

   </li>

 </ul>

        <t>

   Furthermore, this draft document is proving itself already proving to be extremely relevant to the
   research community as it has been used as the basis for proposing
   self-generated Intent-based systems [Bezhaf19], <xref target="Bezahaf19"
   format="default"/>, for advancing IBN-based VNF Virtual Network Function (VNF) placement solutions based on Internet-Based Networks (IBNs) that rely on defining user intent profiles corresponding to abstract network
   services
   [Leivadeas21], <xref target="Leivadeas21" format="default"/>, for improving
   existing solutions in provisioning intent-based networks, and for proposing new
   approaches to service management <xref target="Davoli21"/>, or target="Davoli21"
   format="default"/>, and even for defining grammars for users to specify the
   high-level requirements for blockchain selection in the form of intent
   <xref target="Padovan20"/>. target="Padovan20" format="default"/>. As well, the draft document has been
   mentioned in surveys addressing the topic of intelligent intent-based
   autonomous networks <xref target="Mehmood21"/>, target="Mehmood21" format="default"/> <xref target="Szilagyi21"/>.</t>
   target="Szilagyi21" format="default"/>.</t>
        <t>
   This document also describes as well an example on how this proposal has been
   successfully applied in an academic environment [IBN-POC] <xref target="POC-IBN"
   format="default"/> by researchers in the area of SDN/NFV Software-Defined Networking / Network Function Virtualization (SDN/NFV) for defining the
   scope of their project. The specific problem addressed by researches researchers is how
   to apply intent concepts at different levels that correspond to different
   stakeholders.</t>
        <t>
   The IEEE Communications Society Technical Committee on Network Operation and
   Management (IEEE-CNOM), IRTF-NMRG IRTF Network Management Research Group, and IFIP WG6.6 have developed a taxonomy
   for network and service management [IFIP-NSM] <xref target="IFIP-NSM"
   format="default"/> that is used by the research community in network
   management and operations to structure the research area through a
   well-defined set of keywords and to improve quality of reviews in
   submissions to journals,
   conferences conferences, and workshops. The proposed intent
   taxonomy may be contributed as an extension to this taxonomy for intent driven intent-driven management.</t>
      </section>
      <section title="Standards anchor="sect-1.2" numbered="true" toc="default">
        <name>Standards and open source activities" anchor="sect-1.2"><t> Open-Source Activities</name>

	<t>
   Several SDOs and open source open-source projects, such as Internet Research Task
   Force (IRTF)/ Network Management Research Group (NMRG), the IRTF NMRG, Open Networking
   Foundation (ONF) [ONF] <xref target="ONF" format="default"/> / Open Network
   Operating System (ONOS) [ONOS], <xref target="ONOS" format="default"/>, European
   Telecommunications Standards Institute
   (ETSI)/Experiential (ETSI) / Experiential Networked
   Intelligence (ENI), and TMF with its
   Autonomous Networks, autonomous networks, have proposed intents
   for defining a set of network operations to execute in a declarative
   manner.</t>

   <t>
   More recently, the IRTF NMRG is working on the Intent-based "Intent-Based Networking -
   Concepts and Definitions document, Definitions" <xref
   target="I-D.irtf-nmrg-ibn-concepts-definitions"/>. target="RFC9315" format="default"/>. This document clarifies
   the concept of "Intent" and provides an overview of the functionality that
   is associated with it.  The goal is to contribute towards a common and
   shared understanding of terms, concepts, and functionality that can be used
   as the foundation to guide further definition of associated research and
   engineering problems and their solutions.</t>
        <t>
   The present document, together with <xref
   target="I-D.irtf-nmrg-ibn-concepts-definitions"/>, target="RFC9315" format="default"/>, aims to become the
   foundation for future intent-related topic discussions regarding the
   NMRG.</t>

   <t>
   The SDOs usually came come up with their own way of specifying an intent, intent and
   with
   their own understanding of what an intent is. Besides that,

   Additionally, each SDO defines a set of terms and level of abstraction, its intended intent users, and the applications and usage scenarios.</t> scenarios.

   </t>
        <t>
   However, most intent approaches proposed by SDOs share the same following features:</t>

	<t><list style="symbols"><t>It
        <ul spacing="normal">
          <li>It must be declarative in nature, meaning that an intent user
     specifies the goal on the network without specifying how to achieve
     that goal.</t>

	<t>It goal.</li>
          <li>It must be vendor agnostic, agnostic in the sense that it abstracts the
     network capabilities, capabilities or the network infrastructure from the intent
     user, and it can be ported across different platforms.</t>

	<t>It platforms.</li>
          <li>It must provide an easy-to-use interface, which simplifies the
     intent users'
     interaction of the intent users with the intent system through the usage
     of familiar terminology or concepts.</t>

	</list>
	</t>

	<t> concepts.</li>

     <li>
   It should be able to detect and resolve intent conflicts, which include,
   for example, static (compile-time) conflicts and dynamic (run-time) conflicts.</t>
   conflicts.
</li>
        </ul>

      </section>
      <section title="Scope" anchor="sect-1.3"><t> anchor="sect-1.3" numbered="true" toc="default">
        <name>Scope</name>

        <t>
   The focus of this document is on the definition of criteria enabling
   to categorize
   the categorization of intents from viewpoint of the stakeholders' viewpoint. stakeholders.  Concepts and
   definitions related to IBN are provided in <xref target="I-D.irtf-nmrg-ibn-concepts-definitions"/>.</t> target="RFC9315" format="default"/>.</t>
        <t>
   This document mostly addresses intents in the context of network
   intents, however
   intents; however, other types of intents are not excluded, as
   presented in section 4.4. Sections <xref target="sect-4.4" format="counter"/> and section 6.2. .</t> <xref target="sect-6.2" format="counter"/>.</t>
        <t>
   It is impossible to fully differentiate intents only by the common
   characteristics followed by concepts, terms terms, and intentions. This
   document clarifies what an intent represents for different
   stakeholders through a classification on various dimensions, such as
   solutions, intent users, and intent types. This classification
   ensures common understanding among all participants and is used to
   determine the scope and priority of individual projects,
   proof-of-concept
   proof of concepts (PoCs), research initiatives, or open source open-source projects.</t>
        <t>
   The scope of intent classification in this document includes
   solutions, intent users users, and intent types, and types; the initial
   classification table is made according to this scope. The
   methodology presented can be used to update the classification
   tables by adding or removing different solutions, intent users, or
   intent types to cater for to future scenarios, applications applications, or domains.</t>
      </section>
    </section>
    <section title="Acronyms" anchor="sect-2"><t>

	  <list>
     <t>AI: Artificial Intelligence</t>
     <t>CE: Customer Equipment</t>
     <t>CFS: anchor="sect-2" numbered="true" toc="default">
      <name>Abbreviations</name>

      <dl>
<dt>AI:
</dt>
<dd>Artificial Intelligence
</dd>

<dt>CE:
</dt>
<dd> Customer Equipment
</dd>

<dt>CFS:
</dt>
<dd>Customer Facing Service</t>
     <t>CLI: Command Line Interface</t>
     <t>DB: Database</t>
     <t>DC: Data Center</t>
     <t>ECA: Event-Condition-Action</t>
     <t>GBP: Group-Based Policy</t>
     <t>GPU: Graphics Service
</dd>

<dt>CLI:
</dt>
<dd>Command-Line Interface
</dd>

<dt>DB:
</dt>
<dd>Database
</dd>

<dt>DC:
</dt>
<dd>Data Center
</dd>

<dt>ECA:
</dt>
<dd>Event Condition Action
</dd>

<dt>GBP:
</dt>
<dd>Group-Based Policy
</dd>

<dt>GPU:
</dt>
<dd>Graphics Processing Unit</t>
     <t>IBN: Intent Based Network</t>
     <t>NFV: Network Unit
</dd>

<dt>IBN:
</dt>
<dd>Intent-Based Network
</dd>

<dt>NFV:
</dt>
<dd>Network Function Virtualization</t>
     <t>O&amp;M: Operations Virtualization
</dd>

<dt>O&amp;M:
</dt>
<dd>OAM &amp; Maintenance</t>
     <t>ONF: Open Maintenance
</dd>

<dt>ONF:
</dt>
<dd>Open Networking Foundation</t>
     <t>ONOS: Open Foundation
</dd>

<dt>ONOS:
</dt>
<dd>Open Network Operating System</t>
     <t>PNF: Physical System
</dd>

<dt>PNF:
</dt>
<dd>Physical Network Function</t>
     <t>QoE: Quality of Experience</t>
     <t>RFS: Resource Function
</dd>

<dt>QoE:
</dt>
<dd>Quality of Experience
</dd>

<dt>RFS:
</dt>
<dd>Resource Facing Service</t>
     <t>SDO: Standards Service
</dd>

<dt>SDO:
</dt>
<dd>Standards Development Organization</t>
     <t>SD-WAN: Software-Defined Organization
</dd>

<dt>SD-WAN:
</dt>
<dd>Software-Defined Wide-Area Network</t>
     <t>SLA: Service Network
</dd>

<dt>SLA:
</dt>
<dd>Service Level Agreement</t>
     <t>SUPA: Simplified Agreement
</dd>

<dt>SUPA:
</dt>
<dd>Simplified Use of Policy Abstractions</t>
     <t>VM: Virtual Machine</t>
     <t>VNF: Virtual Abstractions
</dd>

<dt>VM:
</dt>
<dd>Virtual Machine
</dd>

<dt>VNF:
</dt>
<dd>Virtual Network Function</t>
	</list>
	</t> Function
</dd>

      </dl>

</section>
    <section title="Definitions" anchor="sect-3"><t> anchor="sect-3" numbered="true" toc="default">
      <name>Definitions</name>
      <t>
   A common and shared understanding of terms and definitions related
   to IBN is provided in <xref target="I-D.irtf-nmrg-ibn-concepts-definitions"/>, target="RFC9315" format="default"/> as follows:

   <list style="hanging" hangIndent="3">

   <t hangText="Intent:">A

      </t>
      <dl newline="false" spacing="normal" indent="3">
        <dt>Intent:</dt>
        <dd>A set of operational goals (that a network should meet)
   and outcomes (that a network is supposed to deliver), deliver) defined
   in a declarative manner without specifying how to achieve or
   implement them.</t>

   <t hangText="Intent-Based Network:">A them.</dd>
        <dt>Intent-Based Network:</dt>
        <dd>A network that can be managed using intent.</t>

   <t hangText="Policy:">A intent.</dd>
        <dt>Policy:</dt>
        <dd>A set of rules that governs the choices in behaviour behavior of a system.</t>

   <t hangText="Intent User:">A system.</dd>
        <dt>Intent User:</dt>
        <dd>A user that defines and issues the intent request to the
   intent-based management system.</t>

  </list>
  </t> system.</dd>
      </dl>
      <t>
   Other definitions relevant to this draft, document, such as intent scope,
   intent network scope, intent abstraction, intent abstraction, and
   intent lifecycle life cycle are available in section 5.</t> <xref target="sect-5"/>.</t>
    </section>
    <section title="Abstract anchor="sect-4" numbered="true" toc="default">
      <name>Abstract Intent Requirements" anchor="sect-4"><t> Requirements</name>
      <t>
   In order to understand the different intent requirements that would
   drive intent classification, we first need to understand what intent
   means for different intent users.</t>
      <section title="What anchor="sect-4.1" numbered="true" toc="default">
        <name>What is Intent?" anchor="sect-4.1"><t> intent?</name>
        <t>
   The term Intent "Intent" has become very widely used in the industry for different purposes,
   purposes; sometimes it its use is not even in agreement with SDO
   shared SDO-shared principles
   mentioned in the Introduction section.<xref target="I-D.irtf-nmrg-ibn-concepts-definitions"/> draft <xref target="sect-1" format="default"></xref>. <xref target="RFC9315"
   format="default"/> brings clarification with relation to what an intent is
   and how it differentiates from policies and services.</t>
        <t>
   Different stakeholders have different perspective perspectives of the network and
   therefore network;
   therefore, they have different intent requirements. Their intent is sometimes
   technical, non-technical, abstract abstract, or technology specific.  Therefore, it
   is important to start a discussion in the industry and academia academic communities
   about what intent is for different solutions and intent users. It is also
   imperative to try to propose some intent categories/ classifications categories/classifications that
   could be understood by a wider audience. This would help us define intent
   interfaces, domain-specific languages, and models.</t>
      </section>
      <section title="Intent anchor="sect-4.2" numbered="true" toc="default">
        <name>Intent Solutions and Intent Users" anchor="sect-4.2"><t> Users</name>
        <t>
   Intent types are defined by all aspects that are required to profile
   different requirements to easily distinguish among between them. However, in order
   to facilitate a clustered classification, we can focus on two aspects, aspects: the
   solution and intent user. They can be considered as to be the main keys to
   classify intents, as we can easily group requirements by solution and intent
   user.</t>
        <t>
   On the one hand, different solutions and intent users have different
   requirements, expectations expectations, and priorities for intent-based
   networking. Therefore, intent users require different intent types,
   depending on their context, since they participate in different use
   cases. For instance, some intent users are more technical and require
   intents that expose more technical information. Other intent users do not
   have knowledge of the network infrastructure and require intents that shield
   them from different networking concepts and technologies.</t>
        <t>
   The following are the solutions and intent users that intent-based
   networking needs to support:</t>

	<texttable title="- Intent
        <table anchor="tab-intent-solutions-and-intent-users" align="center">
          <name>Intent Solutions and Intent Users" anchor="tab-intent-solutions-and-intent-users" style="all"><ttcol> Solutions</ttcol>
	<ttcol> Intent Users</ttcol>
	<c>Carrier Users</name>
          <thead>
            <tr>
              <th align="left"> Solutions</th>
              <th align="left"> Intent Users</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Carrier Networks   </c>
	<c>Network Operator   </td>

	      <td align="left">Network Operators, Service Designers/App Developer Designers / App Developers, Service Operators Customers/Subscribers</c>
	<c>DC Operators, Customers / Subscribers</td>
            </tr>
            <tr>
              <td align="left">DC Networks   </c>
	<c>Cloud Administrator   </td>
              <td align="left">Cloud Administrators, Underlay Network Administrator Administrators, Application Developers Customer/Tenants</c>
	<c>Enterprise Developers, Customers / Tenants</td>
            </tr>
            <tr>
              <td align="left">Enterprise Networks  </c>
	<c>Enterprise Administrator  </td>
              <td align="left">Enterprise Administrators, Application Developers End-Users</c>
	</texttable> Developers, End Users</td>
            </tr>
          </tbody>
        </table>
        <t>
   These intent solutions and intent users represent a starting point
   for the classification and are expendable through the methodology
   presented in section 6.1. .</t>

	<t><list style="symbols"><t>For <xref target="sect-6.1"/>.</t>
        <ul spacing="normal">

	  <li>For carrier networks scenario, network scenarios, for example, if a
     customer/subscriber wants to watch high-definition video, then the
     intent is to convert the video image to 1080p rate.</t>

	<t>For 1080p.</li>
          <li>For DC networks scenario, network scenarios, administrators have their own clear
     network intent such as load balancing. For all traffic flows that
     need NFV service chaining, they can restrict the maximum load of any VNF
     node/container
     node / container below 50% and the maximum load of any network link
     below 70%.</t>

	<t>For 70%.</li>
          <li>For enterprise networks scenario, network scenarios, when hosting a video conference conference,
     multiple remote accesses are required. An example of the intent
     from the network administrator is: is as follows: for any end-user end user of this
     application, the arrival time of hologram objects of all the
     remote tele-presenters should be synchronised synchronized within 50ms 50 ms to reach
     the destination viewer for each conversation session.</t>

       <t></t>

	</list>
	</t> session.</li>
        </ul>

      </section>
      <section title="Benefits anchor="sect-4.3" numbered="true" toc="default">
        <name>Benefits of Intents for Different Stakeholders" anchor="sect-4.3"><t> Stakeholders</name>
        <t>
   Current network APIs and CLIs are too complex because they are highly
   integrated with the low level low-level concepts exposed by networks.

 Customers, application developers developers, and end-users end users must not be required to set
 IP addresses, VLANs, subnets, or ports, while whereas operators may still want to
 have both more technical and network visibility.

	All stakeholders would benefit from
   the simpler interfaces, like:</t>

	<t><list style="symbols"><t>Request such as:</t>

        <ul spacing="normal">
          <li>request gold VPN service between my sites A, B B, and C</t>

	<t>Provide C</li>
          <li>provide CE redundancy for the customer sites</t>

	<t>Add sites</li>
          <li>add access rules to the network service</t>

	</list>
	</t> service</li>
        </ul>
        <t>

   Operators and administrators manually troubleshoot and fix their networks
   and services. They instead want to:</t>

	<t><list style="symbols"><t>simplify
        <ul spacing="normal">
          <li>simplify and automate network operations</t>

	<t>simplify operations</li>
          <li>simplify definitions of network services</t>

	<t>provide services</li>
          <li>provide simple customer APIs for value added value-added services (operators)</t>

	<t>be (operators)</li>
          <li>be informed if the network or service is not behaving as requested</t>

	<t>enable requested</li>
          <li>enable automatic optimization and correction for selected scenarios</t>

	<t>have scenarios</li>
          <li>have systems that learn from historic information and behaviour</t>

	</list>
	</t> behavior</li>
        </ul>
        <t>
   Currently, intent users cannot build their own services and policies
   without becoming technical experts and performing manual maintenance
   actions. They instead want to be able to:</t>

	<t><list style="symbols"><t>build
        <ul spacing="normal">
          <li>build their own network services with their own policies via
      simple interfaces, without becoming networking experts</t>

	<t>have experts</li>
          <li>have their network services up and running based on intent and
      automation only, without any manual actions or maintenance</t>

	<t></t>

	</list>
	</t> maintenance</li>
        </ul>
      </section>
      <section title="Intent anchor="sect-4.4" numbered="true" toc="default">
        <name>Intent Types that need That Need to be supported" anchor="sect-4.4"><t> Be Supported</name>
        <t>
   Next to the intent solutions and intent users, another way to
   categorize the intent is through the intent types. The following
   intent types and subtypes need to be supported, supported in order to address
   the requirements from different solutions and intent users:</t>

	<t><list style="symbols"><t>Customer users.</t>
        <ul spacing="normal">
          <li>
            <t>Customer service intent<list style="symbols"><t>for intent</t>
            <ul spacing="normal">
              <li>for customer self-service self service with SLA</t>

	<t>for SLA</li>
              <li>for service operator orders</t>

	</list>
	</t> orders</li>
            </ul>
          </li>
          <li>
            <t>Network and underlay network service intent<list style="symbols"><t>for intent</t>
            <ul spacing="normal">
              <li>for service operator orders</t>

	<t>for intent driven orders</li>
              <li>for intent-driven network configuration, verification, correction correction, and
        optimization</t>

	<t>for
        optimization</li>
              <li>for intent created and provided by the underlay network administrator</t>

	</list>
	</t> administrator</li>
            </ul>
          </li>
          <li>
            <t>Network and underlay network intent<list style="symbols"><t>for intent</t>
            <ul spacing="normal">
              <li>for network configuration</t>

	<t>for configuration</li>
              <li>for automated lifecycle life-cycle management of network configurations</t>

	<t>for configurations</li>
              <li>for network resources (switches, routers, routing, policies, underlay)</t>

	</list>
	</t> and underlay)</li>
            </ul>
          </li>
          <li>
            <t>Cloud management intent<list style="symbols"><t>for intent</t>
            <ul spacing="normal">
              <li>for DC configuration, VMs, DB servers, APP servers</t>

	<t>for and Application servers</li>

              <li>for communication between VMs</t>

	</list>
	</t> VMs</li>
            </ul>
          </li>
          <li>
            <t>Cloud resource management intent<list style="symbols"><t>for intent</t>
            <ul spacing="normal">
              <li>for cloud resource life-cycle management (policy driven (policy-driven self-configuration and auto-scaling and recovery/optimization)</t>

	</list>
	</t> recovery/optimization)</li>
            </ul>
          </li>
          <li>
            <t>Strategy intent<list style="symbols"><t>for intent</t>
            <ul spacing="normal">
              <li>for security, QoS, application policies, traffic steering, etc.</t>

	<t>for etc.</li>
              <li>for configuring and monitoring policies, alarms alarm generation for
         non-compliance, auto-recovery</t>

	<t>for and auto-recovery</li>
              <li>for design models and policies for network and network service design</t>

	<t>for design</li>
              <li>for design workflows, models models, and policies for operational task intents</t>

	</list>
	</t> intents</li>
            </ul>
          </li>
          <li>
            <t>Operational task intents<list style="symbols"><t>for intents</t>
            <ul spacing="normal">
              <li>for network migration</t>

	<t>for migration</li>
              <li>for device replacements</t>

	<t>for replacements</li>
              <li>for network software upgrades</t>

	<t>for upgrades</li>
              <li>for automating any other tasks that operators/administrator often perform</t>

	</list>
	</t>

	</list>
	</t> perform</li>
            </ul>
          </li>
        </ul>
        <t>
   It is important to mention there all of the previously mentioned types and
   subtypes may affect other intents. For example, operational task intent can
   modify many other intents. The task itself is short-lived, short lived, but the
   modification of other intents has an impact on their life-cycle, life cycle, so those
   changes must continue to be continuously monitored and
   self-corrected/self-optimized.</t>
   self corrected/optimized.</t>
      </section>
    </section>
    <section title="Functional anchor="sect-5" numbered="true" toc="default">
      <name>Functional Characteristics and Behaviour" anchor="sect-5"><t> Behavior</name>
      <t>
   Intent can be used to operate immediately on a target (much like
   issuing a command), command) or whenever it is appropriate (e.g., in response
   to an event). In either case, intent has a number of behaviours behaviors that
   serve to further organize its purpose, as described by the following
   subsections.</t>
      <section title="Abstracting anchor="sect-5.1" numbered="true" toc="default">
        <name>Abstracting Intent Operation" anchor="sect-5.1"><t> Operation</name>
        <t>
   The modelling modeling of intents can be abstracted using the following three-tuple:</t>
        <t>{Context, Capabilities, Constraints}</t>

	<t><list style="symbols"><t>Context
        <ul spacing="normal">
          <li>Context grounds the intent, intent and determines if it is relevant or
     not for the current situation. Thus, context selects intents based
     on applicability.</t>

	<t>Capabilities applicability.</li>
          <li>Capabilities describe the functionality that the intent can
     perform.  Capabilities take different forms, forms depending on the
     expressivity of the intent as well as the programming paradigm(s)
     used.</t>

	<t>Constraints
     used.</li>
          <li>Constraints define any restrictions on the capabilities to be used
     for that particular context.</t>

	</list>
	</t> context.</li>
        </ul>
        <t>
   Metadata can be attached via strategy templates to each of the
   elements of the three-tuple, three-tuple and may be used to describe how the
   intent should be used and how it operates, operates as well as prescribe any
   operational dependencies that must be taken into account.</t>
        <t>
   Although different intent categories share the same abstracted intent
   model, each category will have its own specific context, capabilities capabilities,
   and constraints.</t>
      </section>
      <section title="Intent anchor="sect-5.2" numbered="true" toc="default">
        <name>Intent User Types" anchor="sect-5.2"><t> Types</name>
        <t>
   Expanding on the introduction in section 4.2. , <xref target="sect-4.2"/>, intent user
   types represent the intent users that define and issue the intent request.
   Depending on the intent solutions, there are specific intent users.
   Examples of intent users are customers, network operators, service
   operators, enterprise administrators, cloud administrators, and underlay
   network administrators, or application developers.</t>

	<t><list style="symbols"><t>Customers
        <ul spacing="normal">
          <li>Customers and end-users end users do not necessarily know the functional and
     operational details of the network that they are using.
     Furthermore, they lack skills to understand such details; in fact,
     such knowledge is typically not relevant to their job. In
     addition, the network may not expose these details to its intent
     users. This class of intent users focuses on the applications that
     they run, run and uses services offered by the network.  Hence, they
     want to specify policies that provide consistent behaviour behavior
     according to their business needs. They do not have to worry about
     how the intents are deployed onto the underlying network, network and
     especially,
     especially whether the intents need to be translated to different
     forms to enable network elements to understand them.</t>

	<t>Application them.</li>
          <li>Application developers work in a set of abstractions defined by
     their application and programming environment(s). For example,
     many application developers think in terms of objects (e.g., a
     VPN).  While this makes sense to the application developer, most
     network devices do not have a VPN object per se; rather, the VPN
     is formed through a set of configuration statements for that
     device in concert with configuration statements for the other
     devices that together make up the VPN. Hence, the view of
     application developers matches the services provided by the
     network,
     network but may not directly correspond to other views of other
     intent users.</t>

	<t>Network users.</li>
          <li>Network operators may have the knowledge of the underlying
     network. However, they may not understand the details of the
     applications and services of customers.</t>

	</list>
	</t> customers.</li>
        </ul>
      </section>
      <section title="Intent Scope" anchor="sect-5.3"><t> anchor="sect-5.3" numbered="true" toc="default">
        <name>Intent Scope</name>
        <t>
   Intents are used to manage the behaviour behavior of the networks they are
   applied to and all intents are applied within a specific scope, such
   as:</t>

	<t><list style="symbols"><t>Connectivity
        <ul spacing="normal">
          <li>connectivity scope, if the intent creates or modifies a connection.</t>

	<t>Security/privacy connection</li>
          <li>security/privacy scope, if the intent specifies the security
     characteristics of the network, customers, or end-users.</t>

	<t>Application end users</li>
          <li>application scope, when the intent specifies the applications to
     be affected by the intent request.</t>

	<t>QoS request</li>
          <li>QoS scope, when the intent specifies the QoS characteristics of
     the network.</t>

	</list>
	</t> network</li>
        </ul>
        <t>
   These intent scopes are expendable through the methodology presented
   in section 6.1. .</t> <xref target="sect-6.1"/>.</t>
      </section>
      <section title="Intent anchor="sect-5.4" numbered="true" toc="default">
        <name>Intent Network Scope" anchor="sect-5.4"><t> Scope</name>
        <t>
   Regardless on of the intent user type, their intent request is affecting affects
   the network, or network components, which are representing the intent
   targets.</t>
        <t>
   Thus, the intent network scope, or policy target as known in the area of
   declarative policy, can represent VNFs or PNFs, physical network
   elements, campus networks, SD-WAN networks, radio access networks, SD-WANs, RANs,
   cloud edge, edges, cloud core, branch, cores, branches, etc.</t>
      </section>
      <section title="Intent Abstraction" anchor="sect-5.5"><t> anchor="sect-5.5" numbered="true" toc="default">
        <name>Intent Abstraction</name>
        <t>
   Intent can be classified by whether it is necessary to feedback feed back
   technical network information or non-technical information to the
   intent user after the intent is executed. As well, intent abstraction
   covers the level of technical details in the intent itself.</t>

	<t><list style="symbols"><t>For non-technical
        <ul spacing="normal">
          <li>Non-technical intent users, they users do not care how the intent is
     executed, or
     executed nor do they care about the details of the network. As a result, they do not
     need to know the configuration information of the underlying
     network. They only focus on whether the intent execution result
     achieves the goal, goal and the execution effect such as the quality of
     completion and the length of execution. In this scenario, we refer
     to an abstraction without technical feedback.</t>

	<t>For administrators, feedback.</li>
          <li>Administrators, such as network administrators, they perform
     intents, such as allocating network resources, selecting
     transmission paths, handling network failures, etc. They require
     multiple feedback indicators for network resource conditions,
     congestion conditions, fault conditions, etc. etc., after execution. In
     this case, we refer to an abstraction with technical feedback.</t>

	</list>
	</t> feedback.</li>
        </ul>
        <t>
   As per intent the definition of "intent" provided in <xref target="I-D.irtf-nmrg-ibn-concepts-definitions"/>, target="RFC9315" format="default"/>, lower-level intents are not
   considered to qualify as intents. However, we kept this classification to
   identify any PoCs/Demos/Use PoCs / Demos / Use Cases that still either require or implement
   a lower level of abstraction for intents.</t>
      </section>

      <section title="Intent Life-cycle" anchor="sect-5.6"><t> anchor="sect-5.6" numbered="true" toc="default">
        <name>Intent Life Cycle</name>
        <t>
   Intents can be classified into transient and persistent intents:</t>

	<t><list style="symbols"><t>If the
        <dl spacing="normal">
          <dt>Transient:</dt><dd>The intent is transient, it has no life-cycle management.  As
     soon as the specified operation is successfully carried out, the
     intent is finished, finished and can no longer affect the target object.</t>

	<t>If the object.</dd>
          <dt>Persistent:</dt><dd>The intent is persistent, it has life-cycle management.  Once
     the intent is successfully activated and deployed, the system will
     keep all relevant intents active until they are deactivated or
     removed.</t>

	</list>
	</t>
     removed.</dd>
        </dl>
      </section>
      <section title="Autonomous anchor="sect-5.7" numbered="true" toc="default">
        <name>Autonomous Driving Levels" anchor="sect-5.7"><t> Levels</name>
        <t>
   In different phases of the autonomous driving network [TMF-auto], <xref
   target="TMF-AUTO" format="default"/>, the intents are different. Depending
   on the Autonomous Network Level of the overall solution, we may have
   different intent requirements and types. For example, at lower level levels, the
   customer intent is
   automatically is:</t>
   <ul spacing="normal">
     <li>automatically converted to configuration policies only, only
   while at the higher levels the customer intent is covering levels,</li>
   <li>covering the full life cycle, it
   is converted
   cycle,</li>
   <li>converted to both configuration and monitoring policies and is
   self-assured policies, and</li>
   <li> self assured using AI.</t> AI.</li>
   </ul>
        <t>
   A typical example
   Typical examples of autonomous driving network networks level 0 to 5 are
   listed as
   shown below.</t>

	<t><list style="symbols"><t>Level

   <dl newline="true">

<dt>Level 0 - Traditional manual network: O&amp;M
</dt>
<dd><t>O&amp;M personnel manually control the network and obtain network alarms
and logs. - logs.</t><t>- No intent</t>

	<t>Level
</dd>

<dt>Level 1 - Partially automated network: Automated
</dt>
<dd><t>Automated scripts are used to automate service provisioning, network
deployment, and maintenance. Shallow The network provides shallow perception of the
network status and decision making suggestions of machine; - suggestions.
</t><t>- No intent</t>

	<t>Level
</dd>

<dt>Level 2 - Automated network: Automation
</dt>

<dd><t>

 This entails the automation of most service provisioning, network deployment,
 and maintenance of a comprehensive perception of network status and local
 machine
     decision making; - decision-making.</t> <t>- simple intent on service provisioning</t>

	<t>Level
</dd>

<dt>Level 3 - Self-optimization network: Deep
</dt>
<dd><t> This entails a deep awareness of network status and automatic network
control, meeting requirements of intent users of the network. - network.</t> <t>- Intent based on
  network status cognition</t>

	<t>Level
</dd>

<dt>Level 4 - Partial autonomous network: In
</dt>
<dd><t>In a limited environment, people do not need to participate in
decision-making and networks can adjust itself. - themselves.</t> <t>- Intent based on limited AI</t>

	<t>Level
</dd>

<dt>Level 5 - Autonomous network: In
</dt>
<dd><t>In different network environments and network conditions, the network can
automatically adapt to and adjust to meet people's intentions. - intentions.</t> <t>- Intent based on AI</t>

	</list>
	</t>
</dd>

</dl>

</section>
    </section>
    <section title="Intent Classification" anchor="sect-6"><t> anchor="sect-6" numbered="true" toc="default">
      <name>Intent Classification</name>
      <t>
   This section proposes an approach to intent classification approach that may help
   to classify mainstream intent related intent-related demos/tools.</t>
      <t>
   The three classifications in this document have been proposed from
   scratch, following
   scratch (following the methodology presented, presented) through three
   iterations: one for a carrier network intent solution, one for a DC
   intent solution, and one for an enterprise intent solution. For each
   intent solution, we identified the specific intent users and intent
   types.  Then, we further identified intent scope, network scope,
   abstractions, and life-cycle requirements.</t>
      <t>
   These classifications and the generated tables can be easily
   extended.

   For example, for the DC intent solution, a new category "resource scope" is
   identified, i.e. resource scope, and the classification table has
   been extended accordingly.</t>
      <t>
   In the future, as new scenarios, applications, and domains are
   emerging, emerge, new classifications and taxonomies can be identified,
   following the proposed methodology.</t>
      <t>
   The intent classifications have been documented to the best of our
   knowledge at this point in time. the time of writing. Additional classifications will most
   probably see the
   likely come to light in the future.</t>
      <t>
   The output of the intent classification is the intent taxonomy
   introduced in the next sections.</t> subsections of this section.</t>
   <t>
   Thus, this section first introduces  the subsections of <xref target="sect-6" format="default"/> introduce the proposed intent
   classification methodology, followed by the consolidated intent taxonomy
   for three intent solutions, and then by the concrete examples of intent
   classifications for three different intent solutions (e.g. (e.g., carrier
   network, data center, and enterprise) that were derived using the
   proposed methodology and then can be filled in for PoCs, demos,
   research projects projects, or future drafts.</t> documents.</t>
      <section title="Intent anchor="sect-6.1" numbered="true" toc="default">
        <name>Intent Classification Methodology" anchor="sect-6.1"><t> Methodology</name>
        <t>
   This section describes the methodology used to derive the initial
   classification proposed in the draft. document. The proposed methodology can be
   used to create new intent classifications from scratch, scratch by analysing analyzing
   the solution knowledge. As well, the methodology can be used to
   update existing classification tables by adding or removing different
   solutions, intent users users, or intent types in order to cater for to future
   scenarios, applications applications, or domains.</t>
        <figure title="- Intent anchor="fig-1">
          <name>Intent Classification Methodology" anchor="fig-1"><artwork><![CDATA[ Methodology</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[
          +------------------------------------------+
          |Solution Knowledge (requirements,         |
          |use cases, technologies, network, intent  |
          |users, intent requirements)               |
          +----------------+-------------------------+
                           | Input             Rx=Read
                           |                   Ux=Update (Add/Remove)
                  +--------V--------+
                  |1.Identify Intent|
                  |  Solution       +------------+
                  |                 |            |
                  +---------^-+-----+            |
                         R1 | | U1               |
+---------------+ U8        | |    R2         +--v----------------+
|8.Identify New +---------+ | |   +-----------> 2.Identify        |
|  Categories   | R8      | | |   | U2        |   Intent          |
|               <-------- | | |   | +---------+   User Types      |
+--------^------+       | | | |   | |         +-------|-----------+
         |              | | | |   | |                 |
         |             ++-+-v-v---+-v-+               |
+--------+------+ U7   |              | R3     +------v------------+
|7.Identify     +------>   Intent     +--------> 3.Identify        |
|  Life-cycle  Life-Cycle   | R7   |Classification| U3     |   Type            |
|  Requirements <------+              <--------+   of Intent       |
+--------^------+      +^--^-+--^-+---+        +------|------------+
         |              || | |  | |                   |
         |              || | |  | |                   |
+--------+-----+        || | |  | | R4        +-------v-----------+
|6.Identify    | U6     || | |  | +-----------> 4.Identify        |
|  Abstractions+---------| | |  |   U4        |   Intent          |
|              <---------+ | |  +-------------+   Scope           |
+-------^------+ R6        | |                +-------+-----------+
        |                  | |                        |
        |               U5 | |R5                      |
        |          +-------+-v--------+               |
        |          |5.Identify Network|               |
        +----------+  Scope           <---------------+
                   +------------------+
]]></artwork>
        </figure>
        <t>
   The intent classification workflow starts from the solution
   knowledge, which can provide information on requirements, use cases,
   technologies used, network properties, intent users that define and
   issue the intent request, and requirements. The following, following defines
   the steps to classify an intent:

   <list style="numbers">

	<t>
   The

        </t>

        <ol spacing="normal" type="1"><li>
   Receive the information provided in the solution knowledge is given as
   input for identifying the intent solution (e.g. (e.g., carrier, enterprise,
   and data center). Intent solutions are reviewed against the existing
   classification and they can either be used if present or added if not
   there or removed
   there; if not needed, they can be removed from the classification. (R1-U1).</t>

	<t> classification (R1-U1).</li>
          <li>
   Identify the intent user types (e.g. (e.g., customer, network operators, service
   operators, etc.), review etc.).  Review the existing intent classification and classification. Then use the intent
   user type if present, present; add it if it is not there or remove it if not needed (R2-U2).</t>

	<t>
   (R2-U2).</li>
          <li>
   Identify the types of intent (e.g. (e.g., network intent, customer
   service intent) and then review intent).  Review the existing classification and
   use/add/remove
   then use, add, or remove the intent type (R3-U3).</t>

	<t> (R3-U3).</li>
          <li>
   Identify the intent scopes (e.g. (e.g., connectivity, application) based
   on the solution knowledge and then knowledge.  Then, review the existing classification and
   use/add/remove classification.
   Use, add, or remove the identified intent scope (R4-U4).</t>

	<t> (R4-U4).</li>
          <li>
   Identify the network scopes (e.g. (e.g., campus, radio access) and then access).  Then,
   review the existing classification and either use it classification.  Either use, add, or add/remove remove the
   identified network scope (R5-U5).</t>

	<t> (R5-U5).</li>
          <li>
   Identify the abstractions (e.g. (e.g., technical, non-technical) and
   then non-technical).
   Then, review the existing classification and use/add/remove either use, add, or remove the
   abstractions (R6-U6).</t>

	<t> (R6-U6).</li>
          <li>
   Identify the life-cycle requirements (e.g. (e.g., persistent, transient)
   and then transient).
   Then, review the existing classification and use/add/remove classification.  Either use, add, or remove the
   life-cycle requirements (R7-U7).</t>

	<t> (R7-U7).</li>
   <li>

Identify any new categories categories. Use and use/add add the newly identified categories. New
categories can be identified as new domains or applications are emerging, emerge or as new
areas of concern (e.g. (e.g., privacy, compliance) might arise, which arise that are not listed in the
current
   methodology.</t>

   </list>
	</t> methodology.</li>
        </ol>
      </section>

      <section title="Intent Taxonomy" anchor="sect-6.2"><t> anchor="sect-6.2" numbered="true" toc="default">
        <name>Intent Taxonomy</name>
        <t>
   The following taxonomy describes the various intent solutions, intent
   user types, intent types, intent scopes, network scopes, abstractions
   and life-cycle abstractions,
   and life cycles.  The taxonomy represents the output of the intent classification
   tables for each of the solutions addressed (i.e. (i.e., carrier, data
   center, and enterprise solutions).</t>
        <t>
   The intent scope categories in Figure 2 <xref target="fig-2"/> are shared among the carrier,
   DC, and enterprise solutions. The abbreviations (Cx) in sections
   6.3.2. 6.4.2. Sections
   <xref target="sect-6.3.2" format="counter"/> and <xref target="sect-6.4.2" format="counter"/> are introduced with the scope of fitting as column
	title in the following tables.</t>

        <figure title="- Intent Taxonomy" anchor="fig-2"><artwork><![CDATA[ anchor="fig-2">
          <name>Intent Taxonomy</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[
                                +--------------------------------+
                            +-->|Carrier  Enterprise  Data Center|
                            |   +--------------------------------+
                            |   +--------------------------------+
                            |   |Customer/Subscriber/End-User   |Customer/Subscriber/End User    |
              +----------+  |   |Network or Service Operator     |
            +>+Solutions
            +>+Solution  +--+   |Application Developer           |
            | +----------+   +->|Enterprise Administrator        |
            |                |  |Cloud Administrator             |
            | +----------+   |  |Underlay Network Administrator  |
            +>+Intent    +---+  +--------------------------------+
            | |User      |      +--------------------------------+
            | |Types |Type      |      |Customer Service Intent         |
            | +----------+      |Strategy Intent                 |
            | +----------+      |Network Service Intent          |
            +>+Intent    +----->|Underlay Network Service Intent |
   +------+ | |Type      |      |Network Intent                  |
   |Intent+-+ +----------+      |Underlay Network Intent         |
   +------+ |                   |Operational Task Intent         |
            | +----------+      |Cloud Management Intent         |
            +>+Intent    +---+  |Cloud Resource Management Intent|
            | |Scope     |   |  +--------------------------------+
            | +----------+   |  +--------------------------------+
            |                +->|Connectivity   Application  QoS |
            | +----------+      |Security/Privacy Storage Compute|
            +>+Network   +---+  +--------------------------------+
            | |Scope     |   |  +--------------------------------+
            | +----------+   |  |Radio Access      Branch        |
            |                +->|Transport Access  SD-WAN        |
            | +----------+      |Transport Aggr.   VNF      PNF  |
            +>+Abstrac
            +>+Abstrac-  +----+ |Transport Core    Physical      |
            | |tion      |    | |Cloud Edge        Logical       |
            | +----------+    | |Cloud Core        Campus        |
            | +----------+    | +--------------------------------+
            +>+Life      |    | +--------------------------------+
              |cycle
              |Cycle     +--+ +>|Technical         Non-Technical |
              +----------+  |   +--------------------------------+
                            |   +--------------------------------+
                            +-->|Persistent        Transient     |
                                +--------------------------------+
]]></artwork>
        </figure>
      </section>
      <section title="Intent anchor="sect-6.3" numbered="true" toc="default">
        <name>Intent Classification for Carrier Solution" anchor="sect-6.3"><section title="Intent Solution</name>
        <section anchor="sect-6.3.1" numbered="true" toc="default">
          <name>Intent Users and Intent Types" anchor="sect-6.3.1"><t> Types</name>
          <t>
   This section addresses step steps 1, 2, and 3 from Figure 1 and the <xref target="fig-1"/>.  The
   following table describes the intent users in carrier solutions and
   intent types with their descriptions for different intent users.</t>

<figure><artwork><![CDATA[
+-------------+-------------+---------------------------------------+
| Intent User | Intent Type |      Intent

<table anchor="intent" align="center">
<name>Intent Classification for Carrier Solution</name>
<thead>
  <tr>
    <th>Intent User</th>
    <th>Intent Type</th>
    <th>Intent Type Description          |
+-------------------------------------------------------------------+
| Customer/   |Customer     |Customer self-service Description</th>
  </tr>
</thead>

<tbody>
  <tr>
    <td rowspan="2" colspan="1">Customer/Subscriber</td>
    <td>Customer Service Intent</td>
    <td><t>Customer self service with SLA and     |
| Subscriber  |Service      |value added service                    |
|             |Intent       |Example: value-added service.</t>
    <t>Example: Always maintain a high quality  |
|             |             |of of service and high bandwidth
    for gold |
|             |             |level gold-level subscribers.                     |
|             |             |Operational </t>
    <t>Operation statement: Measure the     |
|             |             |network network congestion status, give        |
|             |             |different
    different adaptive parameters to       |
|             |             |stations stations of different priority, thus in|
|             |             |heavy priority;
    thus, in a heavy load situation, make the         |
|             |             |bandwidth bandwidth of the
    high-priority         |
|             |             |customers customers guaranteed.                  |
|             |             |At At the same time time, ensure the
    overall    |
|             |             |utilization utilization of system, the system and  improve         |
|             |             |the the overall throughput of the system.  |
|             +-----------------------------------------------------+
|             |Strategy     |Customer
    system.</t></td>
  </tr>
  <tr>
      <td>Strategy Intent</td>
      <td><t>Customer designs models and policy     |
|             |Intent       |intents intents to be used by
      customer service |
|             |             |intents.                               |
|             |             |Example: intents.</t>
      <t>Example: Request reliable service      |
|             |             |during during peak traffic periods for apps   |
|             |             |of type video.                         |
+-------------------------------------------------------------------+
|Network      |Network      |Service
      video-type apps.</t></td>
  </tr>

  <tr>
    <td rowspan="4">Network Operator</td>
    <td>Network Service Intent</td>
    <td> <t>Service provided by the network service    |
|Operator     |Service      |operator operator to the customer               |
|             |Intent       |(e.g.
    (e.g., the service operator)            |
|             |             |Example: operator).</t>
     <t>Example: Request network service with  |
|             |             |delay delay guarantee for
    access customer A. |
|             +-------------+---------------------------------------+
|             |Network      |Network A.</t></td>
  </tr>
  <tr>
    <td>Network Intent</td>
    <td> <t>Network operator requests network-wide |
|             |Intent       |(service (service underlay or other network-wide|
|             |             |configuration)
    network-wide configuration) or network resource     |
|             |             |configurations network-resource configurations
    (switches, routers,     |
|             |             |routing, routing, or policies). Includes           |
|             |             |connectivity, connectivity, routing, QoS,
    security,  |
|             |             |application application policies, traffic steering |
|             |             |policies, configuration policies,      |
|             |             |monitoring policies, alarm
    generation  |
|             |             |for for non-compliance, auto-recovery, etc.|
|             |             |Example: etc.</t>
     <t>Example: Request high priority queueing|
|             |             |for queuing for traffic of class A.                |
|             +-----------------------------------------------------+
|             |Operational  |Network A.</t></td>
  </tr>
  <tr>
    <td>Operational Task Intent</td>
    <td> <t>Network operator requests execution of |
|             |Task         |any any automated task other than
    network  |
|             |Intent       |service service intent and network intent      |
|             |             |(e.g. (e.g., network migration, server        |
|             |             |replacements,
replacements, device replacements,     |
|             |             |network or network software upgrades).            |
|             |             |Example: upgrades).</t>
 <t>Example: Request migration of all      |
|             |             |services services in network N to backup path P.|
|             +-----------------------------------------------------+
|             |Strategy     |Network P.</t></td>
  </tr>

  <tr>
    <td>Strategy Intent</td>
    <td> <t>Network operator designs models, policy|
|             |Intent       |intents policy intents, and workflows to be used
    by    |
|             |             |network network service Intents, intents, network       |
|             |             |intents intents, and operational task intents.  |
|             |             |Workflows
    Workflows can automate any tasks that  |
|             |             |network the network operator often performed performs in    |
|             |             |addition
    addition to network service intents and|
|             |             |network intents                        |
|             |             |Example: and network intents.</t>  <t>Example: Ensure the
    load on any link in|
|             |             |the in the network is not higher than 50%.    |
+-------------+-------------+---------------------------------------+
+-------------+-------------+---------------------------------------+
| Service     | Customer    | 50%.</t></td>
  </tr>
  <tr>
    <td rowspan="4">Service Operator</td>
    <td>Customer Service Intent</td>
    <td> <t>Service operator's customer orders,   |
| Operator    | Service     |
    customer service / SLA                |
|             | Intent      | Example: service, or SLA.</t>

     <t>Example: Provide service S with       |
|             |             |
    guaranteed bandwidth for customer A.  |
|             +-----------------------------------------------------+
|             | Network     | A.</t></td>
  </tr>
  <tr>
    <td>Network Service Intent</td>
    <td> <t>Service operator's network orders /   |
|             | Service     |
    network SLA                           |
|             | Intent      | Example: SLA.</t>
     <t>Example: Provide network guarantees in|
|             |             | in
    terms of security, low latency latency, and    |
|             |             |
    high bandwidth                        |
|             +-----------------------------------------------------+
|             | Operational | Service bandwidth.</t></td>
  </tr>
  <tr>
    <td>Operational Task Intent</td>
    <td> <t>Service operator requests execution of|
|             | Task        | of
    any automated task other than         |
|             | Intent      |
    customer service intent and network   |
|             |             |
    service intent                        |
|             |             | Example: intent.</t>
     <t>Example: Update service operator      |
|             |             |
    portal platforms and their software   |
|             |             |
    regularly. Move services from network |
|             |             |
    operator 1 to network operator 2.     |
|             +-----------------------------------------------------+
|             | Strategy    | Service 2.</t> </td>
  </tr>
  <tr>
    <td>Strategy Intent</td>
    <td> <t>Service operator designs models,      |
|             | Intent      |
    policy intents intents, and workflows to be    |
|             |             |
    used by customer service intents,     |
|             |             |
    network service intents intents, and           |
|             |             |
    operational task intents. Workflows   |
|             |             |
    can automate any tasks task that the service   |
|             |             |
    operator often performed performs in addition  |
|             |             |
    to network service intents and network|
|             |             | intents.                              |
|             |             | Example: network
    intents.</t>
     <t>Example: Request network service      |
|             |             |
    guarantee to avoid network congestion |
|             |             |
    during special periods                |
|             |             |
    such as black Friday, Black Friday and Christmas.  |
+-------------+-------------+---------------------------------------+
| Application | Customer    | Customer Christmas.</t> </td>
  </tr>
  <tr>
    <td rowspan="5">Application Developer</td>
    <td>Customer Service Intent</td>
    <td> <t>Customer service intent API provided  |
| Developer   | Service     |
    to the application developers         |
|             | Intent      | Example: developers.</t>
     <t>Example: API to request network to    |
|             |             |
    watch HD video 4K/8K.                 |
|             +-----------------------------------------------------+
|             | Network     | Network (4K/8K).</t></td>
  </tr>
  <tr>
    <td>Network Service Intent</td>
    <td> <t>Network service intent API provided to|
|             | Service     | to
    the application developers            |
|             | Intent      | Example:API developers.</t>
     <t>Example: API to request network service|
|             |             | , monitoring service,
    monitoring, and traffic grooming.    |
|             +-----------------------------------------------------+
|             | Network     | Network grooming.</t></td>
  </tr>
  <tr>
    <td>Network Intent</td>
    <td> <t>Network intent API provided to the    |
|             | Intent      |
    application developers                |
|             |             | Example: developers.</t>
     <t>Example: API to request network       |
|             |             | resources configuration.              |
|             +-----------------------------------------------------+
|             | Operational | Operational
    resource configurations.</t></td>
  </tr>
  <tr>
    <td>Operational Task Intent</td>
    <td> <t>Operational task intent API provided  |
|             | Task        |
    to the application developers. This is|
|             | Intent      | is
    for the trusted internal operator /   |
|             |             | service providers / customer DevOps   |
|             |             | Example: DevOps.</t>
     <t>Example: API to request server        |
|             |             | migrations.                           |
|             +-----------------------------------------------------+
|             | Strategy    | Application
    migrations.</t></td>
  </tr>
  <tr>
    <td>Strategy Intent</td>
    <td> <t>Application developer designs models, |
|             | Intent      | policy
    policy, and workflows to be used by    |
|             |             |
    customer service intents, network     |
|             |             |
    service intents intents, and operational       |
|             |             |
    task intents. This is for the trusted |
|             |             |
    internal operator/service provider/   |
|             |             | operator / service provider / customer DevOps                       |
|             |             | Example: DevOps.</t>
     <t>Example: API to design network load   |
|             |             | balancing load-balancing strategies during peak times|
+-------------+-------------+---------------------------------------+

         Table 2 - Intent Classification for Carrier Solution
]]></artwork>
	</figure> times.</t></td>
  </tr>
</tbody>
</table>

        </section>
        <section title="Intent Categories" anchor="sect-6.3.2"><t> anchor="sect-6.3.2" numbered="true" toc="default">
          <name>Intent Categories</name>

	  <t>
   This subsection addresses step steps 4 to 7 from Figure 1, and the <xref target="fig-1"/>. The
   following are the proposed categories:

   <list style="symbols">

     <t>Intent

          </t>
	  <dl>

	    <dt>Intent Scope: C1=Connectivity,
	    </dt>
	    <dd>C1=Connectivity, C2=Security/Privacy, C3=Application, C4=QoS</t>

     <t>Network C4=QoS
	    </dd>
	    	    <dt>Network Scope:

     <list style="symbols">

       <t>Network
	    </dt>
	    <dd>
	      <dl>
		<dt>
		</dt>
		<dd>
		</dd>
		<dt>Network Domain: C1=Radio
		</dt>
		<dd>C1=Radio Access, C2=Transport Access, C3=Transport Aggregation, C4=Transport Core, C5=Cloud Edge, C6=Cloud Core)</t>

       <t>Network Core
		</dd>

				<dt>Network Function (NF) Scope: C1=VNFs, C2=PNFs</t>

     </list></t>

       <t>Abstraction
		</dt>
		<dd>C1=VNFs, C2=PNFs
		</dd>

	    </dl>
	    </dd>
	    	    <dt>Abstraction (ABS): C1=Technical
	    </dt>
	    <dd>C1=Technical (with technical feedback), C2=Non-technical (without technical feedback) see section 5.2. .</t>

       <t>Life-cycle (see <xref target="sect-5.2"/>).
	    </dd>

<dt>Life cycle (L-C): C1=Persistent
</dt>
<dd>C1=Persistent (full life-cycle), life cycle), C2=Transient (short lived)</t>

      </list></t> lived)

</dd>
	  </dl>

</section>
        <section title="Intent anchor="sect-6.3.3" numbered="true" toc="default">
          <name>Intent Classification Example" anchor="sect-6.3.3"><t> Example</name>

          <t>
	    This section depicts contains an example on of how the methodology described in
   section 6.1.
   <xref target="sect-6.1"/> can be used in order to classify intents introduced in the 'A "A
   Multi-Level Approach to IBN' IBN" PoC demonstration [POC-IBN]. <xref target="POC-IBN"
   format="default"/>. This PoC is led by academics carrying out research in the
   area of SDN/NFV SDN/NFV, and the specific problem they are addressing is to apply the application of
   the intent concept at different levels that correspond to different
   stakeholders. For this research work, they considered two types of intents:
   slice intents and service chain intents.</t>
   <t>

   In this PoC [POC-IBN], <xref target="POC-IBN" format="default"/>, a slice intent
   expresses a request for a network slice with two types of components: a set
   of top layer top-layer virtual functions, functions and a set of virtual switches and/or
   routers of L2/L3 VNFs. A service chain intent expressed expresses a request for a
   service operated through a chain of service components running in L4-L7
   virtual functions.</t>
          <t>
   Following the intent classification methodology described
   step-by-step
   step by step in section 6.1. , <xref target="sect-6.1"/>, the following can be derived:</t>

	<t><list style="numbers"><t>The
          <ol spacing="normal" type="1"><li>The intent solution for both intents is carrier network.</t>

	<t>The network.</li>
            <li>The intent user type is network operator for the slice intent, intent and
     service operator for the service chain intent.</t>

	<t>The intent.</li>
            <li>The type of intent, intent is a network service intent for the slice
     intent,
     intent and a customer service intent for the service chain intent.</t>

	<t>The intent.</li>
            <li>The intent scopes are connectivity and application.</t>

	<t>The application.</li>
            <li>The network scope is VNF, cloud edge, and cloud core.</t>

	<t>The core.</li>
            <li>The abstractions are with technical feedback for the slice intent, intent
     and without technical feedback for the service chain intent</t>

	<t>The life-cycle intent.</li>
            <li>The life cycle is persistent.</t>

	</list>
	</t> persistent.</li>
          </ol>
          <t>
   The following table shows how to represent this information in a
   tabular form. The 'X' "X" in the table refers to the slice intent, and intent;
   the 'Y' "Y" in the table refers to the service chain intent. </t>

<figure><artwork><![CDATA[
+---------+---------+-----------+-----+-----------------+-----+-----+
| Intent  | Intent  | Intent    | NF  | Network         | ABS

<figure title="Intent Classification Example for Carrier Solution"><artwork><![CDATA[
+==========+===========+===========+=====+=================+=====+=====+
|Intent    |Intent Type|Intent     |NF   |Network          |ABS  |L-C  |
|User      | User    | Type    | Scope     |Scope| Scope           |Scope      |Scope|Scope            |     |     |
|          |         +-----------+-----+-----------------+-----+-----+           +==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+
|          |           |C1|C2|C3|C4|C1|C2|C1|C2|C3|C4|C5|C6|C1|C2|C1|C2|
+---------+---------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|Customer
+==========+===========+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+
|Customer/ |Customer   |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|/ Sub-   |Service
|Subscriber|Service    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| scriber          |Intent     |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|         +---------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+          +-----------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|          |Strategy   |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|          |Intent     |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
+---------+---------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
+----------+-----------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|Network   |Network    |X |  |X |  |X |  |  |  |  |  |X |  |X |  |X |  |
|Operator  |Service    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|          |Intent     |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|         +---------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+          +-----------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|          |Network    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|          |Intent     |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|         +---------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|         |Operatio-|  |  |  |  |  |          +-----------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|  |  |  |  |  |  |  |  |  |  |
|         |nal Task          |Operational|  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|
|         |Intent   |          |Task Intent|  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|         +---------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+          +-----------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|          |Strategy   |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|          |Intent     |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
+---------+---------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
+----------+-----------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|Service   |Customer   |Y |  |Y |  |Y |  |  |  |  |  |Y |Y |  |Y |Y |  |
|Operator |Service  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|  |Intent     |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|         +---------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+          +-----------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|          |Network    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|          |Service    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|          |Intent     |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|         +---------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+          +-----------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|          |Op Task    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|          |Intent     |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|         +---------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+          +-----------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|          |Strategy   |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|          |Intent     |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
+---------+---------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
+----------+-----------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|App       |Customer   |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|Developer|Intent
|Developer |Intent     |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|         +---------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+          +-----------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|          |Network    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|          |Service    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|          |Intent     |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|         +---------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+          +-----------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|          |Network    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|          |Intent     |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|         +---------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+          +-----------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|          |Op Task    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|          |Intent     |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|         +---------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+          +-----------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|          |Strategy   |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|          |Intent     |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
+---------+---------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+

      Table 3 - Intent Classification Example for Carrier Solution
+----------+-----------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
]]></artwork>
</figure>

</section>
      </section>
      <section title="Intent anchor="sect-6.4" numbered="true" toc="default">
        <name>Intent Classification for Data Center Network Solutions" anchor="sect-6.4"><section title="Intent Solutions</name>
        <section anchor="sect-6.4.1" numbered="true" toc="default">
          <name>Intent Users and Intent Types" anchor="sect-6.4.1"><t> Types</name>

          <t>
   The following table describes the intent users in DC network
   solutions and intent types with their descriptions for different
   intent users.</t>

	<figure><artwork><![CDATA[
+---------------+-------------+-------------------------------------+
| Intent User   | Intent Type |    Intent

<table anchor="intent-classification-DCNS" align="center">
<name>Intent Classification for Data Center Network Solutions</name>
<thead>
  <tr>
    <th>Intent User</th>
    <th>Intent Type</th>
    <th>Intent Type Description          |
+-------------------------------------------------------------------+
| Customer /    | Customer    | Customer self-service Description</th>
  </tr>
</thead>
<tbody>
  <tr>
    <td rowspan="2" colspan="1">Customer/Tenants</td>
    <td>Customer Service</td>
    <td><t>Customer self service via tenant    |
| Tenants       | Service     | portal.                             |
|               |             | Example: portal.</t>
    <t>Example: Request GPU computing and  |
|               |             |
    storage resources to meet 10k video |
|               |             |
    surveillance services.              |
|               +---------------------------------------------------+
|               | Strategy    | This services.</t></td>
  </tr>
  <tr>
    <td>Strategy Intent</td>
    <td><t>This includes models and policy     |
|               | Intent      |
    intents designed by customers/      |
|               |             | tenants customers/tenants to be reused later during   |
|               |             | instantiation.                      |
|               |             | Example:
    instantiation.</t>
    <t>Example: Request dynamic computing  |
|               |             |
    and storage resources of the service|
|               |             | service
    in special and daily times.         |
|               |             |                                     |
+-------------------------------------------------------------------+
|               | Cloud       | Configuration times.</t></td>
  </tr>
  <tr>
    <td rowspan="4" colspan="1">Cloud Administrator</td>
    <td>Cloud Management Intent</td>

    <td><t>Configuration of VMs, DB Servers,   |
| Cloud         | Management  | app servers, connectivity,          |
| Administrator | Intent      | and communication between servers and VMs.          |
|               |             | Example:
  </t>
    <t>Example: Request connectivity       |
|               |             |
    between VMs A,B,and A, B, and C in network N1.|
|               +---------------------------------------------------+
|               | Cloud       | Policy-driven self-configuration and|
|               | N1.</t></td>
  </tr>
  <tr>
    <td>Cloud Resource    | and recovery / optimization         |
|               | Management  | Example: Intent</td>
    <td><t>Policy-driven self configuration
    and recovery/optimization.</t>
    <t>Example: Request automatic life     |
|               | Intent      |-cycle life-cycle
    management of VM cloud        |
|               |             | resources.                          |
|               +---------------------------------------------------+
|               | Operational | Cloud resources.</t></td>
  </tr>
  <tr>
    <td>Operational Task Intent</td>
    <td><t>Cloud administrator requests        |
|               | Task Intent |
    execution of any automated task     |
|               |             |
    other than cloud management         |
|               |             |
    intents and cloud resource          |
|               |             |
    management intents.                 |
|               |             | Example: </t>
    <t>Example: Request upgrade operating  |
|               |             |
    system to version X on all VMs      |
|               |             |
    in network N1.                      |
|               |             |Operational </t>
    <t>Operational statement: an An intent to  |
|               |             |update
    update a system might reconfigure the|
|               |             |system the
    system topology (connect to a service|
|               |             |and service
    and to peers), exchange data (update |
|               |             |the
    the content), and uphold a certain   |
|               |             |QoE
    QoE level (allocate sufficient       |
|               |             |network
    network resources). The network,     |
|               |             |thus, Thus, the network
    carries out the necessary      |
|               |             |configuration
    configuration to best serve such an  |
|               |             |intent; e.g.
    intent, e.g., setting up direct       |
|               |             |connections
    connections between terminals, terminals and   |
|               |             |allocating
    allocating fair shares of router     |
|               |             |queues
    queues considering other network     |
|               |             |services.
|               +---------------------------------------------------+
|               | Strategy    | Cloud services.</t></td>
  </tr>
  <tr>
    <td>Strategy Intent</td>
    <td><t>Cloud administrator designs models, |
|               | Intent      |
    policy intents intents, and workflows to be  |
|               |             |
    used by other intents. Automate any |
|               |             |
    tasks that administrator often      |
|               |             | performs,
    performs in addition to life-cycle |
|               |             | life cycle
    of cloud management intents and     |
|               |             |
    cloud management resource intents.  |
|               |             | Example: intents.</t>
    <t>Example: In case of emergency,      |
|               |             |
    automatically migrate all cloud     |
|               |             |
    resources to DC2.                   |
+---------------+---------------------------------------------------+
| Underlay      | Underlay    | DC2.</t></td>
  </tr>
  <tr>
    <td rowspan="4" colspan="1">Underlay Network Administrator</td>
    <td>Underlay Network Service Intent</td>
    <td><t>Service created and provided by     |
| Network       | Network     |
    the underlay network administrator. |
| Administrator | Service     | Example: administrator.</t>
    <t>Example: Request underlay service   |
|               | Intent      |
    between DC1 and DC2 with            |
|               |             | bandwidth B.                        |
|               +---------------------------------------------------+
|               | Underlay    | Underlay B.</t></td>
  </tr>
  <tr>
    <td>Underlay Network Intent</td>
    <td><t>Underlay network administrator      |
|               | Network     |
    requests some DCN-wide underlay     |
|               | Intent      |
    network configuration or network    |
|               |             |
    resource configurations.            |
|               |             | Example: configurations.</t>
    <t>Example: Establish and allocate     |
|               |             |
    DHCP address pool.                  |
|               +---------------------------------------------------+
|               | Operational | Underlay pool.</t></td>
  </tr>
  <tr>
    <td>Operational Task Intent</td>
    <td><t>Underlay network administrator      |
|               | Task Intent |
    requests execution of the any       |
|               |             |
    automated task other than underlay  |
|               |             |
    network service and resource        |
|               |             | intent.                             |
|               |             | Example: intent.</t>
    <t>Example: Request automatic rapid    |
|               |             |
    detection of device failures and    |
|               |             |
    pre-alarm correlation.              |
|               +---------------------------------------------------+
|               | Strategy    | Underlay correlation.</t></td>
  </tr>
  <tr>
    <td>Strategy Intent</td>
    <td><t>Underlay network administrator      |
|               | Intent      |
    designs models, policy intents &    |
|               |             | intents, and
    workflows to be used by other       |
|               |             |
    intents. Automate any tasks that    |
|               |             |
    the administrator often performs.       |
|               |             | Example: performs.</t>
    <t>Example: For all traffic flows      |
|               |             |
    that need NFV service chaining,     |
|               |             |
    restrict the maximum load of any    |
|               |             |
    VNF node/container below 50% and    |
|               |             |
    the maximum load of any network     |
|               |             |
    link below 70%.                     |
+-------------------------------------------------------------------+
|               | Cloud       | Cloud 70%.</t></td>
  </tr>
  <tr>
    <td rowspan="6" colspan="1">Application Developer</td>
    <td>Cloud Management Intent</td>
    <td><t>Cloud management intent API         |
|               | Management  |
    provided to the application         |
|               | Intent      | developers.                         |
|               |             | Example: developers.</t>
    <t>Example: API to request             |
|               |             | configuration of VMs, VMs or DB Servers.|
| Application   +---------------------------------------------------+
| Developer     | Cloud       | Cloud Servers.
</t></td>
  </tr>

  <tr>
    <td>Cloud Resource Management Intent</td>
    <td><t>Cloud resource management intent    |
|               | Resource    |
    API provided to the application     |
|               | Management  | developers.                         |
|               | Intent      | Example: developers.</t>
    <t>Example:
    API to request automatic   |
|               |             |
    life-cycle management of cloud      |
|               |             | resources.                          |
|               +---------------------------------------------------+
|               | Underlay    | Underlay resources.</t></td>
  </tr>
  <tr>
    <td>Underlay Network Service Intent</td>
    <td><t>Underlay network service API        |
|               | Network     |
    provided to the application         |
|               | Service     |
    developers.                         |
|               | Intent      | Example: </t>
    <t>Example: API to request real-time   |
|               |             |
    monitoring of device condition.     |
|               +---------------------------------------------------+
|               | Underlay    | Underlay condition.</t></td>
  </tr>
  <tr>
    <td>Underlay Network Intent</td>
    <td><t>Underlay network resource API       |
|               | Network     |
    provided to the application         |
|               | Intent      | developers.                         |
|               |             | Example: developers.</t>
    <t>Example: API to request dynamic     |
|               |             |
    management of IPv4 address pool     |
|               |             | resources.                          |
|               |             |                                     |
|               +---------------------------------------------------+
|               | Operational | Operational resources.</t></td>
  </tr>
  <tr>
    <td>Operational Task Intent</td>
    <td><t>Operational task intent API         |
|               | Task Intent |
    provided to the trusted             |
|               |             |
    application developer (internal     |
|               |             | DevOps).                            |
|               |             | Example: DevOps).</t>
    <t>Example: API to request automatic   |
|               |             |
    rapid detection of device failures  |
|               |             |
    and pre-alarm correlation           |
|               |             |                                     |
|               +---------------------------------------------------+
|               | Strategy    | Application correlation.</t></td>
  </tr>
  <tr>
    <td>Strategy Intent</td>
    <td><t>Application developer designs       |
|               | Intent      |
    models, policy intents intents, and          |
|               |             |
    building blocks to be used by       |
|               |             |
    other intents. This is for the      |
|               |             |
    trusted internal DCN DevOps.        |
|               |             | Example: </t>
    <t>Example: API to request load        |
|               |             | balancing thresholds.               |
+---------------+-------------+-------------------------------------+

   Table 4 - Intent Classification for Data Center Network Solutions
]]></artwork>
	</figure> load-balancing thresholds.</t></td>
  </tr>
</tbody>
</table>

        </section>
        <section title="Intent Categories" anchor="sect-6.4.2"><t> anchor="sect-6.4.2" numbered="true" toc="default">
          <name>Intent Categories</name>
          <t>
   The following are the proposed categories:

   <list style="symbols">

     <t>Intent

          </t>
	  <dl>

<dt>Intent Scope: C1=Connectivity,
</dt>
<dd>C1=Connectivity, C2=Security/Privacy, C3=Application,
     C4=QoS C5=Storage C6=Compute</t>

     <t>Network C4=QoS, C5=Storage, C6=Compute
</dd>

<dt>Network Scope

     <list style="symbols">

       <t>Network
</dt>
<dd>
</dd>
<dt>
</dt>
<dd>
  <dl>
    <dt>Network Domain: DC Network</t>

       <t>DCN
    </dt>
    <dd>DC Network
    </dd>
        <dt>DCN Network (DCN Net) Scope: C1=Logical, C2=Physical</t>

       <t>DCN
    </dt>
    <dd>C1=Logical, C2=Physical
    </dd>
    <dt>DCN Resource (DCN Res) Scope: C1=Virtual, C2=Physical</t>
     </list></t>

     <t>Abstraction
    </dt>
    <dd>C1=Virtual, C2=Physical
    </dd>
  </dl>
</dd>

<dt>Abstraction (ABS): C1=Technical
</dt>
<dd>C1=Technical (with technical feedback), C2=Non-technical (without
technical feedback), see section 5.2.</t>

     <t>Life-cycle feedback) (see <xref target="sect-5.2"/>).
</dd>

<dt>Life cycle (L-C): C1=Persistent
</dt>
<dd>C1=Persistent (full life-cycle), life cycle), C2=Transient (short lived)</t>
     </list></t> lived)
</dd>

	  </dl>

</section>
        <section title="Intent anchor="sect-6.4.3" numbered="true" toc="default">
          <name>Intent Classification Example" anchor="sect-6.4.3"><t> Example</name>
          <t>
   This section depicts an example on how the methodology described in
   section 6.1. <xref target="sect-6.1"/>
   can be used by the research community to classify intents. As
   mentioned in 6.3.3. <xref target="sect-6.3.3"/>, a successful use of the classification proposed in this draft
   document is introduced in the 'A PoC demonstration titled "A Multi-Level Approach to IBN' PoC demonstration [POC-IBN]. IBN" <xref target="POC-IBN" format="default"/>. The PoC is led by
   academics carrying out research in the area of SDN/NFV and SDN/NFV; the specific problem
   they are addressing is to apply the application of the intent concept at different levels that
   correspond to different stakeholders.</t>
          <t>
   For their research work, they considered two types of intents: slice
   intents and service chain intents. For the data center solution, only
   the slice intent is relevant.</t>
          <t>
   As already mentioned in section 6.3.3. , <xref target="sect-6.3.3"/>, a slice intent expresses a
   request for a network slice with two types of components: a set of
   top layer
   top-layer virtual functions, functions and a set of virtual switches and/or
   routers of L2/L3 VNFs.</t>
          <t>
   Following the intent classification methodology described
   step-by-step
   step by step in section 6.1. , <xref target="sect-6.1"/>, we identify the following:</t>

	<t><list style="numbers"><t>The

   <ol spacing="normal" type="1"><li>The intent solution is for the data center.</t>

	<t>The center.</li>
            <li>The intent user type is the cloud administrator for the slice
     intent and service chain intent.</t>

	<t>The intent.</li>
            <li>The type of intent, intent is a cloud management intent, intent for the slice
     intent.</t>

	<t>The
     intent.</li>
            <li>The intent scopes are connectivity and application.</t>

	<t>The application.</li>
            <li>The network scope is logical, and logical; the resource scope is virtual.</t>

	<t>The virtual.</li>
            <li>The abstractions are with technical feedback for the slice intent.</t>

	<t>The life-cycle intent.</li>
            <li>The life cycle is persistent.</t>

	</list>
	</t> persistent.</li>
          </ol>
          <t>
   The following table shows how to represent this information in a
   tabular form, where form; the 'X' "X" in the table refers to the slice intent.</t>

<figure><artwork><![CDATA[
+---------+-------------+-----------------+-----+-----+-----+-----+

<figure title="Intent Classification Example for Data Center Network Solutions"><artwork><![CDATA[
+===========+=============+=================+=====+=====+=====+=====+
|Intent   | Intent      | User| Intent          | DCN | DCN | ABS | L-C |
|User     | Type |Intent           |DCN  |DCN  |ABS  |L-C  | Scope
| Res           | Net             |Scope            |Res  |Net  |     |     |
|           |             +-----------------+-----+-----+-----+-----+             +==+==+==+==+==+==+==+==+==+==+==+==+==+==+
|           |             |C1|C2|C3|C4|C5|C6|C1|C2|C1|C2|C1|C2|C1|C2|
+---------+-------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|Customer
+===========+=============+==+==+==+==+==+==+==+==+==+==+==+==+==+==+
|Customer/  | Customer    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|/Tenants
|Tenants    | Service     |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Intent      |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           +-------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|           | Strategy    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Intent      |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
+---------+-------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| Cloud   |
+-----------+-------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|Cloud Admin| Cloud       |X |  |X |  |  |  |X |  |X |  |X |  |X |  |
|           | Management  |  |  |  |  | Admin  | Management  |X  |  |X  |  |  |  |X  |  |X  |  |X  |  |X  |  |
|           | Intent      |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           +-------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|           | Cloud       |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Resource    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Management  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Intent      |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           +-------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|           | Operational |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Task Intent |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           +-------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|           | Strategy    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Intent      |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
+---------+-------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
+-----------+-------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|Underlay   | Underlay    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|Network    | Network     |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|Admin      | Intent      |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           +-------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|           | Underlay    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Network     |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Resource    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Intent      |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           +-------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|           | Operational |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Task Intent |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           +-------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|           | Strategy    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Intent      |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
+---------+-------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
+-----------+-------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|App        | Cloud       |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|Developer|
|Developer  | Management  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Intent      |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           +-------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|           | Cloud       |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Resource    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Management  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Intent      |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           +-------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|           | Underlay    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Network     |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Intent      |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           +-------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|           | Underlay    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Network     |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Resource    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Intent      |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           +-------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|           | Operational |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Task Intent |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           +-------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|           | Strategy    |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
|           | Intent      |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
+---------+-------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+

Table 5 - Intent Classification Example for Data Center Network
                                 Solutions
+-----------+-------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
]]></artwork>
        </figure>

        </section>
      </section>
      <section title="Intent anchor="sect-6.5" numbered="true" toc="default">
        <name>Intent Classification for Enterprise Solution" anchor="sect-6.5"><section title="Intent Solution</name>
        <section anchor="sect-6.5.1" numbered="true" toc="default">
          <name>Intent Users and Intent Types" anchor="sect-6.5.1"><t> Types</name>
          <t>
   The following table describes the intent users in enterprise
   solutions and their intent types.</t>

	<figure><artwork><![CDATA[
+--------------+-------------+-------------------------------------+
| Intent User  | Intent Type |    Intent Type Description          |
+--------------+---------------------------------------------------+
| End-User     | Customer    |

<table anchor="int-class-enterprise-solution">
  <name>Intent Classification for Enterprise end-user self-service or |
|              | Solution</name>
  <thead>
    <tr>
      <td>Intent User</td>
      <td>Intent Type</td>
      <td>Intent Type Description</td>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td rowspan="2">End User</td>
      <td>Customer Service     | applications, Intent</td>
      <td><t>Enterprise end user self service or
      applications; enterprise may have   |
|              | Intent      |
      multiple types of end-users.        |
|              |             | Example: end users.</t>
      <t>Example: Request access to VPN      |
|              |             | service.                            |
|              |             |
      Request video conference between    |
|              |             | end-user
      end user A and B.                   |
|              +---------------------------------------------------+
|              | Strategy    | This B.</t></td>
    </tr>
    <tr>
      <td>Strategy Intent</td>
      <td><t>This includes models and policy     |
|              | Intent      |
      intents designed by end-users end users to be |
|              |             |
      used by end-user intents and their  |
|              |             | applications.                       |
|              |             | Example: applications.</t>
      <t>Example: Create a video conference  |
|              |             |
      type for a weekly meeting.          |
+------------------------------------------------------------------+
|Enterprise    | Network     | meeting.</t></td>
    </tr>
    <tr>
      <td rowspan="4">Enterprise Administrator (internal or MSP)</td>
      <td>Network Service Intent</td>
      <td><t>Service provided by the             |
|Administrator | Service     |
      administrator to the end-users      |
|(internal or  | Intent      | end users
      and their applications.             |
| MSP)         |             | Example: </t>
      <t>Example: For any end-user end user of        |
|              |             |
      application X, the arrival of       |
|              |             |
      hologram objects of all the remote  |
|              |             |
      tele-presenters should be           |
|              |             | synchronised
      synchronized within 50ms 50 ms to reach   |
|              |             |
      the destination viewer for each     |
|              |             |
      conversation session.               |
|              |             |
      Create management VPN connectivity  |
|              |             |
      for type of service A.              |
|              |             | Operational </t>
      <t>Operational statement: The job of   |
|              |             |
      the network layer is to ensure that |
|              |             |
      the delay is between 50-70ms through|
|              |             | 50-70 ms through
      the routing algorithm. At the same  |
|              |             | time,the
      time, the node resources need to meet|
|              |             | meet
      the bandwidth requirements of 4K    |
|              |             |
      video conferences.                  |
+------------------------------------------------------------------+
|              | Network     | Administrator conferences.</t></td>
    </tr>
    <tr>
      <td>Network Intent</td>
      <td><t>Administrator requires network wide |
|              | Intent      | network-wide
      configuration (e.g. underlay,       |
|              |             | (e.g., underlay or
      campus) or resource configuration   |
|              |             |
      (switches, routers, or policies).      |
|              |             | Example: </t>
      <t>Example: Configure switches in      |
|              |             |
      campus network 1 to prioritise      |
|              |             | prioritize
      traffic of type A.                  |
|              |             |
      Configure YouTube as business       |
|              |             | non-relevant.                       |
|              +---------------------------------------------------+
|              | Operational | Administrator
      non-relevant.</t></td>
    </tr>
    <tr>
      <td>Operational Task Intent</td>
      <td><t>Administrator requests execution of |
|              | Task Intent |
      any automated task other than       |
|              |             |
      network service intents and network |
|              |             | intents.                            |
|              |             | Example: intents.</t>
      <t>Example: Request network security   |
|              |             |
      automated tasks such as web         |
|              |             |
      filtering and DDOS DDoS cloud protection.|
|              +---------------------------------------------------+
|              | Strategy    | Administrator protection.</t></td>
    </tr>
    <tr>
      <td>Strategy Intent</td>
      <td><t>Administrator designs models, policy|
|              | Intent      | intents policy
      intents, and workflows to be used by |
|              |             |
      other intents. Automate any tasks   |
|              |             |
      that the administrator often performs.  |
|              |             | Example: </t>
      <t>Example: In case of emergency,      |
|              |             |
      automatically shift all traffic of  |
|              |             |
      type A through network N.           |
|              |             |                                     |
+--------------+-------------+-------------------------------------+
| Application  | End-User    | End-user N.</t></td>
    </tr>
    <tr>
      <td rowspan="5">Application Developer</td>
      <td>End-User Intent</td>
      <td><t>End-user service / application      |
| Developer    | Intent      |
      intent API provided to the          |
|              |             |
      application developers.             |
|              |             | Example: developers.</t>
      <t>Example: API for request to open a  |
|              |             |
      VPN service.                        |
|              +---------------------------------------------------+
|              | Network     | Network service.</t></td>
    </tr>
    <tr>
      <td>Network Service Intent</td>
      <td><t>Network service API provided to     |
|              | Service     |
      application developers.             |
|              | Intent      | Example: </t>
      <t>Example: API for request network    |
|              |             |
      bandwidth and latency for           |
|              |             |
      hosting a video conference.           |
|              +---------------------------------------------------+
|              | Network     | Network conference.</t></td>
    </tr>
    <tr>
      <td>Network Intent</td>
      <td><t>Network API provided to application |
|              | Intent      | developers.                         |
|              |             | Example:
      developers.</t>
      <t>Example: API for request of requesting network |
|              |             | devices configuration.              |
|              +---------------------------------------------------+
|              | Operational | Operational
      device configuration.</t></td>
    </tr>
    <tr>
      <td>Operational Task Intent</td>
      <td><t>Operational task intent API provided|
|              | Task Intent | provided
      to the trusted application developer|
|              |             | developer
      (internal DevOps).                  |
|              |             | Example: DevOps).</t>
      <t>Example: API for requesting         |
|              |             |
      automatic monitoring and            |
|              |             |
      interception for network security   |
|              +---------------------------------------------------+
|              | Strategy    | Application security.</t></td>
    </tr>
    <tr>
      <td>Strategy Intent</td>
      <td><t>Application developer designs       |
|              | Intent      |
      models, policy intents intents, and building |
|              |             |
      blocks to be used by other intents. |
|              |             |
      This is for the trusted internal    |
|              |             | DevOps.                             |
|              |             | Example: DevOps.</t>
      <t>Example: API for strategy intent in |
|              |             |
      case of emergencies.                |
|              |             |                                     |
+--------------+-------------+-------------------------------------+

       Table 6 - Intent Classification for Enterprise Solution
]]></artwork>
	</figure> emergencies.</t></td>
    </tr>
  </tbody>
</table>

        </section>
        <section title="Intent Categories" anchor="sect-6.5.2"><t> anchor="sect-6.5.2" numbered="true" toc="default">
          <name>Intent Categories</name>
          <t>
   The following are the proposed categories:

     <list style="symbols">

       <t>Intent

          </t>

	  <dl>

	    <dt>Intent Scope: C1=Connectivity,
	    </dt>
	    <dd>C1=Connectivity, C2=Security/Privacy, C3=Application,
       C4=QoS</t>

       <t>Network C4=QoS
	    </dd>

	    <dt>Network (Net) Scope: C1=Campus,
	    </dt>
	    <dd>C1=Campus, C2=Branch, C3=SD-WAN</t>

       <t>Abstraction C3=SD-WAN
	    </dd>

	    <dt>Abstraction (ABS): C1=Technical
	    </dt>
	    <dd>C1=Technical (with technical feedback), C2=Non-technical
	    (without technical feedback), see section 5.2.</t>

       <t>Life-cycle feedback) (see <xref target="sect-5.2"/>)
	    </dd>

	    <dt>Life cycle (L-C): C1=Persistent
	    </dt>
	    <dd>C1=Persistent (full life-cycle), life cycle), C2=Transient (short lived)</t>

     </list></t> lived)
	    </dd>

</dl>

<t>
   The following is the intent classification table example for
   enterprise solutions.</t>

<figure><artwork><![CDATA[

<figure title="Intent Categories for Enterprise Solution "><artwork><![CDATA[
+---------------+-------------+-----------+--------+-----+-----+
| Intent User   | Intent Type | Intent    | Net    | ABS | L-C |
|               |             | Scope     |        |     |     |
|               |             +-----------+--------+-----+-----+
|               |             |C1|C2|C3|C4|C1|C2|C3|C1|C2|C1|C2|
+---------------+-------------+--+--+--+--+--+--+--+--+--+--+--+
| End-User End User      | Customer    |  |  |  |  |  |  |  |  |  |  |  |
|               | Service     |  |  |  |  |  |  |  |  |  |  |  |
|               | Intent      |  |  |  |  |  |  |  |  |  |  |  |
|               +-------------+--+--+--+--+--+--+--+--+--+--+--+
|               | Strategy    |  |  |  |  |  |  |  |  |  |  |  |
|               | Intent      |  |  |  |  |  |  |  |  |  |  |  |
+---------------+-------------+--+--+--+--+--+--+--+--+--+--+--+
| Enterprise    | Network     |  |  |  |  |  |  |  |  |  |  |  |
| Administrator | Service     |  |  |  |  |  |  |  |  |  |  |  |
|               | Intent      |  |  |  |  |  |  |  |  |  |  |  |
|               +-------------+--+--+--+--+--+--+--+--+--+--+--+
|               | Network     |  |  |  |  |  |  |  |  |  |  |  |
|               | Intent      |  |  |  |  |  |  |  |  |  |  |  |
|               +-------------+--+--+--+--+--+--+--+--+--+--+--+
|               | Operational |  |  |  |  |  |  |  |  |  |  |  |
|               | Task        |  |  |  |  |  |  |  |  |  |  |  |
|               | Intent      |  |  |  |  |  |  |  |  |  |  |  |
|               +-------------+--+--+--+--+--+--+--+--+--+--+--+
|               | Strategy    |  |  |  |  |  |  |  |  |  |  |  |
|               | Intent      |  |  |  |  |  |  |  |  |  |  |  |
+---------------+-------------+--+--+--+--+--+--+--+--+--+--+--+
| Application   | End-User    |  |  |  |  |  |  |  |  |  |  |  |
| Developer     | Intent      |  |  |  |  |  |  |  |  |  |  |  |
|               +-------------+--+--+--+--+--+--+--+--+--+--+--+
|               | Network     |  |  |  |  |  |  |  |  |  |  |  |
|               | Service     |  |  |  |  |  |  |  |  |  |  |  |
|               | Intent      |  |  |  |  |  |  |  |  |  |  |  |
|               +-------------+--+--+--+--+--+--+--+--+--+--+--+
|               | Network     |  |  |  |  |  |  |  |  |  |  |  |
|               | Intent      |  |  |  |  |  |  |  |  |  |  |  |
|               +-------------+--+--+--+--+--+--+--+--+--+--+--+
|               | Operational |  |  |  |  |  |  |  |  |  |  |  |
|               | Task        |  |  |  |  |  |  |  |  |  |  |  |
|               | Intent      |  |  |  |  |  |  |  |  |  |  |  |
|               +-------------+--+--+--+--+--+--+--+--+--+--+--+
|               | Strategy    |  |  |  |  |  |  |  |  |  |  |  |
|               | Intent      |  |  |  |  |  |  |  |  |  |  |  |
+---------------+-------------+--+--+--+--+--+--+--+--+--+--+--+

       Table 7 - Intent Categories for Enterprise Solution
]]></artwork>
</figure>
        </section>
      </section>
    </section>
    <section title="Conclusions" anchor="sect-7"><t> anchor="sect-7" numbered="true" toc="default">
      <name>Conclusions</name>
      <t>
   This document is aligned with the RG objectives and supports
   investigations into intent-based networking by proposing an intent
   categorization methodology and taxonomy. It brings clarification on to
   what an intent represents for different stakeholders through the
   proposal of an Intent Classification intent classification approach, ensuring that a
   common understanding among all the participants exists. This,
   together with the proposed intent taxonomy provides a solid
   foundation for future intent-related topic discussions within the NMRG.</t>
      <t>
   The benefits of this intent classification draft document in the research community
   have been demonstrated through a PoC implementation
   [POC-IBN] <xref target="POC-IBN"
   format="default"/> in which the draft's document's concepts have been applied at different levels
   corresponding to different stakeholders have been applied to.</t> stakeholders.</t>
    </section>
    <section title="Security Considerations" anchor="sect-8"><t> anchor="sect-8" numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>
   This document identifies the security and privacy as categories of
   the intent scope. The intents could be solely security intents and
   privacy intents intents, or security can be embedded in the intents that
   include also connectivity, application, and QoS scope.</t>
      <t>
   Security and privacy scope, scope is when the intent specifies the security
   characteristics of the network, customers, or end-users, end users, and privacy
   for customers and end-users.</t> end users.</t>
   <t>

   More details of these security intents would will be described in future
   documents that specify architecture, functionality, user intents intents, and
   models. As well, an An analysis of the security considerations of the
   overall intent-based system is provided in section 10 of <xref target="I-D.irtf-nmrg-ibn-concepts-definitions"/>.</t> target="RFC9315" sectionFormat="of" section="9"  format="default"/>.</t>
    </section>

    <section title="IANA Considerations" anchor="sect-9"><t> anchor="sect-9" numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>
   This document has no actions for IANA.</t>

	</section>

	<section title="Contributors" anchor="sect-10"><t>
   The following people all contributed to creating this document:</t>

   <t>Contributed significant text:</t>
<figure><artwork><![CDATA[
      Xueyuan Sun, China Telecom
      Will (Shucheng) Liu, Huawei
]]></artwork>
	</figure>

	<t>Contributed text in early drafts:</t>
<figure><artwork><![CDATA[
      Ying Chen, China Unicom
      John Strassner, Huawei
      Weiping Xu, Huawei
      Richard Meade, Huawei
]]></artwork>
	</figure>

	</section>

	<section title="Acknowledgments" anchor="sect-11"><t>
   This document has benefited from reviews, suggestions, comments and
   proposed text provided by the following members, listed in
   alphabetical order: Mehdi Bezahaf, Brian E Carpenter, Laurent
   Ciavaglia, Benoit Claise, Alexander Clemm, Yehia Elkhatib, Jerome
   Francois, Pedro Andres Aranda Gutierrez, Daniel King, Branislav
   Meandzija, Bob Natale, Juergen Schoenwaelder, Xiaolin Song, Jeff
   Tantsura.</t>

	<t>
   We thank to Barbara Martini, Walter Cerroni, Molka Gharbaoui, Davide
   Borsatti, for contributing with their 'A multi-level approach to
   IBN' PoC demonstration a first attempt to adopt the intent
   classification methodology.</t> IANA actions.
      </t>
    </section>

  </middle>

  <back>
	<references title="Informative References">

	<!--
   draft-irtf-nmrg-ibn-intent-classification-08-manual.txt(1684): Warning: Failed
   parsing a reference.  Are all elements separated by commas (not periods, not
   just spaces)?:
   [Bezahaf21] Bezahaf, M., Davies, E., Rotsos, C. and Race, N., "To All
             Intents and Purposes: Towards Flexible Intent Expression,"
             2021 IEEE 7th International Conference on Network
             Softwarization (NetSoft), 2021. -->

    <references>
      <name>Informative References</name>

<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9315.xml"/>

      <reference anchor="Bezahaf21">
        <front>
          <title>To All Intents and Purposes: Towards Flexible Intent Expression</title>
          <author initials="M." surname="Bezahaf" fullname="M. Bezahaf">
            <organization/>
          </author>
          <author initials="E." surname="Davies" fullname="E. Davies">
            <organization/>
          </author>
          <author initials="C." surname="Rotsos" fullname="C. Rotsos">
            <organization/>
          </author>
          <author initials="N." surname="Race" fullname="N. Race">
            <organization/>
          </author>
          <date month="" month="July" year="2021"/>
        </front>
	<seriesInfo name="IEEE name="DOI" value="10.1109/NetSoft51509.2021.9492554"/>
        <refcontent>IEEE 7th International Conference on Network Softwarization (NetSoft)" value=""/> (NetSoft)</refcontent>
      </reference>

	<!--
   draft-irtf-nmrg-ibn-intent-classification-08-manual.txt(1689): Warning:
   Failed parsing a reference.  Are all elements separated by commas (not
   periods, not just spaces)?: [Bezhaf19] Bezahaf, M., Hernandez, MP,
   Bardwell, L., Davies, E., Broadbent, M.,King, D. and Hutchison, D. ,
   "Self-Generated Intent-Based System," 2019 10th International Conference on
   Networks of the Future (NoF), 2019.
   -->

      <reference anchor="Bezhaf19"> anchor="Bezahaf19">
        <front>
          <title>Self-Generated Intent-Based System</title>
          <author initials="M." surname="Bezahaf" fullname="M. Bezahaf">
            <organization/>
          </author>
          <author initials="M." surname="Hernandez" fullname="M. Hernandez">
            <organization/>
          </author>
          <author initials="L." surname="Bardwell" fullname="L. Bardwell">
            <organization/>
          </author>
          <author initials="E." surname="Davies" fullname="E. Davies">
            <organization/>
          </author>
          <author initials="M." surname="Broadbent" fullname="M. Broadbent">
            <organization/>
          </author>
          <author initials="D." surname="King" fullname="D. King">
            <organization/>
          </author>
          <author initials="D." surname="Hutchison" fullname="D. Hutchison">
            <organization/>
          </author>
          <date month="" month="October" year="2019"/>
        </front>
	<seriesInfo name="10th name="DOI" value="10.1109/NoF47743.2019.9015045"/>
        <refcontent>10th International Conference on Networks of the Future (NoF)" value=""/> (NoF)</refcontent>
      </reference>

	<!--
   draft-irtf-nmrg-ibn-intent-classification-08-manual.txt(1694): Warning: Failed
   parsing a reference.  Are all elements separated by commas (not periods, not
   just spaces)?:
   [Jacobs18] Jacobs, A.S., Pfitscher,R.J., Ferreira, R.A., and Granville,
             L.Z., "Refining Network Intents for Self-Driving Networks",
             Proceedings of the Afternoon Workshop on Self-Driving Networks
             (SelfDN 2018), 2018.
   -->

      <reference anchor="Jacobs18">
        <front>
          <title>Refining Network Intents for Self-Driving Networks</title>
          <author initials="A." surname="Jacobs" fullname="A. Jacobs">
            <organization/>
          </author>
          <author initials="R." surname="Pfitscher" fullname="R. Pfitscher">
            <organization/>
          </author>
          <author initials="R." surname="Ferreira" fullname="R. Ferreira">
            <organization/>
          </author>
          <author initials="L." surname="Granville" fullname="L. Granville">
            <organization/>
          </author>
          <date month="" month="August" year="2018"/>
        </front>
	<seriesInfo name="Proceedings name="DOI" value="10.1145/3229584.3229590"/>
        <refcontent>Proceedings of the Afternoon Workshop on Self-Driving Networks (SelfDN)" value=""/> (SelfDN)</refcontent>
      </reference>

	<!--
   draft-irtf-nmrg-ibn-intent-classification-08-manual.txt(1699): Warning: Failed
   parsing a reference.  Are all elements separated by commas (not periods, not
   just spaces)?:
   [Banerjee21] Banerjee,A., Mwanje. S. and Carle, G., "Contradiction
             Management in Intent-driven Cognitive Autonomous RAN",
             2021.
   -->

      <reference anchor="Banerjee21">
        <front>
          <title>Contradiction Management in Intent-driven Cognitive Autonomous RAN</title>
          <author initials="A." surname="Banerjee" fullname="A. Banerjee">
            <organization/>
          </author>
          <author initials="S." surname="Mwanje" fullname="S. Mwanje">
            <organization/>
          </author>
          <author initials="G." surname="Carle" fullname="G. Carle">
            <organization/>
          </author>
          <date month="" month="September" year="2021"/>
        </front>
      </reference>

      <reference anchor="Tian19"><front> anchor="Tian19">
        <front>
          <title>Safely and automatically updating in-network ACL configurations with intent language</title>
          <author initials="B." surname="Tian" fullname="B. Tian">
            <organization/>
          </author>
          <author initials="X." surname="Zhang" fullname="X. Zhang">
            <organization/>
          </author>
          <author initials="E." surname="Zhai" fullname="E. Zhai">
            <organization/>
          </author>
          <author initials="H." surname="Liu" fullname="H. Liu">
            <organization/>
          </author>
          <author initials="Q." surname="Ye" fullname=""> fullname="Q. Ye">
            <organization/>
          </author>
          <author initials="C." surname="Wang" fullname="C. Wang">
            <organization/>
          </author>
          <author initials="X." surname="Wu" fullname="X. Wu">
            <organization/>
          </author>
          <author initials="Z." surname="Ji" fullname="Z. Ji">
            <organization/>
          </author>
          <author initials="Y." surname="Sang" fullname="Y. Sang">
            <organization/>
          </author>
          <author initials="M." surname="Zhang" fullname="M. Zhang">
            <organization/>
          </author>
          <author initials="D." surname="Yu" fullname="D. Yu">
            <organization/>
          </author>
          <author initials="C." surname="Tian" fullname="C. Tian">
            <organization/>
          </author>
          <author initials="H." surname="Zheng" fullname="H. Zheng">
            <organization/>
          </author>
          <author initials="B." surname="Zhao" fullname="B. Zhao">
            <organization/>
          </author>
          <date month="August" year="2019"/>
        </front>
	<seriesInfo name="SIGCOMM" value="'19"/>
	</reference>

	<!--
   draft-irtf-nmrg-ibn-intent-classification-08-manual.txt(1708): Warning: Failed
   parsing a reference.  Are all elements separated by commas (not periods, not
   just spaces)?:
   [Leivadeas21] Leivadeas, A. and Falkner, M., "VNF Placement Problem:
             A Multi-Tenant Intent-Based Networking Approach," 24th
             Conference name="DOI" value="10.1145/3341302.3342088"/>
        <refcontent>SIGCOMM '19: Proceedings of the ACM Special Interest Group on Innovation in Clouds, Internet and Networks
             and Workshops (ICIN), 2021. --> Data Communication</refcontent>
      </reference>

      <reference anchor="Leivadeas21">
        <front>
          <title>VNF Placement Problem: A Multi-Tenant Intent-Based Networking Approach</title>
          <author initials="A." surname="Leivadeas" fullname="A. Leivadeas">
            <organization/>
          </author>
          <author initials="M." surname="Falkner" fullname="M. Falkner">
            <organization/>
          </author>
          <date month="" month="March" year="2021"/>
        </front>
	<seriesInfo name="24th name="DOI" value="10.1109/ICIN51074.2021.9385553"/>
        <refcontent>24th Conference on Innovation in Clouds, Internet and Networks and Workshops (ICIN)" value=""/> (ICIN)</refcontent>
      </reference>

      <reference anchor="Davoli21"><front> anchor="Davoli21">
        <front>
          <title>Programmability and Management of Software-defined Software-Defined Network Infrastructures</title>
          <author initials="G." surname="Davoli" fullname="G. Davoli">
	</author>
          <date year="2021"/>
        </front>
      </reference>

      <reference anchor="Padovan20"><front> anchor="Padovan20">
        <front>
          <title>Design and Implementation of a Blockchain Intent Management System</title>
          <author initials="S." surname="Padovan" fullname="S. Padovan">
	</author>
          <date month="November" year="2020"/>
        </front>
      </reference>

      <reference anchor="Mehmood21"><front> anchor="Mehmood21">
        <front>
          <title>Intent-driven Autonomous Network and Service Management in Future Networks: A Structured Literature Review</title>
          <author initials="K." surname="Mehmood" fullname="K. Mehmood">
	</author>
          <author initials="K." surname="Kralevska" fullname="K. Kralevska">
	</author>
          <author initials="D." surname="Palma" fullname="Palma, D."> fullname="D. Palma">
	</author>
        <date month="August" year="2021"/>
        </front>
	<seriesInfo name="DOI" value="10.48550/arXiv.2108.04560"/>
      </reference>

      <reference anchor="Szilagyi21"><front> anchor="Szilagyi21">
        <front>
          <title>I2BN: Intelligent Intent Based Networks</title>
          <author initials="P." surname="Szilagyi" surname="Szilágyi " fullname="P. Szilagyi"> Szilágyi">
	</author>
          <date month="June" year="2021"/>
        </front>
	<seriesInfo name="Journal" value="of name="DOI" value="10.13052/jicts2245-800X.926"/>
        <refcontent>Journal of ICT Standardization"/> Standardization</refcontent>
<refcontent>Volume 9, Issue 2</refcontent>
      </reference>

	<!--
   draft-irtf-nmrg-ibn-intent-classification-08-manual.txt(1726): Warning: Failed
   parsing a reference.  Are all elements separated by commas (not periods, not
   just spaces)?:
   [POC-IBN] Barbara Martini, Walter Cerroni, Molka Gharbaoui, Davide
             Borsatti, "A multi-level approach to IBN", July 2020,
             https://www.ietf.org/proceedings/108/slides/slides-108-nmrg-
             ietf-108-hackathon-report-a-multi-level-approach-to-ibn-02
   -->

      <reference anchor="POC-IBN" target="https://www.ietf.org/proceedings/108/slides/slides-108-nmrg-ietf-108-hackathon-report-a-multi-level-approach-to-ibn-02">
        <front>
          <title>A multi-level approach Multi-Level Approach to IBN</title>
          <author initials="B." surname="Martini" fullname="B. Martini">
            <organization/>
          </author>
          <author initials="W." surname="Cerroni" fullname="W. Cerroni">
            <organization/>
          </author>
          <author initials="M." surname="Gharbaoui" fullname="M. Gharbaoui">
            <organization/>
          </author>
          <author initials="D." surname="Borsatti" fullname="D. Borsatti">
            <organization/>
          </author>
          <date month="July" year="2020"/>
        </front>
	<refcontent>IETF 108 Hackathon Report</refcontent>
      </reference>

	<!--
   draft-irtf-nmrg-ibn-intent-classification-08-manual.txt(1729): Warning: Failed
   parsing a reference.  Are all elements separated by commas (not periods, not
   just spaces)?:
   [IFIP-NSM] IFIP - Network and Service Management Taxonomy,
             https://www.simpleweb.org/ifip/taxonomy.html
   -->

      <reference anchor="IFIP-NSM" target="https://www.simpleweb.org/ifip/taxonomy.html">
        <front>
         <title>IFIP - Network
          <title>Network and Service Management Taxonomy</title>
          <author initials="." surname="" fullname="">
            <organization/>
          <author>
            <organization>IFIP</organization>
          </author>
          <date month="" year=""/>
        </front>
        <seriesInfo name="" value=""/>
      </reference>

	<!--
   draft-irtf-nmrg-ibn-intent-classification-08-manual.txt(1732): Warning: Failed
   parsing a reference.  Are all elements separated by commas (not periods, not
   just spaces)?:
   [ONF] ONF, "Intent Definition Principles", 2017,
   [<https://www.opennetworking.org/images/stories/downloads/sdn-
   [resources/technical-reports/TR-523_Intent_Definition_Principles.pdf>.
   -->

<reference anchor="ONF" target="https://www.opennetworking.org/images/stories/downloads/sdn-resources/technical-reports/TR-523_Intent_Definition_Principles.pdf"> target="https://opennetworking.wpengine.com/wp-content/uploads/2014/10/TR-523_Intent_Definition_Principles.pdf">
        <front>
          <title>Intent NBI - Definition and Principles</title>
          <author initials="." surname="" fullname="">
            <organization/>
          <author>
            <organization>Open Networking Foundation</organization>
          </author>
          <date month="" year="2017"/> month="October" year="2016"/>
        </front>
        <seriesInfo name="" value=""/>
      </reference>

	<!--
   draft-irtf-nmrg-ibn-intent-classification-08-manual.txt(1734): Warning: Failed
   parsing a reference.  Are all elements separated by commas (not periods, not
   just spaces)?:
   [ONOS] ONOS, "ONOS Intent Framework", 2017,
   [<https://wiki.onosproject.org/display/ONOS/Intent+Framework/>.
   -->

      <reference anchor="ONOS" target="https://wiki.onosproject.org/display/ONOS/Intent+Framework/">
        <front>
         <title>ONOS Intent
          <title>Intent Framework</title>
          <author initials="." surname="" fullname="">
            <organization/>
          </author>
          <author initials="." surname="" fullname=""> initials="A" surname="Koshibe" fullname="A. Koshibe">
            <organization/>
	  </author>
          <date month="" year="2017"/> year="2016"/>
        </front>
        <seriesInfo name="" value=""/>
      </reference>

	&I-D.irtf-nmrg-ibn-concepts-definitions;

<!-- [rfced] [TMF-auto] URL https://www.tmforum.org/wp-content/uploads/2019/05/22553-Autonomous-Networks-whitepaper.pdf -->

	<!--
   draft-irtf-nmrg-ibn-intent-classification-08-manual.txt(1741): Warning: Failed
   parsing a reference.  Are all elements separated by commas (not periods, not
   just spaces)?:
   [TMF-auto] Aaron Richard Earl Boasman-Patel,et, A whitepaper of
             Autonomous Networks: Empowering Digital Transformation For
             the Telecoms Industry, inform.tmforum.org, 15 May, 2019.
   -->

      <reference anchor="TMF-auto"> anchor="TMF-AUTO">
        <front>
         <title>A whitepaper of Autonomous
          <title>Autonomous Networks: Empowering Digital Transformation
For The Telecoms Industry</title>
          <author initials="A." surname="Boasman-Patel" fullname="A. Boasman-Patel ">
            <organization/>
          </author>
	  <author initials="D." surname="Sun" fullname="D. Sun">
            <organization/>
	  </author>
	  <author initials="Y." surname="Wang" fullname="Y. Wang">
            <organization/>
	  </author>
	  <author initials="C." surname="Maitre" fullname="C. Maitre">
            <organization/>
	  </author>
	  <author initials="J." surname="Domingos" fullname="J. Domingos">
            <organization/>
	  </author>
	  <author initials="Y." surname="Troullides" fullname="Y. Troullides">
            <organization/>
	  </author>
	  <author initials="I." surname="Mas" fullname="I. Mas">
            <organization/>
	  </author>
	  <author initials="G." surname="Traver" fullname="G. Traver">
            <organization/>
	  </author>
	  <author initials="G." surname="Lupo" fullname="G. Lupo">
            <organization/>
	  </author>
	  <date month="May" year="2019"/>
        </front>
        <seriesInfo name="" value=""/>
      </reference>

	&RFC2119;
	&RFC7575;
	&RFC8328;
	&RFC3198;
	&RFC6020;
	&RFC7285;
	&I-D.du-anima-an-intent;
	&I-D.ietf-supa-generic-policy-info-model;
	&I-D.ietf-anima-prefix-management;

    </references>

    <section anchor="sect-11" numbered="false" toc="default">
      <name>Acknowledgments</name>
      <t>
   This document has benefited from reviews, suggestions, comments, and
   proposed text provided by the following members listed in
   alphabetical order: <contact fullname="Mehdi Bezahaf"/>, <contact fullname="Brian E. Carpenter"/>, <contact fullname="Laurent
   Ciavaglia"/>, <contact fullname="Benoit Claise"/>, <contact fullname="Alexander Clemm"/>, <contact fullname="Yehia Elkhatib"/>, <contact fullname="Jerome
   Francois"/>, <contact fullname="Pedro Andres Aranda Gutierrez"/>, <contact fullname="Daniel King"/>, <contact fullname="Branislav
   Meandzija"/>, <contact fullname="Bob Natale"/>, <contact fullname="Juergen Schoenwaelder"/>, <contact fullname="Xiaolin Song"/>, and <contact fullname="Jeff
   Tantsura"/>.</t>
      <t>
   We thank <contact fullname="Barbara Martini"/>, <contact fullname="Walter Cerroni"/>, <contact fullname="Molka Gharbaoui"/>, and <contact fullname="Davide
   Borsatti"/> for contributing with their "A multi-level approach to
   IBN" PoC demonstration, a first attempt to adopt the intent
   classification methodology.</t>
    </section>

    <section anchor="sect-10" numbered="false" toc="default">
      <name>Contributors</name>
      <t>The following people all contributed to creating this document:</t>
      <t>Contributed significant text:</t>

 <author initials="X" surname="Sun" fullname="Xueyuan Sun">
      <organization>China Telecom</organization>
 </author>

  <author initials="W" surname="Liu" fullname="Will (Shucheng) Liu">
      <organization>Huawei</organization>
 </author>

<t>Contributed text in early draft versions of this document:</t>

 <author initials="Y" surname="Chen" fullname="Ying Chen">
      <organization>China Unicom</organization>
 </author>

 <author initials="J" surname="Strassner" fullname="John Strassner">
      <organization>Huawei</organization>
 </author>
  <author initials="W" surname="Xu" fullname="Weiping Xu">
      <organization>Huawei </organization>
  </author>
   <author initials="R" surname="Meade" fullname="Richard Meade">
      <organization>Huawei</organization>
 </author>

</section>

  </back>
</rfc>