--- 1/draft-ietf-ospf-sr-yang-11.txt 2020-07-12 12:13:20.416603256 -0700 +++ 2/draft-ietf-ospf-sr-yang-12.txt 2020-07-12 12:13:20.472604670 -0700 @@ -1,25 +1,25 @@ Internet D. Yeung Internet-Draft Arrcus Intended status: Standards Track Y. Qu -Expires: August 8, 2020 Futurewei +Expires: January 13, 2021 Futurewei J. Zhang Juniper Networks I. Chen The MITRE Corporation A. Lindem Cisco Systems - February 5, 2020 + July 12, 2020 YANG Data Model for OSPF SR (Segment Routing) Protocol - draft-ietf-ospf-sr-yang-11 + draft-ietf-ospf-sr-yang-12 Abstract This document defines a YANG data model that can be used to configure and manage OSPF Segment Routing. The model is based on YANG 1.1 as defined in RFC 7950 and conforms to the Network Management Datastore Architecture (NDMA) as described in RFC 8342. Status of This Memo @@ -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 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 August 8, 2020. + This Internet-Draft will expire on January 13, 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 @@ -53,27 +53,27 @@ the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . . . 3 3. OSPF Segment Routing . . . . . . . . . . . . . . . . . . . . 3 4. OSPF Segment Routing YANG Module . . . . . . . . . . . . . . 7 - 5. Security Considerations . . . . . . . . . . . . . . . . . . . 22 - 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 - 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 - 7.1. Normative References . . . . . . . . . . . . . . . . . . 23 - 7.2. Informative References . . . . . . . . . . . . . . . . . 24 - Appendix A. Contributors' Addreses . . . . . . . . . . . . . . . 26 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 + 5. Security Considerations . . . . . . . . . . . . . . . . . . . 20 + 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 + 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 21 + 7.1. Normative References . . . . . . . . . . . . . . . . . . 21 + 7.2. Informative References . . . . . . . . . . . . . . . . . 22 + Appendix A. Contributors' Addreses . . . . . . . . . . . . . . . 24 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24 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. Furthermore, YANG data models can be used as the basis for implementation of other interfaces, such as CLI and programmatic @@ -313,33 +313,39 @@ | +--ro range-size? uint24 | +--ro sid-sub-tlv | +--ro sid? uint32 +--ro srms-preference-tlv +--ro preference? uint8 4. OSPF Segment Routing YANG Module file "ietf-ospf-sr@2020-02-05.yang" module ietf-ospf-sr { + yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-sr"; prefix ospf-sr; import ietf-inet-types { prefix "inet"; + reference "RFC 6991 - Common YANG Data Types"; } import ietf-yang-types { prefix "yang"; + reference "RFC 6991 - Common YANG Data Types"; } + import ietf-routing { prefix "rt"; + reference "RFC 8349 - A YANG Data Model for Routing + Management (NMDA Version)"; } import ietf-segment-routing-common { prefix "sr-cmn"; } import ietf-segment-routing-mpls { prefix "sr-mpls"; } import ietf-ospf { prefix "ospf"; } @@ -367,145 +373,49 @@ "; description "This YANG module defines the generic configuration and operational state for OSPF Segment Routing, which is common across all of the vendor implementations. It is intended that the module will be extended by vendors to define vendor-specific OSPF Segment Routing configuration and operational parameters and policies. + This YANG model conforms to the Network Management + Datastore Architecture (NMDA) as described in RFC 8242. + Copyright (c) 2020 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 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). + (https://trustee.ietf.org/license-info). + + This version of this YANG module is part of RFC XXXX + (https://www.rfc-editor.org/info/rfcXXXX); 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. This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; reference "RFC XXXX"; - revision 2020-02-05 { - description - ""; - reference - "RFC XXXX: A YANG Data Model for OSPF Segment Routing."; - } - - revision 2019-08-13 { - description - ""; - reference - "RFC XXXX: A YANG Data Model for OSPF Segment Routing."; - } - - revision 2019-08-07 { - description - ""; - reference - "RFC XXXX: A YANG Data Model for OSPF Segment Routing."; - } - - revision 2019-07-07 { - description - ""; - reference - "RFC XXXX: A YANG Data Model for OSPF Segment Routing."; - } - - revision 2019-03-05 { - description - ""; - reference - "RFC XXXX: A YANG Data Model for OSPF Segment Routing."; - } - - revision 2018-06-25 { - description - ""; - - reference - "RFC XXXX: A YANG Data Model for OSPF Segment Routing."; - } - - revision 2018-03-03 { - description - "* Remove OSPF instance."; - reference - "RFC XXXX: A YANG Data Model for OSPF Segment Routing."; - } - - revision 2017-12-28 { - description - ""; - reference - "RFC XXXX: A YANG Data Model for OSPF Segment Routing."; - } - - revision 2017-07-02 { - description - "* Implement NMDA model. - * Add local-block-tlvs and srms-preference-tlv. - * Remove sid-binding-sub-tlvs."; - reference - "RFC XXXX: A YANG Data Model for OSPF Segment Routing."; - } - - revision 2017-03-12 { - description - "* Add p-flag in adj-sid sub-tlv."; - reference - "RFC XXXX: A YANG Data Model for OSPF Segment Routing."; - } - revision 2016-10-31 { - description - "* Update authors information. - * Add import of ietf-segment-routing-common module."; - reference - "RFC XXXX: A YANG Data Model for OSPF Segment Routing."; - } - - revision 2016-07-07 { - description - "* Change routing-protocol to control-plane-protocol."; - reference - "RFC XXXX: A YANG Data Model for OSPF Segment Routing."; - } - revision 2016-03-20 { - description - "* Remove routing-instance."; - reference - "RFC XXXX: A YANG Data Model for OSPF Segment Routing."; - } - - revision 2015-10-19 { - description - "* Add per-protocol SRGB support. - * Editorial changes."; - reference - "RFC XXXX: A YANG Data Model for OSPF Segment Routing."; - } - - revision 2015-09-02 { - description - "* Author list update. - * Editorial changes."; - reference - "RFC XXXX: A YANG Data Model for OSPF Segment Routing."; - } - - revision 2015-07-06 { + revision 2020-07-12 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for OSPF Segment Routing."; } feature ti-lfa { description "Topology-Independent Loop-Free Alternate (TI-LFA) computation using segment routing."; @@ -1059,21 +977,21 @@ 7.1. Normative References [I-D.ietf-ospf-yang] Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem, "YANG Data Model for OSPF Protocol", draft-ietf-ospf- yang-29 (work in progress), October 2019. [I-D.ietf-spring-sr-yang] Litkowski, S., Qu, Y., Lindem, A., Sarkar, P., and J. Tantsura, "YANG Data Model for Segment Routing", draft- - ietf-spring-sr-yang-15 (work in progress), January 2020. + ietf-spring-sr-yang-17 (work in progress), July 2020. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, DOI 10.17487/RFC2328, April 1998, .