Babel routing protocol B. Stark
Internet-Draft AT&T
Intended status: Informational July 3, 2017
Expires: January 4, 2018

Babel Information Model


This Babel Information Model can be used to create data models under various data modeling regimes (e.g., YANG). It allows a Babel implementation (via a management protocol such as netconf) to report on its current state and may allow some limited configuration of protocol constants.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on January 4, 2018.

Copyright Notice

Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents ( in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

1. Introduction

Babel is a loop-avoiding distance-vector routing protocol defined in RFC 6126 and draft-ietf-babel-rfc6126bis. Babel Hashed Message Authentication Code (HMAC) Cryptographic Authentication, defined in RFC 7298, describes a cryptographic authentication mechanism for the Babel routing protocol. This document describes an information model for Babel (including HMAC) that can be used to created management protocol data models (such as a netconf [RFC6241] YANG data model). Other Babel extensions may be included in this document when they become working group drafts.

Due to the simplicity of the Babel protocol and the fact that it is designed to be used in non-professionally administered environments (such as home networks), most of the information model is focused on reporting status of the Babel protocol, and very little of that is considered mandatory to implement (conditional on a management protocol with Babel support being implemented). Some parameters may be configurable; however, it is up to the Babel implementation whether to allow any of these to be configured within its implementation. Where the implementation does not allow configuration of these parameters, it may still choose to expose them as read-only.

1.1. Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

1.2. Notation

This document uses a programming language-like notation to define the properties of the objects of the information model. An optional property is enclosed by square brackets, [ ], and a list property is 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 n means no upper bound.

2. The Information Model

2.1. Definition of babel-information

     object {
          string                babel-implementation-version;
          int                   babel-self-router-id;
         [int                   babel-self-seqno;]
          string                babel-cost-comp-algorithms<1..*>;
          babel-constants-obj   babel-constants;
          babel-interfaces-obj  babel-interfaces<0..*>;
          babel-sources-obj     babel-sources<0..*>;
          babel-routes-obj      babel-routes<0..*>;

2.2. Definition of babel-constants

     object {
          int          babel-udp-port;
         [int          babel-multicast-group-ipv6;]
         [int          babel-multicast-group-ipv4;]

2.3. Definition of babel-interfaces

     object {
          uri                  babel-interface-reference;
         [int                  babel-interface-seqno;]
         [int                  babel-interface-hello-interval;]
         [int                  babel-interface-update-interval;]
          boolean              babel-request-trigger-ack;
          boolean              babel-lossy-link;
         [int                  babel-external-cost;]
          babel-neighbors-obj  babel-neighbors<1..*>;
         [babel-csa-obj        babel-csa<1..*>;]

2.4. Definition of babel-neighbors

     object {
          some address format  babel-neighbor-address;
          string               babel-hello-history;
          int                  babel-txcost;
          int                  babel-hello-seqno;
          int                  babel-neighbor-ihu-interval;
         [int                  babel-rxcost]

2.5. Definition of babel-csa

     object {
          string               placeholder;

2.6. Definition of babel-sources

     object {
          (prefix, plen)       babel-source-prefix;
          int                  babel-source-router-id;
          int                  babel-source-seqno;
          int                  babel-source-metric;
         [int                  babel-source-garbage-collection-time;]

2.7. Definition of babel-routes

     object {
          (prefix, plen)       babel-route-prefix;
          int                  babel-route-router-id;
          int                  babel-route-neighbor;
          int                  babel-route-metric;
          int                  babel-route-seqno;
          ip address           babel-route-next-hop;
          boolean              babel-route-selected;

3. Acknowledgements

This information model was originally derived from RFC 6126. That model is being modified according to draft-ietf-babel-rfc6126bis. Juliusz Chroboczek review has been very helpful in refing this information model.

4. References

4.1. Normative References

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997.

4.2. Informative References

[babel-rfc6126bis] Chroboczek, J., "The Babel Routing Protocol", Work in Progress, draft-ietf-babel-rfc6126bis, May 2017.
[RFC6126] Chroboczek, J., "The Babel Routing Protocol", RFC 6126, DOI 10.17487/RFC6126, April 2011.
[RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J. and A. Bierman, "Network Configuration Protocol (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011.
[RFC7298] Ovsienko, D., "Babel Hashed Message Authentication Code (HMAC) Cryptographic Authentication", RFC 7298, DOI 10.17487/RFC7298, July 2014.

Appendix A. Open Issues

This draft must be reviewed against draft-ietf-babel-rfc6126bis.

Following are some issues where a conscious decision may be useful:

Author's Address

Barbara Stark AT&T Atlanta, GA, US EMail: