<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="std" docName="draft-ietf-lsr-ospfv3-extended-lsa-yang-29" number="9587" ipr="trust200902" consensus="true" submissionType="IETF" tocInclude="true" updates="" obsoletes="" sortRefs="true" symRefs="true" xml:lang="en" prepTime="2024-06-07T15:32:43" indexInclude="true" scripts="Common,Latin" tocDepth="3">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-lsr-ospfv3-extended-lsa-yang-29" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc9587" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="YANG Data Model for OSPFv3 Extended LSAs">YANG Data Model for OSPFv3 Extended Link State Advertisements (LSAs)</title>
    <seriesInfo name="RFC" value="9587" stream="IETF"/>
    <author fullname="Acee Lindem" initials="A." surname="Lindem">
      <organization showOnFrontPage="true">LabN Consulting, L.L.C.</organization>
      <address>
        <postal>
          <street>301 Midenhall Way</street>
          <city>Cary</city>
          <region>NC</region>
          <code>27513</code>
          <country>United States of America</country>
        </postal>
        <email>acee.ietf@gmail.com</email>
      </address>
    </author>
    <author fullname="Sharmila Palani" initials="S." surname="Palani">
      <organization showOnFrontPage="true">Microsoft</organization>
      <address>
        <postal>
          <street>1 Microsoft Way</street>
          <city>Redmond</city>
          <region>WA</region>
          <code>98052</code>
          <country>United States of America</country>
        </postal>
        <email>sharmila.palani@microsoft.com</email>
      </address>
    </author>
    <author fullname="Yingzhen Qu" initials="Y" surname="Qu">
      <organization showOnFrontPage="true">Futurewei Technologies</organization>
      <address>
        <postal>
          <street>2330 Central Expressway</street>
          <city>Santa Clara</city>
          <region>CA</region>
          <code>95050</code>
          <country>United States of America</country>
        </postal>
        <email>yingzhen.ietf@gmail.com</email>
      </address>
    </author>
    <date month="06" year="2024"/>
    <area>rtg</area>
    <workgroup>lsr</workgroup>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">This document defines a YANG data model augmenting the IETF OSPF
      YANG data model (RFC 9129) to provide support for
      OSPFv3 Link State Advertisement (LSA) Extensibility as defined in
      RFC 8362. OSPFv3 Extended LSAs provide extensible TLV-based LSAs for the
      base LSA types defined in RFC 5340.</t>
    </abstract>
    <boilerplate>
      <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1">
        <name slugifiedName="name-status-of-this-memo">Status of This Memo</name>
        <t indent="0" pn="section-boilerplate.1-1">
            This is an Internet Standards Track document.
        </t>
        <t indent="0" pn="section-boilerplate.1-2">
            This document is a product of the Internet Engineering Task Force
            (IETF).  It represents the consensus of the IETF community.  It has
            received public review and has been approved for publication by
            the Internet Engineering Steering Group (IESG).  Further
            information on Internet Standards is available in Section 2 of 
            RFC 7841.
        </t>
        <t indent="0" pn="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <eref target="https://www.rfc-editor.org/info/rfc9587" brackets="none"/>.
        </t>
      </section>
      <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.2">
        <name slugifiedName="name-copyright-notice">Copyright Notice</name>
        <t indent="0" pn="section-boilerplate.2-1">
            Copyright (c) 2024 IETF Trust and the persons identified as the
            document authors. All rights reserved.
        </t>
        <t indent="0" pn="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<eref target="https://trustee.ietf.org/license-info" brackets="none"/>) in effect on the date of
            publication of this document. Please review these documents
            carefully, as they describe your rights and restrictions with
            respect to this document. Code Components extracted from this
            document must include Revised BSD License text as described in
            Section 4.e of the Trust Legal Provisions and are provided without
            warranty as described in the Revised BSD License.
        </t>
      </section>
    </boilerplate>
    <toc>
      <section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1">
        <name slugifiedName="name-table-of-contents">Table of Contents</name>
        <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1">
          <li pn="section-toc.1-1.1">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-overview">Overview</xref></t>
          </li>
          <li pn="section-toc.1-1.2">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-tree-diagrams">Tree Diagrams</xref></t>
          </li>
          <li pn="section-toc.1-1.3">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-ospfv3-extended-lsas">OSPFv3 Extended LSAs</xref></t>
          </li>
          <li pn="section-toc.1-1.4">
            <t indent="0" pn="section-toc.1-1.4.1"><xref derivedContent="4" format="counter" sectionFormat="of" target="section-4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-ospfv3-extended-lsa-yang-mo">OSPFv3 Extended LSA YANG Module</xref></t>
          </li>
          <li pn="section-toc.1-1.5">
            <t indent="0" pn="section-toc.1-1.5.1"><xref derivedContent="5" format="counter" sectionFormat="of" target="section-5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.6">
            <t indent="0" pn="section-toc.1-1.6.1"><xref derivedContent="6" format="counter" sectionFormat="of" target="section-6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.7">
            <t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="7" format="counter" sectionFormat="of" target="section-7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-references">References</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.7.2">
              <li pn="section-toc.1-1.7.2.1">
                <t indent="0" pn="section-toc.1-1.7.2.1.1"><xref derivedContent="7.1" format="counter" sectionFormat="of" target="section-7.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
              </li>
              <li pn="section-toc.1-1.7.2.2">
                <t indent="0" pn="section-toc.1-1.7.2.2.1"><xref derivedContent="7.2" format="counter" sectionFormat="of" target="section-7.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.8">
            <t indent="0" pn="section-toc.1-1.8.1"><xref derivedContent="Appendix A" format="default" sectionFormat="of" target="section-appendix.a"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-configuration-example">Configuration Example</xref></t>
          </li>
          <li pn="section-toc.1-1.9">
            <t indent="0" pn="section-toc.1-1.9.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgements">Acknowledgements</xref></t>
          </li>
          <li pn="section-toc.1-1.10">
            <t indent="0" pn="section-toc.1-1.10.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.c"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Addresses</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section numbered="true" removeInRFC="false" toc="include" pn="section-1">
      <name slugifiedName="name-overview">Overview</name>
      <t indent="0" pn="section-1-1">YANG <xref target="RFC7950" format="default" sectionFormat="of" derivedContent="RFC7950"/> is a data definition language
      used to define the contents of a conceptual datastore
      that allows networked devices to be managed using NETCONF
      <xref target="RFC6241" format="default" sectionFormat="of" derivedContent="RFC6241"/>.  YANG is proving relevant beyond its
      initial confines as bindings to other interfaces (e.g., RESTCONF <xref target="RFC8040" format="default" sectionFormat="of" derivedContent="RFC8040"/>) and
      encodings other than XML (e.g., JSON) are being defined.  Furthermore,
      YANG data models can be used as the basis for implementation of other
      interfaces, such as Command-Line Interfaces (CLIs) and programmatic APIs.</t>
      <t indent="0" pn="section-1-2">This document defines a YANG data model augmenting the IETF OSPF
      YANG data model <xref target="RFC9129" format="default" sectionFormat="of" derivedContent="RFC9129"/>, which itself augments
      <xref target="RFC8349" format="default" sectionFormat="of" derivedContent="RFC8349"/>, to provide support for configuration and
      operational state for OSPFv3 Extended Link State Advertisements (LSAs) as defined in
      <xref target="RFC8362" format="default" sectionFormat="of" derivedContent="RFC8362"/>. </t>
      <t indent="0" pn="section-1-3">The YANG module specified in this document conforms to the Network Management
         Datastore Architecture (NMDA) <xref target="RFC8342" format="default" sectionFormat="of" derivedContent="RFC8342"/>.</t>
    </section>
    <section numbered="true" removeInRFC="false" toc="include" pn="section-2">
      <name slugifiedName="name-tree-diagrams">Tree Diagrams</name>
      <t indent="0" pn="section-2-1"> This document uses the graphical representation of data models
          defined in <xref target="RFC8340" format="default" sectionFormat="of" derivedContent="RFC8340"/>. </t>
    </section>
    <section numbered="true" removeInRFC="false" toc="include" pn="section-3">
      <name slugifiedName="name-ospfv3-extended-lsas">OSPFv3 Extended LSAs</name>
      <t indent="0" pn="section-3-1">This document defines a YANG data model for the OSPFv3 Extended LSA feature. It is an
      augmentation of the OSPF base model <xref target="RFC9129" format="default" sectionFormat="of" derivedContent="RFC9129"/> to provide support for OSPFv3 LSA Extensibility <xref target="RFC8362" format="default" sectionFormat="of" derivedContent="RFC8362"/>.
      OSPFv3 Extended LSAs provide extensible TLV-based LSAs for the
      base LSA types defined in <xref target="RFC5340" format="default" sectionFormat="of" derivedContent="RFC5340"/>.</t>
      <t indent="0" pn="section-3-2">The OSPFv3 Extended LSA YANG module requires support for the OSPF base
    model, which defines basic OSPF
   configuration and state. The OSPF YANG data model augments the "ietf-routing" YANG
   data model defined in <xref target="RFC8349" format="default" sectionFormat="of" derivedContent="RFC8349"/>.
   The augmentations defined in the "ietf-ospfv3-extended-lsa" YANG
   module provide global configuration, area configuration, and the addition of OSPFv3
    Extended LSAs to the Link State Database (LSDB) operational state.</t>
      <sourcecode type="yangtree" markers="false" pn="section-3-3">
module: ietf-ospfv3-extended-lsa

  augment /rt:routing/rt:control-plane-protocols
            /rt:control-plane-protocol/ospf:ospf:
    +--rw extended-lsa-support?   boolean
  augment /rt:routing/rt:control-plane-protocols
            /rt:control-plane-protocol/ospf:ospf/ospf:areas
            /ospf:area:
    +--rw extended-lsa-support?   boolean
  augment /rt:routing/rt:control-plane-protocols
            /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area
            /ospf:interfaces/ospf:interface/ospf:database
            /ospf:link-scope-lsa-type/ospf:link-scope-lsas
            /ospf:link-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3
            /ospf:body:
    +--ro e-link
       +--ro rtr-priority?   uint8
       +--ro lsa-options
       |  +--ro lsa-options*   identityref
       +--ro e-link-tlvs* []
          +--ro unknown-tlv
          |  +--ro type?     uint16
          |  +--ro length?   uint16
          |  +--ro value?    yang:hex-string
          +--ro intra-prefix-tlv
          |  +--ro metric?           ospf:ospf-metric
          |  +--ro prefix?           inet:ip-prefix
          |  +--ro prefix-options
          |  |  +--ro prefix-options*   identityref
          |  +--ro sub-tlvs* []
          |     +--ro unknown-sub-tlv
          |        +--ro type?     uint16
          |        +--ro length?   uint16
          |        +--ro value?    yang:hex-string
          +--ro ipv6-link-local-addr-tlv
          |  +--ro link-local-address?   inet:ipv6-address
          |  +--ro sub-tlvs* []
          |     +--ro unknown-sub-tlv
          |        +--ro type?     uint16
          |        +--ro length?   uint16
          |        +--ro value?    yang:hex-string
          +--ro ipv4-link-local-addr-tlv
             +--ro link-local-address?   inet:ipv4-address
             +--ro sub-tlvs* []
                +--ro unknown-sub-tlv
                   +--ro type?     uint16
                   +--ro length?   uint16
                   +--ro value?    yang:hex-string
  augment /rt:routing/rt:control-plane-protocols
            /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area
            /ospf:database/ospf:area-scope-lsa-type
            /ospf:area-scope-lsas/ospf:area-scope-lsa/ospf:version
            /ospf:ospfv3/ospf:ospfv3/ospf:body:
    +--ro e-router
    |  +--ro router-bits
    |  |  +--ro rtr-lsa-bits*   identityref
    |  +--ro lsa-options
    |  |  +--ro lsa-options*   identityref
    |  +--ro e-router-tlvs* []
    |     +--ro unknown-tlv
    |     |  +--ro type?     uint16
    |     |  +--ro length?   uint16
    |     |  +--ro value?    yang:hex-string
    |     +--ro link-tlv
    |        +--ro interface-id?            uint32
    |        +--ro neighbor-interface-id?   uint32
    |        +--ro neighbor-router-id?      rt-types:router-id
    |        +--ro type?                    ospf:router-link-type
    |        +--ro metric?                  ospf:ospf-link-metric
    |        +--ro sub-tlvs* []
    |           +--ro unknown-sub-tlv
    |              +--ro type?     uint16
    |              +--ro length?   uint16
    |              +--ro value?    yang:hex-string
    +--ro e-network
    |  +--ro lsa-options
    |  |  +--ro lsa-options*   identityref
    |  +--ro e-network-tlvs* []
    |     +--ro unknown-tlv
    |     |  +--ro type?     uint16
    |     |  +--ro length?   uint16
    |     |  +--ro value?    yang:hex-string
    |     +--ro attached-router-tlv
    |        +--ro adjacent-neighbor-router-id*   rt-types:router-id
    +--ro e-nssa
    |  +--ro e-external-tlvs* []
    |     +--ro unknown-tlv
    |     |  +--ro type?     uint16
    |     |  +--ro length?   uint16
    |     |  +--ro value?    yang:hex-string
    |     +--ro external-prefix-tlv
    |        +--ro flags
    |        |  +--ro ospfv3-e-external-prefix-bits*   identityref
    |        +--ro metric?           ospf:ospf-metric
    |        +--ro prefix?           inet:ip-prefix
    |        +--ro prefix-options
    |        |  +--ro prefix-options*   identityref
    |        +--ro sub-tlvs* []
    |           +--ro ipv6-fwd-addr-sub-tlv
    |           |  +--ro forwarding-address?   inet:ipv6-address
    |           +--ro ipv4-fwd-addr-sub-tlv
    |           |  +--ro forwarding-address?   inet:ipv4-address
    |           +--ro route-tag-sub-tlv
    |           |  +--ro route-tag?   uint32
    |           +--ro unknown-sub-tlv
    |              +--ro type?     uint16
    |              +--ro length?   uint16
    |              +--ro value?    yang:hex-string
    +--ro e-inter-area-prefix
    |  +--ro e-inter-prefix-tlvs* []
    |     +--ro unknown-tlv
    |     |  +--ro type?     uint16
    |     |  +--ro length?   uint16
    |     |  +--ro value?    yang:hex-string
    |     +--ro inter-prefix-tlv
    |        +--ro metric?           ospf:ospf-metric
    |        +--ro prefix?           inet:ip-prefix
    |        +--ro prefix-options
    |        |  +--ro prefix-options*   identityref
    |        +--ro sub-tlvs* []
    |           +--ro unknown-sub-tlv
    |              +--ro type?     uint16
    |              +--ro length?   uint16
    |              +--ro value?    yang:hex-string
    +--ro e-inter-area-router
    |  +--ro e-inter-router-tlvs* []
    |     +--ro unknown-tlv
    |     |  +--ro type?     uint16
    |     |  +--ro length?   uint16
    |     |  +--ro value?    yang:hex-string
    |     +--ro inter-router-tlv
    |        +--ro lsa-options
    |        |  +--ro lsa-options*   identityref
    |        +--ro metric?                  ospf:ospf-metric
    |        +--ro destination-router-id?   rt-types:router-id
    |        +--ro sub-tlvs* []
    |           +--ro unknown-sub-tlv
    |              +--ro type?     uint16
    |              +--ro length?   uint16
    |              +--ro value?    yang:hex-string
    +--ro e-intra-area-prefix
       +--ro referenced-ls-type?         uint16
       +--ro referenced-link-state-id?   uint32
       +--ro referenced-adv-router?      rt-types:router-id
       +--ro e-intra-prefix-tlvs* []
          +--ro unknown-tlv
          |  +--ro type?     uint16
          |  +--ro length?   uint16
          |  +--ro value?    yang:hex-string
          +--ro intra-prefix-tlv
             +--ro metric?           ospf:ospf-metric
             +--ro prefix?           inet:ip-prefix
             +--ro prefix-options
             |  +--ro prefix-options*   identityref
             +--ro sub-tlvs* []
                +--ro unknown-sub-tlv
                   +--ro type?     uint16
                   +--ro length?   uint16
                   +--ro value?    yang:hex-string
  augment /rt:routing/rt:control-plane-protocols
            /rt:control-plane-protocol/ospf:ospf/ospf:database
            /ospf:as-scope-lsa-type/ospf:as-scope-lsas
            /ospf:as-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3
            /ospf:body:
    +--ro e-as-external
       +--ro e-external-tlvs* []
          +--ro unknown-tlv
          |  +--ro type?     uint16
          |  +--ro length?   uint16
          |  +--ro value?    yang:hex-string
          +--ro external-prefix-tlv
             +--ro flags
             |  +--ro ospfv3-e-external-prefix-bits*   identityref
             +--ro metric?           ospf:ospf-metric
             +--ro prefix?           inet:ip-prefix
             +--ro prefix-options
             |  +--ro prefix-options*   identityref
             +--ro sub-tlvs* []
                +--ro ipv6-fwd-addr-sub-tlv
                |  +--ro forwarding-address?   inet:ipv6-address
                +--ro ipv4-fwd-addr-sub-tlv
                |  +--ro forwarding-address?   inet:ipv4-address
                +--ro route-tag-sub-tlv
                |  +--ro route-tag?   uint32
                +--ro unknown-sub-tlv
                   +--ro type?     uint16
                   +--ro length?   uint16
                   +--ro value?    yang:hex-string
</sourcecode>
    </section>
    <section numbered="true" removeInRFC="false" toc="include" pn="section-4">
      <name slugifiedName="name-ospfv3-extended-lsa-yang-mo">OSPFv3 Extended LSA YANG Module</name>
      <t indent="0" pn="section-4-1">The following RFCs are not referenced in the document text
but are referenced in the "ietf-ospfv3-extended-lsa.yang" module:
<xref target="RFC6991" format="default" sectionFormat="of" derivedContent="RFC6991"/> and <xref target="RFC8294" format="default" sectionFormat="of" derivedContent="RFC8294"/>.</t>
      <sourcecode name="ietf-ospfv3-extended-lsa@2024-06-07.yang" type="yang" markers="true" pn="section-4-2">
module ietf-ospfv3-extended-lsa {
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:ietf-ospfv3-extended-lsa";
  prefix ospfv3-e-lsa;

  import ietf-routing-types {
    prefix rt-types;
    reference
      "RFC 8294: Common YANG Data Types for the Routing Area";
  }
  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-ospf {
    prefix ospf;
    reference
      "RFC 9129: YANG Data Model for the OSPF Protocol";
  }

  organization
    "IETF LSR - Link State Routing Working Group";
  contact
    "WG Web:   &lt;https://datatracker.ietf.org/wg/lsr/&gt;
     WG List:  &lt;mailto:lsr@ietf.org&gt;

     Author:   Acee Lindem
               &lt;mailto:acee.ietf@gmail.com&gt;
     Author:   Sharmila Palani
               &lt;mailto:sharmila.palani@microsoft.com&gt;
     Author:   Yingzhen Qu
               &lt;mailto:yingzhen.ietf@gmail.com&gt;";
  description
    "This YANG module defines the configuration and operational
     state for OSPFv3 Extended LSAs, which is common across all
     vendor implementations.  The semantics and encodings for
     OSPFv3 Extended LSAs are described in RFC 8362.  OSPFv3
     Extended LSAs provide extensible TLV-based LSAs for the base
     LSA types defined in RFC 5340.

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

     Copyright (c) 2024 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 9587; see the
     RFC itself for full legal notices.";

  reference
    "RFC 9587: YANG Data Model for OSPFv3 Extended Link State
     Advertisements (LSAs)";

  revision 2024-06-07 {
    description
      "Initial revision.";
    reference
      "RFC 9587: YANG Data Model for OSPFv3 Extended Link State
       Advertisements (LSAs)";
  }

  /*
   * OSPFv3 Extended LSA Type Identities
   */

  identity ospfv3-e-router-lsa {
    base ospf:ospfv3-lsa-type;
    description
      "OSPFv3 E-Router-LSA - Type 0xA021.";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 4.1";
  }

  identity ospfv3-e-network-lsa {
    base ospf:ospfv3-lsa-type;
    description
      "OSPFv3 E-Network-LSA - Type 0xA022.";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 4.2";
  }

  identity ospfv3-e-summary-lsa-type {
    base ospf:ospfv3-lsa-type;
    description
      "OSPFv3 Extended Summary LSA types:
       E-Inter-Area-Prefix-LSA and E-Inter-Area-Router-LSA.";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Sections 4.3 and 4.4";
  }

  identity ospfv3-e-inter-area-prefix-lsa {
    base ospfv3-e-summary-lsa-type;
    description
      "OSPFv3 E-Inter-Area-Prefix-LSA - Type 0xA023.";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 4.3";
  }

  identity ospfv3-e-inter-area-router-lsa {
    base ospfv3-e-summary-lsa-type;
    description
      "OSPFv3 E-Inter-Area-Router-LSA - Type 0xA024.";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 4.4";
  }

  identity ospfv3-e-external-lsa-type {
    base ospf:ospfv3-lsa-type;
    description
      "OSPFv3 Extended External LSA types:
       E-AS-External-LSA and E-NSSA-LSA (where
       NSSA expands to Not-So-Stubby-Area).";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Sections 4.5 and 4.6";
  }

  identity ospfv3-e-as-external-lsa {
    base ospfv3-e-external-lsa-type;
    description
      "OSPFv3 E-AS-External-LSA - Type 0xC025.";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 4.5";
  }

  identity ospfv3-e-nssa-lsa {
    base ospfv3-e-external-lsa-type;
    description
      "OSPFv3 E-NSSA-LSA - Type 0xA027.";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 4.6";
  }

  identity ospfv3-e-link-lsa {
    base ospf:ospfv3-lsa-type;
    description
      "OSPFv3 E-Link-LSA - Type 0x8028.";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 4.7";
  }

  identity ospfv3-e-intra-area-prefix-lsa {
    base ospf:ospfv3-lsa-type;
    description
      "OSPFv3 E-Intra-Area-Prefix-LSA - Type 0xA029.";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 4.8";
  }

  identity ospfv3-e-prefix-option {
    description
      "Base identity for OSPFv3 prefix options.";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 3.1";
  }

  identity nu-bit {
    base ospfv3-e-prefix-option;
    description
      "When set, the prefix should be excluded
       from IPv6 unicast calculations.";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 3.1
       RFC 5340: OSPF for IPv6, Appendix A.4.1.1";
  }

  identity la-bit {
    base ospfv3-e-prefix-option;
    description
      "When set, the prefix is actually an IPv6 interface
       address of the advertising router.";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 3.1
       RFC 5340: OSPF for IPv6, Appendix A.4.1.1";
  }

  identity p-bit {
    base ospfv3-e-prefix-option;
    description
      "When set, the NSSA prefix should be translated to an
       E-AS-External-LSA and advertised by the translating
       NSSA Border Router.";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 3.1
       RFC 5340: OSPF for IPv6, Appendix A.4.1.1";
  }

  identity dn-bit {
    base ospfv3-e-prefix-option;
    description
      "When set, the E-Inter-Area-Prefix-LSA or
       E-AS-External-LSA prefix has been advertised as an
       L3VPN prefix.";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 3.1
       RFC 5340: OSPF for IPv6, Appendix A.4.1.1";
  }

  identity n-bit {
    base ospfv3-e-prefix-option;
    description
      "When set, the prefix is a host address that identifies
       the advertising router.";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 3.1
       RFC 5340: OSPF for IPv6, Appendix A.4.1.1";
  }

  identity ospfv3-e-external-prefix-option {
    description
      "Base identity for OSPFv3 external prefix options.";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 3.6";
  }

  identity e-bit {
    base ospfv3-e-external-prefix-option;
    description
      "When the E-bit is set, the metric specified is a Type 2
       external metric.  This means the metric is considered larger
       than any intra-AS path.  When the E-bit is clear, the
       specified metric is a Type 1 external metric.  This means
       that it is expressed in the same units as other LSAs (i.e.,
       the same units as the interface costs in Router-LSAs).";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 3.6";
  }

  grouping unknown-sub-tlv {
    description
      "Unknown TLV grouping.";
    container unknown-sub-tlv {
      uses ospf:tlv;
      description
        "Unknown External TLV sub-TLV.";
    }
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 6.3";
  }

  grouping ospfv3-lsa-prefix {
    description
      "OSPFv3 LSA prefix.";
    leaf prefix {
      type inet:ip-prefix;
      description
        "LSA prefix.";
    }
    container prefix-options {
      leaf-list prefix-options {
        type identityref {
          base ospfv3-e-prefix-option;
        }
        description
          "OSPFv3 prefix options flag list.  This list will
           contain the identities for the OSPFv3 options
           that are set for the OSPFv3 prefix.";
      }
      description
        "Prefix options.";
      reference
        "RFC 8362:  OSPFv3 Link State Advertisement (LSA)
         Extensibility, Section 3.1";
    }
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 3";
  }

  grouping external-prefix-tlv {
    container external-prefix-tlv {
      description
        "External-Prefix TLV.";
      container flags {
        leaf-list ospfv3-e-external-prefix-bits {
          type identityref {
            base ospfv3-e-external-prefix-option;
          }
          description
            "OSPFv3 External-Prefix TLV bits list.";
        }
        description
          "External prefix flags.";
      }
      leaf metric {
        type ospf:ospf-metric;
        description
          "External prefix metric.";
      }
      uses ospfv3-lsa-prefix;
      list sub-tlvs {
        description
          "External-Prefix TLV sub-TLVs.";
        container ipv6-fwd-addr-sub-tlv {
          description
            "IPv6-Forwarding-Address sub-TLV for
             E-AS-External-LSAs and E-NSSA-LSAs for the IPv6
             address family.";
          leaf forwarding-address {
            type inet:ipv6-address;
            description
              "IPv6 forwarding address.";
          }
          reference
            "RFC 8362: OSPFv3 Link State Advertisement (LSA)
             Extensibility, Section 3.10";
        }
        container ipv4-fwd-addr-sub-tlv {
          description
            "IPv4-Forwarding-Address sub-TLV for
             E-AS-External-LSAs and E-NSSA-LSAs for the IPv4
             address family.";
          leaf forwarding-address {
            type inet:ipv4-address;
            description
              "IPv4 forwarding address.";
          }
          reference
            "RFC 8362: OSPFv3 Link State Advertisement (LSA)
             Extensibility, Section 3.11";
        }
        container route-tag-sub-tlv {
          description
            "Route-Tag sub-TLV.";
          leaf route-tag {
            type uint32;
            description
              "Route tag.";
          }
          reference
            "RFC 8362: OSPFv3 Link State Advertisement (LSA)
             Extensibility, Section 3.12";
        }
        uses unknown-sub-tlv;
      }
    }
    description
      "External-Prefix TLV grouping.";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 3.6";
  }

  grouping intra-area-prefix-tlv {
    container intra-prefix-tlv {
      description
        "Intra-Area-Prefix-LSA TLV.";
      leaf metric {
        type ospf:ospf-metric;
        description
          "Intra-Area Prefix metric.";
      }
      uses ospfv3-lsa-prefix;
      list sub-tlvs {
        description
          "Intra-Area-Prefix TLV sub-TLVs.";
        uses unknown-sub-tlv;
      }
    }
    description
      "Intra-Area-Prefix TLV grouping.";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 3.7";
  }

  grouping ipv6-link-local-addr-tlv {
    container ipv6-link-local-addr-tlv {
      description
        "IPv6 Link-Local Address TLV.";
      leaf link-local-address {
        type inet:ipv6-address;
        description
          "IPv6 Link-Local address.";
      }
      list sub-tlvs {
        description
          "IPv6 Link-Local Address TLV sub-TLVs.";
        uses unknown-sub-tlv;
      }
    }
    description
      "IPv6 Link-Local Address TLV grouping.";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 3.8";
  }

  grouping ipv4-link-local-addr-tlv {
    container ipv4-link-local-addr-tlv {
      description
        "IPv4 Link-Local Address TLV.";
      leaf link-local-address {
        type inet:ipv4-address;
        description
          "IPv4 Link-Local address.";
      }
      list sub-tlvs {
        description
          "IPv4 Link-Local Address TLV sub-TLVs.";
        uses unknown-sub-tlv;
      }
    }
    description
      "IPv4 Link-Local Address TLV grouping.";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 3.9";
  }

  /* Configuration */

  augment "/rt:routing/rt:control-plane-protocols"
        + "/rt:control-plane-protocol/ospf:ospf" {
    when "../rt:type = 'ospf:ospfv3'" {
      description
        "This augments the OSPFv3 routing protocol when used.";
    }
    description
      "This augments the OSPFv3 protocol instance-level
       configuration with Extended LSA support.  When enabled,
       OSPFv3 Extended LSAs will be advertised and OSPFv3 Legacy
       LSAs will not be advertised.  When disabled, OSPFv3 Legacy
       LSAs will be advertised.  However, OSPFv3 Extended LSAs
       could still be advertised in Extended LSA Sparse Mode to
       support incrementally deployed features as described in
       Section 6.2 of RFC 8362.";
    leaf extended-lsa-support {
      type boolean;
      default "false";
      description
        "Enable OSPFv3 Extended LSA support for the OSPFv3
         domain.";
      reference
        "RFC 8362: OSPFv3 Link State Advertisement (LSA)
         Extensibility, Appendix A - Global Configuration Support";
    }
  }

  augment "/rt:routing/rt:control-plane-protocols/"
        + "rt:control-plane-protocol/ospf:ospf/ospf:"
        + "areas/ospf:area" {
    when "../../../rt:type = 'ospf:ospfv3'" {
      description
        "This augments the OSPFv3 protocol area-level
         configuration when used.";
    }
    description
      "This augments the OSPFv3 protocol area-level
       configuration with Extended LSA support.";
    leaf extended-lsa-support {
      type boolean;
      must "derived-from(../ospf:area-type,'stub-nssa-area') or "
         + "(current() = 'true') or "
         + "(../../../extended-lsa-support = 'false')" {
        description
          "For regular areas, i.e., areas where AS-scoped LSAs
           are flooded, disabling AreaExtendedLSASupport at the
           area level is prohibited when ExtendedLSASupport is
           enabled at the instance level.  E-AS-External-LSAs
           are flooded into all OSPFv3 regular areas (i.e., not
           a stub or an NSSA), and disabling support at the
           area level is not possible.";
      }
      description
        "This augments the OSPFv3 protocol area-level
         configuration with Extended LSA support.  When enabled,
         OSPFv3 Extended LSAs will be advertised and OSPFv3 Legacy
         LSAs will not be advertised.  When disabled, OSPFv3
         Legacy LSAs will be advertised.  However, OSPFv3 Extended
         LSAs could still be advertised in Extended LSA Sparse
         Mode to support incrementally deployed features as
         described in Section 6.2 of RFC 8362.  If not specified,
         Extended LSA support status is inherited from the
         instance-level configuration.";
      reference
        "RFC 8362: OSPFv3 Link State Advertisement (LSA)
         Extensibility, Appendix B - Area Configuration Support";
    }
  }

  /*
   * Link State Database (LSDB) Augmentations
   */

  augment "/rt:routing/"
        + "rt:control-plane-protocols/rt:control-plane-protocol/"
        + "ospf:ospf/ospf:areas/ospf:area/"
        + "ospf:interfaces/ospf:interface/ospf:database/"
        + "ospf:link-scope-lsa-type/ospf:link-scope-lsas/"
        + "ospf:link-scope-lsa/ospf:version/ospf:ospfv3/"
        + "ospf:ospfv3/ospf:body" {
    when "../../../../../../../../../../../"
       + "rt:type = 'ospf:ospfv3'" {
      description
        "This augmentation is only valid for OSPFv3.";
    }
    description
      "This augmentation adds OSPFv3 Link-scoped Extended LSAs
       to the operational state for an interface Link State
       Database (LSDB).";
    container e-link {
      when "../../ospf:header/ospf:type = "
         + "'ospfv3-e-lsa:ospfv3-e-link-lsa'" {
        description
          "Only applies to E-Link-LSAs.";
      }
      description
        "E-Link-LSA contents.";
      reference
        "RFC 8362: OSPFv3 Link State Advertisement (LSA)
         Extensibility, Section 4.7";
      leaf rtr-priority {
        type uint8;
        description
          "Router priority for the interface.";
      }
      uses ospf:ospfv3-lsa-options;
      list e-link-tlvs {
        description
          "E-Link-LSA TLVs.";
        container unknown-tlv {
          uses ospf:tlv;
          description
            "Unknown E-Link TLV.";
        }
        uses intra-area-prefix-tlv;
        uses ipv6-link-local-addr-tlv;
        uses ipv4-link-local-addr-tlv;
      }
    }
  }

  augment "/rt:routing/"
        + "rt:control-plane-protocols/rt:control-plane-protocol/"
        + "ospf:ospf/ospf:areas/ospf:area/ospf:database/"
        + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/"
        + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/"
        + "ospf:ospfv3/ospf:body" {
    when "../../../../../../../../../"
       + "rt:type = 'ospf:ospfv3'" {
      description
        "This augmentation is only valid for OSPFv3.";
    }
    description
      "This augmentation adds OSPFv3 Area-scoped Extended LSAs
       to the operational state for an area LSDB.";
    reference
      "RFC 8362: OSPFv3 Link State Advertisement (LSA)
       Extensibility, Section 4";
    container e-router {
      when "../../ospf:header/ospf:type = "
         + "'ospfv3-e-lsa:ospfv3-e-router-lsa'" {
        description
          "Only valid for OSPFv3 E-Router-LSAs.";
      }
      description
        "OSPFv3 E-Router-LSA contents.";
      reference
        "RFC 8362: OSPFv3 Link State Advertisement (LSA)
         Extensibility, Section 4.1";
      uses ospf:ospf-router-lsa-bits;
      uses ospf:ospfv3-lsa-options;
      list e-router-tlvs {
        description
          "E-Router-LSA TLVs.";
        container unknown-tlv {
          uses ospf:tlv;
          description
            "Unknown E-Router TLV.";
        }
        container link-tlv {
          description
            "E-Router-LSA TLV.";
          leaf interface-id {
            type uint32;
            description
              "Interface ID for link.";
          }
          leaf neighbor-interface-id {
            type uint32;
            description
              "Neighbor's Interface ID for link.";
          }
          leaf neighbor-router-id {
            type rt-types:router-id;
            description
              "Neighbor's Router ID for link.";
          }
          leaf type {
            type ospf:router-link-type;
            description
              "Link type: 1 - Point-to-Point Link
                          2 - Transit Network Link
                          3 - Stub Network Link
                          4 - Virtual Link.";
          }
          leaf metric {
            type ospf:ospf-link-metric;
            description
              "Link metric.";
          }
          list sub-tlvs {
            description
              "Link TLV sub-TLVs.";
            uses unknown-sub-tlv;
          }
        }
      }
    }
    container e-network {
      when "../../ospf:header/ospf:type = "
         + "'ospfv3-e-lsa:ospfv3-e-network-lsa'" {
        description
          "Only applies to E-Network-LSAs.";
      }
      description
        "E-Network-LSA contents.";
      reference
        "RFC 8362: OSPFv3 Link State Advertisement (LSA)
         Extensibility, Section 4.2";
      uses ospf:ospfv3-lsa-options;
      list e-network-tlvs {
        description
          "E-Network-LSA TLVs.";
        container unknown-tlv {
          uses ospf:tlv;
          description
            "Unknown E-Network TLV.";
        }
        container attached-router-tlv {
          description
            "Attached-Routers TLV.";
          leaf-list adjacent-neighbor-router-id {
            type rt-types:router-id;
            description
              "Adjacent neighbor's Router ID.";
          }
        }
      }
    }
    container e-nssa {
      when "../../ospf:header/ospf:type = "
         + "'ospfv3-e-lsa:ospfv3-e-nssa-lsa'" {
        description
          "Only applies to E-NSSA-LSAs.";
      }
      description
        "E-NSSA-LSA contents.";
      list e-external-tlvs {
        description
          "E-NSSA-LSA TLVs.";
        container unknown-tlv {
          uses ospf:tlv;
          description
            "Unknown E-External TLV.";
        }
        uses external-prefix-tlv;
      }
      reference
        "RFC 8362: OSPFv3 Link State Advertisement (LSA)
         Extensibility, Section 4.6";
    }
    container e-inter-area-prefix {
      when "../../ospf:header/ospf:type = "
         + "'ospfv3-e-lsa:ospfv3-e-inter-area-prefix-lsa'" {
        description
          "Only applies to E-Inter-Area-Prefix-LSAs.";
      }
      description
        "E-Inter-Area-Prefix-LSA contents.";
      reference
        "RFC 8362: OSPFv3 Link State Advertisement (LSA)
         Extensibility, Section 4.3";
      list e-inter-prefix-tlvs {
        description
          "E-Inter-Area-Prefix-LSA TLVs.";
        container unknown-tlv {
          uses ospf:tlv;
          description
            "Unknown E-Inter-Area-Prefix TLV.";
        }
        container inter-prefix-tlv {
          description
            "Unknown E-Inter-Area-Prefix-LSA TLV.";
          leaf metric {
            type ospf:ospf-metric;
            description
              "Inter-Area Prefix metric.";
          }
          uses ospfv3-lsa-prefix;
          list sub-tlvs {
            description
              "Inter-Area-Prefix TLV sub-TLVs.";
            uses unknown-sub-tlv;
          }
        }
      }
    }
    container e-inter-area-router {
      when "../../ospf:header/ospf:type = "
         + "'ospfv3-e-lsa:ospfv3-e-inter-area-router-lsa'" {
        description
          "Only applies to E-Inter-Area-Router-LSAs.";
      }
      description
        "E-Inter-Area-Router-LSA contents.";
      reference
        "RFC 8362: OSPFv3 Link State Advertisement (LSA)
         Extensibility, Section 4.4";
      list e-inter-router-tlvs {
        description
          "E-Inter-Area-Router-LSA TLVs.";
        container unknown-tlv {
          uses ospf:tlv;
          description
            "Unknown E-Inter-Area-Router TLV.";
        }
        container inter-router-tlv {
          description
            "Unknown E-Inter-Area-Router-LSA TLV.";
          uses ospf:ospfv3-lsa-options;
          leaf metric {
            type ospf:ospf-metric;
            description
              "Inter-Area Router metric.";
          }
          leaf destination-router-id {
            type rt-types:router-id;
            description
              "Destination Router ID.";
          }
          list sub-tlvs {
            description
              "Inter-Area-Router TLV sub-TLVs.";
            uses unknown-sub-tlv;
          }
        }
      }
    }
    container e-intra-area-prefix {
      when "../../ospf:header/ospf:type = "
         + "'ospfv3-e-lsa:ospfv3-e-intra-area-prefix-lsa'" {
        description
          "Only applies to E-Intra-Area-Prefix-LSAs.";
      }
      description
        "E-Intra-Area-Prefix-LSA contents.";
      reference
        "RFC 8362: OSPFv3 Link State Advertisement (LSA)
         Extensibility, Section 4.8";
      leaf referenced-ls-type {
        type uint16;
        description
          "Referenced Link State type.";
      }
      leaf referenced-link-state-id {
        type uint32;
        description
          "Referenced Link State ID.";
      }
      leaf referenced-adv-router {
        type rt-types:router-id;
        description
          "Referenced advertising router.";
      }
      list e-intra-prefix-tlvs {
        description
          "E-Intra-Area-Prefix-LSA TLVs.";
        container unknown-tlv {
          uses ospf:tlv;
          description
            "Unknown E-Intra-Area-Prefix TLV.";
        }
        uses intra-area-prefix-tlv;
      }
    }
  }

  augment "/rt:routing/"
        + "rt:control-plane-protocols/rt:control-plane-protocol/"
        + "ospf:ospf/ospf:database/"
        + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/"
        + "ospf:as-scope-lsa/ospf:version/ospf:ospfv3/"
        + "ospf:ospfv3/ospf:body" {
    when "../../../../../../../"
       + "rt:type = 'ospf:ospfv3'" {
      description
        "This augmentation is only valid for OSPFv3.";
    }
    description
      "This augmentation adds OSPFv3 AS-scoped Extended LSAs to
       the operational state for an AS instance-level LSDB.";
    container e-as-external {
      when "../../ospf:header/ospf:type = "
         + "'ospfv3-e-lsa:ospfv3-e-as-external-lsa'" {
        description
          "Only applies to E-AS-External-LSAs.";
      }
      description
        "E-AS-External-LSA contents.";
      list e-external-tlvs {
        description
          "E-AS-External-LSA TLVs.";
        container unknown-tlv {
          uses ospf:tlv;
          description
            "Unknown E-External TLV.";
        }
        uses external-prefix-tlv;
      }
      reference
        "RFC 8362: OSPFv3 Link State Advertisement (LSA)
         Extensibility, Section 4.5";
    }
  }
}
</sourcecode>
    </section>
    <section anchor="Security" numbered="true" removeInRFC="false" toc="include" pn="section-5">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-5-1">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" format="default" sectionFormat="of" derivedContent="RFC6241"/> or RESTCONF <xref target="RFC8040" format="default" sectionFormat="of" derivedContent="RFC8040"/>.
The lowest NETCONF layer is the secure transport layer, and the
mandatory-to-implement secure transport is Secure Shell (SSH)
<xref target="RFC6242" format="default" sectionFormat="of" derivedContent="RFC6242"/>. The lowest RESTCONF layer is HTTPS, and the
mandatory-to-implement secure transport is TLS <xref target="RFC8446" format="default" sectionFormat="of" derivedContent="RFC8446"/>.</t>
      <t indent="0" pn="section-5-2">The Network Configuration Access Control Model (NACM) <xref target="RFC8341" format="default" sectionFormat="of" derivedContent="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 indent="0" pn="section-5-3">There are a number of data nodes defined in the
"ietf-ospfv3-extended-lsa.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 indent="3" pn="section-5-4">/ospf:ospf/extended-lsa-support</t>
      <t indent="3" pn="section-5-5">/ospf:ospf/ospf:areas/ospf:area/extended-lsa-support</t>
      <t indent="0" pn="section-5-6">
          The ability to disable or enable OSPFv3 Extended LSA support can result
          in a Denial-of-Service (DoS) attack, since OSPFv3 routers will use solely OSPFv3
          Extended LSAs or OSPFv3 Legacy LSAs for the OSPFv3 SPF computation. OSPFv3
          routers using different types of LSAs will
          result in incomplete reachability and possible partitioning of the OSPFv3 routing
          domain. Refer to <xref target="RFC8362" sectionFormat="of" section="6" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8362#section-6" derivedContent="RFC8362"/>
for more information on
          OSPFv3 Extended LSA compatibility.
      </t>
      <t indent="0" pn="section-5-7">Some of the readable data nodes in the "ietf-ospfv3-extended-lsa.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.</t>
      <t indent="0" pn="section-5-8">Exposing the Link State Database (LSDB) will in turn
      expose the detailed topology of the network. This includes topological information
      from other routers. This may be undesirable 
      due to the fact that exposure may facilitate other attacks. Additionally,
      network operators may consider their topologies to be sensitive confidential
      data.</t>
    </section>
    <section numbered="true" removeInRFC="false" toc="include" pn="section-6">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <t indent="0" pn="section-6-1">Per this document, IANA has registered the following URI in the "IETF XML Registry" <xref target="RFC3688" format="default" sectionFormat="of" derivedContent="RFC3688"/>:
      </t>
      <dl spacing="compact" indent="3" newline="false" pn="section-6-2">
        <dt pn="section-6-2.1">URI:</dt>
        <dd pn="section-6-2.2">urn:ietf:params:xml:ns:yang:ietf-ospfv3-extended-lsa</dd>
        <dt pn="section-6-2.3">Registrant Contact:</dt>
        <dd pn="section-6-2.4">The IESG.</dd>
        <dt pn="section-6-2.5">XML:</dt>
        <dd pn="section-6-2.6">N/A; the requested URI is an XML namespace.</dd>
      </dl>
      <t indent="0" pn="section-6-3">
     Per this document, IANA has registered the following YANG module in the "YANG Module Names"
     registry <xref target="RFC6020" format="default" sectionFormat="of" derivedContent="RFC6020"/>:
      </t>
      <dl spacing="compact" indent="3" newline="false" pn="section-6-4">
        <dt pn="section-6-4.1">Name:</dt>
        <dd pn="section-6-4.2">ietf-ospfv3-extended-lsa</dd>
        <dt pn="section-6-4.3">Maintained by IANA:</dt>
        <dd pn="section-6-4.4">N</dd>
        <dt pn="section-6-4.5">Namespace:</dt>
        <dd pn="section-6-4.6">urn:ietf:params:xml:ns:yang:ietf-ospfv3-extended-lsa</dd>
        <dt pn="section-6-4.7">Prefix:</dt>
        <dd pn="section-6-4.8">ospfv3-e-lsa</dd>
        <dt pn="section-6-4.9">Reference:</dt>
        <dd pn="section-6-4.10">RFC 9587</dd>
      </dl>
    </section>
  </middle>
  <back>
    <references pn="section-7">
      <name slugifiedName="name-references">References</name>
      <references pn="section-7.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <reference anchor="RFC3688" target="https://www.rfc-editor.org/info/rfc3688" quoteTitle="true" derivedAnchor="RFC3688">
          <front>
            <title>The IETF XML Registry</title>
            <author fullname="M. Mealling" initials="M." surname="Mealling"/>
            <date month="January" year="2004"/>
            <abstract>
              <t indent="0">This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="81"/>
          <seriesInfo name="RFC" value="3688"/>
          <seriesInfo name="DOI" value="10.17487/RFC3688"/>
        </reference>
        <reference anchor="RFC5340" target="https://www.rfc-editor.org/info/rfc5340" quoteTitle="true" derivedAnchor="RFC5340">
          <front>
            <title>OSPF for IPv6</title>
            <author fullname="R. Coltun" initials="R." surname="Coltun"/>
            <author fullname="D. Ferguson" initials="D." surname="Ferguson"/>
            <author fullname="J. Moy" initials="J." surname="Moy"/>
            <author fullname="A. Lindem" initials="A." surname="Lindem"/>
            <date month="July" year="2008"/>
            <abstract>
              <t indent="0">This document describes the modifications to OSPF to support version 6 of the Internet Protocol (IPv6). The fundamental mechanisms of OSPF (flooding, Designated Router (DR) election, area support, Short Path First (SPF) calculations, etc.) remain unchanged. However, some changes have been necessary, either due to changes in protocol semantics between IPv4 and IPv6, or simply to handle the increased address size of IPv6. These modifications will necessitate incrementing the protocol version from version 2 to version 3. OSPF for IPv6 is also referred to as OSPF version 3 (OSPFv3).</t>
              <t indent="0">Changes between OSPF for IPv4, OSPF Version 2, and OSPF for IPv6 as described herein include the following. Addressing semantics have been removed from OSPF packets and the basic Link State Advertisements (LSAs). New LSAs have been created to carry IPv6 addresses and prefixes. OSPF now runs on a per-link basis rather than on a per-IP-subnet basis. Flooding scope for LSAs has been generalized. Authentication has been removed from the OSPF protocol and instead relies on IPv6's Authentication Header and Encapsulating Security Payload (ESP).</t>
              <t indent="0">Even with larger IPv6 addresses, most packets in OSPF for IPv6 are almost as compact as those in OSPF for IPv4. Most fields and packet- size limitations present in OSPF for IPv4 have been relaxed. In addition, option handling has been made more flexible.</t>
              <t indent="0">All of OSPF for IPv4's optional capabilities, including demand circuit support and Not-So-Stubby Areas (NSSAs), are also supported in OSPF for IPv6. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5340"/>
          <seriesInfo name="DOI" value="10.17487/RFC5340"/>
        </reference>
        <reference anchor="RFC6020" target="https://www.rfc-editor.org/info/rfc6020" quoteTitle="true" derivedAnchor="RFC6020">
          <front>
            <title>YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)</title>
            <author fullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/>
            <date month="October" year="2010"/>
            <abstract>
              <t indent="0">YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6020"/>
          <seriesInfo name="DOI" value="10.17487/RFC6020"/>
        </reference>
        <reference anchor="RFC6241" target="https://www.rfc-editor.org/info/rfc6241" quoteTitle="true" derivedAnchor="RFC6241">
          <front>
            <title>Network Configuration Protocol (NETCONF)</title>
            <author fullname="R. Enns" initials="R." role="editor" surname="Enns"/>
            <author fullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/>
            <author fullname="J. Schoenwaelder" initials="J." role="editor" surname="Schoenwaelder"/>
            <author fullname="A. Bierman" initials="A." role="editor" surname="Bierman"/>
            <date month="June" year="2011"/>
            <abstract>
              <t indent="0">The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6241"/>
          <seriesInfo name="DOI" value="10.17487/RFC6241"/>
        </reference>
        <reference anchor="RFC6242" target="https://www.rfc-editor.org/info/rfc6242" quoteTitle="true" derivedAnchor="RFC6242">
          <front>
            <title>Using the NETCONF Protocol over Secure Shell (SSH)</title>
            <author fullname="M. Wasserman" initials="M." surname="Wasserman"/>
            <date month="June" year="2011"/>
            <abstract>
              <t indent="0">This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. This document obsoletes RFC 4742. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6242"/>
          <seriesInfo name="DOI" value="10.17487/RFC6242"/>
        </reference>
        <reference anchor="RFC6991" target="https://www.rfc-editor.org/info/rfc6991" quoteTitle="true" derivedAnchor="RFC6991">
          <front>
            <title>Common YANG Data Types</title>
            <author fullname="J. Schoenwaelder" initials="J." role="editor" surname="Schoenwaelder"/>
            <date month="July" year="2013"/>
            <abstract>
              <t indent="0">This document introduces a collection of common data types to be used with the YANG data modeling language. This document obsoletes RFC 6021.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6991"/>
          <seriesInfo name="DOI" value="10.17487/RFC6991"/>
        </reference>
        <reference anchor="RFC7950" target="https://www.rfc-editor.org/info/rfc7950" quoteTitle="true" derivedAnchor="RFC7950">
          <front>
            <title>The YANG 1.1 Data Modeling Language</title>
            <author fullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/>
            <date month="August" year="2016"/>
            <abstract>
              <t indent="0">YANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols. This document describes the syntax and semantics of version 1.1 of the YANG language. YANG version 1.1 is a maintenance release of the YANG language, addressing ambiguities and defects in the original specification. There are a small number of backward incompatibilities from YANG version 1. This document also specifies the YANG mappings to the Network Configuration Protocol (NETCONF).</t>
            </abstract>
          </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" quoteTitle="true" derivedAnchor="RFC8040">
          <front>
            <title>RESTCONF Protocol</title>
            <author fullname="A. Bierman" initials="A." surname="Bierman"/>
            <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
            <author fullname="K. Watsen" initials="K." surname="Watsen"/>
            <date month="January" year="2017"/>
            <abstract>
              <t indent="0">This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF).</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8040"/>
          <seriesInfo name="DOI" value="10.17487/RFC8040"/>
        </reference>
        <reference anchor="RFC8294" target="https://www.rfc-editor.org/info/rfc8294" quoteTitle="true" derivedAnchor="RFC8294">
          <front>
            <title>Common YANG Data Types for the Routing Area</title>
            <author fullname="X. Liu" initials="X." surname="Liu"/>
            <author fullname="Y. Qu" initials="Y." surname="Qu"/>
            <author fullname="A. Lindem" initials="A." surname="Lindem"/>
            <author fullname="C. Hopps" initials="C." surname="Hopps"/>
            <author fullname="L. Berger" initials="L." surname="Berger"/>
            <date month="December" year="2017"/>
            <abstract>
              <t indent="0">This document defines a collection of common data types using the YANG data modeling language. These derived common types are designed to be imported by other modules defined in the routing area.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8294"/>
          <seriesInfo name="DOI" value="10.17487/RFC8294"/>
        </reference>
        <reference anchor="RFC8341" target="https://www.rfc-editor.org/info/rfc8341" quoteTitle="true" derivedAnchor="RFC8341">
          <front>
            <title>Network Configuration Access Control Model</title>
            <author fullname="A. Bierman" initials="A." surname="Bierman"/>
            <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
            <date month="March" year="2018"/>
            <abstract>
              <t indent="0">The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF or RESTCONF protocol access for particular users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. This document defines such an access control model.</t>
              <t indent="0">This document obsoletes RFC 6536.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="91"/>
          <seriesInfo name="RFC" value="8341"/>
          <seriesInfo name="DOI" value="10.17487/RFC8341"/>
        </reference>
        <reference anchor="RFC8342" target="https://www.rfc-editor.org/info/rfc8342" quoteTitle="true" derivedAnchor="RFC8342">
          <front>
            <title>Network Management Datastore Architecture (NMDA)</title>
            <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
            <author fullname="J. Schoenwaelder" initials="J." surname="Schoenwaelder"/>
            <author fullname="P. Shafer" initials="P." surname="Shafer"/>
            <author fullname="K. Watsen" initials="K." surname="Watsen"/>
            <author fullname="R. Wilton" initials="R." surname="Wilton"/>
            <date month="March" year="2018"/>
            <abstract>
              <t indent="0">Datastores are a fundamental concept binding the data models written in the YANG data modeling language to network management protocols such as the Network Configuration Protocol (NETCONF) and RESTCONF. This document defines an architectural framework for datastores based on the experience gained with the initial simpler model, addressing requirements that were not well supported in the initial model. This document updates RFC 7950.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8342"/>
          <seriesInfo name="DOI" value="10.17487/RFC8342"/>
        </reference>
        <reference anchor="RFC8349" target="https://www.rfc-editor.org/info/rfc8349" quoteTitle="true" derivedAnchor="RFC8349">
          <front>
            <title>A YANG Data Model for Routing Management (NMDA Version)</title>
            <author fullname="L. Lhotka" initials="L." surname="Lhotka"/>
            <author fullname="A. Lindem" initials="A." surname="Lindem"/>
            <author fullname="Y. Qu" initials="Y." surname="Qu"/>
            <date month="March" year="2018"/>
            <abstract>
              <t indent="0">This document specifies three YANG modules and one submodule. Together, they form the core routing data model that serves as a framework for configuring and managing a routing subsystem. It is expected that these modules will be augmented by additional YANG modules defining data models for control-plane protocols, route filters, and other functions. The core routing data model provides common building blocks for such extensions -- routes, Routing Information Bases (RIBs), and control-plane protocols.</t>
              <t indent="0">The YANG modules in this document conform to the Network Management Datastore Architecture (NMDA). This document obsoletes RFC 8022.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8349"/>
          <seriesInfo name="DOI" value="10.17487/RFC8349"/>
        </reference>
        <reference anchor="RFC8362" target="https://www.rfc-editor.org/info/rfc8362" quoteTitle="true" derivedAnchor="RFC8362">
          <front>
            <title>OSPFv3 Link State Advertisement (LSA) Extensibility</title>
            <author fullname="A. Lindem" initials="A." surname="Lindem"/>
            <author fullname="A. Roy" initials="A." surname="Roy"/>
            <author fullname="D. Goethals" initials="D." surname="Goethals"/>
            <author fullname="V. Reddy Vallem" initials="V." surname="Reddy Vallem"/>
            <author fullname="F. Baker" initials="F." surname="Baker"/>
            <date month="April" year="2018"/>
            <abstract>
              <t indent="0">OSPFv3 requires functional extension beyond what can readily be done with the fixed-format Link State Advertisement (LSA) as described in RFC 5340. Without LSA extension, attributes associated with OSPFv3 links and advertised IPv6 prefixes must be advertised in separate LSAs and correlated to the fixed-format LSAs. This document extends the LSA format by encoding the existing OSPFv3 LSA information in Type-Length-Value (TLV) tuples and allowing advertisement of additional information with additional TLVs. Backward-compatibility mechanisms are also described.</t>
              <t indent="0">This document updates RFC 5340, "OSPF for IPv6", and RFC 5838, "Support of Address Families in OSPFv3", by providing TLV-based encodings for the base OSPFv3 unicast support and OSPFv3 address family support.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8362"/>
          <seriesInfo name="DOI" value="10.17487/RFC8362"/>
        </reference>
        <reference anchor="RFC8446" target="https://www.rfc-editor.org/info/rfc8446" quoteTitle="true" derivedAnchor="RFC8446">
          <front>
            <title>The Transport Layer Security (TLS) Protocol Version 1.3</title>
            <author fullname="E. Rescorla" initials="E." surname="Rescorla"/>
            <date month="August" year="2018"/>
            <abstract>
              <t indent="0">This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery.</t>
              <t indent="0">This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8446"/>
          <seriesInfo name="DOI" value="10.17487/RFC8446"/>
        </reference>
        <reference anchor="RFC9129" target="https://www.rfc-editor.org/info/rfc9129" quoteTitle="true" derivedAnchor="RFC9129">
          <front>
            <title>YANG Data Model for the OSPF Protocol</title>
            <author fullname="D. Yeung" initials="D." surname="Yeung"/>
            <author fullname="Y. Qu" initials="Y." surname="Qu"/>
            <author fullname="Z. Zhang" initials="Z." surname="Zhang"/>
            <author fullname="I. Chen" initials="I." surname="Chen"/>
            <author fullname="A. Lindem" initials="A." surname="Lindem"/>
            <date month="October" year="2022"/>
            <abstract>
              <t indent="0">This document defines a YANG data model that can be used to configure and manage OSPF. The model is based on YANG 1.1 as defined in RFC 7950 and conforms to the Network Management Datastore Architecture (NMDA) as described in RFC 8342.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9129"/>
          <seriesInfo name="DOI" value="10.17487/RFC9129"/>
        </reference>
        <reference anchor="W3C.REC-xml-20081126" target="https://www.w3.org/TR/xml/" quoteTitle="true" derivedAnchor="W3C.REC-xml-20081126">
          <front>
            <title>Extensible Markup Language (XML) 1.0 (Fifth Edition)</title>
            <author initials="T." surname="Bray"/>
            <author initials="J." surname="Paoli"/>
            <author initials="C. M." surname="Sperberg-McQueen"/>
            <author initials="E." surname="Maler"/>
            <author initials="F." surname="Yergeau"/>
            <date month="November" year="2008"/>
          </front>
          <refcontent>W3C Recommendation REC-xml-20081126</refcontent>
        </reference>
      </references>
      <references pn="section-7.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="RFC7951" target="https://www.rfc-editor.org/info/rfc7951" quoteTitle="true" derivedAnchor="RFC7951">
          <front>
            <title>JSON Encoding of Data Modeled with YANG</title>
            <author fullname="L. Lhotka" initials="L." surname="Lhotka"/>
            <date month="August" year="2016"/>
            <abstract>
              <t indent="0">This document defines encoding rules for representing configuration data, state data, parameters of Remote Procedure Call (RPC) operations or actions, and notifications defined using YANG as JavaScript Object Notation (JSON) text.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7951"/>
          <seriesInfo name="DOI" value="10.17487/RFC7951"/>
        </reference>
        <reference anchor="RFC8340" target="https://www.rfc-editor.org/info/rfc8340" quoteTitle="true" derivedAnchor="RFC8340">
          <front>
            <title>YANG Tree Diagrams</title>
            <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
            <author fullname="L. Berger" initials="L." role="editor" surname="Berger"/>
            <date month="March" year="2018"/>
            <abstract>
              <t indent="0">This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="215"/>
          <seriesInfo name="RFC" value="8340"/>
          <seriesInfo name="DOI" value="10.17487/RFC8340"/>
        </reference>
        <reference anchor="RFC8792" target="https://www.rfc-editor.org/info/rfc8792" quoteTitle="true" derivedAnchor="RFC8792">
          <front>
            <title>Handling Long Lines in Content of Internet-Drafts and RFCs</title>
            <author fullname="K. Watsen" initials="K." surname="Watsen"/>
            <author fullname="E. Auerswald" initials="E." surname="Auerswald"/>
            <author fullname="A. Farrel" initials="A." surname="Farrel"/>
            <author fullname="Q. Wu" initials="Q." surname="Wu"/>
            <date month="June" year="2020"/>
            <abstract>
              <t indent="0">This document defines two strategies for handling long lines in width-bounded text content. One strategy, called the "single backslash" strategy, is based on the historical use of a single backslash ('\') character to indicate where line-folding has occurred, with the continuation occurring with the first character that is not a space character (' ') on the next line. The second strategy, called the "double backslash" strategy, extends the first strategy by adding a second backslash character to identify where the continuation begins and is thereby able to handle cases not supported by the first strategy. Both strategies use a self-describing header enabling automated reconstitution of the original content.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8792"/>
          <seriesInfo name="DOI" value="10.17487/RFC8792"/>
        </reference>
      </references>
    </references>
    <section numbered="true" removeInRFC="false" toc="include" pn="section-appendix.a">
      <name slugifiedName="name-configuration-example">Configuration Example</name>
      <t indent="0" pn="section-appendix.a-1">The following is an XML example (per <xref target="W3C.REC-xml-20081126" format="default" sectionFormat="of" derivedContent="W3C.REC-xml-20081126"/>) using the YANG data model for OSPFv3 Extended LSAs. (Line breaks are used per <xref target="RFC8792" format="default" sectionFormat="of" derivedContent="RFC8792"/> and are for display purposes only.)</t>
      <sourcecode type="xml" markers="false" pn="section-appendix.a-2">
Note: '\' line wrapping per RFC 8792.

&lt;?xml version='1.0' encoding='UTF-8'?&gt;
  &lt;routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing"&gt;
    &lt;router-id&gt;192.0.2.1&lt;/router-id&gt;
    &lt;control-plane-protocols&gt;
      &lt;control-plane-protocol&gt;
        &lt;type xmlns:ospf="urn:ietf:params:xml:ns:yang:ietf-ospf"&gt;\
        ospf:ospfv3&lt;/type&gt;
        &lt;name&gt;"OSPFv3"&lt;/name&gt;
        &lt;ospf xmlns="urn:ietf:params:xml:ns:yang:ietf-ospf"&gt;
          &lt;extended-lsa-support xmlns="urn:ietf:params:xml:ns:yang:\
            ietf-ospfv3-extended-lsa"&gt;true&lt;/extended-lsa-support&gt;
        &lt;/ospf&gt;
      &lt;/control-plane-protocol&gt;
    &lt;/control-plane-protocols&gt;
  &lt;/routing&gt;
</sourcecode>
      <t indent="0" pn="section-appendix.a-3">The following is the same example using JSON format <xref target="RFC7951" format="default" sectionFormat="of" derivedContent="RFC7951"/>.</t>
      <sourcecode type="json" markers="false" pn="section-appendix.a-4">
{
  "routing": {
    "router-id": "192.0.2.1",
    "control-plane-protocols": {
      "control-plane-protocol": {
        "type": "ospf:ospfv3",
        "name": "\"OSPFv3\"",
        "ospf": {
          "extended-lsa-support": true
        }
      }
    }
  }
}
</sourcecode>
    </section>
    <section anchor="Acknowledgements" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.b">
      <name slugifiedName="name-acknowledgements">Acknowledgements</name>
      <t indent="0" pn="section-appendix.b-1">The YANG data model defined in this document was developed using the suite of YANG tools written
      and maintained by numerous authors.</t>
      <t indent="0" pn="section-appendix.b-2">Thanks much to <contact fullname="Tom Petch"/>, <contact fullname="Mahesh Jethanandani"/>, <contact fullname="Renato Westphal"/>,
      <contact fullname="Victoria Pritchard"/>, <contact fullname="Reshad Rahman"/>, and <contact fullname="Chris Hopps"/> for their review and comments.</t>
    </section>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.c">
      <name slugifiedName="name-authors-addresses">Authors' Addresses</name>
      <author fullname="Acee Lindem" initials="A." surname="Lindem">
        <organization showOnFrontPage="true">LabN Consulting, L.L.C.</organization>
        <address>
          <postal>
            <street>301 Midenhall Way</street>
            <city>Cary</city>
            <region>NC</region>
            <code>27513</code>
            <country>United States of America</country>
          </postal>
          <email>acee.ietf@gmail.com</email>
        </address>
      </author>
      <author fullname="Sharmila Palani" initials="S." surname="Palani">
        <organization showOnFrontPage="true">Microsoft</organization>
        <address>
          <postal>
            <street>1 Microsoft Way</street>
            <city>Redmond</city>
            <region>WA</region>
            <code>98052</code>
            <country>United States of America</country>
          </postal>
          <email>sharmila.palani@microsoft.com</email>
        </address>
      </author>
      <author fullname="Yingzhen Qu" initials="Y" surname="Qu">
        <organization showOnFrontPage="true">Futurewei Technologies</organization>
        <address>
          <postal>
            <street>2330 Central Expressway</street>
            <city>Santa Clara</city>
            <region>CA</region>
            <code>95050</code>
            <country>United States of America</country>
          </postal>
          <email>yingzhen.ietf@gmail.com</email>
        </address>
      </author>
    </section>
  </back>
</rfc>
