draft-ietf-ospf-yang-14.txt   draft-ietf-ospf-yang-15.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 1, 2019 Huawei Expires: March 2, 2019 Huawei
J. Zhang J. Zhang
Juniper Networks Juniper Networks
I. Chen I. Chen
Jabil Jabil
A. Lindem A. Lindem
Cisco Systems Cisco Systems
August 28, 2018 August 29, 2018
Yang Data Model for OSPF Protocol Yang Data Model for OSPF Protocol
draft-ietf-ospf-yang-14 draft-ietf-ospf-yang-15
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 1, 2019. This Internet-Draft will expire on March 2, 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 6, line 5 skipping to change at page 6, line 5
suppression [RFC6860]. suppression [RFC6860].
8. ttl-security: Support OSPF Time to Live (TTL) security check 8. ttl-security: Support OSPF Time to Live (TTL) security check
suppression [RFC5082]. suppression [RFC5082].
9. nsr: Support OSPF Non-Stop Routing (NSR). 9. nsr: Support OSPF Non-Stop Routing (NSR).
10. graceful-restart: Support Graceful OSPF Restart [RFC3623], 10. graceful-restart: Support Graceful OSPF Restart [RFC3623],
[RFC5187]. [RFC5187].
11. admin-control> Support Administrative control of the protocol 11. admin-control: Support Administrative control of the protocol
state. state.
12. auto-cost: Support OSPF interface cost calculation according to 12. auto-cost: Support OSPF interface cost calculation according to
reference bandwidth [RFC2328]. reference bandwidth [RFC2328].
13. max-ecmp: Support configuration of the maximum number of Equal- 13. max-ecmp: Support configuration of the maximum number of Equal-
Cost Multi-Path (ECMP) paths. Cost Multi-Path (ECMP) paths.
14. max-lsa: Support configuration of the maximum number of LSAs the 14. max-lsa: Support configuration of the maximum number of LSAs the
OSPF instance will accept [RFC1765]. OSPF instance will accept [RFC1765].
skipping to change at page 6, line 45 skipping to change at page 6, line 45
23. stub-router: Support RFC 6987 OSPF Stub Router advertisement 23. stub-router: Support RFC 6987 OSPF Stub Router advertisement
[RFC6987]. [RFC6987].
24. pe-ce-protocol: Support OSPF as a PE-CE protocol [RFC4577], 24. pe-ce-protocol: Support OSPF as a PE-CE protocol [RFC4577],
[RFC6565]. [RFC6565].
25. ietf-spf-delay: Support IETF SPF delay algorithm [RFC8405]. 25. ietf-spf-delay: Support IETF SPF delay algorithm [RFC8405].
26. bfd: Support BFD detection of OSPF neighbor reachability 26. bfd: Support BFD detection of OSPF neighbor reachability
[RFC5880], xref target="RFC5881"/> [RFC5880], [RFC5881], and [I-D.ietf-bfd-yang].
It is expected that vendors will support additional features through It is expected that vendors will support additional features through
vendor-specific augmentations. vendor-specific augmentations.
2.5. OSPF Router Configuration/Operational State 2.5. OSPF Router Configuration/Operational State
The ospf container is the top level container in this data model. It The ospf container is the top level container in this data model. It
represents an OSPF protocol engine instance and contains the router represents an OSPF protocol engine instance and contains the router
level configuration and operational state. The operational state level configuration and operational state. The operational state
includes the instance statistics, IETF SPF delay statistics, AS- includes the instance statistics, IETF SPF delay statistics, AS-
skipping to change at page 22, line 9 skipping to change at page 22, line 9
+---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], [RFC6021], [RFC7770], [RFC8294], and [RFC4576], [RFC5250], [RFC5881], [RFC6021], [RFC7770], and [RFC8294].
[I-D.ietf-bfd-yang].
<CODE BEGINS> file "ietf-ospf@2018-08-28.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";
prefix ospf; prefix ospf;
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
reference "RFC 6021 - Common YANG Data Types"; reference "RFC 6021 - Common YANG Data Types";
} }
skipping to change at page 23, line 4 skipping to change at page 22, line 51
prefix "iana-rt-types"; prefix "iana-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 reference "RFC 8349 - A YANG Data Model for Routing
Management (NMDA Version)"; Management (NMDA Version)";
} }
import ietf-key-chain { import ietf-key-chain {
prefix "key-chain"; prefix "key-chain";
reference "RFC 8177 - YANG Data Model for Key Chains"; reference "RFC 8177 - YANG Data Model for Key Chains";
} }
import ietf-bfd-types { import ietf-bfd-types {
prefix "bfd-types"; prefix "bfd-types";
reference "RFC YYYY - YANG Data Model for Bidirectional reference "RFC YYYY - YANG Data Model for Bidirectional
Forwarding Detection (BFD)"; Forwarding Detection (BFD). Please replace YYYY with
published RFC number for draft-ietf-bfd-yang-17.";
} }
organization organization
"IETF OSPF - OSPF Working Group"; "IETF OSPF - OSPF Working Group";
contact contact
"WG Web: <http://datatracker.ietf.org/group/ospf/> "WG Web: <http://datatracker.ietf.org/group/ospf/>
WG List: <mailto:ospf@ietf.org> WG List: <mailto:ospf@ietf.org>
Editor: Derek Yeung Editor: Derek Yeung
skipping to change at page 24, line 13 skipping to change at page 24, line 13
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.";
revision 2018-08-28 { revision 2018-08-29 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for OSPF."; "RFC XXXX: A YANG Data Model for OSPF.";
} }
feature multi-topology { feature multi-topology {
description description
"Support Multiple-Topolgy Routing (MTR)."; "Support Multiple-Topolgy Routing (MTR).";
reference "RFC 4915 - Multi-Topology Routing"; reference "RFC 4915 - Multi-Topology Routing";
skipping to change at page 99, line 32 skipping to change at page 99, line 32
then error-tag and error-app-tag should be set to a then error-tag and error-app-tag should be set to a
meaningful value."; meaningful value.";
input { input {
leaf routing-protocol-name { leaf routing-protocol-name {
type leafref { type leafref {
path "/rt:routing/rt:control-plane-protocols/" path "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rt:name"; + "rt:control-plane-protocol/rt:name";
} }
mandatory "true"; mandatory "true";
description description
"OSPF protocol instance whose link-state database is to "OSPF protocol instance whose Link State Database is to
be cleared. be cleared.
If the referenced OSPF instance doesn't exist, then If the referenced OSPF instance doesn't exist, then
this operation SHALL fail with error-tag 'data-missing' this operation SHALL fail with error-tag 'data-missing'
and error-app-tag and error-app-tag
'routing-protocol-instance-not-found'."; 'routing-protocol-instance-not-found'.";
} }
} }
} }
skipping to change at page 108, line 15 skipping to change at page 108, line 15
Thanks to Tom Petch for last call review and improvement of the Thanks to Tom Petch for last call review and improvement of the
document organization. document organization.
This document was produced using Marshall Rose's xml2rfc tool. This document was produced using Marshall Rose's xml2rfc tool.
7. Normative References 7. Normative References
[I-D.ietf-bfd-yang] [I-D.ietf-bfd-yang]
Rahman, R., Zheng, L., Jethanandani, M., Networks, J., and Rahman, R., Zheng, L., Jethanandani, M., Networks, J., and
G. Mirsky, "YANG Data Model for Bidirectional Forwarding G. Mirsky, "YANG Data Model for Bidirectional Forwarding
Detection (BFD)", draft-ietf-bfd-yang-16 (work in Detection (BFD)", draft-ietf-bfd-yang-17 (work in
progress), June 2018. progress), August 2018.
[RFC0905] "ISO Transport Protocol specification ISO DP 8073", [RFC0905] "ISO Transport Protocol specification ISO DP 8073",
RFC 905, DOI 10.17487/RFC0905, April 1984, RFC 905, DOI 10.17487/RFC0905, April 1984,
<https://www.rfc-editor.org/info/rfc905>. <https://www.rfc-editor.org/info/rfc905>.
[RFC1765] Moy, J., "OSPF Database Overflow", RFC 1765, [RFC1765] Moy, J., "OSPF Database Overflow", RFC 1765,
DOI 10.17487/RFC1765, March 1995, <https://www.rfc- DOI 10.17487/RFC1765, March 1995, <https://www.rfc-
editor.org/info/rfc1765>. editor.org/info/rfc1765>.
[RFC1793] Moy, J., "Extending OSPF to Support Demand Circuits", [RFC1793] Moy, J., "Extending OSPF to Support Demand Circuits",
 End of changes. 13 change blocks. 
14 lines changed or deleted 15 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/