--- 1/draft-ietf-i2rs-yang-l3-topology-14.txt 2017-12-14 09:13:37.189456684 -0800 +++ 2/draft-ietf-i2rs-yang-l3-topology-15.txt 2017-12-14 09:13:37.253458201 -0800 @@ -1,27 +1,27 @@ Network Working Group A. Clemm Internet-Draft Huawei Intended status: Standards Track J. Medved -Expires: June 16, 2018 Cisco +Expires: June 17, 2018 Cisco R. Varga Pantheon Technologies SRO X. Liu Jabil H. Ananthakrishnan Packet Design N. Bahadur Bracket Computing - December 13, 2017 + December 14, 2017 A YANG Data Model for Layer 3 Topologies - draft-ietf-i2rs-yang-l3-topology-14.txt + draft-ietf-i2rs-yang-l3-topology-15.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 https://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 16, 2018. + This Internet-Draft will expire on June 17, 2018. 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 (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -177,33 +177,34 @@ | +-----------------------+ | | | ietf-network | | | +----------^------------+ | | | | | +-----------------------+ | | | ietf-network-topology | | | +----------+------------+ | +-------------^---------------+ | | - +-----------^-------------+ - | L3-UNICAST-TOPOLOGY | - +----+------^--------+----+ + +------------^-------------+ + | ietf-l3-unicast-topology | + +------------^-------------+ | | - +-------^-------+ - | ospf-topology | - +---------------+ + +-----------^-----------+ + | example-ospf-topology | + +-----------------------+ Figure 1: Overall model structure YANG modules "ietf-network" and "ietf-network-topology" collectively - define the basic network topology model. YANG module "ietf-l3- + define the basic network topology model + [I-D.draft-ietf-i2rs-yang-network-topo]. YANG module "ietf-l3- unicast-topology" augments those models with additional definitions needed to represent Layer 3 Unicast topologies. This module in turn can be augmented by YANG modules with additional definitions for specific types of Layer 3 Unicast topologies, such as OSPF and for IS-IS topologies. The YANG modules ietf-network and ietf-network-topology are designed to be used in conjunction with implementations that support the Network Management Datastore Architecture (NMDA) defined in [I-D.draft-ietf-netmod-revised-datastores]. Accordingly, the same is @@ -287,21 +288,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. 6. Layer 3 Unicast Topology YANG Module - file "ietf-l3-unicast-topology@2017-12-13.yang" + file "ietf-l3-unicast-topology@2017-12-14.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 "nw"; } import ietf-network-topology { prefix "nt"; @@ -332,33 +333,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-14; + draft-ietf-i2rs-yang-l3-topology-15; see the RFC itself for full legal notices. NOTE TO RFC EDITOR: Please replace above reference to - draft-ietf-i2rs-yang-l3-topology-14 with RFC + draft-ietf-i2rs-yang-l3-topology-15 with RFC number when published (i.e. RFC xxxx)."; - revision "2017-12-13" { + revision "2017-12-14" { description "Initial revision. NOTE TO RFC EDITOR: Please replace the following reference - to draft-ietf-i2rs-yang-l3-topology-14 with + to draft-ietf-i2rs-yang-l3-topology-15 with RFC number when published (i.e. RFC xxxx)."; reference - "draft-ietf-i2rs-yang-l3-topology-14"; + "draft-ietf-i2rs-yang-l3-topology-15"; } identity flag-identity { description "Base type for flags"; } typedef l3-event-type { type enumeration { enum "add" { description @@ -688,26 +689,26 @@ URI: urn:ietf:params:xml:ns:yang:ietf-l3-unicast-topology-state 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 Namespace: urn:ietf:params:xml:ns:yang:ietf-l3-unicast-topology Prefix: l3t - Reference: draft-ietf-i2rs-yang-l3-topology-14.txt (RFC form) + Reference: draft-ietf-i2rs-yang-l3-topology-15.txt (RFC form) Name: ietf-l3-unicast-topology-state Namespace: urn:ietf:params:xml:ns:yang:ietf-l3-unicast-topology-state Prefix: l3t-s - Reference: draft-ietf-i2rs-yang-l3-topology-14.txt (RFC form) + Reference: draft-ietf-i2rs-yang-l3-topology-15.txt (RFC form) 9. Security Considerations The YANG module defined in this document is designed to be accessed via network management protocols such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS [RFC5246]. @@ -901,21 +902,21 @@ Like ietf-network-state and ietf-network-topology-state, ietf-l3- unicast-topology SHOULD NOT be supported by implementations that support NMDA. It is for this reason that the module is defined in the Appendix. The definition of the module follows below. As the structure of the module mirrors that of its underlying module, the YANG tree is not depicted separately. - file "ietf-l3-unicast-topology-state@2017-12-13.yang" + file "ietf-l3-unicast-topology-state@2017-12-14.yang" module ietf-l3-unicast-topology-state { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-l3-unicast-topology-state"; prefix "l3t-s"; import ietf-network-state { prefix "nw-s"; } import ietf-network-topology-state { prefix "nt-s"; @@ -954,33 +955,33 @@ 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-14; + draft-ietf-i2rs-yang-l3-topology-15; see the RFC itself for full legal notices. NOTE TO RFC EDITOR: Please replace above reference to - draft-ietf-i2rs-yang-l3-topology-14 with RFC + draft-ietf-i2rs-yang-l3-topology-15 with RFC number when published (i.e. RFC xxxx)."; - revision "2017-12-13" { + revision "2017-12-14" { description "Initial revision. NOTE TO RFC EDITOR: Please replace the following reference - to draft-ietf-i2rs-yang-l3-topology-14 with + to draft-ietf-i2rs-yang-l3-topology-15 with RFC number when published (i.e. RFC xxxx)."; reference - "draft-ietf-i2rs-yang-l3-topology-14"; + "draft-ietf-i2rs-yang-l3-topology-15"; } augment "/nw-s:networks/nw-s:network/nw-s:network-types" { description "Introduce new network type for L3 unicast topology"; uses l3t:l3-unicast-topology-type; } augment "/nw-s:networks/nw-s:network" { when "nw-s:network-types/l3t-s:l3-unicast-topology" { description "Augmentation parameters apply only for networks with @@ -1085,24 +1086,24 @@ illustrates how the general topology model can be refined across multiple levels. It does not constitute full-fledged OSPF topology model which may be more comprehensive and refined than the model that is described here. B.1. Example OSPF Topology B.1.1. Model Overview The following model shows how the Layer 3 Unicast topology model can - be extended to cover OSFP topologies. For this purpose, a set of - augmentations are introduced in a separate YANG module, "example- - ospf-topology", whose structure is depicted in the following diagram. - As before, the notation syntax follows + be extended, in this case to cover OSFP topologies. For this + purpose, a set of augmentations are introduced in a separate YANG + module, "example-ospf-topology", whose structure is depicted in the + following diagram. As before, the notation syntax follows [I-D.draft-ietf-netmod-yang-tree-diagrams]. module: example-ospf-topology augment /nw:networks/nw:network/nw:network-types/l3t:l3-unicast-topology: +--rw ospf! augment /nw:networks/nw:network/l3t:l3-topology-attributes: +--rw ospf-topology-attributes +--rw area-id? area-id-type augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes: +--rw ospf-node-attributes @@ -1158,21 +1159,21 @@ OSPF routers or interfaces. B.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 CODE BEGINS and CODE ENDS tags. - file "example-ospf-topology@2017-12-13.yang" + file "example-ospf-topology@2017-12-14.yang" module example-ospf-topology { yang-version 1.1; namespace "urn:example:example-ospf-topology"; prefix "ex-ospft"; import ietf-yang-types { prefix "yang"; } import ietf-network { prefix "nw"; }