< draft-ietf-babel-information-model-05.txt   draft-ietf-babel-information-model-06.txt >
Babel routing protocol B. Stark Babel routing protocol B. Stark
Internet-Draft AT&T Internet-Draft AT&T
Intended status: Informational M. Jethanandani Intended status: Informational M. Jethanandani
Expires: September 6, 2019 VMware Expires: January 9, 2020 VMware
March 5, 2019 July 8, 2019
Babel Information Model Babel Information Model
draft-ietf-babel-information-model-05 draft-ietf-babel-information-model-06
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. It allows a Babel implementation (via various data modeling regimes. It allows a Babel implementation (via
a management protocol or interface) to report on its current state a management protocol or interface) to report on its current state
and may allow some limited configuration of protocol constants. and may allow some limited configuration of 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 September 6, 2019. This Internet-Draft will expire on January 9, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 16 skipping to change at page 2, line 16
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 . . . . . . . . . . . . . . . . . . . . 7 3. The Information Model . . . . . . . . . . . . . . . . . . . . 7
3.1. Definition of babel-information-obj . . . . . . . . . . . 7 3.1. Definition of babel-information-obj . . . . . . . . . . . 7
3.2. Definition of babel-constants-obj . . . . . . . . . . . . 9 3.2. Definition of babel-constants-obj . . . . . . . . . . . . 9
3.3. Definition of babel-interfaces-obj . . . . . . . . . . . 9 3.3. Definition of babel-interfaces-obj . . . . . . . . . . . 9
3.4. Definition of babel-if-stats-obj . . . . . . . . . . . . 11 3.4. Definition of babel-if-stats-obj . . . . . . . . . . . . 11
3.5. Definition of babel-neighbors-obj . . . . . . . . . . . . 11 3.5. Definition of babel-neighbors-obj . . . . . . . . . . . . 12
3.6. Definition of babel-nbr-stats-obj . . . . . . . . . . . . 13 3.6. Definition of babel-nbr-stats-obj . . . . . . . . . . . . 13
3.7. Definition of babel-routes-obj . . . . . . . . . . . . . 13 3.7. Definition of babel-routes-obj . . . . . . . . . . . . . 14
3.8. Definition of babel-hmac-obj . . . . . . . . . . . . . . 14 3.8. Definition of babel-hmac-obj . . . . . . . . . . . . . . 15
3.9. Definition of babel-hmac-keys-obj . . . . . . . . . . . . 15 3.9. Definition of babel-hmac-keys-obj . . . . . . . . . . . . 16
3.10. Definition of babel-dtls-obj . . . . . . . . . . . . . . 16 3.10. Definition of babel-dtls-obj . . . . . . . . . . . . . . 16
3.11. Definition of babel-dtls-certs-obj . . . . . . . . . . . 17 3.11. Definition of babel-dtls-certs-obj . . . . . . . . . . . 17
4. Extending the Information Model . . . . . . . . . . . . . . . 18 4. Extending the Information Model . . . . . . . . . . . . . . . 18
5. Security Considerations . . . . . . . . . . . . . . . . . . . 18 5. Security Considerations . . . . . . . . . . . . . . . . . . . 18
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.1. Normative References . . . . . . . . . . . . . . . . . . 20 8.1. Normative References . . . . . . . . . . . . . . . . . . 20
8.2. Informative References . . . . . . . . . . . . . . . . . 20 8.2. Informative References . . . . . . . . . . . . . . . . . 20
Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . 22 Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . 21
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 24 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27
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
[I-D.ietf-babel-rfc6126bis]. [I-D.ietf-babel-hmac] defines a [I-D.ietf-babel-rfc6126bis]. [I-D.ietf-babel-hmac] defines a
security mechanism that allows Babel packets to be cryptographically security mechanism that allows Babel packets to be cryptographically
authenticated, and [I-D.ietf-babel-dtls] defines a security mechanism authenticated, and [I-D.ietf-babel-dtls] defines a security mechanism
that allows Babel packets to be encrypted. This document describes that allows Babel packets to be encrypted. This document describes
an information model for Babel (including implementations using one an information model for Babel (including implementations using one
of these security mechanisms) that can be used to create management of these security mechanisms) that can be used to create management
skipping to change at page 4, line 27 skipping to change at page 4, line 27
information model does not define a precision. information model does not define a precision.
2. Overview 2. Overview
The Information Model is hierarchically structured as follows: The Information Model is hierarchically structured as follows:
+-- babel-information +-- babel-information
+-- babel-implementation-version +-- babel-implementation-version
+-- babel-enable +-- babel-enable
+-- router-id +-- router-id
+-- babel-supported-link-types +-- babel-supported-link-properties
+-- self-seqno +-- self-seqno
+-- babel-metric-comp-algorithms +-- babel-metric-comp-algorithms
+-- babel-security-supported +-- babel-security-supported
+-- babel-hmac-enable +-- babel-hmac-enable
+-- babel-hmac-algorithms +-- babel-hmac-algorithms
+-- babel-dtls-enable +-- babel-dtls-enable
+-- babel-dtls-cert-types +-- babel-dtls-cert-types
+-- babel-stats-enable +-- babel-stats-enable
+-- babel-stats-reset +-- babel-stats-reset
+-- babel-constants +-- babel-constants
| +-- babel-udp-port | +-- babel-udp-port
| +-- babel-mcast-group | +-- babel-mcast-group
+-- babel-interfaces +-- babel-interfaces
| +-- babel-interface-reference | +-- babel-interface-reference
| +-- babel-interface-enable | +-- babel-interface-enable
| +-- babel-link-type | +-- babel-link-properties
| +-- babel-interface-metric-algorithm | +-- babel-interface-metric-algorithm
| +-- babel-mcast-hello-seqno | +-- babel-mcast-hello-seqno
| +-- babel-mcast-hello-interval | +-- babel-mcast-hello-interval
| +-- babel-update-interval | +-- babel-update-interval
| +-- babel-interfaces-hmac-keys
| +-- babel-hmac-algorithm
| +-- babel-hmac-verify
| +-- babel-interfaces-dtls-certs
| +-- babel-dtls-cached-info
| +-- babel-dtls-cert-prefer
| +-- babel-packet-log-enable | +-- babel-packet-log-enable
| +-- babel-packet-log | +-- babel-packet-log
| +-- babel-if-stats | +-- babel-if-stats
| | +-- babel-sent-mcast-hello | | +-- babel-sent-mcast-hello
| | +-- babel-sent-mcast-update | | +-- babel-sent-mcast-update
| | +-- babel-received-packets | | +-- babel-received-packets
| +-- babel-neighbors | +-- babel-neighbors
| | +-- babel-neighbor-address | | +-- babel-neighbor-address
| | +-- babel-hello-mcast-history | | +-- babel-hello-mcast-history
| | +-- babel-hello-ucast-history | | +-- babel-hello-ucast-history
skipping to change at page 5, line 35 skipping to change at page 5, line 41
| +-- babel-route-prefix-length | +-- babel-route-prefix-length
| +-- babel-route-router-id | +-- babel-route-router-id
| +-- babel-route-neighbor | +-- babel-route-neighbor
| +-- babel-route-received-metric | +-- babel-route-received-metric
| +-- babel-route-calculated-metric | +-- babel-route-calculated-metric
| +-- babel-route-seqno | +-- babel-route-seqno
| +-- babel-route-next-hop | +-- babel-route-next-hop
| +-- babel-route-feasible | +-- babel-route-feasible
| +-- babel-route-selected | +-- babel-route-selected
+-- babel-hmac +-- babel-hmac
| +-- babel-hmac-algorithm | +-- babel-hmac-default-apply
| +-- babel-hmac-verify
| +-- babel-hmac-interfaces
| | +-- babel-hmac-key-name | | +-- babel-hmac-key-name
| | +-- babel-hmac-key-use-sign | | +-- babel-hmac-key-use-sign
| | +-- babel-hmac-key-use-verify | | +-- babel-hmac-key-use-verify
| | +-- babel-hmac-key-value | | +-- babel-hmac-key-value
+-- babel-dtls +-- babel-dtls
| +-- babel-dtls-interfaces | +-- babel-dtls-default-apply
| +-- babel-dtls-cached-info
| +-- babel-dtls-cert-prefer
| | +-- babel-cert-value | | +-- babel-cert-value
| | +-- babel-cert-type | | +-- babel-cert-type
| | +-- babel-cert-private-key | | +-- babel-cert-private-key
| | +-- babel-cert-test | | +-- babel-cert-test
Most parameters are read-only. Following is a descriptive list of Most parameters are read-only. Following is a descriptive list of
the parameters that are not required to be read-only: the parameters that are not required to be read-only:
o enable/disable Babel o enable/disable Babel
o babel-hmac objects o create/delete babel-hmac objects
o babel-dtls objects o create/delete babel-dtls objects
o enable/disable statistics collection o enable/disable statistics collection
o Constant: UDP port o Constant: UDP port
o Constant: IPv6 multicast group o Constant: IPv6 multicast group
o Interface: Link type 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 Babel on this interface
o Interface: enable/disable packet log o Interface: sets of HMAC keys
o HMAC: algorithm o Interface: HMAC algorithm
o HMAC: verify received packets o Interface: verify received HMAC packets
o HMAC: interfaces o Interface: set of DTLS certificates
o HMAC-keys: create new entries o Interface: use cached info extensions
o HMAC-keys: use to sign packets o Interface: preferred order of certificate types
o HMAC-keys: use to verify packets o Interface: enable/disable packet log
o DTLS: interfaces o HMAC-keys: create/delete entries
o DTLS: use cached info extensions o HMAC-keys: use to sign packets
o DTLS: preferred order of certificate types o HMAC-keys: use to verify packets
o DTLS-certs: create new entries o DTLS-certs: create/delete entries
The following parameters are required to return no value when read: The following parameters are required to return no value when read:
o HMAC key values o HMAC key values
o DTLS certificate values
o DTLS certificate values
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.
3. The Information Model 3. The Information Model
3.1. Definition of babel-information-obj 3.1. Definition of babel-information-obj
object { object {
string ro babel-implementation-version; string ro babel-implementation-version;
boolean rw babel-enable; boolean rw babel-enable;
binary ro babel-self-router-id; binary ro babel-self-router-id;
string ro babel-supported-link-types<1..*>; string ro babel-supported-link-properties<1..*>;
[uint ro babel-self-seqno;] [uint ro babel-self-seqno;]
string ro babel-metric-comp-algorithms<1..*>; string ro babel-metric-comp-algorithms<1..*>;
string ro babel-security-supported<0..*>; string ro babel-security-supported<0..*>;
[boolean ro babel-hmac-enable;] [boolean ro babel-hmac-enable;]
[string ro babel-hmac-algorithms<1..*>;] [string ro babel-hmac-algorithms<1..*>;]
[boolean ro babel-dtls-enable;] [boolean ro babel-dtls-enable;]
[string ro babel-dtls-cert-types<1..*>;] [string ro babel-dtls-cert-types<1..*>;]
[boolean rw babel-stats-enable;] [boolean rw babel-stats-enable;]
[operation babel-stats-reset;] [operation babel-stats-reset;]
babel-constants-obj ro babel-constants; babel-constants-obj ro babel-constants;
skipping to change at page 8, line 9 skipping to change at page 8, line 5
indicates the operational state of the protocol). A data model indicates the operational state of the protocol). A data model
that does not replicate parameters for running and operational that does not replicate parameters for running and operational
datastores can implement this as two separate parameters. An datastores can implement this as two separate parameters. An
implementation MAY choose to expose this parameter as read-only implementation MAY choose to expose this parameter as read-only
("ro"). ("ro").
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. [I-D.ietf-babel-rfc6126bis] Babel protocol to identify itself. [I-D.ietf-babel-rfc6126bis]
describes this as an arbitrary string of 8 octets. describes this as an arbitrary string of 8 octets.
babel-supported-link-types: Lists the set of link types supported by babel-supported-link-properties: Lists the collections of link
this instance of Babel. Valid enumeration values are defined in properties supported by this instance of Babel. Valid enumeration
the Babel Link Types registry (see Section 6). values are defined in the Babel Link Properties registry (see
Section 6).
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. This is a 16-bit updates for routes originated by this node. This is a 16-bit
unsigned integer. unsigned integer.
babel-metric-comp-algorithms: List of supported cost computation babel-metric-comp-algorithms: List of supported cost computation
algorithms. Possible values include "k-out-of-j", and "ETX". algorithms. Possible values include "k-out-of-j", and "ETX".
babel-security-supported: List of supported security mechanisms. babel-security-supported: List of supported security mechanisms.
Possible values include "HMAC" and "DTLS". Possible values include "HMAC" and "DTLS".
skipping to change at page 9, line 37 skipping to change at page 9, line 32
babel-mcast-group: Multicast group for sending and listening to babel-mcast-group: Multicast group for sending and listening to
multicast announcements on IPv6. Default is ff02:0:0:0:0:0:1:6. multicast announcements on IPv6. Default is ff02:0:0:0:0:0:1:6.
An implementation MAY choose to expose this parameter as read-only An implementation MAY choose to expose this parameter as read-only
("ro"). ("ro").
3.3. Definition of babel-interfaces-obj 3.3. Definition of babel-interfaces-obj
object { object {
reference ro babel-interface-reference; reference ro babel-interface-reference;
[boolean rw babel-interface-enable;] [boolean rw babel-interface-enable;]
string rw babel-link-type; string rw babel-link-properties;
string ro babel-interface-metric-algorithm; string ro babel-interface-metric-algorithm;
[uint ro babel-mcast-hello-seqno;] [uint ro babel-mcast-hello-seqno;]
[uint ro babel-mcast-hello-interval;] [uint ro babel-mcast-hello-interval;]
[uint ro babel-update-interval;] [uint ro babel-update-interval;]
[reference rw babel-interface-hmac-keys<0..*>;]
[string rw babel-hmac-algorithm;]
[boolean rw babel-hmac-verify;]
[reference rw babel-interface-dtls-certs<0..*>;]
[boolean rw babel-dtls-cached-info;]
[string rw babel-dtls-cert-prefer<0..*>;]
[boolean rw babel-packet-log-enable;] [boolean rw babel-packet-log-enable;]
[reference ro babel-packet-log;] [reference ro babel-packet-log;]
[babel-if-stats-obj ro babel-if-stats;] [babel-if-stats-obj ro babel-if-stats;]
babel-neighbors-obj ro babel-neighbors<0..*>; babel-neighbors-obj ro babel-neighbors<0..*>;
} babel-interfaces-obj; } babel-interfaces-obj;
babel-interface-reference: Reference to an interface object as babel-interface-reference: Reference to an IPv6 interface object as
defined by the data model (e.g., YANG [RFC7950], BBF [TR-181]). defined by the data model (e.g., YANG [RFC7950], BBF [TR-181]).
Data model is assumed to allow for referencing of interface Referencing syntax will be specific to the data model. If there
objects which may be at any layer (physical, Ethernet MAC, IP, is no set of interface objects available, this should be a string
tunneled IP, etc.). Referencing syntax will be specific to the that indicates the interface name used by the underlying operating
data model. If there is no set of interface objects available, system.
this should be a string that indicates the interface name used by
the underlying operating system.
babel-interface-enable: When written, it configures whether the babel-interface-enable: When written, it configures whether the
protocol should be enabled (true) or disabled (false) on this protocol should be enabled (true) or disabled (false) on this
interface. A read from the running or intended datastore interface. A read from the running or intended datastore
indicates the configured administrative value of whether the indicates the configured administrative value of whether the
protocol is enabled (true) or not (false). A read from the protocol is enabled (true) or not (false). A read from the
operational datastore indicates whether the protocol is actually operational datastore indicates whether the protocol is actually
running (true) or not (i.e., it indicates the operational state of running (true) or not (i.e., it indicates the operational state of
the protocol). A data model that does not replicate parameters the protocol). A data model that does not replicate parameters
for running and operational datastores can implement this as two for running and operational datastores can implement this as two
separate parameters. An implementation MAY choose to expose this separate parameters. An implementation MAY choose to expose this
parameter as read-only ("ro"). parameter as read-only ("ro").
babel-link-type: Indicates the type of link. The value MUST be one babel-link-properties: Indicates the properties of the link. The
of those listed in the babel-supported-link-types parameter. value MUST be one of those listed in the babel-supported-link-
Valid enumeration values are identified in Babel Link Types properties parameter. Valid enumeration values are identified in
registry. An implementation MAY choose to expose this parameter Babel Link Properties registry. An implementation MAY choose to
as read-only ("ro"). expose this parameter as read-only ("ro").
babel-interface-metric-algorithm: Indicates the metric computation babel-interface-metric-algorithm: Indicates the metric computation
algorithm used on this interface. The value MUST be one of those algorithm used on this interface. The value MUST be one of those
listed in the babel-information-obj babel-metric-comp-algorithms listed in the babel-information-obj babel-metric-comp-algorithms
parameter. parameter.
babel-mcast-hello-seqno: The current sequence number in use for babel-mcast-hello-seqno: The current sequence number in use for
multicast Hellos sent on this interface. This is a 16-bit multicast Hellos sent on this interface. This is a 16-bit
unsigned integer. unsigned integer.
babel-mcast-hello-interval: The current interval in use for babel-mcast-hello-interval: The current interval in use for
multicast Hellos sent on this interface. Units are centiseconds. multicast Hellos sent on this interface. Units are centiseconds.
This is a 16-bit unsigned integer. This is a 16-bit unsigned integer.
babel-update-interval: The current interval in use for all updates babel-update-interval: The current interval in use for all updates
(multicast and unicast) sent on this interface. Units are (multicast and unicast) sent on this interface. Units are
centiseconds. This is a 16-bit unsigned integer. centiseconds. This is a 16-bit unsigned integer.
babel-interface-hmac-keys: List of references to the babel-hmac
entries that apply to this interface. When an interface instance
is created, all babel-hmac instances with babel-hmac-default-apply
"true" will be included in this list. An implementation MAY
choose to expose this parameter as read-only ("ro").
babel-hmac-algorithm The name of the HMAC algorithm used on this
interface. The value MUST be the same as one of the enumerations
listed in the babel-hmac-algorithms parameter. An implementation
MAY choose to expose this parameter as read-only ("ro").
babel-hmac-verify 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. An implementation MAY choose
to expose this parameter as read-only ("ro").
babel-interface-dtls-certs: List of references to the babel-dtls
entries that apply to this interface. When an interface instance
is created, all babel-dtls instances with babel-dtls-default-apply
"true" will be included in this list. An implementation MAY
choose to expose this parameter as read-only ("ro").
babel-dtls-cached-info: Indicates whether the cached_info extension
is included in ClientHello and ServerHello packets. The extension
is included if the value is "true". An implementation MAY choose
to expose this parameter as read-only ("ro").
babel-dtls-cert-prefer: List of supported certificate types, in
order of preference. The values MUST be among those listed in 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 of a referenced babel-dtls instance and that have a non-
empty babel-cert-private-key will be used to populate the
client_certificate_type extension in a Client Hello.
babel-packet-log-enable: Indicates whether packet logging is enabled babel-packet-log-enable: Indicates whether packet logging is enabled
(true) or disabled (false) on this interface. (true) or disabled (false) on this interface.
babel-packet-log: A reference or url link to a file that contains a babel-packet-log: A reference or url link to a file that contains a
timestamped log of packets received and sent on babel-udp-port on timestamped log of packets received and sent on babel-udp-port on
this interface. The [libpcap] file format with .pcap file this interface. The [libpcap] file format with .pcap file
extension SHOULD be supported for packet log files. Logging is extension SHOULD be supported for packet log files. Logging is
enabled / disabled by babel-packet-log-enable. enabled / disabled by babel-packet-log-enable.
babel-if-stats: Statistics collection object for this interface. babel-if-stats: Statistics collection object for this interface.
skipping to change at page 12, line 32 skipping to change at page 13, line 20
multicast Hello packets are not expected, or processing of multicast Hello packets are not expected, or processing of
multicast packets is not enabled, this MUST be 0. This is a multicast packets is not enabled, this MUST be 0. This is a
16-bit unsigned integer. 16-bit unsigned integer.
babel-exp-ucast-hello-seqno: Expected unicast Hello sequence number babel-exp-ucast-hello-seqno: Expected unicast Hello sequence number
of next Hello to be received from this neighbor. If unicast Hello of next Hello to be received from this neighbor. If unicast Hello
packets are not expected, or processing of unicast packets is not packets are not expected, or processing of unicast packets is not
enabled, this MUST be 0. This is a 16-bit unsigned integer. enabled, this MUST be 0. This is a 16-bit unsigned integer.
babel-ucast-hello-seqno: The current sequence number in use for babel-ucast-hello-seqno: The current sequence number in use for
unicast hellos sent to this neighbor. This is a 16-bit unsigned unicast Hellos sent to this neighbor. This is a 16-bit unsigned
integer. integer.
babel-ucast-hello-interval: The current interval in use for unicast babel-ucast-hello-interval: The current interval in use for unicast
hellos sent to this neighbor. Units are centiseconds. This is a Hellos sent to this neighbor. Units are centiseconds. This is a
16-bit unsigned integer. 16-bit unsigned integer.
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 neighbor in each IHU. See link layer. The rxcost is sent to a neighbor in each IHU. See
[I-D.ietf-babel-rfc6126bis], section 3.4.3. This is a 16-bit [I-D.ietf-babel-rfc6126bis], section 3.4.3. This is a 16-bit
unsigned integer. unsigned integer.
babel-cost: Link cost is computed from the values maintained in the babel-cost: Link cost is computed from the values maintained in the
skipping to change at page 13, line 41 skipping to change at page 14, line 30
babel-received-IHU: A count of the number of IHU packets received babel-received-IHU: A count of the number of IHU packets received
from this neighbor. from this neighbor.
3.7. Definition of babel-routes-obj 3.7. Definition of babel-routes-obj
object { object {
ip-address ro babel-route-prefix; ip-address ro babel-route-prefix;
uint ro babel-route-prefix-length; uint ro babel-route-prefix-length;
binary ro babel-route-router-id; binary ro babel-route-router-id;
string ro babel-route-neighbor; string ro babel-route-neighbor;
[uint ro babel-route-received-metric;] uint ro babel-route-received-metric;
[uint ro babel-route-calculated-metric;] uint ro babel-route-calculated-metric;
uint ro babel-route-seqno; uint ro babel-route-seqno;
ip-address ro babel-route-next-hop; ip-address ro babel-route-next-hop;
boolean ro babel-route-feasible; boolean ro babel-route-feasible;
boolean ro babel-route-selected; boolean ro 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 route babel-route-prefix-length: Length of the prefix for which this route
skipping to change at page 14, line 19 skipping to change at page 15, line 6
route is advertised. route is advertised.
babel-route-neighbor: Reference to the babel-neighbors entry for the babel-route-neighbor: Reference to the babel-neighbors entry for the
neighbor that advertised this route. neighbor that advertised this route.
babel-route-received-metric: The metric with which this route was babel-route-received-metric: The metric with which this route was
advertised by the neighbor, or maximum value to indicate the route advertised by the neighbor, or maximum value to indicate the route
was recently retracted and is temporarily unreachable (see was recently retracted and is temporarily unreachable (see
Section 3.5.5 of [I-D.ietf-babel-rfc6126bis]). This metric will Section 3.5.5 of [I-D.ietf-babel-rfc6126bis]). This metric will
be 0 (zero) if the route was not received from a neighbor but was be 0 (zero) if the route was not received from a neighbor but was
generated through other means. Either babel-route-calculated- generated through other means. At least one of babel-route-
metric or babel-route-received-metric MUST be provided. This is a calculated-metric and babel-route-received-metric MUST be non-
16-bit unsigned integer. zero. Having both be non-zero is expected for a route that is
received and subsequently advertised. This is a 16-bit unsigned
integer.
babel-route-calculated-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. Maximum How the metric is calculated is implementation-specific. Maximum
value indicates the route was recently retracted and is value indicates the route was recently retracted and is
temporarily unreachable (see Section 3.5.5 of temporarily unreachable (see Section 3.5.5 of
[I-D.ietf-babel-rfc6126bis]). Either babel-route-calculated- [I-D.ietf-babel-rfc6126bis]). At least one of babel-route-
metric or babel-route-received-metric MUST be provided. This is a calculated-metric and babel-route-received-metric MUST be non-
16-bit unsigned integer. zero. Having both be non-zero is expected for a route that is
received and subsequently advertised. This is a 16-bit unsigned
integer.
babel-route-seqno: The sequence number with which this route was babel-route-seqno: The sequence number with which this route was
advertised. This is a 16-bit unsigned integer. advertised. This is a 16-bit unsigned integer.
babel-route-next-hop: The next-hop address of this route. This will babel-route-next-hop: The next-hop address of this route. This will
be empty if this route has no next-hop address. 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 feasible, as defined in Section 3.5.1 of is feasible, as defined in Section 3.5.1 of
[I-D.ietf-babel-rfc6126bis]). [I-D.ietf-babel-rfc6126bis]).
skipping to change at page 15, line 4 skipping to change at page 15, line 37
babel-route-feasible: A Boolean flag indicating whether this route babel-route-feasible: A Boolean flag indicating whether this route
is feasible, as defined in Section 3.5.1 of is feasible, as defined in Section 3.5.1 of
[I-D.ietf-babel-rfc6126bis]). [I-D.ietf-babel-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).
3.8. Definition of babel-hmac-obj 3.8. Definition of babel-hmac-obj
object { object {
string rw babel-hmac-algorithm; boolean rw babel-hmac-default-apply;
boolean rw babel-hmac-verify;
boolean rw babel-hmac-apply-all;
reference rw babel-hmac-interfaces<0..*>;
babel-hmac-keys-obj rw babel-hmac-keys<0..*>; babel-hmac-keys-obj rw babel-hmac-keys<0..*>;
} babel-hmac-obj; } babel-hmac-obj;
babel-hmac-algorithm The name of the HMAC algorithm this object babel-hmac-default-apply: A Boolean flag indicating whether this
instance uses. The value MUST be the same as one of the babel-hmac instance is applied to all interfaces, by default. If
enumerations listed in the babel-hmac-algorithms parameter. An "true", this instance is applied to new babel-interfaces instances
implementation MAY choose to expose this parameter as read-only at the time they are created, by including it in the babel-
("ro"). interface-hmac-keys list. If "false", this instance is not
applied to new babel-interfaces instances when they are created.
babel-hmac-verify A Boolean flag indicating whether HMAC hashes in An implementation MAY choose to expose this parameter as read-only
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. An implementation MAY choose
to expose this parameter as read-only ("ro").
babel-hmac-apply-all: A Boolean flag indicating whether this babel-
hmac 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. An implementation MAY choose to expose
this parameter as read-only ("ro").
babel-hmac-interfaces: List of references to the babel-interfaces
entries this 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. An
implementation MAY choose to expose this parameter as read-only
("ro"). ("ro").
babel-hmac-keys: A set of babel-hmac-keys-obj objects. babel-hmac-keys: A set of babel-hmac-keys-obj objects.
3.9. Definition of babel-hmac-keys-obj 3.9. Definition of babel-hmac-keys-obj
object { object {
string ro babel-hmac-key-name; string ro babel-hmac-key-name;
boolean rw babel-hmac-key-use-sign; boolean rw babel-hmac-key-use-sign;
boolean rw babel-hmac-key-use-verify; boolean rw babel-hmac-key-use-verify;
skipping to change at page 16, line 37 skipping to change at page 17, line 4
is not subsequently writable. is not subsequently writable.
babel-hmac-test: An operation that allows the HMAC key and hash babel-hmac-test: An operation that allows the HMAC key and hash
algorithm to be tested to see if they produce an expected outcome. algorithm to be tested to see if they produce an expected outcome.
Input to this operation is a binary string. The implementation is Input to this operation is a binary string. The implementation is
expected to create a hash of this string using the babel-hmac-key- expected to create a hash of this string using the babel-hmac-key-
value and the babel-hmac-algorithm. The output of this operation value and the babel-hmac-algorithm. The output of this operation
is the resulting hash, as a binary string. is the resulting hash, as a binary string.
3.10. Definition of babel-dtls-obj 3.10. Definition of babel-dtls-obj
object { object {
boolean rw babel-dtls-apply-all; boolean rw babel-dtls-default-apply;
reference rw babel-dtls-interfaces<0..*>;
[boolean rw babel-dtls-cached-info;]
[string rw babel-dtls-cert-prefer<0..*>;]
babel-dtls-certs-obj rw babel-dtls-certs<0..*>; babel-dtls-certs-obj rw babel-dtls-certs<0..*>;
} babel-dtls-obj; } babel-dtls-obj;
babel-dtls-apply-all: A Boolean flag indicating whether this babel- babel-dtls-default-apply: A Boolean flag indicating whether this
dtls instance is to be used for all interfaces. If "true", this babel-dtls instance is applied to all interfaces, by default. If
instance applies to all interfaces and the babel-dtls-interfaces "true", this instance is applied to new babel-interfaces instances
parameter is ignored. If babel-dtls-apply-all is "true", there at the time they are created, by including it in the babel-
MUST NOT be other instances of the babel-dtls object. If "false", interface-dtls-certs list. If "false", this instance is not
the babel-dtls-interfaces parameter determines which interfaces applied to new babel-interfaces instances when they are created.
this instance applies to. An implementation MAY choose to expose An implementation MAY choose to expose this parameter as read-only
this parameter as read-only ("ro").
babel-dtls-interfaces: List of references to the babel-interfaces
entries this 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. An
implementation MAY choose to expose this parameter as read-only
("ro"). ("ro").
babel-dtls-cached-info: Indicates whether the cached_info extension
is included in ClientHello and ServerHello packets. The extension
is included if the value is "true". An implementation MAY choose
to expose this parameter as read-only ("ro").
babel-dtls-cert-prefer: List of supported certificate types, in
order of preference. The values MUST be among those listed in 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 to
populate the client_certificate_type extension in a Client Hello.
babel-dtls-certs: A set of babel-dtls-keys-obj objects. This babel-dtls-certs: A set of babel-dtls-keys-obj objects. This
contains both certificates for this implementation to present for contains both certificates for this implementation to present for
authentication, and to accept from others. Certificates with a authentication, and to accept from others. Certificates with a
non-empty babel-cert-private-key can be presented by this non-empty babel-cert-private-key can be presented by this
implementation for authentication. implementation for authentication.
3.11. Definition of babel-dtls-certs-obj 3.11. Definition of babel-dtls-certs-obj
object { object {
string ro babel-cert-name;
string ro babel-cert-value; string ro babel-cert-value;
string ro babel-cert-type; string ro babel-cert-type;
binary -- babel-cert-private-key; binary -- babel-cert-private-key;
[operation babel-cert-test;] [operation babel-cert-test;]
} babel-dtls-certs-obj; } babel-dtls-certs-obj;
babel-cert-name: A unique name for this DTLS certificate that can be
used to identify the certificate in this object instance, since
the value is too long to be useful for identification. This value
can only be provided when this instance is created, and is not
subsequently writable.
babel-cert-value: The DTLS certificate in PEM format [RFC7468]. babel-cert-value: The DTLS certificate in PEM format [RFC7468].
This value can only be provided when this instance is created, and This value can only be provided when this instance is created, and
is not subsequently writable. is not subsequently writable.
babel-cert-type: The name of the certificate type of this object babel-cert-type: The name of the certificate type of this object
instance. The value MUST be the same as one of the enumerations instance. The value MUST be the same as one of the enumerations
listed in the babel-dtls-cert-types parameter. This value can listed in the babel-dtls-cert-types parameter. This value can
only be provided when this instance is created, and is not only be provided when this instance is created, and is not
subsequently writable. subsequently writable.
skipping to change at page 19, line 7 skipping to change at page 18, line 49
(for this device, for trusted devices, and for trusted certificate (for this device, for trusted devices, and for trusted certificate
authorities) to be added and deleted. Public keys and shared secrets authorities) to be added and deleted. Public keys and shared secrets
may be exposed through this model. This model requires that private may be exposed through this model. This model requires that private
keys never be exposed. The Babel security mechanisms that make use keys never be exposed. The Babel security mechanisms that make use
of these credentials (e.g., [I-D.ietf-babel-dtls], of these credentials (e.g., [I-D.ietf-babel-dtls],
[I-D.ietf-babel-hmac]) are expected to define what credentials can be [I-D.ietf-babel-hmac]) are expected to define what credentials can be
used with those mechanisms. used with those mechanisms.
6. IANA Considerations 6. IANA Considerations
This document defines a Babel Link Type registry for the values of This document defines a Babel Link Properties registry for the values
the babel-link-type and babel-supported-link-types parameters to be of the babel-link-properties and babel-supported-link-properties
listed under the Babel Routing Protocol registry. parameters to be listed under the Babel Routing Protocol registry.
Valid Babel Link Type names are normatively defined as Valid Babel Link Properties names are normatively defined as
o MUST be at least 1 character and no more than 20 characters long o MUST be at least 1 character and no more than 20 characters long
o MUST contain only US-ASCII [RFC0020] letters 'A' - 'Z' and 'a' - o MUST contain only US-ASCII [RFC0020] letters 'A' - 'Z' and 'a' -
'z', digits '0' - '9', and hyphens ('-', ASCII 0x2D or decimal 45) 'z', digits '0' - '9', and hyphens ('-', ASCII 0x2D or decimal 45)
o MUST contain at least one letter ('A' - 'Z' or 'a' - 'z') o MUST contain at least one letter ('A' - 'Z' or 'a' - 'z')
o MUST NOT begin or end with a hyphen o MUST NOT begin or end with a hyphen
o hyphens MUST NOT be adjacent to other hyphens o hyphens MUST NOT be adjacent to other hyphens
The rules for Link Type names, excepting the limit of 20 characters The rules for Link Properties names, excepting the limit of 20
maximum, are also expressed below (as a non-normative convenience) characters maximum, are also expressed below (as a non-normative
using ABNF [RFC5234]. convenience) using ABNF [RFC5234].
SRVNAME = *(1*DIGIT [HYPHEN]) ALPHA *([HYPHEN] ALNUM) SRVNAME = *(1*DIGIT [HYPHEN]) ALPHA *([HYPHEN] ALNUM)
ALNUM = ALPHA / DIGIT ; A-Z, a-z, 0-9 ALNUM = ALPHA / DIGIT ; A-Z, a-z, 0-9
HYPHEN = %x2D ; "-" HYPHEN = %x2D ; "-"
ALPHA = %x41-5A / %x61-7A ; A-Z / a-z [RFC5234] ALPHA = %x41-5A / %x61-7A ; A-Z / a-z [RFC5234]
DIGIT = %x30-39 ; 0-9 [RFC5234] DIGIT = %x30-39 ; 0-9 [RFC5234]
The allocation policy of this registry is Specification Required The allocation policy of this registry is Specification Required
[RFC8126]. [RFC8126].
The initial values in the "Babel Link Type" registry are: The initial values in the "Babel Link Properties" registry are:
+----------+-------------------------------------------+------------+ +----------+----------------------------------------+---------------+
| Name | Used for Links Defined By | Reference | | Name | Describes Links with Properties | Reference |
+----------+-------------------------------------------+------------+ +----------+----------------------------------------+---------------+
| ethernet | [IEEE-802.3-2018] | (this | | other | no link property information available | (this |
| | | document) | | | | document) |
| other | to be used when no link type information | (this | | tunnel | a tunneled interface over unknown | (this |
| | available | document) | | | physical link | document) |
| tunnel | to be used for a tunneled interface over | (this | | wired | | (this |
| | unknown physical link | document) | | | | document) |
| wireless | [IEEE-802.11-2016] | (this | | wireless | | (this |
| | | document) | | | | document) |
| exp-* | Reserved for Experimental Use | (this | | exp-* | Reserved for Experimental Use | (this |
| | | document) | | | | document) |
+----------+-------------------------------------------+------------+ +----------+----------------------------------------+---------------+
7. Acknowledgements 7. Acknowledgements
Juliusz Chroboczek, Toke Hoeiland-Joergensen, David Schinazi, Acee Juliusz Chroboczek, Toke Hoeiland-Joergensen, David Schinazi, Acee
Lindem, and Carsten Bormann have been very helpful in refining this Lindem, and Carsten Bormann have been very helpful in refining this
information model. information model.
The language in the Notation section was mostly taken from [RFC8193]. The language in the Notation section was mostly taken from [RFC8193].
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.ietf-babel-rfc6126bis] [I-D.ietf-babel-rfc6126bis]
Chroboczek, J. and D. Schinazi, "The Babel Routing Chroboczek, J. and D. Schinazi, "The Babel Routing
Protocol", draft-ietf-babel-rfc6126bis-07 (work in Protocol", draft-ietf-babel-rfc6126bis-11 (work in
progress), November 2018. progress), June 2019.
[libpcap] Wireshark, "Libpcap File Format", 2015, [libpcap] Wireshark, "Libpcap File Format", 2015,
<https://wiki.wireshark.org/Development/ <https://wiki.wireshark.org/Development/
LibpcapFileFormat>. LibpcapFileFormat>.
[RFC0020] Cerf, V., "ASCII format for network interchange", STD 80, [RFC0020] Cerf, V., "ASCII format for network interchange", STD 80,
RFC 20, DOI 10.17487/RFC0020, October 1969, RFC 20, DOI 10.17487/RFC0020, October 1969,
<https://www.rfc-editor.org/info/rfc20>. <https://www.rfc-editor.org/info/rfc20>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
skipping to change at page 21, line 8 skipping to change at page 20, line 47
[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>.
8.2. Informative References 8.2. Informative References
[I-D.ietf-babel-dtls] [I-D.ietf-babel-dtls]
Decimo, A., Schinazi, D., and J. Chroboczek, "Babel Decimo, A., Schinazi, D., and J. Chroboczek, "Babel
Routing Protocol over Datagram Transport Layer Security", Routing Protocol over Datagram Transport Layer Security",
draft-ietf-babel-dtls-04 (work in progress), February draft-ietf-babel-dtls-07 (work in progress), July 2019.
2019.
[I-D.ietf-babel-hmac] [I-D.ietf-babel-hmac]
Do, C., Kolodziejak, W., and J. Chroboczek, "HMAC Do, C., Kolodziejak, W., and J. Chroboczek, "HMAC
authentication for the Babel routing protocol", draft- authentication for the Babel routing protocol", draft-
ietf-babel-hmac-03 (work in progress), December 2018. ietf-babel-hmac-08 (work in progress), July 2019.
[IEEE-802.11-2016]
"IEEE Standard 802.11-2016 - IEEE Standard for Information
Technology - Telecommunications and information exchange
between systems Local and metropolitan area networks -
Specific requirements - Part 11: Wireless LAN Medium
Access Control (MAC) and Physical Layer (PHY)
Specifications.".
[IEEE-802.3-2018]
"IEEE Standard 802.3-2018 - IEEE Approved Draft Standard
for Ethernet.".
[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
Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, DOI 10.17487/RFC3986, January 2005,
<https://www.rfc-editor.org/info/rfc3986>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, Specifications: ABNF", STD 68, RFC 5234,
DOI 10.17487/RFC5234, January 2008, DOI 10.17487/RFC5234, January 2008,
<https://www.rfc-editor.org/info/rfc5234>. <https://www.rfc-editor.org/info/rfc5234>.
[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 22, line 24 skipping to change at page 21, line 43
[TR-181] Broadband Forum, "Device Data Model", [TR-181] Broadband Forum, "Device Data Model",
<http://cwmp-data-models.broadband-forum.org/>. <http://cwmp-data-models.broadband-forum.org/>.
Appendix A. Open Issues Appendix A. Open Issues
All open issues have been closed. All open issues have been closed.
Closed Issues: Closed Issues:
1. HMAC spec adds other parameters to neighbor table. Check these 1. See minutes of IETF 104 for discussion of issues that led to
changes noted for 2019-07-08
2. HMAC spec adds other parameters to neighbor table. Check these
to see if any need to be readable or writable. / None were to see if any need to be readable or writable. / None were
identified. identified.
2. Actions to add and delete HMAC and DTLS credentials, and 3. Actions to add and delete HMAC and DTLS credentials, and
parameters that allow credential to be identified without parameters that allow credential to be identified without
allowing access to private credential info. Will have separate allowing access to private credential info. Will have separate
sub-tables for HMAC and DTLS credentials. / Instead, there is a sub-tables for HMAC and DTLS credentials. / Instead, there is a
normative statement that the parameter values must never be normative statement that the parameter values must never be
supplied when read. supplied when read.
3. Consider the following statistics: under interface object: sent 4. Consider the following statistics: under interface object: sent
multicast Hello, sent updates, received Babel messages; under multicast Hello, sent updates, received Babel messages; under
neighbor object: sent unicast Hello, sent updates, sent IHU, neighbor object: sent unicast Hello, sent updates, sent IHU,
received Hello, received updates, received IHUs. Would also received Hello, received updates, received IHUs. Would also
need to enable/disable stats and clear stats. need to enable/disable stats and clear stats.
4. Message log (optional to implement) is still in. Support for 5. Message log (optional to implement) is still in. Support for
the libpcap file format is "SHOULD". the libpcap file format is "SHOULD".
5. Single security table with (optional) reference to interfaces 6. Single security table with (optional) reference to interfaces
that security mechanism applies to. / This actually became that security mechanism applies to. / This actually became
separate objects for DTLS and HMAC. separate objects for DTLS and HMAC.
6. Should ABNF be normative in IANA Considerations section? 7. Should ABNF be normative in IANA Considerations section?
Decision was to leave it as is. Decision was to leave it as is.
7. I want to get rid of the security log, because all Babel 8. I want to get rid of the security log, because all Babel
messages (which should be defined as all messages to/from the messages (which should be defined as all messages to/from the
udp-port) are be logged by message-log. I don't like message udp-port) are be logged by message-log. I don't like message
log as it is. I think if logging is enabled it should just log as it is. I think if logging is enabled it should just
write to a text file. This will mean there also needs to be a write to a text file. This will mean there also needs to be a
means of downloading/reading the log file. Closed by having means of downloading/reading the log file. Closed by having
single log for all messages to/from udp port and log is single log for all messages to/from udp port and log is
represented by a string that can be reference to filename or represented by a string that can be reference to filename or
some other part of the overall data model (depends on data some other part of the overall data model (depends on data
model). model).
8. Check description of enable parameters to make sure ok for YANG 9. Check description of enable parameters to make sure ok for YANG
and TR-181. Closed by updating description to be useful for and TR-181. Closed by updating description to be useful for
YANG and TR-181, using language consistent with YANG YANG and TR-181, using language consistent with YANG
descriptions. Done. descriptions. Done.
9. Distinguish signed and unsigned integers? All integers are 10. Distinguish signed and unsigned integers? All integers are
unsigned and size is mentioned in description of each uint unsigned and size is mentioned in description of each uint
parameter. parameter.
10. Datatype of the router-id: Closed by introducing binary datatype 11. Datatype of the router-id: Closed by introducing binary datatype
and using that for router-id and using that for router-id
11. babel-neighbor-address as IPv6-only: Closed by leaving as is 12. babel-neighbor-address as IPv6-only: Closed by leaving as is
(IPv4 and IPv6) (IPv4 and IPv6)
12. babel-implementation-version includes the name of the 13. babel-implementation-version includes the name of the
implementation: Closed by adding "name" to description implementation: Closed by adding "name" to description
13. Delete external-cost?: Closed by deleting. 14. Delete external-cost?: Closed by deleting.
14. Would it be useful to define some parameters for reporting 15. Would it be useful to define some parameters for reporting
statistics or logs? [2 logs are now included. If others are statistics or logs? [2 logs are now included. If others are
needed they need to be proposed. See Open Issues for additional needed they need to be proposed. See Open Issues for additional
thoughts on logs and statistics.] thoughts on logs and statistics.]
15. Closed by defining base64 type and using it for all router IDs: 16. 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?"
16. Closed as "No": Do we need a registry for the supported security 17. Closed as "No": Do we need a registry for the supported security
mechanisms? [Given the current limited set, and unlikelihood of mechanisms? [Given the current limited set, and unlikelihood of
massive expansion, I don't think so. But we can if someone massive expansion, I don't think so. But we can if someone
wants it.] wants it.]
17. This draft must be reviewed against draft-ietf-babel-rfc6126bis. 18. This draft must be reviewed against draft-ietf-babel-rfc6126bis.
[I feel like this has been adequately done, but I could be [I feel like this has been adequately done, but I could be
wrong.] wrong.]
18. babel-interfaces-obj: Juliusz:"This needs further discussion, I 19. 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-type and the neighbors sub-object are optional. If an link-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 simply doesn't have them and that's fine.] it simply doesn't have them and that's fine.]
19. Would it be useful to define some parameters specifically for 20. Would it be useful to define some parameters specifically for
security anomalies? [The 2 logs should be useful in identifying security anomalies? [The 2 logs should be useful in identifying
security anomalies. If more is needed, someone needs to security anomalies. If more is needed, someone needs to
propose.] propose.]
20. I created a basic security model. It's useful for single (or 21. I created a basic security model. It's useful for single (or
no) active security mechanism (e.g., just HMAC, just DTLS, or no) active security mechanism (e.g., just HMAC, just DTLS, or
neither); but not multiple active (both HMAC and DTLS -- which neither); but not multiple active (both HMAC and DTLS -- which
is not the same as HMAC of DTLS and would just mean that HMAC 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 would be used on all unencrypted messages -- but right now the
model doesn't allow for configuring HMAC of unencrypted messages model doesn't allow for configuring HMAC of unencrypted messages
for routers without DTLS, while DTLS is used if possible). OK? for routers without DTLS, while DTLS is used if possible). OK?
[No-one said otherwise.] [No-one said otherwise.]
21. babel-external-cost may need more work. [if no comment, it will 22. babel-external-cost may need more work. [if no comment, it will
be left as is] be left as is]
22. babel-hello-[mu]cast-history: the Hello history is formated as 23. babel-hello-[mu]cast-history: the Hello history is formated as
16 bits, per A.1 of 6126bis. Is that a too implementation 16 bits, per A.1 of 6126bis. Is that a too implementation
specific? [We also now have an optional-to-implement log of specific? [We also now have an optional-to-implement log of
received messages, and I made these optional. So maybe this is received messages, and I made these optional. So maybe this is
ok?] ok?]
23. rxcost, txcost, cost: is it ok to model as integers, since 24. 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 them as integers unless someone insists on something else.] have them as integers unless someone insists on something else.]
24. For the security log, should it also log whether the credentials 25. 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.]
25. Should Babel link types have an IANA registry? [Agreed to do 26. Should Babel link types have an IANA registry? [Agreed to do
this at IETF 102.] this at IETF 102.]
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 from v01 2017-03-13: Addressed comments received in 2016-07-15 email from
J. Chroboczek 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
skipping to change at page 28, line 5 skipping to change at page 27, line 26
hmac keys and DTLS certificates are more explicitly modeled hmac keys and DTLS certificates are more explicitly modeled
* changed definition of babel-security-supported * changed definition of babel-security-supported
* added parameters for HMAC and DTLS * added parameters for HMAC and DTLS
* added statistics * added statistics
* changed all instances of "message" to "packet" * changed all instances of "message" to "packet"
v06 2019-07-08:
* changed Link Type registry in IANA considerations to Lik
Property Types
* changed direction of reference for HMAC and DTLS objects to be
from interface to these objects
* provided DTLS certificate objects with a unique name
* changed received and calculated metric descriptions to make
clear that it is ok to have both
* constrained interface reference to only IPv6 interfaces
Authors' Addresses Authors' Addresses
Barbara Stark Barbara Stark
AT&T AT&T
Atlanta, GA Atlanta, GA
US US
Email: barbara.stark@att.com Email: barbara.stark@att.com
Mahesh Jethanandani Mahesh Jethanandani
VMware VMware
California California
US US
Email: mjethanandani@gmail.com Email: mjethanandani@gmail.com
 End of changes. 88 change blocks. 
197 lines changed or deleted 203 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/