Interface to the Routing System Problem Statement
draft-atlas-irs-problem-statement-00
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Alia Atlas , Thomas Nadeau , David Ward | ||
Last updated | 2013-02-27 (Latest revision 2012-07-30) | ||
Replaced by | draft-atlas-i2rs-problem-statement | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-atlas-i2rs-problem-statement | |
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 applications to have access to and control over information in the Internet's routing system, we need a publically documented interface specification. The interface needs to support real-time, transaction-based interactions using efficient data models and encodings. Furthermore, the interface must support a variety of use cases including those where verified control feed-back loops are needed. This document expands upon these statements of requirements to provide a problem statement for an interface to the Internet routing system.
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.)