Interface to the Routing System Problem Statement
draft-atlas-i2rs-problem-statement-02
Document | Type |
Replaced Internet-Draft
(candidate for i2rs WG)
Expired & archived
|
|
---|---|---|---|
Authors | Alia Atlas , Thomas Nadeau , David Ward | ||
Last updated | 2013-09-12 (Latest revision 2013-08-14) | ||
Replaces | draft-atlas-irs-problem-statement | ||
Replaced by | draft-ietf-i2rs-problem-statement | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Reviews | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Call For Adoption By WG Issued | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-i2rs-problem-statement | |
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
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
Thomas Nadeau
David Ward
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)