draft-ietf-ospf-yang-11.txt   draft-ietf-ospf-yang-12.txt 
Internet D. Yeung Internet D. Yeung
Internet-Draft Arrcus Internet-Draft Arrcus
Intended status: Standards Track Y. Qu Intended status: Standards Track Y. Qu
Expires: October 5, 2018 Huawei Expires: January 3, 2019 Huawei
J. Zhang J. Zhang
Juniper Networks Juniper Networks
I. Chen I. Chen
Jabil Jabil
A. Lindem A. Lindem
Cisco Systems Cisco Systems
April 3, 2018 July 2, 2018
Yang Data Model for OSPF Protocol Yang Data Model for OSPF Protocol
draft-ietf-ospf-yang-11 draft-ietf-ospf-yang-12
Abstract Abstract
This document defines a YANG data model that can be used to configure This document defines a YANG data model that can be used to configure
and manage OSPF. and manage OSPF.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 5, 2018. This Internet-Draft will expire on January 3, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2
skipping to change at page 2, line 25 skipping to change at page 2, line 25
2.2. Overview . . . . . . . . . . . . . . . . . . . . . . . . 3 2.2. Overview . . . . . . . . . . . . . . . . . . . . . . . . 3
2.3. OSPFv2 and OSPFv3 . . . . . . . . . . . . . . . . . . . . 5 2.3. OSPFv2 and OSPFv3 . . . . . . . . . . . . . . . . . . . . 5
2.4. Optional Features . . . . . . . . . . . . . . . . . . . . 5 2.4. Optional Features . . . . . . . . . . . . . . . . . . . . 5
2.5. OSPF Router Configuration/Operational State . . . . . . . 5 2.5. OSPF Router Configuration/Operational State . . . . . . . 5
2.6. OSPF Area Configuration/Operational State . . . . . . . . 8 2.6. OSPF Area Configuration/Operational State . . . . . . . . 8
2.7. OSPF Interface Configuration/Operational State . . . . . 13 2.7. OSPF Interface Configuration/Operational State . . . . . 13
2.8. OSPF notification . . . . . . . . . . . . . . . . . . . . 15 2.8. OSPF notification . . . . . . . . . . . . . . . . . . . . 15
2.9. OSPF RPC Operations . . . . . . . . . . . . . . . . . . . 19 2.9. OSPF RPC Operations . . . . . . . . . . . . . . . . . . . 19
3. OSPF Yang Module . . . . . . . . . . . . . . . . . . . . . . 19 3. OSPF Yang Module . . . . . . . . . . . . . . . . . . . . . . 19
4. Security Considerations . . . . . . . . . . . . . . . . . . . 100 4. Security Considerations . . . . . . . . . . . . . . . . . . . 100
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 101 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 101
6. Normative References . . . . . . . . . . . . . . . . . . . . 101 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 102
Appendix A. Contributors' Addreses . . . . . . . . . . . . . . . 107 7. Normative References . . . . . . . . . . . . . . . . . . . . 102
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 107 Appendix A. Contributors' Addreses . . . . . . . . . . . . . . . 108
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 108
1. Overview 1. Overview
YANG [RFC6020] is a data definition language used to define the YANG [RFC6020] is a data definition language used to define the
contents of a conceptual data store that allows networked devices to contents of a conceptual data store that allows networked devices to
be managed using NETCONF [RFC6241]. YANG is proving relevant beyond be managed using NETCONF [RFC6241]. YANG is proving relevant beyond
its initial confines, as bindings to other interfaces (e.g., ReST) its initial confines, as bindings to other interfaces (e.g., ReST)
and encodings other than XML (e.g., JSON) are being defined. and encodings other than XML (e.g., JSON) are being defined.
Furthermore, YANG data models can be used as the basis for Furthermore, YANG data models can be used as the basis for
implementation of other interfaces, such as CLI and programmatic implementation of other interfaces, such as CLI and programmatic
skipping to change at page 20, line 9 skipping to change at page 20, line 9
The following RFCs and drafts are not referenced in the document text The following RFCs and drafts are not referenced in the document text
but are referenced in the ietf-ospf.yang module: [RFC0905], but are referenced in the ietf-ospf.yang module: [RFC0905],
[RFC1765], [RFC4552], [RFC4576], [RFC4915], [RFC5082], [RFC5185], [RFC1765], [RFC4552], [RFC4576], [RFC4915], [RFC5082], [RFC5185],
[RFC5250], [RFC5286], [RFC5329], [RFC5443], [RFC5613], [RFC5714], [RFC5250], [RFC5286], [RFC5329], [RFC5443], [RFC5613], [RFC5714],
[RFC5880], [RFC5881], [RFC6021], [RFC6860], [RFC6987], [RFC7490], [RFC5880], [RFC5881], [RFC6021], [RFC6860], [RFC6987], [RFC7490],
[RFC7684], [RFC7770], [RFC7777], [RFC8291], [RFC8343], [RFC8349], [RFC7684], [RFC7770], [RFC7777], [RFC8291], [RFC8343], [RFC8349],
[I-D.ietf-bfd-yang], and [I-D.ietf-rtgwg-backoff-algo]. [I-D.ietf-bfd-yang], and [I-D.ietf-rtgwg-backoff-algo].
<CODE BEGINS> file "ietf-ospf@2018-04-03.yang" <CODE BEGINS> file "ietf-ospf@2018-07-02.yang"
module ietf-ospf { module ietf-ospf {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-ospf"; namespace "urn:ietf:params:xml:ns:yang:ietf-ospf";
prefix ospf; prefix ospf;
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
reference "RFC 6021 - Common YANG Data Types"; reference "RFC 6021 - Common YANG Data Types";
} }
skipping to change at page 22, line 10 skipping to change at page 22, line 10
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; This version of this YANG module is part of RFC XXXX;
see the RFC itself for full legal notices."; see the RFC itself for full legal notices.";
revision 2018-04-03 { revision 2018-07-02 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for OSPF."; "RFC XXXX: A YANG Data Model for OSPF.";
} }
feature multi-topology { feature multi-topology {
description description
"Support Multiple-Topolgy Routing (MTR)."; "Support Multiple-Topolgy Routing (MTR).";
reference "RFC 4915 - Multi-Topology Routing"; reference "RFC 4915 - Multi-Topology Routing";
skipping to change at page 23, line 25 skipping to change at page 23, line 25
feature nsr { feature nsr {
description description
"Non-Stop-Routing (NSR) support."; "Non-Stop-Routing (NSR) support.";
} }
feature graceful-restart { feature graceful-restart {
description description
"Graceful OSPF Restart as defined in RFC 3623 and "Graceful OSPF Restart as defined in RFC 3623 and
RFC 5187."; RFC 5187.";
reference "RFC 3630 - Graceful OSPF Restart reference "RFC 3623 - Graceful OSPF Restart
RFC 5187 - OSPFv3 Graceful Restart"; RFC 5187 - OSPFv3 Graceful Restart";
} }
feature admin-control { feature admin-control {
description description
"Administrative control of the protocol state."; "Administrative control of the protocol state.";
} }
feature auto-cost { feature auto-cost {
description description
skipping to change at page 28, line 28 skipping to change at page 28, line 28
description description
"OSPFv2 Area-Scoped Opaque LSA - Type 10"; "OSPFv2 Area-Scoped Opaque LSA - Type 10";
} }
identity ospfv2-as-scope-opaque-lsa { identity ospfv2-as-scope-opaque-lsa {
base ospfv2-opaque-lsa-type; base ospfv2-opaque-lsa-type;
description description
"OSPFv2 AS-Scoped Opaque LSA - Type 11"; "OSPFv2 AS-Scoped Opaque LSA - Type 11";
} }
identity ospfv2-unknown-lsa-type {
base ospfv2-lsa-type;
description
"OSPFv2 Unknown LSA type";
}
identity ospfv3-lsa-type { identity ospfv3-lsa-type {
base ospf-lsa-type; base ospf-lsa-type;
description description
"OSPFv3 LSA types."; "OSPFv3 LSA types.";
} }
identity ospfv3-router-lsa { identity ospfv3-router-lsa {
base ospfv3-lsa-type; base ospfv3-lsa-type;
description description
"OSPFv3 Router LSA - Type 0x2001"; "OSPFv3 Router LSA - Type 0x2001";
skipping to change at page 29, line 45 skipping to change at page 30, line 4
base ospfv3-lsa-type; base ospfv3-lsa-type;
description description
"OSPFv3 Link LSA - Type 0x0008"; "OSPFv3 Link LSA - Type 0x0008";
} }
identity ospfv3-intra-area-prefix-lsa { identity ospfv3-intra-area-prefix-lsa {
base ospfv3-lsa-type; base ospfv3-lsa-type;
description description
"OSPFv3 Intra-area Prefix LSA - Type 0x2009"; "OSPFv3 Intra-area Prefix LSA - Type 0x2009";
} }
identity ospfv3-router-information-lsa { identity ospfv3-router-information-lsa {
base ospfv3-lsa-type; base ospfv3-lsa-type;
description description
"OSPFv3 Router Information LSA - Types 0x800C, "OSPFv3 Router Information LSA - Types 0x800C,
0xA00C, and 0xC00C"; 0xA00C, and 0xC00C";
} }
identity ospfv3-unknown-lsa-type {
base ospfv3-lsa-type;
description
"OSPFv3 Unknown LSA type";
}
identity lsa-log-reason { identity lsa-log-reason {
description description
"Base identity for an LSA log reason."; "Base identity for an LSA log reason.";
} }
identity lsa-refresh { identity lsa-refresh {
base lsa-log-reason; base lsa-log-reason;
description description
"Identity used when the LSA is logged "Identity used when the LSA is logged
as a result of receiving a refresh LSA."; as a result of receiving a refresh LSA.";
skipping to change at page 36, line 47 skipping to change at page 37, line 13
leaf tag { leaf tag {
type uint32; type uint32;
description description
"Node admin tag value."; "Node admin tag value.";
} }
description description
"List of tags."; "List of tags.";
} }
} }
grouping ospf-router-lsa-flags {
leaf flags {
type bits {
bit V {
description
"When set, the router is an endpoint of one or
more virtual links.";
}
bit E {
description
"When set, the router is an AS Boundary Router
(ASBR).";
}
bit B {
description
"When set, the router is an Area Border
Router (ABR).";
}
bit Nt {
description
"When set, the router is an NSSA border router
that is unconditionally translating NSSA LSAs
into AS-external LSAs.";
}
}
description "Router LSA Flags.";
}
description
"Router LSA Flags - Currently common for OSPFv2 and
OSPFv3 but it may diverge with future augmentations.";
}
grouping ospfv2-router-link { grouping ospfv2-router-link {
description "OSPFv2 router link."; description "OSPFv2 router link.";
leaf link-id { leaf link-id {
type union { type union {
type inet:ipv4-address; type inet:ipv4-address;
type yang:dotted-quad; type yang:dotted-quad;
} }
description "Router-LSA Link ID"; description "Router-LSA Link ID";
} }
leaf link-data { leaf link-data {
skipping to change at page 37, line 31 skipping to change at page 38, line 29
grouping ospfv2-lsa-body { grouping ospfv2-lsa-body {
description "OSPFv2 LSA body."; description "OSPFv2 LSA body.";
container router { container router {
when "derived-from-or-self(../../header/type, " when "derived-from-or-self(../../header/type, "
+ "'ospf:ospfv2-router-lsa')" { + "'ospf:ospfv2-router-lsa')" {
description description
"Only applies to Router-LSAs."; "Only applies to Router-LSAs.";
} }
description description
"Router LSA."; "Router LSA.";
leaf flags { uses ospf-router-lsa-flags;
type bits {
bit V {
description
"When set, the router is an endpoint of one or
more virtual links.";
}
bit E {
description
"When set, the router is an AS Boundary Router
(ASBR).";
}
bit B {
description
"When set, the router is an Area Border
Router (ABR).";
}
bit Nt {
description
"When set, the router is an NSSA border router
that is unconditionally translating NSSA LSAs
into AS-external LSAs.";
}
}
description "Flags.";
}
leaf num-of-links { leaf num-of-links {
type uint16; type uint16;
description "Number of links in Router LSA."; description "Number of links in Router LSA.";
} }
container links { container links {
description "All router Links."; description "All router Links.";
list link { list link {
description "Router LSA link."; description "Router LSA link.";
uses ospfv2-router-link; uses ospfv2-router-link;
container topologies { container topologies {
skipping to change at page 46, line 25 skipping to change at page 46, line 48
bit T { bit T {
description description
"When set, an External Route Tag is included "When set, an External Route Tag is included
in the LSA."; in the LSA.";
} }
} }
description "Flags."; description "Flags.";
} }
leaf referenced-ls-type { leaf referenced-ls-type {
type uint16; type identityref {
base ospf:ospfv3-lsa-type;
}
description "Referenced Link State type."; description "Referenced Link State type.";
}
leaf unknown-referenced-ls-type {
type uint16;
description
"Value for an unknown Referenced Link State type.";
} }
uses ospfv3-lsa-prefix; uses ospfv3-lsa-prefix;
leaf forwarding-address { leaf forwarding-address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Forwarding address."; "Forwarding address.";
} }
leaf external-route-tag { leaf external-route-tag {
type uint32; type uint32;
description description
"Route tag."; "Route tag.";
} }
leaf referenced-link-state-id { leaf referenced-link-state-id {
type uint32; type yang:dotted-quad;
description description
"Referenced Link State ID."; "Referenced Link State ID.";
} }
} }
grouping ospfv3-lsa-body { grouping ospfv3-lsa-body {
description "OSPFv3 LSA body."; description "OSPFv3 LSA body.";
container router { container router {
when "derived-from-or-self(../../header/type, " when "derived-from-or-self(../../header/type, "
+ "'ospfv3-router-lsa')" { + "'ospfv3-router-lsa')" {
description description
"Only applies to Router LSAs."; "Only applies to Router LSAs.";
} }
description "Router LSA."; description "Router LSA.";
leaf flags { uses ospf-router-lsa-flags;
type bits {
bit V {
description
"When set, the router is an endpoint of one or
more virtual links.";
}
bit E {
description
"When set, the router is an AS Boundary Router
(ASBR).";
}
bit B {
description
"When set, the router is an Area Border
Router (ABR).";
}
bit Nt {
description
"When set, the router is an NSSA border router
that is unconditionally translating NSSA LSAs
into AS-external LSAs.";
}
}
mandatory true;
description "Router LSA flags.";
}
uses ospfv3-lsa-options; uses ospfv3-lsa-options;
container links { container links {
description "All router link."; description "All router link.";
list link { list link {
description "Router LSA link."; description "Router LSA link.";
leaf interface-id { leaf interface-id {
type uint32; type uint32;
description "Interface ID for link."; description "Interface ID for link.";
} }
skipping to change at page 50, line 40 skipping to change at page 50, line 43
} }
container intra-area-prefix { container intra-area-prefix {
when "derived-from-or-self(../../header/type, " when "derived-from-or-self(../../header/type, "
+ "'ospfv3-intra-area-prefix-lsa')" { + "'ospfv3-intra-area-prefix-lsa')" {
description description
"Only applies to Intra-Area-Prefix LSAs."; "Only applies to Intra-Area-Prefix LSAs.";
} }
description "Intra-Area-Prefix LSA."; description "Intra-Area-Prefix LSA.";
leaf referenced-ls-type { leaf referenced-ls-type {
type uint16; type identityref {
base ospf:ospfv3-lsa-type;
}
description "Referenced Link State type."; description "Referenced Link State type.";
} }
leaf unknown-referenced-ls-type {
type uint16;
description
"Value for an unknown Referenced Link State type.";
}
leaf referenced-link-state-id { leaf referenced-link-state-id {
type uint32; type yang:dotted-quad;
description description
"Referenced Link State ID."; "Referenced Link State ID.";
} }
leaf referenced-adv-router { leaf referenced-adv-router {
type inet:ipv4-address; type rt-types:router-id;
description description
"Referenced Advertising Router."; "Referenced Advertising Router.";
} }
leaf num-of-prefixes { leaf num-of-prefixes {
type uint16; type uint16;
description "Number of prefixes."; description "Number of prefixes.";
} }
container prefixes { container prefixes {
description "All prefixes in this LSA."; description "All prefixes in this LSA.";
list prefix { list prefix {
description "List of prefixes in this LSA."; description "List of prefixes in this LSA.";
skipping to change at page 52, line 11 skipping to change at page 52, line 20
description "LSA age."; description "LSA age.";
} }
leaf type { leaf type {
type identityref { type identityref {
base ospf-lsa-type; base ospf-lsa-type;
} }
mandatory true; mandatory true;
description "LSA type"; description "LSA type";
} }
leaf adv-router { leaf adv-router {
type yang:dotted-quad; type rt-types:router-id;
mandatory true; mandatory true;
description "LSA advertising router."; description "LSA advertising router.";
} }
leaf seq-num { leaf seq-num {
type uint32; type uint32;
mandatory true; mandatory true;
description "LSA sequence number."; description "LSA sequence number.";
} }
leaf checksum { leaf checksum {
type fletcher-checksum16-type; type fletcher-checksum16-type;
skipping to change at page 55, line 34 skipping to change at page 55, line 45
"OSPF LSA key."; "OSPF LSA key.";
leaf lsa-id { leaf lsa-id {
type union { type union {
type yang:dotted-quad; type yang:dotted-quad;
type uint32; type uint32;
} }
description description
"Link-State ID."; "Link-State ID.";
} }
leaf adv-router { leaf adv-router {
type inet:ipv4-address; type rt-types:router-id;
description description
"Advertising router."; "Advertising router.";
} }
} }
grouping instance-stat { grouping instance-stat {
description "Per-instance statistics"; description "Per-instance statistics";
leaf originate-new-lsa-count { leaf originate-new-lsa-count {
type yang:counter32; type yang:counter32;
description "The number of new LSAs originated."; description "The number of new LSAs originated.";
skipping to change at page 84, line 46 skipping to change at page 85, line 9
leaf type { leaf type {
type uint16; type uint16;
description description
"LSA type."; "LSA type.";
} }
leaf lsa-id { leaf lsa-id {
type yang:dotted-quad; type yang:dotted-quad;
description "Link-State ID."; description "Link-State ID.";
} }
leaf adv-router { leaf adv-router {
type yang:dotted-quad; type rt-types:router-id;
description description
"LSA advertising router."; "LSA advertising router.";
} }
leaf seq-num { leaf seq-num {
type uint32; type uint32;
description description
"LSA sequence number."; "LSA sequence number.";
} }
} }
skipping to change at page 101, line 31 skipping to change at page 101, line 41
[RFC8177]. This includes the considerations with respect to the [RFC8177]. This includes the considerations with respect to the
local storage and handling of authentication keys. local storage and handling of authentication keys.
Some of the RPC operations in this YANG module may be considered Some of the RPC operations in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus sensitive or vulnerable in some network environments. It is thus
important to control access to these operations. The OSPF Yang important to control access to these operations. The OSPF Yang
module support the "clear-neighbor" and "clear-database" RPCs. If module support the "clear-neighbor" and "clear-database" RPCs. If
access too either of these is compromised, they can result in access too either of these is compromised, they can result in
temporary network outages be employed to mount DoS attacks. temporary network outages be employed to mount DoS attacks.
5. Acknowledgements 5. IANA Considerations
This document registers a URI in the IETF XML registry [RFC3688].
Following the format in [RFC3688], the following registration is
requested to be made:
URI: urn:ietf:params:xml:ns:yang:ietf-ospf
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
This document registers a YANG module in the YANG Module Names
registry [RFC6020].
name: ietf-ospf
namespace: urn:ietf:params:xml:ns:yang:ietf-ospf
prefix: ospf
reference: RFC XXXX
6. Acknowledgements
The authors wish to thank Yi Yang, Alexander Clemm, Gaurav Gupta, The authors wish to thank Yi Yang, Alexander Clemm, Gaurav Gupta,
Ladislav Lhotka, Stephane Litkowski, Greg Hankins, Manish Gupta and Ladislav Lhotka, Stephane Litkowski, Greg Hankins, Manish Gupta and
Alan Davey for their thorough reviews and helpful comments. Alan Davey for their thorough reviews and helpful comments.
This document was produced using Marshall Rose's xml2rfc tool. This document was produced using Marshall Rose's xml2rfc tool.
6. Normative References 7. Normative References
[I-D.ietf-bfd-yang] [I-D.ietf-bfd-yang]
Rahman, R., Zheng, L., Jethanandani, M., Networks, J., and Rahman, R., Zheng, L., Jethanandani, M., Networks, J., and
G. Mirsky, "YANG Data Model for Bidirectional Forwarding G. Mirsky, "YANG Data Model for Bidirectional Forwarding
Detection (BFD)", draft-ietf-bfd-yang-13 (work in Detection (BFD)", draft-ietf-bfd-yang-13 (work in
progress), March 2018. progress), March 2018.
[I-D.ietf-rtgwg-backoff-algo] [I-D.ietf-rtgwg-backoff-algo]
Decraene, B., Litkowski, S., Gredler, H., Lindem, A., Decraene, B., Litkowski, S., Gredler, H., Lindem, A.,
Francois, P., and C. Bowers, "SPF Back-off Delay algorithm Francois, P., and C. Bowers, "SPF Back-off Delay algorithm
for link state IGPs", draft-ietf-rtgwg-backoff-algo-10 for link state IGPs", draft-ietf-rtgwg-backoff-algo-10
(work in progress), March 2018. (work in progress), March 2018.
[RFC0905] "ISO Transport Protocol specification ISO DP 8073", [RFC0905] "ISO Transport Protocol specification ISO DP 8073",
RFC 905, DOI 10.17487/RFC0905, April 1984, RFC 905, DOI 10.17487/RFC0905, April 1984,
<https://www.rfc-editor.org/info/rfc905>. <https://www.rfc-editor.org/info/rfc905>.
[RFC1765] Moy, J., "OSPF Database Overflow", RFC 1765, [RFC1765] Moy, J., "OSPF Database Overflow", RFC 1765,
DOI 10.17487/RFC1765, March 1995, <https://www.rfc- DOI 10.17487/RFC1765, March 1995,
editor.org/info/rfc1765>. <https://www.rfc-editor.org/info/rfc1765>.
[RFC1793] Moy, J., "Extending OSPF to Support Demand Circuits", [RFC1793] Moy, J., "Extending OSPF to Support Demand Circuits",
RFC 1793, DOI 10.17487/RFC1793, April 1995, RFC 1793, DOI 10.17487/RFC1793, April 1995,
<https://www.rfc-editor.org/info/rfc1793>. <https://www.rfc-editor.org/info/rfc1793>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, <https://www.rfc- DOI 10.17487/RFC2119, March 1997,
editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328,
DOI 10.17487/RFC2328, April 1998, <https://www.rfc- DOI 10.17487/RFC2328, April 1998,
editor.org/info/rfc2328>. <https://www.rfc-editor.org/info/rfc2328>.
[RFC3101] Murphy, P., "The OSPF Not-So-Stubby Area (NSSA) Option", [RFC3101] Murphy, P., "The OSPF Not-So-Stubby Area (NSSA) Option",
RFC 3101, DOI 10.17487/RFC3101, January 2003, RFC 3101, DOI 10.17487/RFC3101, January 2003,
<https://www.rfc-editor.org/info/rfc3101>. <https://www.rfc-editor.org/info/rfc3101>.
[RFC3623] Moy, J., Pillay-Esnault, P., and A. Lindem, "Graceful OSPF [RFC3623] Moy, J., Pillay-Esnault, P., and A. Lindem, "Graceful OSPF
Restart", RFC 3623, DOI 10.17487/RFC3623, November 2003, Restart", RFC 3623, DOI 10.17487/RFC3623, November 2003,
<https://www.rfc-editor.org/info/rfc3623>. <https://www.rfc-editor.org/info/rfc3623>.
[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
(TE) Extensions to OSPF Version 2", RFC 3630, (TE) Extensions to OSPF Version 2", RFC 3630,
DOI 10.17487/RFC3630, September 2003, <https://www.rfc- DOI 10.17487/RFC3630, September 2003,
editor.org/info/rfc3630>. <https://www.rfc-editor.org/info/rfc3630>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>.
[RFC4552] Gupta, M. and N. Melam, "Authentication/Confidentiality [RFC4552] Gupta, M. and N. Melam, "Authentication/Confidentiality
for OSPFv3", RFC 4552, DOI 10.17487/RFC4552, June 2006, for OSPFv3", RFC 4552, DOI 10.17487/RFC4552, June 2006,
<https://www.rfc-editor.org/info/rfc4552>. <https://www.rfc-editor.org/info/rfc4552>.
[RFC4576] Rosen, E., Psenak, P., and P. Pillay-Esnault, "Using a [RFC4576] Rosen, E., Psenak, P., and P. Pillay-Esnault, "Using a
Link State Advertisement (LSA) Options Bit to Prevent Link State Advertisement (LSA) Options Bit to Prevent
Looping in BGP/MPLS IP Virtual Private Networks (VPNs)", Looping in BGP/MPLS IP Virtual Private Networks (VPNs)",
RFC 4576, DOI 10.17487/RFC4576, June 2006, RFC 4576, DOI 10.17487/RFC4576, June 2006,
<https://www.rfc-editor.org/info/rfc4576>. <https://www.rfc-editor.org/info/rfc4576>.
skipping to change at page 103, line 22 skipping to change at page 104, line 7
RFC 4915, DOI 10.17487/RFC4915, June 2007, RFC 4915, DOI 10.17487/RFC4915, June 2007,
<https://www.rfc-editor.org/info/rfc4915>. <https://www.rfc-editor.org/info/rfc4915>.
[RFC5082] Gill, V., Heasley, J., Meyer, D., Savola, P., Ed., and C. [RFC5082] Gill, V., Heasley, J., Meyer, D., Savola, P., Ed., and C.
Pignataro, "The Generalized TTL Security Mechanism Pignataro, "The Generalized TTL Security Mechanism
(GTSM)", RFC 5082, DOI 10.17487/RFC5082, October 2007, (GTSM)", RFC 5082, DOI 10.17487/RFC5082, October 2007,
<https://www.rfc-editor.org/info/rfc5082>. <https://www.rfc-editor.org/info/rfc5082>.
[RFC5185] Mirtorabi, S., Psenak, P., Lindem, A., Ed., and A. Oswal, [RFC5185] Mirtorabi, S., Psenak, P., Lindem, A., Ed., and A. Oswal,
"OSPF Multi-Area Adjacency", RFC 5185, "OSPF Multi-Area Adjacency", RFC 5185,
DOI 10.17487/RFC5185, May 2008, <https://www.rfc- DOI 10.17487/RFC5185, May 2008,
editor.org/info/rfc5185>. <https://www.rfc-editor.org/info/rfc5185>.
[RFC5187] Pillay-Esnault, P. and A. Lindem, "OSPFv3 Graceful [RFC5187] Pillay-Esnault, P. and A. Lindem, "OSPFv3 Graceful
Restart", RFC 5187, DOI 10.17487/RFC5187, June 2008, Restart", RFC 5187, DOI 10.17487/RFC5187, June 2008,
<https://www.rfc-editor.org/info/rfc5187>. <https://www.rfc-editor.org/info/rfc5187>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, (TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008, <https://www.rfc- DOI 10.17487/RFC5246, August 2008,
editor.org/info/rfc5246>. <https://www.rfc-editor.org/info/rfc5246>.
[RFC5250] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The [RFC5250] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The
OSPF Opaque LSA Option", RFC 5250, DOI 10.17487/RFC5250, OSPF Opaque LSA Option", RFC 5250, DOI 10.17487/RFC5250,
July 2008, <https://www.rfc-editor.org/info/rfc5250>. July 2008, <https://www.rfc-editor.org/info/rfc5250>.
[RFC5286] Atlas, A., Ed. and A. Zinin, Ed., "Basic Specification for [RFC5286] Atlas, A., Ed. and A. Zinin, Ed., "Basic Specification for
IP Fast Reroute: Loop-Free Alternates", RFC 5286, IP Fast Reroute: Loop-Free Alternates", RFC 5286,
DOI 10.17487/RFC5286, September 2008, <https://www.rfc- DOI 10.17487/RFC5286, September 2008,
editor.org/info/rfc5286>. <https://www.rfc-editor.org/info/rfc5286>.
[RFC5329] Ishiguro, K., Manral, V., Davey, A., and A. Lindem, Ed., [RFC5329] Ishiguro, K., Manral, V., Davey, A., and A. Lindem, Ed.,
"Traffic Engineering Extensions to OSPF Version 3", "Traffic Engineering Extensions to OSPF Version 3",
RFC 5329, DOI 10.17487/RFC5329, September 2008, RFC 5329, DOI 10.17487/RFC5329, September 2008,
<https://www.rfc-editor.org/info/rfc5329>. <https://www.rfc-editor.org/info/rfc5329>.
[RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF [RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF
for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008, for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008,
<https://www.rfc-editor.org/info/rfc5340>. <https://www.rfc-editor.org/info/rfc5340>.
[RFC5443] Jork, M., Atlas, A., and L. Fang, "LDP IGP [RFC5443] Jork, M., Atlas, A., and L. Fang, "LDP IGP
Synchronization", RFC 5443, DOI 10.17487/RFC5443, March Synchronization", RFC 5443, DOI 10.17487/RFC5443, March
2009, <https://www.rfc-editor.org/info/rfc5443>. 2009, <https://www.rfc-editor.org/info/rfc5443>.
[RFC5613] Zinin, A., Roy, A., Nguyen, L., Friedman, B., and D. [RFC5613] Zinin, A., Roy, A., Nguyen, L., Friedman, B., and D.
Yeung, "OSPF Link-Local Signaling", RFC 5613, Yeung, "OSPF Link-Local Signaling", RFC 5613,
DOI 10.17487/RFC5613, August 2009, <https://www.rfc- DOI 10.17487/RFC5613, August 2009,
editor.org/info/rfc5613>. <https://www.rfc-editor.org/info/rfc5613>.
[RFC5643] Joyal, D., Ed. and V. Manral, Ed., "Management Information [RFC5643] Joyal, D., Ed. and V. Manral, Ed., "Management Information
Base for OSPFv3", RFC 5643, DOI 10.17487/RFC5643, August Base for OSPFv3", RFC 5643, DOI 10.17487/RFC5643, August
2009, <https://www.rfc-editor.org/info/rfc5643>. 2009, <https://www.rfc-editor.org/info/rfc5643>.
[RFC5714] Shand, M. and S. Bryant, "IP Fast Reroute Framework", [RFC5714] Shand, M. and S. Bryant, "IP Fast Reroute Framework",
RFC 5714, DOI 10.17487/RFC5714, January 2010, RFC 5714, DOI 10.17487/RFC5714, January 2010,
<https://www.rfc-editor.org/info/rfc5714>. <https://www.rfc-editor.org/info/rfc5714>.
[RFC5838] Lindem, A., Ed., Mirtorabi, S., Roy, A., Barnes, M., and [RFC5838] Lindem, A., Ed., Mirtorabi, S., Roy, A., Barnes, M., and
R. Aggarwal, "Support of Address Families in OSPFv3", R. Aggarwal, "Support of Address Families in OSPFv3",
RFC 5838, DOI 10.17487/RFC5838, April 2010, RFC 5838, DOI 10.17487/RFC5838, April 2010,
<https://www.rfc-editor.org/info/rfc5838>. <https://www.rfc-editor.org/info/rfc5838>.
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010, (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,
<https://www.rfc-editor.org/info/rfc5880>. <https://www.rfc-editor.org/info/rfc5880>.
[RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, (BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881,
DOI 10.17487/RFC5881, June 2010, <https://www.rfc- DOI 10.17487/RFC5881, June 2010,
editor.org/info/rfc5881>. <https://www.rfc-editor.org/info/rfc5881>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, <https://www.rfc- DOI 10.17487/RFC6020, October 2010,
editor.org/info/rfc6020>. <https://www.rfc-editor.org/info/rfc6020>.
[RFC6021] Schoenwaelder, J., Ed., "Common YANG Data Types", [RFC6021] Schoenwaelder, J., Ed., "Common YANG Data Types",
RFC 6021, DOI 10.17487/RFC6021, October 2010, RFC 6021, DOI 10.17487/RFC6021, October 2010,
<https://www.rfc-editor.org/info/rfc6021>. <https://www.rfc-editor.org/info/rfc6021>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>. <https://www.rfc-editor.org/info/rfc6242>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536, Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012, <https://www.rfc- DOI 10.17487/RFC6536, March 2012,
editor.org/info/rfc6536>. <https://www.rfc-editor.org/info/rfc6536>.
[RFC6565] Pillay-Esnault, P., Moyer, P., Doyle, J., Ertekin, E., and [RFC6565] Pillay-Esnault, P., Moyer, P., Doyle, J., Ertekin, E., and
M. Lundberg, "OSPFv3 as a Provider Edge to Customer Edge M. Lundberg, "OSPFv3 as a Provider Edge to Customer Edge
(PE-CE) Routing Protocol", RFC 6565, DOI 10.17487/RFC6565, (PE-CE) Routing Protocol", RFC 6565, DOI 10.17487/RFC6565,
June 2012, <https://www.rfc-editor.org/info/rfc6565>. June 2012, <https://www.rfc-editor.org/info/rfc6565>.
[RFC6860] Yang, Y., Retana, A., and A. Roy, "Hiding Transit-Only [RFC6860] Yang, Y., Retana, A., and A. Roy, "Hiding Transit-Only
Networks in OSPF", RFC 6860, DOI 10.17487/RFC6860, January Networks in OSPF", RFC 6860, DOI 10.17487/RFC6860, January
2013, <https://www.rfc-editor.org/info/rfc6860>. 2013, <https://www.rfc-editor.org/info/rfc6860>.
[RFC6987] Retana, A., Nguyen, L., Zinin, A., White, R., and D. [RFC6987] Retana, A., Nguyen, L., Zinin, A., White, R., and D.
McPherson, "OSPF Stub Router Advertisement", RFC 6987, McPherson, "OSPF Stub Router Advertisement", RFC 6987,
DOI 10.17487/RFC6987, September 2013, <https://www.rfc- DOI 10.17487/RFC6987, September 2013,
editor.org/info/rfc6987>. <https://www.rfc-editor.org/info/rfc6987>.
[RFC7490] Bryant, S., Filsfils, C., Previdi, S., Shand, M., and N. [RFC7490] Bryant, S., Filsfils, C., Previdi, S., Shand, M., and N.
So, "Remote Loop-Free Alternate (LFA) Fast Reroute (FRR)", So, "Remote Loop-Free Alternate (LFA) Fast Reroute (FRR)",
RFC 7490, DOI 10.17487/RFC7490, April 2015, RFC 7490, DOI 10.17487/RFC7490, April 2015,
<https://www.rfc-editor.org/info/rfc7490>. <https://www.rfc-editor.org/info/rfc7490>.
[RFC7684] Psenak, P., Gredler, H., Shakir, R., Henderickx, W., [RFC7684] Psenak, P., Gredler, H., Shakir, R., Henderickx, W.,
Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute
Advertisement", RFC 7684, DOI 10.17487/RFC7684, November Advertisement", RFC 7684, DOI 10.17487/RFC7684, November
2015, <https://www.rfc-editor.org/info/rfc7684>. 2015, <https://www.rfc-editor.org/info/rfc7684>.
skipping to change at page 106, line 7 skipping to change at page 106, line 40
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>. <https://www.rfc-editor.org/info/rfc8040>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8177] Lindem, A., Ed., Qu, Y., Yeung, D., Chen, I., and J. [RFC8177] Lindem, A., Ed., Qu, Y., Yeung, D., Chen, I., and J.
Zhang, "YANG Data Model for Key Chains", RFC 8177, Zhang, "YANG Data Model for Key Chains", RFC 8177,
DOI 10.17487/RFC8177, June 2017, <https://www.rfc- DOI 10.17487/RFC8177, June 2017,
editor.org/info/rfc8177>. <https://www.rfc-editor.org/info/rfc8177>.
[RFC8291] Thomson, M., "Message Encryption for Web Push", RFC 8291, [RFC8291] Thomson, M., "Message Encryption for Web Push", RFC 8291,
DOI 10.17487/RFC8291, November 2017, <https://www.rfc- DOI 10.17487/RFC8291, November 2017,
editor.org/info/rfc8291>. <https://www.rfc-editor.org/info/rfc8291>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>. <https://www.rfc-editor.org/info/rfc8342>.
[RFC8343] Bjorklund, M., "A YANG Data Model for Interface [RFC8343] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
<https://www.rfc-editor.org/info/rfc8343>. <https://www.rfc-editor.org/info/rfc8343>.
[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
Routing Management (NMDA Version)", RFC 8349, Routing Management (NMDA Version)", RFC 8349,
DOI 10.17487/RFC8349, March 2018, <https://www.rfc- DOI 10.17487/RFC8349, March 2018,
editor.org/info/rfc8349>. <https://www.rfc-editor.org/info/rfc8349>.
Appendix A. Contributors' Addreses Appendix A. Contributors' Addreses
Dean Bogdanovic Dean Bogdanovic
Volta Networks, Inc. Volta Networks, Inc.
EMail: dean@voltanet.io EMail: dean@voltanet.io
Kiran Koushik Agrahara Sreenivasa Kiran Koushik Agrahara Sreenivasa
Cisco Systems Cisco Systems
 End of changes. 44 change blocks. 
109 lines changed or deleted 139 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/