Use Cases for an Interface to BGP Protocol
draft-keyupate-i2rs-bgp-usecases-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Keyur Patel , Rex Fernando , Hannes Gredler , Shane Amante | ||
| Last updated | 2013-09-12 (Latest revision 2013-03-11) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 (I2RS) Programmatic interfaces, as defined in [I-D.ward-i2rs-framework], provides an alternate way to control the configuration and diagnose the operation of the BGP protocol. I2RS may be used for the configuration, manipulation, polling or analyzing protocol data. This document describes set of use cases for which I2RS 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
Rex Fernando
Hannes Gredler
Shane Amante
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)