Babel Information Model
draft-ietf-babel-information-model-00
Babel routing protocol B. Stark
Internet-Draft AT&T
Intended status: Informational July 3, 2017
Expires: January 4, 2018
Babel Information Model
draft-ietf-babel-information-model-00
Abstract
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 http://datatracker.ietf.org/drafts/current/.
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
(http://trustee.ietf.org/license-info) 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.
Stark Expires January 4, 2018 [Page 1]
Internet-Draft Babel Information Model July 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
1.2. Notation . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Information Model . . . . . . . . . . . . . . . . . . . . 3
2.1. Definition of babel-information . . . . . . . . . . . . . 3
2.2. Definition of babel-constants . . . . . . . . . . . . . . 4
2.3. Definition of babel-interfaces . . . . . . . . . . . . . 4
2.4. Definition of babel-neighbors . . . . . . . . . . . . . . 5
2.5. Definition of babel-csa . . . . . . . . . . . . . . . . . 5
2.6. Definition of babel-sources . . . . . . . . . . . . . . . 6
2.7. Definition of babel-routes . . . . . . . . . . . . . . . 6
3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
4. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.1. Normative References . . . . . . . . . . . . . . . . . . 7
4.2. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
Babel is a loop-avoiding distance-vector routing protocol defined in
RFC 6126 [RFC6126] and draft-ietf-babel-rfc6126bis
[babel-rfc6126bis]. Babel Hashed Message Authentication Code (HMAC)
Cryptographic Authentication, defined in RFC 7298 [RFC7298],
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
Show full document text