<?xml version="1.0" encoding="iso-8859-1" ?>
<!--<!DOCTYPE rfc SYSTEM "rfc4748.dtd"> --> version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM 'rfc2629.dtd' [
    <!ENTITY rfc2629 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2629.xml'>
    <!ENTITY rfc2119 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
    <!ENTITY rfc5925 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5925.xml'>
    <!ENTITY rfc3618 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3618.xml'>
		<!ENTITY rfc8407 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8407.xml'>
		<!ENTITY rfc8342 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8342.xml'>
		<!ENTITY rfc6991 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.6991.xml'>
		<!ENTITY rfc8343 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8343.xml'>
		<!ENTITY rfc8344 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8344.xml'>
		<!ENTITY rfc8177 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8177.xml'>
    <!ENTITY rfc6241 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.6241.xml'>
    <!ENTITY rfc8040 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8040.xml'>
    <!ENTITY rfc6242 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.6242.xml'>
    <!ENTITY rfc8446 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8446.xml'>
    <!ENTITY rfc8341 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8341.xml'>
    <!ENTITY rfc6020 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.6020.xml'>
    <!ENTITY rfc3688 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3688.xml'>
	  <!ENTITY rfc7951 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.7951.xml'>
    <!ENTITY rfc7950 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.7950.xml'>
    <!ENTITY rfc8174 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8174.xml'>
		<!ENTITY rfc8294 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8294.xml'>
		<!ENTITY rfc8340 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8340.xml'>
    <!ENTITY rfc8349 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8349.xml'>
    <!ENTITY rfc8519 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8519.xml'>
		<!ENTITY rfc8639 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8639.xml'>
		<!ENTITY rfc8641 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8641.xml'>
		<!ENTITY rfc4271 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4271.xml'>
    <!ENTITY rfc7761 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.7761.xml'>
    <!ENTITY I-D.ietf-pim-yang PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-pim-yang.xml'>
		]>

<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>

<?rfc toc="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc disable-output-escaping="yes"?> "rfc2629-xhtml.ent">

<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std"
     docName="draft-ietf-pim-msdp-yang-18"
     ipr="trust200902"> number="8916" ipr="trust200902"
     obsoletes="" updates="" submissionType="IETF" consensus="true"
     xml:lang="en" tocInclude="true" symRefs="true" sortRefs="true"
     version="3">

  <!-- ***** FRONT MATTER ***** xml2rfc v2v3 conversion 2.45.3 -->
  <front>
    <title abbrev="MSDP YANG Data Model">A YANG Data Model for the Multicast Source Discovery Protocol (MSDP)</title>

    <seriesInfo name="RFC" value="8916"/>
    <author fullname="Xufeng Liu" initials="X" surname="Liu">
      <organization>Volta Networks</organization>
      <address>
        <postal>
          <street></street>
          <city></city>
          <code></code>
          <country></country>
          <street/>
          <city/>
          <code/>
          <country/>
        </postal>
        <email>xufeng.liu.ietf@gmail.com</email>
      </address>
    </author>
    <author fullname="Zheng Zhang" initials="Z" role="editor" surname="Zhang">
      <organization>ZTE Corporation</organization>
      <address>
        <postal>
          <street>No. 50 Software Ave, Avenue, Yuhuatai Distinct</street> District</street>
          <city>Nanjing</city>

          <region></region>

          <code></code>
          <region/>
          <code/>
          <country>China</country>
        </postal>

        <email>zzhang_ietf@hotmail.com</email>
        <email>zhang.zheng@zte.com.cn</email>
      </address>
    </author>
    <author fullname="Anish Peter" initials="A" surname="Peter">
      <organization>Individual contributor</organization> Contributor</organization>
      <address>
        <postal>
          <street></street>

          <city></city>

          <region></region>

          <code></code>

          <country></country>
          <street/>
          <city/>
          <region/>
          <code/>
          <country/>
        </postal>
        <email>anish.ietf@gmail.com</email>
      </address>
    </author>
    <author fullname="Mahesh Sivakumar" initials="M" surname="Sivakumar">
      <organization>Juniper networks</organization> Networks</organization>
      <address>
        <postal>
          <street>1133 Innovation Way</street>

          <city>Sunnyvale, CALIFORNIA 94089</city>

          <region></region>

          <code></code>

          <country>USA</country>
          <city>Sunnyvale</city>
          <region>CA</region>
          <code>94089</code>
          <country>United States of America</country>
        </postal>
        <email>sivakumar.mahesh@gmail.com</email>
      </address>
    </author>
    <author fullname="Feng Guo" initials="F" surname="Guo">
      <organization>Huawei Technologies</organization>
      <address>
        <postal>
          <street>Huawei Bld., No.156 Bldg., No. 156 Beiqing Rd.</street>

          <city>Beijing  100095</city>

          <region></region>

          <code></code>
          <city>Beijing</city>
          <region/>
          <code>100095</code>
          <country>China</country>
        </postal>
        <email>guofeng@huawei.com</email>
      </address>
    </author>
    <author fullname="Pete McAllister" initials="P" surname="McAllister">
      <organization>Metaswitch Networks</organization>
      <address>
        <postal>
          <street>100 Church Street</street>

          <city>Enfield  EN2 6BQ</city>
          <city>Enfield</city>
          <region></region>

          <code></code>

          <country>UK</country>
          <code>EN2 6BQ</code>
          <country>United Kingdom</country>
        </postal>
        <email>pete.mcallister@metaswitch.com</email>
      </address>
    </author>
    <date month="October" year="2020"/>
    <area>Routing</area>
    <workgroup>PIM WG</workgroup>
    <keyword>MSDP, YANG</keyword>
    <keyword>MSDP</keyword>
    <keyword>YANG</keyword>
    <abstract>
      <t>
       This document defines a YANG data model for the configuration and
       management of Multicast Source Discovery Protocol (MSDP) Protocol. protocol
       operations.
      </t>
    </abstract>
  </front>

  <!-- ***** MIDDLE MATTER ***** -->

  <middle>
    <section title="Introduction"> numbered="true" toc="default">
      <name>Introduction</name>
      <t><xref target="RFC3618"/> target="RFC3618" format="default"/> introduces the protocol
      definition of MSDP. the Multicast Source Discovery Protocol (MSDP).
          This document defines a YANG data model that can be used to configure
          and manage the MSDP protocol. protocol operations. The operational state data and
          statistics can also be retrieved by this model.
      </t>
      <t>
        This model is designed to be used along with other multicast
        YANG data models such as PIM <xref target="I-D.ietf-pim-yang"/>, target="PIM-YANG" format="default"/>, which are not covered in this document.
      </t>
      <section title="Terminology"> numbered="true" toc="default">
        <name>Terminology</name>
        <t>The terminology for describing YANG data models is found in
        <xref target="RFC6020"/> target="RFC6020" format="default"/> and <xref target="RFC7950"/>, target="RFC7950" format="default"/>, including:</t>
	<t>
     <list style="symbols">
	<t>action</t>
  <t>augment</t>
  <t>container</t>
  <t>choice</t>
	<t>data model</t>
	<t>data node</t>
  <t>grouping</t>
	<t>identity</t>
  <t>leaf</t>
  <t>list</t>
	<t>module</t>
  <t>uses</t>
	  </list>
	</t>
        <ul spacing="normal">
          <li>action</li>
          <li>augment</li>
          <li>choice</li>
          <li>container</li>
          <li>data model</li>
          <li>data node</li>
          <li>grouping</li>
          <li>identity</li>
          <li>leaf</li>
          <li>list</li>
          <li>module</li>
          <li>uses</li>
        </ul>
        <t>The following abbreviations are used in this document and the defined
    model:</t>
        <t>MSDP: Multicast Source Discovery Protocol <xref target="RFC3618"/>.</t> target="RFC3618" format="default"/></t>
        <t>RP: Rendezvous Point <xref target="RFC7761"/></t> target="RFC7761" format="default"/></t>
        <t>RPF: Reverse Path Forwarding <xref target="RFC7761"/></t> target="RFC7761" format="default"/></t>
        <t>SA: Source-Active <xref target="RFC3618"/>.</t> target="RFC3618" format="default"/></t>
      </section>
      <section title="Conventions numbered="true" toc="default">
        <name>Conventions Used in This Document"> Document</name>
       <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
       "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>",
       "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>",
       "<bcp14>SHOULD NOT</bcp14>",
       "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
       "<bcp14>MAY</bcp14>", and
   "OPTIONAL" "<bcp14>OPTIONAL</bcp14>" in this document
       are to be interpreted as described in
   BCP 14 BCP&nbsp;14
       <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only
       when, they appear in all capitals, as shown here.</t>
      </section>
      <section title="Tree Diagrams"> numbered="true" toc="default">
        <name>Tree Diagrams</name>
        <t>Tree diagrams used in this document follow the notation defined in
           <xref target="RFC8340"/>.</t> target="RFC8340" format="default"/>.</t>
      </section>
      <section title="Prefixes numbered="true" toc="default">
        <name>Prefixes in Data Node Names"> 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 Table 1.</t>

    <texttable <xref target="TABLE_1"/>.</t>
        <table anchor="TABLE_1" title="">

     <ttcol align="left">Prefix</ttcol>
     <ttcol align="center">
          <thead>
            <tr>
              <th align="left">Prefix</th>
              <th align="left">YANG module</ttcol>
     <ttcol align="left">Reference</ttcol>

     <c>yang</c>
     <c>ietf-yang-types</c>
     <c><xref target="RFC6991"/></c>

     <c>inet</c>
     <c>ietf-inet-types</c>
     <c><xref target="RFC6991"/></c>

     <c>rt</c>
     <c>ietf-routing</c>
     <c><xref target="RFC8349"/></c>

     <c>if</c>
     <c>ietf-interfaces</c>
     <c><xref target="RFC8343"/></c>

     <c>ip</c>
     <c>ietf-ip</c>
     <c><xref target="RFC8344"/></c>

     <c>key-chain</c>
     <c>ietf-key-chain</c>
     <c><xref target="RFC8177"/></c>

     <c>rt-types</c>
     <c>ietf-routing-types</c>
     <c><xref target="RFC8294"/></c>

     <c>acl</c>
     <c>ietf-access-control-list</c>
     <c><xref target="RFC8519"/></c>
	</texttable> module</th>
              <th align="left">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">yang</td>
              <td align="left">ietf-yang-types</td>
              <td align="left">
                <xref target="RFC6991" format="default"/></td>
            </tr>
            <tr>
              <td align="left">inet</td>
              <td align="left">ietf-inet-types</td>
              <td align="left">
                <xref target="RFC6991" format="default"/></td>
            </tr>
            <tr>
              <td align="left">rt</td>
              <td align="left">ietf-routing</td>
              <td align="left">
                <xref target="RFC8349" format="default"/></td>
            </tr>
            <tr>
              <td align="left">if</td>
              <td align="left">ietf-interfaces</td>
              <td align="left">
                <xref target="RFC8343" format="default"/></td>
            </tr>
            <tr>
              <td align="left">ip</td>
              <td align="left">ietf-ip</td>
              <td align="left">
                <xref target="RFC8344" format="default"/></td>
            </tr>
            <tr>
              <td align="left">key-chain</td>
              <td align="left">ietf-key-chain</td>
              <td align="left">
                <xref target="RFC8177" format="default"/></td>
            </tr>
            <tr>
              <td align="left">rt-types</td>
              <td align="left">ietf-routing-types</td>
              <td align="left">
                <xref target="RFC8294" format="default"/></td>
            </tr>
            <tr>
              <td align="left">acl</td>
              <td align="left">ietf-access-control-list</td>
              <td align="left">
                <xref target="RFC8519" format="default"/></td>
            </tr>
          </tbody>
        </table>
      </section>
    </section>
    <section title="Design numbered="true" toc="default">
      <name>Design of the Data Model"> Model</name>
      <section title="Scope numbered="true" toc="default">
        <name>Scope of Model"> Model</name>
        <t>The model covers MSDP <xref target="RFC3618"/>.</t> target="RFC3618" format="default"/>.</t>
        <t>This model can be used to configure and manage the MSDP protocol. protocol operations.  The operational state data and statistics
   can be retrieved by this model.  Even though no protocol-specific
   notifications are defined in this model, the subscription and push
   mechanism
   mechanisms, as defined in <xref target="RFC8639"/> target="RFC8639" format="default"/>
   and <xref target="RFC8641"/> target="RFC8641" format="default"/>, can be implemented by
   the user to subscribe to notifications on the data nodes in this
   model.</t>
        <t>The model contains all the basic configuration parameters to operate
   the protocol.  Depending on the implementation choices,
   some systems may not allow some of the advanced parameters to be
   configurable.  The occasionally implemented parameters are modeled as
   optional features in this model.
   This model can be extended, and it has been structured in a way that
   such extensions can be conveniently made.</t>
      </section>
      <section title="Specification"> numbered="true" toc="default">
        <name>Specification</name>
        <t>
           The configuration data nodes cover global
       configuration attributes and per peer per-peer configuration
       attributes. The state data nodes include global, per peer, per-peer,
       and source-active SA information. The container "msdp" is the
       top level
       top-level container in this data model.  The presence of
       this container is expected to enable MSDP protocol functionality.
       No notification is defined in this model.</t>
      </section>
    </section>
    <section title="Module Structure"> numbered="true" toc="default">
      <name>Module Structure</name>
      <t>
       This model imports and augments the ietf-routing "ietf-routing" YANG data model
       defined in <xref target="RFC8349"/>. target="RFC8349" format="default"/>.  Both configuration
       data nodes and state data nodes of as mentioned in <xref target="RFC8349"/> target="RFC8349" format="default"/>
       are augmented.
      </t>
      <t>The YANG data model defined in this document conforms to the Network
   Management Datastore Architecture (NMDA) <xref target="RFC8342"/>. target="RFC8342" format="default"/>.
   The operational state data is combined with the associated configuration
   data in the same hierarchy <xref target="RFC8407"/>.</t>

   <figure align="center">
     <artwork align="center"><![CDATA[ target="RFC8407" format="default"/>.</t>

      <sourcecode type="yangtree"><![CDATA[
module: ietf-msdp
  augment /rt:routing/rt:control-plane-protocols
            /rt:control-plane-protocol:
    +--rw msdp
       +--rw global
       |  +--rw tcp-connection-source?   if:interface-ref
       |  +--rw default-peer* [peer-addr prefix-policy]
                              {filter-policy}?
       |  |  +--rw peer-addr        -> ../../../peers/peer/address
       |  |  +--rw prefix-policy    -> /acl:acls/acl/name
       |  +--rw originating-rp
       |  |  +--rw interface?   if:interface-ref
       |  +--rw sa-filter
       |  |  +--rw in?    -> /acl:acls/acl/name
       |  |  +--rw out?   -> /acl:acls/acl/name
       |  +--rw sa-limit?                uint32
       |  +--rw ttl-threshold?           uint8
       +--rw peers
       |  +--rw peer* [address]
       |     +--rw address                  inet:ipv4-address
       |     +---x clear-peer
       |     +--rw authentication {peer-authentication}?
       |     |  +--rw (authentication-type)?
       |     |     +--:(key-chain)
       |     |     |  +--rw key-chain?
                              key-chain:key-chain-ref
       |     |     +--:(password)
       |     |        +--rw key?                string
       |     |        +--rw crypto-algorithm?   identityref
       |     +--rw enabled?                 boolean
       |     +--rw tcp-connection-source?   if:interface-ref
       |     +--rw description?             string
       |     +--rw mesh-group?              string
       |     +--rw peer-as?                 inet:as-number
                                            {peer-as-verification}?
       |     +--rw sa-filter
       |     |  +--rw in?    -> /acl:acls/acl/name
       |     |  +--rw out?   -> /acl:acls/acl/name
       |     +--rw sa-limit?                uint32
       |     +--rw timer
       |     |  +--rw connect-retry-interval?   uint16
       |     |  +--rw holdtime-interval?        uint16
       |     |  +--rw keepalive-interval?       uint16
       |     +--rw ttl-threshold?           uint8
       |     +--ro session-state?           enumeration
       |     +--ro elapsed-time?            yang:gauge32
       |     +--ro connect-retry-expire?    uint32
       |     +--ro hold-expire?             uint16
       |     +--ro is-default-peer?         boolean
       |     +--ro keepalive-expire?        uint16
       |     +--ro reset-count?             yang:zero-based-counter32
       |     +--ro statistics
       |        +--ro discontinuity-time?   yang:date-and-time
       |        +--ro error
       |        |  +--ro rpf-failure?   uint32
       |        +--ro queue
       |        |  +--ro size-in?    uint32
       |        |  +--ro size-out?   uint32
       |        +--ro received
       |        |  +--ro keepalive?      yang:counter64
       |        |  +--ro notification?   yang:counter64
       |        |  +--ro sa-message?     yang:counter64
       |        |  +--ro sa-response?    yang:counter64
       |        |  +--ro sa-request?     yang:counter64
       |        |  +--ro total?          yang:counter64
       |        +--ro sent
       |           +--ro keepalive?      yang:counter64
       |           +--ro notification?   yang:counter64
       |           +--ro sa-message?     yang:counter64
       |           +--ro sa-response?    yang:counter64
       |           +--ro sa-request?     yang:counter64
       |           +--ro total?          yang:counter64
       +---x clear-all-peers
       +--ro sa-cache
          +--ro entry* [group source-addr]
          |  +--ro group
                     rt-types:ipv4-multicast-group-address
          |  +--ro source-addr
                     rt-types:ipv4-multicast-source-address
          |  +--ro origin-rp* [rp-address]
          |  |  +--ro rp-address       inet:ipv4-address
          |  |  +--ro is-local-rp?     boolean
          |  |  +--ro sa-adv-expire?   uint32
          |  +--ro state-attributes
          |     +--ro up-time?             yang:gauge32
          |     +--ro expire?              yang:gauge32
          |     +--ro holddown-interval?   uint32
          |     +--ro peer-learned-from?   inet:ipv4-address
          |     +--ro rpf-peer?            inet:ipv4-address
          +---x clear
             +---w input
                +---w entry!
                |  +---w group
                           rt-types:ipv4-multicast-group-address
                |  +---w source-addr?
                           rt-types:ipv4-multicast-source-address
                +---w peer-address?   inet:ipv4-address
                +---w peer-as?        inet:as-number
            ]]></artwork>
       <postamble></postamble>
      </figure>        inet:as-number]]></sourcecode>
      <section title="MSDP Configuration"> numbered="true" toc="default">
        <name>MSDP Configuration</name>
        <t>
      MSDP operation requires configuration information that is distributed
      amongst several peers.  Several peers may
   be configured in a mesh-group.  The Source-Active SA information may be filtered
   by peers.</t>
        <t>The configuration modeling branch is composed of MSDP global and
      peer configurations.
   The
   These two parts are the most important parts of MSDP.</t>
        <t>Besides the fundamental features of MSDP protocol, MSDP, several optional features
   are included in the model. These features help the control of MSDP protocol. MSDP.
   The peer features and SA features make the deployment and control easier. The
   connection parameters can be used to control the TCP connection because MSDP
   protocol
   is based on TCP. The authentication features make the protocol more
   secure. The filter features selectively allow operators to prevent SA information
   from being forwarded to peers.</t>
      </section>
      <section title="MSDP State"> numbered="true" toc="default">
        <name>MSDP States</name>
        <t>MSDP states are composed of the MSDP global state, the MSDP peer state, statistics
	information
        information, and SA cache information. The statistics information and SA cache
        information helps help the operator to retrieve data regarding the protocol protocol's condition.</t>
        <t>YANG actions are defined to clear the connection of one specific MSDP peer,
    clear the connections of all MSDP peers, or clear some or all of the SA caches.</t>
      </section>
    </section>
    <section title="MSDP numbered="true" toc="default">
      <name>MSDP YANG Model"> Data Model</name>
      <t>This module references <xref target="RFC3618"/>, target="RFC3618" format="default"/>, <xref target="RFC4271"/>, target="RFC4271" format="default"/>,
  <xref target="RFC5925"/>, target="RFC5925" format="default"/>, <xref target="RFC6991"/>, target="RFC6991" format="default"/>, <xref target="RFC7761"/>, target="RFC7761" format="default"/>,
        <xref target="RFC8177"/>, target="RFC8177" format="default"/>, <xref target="RFC8294"/>, target="RFC8294" format="default"/>, <xref target="RFC8343"/>, target="RFC8343" format="default"/>,
  <xref target="RFC8344"/>, target="RFC8344" format="default"/>, <xref target="RFC8349"/>, target="RFC8349"
  format="default"/>, and <xref target="RFC8519"/>.</t>

  <figure align="center">
    <artwork align="center"><![CDATA[
<CODE BEGINS> file "ietf-msdp@2020-04-15.yang" target="RFC8519" format="default"/>.</t>

      <sourcecode name="ietf-msdp@2020-09-15.yang" type="yang" markers="true"><![CDATA[
module ietf-msdp {

  yang-version 1.1;

  namespace "urn:ietf:params:xml:ns:yang:ietf-msdp";
  prefix msdp;

  import ietf-yang-types {
    prefix "yang";
    reference
      "RFC 6991: Common YANG Data Types";
  }

  import ietf-inet-types {
    prefix "inet";
    reference
      "RFC 6991: Common YANG Data Types";
  }

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

  import ietf-interfaces {
    prefix "if";
    reference
      "RFC 8343: A YANG Data Model for Interface Management";
  }

  import ietf-ip {
    prefix "ip";
    reference
      "RFC 8344: A YANG Data Model for IP Management";
  }

  import ietf-key-chain {
    prefix "key-chain";
    reference
      "RFC 8177: YANG Data Model for Key Chains";
  }

  import ietf-routing-types {
    prefix "rt-types";
    reference
      "RFC 8294: Common YANG Data Types for the Routing Area";
  }

  import ietf-access-control-list {
    prefix acl;
    reference
      "RFC 8519: YANG Data Model for Network Access Control Lists
       (ACLs)";
  }

  organization
    "IETF PIM (Protocols Protocols for IP Multicast) Multicast (pim) Working Group";

  contact
    "WG Web:   <http://tools.ietf.org/wg/pim/>   <https://datatracker.ietf.org/wg/pim/>
     WG List:  <mailto:pim@ietf.org>

     Editor:   Xufeng Liu
               <mailto:xufeng.liu.ietf@gmail.com>

     Editor:   Zheng Zhang
               <mailto:zzhang_ietf@hotmail.com>
               <mailto:zhang.zheng@zte.com.cn>

     Editor:   Anish Peter
               <mailto:anish.ietf@gmail.com>

     Editor:   Mahesh Sivakumar
               <mailto:sivakumar.mahesh@gmail.com>

     Editor:   Feng Guo
               <mailto:guofeng@huawei.com>

     Editor:   Pete McAllister
               <mailto:pete.mcallister@metaswitch.com>";

  // RFC Ed.: replace XXXX with actual RFC number and remove
  // this note

  description
    "The
    "This module defines the YANG data model definitions for the
     Multicast Source Discovery Protocol (MSDP).

     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.

     Copyright (c) 2020 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 Simplified 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
     (https://www.rfc-editor.org/info/rfcXXXX); 8916; 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."; notices.";

  revision 2020-04-15 2020-09-15 {
    description
      "Initial revision.";
    reference
      "RFC XXXX: 8916: A YANG Data Model for MSDP."; the Multicast Source
       Discovery Protocol (MSDP)";
  }

  /*
   * Features
   */

  feature filter-policy {
    description
      "Support policy configuration of peer/message filtering.";
    reference
      "RFC 8519: YANG Data Model for Network Access Control
       Lists (ACLs)";
  }

  feature peer-as-verification {
    description
      "Support configuration of peer AS number."; a peer's Autonomous System Number
       (ASN).";
    reference
      "RFC 4271: A Border Gateway Protocol 4 (BGP-4)";
  }

  feature peer-authentication {
    description
      "Support configuration of peer authentication.";
    reference
      "RFC 8177: YANG Data Model for Key Chains."; Chains";
  }

  /*
   * Identities
   */

  identity msdp {
    base rt:control-plane-protocol;
    description
      "Identity for the Multicast Source Discovery Protocol (MSDP).";
    reference
      "RFC 3618: Multicast Source Discovery Protocol (MSDP)";
  }

  /*
   * Groupings
   */
  grouping authentication-container {
    description
      "Authentication attributes.";
    container authentication {
      if-feature peer-authentication;
      description
        "A container defining authentication attributes.";
      choice authentication-type {
        case key-chain {
          leaf key-chain {
            type key-chain:key-chain-ref;
            description
              "Reference to a key-chain.";
            reference
              "RFC 8177: YANG Data Model for Key Chains."; Chains";
          }
        }
        case password {
          leaf key {
            type string;
            description
              "This leaf specifies the authentication key.";
          }
          leaf crypto-algorithm {
            type identityref {
              base key-chain:crypto-algorithm;
            }
            must "derived-from-or-self(., 'key-chain:md5')" {
              error-message
                "Only the md5 algorithm can be used for MSDP.";
              description
                "Check for crypto-algorithm.";
            }
            description
              "Cryptographic algorithm associated with a key.
               Only the md5 algorithm can be used for MSDP.
               When 'md5' is specified, MSDP control messages
               are secured by TCP MD5 signatures as described
               in RFC RFCs 3618 and RFC 5925.  Both peers of a
               connection SHOULD be configured to the same
               algorithm for the connection to be established.
               When this leaf is not configured, unauthenticated
               TCP is used.";
            reference
              "RFC 3618: Multicast Source Discovery Protocol (MSDP)
               RFC 5925: The TCP Authentication Option
               RFC 8177: YANG Data Model for Key Chains.
               RFC 5925: The TCP Authentication Option."; Chains";
          }
        }
        description
          "Choice of authentication.";
      }
    }
  } // authentication-container

  grouping tcp-connect-source {
    description
      "Attribute to configure a peer TCP connection source.";
    leaf tcp-connection-source {
      type if:interface-ref;
      must "/if:interfaces/if:interface[if:name = current()]/"
         + "ip:ipv4/ip:enabled != 'false'" {
        error-message
          "The interface must have IPv4 enabled.";
        description
          "The interface must have IPv4 enabled.";
        reference
          "RFC 8343: A YANG Data Model for Interface Management";
      }
      description
        "The interface is to be the source for the TCP
         connection.  It is a reference to an entry in the global
         interface list.";
    }
  } // tcp-connect-source

  grouping global-config-attributes {
    description
      "Global MSDP configuration.";

    uses tcp-connect-source;

    list default-peer {
      if-feature filter-policy;
      key "peer-addr prefix-policy";

      description
        "The default peer accepts all MSDP SA Source-Active (SA)
         messages.  A default peer is needed in topologies where
         MSDP peers do not coexist with BGP peers.  The reverse path
         forwarding Reverse Path
         Forwarding (RPF) check on SA messages will fail, and no
         SA messages will be accepted.  In these cases, you can
         configure the peer as a default peer and bypass
         RPF checks.";

      leaf peer-addr {
        type leafref {
          path "../../../peers/peer/address";
        }
        mandatory true;
        description
          "Reference to a peer that is in the peer list.";
      }
      leaf prefix-policy {
        type leafref {
          path "/acl:acls/acl:acl/acl:name";
        }
        description
          "If specified, only those SA entries whose RP Rendezvous
           Point (RP) is permitted in the prefix list are allowed;
           if not specified, all SA messages from the default
           peer are accepted.";
        reference
          "RFC 7761: Protocol Independent Multicast - Sparse Mode
           (PIM-SM): Protocol Specification (Revised)
           RFC 8519: YANG Data Model for Network Access Control
           Lists (ACLs)";
      }
    } // default-peer

    container originating-rp {
      description
        "The container of Originating the originating RP.";
      leaf interface {
        type if:interface-ref;
        must "/if:interfaces/if:interface[if:name = current()]/"
           + "ip:ipv4/ip:enabled != 'false'" {
          error-message
            "The interface must have IPv4 enabled.";
          description
            "The interface must have IPv4 enabled.";
          reference
            "RFC 8343: A YANG Data Model for Interface Management";
        }
        description
          "Reference to an entry in the global interface list.
           The IP address of the interface used in the RP field of
           an SA message entry.  When Anycast anycast RPs are used, all RPs
           use the same IP address.  This parameter can be used to
           define a unique IP address for the RP of each MSDP peer.
           By default, the software uses the RP address of the
           local system.";
      }
    } // originating-rp

    uses sa-filter-container;

    leaf sa-limit {
      type uint32;
      description
        "A limit on the number of SA entries accepted.
         By default,
         If not configured or the value is 0, there is no limit.";
    }
    uses ttl-threshold;
  } // global-config-attributes

  grouping peer-config-attributes {
    description "Per peer
      "Per-peer configuration for MSDP.";

    uses authentication-container;
    leaf enabled {
      type boolean;
      description
        "'true' if the peer is enabled;
         'false' if the peer is disabled.";
    }
    uses tcp-connect-source;

    leaf description {
      type string;
      description
        "The peer description.";
    }
    leaf mesh-group {
      type string;
      description
        "The name of the mesh-group to which this peer belongs to."; belongs.";
      reference
        "RFC 3618: Multicast Source Discovery Protocol (MSDP),
                   section 10.2.";
                   Section 10.2";
    }
    leaf peer-as {
      if-feature peer-as-verification;
      type inet:as-number;
      description
        "Peer's autonomous system number (ASN).
        "The peer's ASN.  Using peer-as to
         do perform the verification
         can provide more controlled ability.  The value can be
         compared with the BGP peer AS. peer's ASN.  If they are different,
         the SA information that comes from this peer may be
         rejected.  If the AS number ASN is the same as the local AS, ASN, then
         the peer is within the same domain; otherwise, this peer
         is external to the domain. Like  This is comparable to the
         definition and usage in BGP."; BGP; see RFC 4271.";
      reference
        "RFC 4271: A Border Gateway Protocol 4 (BGP-4)";
    }
    uses sa-filter-container;
    leaf sa-limit {
      type uint32;
      description
        "A limit on the number of SA entries accepted from this
         peer. By default,
         If not configured or the value is 0, there is no limit.";
    }
    container timer {
      description
        "Timer attributes.";
      reference
        "RFC 3618: Multicast Source Discovery Protocol (MSDP),
                   section 5.";
                   Section 5";
      leaf connect-retry-interval {
        type uint16;
        units seconds;
        default 30;
        description "Peer
          "The peer timer for connect-retry.  By default, MSDP peers
           wait 30 seconds after the session is reset.";
      }
      leaf holdtime-interval {
        type uint16 {
          range "3..65535";
        }
        units seconds;
        default 75;
        description
          "The SA hold down hold-down period of this MSDP peer.";
      }
      leaf keepalive-interval {
        type uint16 {
            range "1..65535";
        }
        units seconds;
        must '. < ../holdtime-interval' {
          error-message
            "The keepalive interval must be smaller than the
             hold time interval"; "
          + "hold-time interval.";
        }
        default 60;
        description
          "The keepalive timer of this MSDP peer.";
      }
    } // timer
    uses ttl-threshold;
  } // peer-config-attributes

  grouping peer-state-attributes {
    description "Per peer
      "Per-peer state attributes for MSDP.";

    leaf session-state {
      type enumeration {
        enum disabled  {
          description
            "Disabled.";
        }
        enum inactive {
          description
            "Inactive.";
        }
        enum listen {
          description
            "Listen.";
        }
        enum connecting {
          description
            "Connecting.";
        }
        enum established {
          description
            "Established.";
        }
      }
      config false;
      description
        "Peer
        "The peer's session state.";
      reference
        "RFC 3618: Multicast Source Discovery Protocol (MSDP),
                   section 11.";
                   Section 11";
    }
    leaf elapsed-time {
      type yang:gauge32;
      units seconds;
      config false;
      description
        "Elapsed time for being in a state.";
    }
    leaf connect-retry-expire {
      type uint32;
      units seconds;
      config false;
      description
        "Connect retry expire time of a peer connection.";
    }
    leaf hold-expire {
      type uint16;
      units seconds;
      config false;
      description
        "Hold expire time of a peer connection.";
    }
    leaf is-default-peer {
      type boolean;
      config false;
      description
        "'true' if this peer is one of the default peer."; peers.";
    }
    leaf keepalive-expire {
      type uint16;
      units seconds;
      config false;
      description
        "Keepalive expire time of this peer.";
    }
    leaf reset-count {
      type yang:zero-based-counter32;
      config false;
      description
        "The reset count of this peer.";
    }

    container statistics {
      config false;
      description
        "A container defining statistics attributes.";

      leaf discontinuity-time {
        type yang:date-and-time;
        description
          "The time on the most recent occasion at which any one
           or more of the statistic statistics counters suffered a
           discontinuity.  If no such discontinuities have occurred
           since the last re-initialization of the local
           management subsystem, then this node contains the time
           the local management subsystem re-initialized itself.";
      }

      container error {
        description
          "A grouping defining error statistics attributes.";
        leaf rpf-failure {
          type uint32;
          description "Number
            "The number of RPF failures.";
        }
      }

      container queue {
        description
          "A container that includes queue statistics attributes.";
        leaf size-in {
          type uint32;
          description
            "The number of messages received from the peer
             currently queued.";
        }
        leaf size-out {
          type uint32;
          description
            "The number of messages queued to be sent to the peer.";
        }
      }

      container received {
        description
          "Received message counters.";
        uses statistics-sent-received;
      }
      container sent {
        description
          "Sent message counters.";
        uses statistics-sent-received;
      }
    } // statistics
  } // peer-state-attributes

  grouping sa-filter-container {
    description
      "A container defining SA filters.";
    container sa-filter {
      description
        "Specifies an access control list Access Control List (ACL) to filter source
         active (SA) SA messages
         coming in to into or going out of the peer.";
      leaf in {
        type leafref {
          path "/acl:acls/acl:acl/acl:name";
        }
        description
          "Filters incoming SA messages only.
           The value is the name to uniquely identify a
           policy that contains one or more rules used to
           accept or reject MSDP SA messages.
           If the policy is not specified, all MSDP SA messages are
           accepted.";
        reference
          "RFC 8519: YANG Data Model for Network Access Control
           Lists (ACLs)";
      }
      leaf out {
        type leafref {
          path "/acl:acls/acl:acl/acl:name";
        }
        description
          "Filters outgoing SA messages only.
           The value is the name to uniquely identify a
           policy that contains one or more rules used to
           accept or reject MSDP SA messages.
           If the policy is not specified, all MSDP SA messages are
           sent.";
        reference
          "RFC 8519: YANG Data Model for Network Access Control
           Lists (ACLs)";
      }
    } // sa-filter
  } // sa-filter-container

  grouping ttl-threshold {
    description
      "Attribute to configure the TTL threshold.";
    leaf ttl-threshold {
      type uint8 {
        range 1..255;
      }
      description "Maximum
        "The maximum number of hops data packets can traverse
         before being dropped.";
    }
  } // ttl-threshold

  grouping statistics-sent-received {
    description
      "A grouping defining sent and received statistics attributes.";
    leaf keepalive {
      type yang:counter64;
      description
        "The number of keepalive messages.";
    }
    leaf notification {
      type yang:counter64;
      description
        "The number of notification messages.";
    }
    leaf sa-message {
      type yang:counter64;
      description
        "The number of SA messages.";
    }
    leaf sa-response {
      type yang:counter64;
      description
        "The number of SA response messages.";
    }
    leaf sa-request {
      type yang:counter64;
      description
        "The number of SA request messages.";
    }
    leaf total {
      type yang:counter64;
      description
        "The number of total messages.";
    }
  } // statistics-sent-received

  /*
   * Data nodes
   */
  augment "/rt:routing/rt:control-plane-protocols/"
        + "rt:control-plane-protocol" {
    when "derived-from-or-self(rt:type, 'msdp:msdp')" {
      description
        "This augmentation is only valid for a routing protocol
         instance of MSDP.";
    }
    description
      "MSDP augmentation to routing control-plane protocol
       configuration and state.";
    container msdp {
      description
        "MSDP configuration and operational state data.";

      container global {
        description
          "Global attributes.";
        uses global-config-attributes;
      }

      container peers {
        description
          "Containing
          "Contains a list of peers.";
        list peer {
          key "address";
          description
            "List
            "A list of MSDP peers.";
          leaf address {
            type inet:ipv4-address;
            description
              "The address of the peer"; peer.";
          }
          action clear-peer {
            description
              "Clears the TCP connection to the peer.";
          }
          uses peer-config-attributes;
          uses peer-state-attributes;
        }
      }

      action clear-all-peers {
        description
          "'All
          "All peers' TCP connection connections are cleared.";
      }

      container sa-cache {
        config false;
        description
          "The SA cache information.";
        list entry {
          key "group source-addr";
          description
            "A list of SA cache entries.";
          leaf group {
            type rt-types:ipv4-multicast-group-address;
            description
              "The group address of this SA cache.";
          }
          leaf source-addr {
            type rt-types:ipv4-multicast-source-address;
            description
              "Source IPv4 address.";
          }
          list origin-rp {
            key "rp-address";
            description "Origin RP information.";
              "Information regarding the originating RP.";
            leaf rp-address {
              type inet:ipv4-address;
              description
                "The RP address.  This is the IP address used in the
                 RP field of an SA message entry.";
            }
            leaf is-local-rp {
              type boolean;
              description
                "'true' if the RP is local;
                 'false' if The the RP is not local.";
            }
            leaf sa-adv-expire {
              type uint32;
              units seconds;
              description
                "The remaining time duration before expiration
                 of the periodic SA advertisement timer on a
                 local RP.";
            }
          }

          container state-attributes {
            description
              "SA cache state attributes for MSDP.";

            leaf up-time {
              type yang:gauge32;
              units seconds;
              description
                "Indicates the duration time when this SA entry is
                 created in the cache.  MSDP is a periodic protocol, protocol;
                 the value can be used to check the state of the
                 SA cache.";
            }
            leaf expire {
              type yang:gauge32;
              units seconds;
              description
                "Indicates the duration time when this SA entry in
                 the cache times out.  MSDP is a periodic protocol, protocol;
                 the value can be used to check the state of the
                 SA cache.";
            }
            leaf holddown-interval {
              type uint32;
              units seconds;
              description
                "Hold-down timer value for SA forwarding.";
              reference
                "RFC 3618: Multicast Source Discovery Protocol
                 (MSDP), section 5.3."; Section 5.3";
            }
            leaf peer-learned-from {
              type inet:ipv4-address;
              description
                "The address of the peer that from which we learned this
                 SA from."; information.";
            }
            leaf rpf-peer {
              type inet:ipv4-address;
              description
                "The address is the SA's originating RP.";
            }
          } // state-attributes
        } // entry

        action clear {
          description
            "Clears MSDP source active (SA) SA cache entries.";
          input {
            container entry {
              presence "If a particular entry is cleared.";
              description
                "The SA cache (S,G) or (*,G) entry to be cleared.
                 If this is not provided, all entries are cleared.";
              leaf group {
                type rt-types:ipv4-multicast-group-address;
                mandatory true;
                description
                  "The group address"; address.";
              }
              leaf source-addr {
                type rt-types:ipv4-multicast-source-address;
                description
                  "Address
                  "The address of the multicast source to be cleared.
                   If this is not provided provided, then all entries related
                   to the given group are cleared.";
              }
            }
            leaf peer-address {
              type inet:ipv4-address;
              description
                "Peer
                "The peer IP address from which MSDP SA cache entries
                 have been learned.  If this is not provided, entries
                 learned from all peers are cleared.";
            }
            leaf peer-as {
              type inet:as-number;
              description
                "ASN
                "The ASN from which MSDP SA cache entries have been
                 learned.  If this is not provided, entries learned
                 from all AS's ASes are cleared.";
            }
          }
        } // clear
      } // sa-cache
    } // msdp
  } // augment
}
<CODE ENDS>
            ]]></artwork>
       <postamble></postamble>
      </figure>
}]]></sourcecode>

    </section>
    <section title="Security Considerations"> numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>The YANG module specified in this document defines a schema for data
   that is designed to be accessed via network management protocols such
   as NETCONF <xref target="RFC6241"/> target="RFC6241" format="default"/> or RESTCONF <xref target="RFC8040"/>. target="RFC8040" format="default"/>.
   The lowest NETCONF layer is the secure transport layer, and the
   mandatory-to-implement secure transport is Secure Shell (SSH) <xref target="RFC6242"/>. target="RFC6242" format="default"/>.
   The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure
   transport is TLS <xref target="RFC8446"/>.</t> target="RFC8446" format="default"/>.</t>
   <t>The NETCONF access control model 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). These data nodes may be considered sensitive or vulnerable
   in some network environments. Write operations (e.g., edit-config)
   to these data nodes without proper protection can have a negative
   effect on network operations. These are the subtrees and data nodes
   and their sensitivity/vulnerability:</t>
      <t>Under /rt:routing/rt:control-plane-protocols/msdp,</t>
   <t>msdp:global
      <list style="simblos">
      <t>This /rt:routing/rt:control-plane-protocols/msdp:</t>

<t indent="3">msdp:global</t>

<t indent="6">This subtree specifies the configuration for the MSDP attributes
        at the global level. Modifying the configuration can cause MSDP
        default peers to be deleted or the connection to be rebuilt, rebuilt and can
        also cause unexpected filtering of the SA.</t>
      </list>
   </t>

   <t>msdp:peers
	  <list style="simblos">
      <t>This

<t indent="3">msdp:peers</t>

<t indent="6">This subtree specifies the configuration for the MSDP attributes
      at the peer level. Modifying the configuration will allow
      unexpected MSDP peer establishment and
      unexpected SA information learning and advertisement.</t>
      <t>The key field

<t indent="6">The writability of the "key" field should be controlled strictly.
      The strictly controlled.
      Misoperation of the key misoperation will break the existing MSDP connection,
      and the associated SA caches will also be deleted.</t>
      </list>
   </t>

      <t>Some of the readable data nodes in this YANG module may be considered
   sensitive or vulnerable in some network environments. It is thus
   important to control read access (e.g., via get, get-config, or
   notification) to these data nodes.  These is msdp subtree are the subtrees and key data
   node
   nodes and their sensitivity/vulnerability:</t>

   <t>/rt:routing/rt:control-plane-protocols/msdp,</t>
   <t>Unauthorized

      <t>/rt:routing/rt:control-plane-protocols/msdp:</t>

   <t indent="3">Unauthorized access to any data node of the above subtree can
   disclose the operational state information of MSDP on this device. For
   example, disclosure of the peer information disclosure may lead to a forged connection
   attack, the ACL nodes' and uncorrected modification of the ACL nodes may lead to the filter errors.
   </t>

   <t>The
   errors.</t>

      <t indent="3">The "key" field is also a sensitive readable configuration.
      Unauthorized reading of this field may lead to leaking of the password leaking. password.
      Modification will allow the unexpected rebuilding of connected peers.</t>
      <t>Authentication configuration is supported via the
   specification of key-chains <xref target="RFC8177"/> target="RFC8177" format="default"/> or
   the direct specification of the
   key and the authentication algorithm.  Hence, authentication
   configuration in the
   "authentication" container inherits the security considerations of discussed in
   <xref target="RFC8177"/>. target="RFC8177" format="default"/>.  This includes the considerations with respect to the
   local storage and handling of authentication keys.</t>

      <t>Some of the RPC operations in this YANG module may be considered
   sensitive or vulnerable in some network environments.  It is thus
   important to control access to these operations.  These are the
   operations and their sensitivity/vulnerability:
      </t>

   <t>/rt:routing/rt:control-plane-protocols/msdp:clear-peer,</t>
   <t>/rt:routing/rt:control-plane-protocols/msdp:clear-sa-cache,</t>
   <t>Unauthorized

      <t>/rt:routing/rt:control-plane-protocols/msdp:clear-peer</t>
      <t>/rt:routing/rt:control-plane-protocols/msdp:clear-sa-cache</t>

      <t indent="3">Unauthorized access to any either of the above action
      operations can lead to rebuilding of the MSDP peers connection rebuilding peers' connections or delete
      deletion of SA records on this device.
     </t>

    </section>

    <section title="IANA Considerations">
	<t>RFC Ed.: Please replace all occurrences of 'XXXX' with numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>IANA has registered the
   actual RFC number (and remove this note).</t>

  <t> The IANA is requested to assign one new following URI from in the IETF "ns" subregistry within
      the "IETF XML
   registry Registry" <xref target="RFC3688"/>.  Authors are suggesting the following URI:</t>

       <t>URI: urn:ietf:params:xml:ns:yang:ietf-msdp</t>
       <t>Registrant Contact: The IESG</t>
       <t>XML: N/A, target="RFC3688" format="default"/>:</t>
      <dl newline="false" spacing="compact">
      <dt>URI:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-msdp</dd>
      <dt>Registrant Contact:</dt><dd>The IESG.</dd>
      <dt>XML:</dt><dd>N/A; the requested URI is an XML namespace</t>

   <t>This document also requests one new namespace.</dd>
      </dl>
      <t>IANA has registered the following YANG module name in the YANG "YANG Module Names registry
      Names" subregistry <xref target="RFC6020"/> with target="RFC6020" format="default"/> within the following suggestion:</t>

       <t>name: ietf-msdp</t>
       <t>namespace: urn:ietf:params:xml:ns:yang:ietf-msdp</t>
       <t>prefix: msdp</t>
       <t>reference: RFC XXXX</t>
   </section>

	<section title="Contributors">
	<t>The authors would like to thank Yisong Liu (liuyisong@huawei.com),
   Benchong Xu (xu.benchong@zte.com.cn),
   Tanmoy Kundu (tanmoy.kundu@alcatel-lucent.com) for their valuable
   contributions.</t>
	</section>

   <section title="Acknowledgement">
	<t>The authors would like to thank Stig Venaas, Jake Holland for their valuable
   comments and suggestions.</t>
      "YANG Parameters" registry:</t>
      <dl newline="false" spacing="compact">
      <dt>Name:</dt><dd>ietf-msdp</dd>
      <dt>Namespace:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-msdp</dd>
      <dt>Prefix:</dt><dd>msdp</dd>
      <dt>Reference:</dt><dd>RFC 8916</dd>
      </dl>
    </section>
  </middle>
  <back>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3618.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4271.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5925.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6020.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6241.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6242.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6991.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7950.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7951.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8040.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8177.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8294.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8340.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8341.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8342.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8343.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8344.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8349.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8446.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8519.xml"/>
      </references>
      <references>
        <name>Informative References</name>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3688.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7761.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8407.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8639.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8641.xml"/>

<!--  *****BACK MATTER ***** draft-ietf-pim-yang (MISSREF)  (Needs to be "long way";
     fangwei hu (lc in XML) needs to be init-capped -->

  <back>

    <references title='Normative References'>
    &rfc2119;
    &rfc3618;
    &rfc4271;
    &rfc5925;
    &rfc6020;
    &rfc6241;
    &rfc6242;
    &rfc6991;
    &rfc7950;
    &rfc7951;
    &rfc8040;
    &rfc8174;
    &rfc8177;
    &rfc8294;
    &rfc8340;
    &rfc8341;
    &rfc8342;
    &rfc8343;
    &rfc8344;
    &rfc8349;
    &rfc8446;
    &rfc8519;
        <reference anchor="PIM-YANG" target="https://tools.ietf.org/html/draft-ietf-pim-yang-17">
          <front>
            <title>A YANG Data Model for Protocol Independent Multicast (PIM)</title>
            <author initials="X" surname="Liu" fullname="Xufeng Liu">
              <organization/>
            </author>
            <author initials="P" surname="McAllister" fullname="Pete McAllister">
              <organization/>
            </author>
            <author initials="A" surname="Peter" fullname="Anish Peter">
              <organization/>
            </author>
            <author initials="M" surname="Sivakumar" fullname="Mahesh Sivakumar">
              <organization/>
            </author>
            <author initials="Y" surname="Liu" fullname="Yisong Liu">
              <organization/>
            </author>
            <author initials="F" surname="Hu" fullname="Fangwei Hu">
              <organization/>
            </author>
            <date month="May" day="19" year="2018"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-pim-yang-17"/>
        </reference>
      </references>

    <references title='Informative References'>
  	&rfc3688;
    &rfc7761;
    &rfc8407;
    &rfc8639;
    &rfc8641;
    &I-D.ietf-pim-yang;
    </references>
    <section title="Data anchor="data-tree-example" numbered="true" toc="default">
      <name>Data Tree Example"> Example</name>
      <t>This section appendix contains an example of an instance data tree in JSON
   encoding <xref target="RFC7951"/>, target="RFC7951" format="default"/>, containing configuration data.</t>
      <section title="The global and peer configuration example">
      <figure align="center">
     <artwork align="center"><![CDATA[ numbered="true" toc="default">
        <name>The Global and Peer Configuration Example</name>
        <sourcecode type="json"><![CDATA[
{
  "ietf-interfaces:interfaces": {
    "interface": [
      {
        "name": "eth1",
        "description": "An interface with MSDP enabled.",
        "type": "iana-if-type:ethernetCsmacd",
        "ietf-ip:ipv4": {
          "forwarding": true,
          "address": [
            {
              "ip": "192.0.2.1",
              "prefix-length": 24
            }
          ]
        }
      }
    ]
  },
  "ietf-access-control-list:acls": {
    "acl": [
      {
        "name": "msdp-default-peer-policy",
        "type": "ietf-access-control-list:ipv4-acl-type",
        "aces": {
          "ace": [
            {
              "name": "accept",
              "actions": {
                "forwarding": "ietf-access-control-list:accept"
              }
            }
          ]
        }
      }
    ]
  },
  "ietf-routing:routing": {
    "router-id": "203.0.113.1",
    "control-plane-protocols": {
      "control-plane-protocol": [
        {
          "type": "ietf-msdp:msdp",
          "name": "msdp-1",
          "ietf-msdp:msdp": {
            "global": {
              "tcp-connection-source": "eth1",
              "default-peer": [
                {
                  "peer-addr": "198.51.100.8",
                  "prefix-policy": "msdp-default-peer-policy"
                }
              ],
              "originating-rp": {
                "interface": "eth1"
              },
              "sa-limit": 0,
              "ttl-threshold": 1
            },
            "peers":{
              "peer":[
            "peers": {
              "peer": [
                {
                  "address": "198.51.100.8",
                  "enabled": true,
                  "tcp-connection-source": "eth1",
                  "description": "x",
                  "mesh-group": "x",
                  "peer-as": 100,
                  "sa-limit": 0,
                  "timer":{
                  "timer": {
                    "connect-retry-interval": 0,
                    "holdtime-interval": 3,
                    "keepalive-interval": 1
                  },
                  "ttl-threshold": 1
                }
              ]
            }
          }
        }
      ]
    }
  }
}
            ]]></artwork>
       <postamble></postamble>
      </figure>
}]]></sourcecode>
      </section>
      <section title="The state example">
        <figure align="center">
     <artwork align="center"><![CDATA[ numbered="true" toc="default">
        <name>The State Example</name>
        <sourcecode type="json"><![CDATA[
{
  "ietf-interfaces:interfaces": {
    "interface": [
      {
        "name": "eth1",
        "description": "An interface with MSDP enabled.",
        "type": "iana-if-type:ethernetCsmacd",
        "phys-address": "00:00:5e:00:53:01",
        "oper-status": "up",
        "statistics": {
          "discontinuity-time": "2020-02-22T11:22:33+02:00"
        },
        "ietf-ip:ipv4": {
          "forwarding": true,
          "mtu": 1500,
          "address": [
            {
              "ip": "192.0.2.1",
              "prefix-length": 24,
              "origin": "static"
            }
          ]
        }
      }
    ]
  },
  "ietf-access-control-list:acls": {
    "acl": [
      {
        "name": "msdp-default-peer-policy",
        "type": "ietf-access-control-list:ipv4-acl-type",
        "aces": {
          "ace": [
            {
              "name": "accept",
              "actions": {
                "forwarding": "ietf-access-control-list:accept"
              }
            }
          ]
        }
      }
    ]
  },
  "ietf-routing:routing": {
    "router-id": "203.0.113.1",
    "control-plane-protocols": {
      "control-plane-protocol": [
        {
          "type": "ietf-msdp:msdp",
          "name": "msdp-1",
          "ietf-msdp:msdp":{
            "global":{
          "ietf-msdp:msdp": {
            "global": {
              "tcp-connection-source": "eth1",
              "default-peer": [
                {
                  "peer-addr": "198.51.100.8",
                  "prefix-policy": "msdp-default-peer-policy"
                }
              ],
              "originating-rp": {
                "interface": "eth1"
              },
              "sa-limit": 0,
              "ttl-threshold": 1
            },
            "peers":{
              "peer":[
            "peers": {
              "peer": [
                {
                  "address": "198.51.100.8",
                  "enabled": true,
                  "tcp-connection-source": "eth1",
                  "description": "x",
                  "mesh-group": "x",
                  "peer-as": 100,
                  "sa-limit": 0,
                  "timer":{
                  "timer": {
                    "connect-retry-interval": 0,
                    "holdtime-interval": 3,
                    "keepalive-interval": 1
                  },
                  "ttl-threshold": 1,
                  "session-state": "established",
                  "elapsed-time": 5,
                  "is-default-peer": true,
                  "keepalive-expire": 1,
                  "reset-count": 1,
                  "statistics": {
                    "discontinuity-time": "2020-02-22T12:22:33+02:00"
                  }
                }
              ]
            },
            "sa-cache": {
              "entry": [
                {
                  "group": "233.252.0.23",
                  "source-addr": "198.51.100.8", "192.0.2.50",
                  "origin-rp": [
                    {
                      "rp-address": "203.0.113.10",
                      "is-local-rp": false,
                      "sa-adv-expire": 150 50
                    }
                  ],
                  "state-attributes": {
                    "up-time": 20, 1000,
                    "expire": 120,
                    "holddown-interval": 150,
                    "peer-learned-from": "203.0.113.10", "198.51.100.8",
                    "rpf-peer": "203.0.113.10" "198.51.100.8"
                  }
                }
              ]
            }
          }
        }
      ]
    }
  }
}
            ]]></artwork>
       <postamble></postamble>
      </figure>
}]]></sourcecode>
      </section>
      <section title="The actions example"> numbered="true" toc="default">
        <name>The Actions Example</name>
        <t>This example shows the input data (in JSON) for executing an "sa-cache "sa&nbhy;cache clear"
  action to clear the cache of all entries which that match the group address of 233.252.0.23.</t>
        <figure align="center">
     <artwork align="left"><![CDATA[
        <sourcecode type="json"><![CDATA[
  {
    "ietf-msdp:sa-cache":{
      "input":{
        "entry":{
          "group":"233.252.0.23"
        }
    "ietf-msdp:sa-cache": {
      "input": {
        "entry": {
          "group": "233.252.0.23"
        }
      }
    }
            ]]></artwork>
       <postamble></postamble>
      </figure>
  }]]></sourcecode>
      </section>
    </section>
    <section numbered="false" toc="default">
      <name>Acknowledgements</name>
      <t>The authors would like to thank <contact fullname="Stig Venaas"/> and
      <contact fullname="Jake Holland"/> for their valuable comments and
      suggestions.</t>
    </section>
    <section numbered="false" toc="default">
      <name>Contributors</name>
      <t>The authors would like to thank the following people
   for their valuable contributions.</t>

     <contact fullname="Yisong Liu">
       <organization></organization>
       <address>
         <postal>
           <street/>
           <city/>
           <region/>
           <code/>
           <country/>
         </postal>
         <email>liuyisong@chinamobile.com</email>
       </address>
     </contact>
     <contact fullname="Benchong Xu">
        <organization></organization>
        <address>
          <postal>
            <street></street>
            <city></city>
            <region></region>
            <country></country>
          </postal>
          <email>xu.benchong@zte.com.cn</email>
        </address>
      </contact>
     <contact fullname="Tanmoy Kundu">
        <organization></organization>
        <address>
          <postal>
            <street></street>
            <city></city>
            <region></region>
            <country></country>
          </postal>
          <email>tanmoy.kundu@alcatel-lucent.com</email>
        </address>
      </contact>
    </section>
  </back>
</rfc>