RFC 7491 on A PCE-Based Architecture for Application-Based Network Operations

rfc-editor@rfc-editor.org Sun, 22 March 2015 16:33 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 (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id D3D6F1A8A63 for <ietf-announce@ietfa.amsl.com>; Sun, 22 Mar 2015 09:33:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id CtFExaFgvJps for <ietf-announce@ietfa.amsl.com>; Sun, 22 Mar 2015 09:33:57 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 9884B1A8A3C for <ietf-announce@ietf.org>; Sun, 22 Mar 2015 09:33:57 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4CED3180092; Sun, 22 Mar 2015 09:32:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7491 on A PCE-Based Architecture for Application-Based Network Operations
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150322163235.4CED3180092@rfc-editor.org>
Date: Sun, 22 Mar 2015 09:32:35 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/PEyjY8zA2PRhk_1zrpbD9ACISZY>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sun, 22 Mar 2015 16:34:00 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 7491

        Title:      A PCE-Based Architecture for Application-Based 
                    Network Operations 
        Author:     D. King, A. Farrel
        Status:     Informational
        Stream:     IETF
        Date:       March 2015
        Mailbox:    daniel@olddog.co.uk, 
        Pages:      71
        Characters: 163636
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-farrkingel-pce-abno-architecture-16.txt

        URL:        https://www.rfc-editor.org/info/rfc7491

Services such as content distribution, distributed databases, or
inter-data center connectivity place a set of new requirements on the
operation of networks.  They need on-demand and application-specific
reservation of network connectivity, reliability, and resources (such
as bandwidth) in a variety of network applications (such as
point-to-point connectivity, network virtualization, or mobile
back-haul) and in a range of network technologies from packet
(IP/MPLS) down to optical.  An environment that operates to meet
these types of requirements is said to have Application-Based
Network Operations (ABNO).  ABNO brings together many existing
technologies and may be seen as the use of a toolbox of existing
components enhanced with a few new elements.

This document describes an architecture and framework for ABNO,
showing how these components fit together.  It provides a cookbook of
existing technologies to satisfy the architecture and meet the needs
of the applications.

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

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

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