--- 1/draft-ietf-ospf-yang-19.txt 2018-12-19 06:13:11.232429639 -0800 +++ 2/draft-ietf-ospf-yang-20.txt 2018-12-19 06:13:11.440434661 -0800 @@ -1,25 +1,25 @@ Internet D. Yeung Internet-Draft Arrcus Intended status: Standards Track Y. Qu -Expires: June 13, 2019 Huawei +Expires: June 22, 2019 Huawei J. Zhang Juniper Networks I. Chen The MITRE Corporation A. Lindem Cisco Systems - December 10, 2018 + December 19, 2018 YANG Data Model for OSPF Protocol - draft-ietf-ospf-yang-19 + draft-ietf-ospf-yang-20 Abstract This document defines a YANG data model that can be used to configure and manage OSPF. 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 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 June 13, 2019. + This Internet-Draft will expire on June 22, 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 (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -58,32 +58,32 @@ 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 2. Design of Data Model . . . . . . . . . . . . . . . . . . . . 3 2.1. OSPF Operational State . . . . . . . . . . . . . . . . . 3 2.2. Overview . . . . . . . . . . . . . . . . . . . . . . . . 4 2.3. OSPFv2 and OSPFv3 . . . . . . . . . . . . . . . . . . . . 5 2.4. Optional Features . . . . . . . . . . . . . . . . . . . . 5 2.5. OSPF Router Configuration/Operational State . . . . . . . 7 2.6. OSPF Area Configuration/Operational State . . . . . . . . 10 - 2.7. OSPF Interface Configuration/Operational State . . . . . 15 - 2.8. OSPF notification . . . . . . . . . . . . . . . . . . . . 18 - 2.9. OSPF RPC Operations . . . . . . . . . . . . . . . . . . . 21 - 3. OSPF YANG Module . . . . . . . . . . . . . . . . . . . . . . 22 - 4. Security Considerations . . . . . . . . . . . . . . . . . . . 112 - 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 113 - 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 113 - 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 114 - 7.1. Normative References . . . . . . . . . . . . . . . . . . 114 - 7.2. Informative References . . . . . . . . . . . . . . . . . 119 - Appendix A. Contributors' Addreses . . . . . . . . . . . . . . . 120 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 120 + 2.7. OSPF Interface Configuration/Operational State . . . . . 16 + 2.8. OSPF notification . . . . . . . . . . . . . . . . . . . . 19 + 2.9. OSPF RPC Operations . . . . . . . . . . . . . . . . . . . 22 + 3. OSPF YANG Module . . . . . . . . . . . . . . . . . . . . . . 23 + 4. Security Considerations . . . . . . . . . . . . . . . . . . . 115 + 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 116 + 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 117 + 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 117 + 7.1. Normative References . . . . . . . . . . . . . . . . . . 117 + 7.2. Informative References . . . . . . . . . . . . . . . . . 122 + Appendix A. Contributors' Addreses . . . . . . . . . . . . . . . 124 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 124 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 @@ -246,53 +246,61 @@ 12. auto-cost: Support OSPF interface cost calculation according to reference bandwidth [RFC2328]. 13. max-ecmp: Support configuration of the maximum number of Equal- Cost Multi-Path (ECMP) paths. 14. max-lsa: Support configuration of the maximum number of LSAs the OSPF instance will accept [RFC1765]. 15. te-rid: Support configuration of the Traffic Engineering (TE) - Router-ID [RFC3630], [RFC5329]. + Router-ID, i.e., the Router Address described in Section 2.4.1 + of [RFC3630] or the Router IPv6 Address TLV described in + Section 3 of [RFC5329]. 16. ldp-igp-sync: Support LDP IGP synchronization [RFC5443]. - 17. ospfv3-authentication-ipsec: Support IPsec for OSPFv3 + 17. ospfv2-authentication-trailer: Support OSPFv2 Authentication + trailer as specified in [RFC5709] or [RFC7166]. + + 18. ospfv3-authentication-ipsec: Support IPsec for OSPFv3 authentication [RFC4552]. - 18. fast-reroute: Support IP Fast Reroute (IP-FRR) [RFC5714]. + 19. ospfv3-authentication-trailer: Support OSPFv3 Authentication + trailer as specified in [RFC7474]. - 19. node-flag: Support node-flag for OSPF prefixes. [RFC7684]. + 20. fast-reroute: Support IP Fast Reroute (IP-FRR) [RFC5714]. - 20. node-tag: Support node admin tag for OSPF instances [RFC7777]. + 21. node-flag: Support node-flag for OSPF prefixes. [RFC7684]. - 21. lfa: Support Loop-Free Alternates (LFAs) [RFC5286]. + 22. node-tag: Support node admin tag for OSPF instances [RFC7777]. - 22. remote-lfa: Support Remote Loop-Free Alternates (R-LFA) + 23. lfa: Support Loop-Free Alternates (LFAs) [RFC5286]. + + 24. remote-lfa: Support Remote Loop-Free Alternates (R-LFA) [RFC7490]. - 23. stub-router: Support RFC 6987 OSPF Stub Router advertisement + 25. stub-router: Support RFC 6987 OSPF Stub Router advertisement [RFC6987]. - 24. pe-ce-protocol: Support OSPF as a PE-CE protocol [RFC4577], + 26. pe-ce-protocol: Support OSPF as a PE-CE protocol [RFC4577], [RFC6565]. - 25. ietf-spf-delay: Support IETF SPF delay algorithm [RFC8405]. + 27. ietf-spf-delay: Support IETF SPF delay algorithm [RFC8405]. - 26. bfd: Support BFD detection of OSPF neighbor reachability + 28. bfd: Support BFD detection of OSPF neighbor reachability [RFC5880], [RFC5881], and [I-D.ietf-bfd-yang]. - 27. hygrid-interface: Support OSPF Hybrid Broadcast and Point-to- + 29. hygrid-interface: Support OSPF Hybrid Broadcast and Point-to- Point Interfaces [RFC6845]. - 28. two-part-metric: Support OSPF Two-Part Metric [RFC8042]. + 30. two-part-metric: Support OSPF Two-Part Metric [RFC8042]. It is expected that vendors will support additional features through vendor-specific augmentations. 2.5. OSPF Router Configuration/Operational State The ospf container is the top level container in this data model. It represents an OSPF protocol engine instance and contains the router level configuration and operational state. The operational state includes the instance statistics, IETF SPF delay statistics, AS- @@ -561,32 +570,50 @@ | | +--rw router-id rt-types:router-id | | +--rw hello-interval? uint16 | | +--rw dead-interval? uint32 | | +--rw retransmit-interval? uint16 | | +--rw transmit-delay? uint16 | | +--rw lls? boolean {lls}? | | +--rw ttl-security {ttl-security}? | | | +--rw enable? boolean | | | +--rw hops? uint8 | | +--rw enable? boolean - | | {admin-control}? + | | | {admin-control}? | | +--rw authentication - | | +--rw (auth-type-selection)? - | | +--:(auth-ipsec) - | | {ospfv3-authentication-ipsec}? - | | | +--rw sa? string - | | +--:(auth-trailer-key-chain) - | | | +--rw key-chain? - | | key-chain:key-chain-ref - | | +--:(auth-trailer-key) - | | +--rw key? string - | | +--rw crypto-algorithm? identityref + | | | +--rw (auth-type-selection)? + | | | +--:(ospfv2-auth) + | | | | +--rw ospfv2-auth-trailer-rfc? + | | | | | ospfv2-auth-trailer-rfc-version + | | | | | {ospfv2-authentication-trailer}? + | | | | +--rw (ospfv2-auth-specification)? + | | | | +--:(auth-key-chain) {key-chain}? + | | | | | +--rw ospfv2-key-chain? + | | | | | key-chain:key-chain-ref + | | | | +--:(auth-key-explicit) + | | | | +--rw ospfv2-key-id? uint32 + | | | | +--rw ospfv2-key? string + | | | | +--rw ospfv2-crypto-algorithm? + | | | | identityref + | | | +--:(ospfv3-auth-ipsec) + | | | | {ospfv3-authentication-ipsec}? + | | | | +--rw sa? string + | | | +--:(ospfv3-auth-trailer) + | | | | {ospfv3-authentication-trailer}? + | | | +--rw (ospfv3-auth-specification)? + | | | +--:(auth-key-chain) {key-chain}? + | | | | +--rw ospfv3-key-chain? + | | | | key-chain:key-chain-ref + | | | +--:(auth-key-explicit) + | | | +--rw ospfv3-sa-id? uint16 + | | | +--rw ospfv3-key? string + | | | +--rw ospfv3-crypto-algorithm? + | | | identityref | | +--ro cost? uint16 | | +--ro state? if-state-type | | +--ro hello-timer? uint32 | | +--ro wait-timer? uint32 | | +--ro dr-router-id? rt-types:router-id | | +--ro dr-ip-addr? inet:ip-address | | +--ro bdr-router-id? rt-types:router-id | | +--ro bdr-ip-addr? inet:ip-address | | +--ro statistics | | | +--ro if-event-count? yang:counter32 @@ -626,32 +653,50 @@ | | +--rw remote-id inet:ip-address | | +--rw hello-interval? uint16 | | +--rw dead-interval? uint32 | | +--rw retransmit-interval? uint16 | | +--rw transmit-delay? uint16 | | +--rw lls? boolean {lls}? | | +--rw ttl-security {ttl-security}? | | | +--rw enable? boolean | | | +--rw hops? uint8 | | +--rw enable? boolean - | | {admin-control}? + | | | {admin-control}? | | +--rw authentication | | | +--rw (auth-type-selection)? - | | | +--:(auth-ipsec) - | | | {ospfv3-authentication-ipsec}? + | | | +--:(ospfv2-auth) + | | | | +--rw ospfv2-auth-trailer-rfc? + | | | | | ospfv2-auth-trailer-rfc-version + | | | | | {ospfv2-authentication-trailer}? + | | | | +--rw (ospfv2-auth-specification)? + | | | | +--:(auth-key-chain) {key-chain}? + | | | | | +--rw ospfv2-key-chain? + | | | | | key-chain:key-chain-ref + | | | | +--:(auth-key-explicit) + | | | | +--rw ospfv2-key-id? uint32 + | | | | +--rw ospfv2-key? string + | | | | +--rw ospfv2-crypto-algorithm? + | | | | identityref + | | | +--:(ospfv3-auth-ipsec) + | | | | {ospfv3-authentication-ipsec}? | | | | +--rw sa? string - | | | +--:(auth-trailer-key-chain) - | | | | +--rw key-chain? - | | | key-chain:key-chain-ref - | | | +--:(auth-trailer-key) - | | | +--rw key? string - | | | +--rw crypto-algorithm? identityref + | | | +--:(ospfv3-auth-trailer) + | | | | {ospfv3-authentication-trailer}? + | | | +--rw (ospfv3-auth-specification)? + | | | +--:(auth-key-chain) {key-chain}? + | | | | +--rw ospfv3-key-chain? + | | | | key-chain:key-chain-ref + | | | +--:(auth-key-explicit) + | | | +--rw ospfv3-sa-id? uint16 + | | | +--rw ospfv3-key? string + | | | +--rw ospfv3-crypto-algorithm? + | | | identityref | | +--rw cost? uint16 | | +--rw mtu-ignore? boolean | | {mtu-ignore}? | | +--rw prefix-suppression? boolean | | {prefix-suppression}? | | +--rw two-part-metric? boolean | | {two-part-metric}? | | +--ro state? if-state-type | | +--ro hello-timer? uint32 | | +--ro wait-timer? uint32 @@ -743,29 +788,47 @@ | +--rw retransmit-interval? uint16 | +--rw transmit-delay? uint16 | +--rw lls? boolean {lls}? | +--rw ttl-security {ttl-security}? | | +--rw enable? boolean | | +--rw hops? uint8 | +--rw enable? boolean | {admin-control}? | +--rw authentication | | +--rw (auth-type-selection)? - | | +--:(auth-ipsec) + | | +--:(ospfv2-auth) + | | | +--rw ospfv2-auth-trailer-rfc? + | | | | ospfv2-auth-trailer-rfc-version + | | | | {ospfv2-authentication-trailer}? + | | | +--rw (ospfv2-auth-specification)? + | | | +--:(auth-key-chain) {key-chain}? + | | | | +--rw ospfv2-key-chain? + | | | | key-chain:key-chain-ref + | | | +--:(auth-key-explicit) + | | | +--rw ospfv2-key-id? uint32 + | | | +--rw ospfv2-key? string + | | | +--rw ospfv2-crypto-algorithm? + | | | identityref + | | +--:(ospfv3-auth-ipsec) | | | {ospfv3-authentication-ipsec}? | | | +--rw sa? string - | | +--:(auth-trailer-key-chain) - | | | +--rw key-chain? + | | +--:(ospfv3-auth-trailer) + | | | {ospfv3-authentication-trailer}? + | | +--rw (ospfv3-auth-specification)? + | | +--:(auth-key-chain) {key-chain}? + | | | +--rw ospfv3-key-chain? | | | key-chain:key-chain-ref - | | +--:(auth-trailer-key) - | | +--rw key? string - | | +--rw crypto-algorithm? identityref + | | +--:(auth-key-explicit) + | | +--rw ospfv3-sa-id? uint16 + | | +--rw ospfv3-key? string + | | +--rw ospfv3-crypto-algorithm? + | | identityref | +--rw cost? uint16 | +--rw mtu-ignore? boolean | | {mtu-ignore}? | +--rw prefix-suppression? boolean | | {prefix-suppression}? | +--ro state? if-state-type | +--ro hello-timer? uint32 | +--ro wait-timer? uint32 | +--ro dr-router-id? rt-types:router-id | +--ro dr-ip-addr? inet:ip-address @@ -1008,23 +1072,23 @@ +---w input +---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], [RFC4576], [RFC4973], [RFC5250], [RFC5309], [RFC5642], [RFC5881], - [RFC6991], [RFC7770], and [RFC8294]. + [RFC6991], [RFC7770], [RFC8294], and [RFC8476]. - file "ietf-ospf@2018-12-10.yang" + file "ietf-ospf@2018-12-16.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 6991 - Common YANG Data Types"; } @@ -1108,21 +1173,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-12-10 { + revision 2018-12-16 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for OSPF."; } feature multi-topology { description "Support Multiple-Topology Routing (MTR)."; reference "RFC 4915 - Multi-Topology Routing"; @@ -1208,44 +1271,64 @@ feature max-lsa { description "Setting the maximum number of LSAs the OSPF instance will accept."; reference "RFC 1765 - OSPF Database Overload"; } feature te-rid { description - "TE Router-ID."; + "Support configuration of the Traffic Engineering (TE) + Router-ID, i.e., the Router Address described in Section + 2.4.1 of RFC3630 or the Router IPv6 Address TLV described + in Section 3 of RFC5329."; reference "RFC 3630 - Traffic Engineering (TE) Extensions to OSPF Version 2 RFC 5329 - Traffic Engineering (TE) Extensions to OSPF Version 3"; } feature ldp-igp-sync { description "LDP IGP synchronization."; reference "RFC 5443 - LDP IGP Synchronization"; } + feature ospfv2-authentication-trailer { + description + "Use OSPFv2 authentication trailer for OSPFv2 + authentication."; + reference "RFC 5709 - Supporting Authentication + Trailer for OSPFv2 + RFC 7474 - Security Extension for OSPFv2 When + Using Manual Key Management"; + } + feature ospfv3-authentication-ipsec { description "Use IPsec for OSPFv3 authentication."; reference "RFC 4552 - Authentication/Confidentiality for OSPFv3"; } + feature ospfv3-authentication-trailer { + description + "Use OSPFv3 authentication trailer for OSPFv3 + authenticatiom."; + reference "RFC 7166 - Supporting Authentication + Trailer for OSPFv3"; + } + feature fast-reroute { description "Support for IP Fast Reroute (IP-FRR)."; - reference "RFC 5714 - IP Fast Reroute Framework"; } feature key-chain { description "Support of keychain for authentication."; reference "RFC8177 - YANG Data Model for Key Chains"; } feature node-flag { @@ -1842,20 +1931,44 @@ typedef fletcher-checksum16-type { type string { pattern '(0x)?[0-9a-fA-F]{4}'; } description "Fletcher 16-bit checksum in hex-string format 0xXXXX."; reference "RFC 905 - ISO Transport Protocol specification ISO DP 8073"; } + typedef ospfv2-auth-trailer-rfc-version { + type enumeration { + enum rfc5709 { + description + "Support OSPF Authentication Trailer as + described in RFC 5709"; + reference "RFC 5709 - OSPFv2 HMAC-SHA Cryptographic + Authentication"; + + } + enum rfc7474 { + description + "Support OSPF Authentication Trailer as + described in RFC 7474"; + reference + "RFC 7474 - Security Extension for OSPFv2 + When Using Manual Key Management Authentication"; + + } + } + description + "OSPFv2 Authentication Trailer Support"; + } + grouping tlv { description "Type-Length-Value (TLV)"; leaf type { type uint16; description "TLV type."; } leaf length { type uint16; description "TLV length (octets)."; @@ -3509,56 +3622,117 @@ type boolean; default true; description "Enable/disable OSPF protocol on the interface."; } container authentication { description "Authentication configuration."; choice auth-type-selection { description - "Options for OSPFv3 authentication configuration."; - case auth-ipsec { + "Options for OSPFv2/OSPFv3 authentication + configuration."; + case ospfv2-auth { + when "derived-from-or-self(../../../../../../rt:type, " + + "'ospf:ospfv2')" { + description "Applied to OSPFv2 only."; + } + leaf ospfv2-auth-trailer-rfc { + if-feature ospfv2-authentication-trailer; + type ospfv2-auth-trailer-rfc-version; + description + "Version of OSFPv2 authentication trailer support - + RFC 5709 or RFC 7474"; + } + choice ospfv2-auth-specification { + description + "Key chain or explicit key parameter specification"; + case auth-key-chain { + if-feature key-chain; + leaf ospfv2-key-chain { + type key-chain:key-chain-ref; + description + "key-chain name."; + } + } + case auth-key-explicit { + leaf ospfv2-key-id { + type uint32; + description + "Key Identifier"; + } + leaf ospfv2-key { + type string; + description + "Key string in ASCII format."; + + } + leaf ospfv2-crypto-algorithm { + type identityref { + base key-chain:crypto-algorithm; + } + description + "Cryptographic algorithm associated with key."; + } + } + } + } + case ospfv3-auth-ipsec { when "derived-from-or-self(../../../../../../rt:type, " + "'ospf:ospfv3')" { description "Applied to OSPFv3 only."; } if-feature ospfv3-authentication-ipsec; leaf sa { type string; description "Security Association (SA) name."; } } - case auth-trailer-key-chain { + case ospfv3-auth-trailer { + when "derived-from-or-self(../../../../../../rt:type, " + + "'ospf:ospfv3')" { + description "Applied to OSPFv3 only."; + } + if-feature ospfv3-authentication-trailer; + choice ospfv3-auth-specification { + description + "Key chain or explicit key parameter specification"; + case auth-key-chain { if-feature key-chain; - leaf key-chain { + leaf ospfv3-key-chain { type key-chain:key-chain-ref; description "key-chain name."; } } - case auth-trailer-key { - leaf key { + case auth-key-explicit { + leaf ospfv3-sa-id { + type uint16; + description + "Security Association (SA) Identifier"; + } + leaf ospfv3-key { type string; description "Key string in ASCII format."; } - leaf crypto-algorithm { + leaf ospfv3-crypto-algorithm { type identityref { base key-chain:crypto-algorithm; } description "Cryptographic algorithm associated with key."; } } - + } + } } } } grouping interface-config { description "Configuration for real interfaces."; leaf interface-type { type enumeration { enum "broadcast" { @@ -5548,20 +5716,25 @@ [RFC5642] Venkata, S., Harwani, S., Pignataro, C., and D. McPherson, "Dynamic Hostname Exchange Mechanism for OSPF", RFC 5642, DOI 10.17487/RFC5642, August 2009, . [RFC5643] Joyal, D., Ed. and V. Manral, Ed., "Management Information Base for OSPFv3", RFC 5643, DOI 10.17487/RFC5643, August 2009, . + [RFC5709] Bhatia, M., Manral, V., Fanto, M., White, R., Barnes, M., + Li, T., and R. Atkinson, "OSPFv2 HMAC-SHA Cryptographic + Authentication", RFC 5709, DOI 10.17487/RFC5709, October + 2009, . + [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 @@ -5594,20 +5767,30 @@ editor.org/info/rfc6845>. [RFC6860] Yang, Y., Retana, A., and A. Roy, "Hiding Transit-Only Networks in OSPF", RFC 6860, DOI 10.17487/RFC6860, January 2013, . [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6991, DOI 10.17487/RFC6991, July 2013, . + [RFC7166] Bhatia, M., Manral, V., and A. Lindem, "Supporting + Authentication Trailer for OSPFv3", RFC 7166, + DOI 10.17487/RFC7166, March 2014, . + + [RFC7474] Bhatia, M., Hartman, S., Zhang, D., and A. Lindem, Ed., + "Security Extension for OSPFv2 When Using Manual Key + Management", RFC 7474, DOI 10.17487/RFC7474, April 2015, + . + [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, . @@ -5673,20 +5856,25 @@ [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, . [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, . + [RFC8476] Tantsura, J., Chunduri, U., Aldrin, S., and P. Psenak, + "Signaling Maximum SID Depth (MSD) Using OSPF", RFC 8476, + DOI 10.17487/RFC8476, December 2018, . + 7.2. Informative References [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, .