Interface to the Routing System Problem Statement
draft-ietf-i2rs-problem-statement-04
The information below is for an old version of the document | |||
---|---|---|---|
Document | Type | Expired Internet-Draft (i2rs WG) | |
Last updated | 2014-12-25 (latest revision 2014-06-23) | ||
Replaces | draft-atlas-i2rs-problem-statement | ||
Stream | IETF | ||
Intended RFC status | Informational | ||
Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
Reviews | |||
Stream | WG state | WG Document | |
Document shepherd | Qin Wu | ||
Shepherd write-up | Show (last changed 2014-12-10) | ||
IESG | IESG state | Expired | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | "Qin Wu" <bill.wu@huawei.com> |
https://www.ietf.org/archive/id/draft-ietf-i2rs-problem-statement-04.txt
Abstract
As modern networks grow in scale and complexity, the need for rapid and dynamic control increases. With scale, the need to automate even the simplest operations is important, but even more critical is the ability to quickly interact with more complex operations such as policy-based controls. In order to enable network applications to have access to and control over information in the Internet's routing system, we need a publicly documented interface specification. The interface needs to support real-time, asynchronous interactions using data models and encodings that are efficient and potentially different from those available today. Furthermore, the interface must be tailored to support a variety of use cases. This document expands upon these statements of requirements to provide a detailed problem statement for an Interface to the Routing System (I2RS).
Authors
Alia Atlas
(akatlas@juniper.net)
Thomas Nadeau
(tnadeau@lucidvision.com)
David Ward
(wardd@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)