A PCE-based Architecture for Application-based Network Operations
draft-farrkingel-pce-abno-architecture-11

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-08-24
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Reviews
Stream WG state (None)
Document shepherd Quintin Zhao
Shepherd write-up Show (last changed 2014-08-19)
IESG IESG state Publication Requested
Consensus Boilerplate Unknown
Telechat date
Responsible AD Alia Atlas
Send notices to draft-farrkingel-pce-abno-architecture.all@tools.ietf.org
Internet Engineering Task Force                                  D. King
Internet-Draft                                        Old Dog Consulting
Intended status: Informational                                 A. Farrel
Expires: 24 February 2015                               Juniper Networks
                                                          24 August 2014

   A PCE-based Architecture for Application-based Network Operations

             draft-farrkingel-pce-abno-architecture-11.txt

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.

King & Farrel                                                   [Page 1]
draft-farrkingel-pce-abno-architecture-11.txt                August 2014

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

King & Farrel                                                   [Page 2]
draft-farrkingel-pce-abno-architecture-11.txt                August 2014

Table of Contents

   1.  Introduction ................................................ 4
    1.1  Scope ..................................................... 5
   2. Application-based Network Operations (ABNO) .................. 5
    2.1  Assumptions and Requirements .............................. 5
    2.2  Implementation of the Architecture ........................ 6
    2.3  Generic Architecture ...................................... 8
      2.3.1 ABNO Components ........................................ 9
      2.3.2 ABNO Functional Interfaces ............................ 15
   3. ABNO Use Cases .............................................. 23
    3.1 Inter-AS Connectivity ..................................... 23
    3.2 Multi-Layer Networking .................................... 29
      3.2.1 Data Center Interconnection across Multi-Layer Networks 33
    3.3 Make-Before-Break ......................................... 36
      3.3.1 Make-Before-Break for Re-optimization ................. 36
Show full document text