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 5824
[ACTIVE]

Requirements for Supporting Customer Resource ReSerVation Protocol (RSVP) and RSVP Traffic Engineering (RSVP-TE) over a BGP/MPLS IP-VPN

Metadata

Publisher
IETF
Doc Type
Informational
Pages
27
Abstract
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.
Publication Date
2010-04-01
Status Note
Informational
DOI
10.17487/RFC5824
Link
https://doi.org/10.17487/RFC5824
Author(s)
Kenji Kumaki
Raymond Zhang
Yuji Kamite
Keyword(s)
Triple-play Service
Latest version of IETF RFC 5824

Document Versions — IETF RFC 5824

  • ▶ IETF RFC 5824 (2010-04-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

Bibliographic Reference(s)

  • Davie, B., Le Faucheur, F., and A. Narayanan, "Support for RSVP in Layer 3 VPNs", Work in Progress, November 2009. EXTERNAL
  • IETF RFC 4804 [Active*]
  • RFC5330 — RFC5330 EXTERNAL
  • IETF RFC 5440 [Active*]
Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC5824.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 5824, Requirements for Supporting Customer Resource ReSerVation Protocol (RSVP) and RSVP Traffic Engineering (RSVP-TE) over a BGP/MPLS IP-VPN. Available at https://doi.org/10.17487/RFC5824
Snippet:
IETF RFC 5824, Requirements for Supporting Customer Resource ReSerVation Protocol (RSVP) and RSVP Traffic Engineering (RSVP-TE) over a BGP/MPLS IP-VPN. Available at https://doi.org/10.17487/RFC5824

HTML (ISO 690 compliant)

Preview:
IETF RFC 5824, Requirements for Supporting Customer Resource ReSerVation Protocol (RSVP) and RSVP Traffic Engineering (RSVP-TE) over a BGP/MPLS IP-VPN. Available at https://doi.org/10.17487/RFC5824
Snippet:
<span class="citation"><cite>IETF RFC 5824</cite>, Requirements for Supporting Customer Resource ReSerVation Protocol (RSVP) and RSVP Traffic Engineering (RSVP-TE) over a BGP/MPLS IP-VPN. Available at <a href="https://doi.org/10.17487/RFC5824" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5824</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 5824, Requirements for Supporting Customer Resource ReSerVation Protocol (RSVP) and RSVP Traffic Engineering (RSVP-TE) over a BGP/MPLS IP-VPN
doi: 10.17487/RFC5824
url: https://doi.org/10.17487/RFC5824
Snippet:
<li>
<cite id="bib-rfc5824">IETF RFC 5824</cite>, Requirements for Supporting Customer Resource ReSerVation Protocol (RSVP) and RSVP Traffic Engineering (RSVP-TE) over a BGP/MPLS IP-VPN
<span class="doi">10.17487/RFC5824</span>
</li>

Referenced By