draft-ietf-babel-information-model-00.txt   draft-ietf-babel-information-model-01.txt 
Babel routing protocol B. Stark Babel routing protocol B. Stark
Internet-Draft AT&T Internet-Draft AT&T
Intended status: Informational July 3, 2017 Intended status: Informational January 2, 2018
Expires: January 4, 2018 Expires: July 6, 2018
Babel Information Model Babel Information Model
draft-ietf-babel-information-model-00 draft-ietf-babel-information-model-01
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
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 http://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 4, 2018. This Internet-Draft will expire on July 6, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 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
(http://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
1.2. Notation . . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Notation . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Information Model . . . . . . . . . . . . . . . . . . . . 3 2. The Information Model . . . . . . . . . . . . . . . . . . . . 4
2.1. Definition of babel-information . . . . . . . . . . . . . 3 2.1. Definition of babel-information . . . . . . . . . . . . . 4
2.2. Definition of babel-constants . . . . . . . . . . . . . . 4 2.2. Definition of babel-constants . . . . . . . . . . . . . . 4
2.3. Definition of babel-interfaces . . . . . . . . . . . . . 4 2.3. Definition of babel-interfaces . . . . . . . . . . . . . 5
2.4. Definition of babel-neighbors . . . . . . . . . . . . . . 5 2.4. Definition of babel-neighbors . . . . . . . . . . . . . . 6
2.5. Definition of babel-csa . . . . . . . . . . . . . . . . . 5 2.5. Definition of babel-security . . . . . . . . . . . . . . 6
2.6. Definition of babel-sources . . . . . . . . . . . . . . . 6 2.6. Definition of babel-trust . . . . . . . . . . . . . . . . 7
2.7. Definition of babel-routes . . . . . . . . . . . . . . . 6 2.7. Definition of babel-sources . . . . . . . . . . . . . . . 7
3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 2.8. Definition of babel-routes . . . . . . . . . . . . . . . 7
4. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
4.1. Normative References . . . . . . . . . . . . . . . . . . 7 4. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.2. Informative References . . . . . . . . . . . . . . . . . 7 4.1. Normative References . . . . . . . . . . . . . . . . . . 9
Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . 8 4.2. Informative References . . . . . . . . . . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8 Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10
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 6126 [RFC6126] and draft-ietf-babel-rfc6126bis RFC 6126bis [RFC6126bis]. Babel Hashed Message Authentication Code
[babel-rfc6126bis]. Babel Hashed Message Authentication Code (HMAC) (HMAC) Cryptographic Authentication, defined in RFC 7298 [RFC7298],
Cryptographic Authentication, defined in RFC 7298 [RFC7298],
describes a cryptographic authentication mechanism for the Babel describes a cryptographic authentication mechanism for the Babel
routing protocol. This document describes an information model for routing protocol. This document describes an information model for
Babel (including HMAC) that can be used to created management Babel (including HMAC) that can be used to created management
protocol data models (such as a netconf [RFC6241] YANG data model). protocol data models (such as a netconf [RFC6241] YANG data model).
Other Babel extensions may be included in this document when they Other Babel extensions may be included in this document when they
become working group drafts. become working group drafts.
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
skipping to change at page 3, line 20 skipping to change at page 3, line 20
1.2. Notation 1.2. Notation
This document uses a programming language-like notation to define the This document uses a programming language-like notation to define the
properties of the objects of the information model. An optional properties of the objects of the information model. An optional
property is enclosed by square brackets, [ ], and a list property is property is enclosed by square brackets, [ ], and a list property is
indicated by two numbers in angle brackets, <m..n>, where m indicates indicated by two numbers in angle brackets, <m..n>, where m indicates
the minimal number of values, and n is the maximum. The symbol * for the minimal number of values, and n is the maximum. The symbol * for
n means no upper bound. n means no upper bound.
The object definitions use base types that are defined as follows:
base64 An opaque array of bytes.
boolean A type representing a boolean value.
counter A non-negative integer that monotonically increases.
Counters may have discontinuities and they are not
expected to persist across restarts.
credentials An opaque type representing credentials needed by a
cryptographic mechanism to secure communication. Data
models must expand this opaque type as needed and
required by the security protocols utilized.
datetime A type representing a date and time using the Gregorian
calendar. The datetime format MUST conform to RFC 3339
[RFC3339].
int A type representing signed or unsigned integer numbers.
This information model does not define a precision nor
does it make a distinction between signed and unsigned
number ranges. This type is also used to represent
enumerations.
ip-address A type representing an IP address. This type supports
both IPv4 and IPv6 addresses.
string A type representing a human-readable string consisting of
a (possibly restricted) subset of Unicode and ISO/IEC
10646 [ISO.10646] characters.
uri A type representing a Uniform Resource Identifier as
defined in STD 66 [RFC3986].
2. The Information Model 2. The Information Model
2.1. Definition of babel-information 2.1. Definition of babel-information
object { object {
string babel-implementation-version; string babel-implementation-version;
int babel-self-router-id; base64 babel-self-router-id;
[int babel-self-seqno;] [int babel-self-seqno;]
string babel-cost-comp-algorithms<1..*>; string babel-cost-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-sources-obj babel-sources<0..*>;
babel-routes-obj babel-routes<0..*>; babel-routes-obj babel-routes<0..*>;
}babel-information-obj; }babel-information-obj;
babel-version: the version of this implementation of the Babel babel-version: the version of this implementation of the Babel
protocol protocol
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 Babel protocol to identify itself; RFC 6126bis [RFC6126bis]
describes this as an arbitrary string of 8 octets
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-cost-comp-algorithm: 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
skipping to change at page 4, line 4 skipping to change at page 4, line 42
babel-cost-comp-algorithm: a set of names of supported cost babel-cost-comp-algorithm: 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-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
2.2. Definition of babel-constants 2.2. Definition of babel-constants
object { object {
int babel-udp-port; int babel-udp-port;
[int babel-multicast-group-ipv6;] [ip-address babel-multicast-group-ipv6;]
[int babel-multicast-group-ipv4;] [ip-address babel-multicast-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-multicast-group-ipv6: multicast group for sending and
listening to multicast announcements on IPv6; default is listening to multicast announcements on IPv6; default is
ff02:0:0:0:0:0:1:6; MAY be configurable ff02:0:0:0:0:0:1:6; MAY be configurable
babel-multicast-group-ipv4: multicast group for sending and babel-multicast-group-ipv4: multicast group for sending and
skipping to change at page 4, line 36 skipping to change at page 5, line 27
object { object {
uri babel-interface-reference; uri babel-interface-reference;
[int babel-interface-seqno;] [int babel-interface-seqno;]
[int babel-interface-hello-interval;] [int babel-interface-hello-interval;]
[int babel-interface-update-interval;] [int babel-interface-update-interval;]
boolean babel-request-trigger-ack; boolean babel-request-trigger-ack;
boolean babel-lossy-link; boolean babel-lossy-link;
[int babel-external-cost;] [int babel-external-cost;]
babel-neighbors-obj babel-neighbors<1..*>; babel-neighbors-obj babel-neighbors<1..*>;
[babel-csa-obj babel-csa<1..*>;] [babel-security-obj babel-security<1..*>;]
}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
babel-interface-seqno: the current sequence number in use for this babel-interface-seqno: the current sequence number in use for this
interface interface
babel-interface-hello-interval: the current hello interval in use babel-interface-hello-interval: the current hello interval in use
for this interface for this interface
skipping to change at page 5, line 18 skipping to change at page 6, line 8
babel-lossy-link: indicates (if true) that the link of this babel-lossy-link: indicates (if true) that the link of this
interface is considered lossy; MAY be configurable interface is considered lossy; MAY be configurable
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 2.4. Definition of babel-neighbors
object { object {
some address format babel-neighbor-address; ip-address babel-neighbor-address;
string babel-hello-history; string babel-hello-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]
}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-history: the Hello history (do we want a human
readable format?) readable format?)
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 FFFF hexadecimal (infinity) if the received from this neighbor, or meximum value (infinity) to
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-router-id: router-id of the neighbor
babel-rxcost: reception cost calculated for this neighbor babel-rxcost: reception cost calculated for this neighbor
2.5. Definition of babel-csa 2.5. Definition of babel-security
object { object {
string placeholder; string babel-security-supported;
}babel-csa-obj; string babel-security-enabled-protocol;
credentials babel-security-self-cred;
babel-trust-obj babel-trust<1..*>;
}babel-security-obj;
placeholder: this section to be filled in, in the future babel-security-supported: list of supported security mechanisms
2.6. Definition of babel-sources babel-security-enabled-protocol: the currently enabled security
protocol; empty if none is enabled
babel-security-self-cred: the credentials this router presents to
participate in the enabled security protocol
babel-trust-obj: a set of babel-trust objects that identify the
credentials of a router whose babel messages are trusted
2.6. Definition of babel-trust
object { object {
(prefix, plen) babel-source-prefix; credentials babel-trust-cred;
int babel-source-router-id; }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-seqno;
int babel-source-metric; int babel-source-metric;
[int babel-source-garbage-collection-time;] [int babel-source-garbage-collection-time;]
}babel-sources-obj; }babel-sources-obj;
babel-source-prefix: Prefix (with prefix length) 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-source-router-id: router-id of the router originating this
prefix prefix
babel-source-seqno: last sequence number used by this source babel-source-seqno: last sequence number used by this source
babel-source-metric: this source's feasibility distance babel-source-metric: this source's feasibility distance
babel-source-garbage-collection-time: garbage-collection timer for babel-source-garbage-collection-time: garbage-collection timer for
this source this source
2.7. Definition of babel-routes 2.8. Definition of babel-routes
object { object {
(prefix, plen) babel-route-prefix; ip-address babel-route-prefix;
int babel-route-router-id; int babel-route-prefix-length;
int babel-route-neighbor; base64 babel-route-router-id;
base64 babel-route-neighbor;
int babel-route-metric; int babel-route-metric;
int babel-route-seqno; int babel-route-seqno;
ip address babel-route-next-hop; ip-address babel-route-next-hop;
boolean babel-route-selected; boolean babel-route-selected;
}babel-routes-obj; }babel-routes-obj;
babel-route-prefix: Prefix (with prefix length) for which this babel-route-prefix: Prefix (expressed in IP address format) for
which this route is advertised
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 router originating this babel-route-router-id: router-id of the source router for which
prefix this route is advertised
babel-route-neighbor: neighbor that advertised this route (is this babel-route-neighbor: neighbor that advertised this route (a
a router-id ?) 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 FFFF hexadecimal (infinity) for a advertised by the neighbor, or maximum value (infinity) to
recently retracted route indicate a recently retracted route
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
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 3. Acknowledgements
This information model was originally derived from RFC 6126 Juliusz Chroboczek review has been very helpful in refining this
[RFC6126]. That model is being modified according to draft-ietf- information model.
babel-rfc6126bis [babel-rfc6126bis]. Juliusz Chroboczek review has
been very helpful in refing this information model. The language in the Notation section was mostly taken from RFC 8193
[RFC8193].
4. References 4. References
4.1. Normative References 4.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,
<http://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC6126bis]
Chroboczek, J., "The Babel Routing Protocol", Work in
Progress, draft-ietf-babel-rfc6126bis, October 2017.
4.2. Informative References 4.2. Informative References
[babel-rfc6126bis] [ISO.10646]
Chroboczek, J., "The Babel Routing Protocol", Work in International Organization for Standardization,
Progress, draft-ietf-babel-rfc6126bis, May 2017. "Information Technology - Universal Multiple-Octet Coded
Character Set (UCS)", ISO Standard 10646:2014, 2014.
[RFC6126] Chroboczek, J., "The Babel Routing Protocol", RFC 6126, [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet:
DOI 10.17487/RFC6126, April 2011, Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002,
<http://www.rfc-editor.org/info/rfc6126>. <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>.
[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,
<http://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC7298] Ovsienko, D., "Babel Hashed Message Authentication Code [RFC7298] Ovsienko, D., "Babel Hashed Message Authentication Code
(HMAC) Cryptographic Authentication", RFC 7298, (HMAC) Cryptographic Authentication", RFC 7298,
DOI 10.17487/RFC7298, July 2014, DOI 10.17487/RFC7298, July 2014,
<http://www.rfc-editor.org/info/rfc7298>. <https://www.rfc-editor.org/info/rfc7298>.
[RFC8193] Burbridge, T., Eardley, P., Bagnulo, M., and J.
Schoenwaelder, "Information Model for Large-Scale
Measurement Platforms (LMAPs)", RFC 8193,
DOI 10.17487/RFC8193, August 2017,
<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.
Following are some issues where a conscious decision may be useful: Following are some issues where a conscious decision may be useful:
babel-self-router-id: Should this be an opaque 64-bit value Closed by defining base64 type and using it for all router IDs:
instead of int? "babel-self-router-id: Should this be an opaque 64-bit value
instead of int?"
Would it be useful to define any of the following as per-interface
constants: hello-interval-lossy, hello-interval-lossless, ihu-
interval, update-interval, ihu-hold-time, route-expiry-time,
garbage-collection-time, max-trigger-delay, max-normal-delay, ack-
limit, resend-trigger-lossy-limit, resend-trigger-lossless-limit,
resend-normal-lossy-limit, resend-normal-lossless-limit
babel-interfaces-obj: "This needs further discussion, I fear some babel-interfaces-obj: "This needs further discussion, I fear some
of these are implementation details." of these are implementation details."
Would it be useful to define some parameters for reporting Would it be useful to define some parameters for reporting
statistics or logs? statistics or logs? [Yes, but these need to be proposed.]
Would it be useful to define some parameters specifically for Would it be useful to define some parameters specifically for
security anomalies? security anomalies? [Yes, but these need to be proposed.]
I created a basic security model. It's useful for single (or no)
active security mechanism; but not multiple active. OK?
Do we need a registry for the supported security mechanisms?
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. 39 change blocks. 
76 lines changed or deleted 156 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/