RFC 7920 on Problem Statement for the Interface to the Routing System
rfc-editor@rfc-editor.org Thu, 30 June 2016 17:44 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC1C512D935; Thu, 30 Jun 2016 10:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.328
X-Spam-Level:
X-Spam-Status: No, score=-108.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oc2TyKwZ8J3W; Thu, 30 Jun 2016 10:44:06 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C4FA12D89B; Thu, 30 Jun 2016 10:44:03 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 45A3FB80B9B; Thu, 30 Jun 2016 10:44:03 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7920 on Problem Statement for the Interface to the Routing System
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160630174403.45A3FB80B9B@rfc-editor.org>
Date: Thu, 30 Jun 2016 10:44:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/liOOIZIiJen-PG_csmcxUUPtkyE>
Cc: i2rs@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2016 17:44:09 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7920
Title: Problem Statement for the Interface
to the Routing System
Author: A. Atlas, Ed.,
T. Nadeau, Ed.,
D. Ward
Status: Informational
Stream: IETF
Date: June 2016
Mailbox: akatlas@juniper.net,
tnadeau@lucidvision.com,
wardd@cisco.com
Pages:
Characters: 28441
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-i2rs-problem-statement-11.txt
URL: https://www.rfc-editor.org/info/rfc7920
DOI: http://dx.doi.org/10.17487/RFC7920
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.
Requirements have emerged to more dynamically manage and program
routing systems due to 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. These
requirements should allow controlling routing information and traffic
paths and extracting 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).
This document is a product of the Interface to the Routing System Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC