draft-ietf-babel-yang-model-03.txt   draft-ietf-babel-yang-model-04.txt 
Babel Working Group M. Jethanandani Babel Working Group M. Jethanandani
Internet-Draft VMware Internet-Draft VMware
Intended status: Standards Track B. Stark Intended status: Standards Track B. Stark
Expires: February 23, 2020 AT&T Expires: April 20, 2020 AT&T
August 22, 2019 October 18, 2019
YANG Data Model for Babel YANG Data Model for Babel
draft-ietf-babel-yang-model-03 draft-ietf-babel-yang-model-04
Abstract Abstract
This document defines a data model for the Babel routing protocol. This document defines a data model for the Babel routing protocol.
The data model is defined using the YANG data modeling language. The data model is defined using the YANG data modeling language.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in BCP 14 "OPTIONAL" in this document are to be interpreted as described in BCP
[RFC2119][RFC8174] when, and only when, they appear in all capitals, 14 [RFC2119][RFC8174] when, and only when, they appear in all
as shown here.. capitals, as shown here.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 23, 2020. This Internet-Draft will expire on April 20, 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 2, line 20 skipping to change at page 2, line 20
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Note to RFC Editor . . . . . . . . . . . . . . . . . . . 2 1.1. Note to RFC Editor . . . . . . . . . . . . . . . . . . . 2
1.2. Tree Diagram Annotations . . . . . . . . . . . . . . . . 3 1.2. Tree Diagram Annotations . . . . . . . . . . . . . . . . 3
2. Babel Module . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Babel Module . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Information Model . . . . . . . . . . . . . . . . . . . . 3 2.1. Information Model . . . . . . . . . . . . . . . . . . . . 3
2.2. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 3 2.2. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 3
2.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 5 2.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 5
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
3.1. URI Registrations . . . . . . . . . . . . . . . . . . . . 28 3.1. URI Registrations . . . . . . . . . . . . . . . . . . . . 30
3.2. YANG Module Name Registration . . . . . . . . . . . . . . 28 3.2. YANG Module Name Registration . . . . . . . . . . . . . . 30
4. Security Considerations . . . . . . . . . . . . . . . . . . . 28 4. Security Considerations . . . . . . . . . . . . . . . . . . . 30
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 31
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 30 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.1. Normative References . . . . . . . . . . . . . . . . . . 30 6.1. Normative References . . . . . . . . . . . . . . . . . . 31
6.2. Informative References . . . . . . . . . . . . . . . . . 31 6.2. Informative References . . . . . . . . . . . . . . . . . 32
Appendix A. An Appendix . . . . . . . . . . . . . . . . . . . . 32 Appendix A. An Appendix . . . . . . . . . . . . . . . . . . . . 33
A.1. Statistics Gathering Enabled . . . . . . . . . . . . . . 32 A.1. Statistics Gathering Enabled . . . . . . . . . . . . . . 33
A.2. Automatic Detection of Properties . . . . . . . . . . . . 33 A.2. Automatic Detection of Properties . . . . . . . . . . . . 34
A.3. Override Default Properties . . . . . . . . . . . . . . . 34 A.3. Override Default Properties . . . . . . . . . . . . . . . 35
A.4. Configuring other Properties . . . . . . . . . . . . . . 36 A.4. Configuring other Properties . . . . . . . . . . . . . . 37
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 38
1. Introduction 1. Introduction
This document defines a data model for the Babel routing protocol This document defines a data model for the Babel routing protocol
[I-D.ietf-babel-rfc6126bis]. The data model is defined using YANG [I-D.ietf-babel-rfc6126bis]. The data model is defined using YANG
1.1 [RFC7950] data modeling language and is Network Management 1.1 [RFC7950] data modeling language and is Network Management
Datastore Architecture (NDMA) [RFC8342] compatible. It is based on Datastore Architecture (NDMA) [RFC8342] compatible. It is based on
the Babel Information Model [I-D.ietf-babel-information-model]. the Babel Information Model [I-D.ietf-babel-information-model].
1.1. Note to RFC Editor 1.1. Note to RFC Editor
skipping to change at page 3, line 8 skipping to change at page 3, line 8
Artwork in this document contains shorthand references to drafts in Artwork in this document contains shorthand references to drafts in
progress. Please apply the following replacements and remove this progress. Please apply the following replacements and remove this
note before publication. note before publication.
o "XXXX" --> the assigned RFC value for this draft both in this o "XXXX" --> the assigned RFC value for this draft both in this
draft and in the YANG models under the revision statement. draft and in the YANG models under the revision statement.
o "ZZZZ" --> the assigned RFC value for Babel Information Model o "ZZZZ" --> the assigned RFC value for Babel Information Model
[I-D.ietf-babel-information-model] [I-D.ietf-babel-information-model]
o Revision date in model, in the format 2019-08-22 needs to get o Revision date in model, in the format 2019-10-18 needs to get
updated with the date the draft gets approved. The date also updated with the date the draft gets approved. The date also
needs to get reflected on the line with <CODE BEGINS>. needs to get reflected on the line with <CODE BEGINS>.
1.2. Tree Diagram Annotations 1.2. Tree Diagram Annotations
For a reference to the annotations used in tree diagrams included in For a reference to the annotations used in tree diagrams included in
this draft, please see YANG Tree Diagrams [RFC8340]. this draft, please see YANG Tree Diagrams [RFC8340].
2. Babel Module 2. Babel Module
skipping to change at page 4, line 43 skipping to change at page 4, line 43
The constants subtree describes the UDP port used for sending and The constants subtree describes the UDP port used for sending and
receiving Babel messages, and the multicast group used to send and receiving Babel messages, and the multicast group used to send and
receive announcements on IPv6. receive announcements on IPv6.
The routes subtree describes objects such as the prefix for which the The routes subtree describes objects such as the prefix for which the
route is advertised, a reference to the neighboring route, and next- route is advertised, a reference to the neighboring route, and next-
hop address. hop address.
Finally, for security two subtree are defined to contain MAC keys and Finally, for security two subtree are defined to contain MAC keys and
DTLS certificates. The mac-key-sets subtree contains keys used with DTLS certificates. The mac subtree contains keys used with the MAC
the MAC security mechanism. The boolean flag babel-mac-default-apply security mechanism. The boolean flag default-apply indicates whether
indicates whether the set of MAC keys is automatically applied to new the set of MAC keys is automatically applied to new interfaces. The
interfaces. The dtls subtree contains certificates used with DTLS dtls subtree contains certificates used with DTLS security mechanism.
security mechanism. Similar to the MAC mechanism, the boolean flag Similar to the MAC mechanism, the boolean flag default-apply
babel-dtls-default-apply indicates whether the set of DTLS indicates whether the set of DTLS certificates is automatically
certificates is automatically applied to new interfaces. applied to new interfaces.
2.3. YANG Module 2.3. YANG Module
This module augments A YANG Data Model for Interface Management This YANG module augments the YANG Routing Management [RFC8349]
[RFC8343], YANG Routing Management [RFC8349], imports definitions module to provide a common framework for all routing subsystems. By
from Common YANG Data Types [RFC6991], and references HMAC: Keyed- augmenting the module it provides a common building block for routes,
Hashing for Message Authentication [RFC2104], Using HMAC-SHA-256, and Routing Information Bases (RIBs). It also has a reference to an
HMAC-SHA-384, and HMAC-SHA-512 [RFC4868], Datagram Transport Layer interface defined by A YANG Data Model for Interface Management
Security Version 1.2 [RFC6347], The Blake2 Cryptographic Hash and [RFC8343].
Message Authentication Code (MAC) [RFC7693], Babel Information Model
[I-D.ietf-babel-information-model], and The Babel Routing Protocol
[I-D.ietf-babel-rfc6126bis].
<CODE BEGINS> file "ietf-babel@2019-08-22.yang" A router running Babel routing protocol can determine the parameters
it needs to use for an interface based on the interface name. For
example, it can detect that eth0 is a wired interface, and that wlan0
is a wireless interface. This is not true for a tunnel interface,
where the link parameters need to be configured explicitly.
For a wired interface, it will assume '2-out-of-3' 'metric-
algorithm', and 'split-horizon' set to true. On other hand, for a
wireless interface it will assume 'etx' 'metric-algorithm', and
'split-horizon' set to false. However, if the wired link is
connected to a wireless radio, the values can be overriden by setting
'metric-algorithm' to 'etx', and 'split-horizon' to false.
Similarly, an interface that is a metered 3G link, and used for
fallback connectivity needs much higher default time constants, e.g.
'mcast-hello-interval', and 'update-interval', in order to avoid
carrying control traffic as much as possible.
In addition to the modules used above, this module imports
definitions from Common YANG Data Types [RFC6991], and references
HMAC: Keyed-Hashing for Message Authentication [RFC2104], Using HMAC-
SHA-256, HMAC-SHA-384, and HMAC-SHA-512 [RFC4868], Datagram Transport
Layer Security Version 1.2 [RFC6347], The Blake2 Cryptographic Hash
and Message Authentication Code (MAC) [RFC7693], Babel Information
Model [I-D.ietf-babel-information-model], and The Babel Routing
Protocol [I-D.ietf-babel-rfc6126bis].
<CODE BEGINS> file "ietf-babel@2019-10-18.yang"
module ietf-babel { module ietf-babel {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-babel"; namespace "urn:ietf:params:xml:ns:yang:ietf-babel";
prefix babel; prefix babel;
import ietf-yang-types { import ietf-yang-types {
prefix yt; prefix yt;
reference reference
"RFC 6991: Common YANG Data Types."; "RFC 6991: Common YANG Data Types.";
skipping to change at page 6, line 12 skipping to change at page 6, line 35
Editor: Mahesh Jethanandani Editor: Mahesh Jethanandani
mjethanandani@gmail.com mjethanandani@gmail.com
Editor: Barbara Stark Editor: Barbara Stark
bs7652@att.com"; bs7652@att.com";
description description
"This YANG module defines a model for the Babel routing "This YANG module defines a model for the Babel routing
protocol. protocol.
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 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here.
Copyright (c) 2019 IETF Trust and the persons identified as Copyright (c) 2019 IETF Trust and the persons identified as
the document authors. All rights reserved. authors of the code. All rights reserved.
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
to the license terms contained in, the Simplified BSD the license terms contained in, the Simplified BSD License set
License set forth in Section 4.c of the IETF Trust's Legal forth in Section 4.c of the IETF Trust's Legal Provisions
Provisions Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX
the RFC itself for full legal notices."; (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself
for full legal notices.";
revision 2019-08-22 { revision 2019-10-18 {
description description
"Initial version."; "Initial version.";
reference reference
"RFC XXXX: Babel YANG Data Model."; "RFC XXXX: Babel YANG Data Model.";
} }
/* /*
* Features
*/
feature two-out-of-three-supported {
description
"This implementation can support two-out-of-three metric
comp algorithm.";
}
feature etx-supported {
description
"This implementation can support Expected Transmission Count
(ETX) metric comp algorithm.";
}
/*
* Identities * Identities
*/ */
identity metric-comp-algorithms { identity metric-comp-algorithms {
description description
"Base identity from which all Babel metric comp algorithms "Base identity from which all Babel metric comp algorithms
are derived."; are derived.";
} }
identity two-out-of-three { identity two-out-of-three {
base "metric-comp-algorithms"; base "metric-comp-algorithms";
if-feature two-out-of-three-supported;
description description
"2-out-of-3 algorithm."; "2-out-of-3 algorithm.";
} }
identity etx { identity etx {
base "metric-comp-algorithms"; base "metric-comp-algorithms";
if-feature etx-supported;
description description
"Expected Transmission Count."; "Expected Transmission Count.";
} }
/* /*
* Babel security type identities * Babel security type identities
*/ */
identity security-supported { identity security-supported {
description description
"Base identity from which all Babel security types are "Base identity from which all Babel security types are
derived."; derived.";
} }
identity mac { identity mac {
skipping to change at page 9, line 17 skipping to change at page 10, line 18
"RFC ZZZZ: Babel Information Model, Section 3.6."; "RFC ZZZZ: Babel Information Model, Section 3.6.";
} }
leaf neighbor { leaf neighbor {
type leafref { type leafref {
path "/rt:routing/rt:control-plane-protocols/" + path "/rt:routing/rt:control-plane-protocols/" +
"rt:control-plane-protocol/babel/interfaces/" + "rt:control-plane-protocol/babel/interfaces/" +
"neighbor-objects/neighbor-address"; "neighbor-objects/neighbor-address";
} }
description description
"Reference to the babel-neighbors entry for the neighbor "Reference to the neighbor-objects entry for the neighbor
that advertised this route."; that advertised this route.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.6."; "RFC ZZZZ: Babel Information Model, Section 3.6.";
} }
leaf received-metric { leaf received-metric {
type uint16; type uint16;
description description
"The metric with which this route was advertised by the "The metric with which this route was advertised by the
neighbor, or maximum value (infinity) to indicate a the neighbor, or maximum value (infinity) to indicate the
route was recently retracted and is temporarily route was recently retracted and is temporarily
unreachable. This metric will be 0 (zero) if the route unreachable. This metric will be 0 (zero) if the route
was not received from a neighbor but was generated was not received from a neighbor but was generated
through other means. At least one of through other means. At least one of
babel-route-calculated-metric or calculated-metric or received-metric MUST be non-NULL.";
babel-route-received-metric MUST be non-NULL.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.6, "RFC ZZZZ: Babel Information Model, Section 3.6,
draft-ietf-babel-rfc6126bis: The Babel Routing Protocol, draft-ietf-babel-rfc6126bis: The Babel Routing Protocol,
Section 3.5.5."; Section 3.5.5.";
} }
leaf calculated-metric { leaf calculated-metric {
type uint16; type uint16;
description description
"A calculated metric for this route. How the metric is "A calculated metric for this route. How the metric is
calculated is implementation-specific. Maximum value calculated is implementation-specific. Maximum value
(infinity) indicates the route was recently retracted (infinity) indicates the route was recently retracted
and is temporarily unreachable. At least one of and is temporarily unreachable. At least one of
babel-route-calculated-metric or calculated-metric or received-metric MUST be non-NULL.";
babel-route-received-metric MUST be non-NULL.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.6, "RFC ZZZZ: Babel Information Model, Section 3.6,
draft-ietf-babel-rfc6126bis: The Babel Routing Protocol, draft-ietf-babel-rfc6126bis: The Babel Routing Protocol,
Section 3.5.5."; Section 3.5.5.";
} }
leaf seqno { leaf seqno {
type uint16; type uint16;
description description
"The sequence number with which this route was advertised."; "The sequence number with which this route was advertised.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.6."; "RFC ZZZZ: Babel Information Model, Section 3.6.";
} }
skipping to change at page 11, line 9 skipping to change at page 12, line 9
"RFC ZZZZ: Babel Information Model, Section 3.1."; "RFC ZZZZ: Babel Information Model, Section 3.1.";
} }
description description
"Common grouping for routing used in RIB."; "Common grouping for routing used in RIB.";
} }
/* /*
* Data model * Data model
*/ */
augment "/rt:routing/rt:control-plane-protocols/" + augment "/rt:routing/rt:control-plane-protocols/" +
"rt:control-plane-protocol" { "rt:control-plane-protocol" {
when "derived-from-or-self(rt:type, 'babel')" { when "derived-from-or-self(rt:type, 'babel')" {
description description
"Augmentation is valid only when the instance of routing type "Augmentation is valid only when the instance of routing type
is of type 'babel'."; is of type 'babel'.";
} }
description description
"Augment the routing module to support a common structure "Augment the routing module to support a common structure
between routing protocols."; between routing protocols.";
reference reference
"YANG Routing Management, RFC 8349, Lhotka & Lindem, March "YANG Routing Management, RFC 8349, Lhotka & Lindem, March
2018."; 2018.";
container babel { container babel {
presence "A Babel container."; presence "A Babel container.";
description
"Babel Information Objects.";
reference
"RFC ZZZZ: Babel Information Model, Section 3.";
leaf version { leaf version {
type string; type string;
config false; config false;
description description
"The name and version of this implementation of the Babel "The name and version of this implementation of the Babel
protocol."; protocol.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.1."; "RFC ZZZZ: Babel Information Model, Section 3.1.";
} }
skipping to change at page 12, line 21 skipping to change at page 13, line 25
"RFC ZZZZ: Babel Information Model, Section 3.1, "RFC ZZZZ: Babel Information Model, Section 3.1,
draft-ietf-babel-rfc6126bis: The Babel Routing Protocol, draft-ietf-babel-rfc6126bis: The Babel Routing Protocol,
Section 3."; Section 3.";
} }
leaf seqno { leaf seqno {
type uint16; type uint16;
config false; config false;
description description
"Sequence number included in route updates for routes "Sequence number included in route updates for routes
originated by this node."; originated by this node.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.1."; "RFC ZZZZ: Babel Information Model, Section 3.1.";
} }
leaf-list metric-comp-algorithms { leaf-list metric-comp-algorithms {
type identityref { type identityref {
base "metric-comp-algorithms"; base "metric-comp-algorithms";
} }
config false; config false;
min-elements 1; min-elements 1;
skipping to change at page 13, line 35 skipping to change at page 14, line 39
} }
leaf stats-enable { leaf stats-enable {
type boolean; type boolean;
description description
"Indicates whether statistics collection is enabled (true) "Indicates whether statistics collection is enabled (true)
or disabled (false) on all interfaces."; or disabled (false) on all interfaces.";
} }
container constants { container constants {
description
"Babel Constants object.";
reference
"RFC ZZZZ: Babel Information Model, Section 3.1.";
leaf udp-port { leaf udp-port {
type inet:port-number; type inet:port-number;
default "6696"; default "6696";
description description
"UDP port for sending and receiving Babel messages. The "UDP port for sending and receiving Babel messages. The
default port is 6696."; default port is 6696.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.2."; "RFC ZZZZ: Babel Information Model, Section 3.2.";
} }
leaf mcast-group { leaf mcast-group {
type inet:ip-address; type inet:ip-address;
default "ff02::1:6"; default "ff02::1:6";
description description
"Multicast group for sending and receiving multicast "Multicast group for sending and receiving multicast
announcements on IPv6."; announcements on IPv6.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.2."; "RFC ZZZZ: Babel Information Model, Section 3.2.";
skipping to change at page 14, line 6 skipping to change at page 15, line 16
leaf mcast-group { leaf mcast-group {
type inet:ip-address; type inet:ip-address;
default "ff02::1:6"; default "ff02::1:6";
description description
"Multicast group for sending and receiving multicast "Multicast group for sending and receiving multicast
announcements on IPv6."; announcements on IPv6.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.2."; "RFC ZZZZ: Babel Information Model, Section 3.2.";
} }
description
"Babel Constants object.";
reference
"RFC ZZZZ: Babel Information Model, Section 3.1.";
} }
list interfaces { list interfaces {
key "reference"; key "reference";
description
"A set of Babel Interface objects.";
reference
"RFC ZZZZ: Babel Information Model, Section 3.3.";
leaf reference { leaf reference {
type if:interface-ref; type if:interface-ref;
description description
"References the name of the interface over which Babel "References the name of the interface over which Babel
packets are sent and received."; packets are sent and received.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.3."; "RFC ZZZZ: Babel Information Model, Section 3.3.";
} }
leaf enable { leaf enable {
skipping to change at page 14, line 42 skipping to change at page 16, line 4
"RFC ZZZZ: Babel Information Model, Section 3.3."; "RFC ZZZZ: Babel Information Model, Section 3.3.";
} }
leaf metric-algorithm { leaf metric-algorithm {
type identityref { type identityref {
base metric-comp-algorithms; base metric-comp-algorithms;
} }
mandatory true; mandatory true;
description description
"Indicates the metric computation algorithm used on this "Indicates the metric computation algorithm used on this
interface. The value MUST be one of those listed in interface. The value MUST be one of those identities
'metric-comp-algorithms'."; based on 'metric-comp-algorithms'.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.X."; "RFC ZZZZ: Babel Information Model, Section 3.X.";
} }
leaf split-horizon { leaf split-horizon {
type boolean; type boolean;
description description
"Indicates whether or not the split horizon optimization "Indicates whether or not the split horizon optimization
is used when calculating metrics on this interface. is used when calculating metrics on this interface.
A value of true indicates split horizon optimization A value of true indicates split horizon optimization
skipping to change at page 16, line 7 skipping to change at page 17, line 17
(true) or disabled (false)."; (true) or disabled (false).";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.3."; "RFC ZZZZ: Babel Information Model, Section 3.3.";
} }
leaf-list mac-key-sets { leaf-list mac-key-sets {
type leafref { type leafref {
path "../../mac/name"; path "../../mac/name";
} }
description description
"List of references to the babel-mac entries that apply "List of references to the mac entries that apply
to this interface. When an interface instance is created, to this interface. When an interface instance is
all babel-mac-key-sets instances with created, all mac instances with default-apply 'true'
babel-mac-default-apply 'true' will be included in this will be included in this list.";
list.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.3."; "RFC ZZZZ: Babel Information Model, Section 3.3.";
} }
leaf mac-verify { leaf mac-verify {
type boolean; type boolean;
description description
"A Boolean flag indicating whether MAC hashes in "A Boolean flag indicating whether MAC hashes in
incoming Babel packets are required to be present and incoming Babel packets are required to be present and
are verified. If this parameter is 'true', incoming are verified. If this parameter is 'true', incoming
skipping to change at page 16, line 41 skipping to change at page 17, line 50
(true) or disabled (false)."; (true) or disabled (false).";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.3."; "RFC ZZZZ: Babel Information Model, Section 3.3.";
} }
leaf-list dtls-certs { leaf-list dtls-certs {
type leafref { type leafref {
path "../../dtls/name"; path "../../dtls/name";
} }
description description
"List of references to the babel-dtls-cert-sets entries "List of references to the dtls entries that apply to
that apply to this interface. When an interface instance this interface. When an interface instance
is created, all babel-dtls instances with is created, all dtls instances with default-apply
babel-dtls-default-apply 'true' will be included in 'true' will be included in this list.";
this list.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.3."; "RFC ZZZZ: Babel Information Model, Section 3.3.";
} }
leaf dtls-cached-info { leaf dtls-cached-info {
type boolean; type boolean;
description description
"Indicates whether the cached_info extension is included "Indicates whether the cached_info extension is included
in ClientHello and ServerHello packets. The extension in ClientHello and ServerHello packets. The extension
is included if the value is 'true'."; is included if the value is 'true'.";
skipping to change at page 17, line 19 skipping to change at page 18, line 27
"RFC ZZZZ: Babel Information Model, Section 3.3."; "RFC ZZZZ: Babel Information Model, Section 3.3.";
} }
leaf-list dtls-cert-prefer { leaf-list dtls-cert-prefer {
type leafref { type leafref {
path "../../dtls/certs/type"; path "../../dtls/certs/type";
} }
ordered-by user; ordered-by user;
description description
"List of supported certificate types, in order of "List of supported certificate types, in order of
preference. The values MUST be among those listed in the preference. The values MUST be among those listed in
babel-dtls-cert-types parameter. This list is used to dtls-cert-types. This list is used to populate the
populate the server_certificate_type extension in a server_certificate_type extension in a Client Hello.
Client Hello. Values that are present in at least one Values that are present in at least one instance in the
instance in the babel-dtls-certs object of a referenced certs object under dtls of a referenced dtls instance
babel-dtls instance and that have a non-empty and that have a non-empty private-key will be used to
babel-cert-private-key will be used to populate the populate the client_certificate_type extension in a
client_certificate_type extension in a Client Hello."; Client Hello.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.3."; "RFC ZZZZ: Babel Information Model, Section 3.3.";
} }
leaf packet-log-enable { leaf packet-log-enable {
type boolean; type boolean;
description description
"If true, logging of babel packets received on this "If true, logging of babel packets received on this
interface is enabled; if false, babel packets are not interface is enabled; if false, babel packets are not
logged."; logged.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.3."; "RFC ZZZZ: Babel Information Model, Section 3.3.";
} }
leaf packet-log { leaf packet-log {
type inet:uri; type inet:uri;
config false; config false;
description description
"A reference or url link to a file that contains a "A reference or url link to a file that contains a
timestamped log of packets received and sent on timestamped log of packets received and sent on
babel-udp-port on this interface. The [libpcap] file udp-port on this interface. The [libpcap] file
format with .pcap file extension SHOULD be supported for format with .pcap file extension SHOULD be supported for
packet log files. Logging is enabled / disabled by packet log files. Logging is enabled / disabled by
packet-log-enable."; packet-log-enable.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.3."; "RFC ZZZZ: Babel Information Model, Section 3.3.";
} }
container stats { container stats {
config false; config false;
description
"Statistics collection object for this interface.";
reference
"RFC ZZZZ: Babel Information Model, Section 3.3.";
leaf sent-mcast-hello { leaf sent-mcast-hello {
type yt:counter32; type yt:counter32;
description description
"A count of the number of multicast Hello packets sent "A count of the number of multicast Hello packets sent
on this interface."; on this interface.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.4."; "RFC ZZZZ: Babel Information Model, Section 3.4.";
} }
leaf sent-mcast-update { leaf sent-mcast-update {
skipping to change at page 19, line 17 skipping to change at page 20, line 30
leaf received-packets { leaf received-packets {
type yt:counter32; type yt:counter32;
description description
"A count of the number of Babel packets received on "A count of the number of Babel packets received on
this interface."; this interface.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.4."; "RFC ZZZZ: Babel Information Model, Section 3.4.";
} }
action reset { action reset {
description description
"The information model [RFC ZZZZ] defines this reset "The information model [RFC ZZZZ] defines reset
action as a system-wide reset of Babel statistics action as a system-wide reset of Babel statistics.
parameters, but in YANG the reset action has to be In YANG the reset action is associated with the
contained in the container where the action needs to container where the action is defined. In this case
be performed."; the action is associated with the stats container
inside an interface. The action will therefore
reset statistics at an interface level.
Implementations that want to support a system-wide
reset of Babel statistics need to call this action
for every instance of the interface.";
input { input {
leaf reset-at { leaf reset-at {
type yt:date-and-time; type yt:date-and-time;
description description
"The time when the reset was issued."; "The time when the reset was issued.";
} }
} }
output { output {
leaf reset-finished-at { leaf reset-finished-at {
type yt:date-and-time; type yt:date-and-time;
description description
"The time when the reset finished."; "The time when the reset finished.";
} }
} }
} }
description
"Statistics collection object for this interface.";
reference
"RFC ZZZZ: Babel Information Model, Section 3.3.";
} }
list neighbor-objects { list neighbor-objects {
key "neighbor-address"; key "neighbor-address";
config false; config false;
description
"A set of Babel Neighbor Object.";
reference
"RFC ZZZZ: Babel Information Model, Section 3.5.";
leaf neighbor-address { leaf neighbor-address {
type inet:ip-address; type inet:ip-address;
description description
"IPv4 or v6 address the neighbor sends packets from."; "IPv4 or v6 address the neighbor sends packets from.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.5."; "RFC ZZZZ: Babel Information Model, Section 3.5.";
} }
leaf hello-mcast-history { leaf hello-mcast-history {
type string; type string;
description description
"The multicast Hello history of whether or not the "The multicast Hello history of whether or not the
multicast Hello packets prior to babel-exp-mcast- multicast Hello packets prior to exp-mcast-
hello-seqno were received, with a '1' for the most hello-seqno were received, with a '1' for the most
recent Hello placed in the most significant bit and recent Hello placed in the most significant bit and
prior Hellos shifted right (with '0' bits placed prior Hellos shifted right (with '0' bits placed
between prior Hellos and most recent Hello for any between prior Hellos and most recent Hello for any
not-received Hellos); represented as a string using not-received Hellos); represented as a string using
utf-8 encoded hex digits where a '1' bit = Hello utf-8 encoded hex digits where a '1' bit = Hello
received and a '0' bit = Hello not received."; received and a '0' bit = Hello not received.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.5."; "RFC ZZZZ: Babel Information Model, Section 3.5.";
} }
leaf hello-ucast-history { leaf hello-ucast-history {
type string; type string;
description description
"The unicast Hello history of whether or not the "The unicast Hello history of whether or not the
unicast Hello packets prior to babel-exp-ucast- unicast Hello packets prior to exp-ucast-hello-seqno
hello-seqno were received, with a '1' for the most were received, with a '1' for the most
recent Hello placed in the most significant bit and recent Hello placed in the most significant bit and
prior Hellos shifted right (with '0' bits placed prior Hellos shifted right (with '0' bits placed
between prior Hellos and most recent Hello for any between prior Hellos and most recent Hello for any
not-received Hellos); represented as a string using not-received Hellos); represented as a string using
utf-8 encoded hex digits where a '1' bit = Hello utf-8 encoded hex digits where a '1' bit = Hello
received and a '0' bit = Hello not received."; received and a '0' bit = Hello not received.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.5."; "RFC ZZZZ: Babel Information Model, Section 3.5.";
} }
skipping to change at page 22, line 22 skipping to change at page 23, line 43
leaf cost { leaf cost {
type int32; type int32;
description description
"Link cost is computed from the values maintained in "Link cost is computed from the values maintained in
the neighbor table. The statistics kept in the neighbor the neighbor table. The statistics kept in the neighbor
table about the reception of Hellos, and the txcost table about the reception of Hellos, and the txcost
computed from received IHU packets."; computed from received IHU packets.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.5."; "RFC ZZZZ: Babel Information Model, Section 3.5.";
} }
description
"A set of Babel Neighbor Object.";
reference
"RFC ZZZZ: Babel Information Model, Section 3.5.";
} }
description
"A set of Babel Interface objects.";
reference
"RFC ZZZZ: Babel Information Model, Section 3.3.";
} }
list mac { list mac {
key "name"; key "name";
description
"A mac object. If this object is implemented, it
provides access to parameters related to the MAC security
mechanism.";
reference
"RFC ZZZZ: Babel Information Model, Section 3.7.";
leaf name { leaf name {
type string; type string;
description description
"A string that uniquely identifies the mac object."; "A string that uniquely identifies the mac object.";
} }
leaf default-apply { leaf default-apply {
type boolean; type boolean;
description description
"A Boolean flag indicating whether this babel-mac "A Boolean flag indicating whether this mac
instance is applied to all new interfaces, by default. If instance is applied to all new interfaces, by default.
'true', this instance is applied to new If 'true', this instance is applied to new
babel-interfaces instances at the time they are created, interfaces instances at the time they are created,
by including it in the babel-interface-mac-keys list. by including it in the mac-key-sets list under
If 'false', this instance is not applied to new interfaces. If 'false', this instance is not applied
babel-interfaces instances when they are created."; to new interfaces instances when they are created.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.7."; "RFC ZZZZ: Babel Information Model, Section 3.7.";
} }
list keys { list keys {
key "name"; key "name";
min-elements "1"; min-elements "1";
description
"A set of keys objects.";
reference
"RFC ZZZZ: Babel Information Model, Section 3.8.";
leaf name { leaf name {
type string; type string;
mandatory true; mandatory true;
description description
"A unique name for this MAC key that can be used to "A unique name for this MAC key that can be used to
identify the key in this object instance, since the key identify the key in this object instance, since the key
value is not allowed to be read. This value can only be value is not allowed to be read. This value can only be
provided when this instance is created, and is not provided when this instance is created, and is not
subsequently writable."; subsequently writable.";
reference reference
skipping to change at page 24, line 14 skipping to change at page 25, line 39
mandatory true; mandatory true;
description description
"The value of the MAC key. An implementation MUST NOT "The value of the MAC key. An implementation MUST NOT
allow this parameter to be read. This can be done by allow this parameter to be read. This can be done by
always providing an empty string, or through always providing an empty string, or through
permissions, or other means. This value MUST be permissions, or other means. This value MUST be
provided when this instance is created, and is not provided when this instance is created, and is not
subsequently writable. subsequently writable.
This value is of a length suitable for the associated This value is of a length suitable for the associated
babel-mac-key-algorithm. If the algorithm is based on algorithm. If the algorithm is based on
the HMAC construction [RFC2104], the length MUST be the HMAC construction [RFC2104], the length MUST be
between 0 and the block size of the underlying hash between 0 and the block size of the underlying hash
inclusive (where 'HMAC-SHA256' block size is 64 inclusive (where 'HMAC-SHA256' block size is 64
bytes as described in [RFC4868]). If the algorithm bytes as described in [RFC4868]). If the algorithm
is 'BLAKE2s', the length MUST be between 0 and 32 is 'BLAKE2s', the length MUST be between 0 and 32
bytes inclusive, as described in [RFC7693]."; bytes inclusive, as described in [RFC7693].";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.8, "RFC ZZZZ: Babel Information Model, Section 3.8,
RFC 2104: HMAC: Keyed-Hashing for Message RFC 2104: HMAC: Keyed-Hashing for Message
Authentication Authentication
skipping to change at page 24, line 38 skipping to change at page 26, line 16
Authentication Code (MAC)."; Authentication Code (MAC).";
} }
leaf algorithm { leaf algorithm {
type identityref { type identityref {
base mac-algorithms; base mac-algorithms;
} }
description description
"The name of the MAC algorithm used with this key. The "The name of the MAC algorithm used with this key. The
value MUST be the same as one of the enumerations value MUST be the same as one of the enumerations
listed in the babel-mac-algorithms parameter."; listed in the mac-algorithms parameter.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.8."; "RFC ZZZZ: Babel Information Model, Section 3.8.";
} }
action test { action test {
description
"An operation that allows the MAC key and hash
algorithm to be tested to see if they produce an
expected outcome. Input to this operation is a
binary string. The implementation is expected to
create a hash of this string using the value and
the algorithm. The output of this operation is
the resulting hash, as a binary string.";
reference
"RFC ZZZZ: Babel Information Model, Section 3.8.";
input { input {
leaf test-string { leaf test-string {
type binary; type binary;
mandatory true; mandatory true;
description description
"The test string on which this test has to be "Input to this operation is a binary string.
performed."; The implementation is expected to create
a hash of this string using the value and
the algorithm.";
reference
"RFC ZZZZ: Babel Information Model, Section 3.8.";
} }
} }
output { output {
leaf resulting-hash { leaf resulting-hash {
type binary; type binary;
mandatory true; mandatory true;
description description
"An operation that allows the MAC key and hash "The output of this operation is
algorithm to be tested to see if they produce an the resulting hash, as a binary string.";
expected outcome. Input to this operation is a
binary string. The implementation is expected to
create a hash of this string using the
babel-mac-key-value and the babel-mac-algorithm.
The output of this operation is the resulting hash,
as a binary string.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.8."; "RFC ZZZZ: Babel Information Model, Section 3.8.";
} }
} }
} }
description
"A set of babel-mac-keys-obj objects.";
reference
"RFC ZZZZ: Babel Information Model, Section 3.8.";
} }
description
"A babel-mac-obj object. If this object is implemented, it
provides access to parameters related to the MAC security
mechanism.";
reference
"RFC ZZZZ: Babel Information Model, Section 3.7.";
} }
list dtls { list dtls {
key "name"; key "name";
description
"A dtls object. If this object is implemented,
it provides access to parameters related to the DTLS
security mechanism.";
reference
"RFC ZZZZ: Babel Information Model, Section 3.9";
leaf name { leaf name {
type string; type string;
description description
"A string that uniquely identifies a dtls object."; "A string that uniquely identifies a dtls object.";
} }
leaf default-apply { leaf default-apply {
type boolean; type boolean;
mandatory true; mandatory true;
description description
"A Boolean flag indicating whether this babel-dtls "A Boolean flag indicating whether this dtls
instance is applied to all new interfaces, by default. If instance is applied to all new interfaces, by default. If
'true', this instance is applied to new babel-interfaces 'true', this instance is applied to new interfaces
instances at the time they are created, by including it instances at the time they are created, by including it
in the babel-interface-dtls-certs list. If 'false', in the dtls-certs list under interfaces. If 'false',
this instance is not applied to new babel-interfaces this instance is not applied to new interfaces
instances when they are created."; instances when they are created.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.9."; "RFC ZZZZ: Babel Information Model, Section 3.9.";
} }
list certs { list certs {
key "name"; key "name";
min-elements "1"; min-elements "1";
description
"A set of cert objects. This contains
both certificates for this implementation to present
for authentication, and to accept from others.
Certificates with a non-empty private-key
can be presented by this implementation for
authentication.";
reference
"RFC ZZZZ: Babel Information Model, Section 3.10.";
leaf name { leaf name {
type string; type string;
description description
"A unique name for this DTLS certificate that can be "A unique name for this DTLS certificate that can be
used to identify the certificate in this object used to identify the certificate in this object
instance, since the value is too long to be useful instance, since the value is too long to be useful
for identification. This value MUST NOT be empty for identification. This value MUST NOT be empty
and can only be provided when this instance is created and can only be provided when this instance is created
(i.e., it is not subsequently writable)."; (i.e., it is not subsequently writable).";
reference reference
skipping to change at page 26, line 48 skipping to change at page 28, line 41
} }
leaf type { leaf type {
type identityref { type identityref {
base dtls-cert-types; base dtls-cert-types;
} }
mandatory true; mandatory true;
description description
"The name of the certificate type of this object "The name of the certificate type of this object
instance. The value MUST be the same as one of the instance. The value MUST be the same as one of the
enumerations listed in the babel-dtls-cert-types enumerations listed in the dtls-cert-types
parameter. This value can only be provided when this parameter. This value can only be provided when this
instance is created, and is not subsequently writable."; instance is created, and is not subsequently writable.";
reference reference
"RFC ZZZZ: Babel Information Model, Section 3.10."; "RFC ZZZZ: Babel Information Model, Section 3.10.";
} }
leaf private-key { leaf private-key {
type binary; type binary;
mandatory true; mandatory true;
description description
skipping to change at page 27, line 45 skipping to change at page 29, line 38
type binary; type binary;
mandatory true; mandatory true;
description description
"The output of this operation is a binary string, "The output of this operation is a binary string,
and is the resulting hash computed using the and is the resulting hash computed using the
certificate public key, and the SHA-256 certificate public key, and the SHA-256
hash algorithm."; hash algorithm.";
} }
} }
} }
description
"A set of babel-dtls-keys-obj objects. This contains
both certificates for this implementation to present
for authentication, and to accept from others.
Certificates with a non-empty babel-cert-private-key
can be presented by this implementation for
authentication.";
reference
"RFC ZZZZ: Babel Information Model, Section 3.10.";
} }
description
"A babel-dtls-obj object. If this object is implemented,
it provides access to parameters related to the DTLS
security mechanism.";
reference
"RFC ZZZZ: Babel Information Model, Section 3.9";
} }
description
"Babel Information Objects.";
reference
"RFC ZZZZ: Babel Information Model, Section 3.";
uses routes; uses routes;
} }
} }
} }
<CODE ENDS> <CODE ENDS>
3. IANA Considerations 3. IANA Considerations
skipping to change at page 31, line 14 skipping to change at page 32, line 39
[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
Routing Management (NMDA Version)", RFC 8349, Routing Management (NMDA Version)", RFC 8349,
DOI 10.17487/RFC8349, March 2018, DOI 10.17487/RFC8349, March 2018,
<https://www.rfc-editor.org/info/rfc8349>. <https://www.rfc-editor.org/info/rfc8349>.
6.2. Informative References 6.2. Informative References
[I-D.ietf-babel-information-model] [I-D.ietf-babel-information-model]
Stark, B. and M. Jethanandani, "Babel Information Model", Stark, B. and M. Jethanandani, "Babel Information Model",
draft-ietf-babel-information-model-08 (work in progress), draft-ietf-babel-information-model-10 (work in progress),
August 2019. October 2019.
[RFC2104] Krawczyk, H., Bellare, M., and R. Canetti, "HMAC: Keyed- [RFC2104] Krawczyk, H., Bellare, M., and R. Canetti, "HMAC: Keyed-
Hashing for Message Authentication", RFC 2104, Hashing for Message Authentication", RFC 2104,
DOI 10.17487/RFC2104, February 1997, DOI 10.17487/RFC2104, February 1997,
<https://www.rfc-editor.org/info/rfc2104>. <https://www.rfc-editor.org/info/rfc2104>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6020>. <https://www.rfc-editor.org/info/rfc6020>.
 End of changes. 66 change blocks. 
161 lines changed or deleted 230 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/