{
  "draft": "draft-ietf-l3vpn-e2e-rsvp-te-reqts-05",
  "doc_id": "RFC5824",
  "title": "Requirements for Supporting Customer Resource ReSerVation Protocol (RSVP) and RSVP Traffic Engineering (RSVP-TE) over a BGP/MPLS IP-VPN",
  "authors": [
    "K. Kumaki, Ed.",
    "R. Zhang",
    "Y. Kamite"
  ],
  "format": [
    "TEXT",
    "HTML"
  ],
  "page_count": "27",
  "pub_status": "INFORMATIONAL",
  "status": "INFORMATIONAL",
  "source": "Layer 3 Virtual Private Networks",
  "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.\n\n 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.",
  "pub_date": "April 2010",
  "keywords": [
    "triple-play service"
  ],
  "obsoletes": [],
  "obsoleted_by": [],
  "updates": [],
  "updated_by": [],
  "see_also": [],
  "doi": "10.17487/RFC5824",
  "errata_url": null
}