Last Call: <draft-farrkingel-pce-abno-architecture-13.txt> (A PCE-based Architecture for Application-based Network Operations) to Informational RFC

The IESG <iesg-secretary@ietf.org> Fri, 12 December 2014 22:44 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C62EF1A0120 for <ietf-announce@ietfa.amsl.com>; Fri, 12 Dec 2014 14:44:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
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 tBRBsMR7t1T1 for <ietf-announce@ietfa.amsl.com>; Fri, 12 Dec 2014 14:44:51 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D5A51A000D for <ietf-announce@ietf.org>; Fri, 12 Dec 2014 14:44:51 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-farrkingel-pce-abno-architecture-13.txt> (A PCE-based Architecture for Application-based Network Operations) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20141212224451.25381.34211.idtracker@ietfa.amsl.com>
Date: Fri, 12 Dec 2014 14:44:51 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/csxc7cRCfXOU2q_pc51GGW-9sCs
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 12 Dec 2014 22:44:53 -0000

The IESG has received a request from an individual submitter to consider
the following document:
- 'A PCE-based Architecture for Application-based Network Operations'
  <draft-farrkingel-pce-abno-architecture-13.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2015-01-09. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   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.  Additionally, existing services or capabilities like
   pseudowire connectivity or global concurrent optimization can benefit
   from a operational scheme that considers the application needs and
   the network status.  An environment that operates to meet these types
   of requirement is said to have Application-Based Network Operations
   (ABNO).

   ABNO brings together many existing technologies for gathering
   information about the resources available in a network, for
   consideration of topologies and how those topologies map to
   underlying network resources, for requesting path computation, and
   for provisioning or reserving network resources.  Thus, ABNO may be
   seen as the use of a toolbox of existing components enhanced with a
   few new elements.  The key component within an ABNO is the Path
   Computation Element (PCE), which can be used for computing paths and
   is further extended to provide policy enforcement capabilities for
   ABNO.

   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.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-farrkingel-pce-abno-architecture/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-farrkingel-pce-abno-architecture/ballot/


No IPR declarations have been submitted directly on this I-D.