draft-ietf-lsr-ospf-yang-augmentation-v1-01.txt   draft-ietf-lsr-ospf-yang-augmentation-v1-02.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: October 26, 2020 Futurewei Expires: January 13, 2021 Futurewei
April 24, 2020 July 12, 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-01 draft-ietf-lsr-ospf-yang-augmentation-v1-02
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 October 26, 2020. This Internet-Draft will expire on January 13, 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 17 skipping to change at page 2, line 17
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 . . . . . . . . . . . . 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. Security Considerations . . . . . . . . . . . . . . . . . . . 19 6. YANG Module for OSPF Application-Specific Link Attributes . . 19
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 7. Security Considerations . . . . . . . . . . . . . . . . . . . 26
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 21 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28
9.1. Normative References . . . . . . . . . . . . . . . . . . 21 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 28
9.2. Informative References . . . . . . . . . . . . . . . . . 23 10.1. Normative References . . . . . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 10.2. Informative References . . . . . . . . . . . . . . . . . 29
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30
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 19, line 34 skipping to change at page 19, line 34
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.";
} }
} }
} }
<CODE ENDS> <CODE ENDS>
6. Security Considerations 6. YANG Module for OSPF Application-Specific Link Attributes
This document defines a YANG module for OSPF Application-Specific
Link Attributes feature as defined in
[I-D.ietf-ospf-te-link-attr-reuse]. It is an augmentation of the
OSPF base model.
module: ietf-ospf-link-attr
augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/ospf:ospf:
+--rw ospf-link-attr
+--rw (link-attr-op-mode)
+--:(legacy)
| +--rw legacy? empty
+--:(transition)
| +--rw transition? empty
+--:(app-specific)
+--rw app-specific? empty
augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area
/ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas
/ospf:area-scope-lsa/ospf:version/ospf:ospfv2/ospf:ospfv2
/ospf:body/ospf:opaque/ospf:extended-link-opaque
/ospf:extended-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
augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area
/ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas
/ospf:area-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
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"
module ietf-ospf-link-attr {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-link-attr";
prefix ospf-link-attr;
import ietf-routing {
prefix "rt";
reference "RFC 8349: A YANG Data Model for Routing
Management (NMDA Version)";
}
import ietf-ospf {
prefix "ospf";
}
import ietf-ospfv3-extended-lsa {
prefix "ospfv3-e-lsa";
}
organization
"IETF LSR - Link State Routing Working Group";
contact
"WG Web: <http://tools.ietf.org/wg/lsr>
WG List: <mailto:lsr@ietf.org>
Author: Yingzhen Qu
<mailto:yqu@futurewei.com>
Author: Acee Lindem
<mailto:acee@cisco.com>
Author: Stephane Litkowski
<mailto:slitkows.ietf@gmail.com>";
description
"This YANG module defines the configuration and operational
state for OSPF application specific link attributes feature
as defined in RFC xxxx.
This YANG model conforms to the Network Management
Datastore Architecture (NMDA) as described in RFC 8242.
Copyright (c) 2020 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX;
see the RFC itself for full legal notices.
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
'MAY', and 'OPTIONAL' in this document are to be interpreted as
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here.";
reference "RFC XXXX";
revision 2020-07-12 {
description
"Initial version";
reference
"RFC XXXX: A YANG Data Model for OSPF application specific
link attributes.";
}
identity sabm-bit {
description
"Base identity for sabm bits.";
}
identity rsvp-te-bit {
base sabm-bit;
description
"R bit, RSVP-TE.";
}
identity sr-policy-bit {
base sabm-bit;
description
"S bit, Segment Routing Policy.";
}
identity lfa-bit {
base sabm-bit;
description
"F bit, Loop Free Alternate (LFA). Includes all LFA types.";
}
grouping application-specific-link-attributes-sub-tlvs {
description
"OSPF Application-Specific Link Attributes (ASLA) sub-TLV.
The ASLA sub-TLV is a sub-TLV of the OSPFv2 Extended Link
TLV [RFC7684] and OSPFv3 Router-Link TLV [RFC8362].";
container application-specific-link-attributes-sub-tlvs {
description "Application-Specific Link Attributes sub-TLV.";
list asla-sub-tlvs {
leaf sabm-length {
type uint8;
description
"Standard Application Identifier Bit Mask Length in
octets.";
}
leaf udabm-length {
type uint8;
description
"User Defined Application Identifier Bit Mask Length
in octets.";
}
container sabm {
leaf-list sabm-bits {
type identityref {
base sabm-bit;
}
description
"SABM bits list. This list will contain
identities for the bits which are set in the
SABA bits.";
}
description
"Standard Application Identifier Bit Mask.";
}
container udabm {
description
"User Defined Application Identifier Bit Mask.
This container is to be augmented by user defined
applications.";
}
container link-attributes-sub-sub-tlvs {
uses ospf:unknown-tlvs;
description
"Link Attributes sub-sub-TLVs.";
}
}
}
}
augment "/rt:routing/rt:control-plane-protocols"
+ "/rt:control-plane-protocol/ospf:ospf" {
when "../rt:type = 'ospf:ospfv2' or "
+ "../rt:type = 'ospf:ospfv3'" {
description
"This augments the OSPF routing protocol when used.";
}
description
"This augments OSPF protocol configuration
with application-specific link attributes.";
container ospf-link-attr {
choice link-attr-op-mode {
mandatory "true";
leaf legacy {
type empty;
description
"Only send legacy advertisements.";
}
leaf transition {
type empty;
description
"Send both application-specific and legacy advertisements.";
}
leaf app-specific{
type empty;
description
"Only send application-specific advertisements.";
}
description
"Link attributes mode";
}
description
"Link attributes operation mode.";
}
}
/* Database */
augment "/rt:routing/"
+ "rt:control-plane-protocols/rt:control-plane-protocol/"
+ "ospf:ospf/ospf:areas/"
+ "ospf:area/ospf:database/"
+ "ospf:area-scope-lsa-type/ospf:area-scope-lsas/"
+ "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/"
+ "ospf:ospfv2/ospf:body/ospf:opaque/"
+ "ospf:extended-link-opaque/ospf:extended-link-tlv" {
when "../../../../../../../../../../../../"
+ "rt:type = 'ospf:ospfv2'" {
description
"This augmentation is only valid for OSPFv2.";
}
description
"OSPF Application-Specific Link Attributes (ASLA) sub-TLV is
a sub-TLV of OSPFv2 Extended Link TLV (RFC7684).";
uses application-specific-link-attributes-sub-tlvs;
}
augment "/rt:routing/"
+ "rt:control-plane-protocols/rt:control-plane-protocol/"
+ "ospf:ospf/ospf:areas/ospf:area/ospf:database/"
+ "ospf:area-scope-lsa-type/ospf:area-scope-lsas/"
+ "ospf:area-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 Area scope router-link TLV.";
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>
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
is HTTPS, and the mandatory-to-implement secure transport is TLS is HTTPS, and the mandatory-to-implement secure transport is TLS
[RFC5246]. [RFC5246].
The NETCONF access control model [RFC6536] provides the means to The NETCONF access control model [RFC6536] provides the means to
skipping to change at page 20, line 17 skipping to change at page 27, line 5
Some of the readable data nodes in the modules may be considered Some of the readable data nodes in the modules 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 read access (e.g., via get, get-config, or important to control read access (e.g., via get, get-config, or
notification) to these data nodes. The exposure of the Link State notification) to these data nodes. The exposure of the Link State
Database (LSDB) will expose the detailed topology of the network. Database (LSDB) will expose the detailed topology of the network.
This may be undesirable since both due to the fact that exposure may This may be undesirable since both due to the fact that exposure may
facilitate other attacks. Additionally, network operators may facilitate other attacks. Additionally, network operators may
consider their topologies to be sensitive confidential data. consider their topologies to be sensitive confidential data.
7. IANA Considerations 8. IANA Considerations
This document registers URIs in the IETF XML registry [RFC3688]. This document registers URIs in the IETF XML registry [RFC3688].
Following the format in [RFC3688], the following registrations is Following the format in [RFC3688], the following registrations is
requested to be made: requested to be made:
URI: urn:ietf:params:xml:ns:yang:ietf-ospfv3-te URI: urn:ietf:params:xml:ns:yang:ietf-ospfv3-te
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace. XML: N/A, the requested URI is an XML namespace.
URI: urn:ietf:params:xml:ns:yang:ietf-ospf-two-metric URI: urn:ietf:params:xml:ns:yang:ietf-ospf-two-metric
skipping to change at page 20, line 39 skipping to change at page 27, line 27
XML: N/A, the requested URI is an XML namespace. XML: N/A, the requested URI is an XML namespace.
URI: urn:ietf:params:xml:ns:yang:ietf-ospf-grace-linkdown URI: urn:ietf:params:xml:ns:yang:ietf-ospf-grace-linkdown
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace. XML: N/A, the requested URI is an XML namespace.
URI: urn:ietf:params:xml:ns:yang:ietf-ospf-lls-localid URI: urn:ietf:params:xml:ns:yang:ietf-ospf-lls-localid
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace. XML: N/A, the requested URI is an XML namespace.
URI: urn:ietf:params:xml:ns:yang:ietf-ospf-link-attr
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
This document registers the YANG modules in the YANG Module Names This document registers the YANG modules in the YANG Module Names
registry [RFC6020]. registry [RFC6020].
name: ietf-ospfv3-te name: ietf-ospfv3-te
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
reference: RFC XXXX reference: RFC XXXX
name: ietf-ospf-two-metric name: ietf-ospf-two-metric
namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-two-metric namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-two-metric
skipping to change at page 21, line 4 skipping to change at page 27, line 43
name: ietf-ospfv3-te name: ietf-ospfv3-te
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
reference: RFC XXXX reference: RFC XXXX
name: ietf-ospf-two-metric name: ietf-ospf-two-metric
namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-two-metric namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-two-metric
prefix: ospf-two-metric prefix: ospf-two-metric
reference: RFC XXXX reference: RFC XXXX
name: ietf-ospf-grace-linkdown name: ietf-ospf-grace-linkdown
namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-grace-linkdown namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-grace-linkdown
prefix: ospf-grace-linkdown prefix: ospf-grace-linkdown
reference: RFC XXXX reference: RFC XXXX
name: ietf-ospf-lls-localid name: ietf-ospf-lls-localid
namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-lls-localid namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-lls-localid
prefix: ospf-lls-localid prefix: ospf-lls-localid
reference: RFC XXXX reference: RFC XXXX
name: ietf-ospf-link-attr
namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-link-attr
prefix: ospf-link-attr
reference: RFC XXXX
8. Acknowledgements 9. Acknowledgements
This document was produced using Marshall Rose's xml2rfc tool. This document was produced using Marshall Rose's xml2rfc tool.
The YANG model was developed using the suite of YANG tools written The YANG model was developed using the suite of YANG tools written
and maintained by numerous authors. and maintained by numerous authors.
9. References 10. References
9.1. Normative References 10.1. Normative References
[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, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
skipping to change at page 23, line 5 skipping to change at page 29, line 42
Jalil, "OSPF Graceful Link Shutdown", RFC 8379, Jalil, "OSPF Graceful Link Shutdown", RFC 8379,
DOI 10.17487/RFC8379, May 2018, DOI 10.17487/RFC8379, May 2018,
<https://www.rfc-editor.org/info/rfc8379>. <https://www.rfc-editor.org/info/rfc8379>.
[RFC8510] Psenak, P., Ed., Talaulikar, K., Henderickx, W., and P. [RFC8510] Psenak, P., Ed., Talaulikar, K., Henderickx, W., and P.
Pillay-Esnault, "OSPF Link-Local Signaling (LLS) Pillay-Esnault, "OSPF Link-Local Signaling (LLS)
Extensions for Local Interface ID Advertisement", Extensions for Local Interface ID Advertisement",
RFC 8510, DOI 10.17487/RFC8510, January 2019, RFC 8510, DOI 10.17487/RFC8510, January 2019,
<https://www.rfc-editor.org/info/rfc8510>. <https://www.rfc-editor.org/info/rfc8510>.
9.2. Informative References 10.2. Informative References
[I-D.ietf-ospf-te-link-attr-reuse]
Psenak, P., Ginsberg, L., Henderickx, W., Tantsura, J.,
and J. Drake, "OSPF Application-Specific Link Attributes",
draft-ietf-ospf-te-link-attr-reuse-16 (work in progress),
June 2020.
[I-D.ietf-ospf-yang] [I-D.ietf-ospf-yang]
Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem, Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem,
"YANG Data Model for OSPF Protocol", draft-ietf-ospf- "YANG Data Model for OSPF Protocol", draft-ietf-ospf-
yang-29 (work in progress), October 2019. yang-29 (work in progress), October 2019.
Authors' Addresses Authors' Addresses
Acee Lindem Acee Lindem
Cisco Systems Cisco Systems
 End of changes. 13 change blocks. 
17 lines changed or deleted 351 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/