draft-ietf-i2rs-yang-l3-topology-05.txt   draft-ietf-i2rs-yang-l3-topology-06.txt 
Network Working Group A. Clemm Network Working Group A. Clemm
Internet-Draft Sympotech Internet-Draft Sympotech
Intended status: Standards Track J. Medved Intended status: Standards Track J. Medved
Expires: May 20, 2017 Cisco Expires: June 3, 2017 Cisco
R. Varga R. Varga
Pantheon Technologies SRO Pantheon Technologies SRO
X. Liu X. Liu
Ericsson Ericsson
I. Bryskin I. Bryskin
Huawei 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
November 16, 2016 November 30, 2016
A YANG Data Model for Layer 3 Topologies A YANG Data Model for Layer 3 Topologies
draft-ietf-i2rs-yang-l3-topology-05.txt draft-ietf-i2rs-yang-l3-topology-06.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 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 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 May 20, 2017. This Internet-Draft will expire on June 3, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Definitions and Acronyms . . . . . . . . . . . . . . . . . . 4 2. Definitions and Acronyms . . . . . . . . . . . . . . . . . . 4
3. Model Structure . . . . . . . . . . . . . . . . . . . . . . . 5 3. Model Structure . . . . . . . . . . . . . . . . . . . . . . . 4
4. Layer 3 Unicast Topology Model Overview . . . . . . . . . . . 5 4. Layer 3 Unicast Topology Model Overview . . . . . . . . . . . 5
5. Layer 3 Unicast Topology YANG Module . . . . . . . . . . . . 7 5. Layer 3 Unicast Topology YANG Module . . . . . . . . . . . . 7
6. Extending the Model . . . . . . . . . . . . . . . . . . . . . 14 6. Extending the Model . . . . . . . . . . . . . . . . . . . . . 14
6.1. Example 1: OSPF Topology . . . . . . . . . . . . . . . . 14 6.1. Example 1: OSPF Topology . . . . . . . . . . . . . . . . 14
6.1.1. Model Overview . . . . . . . . . . . . . . . . . . . 14 6.1.1. Model Overview . . . . . . . . . . . . . . . . . . . 14
6.1.2. OSPF Topology YANG Module . . . . . . . . . . . . . . 16 6.1.2. OSPF Topology YANG Module . . . . . . . . . . . . . . 16
6.2. Example 2: IS-IS Topology . . . . . . . . . . . . . . . . 21 6.2. Example 2: IS-IS Topology . . . . . . . . . . . . . . . . 21
6.2.1. Model Overview . . . . . . . . . . . . . . . . . . . 21 6.2.1. Model Overview . . . . . . . . . . . . . . . . . . . 21
6.2.2. IS-IS Topology YANG Module . . . . . . . . . . . . . 23 6.2.2. IS-IS Topology YANG Module . . . . . . . . . . . . . 23
7. Interactions with Other YANG Modules . . . . . . . . . . . . 28 7. Interactions with Other YANG Modules . . . . . . . . . . . . 28
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
9. Security Considerations . . . . . . . . . . . . . . . . . . . 29 9. Security Considerations . . . . . . . . . . . . . . . . . . . 29
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 29 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 29
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 29
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 30 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 30
12.1. Normative References . . . . . . . . . . . . . . . . . . 30 12.1. Normative References . . . . . . . . . . . . . . . . . . 30
12.2. Informative References . . . . . . . . . . . . . . . . . 31 12.2. Informative References . . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31
1. Introduction 1. Introduction
This document introduces a YANG [RFC7950] [RFC6991] data model for This document introduces a YANG [RFC7950] [RFC6991] data model for
Layer 3 network topologies, specifically Layer 3 Unicast. The model Layer 3 network topologies, specifically Layer 3 Unicast. The model
allows an application to have a holistic view of the topology of a allows an application to have a holistic view of the topology of a
Layer 3 network, all contained in a single conceptual YANG datastore. Layer 3 network, all contained in a single conceptual YANG datastore.
The data model builds on top of, and augments, the data model for The data model builds on top of, and augments, the data model for
skipping to change at page 7, line 27 skipping to change at page 7, line 27
type of event, the topology from which it originated, and the type of event, the topology from which it originated, and the
affected node, or link, or prefix, or termination point. In affected node, or link, or prefix, or termination point. In
addition, as a convenience to applications, additional data of the addition, as a convenience to applications, additional data of the
affected node, or link, or termination point (respectively) is affected node, or link, or termination point (respectively) is
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.
5. Layer 3 Unicast Topology YANG Module 5. Layer 3 Unicast Topology YANG Module
<CODE BEGINS> file "ietf-l3-unicast-topology@2016-11-16.yang" <CODE BEGINS> file "ietf-l3-unicast-topology@2016-11-30.yang"
module ietf-l3-unicast-topology { module ietf-l3-unicast-topology {
yang-version 1.1; yang-version 1.1;
namespace namespace
"urn:ietf:params:xml:ns:yang:ietf-l3-unicast-topology"; "urn:ietf:params:xml:ns:yang:ietf-l3-unicast-topology";
prefix "l3t"; prefix "l3t";
import ietf-network { import ietf-network {
prefix "nd"; prefix "nd";
} }
import ietf-network-topology { import ietf-network-topology {
prefix "lnk"; prefix "lnk";
skipping to change at page 8, line 33 skipping to change at page 8, line 33
topologies. topologies.
Copyright (c) 2016 IETF Trust and the persons identified as Copyright (c) 2016 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of This version of this YANG module is part of
draft-ietf-i2rs-yang-l3-topology-05; draft-ietf-i2rs-yang-l3-topology-06;
see the RFC itself for full legal notices. see the RFC itself for full legal notices.
NOTE TO RFC EDITOR: Please replace above reference to NOTE TO RFC EDITOR: Please replace above reference to
draft-ietf-i2rs-yang-l3-topology-05 with RFC draft-ietf-i2rs-yang-l3-topology-06 with RFC
number when published (i.e. RFC xxxx)."; number when published (i.e. RFC xxxx).";
revision "2016-11-16" { revision "2016-11-30" {
description description
"Initial revision. "Initial revision.
NOTE TO RFC EDITOR: Please replace the following reference NOTE TO RFC EDITOR: Please replace the following reference
to draft-ietf-i2rs-yang-l3-topology-05 with to draft-ietf-i2rs-yang-l3-topology-06 with
RFC number when published (i.e. RFC xxxx)."; RFC number when published (i.e. RFC xxxx).";
reference reference
"draft-ietf-i2rs-yang-l3-topology-05"; "draft-ietf-i2rs-yang-l3-topology-06";
} }
identity flag-identity { identity flag-identity {
description "Base type for flags"; description "Base type for flags";
} }
typedef l3-event-type { typedef l3-event-type {
type enumeration { type enumeration {
enum "add" { enum "add" {
description description
"An Layer 3 node or link or prefix or termination-point has "An Layer 3 node or link or prefix or termination-point has
skipping to change at page 14, line 51 skipping to change at page 14, line 51
be refined across multiple levels; they do not constitute full- be refined across multiple levels; they do not constitute full-
fledged OSPF and IS-IS topology models which may be more fledged OSPF and IS-IS topology models which may be more
comprehensive and refined than the models that are described here. comprehensive and refined than the models that are described here.
6.1. Example 1: OSPF Topology 6.1. Example 1: OSPF Topology
6.1.1. Model Overview 6.1.1. Model Overview
The following model shows how the Layer 3 Unicast topology model can The following model shows how the Layer 3 Unicast topology model can
be extended to cover OSFP topologies. For this purpose, a set of be extended to cover OSFP topologies. For this purpose, a set of
augmentations are introduced in a separate YANG module, "ietf-ospf- augmentations are introduced in a separate YANG module, "example-
topology", whose structure is depicted in the following diagram. ietf-ospf-topology", whose structure is depicted in the following
diagram. Like before, brackets enclose list keys, "rw" means
Like before, brackets enclose list keys, "rw" means configuration, configuration, "ro" operational state data, "?" designates optional
"ro" operational state data, "?" designates optional nodes, "*" nodes, "*" designates nodes that can have multiple instances.
designates nodes that can have multiple instances. Parantheses Parantheses enclose choice and case nodes. A "+" at the end of a
enclose choice and case nodes. A "+" at the end of a line indicates line indicates a line break.
a line break.
module: ietf-ospf-topology module: example-ietf-ospf-topology
augment /nd:networks/nd:network/nd:network-types/+ augment /nd:networks/nd:network/nd:network-types/+
l3t:l3-unicast-topology: l3t:l3-unicast-topology:
+--rw ospf! +--rw ospf!
augment /nd:networks/nd:network/l3t:l3-topology-attributes: augment /nd:networks/nd:network/l3t:l3-topology-attributes:
+--rw ospf-topology-attributes +--rw ospf-topology-attributes
+--rw area-id? area-id-type +--rw area-id? area-id-type
augment /nd:networks/nd:network/nd:node/l3t:l3-node-attributes: augment /nd:networks/nd:network/nd:node/l3t:l3-node-attributes:
+--rw ospf-node-attributes +--rw ospf-node-attributes
+--rw (router-type)? +--rw (router-type)?
| +--:(abr) | +--:(abr)
skipping to change at page 16, line 35 skipping to change at page 16, line 35
In addition, the module extends notifications for events concerning In addition, the module extends notifications for events concerning
Layer 3 nodes, links, termination points, and prefixes with OSPF Layer 3 nodes, links, termination points, and prefixes with OSPF
attributes. attributes.
It should be noted that the model defined here represents topology It should be noted that the model defined here represents topology
and is intended as an example. It does not define how to configure and is intended as an example. It does not define how to configure
OSPF routers or interfaces. OSPF routers or interfaces.
6.1.2. OSPF Topology YANG Module 6.1.2. OSPF Topology YANG Module
<CODE BEGINS> file "ietf-ospf-topology@2016-11-16.yang" The OSPF Topology YANG Module is specified below. As mentioned, the
module ietf-ospf-topology { module is intended as an example for how the Layer 3 Unicast topology
model can be extended to cover OSFP topologies, but it is not
normative. Accordingly, the module is not delimited with <CODE
BEGINS> and <CODE ENDS> tags.
file "example-ietf-ospf-topology@2016-11-30.yang"
module example-ietf-ospf-topology {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-topology"; namespace "urn:ietf:params:xml:ns:yang:example-ietf-ospf-topology";
prefix "ospft"; prefix "ospft";
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix "yang";
} }
import ietf-network { import ietf-network {
prefix "nd"; prefix "nd";
} }
import ietf-network-topology { import ietf-network-topology {
prefix "lnk"; prefix "lnk";
} }
skipping to change at page 17, line 41 skipping to change at page 17, line 47
"This module defines a model for OSPF network topologies. "This module defines a model for OSPF network topologies.
Copyright (c) 2016 IETF Trust and the persons identified as Copyright (c) 2016 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of This version of this YANG module is part of
draft-ietf-i2rs-yang-l3-topology-05; draft-ietf-i2rs-yang-l3-topology-06;
see the RFC itself for full legal notices. see the RFC itself for full legal notices.
NOTE TO RFC EDITOR: Please replace above reference to NOTE TO RFC EDITOR: Please replace above reference to
draft-ietf-i2rs-yang-l3-topology-05 with RFC draft-ietf-i2rs-yang-l3-topology-06 with RFC
number when published (i.e. RFC xxxx)."; number when published (i.e. RFC xxxx).";
revision "2016-11-16" {
revision "2016-11-30" {
description description
"Initial revision. "Initial revision.
NOTE TO RFC EDITOR: Please replace the following reference NOTE TO RFC EDITOR: Please replace the following reference
to draft-ietf-i2rs-yang-l3-topology-05 with to draft-ietf-i2rs-yang-l3-topology-06 with
RFC number when published (i.e. RFC xxxx)."; RFC number when published (i.e. RFC xxxx).";
reference reference
"draft-ietf-i2rs-yang-l3-topology-05"; "draft-ietf-i2rs-yang-l3-topology-06";
} }
typedef area-id-type { typedef area-id-type {
type yang:dotted-quad; type yang:dotted-quad;
description description
"Area ID type."; "Area ID type.";
} }
grouping ospf-topology-type { grouping ospf-topology-type {
description description
"Identifies the OSPF topology type."; "Identifies the OSPF topology type.";
container ospf { container ospf {
skipping to change at page 21, line 4 skipping to change at page 21, line 10
uses ospf-topology-type; uses ospf-topology-type;
uses ospft:ospf-node-attributes; uses ospft:ospf-node-attributes;
} }
augment "/l3t:l3-link-event" { augment "/l3t:l3-link-event" {
description description
"OSPF link event"; "OSPF link event";
uses ospf-topology-type; uses ospf-topology-type;
uses ospft:ospf-link-attributes; uses ospft:ospf-link-attributes;
} }
} }
<CODE ENDS>
6.2. Example 2: IS-IS Topology 6.2. Example 2: IS-IS Topology
6.2.1. Model Overview 6.2.1. Model Overview
IS-IS topologies are another type of Layer 3 Unicast topology. Like IS-IS topologies are another type of Layer 3 Unicast topology. Like
in the case of OSPF topology, a model for IS-IS topology can be in the case of OSPF topology, a model for IS-IS topology can be
defined in a separate module which augments "ietf-l3-unicast-igp- defined in a separate module which augments "ietf-l3-unicast-igp-
topology". The structure of a corresponding model, "ietf-isis- topology". The structure of a corresponding model, "ietf-isis-
topology", is depicted in the following diagram. Like before, topology", is depicted in the following diagram. Like before,
brackets enclose list keys, "rw" means configuration, "ro" brackets enclose list keys, "rw" means configuration, "ro"
operational state data, "?" designates optional nodes, "*" designates operational state data, "?" designates optional nodes, "*" designates
nodes that can have multiple instances. Parantheses enclose choice nodes that can have multiple instances. Parantheses enclose choice
and case nodes. A "+" at the end of a line indicates a line break. and case nodes. A "+" at the end of a line indicates a line break.
module: ietf-isis-topology module: example-ietf-isis-topology
augment /nd:networks/nd:network/nd:network-types/+ augment /nd:networks/nd:network/nd:network-types/+
l3t:l3-unicast-topology: l3t:l3-unicast-topology:
+--rw isis! +--rw isis!
augment /nd:networks/nd:network/l3t:l3-topology-attributes: augment /nd:networks/nd:network/l3t:l3-topology-attributes:
+--rw isis-topology-attributes +--rw isis-topology-attributes
+--rw net? area-address +--rw net? area-address
augment /nd:networks/nd:network/nd:node/l3t:l3-node-attributes: augment /nd:networks/nd:network/nd:node/l3t:l3-node-attributes:
+--rw isis-node-attributes +--rw isis-node-attributes
+--rw iso +--rw iso
| +--rw iso-system-id? system-id | +--rw iso-system-id? system-id
skipping to change at page 23, line 11 skipping to change at page 23, line 11
objects include router-type, iso-system-id to identify the router, objects include router-type, iso-system-id to identify the router,
a list of multi-topology-id, a list of NET ids, and traffic a list of multi-topology-id, a list of NET ids, and traffic
engineering attributes. 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 nodes and links with IS-IS In addition, the module augments nodes and links with IS-IS
attributes. attributes.
Again, it should be noted that the model defined here represents Again, it should be noted that the model defined here represents a
topology and is intended as an example. It does not define how to topology and is intended as an example. It does not define how to
configure IS-IS routers or interfaces. configure IS-IS routers or interfaces.
6.2.2. IS-IS Topology YANG Module 6.2.2. IS-IS Topology YANG Module
<CODE BEGINS> file "ietf-isis-topology@2016-11-16.yang" The IS-IS Topology YANG Module is specified as follows. As
module ietf-isis-topology { mentioned, the module is intended as an example for how the Layer 3
Unicast topology model can be extended to cover IS-IS topologies, but
it is not normative. Accordingly, the module is not delimited with
<CODE BEGINS> and <CODE ENDS> tags.
file "example-ietf-isis-topology@2016-11-30.yang"
module example-ietf-isis-topology {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-isis-topology"; namespace "urn:ietf:params:xml:ns:yang:example-ietf-isis-topology";
prefix "isist"; prefix "isist";
import ietf-network { import ietf-network {
prefix "nd"; prefix "nd";
} }
import ietf-network-topology { import ietf-network-topology {
prefix "lnk"; prefix "lnk";
} }
import ietf-l3-unicast-topology { import ietf-l3-unicast-topology {
prefix "l3t"; prefix "l3t";
} }
skipping to change at page 24, line 20 skipping to change at page 24, line 26
"This module defines a model for IS-IS network topologies. "This module defines a model for IS-IS network topologies.
Copyright (c) 2016 IETF Trust and the persons identified as Copyright (c) 2016 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of This version of this YANG module is part of
draft-ietf-i2rs-yang-l3-topology-05; draft-ietf-i2rs-yang-l3-topology-06;
see the RFC itself for full legal notices. see the RFC itself for full legal notices.
NOTE TO RFC EDITOR: Please replace above reference to NOTE TO RFC EDITOR: Please replace above reference to
draft-ietf-i2rs-yang-l3-topology-05 with RFC draft-ietf-i2rs-yang-l3-topology-06 with RFC
number when published (i.e. RFC xxxx)."; number when published (i.e. RFC xxxx).";
revision "2016-11-16" { revision "2016-11-30" {
description description
"Initial revision. "Initial revision.
NOTE TO RFC EDITOR: Please replace the following reference NOTE TO RFC EDITOR: Please replace the following reference
to draft-ietf-i2rs-yang-l3-topology-5 with to draft-ietf-i2rs-yang-l3-topology-06 with
RFC number when published (i.e. RFC xxxx)."; RFC number when published (i.e. RFC xxxx).";
reference reference
draft-ietf-i2rs-yang-l3-topology-05; draft-ietf-i2rs-yang-l3-topology-06;
} }
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 description
"ISO pseudonode id for broadcast network."; "ISO pseudonode id for broadcast network.";
} }
typedef area-address{ typedef area-address{
type string { type string {
skipping to change at page 28, line 4 skipping to change at page 28, line 10
"ISIS node event"; "ISIS node event";
uses isis-topology-type; uses isis-topology-type;
uses isis-node-attributes; uses isis-node-attributes;
} }
augment "/l3t:l3-link-event" { augment "/l3t:l3-link-event" {
description description
"ISIS link event"; "ISIS link event";
uses isis-topology-type; uses isis-topology-type;
uses isis-link-attributes; uses isis-link-attributes;
} }
} }
<CODE ENDS>
7. Interactions with Other YANG Modules 7. Interactions with Other YANG Modules
As described in section Section 3, the model builds on top of, and As described in section Section 3, the model builds on top of, and
augments, the YANG modules defined in augments, the YANG modules defined in
[I-D.draft-ietf-i2rs-yang-network-topo]. Specifically, module ietf- [I-D.draft-ietf-i2rs-yang-network-topo]. Specifically, module ietf-
l3-unicast-topology augments modules "ietf-network" and "ietf- l3-unicast-topology augments modules "ietf-network" and "ietf-
network-topology". In addition, the model makes use of data types network-topology". In addition, the model makes use of data types
that have been defined in [RFC6991]. that have been defined in [RFC6991].
The moodel defines a protocol independent YANG data model with layer The moodel defines a protocol independent YANG data model with layer
skipping to change at page 28, line 33 skipping to change at page 28, line 36
The model obeys the requirements for the ephemeral state found in the The model obeys the requirements for the ephemeral state found in the
document [I-D.draft-ietf-i2rs-ephemeral-state]. For ephemeral document [I-D.draft-ietf-i2rs-ephemeral-state]. For ephemeral
topology data that is server provided, the process tasked with topology data that is server provided, the process tasked with
maintaining topology information will load information from the maintaining topology information will load information from the
routing process (such as OSPF) into the data model without relying on routing process (such as OSPF) into the data model without relying on
a configuration datastore. a configuration datastore.
8. IANA Considerations 8. IANA Considerations
This document registers the following namespace URIs in the "IETF XML This document registers the following namespace URI in the "IETF XML
Registry" [RFC3688]: Registry" [RFC3688]:
URI: urn:ietf:params:xml:ns:yang:ietf-l3-unicast-topology URI: urn:ietf:params:xml:ns:yang:ietf-l3-unicast-topology
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A; the requested URI is an XML namespace. XML: N/A; the requested URI is an XML namespace.
URI:urn:ietf:params:xml:ns:yang:ietf-ospf-topology This document registers the following YANG module in the "YANG Module
Registrant Contact: The IESG. Names" registry [RFC6020]:
XML: N/A; the requested URI is an XML namespace.
URI:urn:ietf:params:xml:ns:yang:ietf-isis-topology
Registrant Contact: The IESG.
XML: N/A; the requested URI is an XML namespace.
This document registers the following YANG modules in the "YANG
Module Names" registry [RFC6020]:
Name: ietf-l3-unicast-topology Name: ietf-l3-unicast-topology
Namespace: urn:ietf:params:xml:ns:yang:ietf-l3-unicast-topology Namespace: urn:ietf:params:xml:ns:yang:ietf-l3-unicast-topology
Prefix: l3t Prefix: l3t
Reference: draft-ietf-i2rs-yang-l3-topology-05.txt (RFC form) Reference: draft-ietf-i2rs-yang-l3-topology-06.txt (RFC form)
Name: ietf-ospf-topology
Namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-topology
Prefix: ospft
Reference: draft-ietf-i2rs-yang-l3-topology-05.txt (RFC form)
Name: ietf-isis-topology
Namespace: urn:ietf:params:xml:ns:yang:ietf-isis-topology
Prefix: isist
Reference: draft-ietf-i2rs-yang-l3-topology-05.txt (RFC form)
9. Security Considerations 9. Security Considerations
The YANG module defined in this memo is designed to be accessed via The YANG module defined in this memo is designed to be accessed via
the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the
secure transport layer, and the mandatory-to-implement secure secure transport layer, and the mandatory-to-implement secure
transport is Secure Shell (SSH) [RFC6242]. The NETCONF access transport is Secure Shell (SSH) [RFC6242]. The NETCONF access
control model [RFC6536] provides the means to restrict access for control model [RFC6536] provides the means to restrict access for
particular NETCONF users to a pre-configured subset of all available particular NETCONF users to a pre-configured subset of all available
NETCONF protocol operations and content. NETCONF protocol operations and content.
skipping to change at page 30, line 21 skipping to change at page 30, line 13
Susan Hares, Benoit Claise, and Carl Moberg. Susan Hares, Benoit Claise, and Carl Moberg.
12. References 12. References
12.1. Normative References 12.1. Normative References
[I-D.draft-ietf-i2rs-yang-network-topo] [I-D.draft-ietf-i2rs-yang-network-topo]
Clemm, A., Medved, J., Varga, R., Bahadur, N., Clemm, A., Medved, J., Varga, R., Bahadur, N.,
Ananthakrishnan, H., and X. Liu, "A YANG Data Model for Ananthakrishnan, H., and X. Liu, "A YANG Data Model for
Network Topologies", I-D draft-ietf-i2rs-yang-network- Network Topologies", I-D draft-ietf-i2rs-yang-network-
topo-08, November 2016. topo-09, November 2016.
[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.
[RFC2328] Moy, J., "OSPF Version 2", RFC 2328, April 1998. [RFC2328] Moy, J., "OSPF Version 2", RFC 2328, April 1998.
[RFC3688] Mealling, M., "The IETF XML Registry", RFC 3688, January [RFC3688] Mealling, M., "The IETF XML Registry", RFC 3688, January
2004. 2004.
[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the
 End of changes. 41 change blocks. 
81 lines changed or deleted 58 lines changed or added

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