metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels

Still current, but amended. Parts of this document are changed or extended by RFC 3936, RFC 4420, RFC 4874, RFC 5151, RFC 5420, RFC 5711, RFC 6780, RFC 6790, RFC 7274. Read both.

In plain English — editorial summary, not part of the RFC

This document describes the use of RSVP (Resource Reservation Protocol), including all the necessary extensions, to establish label-switched paths (LSPs) in MPLS (Multi-Protocol Label Switching). Since the flow along an LSP is completely identified by the label applied at the ingress node of the path, these paths may be treated as tunnels. A key application of LSP tunnels is traffic engineering with MPLS as specified in RFC 2702. [STANDARDS-TRACK]

Document record

Document ID
RFC3209
Published
December 2001
Authors
D. Awduche; L. Berger; D. Gan; T. Li; V. Srinivasan; G. Swallow
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
61
Also known as
—
Updated by:
RFC 3936, RFC 4420, RFC 4874, RFC 5151, RFC 5420, RFC 5711, RFC 6780, RFC 6790, RFC 7274

Topics

Referenced by

9 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/3209-rsvp-te-extensions-to-rsvp-for-lsp-tunnels