< draft-ietf-lsr-ospf-yang-augmentation-v1-05.txt   draft-ietf-lsr-ospf-yang-augmentation-v1-06.txt >
Internet A. Lindem Internet A. Lindem
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Standards Track Y. Qu Intended status: Standards Track Y. Qu
Expires: December 23, 2021 Futurewei Expires: January 12, 2022 Futurewei
June 21, 2021 July 11, 2021
OSPF YANG Model Augmentations for Additional Features - Version 1 OSPF YANG Model Augmentations for Additional Features - Version 1
draft-ietf-lsr-ospf-yang-augmentation-v1-05 draft-ietf-lsr-ospf-yang-augmentation-v1-06
Abstract Abstract
This document defines YANG data modules augmenting the IETF OSPF YANG This document defines YANG data modules augmenting the IETF OSPF YANG
model to provide support for Traffic Engineering Extensions to OSPF model to provide support for Traffic Engineering Extensions to OSPF
Version 3 as defined in RF 5329, OSPF Two-Part Metric as defined in Version 3 as defined in RF 5329, OSPF Two-Part Metric as defined in
RFC 8042, OSPF Graceful Link Shutdown as defined in RFC 8379, OSPF RFC 8042, OSPF Graceful Link Shutdown as defined in RFC 8379, OSPF
Link-Local Signaling (LLS) Extensions for Local Interface ID Link-Local Signaling (LLS) Extensions for Local Interface ID
Advertisement as defined in RFC 8510 and OSPF Flexible Algorithm. Advertisement as defined in RFC 8510, OSPF Application-Specific Link
Attributes as defined in RFC 8920, and OSPF Flexible Algorithm.
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 https://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 December 23, 2021. This Internet-Draft will expire on January 12, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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
(https://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
skipping to change at page 2, line 13 skipping to change at page 2, line 14
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
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. YANG Module for Traffic Engineering Extesions to OSPF Version 2. YANG Module for Traffic Engineering Extesions to OSPF Version
3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. YANG Module for OSPF Two-Part Metric . . . . . . . . . . . . 8 3. YANG Module for OSPF Two-Part Metric . . . . . . . . . . . . 9
4. YANG Module for OSPF Graceful Link Shutdown . . . . . . . . . 13 4. YANG Module for OSPF Graceful Link Shutdown . . . . . . . . . 13
5. YANG Module for OSPF LLS Extenstion for Local Interface ID 5. YANG Module for OSPF LLS Extenstion for Local Interface ID
Advertisement . . . . . . . . . . . . . . . . . . . . . . . . 18 Advertisement . . . . . . . . . . . . . . . . . . . . . . . . 18
6. YANG Module for OSPF Application-Specific Link Attributes . . 20 6. YANG Module for OSPF Application-Specific Link Attributes . . 20
7. YANG Module for OSPF Flexible Algorithm . . . . . . . . . . . 26 7. YANG Module for OSPF Flexible Algorithm . . . . . . . . . . . 26
8. Security Considerations . . . . . . . . . . . . . . . . . . . 46 8. Security Considerations . . . . . . . . . . . . . . . . . . . 46
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 47 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 47
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 48 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 48
11. Normative References . . . . . . . . . . . . . . . . . . . . 48 11. Normative References . . . . . . . . . . . . . . . . . . . . 48
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 50 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 50
skipping to change at page 3, line 10 skipping to change at page 3, line 10
RFC8510: OSPF Link-Local Signaling (LLS) Extensions for Local RFC8510: OSPF Link-Local Signaling (LLS) Extensions for Local
Interface ID Advertisement [RFC8510]. Interface ID Advertisement [RFC8510].
RFC8920: OSPF Application-Specific Link Attributes [RFC8920]. RFC8920: OSPF Application-Specific Link Attributes [RFC8920].
RFCxxxx: IGP Flexible Algorithm [I-D.ietf-lsr-flex-algo]. RFCxxxx: IGP Flexible Algorithm [I-D.ietf-lsr-flex-algo].
The augmentations defined in this document requires support for the The augmentations defined in this document requires support for the
OSPF base model[I-D.ietf-ospf-yang] which defines basic OSPF OSPF base model[I-D.ietf-ospf-yang] which defines basic OSPF
configuration and state. The OSPF YANG model augments the ietf- configuration and state. The OSPF YANG model augments the ietf-
routing YANG model defined in [RFC8022]. routing YANG model defined in [RFC8349].
1.1. Requirements Language 1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. YANG Module for Traffic Engineering Extesions to OSPF Version 3 2. YANG Module for Traffic Engineering Extesions to OSPF Version 3
This document defines a YANG module for Traffic Engineering This document defines a YANG module for Traffic Engineering
skipping to change at page 4, line 40 skipping to change at page 4, line 40
+--ro admin-group? uint32 +--ro admin-group? uint32
+--ro neighbor-id +--ro neighbor-id
| +--ro nbr-interface-id inet:ipv4-address | +--ro nbr-interface-id inet:ipv4-address
| +--ro nbr-router-id yang:dotted-quad | +--ro nbr-router-id yang:dotted-quad
+--ro unknown-tlvs +--ro unknown-tlvs
+--ro unknown-tlv* +--ro unknown-tlv*
+--ro type? uint16 +--ro type? uint16
+--ro length? uint16 +--ro length? uint16
+--ro value? yang:hex-string +--ro value? yang:hex-string
<CODE BEGINS> file "ietf-ospfv3-te@2020-04-24.yang" <CODE BEGINS> file "ietf-ospfv3-te@2021-07-11.yang"
module ietf-ospfv3-te { module ietf-ospfv3-te {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-ospfv3-te"; namespace "urn:ietf:params:xml:ns:yang:ietf-ospfv3-te";
prefix ospfv3-te; prefix ospfv3-te;
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
reference "RFC 6991: Common YANG Data Types"; reference "RFC 6991: Common YANG Data Types";
} }
skipping to change at page 5, line 16 skipping to change at page 5, line 16
} }
import ietf-routing-types { import ietf-routing-types {
prefix "rt-types"; prefix "rt-types";
reference "RFC 8294: Common YANG Data Types for the reference "RFC 8294: Common YANG Data Types for the
Routing Area"; Routing Area";
} }
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
reference "RFC 8349: A YANG Data Model for Routing
Management (NMDA Version)";
} }
import ietf-ospf { import ietf-ospf {
prefix "ospf"; prefix "ospf";
} }
organization organization
"IETF LSR - Link State Routing Working Group"; "IETF LSR - Link State Routing Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/lsr> "WG Web: <http://tools.ietf.org/wg/lsr>
WG List: <mailto:lsr@ietf.org> WG List: <mailto:lsr@ietf.org>
Author: Yingzhen Qu Author: Yingzhen Qu
<mailto:yqu@futurewei.com> <mailto:yqu@futurewei.com>
Author: Acee Lindem Author: Acee Lindem
<mailto:acee@cisco.com>"; <mailto:acee@cisco.com>";
description description
"This YANG module defines the configuration and operational "This YANG module defines the configuration and operational
state for OSPFv3 extensions to support intra-area Traffic state for OSPFv3 extensions to support intra-area Traffic
Engineering (TE) as defined in RFC 5329. Engineering (TE) as defined in RFC 5329.
Copyright (c) 2019 IETF Trust and the persons identified as This YANG model conforms to the Network Management
Datastore Architecture (NMDA) as described in RFC 8342.
Copyright (c) 2021 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
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.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2020-04-24 { revision 2021-07-11 {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXXX: A YANG Data Model for OSPFv3 TE."; "RFC XXXX: A YANG Data Model for OSPFv3 TE.";
} }
identity ospfv3-intra-area-te-lsa { identity ospfv3-intra-area-te-lsa {
base ospf:ospfv3-lsa-type; base ospf:ospfv3-lsa-type;
description description
"OSPFv3 Intrea-area TE LSA."; "OSPFv3 intra-area TE LSA.";
} }
grouping ospfv3-intra-area-te { grouping ospfv3-intra-area-te {
description "Grouping for OSPFv3 intra-area-te-lsa."; description "Grouping for OSPFv3 intra-area-te-lsa.";
container ospfv3-intra-area-te { container ospfv3-intra-area-te {
container router-address-tlv { container router-address-tlv {
description "The router IPv6 address tlv advertises a description "The router IPv6 address tlv advertises a
reachable IPv6 address."; reachable IPv6 address.";
leaf router-address { leaf router-address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Router IPv6 address."; "Router IPv6 address.";
} }
} }
container link-tlv { container link-tlv {
description "Describes a singel link, and it is constructed description "Describes a single link, and it is constructed
of a set of Sub-TLVs."; of a set of Sub-TLVs.";
leaf link-type { leaf link-type {
type ospf:router-link-type; type ospf:router-link-type;
mandatory true; mandatory true;
description "Link type."; description "Link type.";
} }
container local-if-ipv6-addrs { container local-if-ipv6-addrs {
description "All local interface IPv6 addresses."; description "All local interface IPv6 addresses.";
leaf-list local-if-ipv6-addr { leaf-list local-if-ipv6-addr {
skipping to change at page 8, line 4 skipping to change at page 8, line 9
} }
} }
leaf admin-group { leaf admin-group {
type uint32; type uint32;
description description
"Administrative group/Resource Class/Color."; "Administrative group/Resource Class/Color.";
} }
container neighbor-id { container neighbor-id {
description "Neighbor link identitification."; description "Neighbor link identification.";
leaf nbr-interface-id { leaf nbr-interface-id {
type inet:ipv4-address; type inet:ipv4-address;
mandatory true; mandatory true;
description "The neighbor's interface ID."; description "The neighbor's interface ID.";
} }
leaf nbr-router-id { leaf nbr-router-id {
type yang:dotted-quad; type yang:dotted-quad;
mandatory true; mandatory true;
description "The neighbor's router ID."; description "The neighbor's router ID.";
} }
skipping to change at page 8, line 39 skipping to change at page 8, line 44
+ "ospf:area/ospf:database/" + "ospf:area/ospf:database/"
+ "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/"
+ "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/"
+ "ospf:ospfv3/ospf:body" { + "ospf:ospfv3/ospf:body" {
when "../../../../../../../../../" when "../../../../../../../../../"
+ "rt:type = 'ospf:ospfv3'" { + "rt:type = 'ospf:ospfv3'" {
description description
"This augmentation is only valid for OSPFv3."; "This augmentation is only valid for OSPFv3.";
} }
description description
"OSPFv3 Intrea-Area-TE-LSA."; "OSPFv3 Intra-Area-TE-LSA.";
uses ospfv3-intra-area-te; uses ospfv3-intra-area-te;
} }
} }
<CODE ENDS> <CODE ENDS>
3. YANG Module for OSPF Two-Part Metric 3. YANG Module for OSPF Two-Part Metric
This document defines a YANG module for OSPF Two-Part Metric feature This document defines a YANG module for OSPF Two-Part Metric feature
as defined in [RFC8042]. It is an augmentation of the OSPF base as defined in [RFC8042]. It is an augmentation of the OSPF base
skipping to change at page 9, line 35 skipping to change at page 9, line 41
/ospf:area-scope-lsa/ospf:version/ospf:ospfv2/ospf:ospfv2 /ospf:area-scope-lsa/ospf:version/ospf:ospfv2/ospf:ospfv2
/ospf:body/ospf:opaque/ospf:te-opaque/ospf:link-tlv: /ospf:body/ospf:opaque/ospf:te-opaque/ospf:link-tlv:
+--ro network-to-router-te-metric? uint32 +--ro network-to-router-te-metric? uint32
augment /rt:routing/rt:control-plane-protocols augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area
/ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas /ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas
/ospf:area-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3 /ospf:area-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3
/ospf:body/ospfv3-te:ospfv3-intra-area-te/ospfv3-te:link-tlv: /ospf:body/ospfv3-te:ospfv3-intra-area-te/ospfv3-te:link-tlv:
+--ro network-to-router-te-metric? uint32 +--ro network-to-router-te-metric? uint32
<CODE BEGINS> file "ietf-ospf-two-part-metric@2020-04-24.yang" <CODE BEGINS> file "ietf-ospf-two-part-metric@2021-07-11.yang"
module ietf-ospf-two-part-metric { module ietf-ospf-two-part-metric {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-two-part-metric"; namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-two-part-metric";
prefix ospf-two-metric; prefix ospf-two-metric;
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
reference "RFC 8349: A YANG Data Model for Routing
Management (NMDA Version)";
} }
import ietf-ospf { import ietf-ospf {
prefix "ospf"; prefix "ospf";
} }
import ietf-ospfv3-te { import ietf-ospfv3-te {
prefix "ospfv3-te"; prefix "ospfv3-te";
} }
organization organization
"IETF LSR - Link State Routing Working Group"; "IETF LSR - Link State Routing Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/lsr> "WG Web: <http://tools.ietf.org/wg/lsr>
WG List: <mailto:lsr@ietf.org> WG List: <mailto:lsr@ietf.org>
Author: Yingzhen Qu Author: Yingzhen Qu
<mailto:yqu@futurewei.com> <mailto:yqu@futurewei.com>
Author: Acee Lindem Author: Acee Lindem
<mailto:acee@cisco.com>"; <mailto:acee@cisco.com>";
description description
"This YANG module defines the configuration and operational "This YANG module defines the configuration and operational
state for OSPF Two-Part Metric feature as defined in RFC 8042. state for OSPF Two-Part Metric feature as defined in RFC 8042.
Copyright (c) 2019 IETF Trust and the persons identified as This YANG model conforms to the Network Management
Datastore Architecture (NMDA) as described in RFC 8342.
Copyright (c) 2021 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
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.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2020-04-24 { revision 2021-07-11 {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXXX: A YANG Data Model for OSPF."; "RFC XXXX: A YANG Data Model for OSPF.";
} }
identity two-part-metric { identity two-part-metric {
base ospf:informational-capability; base ospf:informational-capability;
description description
"When set, the router is capable of supporting OSPF "When set, the router is capable of supporting OSPF
two-part metrics."; two-part metrics.";
reference reference
"RFC 8042: OSPF Two-Part Metric"; "RFC 8042: OSPF Two-Part Metric";
} }
/* RFC 8042 */ /* RFC 8042 */
skipping to change at page 14, line 31 skipping to change at page 14, line 31
+--ro local-int-id? uint32 +--ro local-int-id? uint32
+--ro remote-int-id? uint32 +--ro remote-int-id? uint32
augment /rt:routing/rt:control-plane-protocols augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area
/ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas /ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas
/ospf:area-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3 /ospf:area-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3
/ospf:body/ospfv3-e-lsa:e-router/ospfv3-e-lsa:e-router-tlvs /ospf:body/ospfv3-e-lsa:e-router/ospfv3-e-lsa:e-router-tlvs
/ospfv3-e-lsa:link-tlv: /ospfv3-e-lsa:link-tlv:
+--ro graceful-link-shutdown-sub-tlv! +--ro graceful-link-shutdown-sub-tlv!
<CODE BEGINS> file "ietf-ospf-graceful-link-shutdown@2020-10-31.yang" <CODE BEGINS> file "ietf-ospf-graceful-link-shutdown@2021-07-11.yang"
module ietf-ospf-graceful-link-shutdown { module ietf-ospf-graceful-link-shutdown {
yang-version 1.1; yang-version 1.1;
namespace namespace
"urn:ietf:params:xml:ns:yang:ietf-ospf-graceful-link-shutdown"; "urn:ietf:params:xml:ns:yang:ietf-ospf-graceful-link-shutdown";
prefix ospf-grace-linkdown; prefix ospf-grace-linkdown;
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
reference "RFC 6991: Common YANG Data Types";
} }
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
reference "RFC 8349: A YANG Data Model for Routing
Management (NMDA Version)";
} }
import ietf-ospf { import ietf-ospf {
prefix "ospf"; prefix "ospf";
} }
import ietf-ospfv3-extended-lsa { import ietf-ospfv3-extended-lsa {
prefix "ospfv3-e-lsa"; prefix "ospfv3-e-lsa";
} }
organization organization
"IETF LSR - Link State Routing Working Group"; "IETF LSR - Link State Routing Working Group";
contact contact
skipping to change at page 15, line 27 skipping to change at page 15, line 31
<mailto:acee@cisco.com>"; <mailto:acee@cisco.com>";
description description
"This YANG module defines the configuration and operational "This YANG module defines the configuration and operational
state for OSPF Graceful Link Shutdown feature as defined state for OSPF Graceful Link Shutdown feature as defined
in RFC 8379. in RFC 8379.
This YANG model conforms to the Network Management This YANG model conforms to the Network Management
Datastore Architecture (NDMA) as described in RFC 8342. Datastore Architecture (NDMA) as described in RFC 8342.
Copyright (c) 2020 IETF Trust and the persons identified as Copyright (c) 2021 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
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.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2020-10-31 { revision 2021-07-11 {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXXX: A YANG Data Model for OSPF."; "RFC XXXX: A YANG Data Model for OSPF Graceful Link Shutdown.";
} }
/* RFC 8379 */ /* RFC 8379 */
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/ospf:ospf/" + "rt:control-plane-protocol/ospf:ospf/"
+ "ospf:areas/ospf:area/ospf:interfaces/ospf:interface" { + "ospf:areas/ospf:area/ospf:interfaces/ospf:interface" {
when "../../../../../rt:type = 'ospf:ospfv2' or " when "../../../../../rt:type = 'ospf:ospfv2' or "
+ "../../../../../rt:type = 'ospf:ospfv3'" { + "../../../../../rt:type = 'ospf:ospfv3'" {
description description
"This augments the OSPF interface configuration "This augments the OSPF interface configuration
when used."; when used.";
} }
skipping to change at page 17, line 51 skipping to change at page 18, line 4
+ "rt:type' = 'ospf:ospfv3'" { + "rt:type' = 'ospf:ospfv3'" {
description description
"This augmentation is only valid for OSPFv3 "This augmentation is only valid for OSPFv3
E-Router LSAs"; E-Router LSAs";
} }
container graceful-link-shutdown-sub-tlv { container graceful-link-shutdown-sub-tlv {
presence "Enable graceful link shutdown"; presence "Enable graceful link shutdown";
description description
"Graceful-Link-Shutdown sub-TLV identifies the link as being "Graceful-Link-Shutdown sub-TLV identifies the link as being
gracefully shutdown."; gracefully shutdown.";
} }
description description
"Augment OSPFv3 Area scope router-link TLV."; "Augment OSPFv3 Area scope router-link TLV.";
} }
} }
<CODE ENDS> <CODE ENDS>
5. YANG Module for OSPF LLS Extenstion for Local Interface ID 5. YANG Module for OSPF LLS Extenstion for Local Interface ID
Advertisement Advertisement
This document defines a YANG module for OSPF Link-Local Signaling This document defines a YANG module for OSPF Link-Local Signaling
(LLS) Extensions for Local Interface ID Advertisement feature as (LLS) Extensions for Local Interface ID Advertisement feature as
defined in [RFC8510]. It is an augmentation of the OSPF base model. defined in [RFC8510]. It is an augmentation of the OSPF base model.
module: ietf-ospf-lls-local-id module: ietf-ospf-lls-local-id
augment /rt:routing/rt:control-plane-protocols augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/ospf:ospf: /rt:control-plane-protocol/ospf:ospf:
+--rw lls-int-id +--rw lls-int-id
+--rw enable? boolean +--rw enable? boolean
<CODE BEGINS> file "ietf-ospf-lls-local-id@2020-04-24.yang" <CODE BEGINS> file "ietf-ospf-lls-local-id@2021-07-11.yang"
module ietf-ospf-lls-local-id { module ietf-ospf-lls-local-id {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-lls-local-id"; namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-lls-local-id";
prefix ospf-lls-localid; prefix ospf-lls-localid;
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
reference "RFC 8349: A YANG Data Model for Routing
Management (NMDA Version)";
} }
import ietf-ospf { import ietf-ospf {
prefix "ospf"; prefix "ospf";
} }
organization organization
"IETF LSR - Link State Routing Working Group"; "IETF LSR - Link State Routing Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/lsr> "WG Web: <http://tools.ietf.org/wg/lsr>
WG List: <mailto:lsr@ietf.org> WG List: <mailto:lsr@ietf.org>
Author: Yingzhen Qu Author: Yingzhen Qu
<mailto:yqu@futurewei.com> <mailto:yqu@futurewei.com>
Author: Acee Lindem Author: Acee Lindem
<mailto:acee@cisco.com>"; <mailto:acee@cisco.com>";
description description
"This YANG module defines the configuration and operational "This YANG module defines the configuration and operational
state for OSPF Link-Local Signaling (LLS) Extensions for Local state for OSPF Link-Local Signaling (LLS) Extensions for Local
Interface ID Advertisement feature as defined in RFC 8510. Interface ID Advertisement feature as defined in RFC 8510.
Copyright (c) 2019 IETF Trust and the persons identified as This YANG model conforms to the Network Management
Datastore Architecture (NMDA) as described in RFC 8342.
Copyright (c) 2021 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
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.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2020-04-24 { revision 2021-07-11 {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXXX: A YANG Data Model for OSPF."; "RFC XXXX: A YANG Data Model for OSPF.";
} }
augment "/rt:routing/rt:control-plane-protocols" augment "/rt:routing/rt:control-plane-protocols"
+ "/rt:control-plane-protocol/ospf:ospf" { + "/rt:control-plane-protocol/ospf:ospf" {
when "../rt:type = 'ospf:ospfv2' or " when "../rt:type = 'ospf:ospfv2' or "
+ "../rt:type = 'ospf:ospfv3'" { + "../rt:type = 'ospf:ospfv3'" {
description description
"This augments the OSPF routing protocol when used."; "This augments the OSPF routing protocol when used.";
} }
description description
"This augments the OSPF protocol configuration "This augments the OSPF protocol configuration
to support LLS extesnions for interfacde ID as to support LLS extensions for local interface ID
defined in RFC 8510."; advertisement.";
container lls-int-id { container lls-int-id {
leaf enable { leaf enable {
type boolean; type boolean;
default false; default false;
description description
"Enable LLS to advertise local interface ID."; "Enable LLS to advertise local interface ID.";
} }
description description
"OSPF LLS Extensions for interface ID."; "OSPF LLS Extensions for interface ID.";
reference "RFC 8510 - OSPF Link-Local Signaling (LLS)
Extensions for Local Interface ID Advertisement";
} }
} }
} }
<CODE ENDS> <CODE ENDS>
6. YANG Module for OSPF Application-Specific Link Attributes 6. YANG Module for OSPF Application-Specific Link Attributes
This document defines a YANG module for OSPF Application-Specific This document defines a YANG module for OSPF Application-Specific
Link Attributes feature as defined in [RFC8920]. It is an Link Attributes feature as defined in [RFC8920]. It is an
augmentation of the OSPF base model. augmentation of the OSPF base model.
skipping to change at page 49, line 38 skipping to change at page 49, line 42
[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, DOI 10.17487/RFC6536, March 2012,
<https://www.rfc-editor.org/info/rfc6536>. <https://www.rfc-editor.org/info/rfc6536>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing
Management", RFC 8022, DOI 10.17487/RFC8022, November
2016, <https://www.rfc-editor.org/info/rfc8022>.
[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>.
[RFC8042] Zhang, Z., Wang, L., and A. Lindem, "OSPF Two-Part [RFC8042] Zhang, Z., Wang, L., and A. Lindem, "OSPF Two-Part
Metric", RFC 8042, DOI 10.17487/RFC8042, December 2016, Metric", RFC 8042, DOI 10.17487/RFC8042, December 2016,
<https://www.rfc-editor.org/info/rfc8042>. <https://www.rfc-editor.org/info/rfc8042>.
[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,
 End of changes. 40 change blocks. 
38 lines changed or deleted 55 lines changed or added

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