--- 1/draft-ietf-lsr-yang-isis-reverse-metric-01.txt 2020-12-18 11:13:19.621267610 -0800 +++ 2/draft-ietf-lsr-yang-isis-reverse-metric-02.txt 2020-12-18 11:13:19.649268318 -0800 @@ -1,18 +1,18 @@ Network Working Group C. Hopps Internet-Draft LabN Consulting, L.L.C. -Intended status: Standards Track 28 July 2020 -Expires: 29 January 2021 +Intended status: Standards Track 18 December 2020 +Expires: 21 June 2021 YANG Module for IS-IS Reverse Metric - draft-ietf-lsr-yang-isis-reverse-metric-01 + draft-ietf-lsr-yang-isis-reverse-metric-02 Abstract This document defines a YANG module for managing the reverse metric extension to the the intermediate system to intermediate system routeing protocol. Status of This Memo This Internet-Draft is submitted in full conformance with the @@ -21,21 +21,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 29 January 2021. + This Internet-Draft will expire on 21 June 2021. Copyright Notice Copyright (c) 2020 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 carefully, as they describe your rights @@ -118,21 +118,21 @@ | +--ro whole-lan? boolean | +--ro allow-unreachable? boolean +--ro te-metric? uint32 2.2. YANG Module The following is the YANG module for managing the IS-IS reverse metric functionality defined in [RFC8500]. It imports modules from the following RFCs: [RFC8349], [I-D.ietf-isis-yang-isis-cfg]. - file "ietf-isis-reverse-metric@2020-07-28.yang" + file "ietf-isis-reverse-metric@2020-12-18.yang" module ietf-isis-reverse-metric { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-isis-reverse-metric"; prefix isis-rmetric; import ietf-routing { prefix rt; reference "RFC8349: A YANG Data Model for Routing Management (NMDA Version)"; } @@ -167,21 +167,21 @@ 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 (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX (https://tools.ietf.org/html/rfcXXXX); see the RFC itself for full legal notices."; - revision 2020-07-28 { + revision 2020-12-18 { description "Initial Revision"; reference "RFC XXXX: YANG IS-IS Reverse Metric"; } grouping reverse-metric-data { description "IS-IS reverse metric data."; leaf metric { type isis:wide-metric; description "The reverse metric value."; reference "RFC8500, Section 2"; @@ -237,21 +237,21 @@ type uint32; description "The TE metric value from the sub-TLV if present."; reference "RFC8500, Section 3.5"; } } } augment "/rt:routing/rt:control-plane-protocols/" +"rt:control-plane-protocol/" +"isis:isis" { - when "../rt:type = 'isis:isis'" { + when "derived-from-or-self(../rt:type, 'isis:isis')" { description "This augment is only valid when routing protocol instance type is 'isis'."; } description "The reverse metric configuration for an IS-IS instance."; container reverse-metric { description "Global reverse metric configuration."; @@ -262,21 +262,21 @@ "Enable handling of reverse metric announcements from neighbors. By default reverse metric handling is disabled and must be explicitly enabled through this configuration."; } } } augment "/rt:routing/rt:control-plane-protocols/" +"rt:control-plane-protocol/" +"isis:isis/isis:interfaces/isis:interface" { - when "../../../rt:type = 'isis:isis'" { + when "derived-from-or-self(../../../rt:type, 'isis:isis')" { description "This augment is only valid when routing protocol instance type is 'isis'."; } description "The reverse metric configuration for an interface."; container reverse-metric { description "Announce a reverse metric to neighbors."; @@ -288,42 +288,44 @@ container level-2 { description "Announce a reverse metric to level-2 neighbors."; uses reverse-metric-if-config-data; } } } augment "/rt:routing/rt:control-plane-protocols/" +"rt:control-plane-protocol/" +"isis:isis/isis:interfaces/isis:interface/" +"isis:adjacencies/isis:adjacency" { - when "../../../../../rt:type = 'isis:isis'" { + when "derived-from-or-self(../../../../../rt:type, 'isis:isis')" { description "This augment is only valid when routing protocol instance type is 'isis'"; } description "The reverse metric state advertised by an adjacency."; uses tlv16-reverse-metric; } } 3. IANA Considerations 3.1. Updates to the IETF XML Registry This document registers a URI in the "IETF XML Registry" [RFC3688]. Following the format in [RFC3688], the following registration has been made: - URI urn:ietf:params:xml:ns:yang:ietf-isis-reverse-metric + URI urn:ietf:params:xml:ns:yang:ietf-isis-reverse- + metric + Registrant Contact The IESG. XML N/A; the requested URI is an XML namespace. 3.2. Updates to the YANG Module Names Registry This document registers one YANG module in the "YANG Module Names" registry [RFC6020]. Following the format in [RFC6020], the following registration has been made: @@ -416,20 +418,27 @@ "isis:adjacencies/isis:adjacency/" + "isis-rmetric:reverse-metric" - /isis-rmetric:metric - /isis-rmetric:flags/isis-rmetric:whole-lan - /isis-rmetric:flags/isis-rmetric:allow-unreachable - /isis-rmetric:te-metric 5. Normative References + [I-D.ietf-isis-yang-isis-cfg] + Litkowski, S., Yeung, D., Lindem, A., Zhang, Z., and L. + Lhotka, "YANG Data Model for IS-IS Protocol", draft-ietf- + isis-yang-isis-cfg-42 (work in progress), 15 October 2019, + . + [ISO10589] International Organization for Standardization, "Intermediate system to intermediate system intra-domain- routing routine information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode Network Service (ISO 8473)", ISO Standard 10589, 1992. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . @@ -468,38 +477,31 @@ . [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, . [RFC8500] Shen, N., Amante, S., and M. Abrahamsson, "IS-IS Routing with Reverse Metric", RFC 8500, DOI 10.17487/RFC8500, February 2019, . - [I-D.ietf-isis-yang-isis-cfg] - Litkowski, S., Yeung, D., Lindem, A., Zhang, Z., and L. - Lhotka, "YANG Data Model for IS-IS Protocol", Work in - Progress, Internet-Draft, draft-ietf-isis-yang-isis-cfg- - 42, 15 October 2019, . - 6. Informative References [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, . Appendix A. Examples A.1. Example Enable XML - Below is an example of YANG XML data to enable reverse metric + Below is an example of XML instance data to enable reverse metric processing. isis:isis default @@ -510,22 +512,22 @@ Figure 1: Example XML data to enable reverse metric processing. A.2. Example Use XML - Below is an example of YANG XML data for the ietf-isis-reverse-metric - module. + Below is an example of XML instance data for the ietf-isis-reverse- + metric module. eth0 ianaift:ethernetCsmacd Figure 2: Example XML data for ietf-isis-reverse-metric module. A.3. Example JSON - Below is an example of YANG XML data for the ietf-isis-reverse-metric - module. + Below is an example of JSON instance data for the ietf-isis-reverse- + metric module. { "ietf-interfaces:interfaces": { "interface": [ { "name": "eth0", "type": "iana-if-type:ethernetCsmacd" } ] },