Use Cases for an Interface to BGP Protocol
draft-keyupate-i2rs-bgp-usecases-04

Document Type Expired Internet-Draft (i2rs WG)
Last updated 2015-01-05 (latest revision 2014-07-04)
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Candidate for WG Adoption
Polled for WG adoption but not adopted
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
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-i2rs-bgp-usecases-04.txt

Abstract

A network routing protocol like BGP is typically configured and 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 provides an alternate way to control and diagnose the operation of the BGP protocol. I2RS may be used for the configuration, manipulation, analyzing or collecting the 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 (keyupate@cisco.com)
Rex Fernando (rex@cisco.com)
Hannes Gredler (hannes@juniper.net)
Shane Amante
Russ White (russw@riw.us)
Susan Hares (shares@ndzh.com)

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