--- 1/draft-ietf-lsr-isis-yang-augmentation-v1-01.txt 2021-12-22 12:13:12.817742646 -0800 +++ 2/draft-ietf-lsr-isis-yang-augmentation-v1-02.txt 2021-12-22 12:13:12.873744040 -0800 @@ -1,83 +1,82 @@ Internet A. Lindem Internet-Draft S. Litkowski Intended status: Standards Track Cisco Systems -Expires: December 23, 2021 Y. Qu +Expires: 25 June 2022 Y. Qu Futurewei - June 21, 2021 + 22 December 2021 IS-IS YANG Model Augmentations for Additional Features - Version 1 - draft-ietf-lsr-isis-yang-augmentation-v1-01 + draft-ietf-lsr-isis-yang-augmentation-v1-02 Abstract This document defines YANG data modules augmenting the IETF IS-IS YANG model to provide support for IS-IS Minimum Remaining Lifetime as - defined in RFC 7987, ,IS-IS Application-Specific Link Attributes as - defined in RFC 8919, and IS-IS Flexible Algorithm. + defined in RFC 7987, and IS-IS Application-Specific Link Attributes + as defined in RFC 8919. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. 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 December 23, 2021. + This Internet-Draft will expire on 25 June 2022. Copyright Notice Copyright (c) 2021 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 and restrictions with respect - to this document. Code Components extracted from this document must - include Simplified BSD License text as described in Section 4.e of - the Trust Legal Provisions and are provided without warranty as - described in the Simplified BSD License. + 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 + and restrictions with respect to this document. Code Components + extracted from this document must include Revised BSD License text as + described in Section 4.e of the Trust Legal Provisions and are + provided without warranty as described in the Revised BSD License. Table of Contents 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.2. Tree diagram . . . . . . . . . . . . . . . . . . . . . . 3 2. YANG Module for IS-IS Minimum Remaining Lifetime . . . . . . 3 3. YANG Module for IS-IS Application-Specific Link Attributes . 5 4. YANG Module for IS-IS Flexible Algorithm . . . . . . . . . . 14 5. Security Considerations . . . . . . . . . . . . . . . . . . . 25 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 27 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 27 8.1. Normative References . . . . . . . . . . . . . . . . . . 27 8.2. Informative References . . . . . . . . . . . . . . . . . 29 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29 1. Overview - YANG [RFC6020] [RFC7950] is a data definition language used to define - the contents of a conceptual data store that allows networked devices - to be managed using NETCONF [RFC6241]. YANG is proving relevant - beyond its initial confines, as bindings to other interfaces (e.g., - ReST) and encodings other than XML (e.g., JSON) are being defined. + YANG [RFC7950] is a data definition language used to define the + contents of a conceptual data store that allows networked devices to + be managed using NETCONF [RFC6241]. YANG is proving relevant beyond + its initial confines, as bindings to other interfaces (e.g., ReST) + and encodings other than XML (e.g., JSON) are being defined. Furthermore, YANG data models can be used as the basis for implementation of other interfaces, such as CLI and programmatic APIs. This document defines YANG data modules augmenting the IETF IS-IS YANG model [I-D.ietf-isis-yang-isis-cfg], which itself augments [RFC8349], to provide support for configuration and operational state for the following IS-IS features: RFC7987: IS-IS Minimum Remaining Lifetime[RFC7987]. @@ -113,21 +112,21 @@ module: ietf-isis-remaining-lifetime notifications: +---n corrupt-remaining-lifetime +--ro routing-protocol-name? -> /rt:routing /control-plane-protocols /control-plane-protocol/name +--ro isis-level? level +--ro lsp-id? isis:lsp-id - file "ietf-isis-remaining-lifetime@2021-01-05.yang" + file "ietf-isis-remaining-lifetime@2021-12-22.yang" module ietf-isis-remaining-lifetime { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-isis-remaining-lifetime"; prefix isis-remaining-lifetime; import ietf-isis { prefix "isis"; } @@ -146,47 +145,47 @@ description "This YANG module defines the configuration and operational state for IS-IS Minimum Remaining Lifetime feature as defined in RFC 7987. Copyright (c) 2021 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 + without modification, is permitted pursuant to, and subject to + the license terms contained in, the Revised 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 RFC XXXX; see the RFC itself for full legal notices."; reference "RFC XXXX"; - revision 2021-01-05 { + revision 2021-12-22 { description "Initial version"; reference - "RFC XXXX: A YANG Data Model for IS-IS."; + "RFC XXXX: A YANG Data Model for IS-IS Minimum Remaining Lifetime."; } notification corrupt-remaining-lifetime { uses isis:notification-instance-hdr; leaf lsp-id { type isis:lsp-id; description "LSP ID"; } description "This notification is sent when the system - detects correpted lifetime of an LSP."; + detects corrupted lifetime of an LSP."; reference "RFC 7987: IS-IS Minimum Remaining Lifetime"; } } 3. YANG Module for IS-IS Application-Specific Link Attributes This document defines a YANG module for IS-IS Application-Specific Link Attributes [RFC8919]. It is an augmentation of the IS-IS base model. @@ -262,21 +261,21 @@ | | +--ro ipv4-int-addr? inet:ipv4-address | +--ro ipv4-neighbor-addr | | +--ro ipv4-neighbor-addr? inet:ipv4-address | +--ro ipv6-interface-addr | | +--ro ipv6-int-addr? inet:ipv6-address | +--ro ipv6-neighbor-addr | +--ro ipv6-neighbor-addr? inet:ipv6-address +--ro srlgs +--ro srlg* uint32 - file "ietf-isis-link-attr@2021-01-05.yang" + file "ietf-isis-link-attr@2021-12-22.yang" module ietf-isis-link-attr { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-isis-link-attr"; prefix isis-link-attr; import ietf-inet-types { prefix inet; reference "RFC 6991 - Common YANG Data Types"; } @@ -307,42 +306,43 @@ state for IS-IS application specific link attributes feature as defined in RFC 8919. This YANG model conforms to the Network Management Datastore Architecture (NMDA) as described in RFC 8342. Copyright (c) 2021 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 + without modification, is permitted pursuant to, and subject to + the license terms contained in, the Revised 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 RFC XXXX; see the RFC itself for full legal notices. The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document are to be interpreted as described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, they appear in all capitals, as shown here."; reference "RFC XXXX"; - revision 2021-01-05 { + revision 2021-12-22 { description "Initial version"; reference - "RFC XXXX: A YANG Data Model for IS-IS."; + "RFC XXXX: A YANG Data Model for IS-IS Application-Specific Link + Attributes."; } identity sabm-bit { description "Base identity for sabm bits."; reference "RFC 8919: IS-IS Application-Specific Link Attributes"; } identity rsvp-te-bit { base sabm-bit; @@ -706,21 +711,21 @@ +--ro metric? uint32 augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/isis:isis/isis:database /isis:levels/isis:lsp/isis:mt-ipv6-reachability /isis:prefixes: +--ro fapm-sub-tlvs +--ro fapm-sub-tlv* [] +--ro flex-algo? uint8 +--ro metric? uint32 - file "ietf-isis-flex-algo@2021-06-18.yang" + file "ietf-isis-flex-algo@2021-12-22.yang" module ietf-isis-flex-algo { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-isis-flex-algo"; prefix isis-flex-algo; import ietf-routing { prefix rt; reference "RFC 8349: A YANG Data Model for Routing Management (NMDA Version)"; } @@ -757,38 +762,38 @@ "The YANG module defines the configuration and operational state for ISIS Flexible Algorithm as defined in RFC xxxx. This YANG model conforms to the Network Management Datastore Architecture (NMDA) as described in RFC 8342. Copyright (c) 2021 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 + without modification, is permitted pursuant to, and subject to + the license terms contained in, the Revised 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; see the RFC itself for full legal notices. The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document are to be interpreted as described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, they appear in all capitals, as shown here."; reference "RFC XXXX: YANG Data Model for ISIS Flexible Algorithm."; - revision 2021-06-18 { + revision 2021-12-22 { description "Initial Version"; reference "RFC XXXX: YANG Data Model for ISIS Flexible Algorithm."; } /* Identities */ identity metric-type { description "Base identity for route metric types."; @@ -1257,27 +1261,31 @@ The YANG model was developed using the suite of YANG tools written and maintained by numerous authors. 8. References 8.1. Normative References [I-D.ietf-isis-yang-isis-cfg] Litkowski, S., Yeung, D., Lindem, A., Zhang, J., and L. - Lhotka, "YANG Data Model for IS-IS Protocol", draft-ietf- - isis-yang-isis-cfg-42 (work in progress), October 2019. + Lhotka, "YANG Data Model for IS-IS Protocol", Work in + Progress, Internet-Draft, draft-ietf-isis-yang-isis-cfg- + 42, 15 October 2019, . [I-D.ietf-lsr-flex-algo] Psenak, P., Hegde, S., Filsfils, C., Talaulikar, K., and - A. Gulko, "IGP Flexible Algorithm", draft-ietf-lsr-flex- - algo-15 (work in progress), April 2021. + A. Gulko, "IGP Flexible Algorithm", Work in Progress, + Internet-Draft, draft-ietf-lsr-flex-algo-18, 25 October + 2021, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . @@ -1343,24 +1351,24 @@ BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, . Authors' Addresses Acee Lindem Cisco Systems 301 Midenhall Way Cary, NC 27513 - EMail: acee@cisco.com + Email: acee@cisco.com Stephane Litkowski Cisco Systems - EMail: slitkows.ietf@gmail.com + Email: slitkows.ietf@gmail.com Yingzhen Qu Futurewei 2330 Central Expressway Santa Clara, CA 95050 - USA + United States of America - EMail: yingzhen.qu@futurewei.com + Email: yingzhen.qu@futurewei.com