idnits 2.17.1 draft-hopps-lsr-yang-isis-reverse-metric-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 345 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 254 has weird spacing: '...mespace urn:i...' -- The document date (31 March 2019) is 1852 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO10589' Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group C. Hopps 3 Internet-Draft LabN Consulting, L.L.C. 4 Intended status: Standards Track 31 March 2019 5 Expires: 2 October 2019 7 YANG Data Model for the IS-IS Reverse Metric Extension 8 draft-hopps-lsr-yang-isis-reverse-metric-00 10 Abstract 12 This document defines a YANG module for managing the reverse metric 13 extension to the the intermediate system to intermediate system 14 routeing protocol. 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at https://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on 2 October 2019. 33 Copyright Notice 35 Copyright (c) 2019 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 40 license-info) in effect on the date of publication of this document. 41 Please review these documents carefully, as they describe your rights 42 and restrictions with respect to this document. Code Components 43 extracted from this document must include Simplified BSD License text 44 as described in Section 4.e of the Trust Legal Provisions and are 45 provided without warranty as described in the Simplified BSD License. 47 Table of Contents 49 1. Introduction 50 2. YANG Management 51 2.1. YANG Tree 52 2.2. YANG Module 53 3. IANA Considerations 54 3.1. Updates to the IETF XML Registry 55 3.2. Updates to the YANG Module Names Registry 56 4. Security Considerations 57 5. Normative References 58 6. Informative References 59 Author's Address 61 1. Introduction 63 This document defines a YANG module for managing the reverse metric 64 extension to the intermediate system to intermediate system routeing 65 protocol (IS-IS) [RFC8500], [ISO10589]. Please refer to [RFC8500] 66 for the description and definition of the functionality managed by 67 this module. 69 The YANG data model described in this document conforms to the 70 Network Management Datastore Architecture defined in [RFC8342]. 72 2. YANG Management 74 2.1. YANG Tree 76 The following is the YANG tree diagram ([RFC8340]) for the IS-IS 77 reverse metric extension additions. 79 module: ietf-isis-reverse-metric 80 augment /rt:routing/rt:control-plane-protocols 81 /rt:control-plane-protocol/isis:isis/isis:interfaces 82 /isis:interface: 83 +--rw reverse-metric 84 +--rw reverse-metric 85 | +--rw metric? isis:wide-metric 86 | +--rw flags? bits 87 +--rw exclude-te-metric? boolean 88 augment /rt:routing/rt:control-plane-protocols 89 /rt:control-plane-protocol/isis:isis/isis:interfaces 90 /isis:interface/isis:adjacencies/isis:adjacency: 91 +--ro reverse-metric 92 | +--ro metric? isis:wide-metric 93 | +--ro flags? bits 94 +--ro te-metric? uint32 96 2.2. YANG Module 98 The following is the YANG module for managing the IS-IS reverse 99 metric functionality defined in [RFC8500]. 101 file "ietf-isis-reverse-metric@2019-03-31.yang" 102 module ietf-isis-reverse-metric { 103 yang-version 1.1; 104 namespace "urn:ietf:params:xml:ns:yang:ietf-isis-reverse-metric"; 105 prefix isis-rmetric; 107 import ietf-isis { prefix isis; } 108 import ietf-routing { prefix "rt"; } 110 organization 111 "IETF NETMOD Working Group (NETMOD)"; 112 contact 113 "WG Web: 114 WG List: 116 Author: Christian Hopps 117 "; 119 // RFC Ed.: replace XXXX with actual RFC number and 120 // remove this note. 122 description 123 "This module defines the configuration and operational state for 124 managing the IS-IS reverse metric functionality [RFC8500]. 126 Copyright (c) 2019 IETF Trust and the persons identified as 127 authors of the code. All rights reserved. 129 Redistribution and use in source and binary forms, with or 130 without modification, is permitted pursuant to, and subject to 131 the license terms contained in, the Simplified BSD License set 132 forth in Section 4.c of the IETF Trust's Legal Provisions 133 Relating to IETF Documents 134 (https://trustee.ietf.org/license-info). 136 This version of this YANG module is part of RFC XXXX 137 (https://tools.ietf.org/html/rfcXXXX); see the RFC itself for 138 full legal notices."; 140 revision 2019-03-31 { 141 description "Initial Revision"; 142 reference "RFC XXXX: YANG IS-IS Reverse Metric"; 143 } 145 grouping reverse-metric-data { 146 description "IS-IS reverse metric data."; 147 container reverse-metric { 148 description "IS-IS reverse metric data."; 149 leaf metric { 150 type isis:wide-metric; 151 description "The reverse metric value."; 152 } 153 leaf flags { 154 type bits { 155 bit whole-lan { 156 position 0; 157 description 158 "The 'whole LAN' or W-bit. If true then a DIS 159 processing this reverse metric will add the metric 160 value to all the nodes it advertises in the 161 pseudo-node LSP for this interface. Otherwise it will 162 only increment the metric for the advertising node in 163 the pseudo-node LSP for this interface."; 164 } 165 bit allow-unreachable { 166 position 1; 167 description 168 "The 'allow-unreachable' or U-bit. If true it allows 169 the neighbor to increment the overall metric up to 170 2^24-1 rather than the lesser maximum of 2^24-2, and 171 if done will cause traffic to stop using rather than 172 avoid using the interface."; 173 } 174 } 175 description "The reverse metric flag values."; 176 } 177 } 178 } 180 grouping tlv16-reverse-metric { 181 description "IS-IS reverse metric TLV data."; 182 uses reverse-metric-data; 183 leaf te-metric { 184 type uint32; 185 description "The TE metric value from the sub-TLV if present."; 186 } 187 } 189 augment "/rt:routing/rt:control-plane-protocols/" 190 +"rt:control-plane-protocol/" 191 +"isis:isis/isis:interfaces/isis:interface" { 192 when "rt:type = 'isis:isis'" { 193 description 194 "This augment is only valid when routing protocol instance 195 type is 'isis'."; 196 } 198 description 199 "The reverse metric configuration for an interface."; 201 container reverse-metric { 202 description "Announce a reverse metric to neighbors."; 203 uses reverse-metric-data; 204 leaf exclude-te-metric { 205 type boolean; 206 default false; 207 description 208 "If true and there is a TE metric defined for this 209 interface then do not send the TE metric sub-TLV in the 210 reverse metric TLV."; 211 } 212 } 213 } 214 augment "/rt:routing/rt:control-plane-protocols/" 215 +"rt:control-plane-protocol/" 216 +"isis:isis/isis:interfaces/isis:interface/" 217 +"isis:adjacencies/isis:adjacency" { 218 when "rt:type = 'isis:isis'" { 219 description 220 "This augment is only valid when routing protocol instance 221 type is 'isis'"; 222 } 224 description 225 "The reverse metric state advertised by a neighbor."; 226 uses tlv16-reverse-metric; 227 } 228 } 229 231 3. IANA Considerations 233 3.1. Updates to the IETF XML Registry 235 This document registers a URI in the "IETF XML Registry" [RFC3688]. 236 Following the format in [RFC3688], the following registration has 237 been made: 239 URI urn:ietf:params:xml:ns:yang:ietf-isis-reverse- 240 metric 242 Registrant Contact The IESG. 244 XML N/A; the requested URI is an XML namespace. 246 3.2. Updates to the YANG Module Names Registry 248 This document registers one YANG module in the "YANG Module Names" 249 registry [RFC6020]. Following the format in [RFC6020], the following 250 registration has been made: 252 name ietf-isis-reverse-metric 254 namespace urn:ietf:params:xml:ns:yang:ietf-isis-reverse-metric 256 prefix isis-rmetric 258 reference RFC XXXX (RFC Ed.: replace XXX with actual RFC number and 259 remove this note.) 261 4. Security Considerations 263 The YANG module specified in this document defines a schema for data 264 that is designed to be accessed via network management protocols such 265 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 266 is the secure transport layer, and the mandatory-to-implement secure 267 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 268 is HTTPS, and the mandatory-to-implement secure transport is TLS 269 [RFC8446]. 271 The Network Configuration Access Control Model (NACM) [RFC8341] 272 provides the means to restrict access for particular NETCONF or 273 RESTCONF users to a preconfigured subset of all available NETCONF or 274 RESTCONF protocol operations and content. 276 The YANG module defined in this document can enable, disable and 277 modify the behavior of metrics used by routing. For the security 278 implications regarding these types of changes consult the [RFC8500] 279 which defines the functionality. 281 5. Normative References 283 [ISO10589] International Organization for Standardization, 284 "Intermediate system to intermediate system intra-domain- 285 routing routine information exchange protocol for use in 286 conjunction with the protocol for providing the 287 connectionless-mode Network Service (ISO 8473)", 288 ISO Standard 10589, 1992. 290 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 291 DOI 10.17487/RFC3688, January 2004, 292 . 294 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 295 the Network Configuration Protocol (NETCONF)", RFC 6020, 296 DOI 10.17487/RFC6020, October 2010, 297 . 299 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 300 and A. Bierman, Ed., "Network Configuration Protocol 301 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 302 . 304 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 305 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 306 . 308 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 309 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 310 . 312 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 313 Access Control Model", STD 91, RFC 8341, 314 DOI 10.17487/RFC8341, March 2018, 315 . 317 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 318 and R. Wilton, "Network Management Datastore Architecture 319 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 320 . 322 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 323 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 324 . 326 [RFC8500] Shen, N., Amante, S., and M. Abrahamsson, "IS-IS Routing 327 with Reverse Metric", RFC 8500, DOI 10.17487/RFC8500, 328 February 2019, . 330 6. Informative References 332 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 333 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 334 . 336 Author's Address 338 Christian Hopps 339 LabN Consulting, L.L.C. 341 Email: chopps@chopps.org