[i2rs] I-D Action: draft-ietf-i2rs-problem-statement-10.txt

internet-drafts@ietf.org Fri, 12 February 2016 17:15 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: i2rs@ietf.org
Delivered-To: i2rs@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DF0241A70E2; Fri, 12 Feb 2016 09:15:11 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.14.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160212171511.22650.88015.idtracker@ietfa.amsl.com>
Date: Fri, 12 Feb 2016 09:15:11 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/JfOdFEPWPc3RI_fuNu0XE_vNklE>
Cc: i2rs@ietf.org
Subject: [i2rs] I-D Action: draft-ietf-i2rs-problem-statement-10.txt
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Feb 2016 17:15:12 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Interface to the Routing System of the IETF.

        Title           : Interface to the Routing System Problem Statement
        Authors         : Alia Atlas
                          Thomas D. Nadeau
                          Dave Ward
	Filename        : draft-ietf-i2rs-problem-statement-10.txt
	Pages           : 11
	Date            : 2016-02-12

Abstract:
   Traditionally, routing systems have implemented routing and signaling
   (e.g.  MPLS) to control traffic forwarding in a network.  Route
   computation has been controlled by relatively static policies that
   define link cost, route cost, or import and export routing policies.
   With the advent of highly dynamic data center networking, on-demand
   WAN services, dynamic policy-driven traffic steering and service
   chaining, the need for real-time security threat responsiveness via
   traffic control, and a paradigm of separating policy-based decision-
   making from the router itself, the need has emerged to more
   dynamically manage and program routing systems in order to control
   routing information and traffic paths and to extract network topology
   information, traffic statistics, and other network analytics from
   routing systems.

   This document proposes meeting this need via an Interface to the
   Routing System (I2RS).


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-i2rs-problem-statement/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-i2rs-problem-statement-10

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-i2rs-problem-statement-10


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/