Babel Information Model
draft-ietf-babel-information-model-04

Document Type Active Internet-Draft (babel WG)
Last updated 2018-10-22
Replaces draft-stark-babel-information-model
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Reviews
Stream WG state WG Document (wg milestone: Sep 2018 - IESG Submission of B... )
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Babel routing protocol                                          B. Stark
Internet-Draft                                                      AT&T
Intended status: Informational                          October 22, 2018
Expires: April 25, 2019

                        Babel Information Model
                 draft-ietf-babel-information-model-04

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 https://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 April 25, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (https://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 April 25, 2019                 [Page 1]
Internet-Draft           Babel Information Model            October 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Notation  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  The Information Model . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Definition of babel-information-obj . . . . . . . . . . .   5
     3.2.  Definition of babel-constants-obj . . . . . . . . . . . .   6
     3.3.  Definition of babel-interfaces-obj  . . . . . . . . . . .   7
     3.4.  Definition of babel-neighbors-obj . . . . . . . . . . . .   8
     3.5.  Definition of babel-security-obj  . . . . . . . . . . . .  10
     3.6.  Definition of babel-routes-obj  . . . . . . . . . . . . .  11
   4.  Common Objects  . . . . . . . . . . . . . . . . . . . . . . .  12
     4.1.  Definition of babel-credential-obj  . . . . . . . . . . .  12
     4.2.  Definition of babel-log-obj . . . . . . . . . . . . . . .  13
   5.  Extending the Information Model . . . . . . . . . . . . . . .  13
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  15
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  15
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  15
   Appendix A.  Open Issues  . . . . . . . . . . . . . . . . . . . .  17
   Appendix B.  Change Log . . . . . . . . . . . . . . . . . . . . .  19
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  21

1.  Introduction

   Babel is a loop-avoiding distance-vector routing protocol defined in
   [I-D.ietf-babel-rfc6126bis].  [I-D.ietf-babel-hmac] defines a
   security mechanism that allows Babel messages to be cryptographically
   authenticated, and [I-D.ietf-babel-dtls] defines a security mechanism
   that allows Babel messages to be encrypted.  This document describes
   an information model for Babel (including implementations using one
   of these security mechanisms) that can be used to create management
   protocol data models (such as a NETCONF [RFC6241] YANG [RFC7950] data
   model).

   Due to the simplicity of the Babel protocol, most of the information
   model is focused on reporting Babel protocol operational state, and
   very little of that is considered mandatory to implement (contingent
   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
Show full document text