< draft-ietf-lsr-ospfv3-extended-lsa-yang-09.txt   draft-ietf-lsr-ospfv3-extended-lsa-yang-10.txt >
Internet A. Lindem Internet A. Lindem
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Standards Track S. Palani Intended status: Standards Track S. Palani
Expires: March 31, 2022 Microsoft Expires: 7 September 2022 Microsoft
Y. Qu Y. Qu
Futurewei Futurewei
September 27, 2021 6 March 2022
YANG Model for OSPFv3 Extended LSAs YANG Model for OSPFv3 Extended LSAs
draft-ietf-lsr-ospfv3-extended-lsa-yang-09 draft-ietf-lsr-ospfv3-extended-lsa-yang-10
Abstract Abstract
This document defines a YANG data model augmenting the IETF OSPF YANG This document defines a YANG data model augmenting the IETF OSPF YANG
model to provide support for OSPFv3 Link State Advertisement (LSA) model to provide support for OSPFv3 Link State Advertisement (LSA)
Extensibility as defined in RFC 8362. OSPFv3 Extended LSAs provide Extensibility as defined in RFC 8362. OSPFv3 Extended LSAs provide
extensible TLV-based LSAs for the base LSA types defined in RFC 5340. extensible TLV-based LSAs for the base LSA types defined in RFC 5340.
Status of This Memo Status of This Memo
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 March 31, 2022. This Internet-Draft will expire on 7 September 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2022 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/
(https://trustee.ietf.org/license-info) in effect on the date of license-info) in effect on the date of publication of this document.
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document. Code Components
to this document. Code Components extracted from this document must extracted from this document must include Revised BSD License text as
include Simplified BSD License text as described in Section 4.e of described in Section 4.e of the Trust Legal Provisions and are
the Trust Legal Provisions and are provided without warranty as provided without warranty as described in the Revised BSD License.
described in the Simplified BSD License.
Table of Contents Table of Contents
1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . . . 3
3. OSPFv3 Extended LSAs . . . . . . . . . . . . . . . . . . . . 3 3. OSPFv3 Extended LSAs . . . . . . . . . . . . . . . . . . . . 3
4. OSPFv3 Extended LSA Yang Module . . . . . . . . . . . . . . . 7 4. OSPFv3 Extended LSA Yang Module . . . . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 25 5. Security Considerations . . . . . . . . . . . . . . . . . . . 25
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 26 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 26
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 26 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 27
8.1. Normative References . . . . . . . . . . . . . . . . . . 26 8.1. Normative References . . . . . . . . . . . . . . . . . . 27
8.2. Informative References . . . . . . . . . . . . . . . . . 28 8.2. Informative References . . . . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28
1. Overview 1. Overview
YANG [RFC6020] [RFC7950] is a data definition language used to define YANG [RFC7950] is a data definition language used to define the
the contents of a conceptual data store that allows networked devices contents of a conceptual data store that allows networked devices to
to be managed using NETCONF [RFC6241]. YANG is proving relevant be managed using NETCONF [RFC6241]. YANG is proving relevant beyond
beyond its initial confines, as bindings to other interfaces (e.g., its initial confines, as bindings to other interfaces (e.g., ReST)
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
APIs. APIs.
This document defines a YANG data model augmenting the IETF OSPF YANG This document defines a YANG data model augmenting the IETF OSPF YANG
model [I-D.ietf-ospf-yang], which itself augments [RFC8349], to model [I-D.ietf-ospf-yang], which itself augments [RFC8349], to
provide support for configuration and operational state for OSPFv3 provide support for configuration and operational state for OSPFv3
Extended LSAs as defined in [RFC8362]. Extended LSAs as defined in [RFC8362].
The YANG modules in this document conform to the Network Management The YANG modules in this document conform to the Network Management
skipping to change at page 7, line 49 skipping to change at page 8, line 11
+--ro route-tag-sub-tlv +--ro route-tag-sub-tlv
+--ro route-tag-sub-tlv-length? uint16 +--ro route-tag-sub-tlv-length? uint16
+--ro route-tag? uint32 +--ro route-tag? uint32
4. OSPFv3 Extended LSA Yang Module 4. OSPFv3 Extended LSA Yang Module
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-ospfv3-extended-lsa.yang module: but are referenced in the ietf-ospfv3-extended-lsa.yang module:
[RFC6991], [RFC8294]. [RFC6991], [RFC8294].
<CODE BEGINS> file "ietf-ospfv3-extended-lsa@2020-10-01.yang" <CODE BEGINS> file "ietf-ospfv3-extended-lsa@2022-03-06.yang"
module ietf-ospfv3-extended-lsa { module ietf-ospfv3-extended-lsa {
yang-version 1.1; yang-version 1.1;
namespace namespace
"urn:ietf:params:xml:ns:yang:ietf-ospfv3-extended-lsa"; "urn:ietf:params:xml:ns:yang:ietf-ospfv3-extended-lsa";
prefix ospfv3-e-lsa; prefix ospfv3-e-lsa;
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
skipping to change at page 8, line 44 skipping to change at page 9, line 4
"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: Acee Lindem Author: Acee Lindem
<mailto:acee@cisco.com> <mailto:acee@cisco.com>
Author: Sharmila Palani Author: Sharmila Palani
<mailto:sharmila.palani@microsoft.com> <mailto:sharmila.palani@microsoft.com>
Author: Yingzhen Qu Author: Yingzhen Qu
<mailto:yingzhen.qu@futurewei.com>"; <mailto:yingzhen.qu@futurewei.com>";
description description
"This YANG module defines the configuration "This YANG module defines the configuration
and operational state for OSPFv3 Extended LSAs, which is and operational state for OSPFv3 Extended LSAs, which is
common across all of the vendor implementations. The common across all of the vendor implementations. The
semantics and encodings for OSPFv3 Extended LSAs is semantics and encodings for OSPFv3 Extended LSAs is
described in RFC 8362. described in RFC 8362.
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) 2022 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 - YANG Model for OSPFv3 Extended LSAs"; reference "RFC XXXX - YANG Model for OSPFv3 Extended LSAs";
revision 2020-10-01 { revision 2022-03-06 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for OSPFv3 Extended LSAs."; "RFC XXXX: A YANG Data Model for OSPFv3 Extended LSAs.";
} }
/* /*
* OSPFv3 Extend LSA Type Identities * OSPFv3 Extend LSA Type Identities
*/ */
identity ospfv3-e-router-lsa { identity ospfv3-e-router-lsa {
skipping to change at page 25, line 43 skipping to change at page 26, line 10
The NETCONF access control model [RFC6536] provides the means to The NETCONF access control model [RFC6536] provides the means to
restrict access for particular NETCONF or RESTCONF users to a pre- restrict access for particular NETCONF or RESTCONF users to a pre-
configured subset of all available NETCONF or RESTCONF protocol configured subset of all available NETCONF or RESTCONF protocol
operations and content. operations and content.
There are a number of data nodes defined in ietf-ospfv3-extended- There are a number of data nodes defined in ietf-ospfv3-extended-
lsa.yang module that are writable/creatable/deletable (i.e., config lsa.yang module that are writable/creatable/deletable (i.e., config
true, which is the default). These data nodes may be considered true, which is the default). These data nodes may be considered
sensitive or vulnerable in some network environments. Write sensitive or vulnerable in some network environments. Write
operations (e.g., edit-config) to these data nodes without proper operations (e.g., edit-config) to these data nodes without proper
protection can have a negative effect on network operations. For protection can have a negative effect on network operations. There
OSPFv3 Extended LSAs, the ability to disable OSPFv3 Extended LSA are the subtrees and data nodes and their sensitivity/vlunerability:
support result in a denial of service.
/ospf:ospf/extended-lsa-support
/ospf:ospf/ospf:areas/ospf:area/extended-lsa-support - For OSPFv3
Extended LSAs, the ability to disable OSPFv3 Extended LSA support
result in a denial of service.
Some of the readable data nodes in the ietf-ospfv3-extended-lsa.yang Some of the readable data nodes in the ietf-ospfv3-extended-lsa.yang
module may be considered sensitive or vulnerable in some network module may be considered sensitive or vulnerable in some network
environments. It is thus important to control read access (e.g., via environments. It is thus important to control read access (e.g., via
get, get-config, or notification) to these data nodes. The exposure get, get-config, or notification) to these data nodes. The exposure
of the Link State Database (LSDB) will expose the detailed topology of the Link State Database (LSDB) will expose the detailed topology
of the network. This may be undesirable since both due to the fact of the network and information beyond the scope of OSPF router. This
that exposure may facilitate other attacks. Additionally, network may be undesirable since both due to the fact that exposure may
operators may consider their topologies to be sensitive confidential facilitate other attacks. Additionally, network operators may
data. consider their topologies to be sensitive confidential data.
6. IANA Considerations 6. IANA Considerations
This document registers a URI in the IETF XML registry [RFC3688]. This document registers a URI in the IETF XML registry [RFC3688].
Following the format in [RFC3688], the following registration is Following the format in [RFC3688], the following registration is
requested to be made: requested to be made:
URI: urn:ietf:params:xml:ns:yang:ietf-ospfv3-extended-lsa URI: urn:ietf:params:xml:ns:yang:ietf-ospfv3-extended-lsa
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.
skipping to change at page 26, line 42 skipping to change at page 27, line 13
and maintained by numerous authors. and maintained by numerous authors.
Thanks much to Tom Petch for his review and comments. Thanks much to Tom Petch for his review and comments.
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.ietf-ospf-yang] [I-D.ietf-ospf-yang]
Yeung, D., Qu, Y., Zhang, J., Chen, I., and A. Lindem, Yeung, D., Qu, Y., Zhang, J., Chen, I., and A. Lindem,
"YANG Data Model for OSPF Protocol", draft-ietf-ospf- "YANG Data Model for OSPF Protocol", Work in Progress,
yang-29 (work in progress), October 2019. Internet-Draft, draft-ietf-ospf-yang-29, 17 October 2019,
<https://www.ietf.org/archive/id/draft-ietf-ospf-yang-
29.txt>.
[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 28, line 36 skipping to change at page 29, line 4
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>. <https://www.rfc-editor.org/info/rfc8446>.
8.2. Informative References 8.2. Informative References
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>. <https://www.rfc-editor.org/info/rfc8340>.
Authors' Addresses Authors' Addresses
Acee Lindem Acee Lindem
Cisco Systems Cisco Systems
301 Midenhall Way 301 Midenhall Way
Cary, NC 27513 Cary, NC 27513
Email: acee@cisco.com
EMail: acee@cisco.com
Sharmila Palani Sharmila Palani
Microsoft Microsoft
1 Microsoft Way 1 Microsoft Way
Redmond, WA 98052 Redmond, WA 98052
Email: sharmila.palani@microsoft.com
EMail: sharmila.palani@microsoft.com
Yingzhen Qu Yingzhen Qu
Futurewei Futurewei
2330 Central Expressway 2330 Central Expressway
Santa Clara, CA 95050 Santa Clara, CA 95050
USA United States of America
Email: yingzhen.qu@futurewei.com
EMail: yingzhen.qu@futurewei.com
 End of changes. 23 change blocks. 
39 lines changed or deleted 44 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/