<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp    "&#8203;">
  <!ENTITY nbhy    "&#8209;">
  <!ENTITY wj      "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude"
     ipr="trust200902"
     category="std"
     docName="draft-gong-spring-sr-policy-group-yang-05"
     submissionType="IETF"
     consensus="true"
     xml:lang="en"
     version="3">

  <front>
    <title abbrev="YANG Data Model for SR Policy Group">YANG Data Model for SR Policy Group</title>
    <seriesInfo name="Internet-Draft" value="draft-gong-spring-sr-policy-group-yang-05"/>
    <author fullname="Liyan Gong" initials="L." surname="Gong">
      <organization>China Mobile</organization>
      <address>
        <postal>
          <country>China</country>
        </postal>
        <email>gongliyan@chinamobile.com</email>
      </address>
    </author>
    <author fullname="Changwang Lin" initials="C." surname="Lin">
      <organization>New H3C Technologies</organization>
      <address>
        <postal>
          <country>China</country>
        </postal>
        <email>linchangwang.04414@h3c.com</email>
      </address>
    </author>
    <author fullname="Ran Chen" initials="R." surname="Chen">
      <organization>ZTE Corporation</organization>
      <address>
        <postal>
          <country>China</country>
        </postal>
        <email>chen.ran@zte.com.cn</email>
      </address>
    </author>
    <author fullname="Haiyang Zhang" initials="H." surname="Zhang">
      <organization>New H3C Technologies</organization>
      <address>
        <postal>
          <country>China</country>
        </postal>
        <email>zhang.haiyangA@h3c.com</email>
      </address>
    </author>
    <date year="2026"/>
    <area>Routing</area>
    <workgroup>SPRING Working Group</workgroup>
    <keyword>SR Policy</keyword>
    <keyword>YANG</keyword>
    <keyword>SR Policy Group</keyword>
    <abstract>
      <t>This document defines a YANG data model for Segment Routing (SR)
      Policy Group that can be used for configuring, instantiating, and
      managing SR Policy groups. The model is generic and applies equally
      to the MPLS and SRv6 instantiations of SR Policy groups.</t>
    </abstract>
  </front>

  <middle>

    <section anchor="introduction" numbered="true">
      <name>Introduction</name>
      <t>The Network Configuration Protocol (NETCONF) <xref target="RFC6241"/> defines
      mechanisms to manage network devices. YANG <xref target="RFC7950"/> is a modular
      language that represents data structures in an XML tree format, and
      is used as a data modeling language for the NETCONF.</t>
      <t><xref target="I-D.ietf-spring-sr-policy-group"/> describes SR Policy Groups in MPLS
      and IPv6 environments. It illustrates some use cases for parent SR
      Policies and SR Policy Groups to provide best practice cases for
      operators.</t>
      <t><xref target="I-D.ietf-spring-sr-policy-yang"/> defines a YANG data model for SR
      Policy that can be used for configuring, instantiating, and managing
      SR policies.</t>
      <t>This document defines a YANG data model for SR Policy Groups that can
      be used for configuring, instantiating, and managing SR Policy
      groups. The model is generic and applies equally to the MPLS and
      SRv6 instantiations of SR Policy groups.</t>

      <section anchor="terminology" numbered="true">
        <name>Terminology</name>
        <t>The terminology for describing YANG data models is found in
        <xref target="RFC7950"/>, including:</t>
        <ul spacing="normal">
          <li>augment</li>
          <li>data model</li>
          <li>data node</li>
          <li>identity</li>
          <li>module</li>
        </ul>
        <t>The definitions of the basic terms are identical to those found in
        Segment Routing Architecture <xref target="RFC8402"/>, Segment Routing Policy
        Architecture <xref target="RFC9256"/>, and Segment Routing Policy Group
        <xref target="I-D.ietf-spring-sr-policy-group"/>.</t>
      </section>

      <section anchor="conventions" numbered="true">
        <name>Conventions Used in This Document</name>
        <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
        "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
        "OPTIONAL" in this document are to be interpreted as described in
        BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
        appear in all capitals, as shown here.</t>
      </section>

      <section anchor="tree-diagrams" numbered="true">
        <name>Tree Diagrams</name>
        <t>Tree diagrams used in this document follow the notation defined in
        <xref target="RFC8340"/>.</t>
      </section>

      <section anchor="prefixes" numbered="true">
        <name>Prefixes in Data Node Names</name>
        <t>In this document, names of data nodes, actions, and other data model
        objects are often used without a prefix, as long as it is clear from
        the context in which YANG module each name is defined. Otherwise,
        names are prefixed using the standard prefix associated with the
        corresponding YANG module, as shown in <xref target="tab-prefixes"/>.</t>

        <table anchor="tab-prefixes">
          <name>Prefixes in Data Node Names</name>
          <thead>
            <tr>
              <th align="left">Prefix</th>
              <th align="left">YANG module</th>
              <th align="left">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">rt</td>
              <td align="left">ietf-routing</td>
              <td align="left"><xref target="RFC8349"/></td>
            </tr>
            <tr>
              <td align="left">sr-policy</td>
              <td align="left">ietf-sr-policy</td>
              <td align="left"><xref target="I-D.ietf-spring-sr-policy-yang"/></td>
            </tr>
          </tbody>
        </table>
      </section>
    </section>

    <section anchor="model-overview" numbered="true">
      <name>Model Overview</name>
      <t>The SR Policy Group YANG data model is defined in this document.</t>
      <t>The ietf-sr-policy-group.yang data model provides the methods for
      configuring and managing SR Policy groups. It includes:</t>
      <ul spacing="normal">
        <li>Configuration of SR Policy groups: a container that defines a
        list of policy groups with their attributes, such as service
        identification methods, mapping relationships between DSCP and
        color, between dot1q and color, and between service class and
        color.</li>
      </ul>
    </section>

    <section anchor="yang-module" numbered="true">
      <name>SR Policy Group YANG Module</name>

      <section anchor="tree-view" numbered="true">
        <name>Tree View</name>
        <t>The following diagram depicts the high-level YANG organization
        and hierarchy for an SR Policy Group specification:</t>

        <figure anchor="fig-overview-tree">
          <name>High-Level Tree View of SR Policy Group</name>
          <artwork type="ascii-art" align="left"><![CDATA[
    Segment-routing
       Traffic-engineering
       + attributes
       |   + ......
       + policies
       |    policy* [headend color endpoint]
       |       ......
       + sr-policy-groups
           sr-policy-group* [group-color]
             + name
             + description
             + service-distinguish-method
             + forward-based-dscp
             |  + best-effort-dscp-list-v4
             |  + best-effort-dscp-list-v6
             |  + dscp-mismatch-drop
             |  + dscp-color-mapping-entries
             |       mapping-entry* [policy-color dataplane]
             |          dscp-list
             |          ......
             + forward-based-dot1q
             |  + best-effort-dot1q-list
             |  + dot1q-mismatch-drop
             |  + dot1q-color-mapping-entries
             |       mapping-entry* [policy-color]
             |          dot1q-list
             |          ......
             + forward-based-serviceclass
                + best-effort-classlist
                + class-mismatch-drop
                + class-color-mapping-entries
                     mapping-entry* [policy-color]
                        class-list
                        ......
]]></artwork>
        </figure>

        <t>The SR Policy Group YANG data model augments
        "/rt:routing/sr-policy:segment-routing/sr-policy:traffic-engineering",
        i.e., the SR Policy model specified in
        <xref target="I-D.ietf-spring-sr-policy-yang"/>, and specifies
        the configuration to manage the SR Policy groups.</t>
        <t>The complete tree of the ietf-sr-policy-group.yang data model is
        represented as follows. See <xref target="RFC8340"/> for an explanation of the
        symbols used.</t>

        <figure anchor="fig-full-tree">
          <name>Full Tree View of ietf-sr-policy-group Module</name>
          <artwork type="ascii-art" align="left"><![CDATA[
module: ietf-sr-policy-group
  augment /rt:routing/sr-policy:segment-routing
          /sr-policy:traffic-engineering:
    +--rw sr-policy-groups
       +--rw sr-policy-group* [group-color]
          +--rw group-color                   uint32
          +--rw name?                         string
          +--rw description?                  string
          +--rw service-distinguish-method?   enumeration
          +--rw forward-based-dscp
          |  +--rw best-effort-dscp-list-v4?     string
          |  +--rw best-effort-dscp-list-v6?     string
          |  +--rw dscp-mismatch-drop?           boolean
          |  +--rw dscp-color-mapping-entries
          |     +--rw mapping-entry* [policy-color dataplane]
          |        +--rw policy-color     uint32
          |        +--rw dataplane        dataplane-type
          |        +--rw dscp-list?       string
          |        +--rw is-as-default?   boolean
          +--rw forward-based-dot1q
          |  +--rw best-effort-dot1q-list?        string
          |  +--rw dot1q-mismatch-drop?           boolean
          |  +--rw dot1q-color-mapping-entries
          |     +--rw mapping-entry* [policy-color]
          |        +--rw policy-color     uint32
          |        +--rw dot1q-list?      string
          |        +--rw is-as-default?   boolean
          +--rw forward-based-serviceclass
             +--rw best-effort-classlist?         string
             +--rw class-mismatch-drop?           boolean
             +--rw class-color-mapping-entries
                +--rw mapping-entry* [policy-color]
                   +--rw policy-color     uint32
                   +--rw class-list?      string
                   +--rw is-as-default?   boolean
]]></artwork>
        </figure>
      </section>

      <section anchor="yang-code" numbered="true">
        <name>YANG Module</name>
        <t>This module augments the "ietf-sr-policy" YANG data model
        defined in <xref target="I-D.ietf-spring-sr-policy-yang"/> and
        imports the "ietf-routing" module defined in
        <xref target="RFC8349"/>.</t>

        <sourcecode name="ietf-sr-policy-group@2026-11-16.yang" type="yang" markers="true"><![CDATA[
module ietf-sr-policy-group {
  yang-version "1.1";
  namespace "urn:ietf:params:xml:ns:yang:ietf-sr-policy-group";
  prefix "sr-policy-group";

  import ietf-routing {
    prefix rt;
    reference
      "RFC 8349: A YANG Data Model for Routing Management
                 (NMDA Version)";
  }

  import ietf-sr-policy {
    prefix sr-policy;
    reference
      "RFC XXXX: YANG Data Model for Segment Routing Policy";
  }

  organization
    "IETF SPRING Working Group";

  contact
    "WG Web:   <https://datatracker.ietf.org/wg/spring/>
     WG List:  SPRING <mailto:spring@ietf.org>

     Author:   Liyan Gong
               <mailto:gongliyan@chinamobile.com>
     Author:   Changwang Lin
               <mailto:linchangwang.04414@h3c.com>
     Author:   Ran Chen
               <mailto:chen.ran@zte.com.cn>
     Author:   Haiyang Zhang
               <mailto:zhang.haiyangA@h3c.com>";

  description
    "This module describes a YANG model for configuring and managing
     SR Policy Groups.

     This YANG model conforms to the Network Management
     Datastore Architecture (NMDA) as described in RFC 8342.

     Copyright (c) 2026 IETF Trust and the persons identified as
     authors of the code.  All rights reserved.

     Redistribution and use in source and binary forms, with or
     without modification, is permitted pursuant to, and subject to
     the license terms contained in, the Revised BSD License set
     forth in Section 4.c of the IETF Trust's Legal Provisions
     Relating to IETF Documents
     (https://trustee.ietf.org/license-info).

     This version of this YANG module is part of RFC XXXX;
     see the RFC itself for full legal notices.

     The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
     NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
     'MAY', and 'OPTIONAL' in this document are to be interpreted as
     described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
     they appear in all capitals, as shown here.";

  revision 2026-11-16 {
    description
      "Initial revision.";
    reference
      "RFC XXXX: YANG Data Model for SR Policy Group";
  }

  typedef dataplane-type {
    type enumeration {
      enum mpls {
        value 1;
          description "Segment-routing MPLS";
      }
      enum srv6 {
        value 2;
          description "Segment-routing v6";
      }
    }
    description "Dataplane type of segment routing";
  }

  augment "/rt:routing/sr-policy:segment-routing"
        + "/sr-policy:traffic-engineering" {
    description
      "SR Policy Group augmentation to the segment routing traffic
       engineering model.";
    container sr-policy-groups {
      description
        "Configuration parameters of SR Policy Group.";
      list sr-policy-group {
        key "group-color";
        description
          "Each entry contains parameters for SR Policy Group
           identified by the 'group-color' key.";
        leaf group-color {
          type uint32 {
            range "1..4294967295";
          }
          mandatory true;
          description "Color associated with the policy group";
        }
        leaf name {
          type string {
            length "1..59";
          }
          description "SR Policy Group name";
        }
        leaf description {
          type string;
          description "Description of the policy group";
        }
        leaf service-distinguish-method {
          type enumeration {
            enum DSCP-based {
              value 1;
              description "Distinguish service type based on DSCP
                in the message";
            }
            enum dot1q-based {
              value 2;
              description "Distinguish service type based on dot1q";
            }
            enum ServiceClass-based {
              value 3;
              description "Distinguish service type based on service
                class";
            }
            enum None {
              value 4;
              description "Not configure service type recognition
                method";
            }
          }
          description "Service traffic steering methods within SR
            Policy Group";
        }
        container forward-based-dscp {
          description "parameters of DSCP based steering traffic
            for SR Policy Group";
          leaf best-effort-dscp-list-v4 {
            type string;
            description "DSCP values for IPv4 packets matching
              best-effort. It is a comma-separated list of DSCP
              values. Each item can be an individual DSCP value
              or a DSCP value range. Use a tilde (~) to separate
              the start and end DSCP values of a range.
              Example: 1,2,3,5~8.";
          }
          leaf best-effort-dscp-list-v6 {
            type string;
            description "DSCP values for IPv6 packets matching
              best-effort. It is a comma-separated list of DSCP
              values. Each item can be an individual DSCP value
              or a DSCP value range. Use a tilde (~) to separate
              the start and end DSCP values of a range.
              Example: 1,2,3,5~8.";
          }
          leaf dscp-mismatch-drop {
            type boolean;
            default "false";
            description "When all DSCP values configured for
              best effort forwarding and SR policy forwarding do
              not match, and no default forwarding path is
              specified, discard traffic.";
          }
          container dscp-color-mapping-entries {
            description "DSCP-color mapping table";
            list mapping-entry {
              key "policy-color dataplane";
              description "This table contains color-DSCP mappings
                for an SR Policy Group.";
              leaf policy-color {
                type uint32 {
                  range "1..4294967295";
                }
                mandatory true;
                description "Color associated with the policy
                  group";
              }
              leaf dataplane {
                type dataplane-type;
                mandatory true;
                description "The data plane type of the mapping
                  relationship between DSCP and color";
              }
              leaf dscp-list {
                type string;
                description "DSCP values for packets matching.
                  It is a comma-separated list of DSCP values.
                  Each item can be an individual DSCP value or
                  a DSCP value range. Use a tilde (~) to separate
                  the start and end DSCP values of a range.
                 Example: 1,2,3,5~8.";
              }
              leaf is-as-default {
                type boolean;
                default false;
                description "Whether to use the SR policy
                  with this color as the default policy for
                  packets";
              }
            }
          }
        }
        container forward-based-dot1q {
          description "parameters of dot1q based steering
            traffic for SR Policy Group";
          leaf best-effort-dot1q-list {
            type string;
            description "Dot1q values for packets matching
              best-effort. It is a comma-separated list of
              dot1q values. Each item can be an individual
              dot1q value or a dot1q value range. Use a
              tilde (~) to separate the start and end dot1q
              values of a range. Example: 1,2,3,5~8.";
          }
          leaf dot1q-mismatch-drop {
            type boolean;
            default "false";
            description "When all dot1q values configured
              for best effort forwarding and SR policy
              forwarding do not match, and no default
              forwarding path is specified, discard traffic.";
          }
          container dot1q-color-mapping-entries {
            description "Dot1q-color mapping table";
            list mapping-entry {
              key "policy-color";
              description "This table contains color-dot1q
                mappings for an SR Policy Group.";
              leaf policy-color {
                type uint32 {
                  range "1..4294967295";
                }
                mandatory true;
                description "Color associated with the policy
                  group";
              }
              leaf dot1q-list {
                type string;
                description "Dot1q values for packets
                  matching. It is a comma-separated list of
                  dot1q values. Each item can be an individual
                  dot1q value or a dot1q value range. Use a tilde
                  (~) to separate the start and end dot1q values
                  of a range. Example: 1,2,3,5~8.";
              }
              leaf is-as-default {
                type boolean;
                default false;
                description "Whether to use the SR policy
                  with this color as the default policy for
                  packets";
              }
            }
          }
        }
        container forward-based-serviceclass {
          description "parameters of service class based steering
            traffic for SR Policy Group";
          leaf best-effort-classlist {
            type string;
            description "Service class values for packets matching
              best-effort. It is a comma-separated list of
              service class values. Each item can be an
              individual service class value or a service
              class value range. Use a tilde (~) to separate
              the start and end service class values of a
              range. Example: 1,2,3,5~8.";
          }
          leaf class-mismatch-drop {
            type boolean;
            default "false";
            description "When all service class values configured
              for best effort forwarding and SR policy forwarding
              do not match, and no default forwarding path is
              specified, discard traffic.";
          }
          container class-color-mapping-entries {
            description "Serviceclass-color mapping table";
            list mapping-entry {
              key "policy-color";
              description "This table contains color-serviceclass
                mappings for an SR Policy Group.";
              leaf policy-color {
                type uint32 {
                  range "1..4294967295";
                }
                mandatory true;
                description "Color associated with the policy
                  group";
              }
              leaf class-list {
                type string;
                description "Service class values for packets
                  matching. It is a comma-separated list of
                  service class values. Each item can be an
                  individual service class value or a service
                  class value range. Use a tilde (~) to separate
                  the start and end service class values of
                  a range. Example: 1,2,3,5~8.";
              }
              leaf is-as-default {
                type boolean;
                default false;
                description "Whether to use the SR policy
                  with this color as the default policy for
                  packets";
              }
            }
          }
        }
      }
    } // sr-policy-groups
  } // augment
}
]]></sourcecode>
      </section>
    </section>

    <section anchor="security" numbered="true">
      <name>Security Considerations</name>
      <t>This section is modeled after the template described in
      Section 3.7.1 of <xref target="RFC9907"/>.</t>
      <t>The "ietf-sr-policy-group" YANG module defines a data model that
      is designed to be accessed via YANG-based management protocols,
      such as Network Configuration Protocol (NETCONF)
      <xref target="RFC6241"/> and RESTCONF <xref target="RFC8040"/>.
      These YANG-based management protocols (1) have to use a secure
      transport layer (e.g., Secure Shell (SSH) <xref target="RFC4252"/>,
      TLS <xref target="RFC9846"/>, and QUIC <xref target="RFC9000"/>)
      and (2) have to use mutual authentication.</t>
      <t>The Network Configuration Access Control Model (NACM)
      <xref target="RFC8341"/> provides the means to restrict access for
      particular NETCONF or RESTCONF users to a preconfigured subset of
      all available NETCONF or RESTCONF protocol operations and
      content.</t>
      <t>There are a number of data nodes defined in this YANG module
      that are writable/creatable/deletable (i.e., config true, which is
      the default). All writable data nodes are likely to be sensitive or
      vulnerable in some network environments. Write operations (e.g.,
      edit-config) and delete operations to these data nodes without
      proper protection or authentication can have a negative effect on
      network operations. The following subtrees and data nodes have
      particular sensitivities/vulnerabilities:</t>
      <artwork><![CDATA[
  rt:routing/sr-policy:segment-routing/sr-policy:traffic-engineering/
  sr-policy-group:sr-policy-groups

  rt:routing/sr-policy:segment-routing/sr-policy:traffic-engineering/
  sr-policy-group:sr-policy-groups/sr-policy-group:sr-policy-group/
  sr-policy-group:service-distinguish-method

  rt:routing/sr-policy:segment-routing/sr-policy:traffic-engineering/
  sr-policy-group:sr-policy-groups/sr-policy-group:sr-policy-group/
  sr-policy-group:forward-based-dscp

  rt:routing/sr-policy:segment-routing/sr-policy:traffic-engineering/
  sr-policy-group:sr-policy-groups/sr-policy-group:sr-policy-group/
  sr-policy-group:forward-based-dot1q

  rt:routing/sr-policy:segment-routing/sr-policy:traffic-engineering/
  sr-policy-group:sr-policy-groups/sr-policy-group:sr-policy-group/
  sr-policy-group:forward-based-serviceclass
]]></artwork>
      <t>An unauthorized modification of the SR Policy Group
      configuration, such as the mapping relationships between DSCP,
      dot1q, or service class values and SR Policy colors, could cause
      traffic to be steered onto unintended paths, disrupt services, or
      violate traffic segregation policies.</t>
      <t>This YANG module does not define any read-only data nodes
      (i.e., config false), RPC operations, or actions.</t>
    </section>

    <section anchor="iana" numbered="true">
      <name>IANA Considerations</name>
      <t>This document requests IANA to register the following URI in
      the "ns" registry within the "IETF XML Registry" group
      <xref target="RFC3688"/>:</t>
      <artwork><![CDATA[
   URI:  urn:ietf:params:xml:ns:yang:ietf-sr-policy-group
   Registrant Contact: The IESG.
   XML:  N/A, the requested URI is an XML namespace.
]]></artwork>
      <t>This document requests IANA to register the following YANG
      module in the "YANG Module Names" registry
      <xref target="RFC7950"/>:</t>
      <artwork><![CDATA[
   Name:         ietf-sr-policy-group
   Maintained by IANA? N
   Namespace:    urn:ietf:params:xml:ns:yang:ietf-sr-policy-group
   Prefix:       sr-policy-group
   Reference:    RFC XXXX
]]></artwork>
    </section>

  </middle>

  <back>
    <references>
      <name>References</name>

      <references anchor="normative">
        <name>Normative References</name>

        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author initials="S." surname="Bradner" fullname="S. Bradner"/>
            <date year="1997" month="March"/>
          </front>
            <seriesInfo name="BCP" value="14"/>
            <seriesInfo name="RFC" value="2119"/>
            <seriesInfo name="DOI" value="10.17487/RFC2119"/>
          
        </reference>

        <reference anchor="RFC3688" target="https://www.rfc-editor.org/info/rfc3688">
          <front>
            <title>The IETF XML Registry</title>
            <author initials="M." surname="Mealling" fullname="M. Mealling"/>
            <date year="2008" month="June"/>
          </front>
            <seriesInfo name="BCP" value="82"/>
            <seriesInfo name="RFC" value="3688"/>
            <seriesInfo name="DOI" value="10.17487/RFC3688"/>
        </reference>

        <reference anchor="RFC4252" target="https://www.rfc-editor.org/info/rfc4252">
          <front>
            <title>The Secure Shell (SSH) Authentication Protocol</title>
            <author initials="T." surname="Ylonen" fullname="T. Ylonen"/>
            <author initials="C." surname="Lonvick" fullname="C. Lonvick" role="editor"/>
            <date year="2006" month="January"/>
          </front>
            <seriesInfo name="RFC" value="4252"/>
            <seriesInfo name="DOI" value="10.17487/RFC4252"/>
        </reference>

        <reference anchor="RFC6241" target="https://www.rfc-editor.org/info/rfc6241">
          <front>
            <title>Network Configuration Protocol (NETCONF)</title>
            <author initials="R." surname="Enns" fullname="R. Enns"/>
            <author initials="M." surname="Bjorklund" fullname="M. Bjorklund"/>
            <author initials="J." surname="Schoenwaelder" fullname="J. Schoenwaelder"/>
            <author initials="A." surname="Bierman" fullname="A. Bierman"/>
            <date year="2011" month="June"/>
          </front>
            <seriesInfo name="RFC" value="6241"/>
            <seriesInfo name="DOI" value="10.17487/RFC6241"/>
          
        </reference>

        <reference anchor="RFC7950" target="https://www.rfc-editor.org/info/rfc7950">
          <front>
            <title>The YANG 1.1 Data Modeling Language</title>
            <author initials="M." surname="Bjorklund" fullname="M. Bjorklund"/>
            <date year="2016" month="August"/>
          </front>
            <seriesInfo name="RFC" value="7950"/>
            <seriesInfo name="DOI" value="10.17487/RFC7950"/>
          
        </reference>

        <reference anchor="RFC8040" target="https://www.rfc-editor.org/info/rfc8040">
          <front>
            <title>RESTCONF Protocol</title>
            <author initials="A." surname="Bierman" fullname="A. Bierman"/>
            <author initials="M." surname="Bjorklund" fullname="M. Bjorklund"/>
            <author initials="K." surname="Watsen" fullname="K. Watsen"/>
            <date year="2017" month="January"/>
          </front>
            <seriesInfo name="RFC" value="8040"/>
            <seriesInfo name="DOI" value="10.17487/RFC8040"/>
        </reference>

        <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author initials="B." surname="Leiba" fullname="B. Leiba"/>
            <date year="2017" month="May"/>
          </front>
            <seriesInfo name="BCP" value="14"/>
            <seriesInfo name="RFC" value="8174"/>
            <seriesInfo name="DOI" value="10.17487/RFC8174"/>
          
        </reference>

        <reference anchor="RFC8340" target="https://www.rfc-editor.org/info/rfc8340">
          <front>
            <title>YANG Tree Diagrams</title>
            <author initials="M." surname="Bjorklund" fullname="M. Bjorklund"/>
            <author initials="L." surname="Berger" fullname="L. Berger"/>
            <date year="2018" month="March"/>
          </front>
            <seriesInfo name="BCP" value="215"/>
            <seriesInfo name="RFC" value="8340"/>
            <seriesInfo name="DOI" value="10.17487/RFC8340"/>
          
        </reference>

        <reference anchor="RFC8341" target="https://www.rfc-editor.org/info/rfc8341">
          <front>
            <title>Network Configuration Access Control Model</title>
            <author initials="M." surname="Bierman" fullname="M. Bierman"/>
            <author initials="M." surname="Bjorklund" fullname="M. Bjorklund"/>
            <date year="2018" month="March"/>
          </front>
            <seriesInfo name="BCP" value="90"/>
            <seriesInfo name="RFC" value="8341"/>
            <seriesInfo name="DOI" value="10.17487/RFC8341"/>
        </reference>

        <reference anchor="RFC8349" target="https://www.rfc-editor.org/info/rfc8349">
          <front>
            <title>A YANG Data Model for Routing Management (NMDA Version)</title>
            <author initials="L." surname="Lhotka" fullname="L. Lhotka"/>
            <author initials="A." surname="Lindem" fullname="A. Lindem"/>
            <author initials="Y." surname="Qu" fullname="Y. Qu"/>
            <date year="2018" month="March"/>
          </front>
            <seriesInfo name="RFC" value="8349"/>
            <seriesInfo name="DOI" value="10.17487/RFC8349"/>
          
        </reference>

        <reference anchor="RFC8402" target="https://www.rfc-editor.org/info/rfc8402">
          <front>
            <title>Segment Routing Architecture</title>
            <author initials="C." surname="Filsfils" fullname="C. Filsfils"/>
            <author initials="S." surname="Previdi" fullname="S. Previdi"/>
            <author initials="L." surname="Ginsberg" fullname="L. Ginsberg"/>
            <author initials="B." surname="Decraene" fullname="B. Decraene"/>
            <author initials="S." surname="Litkowski" fullname="S. Litkowski"/>
            <author initials="R." surname="Shakir" fullname="R. Shakir"/>
            <date year="2018" month="July"/>
          </front>
            <seriesInfo name="RFC" value="8402"/>
            <seriesInfo name="DOI" value="10.17487/RFC8402"/>
          
        </reference>

        <reference anchor="RFC9000" target="https://www.rfc-editor.org/info/rfc9000">
          <front>
            <title>QUIC: A UDP-Based Multiplexed and Secure Transport</title>
            <author initials="J." surname="Iyengar" fullname="J. Iyengar" role="editor"/>
            <author initials="M." surname="Thomson" fullname="M. Thomson" role="editor"/>
            <date year="2021" month="May"/>
          </front>
            <seriesInfo name="RFC" value="9000"/>
            <seriesInfo name="DOI" value="10.17487/RFC9000"/>
        </reference>

        <reference anchor="RFC9256" target="https://www.rfc-editor.org/info/rfc9256">
          <front>
            <title>Segment Routing Policy Architecture</title>
            <author initials="C." surname="Filsfils" fullname="C. Filsfils"/>
            <author initials="K." surname="Talaulikar" fullname="K. Talaulikar"/>
            <author initials="D." surname="Voyer" fullname="D. Voyer"/>
            <author initials="A." surname="Bogdanov" fullname="A. Bogdanov"/>
            <author initials="P." surname="Mattes" fullname="P. Mattes"/>
            <date year="2022" month="July"/>
          </front>
            <seriesInfo name="RFC" value="9256"/>
            <seriesInfo name="DOI" value="10.17487/RFC9256"/>
          
        </reference>

        <reference anchor="RFC9846" target="https://www.rfc-editor.org/info/rfc9846">
          <front>
            <title>The Transport Layer Security (TLS) Protocol Version 1.3</title>
            <author initials="E." surname="Rescorla" fullname="E. Rescorla"/>
            <date year="2026" month="July"/>
          </front>
            <seriesInfo name="RFC" value="9846"/>
            <seriesInfo name="DOI" value="10.17487/RFC9846"/>
        </reference>

        <reference anchor="RFC9907" target="https://www.rfc-editor.org/info/rfc9907">
          <front>
            <title>Guidelines for Authors and Reviewers of Documents Containing YANG Data Models</title>
            <author initials="A." surname="Bierman" fullname="A. Bierman"/>
            <author initials="M." surname="Boucadair" fullname="M. Boucadair" role="editor"/>
            <author initials="Q." surname="Wu" fullname="Q. Wu"/>
            <date year="2026" month="March"/>
          </front>
            <seriesInfo name="BCP" value="216"/>
            <seriesInfo name="RFC" value="9907"/>
            <seriesInfo name="DOI" value="10.17487/RFC9907"/>
        </reference>

        <reference anchor="I-D.ietf-spring-sr-policy-yang">
          <front>
            <title>YANG Data Model for Segment Routing Policy</title>
            <author initials="T." surname="Saleh" fullname="Tarik Saleh" role="editor"/>
            <author initials="K." surname="Raza" fullname="Kamran Raza"/>
            <author initials="Z." surname="Shunwan" fullname="Zhuang Shunwan"/>
            <author initials="S." surname="Matsushima" fullname="Satoru Matsushima"/>
            <author initials="V." surname="Beeram" fullname="Vishnu Pavan Beeram"/>
            <date year="2026" month="November"/>
          </front>
            <seriesInfo name="Internet-Draft" value="draft-ietf-spring-sr-policy-yang-09"/>
        </reference>
      </references>

      <references anchor="informative">
        <name>Informative References</name>

        <reference anchor="I-D.ietf-spring-sr-policy-group">
          <front>
            <title>SR Policy Group</title>
            <author initials="W." surname="Cheng" fullname="Weiqiang Cheng"/>
            <author initials="W." surname="Jiang" fullname="Wenying Jiang"/>
            <author initials="C." surname="Lin" fullname="Changwang Lin"/>
            <author initials="R." surname="Chen" fullname="Ran Chen"/>
            <author initials="Y." surname="Zhang" fullname="YaWei Zhang"/>
            <date year="2026" month="August"/>
          </front>
            <seriesInfo name="Internet-Draft" value="draft-ietf-spring-sr-policy-group-01"/>
        </reference>
      </references>
    </references>
  </back>
</rfc>