--- 1/draft-ietf-ospf-yang-12.txt 2018-07-26 16:13:14.875139936 -0700 +++ 2/draft-ietf-ospf-yang-13.txt 2018-07-26 16:13:15.063144492 -0700 @@ -1,84 +1,84 @@ Internet D. Yeung Internet-Draft Arrcus Intended status: Standards Track Y. Qu -Expires: January 3, 2019 Huawei +Expires: January 27, 2019 Huawei J. Zhang Juniper Networks I. Chen Jabil A. Lindem Cisco Systems - July 2, 2018 + July 26, 2018 Yang Data Model for OSPF Protocol - draft-ietf-ospf-yang-12 + draft-ietf-ospf-yang-13 Abstract This document defines a YANG data model that can be used to configure and manage OSPF. 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/. + Drafts is at http://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 January 3, 2019. + This Internet-Draft will expire on January 27, 2019. Copyright Notice Copyright (c) 2018 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 + (http://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. Table of Contents 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 2. Design of Data Model . . . . . . . . . . . . . . . . . . . . 3 2.1. OSPF Operational State . . . . . . . . . . . . . . . . . 3 2.2. Overview . . . . . . . . . . . . . . . . . . . . . . . . 3 2.3. OSPFv2 and OSPFv3 . . . . . . . . . . . . . . . . . . . . 5 2.4. Optional Features . . . . . . . . . . . . . . . . . . . . 5 2.5. OSPF Router Configuration/Operational State . . . . . . . 5 2.6. OSPF Area Configuration/Operational State . . . . . . . . 8 2.7. OSPF Interface Configuration/Operational State . . . . . 13 - 2.8. OSPF notification . . . . . . . . . . . . . . . . . . . . 15 + 2.8. OSPF notification . . . . . . . . . . . . . . . . . . . . 16 2.9. OSPF RPC Operations . . . . . . . . . . . . . . . . . . . 19 - 3. OSPF Yang Module . . . . . . . . . . . . . . . . . . . . . . 19 - 4. Security Considerations . . . . . . . . . . . . . . . . . . . 100 - 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 101 - 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 102 - 7. Normative References . . . . . . . . . . . . . . . . . . . . 102 - Appendix A. Contributors' Addreses . . . . . . . . . . . . . . . 108 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 108 + 3. OSPF Yang Module . . . . . . . . . . . . . . . . . . . . . . 20 + 4. Security Considerations . . . . . . . . . . . . . . . . . . . 104 + 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 105 + 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 106 + 7. Normative References . . . . . . . . . . . . . . . . . . . . 106 + Appendix A. Contributors' Addreses . . . . . . . . . . . . . . . 112 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 112 1. Overview YANG [RFC6020] 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 @@ -246,34 +246,65 @@ | +--rw enable? boolean | +--rw reference-bandwidth? uint32 +--rw spf-control | +--rw paths? uint16 {max-ecmp}? | +--rw ietf-spf-delay {ietf-spf-delay}? | +--rw initial-delay? uint16 | +--rw short-delay? uint16 | +--rw long-delay? uint16 | +--rw hold-down? uint16 | +--rw time-to-learn? uint16 + | +--ro current-state? enumeration + | +--ro remaining-time-to-learn? uint16 + | +--ro remaining-hold-down? uint16 + | +--ro last-event-received? yang:timestamp + | +--ro next-spf-time? yang:timestamp + | +--ro last-spf-time? yang:timestamp +--rw database-control | +--rw max-lsa? uint32 {max-lsa}? +--rw stub-router {stub-router}? | +--rw (trigger)? | +--:(always) | +--rw always! +--rw mpls | +--rw te-rid {te-rid}? | | +--rw ipv4-router-id? inet:ipv4-address | | +--rw ipv6-router-id? inet:ipv6-address | +--rw ldp | +--rw igp-sync? boolean {ldp-igp-sync}? +--rw fast-reroute {fast-reroute}? | +--rw lfa {lfa}? + +--ro protected-routes + | +--ro af-stats* [af prefix alternate] + | +--ro af iana-rt-types:address-family + | +--ro prefix string + | +--ro alternate string + | +--ro alternate-type? enumeration + | +--ro best? boolean + | +--ro non-best-reason? string + | +--ro protection-available? bits + | +--ro alternate-metric1? uint32 + | +--ro alternate-metric2? uint32 + | +--ro alternate-metric3? uint32 + +--ro unprotected-routes + | +--ro af-stats* [af prefix] + | +--ro af iana-rt-types:address-family + | +--ro prefix string + +--ro protection-statistics* [frr-protection-method] + | +--ro frr-protection-method string + | +--ro af-stats* [af] + | +--ro af iana-rt-types:address-family + | +--ro total-routes? uint32 + | +--ro unprotected-routes? uint32 + | +--ro protected-routes? uint32 + | +--ro linkprotected-routes? uint32 + | +--ro nodeprotected-routes? uint32 +--rw node-tags {node-tag}? | +--rw node-tag* [tag] | +--rw tag uint32 +--ro router-id? +--ro local-rib | +--ro route* [prefix] | +--ro prefix inet:ip-prefix | +--ro next-hops | | +--ro next-hop* [next-hop] | | +--ro outgoing-interface? if:interface-ref @@ -284,32 +315,20 @@ +--ro statistics | +--ro originate-new-lsa-count? yang:counter32 | +--ro rx-new-lsas-count? yang:counter32 | +--ro as-scope-lsa-count? yang:gauge32 | +--ro as-scope-lsa-chksum-sum? uint32 | +--ro database | +--ro as-scope-lsa-type* | +--ro lsa-type? uint16 | +--ro lsa-count? yang:gauge32 | +--ro lsa-cksum-sum? int32 - +--ro ietf-spf-delay - | +--ro initial-delay? uint16 - | +--ro short-delay? uint16 - | +--ro long-delay? uint16 - | +--ro hold-down? uint16 - | +--ro time-to-learn? uint16 - | +--ro current-state? enumeration - | +--ro remaining-time-to-learn? uint16 - | +--ro remaining-hold-down? uint16 - | +--ro last-event-received? yang:timestamp - | +--ro next-spf-time? yang:timestamp - | +--ro last-spf-time? yang:timestamp +--ro database | +--ro as-scope-lsa-type* [lsa-type] | +--ro as-scope-lsas | +--ro as-scope-lsa* [lsa-id adv-router] | +--ro lsa-id union | +--ro adv-router inet:ipv4-address | +--ro decoded-completed? boolean | +--ro raw-data? yang:hex-string | +--ro (version)? | +--:(ospfv2) @@ -901,26 +919,25 @@ +---w routing-protocol-name -> /rt:routing/control-plane-protocols/ control-plane-protocol/name 3. OSPF Yang Module The following RFCs and drafts are not referenced in the document text but are referenced in the ietf-ospf.yang module: [RFC0905], [RFC1765], [RFC4552], [RFC4576], [RFC4915], [RFC5082], [RFC5185], [RFC5250], [RFC5286], [RFC5329], [RFC5443], [RFC5613], [RFC5714], - [RFC5880], [RFC5881], [RFC6021], [RFC6860], [RFC6987], [RFC7490], - [RFC7684], [RFC7770], [RFC7777], [RFC8291], [RFC8343], [RFC8349], - [I-D.ietf-bfd-yang], and [I-D.ietf-rtgwg-backoff-algo]. + [RFC7684], [RFC7770], [RFC7777], [RFC8294], [RFC8343], [RFC8349], + [I-D.ietf-bfd-yang], and [RFC8405]. - file "ietf-ospf@2018-07-02.yang" + file "ietf-ospf@2018-07-27.yang" module ietf-ospf { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-ospf"; prefix ospf; import ietf-inet-types { prefix "inet"; reference "RFC 6021 - Common YANG Data Types"; } @@ -931,27 +948,27 @@ } import ietf-interfaces { prefix "if"; reference "RFC 8343 - A YANG Data Model for Interface Management (NDMA Version)"; } import ietf-routing-types { prefix "rt-types"; - reference "RFC 8291 - Common YANG Data Types for the + reference "RFC 8294 - Common YANG Data Types for the Routing Area"; } import iana-routing-types { prefix "iana-rt-types"; - reference "RFC 8291 - Common YANG Data Types for the + reference "RFC 8294 - Common YANG Data Types for the Routing Area"; } import ietf-routing { prefix "rt"; reference "RFC 8349 - A YANG Data Model for Routing Management (NMDA Version)"; } import ietf-key-chain { @@ -1005,21 +1021,21 @@ 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 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."; - revision 2018-07-02 { + revision 2018-07-27 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for OSPF."; } feature multi-topology { description "Support Multiple-Topolgy Routing (MTR)."; reference "RFC 4915 - Multi-Topology Routing"; @@ -2789,20 +2807,207 @@ container lfa { if-feature lfa; description "This container may be augmented with global parameters for Loop-Free Alternatives (LFA). Container creation has no effect on LFA activation."; } } } + grouping instance-fast-reroute-state { + description "IPFRR state data grouping"; + + container protected-routes { + config false; + description "Instance protection statistics"; + + list af-stats { + key "af prefix alternate"; + description "Per AF protected prefix information"; + + leaf af { + type iana-rt-types:address-family; + description + "Address-family"; + } + leaf prefix { + type string; + description + "Protected prefix."; + } + leaf alternate { + type string; + description + "Alternate nexthop for the prefix."; + } + leaf alternate-type { + type enumeration { + enum equal-cost { + description + "ECMP alternate."; + } + enum lfa { + description + "LFA alternate."; + } + enum remote-lfa { + description + "Remote LFA alternate."; + } + enum tunnel { + description + "Tunnel based alternate + (like RSVP-TE or GRE)."; + } + enum ti-lfa { + description + "TI-LFA alternate."; + } + enum mrt { + description + "MRT alternate."; + } + enum other { + description + "Unknown alternate type."; + } + } + description + "Type of alternate."; + + } + leaf best { + type boolean; + description + "Indicates if the alternate is the preferred."; + } + leaf non-best-reason { + type string; + description + "Information field to describe why the alternate + is not best."; + } + leaf protection-available { + type bits { + bit node-protect { + position 0; + description + "Node protection available."; + } + bit link-protect { + position 1; + description + "Link protection available."; + } + bit srlg-protect { + position 2; + description + "SRLG protection available."; + } + bit downstream-protect { + position 3; + description + "Downstream protection available."; + } + bit other { + position 4; + description + "Other protection available."; + } + } + description "Protection provided by the alternate."; + } + leaf alternate-metric1 { + type uint32; + description + "Metric from Point of Local Repair (PLR) to + destination through the alternate path."; + } + leaf alternate-metric2 { + type uint32; + description + "Metric from PLR to the alternate node"; + } + leaf alternate-metric3 { + type uint32; + description + "Metric from alternate node to the destination"; + } + } + } + + container unprotected-routes { + config false; + description "List of prefixes that are not protected"; + + list af-stats { + key "af prefix"; + description "Per AF unprotected prefix statistics."; + + leaf af { + type iana-rt-types:address-family; + + description "Address-family"; + } + leaf prefix { + type string; + description "Unprotected prefix."; + } + } + } + + list protection-statistics { + key frr-protection-method; + config false; + description "List protection method statistics"; + + leaf frr-protection-method { + type string; + description "Protection method used."; + } + list af-stats { + key af; + description "Per AF protection statistics."; + + leaf af { + type iana-rt-types:address-family; + description "Address-family"; + } + leaf total-routes { + type uint32; + description "Total prefixes."; + } + leaf unprotected-routes { + type uint32; + description + "Total prefixes that are not protected."; + } + leaf protected-routes { + type uint32; + description + "Total prefixes that are protected."; + } + leaf linkprotected-routes { + type uint32; + description + "Total prefixes that are link protected."; + } + leaf nodeprotected-routes { + type uint32; + description + "Total prefixes that are node protected."; + } + } + } + } + grouping interface-fast-reroute-config { description "This group defines interface configuration of IP-FRR."; container fast-reroute { if-feature fast-reroute; container lfa { if-feature lfa; leaf candidate-enable { type boolean; default true; @@ -3497,21 +3701,21 @@ description "Route type for this route."; } leaf route-tag { type uint32; description "Route tag for this route."; } } } } - grouping ietf-spf-delay-config { + grouping ietf-spf-delay { leaf initial-delay { type uint16; units msec; description "Delay used while in QUIET state (milliseconds)."; } leaf short-delay { type uint16; units msec; description @@ -3530,30 +3734,24 @@ "Timer used to consider an IGP stability period (milliseconds)."; } leaf time-to-learn { type uint16; units msec; description "Duration used to learn all the IGP events related to a single component failure (milliseconds)."; } - description - "Grouping for IETF SPF delay configuration."; - } - - grouping ietf-spf-delay-state { leaf current-state { type enumeration { enum "quiet" { description "QUIET state"; - } enum "short-wait" { description "SHORT_WAIT state"; } enum "long-wait" { description "LONG_WAIT state"; } } config false; description @@ -3585,22 +3783,23 @@ description "Time when next SPF has been scheduled."; } leaf last-spf-time { type yang:timestamp; config false; description "Time of last SPF computation."; } description - "Grouping for IETF SPF backoff operational states."; + "Grouping for IETF SPF delay configuration and state"; } + grouping node-tag-config { description "OSPF node tag config state."; container node-tags { if-feature node-tag; list node-tag { key tag; leaf tag { type uint32; description @@ -3761,21 +3959,21 @@ leaf paths { if-feature max-ecmp; type uint16 { range "1..32"; } description "Maximum number of Equal-Cost Multi-Path (ECMP) paths."; } container ietf-spf-delay { if-feature ietf-spf-delay; - uses ietf-spf-delay-config; + uses ietf-spf-delay; description "IETF SPF delay algorithm configuration."; } description "SPF calculation control."; } container database-control { leaf max-lsa { if-feature max-lsa; type uint32 { @@ -3826,23 +4025,25 @@ } container ldp { description "OSPF MPLS LDP config state."; leaf igp-sync { if-feature ldp-igp-sync; type boolean; description "Enable LDP IGP synchronization."; } + } } uses instance-fast-reroute-config; + uses instance-fast-reroute-state; uses node-tag-config; } grouping instance-state { description "OSPF instance operational state."; leaf router-id { type rt-types:router-id; config false; @@ -3852,28 +4053,20 @@ } uses local-rib; container statistics { config false; description "Per-instance statistics"; uses instance-stat; } - container ietf-spf-delay { - if-feature ietf-spf-delay; - config false; - uses ietf-spf-delay-state; - description - "IETF SPF delay state."; - } - container database { config false; description "AS-scope LSA database."; list as-scope-lsa-type { key "lsa-type"; description "List OSPF AS-scope LSA databases."; leaf lsa-type { type uint16; description "OSPF AS scope LSA type."; } @@ -4857,66 +5051,60 @@ Ladislav Lhotka, Stephane Litkowski, Greg Hankins, Manish Gupta and Alan Davey for their thorough reviews and helpful comments. This document was produced using Marshall Rose's xml2rfc tool. 7. Normative References [I-D.ietf-bfd-yang] Rahman, R., Zheng, L., Jethanandani, M., Networks, J., and G. Mirsky, "YANG Data Model for Bidirectional Forwarding - Detection (BFD)", draft-ietf-bfd-yang-13 (work in - progress), March 2018. - - [I-D.ietf-rtgwg-backoff-algo] - Decraene, B., Litkowski, S., Gredler, H., Lindem, A., - Francois, P., and C. Bowers, "SPF Back-off Delay algorithm - for link state IGPs", draft-ietf-rtgwg-backoff-algo-10 - (work in progress), March 2018. + Detection (BFD)", draft-ietf-bfd-yang-16 (work in + progress), June 2018. [RFC0905] "ISO Transport Protocol specification ISO DP 8073", RFC 905, DOI 10.17487/RFC0905, April 1984, . [RFC1765] Moy, J., "OSPF Database Overflow", RFC 1765, - DOI 10.17487/RFC1765, March 1995, - . + DOI 10.17487/RFC1765, March 1995, . [RFC1793] Moy, J., "Extending OSPF to Support Demand Circuits", RFC 1793, DOI 10.17487/RFC1793, April 1995, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, - DOI 10.17487/RFC2119, March 1997, - . + DOI 10.17487/RFC2119, March 1997, . [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, - DOI 10.17487/RFC2328, April 1998, - . + DOI 10.17487/RFC2328, April 1998, . [RFC3101] Murphy, P., "The OSPF Not-So-Stubby Area (NSSA) Option", RFC 3101, DOI 10.17487/RFC3101, January 2003, . [RFC3623] Moy, J., Pillay-Esnault, P., and A. Lindem, "Graceful OSPF Restart", RFC 3623, DOI 10.17487/RFC3623, November 2003, . [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering (TE) Extensions to OSPF Version 2", RFC 3630, - DOI 10.17487/RFC3630, September 2003, - . + DOI 10.17487/RFC3630, September 2003, . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, - DOI 10.17487/RFC3688, January 2004, - . + DOI 10.17487/RFC3688, January 2004, . [RFC4552] Gupta, M. and N. Melam, "Authentication/Confidentiality for OSPFv3", RFC 4552, DOI 10.17487/RFC4552, June 2006, . [RFC4576] Rosen, E., Psenak, P., and P. Pillay-Esnault, "Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs)", RFC 4576, DOI 10.17487/RFC4576, June 2006, . @@ -4936,117 +5124,117 @@ RFC 4915, DOI 10.17487/RFC4915, June 2007, . [RFC5082] Gill, V., Heasley, J., Meyer, D., Savola, P., Ed., and C. Pignataro, "The Generalized TTL Security Mechanism (GTSM)", RFC 5082, DOI 10.17487/RFC5082, October 2007, . [RFC5185] Mirtorabi, S., Psenak, P., Lindem, A., Ed., and A. Oswal, "OSPF Multi-Area Adjacency", RFC 5185, - DOI 10.17487/RFC5185, May 2008, - . + DOI 10.17487/RFC5185, May 2008, . [RFC5187] Pillay-Esnault, P. and A. Lindem, "OSPFv3 Graceful Restart", RFC 5187, DOI 10.17487/RFC5187, June 2008, . [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS) Protocol Version 1.2", RFC 5246, - DOI 10.17487/RFC5246, August 2008, - . + DOI 10.17487/RFC5246, August 2008, . [RFC5250] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The OSPF Opaque LSA Option", RFC 5250, DOI 10.17487/RFC5250, July 2008, . [RFC5286] Atlas, A., Ed. and A. Zinin, Ed., "Basic Specification for IP Fast Reroute: Loop-Free Alternates", RFC 5286, - DOI 10.17487/RFC5286, September 2008, - . + DOI 10.17487/RFC5286, September 2008, . [RFC5329] Ishiguro, K., Manral, V., Davey, A., and A. Lindem, Ed., "Traffic Engineering Extensions to OSPF Version 3", RFC 5329, DOI 10.17487/RFC5329, September 2008, . [RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008, . [RFC5443] Jork, M., Atlas, A., and L. Fang, "LDP IGP Synchronization", RFC 5443, DOI 10.17487/RFC5443, March 2009, . [RFC5613] Zinin, A., Roy, A., Nguyen, L., Friedman, B., and D. Yeung, "OSPF Link-Local Signaling", RFC 5613, - DOI 10.17487/RFC5613, August 2009, - . + DOI 10.17487/RFC5613, August 2009, . [RFC5643] Joyal, D., Ed. and V. Manral, Ed., "Management Information Base for OSPFv3", RFC 5643, DOI 10.17487/RFC5643, August 2009, . [RFC5714] Shand, M. and S. Bryant, "IP Fast Reroute Framework", RFC 5714, DOI 10.17487/RFC5714, January 2010, . [RFC5838] Lindem, A., Ed., Mirtorabi, S., Roy, A., Barnes, M., and R. Aggarwal, "Support of Address Families in OSPFv3", RFC 5838, DOI 10.17487/RFC5838, April 2010, . [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010, . [RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, - DOI 10.17487/RFC5881, June 2010, - . + DOI 10.17487/RFC5881, June 2010, . [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, - DOI 10.17487/RFC6020, October 2010, - . + DOI 10.17487/RFC6020, October 2010, . [RFC6021] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6021, DOI 10.17487/RFC6021, October 2010, . [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, . [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, . [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration Protocol (NETCONF) Access Control Model", RFC 6536, - DOI 10.17487/RFC6536, March 2012, - . + DOI 10.17487/RFC6536, March 2012, . [RFC6565] Pillay-Esnault, P., Moyer, P., Doyle, J., Ertekin, E., and M. Lundberg, "OSPFv3 as a Provider Edge to Customer Edge (PE-CE) Routing Protocol", RFC 6565, DOI 10.17487/RFC6565, June 2012, . [RFC6860] Yang, Y., Retana, A., and A. Roy, "Hiding Transit-Only Networks in OSPF", RFC 6860, DOI 10.17487/RFC6860, January 2013, . [RFC6987] Retana, A., Nguyen, L., Zinin, A., White, R., and D. McPherson, "OSPF Stub Router Advertisement", RFC 6987, - DOI 10.17487/RFC6987, September 2013, - . + DOI 10.17487/RFC6987, September 2013, . [RFC7490] Bryant, S., Filsfils, C., Previdi, S., Shand, M., and N. So, "Remote Loop-Free Alternate (LFA) Fast Reroute (FRR)", RFC 7490, DOI 10.17487/RFC7490, April 2015, . [RFC7684] Psenak, P., Gredler, H., Shakir, R., Henderickx, W., Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute Advertisement", RFC 7684, DOI 10.17487/RFC7684, November 2015, . @@ -5064,40 +5252,47 @@ [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [RFC8177] Lindem, A., Ed., Qu, Y., Yeung, D., Chen, I., and J. Zhang, "YANG Data Model for Key Chains", RFC 8177, - DOI 10.17487/RFC8177, June 2017, - . + DOI 10.17487/RFC8177, June 2017, . - [RFC8291] Thomson, M., "Message Encryption for Web Push", RFC 8291, - DOI 10.17487/RFC8291, November 2017, - . + [RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger, + "Common YANG Data Types for the Routing Area", RFC 8294, + DOI 10.17487/RFC8294, December 2017, . [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., and R. Wilton, "Network Management Datastore Architecture (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, . [RFC8343] Bjorklund, M., "A YANG Data Model for Interface Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, . [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for Routing Management (NMDA Version)", RFC 8349, - DOI 10.17487/RFC8349, March 2018, - . + DOI 10.17487/RFC8349, March 2018, . + + [RFC8405] Decraene, B., Litkowski, S., Gredler, H., Lindem, A., + Francois, P., and C. Bowers, "Shortest Path First (SPF) + Back-Off Delay Algorithm for Link-State IGPs", RFC 8405, + DOI 10.17487/RFC8405, June 2018, . Appendix A. Contributors' Addreses Dean Bogdanovic Volta Networks, Inc. EMail: dean@voltanet.io Kiran Koushik Agrahara Sreenivasa Cisco Systems