<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.farrkingel-pce-abno-architecture" target="https://datatracker.ietf.org/doc/html/draft-farrkingel-pce-abno-architecture-00">
   <front>
      <title>A PCE-based Architecture for Application-based Network Operations</title>
      <author initials="D." surname="King" fullname="Daniel King">
         </author>
      <author initials="A." surname="Farrel" fullname="Adrian Farrel">
         </author>
      <date month="December" day="1" year="2012" />
      <abstract>
	 <t>   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).  An environment that operates to meet this type of
   requirement is said to have Application-Based Network Operations
   (ABNO).

   ABNO brings together several 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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-farrkingel-pce-abno-architecture-00" />
   
</reference>
