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

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Authors Keyur Patel  , Rex Fernando  , Hannes Gredler  , Shane Amante 
Last updated 2013-04-24 (latest revision 2012-10-21)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-keyupate-irs-bgp-usecases-01.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 state and debugging of the protocol. Interface to the Routing System's (IRS) Programmatic 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 set of use cases for which IRS can be used for BGP protocol. It is intended to provide a base for the solution draft describing a set of interfaces to the BGP protocol.

Authors

Keyur Patel (keyupate@cisco.com)
Rex Fernando (rex@cisco.com)
Hannes Gredler (hannes@juniper.net)
Shane Amante (shane@level3.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)