BGP Configuration Model for Service Provider Networks

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-10-26
Replaced by draft-ietf-idr-bgp-model
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized 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                                          A. Shaikh
Internet-Draft                                                    Google
Intended status: Informational                                K. D'Souza
Expires: April 29, 2015                                             AT&T
                                                               D. Bansal
                                                               R. Shakir
                                                        October 26, 2014

         BGP Configuration Model for Service Provider Networks


   This document defines a YANG data model for configuring and managing
   BGP, including protocol, policy, and operational aspects based on
   carrier and content provider operational requirements.

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 April 29, 2015.

Copyright Notice

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

Shaikh, et al.           Expires April 29, 2015                 [Page 1]
Internet-Draft           BGP Configuration Model            October 2014

   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

   This document describes a YANG [RFC6020] data model for BGP [RFC4271]
   protocol and policy configuration, as well as defining key
   operational state data.  The model is intended to be vendor-neutral,
   in order to allow operators to manage BGP configuration in
   heterogeneous environments with routers supplied by multiple vendors.
   The model is also intended to be readily mapped to existing
   implementations, however, to facilitate support from as large a set
   of routing hardware and software vendors as possible.

1.1.  Goals and approach

   This model does not (in the current iteration) aim to be feature
   complete (i.e., cover all possible features of a BGP implementation).
   Rather its development is driven by examination of BGP configurations
   in use across a number of operator network deployments.

   The focus area of the first version of the model is on base BGP
   protocol configuration and policy configuration with "hooks" to add
   support for additional address families, as well as operational data
   to enable a common model for reading BGP-related state from devices.

   Configuration items that are deemed to be widely available in
   existing major BGP implementations are included in the model.  Those
   configuration items that are only available from a single
   implementation are omitted from the model with the expectation they
   will be available in companion modules that augment the current
   model.  This allows clarity in identifying data that is part of the
   vendor-neutral model.

   Where possible, naming in the model follows conventions used in
   available standards documents, and otherwise tries to be self-
   explanatory with sufficient descriptions of the intended behavior.
   Similarly, configuration data value constraints and default values,
   where used, are based on recommendations in current standards
   documentation.  Since implementations vary widely in this respect,
   this version of the model specifies only a limited set of defaults
   and ranges with the expectation of being more prescriptive in future
   versions based on actual operator use.

Shaikh, et al.           Expires April 29, 2015                 [Page 2]
Internet-Draft           BGP Configuration Model            October 2014

2.  Model overview

   The BGP model is defined across several YANG modules but at a high
   level is organized into three main parts:
Show full document text