Aggregation of Resource ReSerVation Protocol (RSVP) Reservations over MPLS TE/DS-TE Tunnels
RFC 4804
|
Document |
Type |
|
RFC - Proposed Standard
(February 2007; Errata)
|
|
Last updated |
|
2015-10-14
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Reviews |
|
|
Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
No shepherd assigned
|
IESG |
IESG state |
|
RFC 4804 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Magnus Westerlund
|
|
Send notices to |
|
(None)
|
Network Working Group F. Le Faucheur, Ed.
Request for Comments: 4804 Cisco Systems, Inc.
Category: Standards Track February 2007
Aggregation of Resource ReSerVation Protocol (RSVP)
Reservations over MPLS TE/DS-TE Tunnels
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract
RFC 3175 specifies aggregation of Resource ReSerVation Protocol
(RSVP) end-to-end reservations over aggregate RSVP reservations.
This document specifies aggregation of RSVP end-to-end reservations
over MPLS Traffic Engineering (TE) tunnels or MPLS Diffserv-aware
MPLS Traffic Engineering (DS-TE) tunnels. This approach is based on
RFC 3175 and simply modifies the corresponding procedures for
operations over MPLS TE tunnels instead of aggregate RSVP
reservations. This approach can be used to achieve admission control
of a very large number of flows in a scalable manner since the
devices in the core of the network are unaware of the end-to-end RSVP
reservations and are only aware of the MPLS TE tunnels.
Faucheur Standards Track [Page 1]
RFC 4804 RSVP Aggregation over MPLS TE Tunnels February 2007
Table of Contents
1. Introduction ....................................................3
2. Specification of Requirements ...................................7
3. Definitions .....................................................7
4. Operations of RSVP Aggregation over TE with
Pre-established Tunnels .........................................8
4.1. Reference Model ............................................9
4.2. Receipt of E2E Path Message by the Aggregator ..............9
4.3. Handling of E2E Path Message by Transit LSRs ..............11
4.4. Receipt of E2E Path Message by the Deaggregator ...........11
4.5. Handling of E2E Resv Message by the Deaggregator ..........12
4.6. Handling of E2E Resv Message by the Aggregator ............12
4.7. Forwarding of E2E Traffic by the Aggregator ...............14
4.8. Removal of E2E Reservations ...............................14
4.9. Removal of the TE Tunnel ..................................14
4.10. Example Signaling Flow ...................................15
5. IPv4 and IPv6 Applicability ....................................16
6. E2E Reservations Applicability .................................16
7. Example Deployment Scenarios ...................................16
7.1. Voice and Video Reservations Scenario .....................16
7.2. PSTN/3G Voice Trunking Scenario ...........................17
8. Security Considerations ........................................18
9. Acknowledgments ................................................20
10. Normative References ..........................................20
11. Informative References ........................................21
Appendix A - Optional Use of RSVP Proxy on RSVP Aggregator ........23
Appendix B - Example Usage of RSVP Aggregation over DSTE Tunnels
for VoIP Call Admission Control (CAC) ................25
Faucheur Standards Track [Page 2]
RFC 4804 RSVP Aggregation over MPLS TE Tunnels February 2007
1. Introduction
The Integrated Services (Intserv) [INT-SERV] architecture provides a
means for the delivery of end-to-end Quality of Service (QoS) to
applications over heterogeneous networks.
[RSVP] defines the Resource reSerVation Protocol that can be used by
applications to request resources from the network. The network
responds by explicitly admitting or rejecting these RSVP requests.
Certain applications that have quantifiable resource requirements
express these requirements using Intserv parameters as defined in the
appropriate Intserv service specifications ([GUARANTEED],
[CONTROLLED]).
The Differentiated Services (DiffServ) architecture ([DIFFSERV]) was
then developed to support the differentiated treatment of packets in
very large scale environments. In contrast to the per-flow
orientation of Intserv and RSVP, Diffserv networks classify packets
into one of a small number of aggregated flows or "classes", based on
the Diffserv codepoint (DSCP) in the packet IP header. At each
Diffserv router, packets are subjected to a "per-hop behavior" (PHB),
which is invoked by the DSCP. The primary benefit of Diffserv is its
Show full document text