Interface to the Routing System Problem Statement
draft-atlas-irs-problem-statement-00

 
Document Type Replaced Internet-Draft (individual)
Last updated 2013-02-27 (latest revision 2012-07-30)
Replaced by draft-atlas-i2rs-problem-statement
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-atlas-i2rs-problem-statement
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

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-atlas-irs-problem-statement-00.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 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 (akatlas@juniper.net)
Tom Nadeau (tnadeau@juniper.net)
David Ward (wardd@cisco.com)

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