draft-ietf-i2rs-yang-l3-topology-07.txt   draft-ietf-i2rs-yang-l3-topology-08.txt 
Network Working Group A. Clemm Network Working Group A. Clemm
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Standards Track J. Medved Intended status: Standards Track J. Medved
Expires: July 7, 2017 Cisco Expires: July 8, 2017 Cisco
R. Varga R. Varga
Pantheon Technologies SRO Pantheon Technologies SRO
X. Liu X. Liu
Ericsson Ericsson
H. Ananthakrishnan H. Ananthakrishnan
Packet Design Packet Design
N. Bahadur N. Bahadur
Bracket Computing Bracket Computing
January 3, 2017 January 4, 2017
A YANG Data Model for Layer 3 Topologies A YANG Data Model for Layer 3 Topologies
draft-ietf-i2rs-yang-l3-topology-07.txt draft-ietf-i2rs-yang-l3-topology-08.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 40 skipping to change at page 1, line 40
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 July 7, 2017. This Internet-Draft will expire on July 8, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 18 skipping to change at page 2, line 18
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.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Definitions and Acronyms . . . . . . . . . . . . . . . . . . 3 2. Definitions and Acronyms . . . . . . . . . . . . . . . . . . 3
3. Model Structure . . . . . . . . . . . . . . . . . . . . . . . 4 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 . . . . . . . . . . . . . . . . . . . . . 15
6.1. Example 1: OSPF Topology . . . . . . . . . . . . . . . . 15 6.1. Example 1: OSPF Topology . . . . . . . . . . . . . . . . 15
6.1.1. Model Overview . . . . . . . . . . . . . . . . . . . 15 6.1.1. Model Overview . . . . . . . . . . . . . . . . . . . 15
6.1.2. OSPF Topology YANG Module . . . . . . . . . . . . . . 17 6.1.2. OSPF Topology YANG Module . . . . . . . . . . . . . . 17
6.2. Example 2: IS-IS Topology . . . . . . . . . . . . . . . . 22 6.2. Example 2: IS-IS Topology . . . . . . . . . . . . . . . . 22
6.2.1. Model Overview . . . . . . . . . . . . . . . . . . . 22 6.2.1. Model Overview . . . . . . . . . . . . . . . . . . . 22
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
skipping to change at page 7, line 28 skipping to change at page 7, line 28
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@2017-01-03.yang" <CODE BEGINS> file "ietf-l3-unicast-topology@2017-01-04.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 29 skipping to change at page 8, line 29
topologies. topologies.
Copyright (c) 2017 IETF Trust and the persons identified as Copyright (c) 2017 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-07; draft-ietf-i2rs-yang-l3-topology-08;
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-07 with RFC draft-ietf-i2rs-yang-l3-topology-08 with RFC
number when published (i.e. RFC xxxx)."; number when published (i.e. RFC xxxx).";
revision "2017-01-03" { revision "2017-01-04" {
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-07 with to draft-ietf-i2rs-yang-l3-topology-08 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-07"; "draft-ietf-i2rs-yang-l3-topology-08";
} }
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
skipping to change at page 12, line 12 skipping to change at page 12, line 12
description description
"Containing termination point attributes"; "Containing termination point attributes";
choice termination-point-type { choice termination-point-type {
description description
"Indicates the termination point type"; "Indicates the termination point type";
case ip { case ip {
leaf-list ip-address { leaf-list ip-address {
type inet:ip-address; type inet:ip-address;
description description
"IPv4 or IPv6 address"; "IPv4 or IPv6 address.";
} }
} }
case unnumbered { case unnumbered {
leaf unnumbered-id { leaf unnumbered-id {
type uint32; type uint32;
description description
"Unnumbered interface identifier"; "Unnumbered interface identifier.
The identifier will correspond to the ifIndex value
of the interface, i.e. the ifIndex value of the
ifEntry that represents the interface in
implementations where the Interfaces Group MIB
(RFC 2863) is supported.";
reference
"RFC 2863: The Interfaces Group MIB";
} }
} }
case interface-name { case interface-name {
leaf interface-name { leaf interface-name {
type string; type string;
description description
"A name of the interface. The name can (but does not "A name of the interface. The name can (but does not
have to) correspond to an interface reference of a have to) correspond to an interface reference of a
containing node's interface, i.e. the path name of a containing node's interface, i.e. the path name of a
corresponding interface data node on the containing corresponding interface data node on the containing
skipping to change at page 17, line 34 skipping to change at page 17, line 34
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
The OSPF Topology YANG Module is specified below. As mentioned, the The OSPF Topology YANG Module is specified below. As mentioned, the
module is intended as an example for how the Layer 3 Unicast 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 model can be extended to cover OSFP topologies, but it is not
normative. Accordingly, the module is not delimited with <CODE normative. Accordingly, the module is not delimited with CODE BEGINS
BEGINS> and <CODE ENDS> tags. and CODE ENDS tags.
file "example-ietf-ospf-topology@2017-01-03.yang" file "example-ietf-ospf-topology@2017-01-04.yang"
module example-ietf-ospf-topology { module example-ietf-ospf-topology {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:example-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";
} }
skipping to change at page 18, line 38 skipping to change at page 18, line 38
"This module defines a model for OSPF network topologies. "This module defines a model for OSPF network topologies.
Copyright (c) 2017 IETF Trust and the persons identified as Copyright (c) 2017 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-07; draft-ietf-i2rs-yang-l3-topology-08;
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-07 with RFC draft-ietf-i2rs-yang-l3-topology-08 with RFC
number when published (i.e. RFC xxxx)."; number when published (i.e. RFC xxxx).";
revision "2017-01-03" { revision "2017-01-04" {
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-07 with to draft-ietf-i2rs-yang-l3-topology-08 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-07"; "draft-ietf-i2rs-yang-l3-topology-08";
} }
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 23, line 36 skipping to change at page 23, line 36
Again, it should be noted that the model defined here represents a 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
The IS-IS Topology YANG Module is specified as follows. As The IS-IS Topology YANG Module is specified as follows. As
mentioned, the module is intended as an example for how the Layer 3 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 Unicast topology model can be extended to cover IS-IS topologies, but
it is not normative. Accordingly, the module is not delimited with it is not normative. Accordingly, the module is not delimited with
<CODE BEGINS> and <CODE ENDS> tags. CODE BEGINS and CODE ENDS tags.
file "example-ietf-isis-topology@2017-01-03.yang" file "example-ietf-isis-topology@2017-01-04.yang"
module example-ietf-isis-topology { module example-ietf-isis-topology {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:example-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";
} }
skipping to change at page 24, line 35 skipping to change at page 24, line 35
"This module defines a model for IS-IS network topologies. "This module defines a model for IS-IS network topologies.
Copyright (c) 2017 IETF Trust and the persons identified as Copyright (c) 2017 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-07; draft-ietf-i2rs-yang-l3-topology-08;
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-07 with RFC draft-ietf-i2rs-yang-l3-topology-08 with RFC
number when published (i.e. RFC xxxx)."; number when published (i.e. RFC xxxx).";
revision "2017-01-03" { revision "2017-01-04" {
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-07 with to draft-ietf-i2rs-yang-l3-topology-08 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-07; draft-ietf-i2rs-yang-l3-topology-08;
} }
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{
skipping to change at page 29, line 11 skipping to change at page 29, line 11
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.
This document registers the following YANG module in the "YANG Module This document registers the following YANG module in the "YANG Module
Names" registry [RFC6020]: 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-07.txt (RFC form) Reference: draft-ietf-i2rs-yang-l3-topology-08.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 29, line 48 skipping to change at page 29, line 48
The model presented in this paper was contributed to by more people The model presented in this paper was contributed to by more people
than can be listed on the author list. Additional contributors than can be listed on the author list. Additional contributors
include: include:
o Vishnu Pavan Beeram, Juniper o Vishnu Pavan Beeram, Juniper
o Igor Bryskin, Huawei o Igor Bryskin, Huawei
o Ken Gray, Cisco o Ken Gray, Cisco
o Aihua Guo, Adva Optical o Aihua Guo, Huawei
o Tom Nadeau, Brocade o Tom Nadeau, Brocade
o Tony Tkacik o Tony Tkacik
o Aleksandr Zhdankin, Cisco o Aleksandr Zhdankin, Cisco
11. Acknowledgements 11. Acknowledgements
We wish to acknowledge the helpful contributions, comments, and We wish to acknowledge the helpful contributions, comments, and
suggestions that were received from Ladislav Lhotka, Andy Bierman, suggestions that were received from Ladislav Lhotka, Andy Bierman,
skipping to change at page 30, line 28 skipping to change at page 30, line 28
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-10, January 2017. topo-10, January 2017.
[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.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000.
[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
Network Configuration Protocol (NETCONF)", RFC 6020, Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010. 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)", Bierman, "Network Configuration Protocol (NETCONF)",
RFC 6241, June 2011. RFC 6241, June 2011.
 End of changes. 30 change blocks. 
30 lines changed or deleted 40 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/