<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-i2rs-problem-statement" target="https://datatracker.ietf.org/doc/html/draft-ietf-i2rs-problem-statement-02">
   <front>
      <title>Interface to the Routing System Problem Statement</title>
      <author initials="A." surname="Atlas" fullname="Alia Atlas">
         </author>
      <author initials="T." surname="Nadeau" fullname="Thomas Nadeau">
         </author>
      <author initials="D." surname="Ward" fullname="David Ward">
         </author>
      <date month="June" day="6" year="2014" />
      <abstract>
	 <t>   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&#x27;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).

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-i2rs-problem-statement-02" />
   
</reference>
