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

Document Type RFC - Informational (March 2015; No errata)
Last updated 2015-03-22
Stream IETF
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 RFC 7491 (Informational)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alia Atlas
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
IANA action state No IC
Internet Engineering Task Force (IETF)                           D. King
Request for Comments: 7491                            Old Dog Consulting
Category: Informational                                        A. Farrel
ISSN: 2070-1721                                         Juniper Networks
                                                              March 2015

   A PCE-Based Architecture for Application-Based Network Operations

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.  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.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7491.

King & Farrel                 Informational                     [Page 1]
RFC 7491             PCE-Based Architecture for ABNO          March 2015

Copyright Notice

   Copyright (c) 2015 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                 Informational                     [Page 2]
RFC 7491             PCE-Based Architecture for ABNO          March 2015

Table of Contents

   1. Introduction ....................................................4
      1.1. Scope ......................................................5
   2. Application-Based Network Operations (ABNO) .....................6
      2.1. Assumptions ................................................6
      2.2. Implementation of the Architecture .........................6
      2.3. Generic ABNO Architecture ..................................7
           2.3.1. ABNO Components .....................................8
           2.3.2. Functional Interfaces ..............................15
   3. ABNO Use Cases .................................................24
      3.1. Inter-AS Connectivity .....................................24
      3.2. Multi-Layer Networking ....................................30
           3.2.1. Data Center Interconnection across
                  Multi-Layer Networks ...............................34
      3.3. Make-before-Break .........................................37
           3.3.1. Make-before-Break for Reoptimization ...............37
           3.3.2. Make-before-Break for Restoration ..................38
           3.3.3. Make-before-Break for Path Test and Selection ......40
      3.4. Global Concurrent Optimization ............................42
           3.4.1. Use Case: GCO with MPLS LSPs .......................43
      3.5. Adaptive Network Management (ANM) .........................45
           3.5.1. ANM Trigger ........................................46
           3.5.2. Processing Request and GCO Computation .............46
           3.5.3. Automated Provisioning Process .....................47
Show full document text