< draft-ietf-babel-information-model-07.txt   draft-ietf-babel-information-model-08.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: January 21, 2020 VMware Expires: February 4, 2020 VMware
July 20, 2019 August 3, 2019
Babel Information Model Babel Information Model
draft-ietf-babel-information-model-07 draft-ietf-babel-information-model-08
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 January 21, 2020. This Internet-Draft will expire on February 4, 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 13 skipping to change at page 2, line 13
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. 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 . . . . . . . . . . . . 8
3.3. Definition of babel-interfaces-obj . . . . . . . . . . . 9 3.3. Definition of babel-interfaces-obj . . . . . . . . . . . 9
3.4. Definition of babel-if-stats-obj . . . . . . . . . . . . 12 3.4. Definition of babel-if-stats-obj . . . . . . . . . . . . 11
3.5. Definition of babel-neighbors-obj . . . . . . . . . . . . 12 3.5. Definition of babel-neighbors-obj . . . . . . . . . . . . 12
3.6. Definition of babel-nbr-stats-obj . . . . . . . . . . . . 14 3.6. Definition of babel-nbr-stats-obj . . . . . . . . . . . . 13
3.7. Definition of babel-routes-obj . . . . . . . . . . . . . 14 3.7. Definition of babel-routes-obj . . . . . . . . . . . . . 14
3.8. Definition of babel-hmac-key-sets-obj . . . . . . . . . . 16 3.8. Definition of babel-hmac-key-sets-obj . . . . . . . . . . 15
3.9. Definition of babel-hmac-keys-obj . . . . . . . . . . . . 16 3.9. Definition of babel-hmac-keys-obj . . . . . . . . . . . . 16
3.10. Definition of babel-dtls-cert-sets-obj . . . . . . . . . 17 3.10. Definition of babel-dtls-cert-sets-obj . . . . . . . . . 17
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. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 7.1. Normative References . . . . . . . . . . . . . . . . . . 19
8.1. Normative References . . . . . . . . . . . . . . . . . . 20 7.2. Informative References . . . . . . . . . . . . . . . . . 20
8.2. Informative References . . . . . . . . . . . . . . . . . 21 Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . 21
Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . 22 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 23
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 24 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28
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-properties
+-- self-seqno +-- self-seqno
+-- babel-metric-comp-algorithms +-- babel-metric-comp-algorithms
+-- babel-security-supported +-- babel-security-supported
+-- babel-hmac-algorithms +-- babel-hmac-algorithms
+-- 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-properties
| +-- babel-interface-metric-algorithm | +-- babel-interface-metric-algorithm
| +-- babel-interface-split-horizon
| +-- babel-mcast-hello-seqno | +-- babel-mcast-hello-seqno
| +-- babel-mcast-hello-interval | +-- babel-mcast-hello-interval
| +-- babel-update-interval | +-- babel-update-interval
| +-- babel-hmac-enable | +-- babel-hmac-enable
| +-- babel-if-hmac-key-sets | +-- babel-if-hmac-key-sets
| +-- babel-hmac-algorithm | +-- babel-hmac-algorithm
| +-- babel-hmac-verify | +-- babel-hmac-verify
| +-- babel-dtls-enable | +-- babel-dtls-enable
| +-- babel-if-dtls-cert-sets | +-- babel-if-dtls-cert-sets
| +-- babel-dtls-cached-info | +-- babel-dtls-cached-info
skipping to change at page 7, line 19 skipping to change at page 7, line 19
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-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..*>;
[string ro babel-hmac-algorithms<1..*>;] [string ro babel-hmac-algorithms<1..*>;]
[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;
babel-interfaces-obj ro babel-interfaces<0..*>; babel-interfaces-obj ro babel-interfaces<0..*>;
babel-routes-obj ro babel-routes<0..*>; babel-routes-obj ro babel-routes<0..*>;
skipping to change at page 8, line 7 skipping to change at page 8, line 5
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. The router-id describes this as an arbitrary string of 8 octets. The router-id
value MUST NOT consist of all zeroes or all ones. value MUST NOT consist of all zeroes or all ones.
babel-supported-link-properties: Lists the collections of link
properties supported by this instance of Babel. Valid enumeration
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 "2-out-of-3", 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".
babel-hmac-algorithms: List of supported HMAC computation babel-hmac-algorithms: List of supported HMAC computation
algorithms. Possible values include "HMAC-SHA256", "BLAKE2s". algorithms. Possible values include "HMAC-SHA256", "BLAKE2s".
babel-dtls-cert-types: List of supported DTLS certificate types. babel-dtls-cert-types: List of supported DTLS certificate types.
Possible values include "X.509" and "RawPublicKey". Possible values include "X.509" and "RawPublicKey".
skipping to change at page 9, line 27 skipping to change at page 9, line 20
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-properties; string rw babel-interface-metric-algorithm;
string ro babel-interface-metric-algorithm; boolean rw babel-interface-split-horizon;
[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;]
[boolean rw babel-hmac-enable;] [boolean rw babel-hmac-enable;]
[reference rw babel-if-hmac-key-sets<0..*>;] [reference rw babel-if-hmac-key-sets<0..*>;]
[string rw babel-hmac-algorithm;] [string rw babel-hmac-algorithm;]
[boolean rw babel-hmac-verify;] [boolean rw babel-hmac-verify;]
[boolean rw babel-dtls-enable;] [boolean rw babel-dtls-enable;]
[reference rw babel-if-dtls-cert-sets<0..*>;] [reference rw babel-if-dtls-cert-sets<0..*>;]
[boolean rw babel-dtls-cached-info;] [boolean rw babel-dtls-cached-info;]
skipping to change at page 10, line 17 skipping to change at page 10, line 9
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-properties: Indicates the properties of the link. The
value MUST be one of those listed in the babel-supported-link-
properties parameter. Valid enumeration values are identified in
Babel Link Properties registry. An implementation MAY choose to
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. An implementation MAY choose to expose this parameter
as read-only ("ro").
babel-interface-split-horizon: Indicates whether or not the split
horizon optimization is used when calculating metrics on this
interface. A value of true indicates split horizon optimization
is used.
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
skipping to change at page 15, line 23 skipping to change at page 15, line 10
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. At least one of babel-route- generated through other means. At least one of babel-route-
calculated-metric and babel-route-received-metric MUST be non- calculated-metric and babel-route-received-metric MUST be non-
zero. Having both be non-zero is expected for a route that is zero. Having both be non-zero is expected for a route that is
received and subsequently advertised. This is a 16-bit unsigned received and subsequently advertised. This is a 16-bit unsigned
integer. integer; if the data model uses zero (0) to represent NULL values
for unsigned integers, the data model may use a different data
type that allows differentiation between zero (0) and NULL.
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]). At least one of babel-route- [I-D.ietf-babel-rfc6126bis]). At least one of babel-route-
calculated-metric and babel-route-received-metric MUST be non- calculated-metric and babel-route-received-metric MUST be non-
zero. Having both be non-zero is expected for a route that is zero. Having both be non-zero is expected for a route that is
received and subsequently advertised. This is a 16-bit unsigned received and subsequently advertised. This is a 16-bit unsigned
integer. integer; but it may be represented by a data model as a signed
integer for schemas that use 0 (zero) to represent NULL with
unsigned integers and use negative numbers to represent NULL with
signed integers.
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 19, line 13 skipping to change at page 19, line 4
the various parameters, and a [TR-181] data model will be secured by the various parameters, and a [TR-181] data model will be secured by
the mechanisms defined for the management protocol used to transport the mechanisms defined for the management protocol used to transport
it. it.
This information model defines objects that can allow credentials This information model defines objects that can allow credentials
(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. Acknowledgements
This document defines a Babel Link Properties registry for the values
of the babel-link-properties and babel-supported-link-properties
parameters to be listed under the Babel Routing Protocol registry.
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 contain only US-ASCII [RFC0020] letters 'A' - 'Z' and 'a' -
'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 NOT begin or end with a hyphen
o hyphens MUST NOT be adjacent to other hyphens
The rules for Link Properties names, excepting the limit of 20
characters maximum, are also expressed below (as a non-normative
convenience) using ABNF [RFC5234].
SRVNAME = *(1*DIGIT [HYPHEN]) ALPHA *([HYPHEN] ALNUM)
ALNUM = ALPHA / DIGIT ; A-Z, a-z, 0-9
HYPHEN = %x2D ; "-"
ALPHA = %x41-5A / %x61-7A ; A-Z / a-z [RFC5234]
DIGIT = %x30-39 ; 0-9 [RFC5234]
The allocation policy of this registry is Specification Required
[RFC8126].
The initial values in the "Babel Link Properties" registry are:
+----------+----------------------------------------+---------------+
| Name | Links Properties | Reference |
+----------+----------------------------------------+---------------+
| other | implementation-specific default | (this |
| | properties used | document) |
| tunnel | 2-out-of-3, split horizon, RTT | (this |
| | | document) |
| wired | 2-out-of-3, split horizon, no RTT | (this |
| | | document) |
| wireless | ETX, no split horizon, no RTT | (this |
| | | document) |
| exp-* | Reserved for Experimental Use | (this |
| | | document) |
+----------+----------------------------------------+---------------+
The link properties listed are expected to include the metric
computation algorithm that will be used for the link and whether
split horizon optimization is used. If round trip time is used in
metric computation, this should also be noted (any link property that
does not mention RTT will be assumed not to use it).
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 7. References
8.1. Normative References 7.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-11 (work in Protocol", draft-ietf-babel-rfc6126bis-11 (work in
progress), June 2019. 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>.
skipping to change at page 21, line 23 skipping to change at page 20, line 5
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26, Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017, RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>. <https://www.rfc-editor.org/info/rfc8126>.
[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 7.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-07 (work in progress), July 2019. draft-ietf-babel-dtls-07 (work in progress), July 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-08 (work in progress), July 2019. ietf-babel-hmac-08 (work in progress), July 2019.
skipping to change at page 28, line 36 skipping to change at page 27, line 27
* https://github.com/bhstark2/babel-information-model/issues/16 * https://github.com/bhstark2/babel-information-model/issues/16
with nits with nits
* https://github.com/bhstark2/babel-information-model/issues/14 * https://github.com/bhstark2/babel-information-model/issues/14
addressing parameters not allowed to be empty/null addressing parameters not allowed to be empty/null
* https://github.com/bhstark2/babel-information-model/issues/18 * https://github.com/bhstark2/babel-information-model/issues/18
on IANA link properties table on IANA link properties table
v08 2019-08-04:
* Deleted IANA Considerations section
* Deleted babel-supported-link-properties and babel-link-
properties in all places3
* Made babel-interface-metric-algorithm rw
* Added boolean rw babel-interface-split-horizon parameter
* Replaced the "k-out-of-j" enumeration for expression of
algorithmic capabilities with "2-out-of-3"
* Calculated and received metrics datatype can be signed int if
needed to represent NULL value
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. 26 change blocks. 
96 lines changed or deleted 55 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/