draft-ietf-ospf-yang-16.txt   draft-ietf-ospf-yang-17.txt 
Internet D. Yeung Internet D. Yeung
Internet-Draft Arrcus Internet-Draft Arrcus
Intended status: Standards Track Y. Qu Intended status: Standards Track Y. Qu
Expires: March 15, 2019 Huawei Expires: March 16, 2019 Huawei
J. Zhang J. Zhang
Juniper Networks Juniper Networks
I. Chen I. Chen
MITRE Corporation MITRE Corporation
A. Lindem A. Lindem
Cisco Systems Cisco Systems
September 11, 2018 September 12, 2018
Yang Data Model for OSPF Protocol YANG Data Model for OSPF Protocol
draft-ietf-ospf-yang-16 draft-ietf-ospf-yang-17
Abstract Abstract
This document defines a YANG data model that can be used to configure This document defines a YANG data model that can be used to configure
and manage OSPF. The model is based on YANG 1.1 as defined in RFC and manage OSPF. The model is based on YANG 1.1 as defined in RFC
7950 and conforms to the Network Management Datastore Architecture 7950 and conforms to the Network Management Datastore Architecture
(NDMA) as described in RFC 8342. (NDMA) as described in RFC 8342.
Status of This Memo Status of This Memo
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 15, 2019. This Internet-Draft will expire on March 16, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 26 skipping to change at page 2, line 26
2. Design of Data Model . . . . . . . . . . . . . . . . . . . . 3 2. Design of Data Model . . . . . . . . . . . . . . . . . . . . 3
2.1. OSPF Operational State . . . . . . . . . . . . . . . . . 3 2.1. OSPF Operational State . . . . . . . . . . . . . . . . . 3
2.2. Overview . . . . . . . . . . . . . . . . . . . . . . . . 4 2.2. Overview . . . . . . . . . . . . . . . . . . . . . . . . 4
2.3. OSPFv2 and OSPFv3 . . . . . . . . . . . . . . . . . . . . 5 2.3. OSPFv2 and OSPFv3 . . . . . . . . . . . . . . . . . . . . 5
2.4. Optional Features . . . . . . . . . . . . . . . . . . . . 5 2.4. Optional Features . . . . . . . . . . . . . . . . . . . . 5
2.5. OSPF Router Configuration/Operational State . . . . . . . 7 2.5. OSPF Router Configuration/Operational State . . . . . . . 7
2.6. OSPF Area Configuration/Operational State . . . . . . . . 10 2.6. OSPF Area Configuration/Operational State . . . . . . . . 10
2.7. OSPF Interface Configuration/Operational State . . . . . 15 2.7. OSPF Interface Configuration/Operational State . . . . . 15
2.8. OSPF notification . . . . . . . . . . . . . . . . . . . . 17 2.8. OSPF notification . . . . . . . . . . . . . . . . . . . . 17
2.9. OSPF RPC Operations . . . . . . . . . . . . . . . . . . . 21 2.9. OSPF RPC Operations . . . . . . . . . . . . . . . . . . . 21
3. OSPF Yang Module . . . . . . . . . . . . . . . . . . . . . . 22 3. OSPF YANG Module . . . . . . . . . . . . . . . . . . . . . . 22
4. Security Considerations . . . . . . . . . . . . . . . . . . . 106 4. Security Considerations . . . . . . . . . . . . . . . . . . . 106
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 107 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 107
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 107 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 107
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 108 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 108
7.1. Normative References . . . . . . . . . . . . . . . . . . 108 7.1. Normative References . . . . . . . . . . . . . . . . . . 108
7.2. Informative References . . . . . . . . . . . . . . . . . 112 7.2. Informative References . . . . . . . . . . . . . . . . . 112
Appendix A. Contributors' Addreses . . . . . . . . . . . . . . . 114 Appendix A. Contributors' Addreses . . . . . . . . . . . . . . . 114
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 114 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 114
1. Overview 1. Overview
skipping to change at page 22, line 5 skipping to change at page 22, line 5
| +---w routing-protocol-name | +---w routing-protocol-name
| + -> /rt:routing/control-plane-protocols/ | + -> /rt:routing/control-plane-protocols/
| + control-plane-protocol/name | + control-plane-protocol/name
| +---w interface? if:interface-ref | +---w interface? if:interface-ref
+---x clear-database +---x clear-database
+---w input +---w input
+---w routing-protocol-name +---w routing-protocol-name
-> /rt:routing/control-plane-protocols/ -> /rt:routing/control-plane-protocols/
control-plane-protocol/name control-plane-protocol/name
3. OSPF Yang Module 3. OSPF 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-ospf.yang module: [RFC0905], but are referenced in the ietf-ospf.yang module: [RFC0905],
[RFC4576], [RFC5250], [RFC5881], [RFC6991], [RFC7770], and [RFC8294]. [RFC4576], [RFC5250], [RFC5881], [RFC6991], [RFC7770], and [RFC8294].
<CODE BEGINS> file "ietf-ospf@2018-08-29.yang" <CODE BEGINS> file "ietf-ospf@2018-08-29.yang"
module ietf-ospf { module ietf-ospf {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-ospf"; namespace "urn:ietf:params:xml:ns:yang:ietf-ospf";
skipping to change at page 107, line 24 skipping to change at page 107, line 24
For OSPF authentication, configuration is supported via the For OSPF authentication, configuration is supported via the
specification of key-chains [RFC8177] or the direct specification of specification of key-chains [RFC8177] or the direct specification of
key and authentication algorithm. Hence, authentification key and authentication algorithm. Hence, authentification
configuration using the "auth-table-trailer" case in the configuration using the "auth-table-trailer" case in the
"authentication" container inherits the security considerations of "authentication" container inherits the security considerations of
[RFC8177]. This includes the considerations with respect to the [RFC8177]. This includes the considerations with respect to the
local storage and handling of authentication keys. local storage and handling of authentication keys.
Some of the RPC operations in this YANG module may be considered Some of the RPC operations in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus sensitive or vulnerable in some network environments. It is thus
important to control access to these operations. The OSPF Yang important to control access to these operations. The OSPF YANG
module support the "clear-neighbor" and "clear-database" RPCs. If module support the "clear-neighbor" and "clear-database" RPCs. If
access too either of these is compromised, they can result in access too either of these is compromised, they can result in
temporary network outages be employed to mount DoS attacks. temporary network outages be employed to mount DoS attacks.
5. IANA Considerations 5. 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:
skipping to change at page 114, line 46 skipping to change at page 114, line 46
Juniper Networks Juniper Networks
10 Technology Park Drive 10 Technology Park Drive
Westford, MA 01886 Westford, MA 01886
USA USA
EMail: zzhang@juniper.net EMail: zzhang@juniper.net
Ing-Wher Chen Ing-Wher Chen
MITRE Corporation MITRE Corporation
EMail: ing-wher_chen@mitre.org EMail: ingwherchen@mitre.org
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
 End of changes. 8 change blocks. 
9 lines changed or deleted 9 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/