Browse Prior Art Database

Applicability of a Stateful Path Computation Element (PCE) (RFC8051)

IP.com Disclosure Number: IPCOM000248768D
Original Publication Date: 2017-Jan-01
Included in the Prior Art Database: 2017-Jan-07
Document File: 48 page(s) / 58K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

X. Zhang: AUTHOR [+4]

Abstract

[RFC4655] defines the architecture for a model based on the Path Computation Element (PCE) for the computation of Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering Label Switched Paths (TE LSPs). To perform such a constrained computation, a PCE stores the network topology (i.e., TE links and nodes) and resource information (i.e., TE attributes) in its TE Database (TED). [RFC5440] describes the Path Computation Element Protocol (PCEP) for interaction between a Path Computation Client (PCC) and a PCE, or between two PCEs, enabling computation of TE LSPs.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 5% of the total text.

Internet Engineering Task Force (IETF)                     X. Zhang, Ed. Request for Comments: 8051                           Huawei Technologies Category: Informational                                    I. Minei, Ed. ISSN: 2070-1721                                             Google, Inc.                                                             January 2017

        Applicability of a Stateful Path Computation Element (PCE)

Abstract

   A stateful Path Computation Element (PCE) maintains information about    Label Switched Path (LSP) characteristics and resource usage within a    network in order to provide traffic-engineering calculations for its    associated Path Computation Clients (PCCs).  This document describes    general considerations for a stateful PCE deployment and examines its    applicability and benefits, as well as its challenges and    limitations, through a number of use cases.  PCE Communication    Protocol (PCEP) extensions required for stateful PCE usage are    covered in separate documents.

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

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

Zhang & Minei                 Informational                     [Page 1]
 RFC 8051            Applicability for a Stateful PCE        January 2017

 Copyright Notice

   Copyright (c) 2017 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3

 ...