draft-ietf-babel-information-model-01.txt   draft-ietf-babel-information-model-02.txt 
Babel routing protocol B. Stark Babel routing protocol B. Stark
Internet-Draft AT&T Internet-Draft AT&T
Intended status: Informational January 2, 2018 Intended status: Informational April 5, 2018
Expires: July 6, 2018 Expires: October 7, 2018
Babel Information Model Babel Information Model
draft-ietf-babel-information-model-01 draft-ietf-babel-information-model-02
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 July 6, 2018. This Internet-Draft will expire on October 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 10 skipping to change at page 2, line 10
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. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
1.2. Notation . . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Notation . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Information Model . . . . . . . . . . . . . . . . . . . . 4 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Definition of babel-information . . . . . . . . . . . . . 4 3. The Information Model . . . . . . . . . . . . . . . . . . . . 5
2.2. Definition of babel-constants . . . . . . . . . . . . . . 4 3.1. Definition of babel-information-obj . . . . . . . . . . . 5
2.3. Definition of babel-interfaces . . . . . . . . . . . . . 5 3.2. Definition of babel-constants-obj . . . . . . . . . . . . 6
2.4. Definition of babel-neighbors . . . . . . . . . . . . . . 6 3.3. Definition of babel-interfaces-obj . . . . . . . . . . . 7
2.5. Definition of babel-security . . . . . . . . . . . . . . 6 3.4. Definition of babel-neighbors-obj . . . . . . . . . . . . 8
2.6. Definition of babel-trust . . . . . . . . . . . . . . . . 7 3.5. Definition of babel-security-obj . . . . . . . . . . . . 9
2.7. Definition of babel-sources . . . . . . . . . . . . . . . 7 3.6. Definition of babel-routes-obj . . . . . . . . . . . . . 10
2.8. Definition of babel-routes . . . . . . . . . . . . . . . 7 4. Common Objects . . . . . . . . . . . . . . . . . . . . . . . 11
3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 4.1. Definition of babel-credential-obj . . . . . . . . . . . 11
4. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.2. Definition of babel-log-obj . . . . . . . . . . . . . . . 11
4.1. Normative References . . . . . . . . . . . . . . . . . . 9 5. Extending the Information Model . . . . . . . . . . . . . . . 11
4.2. Informative References . . . . . . . . . . . . . . . . . 9 6. Security Considerations . . . . . . . . . . . . . . . . . . . 12
Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . 10 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
9.1. Normative References . . . . . . . . . . . . . . . . . . 12
9.2. Informative References . . . . . . . . . . . . . . . . . 12
Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . 13
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 14
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 16
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
RFC 6126bis [RFC6126bis]. Babel Hashed Message Authentication Code draft-ietf-babel-rfc6126bis [rfc6126bis]. draft-babel-7298bis
(HMAC) Cryptographic Authentication, defined in RFC 7298 [RFC7298], [BABEL-HMAC] defines a security mechanism that allows Babel messages
describes a cryptographic authentication mechanism for the Babel to be cryptographically authenticated, and draft-babel-dtls
routing protocol. This document describes an information model for [BABEL-DTLS] defines a security mechanism that allows Babel messages
Babel (including HMAC) that can be used to created management to encrypted. This document describes an information model for Babel
protocol data models (such as a netconf [RFC6241] YANG data model). (including implementations using one of these security mechanisms)
Other Babel extensions may be included in this document when they that can be used to created management protocol data models (such as
become working group drafts. 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 and the fact that it is
designed to be used in non-professionally administered environments designed to be used in non-professionally administered environments
(such as home networks), most of the information model is focused on (such as home networks), most of the information model is focused on
reporting status of the Babel protocol, and very little of that is reporting status of the Babel protocol, and very little of that is
considered mandatory to implement (conditional on a management considered mandatory to implement (conditional on a management
protocol with Babel support being implemented). Some parameters may protocol with Babel support being implemented). Some parameters may
be configurable; however, it is up to the Babel implementation be configurable; however, it is up to the Babel implementation
whether to allow any of these to be configured within its whether to allow any of these to be configured within its
implementation. Where the implementation does not allow 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.
This does not preclude a data model based on this Information Model
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].
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
skipping to change at page 4, line 8 skipping to change at page 4, line 15
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. The Information Model 2. Overview
2.1. Definition of babel-information The Information Model is hierarchically structured as follows:
information object
includes implementation version, router id, this node seqno,
enable flag parameters
constants object (exactly one per information object)
includes UDP port and optional multicast and unicast groups
parameters
interfaces object
includes interface reference, Hello seqno and intervals,
update interval, link type, external cost parameters
neighbors object
includes neighbor IP address, Hello history, cost
parameters
security object (per interface)
includes supported and enabled security mechanisms, self
credentials (credential object), trusted credentials
(credential object)
security object (common to all interfaces)
includes supported and enabled security mechanisms, self
credentials (credential object), trusted credentials
(credential object)
routes object
includes route prefix, source router, reference to
advertising neighbor, metric, sequence number, whether
route is feasible, whether route is selected
Following is a list of the data elements that an implementation can
choose to allow to be configurable:
o enable/disable babel
o Constant: UDP port
o Constant: IPv6 multicast group
o Constant: IPv4 multicast group
o Interface: Link type
o Interface: External cost (must be configurable if implemented, but
implementation is optional)
o Interface: enable/disable babel on this interface
o Interface: enable/disable message log
o Security: self credentials
o Security: trusted credentials
o Security: enable/disable security log
Note that this overview is intended simply to be informative and is
not normative. If there is any discrepancy between this overview and
the detailed information model definitions in subsequent sections,
the error is in this overview.
3. The Information Model
3.1. Definition of babel-information-obj
object { object {
string babel-implementation-version; string babel-implementation-version;
boolean babel-enable;
base64 babel-self-router-id; base64 babel-self-router-id;
string babel-supported-link-types<1..*>;
[int babel-self-seqno;] [int babel-self-seqno;]
string babel-cost-comp-algorithms<1..*>; string babel-metric-comp-algorithms<1..*>;
babel-constants-obj babel-constants; babel-constants-obj babel-constants;
babel-interfaces-obj babel-interfaces<0..*>; babel-interfaces-obj babel-interfaces<0..*>;
babel-sources-obj babel-sources<0..*>;
babel-routes-obj babel-routes<0..*>; babel-routes-obj babel-routes<0..*>;
[babel-security-obj babel-security;]
}babel-information-obj; }babel-information-obj;
babel-version: the version of this implementation of the Babel babel-implementation-version: the version of this implementation
protocol of the Babel protocol
babel-enable: if true, the babel implementation is running; if
false, the babel implementation is not currently running; MAY be
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; RFC 6126bis [RFC6126bis] Babel protocol to identify itself; draft-ietf-babel-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
where the following enumeration values MUST be supported: 1 =
wireless, 2 = physical-layer ethernet, 99 = 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-cost-comp-algorithm: 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-constants: a babel-constants object
babel-interfaces: a set of babel-interface objects babel-interfaces: a set of babel-interface objects
babel-security: a babel-security object that applies to all
interfaces; if this object is implemented, it allows a security
mechanism to be enabled or disabled in a manner that applies to
all Babel messages on all interfaces
babel-sources: a set of babel-source objects babel-sources: a set of babel-source objects
babel-routes: a set of babel-route objects babel-routes: a set of babel-route objects; includes received and
routes routes
2.2. Definition of babel-constants 3.2. Definition of babel-constants-obj
object { object {
int babel-udp-port; int babel-udp-port;
[ip-address babel-multicast-group-ipv6;] [ip-address babel-mcast-group-ipv6;]
[ip-address babel-multicast-group-ipv4;] [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-multicast-group-ipv6: multicast group for sending and babel-mcast-group-ipv6: multicast group for sending and listening
listening to multicast announcements on IPv6; default is to multicast announcements on IPv6; default is ff02:0:0:0:0:0:1:6;
ff02:0:0:0:0:0:1:6; MAY be configurable MAY be configurable
babel-multicast-group-ipv4: multicast group for sending and babel-mcast-group-ipv4: multicast group for sending and listening
listening to multicast announcements on IPv4; default is to multicast announcements on IPv4; default is 224.0.0.111; MAY be
224.0.0.111; MAY be configurable configurable
2.3. Definition of babel-interfaces 3.3. Definition of babel-interfaces-obj
object { object {
uri babel-interface-reference; string babel-interface-reference;
[int babel-interface-seqno;] [boolean babel-interface-enable;]
[int babel-interface-hello-interval;] int babel-link-type;
[int babel-interface-update-interval;] [int babel-mcast-hello-seqno;]
boolean babel-request-trigger-ack; [int babel-ucast-hello-seqno;]
boolean babel-lossy-link; [int babel-mcast-hello-interval;]
[int babel-ucast-hello-interval;]
[int babel-update-interval;]
[int babel-external-cost;] [int babel-external-cost;]
[boolean babel-message-log-enable;]
[babel-log-obj babel-message-log<0..*>;]
babel-neighbors-obj babel-neighbors<1..*>; babel-neighbors-obj babel-neighbors<1..*>;
[babel-security-obj babel-security<1..*>;] [babel-security-obj babel-interface-security;]
}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 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
at any layer (physical, Ethernet MAC, IP, tunneled IP, etc.);
referencing syntax will be specific to the data model; if there is
no set of interface objects available, this should be a string
that indicates the interface name used by the underlying operating
system
babel-interface-seqno: the current sequence number in use for this babel-interface-enable: if true, babel sends and receives messages
interface on this interface; if false, babel messages received on this
interface are ignored and none are sent; MAY be configurable
babel-interface-hello-interval: the current hello interval in use babel-link-type: indicates the type of link; integer values
for this interface specify an enumeration of a supported link type where the
following enumerations MUST be supported: 1 = wireless, 2 =
physical-layer ethernet, 99 = other; additional values MAY be
supported; MAY be configurable
babel-interface-update-interval: the current update interval in babel-mcast-hello-seqno: the current sequence number in use for
use for this interface multicast hellos on this interface
babel-request-trigger-ack: requests acknowledgement of triggered babel-ucast-hello-seqno: the current sequence number in use for
updates (if number of neighbors less than babel-ack-limit); MAY be unicast hellos on this interface
configurable
babel-lossy-link: indicates (if true) that the link of this babel-mcast-hello-interval: the current multicast hello interval
interface is considered lossy; MAY be configurable in use for this interface
babel-ucast-hello-interval: the current unicast hello interval in
use for this interface
babel-update-interval: the current update interval in use for this
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 (need to determine how to express this);MUST be
configurable if implemented configurable if implemented
2.4. Definition of babel-neighbors babel-message-log-enable: if true, logging of babel messages
received on this interface is enabled; if false, babel messages
are not logged; MUST be configurable, if implemented
babel-message-log: log entries that have timestamp of a received
Babel message and the entire received Babel message, including
Ethernet frame and IP headers; an implementation must restrict the
size of this log, but how and what size is implementation-specific
babel-neighbors: a set of babel-neighbors objects
babel-interface-security: a babel-security object that applies to
this interface; if implemented, this allows security to be enabled
only on specific interfaces or allows different security
mechanisms to be enabled on different interfaces
3.4. Definition of babel-neighbors-obj
object { object {
ip-address babel-neighbor-address; ip-address babel-neighbor-address;
string babel-hello-history; [string babel-hello-mcast-history;]
[string babel-hello-ucast-history;]
int babel-txcost; int babel-txcost;
int babel-hello-seqno; int babel-hello-seqno;
int babel-neighbor-ihu-interval; int babel-neighbor-ihu-interval;
[int babel-rxcost] [int babel-rxcost]
[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-history: the Hello history (do we want a human babel-hello-mcast-history: the multicast Hello history of whether
readable format?) or not each of the 16 multicast Hello messages prior to babel-
hello-seqno was received; represented as a 16 bit (4 hex digits)
value where 1 = Hello received and 0 = Hello not received; see
draft-ietf-babel-rfc6126bis [rfc6126bis] section A.1
babel-hello-ucast-history: the unicast Hello history of whether or
not each of the 16 unicast Hello messages prior to babel-hello-
seqno was received; represented as a 16 bit (4 hex digits) value
where 1 = Hello received and 0 = 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 meximum 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-hello-seqno: expected Hello sequence number
babel-neighbor-ihu-interval: current IHU interval for this babel-neighbor-ihu-interval: current IHU interval for this
neighbor neighbor
babel-router-id: router-id of the neighbor babel-rxcost: reception cost calculated for this neighbor; this
value is usually derived from the Hello history, which may be
combined with other data, such as statistics maintained by the
link layer; the rxcost is sent to a neighbour in each IHU
babel-rxcost: reception cost calculated for this neighbor babel-cost: link cost is computed from the values maintained in
the neighbour table: the statistics kept in the neighbour table
about the reception of Hellos, and the txcost computed from
received IHU packets
2.5. Definition of babel-security 3.5. Definition of babel-security-obj
object { object {
string babel-security-supported; string babel-security-supported;
string babel-security-enabled-protocol; string babel-security-enabled-protocol;
credentials babel-security-self-cred; babel-credential-obj babel-security-self-cred<1..*>;
babel-trust-obj babel-trust<1..*>; babel-credential-obj babel-security-trust<1..*>;
}babel-security-obj; [boolean babel-credvalid-log-enable;]
[babel-log-obj babel-credvalid-log<0..*>;]
}babel-security-obj;
babel-security-supported: list of supported security mechanisms babel-security-supported: list of supported security mechanisms
babel-security-enabled-protocol: the currently enabled security babel-security-enabled-protocol: the currently enabled security
protocol; empty if none is enabled protocol; empty if none is enabled
babel-security-self-cred: the credentials this router presents to babel-security-self-cred: credentials this router presents to
participate in the enabled security protocol participate in the enabled security protocol; ; adding and
babel-trust-obj: a set of babel-trust objects that identify the deleting credentials MAY be allowed
credentials of a router whose babel messages are trusted
2.6. Definition of babel-trust
object {
credentials babel-trust-cred;
}babel-trust-obj;
babel-trust-cred: the credentials of a router whose babel messages
can be trusted
2.7. Definition of babel-sources
object {
ip-address babel-source-prefix;
int babel-source-prefix-length;
base64 babel-source-router-id;
int babel-source-seqno;
int babel-source-metric;
[int babel-source-garbage-collection-time;]
}babel-sources-obj;
babel-source-prefix: Prefix this entry applies to
babel-source-prefix-length: Length of the source prefix
babel-source-router-id: router-id of the router originating this babel-security-trust: a set of babel-credential-obj objects that
prefix identify the credentials of routers whose babel messages may be
trusted or of a certificate authority (CA) whose signing of a
router's credentials implies the router credentials can be
trusted; 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 may not be sufficient to
determine trust; adding and deleting credentials MAY be allowed
babel-source-seqno: last sequence number used by this source babel-credvalid-log-enable: if true, logging of messages that
include credentials used for authentication is enabled; if false,
these messages are not logged; MUST be configurable, if
implemented
babel-source-metric: this source's feasibility distance babel-credvalid-log: log entries that have the timestamp a message
containing credentials used for peer authentication (e.g., DTLS
Server Hello) was received on a Babel port, and the entire
received message (including Ethernet frame and IP headers); an
implementation must restrict the size of this log, but how and
what size is implementation-specific
babel-source-garbage-collection-time: garbage-collection timer for 3.6. Definition of babel-routes-obj
this source
2.8. Definition of babel-routes
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;
base64 babel-route-neighbor; [int babel-route-metric;]
int babel-route-metric; [int babel-route-announced-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-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-neighbor: neighbor that advertised this route (a
router-id)
babel-route-metric: the metric with which this route was babel-route-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 indicate a recently retracted route; this metric will be 0 (zero)
if the route was not received from a neighbor but was generated
through other means; either babel-route-announced-metric or babel-
route-metric MUST be provided
babel-route-announced-metric: a calculated metric for this route;
how the metric is calculated is implementation-specific; either
babel-route-announced-metric or babel-route-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 babel-route-next-hop: the next-hop address of this route; this
will be empty if this route has no next-hop address
babel-route-feasible: a boolean flag indicating whether this route
is known to work; a route that is not feasible will never be
selected
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
3. Acknowledgements 4. Common Objects
Juliusz Chroboczek review has been very helpful in refining this 4.1. Definition of babel-credential-obj
object {
credentials babel-cred;
}babel-credential-obj;
babel-cred: a credential, such as an X.509 certificate, a public
key, etc. used for signing and/or encrypting babel messages
4.2. Definition of babel-log-obj
object {
datetime babel-log-time;
string babel-log-entry;
}babel-log-obj;
babel-log-time: 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
babel-log-entry: the logged message, as a string of utf-8 encoded
hex characters
5. Extending the Information Model
Implementations MAY extend this information model with other
parameters or objects. For example, an implementation MAY choose to
expose babel route filtering rules by adding a route filtering object
with parameters appropriate to how route filtering is done in that
implementation. The precises means used to extend the information
model would be specific to the data model the implementation uses to
expose this information.
6. Security Considerations
This document defines a set of information model objects 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
used to transmit this information or allow for its configuration is
also responsible for ensuring this is done so in a secure manner.
7. IANA Considerations
This document makes no IANA requests.
8. Acknowledgements
Juliusz Chroboczek's review has been very helpful in refining this
information model. 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].
4. References 9. References
4.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.
4.2. Informative References 9.2. Informative References
[BABEL-DTLS]
Schinazi, D., "TBD", Work in Progress, rfc6347, March
2018.
[BABEL-HMAC]
Ovsienko, D., "Babel HMAC Cryptographic Authentication",
Work in Progress, draft-ovsienko-babel-rfc7298bis, March
2018.
[ISO.10646] [ISO.10646]
International Organization for Standardization, International Organization for Standardization,
"Information Technology - Universal Multiple-Octet Coded "Information Technology - Universal Multiple-Octet Coded
Character Set (UCS)", ISO Standard 10646:2014, 2014. Character Set (UCS)", ISO Standard 10646:2014, 2014.
[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet:
Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002,
<https://www.rfc-editor.org/info/rfc3339>. <https://www.rfc-editor.org/info/rfc3339>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, DOI 10.17487/RFC3986, January 2005, RFC 3986, DOI 10.17487/RFC3986, January 2005,
<https://www.rfc-editor.org/info/rfc3986>. <https://www.rfc-editor.org/info/rfc3986>.
[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>.
[RFC7298] Ovsienko, D., "Babel Hashed Message Authentication Code
(HMAC) Cryptographic Authentication", RFC 7298,
DOI 10.17487/RFC7298, July 2014,
<https://www.rfc-editor.org/info/rfc7298>.
[RFC8193] Burbridge, T., Eardley, P., Bagnulo, M., and J. [RFC8193] Burbridge, T., Eardley, P., Bagnulo, M., and J.
Schoenwaelder, "Information Model for Large-Scale Schoenwaelder, "Information Model for Large-Scale
Measurement Platforms (LMAPs)", RFC 8193, Measurement Platforms (LMAPs)", RFC 8193,
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. This draft must be reviewed against draft-ietf-babel-rfc6126bis. [I
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
fear some of these are implementation details." [In the absence
of discussion, the current model stands. Note that all but
link-type and the neighbors sub-object are optional; if an
implementation does not have any of the optional elements then
it 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
security anomalies? [The 2 logs should be useful in identifying
security anomalies. If more is needed, someone needs to
propose.]
4. I created a basic security model. It's useful for single (or
no) active security mechanism (e.g., just HMAC, just DTLS, or
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?
5. 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.]
6. babel-external-cost may need more work. [if no comment, it will
be left as is]
7. babel-hello-[mu]cast-history: the Hello history is formated as
16 bits, per A.1 of 6126bis. Is that a too implementation
specific? [We also now have an optional-to-implement log of
received messages, and I made these optional. So maybe this is
ok?]
8. rxcost, txcost, cost: is it ok to model as integers, since
6126bis 2.1 says costs and metrics need not be integers. [I
have them as integers unless someone insists on something else.]
9. Should babel link types have an IANA registry? [Right now, none
is defined.]
10. 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
because if you log Hellos it was ok and if you don't it wasn't.]
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?"
babel-interfaces-obj: "This needs further discussion, I fear some Appendix B. Change Log
of these are implementation details."
Would it be useful to define some parameters for reporting Individual Drafts:
statistics or logs? [Yes, but these need to be proposed.]
Would it be useful to define some parameters specifically for v00 2016-07-07 EBD Initial individual draft version
security anomalies? [Yes, but these need to be proposed.]
I created a basic security model. It's useful for single (or no) v01 2017-03-13 Addressed comments received in 2016-07-15 email
active security mechanism; but not multiple active. OK? from J. Chroboczek
Do we need a registry for the supported security mechanisms? Working group drafts:
v00 2017-07-03 Addressed points noted with "oops" in
https://www.ietf.org/proceedings/98/slides/slides-98-babel-babel-
information-model-00.pdf
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
Notation section, and used these in all data types. Added babel-
security and babel-trust.
v02 2018-mm-dd
- changed babel-version description to babel-implementation-
version
- replace optional babel-interface-seqno with optional babel-
mcast-hello-seqno and babel-ucast-hello-seqno
- replace optional babel-interface-hello-interval with optional
babel-mcast-hello-interval and babel-ucast-hello-interval
- remove babel-request-trigger-ack
- remove "babel-router-id: router-id of the neighbor"; note
that parameter had previously been removed but description had
accidentally not been removed
- added an optional "babel-cost" field to babel-neighbors
object, since the spec does not define how exactly the cost is
computed from rxcost/txcost
- deleted babel-source-garbage-collection-time
- change babel-lossy-link to babel-link-type and make this an
enumeration; added at top level babel-supported-link-types so
which are supported by this implementation can be reported
- changes to babel-security-obj to allow self credentials to be
one or more instances of a credential object; allowed trusted
credentials to include CA credentials; made some parameter name
changes
- updated references and Introduction
- added Overview section
- deleted babel-sources-obj
- added feasible Boolean to routes
- added section to briefly describe extending the information
model.
- deleted babel-route-neighbor
- tried to make definition of babel-interface-reference clearer
- added security and message logs
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. 67 change blocks. 
140 lines changed or deleted 433 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/