Document Action: 'A PCE-based Architecture for Application-based Network Operations' to Informational RFC (draft-farrkingel-pce-abno-architecture-16.txt)

The IESG <> Wed, 28 January 2015 21:14 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 032D81A005C for <>; Wed, 28 Jan 2015 13:14:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -101.9
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id qQqX912Y5738; Wed, 28 Jan 2015 13:14:43 -0800 (PST)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 10D481A1A12; Wed, 28 Jan 2015 13:14:36 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Document Action: 'A PCE-based Architecture for Application-based Network Operations' to Informational RFC (draft-farrkingel-pce-abno-architecture-16.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.1.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Wed, 28 Jan 2015 13:14:36 -0800
Archived-At: <>
Cc: RFC Editor <>
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 28 Jan 2015 21:14:56 -0000

The IESG has approved the following document:
- 'A PCE-based Architecture for Application-based Network Operations'
  (draft-farrkingel-pce-abno-architecture-16.txt) as Informational RFC

This document has been reviewed in the IETF but is not the product of an
IETF Working Group.

The IESG contact person is Alia Atlas.

A URL of this Internet Draft is:

Technical Summary

   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 this type of
   requirement is said to have Application-Based Network Operations

   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

   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.

Working Group Summary

   This document is not the product of any IETF working group. There is
   currently no working group chartered to work on this topic.

   However, the document has been widely circulated for review with
   focus in the PCE, ALTO, and OPSAWG. Notification of the document with
   a request for review was also sent to the I2RS and RTGWG working
   groups. The SDNRG of the IRTF has had this work presented at several
   IETF meetings.

Document Quality

   There are currently believed to be two implementations of network
   management packages in operators' research labs that are based on the
   architectural model described here. A further implementation is
   rumored to be planned by a third network operator.

   Although the operators have not been publically forthcoming about
   their implementations, some information can be found at:


   Quintin Zhao <> is the Document Shepherd.
   Alia Atlas <> is the Responsible Area Director.