Requirements for Supporting Customer Resource ReSerVation Protocol (RSVP) and RSVP Traffic Engineering (RSVP-TE) over a BGP/MPLS IP-VPN
RFC 5824
Revision differences
Document history
Date | By | Action |
---|---|---|
2022-01-12
|
(System) | Received changes through RFC Editor sync (removed Errata tag) |
2022-01-11
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'Today, customers expect to run triple-play services through BGP/MPLS IP-VPNs. Some service providers will deploy services … Received changes through RFC Editor sync (changed abstract to '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.') |
2015-10-14
|
(System) | Notify list changed from l3vpn-chairs@ietf.org, draft-ietf-l3vpn-e2e-rsvp-te-reqts@ietf.org to (None) |
2010-04-29
|
Cindy Morgan | State Changes to RFC Published from RFC Ed Queue by Cindy Morgan |
2010-04-29
|
Cindy Morgan | [Note]: 'RFC 5824' added by Cindy Morgan |
2010-04-28
|
(System) | RFC published |