--- 1/draft-ietf-i2rs-yang-l3-topology-08.txt 2017-06-25 23:13:09.374170092 -0700 +++ 2/draft-ietf-i2rs-yang-l3-topology-09.txt 2017-06-25 23:13:09.430171420 -0700 @@ -1,27 +1,27 @@ Network Working Group A. Clemm Internet-Draft Huawei Intended status: Standards Track J. Medved -Expires: July 8, 2017 Cisco +Expires: December 28, 2017 Cisco R. Varga Pantheon Technologies SRO X. Liu Ericsson H. Ananthakrishnan Packet Design N. Bahadur Bracket Computing - January 4, 2017 + June 26, 2017 A YANG Data Model for Layer 3 Topologies - draft-ietf-i2rs-yang-l3-topology-08.txt + draft-ietf-i2rs-yang-l3-topology-09.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 8, 2017. + This Internet-Draft will expire on December 28, 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 @@ -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-04.yang" + file "ietf-l3-unicast-topology@2017-06-26.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-08; + draft-ietf-i2rs-yang-l3-topology-09; see the RFC itself for full legal notices. NOTE TO RFC EDITOR: Please replace above reference to - draft-ietf-i2rs-yang-l3-topology-08 with RFC + draft-ietf-i2rs-yang-l3-topology-09 with RFC number when published (i.e. RFC xxxx)."; - revision "2017-01-04" { + revision "2017-06-26" { description "Initial revision. NOTE TO RFC EDITOR: Please replace the following reference - to draft-ietf-i2rs-yang-l3-topology-08 with + to draft-ietf-i2rs-yang-l3-topology-09 with RFC number when published (i.e. RFC xxxx)."; reference - "draft-ietf-i2rs-yang-l3-topology-08"; + "draft-ietf-i2rs-yang-l3-topology-09"; } identity flag-identity { description "Base type for flags"; } typedef l3-event-type { type enumeration { enum "add" { description @@ -738,21 +738,21 @@ 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 CODE BEGINS and CODE ENDS tags. - file "example-ietf-ospf-topology@2017-01-04.yang" + file "example-ietf-ospf-topology@2017-06-26.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"; } @@ -788,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-08; + draft-ietf-i2rs-yang-l3-topology-09; see the RFC itself for full legal notices. NOTE TO RFC EDITOR: Please replace above reference to - draft-ietf-i2rs-yang-l3-topology-08 with RFC + draft-ietf-i2rs-yang-l3-topology-09 with RFC number when published (i.e. RFC xxxx)."; - revision "2017-01-04" { + revision "2017-06-26" { description "Initial revision. NOTE TO RFC EDITOR: Please replace the following reference - to draft-ietf-i2rs-yang-l3-topology-08 with + to draft-ietf-i2rs-yang-l3-topology-09 with RFC number when published (i.e. RFC xxxx)."; reference - "draft-ietf-i2rs-yang-l3-topology-08"; + "draft-ietf-i2rs-yang-l3-topology-09"; } typedef area-id-type { type yang:dotted-quad; description "Area ID type."; } grouping ospf-topology-type { description "Identifies the OSPF topology type."; container ospf { @@ -1024,21 +1024,21 @@ 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 CODE BEGINS and CODE ENDS tags. - file "example-ietf-isis-topology@2017-01-04.yang" + file "example-ietf-isis-topology@2017-06-26.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"; } @@ -1048,21 +1048,21 @@ organization "IETF I2RS (Interface to the Routing System) Working Group"; contact "WG Web: WG List: WG Chair: Susan Hares WG Chair: Russ White Editor: Alexander Clemm - + Editor: Jan Medved Editor: Robert Varga Editor: Xufeng Liu Editor: Nitin Bahadur Editor: Hariharan Ananthakrishnan "; @@ -1075,21 +1075,21 @@ 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-08; see the RFC itself for full legal notices. NOTE TO RFC EDITOR: Please replace above reference to draft-ietf-i2rs-yang-l3-topology-08 with RFC number when published (i.e. RFC xxxx)."; - revision "2017-01-04" { + revision "2017-06-26" { description "Initial revision. NOTE TO RFC EDITOR: Please replace the following reference to draft-ietf-i2rs-yang-l3-topology-08 with RFC number when published (i.e. RFC xxxx)."; reference draft-ietf-i2rs-yang-l3-topology-08; } typedef iso-pseudonode-id { type string { @@ -1347,21 +1347,21 @@ Susan Hares, Benoit Claise, and Carl Moberg. 12. References 12.1. Normative References [I-D.draft-ietf-i2rs-yang-network-topo] 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. + topo-13, June 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 @@ -1400,22 +1400,22 @@ Requirements", I-D draft-ietf-i2rs-ephemeral-state-23, 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. [I-D.draft-ietf-teas-yang-te-topo] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and - O. Gonzelz De Dios, "YANG Data Model for TE Topologies", - I-D draft-ietf-teas-yang-te-topo-06, October 2016. + O. Gonzalez De Dios, "YANG Data Model for TE Topologies", + I-D draft-ietf-teas-yang-te-topo-09, June 2017. [RFC7223] Bjorklund, M., "A YANG Data Model for Routing Management", RFC 7223, May 2014. [RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing Management", RFC 8022, November 2016. Authors' Addresses Alexander Clemm