draft-ietf-ospf-yang-25.txt   draft-ietf-ospf-yang-26.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: February 6, 2020 Huawei Expires: February 8, 2020 Futurewei
J. Zhang J. Zhang
Juniper Networks Juniper Networks
I. Chen I. Chen
The MITRE Corporation The MITRE Corporation
A. Lindem A. Lindem
Cisco Systems Cisco Systems
August 5, 2019 August 7, 2019
YANG Data Model for OSPF Protocol YANG Data Model for OSPF Protocol
draft-ietf-ospf-yang-25 draft-ietf-ospf-yang-26
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 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 February 6, 2020. This Internet-Draft will expire on February 8, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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 23, line 35 skipping to change at page 23, line 35
-> /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], [RFC4973], [RFC5250], [RFC5309], [RFC5642], [RFC5881], [RFC4576], [RFC4973], [RFC5250], [RFC5309], [RFC5642], [RFC5881],
[RFC6991], [RFC7770], [RFC7884], [RFC8294], and [RFC8476]. [RFC6991], [RFC7770], [RFC7884], [RFC8294], and [RFC8476].
<CODE BEGINS> file "ietf-ospf@2019-08-05.yang" <CODE BEGINS> file "ietf-ospf@2019-08-07.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 6991: Common YANG Data Types"; reference "RFC 6991: Common YANG Data Types";
} }
skipping to change at page 24, line 51 skipping to change at page 24, line 51
contact contact
"WG Web: <https://datatracker.ietf.org/group/lsr/> "WG Web: <https://datatracker.ietf.org/group/lsr/>
WG List: <mailto:lsr@ietf.org> WG List: <mailto:lsr@ietf.org>
Editor: Derek Yeung Editor: Derek Yeung
<mailto:derek@arrcus.com> <mailto:derek@arrcus.com>
Author: Acee Lindem Author: Acee Lindem
<mailto:acee@cisco.com> <mailto:acee@cisco.com>
Author: Yingzhen Qu Author: Yingzhen Qu
<mailto:yingzhen.qu@huawei.com> <mailto:yingzhen.qu@futurewei.com>
Author: Salih K A Author: Salih K A
<mailto:salih@juniper.net> <mailto:salih@juniper.net>
Author: Ing-Wher Chen Author: Ing-Wher Chen
<mailto:ingwherchen@mitre.org>"; <mailto:ingwherchen@mitre.org>";
description description
"This YANG module defines the generic configuration and "This YANG module defines the generic configuration and
operational state for the OSPF protocol common to all operational state for the OSPF protocol common to all
vendor implementations. It is intended that the module vendor implementations. It is intended that the module
skipping to change at page 25, line 44 skipping to change at page 25, line 44
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.
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 2019-08-05 { revision 2019-08-07 {
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-Topology Routing (MTR)."; "Support Multiple-Topology Routing (MTR).";
reference "RFC 4915: Multi-Topology Routing"; reference "RFC 4915: Multi-Topology Routing";
skipping to change at page 54, line 41 skipping to change at page 54, line 41
container router-address-tlv { container router-address-tlv {
description description
"Router address TLV."; "Router address TLV.";
leaf router-address { leaf router-address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"Router address."; "Router address.";
} }
} }
container link-tlvs { container link-tlv {
description "All link TLVs in the LSA."; description "Describes a singel link, and it is constructed
list link-tlv { of a set of Sub-TLVs.";
description "Link TLV."; leaf link-type {
leaf link-type { type router-link-type;
type router-link-type; mandatory true;
mandatory true; description "Link type.";
description "Link type."; }
} leaf link-id {
leaf link-id { type union {
type union { type inet:ipv4-address;
type inet:ipv4-address; type yang:dotted-quad;
type yang:dotted-quad;
}
mandatory true;
description "Link ID.";
}
container local-if-ipv4-addrs {
description "All local interface IPv4 addresses.";
leaf-list local-if-ipv4-addr {
type inet:ipv4-address;
description
"List of local interface IPv4 addresses.";
}
}
container remote-if-ipv4-addrs {
description "All remote interface IPv4 addresses.";
leaf-list remote-if-ipv4-addr {
type inet:ipv4-address;
description
"List of remote interface IPv4 addresses.";
}
}
leaf te-metric {
type uint32;
description "TE metric.";
} }
leaf max-bandwidth { mandatory true;
type rt-types:bandwidth-ieee-float32; description "Link ID.";
description "Maximum bandwidth."; }
container local-if-ipv4-addrs {
description "All local interface IPv4 addresses.";
leaf-list local-if-ipv4-addr {
type inet:ipv4-address;
description
"List of local interface IPv4 addresses.";
} }
leaf max-reservable-bandwidth { }
type rt-types:bandwidth-ieee-float32; container remote-if-ipv4-addrs {
description "Maximum reservable bandwidth."; description "All remote interface IPv4 addresses.";
leaf-list remote-if-ipv4-addr {
type inet:ipv4-address;
description
"List of remote interface IPv4 addresses.";
} }
container unreserved-bandwidths { }
description "All unreserved bandwidths."; leaf te-metric {
list unreserved-bandwidth { type uint32;
leaf priority { description "TE metric.";
type uint8 { }
range "0 .. 7"; leaf max-bandwidth {
} type rt-types:bandwidth-ieee-float32;
description "Priority from 0 to 7."; description "Maximum bandwidth.";
} }
leaf unreserved-bandwidth { leaf max-reservable-bandwidth {
type rt-types:bandwidth-ieee-float32; type rt-types:bandwidth-ieee-float32;
description "Unreserved bandwidth."; description "Maximum reservable bandwidth.";
}
container unreserved-bandwidths {
description "All unreserved bandwidths.";
list unreserved-bandwidth {
leaf priority {
type uint8 {
range "0 .. 7";
} }
description description "Priority from 0 to 7.";
"List of unreserved bandwidths for different }
priorities."; leaf unreserved-bandwidth {
type rt-types:bandwidth-ieee-float32;
description "Unreserved bandwidth.";
} }
}
leaf admin-group {
type uint32;
description description
"Administrative group/Resource Class/Color."; "List of unreserved bandwidths for different
priorities.";
} }
uses unknown-tlvs;
} }
leaf admin-group {
type uint32;
description
"Administrative group/Resource Class/Color.";
}
uses unknown-tlvs;
} }
uses unknown-tlvs;
} }
container extended-prefix-opaque { container extended-prefix-opaque {
description "All extended prefix TLVs in the LSA."; description "All extended prefix TLVs in the LSA.";
list extended-prefix-tlv { list extended-prefix-tlv {
description "Extended prefix TLV."; description "Extended prefix TLV.";
leaf route-type { leaf route-type {
type enumeration { type enumeration {
enum unspecified { enum unspecified {
value "0"; value "0";
skipping to change at page 126, line 28 skipping to change at page 126, line 28
EMail: kk@employees.org EMail: kk@employees.org
Authors' Addresses Authors' Addresses
Derek Yeung Derek Yeung
Arrcus Arrcus
EMail: derek@arrcus.com EMail: derek@arrcus.com
Yingzhen Qu Yingzhen Qu
Huawei Futurewei
2330 Central Expressway 2330 Central Expressway
Santa Clara, CA 95050 Santa Clara, CA 95050
USA USA
EMail: yingzhen.qu@huawei.com EMail: yingzhen.qu@futurewei.com
Jeffrey Zhang Jeffrey Zhang
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
 End of changes. 19 change blocks. 
73 lines changed or deleted 70 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/