A Data Model for Network Instances in Service Provider Networks

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-10-19
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
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                                          R. Shakir
Internet-Draft                                       Jive Communications
Intended status: Informational                          October 19, 2015
Expires: April 21, 2016

    A Data Model for Network Instances in Service Provider Networks


   This document defines a YANG data model for configuring and managing
   forwarding instances on a network device - focused primarily on
   deployments in service provider networks.  The model is vendor-
   neutral and based on operational requirements expressed by operators.
   A 'network instance' is defined to be a discrete forwarding table on
   a network element, which contains Layer 3 and/or Layer 2 forwarding
   entries.  Each network instance may instantiate its own sets of
   protocols which control installation of forwarding entries into one
   or more tables (which may be Layer 2 FIBs, or Layer 3 RIBs).

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 April 21, 2016.

Copyright Notice

   Copyright (c) 2015 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

Shakir                   Expires April 21, 2016                 [Page 1]
Internet-Draft           Network Instance Model             October 2015

   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.

1.  Introduction

   Within service provider networks, it is typical for a network element
   to maintain multiple forwarding tables, allowing the network to
   support multiple topologies.  For instance, a service provider may
   offer Layer 2 or Layer 3 VPN services to its customers - which
   requires a forwarding table per customer to be maintained on a
   network element.  In other cases, multiple L3 services may be
   deployed to allow services such as Internet connectivity and private
   topologies to be maintained on a device.

   This YANG [RFC6020] data model defines a construct which can be used
   to configure and retrieve operational state related to such

1.1.  Goals and Approach

   The concept of maintaining multiple Layer 2 virtual switch instances
   (VSIs) and/or multiple Layer 3 virtual routing and forwarding (VRF)
   tables is common on network elements that are deployed in service
   provider networks.  However, within such networks there are
   requirements for a network instance to run both Layer 2 and Layer 3
   routing protocols, or contain routed interfaces (e.g., a VPLS service
   where there is a Layer 3 interface within it, for subscriber
   termination or to act as a default gateway).  For this reason, the
   intention of the model presented here is to define a generic
   construct which allows isolation of a forwarding table which may
   contain Layer 3 RIB entries, Layer 2 FIB entries, or a combination
   both.  This differs to the approach taken in other models, which tend
   to focus on solely L2 VSIs or L3 VRFs.  An instance within the model
   is referred to as network instance - and may be configured to support
   L3 RIB entries only (i.e., be functionally equivalent to a VRF), L2
   FIB entries only (i.e., act as a VSI) or support a combination of

   The model presented in this document is explicitly biased towards
   deployments on service provider network equipment, as discussed
   between members of the OpenConfig project.

Shakir                   Expires April 21, 2016                 [Page 2]
Internet-Draft           Network Instance Model             October 2015

2.  Model overview

   module: openconfig-network-instance
      +--rw network-instances
         +--rw network-instance* [name]
            +--rw name                       -> ../config/name
            +--rw config
            +--ro state
Show full document text