draft-ietf-babel-yang-model-00.txt   draft-ietf-babel-yang-model-01.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: June 21, 2019 AT&T Expires: September 6, 2019 AT&T
December 18, 2018 March 5, 2019
YANG Data Model for Babel YANG Data Model for Babel
draft-ietf-babel-yang-model-00 draft-ietf-babel-yang-model-01
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", "MAY", and "OPTIONAL" in this
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 21, 2019. This Internet-Draft will expire on September 6, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Definitions and Acronyms . . . . . . . . . . . . . . . . 2 1.1. Note to RFC Editor . . . . . . . . . . . . . . . . . . . 2
1.2. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Definitions and Acronyms . . . . . . . . . . . . . . . . 3
1.3. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 3
2. Babel Module . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Babel Module . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Information Model . . . . . . . . . . . . . . . . . . . . 3 2.1. Information Model . . . . . . . . . . . . . . . . . . . . 3
2.2. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 3 2.2. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 5
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33
3.1. URI Registrations . . . . . . . . . . . . . . . . . . . . 21 3.1. URI Registrations . . . . . . . . . . . . . . . . . . . . 33
3.2. YANG Module Name Registration . . . . . . . . . . . . . . 21 3.2. YANG Module Name Registration . . . . . . . . . . . . . . 33
4. Security Considerations . . . . . . . . . . . . . . . . . . . 22 4. Security Considerations . . . . . . . . . . . . . . . . . . . 33
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 34
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.1. Normative References . . . . . . . . . . . . . . . . . . 22 6.1. Normative References . . . . . . . . . . . . . . . . . . 34
6.2. Informative References . . . . . . . . . . . . . . . . . 23 6.2. Informative References . . . . . . . . . . . . . . . . . 34
Appendix A. An Appendix . . . . . . . . . . . . . . . . . . . . 24 Appendix A. An Appendix . . . . . . . . . . . . . . . . . . . . 35
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35
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 the [I-D.ietf-babel-rfc6126bis]. The data model is defined using YANG
YANG [RFC7950] data modeling language. It is based on the Babel 1.1 [RFC7950] data modeling language and is Network Management
Information Model [I-D.ietf-babel-information-model]. Datastore Architecture (NDMA) [RFC8342] compatible. It is based on
the Babel Information Model [I-D.ietf-babel-information-model].
1.1. Note to RFC Editor
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 progress. Please apply the following replacements and remove this
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 Revision date in model, in the format 2018-04-27 needs to get o "ZZZZ" --> the assigned RFC value for Babel Information Model
[I-D.ietf-babel-information-model]
o Revision date in model, in the format 2019-03-07 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.1. Definitions and Acronyms 1.2. Definitions and Acronyms
o o
1.2. Tree Diagram 1.3. Tree Diagram
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
This document defines a YANG 1.1 [RFC7950] data model for the This document defines a YANG 1.1 [RFC7950] data model for the
configuration and management of Babel. The YANG module is based on configuration and management of Babel. The YANG module is based on
the Babel Information Model [I-D.ietf-babel-information-model]. the Babel Information Model [I-D.ietf-babel-information-model].
2.1. Information Model 2.1. Information Model
The following diagram illustrates a top level hierarchy of the model.
In addition to information like the version number implemented by
this device, the model contains subtrees on constants, interfaces,
routes and security.
module: ietf-babel
augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol:
+--rw babel!
+--ro version? string
+--rw enable? boolean
+--ro router-id binary
+--rw link-type* identityref
+--ro sequence-number? uint16
+--rw metric-comp-algorithms* identityref
+--rw security-supported* identityref
+--rw hmac-enable? boolean
+--rw hmac-algorithms* identityref
+--rw dtls-enable? boolean
+--rw dtls-cert-types* identityref
+--rw stats-enable? boolean
+--rw constants
| ...
+--rw interfaces* [reference]
| ...
+--rw hmac* [algorithm]
| ...
+--rw dtls* [name]
...
augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route:
+--ro routes* [prefix]
+--ro prefix inet:ip-prefix
+--ro router-id? binary
+--ro neighbor? leafref
+--ro (metric)
| ...
+--ro seqno? uint16
+--ro next-hop? inet:ip-address
+--ro feasible? boolean
+--ro selected? boolean
The interfaces subtree describes attributes such as interface object
that is being referenced, the type of link as enumerated by Babel
Link Types, and whether the interface is enabled or not.
The constants subtree describes the UDP port used for sending and
receiving Babel messages, and the multicast group used to send and
receive announcements on IPv6.
The routes subtree describes objects such as the prefix for which the
route is advertised, a reference to the neighboring route, and next-
hop address.
Finally, for security two subtree are defined. The hmac subtree
which refers to parameters related to HMAC security mechanism. The
boolean flag apply-all indicates whether HMAC mechanism is applicable
for all interfaces or just for interfaces listed in the leaf-list
'interfaces'. The dtls subtree refers to parameters related to DTLS
security mechanism. Similar to the HMAC mechanism, the boolean flag
apply-all indicates whether DTLS mechanism is applicable for all
interfaces or just for interfaces listed in the leaf-list
'interfaces'.
2.2. YANG Module 2.2. YANG Module
This module imports definitions from Common YANG Data Types This module augments A YANG Data Model for Interface Management
[RFC6991]. [RFC8343], YANG Routing Management [RFC8349], and imports definitions
from Common YANG Data Types [RFC6991].
module: ietf-babel module: ietf-babel
+--rw babel! augment /rt:routing/rt:control-plane-protocols
+--rw version? string /rt:control-plane-protocol:
+--rw enable? boolean +--rw babel!
+--rw router-id binary +--ro version? string
+--rw link-type* identityref +--rw enable? boolean
+--ro sequence-number? yang:counter32 +--ro router-id binary
+--rw cost-compute-algorithm* identityref +--rw link-type* identityref
+--rw security-supported* identityref +--ro sequence-number? uint16
+--rw transport +--rw metric-comp-algorithms* identityref
| +--rw udp-port? inet:port-number +--rw security-supported* identityref
| +--rw mcast-group? inet:ip-address +--rw hmac-enable? boolean
+--rw interfaces* [reference] +--rw hmac-algorithms* identityref
| +--rw reference if:interface-ref +--rw dtls-enable? boolean
| +--rw enable? boolean +--rw dtls-cert-types* identityref
| +--rw link-type? identityref +--rw stats-enable? boolean
| +--ro mcast-hello-seqno? int16 +--rw constants
| +--ro ucast-hello-seqno? int16 | +--rw udp-port? inet:port-number
| +--ro mcast-hello-interval? int16 | +--rw mcast-group? inet:ip-address
| +--ro ucast-hello-interval? int16 +--rw interfaces* [reference]
| +--rw update-interval? uint32 | +--rw reference if:interface-ref
| +--rw external-cost? uint32 | +--rw enable? boolean
| +--rw message-log-enable? boolean | +--rw link-type? identityref
| +--rw message-log* [log-time] | +--rw metric-algorithm? identityref
| | +--rw log-time yang:timestamp | +--ro mcast-hello-seqno? uint16
| | +--rw log-entry? string | +--ro mcast-hello-interval? uint16
| +--rw neighbor-objects* [neighbor-address] | +--rw update-interval? uint16
| | +--rw neighbor-address inet:ip-address | +--rw packet-log-enable? boolean
| | +--rw hello-mcast-history? string | +--rw packet-log? inet:uri
| | +--rw hello-ucast-history? string | +--ro stats
| | +--rw txcost? int32 | | +--ro sent-mcast-hello? yt:counter32
| | +--rw exp-mcast-hello-seqno? int32 | | +--ro sent-mcast-update? yt:counter32
| | +--rw exp-ucast-hello-seqno? int32 | | +--ro received-packets? yt:counter32
| | +--rw neighbor-ihu-interval? int32 | | +---x reset
| | +--rw rxcost? int32 | | +---w input
| | +--rw cost? int32 | | | +---w reset-at? yt:date-and-time
| +--rw security* [mechanism] | | +--ro output
| +--rw mechanism string | | +--ro reset-finished-at? yt:date-and-time
| +--rw enable? boolean | +--rw neighbor-objects* [neighbor-address]
| +--rw self-cred* [id] | +--rw neighbor-address inet:ip-address
| | +--rw id string | +--rw hello-mcast-history? string
| | +--rw cred? binary | +--rw hello-ucast-history? string
| +--rw trust* [id] | +--rw txcost? int32
| | +--rw id string | +--rw exp-mcast-hello-seqno? uint16
| | +--rw cred? binary | +--rw exp-ucast-hello-seqno? uint16
| +--rw credvalid-log-enable? boolean | +--rw ucast-hello-seqno? uint16
| +--rw credvalid-log* [log-time] | +--rw ucast-hello-interval? uint16
| +--rw log-time yang:timestamp | +--rw rxcost? int32
| +--rw log-entry? string | +--rw cost? int32
+--rw routes* [prefix] | +--ro stats
| +--rw prefix inet:ip-address | +--ro sent-ucast-hello? yt:counter32
| +--rw prefix-length? inet:ip-prefix | +--ro sent-ucast-update? yt:counter32
| +--rw router-id? binary | +--ro sent-ihu? yt:counter32
| +--rw neighbor? | +--ro received-hello? yt:counter32
| | -> ../../interfaces/neighbor-objects/neighbor-address | +--ro received-update? yt:counter32
| +--rw (metric) | +--ro received-ihu? yt:counter32
| | +--:(received-metric) | +---x reset
| | | +--rw received-metric? int32 | +---w input
| | +--:(calcuated-metric) | | +---w reset-at? yt:date-and-time
| | +--rw calcuated-metric? int32 | +--ro output
| +--rw seqno? int32 | +--ro reset-finished-at? yt:date-and-time
| +--rw next-hop? inet:ip-address +--rw hmac* [algorithm]
| +--rw feasible? boolean | +--rw algorithm identityref
| +--rw selected? boolean | +--rw verify boolean
+--rw security* [mechanism] | +--rw apply-all boolean
+--rw mechanism string | +--rw interfaces* if:interface-ref
+--rw enable? boolean | +--rw hmac-keys* [name]
+--rw self-cred* [id] | +--rw name string
| +--rw id string | +--rw use-sign boolean
| +--rw cred? binary | +--rw use-verify boolean
+--rw trust* [id] | +--rw value binary
| +--rw id string | +---x test
| +--rw cred? binary | +---w input
+--rw credvalid-log-enable? boolean | | +---w test-string binary
+--rw credvalid-log* [log-time] | +--ro output
+--rw log-time yang:timestamp | +--ro resulting-hash binary
+--rw log-entry? string +--rw dtls* [name]
+--rw name string
+--rw apply-all boolean
+--rw interfaces* if:interface-ref
+--rw cached-info? boolean
+--rw cert-prefer* identityref
+--rw certs* [name]
+--rw name string
+--rw value string
+--rw type identityref
+--rw private-key binary
+---x test
+---w input
| +---w test-string binary
+--ro output
+--ro resulting-hash binary
augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route:
+--ro routes* [prefix]
+--ro prefix inet:ip-prefix
+--ro router-id? binary
+--ro neighbor? leafref
+--ro (metric)
| +--:(received-metric)
| | +--ro received-metric? uint16
| +--:(calculated-metric)
| +--ro calculated-metric? uint16
+--ro seqno? uint16
+--ro next-hop? inet:ip-address
+--ro feasible? boolean
+--ro selected? boolean
<CODE BEGINS> file "ietf-babel@2018-12-18.yang" <CODE BEGINS> file "ietf-babel@2019-03-07.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 yang; prefix yt;
reference reference
"RFC 6991 - Common YANG Data Types."; "RFC 6991 - Common YANG Data Types.";
} }
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference reference
"RFC 6991 - Common YANG Data Types."; "RFC 6991 - Common YANG Data Types.";
} }
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
reference reference
"RFC 8343 - A YANG Data Model for Interface Management"; "RFC 8343 - A YANG Data Model for Interface Management";
} }
import ietf-routing {
prefix "rt";
reference
"RFC 8349 - YANG Routing Management";
}
organization organization
"IETF Babel routing protocl Working Group"; "IETF Babel routing protocol Working Group";
contact contact
"WG Web: http://tools.ietf.org/wg/babel/ "WG Web: http://tools.ietf.org/wg/babel/
WG List: babel@ietf.org WG List: babel@ietf.org
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
"This YANG module defines a model for the Babel routing
protocol.
Copyright (c) 2018 IETF Trust and the persons identified as
the document authors. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";
revision 2019-03-07 {
description description
"This YANG module defines a model for the Babel routing "Initial version.";
protocol. reference
"RFC XXX: Babel YANG Data Model.";
}
Copyright (c) 2018 IETF Trust and the persons identified as /*
the document authors. All rights reserved. * Identities
Redistribution and use in source and binary forms, with or */
without modification, is permitted pursuant to, and subject identity link-type {
to the license terms contained in, the Simplified BSD description
License set forth in Section 4.c of the IETF Trust's Legal "Base identity from which all Babel Link Types are derived.";
Provisions Relating to IETF Documents }
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";
revision 2018-12-18 { identity ethernet {
description base "link-type";
"Initial version."; description
reference "Ethernet link type for Babel Routing Protocol.";
"RFC XXX: Babel YANG Data Model."; }
} identity other {
base "link-type";
description
"Other link type for Babel Routing Protocol.";
}
identity tunnel {
base "link-type";
description
"Tunnel link type for Babel Routing Protocol.";
}
identity wireless {
base "link-type";
description
"Wireless link type for Babel Routing Protocol.";
}
identity moca {
base "link-type";
description
"Multimedia over Coax Alliance.";
}
identity g-hn-over-coax {
base "link-type";
description
"G.hn over coax.";
reference
"G.9960: Unified high-speed wireline-base home networking
transceivers.";
}
identity g-hn-over-powerline {
base "link-type";
description
"G.hn over powerline.";
reference
"G.9960: Unified high-speed wireline-base home networking
transceivers.";
}
identity home-plug {
base "link-type";
description
"HomePlug Power Alliance.";
/* reference
* Identities "IEEE 1901: HD-PC";
*/ }
identity babel-link-type { identity ieee-802-15 {
description base "link-type";
"Base identity from which all Babel Link Types are derived."; description
} "Wireless Personal Area Networks (WPAN).";
reference
"IEEE 802.15: Wireless Personal Area Networks (WPAN).";
}
identity ethernet { identity metric-comp-algorithms {
base "babel-link-type"; description
description "Base identity from which all Babel metric comp algorithms
"Ethernet link type for Babel Routing Protocol."; are derived.";
} }
identity other { identity k-out-of-j {
base "babel-link-type"; base "metric-comp-algorithms";
description description
"Other link type for Babel Routing Protocol."; "k-out-of-j algorithm.";
} }
identity tunnel { identity etx {
base "babel-link-type"; base "metric-comp-algorithms";
description description
"Tunnel link type for Babel Routing Protocol."; "Expected Transmission Count.";
} }
identity wireless {
base "babel-link-type";
description
"Wireless link type for Babel Routing Protocol.";
}
identity moca {
base "babel-link-type";
description
"Multimedia over Coax Alliance.";
}
identity g-hn-over-coax {
base "babel-link-type";
description
"G.hn over coax.";
reference
"G.9960: Unified high-speed wireline-base home networking
transceivers.";
}
identity g-hn-over-powerline {
base "babel-link-type";
description
"G.hn over powerline.";
reference
"G.9960: Unified high-speed wireline-base home networking
transceivers.";
}
identity home-plug {
base "babel-link-type";
description
"HomePlug Power Alliance.";
reference
"IEEE 1901: HD-PC";
}
identity ieee-802-15 {
base "babel-link-type";
description
"Wireless Personal Area Networks (WPAN).";
reference
"IEEE 802.15: Wireless Personal Area Networks (WPAN).";
}
identity babel-cost-compute-algorithm { /*
description * Babel security type identities
"Base identity from which all Babel cost compute algorithms */
are derived."; identity security-supported {
} description
identity k-out-of-j { "Base identity from which all Babel security types are
base "babel-cost-compute-algorithm"; derived.";
description }
"k-out-of-j algorithm.";
}
identity etx {
base "babel-cost-compute-algorithm";
description
"Expected Transmission Count.";
}
/* identity hmac {
* Babel type identities base security-supported;
*/ description
identity babel-security-supported { "HMAC supported.";
description }
"Base identity from which all Babel security types are
derived.";
}
/* identity dtls {
* Features base security-supported;
*/ description
"Datagram Transport Layer Security (DTLS) supported.";
reference
"RFC 6347, Datagram Transport Layer Security Version 1.2.";
/* }
* Features supported
*/
/* /*
* Typedefs * Babel HMAC algorithms identities.
*/ */
typedef base64 { identity hmac-algorithms {
type string { description
pattern '(([A-Za-z0-9+/]{4})*([A-Za-z0-9+/]{3}=|' "Base identity for all Babel HMAC algorithms.";
+ '[A-Za-z0-9+/]{2}==)?){1}'; }
}
description
"A binary-to-text encoding scheme to represent binary data in
an ASCII string format.";
reference
"RFC 4648, The Base16, Base32, and Base64 Data Encodings";
}
/* identity hmac-sha256 {
* Groupings base hmac-algorithms;
*/ description
grouping log { "HMAC-SHA256 algorithm supported.";
leaf log-time { }
type yang:timestamp;
description
"The date and time (according to the device internal
clock setting, which may be a time relative to boot
time, acquired from NTP, configured by the user, etc.)
when this log entry was created.";
reference
"RFC YYYY, Babel Information Model, Section 4.2.";
}
leaf log-entry { identity blake2s {
type string; base hmac-algorithms;
description description
"The logged message, as a string of utf-8 encoded hex "BLAKE2s algorithm supported.";
characters."; reference
reference "RFC 7693, The BLAKE2 Cryptographic Hash and Message
"RFC YYYY, Babel Information Model, Section 4.2."; Authentication Code (MAC).";
}
} /*
description * Babel Cert Types
"A babel-log-obj list."; */
reference identity dtls-cert-types {
"RFC YYYY, Babel Information Model, Section 4.2."; description
} "Base identity for Babel DTLS certificate types.";
}
grouping credential { identity x-509 {
leaf id { base dtls-cert-types;
type string; description
"X.509 certificate type.";
}
identity raw-public-key {
base dtls-cert-types;
description
"Raw Public Key type.";
}
/*
* Babel routing protocol identity.
*/
identity babel {
base "rt:control-plane-protocol";
description
"Babel routing protocol";
}
/*
* Features
*/
/*
* Features supported
*/
/*
* Typedefs
*/
/*
* Groupings
*/
grouping routes {
list routes {
key "prefix";
leaf prefix {
type inet:ip-prefix;
description description
"An identifier that identifies this credential uniquely."; "Prefix (expressed in ip-address/prefix-length format) for
which this route is advertised.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.6.";
} }
leaf cred { leaf router-id {
type binary; type binary;
description description
"A credential, such as an X.509 certificate, a public key, "router-id of the source router for which this route is
etc. used for signing and/or encrypting babel messages."; advertised.";
reference reference
"RFC YYYY, Babel Information Model, Section 4.1."; "RFC ZZZZ, Babel Information Model, Section 3.6.";
} }
description
"A babel-credential-obj list.";
reference
"RFC YYYY, Babel Information Model, Section 4.1.";
}
grouping security { leaf neighbor {
leaf mechanism { type leafref {
type string; path "/rt:routing/rt:control-plane-protocols/" +
"rt:control-plane-protocol/babel/interfaces/" +
"neighbor-objects/neighbor-address";
}
description description
"The name of the security mechanism this object instance "Reference to the babel-neighbors entry for the neighbor
is about. The value MUST be the same as one of the that advertised this route.";
identities listed as the babel-security-supported
parameter.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.5."; "RFC ZZZZ, Babel Information Model, Section 3.6.";
} }
leaf enable { choice metric {
type boolean; mandatory "true";
leaf received-metric {
type uint16;
description
"The metric with which this route was advertised by the
neighbor, or maximum value (infinity) to indicate a the
route was recently retracted and is temporarily
unreachable. this metric will be 0 (zero) if the route
was not received from a neighbor but was generated
through other means. Either babel-route-calculated-metric
or babel-route-received-metric MUST be provided.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.6,
draft-ietf-babel-rfc6126bis, The Babel Routing Protocol,
Section 3.5.5.";
}
leaf calculated-metric {
type uint16;
description
"A calculated metric for this route. How the metric is
calculated is implementation-specific. Maximum value
(infinity) indicates the route was recently retracted
and is temporarily unreachable. Either
babel-route-calculated-metric or
babel-route-received-metric MUST be provided.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.6,
draft-ietf-babel-rfc6126bis, The Babel Routing Protocol,
Section 3.5.5.";
}
description description
"If true, the security mechanism is running. If false, "Either babel-route-calculated-metric or
the security mechanism is not currently running."; babel-route-received-metric MUST be provided.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.5."; "RFC ZZZZ, Babel Information Model, Section 3.6,
draft-ietf-babel-rfc6126bis, The Babel Routing Protocol,
Section 3.5.5.";
} }
list self-cred { leaf seqno {
key "id"; type uint16;
uses credential;
description description
"Credentials this router presents to participate in the "The sequence number with which this route was advertised.";
enabled security mechanism. Any private key component of
a credential MUST NOT be readable. Adding and deleting
credentials MAY be allowed.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.5."; "RFC ZZZZ, Babel Information Model, Section 3.6.";
} }
list trust { leaf next-hop {
key "id"; type inet:ip-address;
uses credential;
description description
"A list of credential-obj objects that identify the "The next-hop address of this route. This will be empty if
credentials of routers whose babel messages may be this route has no next-hop address.";
trusted or of a certificate authority (CA) whose signing
of a router's credentials implies the router credentials
can be trusted, in the context of this security
mechanism. How a security mechanism interacts with this
list is determined by the mechanism. A security algorithm
may do additional validation of credentials, such as
checking validity dates or revocation lists, so presence
in this list may not be sufficient to determine trust.
Adding and deleting credentials MAY be allowed.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.5."; "RFC ZZZZ, Babel Information Model, Section 3.6.";
} }
leaf credvalid-log-enable { leaf feasible {
type boolean; type boolean;
description description
"If true, logging of messages that include credentials "A boolean flag indicating whether this route is feasible.";
used for authentication is enabled. If false, these
messages are not logged.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.5."; "RFC ZZZZ, Babel Information Model, Section 3.6,
draft-ietf-babel-rfc6126bis, The Babel Routing Protocol,
Section 3.5.1.";
} }
list credvalid-log { leaf selected {
key "log-time"; type boolean;
uses log;
description description
"Log entries that have the timestamp a message containing "A boolean flag indicating whether this route is selected,
credentials used for peer authentication (e.g., DTLS i.e., whether it is currently being used for forwarding and
Server Hello) was received on a Babel port, and the is being advertised.";
entire received message (including Ethernet frame and IP
headers, if possible); an implementation must restrict
the size of this log, but how and what size is
implementation-specific.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.5."; "RFC ZZZZ, Babel Information Model, Section 3.6.";
} }
description description
"A babel-security-obj list."; "A set of babel-route-obj objects. Includes received and
routes routes.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.5."; "RFC ZZZZ, Babel Information Model, Section 3.1.";
} }
description
"Common grouping for routing used in RIB augmentation.";
}
/*
* Data model
*/
augment "/rt:routing/rt:control-plane-protocols/" +
"rt:control-plane-protocol" {
when "derived-from-or-self(rt:type, 'babel')" {
description
"Augmentation is valid only when the instance of routing type
is of type 'babel'.";
}
description
"Augment the routing module to support features such as VRF.";
reference
"YANG Routing Management, RFC 8349, Lhotka & Lindem, March
2018.";
/*
* Data model
*/
container babel { container babel {
presence "A Babel container."; presence "A Babel container.";
description
"This is a top level container for the Babel routing protocol.";
leaf version { leaf version {
type string; type string;
config false;
description description
"This is the version of the babel protocol implemented."; "The name and version of this implementation of the Babel
protocol.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.1."; "RFC ZZZZ, Babel Information Model, Section 3.1.";
} }
leaf enable { leaf enable {
type boolean; type boolean;
default false; default false;
description description
"When written, it configures whether the protocol should be "When written, it configures whether the protocol should be
enabled. A read from the <running> or <intended> datastore enabled. A read from the <running> or <intended> datastore
therefore indicates the configured adminstrative value of therefore indicates the configured administrative value of
whether the protocol is enabled or not. whether the protocol is enabled or not.
A read from the <operational> datastore indicates whether A read from the <operational> datastore indicates whether
the protocol is actually running or not, i.e. it indicates the protocol is actually running or not, i.e. it indicates
the operational state of the protocol."; the operational state of the protocol.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.1."; "RFC ZZZZ, Babel Information Model, Section 3.1.";
} }
leaf router-id { leaf router-id {
type binary; type binary;
config false;
mandatory "true"; mandatory "true";
description description
"Every Babel speaker is assigned a router-id, which is an "Every Babel speaker is assigned a router-id, which is an
arbitrary string of 8 octets that is assumed to be unique arbitrary string of 8 octets that is assumed to be unique
across the routing domain"; across the routing domain";
reference reference
"RFC YYYY, Babel Information Model, Section 3.1, "RFC ZZZZ, Babel Information Model, Section 3.1,
rfc6126bis, The Babel Routing Protocol. Section 3."; rfc6126bis, The Babel Routing Protocol. Section 3.";
} }
leaf-list link-type { leaf-list link-type {
type identityref { type identityref {
base "babel-link-type"; base "link-type";
} }
description description
"Link types supported by this implementation of Babel."; "Link types supported by this implementation of Babel.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.1."; "RFC ZZZZ, Babel Information Model, Section 3.1.";
} }
leaf sequence-number { leaf sequence-number {
type yang:counter32; 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 YYYY, Babel Information Model, Section 3.1."; "RFC ZZZZ, Babel Information Model, Section 3.1.";
} }
leaf-list cost-compute-algorithm { leaf-list metric-comp-algorithms {
type identityref { type identityref {
base "babel-cost-compute-algorithm"; base "metric-comp-algorithms";
} }
description description
"List of cost compute algorithms supported by this "List of cost compute algorithms supported by this
implementation of Babel."; implementation of Babel.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.1."; "RFC ZZZZ, Babel Information Model, Section 3.1.";
} }
leaf-list security-supported { leaf-list security-supported {
type identityref { type identityref {
base "babel-security-supported"; base "security-supported";
} }
description description
"Babel security mechanism used by this implementation or "Babel security mechanism used by this implementation or
per interface."; per interface.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.1."; "RFC ZZZZ, Babel Information Model, Section 3.1.";
} }
container transport { leaf hmac-enable {
type boolean;
description
"Indicates whether the HMAC security mechanism is enabled
(true) or disabled (false).";
reference
"RFC ZZZZ, Babel Information Model, Section 3.1.";
}
leaf-list hmac-algorithms {
type identityref {
base hmac-algorithms;
}
description
"List of supported HMAC computation algorithms. Possible
values include 'HMAC-SHA256', 'BLAKE2s'.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.1.";
}
leaf dtls-enable {
type boolean;
description
"Indicates whether the DTLS security mechanism is enabled
(true) or disabled (false).";
reference
"RFC ZZZZ, Babel Information Model, Section 3.1.";
}
leaf-list dtls-cert-types {
type identityref {
base dtls-cert-types;
}
description
"List of supported DTLS certificate types. Possible values
include 'X.509' and 'RawPublicKey'.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.1.";
}
leaf stats-enable {
type boolean;
description
"Indicates whether statistics collection is enabled (true)
or disabled (false) on all interfaces, including
neighbor-specific statistics (babel-nbr-stats).";
}
container constants {
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 YYYY, 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:0:0:0:0:0:1:6"; default "ff02:0:0:0:0:0: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 YYYY, Babel Information Model, Section 3.2."; "RFC ZZZZ, Babel Information Model, Section 3.2.";
} }
description description
"Babel Transport object."; "Babel Constants object.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.1."; "RFC ZZZZ, Babel Information Model, Section 3.1.";
} }
list interfaces { list interfaces {
key "reference"; key "reference";
leaf reference { leaf reference {
type if:interface-ref; type if:interface-ref;
description description
"Reference to an interface object as defined by the data "Reference to an interface object as defined by the data
model (e.g., YANG, BBF TR-181); data model is assumed to model (e.g., YANG, BBF TR-181); data model is assumed to
allow for referencing of interface objects which may be at allow for referencing of interface objects which may be at
any layer (physical, Ethernet MAC, IP, tunneled IP, etc.). any layer (physical, Ethernet MAC, IP, tunneled IP, etc.).
skipping to change at page 13, line 50 skipping to change at page 18, line 48
description description
"Reference to an interface object as defined by the data "Reference to an interface object as defined by the data
model (e.g., YANG, BBF TR-181); data model is assumed to model (e.g., YANG, BBF TR-181); data model is assumed to
allow for referencing of interface objects which may be at allow for referencing of interface objects which may be at
any layer (physical, Ethernet MAC, IP, tunneled IP, etc.). any layer (physical, Ethernet MAC, IP, tunneled IP, etc.).
Referencing syntax will be specific to the data model. If Referencing syntax will be specific to the data model. If
there is no set of interface objects available, this should there is no set of interface objects available, this should
be a string that indicates the interface name used by the be a string that indicates the interface name used by the
underlying operating system."; underlying operating system.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.3."; "RFC ZZZZ, Babel Information Model, Section 3.3.";
} }
leaf enable { leaf enable {
type boolean; type boolean;
default "true"; default "true";
description description
"If true, babel sends and receives messages on this "If true, babel sends and receives messages on this
interface. If false, babel messages received on this interface. If false, babel messages received on this
interface are ignored and none are sent."; interface are ignored and none are sent.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.3."; "RFC ZZZZ, Babel Information Model, Section 3.3.";
} }
leaf link-type { leaf link-type {
type identityref { type identityref {
base babel-link-type; base link-type;
} }
default "ethernet";
description description
"Indicates the type of link. Set of values of supported "Indicates the type of link. Set of values of supported
link types where the following enumeration values MUST link types where the following enumeration values MUST
be supported when applicable: 'ethernet', 'wireless', be supported when applicable: 'ethernet', 'wireless',
'tunnel', and 'other'. Additional values MAY be 'tunnel', and 'other'. Additional values MAY be
supported."; supported.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.3."; "RFC ZZZZ, Babel Information Model, Section 3.3.";
} }
leaf mcast-hello-seqno {
type int16; leaf metric-algorithm {
config false; type identityref {
base metric-comp-algorithms;
}
default "k-out-of-j";
description description
"The current sequence number in use for multicast hellos "Indicates the metric computation algorithm used on this
sent on this interface."; interface. The value MUST be one of those listed in the
reference babel-information-obj babel-metric-comp-algorithms
"RFC YYYY, Babel Information Model, Section 3.3."; parameter.";
} }
leaf ucast-hello-seqno {
type int16; leaf mcast-hello-seqno {
type uint16;
config false; config false;
description description
"The current sequence number in use for unicast hellos "The current sequence number in use for multicast hellos
sent on this interface."; sent on this interface.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.3."; "RFC ZZZZ, Babel Information Model, Section 3.3.";
} }
leaf mcast-hello-interval { leaf mcast-hello-interval {
type int16; type uint16;
config false; config false;
description description
"The current multicast hello interval in use for hellos "The current multicast hello interval in use for hellos
sent on this interface."; sent on this interface.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.3."; "RFC ZZZZ, Babel Information Model, Section 3.3.";
}
leaf ucast-hello-interval {
type int16;
config false;
description
"The current unicast hello interval in use for hellos sent
on this interface.";
reference
"RFC YYYY, Babel Information Model, Section 3.3.";
} }
leaf update-interval { leaf update-interval {
type uint32; type uint16;
units centiseconds;
description description
"The current update interval in use for this interface."; "The current update interval in use for this interface.
Units are centiseconds.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.3."; "RFC ZZZZ, Babel Information Model, Section 3.3.";
} }
leaf external-cost {
type uint32; leaf packet-log-enable {
type boolean;
description description
"External input to cost of link of this interface. If "If true, logging of babel packets received on this
supported, this is a value that is added to the metrics interface is enabled; if false, babel packets are not
of routes learned over this interface. How an logged.";
implementation uses the value is up to the implementation,
which means the use may not be consistent across
implementations.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.3."; "RFC ZZZZ, Babel Information Model, Section 3.3.";
} }
leaf message-log-enable {
type boolean; leaf packet-log {
type inet:uri;
description description
"If true, logging of babel messages received on this "A reference or url link to a file that contains a
interface is enabled; if false, babel messages are not timestamped log of packets received and sent on
logged."; babel-udp-port on this interface. The [libpcap] file
format with .pcap file extension SHOULD be supported for
packet log files. Logging is enabled / disabled by
packet-log-enable.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.3."; "RFC ZZZZ, Babel Information Model, Section 3.3.";
} }
list message-log { container stats {
key "log-time"; config false;
leaf sent-mcast-hello {
type yt:counter32;
description
"A count of the number of multicast Hello packets sent
on this interface.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.4.";
}
uses log; leaf sent-mcast-update {
type yt:counter32;
description
"A count of the number of multicast update packets sent
on this interface.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.4.";
}
leaf received-packets {
type yt:counter32;
description
"A count of the number of Babel packets received on
this interface.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.4.";
}
action reset {
input {
leaf reset-at {
type yt:date-and-time;
description
"The time when the reset was issued.";
}
}
output {
leaf reset-finished-at {
type yt:date-and-time;
description
"The time when the reset finished.";
}
}
}
description description
"Log entries that have timestamp of a received Babel "Statistics collection object for this interface.";
message and the entire received Babel message (including
Ethernet frame and IP headers, if possible). An
implementation must restrict the size of this log, but how
and what size is implementation specific.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.3."; "RFC ZZZZ, Babel Information Model, Section 3.3.";
} }
list neighbor-objects { list neighbor-objects {
key "neighbor-address"; key "neighbor-address";
leaf neighbor-address { leaf neighbor-address {
type inet:ip-address; type inet:ip-address;
description description
"IPv4 or v6 address the neighbor sends messages from."; "IPv4 or v6 address the neighbor sends packets from.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.4."; "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 messages prior to babel-exp-mcast- multicast Hello packets prior to babel-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 YYYY, Babel Information Model, Section 3.4."; "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 messages prior to babel-exp-ucast- unicast Hello packets prior to babel-exp-ucast-
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 YYYY, Babel Information Model, Section 3.4."; "RFC ZZZZ, Babel Information Model, Section 3.5.";
} }
leaf txcost { leaf txcost {
type int32; type int32;
default "0";
description description
"Transmission cost value from the last IHU packet "Transmission cost value from the last IHU packet
received from this neighbor, or maximum value received from this neighbor, or maximum value
(infinity) to indicates the IHU hold timer for this (infinity) to indicates the IHU hold timer for this
neighbor has expired description."; neighbor has expired description.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.4."; "RFC ZZZZ, Babel Information Model, Section 3.5.";
} }
leaf exp-mcast-hello-seqno { leaf exp-mcast-hello-seqno {
type int32; type uint16;
default "0";
description description
"Expected multicast Hello sequence number of next Hello "Expected multicast Hello sequence number of next Hello
to be received from this neighbor; if multicast Hello to be received from this neighbor; if multicast Hello
messages are not expected, or processing of multicast packets are not expected, or processing of multicast
messages is not enabled, this MUST be 0."; packets is not enabled, this MUST be 0.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.4."; "RFC ZZZZ, Babel Information Model, Section 3.5.";
} }
leaf exp-ucast-hello-seqno { leaf exp-ucast-hello-seqno {
type int32; type uint16;
default "0";
description description
"Expected unicast Hello sequence number of next Hello to "Expected unicast Hello sequence number of next Hello to
be received from this neighbor; if unicast Hello be received from this neighbor; if unicast Hello
messages are not expected, or processing of unicast packets are not expected, or processing of unicast
messages is not enabled, this MUST be 0."; packets is not enabled, this MUST be 0.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.4."; "RFC ZZZZ, Babel Information Model, Section 3.5.";
} }
leaf neighbor-ihu-interval { leaf ucast-hello-seqno {
type int32; type uint16;
description description
"Current IHU interval for this neighbor."; "Expected unicast Hello sequence number of next Hello
to be received from this neighbor. If unicast Hello
packets are not expected, or processing of unicast
packets is not enabled, this MUST be 0.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.4."; "RFC ZZZZ, Babel Information Model, Section 3.5.";
} }
leaf ucast-hello-interval {
type uint16;
units centiseconds;
description
"The current interval in use for unicast hellos sent to
this neighbor. Units are centiseconds.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.5.";
}
leaf rxcost { leaf rxcost {
type int32; type int32;
description description
"Reception cost calculated for this neighbor. This value "Reception cost calculated for this neighbor. This value
is usually derived from the Hello history, which may be is usually derived from the Hello history, which may be
combined with other data, such as statistics maintained combined with other data, such as statistics maintained
by the link layer. The rxcost is sent to a neighbour in by the link layer. The rxcost is sent to a neighbor in
each IHU."; each IHU.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.4."; "RFC ZZZZ, Babel Information Model, Section 3.5.";
} }
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 neighbour table. The statistics kept in the neighbour 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 YYYY, Babel Information Model, Section 3.4."; "RFC ZZZZ, Babel Information Model, Section 3.5.";
} }
description
"A set of Babel Neighbor Object.";
reference
"RFC YYYY, Babel Information Model, Section 3.3.";
}
list security { container stats {
key "mechanism"; config false;
leaf sent-ucast-hello {
type yt:counter32;
description
"A count of the number of unicast Hello packets sent
to this neighbor.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.6.";
}
uses security; leaf sent-ucast-update {
type yt:counter32;
description
"A count of the number of unicast update packets sent
to this neighbor.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.6.";
}
leaf sent-ihu {
type yt:counter32;
description
"A count of the number of IHU packets sent to this
neighbor.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.6.";
}
leaf received-hello {
type yt:counter32;
description
"A count of the number of Hello packets received from
this neighbor.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.6.";
}
leaf received-update {
type yt:counter32;
description
"A count of the number of update packets received
from this neighbor.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.6.";
}
leaf received-ihu {
type yt:counter32;
description
"A count of the number of IHU packets received from
this neighbor.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.6.";
}
action reset {
input {
leaf reset-at {
type yt:date-and-time;
description
"The time the reset was issued.";
}
}
output {
leaf reset-finished-at {
type yt:date-and-time;
description
"The time when the reset operation finished.";
}
}
}
description
"Statistics collection object for this neighbor.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.6.";
}
description description
"A security-obj object that applies to this interface. If "A set of Babel Neighbor Object.";
implemented, this allows security to be enabled only on
specific interfaces or allows different security mechanisms
to be enabled on different interfaces.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.3."; "RFC ZZZZ, Babel Information Model, Section 3.5.";
} }
description description
"A set of Babel Interface objects."; "A set of Babel Interface objects.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.1."; "RFC ZZZZ, Babel Information Model, Section 3.3.";
} }
list routes { list hmac {
key "prefix"; key "algorithm";
leaf prefix { leaf algorithm {
type inet:ip-address; type identityref {
base hmac-algorithms;
}
description description
"Prefix (expressed in IP address format) for which this "The name of the HMAC algorithm this object instance uses.
route is advertised."; The value MUST be the same as one of the enumerations
listed in the babel-hmac-algorithms parameter.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.6."; "RFC ZZZZ, Babel Information Model, Section 3.8.";
} }
leaf prefix-length { leaf verify {
type inet:ip-prefix; type boolean;
mandatory "true";
description description
"Length of the prefix for which this route is advertised."; "A Boolean flag indicating whether HMAC hashes in incoming
Babel packets are required to be present and are
verified. If this parameter is 'true', incoming packets
are required to have a valid HMAC hash.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.6."; "RFC ZZZZ, Babel Information Model, Section 3.8.";
} }
leaf router-id { leaf apply-all {
type binary; type boolean;
mandatory "true";
description description
"router-id of the source router for which this route is "A Boolean flag indicating whether this babel-hmac
advertised."; instance is to be used for all interfaces. If 'true',
this instance applies to all interfaces and the
babel-hmac-interfaces parameter is ignored. If
babel-hmac-apply-all is 'true', there MUST NOT be other
instances of the babel-hmac object. If 'false', the
babel-hmac-interfaces parameter determines which
interfaces this instance applies to.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.6."; "RFC ZZZZ, Babel Information Model, Section 3.8.";
} }
leaf neighbor { leaf-list interfaces {
type leafref { type if:interface-ref;
path "../../interfaces/neighbor-objects/neighbor-address"; min-elements "1";
}
description description
"Reference to the babel-neighbors entry for the neighbor "List of references to the babel-interfaces entries this
that advertised this route."; babel-hmac entry applies to. This parameter is ignored
if babel-hmac-apply-all is 'true'. An interface MUST NOT
be listed in multiple instances of the babel-hmac
object.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.6."; "RFC ZZZZ, Babel Information Model, Section 3.8.";
} }
choice metric { list hmac-keys {
mandatory "true"; key "name";
leaf received-metric { min-elements "1";
type int32;
leaf name {
type string;
mandatory "true";
description description
"The metric with which this route was advertised by the "A unique name for this HMAC key that can be used to
neighbor, or maximum value (infinity) to indicate a the identify the key in this object instance, since the key
route was recently retracted and is temporarily value is not allowed to be read. This value can only be
unreachable. this metric will be 0 (zero) if the route provided when this instance is created, and is not
was not received from a neighbor but was generated subsequently writable.";
through other means. Either babel-route-calculated-metric
or babel-route-received-metric MUST be provided.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.6, "RFC ZZZZ, Babel Information Model, Section 3.9.";
draft-ietf-babel-rfc6126bis, The Babel Routing Protocol,
Section 3.5.5.";
} }
leaf calcuated-metric {
type int32; leaf use-sign {
type boolean;
mandatory "true";
description description
"A calculated metric for this route. How the metric is "Indicates whether this key value is used to sign sent
calculated is implementation-specific. Maximum value Babel packets. Sent packets are signed using this key
(infinity) indicates the route was recently retracted if the value is 'true'. If the value is 'false', this
and is temporarily unreachable. Either key is not used to sign sent Babel packets.";
babel-route-calculated-metric or
babel-route-received-metric MUST be provided.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.6, "RFC ZZZZ, Babel Information Model, Section 3.9.";
draft-ietf-babel-rfc6126bis, The Babel Routing Protocol, }
Section 3.5.5.";
leaf use-verify {
type boolean;
mandatory "true";
description
"Indicates whether this key value is used to verify
incoming Babel packets. This key is used to verify
incoming packets if the value is 'true'. If the value
is 'false', no HMAC is computed from this key for
comparing an incoming packet.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.9.";
}
leaf value {
type binary;
mandatory "true";
description
"The value of the HMAC key. An implementation MUST NOT
allow this parameter to be read. This can be done by
always providing an empty string, or through
permissions, or other means. This value can only be
provided when this instance is created, and is not
subsequently writable.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.9.";
}
action test {
input {
leaf test-string {
type binary;
mandatory "true";
description
"The test string on which this test has to be
performed.";
}
}
output {
leaf resulting-hash {
type binary;
mandatory "true";
description
"An operation that allows the HMAC 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
babel-hmac-key-value and the babel-hmac-algorithm.
The output of this operation is the resulting hash,
as a binary string.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.9.";
}
}
} }
description description
"Either babel-route-calculated-metric or "A set of babel-hmac-keys-obj objects.";
babel-route-received-metric MUST be provided.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.6, "RFC ZZZZ, Babel Information Model, Section 3.8.";
draft-ietf-babel-rfc6126bis, The Babel Routing Protocol,
Section 3.5.5.";
} }
description
"A babel-hmac-obj object. If this object is implemented, it
provides access to parameters related to the HMAC security
mechanism.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.1.";
}
leaf seqno { list dtls {
type int32; key "name";
leaf name {
type string;
description description
"The sequence number with which this route was advertised."; "TODO: This attribute does not exist in the model, but is
needed for this model to work.";
}
leaf apply-all {
type boolean;
mandatory "true";
description
"A Boolean flag indicating whether this babel-dtls
instance is to be used for all interfaces. If 'true',
this instance applies to all interfaces and the
babel-dtls-interfaces parameter is ignored. If
babel-dtls-apply-all is 'true', there MUST NOT be other
instances of the babel-dtls object. If 'false', the
babel-dtls-interfaces parameter determines which
interfaces this instance applies to.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.6."; "RFC ZZZZ, Babel Information Model, Section 3.10.";
} }
leaf next-hop { leaf-list interfaces {
type inet:ip-address; type if:interface-ref;
min-elements "1";
description description
"The next-hop address of this route. This will be empty if "List of references to the babel-interfaces entries this
this route has no next-hop address."; babel-dtls entry applies to. This parameter is ignored
if babel-dtls-apply-all is 'true'. An interface MUST NOT
be listed in multiple instances of the babel-dtls object.
If this list is empty, then it applies to all
interfaces.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.6."; "RFC ZZZZ, Babel Information Model, Section 3.10.";
} }
leaf feasible { leaf cached-info {
type boolean; type boolean;
description description
"A boolean flag indicating whether this route is feasible."; "Indicates whether the cached_info extension is included
in ClientHello and ServerHello packets. The extension
is included if the value is 'true'.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.6, "RFC ZZZZ, Babel Information Model, Section 3.10.";
draft-ietf-babel-rfc6126bis, The Babel Routing Protocol,
Section 3.5.1.";
} }
leaf selected { leaf-list cert-prefer {
type boolean; type identityref {
base dtls-cert-types;
}
ordered-by user;
description description
"A boolean flag indicating whether this route is selected, "List of supported certificate types, in order of
i.e., whether it is currently being used for forwarding and preference. The values MUST be among those listed in
is being advertised."; the babel-dtls-cert-types parameter. This list is used
to populate the server_certificate_type extension in
a Client Hello. Values that are present in at least one
instance in the babel-dtls-certs object with a non-empty
babel-cert-private-key will be used bto populate the
client_certificate_type extension in a Client Hello.";
reference reference
"RFC YYYY, Babel Information Model, Section 3.6."; "RFC ZZZZ, Babel Information Model, Section 3.10.";
} }
description
"A set of babel-route-obj objects. Includes received and
routes routes.";
reference
"RFC YYYY, Babel Information Model, Section 3.1.";
}
list security { list certs {
key "mechanism"; key "name";
min-elements "1";
leaf name {
type string;
description
"A unique name that identifies the cert in the list.";
}
uses security; leaf value {
type string;
mandatory "true";
description
"The DTLS certificate in PEM format [RFC7468]. This
value can only be provided when this instance is
created, and is not subsequently writable.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.11.";
}
leaf type {
type identityref {
base dtls-cert-types;
}
mandatory "true";
description
"The name of the certificate type of this object
instance. The value MUST be the same as one of the
enumerations listed in the babel-dtls-cert-types
parameter. This value can only be provided when this
instance is created, and is not subsequently writable.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.11.";
}
leaf private-key {
type binary;
mandatory "true";
description
"The value of the private key. If this is non-empty,
this certificate can be used by this implementation to
provide a certificate during DTLS handshaking. An
implementation MUST NOT allow this parameter to be
read. This can be done by always providing an empty
string, or through permissions, or other means. This
value can only be provided when this instance is
created, and is not subsequently writable.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.11.";
}
action test {
input {
leaf test-string {
type binary;
mandatory "true";
description
"The test string on which this test has to be
performed.";
}
}
output {
leaf resulting-hash {
type binary;
mandatory "true";
description
"The output of this operation is a binary string,
and is the resulting hash computed using the
certificate public key, and the SHA-256
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 description
"A security-obj object that applies to all interfaces. If this "A babel-dtls-obj object. If this object is implemented,
object is implemented, it allows a security mechanism to be it provides access to parameters related to the DTLS
enabled or disabled in a manner that applies to all Babel security mechanism.";
messages on all interfaces";
reference reference
"RFC YYYY, Babel Information Model, Section 3.1."; "RFC ZZZZ, Babel Information Model, Section 3.1";
} }
description
"Babel Information Objects.";
reference
"RFC ZZZZ, Babel Information Model, Section 3.";
} }
} }
augment "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route" {
when "derived-from(rt:source-protocol, 'babel')" {
description
"Augmentation is valid for a routes whose source protocol
is Babel.";
}
description
"Babel specific route attributes.";
uses routes;
}
}
<CODE ENDS> <CODE ENDS>
3. IANA Considerations 3. IANA Considerations
This document registers ?? URIs and ?? YANG modules. This document registers one URIs and one YANG module.
3.1. URI Registrations 3.1. URI Registrations
URI: urn:ietf:params:xml:ns:yang:ietf-babel
3.2. YANG Module Name Registration 3.2. YANG Module Name Registration
This document registers ?? YANG module in the YANG Module Names This document registers one YANG module in the YANG Module Names
registry YANG [RFC6020]. registry YANG [RFC6020].
name: Name:ietf-babel
namespace: urn:ietf:params:xml:ns:yang: Namespace: urn:ietf:params:xml:ns:yang:ietf-babel
prefix: babel prefix: babel
reference: RFC XXXX reference: RFC XXXX
4. Security Considerations 4. Security Considerations
The YANG module specified in this document defines a schema for data The YANG module specified in this document defines a schema for data
that is designed to be accessed via network management protocol such that is designed to be accessed via network management protocol such
as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
is the secure transport layer and the mandatory-to-implement secure is the secure transport layer and the mandatory-to-implement secure
transport is SSH [RFC6242]. The lowest RESTCONF layer is HTTPS, and transport is SSH [RFC6242]. The lowest RESTCONF layer is HTTPS, and
the mandatory-to-implement secure transport is TLS [RFC5246]. the mandatory-to-implement secure transport is TLS [RFC8446].
The NETCONF Access Control Model (NACM [RFC8341]) provides the means The NETCONF Access Control Model (NACM [RFC8341]) provides the means
to restrict access for particular NETCONF users to a pre-configured to restrict access for particular NETCONF users to a pre-configured
subset of all available NETCONF protocol operations and content. subset of all available NETCONF protocol operations and content.
There are a number of data nodes defined in the YANG module which are There are a number of data nodes defined in the YANG module which are
writable/creatable/deletable (i.e., config true, which is the writable/created/deleted (i.e., config true, which is the default).
default). These data nodes may be considered sensitive or vulnerable These data nodes may be considered sensitive or vulnerable in some
in some network environments. Write operations (e.g., <edit-config>) network environments. Write operations (e.g., <edit-config>) to
to these data nodes without proper protection can have a negative these data nodes without proper protection can have a negative effect
effect on network operations. on network operations.
These are the subtrees and data nodes and their sensitivity/ These are the subtrees and data nodes and their sensitivity/
vulnerability: vulnerability:
5. Acknowledgements 5. Acknowledgements
6. References 6. References
6.1. Normative References 6.1. Normative References
skipping to change at page 23, line 13 skipping to change at page 34, line 36
<https://www.rfc-editor.org/info/rfc6991>. <https://www.rfc-editor.org/info/rfc6991>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8343] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
<https://www.rfc-editor.org/info/rfc8343>.
[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
Routing Management (NMDA Version)", RFC 8349,
DOI 10.17487/RFC8349, March 2018,
<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., "Babel Information Model", draft-ietf-babel- Stark, B. and M. Jethanandani, "Babel Information Model",
information-model-04 (work in progress), October 2018. draft-ietf-babel-information-model-05 (work in progress),
March 2019.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008,
<https://www.rfc-editor.org/info/rfc5246>.
[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>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
skipping to change at page 24, line 5 skipping to change at page 35, line 32
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>. <https://www.rfc-editor.org/info/rfc8340>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341, Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018, DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/info/rfc8341>. <https://www.rfc-editor.org/info/rfc8341>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>.
Appendix A. An Appendix Appendix A. An Appendix
Authors' Addresses Authors' Addresses
Mahesh Jethanandani Mahesh Jethanandani
VMware VMware
California California
USA USA
Email: mjethanandani@gmail.com Email: mjethanandani@gmail.com
 End of changes. 196 change blocks. 
574 lines changed or deleted 1123 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/