MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements

Metadata

Publisher: IETF
Doc Type: Informational
Pages: 29
Abstract: This document discusses requirements for the support of inter-AS MPLS Traffic Engineering (MPLS TE). Its main objective is to present a set of requirements and scenarios which would result in general guidelines for the definition, selection, and specification development for any technical solution(s) meeting these requirements and supporting the scenarios. This memo provides information for the Internet community.
Publication Date: 2005-11-01
Status Note: Informational
DOI: 10.17487/RFC4216
Link: https://doi.org/10.17487/RFC4216
Author(s): Raymond Zhang
JP Vasseur
Keyword(s): Inter-AS, MPLS-TE

Latest version of IETF RFC 4216

Document Versions — IETF RFC 4216

▶ IETF RFC 4216 (2005-11-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

IETF RFC 2119 [Active*]
IETF RFC 2702 [Active*]
IETF RFC 3209 [Active*]

Bibliographic Reference(s)

Vasseur, J.-P., et al., "Path Computation Element (PCE) communication Protocol (PCEP) - Version 1", Work in Progress, September 2005. EXTERNAL
Lee, CY., Farrel, A., and S. De Cnodder, "Exclude Routes - Extension to RSVP-TE", Work in Progress, August 2005. EXTERNAL
Rosen, E. and Y. Rekhter, "BGP/MPLS IP VPNs" , Work in Progress, October 2004. EXTERNAL
Farrel, A., Vasseur, J.-P., and J. Ash, "Path Computation Element (PCE) Architecture", Work in Progress, September 2005. EXTERNAL
Kompella, K. and G. Swallow, "Detecting MPLS Data Plane Failures", Work in Progress, May 2005. EXTERNAL
IETF RFC 1771 [Superseded*]
IETF RFC 2430 [Active*]
IETF RFC 2475 [Active*]
IETF RFC 2597 [Active*]
IETF RFC 3031 [Active*]
IETF RFC 3246 [Active*]
IETF RFC 3270 [Active*]
IETF RFC 3272 [Superseded*]
IETF RFC 3346 [Active*]
IETF RFC 3443 [Active*]
IETF RFC 3469 [Active*]
IETF RFC 3473 [Active*]
IETF RFC 3564 [Active*]
IETF RFC 4090 [Active*]
IETF RFC 4206 [Active*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC4216.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 4216, MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements. Available at https://doi.org/10.17487/RFC4216

Snippet:

IETF RFC 4216, MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements. Available at https://doi.org/10.17487/RFC4216

HTML (ISO 690 compliant)

Preview:

IETF RFC 4216, MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements. Available at https://doi.org/10.17487/RFC4216

Snippet:

<span class="citation"><cite>IETF RFC 4216</cite>, MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements. Available at <a href="https://doi.org/10.17487/RFC4216" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4216</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 4216, MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements
doi: 10.17487/RFC4216
url: https://doi.org/10.17487/RFC4216

Snippet:

<li>
<cite id="bib-rfc4216">IETF RFC 4216</cite>, MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements
<span class="doi">10.17487/RFC4216</span>
</li>

Referenced By

IETF RFC 4561 [Active*]
IETF RFC 4655 [Active*]
IETF RFC 4726 [Active*]
IETF RFC 4736 [Active*]
IETF RFC 4874 [Active*]
IETF RFC 5151 [Active*]
IETF RFC 5152 [Active*]
IETF RFC 5298 [Active*]
IETF RFC 5316 [Superseded*]
IETF RFC 5376 [Active*]
IETF RFC 5392 [Active*]
IETF RFC 5394 [Active*]
IETF RFC 5441 [Active*]
IETF RFC 5520 [Active*]
IETF RFC 5559 [Active*]
IETF RFC 6411 [Active*]
IETF RFC 6805 [Active*]