draft-ietf-babel-information-model-02.txt   draft-ietf-babel-information-model-03.txt 
Babel routing protocol B. Stark Babel routing protocol B. Stark
Internet-Draft AT&T Internet-Draft AT&T
Intended status: Informational April 5, 2018 Intended status: Informational June 5, 2018
Expires: October 7, 2018 Expires: December 7, 2018
Babel Information Model Babel Information Model
draft-ietf-babel-information-model-02 draft-ietf-babel-information-model-03
Abstract Abstract
This Babel Information Model can be used to create data models under This Babel Information Model can be used to create data models under
various data modeling regimes (e.g., YANG). It allows a Babel various data modeling regimes (e.g., YANG). It allows a Babel
implementation (via a management protocol such as netconf) to report implementation (via a management protocol such as netconf) to report
on its current state and may allow some limited configuration of on its current state and may allow some limited configuration of
protocol constants. protocol constants.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 October 7, 2018. This Internet-Draft will expire on December 7, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 14 skipping to change at page 2, line 14
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
1.2. Notation . . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Notation . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. The Information Model . . . . . . . . . . . . . . . . . . . . 5 3. The Information Model . . . . . . . . . . . . . . . . . . . . 5
3.1. Definition of babel-information-obj . . . . . . . . . . . 5 3.1. Definition of babel-information-obj . . . . . . . . . . . 5
3.2. Definition of babel-constants-obj . . . . . . . . . . . . 6 3.2. Definition of babel-constants-obj . . . . . . . . . . . . 6
3.3. Definition of babel-interfaces-obj . . . . . . . . . . . 7 3.3. Definition of babel-interfaces-obj . . . . . . . . . . . 6
3.4. Definition of babel-neighbors-obj . . . . . . . . . . . . 8 3.4. Definition of babel-neighbors-obj . . . . . . . . . . . . 8
3.5. Definition of babel-security-obj . . . . . . . . . . . . 9 3.5. Definition of babel-security-obj . . . . . . . . . . . . 9
3.6. Definition of babel-routes-obj . . . . . . . . . . . . . 10 3.6. Definition of babel-routes-obj . . . . . . . . . . . . . 11
4. Common Objects . . . . . . . . . . . . . . . . . . . . . . . 11 4. Common Objects . . . . . . . . . . . . . . . . . . . . . . . 12
4.1. Definition of babel-credential-obj . . . . . . . . . . . 11 4.1. Definition of babel-credential-obj . . . . . . . . . . . 12
4.2. Definition of babel-log-obj . . . . . . . . . . . . . . . 11 4.2. Definition of babel-log-obj . . . . . . . . . . . . . . . 12
5. Extending the Information Model . . . . . . . . . . . . . . . 11 5. Extending the Information Model . . . . . . . . . . . . . . . 12
6. Security Considerations . . . . . . . . . . . . . . . . . . . 12 6. Security Considerations . . . . . . . . . . . . . . . . . . . 13
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
9.1. Normative References . . . . . . . . . . . . . . . . . . 12 9.1. Normative References . . . . . . . . . . . . . . . . . . 13
9.2. Informative References . . . . . . . . . . . . . . . . . 12 9.2. Informative References . . . . . . . . . . . . . . . . . 14
Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . 13 Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . 14
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 14 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 16
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 16 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction 1. Introduction
Babel is a loop-avoiding distance-vector routing protocol defined in Babel is a loop-avoiding distance-vector routing protocol defined in
draft-ietf-babel-rfc6126bis [rfc6126bis]. draft-babel-7298bis draft-ietf-babel-rfc6126bis [rfc6126bis]. draft-babel-7298bis
[BABEL-HMAC] defines a security mechanism that allows Babel messages [BABEL-HMAC] defines a security mechanism that allows Babel messages
to be cryptographically authenticated, and draft-babel-dtls to be cryptographically authenticated, and draft-babel-dtls
[BABEL-DTLS] defines a security mechanism that allows Babel messages [BABEL-DTLS] defines a security mechanism that allows Babel messages
to encrypted. This document describes an information model for Babel to encrypted. This document describes an information model for Babel
(including implementations using one of these security mechanisms) (including implementations using one of these security mechanisms)
that can be used to created management protocol data models (such as that can be used to created management protocol data models (such as
a netconf [RFC6241] YANG data model). a netconf [RFC6241] YANG data model).
Due to the simplicity of the Babel protocol and the fact that it is Due to the simplicity of the Babel protocol, most of the information
designed to be used in non-professionally administered environments model is focused on reporting status of the Babel protocol, and very
(such as home networks), most of the information model is focused on little of that is considered mandatory to implement (conditional on a
reporting status of the Babel protocol, and very little of that is management protocol with Babel support being implemented). Some
considered mandatory to implement (conditional on a management parameters may be configurable; however, it is up to the Babel
protocol with Babel support being implemented). Some parameters may implementation whether to allow any of these to be configured within
be configurable; however, it is up to the Babel implementation its implementation. Where the implementation does not allow
whether to allow any of these to be configured within its
implementation. Where the implementation does not allow
configuration of these parameters, it may still choose to expose them configuration of these parameters, it may still choose to expose them
as read-only. as read-only.
The Information Model is presented using a hierarchical structure. The Information Model is presented using a hierarchical structure.
This does not preclude a data model based on this Information Model This does not preclude a data model based on this Information Model
from using a referential or other structure. from using a referential or other structure.
1.1. Requirements Language 1.1. 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
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119] and
updated by RFC 8174 [RFC8174] .
1.2. Notation 1.2. Notation
This document uses a programming language-like notation to define the This document uses a programming language-like notation to define the
properties of the objects of the information model. An optional properties of the objects of the information model. An optional
property is enclosed by square brackets, [ ], and a list property is property is enclosed by square brackets, [ ], and a list property is
indicated by two numbers in angle brackets, <m..n>, where m indicates indicated by two numbers in angle brackets, <m..n>, where m indicates
the minimal number of values, and n is the maximum. The symbol * for the minimal number of values, and n is the maximum. The symbol * for
n means no upper bound. n means no upper bound.
skipping to change at page 3, line 48 skipping to change at page 3, line 47
models must expand this opaque type as needed and models must expand this opaque type as needed and
required by the security protocols utilized. required by the security protocols utilized.
datetime A type representing a date and time using the Gregorian datetime A type representing a date and time using the Gregorian
calendar. The datetime format MUST conform to RFC 3339 calendar. The datetime format MUST conform to RFC 3339
[RFC3339]. [RFC3339].
int A type representing signed or unsigned integer numbers. int A type representing signed or unsigned integer numbers.
This information model does not define a precision nor This information model does not define a precision nor
does it make a distinction between signed and unsigned does it make a distinction between signed and unsigned
number ranges. This type is also used to represent number ranges.
enumerations.
ip-address A type representing an IP address. This type supports ip-address A type representing an IP address. This type supports
both IPv4 and IPv6 addresses. both IPv4 and IPv6 addresses.
string A type representing a human-readable string consisting of string A type representing a human-readable string consisting of
a (possibly restricted) subset of Unicode and ISO/IEC a (possibly restricted) subset of Unicode and ISO/IEC
10646 [ISO.10646] characters. 10646 [ISO.10646] characters.
uri A type representing a Uniform Resource Identifier as uri A type representing a Uniform Resource Identifier as
defined in STD 66 [RFC3986]. defined in STD 66 [RFC3986].
2. Overview 2. Overview
The Information Model is hierarchically structured as follows: The Information Model is hierarchically structured as follows:
information object information object
includes implementation version, router id, this node seqno, includes implementation version, router id, this node seqno,
enable flag parameters enable flag parameters, supported security mechanisms
constants object (exactly one per information object) constants object (exactly one per information object)
includes UDP port and optional multicast and unicast groups includes UDP port and optional multicast group
parameters parameters
interfaces object interfaces object
includes interface reference, Hello seqno and intervals, includes interface reference, Hello seqno and intervals,
update interval, link type, external cost parameters update interval, link type, external cost parameters
neighbors object neighbors object
includes neighbor IP address, Hello history, cost includes neighbor IP address, Hello history, cost
parameters parameters
security object (per interface) security object (per interface)
includes supported and enabled security mechanisms, self includes enable flag, self credentials (credential
credentials (credential object), trusted credentials object), trusted credentials (credential object)
(credential object)
security object (common to all interfaces) security object (common to all interfaces)
includes supported and enabled security mechanisms, self includes enable flag, self credentials (credential
credentials (credential object), trusted credentials object), trusted credentials (credential object)
(credential object)
routes object routes object
includes route prefix, source router, reference to includes route prefix, source router, reference to
advertising neighbor, metric, sequence number, whether advertising neighbor, metric, sequence number, whether
route is feasible, whether route is selected route is feasible, whether route is selected
Following is a list of the data elements that an implementation can Following is a list of the data elements that an implementation can
choose to allow to be configurable: choose to allow to be configurable:
o enable/disable babel o enable/disable babel
o Constant: UDP port o Constant: UDP port
o Constant: IPv6 multicast group o Constant: IPv6 multicast group
o Constant: IPv4 multicast group
o Interface: Link type o Interface: Link type
o Interface: External cost (must be configurable if implemented, but o Interface: External cost (must be configurable if implemented, but
implementation is optional) implementation is optional)
o Interface: enable/disable babel on this interface o Interface: enable/disable babel on this interface
o Interface: enable/disable message log o Interface: enable/disable message log
o Security: enable/disable this security mechanism
o Security: self credentials o Security: self credentials
o Security: trusted credentials o Security: trusted credentials
o Security: enable/disable security log o Security: enable/disable security log
Note that this overview is intended simply to be informative and is Note that this overview is intended simply to be informative and is
not normative. If there is any discrepancy between this overview and not normative. If there is any discrepancy between this overview and
the detailed information model definitions in subsequent sections, the detailed information model definitions in subsequent sections,
the error is in this overview. the error is in this overview.
skipping to change at page 5, line 37 skipping to change at page 5, line 33
3.1. Definition of babel-information-obj 3.1. Definition of babel-information-obj
object { object {
string babel-implementation-version; string babel-implementation-version;
boolean babel-enable; boolean babel-enable;
base64 babel-self-router-id; base64 babel-self-router-id;
string babel-supported-link-types<1..*>; string babel-supported-link-types<1..*>;
[int babel-self-seqno;] [int babel-self-seqno;]
string babel-metric-comp-algorithms<1..*>; string babel-metric-comp-algorithms<1..*>;
string babel-security-supported<0..*>;
babel-constants-obj babel-constants; babel-constants-obj babel-constants;
babel-interfaces-obj babel-interfaces<0..*>; babel-interfaces-obj babel-interfaces<0..*>;
babel-routes-obj babel-routes<0..*>; babel-routes-obj babel-routes<0..*>;
[babel-security-obj babel-security;] babel-security-obj babel-security<0..*>;
}babel-information-obj; }babel-information-obj;
babel-implementation-version: the version of this implementation babel-implementation-version: the version of this implementation
of the Babel protocol of the Babel protocol
babel-enable: if true, the babel implementation is running; if babel-enable: if true, the babel implementation is running; if
false, the babel implementation is not currently running; MAY be false, the babel implementation is not currently running; MAY be
configurable to allow babel to be started or stopped configurable to allow babel to be started or stopped
babel-self-router-id: the router-id used by this instance of the babel-self-router-id: the router-id used by this instance of the
Babel protocol to identify itself; draft-ietf-babel-rfc6126bis Babel protocol to identify itself; draft-ietf-babel-rfc6126bis
[rfc6126bis] describes this as an arbitrary string of 8 octets [rfc6126bis] describes this as an arbitrary string of 8 octets
babel-supported-link-types: set of values of supported link types babel-supported-link-types: set of values of supported link types
where the following enumeration values MUST be supported: 1 = where the following enumeration values MUST be supported when
wireless, 2 = physical-layer ethernet, 99 = other applicable: "ethernet", "wireless", "tunnel", and "other"
babel-self-seqno: the current sequence number included in route babel-self-seqno: the current sequence number included in route
updates for routes originated by this node updates for routes originated by this node
babel-metric-comp-algorithms: a set of names of supported cost babel-metric-comp-algorithms: a set of names of supported cost
computation algorithms; possible values include "k-out-of-j", computation algorithms; possible values include "k-out-of-j",
"ETX" "ETX"
babel-constants: a babel-constants object babel-security-supported: list of supported security mechanisms;
as babel security mechanisms are defined, they will need to
indicate what enumeration value is to be used to represent them in
this parameter
babel-interfaces: a set of babel-interface objects babel-constants: a babel-constants-obj object
babel-security: a babel-security object that applies to all babel-interfaces: a set of babel-interface-obj objects
babel-security: a babel-security-obj object that applies to all
interfaces; if this object is implemented, it allows a security interfaces; if this object is implemented, it allows a security
mechanism to be enabled or disabled in a manner that applies to mechanism to be enabled or disabled in a manner that applies to
all Babel messages on all interfaces all Babel messages on all interfaces
babel-sources: a set of babel-source objects babel-routes: a set of babel-route-obj objects; includes received
and routes routes
babel-routes: a set of babel-route objects; includes received and
routes routes
3.2. Definition of babel-constants-obj 3.2. Definition of babel-constants-obj
object { object {
int babel-udp-port; int babel-udp-port;
[ip-address babel-mcast-group-ipv6;] [ip-address babel-mcast-group-ipv6;]
[ip-address babel-mcast-group-ipv4;]
}babel-constants-obj; }babel-constants-obj;
babel-udp-port: UDP port for sending and listening for Babel babel-udp-port: UDP port for sending and listening for Babel
messages; default is 6696; MAY be configurable messages; default is 6696; MAY be configurable
babel-mcast-group-ipv6: multicast group for sending and listening babel-mcast-group-ipv6: multicast group for sending and listening
to multicast announcements on IPv6; default is ff02:0:0:0:0:0:1:6; to multicast announcements on IPv6; default is ff02:0:0:0:0:0:1:6;
MAY be configurable MAY be configurable
babel-mcast-group-ipv4: multicast group for sending and listening
to multicast announcements on IPv4; default is 224.0.0.111; MAY be
configurable
3.3. Definition of babel-interfaces-obj 3.3. Definition of babel-interfaces-obj
object { object {
string babel-interface-reference; string babel-interface-reference;
[boolean babel-interface-enable;] [boolean babel-interface-enable;]
int babel-link-type; int babel-link-type;
[int babel-mcast-hello-seqno;] [int babel-mcast-hello-seqno;]
[int babel-ucast-hello-seqno;] [int babel-ucast-hello-seqno;]
[int babel-mcast-hello-interval;] [int babel-mcast-hello-interval;]
[int babel-ucast-hello-interval;] [int babel-ucast-hello-interval;]
[int babel-update-interval;] [int babel-update-interval;]
[int babel-external-cost;] [int babel-external-cost;]
skipping to change at page 7, line 19 skipping to change at page 7, line 16
[boolean babel-interface-enable;] [boolean babel-interface-enable;]
int babel-link-type; int babel-link-type;
[int babel-mcast-hello-seqno;] [int babel-mcast-hello-seqno;]
[int babel-ucast-hello-seqno;] [int babel-ucast-hello-seqno;]
[int babel-mcast-hello-interval;] [int babel-mcast-hello-interval;]
[int babel-ucast-hello-interval;] [int babel-ucast-hello-interval;]
[int babel-update-interval;] [int babel-update-interval;]
[int babel-external-cost;] [int babel-external-cost;]
[boolean babel-message-log-enable;] [boolean babel-message-log-enable;]
[babel-log-obj babel-message-log<0..*>;] [babel-log-obj babel-message-log<0..*>;]
babel-neighbors-obj babel-neighbors<1..*>; babel-neighbors-obj babel-neighbors<0..*>;
[babel-security-obj babel-interface-security;] [babel-security-obj babel-interface-security<0..*>;]
}babel-interfaces-obj; }babel-interfaces-obj;
babel-interface-reference: reference to an interface object as babel-interface-reference: reference to an interface object as
defined by the data model (e.g., YANG, BBF TR-181); data model is defined by the data model (e.g., YANG, BBF TR-181); data model is
assumed to allow for referencing of interface objects which may be assumed to allow for referencing of interface objects which may be
at any layer (physical, Ethernet MAC, IP, tunneled IP, etc.); at any layer (physical, Ethernet MAC, IP, tunneled IP, etc.);
referencing syntax will be specific to the data model; if there is referencing syntax will be specific to the data model; if there is
no set of interface objects available, this should be a string no set of interface objects available, this should be a string
that indicates the interface name used by the underlying operating that indicates the interface name used by the underlying operating
system system
babel-interface-enable: if true, babel sends and receives messages babel-interface-enable: if true, babel sends and receives messages
on this interface; if false, babel messages received on this on this interface; if false, babel messages received on this
interface are ignored and none are sent; MAY be configurable interface are ignored and none are sent; MAY be configurable
babel-link-type: indicates the type of link; integer values babel-link-type: indicates the type of link; set of values of
specify an enumeration of a supported link type where the supported link types where the following enumeration values MUST
following enumerations MUST be supported: 1 = wireless, 2 = be supported when applicable: "ethernet", "wireless", "tunnel",
physical-layer ethernet, 99 = other; additional values MAY be and "other"; additional values MAY be supported; MAY be
supported; MAY be configurable configurable
babel-mcast-hello-seqno: the current sequence number in use for babel-mcast-hello-seqno: the current sequence number in use for
multicast hellos on this interface multicast hellos sent on this interface
babel-ucast-hello-seqno: the current sequence number in use for babel-ucast-hello-seqno: the current sequence number in use for
unicast hellos on this interface unicast hellos sent on this interface
babel-mcast-hello-interval: the current multicast hello interval babel-mcast-hello-interval: the current multicast hello interval
in use for this interface in use for hellos sent on this interface
babel-ucast-hello-interval: the current unicast hello interval in babel-ucast-hello-interval: the current unicast hello interval in
use for this interface use for hellos sent on this interface
babel-update-interval: the current update interval in use for this babel-update-interval: the current update interval in use for this
interface interface
babel-external-cost: external input to cost of link of this babel-external-cost: external input to cost of link of this
interface (need to determine how to express this);MUST be interface; if supported, this is a value that is added to the
configurable if implemented metrics of routes learned over this interface; how an
implementation uses the value is up to the implementation, which
means the use may not be consistent across implementations; MUST
be configurable if implemented
babel-message-log-enable: if true, logging of babel messages babel-message-log-enable: if true, logging of babel messages
received on this interface is enabled; if false, babel messages received on this interface is enabled; if false, babel messages
are not logged; MUST be configurable, if implemented are not logged; MUST be configurable, if implemented
babel-message-log: log entries that have timestamp of a received babel-message-log: log entries that have timestamp of a received
Babel message and the entire received Babel message, including Babel message and the entire received Babel message (including
Ethernet frame and IP headers; an implementation must restrict the Ethernet frame and IP headers, if possible); an implementation
size of this log, but how and what size is implementation-specific must restrict the size of this log, but how and what size is
implementation-specific
babel-neighbors: a set of babel-neighbors objects babel-neighbors: a set of babel-neighbors-obj objects
babel-interface-security: a babel-security object that applies to babel-interface-security: a babel-security-obj object that applies
this interface; if implemented, this allows security to be enabled to this interface; if implemented, this allows security to be
only on specific interfaces or allows different security enabled only on specific interfaces or allows different security
mechanisms to be enabled on different interfaces mechanisms to be enabled on different interfaces
3.4. Definition of babel-neighbors-obj 3.4. Definition of babel-neighbors-obj
object { object {
ip-address babel-neighbor-address; ip-address babel-neighbor-address;
[string babel-hello-mcast-history;] [string babel-hello-mcast-history;]
[string babel-hello-ucast-history;] [string babel-hello-ucast-history;]
int babel-txcost; int babel-txcost;
int babel-hello-seqno; int babel-exp-mcast-hello-seqno;
int babel-exp-ucast-hello-seqno;
int babel-neighbor-ihu-interval; int babel-neighbor-ihu-interval;
[int babel-rxcost] [int babel-rxcost]
[int babel-cost] [int babel-cost]
}babel-neighbors-obj; }babel-neighbors-obj;
babel-neighbor-address: (IPv4 or v6) address the neighbor sends babel-neighbor-address: (IPv4 or v6) address the neighbor sends
messages from messages from
babel-hello-mcast-history: the multicast Hello history of whether babel-hello-mcast-history: the multicast Hello history of whether
or not each of the 16 multicast Hello messages prior to babel- or not the multicast Hello messages prior to babel-exp-mcast-
hello-seqno was received; represented as a 16 bit (4 hex digits) hello-seqno were received, with a "1" for the most recent Hello
value where 1 = Hello received and 0 = Hello not received; see placed in the most significant bit and prior Hellos shifted right
draft-ietf-babel-rfc6126bis [rfc6126bis] section A.1 (with "0" bits placed between prior Hellos and most recent Hello
for any not-received Hellos); represented as a string using utf-8
encoded hex digits where a "1" bit = Hello received and a "0" bit
= Hello not received; see draft-ietf-babel-rfc6126bis [rfc6126bis]
section A.1
babel-hello-ucast-history: the unicast Hello history of whether or babel-hello-ucast-history: the unicast Hello history of whether or
not each of the 16 unicast Hello messages prior to babel-hello- not the unicast Hello messages prior to babel-exp-ucast-hello-
seqno was received; represented as a 16 bit (4 hex digits) value seqno were received, with a "1" for the most recent Hello placed
where 1 = Hello received and 0 = Hello not received; see draft- in the most significant bit and prior Hellos shifted right (with
ietf-babel-rfc6126bis [rfc6126bis] section A.1 "0" bits placed between prior Hellos and most recent Hello for any
unreceived Hellos); represented as a string using utf-8 encoded
hex digits where a "1" bit = Hello received and a "0" bit = Hello
not received; see draft-ietf-babel-rfc6126bis [rfc6126bis] section
A.1
babel-txcost: transmission cost value from the last IHU packet babel-txcost: transmission cost value from the last IHU packet
received from this neighbor, or maximum value (infinity) to received from this neighbor, or maximum value (infinity) to
indicates the IHU hold timer for this neighbor has expired indicates the IHU hold timer for this neighbor has expired
babel-hello-seqno: expected Hello sequence number babel-exp-mcast-hello-seqno: expected multicast Hello sequence
number of next Hello to be received from this neighbor; if
multicast Hello messages are not expected, or processing of
multicast messages is not enabled, this MUST be 0
babel-exp-ucast-hello-seqno: expected unicast Hello sequence
number of next Hello to be received from this neighbor; if unicast
Hello messages are not expected, or processing of unicast messages
is not enabled, this MUST be 0
babel-neighbor-ihu-interval: current IHU interval for this babel-neighbor-ihu-interval: current IHU interval for this
neighbor neighbor
babel-rxcost: reception cost calculated for this neighbor; this babel-rxcost: reception cost calculated for this neighbor; this
value is usually derived from the Hello history, which may be value is usually derived from the Hello history, which may be
combined with other data, such as statistics maintained by the combined with other data, such as statistics maintained by the
link layer; the rxcost is sent to a neighbour in each IHU link layer; the rxcost is sent to a neighbour in each IHU
babel-cost: link cost is computed from the values maintained in babel-cost: link cost is computed from the values maintained in
skipping to change at page 9, line 27 skipping to change at page 10, line 4
value is usually derived from the Hello history, which may be value is usually derived from the Hello history, which may be
combined with other data, such as statistics maintained by the combined with other data, such as statistics maintained by the
link layer; the rxcost is sent to a neighbour in each IHU link layer; the rxcost is sent to a neighbour in each IHU
babel-cost: link cost is computed from the values maintained in babel-cost: link cost is computed from the values maintained in
the neighbour table: the statistics kept in the neighbour table the neighbour table: the statistics kept in the neighbour table
about the reception of Hellos, and the txcost computed from about the reception of Hellos, and the txcost computed from
received IHU packets received IHU packets
3.5. Definition of babel-security-obj 3.5. Definition of babel-security-obj
object { object {
string babel-security-supported; string babel-security-mechanism
string babel-security-enabled-protocol; boolean babel-security-enable;
babel-credential-obj babel-security-self-cred<1..*>; babel-credential-obj babel-security-self-cred<0..*>;
babel-credential-obj babel-security-trust<1..*>; babel-credential-obj babel-security-trust<0..*>;
[boolean babel-credvalid-log-enable;] [boolean babel-credvalid-log-enable;]
[babel-log-obj babel-credvalid-log<0..*>;] [babel-log-obj babel-credvalid-log<0..*>;]
}babel-security-obj; }babel-security-obj;
babel-security-supported: list of supported security mechanisms babel-security-mechanism: the name of the security mechanism this
object instance is about; the value MUST be the same as one of the
enumerations listed in the babel-security-supported parameter
babel-security-enabled-protocol: the currently enabled security babel-security-enable: if true, the security mechanism is running;
protocol; empty if none is enabled if false, the security mechanism is not currently running; MAY be
configurable to allow security mechanism to be started or stopped
babel-security-self-cred: credentials this router presents to babel-security-self-cred: credentials this router presents to
participate in the enabled security protocol; ; adding and participate in the enabled security mechanism; any private key
component of a credential MUST NOT be readable; adding and
deleting credentials MAY be allowed deleting credentials MAY be allowed
babel-security-trust: a set of babel-credential-obj objects that babel-security-trust: a set of babel-credential-obj objects that
identify the credentials of routers whose babel messages may be identify the credentials of routers whose babel messages may be
trusted or of a certificate authority (CA) whose signing of a trusted or of a certificate authority (CA) whose signing of a
router's credentials implies the router credentials can be router's credentials implies the router credentials can be
trusted; how a security mechanism interacts with this list is trusted, in the context of this security mechanism; how a security
determined by the mechanism; a security algorithm may do mechanism interacts with this list is determined by the mechanism;
additional validation of credentials, such as checking validity a security algorithm may do additional validation of credentials,
dates or revocation lists, so presence may not be sufficient to such as checking validity dates or revocation lists, so presence
determine trust; adding and deleting credentials MAY be allowed in this list may not be sufficient to determine trust; adding and
deleting credentials MAY be allowed
babel-credvalid-log-enable: if true, logging of messages that babel-credvalid-log-enable: if true, logging of messages that
include credentials used for authentication is enabled; if false, include credentials used for authentication is enabled; if false,
these messages are not logged; MUST be configurable, if these messages are not logged; MUST be configurable, if
implemented implemented
babel-credvalid-log: log entries that have the timestamp a message babel-credvalid-log: log entries that have the timestamp a message
containing credentials used for peer authentication (e.g., DTLS containing credentials used for peer authentication (e.g., DTLS
Server Hello) was received on a Babel port, and the entire Server Hello) was received on a Babel port, and the entire
received message (including Ethernet frame and IP headers); an received message (including Ethernet frame and IP headers, if
implementation must restrict the size of this log, but how and possible); an implementation must restrict the size of this log,
what size is implementation-specific but how and what size is implementation-specific
3.6. Definition of babel-routes-obj 3.6. Definition of babel-routes-obj
object { object {
ip-address babel-route-prefix; ip-address babel-route-prefix;
int babel-route-prefix-length; int babel-route-prefix-length;
base64 babel-route-router-id; base64 babel-route-router-id;
[int babel-route-metric;] string babel-route-neighbor;
[int babel-route-announced-metric;] [int babel-route-received-metric;]
[int babel-route-calculated-metric;]
int babel-route-seqno; int babel-route-seqno;
ip-address babel-route-next-hop; ip-address babel-route-next-hop;
boolean babel-route-feasible; boolean babel-route-feasible;
boolean babel-route-selected; boolean babel-route-selected;
}babel-routes-obj; }babel-routes-obj;
babel-route-prefix: Prefix (expressed in IP address format) for babel-route-prefix: Prefix (expressed in IP address format) for
which this route is advertised which this route is advertised
babel-route-prefix-length: Length of the prefix for which this babel-route-prefix-length: Length of the prefix for which this
route is advertised route is advertised
babel-route-router-id: router-id of the source router for which babel-route-router-id: router-id of the source router for which
this route is advertised this route is advertised
babel-route-metric: the metric with which this route was babel-route-neighbor: reference to the babel-neighbors entry for
the neighbor that advertised this route
babel-route-received-metric: the metric with which this route was
advertised by the neighbor, or maximum value (infinity) to advertised by the neighbor, or maximum value (infinity) to
indicate a recently retracted route; this metric will be 0 (zero) indicate a the route was recently retracted and is temporarily
if the route was not received from a neighbor but was generated unreachable (see Section 3.5.5 of draft-ietf-babel-rfc6126bis
through other means; either babel-route-announced-metric or babel- [rfc6126bis]); this metric will be 0 (zero) if the route was not
route-metric MUST be provided received from a neighbor but was generated through other means;
either babel-route-calculated-metric or babel-route-received-
metric MUST be provided
babel-route-announced-metric: a calculated metric for this route; babel-route-calculated-metric: a calculated metric for this route;
how the metric is calculated is implementation-specific; either how the metric is calculated is implementation-specific; maximum
babel-route-announced-metric or babel-route-metric MUST be value (infinity) indicates the route was recently retracted and is
provided temporarily unreachable (see Section 3.5.5 of draft-ietf-babel-
rfc6126bis [rfc6126bis]); either babel-route-calculated-metric or
babel-route-received-metric MUST be provided
babel-route-seqno: the sequence number with which this route was babel-route-seqno: the sequence number with which this route was
advertised advertised
babel-route-next-hop: the next-hop address of this route; this babel-route-next-hop: the next-hop address of this route; this
will be empty if this route has no next-hop address will be empty if this route has no next-hop address
babel-route-feasible: a boolean flag indicating whether this route babel-route-feasible: a boolean flag indicating whether this route
is known to work; a route that is not feasible will never be is feasible, as defined in Section 3.5.1 of draft-ietf-babel-
selected rfc6126bis [rfc6126bis])
babel-route-selected: a boolean flag indicating whether this route babel-route-selected: a boolean flag indicating whether this route
is selected, i.e., whether it is currently being used for is selected, i.e., whether it is currently being used for
forwarding and is being advertised forwarding and is being advertised
4. Common Objects 4. Common Objects
4.1. Definition of babel-credential-obj 4.1. Definition of babel-credential-obj
object { object {
credentials babel-cred; credentials babel-cred;
}babel-credential-obj; }babel-credential-obj;
babel-cred: a credential, such as an X.509 certificate, a public babel-cred: a credential, such as an X.509 certificate, a public
key, etc. used for signing and/or encrypting babel messages key, etc. used for signing and/or encrypting babel messages
4.2. Definition of babel-log-obj 4.2. Definition of babel-log-obj
object { object {
datetime babel-log-time; datetime babel-log-time;
string babel-log-entry; string babel-log-entry;
skipping to change at page 12, line 5 skipping to change at page 12, line 44
babel-log-entry: the logged message, as a string of utf-8 encoded babel-log-entry: the logged message, as a string of utf-8 encoded
hex characters hex characters
5. Extending the Information Model 5. Extending the Information Model
Implementations MAY extend this information model with other Implementations MAY extend this information model with other
parameters or objects. For example, an implementation MAY choose to parameters or objects. For example, an implementation MAY choose to
expose babel route filtering rules by adding a route filtering object expose babel route filtering rules by adding a route filtering object
with parameters appropriate to how route filtering is done in that with parameters appropriate to how route filtering is done in that
implementation. The precises means used to extend the information implementation. The precise means used to extend the information
model would be specific to the data model the implementation uses to model would be specific to the data model the implementation uses to
expose this information. expose this information.
6. Security Considerations 6. Security Considerations
This document defines a set of information model objects and This document defines a set of information model objects and
parameters that may be exposed to be visible from other devices, and parameters that may be exposed to be visible from other devices, and
some of which may be configured. Any mechanism or protocol that is some of which may be configured. Any mechanism or protocol that is
used to transmit this information or allow for its configuration is used to transmit this information or allow for its configuration is
also responsible for ensuring this is done so in a secure manner. also responsible for ensuring this is done so in a secure manner.
This information model defines objects that can allow credentials
(for this device, for trusted devices, and for trusted certificate
authorities) to be added and deleted. Public keys and shared secrets
may be exposed through this model. This model requires that private
keys never be exposed. The Babel security mechanisms that make use
of these credentials are not defined or identified in this model.
7. IANA Considerations 7. IANA Considerations
This document makes no IANA requests. This document makes no IANA requests.
8. Acknowledgements 8. Acknowledgements
Juliusz Chroboczek's review has been very helpful in refining this Juliusz Chroboczek, Toke Hoeiland-Joergensen, and David Schinazi have
information model. been very helpful in refining this information model.
The language in the Notation section was mostly taken from RFC 8193 The language in the Notation section was mostly taken from RFC 8193
[RFC8193]. [RFC8193].
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[rfc6126bis] [rfc6126bis]
Chroboczek, J., "The Babel Routing Protocol", Work in Chroboczek, J., "The Babel Routing Protocol", Work in
Progress, draft-ietf-babel-rfc6126bis, October 2017. Progress, draft-ietf-babel-rfc6126bis, October 2017.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
9.2. Informative References 9.2. Informative References
[BABEL-DTLS] [BABEL-DTLS]
Schinazi, D., "TBD", Work in Progress, rfc6347, March Schinazi, D., "TBD", Work in Progress, rfc6347, March
2018. 2018.
[BABEL-HMAC] [BABEL-HMAC]
Ovsienko, D., "Babel HMAC Cryptographic Authentication", Ovsienko, D., "Babel HMAC Cryptographic Authentication",
Work in Progress, draft-ovsienko-babel-rfc7298bis, March Work in Progress, draft-ovsienko-babel-rfc7298bis, March
2018. 2018.
skipping to change at page 13, line 37 skipping to change at page 14, line 48
DOI 10.17487/RFC8193, August 2017, DOI 10.17487/RFC8193, August 2017,
<https://www.rfc-editor.org/info/rfc8193>. <https://www.rfc-editor.org/info/rfc8193>.
Appendix A. Open Issues Appendix A. Open Issues
This draft must be reviewed against draft-ietf-babel-rfc6126bis. [I This draft must be reviewed against draft-ietf-babel-rfc6126bis. [I
feel like this has been adequately done, but I could be wrong.] feel like this has been adequately done, but I could be wrong.]
Following are some issues where a conscious decision may be useful: Following are some issues where a conscious decision may be useful:
1. babel-interfaces-obj: Juliusz:"This needs further discussion, I 1. babel-interfaces-obj: Juliusz:"This needs further discussion, I
fear some of these are implementation details." [In the absence fear some of these are implementation details." [In the absence
of discussion, the current model stands. Note that all but of discussion, the current model stands. Note that all but link-
link-type and the neighbors sub-object are optional; if an type and the neighbors sub-object are optional; if an
implementation does not have any of the optional elements then implementation does not have any of the optional elements then it
it simply doesn't have them and that's fine.] simply doesn't have them and that's fine.]
2. Would it be useful to define some parameters for reporting
statistics or logs? [2 logs are now included. If others are
needed they need to be proposed.]
3. Would it be useful to define some parameters specifically for 2. Would it be useful to define some parameters for reporting
security anomalies? [The 2 logs should be useful in identifying statistics or logs? [2 logs are now included. If others are
security anomalies. If more is needed, someone needs to needed they need to be proposed.]
propose.]
4. I created a basic security model. It's useful for single (or 3. Would it be useful to define some parameters specifically for
no) active security mechanism (e.g., just HMAC, just DTLS, or security anomalies? [The 2 logs should be useful in identifying
neither); but not multiple active (both HMAC and DTLS -- which security anomalies. If more is needed, someone needs to
is not the same as HMAC of DTLS and would just mean that HMAC propose.]
would be used on all unencrypted messages -- but right now the
model doesn't allow for configuring HMAC of unencrypted messages
for routers without DTLS, while DTLS is used if possible). OK?
5. Do we need a registry for the supported security mechanisms? 4. I created a basic security model. It's useful for single (or no)
[Given the current limited set, and unlikelihood of massive active security mechanism (e.g., just HMAC, just DTLS, or
expansion, I don't think so. But we can if someone wants it.] neither); but not multiple active (both HMAC and DTLS -- which is
not the same as HMAC of DTLS and would just mean that HMAC would
be used on all unencrypted messages -- but right now the model
doesn't allow for configuring HMAC of unencrypted messages for
routers without DTLS, while DTLS is used if possible). OK?
6. babel-external-cost may need more work. [if no comment, it will 5. babel-external-cost may need more work. [if no comment, it will
be left as is] be left as is]
7. babel-hello-[mu]cast-history: the Hello history is formated as 6. babel-hello-[mu]cast-history: the Hello history is formated as 16
16 bits, per A.1 of 6126bis. Is that a too implementation bits, per A.1 of 6126bis. Is that a too implementation specific?
specific? [We also now have an optional-to-implement log of [We also now have an optional-to-implement log of received
received messages, and I made these optional. So maybe this is messages, and I made these optional. So maybe this is ok?]
ok?]
8. rxcost, txcost, cost: is it ok to model as integers, since 7. rxcost, txcost, cost: is it ok to model as integers, since
6126bis 2.1 says costs and metrics need not be integers. [I 6126bis 2.1 says costs and metrics need not be integers. [I have
have them as integers unless someone insists on something else.] them as integers unless someone insists on something else.]
9. Should babel link types have an IANA registry? [Right now, none 8. Should babel link types have an IANA registry? [Right now, none
is defined.] is defined.]
10. For the security log, should it also log whether the credentials 9. For the security log, should it also log whether the credentials
were considered ok? [Right now it doesn't and I think that's ok were considered ok? [Right now it doesn't and I think that's ok
because if you log Hellos it was ok and if you don't it wasn't.] because if you log Hellos it was ok and if you don't it wasn't.]
Closed Issues: Closed Issues:
Closed by defining base64 type and using it for all router IDs: Closed by defining base64 type and using it for all router IDs:
"babel-self-router-id: Should this be an opaque 64-bit value "babel-self-router-id: Should this be an opaque 64-bit value
instead of int?" instead of int?"
Closed as "No": Do we need a registry for the supported security
mechanisms? [Given the current limited set, and unlikelihood of
massive expansion, I don't think so. But we can if someone wants
it.]
Appendix B. Change Log Appendix B. Change Log
Individual Drafts: Individual Drafts:
v00 2016-07-07 EBD Initial individual draft version v00 2016-07-07 EBD Initial individual draft version
v01 2017-03-13 Addressed comments received in 2016-07-15 email v01 2017-03-13 Addressed comments received in 2016-07-15 email
from J. Chroboczek from J. Chroboczek
Working group drafts: Working group drafts:
v00 2017-07-03 Addressed points noted with "oops" in v00 2017-07-03 Addressed points noted with "oops" in
https://www.ietf.org/proceedings/98/slides/slides-98-babel-babel- https://www.ietf.org/proceedings/98/slides/slides-98-babel-babel-
information-model-00.pdf information-model-00.pdf
v01 2018-01-02 Removed item from issue list that was agreed (in v01 2018-01-02 Removed item from issue list that was agreed (in
Prague) not to be an issue. Added description of data types under Prague) not to be an issue. Added description of data types under
Notation section, and used these in all data types. Added babel- Notation section, and used these in all data types. Added babel-
security and babel-trust. security and babel-trust.
v02 2018-mm-dd v02 2018-04-05
- changed babel-version description to babel-implementation- - changed babel-version description to babel-implementation-
version version
- replace optional babel-interface-seqno with optional babel- - replace optional babel-interface-seqno with optional babel-
mcast-hello-seqno and babel-ucast-hello-seqno mcast-hello-seqno and babel-ucast-hello-seqno
- replace optional babel-interface-hello-interval with optional - replace optional babel-interface-hello-interval with optional
babel-mcast-hello-interval and babel-ucast-hello-interval babel-mcast-hello-interval and babel-ucast-hello-interval
skipping to change at page 16, line 15 skipping to change at page 17, line 30
- added section to briefly describe extending the information - added section to briefly describe extending the information
model. model.
- deleted babel-route-neighbor - deleted babel-route-neighbor
- tried to make definition of babel-interface-reference clearer - tried to make definition of babel-interface-reference clearer
- added security and message logs - added security and message logs
v03 2018-05-31
- added reference to RFC 8174 (update to RFC 2119 on key words)
- applied edits to Introduction text per Juliusz email of
2018-04-06
- Deleted sentence in definition of "int" data type that said
it was also used for enumerations. Changed all enumerations to
strings. The only enumerations were for link types, which are
now "ethernet", "wireless", "tunnel", and "other".
- deleted [ip-address babel-mcast-group-ipv4;]
- babel-external-cost description changed
- babel-security-self-cred: Added "any private key component of
a credential MUST NOT be readable;"
- hello-history parameters put recent Hello in most significant
bit and length of parameter is not constrained.
- babel-hello-seqno in neighbors-obj changed to babel-exp-
mcast-hello-seqno and babel-exp-ucast-hello-seqno
- added babel-route-neighbor back again; it was mistakenly
deleted
- changed babel-route-metric and babel-route-announced-metric
to babel-route-received-metric and babel-route-calculated-
metric
- changed model of security object to put list of supported
mechanisms at top level and separate security object per
mechanism; this caused some other changes to the security
object
Author's Address Author's Address
Barbara Stark Barbara Stark
AT&T AT&T
Atlanta, GA Atlanta, GA
US US
Email: barbara.stark@att.com Email: barbara.stark@att.com
 End of changes. 70 change blocks. 
162 lines changed or deleted 236 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/