idnits 2.17.1 draft-acee-lsr-isis-yang-augmentation-v1-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: ---------------------------------------------------------------------------- No issues found here. 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 == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (November 3, 2019) is 1626 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC5329' is defined on line 247, but no explicit reference was found in the text ** Obsolete normative reference: RFC 5246 (Obsoleted by RFC 8446) ** Obsolete normative reference: RFC 6536 (Obsoleted by RFC 8341) ** Obsolete normative reference: RFC 8022 (Obsoleted by RFC 8349) Summary: 3 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet A. Lindem 3 Internet-Draft S. Litkowski 4 Intended status: Informational Cisco Systems 5 Expires: May 6, 2020 Y. Qu 6 Futurewei 7 November 3, 2019 9 IS-IS YANG Model Augmentations for Additional Features - Version 1 10 draft-acee-lsr-isis-yang-augmentation-v1-00 12 Abstract 14 This document defines YANG data modules augmenting the IETF IS-IS 15 YANG model to provide support for IS-IS Minimum Remaining Lifetime as 16 defined in RFC 7987. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on May 6, 2020. 35 Copyright Notice 37 Copyright (c) 2019 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 53 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 54 2. YANG Module for IS-IS Minimum Remaining Lifetime . . . . . . 2 55 3. Security Considerations . . . . . . . . . . . . . . . . . . . 4 56 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 57 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 58 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 59 6.1. Normative References . . . . . . . . . . . . . . . . . . 5 60 6.2. Informative References . . . . . . . . . . . . . . . . . 7 61 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 63 1. Overview 65 YANG [RFC6020] [RFC7950] is a data definition language used to define 66 the contents of a conceptual data store that allows networked devices 67 to be managed using NETCONF [RFC6241]. YANG is proving relevant 68 beyond its initial confines, as bindings to other interfaces (e.g., 69 ReST) and encodings other than XML (e.g., JSON) are being defined. 70 Furthermore, YANG data models can be used as the basis for 71 implementation of other interfaces, such as CLI and programmatic 72 APIs. 74 This document defines YANG data modules augmenting the IETF IS-IS 75 YANG model [I-D.ietf-isis-yang-isis-cfg], which itself augments 76 [RFC8349], to provide support for configuration and operational state 77 for the following IS-IS features: 79 RFC7987: IS-IS Minimum Remaining Lifetime[RFC7987]. 81 The augmentations defined in this document requires support for the 82 IS-IS base model[I-D.ietf-isis-yang-isis-cfg] which defines basic IS- 83 IS configuration and state. The IS-IS YANG model augments the ietf- 84 routing YANG model defined in [RFC8022]. 86 1.1. Requirements Language 88 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 89 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 90 document are to be interpreted as described in [RFC2119]. 92 2. YANG Module for IS-IS Minimum Remaining Lifetime 94 This document defines a YANG module for IS-IS Minimum Remaining 95 Lifetime as defined in [RFC7987]. It is an augmentation of the IS-IS 96 base model. 98 module: ietf-isis-remaining-lifetime 100 notifications: 101 +---n corrupt-remaining-lifetime 102 +--ro routing-protocol-name? -> /rt:routing 103 /control-plane-protocols 104 /control-plane-protocol/name 105 +--ro isis-level? level 106 +--ro lsp-id? isis:lsp-id 108 file "ietf-isis-remaining-lifetime@2019-10-28.yang" 109 module ietf-isis-remaining-lifetime { 110 yang-version 1.1; 111 namespace "urn:ietf:params:xml:ns:yang:ietf-isis-remaining-lifetime"; 113 prefix isis-remaining-lifetime; 115 import ietf-isis { 116 prefix "isis"; 117 } 119 organization 120 "IETF LSR - Link State Routing Working Group"; 122 contact 123 "WG Web: 124 WG List: 126 Author: Yingzhen Qu 127 128 Author: Acee Lindem 129 130 Author: Stephane Litkowski 131 "; 133 description 134 "This YANG module defines the configuration and operational 135 state for IS-IS Minimum Remaining Lifetime feature as defined 136 in RFC 7987. 138 Copyright (c) 2019 IETF Trust and the persons identified as 139 authors of the code. All rights reserved. 141 Redistribution and use in source and binary forms, with or 142 without modification, is permitted pursuant to, and subject 143 to the license terms contained in, the Simplified BSD License 144 set forth in Section 4.c of the IETF Trust's Legal Provisions 145 Relating to IETF Documents 146 (http://trustee.ietf.org/license-info). 148 This version of this YANG module is part of RFC XXXX; 149 see the RFC itself for full legal notices."; 151 reference "RFC XXXX"; 153 revision 2019-10-28 { 154 description 155 "Initial version"; 156 reference 157 "RFC XXXX: A YANG Data Model for IS-IS."; 158 } 160 notification corrupt-remaining-lifetime { 161 uses isis:notification-instance-hdr; 162 leaf lsp-id { 163 type isis:lsp-id; 164 description "LSP ID"; 165 } 166 description 167 "This notification is sent when the system 168 detects correpted lifetime of an LSP."; 169 } 170 } 171 173 3. Security Considerations 175 The YANG modules specified in this document define a schema for data 176 that is designed to be accessed via network management protocols such 177 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 178 is the secure transport layer, and the mandatory-to-implement secure 179 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 180 is HTTPS, and the mandatory-to-implement secure transport is TLS 181 [RFC5246]. 183 The NETCONF access control model [RFC6536] provides the means to 184 restrict access for particular NETCONF or RESTCONF users to a pre- 185 configured subset of all available NETCONF or RESTCONF protocol 186 operations and content. 188 There are a number of data nodes defined in the modules that are 189 writable/creatable/deletable (i.e., config true, which is the 190 default). These data nodes may be considered sensitive or vulnerable 191 in some network environments. Write operations (e.g., edit-config) 192 to these data nodes without proper protection can have a negative 193 effect on network operations. 195 Some of the readable data nodes in the modules may be considered 196 sensitive or vulnerable in some network environments. It is thus 197 important to control read access (e.g., via get, get-config, or 198 notification) to these data nodes. The exposure of the Link State 199 Database (LSDB) will expose the detailed topology of the network. 200 This may be undesirable since both due to the fact that exposure may 201 facilitate other attacks. Additionally, network operators may 202 consider their topologies to be sensitive confidential data. 204 4. IANA Considerations 206 This document registers URIs in the IETF XML registry [RFC3688]. 207 Following the format in [RFC3688], the following registrations is 208 requested to be made: 210 URI: urn:ietf:params:xml:ns:yang:ietf-isis-remaining-lifetime 211 Registrant Contact: The IESG. 212 XML: N/A, the requested URI is an XML namespace. 214 This document registers the YANG modules in the YANG Module Names 215 registry [RFC6020]. 217 name: ietf-isis-remaining-lifetime 218 namespace: urn:ietf:params:xml:ns:yang:ietf-isis-remaining-lifetime 219 prefix: isis-remaining-lifetime 220 reference: RFC XXXX 222 5. Acknowledgements 224 This document was produced using Marshall Rose's xml2rfc tool. 226 The YANG model was developed using the suite of YANG tools written 227 and maintained by numerous authors. 229 6. References 231 6.1. Normative References 233 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 234 Requirement Levels", BCP 14, RFC 2119, 235 DOI 10.17487/RFC2119, March 1997, 236 . 238 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 239 DOI 10.17487/RFC3688, January 2004, 240 . 242 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security 243 (TLS) Protocol Version 1.2", RFC 5246, 244 DOI 10.17487/RFC5246, August 2008, 245 . 247 [RFC5329] Ishiguro, K., Manral, V., Davey, A., and A. Lindem, Ed., 248 "Traffic Engineering Extensions to OSPF Version 3", 249 RFC 5329, DOI 10.17487/RFC5329, September 2008, 250 . 252 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 253 the Network Configuration Protocol (NETCONF)", RFC 6020, 254 DOI 10.17487/RFC6020, October 2010, 255 . 257 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 258 and A. Bierman, Ed., "Network Configuration Protocol 259 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 260 . 262 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 263 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 264 . 266 [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration 267 Protocol (NETCONF) Access Control Model", RFC 6536, 268 DOI 10.17487/RFC6536, March 2012, 269 . 271 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 272 RFC 7950, DOI 10.17487/RFC7950, August 2016, 273 . 275 [RFC7987] Ginsberg, L., Wells, P., Decraene, B., Przygienda, T., and 276 H. Gredler, "IS-IS Minimum Remaining Lifetime", RFC 7987, 277 DOI 10.17487/RFC7987, October 2016, 278 . 280 [RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing 281 Management", RFC 8022, DOI 10.17487/RFC8022, November 282 2016, . 284 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 285 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 286 . 288 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 289 Routing Management (NMDA Version)", RFC 8349, 290 DOI 10.17487/RFC8349, March 2018, 291 . 293 6.2. Informative References 295 [I-D.ietf-isis-yang-isis-cfg] 296 Litkowski, S., Yeung, D., Lindem, A., Zhang, Z., and L. 297 Lhotka, "YANG Data Model for IS-IS Protocol", draft-ietf- 298 isis-yang-isis-cfg-42 (work in progress), October 2019. 300 Authors' Addresses 302 Acee Lindem 303 Cisco Systems 304 301 Midenhall Way 305 Cary, NC 27513 307 EMail: acee@cisco.com 309 Stephane Litkowski 310 Cisco Systems 312 EMail: slitkows.ietf@gmail.com 314 Yingzhen Qu 315 Futurewei 316 2330 Central Expressway 317 Santa Clara, CA 95050 318 USA 320 EMail: yingzhen.qu@futurewei.com