draft-ietf-isis-yang-isis-cfg-41.txt   draft-ietf-isis-yang-isis-cfg-42.txt 
IS-IS Working Group S. Litkowski IS-IS Working Group S. Litkowski
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Standards Track D. Yeung Intended status: Standards Track D. Yeung
Expires: April 10, 2020 Arrcus, Inc Expires: April 17, 2020 Arrcus, Inc
A. Lindem A. Lindem
Cisco Systems Cisco Systems
J. Zhang J. Zhang
Juniper Networks Juniper Networks
L. Lhotka L. Lhotka
CZ.NIC CZ.NIC
October 08, 2019 October 15, 2019
YANG Data Model for IS-IS Protocol YANG Data Model for IS-IS Protocol
draft-ietf-isis-yang-isis-cfg-41 draft-ietf-isis-yang-isis-cfg-42
Abstract Abstract
This document defines a YANG data model that can be used to configure This document defines a YANG data model that can be used to configure
and manage the IS-IS protocol on network elements. and manage the IS-IS protocol on network elements.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
skipping to change at page 1, line 46 skipping to change at page 1, line 46
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 10, 2020. This Internet-Draft will expire on April 17, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 10, line 18 skipping to change at page 10, line 18
lsp-mtu, lsp-lifetime, lsp-refresh, default-metric, etc. lsp-mtu, lsp-lifetime, lsp-refresh, default-metric, etc.
2.2. Multi-topology Parameters 2.2. Multi-topology Parameters
The model supports multi-topology (MT) IS-IS as defined in [RFC5120]. The model supports multi-topology (MT) IS-IS as defined in [RFC5120].
The "topologies" container is used to enable support of the MT The "topologies" container is used to enable support of the MT
extensions. extensions.
The "name" used in the topology list should refer to an existing The "name" used in the topology list should refer to an existing
Routing Information Based (RIB) defined for the device [RFC8349]. Routing Information Base (RIB) defined for the device [RFC8349].
Some specific parameters can be defined on a per-topology basis, both Some specific parameters can be defined on a per-topology basis, both
at the global level and at the interface level: for example, an at the global level and at the interface level: for example, an
interface metric can be defined per topology. interface metric can be defined per topology.
Multiple address families (such as, IPv4 or IPv6) can also be enabled Multiple address families (such as, IPv4 or IPv6) can also be enabled
within the default topology. This can be achieved using the address- within the default topology. This can be achieved using the address-
families container (requiring the "nlpid-control" feature to be families container (requiring the "nlpid-control" feature to be
supported). supported).
skipping to change at page 23, line 33 skipping to change at page 23, line 33
6. IS-IS YANG Module 6. IS-IS YANG Module
The following RFCs, drafts and external standards are not referenced The following RFCs, drafts and external standards are not referenced
in the document text but are referenced in the ietf-isis.yang module: in the document text but are referenced in the ietf-isis.yang module:
[ISO-10589], [RFC1195], [RFC4090],[RFC5029], [RFC5130], [RFC5302], [ISO-10589], [RFC1195], [RFC4090],[RFC5029], [RFC5130], [RFC5302],
[RFC5305], [RFC5306], [RFC5307], [RFC5308], [RFC5880], [RFC5881], [RFC5305], [RFC5306], [RFC5307], [RFC5308], [RFC5880], [RFC5881],
[RFC6119], [RFC6232], [RFC7794], [RFC7981], [RFC8570], [RFC7917], [RFC6119], [RFC6232], [RFC7794], [RFC7981], [RFC8570], [RFC7917],
[RFC8405]. [RFC8405].
<CODE BEGINS> file "ietf-isis@2019-10-08.yang" <CODE BEGINS> file "ietf-isis@2019-10-15.yang"
module ietf-isis { module ietf-isis {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-isis"; namespace "urn:ietf:params:xml:ns:yang:ietf-isis";
prefix isis; prefix isis;
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
reference "RFC 8349 - A YANG Data Model for Routing reference "RFC 8349 - A YANG Data Model for Routing
Management (NMDA Version)"; Management (NMDA Version)";
skipping to change at page 25, line 46 skipping to change at page 25, line 46
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
'MAY', and 'OPTIONAL' in this document are to be interpreted as 'MAY', and 'OPTIONAL' in this document are to be interpreted as
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here. they appear in all capitals, as shown here.
This version of this YANG module is part of RFC XXXX; This version of this YANG module is part of RFC XXXX;
see the RFC itself for full legal notices."; see the RFC itself for full legal notices.";
revision 2019-10-08 { revision 2019-10-15 {
description description
"Initial revision."; "Initial revision.";
reference "RFC XXXX"; reference "RFC XXXX";
} }
/* Identities */ /* Identities */
identity isis { identity isis {
base rt:routing-protocol; base rt:routing-protocol;
description "Identity for the IS-IS routing protocol."; description "Identity for the IS-IS routing protocol.";
} }
skipping to change at page 77, line 17 skipping to change at page 77, line 17
leaf ip-prefix { leaf ip-prefix {
type inet:ipv4-address; type inet:ipv4-address;
description "IPv4 prefix address"; description "IPv4 prefix address";
} }
leaf prefix-len { leaf prefix-len {
type uint8; type uint8;
description "IPv4 prefix length (in bits)"; description "IPv4 prefix length (in bits)";
} }
leaf i-e { leaf i-e {
type boolean; type boolean;
description "Internal or External (I/E) Metric bit value. description
Set to false to indicate an internal metric."; "Internal or External (I/E) Metric bit value.
Set to 'false' to indicate an internal metric.";
} }
container default-metric { container default-metric {
leaf metric { leaf metric {
type std-metric; type std-metric;
description "Default IS-IS metric for IPv4 prefix"; description "Default IS-IS metric for IPv4 prefix";
} }
description "IS-IS default metric container."; description "IS-IS default metric container.";
} }
container delay-metric { container delay-metric {
leaf metric { leaf metric {
skipping to change at page 86, line 43 skipping to change at page 86, line 45
key id; key id;
leaf id { leaf id {
type uint32; type uint32;
description "Unique identifier of an instance of a description "Unique identifier of an instance of a
particular neighbor."; particular neighbor.";
} }
leaf i-e { leaf i-e {
type boolean; type boolean;
description description
"Internal or External (I/E) Metric bit value"; "Internal or External (I/E) Metric bit value.
Set to 'false' to indicate an internal metric.";
} }
container default-metric { container default-metric {
leaf metric { leaf metric {
type std-metric; type std-metric;
description "IS-IS default metric value"; description "IS-IS default metric value";
} }
description "IS-IS default metric container"; description "IS-IS default metric container";
} }
container delay-metric { container delay-metric {
leaf metric { leaf metric {
type std-metric; type std-metric;
description "IS-IS delay metric value"; description "IS-IS delay metric value";
} }
leaf supported { leaf supported {
type boolean; type boolean;
 End of changes. 10 change blocks. 
10 lines changed or deleted 13 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/