Path Computation Element Communication Protocol (PCEP) Extensions for PCE-Initiated LSP Setup in a Stateful PCE Model

Crabbe, Edward; Minei, Ina; Sivabalan, Siva; Varga, Robert

doi:10.17487/rfc8281

Cited by 14 publications

(21 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The AS-PCE can instantiate or remove LSPs into the network using the PCEP initiate request message (PCInitiate) [17]. This message includes the endpoints and the computed explicit route object (ERO), dening the route and resources to be traversed and allocated by the LSP.…”

Section: Connectivity Provisioningmentioning

confidence: 99%

SDN orchestration architectures and their integration with Cloud Computing applications

Mayoral

Vilalta

Muñoz

et al. 2017

Optical Switching and Networking

View full text Add to dashboard Cite

Emerging cloud-based applications, running in geographically distributed data centers (DCs), generate new dynamic trac patterns which claim for a more ecient management of the trac ows. Geographically distributed DCs interconnection requires automatic and more dynamic provisioning and deletion of end-toend (E2E) connectivity services, through heterogeneous network domains. Each network domain may use a dierent data transport technology but also a dierent control/management system. The fast development of Software Dened Networking (SDN) and the interworking with current control plane technologies such as Generalized Multi-protocol Label Switching (GMPLS), demand orchestration over the heterogeneous control instances to provide seamless E2E connectivity services to external applications (i.e. cloud computing applications).In this work, we present dierent orchestration architectures based on the SDN principles which use the Path Computation Element (PCE) as a fundamental component. In particular, a single SDN controller orchestration approach is compared with an orchestration architecture based on the Application Based Network Operations (ABNO) dened within the International Engineering Task Force (IETF), in order to nd the potential benets and drawbacks of both architectures. Finally, the SDN IT and Network Orchestration (SINO) platform which integrates the management of Cloud Computing infrastructure with the network orchestration, it is used to validate both architectures by evaluating their performance providing two inter-DC connectivity services: E2E connectivity and Virtual Machine (VM) migration.

show abstract

Section: Connectivity Provisioningmentioning

confidence: 99%

SDN orchestration architectures and their integration with Cloud Computing applications

Mayoral

Vilalta

Muñoz

et al. 2017

Optical Switching and Networking

View full text Add to dashboard Cite

show abstract

“…5): i) the controller that receives network-level requests and implements the workflows to coordinate the rest of components; ii) an active stateful front-end PCE (fPCE) [13], [36] with LSP initiation capabilities [37] able to issue requests to the Provisioning Manager (PM), and delegating complex computations to the back-end PCE (bPCE); iii) a PM dealing with new connections' set-up; iv) a Topology Module storing the network topology in the Traffic Engineering Database (TED) and the set of already established lightpaths in the LSP Database (LSP-DB); and v) a bPCE responsible for dealing with computationally intensive algorithms [38], such as CP-VNT creation and reconnection algorithms. The modules in the ABNO architecture interoperate by means of PCEP [14].…”

Section: Workflows and Protocol Extensionsmentioning

confidence: 99%

ABNO-driven content distribution in the telecom cloud

Gifre

Tornatore

Contreras

et al. 2017

Optical Switching and Networking

View full text Add to dashboard Cite

Abstract-As current sustained traffic growth is expected to strain capacity of today's metro network, novel content distribution architectures where contents are placed closer to the users are being investigated. In that regard, telecom operators can deploy datacenters (DCs) in metro areas, thus reducing the impact of the traffic going from users to DCs. However, effective solutions to distribute contents to those metro DCs and to synchronize contents among them need to be investigated. In this paper, a hierarchical content distribution architecture for the telecom cloud is investigated: core DCs placed in geographically distributed locations, are interconnected through permanent "per content provider" (CP) virtual network topology (CP-VNT); additionally, metro DCs are placed close to users, and need also to be interconnected with the core DCs. CP's data is replicated in the core DCs through the CP-VNT, while metro-to-core (M2C) anycast connections are established periodically for metro DCs to synchronize contents. Since failures in the interconnection network might disconnect the CP-VNTs, in this paper recovery mechanisms are proposed to reconnect topologies and anycast connections. Topology creation, anycast provisioning and recovery problems are first formally stated and modelled as Integer Linear Programs (ILP). Solving these models, however, becomes impractical for realsized scenarios, so heuristic algorithms are also proposed. Exhaustive simulation results show that the investigated architecture provides significant improvements in both supported traffic and restorability compared to the case of a single core DC. Workflows to implement the algorithms within the Applications-based Network Operations (ABNO) architecture and extensions for PCEP are proposed. Finally, the architecture is experimentally validated in our ABNObased iONE test-bed.Keywords: Datacenter interconnection, Optical networks, Content distribution. INTRODUCTIONCloud-based contents are experiencing an exponential growth in users and data volume. In [1], Cisco forecast a yearly global growth of 23% in datacenter (DC)-to-user traffic, 29% in DC-to-DC traffic, and 22% in the intra-DC traffic. Likewise, Alcatel-Lucent highlights that metro traffic will increase 560% by 2017 mainly driven by IP video and cloud traffic [2], growing two times faster than core network traffic. They conclude that placing contents in DCs closer to users can result in a 41% bandwidth reduction in the metro networks. The resulting distributed DC architecture should come together with the extension of the core network functionalities towards the metro, as proposed in [3].Robust telecom infrastructures are needed to minimize the impact of failures on the services [4]; this is especially relevant in the case of video distribution. In fact, prolonged service outages and disruptions have negatively impacted the confidence of important companies toward cloud environments. Telecom operators are in a vantage position to capitalize on highly-reliable cloud services since they o...

show abstract

“…The applicability of this object to the PCInitiate message is the same as for other objects on those messages as described in [RFC8281]. These messages use the <attribute-list> as defined in [RFC5440] and extended by further PCEP extensions, so the <attribute-list> as extended in Section 5 can be used to include the INTER-LAYER object on these messages.…”

Section: Protocol Extensionsmentioning

confidence: 99%

“…Processing for PCE-initiated LSPs is described in [RFC8281]. That document defines the PCInitiate message that is used by a PCE to request a PCC to set up a new LSP.…”

Section: Stateful Pce and Pce Initiated Lspsmentioning

confidence: 99%

See 1 more Smart Citation

Extensions to the Path Computation Element Communication Protocol (PCEP) for Inter-Layer MPLS and GMPLS Traffic Engineering

Takeda¹,

Oki²,

Zhang³

et al. 2017

View full text Add to dashboard Cite

The Path Computation Element (PCE) provides path computation functions in support of traffic engineering in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks.MPLS and GMPLS networks may be constructed from layered service networks. It is advantageous for overall network efficiency to provide end-to-end traffic engineering across multiple network layers through a process called inter-layer traffic engineering. PCE is a candidate solution for such requirements.

show abstract

Path Computation Element Communication Protocol (PCEP) Extensions for PCE-Initiated LSP Setup in a Stateful PCE Model

Abstract: The Path Computation Element Communication Protocol (PCEP) provides mechanisms for Path Computation Elements (PCEs) to perform path computations in response to Path Computation Client (PCC) requests.

Cited by 14 publications

References 5 publications

SDN orchestration architectures and their integration with Cloud Computing applications

SDN orchestration architectures and their integration with Cloud Computing applications

ABNO-driven content distribution in the telecom cloud

Extensions to the Path Computation Element Communication Protocol (PCEP) for Inter-Layer MPLS and GMPLS Traffic Engineering

Contact Info

Product

Resources

About