RFC 5467: GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6387.
Current version: RFC 6387 — GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs)
In plain English — editorial summary, not part of the RFC
This document defines a method for the support of GMPLS asymmetric bandwidth bidirectional Label Switched Paths (LSPs). The presented approach is applicable to any switching technology and builds on the original Resource Reservation Protocol (RSVP) model for the transport of traffic-related parameters. The procedures described in this document are experimental. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC5467
- Published
- March 2009
- Authors
- L. Berger; A. Takacs; D. Caviglia; D. Fedyk; J. Meuric
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- rtg
- Pages
- 14
- Also known as
- —
- Obsoleted by:
- RFC 6387
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5710PathErr Message Triggered MPLS and GMPLS LSP ReroutesCurrent
January 2010
- RFC 5711Node Behavior upon Originating and Receiving Resource Reservation Protocol (RSVP) Path Error MessagesCurrent
January 2010
- RFC 4873GMPLS Segment RecoveryUpdated
May 2007
- RFC 4736Reoptimization of Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Loosely Routed Label Switched Path (LSP)Current
November 2006
- RFC 4558Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification StatementCurrent
June 2006
- RFC 6517Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN SolutionCurrent
February 2012
- RFC 3473Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) ExtensionsUpdated
February 2003
- RFC 3468The Multiprotocol Label Switching (MPLS) Working Group decision on MPLS signaling protocolsCurrent
February 2003
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?