Use Cases for an Interface to BGP Protocol
draft-keyupate-irs-bgp-usecases-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Authors Keyur Patel  , Hannes Gredler  , Rex Fernando  , Shane Amante 
Last updated 2012-10-14
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                                           K. Patel
Internet-Draft                                             Cisco Systems
Intended status: Informational                                H. Gredler
Expires: April 17, 2013                                 Juniper Networks
                                                             R. Fernando
                                                           Cisco Systems
                                                               S. Amante
                                            Level 3 Communications, Inc.
                                                        October 14, 2012

               Use Cases for an Interface to BGP Protocol
                 draft-keyupate-irs-bgp-usecases-00.txt

Abstract

   A network routing protocol like BGP is typically configured and
   results of its operation are analyzed through some form of Command
   Line Interface (CLI) or NETCONF.  These interactions to control BGP
   and diagnose its operation encompass: configuration of protocol
   parameters, display of protocol data, setting of certain protocol
   states and debugging of the protocol.

   Interface to the Routing System's (IRS) Programatic interfaces, as
   defined in [I-D.ward-irs-framework], provides an alternate way to
   control the configuration and diagnose the operation of the BGP
   protocol.  IRS may be used for the configuration, manipulation,
   polling or analyzing protocol data.  This document describes a set of
   use cases for which IRS can be used for BGP protocol.  It is indended
   to provide a base for the solution draft descibring a set of
   Interfaces to the BGP protocol.

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 17, 2013.

Patel, et al.            Expires April 17, 2013                 [Page 1]
Internet-Draft      Use Cases for an Interface to BGP       October 2012

Copyright Notice

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

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Patel, et al.            Expires April 17, 2013                 [Page 2]
Internet-Draft      Use Cases for an Interface to BGP       October 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Requirements Language  . . . . . . . . . . . . . . . . . .  4
   2.  BGP Configuration  . . . . . . . . . . . . . . . . . . . . . .  4
     2.1.  BGP Protocol Configuration . . . . . . . . . . . . . . . .  5
     2.2.  BGP Policy Configuration . . . . . . . . . . . . . . . . .  6
   3.  BGP Protocol Operation . . . . . . . . . . . . . . . . . . . .  8
     3.1.  BGP Error Handling for Internal BGP Sessions . . . . . . .  8
     3.2.  Tracing Dropped BGP Routes . . . . . . . . . . . . . . . .  8
   4.  BGP Route Manipulation . . . . . . . . . . . . . . . . . . . .  9
     4.1.  Customized Best Path Selection Criteria  . . . . . . . . .  9
Show full document text