{
  "number": 5824,
  "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"
  ],
  "published": "2010-04",
  "status": "Informational",
  "stream": "IETF",
  "area": "rtg",
  "working_group": "l3vpn",
  "pages": 27,
  "formats": [
    "TXT",
    "HTML"
  ],
  "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\nService 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.",
  "keywords": [
    "triple-play service"
  ],
  "draft": "draft-ietf-l3vpn-e2e-rsvp-te-reqts-05",
  "doi": "10.17487/RFC5824",
  "urls": {
    "html": "https://rfc.dk/rfc5824/",
    "text": "https://rfc.dk/rfc5824.txt",
    "rfc_editor": "https://www.rfc-editor.org/rfc/rfc5824",
    "datatracker": "https://datatracker.ietf.org/doc/rfc5824/"
  },
  "text_modified": "2010-04-29T02:17:18Z"
}