--- 1/draft-ietf-i2rs-yang-l3-topology-07.txt 2017-01-04 14:13:09.110764059 -0800 +++ 2/draft-ietf-i2rs-yang-l3-topology-08.txt 2017-01-04 14:13:09.146764434 -0800 @@ -1,27 +1,27 @@ Network Working Group A. Clemm Internet-Draft Huawei Intended status: Standards Track J. Medved -Expires: July 7, 2017 Cisco +Expires: July 8, 2017 Cisco R. Varga Pantheon Technologies SRO X. Liu Ericsson H. Ananthakrishnan Packet Design N. Bahadur Bracket Computing - January 3, 2017 + January 4, 2017 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 This document defines a YANG data model for layer 3 network topologies. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. @@ -29,21 +29,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference 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 (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -53,21 +53,21 @@ the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Definitions and Acronyms . . . . . . . . . . . . . . . . . . 3 3. Model Structure . . . . . . . . . . . . . . . . . . . . . . . 4 4. Layer 3 Unicast Topology Model Overview . . . . . . . . . . . 5 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.1. Model Overview . . . . . . . . . . . . . . . . . . . 15 6.1.2. OSPF Topology YANG Module . . . . . . . . . . . . . . 17 6.2. Example 2: IS-IS Topology . . . . . . . . . . . . . . . . 22 6.2.1. Model Overview . . . . . . . . . . . . . . . . . . . 22 6.2.2. IS-IS Topology YANG Module . . . . . . . . . . . . . 23 7. Interactions with Other YANG Modules . . . . . . . . . . . . 28 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 9. Security Considerations . . . . . . . . . . . . . . . . . . . 29 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 29 @@ -273,21 +273,21 @@ type of event, the topology from which it originated, and the affected node, or link, or prefix, or termination point. In addition, as a convenience to applications, additional data of the affected node, or link, or termination point (respectively) is included. While this makes notifications larger in volume than they would need to be, it avoids the need for subsequent retrieval of context information, which also might have changed in the meantime. 5. Layer 3 Unicast Topology YANG Module - file "ietf-l3-unicast-topology@2017-01-03.yang" + file "ietf-l3-unicast-topology@2017-01-04.yang" module ietf-l3-unicast-topology { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-l3-unicast-topology"; prefix "l3t"; import ietf-network { prefix "nd"; } import ietf-network-topology { prefix "lnk"; @@ -322,33 +322,33 @@ topologies. Copyright (c) 2017 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-l3-topology-07; + draft-ietf-i2rs-yang-l3-topology-08; see the RFC itself for full legal notices. 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)."; - revision "2017-01-03" { + revision "2017-01-04" { description "Initial revision. 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)."; reference - "draft-ietf-i2rs-yang-l3-topology-07"; + "draft-ietf-i2rs-yang-l3-topology-08"; } identity flag-identity { description "Base type for flags"; } typedef l3-event-type { type enumeration { enum "add" { description @@ -498,28 +498,35 @@ description "Containing termination point attributes"; choice termination-point-type { description "Indicates the termination point type"; case ip { leaf-list ip-address { type inet:ip-address; description - "IPv4 or IPv6 address"; + "IPv4 or IPv6 address."; } } case unnumbered { leaf unnumbered-id { type uint32; 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 { leaf interface-name { type string; description "A name of the interface. The name can (but does not have to) correspond to an interface reference of a containing node's interface, i.e. the path name of a corresponding interface data node on the containing @@ -729,24 +735,24 @@ It should be noted that the model defined here represents topology and is intended as an example. It does not define how to configure OSPF routers or interfaces. 6.1.2. OSPF Topology YANG Module The OSPF Topology YANG Module is specified below. As mentioned, the 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 and tags. + normative. Accordingly, the module is not delimited with CODE BEGINS + 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 { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:example-ietf-ospf-topology"; prefix "ospft"; import ietf-yang-types { prefix "yang"; } import ietf-network { prefix "nd"; } @@ -782,33 +788,33 @@ "This module defines a model for OSPF network topologies. Copyright (c) 2017 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-l3-topology-07; + draft-ietf-i2rs-yang-l3-topology-08; see the RFC itself for full legal notices. 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)."; - revision "2017-01-03" { + revision "2017-01-04" { description "Initial revision. 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)."; reference - "draft-ietf-i2rs-yang-l3-topology-07"; + "draft-ietf-i2rs-yang-l3-topology-08"; } typedef area-id-type { type yang:dotted-quad; description "Area ID type."; } grouping ospf-topology-type { description "Identifies the OSPF topology type."; container ospf { @@ -1016,23 +1022,23 @@ 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 configure IS-IS routers or interfaces. 6.2.2. IS-IS Topology YANG Module The IS-IS Topology YANG Module is specified as follows. As 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 - and 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 { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:example-ietf-isis-topology"; prefix "isist"; import ietf-network { prefix "nd"; } import ietf-network-topology { prefix "lnk"; } @@ -1064,33 +1070,33 @@ "This module defines a model for IS-IS network topologies. Copyright (c) 2017 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-l3-topology-07; + draft-ietf-i2rs-yang-l3-topology-08; see the RFC itself for full legal notices. 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)."; - revision "2017-01-03" { + revision "2017-01-04" { description "Initial revision. 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)."; reference - draft-ietf-i2rs-yang-l3-topology-07; + draft-ietf-i2rs-yang-l3-topology-08; } typedef iso-pseudonode-id { type string { pattern '[0-9a-fA-F]{2}'; } description "ISO pseudonode id for broadcast network."; } typedef area-address{ @@ -1282,21 +1288,21 @@ URI: urn:ietf:params:xml:ns:yang:ietf-l3-unicast-topology Registrant Contact: The IESG. XML: N/A; the requested URI is an XML namespace. This document registers the following YANG module in the "YANG Module Names" registry [RFC6020]: Name: ietf-l3-unicast-topology Namespace: urn:ietf:params:xml:ns:yang:ietf-l3-unicast-topology 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 The YANG module defined in this memo is designed to be accessed via the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) [RFC6242]. The NETCONF access control model [RFC6536] provides the means to restrict access for particular NETCONF users to a pre-configured subset of all available NETCONF protocol operations and content. @@ -1319,21 +1325,21 @@ The model presented in this paper was contributed to by more people than can be listed on the author list. Additional contributors include: o Vishnu Pavan Beeram, Juniper o Igor Bryskin, Huawei o Ken Gray, Cisco - o Aihua Guo, Adva Optical + o Aihua Guo, Huawei o Tom Nadeau, Brocade o Tony Tkacik o Aleksandr Zhdankin, Cisco 11. Acknowledgements We wish to acknowledge the helpful contributions, comments, and suggestions that were received from Ladislav Lhotka, Andy Bierman, @@ -1348,20 +1354,23 @@ Clemm, A., Medved, J., Varga, R., Bahadur, N., Ananthakrishnan, H., and X. Liu, "A YANG Data Model for Network Topologies", I-D draft-ietf-i2rs-yang-network- topo-10, January 2017. [RFC1195] Callon, R., "Use of OSI IS-IS for Routing in TCP/IP and Dual Environments", RFC 1195, December 1990. [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 2004. [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, October 2010. [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. Bierman, "Network Configuration Protocol (NETCONF)", RFC 6241, June 2011.