--- 1/draft-ietf-ospf-yang-05.txt 2016-10-31 17:16:42.828322717 -0700 +++ 2/draft-ietf-ospf-yang-06.txt 2016-10-31 17:16:42.972326289 -0700 @@ -1,24 +1,25 @@ Internet D. Yeung -Internet-Draft Y. Qu -Intended status: Informational Cisco Systems -Expires: January 8, 2017 J. Zhang +Internet-Draft Arrcus +Intended status: Informational Y. Qu +Expires: May 4, 2017 Cisco Systems + J. Zhang Juniper Networks - D. Bogdanovic - - K. Sreenivasa + I. Chen + Kuatro Technologies + A. Lindem Cisco Systems - July 7, 2016 + October 31, 2016 Yang Data Model for OSPF Protocol - draft-ietf-ospf-yang-05 + draft-ietf-ospf-yang-06 Abstract This document defines a YANG data model that can be used to configure and manage OSPF. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. @@ -26,21 +27,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on January 8, 2017. + This Internet-Draft will expire on May 4, 2017. Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -56,32 +57,31 @@ 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 2. Design of Data Model . . . . . . . . . . . . . . . . . . . . 3 2.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 3 2.2. OSPFv2 and OSPFv3 . . . . . . . . . . . . . . . . . . . . 5 2.3. Optional Features . . . . . . . . . . . . . . . . . . . . 5 2.4. Inheritance . . . . . . . . . . . . . . . . . . . . . . . 5 2.5. OSPF Router Configuration . . . . . . . . . . . . . . . . 6 2.6. OSPF Instance Configuration . . . . . . . . . . . . . . . 6 2.7. OSPF Area Configuration . . . . . . . . . . . . . . . . . 7 2.8. OSPF Interface Configuration . . . . . . . . . . . . . . 10 - 2.9. OSPF notification . . . . . . . . . . . . . . . . . . . . 11 - 3. OSPF Segment Routing . . . . . . . . . . . . . . . . . . . . 14 - 4. OSPF BFD Yang Module . . . . . . . . . . . . . . . . . . . . 22 - 5. OSPF Yang Module . . . . . . . . . . . . . . . . . . . . . . 22 - 6. OSPF Segment Routing Yang Module . . . . . . . . . . . . . . 95 - 7. OSPF BFD Yang Module . . . . . . . . . . . . . . . . . . . . 110 - 8. Security Considerations . . . . . . . . . . . . . . . . . . . 113 - 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 113 - 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 113 - 10.1. Normative References . . . . . . . . . . . . . . . . . . 113 - 10.2. Informative References . . . . . . . . . . . . . . . . . 115 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 115 + 2.9. OSPF notification . . . . . . . . . . . . . . . . . . . . 12 + 3. OSPF BFD Yang Module . . . . . . . . . . . . . . . . . . . . 15 + 4. OSPF Yang Module . . . . . . . . . . . . . . . . . . . . . . 15 + 5. OSPF BFD Yang Module . . . . . . . . . . . . . . . . . . . . 91 + 6. Security Considerations . . . . . . . . . . . . . . . . . . . 94 + 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 94 + 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 94 + 8.1. Normative References . . . . . . . . . . . . . . . . . . 94 + 8.2. Informative References . . . . . . . . . . . . . . . . . 96 + Appendix A. Contributors' Addreses . . . . . . . . . . . . . . . 97 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 97 1. Overview YANG [RFC6020] is a data definition language used to define the contents of a conceptual data store that allows networked devices to be managed using NETCONF [RFC6241]. YANG is proving relevant beyond its initial confines, as bindings to other interfaces (e.g., ReST) and encodings other than XML (e.g., JSON) are being defined. Furthermore, YANG data models can be used as the basis for implementation of other interfaces, such as CLI and programmatic @@ -93,43 +93,43 @@ [I-D.ietf-netmod-routing-cfg], and it provides the basis for the development of data models for routing protocols. The interface data model is defined in [RFC7223] and is used for referencing interfaces from the routing protocol. The key-chain data model used for OSPF authentication is defined in [I-D.ietf-rtgwg-yang-key-chain] and provides both a reference to configured key-chains and an enumeration of cryptographic algorithms. Both OSPFv2 [RFC2328] and OSPFv3 [RFC5340] are supported. In addition to the core OSPF protocol, features described in other OSPF - RFCs are also supported. They includes demand circuit [RFC1793], + RFCs are also supported. These includes demand circuit [RFC1793], traffic engineering [RFC3630], multiple address family [RFC5838], - graceful restart [RFC3623] [RFC5187], NSSA [RFC3101], and sham link - [RFC4577]. These non-core features are made optional in the OSPF - data model. + graceful restart [RFC3623] [RFC5187], NSSA [RFC3101], and OSPF(v3) as + a PE-CE Protocol [RFC4577], [RFC6565]. These non-core features are + optional in the OSPF data model. 1.1. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 2. Design of Data Model Although the basis of OSPF configuration elements like routers, areas, and interfaces remains the same, the detailed configuration model varies among router vendors. Differences are observed in terms - of how the protocol engine is tied to routing domain, how multiple - protocol engines are be instantiated, and configuration inheritance, - among others. + of how the protocol engine is tied to the routing domain, how + multiple protocol engines are be instantiated, and configuration + inheritance, among others. The goal of this document is to define a data model that provides a - common user interface to the OSPFv2 and OSPFv3 protocol. There is + common user interface to the OSPFv2 and OSPFv3 protocols. There is very little information that is designated as "mandatory", providing freedom for vendors to adapt this data model to their respective product implementations. 2.1. Overview The OSPF YANG module defined in this document has all the common building blocks for the OSPF protocol. The OSPF YANG module augments the routing/routing-instance/routing- @@ -167,21 +167,21 @@ | +--rw interfaces | | +--rw interface* [interface] | | . | | . | . | . +--rw topologies +--rw topology* [name] The ospf module is intended to match to the vendor specific OSPF - configuration construct that is identified by a local identifier + configuration construct that is identified by the local identifier 'name'. The field 'version' allows support for OSPFv2 and OSPFv3. The ospf container includes one or more OSPF protocol engines, each enclosed in a separate instance entity. Each instance includes information for the routing domain based on the [routing-instance af] specification. There is no default routing domain assumed by the data model. For example, to enable OSPF on a vendor's default IPv4 routing domain, an explicit instance entity with a specification like ["default" "ipv4-unicast"] is required. The instance also contains @@ -215,21 +215,21 @@ This data model supports configuration inheritance at different levels including instance-level, area-level, and interface-level inheritance. The all-instances-inherit, all-areas-inherit, and all-interfaces- inherit containers are defined to provide a consistent way to configure inheritable configuration parameters. For example, parameters defined in the all-instances-inherit container apply to all OSPF instances. However, a particular instance configuration can - override this inheritance. + include leaves that override this inheritance. Inheritance is defined as an optional feature, and vendors are permitted to augment the inheritance containers with their own vendor specific parameters. 2.5. OSPF Router Configuration The ospf container is the top level container in this data model. It contains shared information among the OSPF instances configured within the container. @@ -245,21 +245,21 @@ . 2.6. OSPF Instance Configuration The instance container represents an OSPF protocol engine and contains the router level configuration. The routing domain for each instance is dictated through the specification of [routing-instance af]. The all-areas-inherit container contains area configuration that may - be inherited by configured OSPF areas. + be inherited by configured OSPF areas in the OSPF instance. module: ospf +--rw ospf . . +--rw instance* [af] +--rw af identityref +--rw all-areas-inherit {area-inheritance}? | +--rw area | +--rw interface @@ -336,21 +336,21 @@ | +--rw ranges | | +--rw range* [prefix] | | +--rw prefix inet:ip-prefix | | +--rw advertise? boolean | | +--rw cost? uint24 | +--rw virtual-links | | +--rw virtual-link* [router-id] | | +--rw transit-area-id -> ../../../area-id | | +--rw router-id yang:dotted-quad | | +--rw hello-interval? uint16 - | | +--rw dead-interval? uint16 + | | +--rw dead-interval? uint32 | | +--rw retransmit-interval? uint16 | | +--rw transmit-delay? uint16 | | +--rw mtu-ignore? boolean {mtu-ignore}? | | +--rw lls? boolean {lls}? | | +--rw prefix-suppression? boolean {prefix-suppression}? | | +--rw ttl-security {ttl-security}? | | | +--rw enable? boolean | | | +--rw hops? uint8 | | +--rw enable? boolean {admin-control}? | | +--rw authentication @@ -372,21 +372,22 @@ | | +--:(hmac-sha-1) | | | +--rw hmac-sha-1? empty | | +--:(hmac-sha-256) | | | +--rw hmac-sha-256? empty | | +--:(hmac-sha-384) | | | +--rw hmac-sha-384? empty | | +--:(hmac-sha-512) | | | +--rw hmac-sha-512? empty | | +--:(clear-text) {clear-text}? | | +--rw clear-text? empty - | | +--:(replay-protection-only) {replay-protection-only}? + | | +--:(replay-protection-only) + | | {replay-protection-only}? | | +--rw replay-protection-only? empty | +--rw sham-link | | +--rw sham-link* [local-id remote-id] | | +--rw local-id inet:ip-address | | +--rw remote-id inet:ip-address | | +--rw cost? uint16 | | +--rw hello-interval? uint16 | | +--rw dead-interval? uint16 | | +--rw retransmit-interval? uint16 | | +--rw transmit-delay? uint16 @@ -417,21 +418,22 @@ | | +--:(hmac-sha-1) | | | +--rw hmac-sha-1? empty | | +--:(hmac-sha-256) | | | +--rw hmac-sha-256? empty | | +--:(hmac-sha-384) | | | +--rw hmac-sha-384? empty | | +--:(hmac-sha-512) | | | +--rw hmac-sha-512? empty | | +--:(clear-text) {clear-text}? | | +--rw clear-text? empty - | | +--:(replay-protection-only) {replay-protection-only}? + | | +--:(replay-protection-only) + | | {replay-protection-only}? | | +--rw replay-protection-only? empty 2.8. OSPF Interface Configuration The interface container contains OSPF interface configuration. module: ospf +--rw ospf . . @@ -454,24 +456,24 @@ | | +--rw cost? uint16 | +--rw static-neighbors | | +--rw neighbor* [address] | | +--rw address inet:ip-address | | +--rw cost? uint16 | | +--rw poll-interval? uint16 | | +--rw priority? uint8 | +--rw node-flag? boolean {node-flag}? | +--rw fast-reroute {fast-reroute}? | | +--rw lfa {lfa}? - | | +--rw candidate-disabled? boolean - | | +--rw enabled? boolean + | | +--rw candidate-disable? boolean + | | +--rw enable? boolean | | +--rw remote-lfa {remote-lfa}? - | | +--rw enabled? boolean + | | +--rw enable? boolean | +--rw hello-interval? uint16 | +--rw dead-interval? uint16 | +--rw retransmit-interval? uint16 | +--rw transmit-delay? uint16 | +--rw mtu-ignore? boolean {mtu-ignore}? | +--rw lls? boolean {lls}? | +--rw prefix-suppression? boolean {prefix-suppression}? | +--rw ttl-security {ttl-security}? | | +--rw enable? boolean | | +--rw hops? uint8 @@ -495,21 +497,22 @@ | | +--:(hmac-sha-1) | | | +--rw hmac-sha-1? empty | | +--:(hmac-sha-256) | | | +--rw hmac-sha-256? empty | | +--:(hmac-sha-384) | | | +--rw hmac-sha-384? empty | | +--:(hmac-sha-512) | | | +--rw hmac-sha-512? empty | | +--:(clear-text) {clear-text}? | | +--rw clear-text? empty - | | +--:(replay-protection-only) {replay-protection-only}? + | | +--:(replay-protection-only) + | | {replay-protection-only}? | | +--rw replay-protection-only? empty | +--rw cost? uint16 | +--rw topologies | | +--rw topology* [name] | | +--rw name leafref | | +--rw cost? uint32 | +--rw instance-id? uint8 2.9. OSPF notification @@ -646,392 +649,51 @@ | +--ro status? nssa-translator-state-type +---n restart-status-change +--ro routing-instance? string +--ro routing-protocol-type? -> ... +--ro routing-protocol-name? -> ... +--ro af? -> ... +--ro status? restart-status-type +--ro restart-interval? uint16 +--ro exit-reason? restart-exit-reason-type -3. OSPF Segment Routing - - In addition to the OSPF base YANG model, this document also defines a - model for the OSPF segment routing feature. - - The OSPF SR YANG module requires support for the base segment routing - module [I-D.ietf-spring-sr-yang], which defines the global segment - routing configuration independent of any specific routing protocol - configuration. - - module: ietf-ospf-sr - augment /rt:routing/rt:control-plane-protocols - /rt:control-plane-protocol/ospf:ospf/ospf:instance: - +--rw segment-routing - | +--rw enabled? boolean - | +--rw bindings - | +--rw advertise - | | +--rw policies* string - | +--rw receive? boolean - +--rw protocol-srgb {sr:protocol-srgb}? - +--rw srgb* [lower-bound upper-bound] - +--rw lower-bound uint32 - +--rw upper-bound uint32 - augment /rt:routing/rt:control-plane-protocols - /rt:control-plane-protocol/ospf:ospf/ospf:instance - /ospf:areas/ospf:area/ospf:interfaces/ospf:interface: - +--rw segment-routing - +--rw adjacency-sid - +--rw advertise-adj-group-sid* [group-id] - | +--rw group-id uint32 - +--rw advertise-protection? enumeration - augment /rt:routing/rt:control-plane-protocols - /rt:control-plane-protocol/ospf:ospf/ospf:instance - /ospf:areas/ospf:area/ospf:interfaces/ospf:interface - /ospf:fast-reroute: - +--rw ti-lfa {ti-lfa}? - +--rw enable? boolean - augment /rt:routing-state/rt:control-plane-protocols - /rt:control-plane-protocol/ospf:ospf/ospf:instance: - +--ro segment-routing - | +--ro enabled? boolean - | +--ro bindings - | +--ro advertise - | | +--ro policies* string - | +--ro receive? boolean - +--ro protocol-srgb {sr:protocol-srgb}? - +--ro srgb* [lower-bound upper-bound] - +--ro lower-bound uint32 - +--ro upper-bound uint32 - augment /rt:routing-state/rt:control-plane-protocols - /rt:control-plane-protocol/ospf:ospf/ospf:instance - /ospf:areas/ospf:area/ospf:interfaces/ospf:interface: - +--ro segment-routing - +--ro adjacency-sid - +--ro advertise-adj-group-sid* [group-id] - | +--ro group-id uint32 - +--ro advertise-protection? enumeration - augment /rt:routing-state/rt:control-plane-protocols - /rt:control-plane-protocol/ospf:ospf/ospf:instance - /ospf:areas/ospf:area/ospf:interfaces/ospf:interface - /ospf:database/ospf:link-scope-lsa-type - /ospf:link-scope-lsas/ospf:link-scope-lsa/ospf:version - /ospf:ospfv2/ospf:ospfv2/ospf:body/ospf:opaque - /ospf:extended-prefix-tlvs/ospf:extended-prefix-tlv: - +--ro perfix-sid-sub-tlvs - | +--ro prefix-sid-sub-tlv* - | +--ro flags? bits - | +--ro mt-id? uint8 - | +--ro algorithm? uint8 - | +--ro sid? uint32 - +--ro sid-binding-sub-tlvs - +--ro sid-binding-sub-tlv* - +--ro flags? bits - +--ro mt-id? uint8 - +--ro weight? uint8 - +--ro sid-sub-tlv - | +--ro sid? uint32 - +--ro ero-metric-sub-tlv - | +--ro metric? uint32 - +--ro ipv4-ero-sub-tlv - | +--ro flags? bits - | +--ro ipv4-address? inet:ipv4-address - +--ro unnumbered-ero-sub-tlv - | +--ro flags? bits - | +--ro router-id? yang:dotted-quad - | +--ro interface-id? uint32 - +--ro ipv4-backup-ero-sub-tlv - | +--ro flags? bits - | +--ro ipv4-address? inet:ipv4-address - +--ro unnumbered-backup-ero-sub-tlv - +--ro flags? bits - +--ro router-id? yang:dotted-quad - +--ro interface-id? uint32 - augment /rt:routing-state/rt:control-plane-protocols - /rt:control-plane-protocol/ospf:ospf/ospf:instance - /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-prefix-tlvs/ospf:extended-prefix-tlv: - +--ro perfix-sid-sub-tlvs - | +--ro prefix-sid-sub-tlv* - | +--ro flags? bits - | +--ro mt-id? uint8 - | +--ro algorithm? uint8 - | +--ro sid? uint32 - +--ro sid-binding-sub-tlvs - +--ro sid-binding-sub-tlv* - +--ro flags? bits - +--ro mt-id? uint8 - +--ro weight? uint8 - +--ro sid-sub-tlv - | +--ro sid? uint32 - +--ro ero-metric-sub-tlv - | +--ro metric? uint32 - +--ro ipv4-ero-sub-tlv - | +--ro flags? bits - | +--ro ipv4-address? inet:ipv4-address - +--ro unnumbered-ero-sub-tlv - | +--ro flags? bits - | +--ro router-id? yang:dotted-quad - | +--ro interface-id? uint32 - +--ro ipv4-backup-ero-sub-tlv - | +--ro flags? bits - | +--ro ipv4-address? inet:ipv4-address - +--ro unnumbered-backup-ero-sub-tlv - +--ro flags? bits - +--ro router-id? yang:dotted-quad - +--ro interface-id? uint32 - augment /rt:routing-state/rt:control-plane-protocols - /rt:control-plane-protocol/ospf:ospf/ospf:instance - /ospf:database/ospf:as-scope-lsa-type/ospf:as-scope-lsas - /ospf:as-scope-lsa/ospf:version/ospf:ospfv2 - ospf:ospfv2/ospf:body/ospf:opaque - /ospf:extended-prefix-tlvs/ospf:extended-prefix-tlv: - +--ro perfix-sid-sub-tlvs - | +--ro prefix-sid-sub-tlv* - | +--ro flags? bits - | +--ro mt-id? uint8 - | +--ro algorithm? uint8 - | +--ro sid? uint32 - +--ro sid-binding-sub-tlvs - +--ro sid-binding-sub-tlv* - +--ro flags? bits - +--ro mt-id? uint8 - +--ro weight? uint8 - +--ro sid-sub-tlv - | +--ro sid? uint32 - +--ro ero-metric-sub-tlv - | +--ro metric? uint32 - +--ro ipv4-ero-sub-tlv - | +--ro flags? bits - | +--ro ipv4-address? inet:ipv4-address - +--ro unnumbered-ero-sub-tlv - | +--ro flags? bits - | +--ro router-id? yang:dotted-quad - | +--ro interface-id? uint32 - +--ro ipv4-backup-ero-sub-tlv - | +--ro flags? bits - | +--ro ipv4-address? inet:ipv4-address - +--ro unnumbered-backup-ero-sub-tlv - +--ro flags? bits - +--ro router-id? yang:dotted-quad - +--ro interface-id? uint32 - augment /rt:routing-state/rt:control-plane-protocols - /rt:control-plane-protocol/ospf:ospf/ospf:instance - /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-tlvs/ospf:extended-link-tlv: - +--ro adj-sid-sub-tlvs - | +--ro adj-sid-sub-tlv* - | +--ro flags? bits - | +--ro mt-id? uint8 - | +--ro weight? uint8 - | +--ro sid? uint32 - +--ro lan-adj-sid-sub-tlvs - +--ro lan-adj-sid-sub-tlv* - +--ro flags? bits - +--ro mt-id? uint8 - +--ro weight? uint8 - +--ro neighbor-router-id? yang:dotted-quad - +--ro sid? uint32 - augment /rt:routing-state/rt:control-plane-protocols - /rt:control-plane-protocol/ospf:ospf/ospf:instance - /ospf:areas/ospf:area/ospf:interfaces/ospf:interface - /ospf:database/ospf:link-scope-lsa-type - /ospf:link-scope-lsas/ospf:link-scope-lsa - /ospf:version/ospf:ospfv2/ospf:ospfv2 - /ospf:body/ospf:opaque: - +--ro extended-prefix-range-tlvs - | +--ro extended-prefix-range-tlv* - | +--ro range-size? uint16 - | +--ro flags? bits - | +--ro prefix? inet:ip-prefix - | +--ro perfix-sid-sub-tlvs - | | +--ro prefix-sid-sub-tlv* - | | +--ro flags? bits - | | +--ro mt-id? uint8 - | | +--ro algorithm? uint8 - | | +--ro sid? uint32 - | +--ro sid-binding-sub-tlvs - | | +--ro sid-binding-sub-tlv* - | | +--ro flags? bits - | | +--ro mt-id? uint8 - | | +--ro weight? uint8 - | | +--ro sid-sub-tlv - | | | +--ro sid? uint32 - | | +--ro ero-metric-sub-tlv - | | | +--ro metric? uint32 - | | +--ro ipv4-ero-sub-tlv - | | | +--ro flags? bits - | | | +--ro ipv4-address? inet:ipv4-address - | | +--ro unnumbered-ero-sub-tlv - | | | +--ro flags? bits - | | | +--ro router-id? yang:dotted-quad - | | | +--ro interface-id? uint32 - | | +--ro ipv4-backup-ero-sub-tlv - | | | +--ro flags? bits - | | | +--ro ipv4-address? inet:ipv4-address - | | +--ro unnumbered-backup-ero-sub-tlv - | | +--ro flags? bits - | | +--ro router-id? yang:dotted-quad - | | +--ro interface-id? uint32 - | +--ro unknown-tlvs - | +--ro unknown-tlv* - | +--ro type? uint16 - | +--ro length? uint16 - | +--ro value? yang:hex-string - +--ro sr-algorithm-tlv - | +--ro sr-algorithm* uint8 - +--ro sid-range-tlvs - +--ro sid-range-tlv* - +--ro range-size? ospf:uint24 - +--ro sid-sub-tlv - +--ro sid? uint32 - augment /rt:routing-state/rt:control-plane-protocols - /rt:control-plane-protocol/ospf:ospf/ospf:instance - /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: - +--ro extended-prefix-range-tlvs - | +--ro extended-prefix-range-tlv* - | +--ro range-size? uint16 - | +--ro flags? bits - | +--ro prefix? inet:ip-prefix - | +--ro perfix-sid-sub-tlvs - | | +--ro prefix-sid-sub-tlv* - | | +--ro flags? bits - | | +--ro mt-id? uint8 - | | +--ro algorithm? uint8 - | | +--ro sid? uint32 - | +--ro sid-binding-sub-tlvs - | | +--ro sid-binding-sub-tlv* - | | +--ro flags? bits - | | +--ro mt-id? uint8 - | | +--ro weight? uint8 - | | +--ro sid-sub-tlv - | | | +--ro sid? uint32 - | | +--ro ero-metric-sub-tlv - | | | +--ro metric? uint32 - | | +--ro ipv4-ero-sub-tlv - | | | +--ro flags? bits - | | | +--ro ipv4-address? inet:ipv4-address - | | +--ro unnumbered-ero-sub-tlv - | | | +--ro flags? bits - | | | +--ro router-id? yang:dotted-quad - | | | +--ro interface-id? uint32 - | | +--ro ipv4-backup-ero-sub-tlv - | | | +--ro flags? bits - | | | +--ro ipv4-address? inet:ipv4-address - | | +--ro unnumbered-backup-ero-sub-tlv - | | +--ro flags? bits - | | +--ro router-id? yang:dotted-quad - | | +--ro interface-id? uint32 - | +--ro unknown-tlvs - | +--ro unknown-tlv* - | +--ro type? uint16 - | +--ro length? uint16 - | +--ro value? yang:hex-string - +--ro sr-algorithm-tlv - | +--ro sr-algorithm* uint8 - +--ro sid-range-tlvs - +--ro sid-range-tlv* - +--ro range-size? ospf:uint24 - +--ro sid-sub-tlv - +--ro sid? uint32 - augment /rt:routing-state/rt:control-plane-protocols - /rt:control-plane-protocol/ospf:ospf/ospf:instance - /ospf:database/ospf:as-scope-lsa-type - /ospf:as-scope-lsas/ospf:as-scope-lsa/ospf:version - /ospf:ospfv2/ospf:ospfv2/ospf:body/ospf:opaque: - +--ro extended-prefix-range-tlvs - | +--ro extended-prefix-range-tlv* - | +--ro range-size? uint16 - | +--ro flags? bits - | +--ro prefix? inet:ip-prefix - | +--ro perfix-sid-sub-tlvs - | | +--ro prefix-sid-sub-tlv* - | | +--ro flags? bits - | | +--ro mt-id? uint8 - | | +--ro algorithm? uint8 - | | +--ro sid? uint32 - | +--ro sid-binding-sub-tlvs - | | +--ro sid-binding-sub-tlv* - | | +--ro flags? bits - | | +--ro mt-id? uint8 - | | +--ro weight? uint8 - | | +--ro sid-sub-tlv - | | | +--ro sid? uint32 - | | +--ro ero-metric-sub-tlv - | | | +--ro metric? uint32 - | | +--ro ipv4-ero-sub-tlv - | | | +--ro flags? bits - | | | +--ro ipv4-address? inet:ipv4-address - | | +--ro unnumbered-ero-sub-tlv - | | | +--ro flags? bits - | | | +--ro router-id? yang:dotted-quad - | | | +--ro interface-id? uint32 - | | +--ro ipv4-backup-ero-sub-tlv - | | | +--ro flags? bits - | | | +--ro ipv4-address? inet:ipv4-address - | | +--ro unnumbered-backup-ero-sub-tlv - | | +--ro flags? bits - | | +--ro router-id? yang:dotted-quad - | | +--ro interface-id? uint32 - | +--ro unknown-tlvs - | +--ro unknown-tlv* - | +--ro type? uint16 - | +--ro length? uint16 - | +--ro value? yang:hex-string - +--ro sr-algorithm-tlv - | +--ro sr-algorithm* uint8 - +--ro sid-range-tlvs - +--ro sid-range-tlv* - +--ro range-size? ospf:uint24 - +--ro sid-sub-tlv - +--ro sid? uint32 - -4. OSPF BFD Yang Module +3. OSPF BFD Yang Module - Additionally this document defines a module that can be used to + Additionally, this document defines a module that can be used to configure and monitor the OSPF BFD feature. Bidirectional Forwarding Detection (BFD) [RFC5880] is a network protocol that is used for liveness detection of arbitrary paths between systems. A YANG data model is defined in [I-D.ietf-bfd-yang] that supports BFD configuration and management. As a client of BFD, the OSPF protocol uses the services provided by BFD. The OSPF BFD YANG augments the base OSPF module and is defined - as a separate module. So any implementation that does not support + as a separate module. Hence, an implementation that does not support BFD can still use the OSPF base model without having to import the BFD module [I-D.ietf-bfd-yang]. module: ietf-ospf-bfd augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/ospf:ospf/ospf:instance /ospf:areas/ospf:area/ospf:interfaces/ospf:interface: +--rw bfd - +--rw enabled? boolean + +--rw enable? boolean augment /rt:routing-state/rt:control-plane-protocols /rt:control-plane-protocol/ospf:ospf/ospf:instance /ospf:areas/ospf:area/ospf:interfaces/ospf:interface: +--ro bfd - +--ro enabled? boolean + +--ro enable? boolean -5. OSPF Yang Module +4. OSPF Yang Module - file "ietf-ospf@2016-07-07.yang" + file "ietf-ospf@2016-10-31.yang" module ietf-ospf { namespace "urn:ietf:params:xml:ns:yang:ietf-ospf"; prefix ospf; import ietf-inet-types { prefix "inet"; } import ietf-yang-types { @@ -1059,29 +721,29 @@ "WG Web: WG List: WG Chair: Acee Lindem WG Chair: Abhay Roy Editor: Derek Yeung - + Author: Derek Yeung - + Author: Yingzhen Qu Author: Jeffrey Zhang Author: Ing-Wher Chen - + Author: Dean Bogdanovic Author: Kiran Agrahara Sreenivasa "; description "This YANG module defines the generic configuration and operational state for the OSPF protocol common to all vendor implementations. It is intended that the module will be extended by vendors to define vendor-specific @@ -1093,20 +755,60 @@ IP (ip): Internet Protocol IPv4 (ipv4):Internet Protocol Version 4 IPv6 (ipv6): Internet Protocol Version 6 MTU (mtu) Maximum Transmission Unit "; + revision 2016-10-31 { + description + "* Update authors information. + * Rename candidate-disabled to candidiate-enable + and set the default value to TRUE. + * Rename node identifiers that end with + 'enabled' to 'enable'. + * Set the default value of + ospf/instance/areas/area/interfaces/interface/ + fast-reroute/lfa/enable (previously named 'enabled') + to FALSE. + * Set the default value of + ospf/instance/areas/area/interfaces/interface/ + fast-reroute/remote-lfa/enable (previously named 'enabled') + to FALSE. + * Rename + ospf/instance/areas/area/interfaces/interface/ + static-neighbors/neighbor/address to 'identifier' + with type inet:ip-address + * Add 'dead-timer' to + ospf-state/instance/areas/area/interfaces/interface/ + neighbors/neighbor. + * Remove 'mtu-ignore' and 'prefix-suppression' from + virtual-link configuration. + * Adjust range specifications from 'transmit-delay', + 'dead-interval', and 'retransmit-interval' in + ospf/instance/areas/area/interfaces/interface. + * Change the type of + ospf/instance/areas/area/interface/interface/dead-interval + to uint32 to match RFC2328 Appendix A.3.2. + * Change hello-timer and wait-timer unit to seconds. + * Update hello-timer, dead-timer and wait-timer descriptions. + * Add IEEE bandwidth type and update all TE bandwidth fields to use it. + * Add Nt-bit to OSPFv2 router LSA. + * Remove L-bit from OSPFv2 router LSA. + "; + reference + "RFC XXXX: A YANG Data Model for OSPF."; + } + revision 2016-07-07 { description "* Add ospfv3 AF bit. * Add ospfv2 MT, L, O, DN bit. * Add interface priority config. * Change bdr-ip-address to type ip-address. * Rename leaf interface to name. * Rename rx-bad-packet to if-rx-bad-packet. * Move virtual link placement to backbone area. * Remove cost configuration from virtual link. @@ -1489,20 +1194,48 @@ } typedef checksum16-type { type string { pattern '(0x)?[0-9a-fA-F]{4}'; } description "16-bit checksum in hex-string format 0xXXXX."; } + typedef ieee-bandwidth { + type string { + pattern + '0[xX](0((\.0?)?[pP](\+)?0?|(\.0?))|' + + '1(\.([\da-fA-F]{0,5}[02468aAcCeE]?)?)?[pP](\+)?(12[0-7]|' + + '1[01]\d|0?\d?\d)?)|0[xX][\da-fA-F]{1,8}'; + } + description + "Bandwidth in IEEE 754 floating point 32-bit binary format: + (-1)**(S) * 2**(Exponent-127) * (1 + Fraction), + where Exponent uses 8 bits, and Fraction uses 23 bits. + The units are bytes per second. + The encoding format is the external hexadecimal-significand + character sequences specified in IEEE 754 and C99, + restricted to be normalized, non-negative, and non-fraction: + 0x1.hhhhhhp{+}d or 0X1.HHHHHHP{+}D + where 'h' and 'H' are hexadecimal digits, 'd' and 'D' are + integers in the range of [0..127]. + When six hexadecimal digits are used for 'hhhhhh' or 'HHHHHH', + the least significant digit must be an even number. + 'x' and 'X' indicate hexadecimal; 'p' and 'P' indicate power + of two. + Some examples are: 0x0p0, 0x1p10, and 0x1.abcde2p+20"; + reference + "IEEE Std 754-2008: IEEE Standard for Floating-Point + Arithmetic."; + } + feature multi-topology { description "Support Multiple-Topolgy Routing (MTR)."; } feature multi-area-adj { description "OSPF multi-area adjacency support as in RFC 5185."; } feature explicit-router-id { @@ -1620,20 +1355,25 @@ feature area-inheritance { description "Support area inheritance"; } feature interface-inheritance { description "Support interface inheritance"; } + feature pe-ce-protocol { + description + "Support PE-CE protocol"; + } + grouping tlv { description "TLV"; leaf type { type uint16; description "TLV type."; } leaf length { type uint16; description "TLV length."; @@ -1699,20 +1439,26 @@ bit E { description "When set, the router is an AS Boundary Router (ASBR)."; } bit B { description "When set, the router is an Area Border Router (ABR)."; } + bit Nt { + description + "When set, the router is an NSSA border router + that is unconditionally translating NSSA LSAs + into AS-external LSAs."; + } } description "Flags."; } leaf num-of-links { type uint16; description "Number of links."; } container links { description "All router Links."; list link { @@ -1895,44 +1641,38 @@ type inet:ipv4-address; description "List of remote interface IPv4 addresses."; } } leaf te-metric { type uint32; description "TE metric."; } leaf max-bandwidth { - type decimal64 { - fraction-digits 2; - } + type ieee-bandwidth; description "Maximum bandwidth."; } leaf max-reservable-bandwidth { - type decimal64 { - fraction-digits 2; - } + type ieee-bandwidth; description "Maximum reservable bandwidth."; } container unreserved-bandwidths { description "All unreserved bandwidths."; list unreserved-bandwidth { leaf priority { type uint8 { range "0 .. 7"; } description "Priority from 0 to 7."; } leaf unreserved-bandwidth { - type decimal64 { - fraction-digits 2; - } + type ieee-bandwidth; description "Unreserved bandwidth."; } description "List of unreserved bandwidths for different priorities."; } } leaf admin-group { type uint32; description @@ -2407,25 +2142,20 @@ } bit MC { description "When set, the router supports MOSPF."; } bit E { description "This bit describes the way AS-external LSAs are flooded."; } - bit L { - description - "L-bit is set in Hello and DD packets to indicate that - the packet contains an LLS data block as in RFC 5613."; - } bit O { description "When set, the router is opaque-capable as in RFC 5250."; } bit DN { description "When a type 3, 5 or 7 LSA is sent from a PE to a CE, the DN bit must be set. See RFC 4576."; } } @@ -2691,134 +2424,137 @@ } } grouping interface-fast-reroute-config { description "This group defines interface configuration of IP-FRR."; container fast-reroute { if-feature fast-reroute; container lfa { if-feature lfa; - leaf candidate-disabled { + leaf candidate-enable { type boolean; + default true; description - "Prevent the interface to be used as backup."; + "Enable the interface to be used as backup."; } - leaf enabled { + leaf enable { type boolean; + default false; description "Activates LFA - Per-prefix LFA computation is assumed."; } container remote-lfa { if-feature remote-lfa; - leaf enabled { + leaf enable { type boolean; + default false; description "Activates Remote LFA (R-LFA)."; } description "Remote LFA configuration."; } description "LFA configuration."; } description "IP Fast-reroute configuration."; } } - grouping interface-cost-config { + + grouping interface-physical-link-config { description "Interface cost configuration that only applies to physical interfaces and sham links."; leaf cost { type uint16 { range "1..65535"; } description "Interface cost."; } + leaf mtu-ignore { + if-feature mtu-ignore; + type boolean; + description + "Enable/Disable bypassing the MTU mismatch check in + Database Description packets."; + } + leaf prefix-suppression { + if-feature prefix-suppression; + type boolean; + description + "Suppress advertisement of the prefixes associated + with the interface."; + } + } grouping interface-common-config { description "Common configuration for all types of interfaces, including virtual links and sham links."; leaf hello-interval { type uint16 { range "1..65535"; } units seconds; description "Interval between hello packets in seconds."; } leaf dead-interval { - type uint16 { - range "1..65535"; + type uint32 { + range "1..2147483647"; } units seconds; must "../dead-interval > ../hello-interval" { error-message "The dead interval must be " + "larger than the hello interval"; description "The value MUST be greater than 'hello-internval'."; } description "Interval after which a neighbor is declared down in seconds."; } leaf retransmit-interval { type uint16 { - range "1..65535"; + range "1..3600"; } units seconds; description "Interval between retransmitting unacknowledged Link State Advertisements (LSAs) in seconds."; } leaf transmit-delay { type uint16 { - range "1..65535"; + range "1..3600"; } units seconds; description "Estimated time needed to transmit Link State Update packets on the interface in seconds."; } - leaf mtu-ignore { - if-feature mtu-ignore; - type boolean; - description - "Enable/Disable bypassing the MTU mismatch check in - Database Description packets."; - } - leaf lls { if-feature lls; type boolean; description "Enable/Disable link-local signaling (LLS) support."; } - leaf prefix-suppression { - if-feature prefix-suppression; - type boolean; - description - "Suppress advertisement of the prefixes associated - with the interface."; - } - container ttl-security { if-feature ttl-security; description "TTL security check."; leaf enable { type boolean; description "Enable/Disable TTL security check."; } leaf hops { type uint8 { @@ -2941,27 +2678,27 @@ description "Interface cost for multi-area adjacency."; } } } container static-neighbors { description "Statically configured neighbors."; list neighbor { - key "address"; + key "identifier"; description "Specify a static OSPF neighbor."; - leaf address { + leaf identifier { type inet:ip-address; - description "Neighbor IP address."; + description "Neighbor IPv4 address or router ID."; } leaf cost { type uint16 { range "1..65535"; } description "Neighbor cost."; } leaf poll-interval { type uint16 { @@ -2982,21 +2718,21 @@ leaf node-flag { if-feature node-flag; type boolean; default false; description "Set prefix as a node representative prefix."; } uses interface-fast-reroute-config; uses interface-common-config; - uses interface-cost-config; + uses interface-physical-link-config; } // grouping interface-config grouping neighbor-operation { description "OSPF neighbor operation data."; leaf address { type inet:ip-address; description "Neighbor address."; @@ -3021,46 +2756,55 @@ leaf bdr-ip-addr { type inet:ip-address; description "Neighbor's Backup Designated Router (BDR) IP Address."; } leaf state { type nbr-state-type; description "OSPF neighbor state."; } + leaf dead-timer { + type uint32; + units "seconds"; + description "This timer tracks the remaining time before + the neighbor is declared dead."; + } container statistics { description "Per neighbor statistics"; uses neighbor-stat; } } grouping interface-common-operation { description "OSPF interface common operation state."; + reference "RFC2328 Section 9"; leaf state { type if-state-type; description "Interface state."; } leaf hello-timer { type uint32; - units "milliseconds"; - description "Hello timer."; + units "seconds"; + description "This timer tracks the remaining time before + the next hello packet is sent."; } leaf wait-timer { type uint32; - units "milliseconds"; - description "Wait timer."; + units "seconds"; + description "This timer tracks the remaining time before + the interface exits the Waiting state."; } leaf dr-router-id { type yang:dotted-quad; description "Designated Router (DR) router ID."; } leaf dr-ip-addr { type inet:ip-address; description "Designated Router (DR) IP address."; @@ -3154,29 +2898,28 @@ "OSPF virtual link operation state."; leaf cost { type uint16 { range "1..65535"; } description "Virtual link interface cost."; } uses interface-common-operation; - } grouping sham-link-config { description "OSPF sham link configuration state."; uses interface-common-config; - uses interface-cost-config; + uses interface-physical-link-config; } grouping sham-link-operation { description "OSPF sham link operation state."; uses interface-common-operation; } grouping af-area-config { @@ -3263,28 +3006,27 @@ base area-type; } default normal; description "Area type."; } uses area-common-config; uses af-area-config { - when "../../operation-mode = " + when "../../../operation-mode = " + "'ospf:ships-in-the-night'" { description "Ships in the night configuration."; } } } - grouping area-operation { description "OSPF area operation state."; container statistics { description "Per area statistics"; uses area-stat; } container database { @@ -3694,28 +3435,62 @@ description "OSPF operation mode."; } } grouping ospf-operation { description "OSPF top operation state."; } + grouping multi-topology-area-common-config { + description + "OSPF multi-topology area common configuration state."; + leaf summary { + when "../../../../../areas/area[area-id=current()/../area-id]/" + + "area-type = 'ospf:stub' or " + + "../../../../../areas/area[area-id=current()/../area-id]/" + + "area-type = 'ospf:nssa'" { + description + "Summary advertisement into the stub/NSSA area."; + } + type boolean; + description + "Enable/Disable summary advertisement into the + topology in the stub or NSSA area."; + } + leaf default-cost { + when "../../../../../areas/area[area-id=current()/../area-id]/" + + "area-type = 'ospf:stub' or " + + "../../../../../areas/area[area-id=current()/../area-id]/" + + "area-type = 'ospf:nssa'" { + description + "Cost for LSA default route advertised into the + topology into the stub or NSSA area."; + } + type uint32 { + range "1..16777215"; + } + description + "Set the summary default route cost for a + stub or NSSA area."; + } + } + grouping multi-topology-area-config { description "OSPF multi-topology area configuration state."; - uses area-common-config; + uses multi-topology-area-common-config; uses af-area-config { - when "../../../../operation-mode = " + when "../../../../../operation-mode = " + "'ospf:ships-in-the-night'" { description "Ships in the night configuration."; } } } grouping multi-topology-area-operation { description "OSPF multi-topology area operation state."; @@ -3843,20 +3619,21 @@ leaf router-id { type yang:dotted-quad; description "Virtual Link remote endpoint router ID."; } uses virtual-link-config; } } container sham-links { + if-feature pe-ce-protocol; description "All sham links."; list sham-link { key "local-id remote-id"; description "OSPF sham link"; leaf local-id { type inet:ip-address; description "Address of the local Sham Link endpoint."; } @@ -4537,721 +4314,27 @@ leaf exit-reason { type restart-exit-reason-type; description "Restart exit reason."; } description "This notification is sent when the graceful restart state for the router has changed."; } -} - - -6. OSPF Segment Routing Yang Module - file "ietf-ospf-sr@2016-07-07.yang" - module ietf-ospf-sr { - namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-sr"; - - prefix ospf-sr; - - import ietf-inet-types { - prefix "inet"; - } - import ietf-yang-types { - prefix "yang"; - } - - import ietf-routing { - prefix "rt"; - } - import ietf-segment-routing { - prefix "sr"; - } - import ietf-ospf { - prefix "ospf"; - } - - organization - "Cisco Systems - 170 West Tasman Drive - San Jose, CA 95134-1706 - USA"; - - contact - "WG Web: - WG List: - - WG Chair: Acee Lindem - - - WG Chair: Abhay Roy - - - Editor: Derek Yeung - - Author: Derek Yeung - - Author: Yingzhen Qu - - Author: Acee Lindem - - Author: Jeffrey Zhang - - Author: Ing-Wher Chen - - Author: Greg Hankins - "; - - description - "This YANG module defines the generic configuration - and operational state for OSPF Segment Routing, which is - common across all of the vendor implementations. It is - intended that the module will be extended by vendors to - define vendor-specific OSPF Segment Routing configuration - and operational parameters and policies. - - Terms and Acronyms - - OSPF (ospf): Open Shortest Path First - - IP (ip): Internet Protocol - - IPv4 (ipv4):Internet Protocol Version 4 - - IPv6 (ipv6): Internet Protocol Version 6 - "; - - revision 2016-07-07 { - description - "* Change routing-protocol to control-plane-protocol."; - reference - "RFC XXXX: A YANG Data Model for OSPF Segment Routing."; - } - - revision 2016-03-20 { - description - "* Remove routing-instance."; - reference - "RFC XXXX: A YANG Data Model for OSPF Segment Routing."; - } - - revision 2015-10-19 { - description - "* Add per-protocol SRGB support. - * Editorial changes."; - reference - "RFC XXXX: A YANG Data Model for OSPF Segment Routing."; - } - - revision 2015-09-02 { - description - "* Author list update. - * Editorial changes."; - reference - "RFC XXXX: A YANG Data Model for OSPF Segment Routing."; - } - - revision 2015-07-06 { - description - "Initial revision."; - reference - "RFC XXXX: A YANG Data Model for OSPF Segment Routing."; - } - - feature ti-lfa { - description - "Topology-Independent Loop-Free Alternate (TI-LFA) - computation using segment routing."; - } - - /* Configuration */ - - augment "/rt:routing/rt:control-plane-protocols" - + "/rt:control-plane-protocol/ospf:ospf/ospf:instance" { - when "../../rt:type = 'ospf:ospfv2' or " - + "../../rt:type = 'ospf:ospfv3'" { - description - "This augments the OSPF routing protocol when used."; - } - description - "This augments the OSPF protocol configuration - with segment routing."; - uses sr:controlplane-cfg; - container protocol-srgb { - if-feature sr:protocol-srgb; - uses sr:srgb-cfg; - description - "Per-protocol SRGB."; - } - } - - augment "/rt:routing/rt:control-plane-protocols/" - + "rt:control-plane-protocol/ospf:ospf/ospf:instance/" - + "ospf:areas/ospf:area/ospf:interfaces/ospf:interface" { - when "../../../../../../rt:type = 'ospf:ospfv2' or " - + "../../../../../../rt:type = 'ospf:ospfv3'" { - description - "This augments the OSPF interface configuration - when used."; - } - description - "This augments the OSPF protocol interface - configuration with segment routing."; - - uses sr:igp-interface-cfg; - } - augment "/rt:routing/rt:control-plane-protocols/" - + "rt:control-plane-protocol/ospf:ospf/ospf:instance/" - + "ospf:areas/ospf:area/ospf:interfaces/ospf:interface/" - + "ospf:fast-reroute" { - when "../../../../../../../rt:type = 'ospf:ospfv2' or " - + "../../../../../../../rt:type = 'ospf:ospfv3'" { - description - "This augments the OSPF routing protocol when used."; - } - description - "This augments the OSPF protocol IP-FRR with TI-LFA."; - - container ti-lfa { - if-feature ti-lfa; - leaf enable { - type boolean; - description - "Enables TI-LFA computation."; - } - description - "Topology Independent Loop Free Alternate - (TI-LFA) support."; - } - } - - /* Operational states */ - - augment "/rt:routing-state/" - + "rt:control-plane-protocols/rt:control-plane-protocol/" - + "ospf:ospf/ospf:instance" { - when "../../rt:type = 'ospf:ospfv2' or " - + "../../rt:type = 'ospf:ospfv3'" { - description - "This augments the OSPF routing protocol when used."; - } - description - "This augments the OSPF protocol operational state - with segment routing."; - - uses sr:controlplane-cfg; - container protocol-srgb { - if-feature sr:protocol-srgb; - uses sr:srgb-cfg; - description - "Per-protocol SRGB."; - } - } - augment "/rt:routing-state/" - + "rt:control-plane-protocols/rt:control-plane-protocol/" - + "ospf:ospf/ospf:instance/ospf:areas/ospf:area/" - + "ospf:interfaces/ospf:interface" { - when "../../../../../../rt:type = 'ospf:ospfv2' or " - + "../../../../../../rt:type = 'ospf:ospfv3'" { - description - "This augments the OSPF routing protocol when used."; - } - description - "This augments the OSPF protocol interface - operational state with segment routing."; - - uses sr:igp-interface-cfg; - } - - /* Database */ - - grouping sid-sub-tlv { - description "SID/Label sub-TLV grouping."; - container sid-sub-tlv { - description - "Used to advertise the SID/Label associated with a - prefix or adjacency."; - leaf sid { - type uint32; - description - "Segment Identifier (SID) - A 20 bit label or - 32 bit SID."; - } - } - } - - grouping prefix-sid-sub-tlvs { - description "Prefix Segment ID (SID) sub-TLVs."; - container perfix-sid-sub-tlvs{ - description "Prefix SID sub-TLV."; - list prefix-sid-sub-tlv { - description "Prefix SID sub-TLV."; - leaf flags { - type bits { - bit NP { - description - "No-PHP flag."; - } - bit M { - description - "Mapping server flag."; - - } - bit E { - description - "Explicit-NULL flag."; - } - bit V { - description - "Value/Index flag."; - } - bit L { - description - "Local flag."; - } - } - description "Segment Identifier (SID) Flags."; - } - leaf mt-id { - type uint8; - description "Multi-topology ID."; - } - leaf algorithm { - type uint8; - description - "The algorithm associated with the prefix-SID."; - } - leaf sid { - type uint32; - description "An index or label."; - } - } - } - } - - grouping sid-binding-sub-tlvs { - description "SID/Label binding sub-TLV grouping."; - container sid-binding-sub-tlvs { - description "SID binding sub-TLVs."; - list sid-binding-sub-tlv { - description "SID binding sub-TLV."; - leaf flags { - type bits { - bit M { - description - "Mirroring context flag."; - } - } - description "Flags."; - } - leaf mt-id { - type uint8; - description "Multi-topology ID."; - } - leaf weight { - type uint8; - description "Weight for load-balancing purposes."; - } - - uses sid-sub-tlv; - - container ero-metric-sub-tlv { - description - "The cost of an Explicit Route Object (ERO) path."; - leaf metric { - type uint32; - description "The aggregate IGP or TE path cost."; - } - } - - container ipv4-ero-sub-tlv { - description - "The IPv4 ERO sub-TLV describes a path segment - using IPv4 address."; - leaf flags { - type bits { - bit L { - description - "If set, then the segment path is designated as - 'loose'. Otherwise, the path is 'strict'."; - } - } - description "ERO Flags."; - } - leaf ipv4-address { - type inet:ipv4-address; - description "The address of the explicit route hop."; - } - } - container unnumbered-ero-sub-tlv { - description "The unnumbered interface ID ERO sub-TLV - describes a path segment that includes an - unnumbered interface."; - leaf flags { - type bits { - bit L { - description - "If set, then the segment path is designated as - 'loose'. Otherwise as 'strict'."; - } - } - description "ERO Flags."; - } - leaf router-id { - type yang:dotted-quad; - description "Router-id of the next-hop."; - } - leaf interface-id { - type uint32; - description - "The identifier assigned to the link by the - router specified by the router-id."; - } - } - container ipv4-backup-ero-sub-tlv { - description - "The IPv4 backup ERO sub-TLV describes a path - segment using IPv4 address."; - leaf flags { - type bits { - bit L { - description - "If set, then the segment path is designated as - 'loose'. Otherwise as 'strict'."; - } - } - description "Flags."; - } - leaf ipv4-address { - type inet:ipv4-address; - description "The address of the explicit route hop."; - } - } - container unnumbered-backup-ero-sub-tlv { - description - "The unnumbered interface ID backup ERO sub-TLV - describes a path segment that includes an - unnumbered interface."; - leaf flags { - type bits { - bit L { - description - "If set, then the segment path is designated as - 'loose'. Otherwise, the path is 'strict'."; - } - } - description "Flags."; - } - leaf router-id { - type yang:dotted-quad; - description "Router-id of the next-hop."; - } - leaf interface-id { - type uint32; - description - "The identifier assigned to the link by the - router specified by the router-id."; - } - } - } - } - } - - grouping extended-prefix-range-tlvs { - description "Extended prefix range TLV grouping."; - - container extended-prefix-range-tlvs { - description "The list of range of prefixes."; - list extended-prefix-range-tlv { //type=2? - description "The range of prefixes."; - leaf range-size { - type uint16; - description "The number of prefixes covered by the - advertisement."; - } - leaf flags { - type bits { - bit IA { - description - "Inter-Area flag."; - } - } - description "Flags."; - } - leaf prefix { - type inet:ip-prefix; - description "Address prefix."; - } - uses prefix-sid-sub-tlvs; - uses sid-binding-sub-tlvs; - uses ospf:unknown-tlvs; - } - } - } - grouping sr-algorithm-tlv { - description "SR algorithm TLV grouping."; - container sr-algorithm-tlv { - description "All SR algorithm TLVs."; - leaf-list sr-algorithm { - type uint8; - description - "The Segment Routing (SR) algorithms that the router is - currently using."; - } - } - } - - grouping sid-range-tlvs { - description "SID Range TLV grouping."; - container sid-range-tlvs { - description "List of SID range TLVs."; - list sid-range-tlv { - description "SID range TLV."; - leaf range-size { - type ospf:uint24; - description "The SID range."; - } - uses sid-sub-tlv; - } - } - } - augment "/rt:routing-state/" - + "rt:control-plane-protocols/rt:control-plane-protocol/" - + "ospf:ospf/ospf:instance/ospf:areas/ospf:area/" - + "ospf:interfaces/ospf:interface/ospf:database/" - + "ospf:link-scope-lsa-type/ospf:link-scope-lsas/" - + "ospf:link-scope-lsa/ospf:version/ospf:ospfv2/" - + "ospf:ospfv2/ospf:body/ospf:opaque/" - + "ospf:extended-prefix-tlvs/ospf:extended-prefix-tlv" { - when "../../../../../../../../../../../../../../../../../" - + "rt:type = 'ospf:ospfv2'" { - description - "This augmentation is only valid for OSPFv2."; - } - description - "SR specific TLVs for OSPFv2 extended prefix TLV - in type 9 opaque LSA."; - uses prefix-sid-sub-tlvs; - uses sid-binding-sub-tlvs; - } - - augment "/rt:routing-state/" - + "rt:control-plane-protocols/rt:control-plane-protocol/" - + "ospf:ospf/ospf:instance/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-prefix-tlvs/ospf:extended-prefix-tlv" { - when "../../../../../../../../../../../../../../../" - + "rt:type = 'ospf:ospfv2'" { - description - "This augmentation is only valid for OSPFv2."; - } - description - "SR specific TLVs for OSPFv2 extended prefix TLV - in type 10 opaque LSA."; - uses prefix-sid-sub-tlvs; - uses sid-binding-sub-tlvs; - } - - augment "/rt:routing-state/" - + "rt:control-plane-protocols/rt:control-plane-protocol/" - + "ospf:ospf/ospf:instance/ospf:database/" - + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" - + "ospf:as-scope-lsa/ospf:version/ospf:ospfv2/" - + "ospf:ospfv2/ospf:body/ospf:opaque/" - + "ospf:extended-prefix-tlvs/ospf:extended-prefix-tlv" { - when "../../../../../../../../../../../../../" - + "rt:type = 'ospf:ospfv2'" { - description - "This augmentation is only valid for OSPFv2."; - } - description - "SR specific TLVs for OSPFv2 extended prefix TLV - in type 11 opaque LSA."; - uses prefix-sid-sub-tlvs; - uses sid-binding-sub-tlvs; - } - - augment "/rt:routing-state/" - + "rt:control-plane-protocols/rt:control-plane-protocol/" - + "ospf:ospf/ospf:instance/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-tlvs/ospf:extended-link-tlv" { - when "../../../../../../../../../../../../../../../" - + "rt:type = 'ospf:ospfv2'" { - - description - "This augmentation is only valid for OSPFv2."; - } - description - "SR specific TLVs for OSPFv2 extended link TLV - in type 10 opaque LSA."; - - container adj-sid-sub-tlvs { - description "Adjacency SID optional sub-TLVs."; - list adj-sid-sub-tlv { - description "List of Adjacency SID sub-TLVs."; - leaf flags { - type bits { - bit B { - description - "Backup flag."; - } - bit V { - description - "Value/Index flag."; - } - bit L { - description - "Local/Global flag."; - } - bit S { - description - "Set flag."; - } - } - description "Flags."; - } - leaf mt-id { - type uint8; - description "Multi-topology ID."; - } - leaf weight { - type uint8; - description "Weight used for load-balancing."; - } - leaf sid { - type uint32; - description "Segment Identifier (SID) index/label."; - } - } - } - - container lan-adj-sid-sub-tlvs { - description "LAN Adjacency SID optional sub-TLVs."; - list lan-adj-sid-sub-tlv { - description "List of LAN adjacency SID sub-TLVs."; - leaf flags { - type bits { - bit B { - description - "Backup flag."; - } - bit V { - description - "Value/Index flag."; - } - bit L { - description - "Local/Global flag."; - } - bit S { - description - "Set flag."; - } - } - description "Flags."; - } - leaf mt-id { - type uint8; - description "Multi-topology ID."; - } - leaf weight { - type uint8; - description "Weight used for load-balancing."; - } - leaf neighbor-router-id { - type yang:dotted-quad; - description "Neighbor router ID."; - } - leaf sid { - type uint32; - description "Segment Identifier (SID) index/label."; - } - } - } - } - - augment "/rt:routing-state/" - + "rt:control-plane-protocols/rt:control-plane-protocol/" - + "ospf:ospf/ospf:instance/ospf:areas/ospf:area/" - + "ospf:interfaces/ospf:interface/ospf:database/" - + "ospf:link-scope-lsa-type/ospf:link-scope-lsas/" - + "ospf:link-scope-lsa/ospf:version/ospf:ospfv2/" - + "ospf:ospfv2/ospf:body/ospf:opaque" { - when "../../../../../../../../../../../../../../../" - + "rt:type = 'ospf:ospfv2'" { - description - "This augmentation is only valid for OSPFv2."; - } - - description - "SR specific TLVs for OSPFv2 type 9 opaque LSA."; - - uses extended-prefix-range-tlvs; - uses sr-algorithm-tlv; - uses sid-range-tlvs; - } - - augment "/rt:routing-state/" - + "rt:control-plane-protocols/rt:control-plane-protocol/" - + "ospf:ospf/ospf:instance/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" { - when "../../../../../../../../../../../../../" - + "rt:type = 'ospf:ospfv2'" { - description - "This augmentation is only valid for OSPFv2."; - } - - description - "SR specific TLVs for OSPFv2 type 10 opaque LSA."; - - uses extended-prefix-range-tlvs; - uses sr-algorithm-tlv; - uses sid-range-tlvs; - } - - augment "/rt:routing-state/" - + "rt:control-plane-protocols/rt:control-plane-protocol/" - + "ospf:ospf/ospf:instance/ospf:database/" - + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" - + "ospf:as-scope-lsa/ospf:version/ospf:ospfv2/" - + "ospf:ospfv2/ospf:body/ospf:opaque" { - when "../../../../../../../../../../../" - + "rt:type = 'ospf:ospfv2'" { - description - "This augmentation is only valid for OSPFv2."; - - } - description - "SR specific TLVs for OSPFv2 type 11 opaque LSA."; - - uses extended-prefix-range-tlvs; - uses sr-algorithm-tlv; - uses sid-range-tlvs; - } } -7. OSPF BFD Yang Module +5. OSPF BFD Yang Module - file "ietf-ospf-bfd@2016-07-07.yang" + file "ietf-ospf-bfd@2016-10-31.yang" module ietf-ospf-bfd { namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-bfd"; prefix ospf-bfd; import ietf-routing { prefix "rt"; } import ietf-ospf { prefix "ospf"; @@ -5267,32 +4350,31 @@ "WG Web: WG List: WG Chair: Acee Lindem WG Chair: Abhay Roy Editor: Derek Yeung - + Author: Derek Yeung - + Author: Yingzhen Qu - Author: Acee Lindem Author: Jeffrey Zhang Author: Ing-Wher Chen - + Author: Greg Hankins "; description "This YANG module defines the generic configuration and operational state for OSPF BFD, which is common across all of the vendor implementations. It is intended that the module will be extended by vendors to define vendor-specific OSPF BFD configuration and operational parameters and policies. @@ -5301,20 +4383,28 @@ OSPF (ospf): Open Shortest Path First IP (ip): Internet Protocol IPv4 (ipv4):Internet Protocol Version 4 IPv6 (ipv6): Internet Protocol Version 6 "; + revision 2016-10-31 { + description + "* Update authors information. + * Rename bfd/enabled to bfd/enable"; + reference + "RFC XXXX: A YANG Data Model for OSPF BFD."; + } + revision 2016-07-07 { description "* Change routing-protocol to control-plane-protocol."; reference "RFC XXXX: A YANG Data Model for OSPF BFD."; } revision 2016-03-20 { description "* Remove routing-instance. @@ -5340,21 +4431,21 @@ + "../../../../../../rt:type = 'ospf:ospfv3'" { description "This augments the OSPF routing protocol when used"; } description "This augments OSPF protocol configuration with BFD."; container bfd { description "BFD configuration."; - leaf enabled { + leaf enable { type boolean; default false; description "True if BFD is enabled for the OSPF interface."; } } } /* Operational states */ @@ -5366,49 +4457,49 @@ + "../../../../../../rt:type = 'ospf:ospfv3'" { description "This augments the OSPF routing protocol when used"; } description "This augments OSPF protocol operation with BFD."; container bfd { description "BFD operation."; - leaf enabled { + leaf enable { type boolean; description "True if BFD is enabled for the OSPF interface."; + } } } } -8. Security Considerations +6. Security Considerations The data model defined does not create any security implications. This draft does not change any underlying security issues inherent in [I-D.ietf-netmod-routing-cfg]. -9. Acknowledgements +7. Acknowledgements - The authors wish to thank Acee Lindem, Yi Yang, Alexander Clemm, - Gaurav Gupta, Ing-Wher Chen, Ladislav Lhotka, Stephane Litkowski, - Greg Hankins, Manish Gupta and Alan Davey for their thorough reviews - and helpful comments. + The authors wish to thank Yi Yang, Alexander Clemm, Gaurav Gupta, + Ladislav Lhotka, Stephane Litkowski, Greg Hankins, Manish Gupta and + Alan Davey for their thorough reviews and helpful comments. This document was produced using Marshall Rose's xml2rfc tool. -10. References +8. References -10.1. Normative References +8.1. Normative References [RFC1793] Moy, J., "Extending OSPF to Support Demand Circuits", RFC 1793, DOI 10.17487/RFC1793, April 1995, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . @@ -5463,73 +4554,85 @@ [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, DOI 10.17487/RFC6020, October 2010, . [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, . + [RFC6565] Pillay-Esnault, P., Moyer, P., Doyle, J., Ertekin, E., and + M. Lundberg, "OSPFv3 as a Provider Edge to Customer Edge + (PE-CE) Routing Protocol", RFC 6565, DOI 10.17487/RFC6565, + June 2012, . + [RFC7223] Bjorklund, M., "A YANG Data Model for Interface Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, . -10.2. Informative References +8.2. Informative References [I-D.ietf-bfd-yang] Zheng, L., Rahman, R., Networks, J., Jethanandani, M., and G. Mirsky, "Yang Data Model for Bidirectional Forwarding - Detection (BFD)", draft-ietf-bfd-yang-01 (work in - progress), February 2016. + Detection (BFD)", draft-ietf-bfd-yang-03 (work in + progress), July 2016. [I-D.ietf-netmod-routing-cfg] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing - Management", draft-ietf-netmod-routing-cfg-22 (work in - progress), July 2016. + Management", draft-ietf-netmod-routing-cfg-24 (work in + progress), October 2016. [I-D.ietf-rtgwg-yang-key-chain] Lindem, A., Qu, Y., Yeung, D., Chen, I., Zhang, Z., and Y. Yang, "Routing Key Chain YANG Data Model", draft-ietf- - rtgwg-yang-key-chain-06 (work in progress), June 2016. + rtgwg-yang-key-chain-10 (work in progress), October 2016. - [I-D.ietf-spring-sr-yang] - Litkowski, S., Qu, Y., Sarkar, P., and J. Tantsura, "YANG - Data Model for Segment Routing", draft-ietf-spring-sr- - yang-03 (work in progress), July 2016. +Appendix A. Contributors' Addreses -Authors' Addresses + Dean Bogdanovic + Volta Networks, Inc. - Derek Yeung + EMail: dean@voltanet.io + + Kiran Koushik Agrahara Sreenivasa Cisco Systems - 170 West Tasman Drive - San Jose, CA 95134 + 12515 Research Blvd, Bldg 4 + Austin, TX 78681 USA - EMail: myeung@cisco.com + EMail: kkoushik@cisco.com + +Authors' Addresses + + Derek Yeung + Arrcus + + EMail: derek@arrcus.com Yingzhen Qu Cisco Systems 170 West Tasman Drive San Jose, CA 95134 USA EMail: yiqu@cisco.com + Jeffrey Zhang Juniper Networks 10 Technology Park Drive Westford, MA 01886 USA EMail: zzhang@juniper.net - Dean Bogdanovic - - EMail: ivandean@gmail.com + Ing-Wher Chen + Kuatro Technologies - Kiran Koushik Agrahara Sreenivasa + EMail: ichen@kuatrotech.com + Acee Lindem Cisco Systems - 12515 Research Blvd, Bldg 4 - Austin, TX 78681 - USA + 301 Midenhall Way + Cary, NC 27513 - EMail: kkoushik@cisco.com + EMail: acee@cisco.com