--- 1/draft-ietf-i2rs-yang-network-topo-09.txt 2017-01-03 01:13:08.595074603 -0800 +++ 2/draft-ietf-i2rs-yang-network-topo-10.txt 2017-01-03 01:13:08.663076162 -0800 @@ -1,27 +1,27 @@ Network Working Group A. Clemm -Internet-Draft Sympotech +Internet-Draft Huawei Intended status: Standards Track J. Medved -Expires: June 3, 2017 Cisco +Expires: July 7, 2017 Cisco R. Varga Pantheon Technologies SRO N. Bahadur Bracket Computing H. Ananthakrishnan Packet Design X. Liu Ericsson - November 30, 2016 + January 3, 2017 A Data Model for Network Topologies - draft-ietf-i2rs-yang-network-topo-09.txt + draft-ietf-i2rs-yang-network-topo-10.txt Abstract This document defines an abstract (generic) YANG data model for network/service topologies and inventories. The model serves as a base model which is augmented with technology-specific details in other, more specific topology and inventory models. Status of This Memo @@ -31,25 +31,25 @@ 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 June 3, 2017. + This Internet-Draft will expire on July 7, 2017. Copyright Notice - Copyright (c) 2016 IETF Trust and the persons identified as the + 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 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as @@ -764,39 +764,39 @@ topology data is integrated into a larger, more complex system. 5. Interactions with Other YANG Modules The model makes use of data types that have been defined in [RFC6991]. This is a protocol independent yang model with topology information. It is separate from and not linked with data models that are used to configure routing protocols or routing information. This includes - e.g. model "ietf-routing" [RFC8022] and model "ietf-fb-rib" - [I-D.draft-acee-rtgwg-yang-rib-extend]. + e.g. model "ietf-routing" [RFC8022]. The model obeys the requirements for the ephemeral state found in the document [I-D.draft-ietf-i2rs-ephemeral-state]. For ephemeral topology data that is server provided, the process tasked with maintaining topology information will load information from the routing process (such as OSPF) into the data model without relying on a configuration datastore. 6. YANG Modules 6.1. Defining the Abstract Network: network.yang - file "ietf-network@2016-11-30.yang" + file "ietf-network@2017-01-03.yang" module ietf-network { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-network"; prefix nd; + import ietf-inet-types { prefix inet; } organization "IETF I2RS (Interface to the Routing System) Working Group"; contact "WG Web: WG List: @@ -801,21 +801,21 @@ "WG Web: WG List: WG Chair: Susan Hares WG Chair: Russ White Editor: Alexander Clemm - + Editor: Jan Medved Editor: Robert Varga Editor: Nitin Bahadur @@ -823,46 +823,45 @@ Editor: Xufeng Liu "; description "This module defines a common base model for a collection of nodes in a network. Node definitions are further used in network topologies and inventories. - Copyright (c) 2016 IETF Trust and the persons identified as + 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-network-topo-09; + draft-ietf-i2rs-yang-network-topo-10; see the RFC itself for full legal notices. NOTE TO RFC EDITOR: Please replace above reference to - draft-ietf-i2rs-yang-network-topo-09 with RFC + draft-ietf-i2rs-yang-network-topo-10 with RFC number when published (i.e. RFC xxxx)."; - revision 2016-11-30 { + revision 2017-01-03 { description "Initial revision. NOTE TO RFC EDITOR: Please replace the following reference - to draft-ietf-i2rs-yang-network-topo-09 with + to draft-ietf-i2rs-yang-network-topo-10 with RFC number when published (i.e. RFC xxxx)."; reference - "draft-ietf-i2rs-yang-network-topo-09"; + "draft-ietf-i2rs-yang-network-topo-10"; } typedef node-id { type inet:uri; description "Identifier for a node. The precise structure of the node-id will be up to the implementation. Some implementations MAY for example, pick a uri that includes the network-id as part of the path. The identifier SHOULD be chosen such that the same node in a real network topology will always be @@ -1010,21 +1009,21 @@ } } } } } 6.2. Creating Abstract Network Topology: network-topology.yang - file "ietf-network-topology@2016-11-30.yang" + file "ietf-network-topology@2017-01-03.yang" module ietf-network-topology { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-network-topology"; prefix lnk; import ietf-inet-types { prefix inet; } import ietf-network { prefix nd; @@ -1037,21 +1036,21 @@ "WG Web: WG List: WG Chair: Susan Hares WG Chair: Russ White Editor: Alexander Clemm - + Editor: Jan Medved Editor: Robert Varga Editor: Nitin Bahadur @@ -1059,46 +1058,46 @@ Editor: Xufeng Liu "; description "This module defines a common base model for network topology, augmenting the base network model with links to connect nodes, as well as termination points to terminate links on nodes. - Copyright (c) 2016 IETF Trust and the persons identified as + 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-network-topo-09; + draft-ietf-i2rs-yang-network-topo-10; see the RFC itself for full legal notices. NOTE TO RFC EDITOR: Please replace above reference to - draft-ietf-i2rs-yang-network-topo-09 with RFC + draft-ietf-i2rs-yang-network-topo-10 with RFC number when published (i.e. RFC xxxx)."; - revision 2016-11-30 { + revision 2017-01-03 { description "Initial revision. NOTE TO RFC EDITOR: Please replace the following reference - to draft-ietf-i2rs-yang-network-topo-09 with + to draft-ietf-i2rs-yang-network-topo-10 with RFC number when published (i.e. RFC xxxx)."; reference - "draft-ietf-i2rs-yang-network-topo-09"; + "draft-ietf-i2rs-yang-network-topo-10"; } typedef link-id { type inet:uri; description "An identifier for a link in a topology. The precise structure of the link-id will be up to the implementation. The identifier SHOULD be chosen such that the same link in a real network topology will always be identified through the @@ -1167,24 +1166,21 @@ description "A network link connects a local (source) node and a remote (destination) node via a set of the respective node's termination points. It is possible to have several links between the same source and destination nodes. Likewise, a link could potentially be re-homed between termination points. Therefore, in order to ensure that we would always know to distinguish between links, every link is identified by a dedicated link identifier. Note that a link models a - point-to-point link, not a multipoint link. - Layering dependencies on links in underlay topologies are - not represented, as the layering information of nodes and of - termination points is sufficient."; + point-to-point link, not a multipoint link."; container source { description "This container holds the logical source of a particular link."; leaf source-node { type leafref { path "../../../nd:node/nd:node-id"; require-instance false; } description @@ -1338,26 +1332,26 @@ URI:urn:ietf:params:xml:ns:yang:ietf-network-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-network Namespace: urn:ietf:params:xml:ns:yang:ietf-network Prefix: nd - Reference: draft-ietf-i2rs-yang-network-topo-09.txt (RFC form) + Reference: draft-ietf-i2rs-yang-network-topo-10.txt (RFC form) Name: ietf-network-topology Namespace: urn:ietf:params:xml:ns:yang:ietf-network-topology Prefix: lnk - Reference: draft-ietf-i2rs-yang-network-topo-09.txt (RFC form) + Reference: draft-ietf-i2rs-yang-network-topo-10.txt (RFC form) 8. 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. @@ -1424,25 +1418,20 @@ 2012. [RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991, July 2013. [RFC7950] Bjorklund, M., "The YANG 1.1 Data Modeling Language", RFC 7950, August 2016. 11.2. Informative References - [I-D.draft-acee-rtgwg-yang-rib-extend] - Lindem, A. and Y. Qu, "YANG Data Model for RIB - Extensions", I-D draft-acee-rtgwg-yang-rib-extend-02, - October 2016. - [I-D.draft-ietf-i2rs-ephemeral-state] Haas, J. and S. Hares, "I2RS Ephemeral State Requirements", I-D draft-ietf-i2rs-ephemeral-state-22, November 2016. [I-D.draft-ietf-i2rs-usecase-reqs-summary] Hares, S. and M. Chen, "Summary of I2RS Use Case Requirements", I-D draft-ietf-i2rs-usecase-reqs-summary- 03, November 2016. @@ -1466,23 +1455,23 @@ [RFC7952] Lhotka, L., "Defining and Using Metadata with YANG", RFC 7952, August 2016. [RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing Management", RFC 8022, November 2016. Authors' Addresses Alexander Clemm - Sympotech + Huawei - EMail: alex@sympotech.com + EMail: ludwig@clemm.org Jan Medved Cisco EMail: jmedved@cisco.com Robert Varga Pantheon Technologies SRO EMail: robert.varga@pantheon.sk