draft-ietf-i2rs-yang-l3-topology-00.txt   draft-ietf-i2rs-yang-l3-topology-01.txt 
Network Working Group A. Clemm Network Working Group A. Clemm
Internet-Draft J. Medved Internet-Draft J. Medved
Intended status: Standards Track Cisco Intended status: Standards Track Cisco
Expires: December 10, 2015 R. Varga Expires: June 13, 2016 R. Varga
T. Tkacik T. Tkacik
Pantheon Technologies SRO Pantheon Technologies SRO
X. Liu X. Liu
Ericsson Ericsson
I. Bryskin I. Bryskin
Huawei
A. Guo A. Guo
Adva Optical Adva Optical
H. Ananthakrishnan H. Ananthakrishnan
Packet Design Packet Design
N. Bahadur N. Bahadur
Bracket Computing Bracket Computing
V. Beeram V. Beeram
Juniper Networks Juniper Networks
June 8, 2015 December 11, 2015
A YANG Data Model for Layer 3 Topologies A YANG Data Model for Layer 3 Topologies
draft-ietf-i2rs-yang-l3-topology-00.txt draft-ietf-i2rs-yang-l3-topology-01.txt
Abstract Abstract
This document defines a YANG data model for layer 3 network This document defines a YANG data model for layer 3 network
topologies. topologies.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 45 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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 December 10, 2015. This Internet-Draft will expire on June 13, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 2, line 42 skipping to change at page 2, line 42
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Definitions and Acronyms . . . . . . . . . . . . . . . . . . 4 2. Definitions and Acronyms . . . . . . . . . . . . . . . . . . 4
3. Model overview . . . . . . . . . . . . . . . . . . . . . . . 5 3. Model overview . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Model structure . . . . . . . . . . . . . . . . . . . . . 5 3.1. Model structure . . . . . . . . . . . . . . . . . . . . . 5
3.2. Layer 3 Unicast - IGP . . . . . . . . . . . . . . . . . . 6 3.2. Layer 3 Unicast - IGP . . . . . . . . . . . . . . . . . . 6
3.3. OSPF Topology . . . . . . . . . . . . . . . . . . . . . . 7 3.3. OSPF Topology . . . . . . . . . . . . . . . . . . . . . . 7
3.4. IS-IS Topology . . . . . . . . . . . . . . . . . . . . . 9 3.4. IS-IS Topology . . . . . . . . . . . . . . . . . . . . . 9
4. Layer 3 Unicast IGP Topology YANG Module . . . . . . . . . . 10 4. Layer 3 Unicast IGP Topology YANG Module . . . . . . . . . . 10
5. OSPF Topology YANG Module . . . . . . . . . . . . . . . . . . 17 5. OSPF Topology YANG Module . . . . . . . . . . . . . . . . . . 19
6. ISIS Topology YANG Module . . . . . . . . . . . . . . . . . . 22 6. ISIS Topology YANG Module . . . . . . . . . . . . . . . . . . 26
7. Security Considerations . . . . . . . . . . . . . . . . . . . 25 7. Security Considerations . . . . . . . . . . . . . . . . . . . 31
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 25 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 31
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 26 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 32
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 26 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 32
10.1. Normative References . . . . . . . . . . . . . . . . . . 26 10.1. Normative References . . . . . . . . . . . . . . . . . . 32
10.2. Informative References . . . . . . . . . . . . . . . . . 27 10.2. Informative References . . . . . . . . . . . . . . . . . 33
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33
1. Introduction 1. Introduction
This document introduces a YANG [RFC6020] [RFC6021] data model for This document introduces a YANG [RFC6020] [RFC6991]
Layer 3 network topologies. The model allows an application to have [I-D.draft-ietf-netmod-rfc6020bis-09] data model for Layer 3 network
a holistic view of the topology of a Layer 3 network, all contained topologies. The model allows an application to have a holistic view
in a single conceptual YANG datastore. The data model builds on top of the topology of a Layer 3 network, all contained in a single
of, and augments, the data model for network topologies defined in conceptual YANG datastore. The data model builds on top of, and
augments, the data model for network topologies defined in
[I-D.draft-ietf-i2rs-yang-network-topo]. An earlier revision of that [I-D.draft-ietf-i2rs-yang-network-topo]. An earlier revision of that
Internet Draft contained not just the general model for network Internet Draft contained not just the general model for network
topologies, but also the model for layer 3 network topologies that is topologies, but also the model for layer 3 network topologies that is
being specified here. However, we decided to "split" the earlier being specified here. However, we decided to "split" the earlier
draft to separate the truly general aspects of a topology data model, draft to separate the truly general aspects of a topology data model,
which apply to any type of topology, from the application of this which apply to any type of topology, from the application of this
model to a particular domain, here: a Layer 3 network. model to a particular domain, here: a Layer 3 network.
Specific topology types that are covered in this document include Specific topology types that are covered in this document include
Layer 3 Unicast IGP, IS-IS [RFC1195], and OSPF [RFC2178]. In Layer 3 Unicast IGP, IS-IS [RFC1195], and OSPF [RFC2178]. In
skipping to change at page 3, line 42 skipping to change at page 3, line 43
the network topology with that of the network elements that it the network topology with that of the network elements that it
controls. Alternatively, nodes within the network could propagate controls. Alternatively, nodes within the network could propagate
this understanding to compare and reconcile this understanding either this understanding to compare and reconcile this understanding either
amongst themselves or with help of a controller. Beyond the network amongst themselves or with help of a controller. Beyond the network
element itself, a network controller might even use the data model to element itself, a network controller might even use the data model to
represent its view of the topology that it controls and expose it to represent its view of the topology that it controls and expose it to
applications north of itself. applications north of itself.
There are several reasons to choose YANG to define the data model. There are several reasons to choose YANG to define the data model.
Data defined using YANG can be exposed by a server to client Data defined using YANG can be exposed by a server to client
applications and controllers via Netconf [RFC6241] or via a ReST applications and controllers via Netconf [RFC6241] or via a ReST-like
Interface [I-D.draft-ietf-netconf-restconf] Interface [I-D.draft-ietf-netconf-restconf]
[I-D.draft-ietf-netmod-yang-json]. The fact that it can be used with [I-D.draft-ietf-netmod-yang-json]. The fact that it can be used with
different protocols and interfaces provides for a degree of "future- different protocols and interfaces provides for a degree of "future-
proofing" of model implementations. Also, YANG can serve as the proofing" of model implementations. Also, YANG can serve as the
basis for model-driven toolchains, such as used in the Open Daylight basis for model-driven toolchains, such as used in the Open Daylight
project. project.
The data model is defined in several YANG modules: The data model is defined in several YANG modules:
o Module "l3-unicast-igp-topology" defines a model for Layer 3 o Module "ietf-l3-unicast-igp-topology" defines a model for Layer 3
Unicast IGP topologies. To do so, it augments general network Unicast IGP topologies. To do so, it augments general network
topology model defined in [I-D.draft-ietf-i2rs-yang-network-topo] topology model defined in [I-D.draft-ietf-i2rs-yang-network-topo]
with information specific to Layer 3 Unicast IGP. In doing so, it with information specific to Layer 3 Unicast IGP. In doing so, it
also illustrates the extension patterns associated with extending also illustrates the extension patterns associated with extending
respectively augmenting the general topology model to meet the respectively augmenting the general topology model to meet the
needs of a specific topology. needs of a specific topology.
o Module "ospf-topology" defines a topology model for OSPF, building o Module "ietf-ospf-topology" defines a topology model for OSPF,
on and extending the Layer 3 Unicast IGP topology model. It building on and extending the Layer 3 Unicast IGP topology model.
serves as an example of how the general topology model can be It serves as an example of how the general topology model can be
refined across multiple levels. refined across multiple levels.
o Module "isis-topology" defines a topology model for IS-IS, again o Module "ietf-isis-topology" defines a topology model for IS-IS,
building on and extending the Layer 3 Unicast IGP topology model. again building on and extending the Layer 3 Unicast IGP topology
model.
Information that is kept in the Traffic Engineering Database (TED) is Information that is kept in the Traffic Engineering Database (TED) is
specified in a separate model and outside the scope of this specified in a separate model and outside the scope of this
specification. specification.
2. Definitions and Acronyms 2. Definitions and Acronyms
Datastore: A conceptual store of instantiated management information, Datastore: A conceptual store of instantiated management information,
with individual data items represented by data nodes which are with individual data items represented by data nodes which are
arranged in hierarchical manner. arranged in hierarchical manner.
skipping to change at page 5, line 43 skipping to change at page 5, line 43
^ ^ ^ ^
| | | |
| | | |
+--------^-----+ +-----^---------+ +--------^-----+ +-----^---------+
| ospf-topology| | isis-topology | | ospf-topology| | isis-topology |
+--------------+ +---------------+ +--------------+ +---------------+
Figure 1: Overall model structure Figure 1: Overall model structure
YANG modules ietf-network and ietf-network-topology collectively YANG modules ietf-network and ietf-network-topology collectively
define the basic network topology model. YANG module l3-unicast-igp- define the basic network topology model. YANG module ietf-l3-
topology augments those models with additional definitions needed to unicast-igp-topology augments those models with additional
represent Layer 3 Unicast IGP topologies. This module in turn is definitions needed to represent Layer 3 Unicast IGP topologies. This
augmented by YANG modules with additional definitions for OSPF and module in turn is augmented by YANG modules with additional
for IS-IS topologies, ospf-topology and isis-topology, respectively. definitions for OSPF and for IS-IS topologies, ietf-ospf-topology and
ietf-isis-topology, respectively.
3.2. Layer 3 Unicast - IGP 3.2. Layer 3 Unicast - IGP
The Layer 3 Unicast IGP topology model is defined by YANG module "l3- The Layer 3 Unicast IGP topology model is defined by YANG module
unicast-igp-topology". The model is depicted in the following "ietf-l3-unicast-igp-topology". The model is depicted in the
diagram. Brackets enclose list keys, "rw" means configuration, "ro" following diagram. Brackets enclose list keys, "rw" means
operational state data, "?" designates optional nodes, "*" designates configuration, "ro" operational state data, "?" designates optional
nodes that can have multiple instances. Parantheses enclose choice nodes, "*" designates nodes that can have multiple instances.
and case nodes. Notifications are not depicted. The prefix "nt:" Parantheses enclose choice and case nodes. Notifications are not
refers to the YANG module for network topology. depicted. The prefix "nt:" refers to the YANG module for network
topology.
module: l3-unicast-igp-topology module: ietf-l3-unicast-igp-topology
augment /nw:network/nw:network-types: augment /nw:networks/nw:network/nw:network-types:
+--rw l3-unicast-igp-topology! +--rw l3-unicast-igp-topology!
augment /nw:network: augment /nw:networks/nw:network:
+--rw igp-topology-attributes +--rw igp-topology-attributes
+--rw name? string +--rw name? string
+--rw flag* flag-type +--rw flag* flag-type
augment /nw:network/nw:node: augment /nw:networks/nw:network/nw:node:
+--rw igp-node-attributes +--rw igp-node-attributes
+--rw name? inet:domain-name +--rw name? inet:domain-name
+--rw flag* flag-type +--rw flag* flag-type
+--rw router-id* inet:ip-address +--rw router-id* inet:ip-address
+--rw prefix* [prefix] +--rw prefix* [prefix]
+--rw prefix inet:ip-prefix +--rw prefix inet:ip-prefix
+--rw metric? uint32 +--rw metric? uint32
+--rw flag* flag-type +--rw flag* flag-type
augment /nw:network/nt:link: augment /nw:networks/nw:network/nt:link:
+--rw igp-link-attributes +--rw igp-link-attributes
+--rw name? string +--rw name? string
+--rw flag* flag-type +--rw flag* flag-type
+--rw metric? uint32 +--rw metric? uint32
augment /nw:network/nw:node/nt:termination-point: augment /nw:networks/nw:network/nw:node/nt:termination-point:
+--rw igp-termination-point-attributes +--rw igp-termination-point-attributes
+--rw (termination-point-type)? +--rw (termination-point-type)?
+--:(ip) +--:(ip)
| +--rw ip-address* inet:ip-address | +--rw ip-address* inet:ip-address
+--:(unnumbered) +--:(unnumbered)
+--rw unnumbered-id? uint32 +--rw unnumbered-id? uint32
The module augments the original ietf-network and ietf-network- The module augments the original ietf-network and ietf-network-
topology modules as follows: topology modules as follows:
skipping to change at page 7, line 41 skipping to change at page 7, line 43
included. While this makes notifications larger in volume than they included. While this makes notifications larger in volume than they
would need to be, it avoids the need for subsequent retrieval of would need to be, it avoids the need for subsequent retrieval of
context information, which also might have changed in the meantime. context information, which also might have changed in the meantime.
3.3. OSPF Topology 3.3. OSPF Topology
OSPF is the next type of topology represented in the model. OSPF OSPF is the next type of topology represented in the model. OSPF
represents a particular type of Layer 3 Unicast IGP. Accordingly, represents a particular type of Layer 3 Unicast IGP. Accordingly,
this time the Layer 3 Unicast IGP topology model needs to be this time the Layer 3 Unicast IGP topology model needs to be
extended. The corresponding extensions are introduced in a separate extended. The corresponding extensions are introduced in a separate
YANG module "ospf-topology", whose structure is depicted in the YANG module "ietf-ospf-topology", whose structure is depicted in the
following diagram. For the most part, this module augments "l3- following diagram. For the most part, this module augments "ietf-l3-
unicast-igp-topology". Like before, brackets enclose list keys, "rw" unicast-igp-topology". Like before, brackets enclose list keys, "rw"
means configuration, "ro" operational state data, "?" designates means configuration, "ro" operational state data, "?" designates
optional nodes, "*" designates nodes that can have multiple optional nodes, "*" designates nodes that can have multiple
instances. Parantheses enclose choice and case nodes. Notifications instances. Parantheses enclose choice and case nodes. A "+" at the
respectively augmentations of notifications are not depicted. end of a line indicates a line break. Notifications respectively
augmentations of notifications are not depicted.
module: ospf-topology module: ietf-ospf-topology
augment /nw:network/nw:network-types/l3t:l3-unicast-igp-topology: augment /nw:networks/nw:network/nw:network-types/+
| l3t:l3-unicast-igp-topology:
+--rw ospf! +--rw ospf!
augment /nw:network/l3t:igp-topology-attributes: augment /nw:networks/nw:network/l3t:igp-topology-attributes:
+--rw ospf-topology-attributes +--rw ospf-topology-attributes
+--rw area-id? area-id +--rw area-id? area-id
augment /nw:network/nw:node/l3t:igp-node-attributes: augment /nw:networks/nw:network/nw:node/l3t:igp-node-attributes:
+--rw ospf-node-attributes +--rw ospf-node-attributes
+--rw (router-type)? +--rw (router-type)?
| +--:(abr) | +--:(abr)
| | +--rw abr? empty | | +--rw abr? empty
| +--:(asbr) | +--:(asbr)
| | +--rw asbr? empty | | +--rw asbr? empty
| +--:(internal) | +--:(internal)
| | +--rw internal? empty | | +--rw internal? empty
| +--:(pseudonode) | +--:(pseudonode)
| +--rw pseudonode? empty | +--rw pseudonode? empty
+--rw dr-interface-id? uint32 +--rw dr-interface-id? uint32
+--rw multi-topology-id* uint8 +--rw multi-topology-id* uint8
+--rw capabilities? bits +--rw capabilities? bits
augment /nw:network/nt:link/l3t:igp-link-attributes: augment /nw:networks/nw:network/nt:link/l3t:igp-link-attributes:
+--rw ospf-link-attributes +--rw ospf-link-attributes
+--rw multi-topology-id? uint8 +--rw multi-topology-id? uint8
augment /nw:network/nw:node/l3t:igp-node-attributes/l3t:prefix: augment /nw:networks/nw:network/nw:node/l3t:igp-node-attributes/+
| l3t:prefix:
+--rw ospf-prefix-attributes +--rw ospf-prefix-attributes
+--rw forwarding-address? inet:ipv4-address +--rw forwarding-address? inet:ipv4-address
The module augments "l3-unicast-igp-topology" as follows: The module augments "ietf-l3-unicast-igp-topology" as follows:
o A new topology type for an OSPF topology is introduced. o A new topology type for an OSPF topology is introduced.
o Additional topology attributes are defined in a new grouping which o Additional topology attributes are defined in a new grouping which
augments igp-topology-attributes of the l3-unicast-igp-topology augments igp-topology-attributes of the ietf-l3-unicast-igp-
module. The attributes include an OSPF area-id identifying the topology module. The attributes include an OSPF area-id
OSPF area. identifying the OSPF area.
o Additional data objects for nodes are introduced by augmenting the o Additional data objects for nodes are introduced by augmenting the
igp-node-attributes of the l3-unicast-igp-topology module. New igp-node-attributes of the l3-unicast-igp-topology module. New
objects include router-type, dr-interface-id for pseudonodes, list objects include router-type, dr-interface-id for pseudonodes, list
of multi-topology-ids, ospf node capabilities, and traffic of multi-topology-ids, ospf node capabilities, and traffic
engineering attributes. engineering attributes.
o Links are augmented with a multi-topology-id and traffic o Links are augmented with a multi-topology-id and traffic
engineering link attributes. engineering link attributes.
o Prefixes are augmented with OSPF specific forwarding address. o Prefixes are augmented with OSPF specific forwarding address.
In addition, the module extends IGP node, link and prefix In addition, the module extends IGP node, link and prefix
notifications with OSPF attributes. notifications with OSPF attributes.
3.4. IS-IS Topology 3.4. IS-IS Topology
IS-IS is another type of Layer 3 Unicast IGP. Like OSPF topology, IS-IS is another type of Layer 3 Unicast IGP. Like OSPF topology,
IS-IS topology is defined in a separate module, "isis-topology", IS-IS topology is defined in a separate module, "ietf-isis-topology",
which augments "l3-unicast-igp-topology". The structure is depicted which augments "ietf-l3-unicast-igp-topology". The structure is
in the following diagram. Like before, brackets enclose list keys, depicted in the following diagram. Like before, brackets enclose
"rw" means configuration, "ro" operational state data, "?" designates list keys, "rw" means configuration, "ro" operational state data, "?"
optional nodes, "*" designates nodes that can have multiple designates optional nodes, "*" designates nodes that can have
instances. Parantheses enclose choice and case nodes. Notifications multiple instances. Parantheses enclose choice and case nodes. A
are not depicted. "+" at the end of a line indicates a line break. Notifications are
not depicted.
module: isis-topology module: ietf-isis-topology
augment /nw:network/nw:network-types/l3t:l3-unicast-igp-topology: augment /nw:networks/nw:network/nw:network-types/+
| l3t:l3-unicast-igp-topology:
+--rw isis! +--rw isis!
augment /nw:network/l3t:igp-topology-attributes: augment /nw:networks/nw:network/l3t:igp-topology-attributes:
+--rw isis-topology-attributes +--rw isis-topology-attributes
+--rw net? iso-net-id +--rw net? iso-net-id
augment /nw:network/nw:node/l3t:igp-node-attributes: augment /nw:networks/nw:network/nw:node/l3t:igp-node-attributes:
+--rw isis-node-attributes +--rw isis-node-attributes
+--rw iso +--rw iso
| +--rw iso-system-id? iso-system-id | +--rw iso-system-id? iso-system-id
| +--rw iso-pseudonode-id? iso-pseudonode-id | +--rw iso-pseudonode-id? iso-pseudonode-id
+--rw net* iso-net-id +--rw net* iso-net-id
+--rw multi-topology-id* uint8 +--rw multi-topology-id* uint8
+--rw (router-type)? +--rw (router-type)?
+--:(level-2) +--:(level-2)
| +--rw level-2? empty | +--rw level-2? empty
+--:(level-1) +--:(level-1)
| +--rw level-1? empty | +--rw level-1? empty
+--:(level-1-2) +--:(level-1-2)
+--rw level-1-2? empty +--rw level-1-2? empty
augment /nw:network/nt:link/l3t:igp-link-attributes: augment /nw:networks/nw:network/nt:link/l3t:igp-link-attributes:
+--rw isis-link-attributes +--rw isis-link-attributes
+--rw multi-topology-id? uint8 +--rw multi-topology-id? uint8
The module augments the l3-unicast-igp-topology as follows: The module augments the ietf-l3-unicast-igp-topology as follows:
o A new topology type is introduced for isis. o A new topology type is introduced for isis.
o Additional topology attributes are introduced in a new grouping o Additional topology attributes are introduced in a new grouping
which augments "igp-topology-attributes" of the l3-unicast-igp- which augments "igp-topology-attributes" of the ietf-l3-unicast-
topology module. The attributes include an ISIS NET-id igp-topology module. The attributes include an ISIS NET-id
identifying the area. identifying the area.
o Additional data objects for nodes are introduced by augmenting o Additional data objects for nodes are introduced by augmenting
"igp-node-attributes" of the l3-unicast-igp-topology module. New "igp-node-attributes" of the ietf-l3-unicast-igp-topology module.
objects include router-type, iso-system-id to identify the router, New objects include router-type, iso-system-id to identify the
a list of multi-topology-id, a list of NET ids, and traffic router, a list of multi-topology-id, a list of NET ids, and
engineering attributes. traffic engineering attributes.
o Links are augmented with multi-topology-id and traffic engineering o Links are augmented with multi-topology-id and traffic engineering
link attributes. link attributes.
In addition, the module augments IGP nodes and links with ISIS In addition, the module augments IGP nodes and links with ISIS
attributes. attributes.
4. Layer 3 Unicast IGP Topology YANG Module 4. Layer 3 Unicast IGP Topology YANG Module
<CODE BEGINS> <CODE BEGINS> file "ietf-l3-unicast-igp-topology@2015-12-11.yang"
file "l3-unicast-igp-topology@2015-06-08.yang" module ietf-l3-unicast-igp-topology {
module l3-unicast-igp-topology { yang-version 1.1;
yang-version 1; namespace "urn:ietf:params:xml:ns:yang:ietf-l3-unicast-igp-topology";
namespace "urn:ietf:params:xml:ns:yang:l3-unicast-igp-topology"; prefix "l3t";
prefix "l3t"; import ietf-network {
import ietf-network { prefix "nw";
prefix "nw"; }
} import ietf-network-topology {
import ietf-network-topology { prefix "nt";
prefix "nt"; }
} import ietf-inet-types {
import ietf-inet-types { prefix "inet";
prefix "inet"; }
}
organization "TBD"; organization
contact "TBD"; "IETF I2RS (Interface to the Routing System) Working Group";
description contact
"This module defines a model for the layer 3 IGP topology."; "WG Web: <http://tools.ietf.org/wg/i2rs/>
WG List: <mailto:i2rs@ietf.org>
revision "2015-06-08" { WG Chair: Susan Hares
description "Initial revision"; <mailto:shares@ndzh.com>
reference "TBD";
}
typedef igp-event-type { WG Chair: Jeffrey Haas
type enumeration { <mailto:jhaas@pfrc.org>
enum "add" {
value 0;
description
"An IGP node or link or prefix or termination-point has
been added";
} Editor: Alexander Clemm
enum "remove" { <mailto:alex@cisco.com>
value 1;
description
"An IGP node or link or prefix or termination-point has
been removed";
}
enum "update" {
value 2;
description
"An IGP node or link or prefix or termination-point has
been updated";
}
}
description "IGP Event type for notifications";
} // igp-event-type
identity flag-identity { Editor: Jan Medved
description "Base type for flags"; <mailto:jmedved@cisco.com>
}
identity undefined-flag {
base "flag-identity";
description "Undefined flag";
}
typedef flag-type { Editor: Robert Varga
type identityref { <mailto:rovarga@cisco.com>
base "flag-identity";
}
description "Type for flags";
}
grouping network-ref { Editor: Tony Tkacik
description <mailto:ttkacik@cisco.com>
"Grouping for an absolute reference to a network topology
instance."; Editor: Xufeng Liu
leaf network-ref { <mailto:xufeng.liu@ericsson.com>
type leafref {
path "/nw:network/nw:network-id"; Editor: Igor Bryskin
} <mailto:Igor.Bryskin@huawei.com>
Editor: Aihua Guo
<mailto:aguo@advaoptical.com>
Editor: Nitin Bahadur
<mailto:nitin_bahadur@yahoo.com>
Editor: Hariharan Ananthakrishnan
<mailto:hari@packetdesign.com>
Editor: Vishnu Pavan Beeram
<mailto:vbeeram@juniper.net>";
description
"This module defines a model for Layer 3 Unicast IGP
topologies.
Copyright (c) 2015 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of
draft-ietf-i2rs-yang-network-topo-02;
see the RFC itself for full legal notices.
NOTE TO RFC EDITOR: Please replace above reference to
draft-ietf-i2rs-yang-network-topo-02 with RFC
number when published (i.e. RFC xxxx).";
revision "2015-12-11" {
description
"Initial revision.
NOTE TO RFC EDITOR: Please replace the following reference
to draft-ietf-i2rs-yang-l3-topology-01 with
RFC number when published (i.e. RFC xxxx).";
reference
"draft-ietf-i2rs-yang-l3-topology-01";
}
typedef igp-event-type {
type enumeration {
enum "add" {
value 0;
description description
"An absolute reference to a network topology instance."; "An IGP node or link or prefix or termination-point has
been added";
} }
} enum "remove" {
value 1;
grouping link-ref {
description
"Grouping for an absolute reference to a link instance.";
uses network-ref;
leaf link-ref {
type leafref {
path "/nw:network"
+"[nw:network-id = current()/../network-ref]"
+"/nt:link/nt:link-id";
}
description description
"An absolute reference to a link instance."; "An IGP node or link or prefix or termination-point has
been removed";
}
enum "update" {
value 2;
description
"An IGP node or link or prefix or termination-point has
been updated";
} }
} }
description "IGP Event type for notifications";
} // igp-event-type
grouping node-ref { identity flag-identity {
description "Base type for flags";
}
identity undefined-flag {
base "flag-identity";
description "Undefined flag";
}
typedef flag-type {
type identityref {
base "flag-identity";
}
description "Type for flags";
}
grouping network-ref {
description
"Grouping for an absolute reference to a network topology
instance.";
leaf network-ref {
type leafref {
path "/nw:networks/nw:network/nw:network-id";
}
description description
"Grouping for an absolute reference to a node instance."; "An absolute reference to a network topology instance.";
}
}
grouping link-ref {
description
"Grouping for an absolute reference to a link instance.";
uses network-ref; uses network-ref;
leaf node-ref { leaf link-ref {
type leafref { type leafref {
path "/nw:network" path "/nw:networks/nw:network"
+"[nw:network-id = current()/../network-ref]" +"[nw:network-id = current()/../network-ref]"
+"/nw:node/nw:node-id"; +"/nt:link/nt:link-id";
} }
description description
"An absolute reference to a node instance."; "An absolute reference to a link instance.";
}
}
grouping node-ref {
description
"Grouping for an absolute reference to a node instance.";
uses network-ref;
leaf node-ref {
type leafref {
path "/nw:networks/nw:network"
+"[nw:network-id = current()/../network-ref]"
+"/nw:node/nw:node-id";
} }
description
"An absolute reference to a node instance.";
} }
}
grouping tp-ref { grouping tp-ref {
description
"Grouping for an absolute reference to a termination point.";
uses node-ref;
leaf tp-ref {
type leafref {
path "/nw:networks/nw:network"
+"[nw:network-id = current()/../network-ref]"
+"/nw:node[nw:node-id = current()/../node-ref]"
+"/nt:termination-point/nt:tp-id";
}
description description
"Grouping for an absolute reference to a termination point."; "Grouping for an absolute reference to a termination point.";
uses node-ref;
leaf tp-ref {
type leafref {
path "/nw:network"
+"[nw:network-id = current()/../network-ref]"
+"/nw:node[nw:node-id = current()/../node-ref]"
+"/nt:termination-point/nt:tp-id";
}
description
"Grouping for an absolute reference to a termination point.";
}
} }
}
grouping igp-prefix-attributes { grouping igp-prefix-attributes {
description
"IGP prefix attributes";
leaf prefix {
type inet:ip-prefix;
description description
"IGP prefix attributes"; "IP prefix value";
leaf prefix { }
type inet:ip-prefix; leaf metric {
description "IP prefix value"; type uint32;
} description
leaf metric { "Prefix metric";
type uint32; }
description "Prefix metric"; leaf-list flag {
type flag-type;
description
"Prefix flags";
}
}
grouping l3-unicast-igp-topology-type {
description "Identify the topology type to be L3 unicast.";
container l3-unicast-igp-topology {
presence "indicates L3 Unicast IGP Topology";
description
"The presence of the container node indicates L3 Unicast
IGP Topology";
}
}
grouping igp-topology-attributes {
description "Topology scope attributes";
container igp-topology-attributes {
description "Containing topology attributes";
leaf name {
type string;
description
"Name of the topology";
} }
leaf-list flag { leaf-list flag {
type flag-type; type flag-type;
description "Prefix flags"; description
"Topology flags";
} }
} }
}
grouping l3-unicast-igp-topology-type { grouping igp-node-attributes {
description "Identify the topology type to be L3 unicast."; description "IGP node scope attributes";
container l3-unicast-igp-topology { container igp-node-attributes {
presence "indicates L3 Unicast IGP Topology"; description
"Containing node attributes";
leaf name {
type inet:domain-name;
description description
"The presence of the container node indicates L3 Unicast "Node name";
IGP Topology";
} }
} leaf-list flag {
type flag-type;
grouping igp-topology-attributes { description
description "Topology scope attributes"; "Node operational flags";
container igp-topology-attributes {
description "Containing topology attributes";
leaf name {
type string;
description "Name of the topology";
}
leaf-list flag {
type flag-type;
description "Topology flags";
}
} }
} leaf-list router-id {
type inet:ip-address;
grouping igp-node-attributes { description
description "IGP node scope attributes"; "Router-id for the node";
container igp-node-attributes { }
description "Containing node attributes"; list prefix {
leaf name { key "prefix";
type inet:domain-name; description
description "Node name"; "A list of prefixes along with their attributes";
} uses igp-prefix-attributes;
leaf-list flag {
type flag-type;
description "Node operational flags";
}
leaf-list router-id {
type inet:ip-address;
description "Router-id for the node";
}
list prefix {
key "prefix";
description
"A list of prefixes along with their attributes";
uses igp-prefix-attributes;
}
} }
} }
}
grouping igp-link-attributes { grouping igp-link-attributes {
description "IGP link scope attributes"; description
container igp-link-attributes { "IGP link scope attributes";
description "Containing link attributes"; container igp-link-attributes {
leaf name { description
type string; "Containing link attributes";
description "Link Name"; leaf name {
} type string;
leaf-list flag { description
type flag-type; "Link Name";
description "Link flags"; }
} leaf-list flag {
leaf metric { type flag-type;
type uint32 { description
range "0..16777215" { "Link flags";
description " }
"; leaf metric {
// OSPF/ISIS supports max 3 byte metric. type uint32 {
// Ideally we would like this restriction to be range "0..16777215" {
// defined in the derived models, however, description
// we are not allowed to augment a "must" statement. "This is a metric that can take a 3 byte metric,
} commonly used in OSPF/ISIS";
} }
description "Link Metric";
} }
description
"Link Metric";
} }
} // grouping igp-link-attributes }
}
grouping igp-termination-point-attributes { grouping igp-termination-point-attributes {
description "IGP termination point scope attributes"; description "IGP termination point scope attributes";
container igp-termination-point-attributes { container igp-termination-point-attributes {
description "Containing termination point attributes"; description
choice termination-point-type { "Containing termination point attributes";
description "Indicates the termination point type"; choice termination-point-type {
case ip { description
leaf-list ip-address { "Indicates the termination point type";
type inet:ip-address; case ip {
description "IPv4 or IPv6 address"; leaf-list ip-address {
} type inet:ip-address;
description
"IPv4 or IPv6 address";
} }
case unnumbered { }
leaf unnumbered-id { case unnumbered {
type uint32; leaf unnumbered-id {
description "Unnumbered interface identifier"; type uint32;
} description
"Unnumbered interface identifier";
} }
} }
} }
} // grouping igp-termination-point-attributes }
} // grouping igp-termination-point-attributes
augment "/nw:network/nw:network-types" { augment "/nw:networks/nw:network/nw:network-types" {
description
"Introduce new network type for L3 unicast IGP topology";
uses l3-unicast-igp-topology-type;
}
augment "/nw:networks/nw:network" {
when "nw:network-types/l3-unicast-igp-topology" {
description description
"Introduce new network type for L3 unicast IGP topology"; "Augmentation parameters apply only for networks with
uses l3-unicast-igp-topology-type; L3 unicast IGP topology";
} }
description
"Configuration parameters for L3 unicast IPG for the network
as a whole";
uses igp-topology-attributes;
}
augment "/nw:network" { augment "/nw:networks/nw:network/nw:node" {
when "nw:network-types/l3-unicast-igp-topology" { when "../nw:network-types/l3-unicast-igp-topology" {
description
"Augmentation parameters apply only for networks with
L3 unicast IGP topology";
}
description description
"Configuration parameters for L3 unicast IPG for the network "Augmentation parameters apply only for networks with
as a whole"; L3 unicast IGP topology";
uses igp-topology-attributes;
} }
description
"Configuration parameters for L3 unicast IPG at the node
level";
uses igp-node-attributes;
}
augment "/nw:network/nw:node" { augment "/nw:networks/nw:network/nt:link" {
when "../nw:network-types/l3-unicast-igp-topology" { when "../nw:network-types/l3-unicast-igp-topology" {
description
"Augmentation parameters apply only for networks with
L3 unicast IGP topology";
}
description description
"Configuration parameters for L3 unicast IPG at the node "Augmentation parameters apply only for networks with
level"; L3 unicast IGP topology";
uses igp-node-attributes;
} }
description
"Augment topology link configuration";
uses igp-link-attributes;
}
augment "/nw:network/nt:link" { augment "/nw:networks/nw:network/nw:node/"
when "../nw:network-types/l3-unicast-igp-topology" { +"nt:termination-point" {
description when "../../nw:network-types/l3-unicast-igp-topology" {
"Augmentation parameters apply only for networks with description
L3 unicast IGP topology"; "Augmentation parameters apply only for networks with
} L3 unicast IGP topology";
description "Augment topology link configuration";
uses igp-link-attributes;
} }
description "Augment topology termination point configuration";
uses igp-termination-point-attributes;
}
augment "/nw:network/nw:node/" notification igp-node-event {
+"nt:termination-point" { description
when "../../nw:network-types/l3-unicast-igp-topology" { "Notification event for IGP node";
description leaf igp-event-type {
"Augmentation parameters apply only for networks with type igp-event-type;
L3 unicast IGP topology"; description
} "Event type";
description "Augment topology termination point configuration";
uses igp-termination-point-attributes;
} }
uses node-ref;
uses l3-unicast-igp-topology-type;
uses igp-node-attributes;
}
notification igp-node-event { notification igp-link-event {
description "Notification event for IGP node"; description
leaf igp-event-type { "Notification event for IGP link";
type igp-event-type; leaf igp-event-type {
description "Event type"; type igp-event-type;
} description
uses node-ref; "Event type";
uses l3-unicast-igp-topology-type;
uses igp-node-attributes;
} }
uses link-ref;
uses l3-unicast-igp-topology-type;
uses igp-link-attributes;
}
notification igp-link-event { notification igp-prefix-event {
description "Notification event for IGP link"; description
leaf igp-event-type { "Notification event for IGP prefix";
type igp-event-type; leaf igp-event-type {
description "Event type"; type igp-event-type;
} description
uses link-ref; "Event type";
uses l3-unicast-igp-topology-type;
uses igp-link-attributes;
} }
uses node-ref;
notification igp-prefix-event { uses l3-unicast-igp-topology-type;
description "Notification event for IGP prefix"; container prefix {
leaf igp-event-type { description
type igp-event-type; "Containing IPG prefix attributes";
description "Event type"; uses igp-prefix-attributes;
}
uses node-ref;
uses l3-unicast-igp-topology-type;
container prefix {
description "Containing IPG prefix attributes";
uses igp-prefix-attributes;
}
} }
}
notification termination-point-event { notification termination-point-event {
description "Notification event for IGP termination point"; description
leaf igp-event-type { "Notification event for IGP termination point";
type igp-event-type; leaf igp-event-type {
description "Event type"; type igp-event-type;
} description
uses tp-ref; "Event type";
uses l3-unicast-igp-topology-type;
uses igp-termination-point-attributes;
} }
uses tp-ref;
uses l3-unicast-igp-topology-type;
uses igp-termination-point-attributes;
} }
}
<CODE ENDS> <CODE ENDS>
5. OSPF Topology YANG Module 5. OSPF Topology YANG Module
<CODE BEGINS> <CODE BEGINS> file "ietf-ospf-topology@2015-12-11.yang"
file "ospf-topology@2015-06-08.yang" module ietf-ospf-topology {
module ospf-topology { yang-version 1.1;
yang-version 1; namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-topology";
namespace "urn:ietf:params:xml:ns:yang:ospf-topology";
prefix "ospf"; prefix "ospf";
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
} }
import ietf-network { import ietf-network {
prefix "nw"; prefix "nw";
} }
import ietf-network-topology { import ietf-network-topology {
prefix "nt"; prefix "nt";
} }
import l3-unicast-igp-topology { import ietf-l3-unicast-igp-topology {
prefix "l3t"; prefix "l3t";
} }
organization "TBD"; organization
contact "TBD"; "IETF I2RS (Interface to the Routing System) Working Group";
description "OSPF Topology model";
revision "2015-06-08" { contact
description "Initial revision"; "WG Web: <http://tools.ietf.org/wg/i2rs/>
reference "TBD"; WG List: <mailto:i2rs@ietf.org>
WG Chair: Susan Hares
<mailto:shares@ndzh.com>
WG Chair: Jeffrey Haas
<mailto:jhaas@pfrc.org>
Editor: Alexander Clemm
<mailto:alex@cisco.com>
Editor: Jan Medved
<mailto:jmedved@cisco.com>
Editor: Robert Varga
<mailto:rovarga@cisco.com>
Editor: Tony Tkacik
<mailto:ttkacik@cisco.com>
Editor: Xufeng Liu
<mailto:xufeng.liu@ericsson.com>
Editor: Igor Bryskin
<mailto:Igor.Bryskin@huawei.com>
Editor: Aihua Guo
<mailto:aguo@advaoptical.com>
Editor: Nitin Bahadur
<mailto:nitin_bahadur@yahoo.com>
Editor: Hariharan Ananthakrishnan
<mailto:hari@packetdesign.com>
Editor: Vishnu Pavan Beeram
<mailto:vbeeram@juniper.net>";
description
"This module defines a model for OSPF network topologies.
Copyright (c) 2015 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of
draft-ietf-i2rs-yang-network-topo-02;
see the RFC itself for full legal notices.
NOTE TO RFC EDITOR: Please replace above reference to
draft-ietf-i2rs-yang-network-topo-02 with RFC
number when published (i.e. RFC xxxx).";
revision "2015-12-11" {
description
"Initial revision.
NOTE TO RFC EDITOR: Please replace the following reference
to draft-ietf-i2rs-yang-l3-topology-01 with
RFC number when published (i.e. RFC xxxx).";
reference
"draft-ietf-i2rs-yang-l3-topology-01";
} }
typedef area-id { typedef area-id {
type uint32; type uint32;
description "OSPF Area ID"; description
"OSPF Area ID";
} }
grouping ospf-topology-type { grouping ospf-topology-type {
description description
"Identifies the OSPF topology type."; "Identifies the OSPF topology type.";
container ospf { container ospf {
presence "indiates OSPF Topology"; presence "indiates OSPF Topology";
description description
"Its presence identifies the OSPF topology type."; "Its presence identifies the OSPF topology type.";
} }
} }
augment "/nw:network/nw:network-types/" augment "/nw:networks/nw:network/nw:network-types/"
+ "l3t:l3-unicast-igp-topology" { + "l3t:l3-unicast-igp-topology" {
description description
"Defines the OSPF topology type."; "Defines the OSPF topology type.";
uses ospf-topology-type; uses ospf-topology-type;
} }
augment "/nw:network/l3t:igp-topology-attributes" { augment "/nw:networks/nw:network/l3t:igp-topology-attributes" {
when "../nw:network-types/l3t:l3-unicast-igp-topology/ospf" { when "../nw:network-types/l3t:l3-unicast-igp-topology/ospf" {
description "Augment only for OSPF topology"; description
"Augment only for OSPF topology";
} }
description "Augment topology configuration"; description
"Augment topology configuration";
container ospf-topology-attributes { container ospf-topology-attributes {
description "Containing topology attributes"; description
"Containing topology attributes";
leaf area-id { leaf area-id {
type area-id; type area-id;
description "OSPF area ID"; description
"OSPF area ID";
} }
} }
} }
augment "/nw:network/nw:node/l3t:igp-node-attributes" { augment "/nw:networks/nw:network/nw:node/l3t:igp-node-attributes" {
when "../../nw:network-types/l3t:l3-unicast-igp-topology/ospf" { when "../../nw:network-types/l3t:l3-unicast-igp-topology/ospf" {
description "Augment only for OSPF topology"; description
"Augment only for OSPF topology";
} }
description "Augment node configuration"; description
"Augment node configuration";
uses ospf-node-attributes; uses ospf-node-attributes;
} }
augment "/nw:network/nt:link/l3t:igp-link-attributes" {
augment "/nw:networks/nw:network/nt:link/l3t:igp-link-attributes" {
when "../../nw:network-types/l3t:l3-unicast-igp-topology/ospf" { when "../../nw:network-types/l3t:l3-unicast-igp-topology/ospf" {
description "Augment only for OSPF topology"; description
"Augment only for OSPF topology";
} }
description "Augment link configuration"; description
"Augment link configuration";
uses ospf-link-attributes; uses ospf-link-attributes;
} }
augment "/nw:network/nw:node/l3t:igp-node-attributes/l3t:prefix" { augment "/nw:networks/nw:network/nw:node/"+
"l3t:igp-node-attributes/l3t:prefix" {
when "../../../nw:network-types/l3t:l3-unicast-igp-topology/" when "../../../nw:network-types/l3t:l3-unicast-igp-topology/"
+"ospf" { +"ospf" {
description "Augment only for OSPF topology"; description
"Augment only for OSPF topology";
} }
description "Augment prefix"; description
"Augment prefix";
uses ospf-prefix-attributes; uses ospf-prefix-attributes;
} }
grouping ospf-node-attributes { grouping ospf-node-attributes {
description "OSPF node scope attributes"; description
"OSPF node scope attributes";
container ospf-node-attributes { container ospf-node-attributes {
description "Containing node attributes"; description
"Containing node attributes";
choice router-type { choice router-type {
description "Indicates router type"; description
"Indicates router type";
case abr { case abr {
leaf abr { leaf abr {
type empty; type empty;
description "The node is ABR"; description
"The node is ABR";
} }
} }
case asbr { case asbr {
leaf asbr { leaf asbr {
type empty; type empty;
description "The node is ASBR"; description
"The node is ASBR";
} }
} }
case internal { case internal {
leaf internal { leaf internal {
type empty; type empty;
description "The node is internal"; description
"The node is internal";
} }
} }
case pseudonode { case pseudonode {
leaf pseudonode { leaf pseudonode {
type empty; type empty;
description "The node is pseudonode"; description
"The node is pseudonode";
} }
} }
} }
leaf dr-interface-id { leaf dr-interface-id {
when "../router-type/pseudonode" { when "../router-type/pseudonode" {
description "Valid only for pseudonode"; description
"Valid only for pseudonode";
} }
type uint32; type uint32;
default "0"; default "0";
description "For pseudonodes, DR interface-id"; description
"For pseudonodes, DR interface-id";
} }
leaf-list multi-topology-id { leaf-list multi-topology-id {
type uint8 { type uint8 {
range "0..127"; range "0..127";
} }
max-elements "128"; max-elements "128";
description description
"List of Multi-Topology Identifier up-to 128 (0-127). "List of Multi-Topology Identifier up-to 128 (0-127).
RFC 4915"; See RFC 4915";
} }
leaf capabilities { leaf capabilities {
type bits { type bits {
bit graceful-restart-capable { bit graceful-restart-capable {
position 0; position 0;
description "Graceful restart capable"; description
"Graceful restart capable";
} }
bit graceful-restart-helper { bit graceful-restart-helper {
position 1; position 1;
description "Graceful restart helper"; description
"Graceful restart helper";
} }
bit stub-router-support { bit stub-router-support {
position 2; position 2;
description "Stub router support"; description
"Stub router support";
} }
bit traffic-engineering-support { bit traffic-engineering-support {
position 3; position 3;
description "Traffic engineering support"; description
"Traffic engineering support";
} }
bit point-to-point-over-lan { bit point-to-point-over-lan {
position 4; position 4;
description "Support point to point over LAN"; description
"Support point to point over LAN";
} }
bit experimental-te { bit experimental-te {
position 5; position 5;
description "Support experimental traffic engineering"; description
"Support experimental traffic engineering";
} }
} }
description "OSPF capabilities as bit vector. RFC 4970"; description
"OSPF capabilities as bit vector. RFC 4970";
} }
} // ospf }
} // ospf-node-attributes }
grouping ospf-link-attributes { grouping ospf-link-attributes {
description "OSPF link scope attributes"; description
"OSPF link scope attributes";
container ospf-link-attributes { container ospf-link-attributes {
description "Containing OSPF link attributes"; description
"Containing OSPF link attributes";
leaf multi-topology-id { leaf multi-topology-id {
type uint8 { type uint8 {
range "0..127"; range "0..127";
} }
description "Muti topology ID"; description "Muti topology ID";
} }
} }
} // ospf-link-attributes } // ospf-link-attributes
grouping ospf-prefix-attributes { grouping ospf-prefix-attributes {
description "OSPF prefix attributes"; description
"OSPF prefix attributes";
container ospf-prefix-attributes { container ospf-prefix-attributes {
description "Containing prefix attributes"; description
"Containing prefix attributes";
leaf forwarding-address { leaf forwarding-address {
when "../../l3t:l3-unicast-igp-topology/l3t:ospf/" when "../../l3t:l3-unicast-igp-topology/l3t:ospf/"+
+"l3t:router-type/l3t:asbr" { "l3t:router-type/l3t:asbr" {
description "Valid only for ABSR"; description "Valid only for ABSR";
} }
type inet:ipv4-address; type inet:ipv4-address;
description "Forwarding address for ABSR"; description
"Forwarding address for ABSR";
} }
} }
} }
augment "/l3t:igp-node-event" { augment "/l3t:igp-node-event" {
description "OSPF node event"; description
"OSPF node event";
uses ospf-topology-type; uses ospf-topology-type;
uses ospf:ospf-node-attributes; uses ospf:ospf-node-attributes;
} }
augment "/l3t:igp-link-event" { augment "/l3t:igp-link-event" {
description "OSPF link event"; description
"OSPF link event";
uses ospf-topology-type; uses ospf-topology-type;
uses ospf:ospf-link-attributes; uses ospf:ospf-link-attributes;
} }
augment "/l3t:igp-prefix-event" { augment "/l3t:igp-prefix-event" {
description "OSPF prefix event"; description
"OSPF prefix event";
uses ospf-topology-type; uses ospf-topology-type;
uses ospf:ospf-prefix-attributes; uses ospf:ospf-prefix-attributes;
} }
} }
<CODE ENDS> <CODE ENDS>
6. ISIS Topology YANG Module 6. ISIS Topology YANG Module
<CODE BEGINS> <CODE BEGINS> file "isis-topology@2015-12-11.yang"
file "isis-topology@2015-06-08.yang" module ietf-isis-topology {
module isis-topology { yang-version 1.1;
yang-version 1; namespace "urn:ietf:params:xml:ns:yang:ietf-isis-topology";
namespace "urn:ietf:params:xml:ns:yang:isis-topology";
prefix "isis"; prefix "isis";
import ietf-network { import ietf-network {
prefix "nw"; prefix "nw";
} }
import ietf-network-topology { import ietf-network-topology {
prefix "nt"; prefix "nt";
} }
import l3-unicast-igp-topology { import ietf-l3-unicast-igp-topology {
prefix "l3t"; prefix "l3t";
} }
organization "TBD"; organization
contact "TBD"; "IETF I2RS (Interface to the Routing System) Working Group";
description "ISIS Topology model";
revision "2015-06-08" { contact
description "Initial version"; "WG Web: <http://tools.ietf.org/wg/i2rs/>
reference "TBD"; WG List: <mailto:i2rs@ietf.org>
WG Chair: Susan Hares
<mailto:shares@ndzh.com>
WG Chair: Jeffrey Haas
<mailto:jhaas@pfrc.org>
Editor: Alexander Clemm
<mailto:alex@cisco.com>
Editor: Jan Medved
<mailto:jmedved@cisco.com>
Editor: Robert Varga
<mailto:rovarga@cisco.com>
Editor: Tony Tkacik
<mailto:ttkacik@cisco.com>
Editor: Xufeng Liu
<mailto:xufeng.liu@ericsson.com>
Editor: Igor Bryskin
<mailto:Igor.Bryskin@huawei.com>
Editor: Aihua Guo
<mailto:aguo@advaoptical.com>
Editor: Nitin Bahadur
<mailto:nitin_bahadur@yahoo.com>
Editor: Hariharan Ananthakrishnan
<mailto:hari@packetdesign.com>
Editor: Vishnu Pavan Beeram
<mailto:vbeeram@juniper.net>";
description
"This module defines a model for IS-IS network topologies.
Copyright (c) 2015 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of
draft-ietf-i2rs-yang-network-topo-02;
see the RFC itself for full legal notices.
NOTE TO RFC EDITOR: Please replace above reference to
draft-ietf-i2rs-yang-network-topo-02 with RFC
number when published (i.e. RFC xxxx).";
revision "2015-12-11" {
description
"Initial revision.
NOTE TO RFC EDITOR: Please replace the following reference
to draft-ietf-i2rs-yang-l3-topology-01 with
RFC number when published (i.e. RFC xxxx).";
reference
"draft-ietf-i2rs-yang-l3-topology-01";
} }
typedef iso-system-id { typedef iso-system-id {
type string { type string {
pattern '[0-9a-fA-F]{4}(\.[0-9a-fA-F]{4}){2}'; pattern '[0-9a-fA-F]{4}(\.[0-9a-fA-F]{4}){2}';
} }
description "ISO System ID. RFC 1237"; description
"ISO System ID. RFC 1237";
} }
typedef iso-pseudonode-id { typedef iso-pseudonode-id {
type string { type string {
pattern '[0-9a-fA-F]{2}'; pattern '[0-9a-fA-F]{2}';
} }
description "ISO pseudonode id for broadcast network"; description
"ISO pseudonode id for broadcast network";
} }
typedef iso-net-id { typedef iso-net-id {
type string { type string {
pattern '[0-9a-fA-F]{2}((\.[0-9a-fA-F]{4}){6})'; pattern '[0-9a-fA-F]{2}((\.[0-9a-fA-F]{4}){6})';
} }
description "ISO NET ID. RFC 1237"; description
"ISO NET ID. RFC 1237";
} }
grouping isis-topology-type { grouping isis-topology-type {
description description
"Identifies the ISIS topology type."; "Identifies the ISIS topology type.";
container isis { container isis {
presence "Indicates ISIS Topology"; presence "Indicates ISIS Topology";
description description
"Its presence identifies the ISIS topology type."; "Its presence identifies the ISIS topology type.";
} }
} }
skipping to change at page 23, line 14 skipping to change at page 28, line 33
grouping isis-topology-type { grouping isis-topology-type {
description description
"Identifies the ISIS topology type."; "Identifies the ISIS topology type.";
container isis { container isis {
presence "Indicates ISIS Topology"; presence "Indicates ISIS Topology";
description description
"Its presence identifies the ISIS topology type."; "Its presence identifies the ISIS topology type.";
} }
} }
augment "/nw:network/nw:network-types/" augment "/nw:networks/nw:network/nw:network-types/"
+"l3t:l3-unicast-igp-topology" { +"l3t:l3-unicast-igp-topology" {
description description
"Defines the ISIS topology type."; "Defines the ISIS topology type.";
uses isis-topology-type; uses isis-topology-type;
} }
augment "/nw:network/l3t:igp-topology-attributes" { augment "/nw:networks/nw:network/l3t:igp-topology-attributes" {
when "../nw:network-types/l3t:l3-unicast-igp-topology/isis" { when "../nw:network-types/l3t:l3-unicast-igp-topology/isis" {
description "Augment only for ISIS topology"; description
"Augment only for ISIS topology";
} }
description "Augment topology configuration"; description
"Augment topology configuration";
container isis-topology-attributes { container isis-topology-attributes {
description "Containing topology attributes"; description
"Containing topology attributes";
leaf net { leaf net {
type iso-net-id; type iso-net-id;
description "ISO NET ID value"; description
"ISO NET ID value";
} }
} }
} }
augment "/nw:network/nw:node/" augment "/nw:networks/nw:network/nw:node/"+
+"l3t:igp-node-attributes" { "l3t:igp-node-attributes" {
when "../../nw:network-types/l3t:l3-unicast-igp-topology/isis" { when "../../nw:network-types/l3t:l3-unicast-igp-topology/isis" {
description "Augment only for ISIS topology"; description
"Augment only for ISIS topology";
} }
description "Augment node configuration"; description
"Augment node configuration";
uses isis-node-attributes; uses isis-node-attributes;
} }
augment "/nw:network/nt:link/l3t:igp-link-attributes" { augment "/nw:networks/nw:network/nt:link/l3t:igp-link-attributes" {
when "../../nw:network-types/l3t:l3-unicast-igp-topology/isis" { when "../../nw:network-types/l3t:l3-unicast-igp-topology/isis" {
description "Augment only for ISIS topology"; description
"Augment only for ISIS topology";
} }
description "Augment link configuration"; description
"Augment link configuration";
uses isis-link-attributes; uses isis-link-attributes;
} }
grouping isis-node-attributes { grouping isis-node-attributes {
description "ISIS node scope attributes"; description
"ISIS node scope attributes";
container isis-node-attributes { container isis-node-attributes {
description "Containing node attributes"; description
"Containing node attributes";
container iso { container iso {
description "Containing ISO atrributes"; description
"Containing ISO atrributes";
leaf iso-system-id { leaf iso-system-id {
type iso-system-id; type iso-system-id;
description "ISO system ID"; description
"ISO system ID";
} }
leaf iso-pseudonode-id { leaf iso-pseudonode-id {
type iso-pseudonode-id; type iso-pseudonode-id;
default "00"; default "00";
description "Pseudonode ID"; description
"Pseudonode ID";
} }
} }
leaf-list net { leaf-list net {
type iso-net-id; type iso-net-id;
max-elements 3; max-elements 3;
description "List of ISO NET IDs"; description
"List of ISO NET IDs";
} }
leaf-list multi-topology-id { leaf-list multi-topology-id {
type uint8 { type uint8 {
range "0..127"; range "0..127";
} }
max-elements "128"; max-elements "128";
description description
"List of Multi Topology Identifier upto 128 (0-127). "List of Multi Topology Identifier upto 128 (0-127).
RFC 4915"; RFC 4915";
} }
choice router-type { choice router-type {
description "Indicates router type"; description
"Indicates router type";
case level-2 { case level-2 {
leaf level-2 { leaf level-2 {
type empty; type empty;
description "Level-2 only"; description
"Level-2 only";
} }
} }
case level-1 { case level-1 {
leaf level-1 { leaf level-1 {
type empty; type empty;
description "Level-1 only"; description
"Level-1 only";
} }
} }
case level-1-2 { case level-1-2 {
leaf level-1-2 { leaf level-1-2 {
type empty; type empty;
description "Level-1 and Level-2"; description
"Level-1 and Level-2";
} }
} }
} }
} }
} }
grouping isis-link-attributes { grouping isis-link-attributes {
description "ISIS link scope attributes"; description
"ISIS link scope attributes";
container isis-link-attributes { container isis-link-attributes {
description "Containing link attributes"; description
"Containing link attributes";
leaf multi-topology-id { leaf multi-topology-id {
type uint8 { type uint8 {
range "0..127"; range "0..127";
} }
description "Muti topology ID"; description
"Multi topology ID";
} }
} }
} }
augment "/l3t:igp-node-event" { augment "/l3t:igp-node-event" {
description "ISIS node event"; description
"ISIS node event";
uses isis-topology-type; uses isis-topology-type;
uses isis-node-attributes; uses isis-node-attributes;
} }
augment "/l3t:igp-link-event" { augment "/l3t:igp-link-event" {
description "ISIS link event"; description
"ISIS link event";
uses isis-topology-type; uses isis-topology-type;
uses isis-link-attributes; uses isis-link-attributes;
} }
} // Module isis-topology }
<CODE ENDS> <CODE ENDS>
7. Security Considerations 7. Security Considerations
The transport protocol used for sending the topology data MUST The transport protocol used for sending the topology data MUST
support authentication and SHOULD support encryption. The data-model support authentication and SHOULD support encryption. The data-model
by itself does not create any security implications. by itself does not create any security implications.
8. Contributors 8. Contributors
skipping to change at page 26, line 22 skipping to change at page 32, line 19
Carlos Pignataro, Joel Halpern, Juergen Schoenwaelder, Alia Atlas, Carlos Pignataro, Joel Halpern, Juergen Schoenwaelder, Alia Atlas,
and Susan Hares. and Susan Hares.
10. References 10. References
10.1. Normative References 10.1. Normative References
[I-D.draft-ietf-i2rs-yang-network-topo] [I-D.draft-ietf-i2rs-yang-network-topo]
Clemm, A., Medved, J., Tkacik, T., Varga, R., Bahadur, N., Clemm, A., Medved, J., Tkacik, T., Varga, R., Bahadur, N.,
and H. Ananthakrishnan, "A YANG Data Model for Network and H. Ananthakrishnan, "A YANG Data Model for Network
Topologies", I-D draft-ietf-i2rs-yang-network-topo-01, Topologies", I-D draft-ietf-i2rs-yang-network-topo-02,
June 2015. December 2015.
[I-D.draft-ietf-netconf-restconf] [I-D.draft-ietf-netconf-restconf]
Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", I-D draft-ietf-netconf-restconf-05, June 2015. Protocol", I-D draft-ietf-netconf-restconf-08, October
2015.
[I-D.draft-ietf-netmod-rfc6020bis-09]
Bjorklund, M., "The YANG 1.1 Data Modeling Language", I-D
draft-ietf-netmod-rfc6020bis-09, December 2015.
[I-D.draft-ietf-netmod-yang-json] [I-D.draft-ietf-netmod-yang-json]
Lhotka, L., "JSON Encoding of Data Modeled with YANG", I-D Lhotka, L., "JSON Encoding of Data Modeled with YANG",
draft-ietf-netmod-yang-json-03, February 2015. I-D draft-ietf-netmod-yang-json-06, October 2015.
[RFC1195] Callon, R., "Use of OSI IS-IS for Routing in TCP/IP and [RFC1195] Callon, R., "Use of OSI IS-IS for Routing in TCP/IP and
Dual Environments", RFC 1195, December 1990. Dual Environments", RFC 1195, December 1990.
[RFC2178] Moy, J., "OSPF Version 2", RFC 2178, July 1997. [RFC2178] Moy, J., "OSPF Version 2", RFC 2178, July 1997.
[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the
Network Configuration Protocol (NETCONF)", RFC 6020, Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010. October 2010.
[RFC6021] Schoenwaelder, J., "Common YANG Data Types", RFC 6021,
October 2010.
[RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A.
Bierman, "Network Configuration Protocol (NETCONF)", RFC Bierman, "Network Configuration Protocol (NETCONF)",
6241, June 2011. RFC 6241, June 2011.
[RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991,
July 2013.
[RFC7223] Bjorklund, M., "A YANG Data Model for Interface [RFC7223] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 7223, May 2014. Management", RFC 7223, May 2014.
10.2. Informative References 10.2. Informative References
[I-D.draft-ietf-i2rs-usecase-reqs-summary] [I-D.draft-ietf-i2rs-usecase-reqs-summary]
Hares, S. and M. Chen, "Summary of I2RS Use Case Hares, S. and M. Chen, "Summary of I2RS Use Case
Requirements", I-D draft-ietf-i2rs-usecase-reqs-summary- Requirements", I-D draft-ietf-i2rs-usecase-reqs-summary-
01, May 2015. 01, May 2015.
skipping to change at page 27, line 40 skipping to change at page 33, line 40
Pantheon Technologies SRO Pantheon Technologies SRO
EMail: tony.tkacik@pantheon.sk EMail: tony.tkacik@pantheon.sk
Xufeng Liu Xufeng Liu
Ericsson Ericsson
EMail: xufeng.liu@ericsson.com EMail: xufeng.liu@ericsson.com
Igor Bryskin Igor Bryskin
Adva Optical Huawei
EMail: ibryskin@advaoptical.com EMail: Igor.Bryskin@huawei.com
Aihua Guo Aihua Guo
Adva Optical Adva Optical
EMail: aguo@advaoptical.com EMail: aguo@advaoptical.com
Hariharan Ananthakrishnan Hariharan Ananthakrishnan
Packet Design Packet Design
EMail: hari@packetdesign.com EMail: hari@packetdesign.com
Nitin Bahadur Nitin Bahadur
Bracket Computing Bracket Computing
EMail: nitin_bahadur@yahoo.com EMail: nitin_bahadur@yahoo.com
Vishnu Beeram Vishnu Pavan Beeram
Juniper Networks Juniper Networks
EMail: vbeeram@juniper.net EMail: vbeeram@juniper.net
 End of changes. 191 change blocks. 
466 lines changed or deleted 761 lines changed or added

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