RFC 5824: Requirements for Supporting Customer Resource ReSerVation Protocol (RSVP) and RSVP Traffic Engineering (RSVP-TE) over a BGP/MPLS IP-VPN
In plain English — editorial summary, not part of the RFC
Today, customers expect to run triple-play services through BGP/MPLS IP-VPNs. Some service providers will deploy services that request Quality of Service (QoS) guarantees from a local Customer Edge (CE) to a remote CE across the network. As a result, the application (e.g., voice, video, bandwidth-guaranteed data pipe, etc.) requirements for an end-to-end QoS and reserving an adequate bandwidth continue to increase. Service providers can use both an MPLS and an MPLS Traffic Engineering (MPLS-TE) Label Switched Path (LSP) to meet their service objectives. This document describes service-provider requirements for supporting a customer Resource ReSerVation Protocol (RSVP) and RSVP-TE over a BGP/MPLS IP-VPN. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5824
- Published
- April 2010
- Authors
- K. Kumaki; R. Zhang; Y. Kamite
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 27
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5826Home Automation Routing Requirements in Low-Power and Lossy NetworksCurrent
April 2010
- RFC 5820Extensions to OSPF to Support Mobile Ad Hoc NetworkingUpdated
March 2010
- RFC 5828Generalized Multiprotocol Label Switching (GMPLS) Ethernet Label Switching Architecture and FrameworkCurrent
March 2010
- RFC 5818Data Channel Status Confirmation Extensions for the Link Management ProtocolUpdated
April 2010
- RFC 5817Graceful Shutdown in MPLS and Generalized MPLS Traffic Engineering NetworksCurrent
April 2010
- RFC 5814Label Switched Path (LSP) Dynamic Provisioning Performance Metrics in Generalized MPLS NetworksCurrent
March 2010
- RFC 5813Forwarding and Control Element Separation (ForCES) MIBCurrent
March 2010
- RFC 5812Forwarding and Control Element Separation (ForCES) Forwarding Element ModelUpdated
March 2010
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?