draft-ietf-lsr-ospf-yang-augmentation-v1-02.txt   draft-ietf-lsr-ospf-yang-augmentation-v1-03.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: January 13, 2021 Futurewei Expires: May 4, 2021 Futurewei
July 12, 2020 October 31, 2020
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-02 draft-ietf-lsr-ospf-yang-augmentation-v1-03
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 and OSPF RFC 8042, OSPF Graceful Link Shutdown as defined in RFC 8379 and 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. Advertisement as defined in RFC 8510.
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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 January 13, 2021. This Internet-Draft will expire on May 4, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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 18 skipping to change at page 2, line 18
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 . . . . . . . . . . . . 8
4. YANG Module for OSPF Graceful Link Shutdown . . . . . . . . . 12 4. YANG Module for OSPF Graceful Link Shutdown . . . . . . . . . 12
5. YANG Module for OSPF LLS Extenstion for Local Interface ID 5. YANG Module for OSPF LLS Extenstion for Local Interface ID
Advertisement . . . . . . . . . . . . . . . . . . . . . . . . 17 Advertisement . . . . . . . . . . . . . . . . . . . . . . . . 17
6. YANG Module for OSPF Application-Specific Link Attributes . . 19 6. YANG Module for OSPF Application-Specific Link Attributes . . 19
7. Security Considerations . . . . . . . . . . . . . . . . . . . 26 7. Security Considerations . . . . . . . . . . . . . . . . . . . 25
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 26
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 28 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 26
10.1. Normative References . . . . . . . . . . . . . . . . . . 28 10.1. Normative References . . . . . . . . . . . . . . . . . . 27
10.2. Informative References . . . . . . . . . . . . . . . . . 29 10.2. Informative References . . . . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28
1. Overview 1. Overview
YANG [RFC6020] [RFC7950] is a data definition language used to define YANG [RFC6020] [RFC7950] is a data definition language used to define
the contents of a conceptual data store that allows networked devices the contents of a conceptual data store that allows networked devices
to be managed using NETCONF [RFC6241]. YANG is proving relevant to be managed using NETCONF [RFC6241]. YANG is proving relevant
beyond its initial confines, as bindings to other interfaces (e.g., beyond its initial confines, as bindings to other interfaces (e.g.,
ReST) and encodings other than XML (e.g., JSON) are being defined. ReST) 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 13, line 30 skipping to change at page 13, line 30
+--ro local-remote-int-id-sub-tlv +--ro local-remote-int-id-sub-tlv
+--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!
augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/ospf:ospf/ospf:database
/ospf:as-scope-lsa-type/ospf:as-scope-lsas/ospf:as-scope-lsa
/ospf:version/ospf:ospfv3/ospf:ospfv3/ospf:body
/ospfv3-e-lsa:e-router/ospfv3-e-lsa:e-router-tlvs
/ospfv3-e-lsa:link-tlv:
+--ro graceful-link-shutdown-sub-tlv!
<CODE BEGINS> file "ietf-ospf-graceful-link-shutdown@2020-04-24.yang" <CODE BEGINS> file "ietf-ospf-graceful-link-shutdown@2020-10-31.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";
} }
skipping to change at page 14, line 29 skipping to change at page 14, line 21
"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 Graceful Link Shutdown feature as defined state for OSPF Graceful Link Shutdown feature as defined
in RFC 8379. in RFC 8379.
Copyright (c) 2019 IETF Trust and the persons identified as This YANG model conforms to the Network Management
Datastore Architecture (NDMA) as described in RFC 8342.
Copyright (c) 2020 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 2020-10-31 {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXXX: A YANG Data Model for OSPF."; "RFC XXXX: A YANG Data Model for OSPF.";
} }
/* 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
skipping to change at page 17, line 9 skipping to change at page 17, line 4
"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
"Augemnt OSPFv3 Area scope router-link TLV."; "Augment OSPFv3 Area scope router-link TLV.";
}
augment "/rt:routing/"
+ "rt:control-plane-protocols/rt:control-plane-protocol/"
+ "ospf:ospf/ospf:database/"
+ "ospf:as-scope-lsa-type/ospf:as-scope-lsas/"
+ "ospf:as-scope-lsa/ospf:version/ospf:ospfv3/"
+ "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-router"
+ "/ospfv3-e-lsa:e-router-tlvs/ospfv3-e-lsa:link-tlv" {
when "'ospf:../../../../../../../"
+ "rt:type' = 'ospf:ospfv3'" {
description
"This augmentation is only valid for OSPFv3
E-Router LSAs";
}
container graceful-link-shutdown-sub-tlv {
presence "Enable graceful link shutdown";
description
"Graceful-Link-Shutdown sub-TLV identifies the link as being
gracefully shutdown.";
}
description
"Augemnt OSPFv3 AS 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.
skipping to change at page 20, line 43 skipping to change at page 20, line 14
+--ro udabm-length? uint8 +--ro udabm-length? uint8
+--ro sabm +--ro sabm
| +--ro sabm-bits* identityref | +--ro sabm-bits* identityref
+--ro udabm +--ro udabm
+--ro link-attributes-sub-sub-tlvs +--ro link-attributes-sub-sub-tlvs
+--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
augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/ospf:ospf/ospf:database
/ospf:as-scope-lsa-type/ospf:as-scope-lsas/ospf:as-scope-lsa
/ospf:version/ospf:ospfv3/ospf:ospfv3/ospf:body
/ospfv3-e-lsa:e-router/ospfv3-e-lsa:e-router-tlvs
/ospfv3-e-lsa:link-tlv:
+--ro application-specific-link-attributes-sub-tlvs
+--ro asla-sub-tlvs* []
+--ro sabm-length? uint8
+--ro udabm-length? uint8
+--ro sabm
| +--ro sabm-bits* identityref
+--ro udabm
+--ro link-attributes-sub-sub-tlvs
+--ro unknown-tlvs
+--ro unknown-tlv* []
+--ro type? uint16
+--ro length? uint16
+--ro value? yang:hex-string
<CODE BEGINS> file "ietf-ospf-link-attr@2020-07-12.yang" <CODE BEGINS> file "ietf-ospf-link-attr@2020-10-31.yang"
module ietf-ospf-link-attr { module ietf-ospf-link-attr {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-link-attr"; namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-link-attr";
prefix ospf-link-attr; prefix ospf-link-attr;
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
reference "RFC 8349: A YANG Data Model for Routing reference "RFC 8349: A YANG Data Model for Routing
Management (NMDA Version)"; Management (NMDA Version)";
skipping to change at page 22, line 8 skipping to change at page 21, line 8
<mailto:acee@cisco.com> <mailto:acee@cisco.com>
Author: Stephane Litkowski Author: Stephane Litkowski
<mailto:slitkows.ietf@gmail.com>"; <mailto:slitkows.ietf@gmail.com>";
description description
"This YANG module defines the configuration and operational "This YANG module defines the configuration and operational
state for OSPF application specific link attributes feature state for OSPF application specific link attributes feature
as defined in RFC xxxx. as defined in RFC xxxx.
This YANG model conforms to the Network Management This YANG model conforms to the Network Management
Datastore Architecture (NMDA) as described in RFC 8242. Datastore Architecture (NMDA) as described in RFC 8342.
Copyright (c) 2020 IETF Trust and the persons identified as Copyright (c) 2020 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).
skipping to change at page 22, line 31 skipping to change at page 21, line 31
see the RFC itself for full legal notices. see the RFC itself for full legal notices.
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
'MAY', and 'OPTIONAL' in this document are to be interpreted as 'MAY', and 'OPTIONAL' in this document are to be interpreted as
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here."; they appear in all capitals, as shown here.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2020-07-12 { revision 2020-10-31 {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXXX: A YANG Data Model for OSPF application specific "RFC XXXX: A YANG Data Model for OSPF application specific
link attributes."; link attributes.";
} }
identity sabm-bit { identity sabm-bit {
description description
"Base identity for sabm bits."; "Base identity for sabm bits.";
skipping to change at page 24, line 11 skipping to change at page 23, line 11
description description
"User Defined Application Identifier Bit Mask. "User Defined Application Identifier Bit Mask.
This container is to be augmented by user defined This container is to be augmented by user defined
applications."; applications.";
} }
container link-attributes-sub-sub-tlvs { container link-attributes-sub-sub-tlvs {
uses ospf:unknown-tlvs; uses ospf:unknown-tlvs;
description description
"Link Attributes sub-sub-TLVs."; "Link Attributes sub-sub-TLVs.";
} }
description
"List of application-Specific Link Attributes sub-TLVs.";
} }
} }
} }
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.";
skipping to change at page 25, line 43 skipping to change at page 24, line 46
+ "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";
} }
description description
"Augment OSPFv3 Area scope router-link TLV."; "Augment OSPFv3 Area scope router-link TLV.";
uses application-specific-link-attributes-sub-tlvs; uses application-specific-link-attributes-sub-tlvs;
} }
augment "/rt:routing/"
+ "rt:control-plane-protocols/rt:control-plane-protocol/"
+ "ospf:ospf/ospf:database/"
+ "ospf:as-scope-lsa-type/ospf:as-scope-lsas/"
+ "ospf:as-scope-lsa/ospf:version/ospf:ospfv3/"
+ "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-router"
+ "/ospfv3-e-lsa:e-router-tlvs/ospfv3-e-lsa:link-tlv" {
when "'ospf:../../../../../../../"
+ "rt:type' = 'ospf:ospfv3'" {
description
"This augmentation is only valid for OSPFv3
E-Router LSAs";
}
description
"Augment OSPFv3 AS scope router-link TLV.";
uses application-specific-link-attributes-sub-tlvs;
}
} }
<CODE ENDS> <CODE ENDS>
7. Security Considerations 7. Security Considerations
The YANG modules specified in this document define a schema for data The YANG modules specified in this document define a schema for data
that is designed to be accessed via network management protocols such that is designed to be accessed via network management protocols such
as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
is the secure transport layer, and the mandatory-to-implement secure is the secure transport layer, and the mandatory-to-implement secure
transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
 End of changes. 17 change blocks. 
89 lines changed or deleted 25 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/