A YANG Data Model for Network Bridge Management
draft-vassilev-netmod-network-bridge-00

Document Type Active Internet-Draft (individual)
Last updated 2018-07-14
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Yang Validation 170 errors, 2 warnings.
Additional URLs
- Yang catalog entry for example-bridge@2018-07-15.yang
- Yang catalog entry for ietf-network-bridge-flows@2018-07-15.yang
- Yang catalog entry for ietf-network-bridge-scheduler@2018-07-15.yang
- Yang catalog entry for ietf-network-bridge@2018-07-15.yang
- Yang impact analysis for draft-vassilev-netmod-network-bridge
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        V. Vassilev
Internet-Draft                                               Transpacket
Intended status: Standards Track                           July 14, 2018
Expires: January 15, 2019

            A YANG Data Model for Network Bridge Management
                draft-vassilev-netmod-network-bridge-00

Abstract

   This document introduces new YANG model of a network bridge.

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 January 15, 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.

Vassilev                Expires January 15, 2019                [Page 1]
Internet-Draft              NETWORK-BIRDGE-00                  July 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
       1.1.1.  YANG  . . . . . . . . . . . . . . . . . . . . . . . .   2
       1.1.2.  Tree Diagrams . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Problem Statement . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Solution  . . . . . . . . . . . . . . . . . . . . . . . .   3
       1.3.1.  Forwarding  . . . . . . . . . . . . . . . . . . . . .   3
       1.3.2.  Scheduling  . . . . . . . . . . . . . . . . . . . . .   4
   2.  Network Bridge Module Tree Diagram  . . . . . . . . . . . . .   6
   3.  Network Bridge Flows Module Tree Diagram  . . . . . . . . . .   6
   4.  Network Bridge Scheduler Module Tree Diagram  . . . . . . . .   9
   5.  Network Bridge Module YANG  . . . . . . . . . . . . . . . . .  11
   6.  Network Bridge Flows Module YANG  . . . . . . . . . . . . . .  12
   7.  Network Bridge Scheduler Module YANG  . . . . . . . . . . . .  19
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  27
     8.1.  NETWORK BRIDGE YANG Modules . . . . . . . . . . . . . . .  27
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  28
   10. Normative References  . . . . . . . . . . . . . . . . . . . .  28
   Appendix A.  Example  . . . . . . . . . . . . . . . . . . . . . .  29
     A.1.  Model . . . . . . . . . . . . . . . . . . . . . . . . . .  29
     A.2.  Scheduler diagram . . . . . . . . . . . . . . . . . . . .  31
     A.3.  Topology  . . . . . . . . . . . . . . . . . . . . . . . .  32
     A.4.  CLI listing . . . . . . . . . . . . . . . . . . . . . . .  32
     A.5.  Configuration Data Instance . . . . . . . . . . . . . . .  34
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  44

1.  Introduction

   There is a need for a YANG model for management of network bridges.
   The model should allow the variety of existing forwarding and
   scheduling technologies to be defined as interoperable modules that
   can be interconnected and extended.

1.1.  Terminology

   The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14, [RFC2119].

1.1.1.  YANG

   The following terms are defined in [RFC7950]:

   o  must statement

Vassilev                Expires January 15, 2019                [Page 2]
Internet-Draft              NETWORK-BIRDGE-00                  July 2018

   o  augment statement

   o  context node

   o  container

   o  data node

   o  key leaf

   o  leaf

   o  leaf-list

   o  list

1.1.2.  Tree Diagrams

   Tree diagrams used in this document follow the notation defined in
   [RFC8340].

1.2.  Problem Statement

   This document attempts to address the problem of defining YANG model
   of a network bridge that can be used as common framework by different
Show full document text