File: rfc9130.html

package info (click to toggle)
doc-rfc 20230121-1
links: PTS, VCS
area: non-free
in suites: forky, sid, trixie
size: 1,609,944 kB
file content (7364 lines) | stat: -rw-r--r-- 256,932 bytes
<!DOCTYPE html>
<html lang="en" class="RFC">
<head>
<meta charset="utf-8">
<meta content="Common,Latin" name="scripts">
<meta content="initial-scale=1.0" name="viewport">
<title>RFC 9130: YANG Data Model for the IS-IS Protocol</title>
<meta content="Stephane Litkowski" name="author">
<meta content="Derek Yeung" name="author">
<meta content="Acee Lindem" name="author">
<meta content="Jeffrey Zhang" name="author">
<meta content="Ladislav Lhotka" name="author">
<meta content="
       This document defines a YANG data model that can be used to
      configure and manage the IS-IS protocol on network elements.
       
    " name="description">
<meta content="xml2rfc 3.15.1" name="generator">
<meta content="9130" name="rfc.number">
<!-- Generator version information:
  xml2rfc 3.15.1
    Python 3.9.13
    appdirs 1.4.4
    ConfigArgParse 1.5.3
    google-i18n-address 2.5.1
    html5lib 1.1
    intervaltree 3.1.0
    Jinja2 3.1.2
    kitchen 1.2.6
    lxml 4.9.0
    MarkupSafe 2.1.1
    pycountry 22.3.5
    PyYAML 6.0
    requests 2.28.0
    setuptools 44.1.1
    six 1.16.0
    weasyprint 56.1
-->
<link href="rfc9130.xml" rel="alternate" type="application/rfc+xml">
<link href="#copyright" rel="license">
<style type="text/css">/*

  NOTE: Changes at the bottom of this file overrides some earlier settings.

  Once the style has stabilized and has been adopted as an official RFC style,
  this can be consolidated so that style settings occur only in one place, but
  for now the contents of this file consists first of the initial CSS work as
  provided to the RFC Formatter (xml2rfc) work, followed by itemized and
  commented changes found necssary during the development of the v3
  formatters.

*/

/* fonts */
@import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
@import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
@import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */

@viewport {
  zoom: 1.0;
  width: extend-to-zoom;
}
@-ms-viewport {
  width: extend-to-zoom;
  zoom: 1.0;
}
/* general and mobile first */
html {
}
body {
  max-width: 90%;
  margin: 1.5em auto;
  color: #222;
  background-color: #fff;
  font-size: 14px;
  font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
  line-height: 1.6;
  scroll-behavior: smooth;
}
.ears {
  display: none;
}

/* headings */
#title, h1, h2, h3, h4, h5, h6 {
  margin: 1em 0 0.5em;
  font-weight: bold;
  line-height: 1.3;
}
#title {
  clear: both;
  border-bottom: 1px solid #ddd;
  margin: 0 0 0.5em 0;
  padding: 1em 0 0.5em;
}
.author {
  padding-bottom: 4px;
}
h1 {
  font-size: 26px;
  margin: 1em 0;
}
h2 {
  font-size: 22px;
  margin-top: -20px;  /* provide offset for in-page anchors */
  padding-top: 33px;
}
h3 {
  font-size: 18px;
  margin-top: -36px;  /* provide offset for in-page anchors */
  padding-top: 42px;
}
h4 {
  font-size: 16px;
  margin-top: -36px;  /* provide offset for in-page anchors */
  padding-top: 42px;
}
h5, h6 {
  font-size: 14px;
}
#n-copyright-notice {
  border-bottom: 1px solid #ddd;
  padding-bottom: 1em;
  margin-bottom: 1em;
}
/* general structure */
p {
  padding: 0;
  margin: 0 0 1em 0;
  text-align: left;
}
div, span {
  position: relative;
}
div {
  margin: 0;
}
.alignRight.art-text {
  background-color: #f9f9f9;
  border: 1px solid #eee;
  border-radius: 3px;
  padding: 1em 1em 0;
  margin-bottom: 1.5em;
}
.alignRight.art-text pre {
  padding: 0;
}
.alignRight {
  margin: 1em 0;
}
.alignRight > *:first-child {
  border: none;
  margin: 0;
  float: right;
  clear: both;
}
.alignRight > *:nth-child(2) {
  clear: both;
  display: block;
  border: none;
}
svg {
  display: block;
}
.alignCenter.art-text {
  background-color: #f9f9f9;
  border: 1px solid #eee;
  border-radius: 3px;
  padding: 1em 1em 0;
  margin-bottom: 1.5em;
}
.alignCenter.art-text pre {
  padding: 0;
}
.alignCenter {
  margin: 1em 0;
}
.alignCenter > *:first-child {
  display: table;
  border: none;
  margin: 0 auto;
}

/* lists */
ol, ul {
  padding: 0;
  margin: 0 0 1em 2em;
}
ol ol, ul ul, ol ul, ul ol {
  margin-left: 1em;
}
li {
  margin: 0 0 0.25em 0;
}
.ulCompact li {
  margin: 0;
}
ul.empty, .ulEmpty {
  list-style-type: none;
}
ul.empty li, .ulEmpty li {
  margin-top: 0.5em;
}
ul.ulBare, li.ulBare {
  margin-left: 0em !important;
}
ul.compact, .ulCompact,
ol.compact, .olCompact {
  line-height: 100%;
  margin: 0 0 0 2em;
}

/* definition lists */
dl {
}
dl > dt {
  float: left;
  margin-right: 1em;
}
/* 
dl.nohang > dt {
  float: none;
}
*/
dl > dd {
  margin-bottom: .8em;
  min-height: 1.3em;
}
dl.compact > dd, .dlCompact > dd {
  margin-bottom: 0em;
}
dl > dd > dl {
  margin-top: 0.5em;
  margin-bottom: 0em;
}

/* links */
a {
  text-decoration: none;
}
a[href] {
  color: #22e; /* Arlen: WCAG 2019 */
}
a[href]:hover {
  background-color: #f2f2f2;
}
figcaption a[href],
a[href].selfRef {
  color: #222;
}
/* XXX probably not this:
a.selfRef:hover {
  background-color: transparent;
  cursor: default;
} */

/* Figures */
tt, code, pre {
  background-color: #f9f9f9;
  font-family: 'Roboto Mono', monospace;
}
pre {
  border: 1px solid #eee;
  margin: 0;
  padding: 1em;
}
img {
  max-width: 100%;
}
figure {
  margin: 0;
}
figure blockquote {
  margin: 0.8em 0.4em 0.4em;
}
figcaption {
  font-style: italic;
  margin: 0 0 1em 0;
}
@media screen {
  pre {
    overflow-x: auto;
    max-width: 100%;
    max-width: calc(100% - 22px);
  }
}

/* aside, blockquote */
aside, blockquote {
  margin-left: 0;
  padding: 1.2em 2em;
}
blockquote {
  background-color: #f9f9f9;
  color: #111; /* Arlen: WCAG 2019 */
  border: 1px solid #ddd;
  border-radius: 3px;
  margin: 1em 0;
}
cite {
  display: block;
  text-align: right;
  font-style: italic;
}

/* tables */
table {
  width: 100%;
  margin: 0 0 1em;
  border-collapse: collapse;
  border: 1px solid #eee;
}
th, td {
  text-align: left;
  vertical-align: top;
  padding: 0.5em 0.75em;
}
th {
  text-align: left;
  background-color: #e9e9e9;
}
tr:nth-child(2n+1) > td {
  background-color: #f5f5f5;
}
table caption {
  font-style: italic;
  margin: 0;
  padding: 0;
  text-align: left;
}
table p {
  /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
     be allowed within tables more generally, it would be far better to select on a class. */
  margin: 0;
}

/* pilcrow */
a.pilcrow {
  color: #666; /* Arlen: AHDJ 2019 */
  text-decoration: none;
  visibility: hidden;
  user-select: none;
  -ms-user-select: none;
  -o-user-select:none;
  -moz-user-select: none;
  -khtml-user-select: none;
  -webkit-user-select: none;
  -webkit-touch-callout: none;
}
@media screen {
  aside:hover > a.pilcrow,
  p:hover > a.pilcrow,
  blockquote:hover > a.pilcrow,
  div:hover > a.pilcrow,
  li:hover > a.pilcrow,
  pre:hover > a.pilcrow {
    visibility: visible;
  }
  a.pilcrow:hover {
    background-color: transparent;
  }
}

/* misc */
hr {
  border: 0;
  border-top: 1px solid #eee;
}
.bcp14 {
  font-variant: small-caps;
}

.role {
  font-variant: all-small-caps;
}

/* info block */
#identifiers {
  margin: 0;
  font-size: 0.9em;
}
#identifiers dt {
  width: 3em;
  clear: left;
}
#identifiers dd {
  float: left;
  margin-bottom: 0;
}
/* Fix PDF info block run off issue */
@media print {
  #identifiers dd {
    float: none;
  }
}
#identifiers .authors .author {
  display: inline-block;
  margin-right: 1.5em;
}
#identifiers .authors .org {
  font-style: italic;
}

/* The prepared/rendered info at the very bottom of the page */
.docInfo {
  color: #666; /* Arlen: WCAG 2019 */
  font-size: 0.9em;
  font-style: italic;
  margin-top: 2em;
}
.docInfo .prepared {
  float: left;
}
.docInfo .prepared {
  float: right;
}

/* table of contents */
#toc  {
  padding: 0.75em 0 2em 0;
  margin-bottom: 1em;
}
nav.toc ul {
  margin: 0 0.5em 0 0;
  padding: 0;
  list-style: none;
}
nav.toc li {
  line-height: 1.3em;
  margin: 0.75em 0;
  padding-left: 1.2em;
  text-indent: -1.2em;
}
/* references */
.references dt {
  text-align: right;
  font-weight: bold;
  min-width: 7em;
}
.references dd {
  margin-left: 8em;
  overflow: auto;
}

.refInstance {
  margin-bottom: 1.25em;
}

.references .ascii {
  margin-bottom: 0.25em;
}

/* index */
.index ul {
  margin: 0 0 0 1em;
  padding: 0;
  list-style: none;
}
.index ul ul {
  margin: 0;
}
.index li {
  margin: 0;
  text-indent: -2em;
  padding-left: 2em;
  padding-bottom: 5px;
}
.indexIndex {
  margin: 0.5em 0 1em;
}
.index a {
  font-weight: 700;
}
/* make the index two-column on all but the smallest screens */
@media (min-width: 600px) {
  .index ul {
    -moz-column-count: 2;
    -moz-column-gap: 20px;
  }
  .index ul ul {
    -moz-column-count: 1;
    -moz-column-gap: 0;
  }
}

/* authors */
address.vcard {
  font-style: normal;
  margin: 1em 0;
}

address.vcard .nameRole {
  font-weight: 700;
  margin-left: 0;
}
address.vcard .label {
  font-family: "Noto Sans",Arial,Helvetica,sans-serif;
  margin: 0.5em 0;
}
address.vcard .type {
  display: none;
}
.alternative-contact {
  margin: 1.5em 0 1em;
}
hr.addr {
  border-top: 1px dashed;
  margin: 0;
  color: #ddd;
  max-width: calc(100% - 16px);
}

/* temporary notes */
.rfcEditorRemove::before {
  position: absolute;
  top: 0.2em;
  right: 0.2em;
  padding: 0.2em;
  content: "The RFC Editor will remove this note";
  color: #9e2a00; /* Arlen: WCAG 2019 */
  background-color: #ffd; /* Arlen: WCAG 2019 */
}
.rfcEditorRemove {
  position: relative;
  padding-top: 1.8em;
  background-color: #ffd; /* Arlen: WCAG 2019 */
  border-radius: 3px;
}
.cref {
  background-color: #ffd; /* Arlen: WCAG 2019 */
  padding: 2px 4px;
}
.crefSource {
  font-style: italic;
}
/* alternative layout for smaller screens */
@media screen and (max-width: 1023px) {
  body {
    padding-top: 2em;
  }
  #title {
    padding: 1em 0;
  }
  h1 {
    font-size: 24px;
  }
  h2 {
    font-size: 20px;
    margin-top: -18px;  /* provide offset for in-page anchors */
    padding-top: 38px;
  }
  #identifiers dd {
    max-width: 60%;
  }
  #toc {
    position: fixed;
    z-index: 2;
    top: 0;
    right: 0;
    padding: 0;
    margin: 0;
    background-color: inherit;
    border-bottom: 1px solid #ccc;
  }
  #toc h2 {
    margin: -1px 0 0 0;
    padding: 4px 0 4px 6px;
    padding-right: 1em;
    min-width: 190px;
    font-size: 1.1em;
    text-align: right;
    background-color: #444;
    color: white;
    cursor: pointer;
  }
  #toc h2::before { /* css hamburger */
    float: right;
    position: relative;
    width: 1em;
    height: 1px;
    left: -164px;
    margin: 6px 0 0 0;
    background: white none repeat scroll 0 0;
    box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
    content: "";
  }
  #toc nav {
    display: none;
    padding: 0.5em 1em 1em;
    overflow: auto;
    height: calc(100vh - 48px);
    border-left: 1px solid #ddd;
  }
}

/* alternative layout for wide screens */
@media screen and (min-width: 1024px) {
  body {
    max-width: 724px;
    margin: 42px auto;
    padding-left: 1.5em;
    padding-right: 29em;
  }
  #toc {
    position: fixed;
    top: 42px;
    right: 42px;
    width: 25%;
    margin: 0;
    padding: 0 1em;
    z-index: 1;
  }
  #toc h2 {
    border-top: none;
    border-bottom: 1px solid #ddd;
    font-size: 1em;
    font-weight: normal;
    margin: 0;
    padding: 0.25em 1em 1em 0;
  }
  #toc nav {
    display: block;
    height: calc(90vh - 84px);
    bottom: 0;
    padding: 0.5em 0 0;
    overflow: auto;
  }
  img { /* future proofing */
    max-width: 100%;
    height: auto;
  }
}

/* pagination */
@media print {
  body {

    width: 100%;
  }
  p {
    orphans: 3;
    widows: 3;
  }
  #n-copyright-notice {
    border-bottom: none;
  }
  #toc, #n-introduction {
    page-break-before: always;
  }
  #toc {
    border-top: none;
    padding-top: 0;
  }
  figure, pre {
    page-break-inside: avoid;
  }
  figure {
    overflow: scroll;
  }
  pre.breakable {
    break-inside: auto;
  }
  h1, h2, h3, h4, h5, h6 {
    page-break-after: avoid;
  }
  h2+*, h3+*, h4+*, h5+*, h6+* {
    page-break-before: avoid;
  }
  pre {
    white-space: pre-wrap;
    word-wrap: break-word;
    font-size: 10pt;
  }
  table {
    border: 1px solid #ddd;
  }
  td {
    border-top: 1px solid #ddd;
  }
}

/* This is commented out here, as the string-set: doesn't
   pass W3C validation currently */
/*
.ears thead .left {
  string-set: ears-top-left content();
}

.ears thead .center {
  string-set: ears-top-center content();
}

.ears thead .right {
  string-set: ears-top-right content();
}

.ears tfoot .left {
  string-set: ears-bottom-left content();
}

.ears tfoot .center {
  string-set: ears-bottom-center content();
}

.ears tfoot .right {
  string-set: ears-bottom-right content();
}
*/

@page :first {
  padding-top: 0;
  @top-left {
    content: normal;
    border: none;
  }
  @top-center {
    content: normal;
    border: none;
  }
  @top-right {
    content: normal;
    border: none;
  }
}

@page {
  size: A4;
  margin-bottom: 45mm;
  padding-top: 20px;
  /* The follwing is commented out here, but set appropriately by in code, as
     the content depends on the document */
  /*
  @top-left {
    content: 'Internet-Draft';
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @top-left {
    content: string(ears-top-left);
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @top-center {
    content: string(ears-top-center);
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @top-right {
    content: string(ears-top-right);
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @bottom-left {
    content: string(ears-bottom-left);
    vertical-align: top;
    border-top: solid 1px #ccc;
  }
  @bottom-center {
    content: string(ears-bottom-center);
    vertical-align: top;
    border-top: solid 1px #ccc;
  }
  @bottom-right {
      content: '[Page ' counter(page) ']';
      vertical-align: top;
      border-top: solid 1px #ccc;
  }
  */

}

/* Changes introduced to fix issues found during implementation */
/* Make sure links are clickable even if overlapped by following H* */
a {
  z-index: 2;
}
/* Separate body from document info even without intervening H1 */
section {
  clear: both;
}


/* Top align author divs, to avoid names without organization dropping level with org names */
.author {
  vertical-align: top;
}

/* Leave room in document info to show Internet-Draft on one line */
#identifiers dt {
  width: 8em;
}

/* Don't waste quite as much whitespace between label and value in doc info */
#identifiers dd {
  margin-left: 1em;
}

/* Give floating toc a background color (needed when it's a div inside section */
#toc {
  background-color: white;
}

/* Make the collapsed ToC header render white on gray also when it's a link */
@media screen and (max-width: 1023px) {
  #toc h2 a,
  #toc h2 a:link,
  #toc h2 a:focus,
  #toc h2 a:hover,
  #toc a.toplink,
  #toc a.toplink:hover {
    color: white;
    background-color: #444;
    text-decoration: none;
  }
}

/* Give the bottom of the ToC some whitespace */
@media screen and (min-width: 1024px) {
  #toc {
    padding: 0 0 1em 1em;
  }
}

/* Style section numbers with more space between number and title */
.section-number {
  padding-right: 0.5em;
}

/* prevent monospace from becoming overly large */
tt, code, pre {
  font-size: 95%;
}

/* Fix the height/width aspect for ascii art*/
pre.sourcecode,
.art-text pre {
  line-height: 1.12;
}


/* Add styling for a link in the ToC that points to the top of the document */
a.toplink {
  float: right;
  margin-right: 0.5em;
}

/* Fix the dl styling to match the RFC 7992 attributes */
dl > dt,
dl.dlParallel > dt {
  float: left;
  margin-right: 1em;
}
dl.dlNewline > dt {
  float: none;
}

/* Provide styling for table cell text alignment */
table td.text-left,
table th.text-left {
  text-align: left;
}
table td.text-center,
table th.text-center {
  text-align: center;
}
table td.text-right,
table th.text-right {
  text-align: right;
}

/* Make the alternative author contact informatio look less like just another
   author, and group it closer with the primary author contact information */
.alternative-contact {
  margin: 0.5em 0 0.25em 0;
}
address .non-ascii {
  margin: 0 0 0 2em;
}

/* With it being possible to set tables with alignment
  left, center, and right, { width: 100%; } does not make sense */
table {
  width: auto;
}

/* Avoid reference text that sits in a block with very wide left margin,
   because of a long floating dt label.*/
.references dd {
  overflow: visible;
}

/* Control caption placement */
caption {
  caption-side: bottom;
}

/* Limit the width of the author address vcard, so names in right-to-left
   script don't end up on the other side of the page. */

address.vcard {
  max-width: 30em;
  margin-right: auto;
}

/* For address alignment dependent on LTR or RTL scripts */
address div.left {
  text-align: left;
}
address div.right {
  text-align: right;
}

/* Provide table alignment support.  We can't use the alignX classes above
   since they do unwanted things with caption and other styling. */
table.right {
 margin-left: auto;
 margin-right: 0;
}
table.center {
 margin-left: auto;
 margin-right: auto;
}
table.left {
 margin-left: 0;
 margin-right: auto;
}

/* Give the table caption label the same styling as the figcaption */
caption a[href] {
  color: #222;
}

@media print {
  .toplink {
    display: none;
  }

  /* avoid overwriting the top border line with the ToC header */
  #toc {
    padding-top: 1px;
  }

  /* Avoid page breaks inside dl and author address entries */
  .vcard {
    page-break-inside: avoid;
  }

}
/* Tweak the bcp14 keyword presentation */
.bcp14 {
  font-variant: small-caps;
  font-weight: bold;
  font-size: 0.9em;
}
/* Tweak the invisible space above H* in order not to overlay links in text above */
 h2 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 31px;
 }
 h3 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 24px;
 }
 h4 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 24px;
 }
/* Float artwork pilcrow to the right */
@media screen {
  .artwork a.pilcrow {
    display: block;
    line-height: 0.7;
    margin-top: 0.15em;
  }
}
/* Make pilcrows on dd visible */
@media screen {
  dd:hover > a.pilcrow {
    visibility: visible;
  }
}
/* Make the placement of figcaption match that of a table's caption
   by removing the figure's added bottom margin */
.alignLeft.art-text,
.alignCenter.art-text,
.alignRight.art-text {
   margin-bottom: 0;
}
.alignLeft,
.alignCenter,
.alignRight {
  margin: 1em 0 0 0;
}
/* In print, the pilcrow won't show on hover, so prevent it from taking up space,
   possibly even requiring a new line */
@media print {
  a.pilcrow {
    display: none;
  }
}
/* Styling for the external metadata */
div#external-metadata {
  background-color: #eee;
  padding: 0.5em;
  margin-bottom: 0.5em;
  display: none;
}
div#internal-metadata {
  padding: 0.5em;                       /* to match the external-metadata padding */
}
/* Styling for title RFC Number */
h1#rfcnum {
  clear: both;
  margin: 0 0 -1em;
  padding: 1em 0 0 0;
}
/* Make .olPercent look the same as <ol><li> */
dl.olPercent > dd {
  margin-bottom: 0.25em;
  min-height: initial;
}
/* Give aside some styling to set it apart */
aside {
  border-left: 1px solid #ddd;
  margin: 1em 0 1em 2em;
  padding: 0.2em 2em;
}
aside > dl,
aside > ol,
aside > ul,
aside > table,
aside > p {
  margin-bottom: 0.5em;
}
/* Additional page break settings */
@media print {
  figcaption, table caption {
    page-break-before: avoid;
  }
}
/* Font size adjustments for print */
@media print {
  body  { font-size: 10pt;      line-height: normal; max-width: 96%; }
  h1    { font-size: 1.72em;    padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
  h2    { font-size: 1.44em;    padding-top: 1.5em; } /* 1*1.2*1.2 */
  h3    { font-size: 1.2em;     padding-top: 1.5em; } /* 1*1.2 */
  h4    { font-size: 1em;       padding-top: 1.5em; }
  h5, h6 { font-size: 1em;      margin: initial; padding: 0.5em 0 0.3em; }
}
/* Sourcecode margin in print, when there's no pilcrow */
@media print {
  .artwork,
  .artwork > pre,
  .sourcecode {
    margin-bottom: 1em;
  }
}
/* Avoid narrow tables forcing too narrow table captions, which may render badly */
table {
  min-width: 20em;
}
/* ol type a */
ol.type-a { list-style-type: lower-alpha; }
ol.type-A { list-style-type: upper-alpha; }
ol.type-i { list-style-type: lower-roman; }
ol.type-I { list-style-type: lower-roman; }
/* Apply the print table and row borders in general, on request from the RPC,
and increase the contrast between border and odd row background sligthtly */
table {
  border: 1px solid #ddd;
}
td {
  border-top: 1px solid #ddd;
}
tr {
  break-inside: avoid;
}
tr:nth-child(2n+1) > td {
  background-color: #f8f8f8;
}
/* Use style rules to govern display of the TOC. */
@media screen and (max-width: 1023px) {
  #toc nav { display: none; }
  #toc.active nav { display: block; }
}
/* Add support for keepWithNext */
.keepWithNext {
  break-after: avoid-page;
  break-after: avoid-page;
}
/* Add support for keepWithPrevious */
.keepWithPrevious {
  break-before: avoid-page;
}
/* Change the approach to avoiding breaks inside artwork etc. */
figure, pre, table, .artwork, .sourcecode  {
  break-before: auto;
  break-after: auto;
}
/* Avoid breaks between <dt> and <dd> */
dl {
  break-before: auto;
  break-inside: auto;
}
dt {
  break-before: auto;
  break-after: avoid-page;
}
dd {
  break-before: avoid-page;
  break-after: auto;
  orphans: 3;
  widows: 3
}
span.break, dd.break {
  margin-bottom: 0;
  min-height: 0;
  break-before: auto;
  break-inside: auto;
  break-after: auto;
}
/* Undo break-before ToC */
@media print {
  #toc {
    break-before: auto;
  }
}
/* Text in compact lists should not get extra bottim margin space,
   since that would makes the list not compact */
ul.compact p, .ulCompact p,
ol.compact p, .olCompact p {
 margin: 0;
}
/* But the list as a whole needs the extra space at the end */
section ul.compact,
section .ulCompact,
section ol.compact,
section .olCompact {
  margin-bottom: 1em;                    /* same as p not within ul.compact etc. */
}
/* The tt and code background above interferes with for instance table cell
   backgrounds.  Changed to something a bit more selective. */
tt, code {
  background-color: transparent;
}
p tt, p code, li tt, li code {
  background-color: #f8f8f8;
}
/* Tweak the pre margin -- 0px doesn't come out well */
pre {
   margin-top: 0.5px;
}
/* Tweak the comact list text */
ul.compact, .ulCompact,
ol.compact, .olCompact,
dl.compact, .dlCompact {
  line-height: normal;
}
/* Don't add top margin for nested lists */
li > ul, li > ol, li > dl,
dd > ul, dd > ol, dd > dl,
dl > dd > dl {
  margin-top: initial;
}
/* Elements that should not be rendered on the same line as a <dt> */
/* This should match the element list in writer.text.TextWriter.render_dl() */
dd > div.artwork:first-child,
dd > aside:first-child,
dd > figure:first-child,
dd > ol:first-child,
dd > div:first-child > pre.sourcecode,
dd > table:first-child,
dd > ul:first-child {
  clear: left;
}
/* fix for weird browser behaviour when <dd/> is empty */
dt+dd:empty::before{
  content: "\00a0";
}
/* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */
li > p {
  margin-bottom: 0.5em
}
/* Don't let p margin spill out from inside list items */
li > p:last-of-type {
  margin-bottom: 0;
}
</style>
<link href="rfc-local.css" rel="stylesheet" type="text/css">
<link href="https://dx.doi.org/10.17487/rfc9130" rel="alternate">
  <link href="urn:issn:2070-1721" rel="alternate">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-isis-yang-isis-cfg-42" rel="prev">
  </head>
<body class="xml2rfc">
<script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
<table class="ears">
<thead><tr>
<td class="left">RFC 9130</td>
<td class="center">IS-IS YANG Data Model</td>
<td class="right">October 2022</td>
</tr></thead>
<tfoot><tr>
<td class="left">Litkowski, et al.</td>
<td class="center">Standards Track</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
<div id="external-metadata" class="document-information"></div>
<div id="internal-metadata" class="document-information">
<dl id="identifiers">
<dt class="label-stream">Stream:</dt>
<dd class="stream">Internet Engineering Task Force (IETF)</dd>
<dt class="label-rfc">RFC:</dt>
<dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc9130" class="eref">9130</a></dd>
<dt class="label-category">Category:</dt>
<dd class="category">Standards Track</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2022-10" class="published">October 2022</time>
    </dd>
<dt class="label-issn">ISSN:</dt>
<dd class="issn">2070-1721</dd>
<dt class="label-authors">Authors:</dt>
<dd class="authors">
<div class="author">
      <div class="author-name">S. Litkowski, <span class="editor">Ed.</span>
</div>
<div class="org">Cisco Systems</div>
</div>
<div class="author">
      <div class="author-name">D. Yeung</div>
<div class="org">Arrcus, Inc.</div>
</div>
<div class="author">
      <div class="author-name">A. Lindem</div>
<div class="org">Cisco Systems</div>
</div>
<div class="author">
      <div class="author-name">J. Zhang</div>
<div class="org">Juniper Networks</div>
</div>
<div class="author">
      <div class="author-name">L. Lhotka</div>
<div class="org">CZ.NIC</div>
</div>
</dd>
</dl>
</div>
<h1 id="rfcnum">RFC 9130</h1>
<h1 id="title">YANG Data Model for the IS-IS Protocol</h1>
<section id="section-abstract">
      <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
<p id="section-abstract-1">This document defines a YANG data model that can be used to
      configure and manage the IS-IS protocol on network elements.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
</section>
<div id="status-of-memo">
<section id="section-boilerplate.1">
        <h2 id="name-status-of-this-memo">
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
        </h2>
<p id="section-boilerplate.1-1">
            This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
<p id="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.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
<p id="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
            <span><a href="https://www.rfc-editor.org/info/rfc9130">https://www.rfc-editor.org/info/rfc9130</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="copyright">
<section id="section-boilerplate.2">
        <h2 id="name-copyright-notice">
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
        </h2>
<p id="section-boilerplate.2-1">
            Copyright (c) 2022 IETF Trust and the persons identified as the
            document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
<p id="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) 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.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="toc">
<section id="section-toc.1">
        <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
        </h2>
<nav class="toc"><ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1">
            <p id="section-toc.1-1.1.1" class="keepWithNext"><a href="#section-1" class="auto internal xref">1</a>.  <a href="#name-introduction" class="internal xref">Introduction</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1.2.1">
                <p id="section-toc.1-1.1.2.1.1" class="keepWithNext"><a href="#section-1.1" class="auto internal xref">1.1</a>.  <a href="#name-requirements-language" class="internal xref">Requirements Language</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2">
            <p id="section-toc.1-1.2.1"><a href="#section-2" class="auto internal xref">2</a>.  <a href="#name-design-of-the-data-model" class="internal xref">Design of the Data Model</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.1">
                <p id="section-toc.1-1.2.2.1.1" class="keepWithNext"><a href="#section-2.1" class="auto internal xref">2.1</a>.  <a href="#name-is-is-configuration" class="internal xref">IS-IS Configuration</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.2">
                <p id="section-toc.1-1.2.2.2.1"><a href="#section-2.2" class="auto internal xref">2.2</a>.  <a href="#name-multi-topology-parameters" class="internal xref">Multi-Topology Parameters</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.3">
                <p id="section-toc.1-1.2.2.3.1"><a href="#section-2.3" class="auto internal xref">2.3</a>.  <a href="#name-per-level-parameters" class="internal xref">Per-Level Parameters</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.4">
                <p id="section-toc.1-1.2.2.4.1"><a href="#section-2.4" class="auto internal xref">2.4</a>.  <a href="#name-per-interface-parameters" class="internal xref">Per-Interface Parameters</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.5">
                <p id="section-toc.1-1.2.2.5.1"><a href="#section-2.5" class="auto internal xref">2.5</a>.  <a href="#name-authentication-parameters" class="internal xref">Authentication Parameters</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.6">
                <p id="section-toc.1-1.2.2.6.1"><a href="#section-2.6" class="auto internal xref">2.6</a>.  <a href="#name-igp-ldp-synchronization" class="internal xref">IGP/LDP Synchronization</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.7">
                <p id="section-toc.1-1.2.2.7.1"><a href="#section-2.7" class="auto internal xref">2.7</a>.  <a href="#name-iso-parameters" class="internal xref">ISO Parameters</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.8">
                <p id="section-toc.1-1.2.2.8.1"><a href="#section-2.8" class="auto internal xref">2.8</a>.  <a href="#name-ip-frr" class="internal xref">IP FRR</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.9">
                <p id="section-toc.1-1.2.2.9.1"><a href="#section-2.9" class="auto internal xref">2.9</a>.  <a href="#name-operational-states" class="internal xref">Operational States</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3">
            <p id="section-toc.1-1.3.1"><a href="#section-3" class="auto internal xref">3</a>.  <a href="#name-rpc-operations" class="internal xref">RPC Operations</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4">
            <p id="section-toc.1-1.4.1"><a href="#section-4" class="auto internal xref">4</a>.  <a href="#name-notifications" class="internal xref">Notifications</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5">
            <p id="section-toc.1-1.5.1"><a href="#section-5" class="auto internal xref">5</a>.  <a href="#name-interactions-with-other-yan" class="internal xref">Interactions with Other YANG Modules</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6">
            <p id="section-toc.1-1.6.1"><a href="#section-6" class="auto internal xref">6</a>.  <a href="#name-is-is-yang-module" class="internal xref">IS-IS YANG Module</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7">
            <p id="section-toc.1-1.7.1"><a href="#section-7" class="auto internal xref">7</a>.  <a href="#name-security-considerations" class="internal xref">Security Considerations</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8">
            <p id="section-toc.1-1.8.1"><a href="#section-8" class="auto internal xref">8</a>.  <a href="#name-iana-considerations" class="internal xref">IANA Considerations</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9">
            <p id="section-toc.1-1.9.1"><a href="#section-9" class="auto internal xref">9</a>.  <a href="#name-references" class="internal xref">References</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9.2.1">
                <p id="section-toc.1-1.9.2.1.1"><a href="#section-9.1" class="auto internal xref">9.1</a>.  <a href="#name-normative-references" class="internal xref">Normative References</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9.2.2">
                <p id="section-toc.1-1.9.2.2.1"><a href="#section-9.2" class="auto internal xref">9.2</a>.  <a href="#name-informative-references" class="internal xref">Informative References</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10">
            <p id="section-toc.1-1.10.1"><a href="#appendix-A" class="auto internal xref">Appendix A</a>.  <a href="#name-example-of-is-is-configurat" class="internal xref">Example of IS-IS Configuration in XML</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11">
            <p id="section-toc.1-1.11.1"><a href="#appendix-B" class="auto internal xref"></a><a href="#name-acknowledgments" class="internal xref">Acknowledgments</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12">
            <p id="section-toc.1-1.12.1"><a href="#appendix-C" class="auto internal xref"></a><a href="#name-contributors" class="internal xref">Contributors</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.13">
            <p id="section-toc.1-1.13.1"><a href="#appendix-D" class="auto internal xref"></a><a href="#name-authors-addresses" class="internal xref">Authors' Addresses</a></p>
</li>
        </ul>
</nav>
</section>
</div>
<div id="introduction">
<section id="section-1">
      <h2 id="name-introduction">
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
      </h2>
<p id="section-1-1">
      This document defines a YANG data model <span>[<a href="#RFC7950" class="cite xref">RFC7950</a>]</span> for the IS-IS routing
      protocol.<a href="#section-1-1" class="pilcrow">¶</a></p>
<p id="section-1-2">The data model covers the configuration of an IS-IS routing
      protocol instance, as well as the retrieval of IS-IS operational states.<a href="#section-1-2" class="pilcrow">¶</a></p>
<p id="section-1-3">A simplified tree representation of the data model is
        presented in <a href="#design" class="auto internal xref">Section 2</a>.
        Tree diagrams used in this document follow the notation defined in <span>[<a href="#RFC8340" class="cite xref">RFC8340</a>]</span>.<a href="#section-1-3" class="pilcrow">¶</a></p>
<p id="section-1-4">The module defined in this document is designed as per the Network Management Datastore
      Architecture (NMDA) <span>[<a href="#RFC8342" class="cite xref">RFC8342</a>]</span>.<a href="#section-1-4" class="pilcrow">¶</a></p>
<section id="section-1.1">
        <h3 id="name-requirements-language">
<a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-requirements-language" class="section-name selfRef">Requirements Language</a>
        </h3>
<p id="section-1.1-1">
    The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>",
    "<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>", "<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>",
    "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>", 
    "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are
    to be interpreted as 
    described in BCP 14 <span>[<a href="#RFC2119" class="cite xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="cite xref">RFC8174</a>]</span> 
    when, and only when, they appear in all capitals, as shown here.<a href="#section-1.1-1" class="pilcrow">¶</a></p>
</section>
</section>
</div>
<div id="design">
<section id="section-2">
      <h2 id="name-design-of-the-data-model">
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-design-of-the-data-model" class="section-name selfRef">Design of the Data Model</a>
      </h2>
<p id="section-2-1">The IS-IS YANG module augments the
      "control-plane-protocol" list in the "ietf-routing" module <span>[<a href="#RFC8349" class="cite xref">RFC8349</a>]</span> with specific
      IS-IS parameters.<a href="#section-2-1" class="pilcrow">¶</a></p>
<p id="section-2-2">The diagram below shows the overall structure of the "ietf-isis"
      YANG module defined in this document.  NOTE: '\' line wrapping is per
      <span>[<a href="#RFC8792" class="cite xref">RFC8792</a>]</span>.<a href="#section-2-2" class="pilcrow">¶</a></p>
<div id="section-2-3">
<pre class="breakable lang-yangtree sourcecode">
module: ietf-isis
  augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route:
    +--ro metric?       uint32
    +--ro tag*          uint64
    +--ro route-type?   enumeration
  augment /if:interfaces/if:interface:
    +--rw clns-mtu?   uint16 {osi-interface}?
  augment /rt:routing/rt:control-plane-protocols/rt:
              control-plane-protocol:
    +--rw isis
       +--rw enabled?                  boolean {admin-control}?
       +--rw level-type?               level
       +--rw system-id?                system-id
       +--rw maximum-area-addresses? \
          uint8 {maximum-area-addresses}?
       +--rw area-address*             area-address
       +--rw lsp-mtu?                  uint16
       +--rw lsp-lifetime?             uint16
       +--rw lsp-refresh?              rt-types:timer-value-seconds16
       |                                   {lsp-refresh}?
       +--rw poi-tlv?                  boolean {poi-tlv}?
       +--rw graceful-restart {graceful-restart}?
       |  +--rw enabled?            boolean
       |  +--rw restart-interval?   rt-types:timer-value-seconds16
       |  +--rw helper-enabled?     boolean
       +--rw nsr {nsr}?
       |  +--rw enabled?  boolean
       +--rw node-tags {node-tag}?
       |  +--rw node-tag* [tag]
       |        ...
       +--rw metric-type
       |  +--rw value?     enumeration
       |  +--rw level-1
       |  |     ...
       |  +--rw level-2
       |        ...
       +--rw default-metric
       |  +--rw value?     wide-metric
       |  +--rw level-1
       |  |     ...
       |  +--rw level-2
       |        ...
       +--rw auto-cost {auto-cost}?
       |  +--rw enabled?               boolean
       |  +--rw reference-bandwidth?   uint32
       +--rw authentication
       |  +--rw (authentication-type)?
       |  |     ...
       |  +--rw level-1
       |  |     ...
       |  +--rw level-2
       |        ...
       +--rw address-families {nlpid-control}?
       |  +--rw address-family-list* [address-family]
       |        ...
       +--rw mpls
       |  +--rw te-rid {te-rid}?
       |  |     ...
       |  +--rw ldp
       |        ...
       +--rw spf-control
       |  +--rw paths?            uint16 {max-ecmp}?
       |  +--rw ietf-spf-delay {ietf-spf-delay}?
       |        ...
       +--rw fast-reroute {fast-reroute}?
       |  +--rw lfa {lfa}?
       +--rw preference
       |  +--rw (granularity)?
       |        ...
       +--rw overload
       |  +--rw status?   boolean
       +--rw overload-max-metric {overload-max-metric}?
       |  +--rw timeout?   rt-types:timer-value-seconds16
       +--ro spf-log
       |  +--ro event* [id]
       |        ...
       +--ro lsp-log
       |  +--ro event* [id]
       |        ...
       +--ro hostnames
       |  +--ro hostname* [system-id]
       |        ...
       +--ro database
       |  +--ro levels* [level]
       |        ...
       +--ro local-rib
       |  +--ro route* [prefix]
       |        ...
       +--ro system-counters
       |  +--ro level* [level]
       |        ...
       +--ro protected-routes
       |  +--ro address-family-stats* \
       |     [address-family prefix alternate]
       |        ...
       +--ro unprotected-routes
       |  +--ro prefixes* [address-family prefix]
       |        ...
       +--ro protection-statistics* [frr-protection-method]
       |  +--ro frr-protection-method    identityref
       |  +--ro address-family-stats* [address-family]
       |        ...
       +--rw discontinuity-time?       yang:date-and-time
       +--rw topologies {multi-topology}?
       |  +--rw topology* [name]
       |        ...
       +--rw interfaces
          +--rw interface* [name]
                ...

  rpcs:
    +---x clear-adjacency
    |  +---w input
    |     +---w routing-protocol-instance-name -&gt; /rt:routing/
    |     |                                    control-plane-\
    |     |                                       protocols/
    |     |                                    control-plane-\
    |     |                                       protocol/name
    |     +---w level?                            level
    |     +---w interface?                        if:interface-ref
    +---x clear-database
       +---w input
          +---w routing-protocol-instance-name -&gt; /rt:routing/
          |                                    control-plane-\
          |                                       protocols/
          |                                    control-plane-\
          |                                       protocol/name
          +---w level?                            level

  notifications:
    +---n database-overload
    |  +--ro routing-protocol-name?   -&gt; /rt:routing/
    |  |                                 control-plane-protocols/
    |  |                                 control-plane-protocol/name
    |  +--ro isis-level?              level
    |  +--ro overload?                enumeration
    +---n lsp-too-large
    |  +--ro routing-protocol-name?   -&gt; /rt:routing/
    |  |                                 control-plane-protocols/
    |  |                                 control-plane-protocol/name
    |  +--ro isis-level?              level
    |  +--ro interface-name?          if:interface-ref
    |  +--ro interface-level?         level
    |  +--ro extended-circuit-id?     extended-circuit-id
    |  +--ro pdu-size?                uint32
    |  +--ro lsp-id?                  lsp-id
    +---n if-state-change
    |  +--ro routing-protocol-name?   -&gt; /rt:routing/
    |  |                                 control-plane-protocols/
    |  |                                 control-plane-protocol/name
    |  +--ro isis-level?              level
    |  +--ro interface-name?          if:interface-ref
    |  +--ro interface-level?         level
    |  +--ro extended-circuit-id?     extended-circuit-id
    |  +--ro state?                   if-state-type
    +---n corrupted-lsp-detected
    |  +--ro routing-protocol-name?   -&gt; /rt:routing/
    |  |                                 control-plane-protocols/
    |  |                                 control-plane-protocol/name
    |  +--ro isis-level?              level
    |  +--ro lsp-id?                  lsp-id
    +---n attempt-to-exceed-max-sequence
    |  +--ro routing-protocol-name?   -&gt; /rt:routing/
    |  |                                 control-plane-protocols/
    |  |                                 control-plane-protocol/name
    |  +--ro isis-level?              level
    |  +--ro lsp-id?                  lsp-id
    +---n id-len-mismatch
    |  +--ro routing-protocol-name?   -&gt; /rt:routing/
    |  |                                 control-plane-protocols/
    |  |                                 control-plane-protocol/name
    |  +--ro isis-level?              level
    |  +--ro interface-name?          if:interface-ref
    |  +--ro interface-level?         level
    |  +--ro extended-circuit-id?     extended-circuit-id
    |  +--ro pdu-field-len?           uint8
    |  +--ro raw-pdu?                 binary
    +---n max-area-addresses-mismatch
    |  +--ro routing-protocol-name?   -&gt; /rt:routing/
    |  |                                 control-plane-protocols/
    |  |                                 control-plane-protocol/name
    |  +--ro isis-level?              level
    |  +--ro interface-name?          if:interface-ref
    |  +--ro interface-level?         level
    |  +--ro extended-circuit-id?     extended-circuit-id
    |  +--ro max-area-addresses?      uint8
    |  +--ro raw-pdu?                 binary
    +---n own-lsp-purge
    |  +--ro routing-protocol-name?   -&gt; /rt:routing/
    |  |                                 control-plane-protocols/
    |  |                                 control-plane-protocol/name
    |  +--ro isis-level?              level
    |  +--ro interface-name?          if:interface-ref
    |  +--ro interface-level?         level
    |  +--ro extended-circuit-id?     extended-circuit-id
    |  +--ro lsp-id?                  lsp-id
    +---n sequence-number-skipped
    |  +--ro routing-protocol-name?   -&gt; /rt:routing/
    |  |                                 control-plane-protocols/
    |  |                                 control-plane-protocol/name
    |  +--ro isis-level?              level
    |  +--ro interface-name?          if:interface-ref
    |  +--ro interface-level?         level
    |  +--ro extended-circuit-id?     extended-circuit-id
    |  +--ro lsp-id?                  lsp-id
    +---n authentication-type-failure
    |  +--ro routing-protocol-name?   -&gt; /rt:routing/
    |  |                                 control-plane-protocols/
    |  |                                 control-plane-protocol/name
    |  +--ro isis-level?              level
    |  +--ro interface-name?          if:interface-ref
    |  +--ro interface-level?         level
    |  +--ro extended-circuit-id?     extended-circuit-id
    |  +--ro raw-pdu?                 binary
    +---n authentication-failure
    |  +--ro routing-protocol-name?   -&gt; /rt:routing/
    |  |                                 control-plane-protocols/
    |  |                                 control-plane-protocol/name
    |  +--ro isis-level?              level
    |  +--ro interface-name?          if:interface-ref
    |  +--ro interface-level?         level
    |  +--ro extended-circuit-id?     extended-circuit-id
    |  +--ro raw-pdu?                 binary
    +---n version-skew
    |  +--ro routing-protocol-name?   -&gt; /rt:routing/
    |  |                                 control-plane-protocols/
    |  |                                 control-plane-protocol/name
    |  +--ro isis-level?              level
    |  +--ro interface-name?          if:interface-ref
    |  +--ro interface-level?         level
    |  +--ro extended-circuit-id?     extended-circuit-id
    |  +--ro protocol-version?        uint8
    |  +--ro raw-pdu?                 binary
    +---n area-mismatch
    |  +--ro routing-protocol-name?   -&gt; /rt:routing/
    |  |                                 control-plane-protocols/
    |  |                                 control-plane-protocol/name
    |  +--ro isis-level?              level
    |  +--ro interface-name?          if:interface-ref
    |  +--ro interface-level?         level
    |  +--ro extended-circuit-id?     extended-circuit-id
    |  +--ro raw-pdu?                 binary
    +---n rejected-adjacency
    |  +--ro routing-protocol-name?   -&gt; /rt:routing/
    |  |                                 control-plane-protocols/
    |  |                                 control-plane-protocol/name
    |  +--ro isis-level?              level
    |  +--ro interface-name?          if:interface-ref
    |  +--ro interface-level?         level
    |  +--ro extended-circuit-id?     extended-circuit-id
    |  +--ro raw-pdu?                 binary
    |  +--ro reason?                  string
    +---n protocols-supported-mismatch
    |  +--ro routing-protocol-name?   -&gt; /rt:routing/
    |  |                                 control-plane-protocols/
    |  |                                 control-plane-protocol/name
    |  +--ro isis-level?              level
    |  +--ro interface-name?          if:interface-ref
    |  +--ro interface-level?         level
    |  +--ro extended-circuit-id?     extended-circuit-id
    |  +--ro raw-pdu?                 binary
    |  +--ro protocols*               uint8
    +---n lsp-error-detected
    |  +--ro routing-protocol-name?   -&gt; /rt:routing/
    |  |                                 control-plane-protocols/
    |  |                                 control-plane-protocol/name
    |  +--ro isis-level?              level
    |  +--ro interface-name?          if:interface-ref
    |  +--ro interface-level?         level
    |  +--ro extended-circuit-id?     extended-circuit-id
    |  +--ro lsp-id?                  lsp-id
    |  +--ro raw-pdu?                 binary
    |  +--ro error-offset?            uint32
    |  +--ro tlv-type?                uint8
    +---n adjacency-state-change
    |  +--ro routing-protocol-name?   -&gt; /rt:routing/
    |  |                                 control-plane-protocols/
    |  |                                 control-plane-protocol/name
    |  +--ro isis-level?              level
    |  +--ro interface-name?          if:interface-ref
    |  +--ro interface-level?         level
    |  +--ro extended-circuit-id?     extended-circuit-id
    |  +--ro neighbor?                string
    |  +--ro neighbor-system-id?      system-id
    |  +--ro state?                   adj-state-type
    |  +--ro reason?                  string
    +---n lsp-received
    |  +--ro routing-protocol-name?   -&gt; /rt:routing/
    |  |                                 control-plane-protocols/
    |  |                                 control-plane-protocol/name
    |  +--ro isis-level?              level
    |  +--ro interface-name?          if:interface-ref
    |  +--ro interface-level?         level
    |  +--ro extended-circuit-id?     extended-circuit-id
    |  +--ro lsp-id?                  lsp-id
    |  +--ro sequence?                uint32
    |  +--ro received-timestamp?      yang:timestamp
    |  +--ro neighbor-system-id?      system-id
    +---n lsp-generation
       +--ro routing-protocol-name?   -&gt; /rt:routing/
       |                                 control-plane-protocols/
       |                                 control-plane-protocol/name
       +--ro isis-level?              level
       +--ro lsp-id?                  lsp-id
       +--ro sequence?                uint32
       +--ro send-timestamp?          yang:timestamp
</pre><a href="#section-2-3" class="pilcrow">¶</a>
</div>
<div id="yang-isis-global">
<section id="section-2.1">
        <h3 id="name-is-is-configuration">
<a href="#section-2.1" class="section-number selfRef">2.1. </a><a href="#name-is-is-configuration" class="section-name selfRef">IS-IS Configuration</a>
        </h3>
<p id="section-2.1-1">The IS-IS configuration is divided into two areas:<a href="#section-2.1-1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-2.1-2.1">Global parameters<a href="#section-2.1-2.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-2.1-2.2">Per-interface configuration (see <a href="#yang-interface" class="auto internal xref">Section 2.4</a>)<a href="#section-2.1-2.2" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-2.1-3">Additional modules may be created to support additional
        parameters. These additional modules <span class="bcp14">MUST</span> augment the
        "ietf-isis" module.<a href="#section-2.1-3" class="pilcrow">¶</a></p>
<p id="section-2.1-4">The model includes optional features for which the corresponding
        configuration data nodes are also optional. As an example, the ability
        to control the administrative state of a particular IS-IS instance is
        optional. By advertising the feature "admin-control", a device
        communicates to the client that it supports the ability to shut down a
        particular IS-IS instance.<a href="#section-2.1-4" class="pilcrow">¶</a></p>
<p id="section-2.1-5">The global configuration contains the usual IS-IS parameters, e.g.,
        "lsp-mtu", "lsp-lifetime", "lsp-refresh", "default-metric".<a href="#section-2.1-5" class="pilcrow">¶</a></p>
</section>
</div>
<div id="yang-multitopology">
<section id="section-2.2">
        <h3 id="name-multi-topology-parameters">
<a href="#section-2.2" class="section-number selfRef">2.2. </a><a href="#name-multi-topology-parameters" class="section-name selfRef">Multi-Topology Parameters</a>
        </h3>
<p id="section-2.2-1">The model supports Multi-Topology (MT) IS-IS as defined in <span>[<a href="#RFC5120" class="cite xref">RFC5120</a>]</span>.<a href="#section-2.2-1" class="pilcrow">¶</a></p>
<p id="section-2.2-2">The "topologies" container is used to enable support of the MT
        extensions.<a href="#section-2.2-2" class="pilcrow">¶</a></p>
<p id="section-2.2-3">The "name" used in the topology list should refer to an existing
        Routing Information Base (RIB) defined for the device <span>[<a href="#RFC8349" class="cite xref">RFC8349</a>]</span>.<a href="#section-2.2-3" class="pilcrow">¶</a></p>
<p id="section-2.2-4">Some specific parameters can be defined on a per-topology basis,
        at both the global level and the interface level: for example, an
        interface metric can be defined per topology.<a href="#section-2.2-4" class="pilcrow">¶</a></p>
<p id="section-2.2-5">Multiple address families (such as IPv4 or IPv6) can also be
        enabled within the default topology. This can be achieved using the
        "address-families" container (requiring the "nlpid-control" feature to
        be supported).<a href="#section-2.2-5" class="pilcrow">¶</a></p>
</section>
</div>
<div id="yang-level">
<section id="section-2.3">
        <h3 id="name-per-level-parameters">
<a href="#section-2.3" class="section-number selfRef">2.3. </a><a href="#name-per-level-parameters" class="section-name selfRef">Per-Level Parameters</a>
        </h3>
<p id="section-2.3-1">Some parameters allow per-level configuration. For such
        parameters, the parameter is modeled as a container with three
        configuration locations:<a href="#section-2.3-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlNewline" id="section-2.3-2">
          <dt id="section-2.3-2.1">A top-level container:</dt>
          <dd style="margin-left: 1.5em" id="section-2.3-2.2">Corresponds to "level-all", so the
          configuration applies to both levels.<a href="#section-2.3-2.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.3-2.3">A level-1 container:</dt>
          <dd style="margin-left: 1.5em" id="section-2.3-2.4">Corresponds to parameters specific to level 1.<a href="#section-2.3-2.4" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.3-2.5">A level-2 container:</dt>
          <dd style="margin-left: 1.5em" id="section-2.3-2.6">Corresponds to parameters specific to level 2.<a href="#section-2.3-2.6" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
</dl>
<div id="section-2.3-3">
<pre class="lang-yangtree sourcecode">
            +--rw priority
            |  +--rw value?     uint8
            |  +--rw level-1
            |  |  +--rw value?   uint8
            |  +--rw level-2
            |     +--rw value?   uint8
</pre><a href="#section-2.3-3" class="pilcrow">¶</a>
</div>
<p id="section-2.3-4">Example:<a href="#section-2.3-4" class="pilcrow">¶</a></p>
<div id="section-2.3-5">
<pre class="lang-xml sourcecode">
        &lt;priority&gt;
            &lt;value&gt;250&lt;/value&gt;
            &lt;level-1&gt;
                &lt;value&gt;100&lt;/value&gt;
            &lt;/level-1&gt;
        &lt;/priority&gt;
</pre><a href="#section-2.3-5" class="pilcrow">¶</a>
</div>
<p id="section-2.3-6">An implementation <span class="bcp14">MUST</span> prefer a level-specific
        parameter over a top-level parameter. For example, if the priority is
        100 for the level-1 configuration and 250 for the top-level configuration, the
        implementation must use 100 for the level-1 priority and 250 for the
        level-2 priority.<a href="#section-2.3-6" class="pilcrow">¶</a></p>
<p id="section-2.3-7">Some parameters, such as "overload bit" and "route preference",
        are not modeled to support per-level configuration. If an
        implementation supports per-level configuration for such parameters,
        this implementation <span class="bcp14">MUST</span> augment the current model by
        adding both level-1 and level-2 containers and <span class="bcp14">MUST</span>
        reuse existing configuration groupings.<a href="#section-2.3-7" class="pilcrow">¶</a></p>
<p id="section-2.3-8">Example of augmentation:<a href="#section-2.3-8" class="pilcrow">¶</a></p>
<div id="section-2.3-9">
<pre class="lang-yang sourcecode">
augment "/rt:routing/" +
        "rt:control-plane-protocols/rt:control-plane-protocol"+
        "/isis:isis/isis:overload" {
        when "rt:type = 'isis:isis'" {
          description
            "This augments the IS-IS routing protocol when used.";
        }
        description
          "This augments the IS-IS overload configuration
           with per-level configuration.";

        container level-1 {
          uses isis:overload-global-cfg;
          description
            "Level-1 configuration.";
        }
        container level-2 {
          uses isis:overload-global-cfg;
          description
            "Level-2 configuration.";
        }
}
</pre><a href="#section-2.3-9" class="pilcrow">¶</a>
</div>
<p id="section-2.3-10">If an implementation does not support per-level configuration for a
        parameter modeled with per-level configuration, the implementation
        should advertise a deviation to announce that it does not support the
        configuration of level-1 and level-2 containers.<a href="#section-2.3-10" class="pilcrow">¶</a></p>
<p id="section-2.3-11">Finally, if an implementation supports per-level configuration but
        does not support the "level-all" configuration, it should also advertise
        a deviation.<a href="#section-2.3-11" class="pilcrow">¶</a></p>
</section>
</div>
<div id="yang-interface">
<section id="section-2.4">
        <h3 id="name-per-interface-parameters">
<a href="#section-2.4" class="section-number selfRef">2.4. </a><a href="#name-per-interface-parameters" class="section-name selfRef">Per-Interface Parameters</a>
        </h3>
<p id="section-2.4-1">The per-interface section of the IS-IS instance describes
        the interface-specific parameters.<a href="#section-2.4-1" class="pilcrow">¶</a></p>
<p id="section-2.4-2">The interface is modeled as a reference to an existing interface
        as defined in the "ietf-interfaces" YANG module <span>[<a href="#RFC8343" class="cite xref">RFC8343</a>]</span>.<a href="#section-2.4-2" class="pilcrow">¶</a></p>
<p id="section-2.4-3">Each interface has some interface-specific parameters that may have
        a different per-level value as described in the previous section. An
        interface-specific parameter <span class="bcp14">MUST</span> be preferred over an
        IS-IS global parameter.<a href="#section-2.4-3" class="pilcrow">¶</a></p>
<p id="section-2.4-4">Some parameters, such as "hello-padding", are defined as containers
        to allow easy extension by vendor-specific modules.<a href="#section-2.4-4" class="pilcrow">¶</a></p>
<div id="section-2.4-5">
<pre class="breakable lang-yangtree sourcecode">
    +--rw interfaces
       +--rw interface* [name]
          +--rw name                       if:interface-ref
          +--rw enabled?                   boolean {admin-control}?
          +--rw level-type?                level
          +--rw lsp-pacing-interval?       rt-types:
          |                                   timer-value-\
          |                                      milliseconds
          +--rw lsp-retransmit-interval?   rt-types:
          |                                   timer-value-seconds16
          +--rw passive?                   boolean
          +--rw csnp-interval?             rt-types:
          |                                   timer-value-seconds16
          +--rw hello-padding
          |  +--rw enabled?  boolean
          +--rw mesh-group-enabled?        mesh-group-state
          +--rw mesh-group?                uint8
          +--rw interface-type?            interface-type
          +--rw tag*                       uint32 {prefix-tag}?
          +--rw tag64*                     uint64 {prefix-tag64}?
          +--rw node-flag?                 boolean {node-flag}?
          +--rw hello-authentication
          |  +--rw (authentication-type)?
          |  |  +--:(key-chain) {key-chain}?
          |  |  |  +--rw key-chain?          key-chain:key-chain-ref
          |  |  +--:(password)
          |  |     +--rw key?                string
          |  |     +--rw crypto-algorithm?   identityref
          |  +--rw level-1
          |  |  +--rw (authentication-type)?
          |  |     +--:(key-chain) {key-chain}?
          |  |     |  +--rw key-chain?          key-chain:\
          |  |     |                               key-chain-ref
          |  |     +--:(password)
          |  |        +--rw key?                string
          |  |        +--rw crypto-algorithm?   identityref
          |  +--rw level-2
          |     +--rw (authentication-type)?
          |        +--:(key-chain) {key-chain}?
          |        |  +--rw key-chain?          key-chain:\
          |        |                               key-chain-ref
          |        +--:(password)
          |           +--rw key?                string
          |           +--rw crypto-algorithm?   identityref
          +--rw hello-interval
          |  +--rw value?     rt-types:timer-value-seconds16
          |  +--rw level-1
          |  |  +--rw value?   rt-types:timer-value-seconds16
          |  +--rw level-2
          |     +--rw value?   rt-types:timer-value-seconds16
          +--rw hello-multiplier
          |  +--rw value?     uint16
          |  +--rw level-1
          |  |  +--rw value?   uint16
          |  +--rw level-2
          |     +--rw value?   uint16
          +--rw priority
          |  +--rw value?     uint8
          |  +--rw level-1
          |  |  +--rw value?   uint8
          |  +--rw level-2
          |     +--rw value?   uint8
          +--rw metric
          |  +--rw value?     wide-metric
          |  +--rw level-1
          |  |  +--rw value?   wide-metric
          |  +--rw level-2
          |     +--rw value?   wide-metric
          +--rw bfd {bfd}?
          |  +--rw enabled?                          boolean
          |  +--rw local-multiplier?                 multiplier
          |  |      {client-base-cfg-parms}?
          |  +--rw (interval-config-type)? {client-base-cfg-parms}?
          |     +--:(tx-rx-intervals)
          |     |  +--rw desired-min-tx-interval?   uint32
          |     |  +--rw required-min-rx-interval?  uint32
          |     +--:(single-interval) {single-minimum-interval}?
          |        +--rw min-interval?              uint32
          +--rw address-families {nlpid-control}?
          |  +--rw address-family-list* [address-family]
          |     +--rw address-family    iana-rt-types:address-family
          +--rw mpls
          |  +--rw ldp
          |     +--rw igp-sync?   boolean {ldp-igp-sync}?
          +--rw fast-reroute {fast-reroute}?
          |  +--rw lfa {lfa}?
          |     +--rw candidate-enabled?  boolean
          |     +--rw enabled?            boolean
          |     +--rw remote-lfa {remote-lfa}?
          |     |  +--rw enabled?  boolean
          |     +--rw level-1
          |     |  +--rw candidate-enabled?  boolean
          |     |  +--rw enabled?            boolean
          |     |  +--rw remote-lfa {remote-lfa}?
          |     |     +--rw enabled?  boolean
          |     +--rw level-2
          |        +--rw candidate-enabled?  boolean
          |        +--rw enabled?            boolean
          |        +--rw remote-lfa {remote-lfa}?
          |           +--rw enabled?  boolean
          +--ro adjacencies
          |  +--ro adjacency* []
          |     +--ro neighbor-sys-type?             level
          |     +--ro neighbor-sysid?                system-id
          |     +--ro neighbor-extended-circuit-id?  extended-\
          |     |                                       circuit-id
          |     +--ro neighbor-snpa?                 snpa
          |     +--ro usage?                         level
          |     +--ro hold-timer?                    rt-types:
          |     |                                       timer-value-\
          |     |                                          seconds16
          |     +--ro neighbor-priority?             uint8
          |     +--ro lastuptime?                    yang:timestamp
          |     +--ro state?                         adj-state-type
          +--ro event-counters
          |  +--ro adjacency-changes?             uint32
          |  +--ro adjacency-number?              uint32
          |  +--ro init-fails?                    uint32
          |  +--ro adjacency-rejects?             uint32
          |  +--ro id-len-mismatch?               uint32
          |  +--ro max-area-addresses-mismatch?   uint32
          |  +--ro authentication-type-fails?     uint32
          |  +--ro authentication-fails?          uint32
          |  +--ro lan-dis-changes?               uint32
          +--ro packet-counters
          |  +--ro level* [level]
          |     +--ro level      level-number
          |     +--ro iih
          |     |  +--ro in?    uint32
          |     |  +--ro out?   uint32
          |     +--ro ish
          |     |  +--ro in?    uint32
          |     |  +--ro out?   uint32
          |     +--ro esh
          |     |  +--ro in?    uint32
          |     |  +--ro out?   uint32
          |     +--ro lsp
          |     |  +--ro in?    uint32
          |     |  +--ro out?   uint32
          |     +--ro psnp
          |     |  +--ro in?    uint32
          |     |  +--ro out?   uint32
          |     +--ro csnp
          |     |  +--ro in?    uint32
          |     |  +--ro out?   uint32
          |     +--ro unknown
          |        +--ro in?   uint32
          +--rw discontinuity-time?        yang:date-and-time
          +--rw topologies {multi-topology}?
             +--rw topology* [name]
                +--rw name      -&gt;
                |              ../../../../../../../../rt:\
                |                 ribs/rib/name
                +--rw metric
                   +--rw value?     wide-metric
                   +--rw level-1
                   |  +--rw value?   wide-metric
                   +--rw level-2
                      +--rw value?   wide-metric
</pre><a href="#section-2.4-5" class="pilcrow">¶</a>
</div>
</section>
</div>
<div id="yang-authentication">
<section id="section-2.5">
        <h3 id="name-authentication-parameters">
<a href="#section-2.5" class="section-number selfRef">2.5. </a><a href="#name-authentication-parameters" class="section-name selfRef">Authentication Parameters</a>
        </h3>
<p id="section-2.5-1">The module defined in this document enables authentication configuration through the
        "ietf-key-chain" module <span>[<a href="#RFC8177" class="cite xref">RFC8177</a>]</span>. 
           The IS-IS module imports the "ietf-key-chain" module and reuses
           some groupings to allow global and per-interface configuration of
           authentication. 
           If global authentication is configured, an implementation
           <span class="bcp14">SHOULD</span> authenticate PSNPs (Partial Sequence Number
           PDUs), CSNPs (Complete Sequence Number PDUs), and LSPs (Link
           State PDUs) with the authentication parameters supplied. 
           The authentication of Hello PDUs (Protocol Data Units) can be
           activated on a per-interface basis.<a href="#section-2.5-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="yang-igp-ldp">
<section id="section-2.6">
        <h3 id="name-igp-ldp-synchronization">
<a href="#section-2.6" class="section-number selfRef">2.6. </a><a href="#name-igp-ldp-synchronization" class="section-name selfRef">IGP/LDP Synchronization</a>
        </h3>
<p id="section-2.6-1">
           <span>[<a href="#RFC5443" class="cite xref">RFC5443</a>]</span> defines a mechanism where
           IGP (the Interior Gateway Protocol) needs to be synchronized with LDP
           (the Label Distribution Protocol). 
           An "ldp-igp-sync" feature has been defined in the model to support
           this functionality. 
           The "mpls/ldp/igp-sync" leaf under "interface" allows activation of
           the functionality on a per-interface basis. 
           The "mpls/ldp/igp-sync" container in the global configuration is
           intentionally empty and is not required for feature activation. 
           The goal of this empty container is to facilitate augmentation with
           additional parameters, e.g., timers.<a href="#section-2.6-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="yang-iso">
<section id="section-2.7">
        <h3 id="name-iso-parameters">
<a href="#section-2.7" class="section-number selfRef">2.7. </a><a href="#name-iso-parameters" class="section-name selfRef">ISO Parameters</a>
        </h3>
<p id="section-2.7-1">As the IS-IS protocol is based on the ISO protocol suite, some ISO
        parameters may be required.<a href="#section-2.7-1" class="pilcrow">¶</a></p>
<p id="section-2.7-2">This module augments the "ietf-interfaces" module configuration to support
        selected ISO configuration parameters.<a href="#section-2.7-2" class="pilcrow">¶</a></p>
<p id="section-2.7-3">The "clns-mtu" parameter can be configured for an interface.<a href="#section-2.7-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="yang-frr">
<section id="section-2.8">
        <h3 id="name-ip-frr">
<a href="#section-2.8" class="section-number selfRef">2.8. </a><a href="#name-ip-frr" class="section-name selfRef">IP FRR</a>
        </h3>
<p id="section-2.8-1">
          The YANG module defined in this document supports LFAs (Loop-Free Alternates) <span>[<a href="#RFC5286" class="cite xref">RFC5286</a>]</span> and remote LFAs <span>[<a href="#RFC7490" class="cite xref">RFC7490</a>]</span> as IP Fast Reroute (FRR)
          techniques. 
          The "fast-reroute" container may be augmented by other models to
          support other IP FRR flavors (Maximally Redundant Trees (MRTs)
          as defined in <span>[<a href="#RFC7812" class="cite xref">RFC7812</a>]</span>, Topology Independent LFA
          (TI-LFA) FRR as defined in <span>[<a href="#I-D.ietf-rtgwg-segment-routing-ti-lfa" class="cite xref">SR-TI-LFA</a>]</span>,
          etc.).<a href="#section-2.8-1" class="pilcrow">¶</a></p>
<p id="section-2.8-2">
          The current version of the model supports activation of LFAs and
          remote LFAs at the interface level only. 
          The global "lfa" container is present but kept empty to allow
          augmentation with vendor-specific properties, e.g., policies.<a href="#section-2.8-2" class="pilcrow">¶</a></p>
<p id="section-2.8-3">Remote LFAs are considered an extension of LFAs. Remote LFAs cannot
        be enabled if LFAs are not enabled.<a href="#section-2.8-3" class="pilcrow">¶</a></p>
<p id="section-2.8-4">The "candidate-enabled" data leaf designates that an interface can
        be used as a backup.<a href="#section-2.8-4" class="pilcrow">¶</a></p>
</section>
</div>
<div id="yang-op">
<section id="section-2.9">
        <h3 id="name-operational-states">
<a href="#section-2.9" class="section-number selfRef">2.9. </a><a href="#name-operational-states" class="section-name selfRef">Operational States</a>
        </h3>
<p id="section-2.9-1">Operational states are defined in the "ietf-isis" module in various containers at various levels:<a href="#section-2.9-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlNewline" id="section-2.9-2">
          <dt id="section-2.9-2.1">system-counters:</dt>
          <dd style="margin-left: 1.5em" id="section-2.9-2.2">Provides statistical information about
                the global system.<a href="#section-2.9-2.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.9-2.3">interface:</dt>
          <dd style="margin-left: 1.5em" id="section-2.9-2.4">Provides configuration state information for
                each interface.<a href="#section-2.9-2.4" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.9-2.5">adjacencies:</dt>
          <dd style="margin-left: 1.5em" id="section-2.9-2.6">Provides state information about current
          IS-IS adjacencies.<a href="#section-2.9-2.6" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.9-2.7">spf-log:</dt>
          <dd style="margin-left: 1.5em" id="section-2.9-2.8">Provides information about Shortest Path First (SPF) events for an IS-IS instance.
          This <span class="bcp14">SHOULD</span> be implemented as a wrapping buffer.<a href="#section-2.9-2.8" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.9-2.9">lsp-log:</dt>
          <dd style="margin-left: 1.5em" id="section-2.9-2.10">Provides information about LSP events for an IS-IS instance
          (reception of an LSP or modification of a local LSP).
          This <span class="bcp14">SHOULD</span> be implemented as a wrapping buffer. The implementation <span class="bcp14">MAY</span> optionally log LSP refreshes.<a href="#section-2.9-2.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.9-2.11">local-rib:</dt>
          <dd style="margin-left: 1.5em" id="section-2.9-2.12">Provides the IS-IS internal routing table.<a href="#section-2.9-2.12" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.9-2.13">database:</dt>
          <dd style="margin-left: 1.5em" id="section-2.9-2.14">Provides the contents of the current Link State Database (LSDB).<a href="#section-2.9-2.14" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.9-2.15">hostnames:</dt>
          <dd style="margin-left: 1.5em" id="section-2.9-2.16">Provides the system-ID-to-hostname mappings <span>[<a href="#RFC5301" class="cite xref">RFC5301</a>]</span>.<a href="#section-2.9-2.16" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.9-2.17">fast-reroute:</dt>
          <dd style="margin-left: 1.5em" id="section-2.9-2.18">Provides IP FRR state information.<a href="#section-2.9-2.18" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
</dl>
</section>
</div>
</section>
</div>
<div id="RPC">
<section id="section-3">
      <h2 id="name-rpc-operations">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-rpc-operations" class="section-name selfRef">RPC Operations</a>
      </h2>
<p id="section-3-1">The "ietf-isis" module defines two RPC operations:<a href="#section-3-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlNewline" id="section-3-2">
        <dt id="section-3-2.1">clear-database:</dt>
        <dd style="margin-left: 1.5em" id="section-3-2.2">Resets the contents of a particular IS-IS
        database and restarts database synchronization with all
        neighbors.<a href="#section-3-2.2" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-3-2.3">clear-adjacency:</dt>
        <dd style="margin-left: 1.5em" id="section-3-2.4">Restarts a particular set of IS-IS
        adjacencies.<a href="#section-3-2.4" class="pilcrow">¶</a>
</dd>
      <dd class="break"></dd>
</dl>
</section>
</div>
<div id="notif">
<section id="section-4">
      <h2 id="name-notifications">
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-notifications" class="section-name selfRef">Notifications</a>
      </h2>
<p id="section-4-1">The "ietf-isis" module defines the following notifications:<a href="#section-4-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlNewline" id="section-4-2">
        <dt id="section-4-2.1">database-overload:</dt>
        <dd style="margin-left: 1.5em" id="section-4-2.2">This notification is sent when the IS-IS node's overload condition changes.<a href="#section-4-2.2" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-4-2.3">lsp-too-large:</dt>
        <dd style="margin-left: 1.5em" id="section-4-2.4">This notification is sent when the system tries to propagate a PDU
        that is too large.<a href="#section-4-2.4" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-4-2.5">if-state-change:</dt>
        <dd style="margin-left: 1.5em" id="section-4-2.6">This notification is sent when an interface's state changes.<a href="#section-4-2.6" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-4-2.7">corrupted-lsp-detected:</dt>
        <dd style="margin-left: 1.5em" id="section-4-2.8">This notification is sent when the IS-IS node discovers
                   that an LSP that was previously stored in the LSDB, i.e., local memory, has
                   become corrupted.<a href="#section-4-2.8" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-4-2.9">attempt-to-exceed-max-sequence:</dt>
        <dd style="margin-left: 1.5em" id="section-4-2.10">This notification is sent when the system
                  wraps the 32-bit sequence counter of an LSP.<a href="#section-4-2.10" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-4-2.11">id-len-mismatch:</dt>
        <dd style="margin-left: 1.5em" id="section-4-2.12">This notification is sent when a PDU
                  with a different value for the system ID length is received.<a href="#section-4-2.12" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-4-2.13">max-area-addresses-mismatch:</dt>
        <dd style="margin-left: 1.5em" id="section-4-2.14">This notification is sent when a PDU
                  with a different value for the Maximum Area Addresses is received.<a href="#section-4-2.14" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-4-2.15">own-lsp-purge:</dt>
        <dd style="margin-left: 1.5em" id="section-4-2.16">This notification is sent when the system
                  receives a PDU with its own system ID and zero age.<a href="#section-4-2.16" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-4-2.17">sequence-number-skipped:</dt>
        <dd style="margin-left: 1.5em" id="section-4-2.18">This notification is sent when the system
                  receives a PDU with its own system ID and
                  different contents. The system has to reissue
                  the LSP with a higher sequence number.<a href="#section-4-2.18" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-4-2.19">authentication-type-failure:</dt>
        <dd style="margin-left: 1.5em" id="section-4-2.20">This notification is sent when the system
                  receives a PDU with the wrong authentication type
                  field.<a href="#section-4-2.20" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-4-2.21">authentication-failure:</dt>
        <dd style="margin-left: 1.5em" id="section-4-2.22">This notification is sent when the system
                  receives a PDU with the wrong authentication
                  information.<a href="#section-4-2.22" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-4-2.23">version-skew:</dt>
        <dd style="margin-left: 1.5em" id="section-4-2.24">This notification is sent when the system
                  receives a PDU with a different protocol version
                  number.<a href="#section-4-2.24" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-4-2.25">area-mismatch:</dt>
        <dd style="margin-left: 1.5em" id="section-4-2.26">This notification is sent when the system
                  receives a Hello PDU from an IS that does
                  not share any area address.<a href="#section-4-2.26" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-4-2.27">rejected-adjacency:</dt>
        <dd style="margin-left: 1.5em" id="section-4-2.28">This notification is sent when the system
                  receives a Hello PDU from an IS but does not
                  establish an adjacency for some reason.<a href="#section-4-2.28" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-4-2.29">protocols-supported-mismatch:</dt>
        <dd style="margin-left: 1.5em" id="section-4-2.30">This notification is sent when the system
                  receives a non-pseudonode LSP that has no matching
                  protocol supported.<a href="#section-4-2.30" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-4-2.31">lsp-error-detected:</dt>
        <dd style="margin-left: 1.5em" id="section-4-2.32">This notification is sent when the system
                  receives an LSP with a parse error.<a href="#section-4-2.32" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-4-2.33">adjacency-state-change:</dt>
        <dd style="margin-left: 1.5em" id="section-4-2.34">This notification is sent when an IS-IS adjacency
                   moves to the "up" state or the "down" state.<a href="#section-4-2.34" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-4-2.35">lsp-received:</dt>
        <dd style="margin-left: 1.5em" id="section-4-2.36">This notification is sent when an LSP
                  is received.<a href="#section-4-2.36" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-4-2.37">lsp-generation:</dt>
        <dd style="margin-left: 1.5em" id="section-4-2.38">This notification is sent when an LSP
                  is regenerated.<a href="#section-4-2.38" class="pilcrow">¶</a>
</dd>
      <dd class="break"></dd>
</dl>
</section>
</div>
<div id="interactions">
<section id="section-5">
      <h2 id="name-interactions-with-other-yan">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-interactions-with-other-yan" class="section-name selfRef">Interactions with Other YANG Modules</a>
      </h2>
<p id="section-5-1">The "isis" container augments the
      "/rt:routing/rt:control-plane-protocols/control-plane-protocol"
      container of the "ietf-routing" module <span>[<a href="#RFC8349" class="cite xref">RFC8349</a>]</span> with IS-IS-specific
      parameters.<a href="#section-5-1" class="pilcrow">¶</a></p>
<p id="section-5-2">The "ietf-isis" module augments
      "/if:interfaces/if:interface" as defined by <span>[<a href="#RFC8343" class="cite xref">RFC8343</a>]</span>
      with ISO-specific parameters.<a href="#section-5-2" class="pilcrow">¶</a></p>
<p id="section-5-3">Some IS-IS-specific route attributes are added to route
      objects in the "ietf-routing" module by augmenting
      "/rt:routing-state/rt:ribs/rt:rib/rt:routes/rt:route".<a href="#section-5-3" class="pilcrow">¶</a></p>
<p id="section-5-4">The module defined in this document uses some groupings from "ietf-keychain" <span>[<a href="#RFC8177" class="cite xref">RFC8177</a>]</span>.<a href="#section-5-4" class="pilcrow">¶</a></p>
<p id="section-5-5">The module reuses types from <span>[<a href="#RFC6991" class="cite xref">RFC6991</a>]</span> and <span>[<a href="#RFC8294" class="cite xref">RFC8294</a>]</span>.<a href="#section-5-5" class="pilcrow">¶</a></p>
<p id="section-5-6">To support Bidirectional Forwarding Detection (BFD) for fast detection, the module relies on <span>[<a href="#RFC9314" class="cite xref">RFC9314</a>]</span>.<a href="#section-5-6" class="pilcrow">¶</a></p>
</section>
</div>
<div id="isis-yang">
<section id="section-6">
      <h2 id="name-is-is-yang-module">
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-is-is-yang-module" class="section-name selfRef">IS-IS YANG Module</a>
      </h2>
<p id="section-6-1">The following specifications are referenced in this module: <span>[<a href="#ISO-10589" class="cite xref">ISO-10589</a>]</span>, <span>[<a href="#RFC1195" class="cite xref">RFC1195</a>]</span>, <span>[<a href="#RFC4090" class="cite xref">RFC4090</a>]</span>, <span>[<a href="#RFC5029" class="cite xref">RFC5029</a>]</span>,
 <span>[<a href="#RFC5120" class="cite xref">RFC5120</a>]</span>,
 <span>[<a href="#RFC5130" class="cite xref">RFC5130</a>]</span>,
 <span>[<a href="#RFC5286" class="cite xref">RFC5286</a>]</span>,
 <span>[<a href="#RFC5301" class="cite xref">RFC5301</a>]</span>,
 <span>[<a href="#RFC5302" class="cite xref">RFC5302</a>]</span>, <span>[<a href="#RFC5305" class="cite xref">RFC5305</a>]</span>, <span>[<a href="#RFC5307" class="cite xref">RFC5307</a>]</span>, <span>[<a href="#RFC5308" class="cite xref">RFC5308</a>]</span>,
 <span>[<a href="#RFC5443" class="cite xref">RFC5443</a>]</span>,
 <span>[<a href="#RFC5880" class="cite xref">RFC5880</a>]</span>,
 <span>[<a href="#RFC5881" class="cite xref">RFC5881</a>]</span>, <span>[<a href="#RFC6119" class="cite xref">RFC6119</a>]</span>, <span>[<a href="#RFC6232" class="cite xref">RFC6232</a>]</span>, 
 <span>[<a href="#RFC6241" class="cite xref">RFC6241</a>]</span>,
 <span>[<a href="#RFC6991" class="cite xref">RFC6991</a>]</span>,
 <span>[<a href="#RFC7490" class="cite xref">RFC7490</a>]</span>,
 <span>[<a href="#RFC7794" class="cite xref">RFC7794</a>]</span>,
 <span>[<a href="#RFC7917" class="cite xref">RFC7917</a>]</span>,
 <span>[<a href="#RFC7981" class="cite xref">RFC7981</a>]</span>,
 <span>[<a href="#RFC8177" class="cite xref">RFC8177</a>]</span>,
 <span>[<a href="#RFC8294" class="cite xref">RFC8294</a>]</span>,
 <span>[<a href="#RFC8342" class="cite xref">RFC8342</a>]</span>,
 <span>[<a href="#RFC8343" class="cite xref">RFC8343</a>]</span>,
 <span>[<a href="#RFC8349" class="cite xref">RFC8349</a>]</span>,
 <span>[<a href="#RFC8405" class="cite xref">RFC8405</a>]</span>,
 <span>[<a href="#RFC8570" class="cite xref">RFC8570</a>]</span>,
 <span>[<a href="#RFC8706" class="cite xref">RFC8706</a>]</span>, and
 <span>[<a href="#RFC9314" class="cite xref">RFC9314</a>]</span>.<a href="#section-6-1" class="pilcrow">¶</a></p>
<div id="section-6-2">
<pre class="breakable lang-yang sourcecode">&lt;CODE BEGINS&gt; file "ietf-isis@2022-10-19.yang"

module ietf-isis {
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:ietf-isis";
  prefix isis;

  import ietf-routing {
    prefix rt;
    reference
      "RFC 8349: A YANG Data Model for Routing Management
       (NMDA Version)";
  }
  import ietf-inet-types {
    prefix inet;
    reference
      "RFC 6991: Common YANG Data Types";
  }
  import ietf-yang-types {
    prefix yang;
    reference
      "RFC 6991: Common YANG Data Types";
  }
  import ietf-interfaces {
    prefix if;
    reference
      "RFC 8343: A YANG Data Model for Interface 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 iana-routing-types {
    prefix iana-rt-types;
    reference
      "RFC 8294: Common YANG Data Types for the Routing Area";
  }
  import ietf-bfd-types {
    prefix bfd-types;
    reference
      "RFC 9314: YANG Data Model for Bidirectional Forwarding
       Detection (BFD)";
  }

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

     Editor:   Stephane Litkowski
               &lt;mailto:slitkows.ietf@gmail.com&gt;

     Author:   Derek Yeung
               &lt;mailto:derek@arrcus.com&gt;

     Author:   Acee Lindem
               &lt;mailto:acee@cisco.com&gt;

     Author:   Jeffrey Zhang
               &lt;mailto:zzhang@juniper.net&gt;

     Author:   Ladislav Lhotka
               &lt;mailto:ladislav.lhotka@nic.cz&gt;";
  description
    "This YANG module defines the generic configuration and
     operational states for the IS-IS protocol common to all
     vendor implementations.  It is intended that the module
     will be extended by vendors to define vendor-specific
     IS-IS configuration parameters and policies -
     for example, route maps or route policies.

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

     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) 2022 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 9130; see the
     RFC itself for full legal notices.";
  reference
    "RFC 8342: Network Management Datastore Architecture (NMDA)";

  revision 2022-10-19 {
    description
      "Initial revision.";
    reference
      "RFC 9130: YANG Data Model for the IS-IS Protocol";
  }

  /* Identities */

  identity isis {
    base rt:routing-protocol;
    description
      "Identity for the IS-IS routing protocol.";
  }

  identity lsp-log-reason {
    description
      "Base identity for a Link State PDU (LSP)
       change log reason.";
  }

  identity refresh {
    base lsp-log-reason;
    description
      "Identity used when the LSP log reason is that an LSP
       refresh was received.";
  }

  identity content-change {
    base lsp-log-reason;
    description
      "Identity used when the LSP log reason is
       a change in the contents of the LSP.";
  }

  identity frr-protection-method {
    description
      "Base identity for a Fast Reroute protection method.";
  }

  identity frr-protection-method-lfa {
    base frr-protection-method;
    description
      "Loop-Free Alternate as defined in RFC 5286.";
    reference
      "RFC 5286: Basic Specification for IP Fast Reroute:
       Loop-Free Alternates";
  }

  identity frr-protection-method-rlfa {
    base frr-protection-method;
    description
      "Remote Loop-Free Alternate as defined in RFC 7490.";
    reference
      "RFC 7490: Remote Loop-Free Alternate (LFA)
       Fast Reroute (FRR)";
  }

  identity frr-protection-method-rsvpte {
    base frr-protection-method;
    description
      "RSVP-TE as defined in RFC 4090.";
    reference
      "RFC 4090: Fast Reroute Extensions to RSVP-TE for
       LSP Tunnels";
  }

  identity frr-protection-available-type {
    description
      "Base identity for Fast Reroute protection types
       provided by an alternate path.";
  }

  identity frr-protection-available-node-type {
    base frr-protection-available-type;
    description
      "Node protection is provided by the alternate.";
  }

  identity frr-protection-available-link-type {
    base frr-protection-available-type;
    description
      "Link protection is provided by the alternate.";
  }

  identity frr-protection-available-srlg-type {
    base frr-protection-available-type;
    description
      "Shared Risk Link Group (SRLG) protection is provided by
       the alternate.";
  }

  identity frr-protection-available-downstream-type {
    base frr-protection-available-type;
    description
      "The alternate is downstream of the node in the path.";
  }

  identity frr-protection-available-other-type {
    base frr-protection-available-type;
    description
      "The level of protection is unknown.";
  }

  identity frr-alternate-type {
    description
      "Base identity for the IP Fast Reroute alternate type.";
  }

  identity frr-alternate-type-equal-cost {
    base frr-alternate-type;
    description
      "ECMP-based alternate.";
  }

  identity frr-alternate-type-lfa {
    base frr-alternate-type;
    description
      "LFA-based alternate.";
  }

  identity frr-alternate-type-remote-lfa {
    base frr-alternate-type;
    description
      "Remote-LFA-based alternate.";
  }

  identity frr-alternate-type-tunnel {
    base frr-alternate-type;
    description
      "Tunnel-based alternate (such as RSVP-TE or GRE).";
  }

  identity frr-alternate-mrt {
    base frr-alternate-type;
    description
      "MRT-based alternate.";
  }

  identity frr-alternate-tilfa {
    base frr-alternate-type;
    description
      "TI-LFA-based alternate.";
  }

  identity frr-alternate-other {
    base frr-alternate-type;
    description
      "Other type of alternate.";
  }

  identity unidirectional-link-delay-subtlv-flag {
    description
      "Base identity for the flag corresponding to the
       Unidirectional Link Delay sub-TLV as defined in RFC 8570.";
    reference
      "RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions";
  }

  identity unidirectional-link-delay-subtlv-a-flag {
    base unidirectional-link-delay-subtlv-flag;
    description
      "The 'A' bit field represents the Anomalous (A) bit.
       The A bit is set when the measured value of
       this parameter exceeds its configured
       maximum threshold.
       The A bit is cleared when the measured value
       falls below its configured reuse threshold.
       If the A bit is clear,
       the value represents steady-state link performance.";
  }

  identity min-max-unidirectional-link-delay-subtlv-flag {
    description
      "Base identity for the flag corresponding to the Min/Max
       Unidirectional Link Delay sub-TLV as defined in RFC 8570.";
    reference
      "RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions";
  }

  identity min-max-unidirectional-link-delay-subtlv-a-flag {
    base min-max-unidirectional-link-delay-subtlv-flag;
    description
      "The 'A' bit field represents the Anomalous (A) bit.
       The A bit is set when the measured value of
       this parameter exceeds its configured
       maximum threshold.
       The A bit is cleared when the measured value
       falls below its configured reuse threshold.
       If the A bit is clear,
       the value represents steady-state link performance.";
  }

  identity unidirectional-link-loss-subtlv-flag {
    description
      "Base identity for the flag corresponding to the
       Unidirectional Link Loss sub-TLV as defined in RFC 8570.";
    reference
      "RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions";
  }

  identity unidirectional-link-loss-subtlv-a-flag {
    base unidirectional-link-loss-subtlv-flag;
    description
      "The 'A' bit field represents the Anomalous (A) bit.
       The A bit is set when the measured value of
       this parameter exceeds its configured
       maximum threshold.
       The A bit is cleared when the measured value
       falls below its configured reuse threshold.
       If the A bit is clear,
       the value represents steady-state link performance.";
  }

  identity tlv229-flag {
    description
      "Base identity for the flag corresponding to TLV 229
       (M-Topologies) as defined in RFC 5120.";
    reference
      "RFC 5120: M-ISIS: Multi Topology (MT) Routing in
       Intermediate System to Intermediate Systems (IS-ISs)";
  }

  identity tlv229-overload-flag {
    base tlv229-flag;
    description
      "If set, the originator is overloaded
       and must be avoided in the path calculation.";
  }

  identity tlv229-attached-flag {
    base tlv229-flag;
    description
      "If set, the originator is attached to
       another area using the referred metric.";
  }

  identity router-capability-flag {
    description
      "Base identity for the flag corresponding to the
       Router Capability TLV as defined in RFC 7981.";
    reference
      "RFC 7981: IS-IS Extensions for Advertising Router
       Information";
  }

  identity router-capability-flooding-flag {
    base router-capability-flag;
    description
      "Quote from RFC 7981:
       'If the S bit is set(1), the IS-IS Router CAPABILITY TLV
       MUST be flooded across the entire routing domain.  If the
       S bit is not set(0), the TLV MUST NOT be leaked between
       levels.  This bit MUST NOT be altered during the TLV
       leaking.'";
  }

  identity router-capability-down-flag {
    base router-capability-flag;
    description
      "Quote from RFC 7981:
       'When the IS-IS Router CAPABILITY TLV is leaked from
       Level 2 (L2) to Level 1 (L1), the D bit MUST be set.
       Otherwise, this bit MUST be clear.  IS-IS Router
       CAPABILITY TLVs with the D bit set MUST NOT be leaked from
       Level 1 to Level 2.  This is to prevent TLV looping.'";
  }

  identity lsp-flag {
    description
      "Base identity for LSP attributes as defined in ISO 10589.";
    reference
      "ISO 10589: Intermediate System to Intermediate System
       intra-domain routeing information exchange protocol
       for use in conjunction with the protocol for providing
       the connectionless-mode network service (ISO 8473)";
  }

  identity lsp-partitioned-flag {
    base lsp-flag;
    description
      "Originator partition repair supported.";
  }

  identity lsp-attached-error-metric-flag {
    base lsp-flag;
    description
      "Set when the originator is attached to
       another area using the error metric.";
  }

  identity lsp-attached-delay-metric-flag {
    base lsp-flag;
    description
      "Set when the originator is attached to
       another area using the delay metric.";
  }

  identity lsp-attached-expense-metric-flag {
    base lsp-flag;
    description
      "Set when the originator is attached to
       another area using the expense metric.";
  }

  identity lsp-attached-default-metric-flag {
    base lsp-flag;
    description
      "Set when the originator is attached to
       another area using the default metric.";
  }

  identity lsp-overload-flag {
    base lsp-flag;
    description
      "If set, the originator is overloaded
       and must be avoided in the path calculation.";
  }

  identity lsp-l1-system-flag {
    base lsp-flag;
    description
      "Set when the Intermediate System has an L1 type.";
  }

  identity lsp-l2-system-flag {
    base lsp-flag;
    description
      "Set when the Intermediate System has an L2 type.";
  }

  /* Feature definitions */

  feature osi-interface {
    description
      "Support of OSI-specific parameters on an interface.";
  }

  feature poi-tlv {
    description
      "Support of the Purge Originator Identification (POI) TLV.";
    reference
      "RFC 6232: Purge Originator Identification TLV for IS-IS";
  }

  feature ietf-spf-delay {
    description
      "Support for the IETF SPF delay algorithm.";
    reference
      "RFC 8405: Shortest Path First (SPF) Back-Off Delay Algorithm
       for Link-State IGPs";
  }

  feature bfd {
    description
      "Support for detection of IS-IS neighbor reachability
       via BFD.";
    reference
      "RFC 5880: Bidirectional Forwarding Detection (BFD)
       RFC 5881: Bidirectional Forwarding Detection (BFD)
       for IPv4 and IPv6 (Single Hop)";
  }

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

  feature node-flag {
    description
      "Support for node flags for IS-IS prefixes.";
    reference
      "RFC 7794: IS-IS Prefix Attributes for Extended IPv4 and IPv6
       Reachability";
  }

  feature node-tag {
    description
      "Support for node administrative tags for IS-IS
       routing instances.";
    reference
      "RFC 7917: Advertising Node Administrative Tags in IS-IS";
  }

  feature ldp-igp-sync {
    description
      "Support for LDP IGP synchronization.";
    reference
      "RFC 5443: LDP IGP Synchronization";
  }

  feature fast-reroute {
    description
      "Support for IP Fast Reroute (IP FRR).";
  }

  feature nsr {
    description
      "Support for Non-Stop-Routing (NSR).  The IS-IS NSR feature
       allows a router with redundant control-plane capability
       (e.g., dual Route Processor (RP) cards) to maintain its
       state and adjacencies during planned and unplanned
       IS-IS instance restarts.  It differs from graceful restart
       or Non-Stop Forwarding (NSF) in that no protocol signaling
       or assistance from adjacent IS-IS neighbors is required to
       recover control-plane state.";
  }

  feature lfa {
    description
      "Support for Loop-Free Alternates (LFAs).";
    reference
      "RFC 5286: Basic Specification for IP Fast Reroute:
       Loop-Free Alternates";
  }

  feature remote-lfa {
    description
      "Support for remote LFAs (R-LFAs).";
    reference
      "RFC 7490: Remote Loop-Free Alternate (LFA)
       Fast Reroute (FRR)";
  }

  feature overload-max-metric {
    description
      "Support of overload by setting all links to the maximum
       link metric.  In IS-IS, the overload bit is usually used to
       signal that a node cannot be used as a transit node.  The
       'overload-max-metric' feature provides similar behavior,
       also setting all the link metrics to MAX_METRIC.";
  }

  feature prefix-tag {
    description
      "Support for 32-bit prefix tags.";
    reference
      "RFC 5130: A Policy Control Mechanism in IS-IS Using
       Administrative Tags";
  }

  feature prefix-tag64 {
    description
      "Support for 64-bit prefix tags.";
    reference
      "RFC 5130: A Policy Control Mechanism in IS-IS Using
       Administrative Tags";
  }

  feature auto-cost {
    description
      "Support for an IS-IS interface metric computation
       according to a reference bandwidth.";
  }

  feature te-rid {
    description
      "Traffic Engineering router ID.";
    reference
      "RFC 5305: IS-IS Extensions for Traffic Engineering
       RFC 6119: IPv6 Traffic Engineering in IS-IS";
  }

  feature max-ecmp {
    description
      "Sets the maximum number of ECMP paths.";
  }

  feature multi-topology {
    description
      "Support for Multi-Topology (MT) Routing.";
    reference
      "RFC 5120: M-ISIS: Multi Topology (MT) Routing in
       Intermediate System to Intermediate Systems (IS-ISs)";
  }

  feature nlpid-control {
    description
      "Support for the advertisement of a Network Layer
       Protocol Identifier within an IS-IS configuration.";
  }

  feature graceful-restart {
    description
      "Support for IS-IS graceful restart.";
    reference
      "RFC 8706: Restart Signaling for IS-IS";
  }

  feature lsp-refresh {
    description
      "Configuration of the LSP refresh interval.";
  }

  feature maximum-area-addresses {
    description
      "Support for 'maximum-area-addresses' configuration.";
  }

  feature admin-control {
    description
      "Administrative control of the protocol state.";
  }

  /* Type definitions */

  typedef circuit-id {
    type uint8;
    description
      "This type defines the circuit ID
       associated with an interface.";
  }

  typedef extended-circuit-id {
    type uint32;
    description
      "This type defines the extended circuit ID
       associated with an interface.";
  }

  typedef interface-type {
    type enumeration {
      enum broadcast {
        description
          "Broadcast interface type.";
      }
      enum point-to-point {
        description
          "Point-to-point interface type.";
      }
    }
    description
      "This type defines the type of adjacency
       to be established for the interface.
       'interface-type' determines the type
       of Hello message that is used.";
  }

  typedef level {
    type enumeration {
      enum level-1 {
        description
          "This enum indicates L1-only capability.";
      }
      enum level-2 {
        description
          "This enum indicates L2-only capability.";
      }
      enum level-all {
        description
          "This enum indicates capability for both levels.";
      }
    }
    default "level-all";
    description
      "This type defines the IS-IS level of an object.";
  }

  typedef adj-state-type {
    type enumeration {
      enum up {
        description
          "This state indicates that the adjacency is established.";
      }
      enum down {
        description
          "This state indicates that the adjacency is
           NOT established.";
      }
      enum init {
        description
          "This state indicates that the adjacency is being
           established.";
      }
      enum failed {
        description
          "This state indicates that the adjacency has failed.";
      }
    }
    description
      "This type defines the states of an adjacency.";
  }

  typedef if-state-type {
    type enumeration {
      enum up {
        description
          "'up' state.";
      }
      enum down {
        description
          "'down' state.";
      }
    }
    description
      "This type defines the state of an interface.";
  }

  typedef level-number {
    type uint8 {
      range "1 .. 2";
    }
    description
      "This type defines the current IS-IS level.";
  }

  typedef lsp-id {
    type string {
      pattern '[0-9A-Fa-f]{4}\.[0-9A-Fa-f]{4}\.[0-9A-Fa-f]'
            + '{4}\.[0-9][0-9]-[0-9][0-9]';
    }
    description
      "This type defines the IS-IS LSP ID format using a
       pattern.  An example LSP ID is '0143.0438.AEF0.02-01'.";
  }

  typedef area-address {
    type string {
      pattern '[0-9A-Fa-f]{2}(\.[0-9A-Fa-f]{4}){0,6}';
    }
    description
      "This type defines the area address format.";
  }

  typedef snpa {
    type string {
      length "0 .. 20";
    }
    description
      "This type defines the Subnetwork Point of Attachment (SNPA)
       format.  The SNPA should be encoded according to the rules
       specified for the particular type of subnetwork being used.
       As an example, for an Ethernet subnetwork, the SNPA is
       encoded as a Media Access Control (MAC) address, such as
       '00aa.bbcc.ddee'.";
  }

  typedef system-id {
    type string {
      pattern '[0-9A-Fa-f]{4}\.[0-9A-Fa-f]{4}\.[0-9A-Fa-f]{4}';
    }
    description
      "This type defines the IS-IS system ID by using a pattern.
       An example system ID is '0143.0438.AEF0'.";
  }

  typedef extended-system-id {
    type string {
      pattern '[0-9A-Fa-f]{4}\.[0-9A-Fa-f]{4}\.[0-9A-Fa-f]{4}\.'
            + '[0-9][0-9]';
    }
    description
      "This type defines the IS-IS system ID using a pattern.
       'extended-system-id' contains the pseudonode number
       in addition to the system ID.
       An example extended system ID is '0143.0438.AEF0.00'.";
  }

  typedef wide-metric {
    type uint32 {
      range "0 .. 16777215";
    }
    description
      "This type defines the wide-style format of an IS-IS metric.";
  }

  typedef std-metric {
    type uint8 {
      range "0 .. 63";
    }
    description
      "This type defines the old-style format of the IS-IS metric.";
  }

  typedef mesh-group-state {
    type enumeration {
      enum mesh-inactive {
        description
          "The interface is not part of a mesh group.";
      }
      enum mesh-set {
        description
          "The interface is part of a mesh group.";
      }
      enum mesh-blocked {
        description
          "LSPs must not be flooded over this interface.";
      }
    }
    description
      "This type describes the mesh group state of an interface.";
  }

  /* Grouping for notifications */

  grouping notification-instance-hdr {
    description
      "Instance-specific IS-IS notification data grouping.";
    leaf routing-protocol-name {
      type leafref {
        path "/rt:routing/rt:control-plane-protocols/"
           + "rt:control-plane-protocol/rt:name";
      }
      description
        "Name of the IS-IS instance.";
    }
    leaf isis-level {
      type level;
      description
        "IS-IS level of the instance.";
    }
  }

  grouping notification-interface-hdr {
    description
      "Interface-specific IS-IS notification data grouping.";
    leaf interface-name {
      type if:interface-ref;
      description
        "IS-IS interface name.";
    }
    leaf interface-level {
      type level;
      description
        "IS-IS level of the interface.";
    }
    leaf extended-circuit-id {
      type extended-circuit-id;
      description
        "Extended circuit ID of the interface.";
    }
  }

  /* Groupings for IP Fast Reroute */

  grouping instance-fast-reroute-config {
    description
      "This group defines the global configuration of IP
       Fast Reroute (FRR).";
    container fast-reroute {
      if-feature "fast-reroute";
      description
        "This container may be augmented with global
         parameters for IP FRR.";
      container lfa {
        if-feature "lfa";
        description
          "This container may be augmented with
           global parameters for Loop-Free Alternates (LFAs).
           The creation of this container has no effect on
           LFA activation.";
      }
    }
  }

  grouping interface-lfa-config {
    leaf candidate-enabled {
      type boolean;
      default "true";
      description
        "Enables the interface to be used as a backup.";
    }
    leaf enabled {
      type boolean;
      default "false";
      description
        "Activates the LFA.  Per-prefix LFA computation is assumed.";
    }
    container remote-lfa {
      if-feature "remote-lfa";
      leaf enabled {
        type boolean;
        default "false";
        description
          "Activates the remote LFA (R-LFA).";
      }
      description
        "Remote LFA configuration.";
    }
    description
      "Grouping for LFA interface configuration.";
  }

  grouping interface-fast-reroute-config {
    description
      "This group defines the interface configuration of IP FRR.";
    container fast-reroute {
      if-feature "fast-reroute";
      container lfa {
        if-feature "lfa";
        uses interface-lfa-config;
        container level-1 {
          uses interface-lfa-config;
          description
            "LFA level-1 configuration.";
        }
        container level-2 {
          uses interface-lfa-config;
          description
            "LFA level-2 configuration.";
        }
        description
          "LFA configuration.";
      }
      description
        "Interface IP FRR configuration.";
    }
  }

  grouping instance-fast-reroute-state {
    description
      "IP FRR state data grouping.";
    container protected-routes {
      config false;
      list address-family-stats {
        key "address-family prefix alternate";
        leaf address-family {
          type iana-rt-types:address-family;
          description
            "Address family.";
        }
        leaf prefix {
          type inet:ip-prefix;
          description
            "Protected prefix.";
        }
        leaf alternate {
          type inet:ip-address;
          description
            "Alternate next hop for the prefix.";
        }
        leaf alternate-type {
          type identityref {
            base frr-alternate-type;
          }
          description
            "Type of alternate.";
        }
        leaf best {
          type boolean;
          description
            "Set when the alternate is the preferred alternate;
             clear otherwise.";
        }
        leaf non-best-reason {
          type string {
            length "1..255";
          }
          description
            "Information field that explains why the alternate
             is not the best alternate.  The length should be
             limited to 255 Unicode characters.  The expected format
             is a single line of text.";
        }
        container protection-available {
          leaf-list protection-types {
            type identityref {
              base frr-protection-available-type;
            }
            description
              "This list contains a set of protection
               types defined as identities.
               An identity must be added for each type of
               protection provided by the alternate.
               As an example, if an alternate provides
               SRLG, node, and link protection, three
               identities must be added in this list:
               one for SRLG protection, one for node
               protection, and one for link protection.";
          }
          description
            "Protection types provided by the alternate.";
        }
        leaf alternate-metric-1 {
          type uint32;
          description
            "Metric from the Point of Local Repair (PLR) to the
             destination through the alternate path.";
        }
        leaf alternate-metric-2 {
          type uint32;
          description
            "Metric from the PLR to the alternate node.";
        }
        leaf alternate-metric-3 {
          type uint32;
          description
            "Metric from the alternate node to the destination.";
        }
        description
          "Per-address-family protected prefix statistics.";
      }
      description
        "List of prefixes that are protected.";
    }
    container unprotected-routes {
      config false;
      list prefixes {
        key "address-family prefix";
        leaf address-family {
          type iana-rt-types:address-family;
          description
            "Address family.";
        }
        leaf prefix {
          type inet:ip-prefix;
          description
            "Unprotected prefix.";
        }
        description
          "Per-address-family unprotected prefix statistics.";
      }
      description
        "List of prefixes that are not protected.";
    }
    list protection-statistics {
      key "frr-protection-method";
      config false;
      leaf frr-protection-method {
        type identityref {
          base frr-protection-method;
        }
        description
          "Protection method used.";
      }
      list address-family-stats {
        key "address-family";
        leaf address-family {
          type iana-rt-types:address-family;
          description
            "Address family.";
        }
        leaf total-routes {
          type yang:gauge32;
          description
            "Total prefixes.";
        }
        leaf unprotected-routes {
          type yang:gauge32;
          description
            "Total prefixes that are not protected.";
        }
        leaf protected-routes {
          type yang:gauge32;
          description
            "Total prefixes that are protected.";
        }
        leaf link-protected-routes {
          type yang:gauge32;
          description
            "Total prefixes that are link protected.";
        }
        leaf node-protected-routes {
          type yang:gauge32;
          description
            "Total prefixes that are node protected.";
        }
        description
          "Per-address-family protected prefix statistics.";
      }
      description
        "Global protection statistics.";
    }
  }

  /* Routing table and local Routing Information Base (RIB)
     groupings */

  grouping local-rib {
    description
      "Local RIB: RIB for routes computed by the local IS-IS
       routing instance.";
    container local-rib {
      config false;
      description
        "Local RIB.";
      list route {
        key "prefix";
        description
          "Routes.";
        leaf prefix {
          type inet:ip-prefix;
          description
            "Destination prefix.";
        }
        container next-hops {
          description
            "Next hops for the route.";
          list next-hop {
            key "next-hop";
            description
              "List of next hops for the route.";
            leaf outgoing-interface {
              type if:interface-ref;
              description
                "Name of the outgoing interface.";
            }
            leaf next-hop {
              type inet:ip-address;
              description
                "Next-hop address.";
            }
          }
        }
        leaf metric {
          type uint32;
          description
            "Metric for this route.";
        }
        leaf level {
          type level-number;
          description
            "Level number for this route.";
        }
        leaf route-tag {
          type uint32;
          description
            "Route tag for this route.";
        }
      }
    }
  }

  grouping route-content {
    description
      "IS-IS protocol-specific route properties grouping.";
    leaf metric {
      type uint32;
      description
        "IS-IS metric of a route.";
    }
    leaf-list tag {
      type uint64;
      description
        "List of tags associated with the route.  This list
         provides a consolidated view of both 32-bit and 64-bit
         tags (RFC 5130) available for the prefix.";
      reference
        "RFC 5130: A Policy Control Mechanism in IS-IS Using
         Administrative Tags";
    }
    leaf route-type {
      type enumeration {
        enum l2-intra-area {
          description
            "Level-2 internal route.  As per RFC 5302,
             the prefix is directly connected to the
             advertising router.  It cannot be
             distinguished from an L1-&gt;L2 inter-area
             route.";
          reference
            "RFC 5302: Domain-Wide Prefix Distribution with
             Two-Level IS-IS";
        }
        enum l1-intra-area {
          description
            "Level-1 internal route.  As per RFC 5302,
             the prefix is directly connected to the
             advertising router.";
        }
        enum l2-external {
          description
            "Level-2 external route.  As per RFC 5302,
             such a route is learned from other IGPs.
             It cannot be distinguished from an L1-&gt;L2
             inter-area external route.";
        }
        enum l1-external {
          description
            "Level-1 external route.  As per RFC 5302,
             such a route is learned from other IGPs.";
        }
        enum l1-inter-area {
          description
            "These prefixes are learned via L2 routing.";
        }
        enum l1-inter-area-external {
          description
            "These prefixes are learned via L2 routing
             towards a level-2 external route.";
        }
      }
      description
        "IS-IS route type.";
    }
  }

  /* Grouping definitions for configuration and operational states */

  grouping adjacency-state {
    container adjacencies {
      config false;
      list adjacency {
        leaf neighbor-sys-type {
          type level;
          description
            "Level capability of the neighboring system.";
        }
        leaf neighbor-sysid {
          type system-id;
          description
            "The system ID of the neighbor.";
        }
        leaf neighbor-extended-circuit-id {
          type extended-circuit-id;
          description
            "The circuit ID of the neighbor.";
        }
        leaf neighbor-snpa {
          type snpa;
          description
            "The SNPA of the neighbor.";
        }
        leaf usage {
          type level;
          description
            "Defines the level(s) activated for the adjacency.
             On a point-to-point link, this might be level 1 and
             level 2, but on a LAN, the usage will be level 1
             between neighbors at level 1 or level 2 between
             neighbors at level 2.";
        }
        leaf hold-timer {
          type rt-types:timer-value-seconds16;
          units "seconds";
          description
            "The holding time (in seconds) for this adjacency.
             This value is based on received Hello PDUs and the
             elapsed time since receipt.";
        }
        leaf neighbor-priority {
          type uint8 {
            range "0 .. 127";
          }
          description
            "Priority of the neighboring IS for becoming the
             Designated Intermediate System (DIS).";
        }
        leaf lastuptime {
          type yang:timestamp;
          description
            "When the adjacency most recently entered the
             'up' state, measured in hundredths of a
             second since the last reinitialization of
             the network management subsystem.
             The value is 0 if the adjacency has never
             been in the 'up' state.";
        }
        leaf state {
          type adj-state-type;
          description
            "This leaf describes the state of the interface.";
        }
        description
          "List of operational adjacencies.";
      }
      description
        "This container lists the adjacencies of
         the local node.";
    }
    description
      "Adjacency state.";
  }

  grouping admin-control {
    leaf enabled {
      if-feature "admin-control";
      type boolean;
      default "true";
      description
        "Enables or disables the protocol.";
    }
    description
      "Grouping for administrative control.";
  }

  grouping ietf-spf-delay {
    leaf initial-delay {
      type rt-types:timer-value-milliseconds;
      units "msec";
      default "50";
      description
        "Delay used while in the QUIET state (milliseconds).";
    }
    leaf short-delay {
      type rt-types:timer-value-milliseconds;
      units "msec";
      default "200";
      description
        "Delay used while in the SHORT_WAIT state (milliseconds).";
    }
    leaf long-delay {
      type rt-types:timer-value-milliseconds;
      units "msec";
      default "5000";
      description
        "Delay used while in the LONG_WAIT state (milliseconds).";
    }
    leaf hold-down {
      type rt-types:timer-value-milliseconds;
      units "msec";
      default "10000";
      description
        "This timer value defines the period without any changes
         for the IGP to be considered stable (in milliseconds).";
    }
    leaf time-to-learn {
      type rt-types:timer-value-milliseconds;
      units "msec";
      default "500";
      description
        "Duration used to learn all the IGP events
         related to a single network event (milliseconds).";
    }
    leaf current-state {
      type enumeration {
        enum quiet {
          description
            "QUIET state.";
        }
        enum short-wait {
          description
            "SHORT_WAIT state.";
        }
        enum long-wait {
          description
            "LONG_WAIT state.";
        }
      }
      config false;
      description
        "Current SPF Back-Off algorithm state.";
    }
    leaf remaining-time-to-learn {
      type rt-types:timer-value-milliseconds;
      units "msec";
      config false;
      description
        "Remaining time until the time-to-learn timer fires.";
    }
    leaf remaining-hold-down {
      type rt-types:timer-value-milliseconds;
      units "msec";
      config false;
      description
        "Remaining time until the hold-down timer fires.";
    }
    leaf last-event-received {
      type yang:timestamp;
      config false;
      description
        "Time of the last IGP event received.";
    }
    leaf next-spf-time {
      type yang:timestamp;
      config false;
      description
        "Time when the next SPF has been scheduled.";
    }
    leaf last-spf-time {
      type yang:timestamp;
      config false;
      description
        "Time of the last SPF computation.";
    }
    description
      "Grouping for IETF SPF delay configuration and state.";
    reference
      "RFC 8405: Shortest Path First (SPF) Back-Off Delay Algorithm
       for Link-State IGPs";
  }

  grouping node-tag-config {
    description
      "IS-IS node tag configuration state.";
    container node-tags {
      if-feature "node-tag";
      list node-tag {
        key "tag";
        leaf tag {
          type uint32;
          description
            "Node tag value.";
        }
        description
          "List of tags.";
      }
      description
        "Container for node administrative tags.";
    }
  }

  grouping authentication-global-cfg {
    choice authentication-type {
      case key-chain {
        if-feature "key-chain";
        leaf key-chain {
          type key-chain:key-chain-ref;
          description
            "Reference to a key chain.";
        }
      }
      case password {
        leaf key {
          type string;
          description
            "This leaf specifies the authentication key.  The
             length of the key may be dependent on the
             cryptographic algorithm.";
        }
        leaf crypto-algorithm {
          type identityref {
            base key-chain:crypto-algorithm;
          }
          description
            "Cryptographic algorithm associated with a key.";
        }
      }
      description
        "Choice of authentication.";
    }
    description
      "Grouping for global authentication configuration.";
  }

  grouping metric-type-global-cfg {
    leaf value {
      type enumeration {
        enum wide-only {
          description
            "Advertises the new metric style only (RFC 5305).";
          reference
            "RFC 5305: IS-IS Extensions for Traffic Engineering";
        }
        enum old-only {
          description
            "Advertises the old metric style only (RFC 1195).";
          reference
            "RFC 1195: Use of OSI IS-IS for routing in TCP/IP and
             dual environments";
        }
        enum both {
          description
            "Advertises both metric styles.";
        }
      }
      description
        "Type of metric to be generated:

         -  'wide-only' means that only a new metric style
            is generated.
         -  'old-only' means that only an old metric style
            is generated.
         -  'both' means that both are advertised.

         This leaf only affects IPv4 metrics.";
    }
    description
      "Grouping for global metric style configuration.";
  }

  grouping metric-type-global-cfg-with-default {
    leaf value {
      type enumeration {
        enum wide-only {
          description
            "Advertises the new metric style only (RFC 5305).";
          reference
            "RFC 5305: IS-IS Extensions for Traffic Engineering";
        }
        enum old-only {
          description
            "Advertises the old metric style only (RFC 1195).";
          reference
            "RFC 1195: Use of OSI IS-IS for routing in TCP/IP and
             dual environments";
        }
        enum both {
          description
            "Advertises both metric styles.";
        }
      }
      default "wide-only";
      description
        "Type of metric to be generated:

         -  'wide-only' means that only a new metric style
            is generated.
         -  'old-only' means that only an old metric style
            is generated.
         -  'both' means that both are advertised.

         This leaf only affects IPv4 metrics.";
    }
    description
      "Grouping for global metric style configuration.";
  }

  grouping default-metric-global-cfg {
    leaf value {
      type wide-metric;
      description
        "Value of the metric.";
    }
    description
      "Global default metric configuration grouping.";
  }

  grouping default-metric-global-cfg-with-default {
    leaf value {
      type wide-metric;
      default "10";
      description
        "Value of the metric.";
    }
    description
      "Global default metric configuration grouping.";
  }

  grouping overload-global-cfg {
    leaf status {
      type boolean;
      default "false";
      description
        "This leaf specifies the overload status.";
    }
    description
      "Grouping for overload bit configuration.";
  }

  grouping overload-max-metric-global-cfg {
    leaf timeout {
      type rt-types:timer-value-seconds16;
      units "seconds";
      description
        "Timeout (in seconds) of the overload condition.";
    }
    description
      "Overload maximum metric configuration grouping.";
  }

  grouping route-preference-global-cfg {
    choice granularity {
      case detail {
        leaf internal {
          type uint8;
          description
            "Protocol preference for internal routes.";
        }
        leaf external {
          type uint8;
          description
            "Protocol preference for external routes.";
        }
      }
      case coarse {
        leaf default {
          type uint8;
          description
            "Protocol preference for all IS-IS routes.";
        }
      }
      description
        "Choice for implementation of route preference.";
    }
    description
      "Global route preference grouping.";
  }

  grouping hello-authentication-cfg {
    choice authentication-type {
      case key-chain {
        if-feature "key-chain";
        leaf key-chain {
          type key-chain:key-chain-ref;
          description
            "Reference to a key chain.";
        }
      }
      case password {
        leaf key {
          type string;
          description
            "Authentication key specification.  The length of the
             key may be dependent on the cryptographic algorithm.";
        }
        leaf crypto-algorithm {
          type identityref {
            base key-chain:crypto-algorithm;
          }
          description
            "Cryptographic algorithm associated with a key.";
        }
      }
      description
        "Choice of authentication.";
    }
    description
      "Grouping for Hello authentication.";
  }

  grouping hello-interval-cfg {
    leaf value {
      type rt-types:timer-value-seconds16;
      units "seconds";
      description
        "Interval (in seconds) between successive Hello
         messages.";
    }
    description
      "Interval between Hello messages.";
  }

  grouping hello-interval-cfg-with-default {
    leaf value {
      type rt-types:timer-value-seconds16;
      units "seconds";
      default "10";
      description
        "Interval (in seconds) between successive Hello
         messages.";
    }
    description
      "Interval between Hello messages.";
  }

  grouping hello-multiplier-cfg {
    leaf value {
      type uint16;
      description
        "Number of missed Hello messages prior to
         declaring the adjacency down.";
    }
    description
      "Grouping for the number of missed Hello messages prior to
       declaring the adjacency down.";
  }

  grouping hello-multiplier-cfg-with-default {
    leaf value {
      type uint16;
      default "3";
      description
        "Number of missed Hello messages prior to
         declaring the adjacency down.";
    }
    description
      "Grouping for the number of missed Hello messages prior to
       declaring the adjacency down.";
  }

  grouping priority-cfg {
    leaf value {
      type uint8 {
        range "0 .. 127";
      }
      description
        "Priority of the interface for DIS election.";
    }
    description
      "Interface DIS election priority grouping.";
  }

  grouping priority-cfg-with-default {
    leaf value {
      type uint8 {
        range "0 .. 127";
      }
      default "64";
      description
        "Priority of the interface for DIS election.";
    }
    description
      "Interface DIS election priority grouping.";
  }

  grouping metric-cfg {
    leaf value {
      type wide-metric;
      description
        "Metric value.";
    }
    description
      "Interface metric grouping.";
  }

  grouping metric-cfg-with-default {
    leaf value {
      type wide-metric;
      default "10";
      description
        "Metric value.";
    }
    description
      "Interface metric grouping.";
  }

  grouping metric-parameters {
    container metric-type {
      uses metric-type-global-cfg-with-default;
      container level-1 {
        uses metric-type-global-cfg;
        description
          "Configuration specific to level 1.";
      }
      container level-2 {
        uses metric-type-global-cfg;
        description
          "Configuration specific to level 2.";
      }
      description
        "Metric style global configuration.";
    }
    container default-metric {
      uses default-metric-global-cfg-with-default;
      container level-1 {
        uses default-metric-global-cfg;
        description
          "Configuration specific to level 1.";
      }
      container level-2 {
        uses default-metric-global-cfg;
        description
          "Configuration specific to level 2.";
      }
      description
        "Default metric global configuration.";
    }
    container auto-cost {
      if-feature "auto-cost";
      description
        "Interface auto-cost configuration state.";
      leaf enabled {
        type boolean;
        description
          "Enables or disables interface auto-cost.";
      }
      leaf reference-bandwidth {
        when "../enabled = 'true'" {
          description
            "Only when auto-cost is enabled.";
        }
        type uint32 {
          range "1..4294967";
        }
        units "Mbits";
        description
          "Configures the reference bandwidth used to automatically
           determine the interface cost (Mbits).  The cost is the
           reference bandwidth divided by the interface speed,
           with 1 being the minimum cost.";
      }
    }
    description
      "Grouping for global metric parameters.";
  }

  grouping high-availability-parameters {
    container graceful-restart {
      if-feature "graceful-restart";
      leaf enabled {
        type boolean;
        default "false";
        description
          "Enables graceful restart.";
      }
      leaf restart-interval {
        type rt-types:timer-value-seconds16;
        units "seconds";
        description
          "Interval (in seconds) to attempt graceful restart prior
           to failure.";
      }
      leaf helper-enabled {
        type boolean;
        default "true";
        description
          "Enables a local IS-IS router as a graceful restart
           helper.";
      }
      description
        "Configuration of graceful restart.";
    }
    container nsr {
      if-feature "nsr";
      description
        "Non-Stop Routing (NSR) configuration.";
      leaf enabled {
        type boolean;
        default "false";
        description
          "Enables or disables NSR.";
      }
    }
    description
      "Grouping for high-availability parameters.";
  }

  grouping authentication-parameters {
    container authentication {
      uses authentication-global-cfg;
      container level-1 {
        uses authentication-global-cfg;
        description
          "Configuration specific to level 1.";
      }
      container level-2 {
        uses authentication-global-cfg;
        description
          "Configuration specific to level 2.";
      }
      description
        "Authentication global configuration for
         both LSPs and Sequence Number PDUs (SNPs).";
    }
    description
      "Grouping for authentication parameters.";
  }

  grouping address-family-parameters {
    container address-families {
      if-feature "nlpid-control";
      list address-family-list {
        key "address-family";
        leaf address-family {
          type iana-rt-types:address-family;
          description
            "Address family.";
        }
        leaf enabled {
          type boolean;
          description
            "Activates the address family.";
        }
        description
          "List of address families and whether or not they
           are activated.";
      }
      description
        "Address family configuration.";
    }
    description
      "Grouping for address family parameters.";
  }

  grouping mpls-parameters {
    container mpls {
      container te-rid {
        if-feature "te-rid";
        description
          "Stable IS-IS router IP address used for Traffic
           Engineering.";
        leaf ipv4-router-id {
          type inet:ipv4-address;
          description
            "Router ID value that would be used in TLV 134.";
        }
        leaf ipv6-router-id {
          type inet:ipv6-address;
          description
            "Router ID value that would be used in TLV 140.";
        }
      }
      container ldp {
        container igp-sync {
          if-feature "ldp-igp-sync";
          description
            "This container may be augmented with global
             parameters for LDP IGP synchronization.";
        }
        description
          "LDP configuration.";
      }
      description
        "MPLS configuration.";
    }
    description
      "Grouping for MPLS global parameters.";
  }

  grouping lsp-parameters {
    leaf lsp-mtu {
      type uint16;
      units "bytes";
      default "1492";
      description
        "Maximum size of an LSP PDU in bytes.";
    }
    leaf lsp-lifetime {
      type uint16 {
        range "1..65535";
      }
      units "seconds";
      description
        "Lifetime of the router's LSPs in seconds.";
    }
    leaf lsp-refresh {
      if-feature "lsp-refresh";
      type rt-types:timer-value-seconds16;
      units "seconds";
      description
        "Refresh interval of the router's LSPs in seconds.";
    }
    leaf poi-tlv {
      if-feature "poi-tlv";
      type boolean;
      default "false";
      description
        "Enables the advertisement of the IS-IS Purge Originator
         Identification TLV.";
    }
    description
      "Grouping for LSP global parameters.";
  }

  grouping spf-parameters {
    container spf-control {
      leaf paths {
        if-feature "max-ecmp";
        type uint16 {
          range "1..65535";
        }
        description
          "Maximum number of Equal-Cost Multi-Path (ECMP) paths.";
      }
      container ietf-spf-delay {
        if-feature "ietf-spf-delay";
        uses ietf-spf-delay;
        description
          "IETF SPF delay algorithm configuration.";
      }
      description
        "SPF calculation control.";
    }
    description
      "Grouping for SPF global parameters.";
  }

  grouping instance-config {
    description
      "IS-IS global configuration grouping.";
    uses admin-control;
    leaf level-type {
      type level;
      default "level-all";
      description
        "Level of an IS-IS node.  Can be 'level-1', 'level-2', or
         'level-all'.";
    }
    leaf system-id {
      type system-id;
      description
        "System ID of the node.";
    }
    leaf maximum-area-addresses {
      if-feature "maximum-area-addresses";
      type uint8;
      default "3";
      description
        "Maximum areas supported.";
    }
    leaf-list area-address {
      type area-address;
      description
        "List of areas supported by the protocol instance.";
    }
    uses lsp-parameters;
    uses high-availability-parameters;
    uses node-tag-config;
    uses metric-parameters;
    uses authentication-parameters;
    uses address-family-parameters;
    uses mpls-parameters;
    uses spf-parameters;
    uses instance-fast-reroute-config;
    container preference {
      uses route-preference-global-cfg;
      description
        "Router preference configuration for IS-IS
         protocol instance route installation.";
    }
    container overload {
      uses overload-global-cfg;
      description
        "Router protocol instance overload state configuration.";
    }
    container overload-max-metric {
      if-feature "overload-max-metric";
      uses overload-max-metric-global-cfg;
      description
        "Router protocol instance overload maximum
         metric advertisement configuration.";
    }
  }

  grouping instance-state {
    description
      "IS-IS instance operational state.";
    uses spf-log;
    uses lsp-log;
    uses hostname-db;
    uses lsdb;
    uses local-rib;
    uses system-counters;
    uses instance-fast-reroute-state;
    leaf discontinuity-time {
      type yang:date-and-time;
      description
        "The time of the most recent occasion at which any one
         or more of this IS-IS instance's counters suffered a
         discontinuity.  If no such discontinuities have occurred
         since the IS-IS instance was last reinitialized, then
         this node contains the time the IS-IS instance was
         reinitialized, which normally occurs when it was
         created.";
    }
  }

  grouping multi-topology-config {
    description
      "Per-topology configuration.";
    container default-metric {
      uses default-metric-global-cfg;
      container level-1 {
        uses default-metric-global-cfg;
        description
          "Configuration specific to level 1.";
      }
      container level-2 {
        uses default-metric-global-cfg;
        description
          "Configuration specific to level 2.";
      }
      description
        "Default metric per-topology configuration.";
    }
    uses node-tag-config;
  }

  grouping interface-config {
    description
      "Interface configuration grouping.";
    uses admin-control;
    leaf level-type {
      type level;
      default "level-all";
      description
        "IS-IS level of the interface.";
    }
    leaf lsp-pacing-interval {
      type rt-types:timer-value-milliseconds;
      units "milliseconds";
      default "33";
      description
        "Interval (in milliseconds) between LSP transmissions.";
    }
    leaf lsp-retransmit-interval {
      type rt-types:timer-value-seconds16;
      units "seconds";
      description
        "Interval (in seconds) between LSP retransmissions.";
    }
    leaf passive {
      type boolean;
      default "false";
      description
        "Indicates whether the interface is in passive mode (IS-IS
         is not running, but the network is advertised).";
    }
    leaf csnp-interval {
      type rt-types:timer-value-seconds16;
      units "seconds";
      default "10";
      description
        "Interval (in seconds) between Complete Sequence Number
         Packet (CSNP) messages.";
    }
    container hello-padding {
      leaf enabled {
        type boolean;
        default "true";
        description
          "IS-IS Hello padding activation.  Enabled by default.";
      }
      description
        "IS-IS Hello padding configuration.";
    }
    leaf mesh-group-enabled {
      type mesh-group-state;
      description
        "IS-IS interface mesh group state.";
    }
    leaf mesh-group {
      when "../mesh-group-enabled = 'mesh-set'" {
        description
          "Only valid when 'mesh-group-enabled' equals 'mesh-set'.";
      }
      type uint8;
      description
        "IS-IS interface mesh group ID.";
    }
    leaf interface-type {
      type interface-type;
      default "broadcast";
      description
        "Type of adjacency to be established for the interface.
         This dictates the type of Hello messages that are used.";
    }
    leaf-list tag {
      if-feature "prefix-tag";
      type uint32;
      description
        "List of tags associated with the interface.";
    }
    leaf-list tag64 {
      if-feature "prefix-tag64";
      type uint64;
      description
        "List of 64-bit tags associated with the interface.";
    }
    leaf node-flag {
      if-feature "node-flag";
      type boolean;
      default "false";
      description
        "Sets the prefix as a node representative prefix.";
    }
    container hello-authentication {
      uses hello-authentication-cfg;
      container level-1 {
        uses hello-authentication-cfg;
        description
          "Configuration specific to level 1.";
      }
      container level-2 {
        uses hello-authentication-cfg;
        description
          "Configuration specific to level 2.";
      }
      description
        "Authentication type to be used in Hello messages.";
    }
    container hello-interval {
      uses hello-interval-cfg-with-default;
      container level-1 {
        uses hello-interval-cfg;
        description
          "Configuration specific to level 1.";
      }
      container level-2 {
        uses hello-interval-cfg;
        description
          "Configuration specific to level 2.";
      }
      description
        "Interval between Hello messages.";
    }
    container hello-multiplier {
      uses hello-multiplier-cfg-with-default;
      container level-1 {
        uses hello-multiplier-cfg;
        description
          "Configuration specific to level 1.";
      }
      container level-2 {
        uses hello-multiplier-cfg;
        description
          "Configuration specific to level 2.";
      }
      description
        "Hello multiplier configuration.";
    }
    container priority {
      must '../interface-type = "broadcast"' {
        error-message "Priority only applies to broadcast "
                    + "interfaces.";
        description
          "Checks for a broadcast interface.";
      }
      uses priority-cfg-with-default;
      container level-1 {
        uses priority-cfg;
        description
          "Configuration specific to level 1.";
      }
      container level-2 {
        uses priority-cfg;
        description
          "Configuration specific to level 2.";
      }
      description
        "Priority for DIS election.";
    }
    container metric {
      uses metric-cfg-with-default;
      container level-1 {
        uses metric-cfg;
        description
          "Configuration specific to level 1.";
      }
      container level-2 {
        uses metric-cfg;
        description
          "Configuration specific to level 2.";
      }
      description
        "Metric configuration.";
    }
    container bfd {
      if-feature "bfd";
      description
        "BFD interface configuration.";
      uses bfd-types:client-cfg-parms;
      reference
        "RFC 5880: Bidirectional Forwarding Detection (BFD)
         RFC 5881: Bidirectional Forwarding Detection
         (BFD) for IPv4 and IPv6 (Single Hop)
         RFC 9314: YANG Data Model for Bidirectional Forwarding
         Detection (BFD)";
    }
    container address-families {
      if-feature "nlpid-control";
      list address-family-list {
        key "address-family";
        leaf address-family {
          type iana-rt-types:address-family;
          description
            "Address family.";
        }
        description
          "List of address families.";
      }
      description
        "Interface address families.";
    }
    container mpls {
      container ldp {
        leaf igp-sync {
          if-feature "ldp-igp-sync";
          type boolean;
          default "false";
          description
            "Enables IGP/LDP synchronization.";
        }
        description
          "Configuration related to LDP.";
      }
      description
        "MPLS configuration for IS-IS interfaces.";
    }
    uses interface-fast-reroute-config;
  }

  grouping multi-topology-interface-config {
    description
      "IS-IS interface topology configuration.";
    container metric {
      uses metric-cfg;
      container level-1 {
        uses metric-cfg;
        description
          "Configuration specific to level 1.";
      }
      container level-2 {
        uses metric-cfg;
        description
          "Configuration specific to level 2.";
      }
      description
        "Metric IS-IS interface configuration.";
    }
  }

  grouping interface-state {
    description
      "IS-IS interface operational state.";
    uses adjacency-state;
    uses event-counters;
    uses packet-counters;
    leaf discontinuity-time {
      type yang:date-and-time;
      description
        "The time of the most recent occasion at which any one
         or more of this IS-IS interface's counters suffered a
         discontinuity.  If no such discontinuities have occurred
         since the IS-IS interface was last reinitialized, then
         this node contains the time the IS-IS interface was
         reinitialized, which normally occurs when it was
         created.";
    }
  }

  /* Grouping for the hostname database */

  grouping hostname-db {
    container hostnames {
      config false;
      list hostname {
        key "system-id";
        leaf system-id {
          type system-id;
          description
            "System ID associated with the hostname.";
        }
        leaf hostname {
          type string {
            length "1..255";
          }
          description
            "Hostname associated with the system ID
             as defined in RFC 5301.";
          reference
            "RFC 5301: Dynamic Hostname Exchange Mechanism
             for IS-IS";
        }
        description
          "List of system ID / hostname associations.";
      }
      description
        "Hostname-to-system-ID mapping database.";
    }
    description
      "Grouping for hostname-to-system-ID mapping database.";
  }

  /* Groupings for counters */

  grouping system-counters {
    container system-counters {
      config false;
      list level {
        key "level";
        leaf level {
          type level-number;
          description
            "IS-IS level.";
        }
        leaf corrupted-lsps {
          type uint32;
          description
            "Number of corrupted in-memory LSPs detected.
             LSPs received from the wire with a bad
             checksum are silently dropped and not counted.
             LSPs received from the wire with parse errors
             are counted by 'lsp-errors'.";
        }
        leaf authentication-type-fails {
          type uint32;
          description
            "Number of authentication type mismatches.";
        }
        leaf authentication-fails {
          type uint32;
          description
            "Number of authentication key failures.";
        }
        leaf database-overload {
          type uint32;
          description
            "Number of times the database has become
             overloaded.";
        }
        leaf own-lsp-purge {
          type uint32;
          description
            "Number of times a zero-aged copy of the system's
             own LSP is received from some other IS-IS node.";
        }
        leaf manual-address-drop-from-area {
          type uint32;
          description
            "Number of times a manual address
             has been dropped from the area.";
        }
        leaf max-sequence {
          type uint32;
          description
            "Number of times the system has attempted
             to exceed the maximum sequence number.";
        }
        leaf sequence-number-skipped {
          type uint32;
          description
            "Number of times a sequence number skip has
             occurred.";
        }
        leaf id-len-mismatch {
          type uint32;
          description
            "Number of times a PDU is received with a
             different value for the ID field length
             than that of the receiving system.";
        }
        leaf partition-changes {
          type uint32;
          description
            "Number of partition changes detected.";
        }
        leaf lsp-errors {
          type uint32;
          description
            "Number of LSPs received with errors.";
        }
        leaf spf-runs {
          type uint32;
          description
            "Number of times SPF was run at this level.";
        }
        description
          "List of supported levels.";
      }
      description
        "List of counters for the IS-IS protocol instance.";
    }
    description
      "Grouping for IS-IS system counters.";
  }

  grouping event-counters {
    container event-counters {
      config false;
      leaf adjacency-changes {
        type uint32;
        description
          "The number of times an adjacency state change has
           occurred on this interface.";
      }
      leaf adjacency-number {
        type uint32;
        description
          "The number of adjacencies on this interface.";
      }
      leaf init-fails {
        type uint32;
        description
          "The number of times initialization of this interface has
           failed.  This counts events such as Point-to-Point
           Protocol (PPP) Network Control Protocol (NCP) failures.
           Failures to form an adjacency are counted by
           'adjacency-rejects'.";
      }
      leaf adjacency-rejects {
        type uint32;
        description
          "The number of times an adjacency has been
           rejected on this interface.";
      }
      leaf id-len-mismatch {
        type uint32;
        description
          "The number of times an IS-IS PDU with an ID
           field length different from that for this
           system has been received on this interface.";
      }
      leaf max-area-addresses-mismatch {
        type uint32;
        description
          "The number of times an IS-IS PDU has been
           received on this interface with the
           max area address field differing from that of
           this system.";
      }
      leaf authentication-type-fails {
        type uint32;
        description
          "Number of authentication type mismatches.";
      }
      leaf authentication-fails {
        type uint32;
        description
          "Number of authentication key failures.";
      }
      leaf lan-dis-changes {
        type uint32;
        description
          "The number of times the DIS has changed on this
           interface at this level.  If the interface type is
           'point-to-point', the count is zero.";
      }
      description
        "IS-IS interface event counters.";
    }
    description
      "Grouping for IS-IS interface event counters.";
  }

  grouping packet-counters {
    container packet-counters {
      config false;
      list level {
        key "level";
        leaf level {
          type level-number;
          description
            "IS-IS level.";
        }
        container iih {
          leaf in {
            type uint32;
            description
              "Received IS-IS Hello (IIH) PDUs.";
          }
          leaf out {
            type uint32;
            description
              "Sent IIH PDUs.";
          }
          description
            "Number of IIH PDUs received/sent.";
        }
        container ish {
          leaf in {
            type uint32;
            description
              "Received Intermediate System Hello (ISH) PDUs.";
          }
          leaf out {
            type uint32;
            description
              "Sent ISH PDUs.";
          }
          description
            "ISH PDUs received/sent.";
        }
        container esh {
          leaf in {
            type uint32;
            description
              "Received End System Hello (ESH) PDUs.";
          }
          leaf out {
            type uint32;
            description
              "Sent ESH PDUs.";
          }
          description
            "Number of ESH PDUs received/sent.";
        }
        container lsp {
          leaf in {
            type uint32;
            description
              "Received Link State PDU (LSP) PDUs.";
          }
          leaf out {
            type uint32;
            description
              "Sent LSP PDUs.";
          }
          description
            "Number of LSP PDUs received/sent.";
        }
        container psnp {
          leaf in {
            type uint32;
            description
              "Received Partial Sequence Number PDU (PSNP) PDUs.";
          }
          leaf out {
            type uint32;
            description
              "Sent PSNP PDUs.";
          }
          description
            "Number of PSNP PDUs received/sent.";
        }
        container csnp {
          leaf in {
            type uint32;
            description
              "Received Complete Sequence Number PDU (CSNP) PDUs.";
          }
          leaf out {
            type uint32;
            description
              "Sent CSNP PDUs.";
          }
          description
            "Number of CSNP PDUs received/sent.";
        }
        container unknown {
          leaf in {
            type uint32;
            description
              "Received unknown PDUs.";
          }
          description
            "Number of unknown PDUs received.";
        }
        description
          "List of packet counters for supported levels.";
      }
      description
        "Packet counters per IS-IS level.";
    }
    description
      "Grouping for packet counters per IS-IS level.";
  }

  /* Groupings for various log buffers */

  grouping spf-log {
    container spf-log {
      config false;
      list event {
        key "id";
        leaf id {
          type yang:counter32;
          description
            "Event identifier.  A purely internal value.
             The most recent events are expected to have a bigger
             ID number.";
        }
        leaf spf-type {
          type enumeration {
            enum full {
              description
                "Full SPF computation.";
            }
            enum route-only {
              description
                "SPF computation of route reachability
                 only.";
            }
          }
          description
            "Type of SPF computation performed.";
        }
        leaf level {
          type level-number;
          description
            "IS-IS level number for the SPF computation.";
        }
        leaf schedule-timestamp {
          type yang:timestamp;
          description
            "Timestamp of when the SPF computation was
             scheduled.";
        }
        leaf start-timestamp {
          type yang:timestamp;
          description
            "Timestamp of when the SPF computation started.";
        }
        leaf end-timestamp {
          type yang:timestamp;
          description
            "Timestamp of when the SPF computation ended.";
        }
        list trigger-lsp {
          key "lsp";
          leaf lsp {
            type lsp-id;
            description
              "LSP ID of the LSP that triggered the SPF
               computation.";
          }
          leaf sequence {
            type uint32;
            description
              "Sequence number of the LSP that triggered the SPF
               computation.";
          }
          description
            "This list includes the LSPs that triggered the
             SPF computation.";
        }
        description
          "List of computation events.  Implemented as a
           wrapping buffer.";
      }
      description
        "This container lists the SPF computation events.";
    }
    description
      "Grouping for SPF log events.";
  }

  grouping lsp-log {
    container lsp-log {
      config false;
      list event {
        key "id";
        leaf id {
          type yang:counter32;
          description
            "Event identifier.  A purely internal value.
             The most recent events are expected to have a bigger
             ID number.";
        }
        leaf level {
          type level-number;
          description
            "IS-IS level number for the LSP.";
        }
        container lsp {
          leaf lsp {
            type lsp-id;
            description
              "LSP ID of the LSP.";
          }
          leaf sequence {
            type uint32;
            description
              "Sequence number of the LSP.";
          }
          description
            "LSP identification container for either the received
             LSP or the locally generated LSP.";
        }
        leaf received-timestamp {
          type yang:timestamp;
          description
            "This is the timestamp when the LSP was received.
             In the case of a local LSP update, the timestamp refers
             to the LSP origination time.";
        }
        leaf reason {
          type identityref {
            base lsp-log-reason;
          }
          description
            "Type of LSP change.";
        }
        description
          "List of LSP events.  Implemented as a wrapping buffer.";
      }
      description
        "This container lists the LSP log.
         Local LSP modifications are also included in the list.";
    }
    description
      "Grouping for the LSP log.";
  }

  /* Groupings for the Link State Database (LSDB) descriptions */
  /* Unknown TLV and sub-TLV descriptions */

  grouping tlv {
    description
      "Type-Length-Value (TLV).";
    leaf type {
      type uint16;
      description
        "TLV type.";
    }
    leaf length {
      type uint16;
      description
        "TLV length (octets).";
    }
    leaf value {
      type yang:hex-string;
      description
        "TLV value.";
    }
  }

  grouping unknown-tlvs {
    description
      "Unknown TLVs grouping.  Used for unknown TLVs or
       unknown sub-TLVs.";
    container unknown-tlvs {
      description
        "All unknown TLVs.";
      list unknown-tlv {
        description
          "Unknown TLV.";
        uses tlv;
      }
    }
  }

  /* TLVs and sub-TLVs for prefixes */

  grouping prefix-reachability-attributes {
    description
      "Grouping for extended reachability attributes of an
       IPv4 or IPv6 prefix.";
    leaf external-prefix-flag {
      type boolean;
      description
        "External prefix flag.";
    }
    leaf readvertisement-flag {
      type boolean;
      description
        "Re-advertisement flag.";
    }
    leaf node-flag {
      type boolean;
      description
        "Node flag.";
    }
  }

  grouping prefix-ipv4-source-router-id {
    description
      "Grouping for the IPv4 source router ID of a prefix
       advertisement.";
    leaf ipv4-source-router-id {
      type inet:ipv4-address;
      description
        "IPv4 source router ID address.";
    }
  }

  grouping prefix-ipv6-source-router-id {
    description
      "Grouping for the IPv6 source router ID of a prefix
       advertisement.";
    leaf ipv6-source-router-id {
      type inet:ipv6-address;
      description
        "IPv6 source router ID address.";
    }
  }

  grouping prefix-attributes-extension {
    description
      "Prefix extended attributes as defined in RFC 7794.";
    reference
      "RFC 7794: IS-IS Prefix Attributes for Extended IPv4 and IPv6
       Reachability";
    uses prefix-reachability-attributes;
    uses prefix-ipv4-source-router-id;
    uses prefix-ipv6-source-router-id;
  }

  grouping prefix-ipv4-std {
    description
      "Grouping for attributes of an IPv4 standard prefix
       as defined in RFC 1195.";
    reference
      "RFC 1195: Use of OSI IS-IS for routing in TCP/IP and
       dual environments";
    leaf ip-prefix {
      type inet:ipv4-address;
      description
        "IPv4 prefix address.";
    }
    leaf prefix-len {
      type uint8;
      description
        "IPv4 prefix length (in bits).";
    }
    leaf i-e {
      type boolean;
      description
        "Internal or external (I/E) metric bit value.
         Set to 'false' to indicate an internal metric.";
    }
    container default-metric {
      leaf metric {
        type std-metric;
        description
          "Default IS-IS metric for the IPv4 prefix.";
      }
      description
        "IS-IS default metric container.";
    }
    container delay-metric {
      leaf metric {
        type std-metric;
        description
          "IS-IS delay metric for the IPv4 prefix.";
      }
      leaf supported {
        type boolean;
        default "false";
        description
          "Indicates whether the IS-IS delay metric is supported.";
      }
      description
        "IS-IS delay metric container.";
    }
    container expense-metric {
      leaf metric {
        type std-metric;
        description
          "IS-IS expense metric for the IPv4 prefix.";
      }
      leaf supported {
        type boolean;
        default "false";
        description
          "Indicates whether the IS-IS expense metric is supported.";
      }
      description
        "IS-IS expense metric container.";
    }
    container error-metric {
      leaf metric {
        type std-metric;
        description
          "This leaf describes the IS-IS error metric value.";
      }
      leaf supported {
        type boolean;
        default "false";
        description
          "Indicates whether the IS-IS error metric is supported.";
      }
      description
        "IS-IS error metric container.";
    }
  }

  grouping prefix-ipv4-extended {
    description
      "Grouping for attributes of an IPv4 extended prefix
       as defined in RFC 5305.";
    reference
      "RFC 5305: IS-IS Extensions for Traffic Engineering";
    leaf up-down {
      type boolean;
      description
        "Value of the up/down bit.
         Set to 'true' when the prefix has been advertised down
         the hierarchy.";
    }
    leaf ip-prefix {
      type inet:ipv4-address;
      description
        "IPv4 prefix address.";
    }
    leaf prefix-len {
      type uint8;
      description
        "IPv4 prefix length (in bits).";
    }
    leaf metric {
      type wide-metric;
      description
        "IS-IS wide metric value.";
    }
    leaf-list tag {
      type uint32;
      description
        "List of 32-bit tags associated with the IPv4 prefix.";
    }
    leaf-list tag64 {
      type uint64;
      description
        "List of 64-bit tags associated with the IPv4 prefix.";
    }
    uses prefix-attributes-extension;
  }

  grouping prefix-ipv6-extended {
    description
      "Grouping for attributes of an IPv6 prefix
       as defined in RFC 5308.";
    reference
      "RFC 5308: Routing IPv6 with IS-IS";
    leaf up-down {
      type boolean;
      description
        "Value of the up/down bit.
         Set to 'true' when the prefix has been advertised down
         the hierarchy.";
    }
    leaf ip-prefix {
      type inet:ipv6-address;
      description
        "IPv6 prefix address.";
    }
    leaf prefix-len {
      type uint8;
      description
        "IPv6 prefix length (in bits).";
    }
    leaf metric {
      type wide-metric;
      description
        "IS-IS wide metric value.";
    }
    leaf-list tag {
      type uint32;
      description
        "List of 32-bit tags associated with the IPv6 prefix.";
    }
    leaf-list tag64 {
      type uint64;
      description
        "List of 64-bit tags associated with the IPv6 prefix.";
    }
    uses prefix-attributes-extension;
  }

  /* TLVs and sub-TLVs for neighbors */

  grouping neighbor-link-attributes {
    description
      "Grouping for link attributes as defined
       in RFC 5029.";
    reference
      "RFC 5029: Definition of an IS-IS Link Attribute Sub-TLV";
    leaf link-attributes-flags {
      type uint16;
      description
        "Flags for the link attributes.";
    }
  }

  grouping neighbor-gmpls-extensions {
    description
      "Grouping for GMPLS attributes of a neighbor as defined
       in RFC 5307.";
    reference
      "RFC 5307: IS-IS Extensions in Support of Generalized
       Multi-Protocol Label Switching (GMPLS)";
    leaf link-local-id {
      type uint32;
      description
        "Local identifier of the link.";
    }
    leaf remote-local-id {
      type uint32;
      description
        "Remote identifier of the link.";
    }
    leaf protection-capability {
      type uint8;
      description
        "Describes the protection capabilities
         of the link.  This is the value of the
         first octet of the sub-TLV type 20 value.";
    }
    container interface-switching-capability {
      description
        "Interface switching capabilities of the link.";
      leaf switching-capability {
        type uint8;
        description
          "Switching capability of the link.";
      }
      leaf encoding {
        type uint8;
        description
          "Type of encoding of the LSP being used.";
      }
      container max-lsp-bandwidths {
        description
          "Per-priority maximum LSP bandwidths.";
        list max-lsp-bandwidth {
          leaf priority {
            type uint8 {
              range "0 .. 7";
            }
            description
              "Priority from 0 to 7.";
          }
          leaf bandwidth {
            type rt-types:bandwidth-ieee-float32;
            description
              "Maximum LSP bandwidth.";
          }
          description
            "List of maximum LSP bandwidths for different
             priorities.";
        }
      }
      container tdm-specific {
        when '../switching-capability = 100';
        description
          "Switching-capability-specific information applicable
           when the switching type is Time-Division Multiplexing
           (TDM).";
        leaf minimum-lsp-bandwidth {
          type rt-types:bandwidth-ieee-float32;
          description
            "Minimum LSP bandwidth.";
        }
        leaf indication {
          type uint8;
          description
            "Indicates whether the interface supports Standard
             or Arbitrary SONET/SDH (Synchronous Optical Network /
             Synchronous Digital Hierarchy).";
        }
      }
      container psc-specific {
        when "../switching-capability &gt;= 1 and
              ../switching-capability &lt;= 4";
        description
          "Switching-capability-specific information applicable
           when the switching type is PSC1, PSC2, PSC3, or PSC4
           ('PSC' stands for 'Packet Switching Capability').";
        leaf minimum-lsp-bandwidth {
          type rt-types:bandwidth-ieee-float32;
          description
            "Minimum LSP bandwidth.";
        }
        leaf mtu {
          type uint16;
          units "bytes";
          description
            "Interface MTU.";
        }
      }
    }
  }

  grouping neighbor-extended-te-extensions {
    description
      "Grouping for TE attributes of a neighbor as defined
       in RFC 8570.";
    reference
      "RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions";
    container unidirectional-link-delay {
      description
        "Container for the average delay
         from the local neighbor to the remote neighbor.";
      container flags {
        leaf-list unidirectional-link-delay-subtlv-flags {
          type identityref {
            base unidirectional-link-delay-subtlv-flag;
          }
          description
            "This list contains identities for the bits that
             are set.";
        }
        description
          "Unidirectional Link Delay sub-TLV flags.";
      }
      leaf value {
        type uint32;
        units "usec";
        description
          "Delay value expressed in microseconds.";
      }
    }
    container min-max-unidirectional-link-delay {
      description
        "Container for the minimum and maximum delay
         from the local neighbor to the remote neighbor.";
      container flags {
        leaf-list min-max-unidirectional-link-delay-subtlv-flags {
          type identityref {
            base min-max-unidirectional-link-delay-subtlv-flag;
          }
          description
            "This list contains identities for the bits that
             are set.";
        }
        description
          "Min/Max Unidirectional Link Delay sub-TLV flags.";
      }
      leaf min-value {
        type uint32;
        units "usec";
        description
          "Minimum delay value expressed in microseconds.";
      }
      leaf max-value {
        type uint32;
        units "usec";
        description
          "Maximum delay value expressed in microseconds.";
      }
    }
    container unidirectional-link-delay-variation {
      description
        "Container for the average delay variation
         from the local neighbor to the remote neighbor.";
      leaf value {
        type uint32;
        units "usec";
        description
          "Delay variation value expressed in microseconds.";
      }
    }
    container unidirectional-link-loss {
      description
        "Container for packet loss from the local neighbor to the
         remote neighbor.";
      container flags {
        leaf-list unidirectional-link-loss-subtlv-flags {
          type identityref {
            base unidirectional-link-loss-subtlv-flag;
          }
          description
            "This list contains identities for the bits that
             are set.";
        }
        description
          "Unidirectional Link Loss sub-TLV flags.";
      }
      leaf value {
        type uint32;
        units "percent";
        description
          "Link packet loss expressed as a percentage of
           the total traffic sent over a configurable interval.";
      }
    }
    container unidirectional-link-residual-bandwidth {
      description
        "Container for the residual bandwidth
         from the local neighbor to the remote neighbor.";
      leaf value {
        type rt-types:bandwidth-ieee-float32;
        units "Bps";
        description
          "Residual bandwidth.";
      }
    }
    container unidirectional-link-available-bandwidth {
      description
        "Container for the available bandwidth
         from the local neighbor to the remote neighbor.";
      leaf value {
        type rt-types:bandwidth-ieee-float32;
        units "Bps";
        description
          "Available bandwidth.";
      }
    }
    container unidirectional-link-utilized-bandwidth {
      description
        "Container for the utilized bandwidth
         from the local neighbor to the remote neighbor.";
      leaf value {
        type rt-types:bandwidth-ieee-float32;
        units "Bps";
        description
          "Utilized bandwidth.";
      }
    }
  }

  grouping neighbor-te-extensions {
    description
      "Grouping for TE attributes of a neighbor as defined
       in RFC 5305.";
    reference
      "RFC 5305: IS-IS Extensions for Traffic Engineering";
    leaf admin-group {
      type uint32;
      description
        "Administrative Group / Resource Class/Color.";
    }
    container local-if-ipv4-addrs {
      description
        "All local interface IPv4 addresses.";
      leaf-list local-if-ipv4-addr {
        type inet:ipv4-address;
        description
          "List of local interface IPv4 addresses.";
      }
    }
    container remote-if-ipv4-addrs {
      description
        "All remote interface IPv4 addresses.";
      leaf-list remote-if-ipv4-addr {
        type inet:ipv4-address;
        description
          "List of remote interface IPv4 addresses.";
      }
    }
    leaf te-metric {
      type uint32;
      description
        "TE metric.";
    }
    leaf max-bandwidth {
      type rt-types:bandwidth-ieee-float32;
      description
        "Maximum bandwidth.";
    }
    leaf max-reservable-bandwidth {
      type rt-types:bandwidth-ieee-float32;
      description
        "Maximum reservable bandwidth.";
    }
    container unreserved-bandwidths {
      description
        "All unreserved bandwidths.";
      list unreserved-bandwidth {
        leaf priority {
          type uint8 {
            range "0 .. 7";
          }
          description
            "Priority from 0 to 7.";
        }
        leaf unreserved-bandwidth {
          type rt-types:bandwidth-ieee-float32;
          description
            "Unreserved bandwidth.";
        }
        description
          "List of unreserved bandwidths for different
           priorities.";
      }
    }
  }

  grouping neighbor-extended {
    description
      "Grouping for attributes of an IS-IS extended neighbor.";
    leaf neighbor-id {
      type extended-system-id;
      description
        "System ID of the extended neighbor.";
    }
    container instances {
      description
        "List of all adjacencies between the local
         system and the neighbor system ID.";
      list instance {
        key "id";
        leaf id {
          type uint32;
          description
            "Unique identifier of an instance of a
             particular neighbor.";
        }
        leaf metric {
          type wide-metric;
          description
            "IS-IS wide metric for the extended neighbor.";
        }
        uses neighbor-gmpls-extensions;
        uses neighbor-te-extensions;
        uses neighbor-extended-te-extensions;
        uses neighbor-link-attributes;
        uses unknown-tlvs;
        description
          "Instance of a particular adjacency.";
      }
    }
  }

  grouping neighbor {
    description
      "IS-IS standard neighbor grouping.";
    leaf neighbor-id {
      type extended-system-id;
      description
        "IS-IS neighbor system ID.";
    }
    container instances {
      description
        "List of all adjacencies between the local
         system and the neighbor system ID.";
      list instance {
        key "id";
        leaf id {
          type uint32;
          description
            "Unique identifier of an instance of a
             particular neighbor.";
        }
        leaf i-e {
          type boolean;
          description
            "Internal or external (I/E) metric bit value.
             Set to 'false' to indicate an internal metric.";
        }
        container default-metric {
          leaf metric {
            type std-metric;
            description
              "IS-IS default metric value.";
          }
          description
            "IS-IS default metric container.";
        }
        container delay-metric {
          leaf metric {
            type std-metric;
            description
              "IS-IS delay metric value.";
          }
          leaf supported {
            type boolean;
            default "false";
            description
              "IS-IS delay metric supported.";
          }
          description
            "IS-IS delay metric container.";
        }
        container expense-metric {
          leaf metric {
            type std-metric;
            description
              "IS-IS expense metric value.";
          }
          leaf supported {
            type boolean;
            default "false";
            description
              "IS-IS expense metric supported.";
          }
          description
            "IS-IS expense metric container.";
        }
        container error-metric {
          leaf metric {
            type std-metric;
            description
              "IS-IS error metric value.";
          }
          leaf supported {
            type boolean;
            default "false";
            description
              "IS-IS error metric supported.";
          }
          description
            "IS-IS error metric container.";
        }
        description
          "Instance of a particular adjacency as defined in
           ISO 10589.";
        reference
          "ISO 10589: Intermediate System to Intermediate System
           intra-domain routeing information exchange protocol
           for use in conjunction with the protocol for providing
           the connectionless-mode network service (ISO 8473)";
      }
    }
  }

  /* Top-level TLVs */

  grouping tlv132-ipv4-addresses {
    leaf-list ipv4-addresses {
      type inet:ipv4-address;
      description
        "List of IPv4 addresses of the IS-IS node.  The IS-IS
         reference is TLV 132.";
    }
    description
      "Grouping for TLV 132.";
  }

  grouping tlv232-ipv6-addresses {
    leaf-list ipv6-addresses {
      type inet:ipv6-address;
      description
        "List of IPv6 addresses of the IS-IS node.  The IS-IS
         reference is TLV 232.";
    }
    description
      "Grouping for TLV 232.";
  }

  grouping tlv134-ipv4-te-rid {
    leaf ipv4-te-routerid {
      type inet:ipv4-address;
      description
        "IPv4 Traffic Engineering router ID of the IS-IS node.
         The IS-IS reference is TLV 134.";
    }
    description
      "Grouping for TLV 134.";
  }

  grouping tlv140-ipv6-te-rid {
    leaf ipv6-te-routerid {
      type inet:ipv6-address;
      description
        "IPv6 Traffic Engineering router ID of the IS-IS node.
         The IS-IS reference is TLV 140.";
    }
    description
      "Grouping for TLV 140.";
  }

  grouping tlv129-protocols {
    leaf-list protocol-supported {
      type uint8;
      description
        "List of supported protocols of the IS-IS node.
         The IS-IS reference is TLV 129.";
    }
    description
      "Grouping for TLV 129.";
  }

  grouping tlv137-hostname {
    leaf dynamic-hostname {
      type string;
      description
        "Hostname of the IS-IS node.  The IS-IS reference
         is TLV 137.";
    }
    description
      "Grouping for TLV 137.";
  }

  grouping tlv10-authentication {
    container authentication {
      leaf authentication-type {
        type identityref {
          base key-chain:crypto-algorithm;
        }
        description
          "Authentication type to be used with an IS-IS node.";
      }
      leaf authentication-key {
        type string;
        description
          "Authentication key to be used.  For security reasons,
           the authentication key MUST NOT be presented in
           a cleartext format in response to any request
           (e.g., via get or get-config).";
      }
      description
        "IS-IS node authentication information container.  The
         IS-IS reference is TLV 10.";
    }
    description
      "Grouping for TLV 10.";
  }

  grouping tlv229-mt {
    container mt-entries {
      list topology {
        description
          "List of topologies supported.";
        leaf mt-id {
          type uint16 {
            range "0 .. 4095";
          }
          description
            "Multi-Topology (MT) identifier of the topology.";
        }
        container attributes {
          leaf-list flags {
            type identityref {
              base tlv229-flag;
            }
            description
              "This list contains identities for the bits that
               are set.";
          }
          description
            "TLV 229 flags.";
        }
      }
      description
        "IS-IS node topology information container.  The
         IS-IS reference is TLV 229.";
    }
    description
      "Grouping for TLV 229.";
  }

  grouping tlv242-router-capabilities {
    container router-capabilities {
      list router-capability {
        container flags {
          leaf-list router-capability-flags {
            type identityref {
              base router-capability-flag;
            }
            description
              "This list contains identities for the bits that
               are set.";
          }
          description
            "Router Capability flags.";
        }
        container node-tags {
          if-feature "node-tag";
          list node-tag {
            leaf tag {
              type uint32;
              description
                "Node tag value.";
            }
            description
              "List of tags.";
          }
          description
            "Container for node administrative tags.";
        }
        uses unknown-tlvs;
        description
          "IS-IS node capabilities.  This list element may
           be extended with detailed information.  The IS-IS
           reference is TLV 242.";
      }
      description
        "List of Router Capability TLVs.";
    }
    description
      "Grouping for TLV 242.";
  }

  grouping tlv138-srlg {
    description
      "Grouping for TLV 138.";
    container links-srlgs {
      list links {
        leaf neighbor-id {
          type extended-system-id;
          description
            "System ID of the extended neighbor.";
        }
        leaf flags {
          type uint8;
          description
            "Flags associated with the link.";
        }
        leaf link-local-id {
          type union {
            type inet:ip-address;
            type uint32;
          }
          description
            "Local identifier of the link.
             It could be an IPv4 address or a local identifier.";
        }
        leaf link-remote-id {
          type union {
            type inet:ip-address;
            type uint32;
          }
          description
            "Remote identifier of the link.
             It could be an IPv4 address or a remotely learned
             identifier.";
        }
        container srlgs {
          description
            "List of SRLGs.";
          leaf-list srlg {
            type uint32;
            description
              "SRLG value of the link.";
          }
        }
        description
          "SRLG attribute of a link.";
      }
      description
        "List of links with SRLGs.";
    }
  }

  /* Grouping for LSDB descriptions */

  grouping lsp-entry {
    description
      "IS-IS LSP database entry grouping.";
    leaf decoded-completed {
      type boolean;
      description
        "The IS-IS LSP body has been fully decoded.";
    }
    leaf raw-data {
      type yang:hex-string;
      description
        "The hexadecimal representation of the complete LSP
         as received or originated, in network byte order.";
    }
    leaf lsp-id {
      type lsp-id;
      description
        "LSP ID of the LSP.";
    }
    leaf checksum {
      type uint16;
      description
        "LSP checksum.";
    }
    leaf remaining-lifetime {
      type uint16;
      units "seconds";
      description
        "Remaining lifetime (in seconds) until LSP expiration.";
    }
    leaf sequence {
      type uint32;
      description
        "This leaf describes the sequence number of the LSP.";
    }
    container attributes {
      leaf-list lsp-flags {
        type identityref {
          base lsp-flag;
        }
        description
          "This list contains identities for the bits that
           are set.";
      }
      description
        "LSP attributes.";
    }
    uses tlv132-ipv4-addresses;
    uses tlv232-ipv6-addresses;
    uses tlv134-ipv4-te-rid;
    uses tlv140-ipv6-te-rid;
    uses tlv129-protocols;
    uses tlv137-hostname;
    uses tlv10-authentication;
    uses tlv229-mt;
    uses tlv242-router-capabilities;
    uses tlv138-srlg;
    uses unknown-tlvs;
    container is-neighbor {
      list neighbor {
        key "neighbor-id";
        uses neighbor;
        description
          "List of neighbors.";
      }
      description
        "Standard IS neighbors container.  The IS-IS reference is
         TLV 2.";
    }
    container extended-is-neighbor {
      list neighbor {
        key "neighbor-id";
        uses neighbor-extended;
        description
          "List of extended IS neighbors.";
      }
      description
        "Standard IS extended neighbors container.  The IS-IS
         reference is TLV 22.";
    }
    container ipv4-internal-reachability {
      list prefixes {
        uses prefix-ipv4-std;
        description
          "List of prefixes.";
      }
      description
        "IPv4 internal reachability information container.
         The IS-IS reference is TLV 128.";
    }
    container ipv4-external-reachability {
      list prefixes {
        uses prefix-ipv4-std;
        description
          "List of prefixes.";
      }
      description
        "IPv4 external reachability information container.  The
         IS-IS reference is TLV 130.";
    }
    container extended-ipv4-reachability {
      list prefixes {
        uses prefix-ipv4-extended;
        uses unknown-tlvs;
        description
          "List of prefixes.";
      }
      description
        "IPv4 extended reachability information container.  The
         IS-IS reference is TLV 135.";
    }
    container mt-is-neighbor {
      list neighbor {
        leaf mt-id {
          type uint16 {
            range "0 .. 4095";
          }
          description
            "Multi-Topology (MT) identifier.";
        }
        uses neighbor-extended;
        description
          "List of neighbors.";
      }
      description
        "IS-IS MT neighbor container.  The IS-IS reference is
         TLV 223.";
    }
    container mt-extended-ipv4-reachability {
      list prefixes {
        leaf mt-id {
          type uint16 {
            range "0 .. 4095";
          }
          description
            "MT identifier.";
        }
        uses prefix-ipv4-extended;
        uses unknown-tlvs;
        description
          "List of extended prefixes.";
      }
      description
        "IPv4 MT extended reachability information container.
         The IS-IS reference is TLV 235.";
      reference
        "RFC 5120: M-ISIS: Multi Topology (MT) Routing in
         Intermediate System to Intermediate Systems (IS-ISs)";
    }
    container mt-ipv6-reachability {
      list prefixes {
        leaf mt-id {
          type uint16 {
            range "0 .. 4095";
          }
          description
            "MT identifier.";
        }
        uses prefix-ipv6-extended;
        uses unknown-tlvs;
        description
          "List of IPv6 extended prefixes.";
      }
      description
        "IPv6 MT extended reachability information container.
         The IS-IS reference is TLV 237.";
      reference
        "RFC 5120: M-ISIS: Multi Topology (MT) Routing in
         Intermediate System to Intermediate Systems (IS-ISs)";
    }
    container ipv6-reachability {
      list prefixes {
        uses prefix-ipv6-extended;
        uses unknown-tlvs;
        description
          "List of IPv6 prefixes.";
      }
      description
        "IPv6 reachability information container.  The IS-IS
         reference is TLV 236.";
    }
  }

  grouping lsdb {
    description
      "Link State Database (LSDB) grouping.";
    container database {
      config false;
      list levels {
        key "level";
        leaf level {
          type level-number;
          description
            "LSDB level number (1 or 2).";
        }
        list lsp {
          key "lsp-id";
          uses lsp-entry;
          description
            "List of LSPs in the LSDB.";
        }
        description
          "List of LSPs for the LSDB-level container.";
      }
      description
        "IS-IS LSDB container.";
    }
  }

  /* Augmentations */

  augment "/rt:routing/"
        + "rt:ribs/rt:rib/rt:routes/rt:route" {
    when "derived-from-or-self(rt:source-protocol, 'isis:isis')" {
      description
        "IS-IS-specific route attributes.";
    }
    uses route-content;
    description
      "This augments the route object in the Routing Information
       Base (RIB) with IS-IS-specific attributes.";
  }

  augment "/if:interfaces/if:interface" {
    leaf clns-mtu {
      if-feature "osi-interface";
      type uint16;
      description
        "Connectionless-mode Network Service (CLNS) MTU of the
         interface.";
    }
    description
      "ISO-specific interface parameters.";
  }

  augment "/rt:routing/rt:control-plane-protocols/"
        + "rt:control-plane-protocol" {
    when "derived-from-or-self(rt:type, 'isis:isis')" {
      description
        "This augmentation is only valid when the routing protocol
         instance type is 'isis'.";
    }
    description
      "This augments a routing protocol instance with IS-IS-specific
       parameters.";
    container isis {
      must 'count(area-address) &gt; 0' {
        error-message "At least one area address must be "
                    + "configured.";
        description
          "Enforces the configuration of at least one area.";
      }
      uses instance-config;
      uses instance-state;
      container topologies {
        if-feature "multi-topology";
        list topology {
          key "name";
          leaf enabled {
            type boolean;
            description
              "Enables the topology configuration.";
          }
          leaf name {
            type leafref {
              path "../../../../../../rt:ribs/rt:rib/rt:name";
            }
            description
              "RIB corresponding to the topology.";
          }
          uses multi-topology-config;
          description
            "List of topologies.";
        }
        description
          "MT container.";
      }
      container interfaces {
        list interface {
          key "name";
          leaf name {
            type if:interface-ref;
            description
              "Reference to the interface within
               the routing instance.";
          }
          uses interface-config;
          uses interface-state;
          container topologies {
            if-feature "multi-topology";
            list topology {
              key "name";
              leaf name {
                type leafref {
                  path "../../../../../../../../"
                     + "rt:ribs/rt:rib/rt:name";
                }
                description
                  "RIB corresponding to the topology.";
              }
              uses multi-topology-interface-config;
              description
                "List of interface topologies.";
            }
            description
              "MT container.";
          }
          description
            "List of IS-IS interfaces.";
        }
        description
          "Configuration container specific to IS-IS interfaces.";
      }
      description
        "IS-IS configuration/state top-level container.";
    }
  }

  /* RPC methods */

  rpc clear-adjacency {
    description
      "This RPC request clears a particular set of IS-IS
       adjacencies.  If the operation fails for an internal
       reason, then the 'error-tag' and 'error-app-tag' should be
       set indicating the reason for the failure.";
    reference
      "RFC 6241: Network Configuration Protocol (NETCONF)";
    input {
      leaf routing-protocol-instance-name {
        type leafref {
          path "/rt:routing/rt:control-plane-protocols/"
             + "rt:control-plane-protocol/rt:name";
        }
        mandatory true;
        description
          "Name of the IS-IS protocol instance whose IS-IS
           adjacency is being cleared.

           If the corresponding IS-IS instance doesn't exist,
           then the operation will fail with an 'error-tag' of
           'data-missing' and an 'error-app-tag' of
           'routing-protocol-instance-not-found'.";
      }
      leaf level {
        type level;
        description
          "IS-IS level of the adjacency to be cleared.  If the
           IS-IS level is 'level-all', level-1 and level-2
           adjacencies would both be cleared.

           If the value provided is different from the value
           authorized in the enum type, then the operation
           SHALL fail with an 'error-tag' of 'data-missing' and
           an 'error-app-tag' of 'bad-isis-level'.";
      }
      leaf interface {
        type if:interface-ref;
        description
          "IS-IS interface name.

           If the corresponding IS-IS interface doesn't exist,
           then the operation SHALL fail with an 'error-tag' of
           'data-missing' and an 'error-app-tag' of
           'isis-interface-not-found'.";
      }
    }
  }

  rpc clear-database {
    description
      "This RPC request clears a particular IS-IS database.
       Additionally, all neighbor adjacencies will be forced to
       the DOWN state and self-originated LSPs will be
       reoriginated.  If the operation fails for an IS-IS
       internal reason, then the 'error-tag' and 'error-app-tag'
       should be set indicating the reason for the failure.";
    input {
      leaf routing-protocol-instance-name {
        type leafref {
          path "/rt:routing/rt:control-plane-protocols/"
             + "rt:control-plane-protocol/rt:name";
        }
        mandatory true;
        description
          "Name of the IS-IS protocol instance whose IS-IS
           database or databases are being cleared.

           If the corresponding IS-IS instance doesn't exist,
           then the operation will fail with an 'error-tag' of
           'data-missing' and an 'error-app-tag' of
           'routing-protocol-instance-not-found'.";
      }
      leaf level {
        type level;
        description
          "IS-IS level of the adjacency to be cleared.  If the
           IS-IS level is 'level-all', the databases for both
           level 1 and level 2 would be cleared.

           If the value provided is different from the value
           authorized in the enum type, then the operation
           SHALL fail with an 'error-tag' of 'data-missing' and
           an 'error-app-tag' of 'bad-isis-level'.";
      }
    }
  }

  /* Notifications */

  notification database-overload {
    uses notification-instance-hdr;
    leaf overload {
      type enumeration {
        enum off {
          description
            "Indicates that the IS-IS instance has left the
             overload state.";
        }
        enum on {
          description
            "Indicates that the IS-IS instance has entered the
             overload state.";
        }
      }
      description
        "New overload state of the IS-IS instance.";
    }
    description
      "This notification is sent when an IS-IS instance
       overload state changes.";
  }

  notification lsp-too-large {
    uses notification-instance-hdr;
    uses notification-interface-hdr;
    leaf pdu-size {
      type uint32;
      description
        "Size of the LSP PDU.";
    }
    leaf lsp-id {
      type lsp-id;
      description
        "LSP ID.";
    }
    description
      "This notification is sent when an attempt to propagate
       an LSP that is larger than the dataLinkBlockSize (ISO 10589)
       for the circuit occurs.  The generation of the notification
       must be throttled with at least 5 seconds between successive
       notifications.";
    reference
      "ISO 10589: Intermediate System to Intermediate System
       intra-domain routeing information exchange protocol
       for use in conjunction with the protocol for providing
       the connectionless-mode network service (ISO 8473)";
  }

  notification if-state-change {
    uses notification-instance-hdr;
    uses notification-interface-hdr;
    leaf state {
      type if-state-type;
      description
        "Interface state.";
    }
    description
      "This notification is sent when an interface
       state change is detected.";
  }

  notification corrupted-lsp-detected {
    uses notification-instance-hdr;
    leaf lsp-id {
      type lsp-id;
      description
        "LSP ID.";
    }
    description
      "This notification is sent when an LSP that was stored in
       memory has become corrupted.";
  }

  notification attempt-to-exceed-max-sequence {
    uses notification-instance-hdr;
    leaf lsp-id {
      type lsp-id;
      description
        "LSP ID.";
    }
    description
      "This notification is sent when the system
       wraps the 32-bit sequence counter of an LSP.";
  }

  notification id-len-mismatch {
    uses notification-instance-hdr;
    uses notification-interface-hdr;
    leaf pdu-field-len {
      type uint8;
      description
        "Value for the system ID length in the received PDU.";
    }
    leaf raw-pdu {
      type binary;
      description
        "Received raw PDU.";
    }
    description
      "This notification is sent when a PDU with a different value
       for the system ID length is received.  The generation of the
       notification must be throttled with at least 5 seconds
       between successive notifications.";
  }

  notification max-area-addresses-mismatch {
    uses notification-instance-hdr;
    uses notification-interface-hdr;
    leaf max-area-addresses {
      type uint8;
      description
        "Received number of supported areas.";
    }
    leaf raw-pdu {
      type binary;
      description
        "Received raw PDU.";
    }
    description
      "This notification is sent when a PDU with a different value
       for the Maximum Area Addresses has been received.  The
       generation of the notification must be throttled with
       at least 5 seconds between successive notifications.";
  }

  notification own-lsp-purge {
    uses notification-instance-hdr;
    uses notification-interface-hdr;
    leaf lsp-id {
      type lsp-id;
      description
        "LSP ID.";
    }
    description
      "This notification is sent when the system receives
       a PDU with its own system ID and zero age.";
  }

  notification sequence-number-skipped {
    uses notification-instance-hdr;
    uses notification-interface-hdr;
    leaf lsp-id {
      type lsp-id;
      description
        "LSP ID.";
    }
    description
      "This notification is sent when the system receives a
       PDU with its own system ID and different contents.  The
       system has to originate the LSP with a higher sequence
       number.";
  }

  notification authentication-type-failure {
    uses notification-instance-hdr;
    uses notification-interface-hdr;
    leaf raw-pdu {
      type binary;
      description
        "Received raw PDU.";
    }
    description
      "This notification is sent when the system receives a
       PDU with the wrong authentication type field.
       The generation of the notification must be throttled
       with at least 5 seconds between successive notifications.";
  }

  notification authentication-failure {
    uses notification-instance-hdr;
    uses notification-interface-hdr;
    leaf raw-pdu {
      type binary;
      description
        "Received raw PDU.";
    }
    description
      "This notification is sent when the system receives
       a PDU on which authentication fails.  The generation of the
       notification must be throttled with at least 5 seconds
       between successive notifications.";
  }

  notification version-skew {
    uses notification-instance-hdr;
    uses notification-interface-hdr;
    leaf protocol-version {
      type uint8;
      description
        "Protocol version received in the PDU.";
    }
    leaf raw-pdu {
      type binary;
      description
        "Received raw PDU.";
    }
    description
      "This notification is sent when the system receives a
       PDU with a different protocol version number.
       The generation of the notification must be throttled
       with at least 5 seconds between successive notifications.";
  }

  notification area-mismatch {
    uses notification-instance-hdr;
    uses notification-interface-hdr;
    leaf raw-pdu {
      type binary;
      description
        "Received raw PDU.";
    }
    description
      "This notification is sent when the system receives a
       Hello PDU from an IS that does not share any area
       address.  The generation of the notification must be
       throttled with at least 5 seconds between successive
       notifications.";
  }

  notification rejected-adjacency {
    uses notification-instance-hdr;
    uses notification-interface-hdr;
    leaf raw-pdu {
      type binary;
      description
        "Received raw PDU.";
    }
    leaf reason {
      type string {
        length "0..255";
      }
      description
        "The system may provide a reason to reject the
         adjacency.  If the reason is not available,
         the reason string will not be returned.
         The expected format is a single line of text.";
    }
    description
      "This notification is sent when the system receives a
       Hello PDU from an IS but does not establish an adjacency
       for some reason.  The generation of the notification
       must be throttled with at least 5 seconds between
       successive notifications.";
  }

  notification protocols-supported-mismatch {
    uses notification-instance-hdr;
    uses notification-interface-hdr;
    leaf raw-pdu {
      type binary;
      description
        "Received raw PDU.";
    }
    leaf-list protocols {
      type uint8;
      description
        "List of protocols supported by the remote system.";
    }
    description
      "This notification is sent when the system receives a
       non-pseudonode LSP that has no matching protocols
       supported.  The generation of the notification must be
       throttled with at least 5 seconds between successive
       notifications.";
  }

  notification lsp-error-detected {
    uses notification-instance-hdr;
    uses notification-interface-hdr;
    leaf lsp-id {
      type lsp-id;
      description
        "LSP ID.";
    }
    leaf raw-pdu {
      type binary;
      description
        "Received raw PDU.";
    }
    leaf error-offset {
      type uint32;
      description
        "If the problem is a malformed TLV, the error offset
         points to the start of the TLV.  If the problem is with
         the LSP header, the error offset points to the errant
         byte.";
    }
    leaf tlv-type {
      type uint8;
      description
        "If the problem is a malformed TLV, the TLV type is set
         to the type value of the suspicious TLV.  Otherwise,
         this leaf is not present.";
    }
    description
      "This notification is sent when the system receives an
       LSP with a parse error.  The generation of the notification
       must be throttled with at least 5 seconds between
       successive notifications.";
  }

  notification adjacency-state-change {
    uses notification-instance-hdr;
    uses notification-interface-hdr;
    leaf neighbor {
      type string {
        length "1..255";
      }
      description
        "Name of the neighbor.  It corresponds to the hostname
         associated with the system ID of the neighbor in the
         mapping database (RFC 5301).  If the name of the neighbor
         is not available, it is not returned.";
      reference
        "RFC 5301: Dynamic Hostname Exchange Mechanism for IS-IS";
    }
    leaf neighbor-system-id {
      type system-id;
      description
        "Neighbor system ID.";
    }
    leaf state {
      type adj-state-type;
      description
        "New state of the IS-IS adjacency.";
    }
    leaf reason {
      type string {
        length "1..255";
      }
      description
        "If the adjacency is going to the 'down' state, this leaf
         provides a reason for the adjacency going down.  The reason
         is provided as text.  If the adjacency is going to the 'up'
         state, no reason is provided.  The expected format is a
         single line of text.";
    }
    description
      "This notification is sent when an IS-IS adjacency
       moves to the 'up' state or the 'down' state.";
  }

  notification lsp-received {
    uses notification-instance-hdr;
    uses notification-interface-hdr;
    leaf lsp-id {
      type lsp-id;
      description
        "LSP ID.";
    }
    leaf sequence {
      type uint32;
      description
        "Sequence number of the received LSP.";
    }
    leaf received-timestamp {
      type yang:timestamp;
      description
        "Timestamp when the LSP was received.";
    }
    leaf neighbor-system-id {
      type system-id;
      description
        "Neighbor system ID of the LSP sender.";
    }
    description
      "This notification is sent when an LSP is received.
       The generation of the notification must be throttled with
       at least 5 seconds between successive notifications.";
  }

  notification lsp-generation {
    uses notification-instance-hdr;
    leaf lsp-id {
      type lsp-id;
      description
        "LSP ID.";
    }
    leaf sequence {
      type uint32;
      description
        "Sequence number of the received LSP.";
    }
    leaf send-timestamp {
      type yang:timestamp;
      description
        "Timestamp when the LSP was regenerated.";
    }
    description
      "This notification is sent when an LSP is regenerated.
       The generation of the notification must be throttled with
       at least 5 seconds between successive notifications.";
  }
}

&lt;CODE ENDS&gt;</pre><a href="#section-6-2" class="pilcrow">¶</a>
</div>
</section>
</div>
<div id="Security">
<section id="section-7">
      <h2 id="name-security-considerations">
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
      </h2>
<p id="section-7-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 <span>[<a href="#RFC6241" class="cite xref">RFC6241</a>]</span> or RESTCONF <span>[<a href="#RFC8040" class="cite xref">RFC8040</a>]</span>.
The lowest NETCONF layer is the secure transport layer, and the
mandatory-to-implement secure transport is Secure Shell (SSH)
<span>[<a href="#RFC6242" class="cite xref">RFC6242</a>]</span>. The lowest RESTCONF layer is HTTPS, and the
mandatory-to-implement secure transport is TLS <span>[<a href="#RFC8446" class="cite xref">RFC8446</a>]</span>.<a href="#section-7-1" class="pilcrow">¶</a></p>
<p id="section-7-2">The Network Configuration Access Control Model (NACM) <span>[<a href="#RFC8341" class="cite xref">RFC8341</a>]</span>
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.<a href="#section-7-2" class="pilcrow">¶</a></p>
<p id="section-7-3">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:<a href="#section-7-3" class="pilcrow">¶</a></p>
<p style="margin-left: 1.5em" id="section-7-4">/isis<a href="#section-7-4" class="pilcrow">¶</a></p>
<p style="margin-left: 1.5em" id="section-7-5">/isis/interfaces/interface[name]<a href="#section-7-5" class="pilcrow">¶</a></p>
<p id="section-7-6">For IS-IS, the ability to modify IS-IS configuration will allow the entire IS-IS domain to be compromised, including forming adjacencies with unauthorized routers to misroute traffic or mount a massive Denial-of-Service (DoS) attack.
For example, adding IS-IS on any unprotected interface could allow an IS-IS
      adjacency to be formed with an unauthorized and malicious neighbor. Once
      an adjacency is formed, traffic could be hijacked. As a simpler example,
      a DoS attack could be mounted by changing the cost of an IS-IS interface
      to be asymmetric, such that a hard routing loop ensues. In general,
      unauthorized modification of most IS-IS features will pose its own set
      of security risks; therefore, the Security Considerations sections in the respective reference RFCs should be consulted.<a href="#section-7-6" class="pilcrow">¶</a></p>
<p id="section-7-7">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 are the subtrees and data nodes and their
sensitivity/vulnerability:<a href="#section-7-7" class="pilcrow">¶</a></p>
<p style="margin-left: 1.5em" id="section-7-8">/isis/database<a href="#section-7-8" class="pilcrow">¶</a></p>
<p style="margin-left: 1.5em" id="section-7-9">/isis/local-rib<a href="#section-7-9" class="pilcrow">¶</a></p>
<p id="section-7-10">

Exposure of the Link State Database (LSDB) will reveal the detailed
topology of the network. Similarly, the IS-IS local RIB exposes the reachable
prefixes in the IS-IS routing domain. Exposure of the LSDB and local RIB may
also reveal information beyond the scope of the IS-IS router; this may be
undesirable, since such exposure may facilitate other attacks. Additionally,
the complete IP network topology -- and, if deployed, the TE topology of the
IS-IS domain -- can be reconstructed from the LSDB. Though not as
straightforward, the IS-IS local RIB can also be exploited to discover
topological information. Network operators may consider their topologies to
be sensitive confidential data.<a href="#section-7-10" class="pilcrow">¶</a></p>
<p id="section-7-11">For IS-IS authentication, configuration is supported via the
      specification of a key chain <span>[<a href="#RFC8177" class="cite xref">RFC8177</a>]</span>
      or the direct specification of a key and authentication algorithm.
Hence, authentication configuration using the "key-chain" case in the
"authentication-type" container inherits the security considerations of
 <span>[<a href="#RFC8177" class="cite xref">RFC8177</a>]</span>. This includes considerations with respect to the
   local storage and handling of authentication keys.<a href="#section-7-11" class="pilcrow">¶</a></p>
<p id="section-7-12">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:<a href="#section-7-12" class="pilcrow">¶</a></p>
<p id="section-7-13">The IS-IS YANG
   module supports the "clear-adjacency" and "clear-database" RPCs. If
   access to either of these is compromised, they can be exploited to
   mount DoS attacks due to the resultant network outages.<a href="#section-7-13" class="pilcrow">¶</a></p>
<p id="section-7-14">The actual authentication key data (whether locally specified or part
   of a key chain) is sensitive and needs to be kept secret from
   unauthorized parties; compromise of the key data would allow an attacker to forge IS-IS traffic that would be accepted as authentic,
   potentially compromising the entire IS-IS domain.<a href="#section-7-14" class="pilcrow">¶</a></p>
<p id="section-7-15">The model describes several notifications. Implementations must
      rate-limit the generation of these notifications to avoid creating
      significant notification load. Otherwise, this notification load may
      negatively affect system stability and may be exploited as an attack vector.<a href="#section-7-15" class="pilcrow">¶</a></p>
</section>
</div>
<div id="IANA">
<section id="section-8">
      <h2 id="name-iana-considerations">
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
      </h2>
<p id="section-8-1">The IANA has assigned the following URI in the
      "IETF XML Registry" <span>[<a href="#RFC3688" class="cite xref">RFC3688</a>]</span>.<a href="#section-8-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlCompact dlParallel" id="section-8-2">
        <dt id="section-8-2.1">URI:</dt>
        <dd style="margin-left: 1.5em" id="section-8-2.2">urn:ietf:params:xml:ns:yang:ietf-isis<a href="#section-8-2.2" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-8-2.3">Registrant Contact:</dt>
        <dd style="margin-left: 1.5em" id="section-8-2.4">The IESG<a href="#section-8-2.4" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-8-2.5">XML:</dt>
        <dd style="margin-left: 1.5em" id="section-8-2.6">N/A; the requested URI is an XML namespace.<a href="#section-8-2.6" class="pilcrow">¶</a>
</dd>
      <dd class="break"></dd>
</dl>
<p id="section-8-3">This document also adds the following YANG module name in the "YANG
      Module Names" registry <span>[<a href="#RFC6020" class="cite xref">RFC6020</a>]</span>:<a href="#section-8-3" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlCompact dlParallel" id="section-8-4">
        <dt id="section-8-4.1">Name:</dt>
        <dd style="margin-left: 1.5em" id="section-8-4.2">ietf-isis<a href="#section-8-4.2" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-8-4.3">Maintained by IANA?</dt>
        <dd style="margin-left: 1.5em" id="section-8-4.4">N<a href="#section-8-4.4" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-8-4.5">Namespace:</dt>
        <dd style="margin-left: 1.5em" id="section-8-4.6">urn:ietf:params:xml:ns:yang:ietf-isis<a href="#section-8-4.6" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-8-4.7">Prefix:</dt>
        <dd style="margin-left: 1.5em" id="section-8-4.8">isis<a href="#section-8-4.8" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-8-4.9">Reference:</dt>
        <dd style="margin-left: 1.5em" id="section-8-4.10">RFC 9130<a href="#section-8-4.10" class="pilcrow">¶</a>
</dd>
      <dd class="break"></dd>
</dl>
</section>
</div>
<section id="section-9">
      <h2 id="name-references">
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-references" class="section-name selfRef">References</a>
      </h2>
<section id="section-9.1">
        <h3 id="name-normative-references">
<a href="#section-9.1" class="section-number selfRef">9.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
        </h3>
<dl class="references">
<dt id="ISO-10589">[ISO-10589]</dt>
        <dd>
<span class="refAuthor">ISO</span>, <span class="refTitle">"Intermediate System to Intermediate System intra- domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode network service (ISO 8473)"</span>, <span class="refContent">International Standard 10589: 2002, Second Edition</span>, <time datetime="2002" class="refDate">2002</time>, <span>&lt;<a href="https://www.iso.org/standard/30932.html">https://www.iso.org/standard/30932.html</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC1195">[RFC1195]</dt>
        <dd>
<span class="refAuthor">Callon, R.</span>, <span class="refTitle">"Use of OSI IS-IS for routing in TCP/IP and dual environments"</span>, <span class="seriesInfo">RFC 1195</span>, <span class="seriesInfo">DOI 10.17487/RFC1195</span>, <time datetime="1990-12" class="refDate">December 1990</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc1195">https://www.rfc-editor.org/info/rfc1195</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC2119">[RFC2119]</dt>
        <dd>
<span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03" class="refDate">March 1997</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC3688">[RFC3688]</dt>
        <dd>
<span class="refAuthor">Mealling, M.</span>, <span class="refTitle">"The IETF XML Registry"</span>, <span class="seriesInfo">BCP 81</span>, <span class="seriesInfo">RFC 3688</span>, <span class="seriesInfo">DOI 10.17487/RFC3688</span>, <time datetime="2004-01" class="refDate">January 2004</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3688">https://www.rfc-editor.org/info/rfc3688</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC4090">[RFC4090]</dt>
        <dd>
<span class="refAuthor">Pan, P., Ed.</span>, <span class="refAuthor">Swallow, G., Ed.</span>, and <span class="refAuthor">A. Atlas, Ed.</span>, <span class="refTitle">"Fast Reroute Extensions to RSVP-TE for LSP Tunnels"</span>, <span class="seriesInfo">RFC 4090</span>, <span class="seriesInfo">DOI 10.17487/RFC4090</span>, <time datetime="2005-05" class="refDate">May 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4090">https://www.rfc-editor.org/info/rfc4090</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5029">[RFC5029]</dt>
        <dd>
<span class="refAuthor">Vasseur, JP.</span> and <span class="refAuthor">S. Previdi</span>, <span class="refTitle">"Definition of an IS-IS Link Attribute Sub-TLV"</span>, <span class="seriesInfo">RFC 5029</span>, <span class="seriesInfo">DOI 10.17487/RFC5029</span>, <time datetime="2007-09" class="refDate">September 2007</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5029">https://www.rfc-editor.org/info/rfc5029</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5120">[RFC5120]</dt>
        <dd>
<span class="refAuthor">Przygienda, T.</span>, <span class="refAuthor">Shen, N.</span>, and <span class="refAuthor">N. Sheth</span>, <span class="refTitle">"M-ISIS: Multi Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs)"</span>, <span class="seriesInfo">RFC 5120</span>, <span class="seriesInfo">DOI 10.17487/RFC5120</span>, <time datetime="2008-02" class="refDate">February 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5120">https://www.rfc-editor.org/info/rfc5120</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5130">[RFC5130]</dt>
        <dd>
<span class="refAuthor">Previdi, S.</span>, <span class="refAuthor">Shand, M., Ed.</span>, and <span class="refAuthor">C. Martin</span>, <span class="refTitle">"A Policy Control Mechanism in IS-IS Using Administrative Tags"</span>, <span class="seriesInfo">RFC 5130</span>, <span class="seriesInfo">DOI 10.17487/RFC5130</span>, <time datetime="2008-02" class="refDate">February 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5130">https://www.rfc-editor.org/info/rfc5130</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5286">[RFC5286]</dt>
        <dd>
<span class="refAuthor">Atlas, A., Ed.</span> and <span class="refAuthor">A. Zinin, Ed.</span>, <span class="refTitle">"Basic Specification for IP Fast Reroute: Loop-Free Alternates"</span>, <span class="seriesInfo">RFC 5286</span>, <span class="seriesInfo">DOI 10.17487/RFC5286</span>, <time datetime="2008-09" class="refDate">September 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5286">https://www.rfc-editor.org/info/rfc5286</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5301">[RFC5301]</dt>
        <dd>
<span class="refAuthor">McPherson, D.</span> and <span class="refAuthor">N. Shen</span>, <span class="refTitle">"Dynamic Hostname Exchange Mechanism for IS-IS"</span>, <span class="seriesInfo">RFC 5301</span>, <span class="seriesInfo">DOI 10.17487/RFC5301</span>, <time datetime="2008-10" class="refDate">October 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5301">https://www.rfc-editor.org/info/rfc5301</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5302">[RFC5302]</dt>
        <dd>
<span class="refAuthor">Li, T.</span>, <span class="refAuthor">Smit, H.</span>, and <span class="refAuthor">T. Przygienda</span>, <span class="refTitle">"Domain-Wide Prefix Distribution with Two-Level IS-IS"</span>, <span class="seriesInfo">RFC 5302</span>, <span class="seriesInfo">DOI 10.17487/RFC5302</span>, <time datetime="2008-10" class="refDate">October 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5302">https://www.rfc-editor.org/info/rfc5302</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5305">[RFC5305]</dt>
        <dd>
<span class="refAuthor">Li, T.</span> and <span class="refAuthor">H. Smit</span>, <span class="refTitle">"IS-IS Extensions for Traffic Engineering"</span>, <span class="seriesInfo">RFC 5305</span>, <span class="seriesInfo">DOI 10.17487/RFC5305</span>, <time datetime="2008-10" class="refDate">October 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5305">https://www.rfc-editor.org/info/rfc5305</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5307">[RFC5307]</dt>
        <dd>
<span class="refAuthor">Kompella, K., Ed.</span> and <span class="refAuthor">Y. Rekhter, Ed.</span>, <span class="refTitle">"IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)"</span>, <span class="seriesInfo">RFC 5307</span>, <span class="seriesInfo">DOI 10.17487/RFC5307</span>, <time datetime="2008-10" class="refDate">October 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5307">https://www.rfc-editor.org/info/rfc5307</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5308">[RFC5308]</dt>
        <dd>
<span class="refAuthor">Hopps, C.</span>, <span class="refTitle">"Routing IPv6 with IS-IS"</span>, <span class="seriesInfo">RFC 5308</span>, <span class="seriesInfo">DOI 10.17487/RFC5308</span>, <time datetime="2008-10" class="refDate">October 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5308">https://www.rfc-editor.org/info/rfc5308</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5443">[RFC5443]</dt>
        <dd>
<span class="refAuthor">Jork, M.</span>, <span class="refAuthor">Atlas, A.</span>, and <span class="refAuthor">L. Fang</span>, <span class="refTitle">"LDP IGP Synchronization"</span>, <span class="seriesInfo">RFC 5443</span>, <span class="seriesInfo">DOI 10.17487/RFC5443</span>, <time datetime="2009-03" class="refDate">March 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5443">https://www.rfc-editor.org/info/rfc5443</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5880">[RFC5880]</dt>
        <dd>
<span class="refAuthor">Katz, D.</span> and <span class="refAuthor">D. Ward</span>, <span class="refTitle">"Bidirectional Forwarding Detection (BFD)"</span>, <span class="seriesInfo">RFC 5880</span>, <span class="seriesInfo">DOI 10.17487/RFC5880</span>, <time datetime="2010-06" class="refDate">June 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5880">https://www.rfc-editor.org/info/rfc5880</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5881">[RFC5881]</dt>
        <dd>
<span class="refAuthor">Katz, D.</span> and <span class="refAuthor">D. Ward</span>, <span class="refTitle">"Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop)"</span>, <span class="seriesInfo">RFC 5881</span>, <span class="seriesInfo">DOI 10.17487/RFC5881</span>, <time datetime="2010-06" class="refDate">June 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5881">https://www.rfc-editor.org/info/rfc5881</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6020">[RFC6020]</dt>
        <dd>
<span class="refAuthor">Bjorklund, M., Ed.</span>, <span class="refTitle">"YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)"</span>, <span class="seriesInfo">RFC 6020</span>, <span class="seriesInfo">DOI 10.17487/RFC6020</span>, <time datetime="2010-10" class="refDate">October 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6020">https://www.rfc-editor.org/info/rfc6020</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6119">[RFC6119]</dt>
        <dd>
<span class="refAuthor">Harrison, J.</span>, <span class="refAuthor">Berger, J.</span>, and <span class="refAuthor">M. Bartlett</span>, <span class="refTitle">"IPv6 Traffic Engineering in IS-IS"</span>, <span class="seriesInfo">RFC 6119</span>, <span class="seriesInfo">DOI 10.17487/RFC6119</span>, <time datetime="2011-02" class="refDate">February 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6119">https://www.rfc-editor.org/info/rfc6119</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6232">[RFC6232]</dt>
        <dd>
<span class="refAuthor">Wei, F.</span>, <span class="refAuthor">Qin, Y.</span>, <span class="refAuthor">Li, Z.</span>, <span class="refAuthor">Li, T.</span>, and <span class="refAuthor">J. Dong</span>, <span class="refTitle">"Purge Originator Identification TLV for IS-IS"</span>, <span class="seriesInfo">RFC 6232</span>, <span class="seriesInfo">DOI 10.17487/RFC6232</span>, <time datetime="2011-05" class="refDate">May 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6232">https://www.rfc-editor.org/info/rfc6232</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6241">[RFC6241]</dt>
        <dd>
<span class="refAuthor">Enns, R., Ed.</span>, <span class="refAuthor">Bjorklund, M., Ed.</span>, <span class="refAuthor">Schoenwaelder, J., Ed.</span>, and <span class="refAuthor">A. Bierman, Ed.</span>, <span class="refTitle">"Network Configuration Protocol (NETCONF)"</span>, <span class="seriesInfo">RFC 6241</span>, <span class="seriesInfo">DOI 10.17487/RFC6241</span>, <time datetime="2011-06" class="refDate">June 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6241">https://www.rfc-editor.org/info/rfc6241</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6242">[RFC6242]</dt>
        <dd>
<span class="refAuthor">Wasserman, M.</span>, <span class="refTitle">"Using the NETCONF Protocol over Secure Shell (SSH)"</span>, <span class="seriesInfo">RFC 6242</span>, <span class="seriesInfo">DOI 10.17487/RFC6242</span>, <time datetime="2011-06" class="refDate">June 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6242">https://www.rfc-editor.org/info/rfc6242</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6991">[RFC6991]</dt>
        <dd>
<span class="refAuthor">Schoenwaelder, J., Ed.</span>, <span class="refTitle">"Common YANG Data Types"</span>, <span class="seriesInfo">RFC 6991</span>, <span class="seriesInfo">DOI 10.17487/RFC6991</span>, <time datetime="2013-07" class="refDate">July 2013</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6991">https://www.rfc-editor.org/info/rfc6991</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7490">[RFC7490]</dt>
        <dd>
<span class="refAuthor">Bryant, S.</span>, <span class="refAuthor">Filsfils, C.</span>, <span class="refAuthor">Previdi, S.</span>, <span class="refAuthor">Shand, M.</span>, and <span class="refAuthor">N. So</span>, <span class="refTitle">"Remote Loop-Free Alternate (LFA) Fast Reroute (FRR)"</span>, <span class="seriesInfo">RFC 7490</span>, <span class="seriesInfo">DOI 10.17487/RFC7490</span>, <time datetime="2015-04" class="refDate">April 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7490">https://www.rfc-editor.org/info/rfc7490</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7794">[RFC7794]</dt>
        <dd>
<span class="refAuthor">Ginsberg, L., Ed.</span>, <span class="refAuthor">Decraene, B.</span>, <span class="refAuthor">Previdi, S.</span>, <span class="refAuthor">Xu, X.</span>, and <span class="refAuthor">U. Chunduri</span>, <span class="refTitle">"IS-IS Prefix Attributes for Extended IPv4 and IPv6 Reachability"</span>, <span class="seriesInfo">RFC 7794</span>, <span class="seriesInfo">DOI 10.17487/RFC7794</span>, <time datetime="2016-03" class="refDate">March 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7794">https://www.rfc-editor.org/info/rfc7794</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7917">[RFC7917]</dt>
        <dd>
<span class="refAuthor">Sarkar, P., Ed.</span>, <span class="refAuthor">Gredler, H.</span>, <span class="refAuthor">Hegde, S.</span>, <span class="refAuthor">Litkowski, S.</span>, and <span class="refAuthor">B. Decraene</span>, <span class="refTitle">"Advertising Node Administrative Tags in IS-IS"</span>, <span class="seriesInfo">RFC 7917</span>, <span class="seriesInfo">DOI 10.17487/RFC7917</span>, <time datetime="2016-07" class="refDate">July 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7917">https://www.rfc-editor.org/info/rfc7917</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7950">[RFC7950]</dt>
        <dd>
<span class="refAuthor">Bjorklund, M., Ed.</span>, <span class="refTitle">"The YANG 1.1 Data Modeling Language"</span>, <span class="seriesInfo">RFC 7950</span>, <span class="seriesInfo">DOI 10.17487/RFC7950</span>, <time datetime="2016-08" class="refDate">August 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7950">https://www.rfc-editor.org/info/rfc7950</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7981">[RFC7981]</dt>
        <dd>
<span class="refAuthor">Ginsberg, L.</span>, <span class="refAuthor">Previdi, S.</span>, and <span class="refAuthor">M. Chen</span>, <span class="refTitle">"IS-IS Extensions for Advertising Router Information"</span>, <span class="seriesInfo">RFC 7981</span>, <span class="seriesInfo">DOI 10.17487/RFC7981</span>, <time datetime="2016-10" class="refDate">October 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7981">https://www.rfc-editor.org/info/rfc7981</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8040">[RFC8040]</dt>
        <dd>
<span class="refAuthor">Bierman, A.</span>, <span class="refAuthor">Bjorklund, M.</span>, and <span class="refAuthor">K. Watsen</span>, <span class="refTitle">"RESTCONF Protocol"</span>, <span class="seriesInfo">RFC 8040</span>, <span class="seriesInfo">DOI 10.17487/RFC8040</span>, <time datetime="2017-01" class="refDate">January 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8040">https://www.rfc-editor.org/info/rfc8040</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8174">[RFC8174]</dt>
        <dd>
<span class="refAuthor">Leiba, B.</span>, <span class="refTitle">"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 8174</span>, <span class="seriesInfo">DOI 10.17487/RFC8174</span>, <time datetime="2017-05" class="refDate">May 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8177">[RFC8177]</dt>
        <dd>
<span class="refAuthor">Lindem, A., Ed.</span>, <span class="refAuthor">Qu, Y.</span>, <span class="refAuthor">Yeung, D.</span>, <span class="refAuthor">Chen, I.</span>, and <span class="refAuthor">J. Zhang</span>, <span class="refTitle">"YANG Data Model for Key Chains"</span>, <span class="seriesInfo">RFC 8177</span>, <span class="seriesInfo">DOI 10.17487/RFC8177</span>, <time datetime="2017-06" class="refDate">June 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8177">https://www.rfc-editor.org/info/rfc8177</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8294">[RFC8294]</dt>
        <dd>
<span class="refAuthor">Liu, X.</span>, <span class="refAuthor">Qu, Y.</span>, <span class="refAuthor">Lindem, A.</span>, <span class="refAuthor">Hopps, C.</span>, and <span class="refAuthor">L. Berger</span>, <span class="refTitle">"Common YANG Data Types for the Routing Area"</span>, <span class="seriesInfo">RFC 8294</span>, <span class="seriesInfo">DOI 10.17487/RFC8294</span>, <time datetime="2017-12" class="refDate">December 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8294">https://www.rfc-editor.org/info/rfc8294</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8341">[RFC8341]</dt>
        <dd>
<span class="refAuthor">Bierman, A.</span> and <span class="refAuthor">M. Bjorklund</span>, <span class="refTitle">"Network Configuration Access Control Model"</span>, <span class="seriesInfo">STD 91</span>, <span class="seriesInfo">RFC 8341</span>, <span class="seriesInfo">DOI 10.17487/RFC8341</span>, <time datetime="2018-03" class="refDate">March 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8341">https://www.rfc-editor.org/info/rfc8341</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8342">[RFC8342]</dt>
        <dd>
<span class="refAuthor">Bjorklund, M.</span>, <span class="refAuthor">Schoenwaelder, J.</span>, <span class="refAuthor">Shafer, P.</span>, <span class="refAuthor">Watsen, K.</span>, and <span class="refAuthor">R. Wilton</span>, <span class="refTitle">"Network Management Datastore Architecture (NMDA)"</span>, <span class="seriesInfo">RFC 8342</span>, <span class="seriesInfo">DOI 10.17487/RFC8342</span>, <time datetime="2018-03" class="refDate">March 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8342">https://www.rfc-editor.org/info/rfc8342</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8343">[RFC8343]</dt>
        <dd>
<span class="refAuthor">Bjorklund, M.</span>, <span class="refTitle">"A YANG Data Model for Interface Management"</span>, <span class="seriesInfo">RFC 8343</span>, <span class="seriesInfo">DOI 10.17487/RFC8343</span>, <time datetime="2018-03" class="refDate">March 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8343">https://www.rfc-editor.org/info/rfc8343</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8349">[RFC8349]</dt>
        <dd>
<span class="refAuthor">Lhotka, L.</span>, <span class="refAuthor">Lindem, A.</span>, and <span class="refAuthor">Y. Qu</span>, <span class="refTitle">"A YANG Data Model for Routing Management (NMDA Version)"</span>, <span class="seriesInfo">RFC 8349</span>, <span class="seriesInfo">DOI 10.17487/RFC8349</span>, <time datetime="2018-03" class="refDate">March 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8349">https://www.rfc-editor.org/info/rfc8349</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8405">[RFC8405]</dt>
        <dd>
<span class="refAuthor">Decraene, B.</span>, <span class="refAuthor">Litkowski, S.</span>, <span class="refAuthor">Gredler, H.</span>, <span class="refAuthor">Lindem, A.</span>, <span class="refAuthor">Francois, P.</span>, and <span class="refAuthor">C. Bowers</span>, <span class="refTitle">"Shortest Path First (SPF) Back-Off Delay Algorithm for Link-State IGPs"</span>, <span class="seriesInfo">RFC 8405</span>, <span class="seriesInfo">DOI 10.17487/RFC8405</span>, <time datetime="2018-06" class="refDate">June 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8405">https://www.rfc-editor.org/info/rfc8405</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8446">[RFC8446]</dt>
        <dd>
<span class="refAuthor">Rescorla, E.</span>, <span class="refTitle">"The Transport Layer Security (TLS) Protocol Version 1.3"</span>, <span class="seriesInfo">RFC 8446</span>, <span class="seriesInfo">DOI 10.17487/RFC8446</span>, <time datetime="2018-08" class="refDate">August 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8446">https://www.rfc-editor.org/info/rfc8446</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8570">[RFC8570]</dt>
        <dd>
<span class="refAuthor">Ginsberg, L., Ed.</span>, <span class="refAuthor">Previdi, S., Ed.</span>, <span class="refAuthor">Giacalone, S.</span>, <span class="refAuthor">Ward, D.</span>, <span class="refAuthor">Drake, J.</span>, and <span class="refAuthor">Q. Wu</span>, <span class="refTitle">"IS-IS Traffic Engineering (TE) Metric Extensions"</span>, <span class="seriesInfo">RFC 8570</span>, <span class="seriesInfo">DOI 10.17487/RFC8570</span>, <time datetime="2019-03" class="refDate">March 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8570">https://www.rfc-editor.org/info/rfc8570</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8706">[RFC8706]</dt>
        <dd>
<span class="refAuthor">Ginsberg, L.</span> and <span class="refAuthor">P. Wells</span>, <span class="refTitle">"Restart Signaling for IS-IS"</span>, <span class="seriesInfo">RFC 8706</span>, <span class="seriesInfo">DOI 10.17487/RFC8706</span>, <time datetime="2020-02" class="refDate">February 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8706">https://www.rfc-editor.org/info/rfc8706</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC9314">[RFC9314]</dt>
        <dd>
<span class="refAuthor">Jethanandani, M., Ed.</span>, <span class="refAuthor">Rahman, R., Ed.</span>, <span class="refAuthor">Zheng, L., Ed.</span>, <span class="refAuthor">Pallagatti, S.</span>, and <span class="refAuthor">G. Mirsky</span>, <span class="refTitle">"YANG Data Model for Bidirectional Forwarding Detection (BFD)"</span>, <span class="seriesInfo">RFC 9314</span>, <span class="seriesInfo">DOI 10.17487/RFC9314</span>, <time datetime="2022-09" class="refDate">September 2022</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc9314">https://www.rfc-editor.org/info/rfc9314</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="W3C.REC-xml-20081126">[W3C.REC-xml-20081126]</dt>
      <dd>
<span class="refAuthor">Bray, T.</span>, <span class="refAuthor">Paoli, J.</span>, <span class="refAuthor">Sperberg-McQueen, M.</span>, <span class="refAuthor">Maler, E.</span>, and <span class="refAuthor">F. Yergeau</span>, <span class="refTitle">"Extensible Markup Language (XML) 1.0 (Fifth Edition)"</span>, <span class="seriesInfo">World Wide Web Consortium Recommendation REC-xml-20081126</span>, <time datetime="2008-11" class="refDate">November 2008</time>, <span>&lt;<a href="https://www.w3.org/TR/2008/REC-xml-20081126">https://www.w3.org/TR/2008/REC-xml-20081126</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
<section id="section-9.2">
        <h3 id="name-informative-references">
<a href="#section-9.2" class="section-number selfRef">9.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
        </h3>
<dl class="references">
<dt id="RFC7812">[RFC7812]</dt>
        <dd>
<span class="refAuthor">Atlas, A.</span>, <span class="refAuthor">Bowers, C.</span>, and <span class="refAuthor">G. Enyedi</span>, <span class="refTitle">"An Architecture for IP/LDP Fast Reroute Using Maximally Redundant Trees (MRT-FRR)"</span>, <span class="seriesInfo">RFC 7812</span>, <span class="seriesInfo">DOI 10.17487/RFC7812</span>, <time datetime="2016-06" class="refDate">June 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7812">https://www.rfc-editor.org/info/rfc7812</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8340">[RFC8340]</dt>
        <dd>
<span class="refAuthor">Bjorklund, M.</span> and <span class="refAuthor">L. Berger, Ed.</span>, <span class="refTitle">"YANG Tree Diagrams"</span>, <span class="seriesInfo">BCP 215</span>, <span class="seriesInfo">RFC 8340</span>, <span class="seriesInfo">DOI 10.17487/RFC8340</span>, <time datetime="2018-03" class="refDate">March 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8340">https://www.rfc-editor.org/info/rfc8340</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8792">[RFC8792]</dt>
        <dd>
<span class="refAuthor">Watsen, K.</span>, <span class="refAuthor">Auerswald, E.</span>, <span class="refAuthor">Farrel, A.</span>, and <span class="refAuthor">Q. Wu</span>, <span class="refTitle">"Handling Long Lines in Content of Internet-Drafts and RFCs"</span>, <span class="seriesInfo">RFC 8792</span>, <span class="seriesInfo">DOI 10.17487/RFC8792</span>, <time datetime="2020-06" class="refDate">June 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8792">https://www.rfc-editor.org/info/rfc8792</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="I-D.ietf-rtgwg-segment-routing-ti-lfa">[SR-TI-LFA]</dt>
      <dd>
<span class="refAuthor">Litkowski, S.</span>, <span class="refAuthor">Bashandy, A.</span>, <span class="refAuthor">Filsfils, C.</span>, <span class="refAuthor">Francois, P.</span>, <span class="refAuthor">Decraene, B.</span>, and <span class="refAuthor">D. Voyer</span>, <span class="refTitle">"Topology Independent Fast Reroute using Segment Routing"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-rtgwg-segment-routing-ti-lfa-08</span>, <time datetime="2022-01-21" class="refDate">21 January 2022</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-rtgwg-segment-routing-ti-lfa-08">https://datatracker.ietf.org/doc/html/draft-ietf-rtgwg-segment-routing-ti-lfa-08</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
</section>
<div id="rpc-example">
<section id="appendix-A">
      <h2 id="name-example-of-is-is-configurat">
<a href="#appendix-A" class="section-number selfRef">Appendix A. </a><a href="#name-example-of-is-is-configurat" class="section-name selfRef">Example of IS-IS Configuration in XML</a>
      </h2>
<p id="appendix-A-1">This appendix gives an example of the configuration of an IS-IS instance on a device.
          The example is written in XML <span>[<a href="#W3C.REC-xml-20081126" class="cite xref">W3C.REC-xml-20081126</a>]</span>.<a href="#appendix-A-1" class="pilcrow">¶</a></p>
<div id="appendix-A-2">
<pre class="breakable lang-xml sourcecode">
&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"&gt;
  &lt;routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing"&gt;
      &lt;name&gt;SLI&lt;/name&gt;
      &lt;router-id&gt;192.0.2.1&lt;/router-id&gt;
      &lt;control-plane-protocols&gt;
        &lt;control-plane-protocol&gt;
          &lt;name&gt;IS-IS-example&lt;/name&gt;
          &lt;description/&gt;
          &lt;type&gt;
            &lt;type xmlns:isis="urn:ietf:params:xml:ns:yang:ietf-isis"&gt;
            isis:isis
            &lt;/type&gt;
          &lt;/type&gt;
          &lt;isis xmlns="urn:ietf:params:xml:ns:yang:ietf-isis"&gt;
              &lt;enabled&gt;true&lt;/enabled&gt;
              &lt;level-type&gt;level-2&lt;/level-type&gt;
              &lt;system-id&gt;87FC.FCDF.4432&lt;/system-id&gt;
              &lt;area-address&gt;49.0001&lt;/area-address&gt;
              &lt;mpls&gt;
                &lt;te-rid&gt;
                  &lt;ipv4-router-id&gt;192.0.2.1&lt;/ipv4-router-id&gt;
                &lt;/te-rid&gt;
              &lt;/mpls&gt;
              &lt;lsp-lifetime&gt;65535&lt;/lsp-lifetime&gt;
              &lt;lsp-refresh&gt;65000&lt;/lsp-refresh&gt;
              &lt;metric-type&gt;
                &lt;value&gt;wide-only&lt;/value&gt;
              &lt;/metric-type&gt;
              &lt;default-metric&gt;
                &lt;value&gt;111111&lt;/value&gt;
              &lt;/default-metric&gt;
              &lt;address-families&gt;
                &lt;address-family-list&gt;
                  &lt;address-family&gt;ipv4&lt;/address-family&gt;
                  &lt;enabled&gt;true&lt;/enabled&gt;
                &lt;/address-family-list&gt;
                &lt;address-family-list&gt;
                  &lt;address-family&gt;ipv6&lt;/address-family&gt;
                  &lt;enabled&gt;true&lt;/enabled&gt;
                &lt;/address-family-list&gt;
              &lt;/address-families&gt;
              &lt;interfaces&gt;
                &lt;interface&gt;
                  &lt;name&gt;Loopback0&lt;/name&gt;
                  &lt;tag&gt;200&lt;/tag&gt;
                  &lt;metric&gt;
                    &lt;value&gt;0&lt;/value&gt;
                  &lt;/metric&gt;
                  &lt;passive&gt;true&lt;/passive&gt;
                &lt;/interface&gt;
                &lt;interface&gt;
                  &lt;name&gt;Eth1&lt;/name&gt;
                  &lt;level-type&gt;level-2&lt;/level-type&gt;
                  &lt;interface-type&gt;point-to-point&lt;/interface-type&gt;
                  &lt;metric&gt;
                    &lt;value&gt;167890&lt;/value&gt;
                  &lt;/metric&gt;
                &lt;/interface&gt;
              &lt;/interfaces&gt;
          &lt;/isis&gt;
        &lt;/control-plane-protocol&gt;
      &lt;/control-plane-protocols&gt;
  &lt;/routing&gt;
  &lt;interfaces xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"&gt;
    &lt;interface&gt;
      &lt;name&gt;Loopback0&lt;/name&gt;
      &lt;description/&gt;
      &lt;type xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type"&gt;
      ianaift:softwareLoopback
      &lt;/type&gt;
      &lt;link-up-down-trap-enable&gt;enabled&lt;/link-up-down-trap-enable&gt;
      &lt;ipv4 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip"&gt;
        &lt;address&gt;
          &lt;ip&gt;192.0.2.1&lt;/ip&gt;
          &lt;prefix-length&gt;32&lt;/prefix-length&gt;
        &lt;/address&gt;
      &lt;/ipv4&gt;
      &lt;ipv6 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip"&gt;
        &lt;address&gt;
          &lt;ip&gt;2001:db8::1&lt;/ip&gt;
          &lt;prefix-length&gt;128&lt;/prefix-length&gt;
        &lt;/address&gt;
      &lt;/ipv6&gt;
    &lt;/interface&gt;
    &lt;interface&gt;
      &lt;name&gt;Eth1&lt;/name&gt;
      &lt;description/&gt;
      &lt;type xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type"&gt;
      ianaift:ethernetCsmacd
      &lt;/type&gt;
      &lt;link-up-down-trap-enable&gt;enabled&lt;/link-up-down-trap-enable&gt;
      &lt;ipv4 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip"&gt;
        &lt;address&gt;
          &lt;ip&gt;198.51.100.1&lt;/ip&gt;
          &lt;prefix-length&gt;30&lt;/prefix-length&gt;
        &lt;/address&gt;
      &lt;/ipv4&gt;
      &lt;ipv6 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip"&gt;
        &lt;address&gt;
          &lt;ip&gt;2001:db8:0:0:ff::1&lt;/ip&gt;
          &lt;prefix-length&gt;64&lt;/prefix-length&gt;
        &lt;/address&gt;
      &lt;/ipv6&gt;
    &lt;/interface&gt;
  &lt;/interfaces&gt;
&lt;/data&gt;
</pre><a href="#appendix-A-2" class="pilcrow">¶</a>
</div>
</section>
</div>
<div id="ack">
<section id="appendix-B">
      <h2 id="name-acknowledgments">
<a href="#name-acknowledgments" class="section-name selfRef">Acknowledgments</a>
      </h2>
<p id="appendix-B-1">The authors would like to thank <span class="contact-name">Tom Petch</span>,
      <span class="contact-name">Alvaro Retana</span>, <span class="contact-name">Stewart       Bryant</span>, <span class="contact-name">Barry Leiba</span>, <span class="contact-name">Benjamin Kaduk</span>, <span class="contact-name">Adam Roach</span>,
      and <span class="contact-name">Roman Danyliw</span> for their review and
      comments.<a href="#appendix-B-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="Contributors">
<section id="appendix-C">
      <h2 id="name-contributors">
<a href="#name-contributors" class="section-name selfRef">Contributors</a>
      </h2>
<p id="appendix-C-1">The authors would like to thank
         <span class="contact-name">Kiran Agrahara Sreenivasa</span>, <span class="contact-name">Dean Bogdanovic</span>, <span class="contact-name">Yingzhen Qu</span>,
         <span class="contact-name">Yi Yang</span>, and <span class="contact-name">Jeff Tantsura</span>
         for their major contributions to this document.<a href="#appendix-C-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="authors-addresses">
<section id="appendix-D">
      <h2 id="name-authors-addresses">
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
      </h2>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Stephane Litkowski (<span class="role">editor</span>)</span></div>
<div dir="auto" class="left"><span class="org">Cisco Systems</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:slitkows.ietf@gmail.com" class="email">slitkows.ietf@gmail.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Derek Yeung</span></div>
<div dir="auto" class="left"><span class="org">Arrcus, Inc.</span></div>
<div dir="auto" class="left"><span class="street-address">2077 Gateway Place, Suite 400</span></div>
<div dir="auto" class="left">
<span class="locality">San Jose</span>, <span class="region">CA</span> <span class="postal-code">95110</span>
</div>
<div dir="auto" class="left"><span class="country-name">United States of America</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:derek@arrcus.com" class="email">derek@arrcus.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Acee Lindem</span></div>
<div dir="auto" class="left"><span class="org">Cisco Systems</span></div>
<div dir="auto" class="left"><span class="street-address">301 Midenhall Way</span></div>
<div dir="auto" class="left">
<span class="locality">Cary</span>, <span class="region">NC</span> <span class="postal-code">27513</span>
</div>
<div dir="auto" class="left"><span class="country-name">United States of America</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:acee@cisco.com" class="email">acee@cisco.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Jeffrey Zhang</span></div>
<div dir="auto" class="left"><span class="org">Juniper Networks</span></div>
<div dir="auto" class="left"><span class="street-address">10 Technology Park Drive</span></div>
<div dir="auto" class="left">
<span class="locality">Westford</span>, <span class="region">MA</span> <span class="postal-code">01886</span>
</div>
<div dir="auto" class="left"><span class="country-name">United States of America</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:zzhang@juniper.net" class="email">zzhang@juniper.net</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Ladislav Lhotka</span></div>
<div dir="auto" class="left"><span class="org">CZ.NIC</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:ladislav.lhotka@nic.cz" class="email">ladislav.lhotka@nic.cz</a>
</div>
</address>
</section>
</div>
<script>const toc = document.getElementById("toc");
toc.querySelector("h2").addEventListener("click", e => {
  toc.classList.toggle("active");
});
toc.querySelector("nav").addEventListener("click", e => {
  toc.classList.remove("active");
});
</script>
</body>
</html>