API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 4927
[ACTIVE]

Path Computation Element Communication Protocol (PCECP) Specific Requirements for Inter-Area MPLS and GMPLS Traffic Engineering

Metadata

Publisher
IETF
Doc Type
Informational
Pages
12
Abstract
For scalability purposes, a network may comprise multiple Interior Gateway Protocol (IGP) areas. An inter-area Traffic Engineered Label Switched Path (TE-LSP) is an LSP that transits through at least two IGP areas. In a multi-area network, topology visibility remains local to a given area, and a head-end Label Switching Router (LSR) cannot compute an inter-area shortest constrained path. One key application of the Path Computation Element (PCE)-based architecture is the computation of inter-area TE-LSP paths. The PCE Communication Protocol (PCECP) is used to communicate computation requests from Path Computation Clients (PCCs) to PCEs, and to return computed paths in responses. This document lists a detailed set of PCECP-specific requirements for support of inter-area TE-LSP path computation. It complements the generic requirements for a PCE Communication Protocol. This memo provides information for the Internet community.
Publication Date
2007-06-01
Status Note
Informational
DOI
10.17487/RFC4927
Link
https://doi.org/10.17487/RFC4927
Author(s)
Jean-Louis Le Roux
Keyword(s)
GMPLS, TE LSP, MPLS-TE, PCE
Latest version of IETF RFC 4927

Document Versions — IETF RFC 4927

  • ▶ IETF RFC 4927 (2007-06-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

Bibliographic Reference(s)

  • Bryskin, I., Papadimitriou, D., Berger L., and J. Ash, "Policy-Enabled Path Computation Framework", Work in Progress, March 2007. EXTERNAL
  • Vasseur, J.P., Ed., Ayyangar, A., Ed., and R. Zhang, "A Per-domain path computation method for computing Inter-domain Traffic Engineering (TE) Label Switched Path (LSP)", Work in Progress, April 2007. EXTERNAL
  • IETF RFC 3785 [Active*]
  • IETF RFC 4674 [Active*]
Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC4927.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 4927, Path Computation Element Communication Protocol (PCECP) Specific Requirements for Inter-Area MPLS and GMPLS Traffic Engineering. Available at https://doi.org/10.17487/RFC4927
Snippet:
IETF RFC 4927, Path Computation Element Communication Protocol (PCECP) Specific Requirements for Inter-Area MPLS and GMPLS Traffic Engineering. Available at https://doi.org/10.17487/RFC4927

HTML (ISO 690 compliant)

Preview:
IETF RFC 4927, Path Computation Element Communication Protocol (PCECP) Specific Requirements for Inter-Area MPLS and GMPLS Traffic Engineering. Available at https://doi.org/10.17487/RFC4927
Snippet:
<span class="citation"><cite>IETF RFC 4927</cite>, Path Computation Element Communication Protocol (PCECP) Specific Requirements for Inter-Area MPLS and GMPLS Traffic Engineering. Available at <a href="https://doi.org/10.17487/RFC4927" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4927</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 4927, Path Computation Element Communication Protocol (PCECP) Specific Requirements for Inter-Area MPLS and GMPLS Traffic Engineering
doi: 10.17487/RFC4927
url: https://doi.org/10.17487/RFC4927
Snippet:
<li>
<cite id="bib-rfc4927">IETF RFC 4927</cite>, Path Computation Element Communication Protocol (PCECP) Specific Requirements for Inter-Area MPLS and GMPLS Traffic Engineering
<span class="doi">10.17487/RFC4927</span>
</li>

Referenced By