YANG Data Model for OSPF
SRv6Huawei TechnologiesHuawei Bld., No.156 Beiqing Rd.Beijing100095Chinahuzhibo@huawei.comHuawei TechnologiesHuawei Bld., No.156 Beiqing Rd.Beijing100095Chinagengxuesong@huawei.comCisco Systems, Inc.2000 Innovation Drive Kanata, ON K2K-3E8 CAskraza@cisco.comFuturewei Technologies2330 Central Express WaySanta Clara950950USAyingzhen.qu@futurewei.comCisco Systems301 Midenhall WayCary, NC27513USAacee@cisco.comThis document defines a YANG data model that can be used to configure
and manage OSPFv3 SRv6 as defined in
I-D.ietf-lsr-ospfv3-srv6-extensions.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 RFC 2119.YANG
is a data definition language used to define the contents of a
conceptual data store that allows networked devices to be managed using
NETCONF. 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 APIs.This document defines a YANG data model that can be used to configure
and manage OSPFv3 SRv6 and it is an augmentation to the OSPF YANG data
model.The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP 14
when, and only when,
they appear in all capitals, as shown here.The following terms are defined in :clientserverconfigurationsystem stateoperational stateintended configurationThe following terms are defined in :actionaugmentcontainercontainer with presencedata modeldata nodefeatureleaflistmandatory nodemoduleschema treeRPC (Remote Procedure Call) operationTree diagrams used in this document follow the notation defined in
.In this document, names of data nodes, actions, and other data
model objects are often used without a prefix, as long as it is clear
from the context in which YANG module each name is defined. Otherwise,
names are prefixed using the standard prefix associated with the
corresponding YANG module, as shown in Table 1.This document defines a model for OSPFv3 SRv6 feature. It is an
augmentation of the OSPF base model.The OSPFv3 SRv6 YANG module requires support of OSPF base model which defines basic OSPF configuration and
state and support of OSPFv3 Extended LSAs model .Activation of OSPFv3 SRv6 is done by setting the "enable" leaf to
true. This triggers advertisement of SRv6 extensions based on the
configuration parameters that have been setup using the base SRv6
module .The SRv6 base module [I-D.ietf-spring-srv6-yang] defines locators.
When OSPFv6 SRv6 is enabled, the specified locators are used unless it
is enabled to use the default locator. The default locator can be set
by using two leafs, i.e.,"default-locator" leaf, "locator-name"
leaf.Additional data object (in the OSPFv3 SRv6 model ) for fast reroute
[RFC5286] is introduced by augmenting the fast-reroute container of
the OSPF module. It brings the ability to activate ipv6 TI-LFA
(topology independent LFA)
[I-D.ietf-rtgwg-segment-routing-ti-lfa].OSPFv3 SRv6 model augments OSPF module with the
micro-loop-avoidance container, this container including the leaf
"srv6-enable" brings the ability to activate SRv6 avoid-microloop.The figure below describes the overall structure of the ospfv3-srv6
YANG module:The YANG modules specified in this document define a schema for data
that is designed to be accessed via network management protocols, such
as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer is
the secure transport layer, and the mandatory-to-implement secure
transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer is
HTTPS, and the mandatory-to-implement secure transport is TLS
[RFC8446].The Network Configuration Access Control Model (NACM) [RFC8341]
provides the means to restrict access for particular NETCONF or RESTCONF
users to a preconfigured subset of all available NETCONF or RESTCONF
protocol operations and content.There are a number of data nodes defined in the modules that are
writable/creatable/deletable (i.e., config true, which is the default).
These data nodes may be considered sensitive or vulnerable in some
network environments. Write operations (e.g., edit-config) to these data
nodes without proper protection can have a negative effect on network
operations. These are the subtrees and data nodes and their
sensitivity/vulnerability:srv6micro-loop-avoidancesrv6-ti-lfaThere are a number of data nodes defined in the modules that are
writable/creatable/deletable (i.e., config true, which is the default).
These data nodes may be considered sensitive or vulnerable in some
network environments. Write operations (e.g., edit-config) to these data
nodes without proper protection can have a negative effect on network
operations. These are the subtrees and data nodes and their
sensitivity/vulnerability:srv6-locatorsrv6-capabilitysrv6-msdsrv6-endx-sidTBD.The IANA is requested to assign two new URIs from the IETF XML
registry (). Authors are suggesting the
following URI: This document also requests one new YANG module name in the
YANG Module Names registry () with the following
suggestion :