draft-ietf-tsvwg-rsvp-ipsec-03.txt   draft-ietf-tsvwg-rsvp-ipsec-04.txt 
Generic Aggregate RSVP Reservations September 2006 Generic Aggregate RSVP Reservations January 2007
Internet Draft Francois Le Faucheur Internet Draft Francois Le Faucheur
Bruce Davie Bruce Davie
Cisco Systems, Inc. Cisco Systems, Inc.
Pratik Bose Pratik Bose
Lockheed Martin Lockheed Martin
Chris Christou Chris Christou
Michael Davenport Michael Davenport
Booz Allen Hamilton Booz Allen Hamilton
draft-ietf-tsvwg-rsvp-ipsec-03.txt draft-ietf-tsvwg-rsvp-ipsec-04.txt
Expires: March 2007 September 2006 Expires: July 2007 January 2007
Generic Aggregate RSVP Reservations Generic Aggregate Resource ReSerVation Protocol (RSVP) Reservations
draft-ietf-tsvwg-rsvp-ipsec-03.txt draft-ietf-tsvwg-rsvp-ipsec-04.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
skipping to change at page 1, line 45 skipping to change at page 1, line 45
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
[RSVP-AGG] defines aggregate RSVP reservations allowing resources to [RSVP-AGG] defines aggregate Resource ReSerVation Protocol (RSVP)
be reserved in a Diffserv network for a given DSCP from a given reservations allowing resources to be reserved in a Diffserv network
source to a given destination. [RSVP-AGG] also defines how end-to-end for a given Per Hop Behavior (PHB), or given set of PHBs, from a
RSVP reservations can be aggregated onto such aggregate reservations given source to a given destination. [RSVP-AGG] also defines how end-
Generic Aggregate RSVP Reservations September 2006 Generic Aggregate RSVP Reservations January 2007
when transiting through a Diffserv cloud. There are situations where to-end RSVP reservations can be aggregated onto such aggregate
multiple such aggregate reservations are needed for the same source reservations when transiting through a Diffserv cloud. There are
IP address, destination IP address and DSCP. However, this is not situations where multiple such aggregate reservations are needed for
supported by the aggregate reservations defined in [RSVP-AGG]. In the same source IP address, destination IP address and PHB (or set of
order to support this, the present document defines a more flexible PHBs). However, this is not supported by the aggregate reservations
type of aggregate RSVP reservations, referred to as generic aggregate defined in [RSVP-AGG]. In order to support this, the present document
reservation. Multiple such generic aggregate reservations can be defines a more flexible type of aggregate RSVP reservations, referred
established for a given DSCP from a given source IP address to a to as generic aggregate reservation. Multiple such generic aggregate
given destination IP address. The generic aggregate reservations may reservations can be established for a given PHB (or set of PHBs) from
be used to aggregate end-to-end RSVP reservations. This document also a given source IP address to a given destination IP address. The
defines the procedures for such aggregation. The generic aggregate generic aggregate reservations may be used to aggregate end-to-end
reservations may also be used end-to-end directly by end-systems RSVP reservations. This document also defines the procedures for such
attached to a Diffserv network. aggregation. The generic aggregate reservations may also be used end-
to-end directly by end-systems attached to a Diffserv network.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2007).
Table Of Content Table Of Content
1. Introduction...................................................3 1. Introduction...................................................3
1.1. Related RFCs and Internet-Drafts..........................5 1.1. Related IETF Documents....................................6
1.2. Organization Of This Document.............................6 1.2. Organization Of This Document.............................6
2. Object Definition..............................................6 2. Object Definition..............................................7
2.1. SESSION Class.............................................7 2.1. SESSION Class.............................................8
2.2. SESSION-OF-INTEREST (SOI) Class..........................10 2.2. SESSION-OF-INTEREST (SOI) Class..........................11
3. Processing Rules For Handling Generic Aggregate RSVP Reservations 3. Processing Rules For Handling Generic Aggregate RSVP Reservations
.................................................................12 .................................................................12
3.1. Required Changes to Path and Resv Processing.............12 3.1. Required Changes to Path and Resv Processing.............13
4. Procedures for Aggregation over Generic Aggregate RSVP 4. Procedures for Aggregation over Generic Aggregate RSVP
Reservations.....................................................13 Reservations.....................................................14
5. Example Usage Of Multiple Generic Aggregate Reservations Per DSCP 5. Example Usage Of Multiple Generic Aggregate Reservations Per PHB
From a Given Aggregator to a Given Deaggregator..................17 From a Given Aggregator to a Given Deaggregator..................18
6. Security Considerations.......................................20 6. Security Considerations.......................................20
7. IANA Considerations...........................................20 7. IANA Considerations...........................................23
8. Acknowledgments...............................................21 8. Acknowledgments...............................................24
9. Normative References..........................................21 9. Normative References..........................................25
10. Informative References.......................................22 10. Informative References.......................................25
11. Authors' Addresses...........................................22 11. Authors' Addresses...........................................26
Appendix A: Example Signaling Flow...............................24 Appendix A: Example Signaling Flow...............................28
Specification of Requirements Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", In this document, the key words "MUST", "MUST NOT", "REQUIRED",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
document are to be interpreted as described in [KEYWORDS].
Generic Aggregate RSVP Reservations September 2006 Generic Aggregate RSVP Reservations January 2007
"OPTIONAL" in this document are to be interpreted as described in
[KEYWORDS] and indicate requirement levels for compliant
implementations.
1. Introduction 1. Introduction
[RSVP-AGG] defines RSVP aggregate reservations allowing resources to [RSVP-AGG] defines RSVP aggregate reservations allowing resources to
be reserved in a Diffserv network for a flow characterized by its 3- be reserved in a Diffserv network for a flow characterized by its 3-
tuple <source IP address, destination IP address, DSCP>. tuple <source IP address, destination IP address, DSCP>.
[RSVP-AGG] also defines the procedures for aggregation of end-to-end [RSVP-AGG] also defines the procedures for aggregation of end-to-end
RSVP reservations onto such aggregate reservations when transiting RSVP reservations onto such aggregate reservations when transiting
through a Diffserv cloud. Such aggregation is illustrated in Figure 1. through a Diffserv cloud. Such aggregation is illustrated in Figure 1.
skipping to change at page 3, line 46 skipping to change at page 3, line 50
I = Interior Router I = Interior Router
--> = E2E RSVP reservation --> = E2E RSVP reservation
==> = Aggregate RSVP reservation ==> = Aggregate RSVP reservation
Figure 1 : Aggregation of E2E Reservations Figure 1 : Aggregation of E2E Reservations
over aggregate RSVP Reservations over aggregate RSVP Reservations
These aggregate reservations use a SESSION type specified in [RSVP- These aggregate reservations use a SESSION type specified in [RSVP-
AGG] that contains the receiver (or Deaggregator) IP address and the AGG] that contains the receiver (or Deaggregator) IP address and the
DSCP of the PHB from which Diffserv resources are to be reserved. For DSCP of the Per Hop Behavior (PHB) from which Diffserv resources are
example, in the case of IPv4, the SESSION object is specified as:
Generic Aggregate RSVP Reservations January 2007
to be reserved. For example, in the case of IPv4, the SESSION object
is specified as:
o Class = SESSION, o Class = SESSION,
C-Type = RSVP-AGGREGATE-IP4 C-Type = RSVP-AGGREGATE-IP4
Generic Aggregate RSVP Reservations September 2006
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| IPv4 Session Address (4 bytes) | | IPv4 Session Address (4 bytes) |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| /////////// | Flags | ///////// | DSCP | | /////////// | Flags | ///////// | DSCP |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
These aggregate reservations use a SENDER_TEMPLATE and FILTER_SPEC These aggregate reservations use a SENDER_TEMPLATE and FILTER_SPEC
types specified in [RSVP-AGG] and which contains only the sender (or types specified in [RSVP-AGG] and which contains only the sender (or
Aggregator) IP address. For example, in the case of IPv4, the Aggregator) IP address. For example, in the case of IPv4, the
SENDER_TEMPLATE object is specified as: SENDER_TEMPLATE object is specified as:
o Class = SENDER_TEMPLATE, o Class = SENDER_TEMPLATE,
C-Type = RSVP-AGGREGATE-IP4 C-Type = RSVP-AGGREGATE-IP4
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| IPv4 Aggregator Address (4 bytes) | | IPv4 Aggregator Address (4 bytes) |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
Thus, it is possible to establish, from a given source IP address to Thus, it is possible to establish, from a given source IP address to
a given destination IP address, separate such aggregate reservations a given destination IP address, separate such aggregate reservations
for different DSCPs. However, from a given source IP address to a for different PHBs (or different sets of PHBs). However, from a given
given IP destination address, only a single [RSVP-AGG] aggregate source IP address to a given IP destination address, only a single
reservation can be established for a given DSCP. [RSVP-AGG] aggregate reservation can be established for a given PHB
(or given set of PHBs).
Situations have since been identified where multiple such aggregate Situations have since been identified where multiple such aggregate
reservations are needed for the same source IP address, destination reservations are needed for the same source IP address, destination
IP address and DSCP. One example is where E2E reservations using IP address and PHB (or set of PHBs). One example is where E2E
different preemption priorities (as per [RSVP-PREEMP]) need to be reservations using different preemption priorities (as per [RSVP-
aggregated through a Diffserv cloud using the same DSCP. Using PREEMP]) need to be aggregated through a Diffserv cloud using the
multiple aggregate reservations for the same DSCP allows enforcement same PHB. Using multiple aggregate reservations for the same PHB
of the different preemption priorities within the aggregation region. allows enforcement of the different preemption priorities within the
In turn this allows much more efficient management of the Diffserv aggregation region. In turn this allows more efficient management of
resources and in period of resource shortage allows to sustain a the Diffserv resources and in period of resource shortage allows to
larger number of E2E reservations with higher preemption priorities. sustain a larger number of E2E reservations with higher preemption
priorities.
For example, [SIG-NESTED] discusses in details how end-to-end RSVP For example, [SIG-NESTED] discusses in details how end-to-end RSVP
reservations can be established in a nested VPN environment through reservations can be established in a nested VPN environment through
RSVP aggregation. In particular, [SIG-NESTED] describes how multiple RSVP aggregation. In particular, [SIG-NESTED] describes how multiple
parallel generic aggregate reservations (for the same DSCP), each parallel generic aggregate reservations (for the same PHB), each with
with different preemption priorities, can be used to efficiently
support the preemption priorities of end-to-end reservations.
This document addresses this requirement for multiple aggregate Generic Aggregate RSVP Reservations January 2007
reservations for the same DSCP, by defining a more flexible type of
aggregate RSVP reservations, referred to as generic aggregate
reservations. This is achieved primarily by adding the notions of a
Generic Aggregate RSVP Reservations September 2006 different preemption priorities, can be used to efficiently support
the preemption priorities of end-to-end reservations.
Virtual Destination Port and of an Extended Virtual Destination Port This document addresses this requirement for multiple aggregate
in the RSVP Session object. reservations for the same PHB (or same set of PHBs), by defining a
more flexible type of aggregate RSVP reservations, referred to as
generic aggregate reservations. This is achieved primarily by adding
the notions of a Virtual Destination Port and of an Extended Virtual
Destination Port in the RSVP Session object.
The notion of Virtual Destination Port was introduced in [RSVP-IPSEC] The notion of Virtual Destination Port was introduced in [RSVP-IPSEC]
to address a similar requirement (albeit in a different context) for to address a similar requirement (albeit in a different context) for
identification and demultiplexing of sessions beyond the IP identification and demultiplexing of sessions beyond the IP
destination address. This document reuses this notion from [RSVP- destination address. This document reuses this notion from [RSVP-
IPSEC] for identification and demultiplexing of generic aggregate IPSEC] for identification and demultiplexing of generic aggregate
sessions beyond the IP destination address and DSCP. This allows sessions beyond the IP destination address and PHB. This allows
multiple generic aggregate reservations to be established for a given multiple generic aggregate reservations to be established for a given
DSCP, from a given source IP address to a given destination IP PHB (or set of PHBs), from a given source IP address to a given
address. destination IP address.
[RSVP-TE] introduced the concept of an Extended Tunnel ID (in [RSVP-TE] introduced the concept of an Extended Tunnel ID (in
addition to the tunnel egress address and the Tunnel ID) in the addition to the tunnel egress address and the Tunnel ID) in the
Session object used to establish MPLS Traffic Engineering tunnels Session object used to establish MPLS Traffic Engineering tunnels
with RSVP. The Extended Tunnel ID provides a very convenient with RSVP. The Extended Tunnel ID provides a very convenient
mechanism for the tunnel ingress node to narrow the scope of the mechanism for the tunnel ingress node to narrow the scope of the
session to the ingress-egress pair. The ingress node can achieve this session to the ingress-egress pair. The ingress node can achieve this
by using one of its own IP addresses as a globally unique identifier by using one of its own IP addresses as a globally unique identifier
and including it in the Extended Tunnel ID and therefore within the and including it in the Extended Tunnel ID and therefore within the
Session object. This document reuses this notion of Extended Tunnel Session object. This document reuses this notion of Extended Tunnel
ID from [RSVP-TE], simply renaming it Extended Virtual Destination ID from [RSVP-TE], simply renaming it Extended Virtual Destination
Port. This provides a convenient mechanism to narrow the scope of a Port. This provides a convenient mechanism to narrow the scope of a
generic aggregate session to an Aggregator-Deaggregator pair. generic aggregate session to an Aggregator-Deaggregator pair.
The RSVP Session object for generic aggregate reservations uses the
PHB Identification Code (PHB-ID) defined in [PHB-ID] to identify the
PHB, or set of PHBs, from which the Diffserv resources are to be
reserved. This is instead of using the Diffserv Code Point (DSCP) as
per [RSVP-AGG]. Using the PHB-ID instead of the DSCP allows explicit
indication of whether the Diffserv resources belong to a single PHB
or to a set of PHBs. It also facilitates handling of situations where
a generic aggregate reservation spans two (or more) Diffserv domains
which use different DSCP values for the same Diffserv PHB (or set of
PHBs) from which resources are reserved. This is because the PHB-ID
allows conveying of the PHB (or set of PHBs) independently of what
DSCP value(s) is used locally for that PHB (or set of PHBs).
The generic aggregate reservations may be used to aggregate end-to- The generic aggregate reservations may be used to aggregate end-to-
end RSVP reservations. This document also defines the procedures for end RSVP reservations. This document also defines the procedures for
Generic Aggregate RSVP Reservations January 2007
such aggregation. These procedures are based on those of [RSVP-AGG] such aggregation. These procedures are based on those of [RSVP-AGG]
and this document only specifies the differences with those. and this document only specifies the differences with those.
The generic aggregate reservations may also be used end-to-end The generic aggregate reservations may also be used end-to-end
directly by end-systems attached to a Diffserv network. directly by end-systems attached to a Diffserv network.
1.1. Related RFCs and Internet-Drafts 1.1. Related IETF Documents
This document is heavily based on [RSVP-AGG]. It reuses [RSVP-AGG] This document is heavily based on [RSVP-AGG]. It reuses [RSVP-AGG]
wherever applicable and only specifies the necessary extensions wherever applicable and only specifies the necessary extensions
beyond [RSVP-AGG]. beyond [RSVP-AGG].
The mechanisms defined in [BW-REDUC] allow an existing reservation to The mechanisms defined in [BW-REDUC] allow an existing reservation to
be reduced in allocated bandwidth by RSVP routers in lieu of tearing be reduced in allocated bandwidth by RSVP routers in lieu of tearing
that reservation down. These mechanisms are applicable to the generic that reservation down. These mechanisms are applicable to the generic
aggregate reservations defined in the present document. aggregate reservations defined in the present document.
[RSVP-TUNNEL] describes a general approach to running RSVP over [RSVP-TUNNEL] describes a general approach to running RSVP over
various types of tunnels. One of these types of tunnel, referred to various types of tunnels. One of these types of tunnel, referred to
as a "type 2 tunnel", has some similarity with the generic aggregate as a "type 2 tunnel", has some similarity with the generic aggregate
reservations described in this document. The similarity stems from reservations described in this document. The similarity stems from
Generic Aggregate RSVP Reservations September 2006
the fact that a single, aggregate reservation is made for the tunnel the fact that a single, aggregate reservation is made for the tunnel
while many individual flows are carried over that tunnel. However, while many individual flows are carried over that tunnel. However,
[RSVP-TUNNEL] does not address the use of Diffserv-based [RSVP-TUNNEL] does not address the use of Diffserv-based
classification and scheduling in the core of a network (between classification and scheduling in the core of a network (between
tunnel endpoints), but rather relies on a UDP/IP tunnel header for tunnel endpoints), but rather relies on a UDP/IP tunnel header for
classification. This is why [RSVP-AGG] required additional objects classification. This is why [RSVP-AGG] required additional objects
and procedures beyond those of [RSVP-TUNNEL]. Like [RSVP-AGG], this and procedures beyond those of [RSVP-TUNNEL]. Like [RSVP-AGG], this
document also assumes the use of Diffserv-based classification and document also assumes the use of Diffserv-based classification and
scheduling in the aggregation region and, thus, requires additional scheduling in the aggregation region and, thus, requires additional
objects and procedures beyond those of [RSVP-TUNNEL]. objects and procedures beyond those of [RSVP-TUNNEL].
skipping to change at page 6, line 32 skipping to change at page 6, line 53
1.2. Organization Of This Document 1.2. Organization Of This Document
Section 2 defines the new RSVP objects related to generic aggregate Section 2 defines the new RSVP objects related to generic aggregate
reservations and to aggregation of E2E reservations onto those. reservations and to aggregation of E2E reservations onto those.
Section 3 describes the processing rules for handling of generic Section 3 describes the processing rules for handling of generic
aggregate reservations. Section 4 specifies the procedures for aggregate reservations. Section 4 specifies the procedures for
aggregation of end to end RSVP reservations over generic aggregate aggregation of end to end RSVP reservations over generic aggregate
RSVP reservations. Section 5 provides example usage of how the RSVP reservations. Section 5 provides example usage of how the
generic aggregate reservations may be used. generic aggregate reservations may be used.
The Security Considerations and the IANA Considerations are The Security Considerations and the IANA Considerations are discussed
discussed in Section 6 and 7, respectively. in Section 6 and 7, respectively.
Generic Aggregate RSVP Reservations January 2007
Finally, Appendix 1 provides an example signaling flow is Finally, Appendix 1 provides an example signaling flow is
illustrating aggregation of E2E RSVP reservations onto generic illustrating aggregation of E2E RSVP reservations onto generic
aggregate RSVP reservations. aggregate RSVP reservations.
2. Object Definition 2. Object Definition
This document reuses the RSVP-AGGREGATE-IP4 FILTER_SPEC, RSVP- This document reuses the RSVP-AGGREGATE-IP4 FILTER_SPEC, RSVP-
AGGREGATE-IP6 FILTER_SPEC, RSVP-AGGREGATE-IP4 SENDER_TEMPLATE and AGGREGATE-IP6 FILTER_SPEC, RSVP-AGGREGATE-IP4 SENDER_TEMPLATE and
RSVP-AGGREGATE-IP6 SENDER_TEMPLATE objects defined in [RSVP-AGG]. RSVP-AGGREGATE-IP6 SENDER_TEMPLATE objects defined in [RSVP-AGG].
This document defines: This document defines:
- two new objects (GENERIC-AGGREGATE-IP4 SESSION and GENERIC- - two new objects (GENERIC-AGGREGATE-IP4 SESSION and GENERIC-
AGGREGATE-IP6 SESSION) under the existing SESSION Class, and AGGREGATE-IP6 SESSION) under the existing SESSION Class, and
- two new objects (GENERIC-AGG-IP4-SOI and GENERIC-AGG-IP6-SOI) - two new objects (GENERIC-AGG-IP4-SOI and GENERIC-AGG-IP6-SOI)
under a new SESSION-OF-INTEREST Class. under a new SESSION-OF-INTEREST Class.
Detailed description of these objects is provided below in this Detailed description of these objects is provided below in this
section. section.
Generic Aggregate RSVP Reservations September 2006
The GENERIC-AGGREGATE-IP4 SESSION and GENERIC-AGGREGATE-IP6 SESSION The GENERIC-AGGREGATE-IP4 SESSION and GENERIC-AGGREGATE-IP6 SESSION
objects are applicable to all types of RSVP messages. objects are applicable to all types of RSVP messages.
This specification only defines the use of the GENERIC-AGG-IP4-SOI This specification defines the use of the GENERIC-AGG-IP4-SOI and
and GENERIC-AGG-IP6-SOI objects in two circumstances: GENERIC-AGG-IP6-SOI objects in two circumstances:
- inside an E2E PathErr message which contains an error code of - inside an E2E PathErr message which contains an error code of
NEW-AGGREGATE-NEEDED in order to convey the session of a new NEW-AGGREGATE-NEEDED in order to convey the session of a new
generic aggregate reservation which needs to be established generic aggregate reservation which needs to be established
- inside an E2E Resv message in order to convey the session of - inside an E2E Resv message in order to convey the session of
the generic aggregate reservation onto which this E2E the generic aggregate reservation onto which this E2E
reservation needs to be mapped. reservation needs to be mapped.
Details of the corresponding procedures can be found in section 4. Details of the corresponding procedures can be found in section 4.
However, it is envisioned that the ability to signal, inside RSVP However, it is envisioned that the ability to signal, inside RSVP
messages, the Session of another reservation (which has some messages, the Session of another reservation (which has some
skipping to change at page 7, line 36 skipping to change at page 8, line 5
All the new objects defined in this document are optional with All the new objects defined in this document are optional with
respect to RSVP so that general RSVP implementations not concerned respect to RSVP so that general RSVP implementations not concerned
with generic aggregate reservations do not have to support these with generic aggregate reservations do not have to support these
objects. RSVP routers supporting generic aggregate IPv4 (respectively objects. RSVP routers supporting generic aggregate IPv4 (respectively
IPv6) reservations MUST support the GENERIC-AGGREGATE-IP4 SESSION IPv6) reservations MUST support the GENERIC-AGGREGATE-IP4 SESSION
object (respectively GENERIC-AGGREGATE-IP6 SESSION). RSVP routers object (respectively GENERIC-AGGREGATE-IP6 SESSION). RSVP routers
supporting RSVP aggregation over generic aggregate IPv4 (respectively supporting RSVP aggregation over generic aggregate IPv4 (respectively
IPv6) reservations MUST support the GENERIC-AGG-IP4-SOI object IPv6) reservations MUST support the GENERIC-AGG-IP4-SOI object
(respectively GENERIC-AGG-IP6-SOI). (respectively GENERIC-AGG-IP6-SOI).
Generic Aggregate RSVP Reservations January 2007
2.1. SESSION Class 2.1. SESSION Class
o GENERIC-AGGREGATE-IP4 SESSION object: o GENERIC-AGGREGATE-IP4 SESSION object:
Class = 1 (SESSION) Class = 1 (SESSION)
C-Type = To be allocated by IANA C-Type = To be allocated by IANA
0 7 8 15 16 23 24 31 0 7 8 15 16 23 24 31
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| IPv4 DestAddress (4 bytes) | | IPv4 DestAddress (4 bytes) |
+-------------+-------------+-------------+--+----------+ +-------------+-------------+-------------+-------------+
| Reserved | Flags | vDstPort |Rd| DSCP | | Reserved | Flags | PHB-ID |
+-------------+-------------+-------------+--+----------+ +-------------+-------------+-------------+-------------+
| Reserved | vDstPort |
+-------------+-------------+-------------+-------------+
| Extended vDstPort | | Extended vDstPort |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
0 7 8 15 16 23 24 31 0 7 8 15 16 23 24 31
IPv4 DestAddress (IPv4 Destination Address) IPv4 DestAddress (IPv4 Destination Address)
IPv4 address of the receiver (or Deaggregator) IPv4 address of the receiver (or Deaggregator)
Generic Aggregate RSVP Reservations September 2006
Reserved Reserved
A 8-bit field. All bits MUST be set to 0 on transmit. This field A 8-bit field. All bits MUST be set to 0 on transmit. This field
MUST be ignored on receipt. MUST be ignored on receipt.
Flags Flags
A 8-bit field. The content and processing of this field are the A 8-bit field. The content and processing of this field are the
same as for the Flags field of the IPv4/UDP SESSION object (see same as for the Flags field of the IPv4/UDP SESSION object (see
[RSVP]) [RSVP])
VDstPort (Virtual Destination Port) PHB-ID (Per Hop Behavior Identification Code)
An 8-bit identifier used in the SESSION that remains constant A 16-bit field containing the Per Hop Behavior Identification
over the life of the generic aggregate reservation. Code of the PHB, or of the set of PHBs, from which Diffserv
resources are to be reserved. This field MUST be encoded as
specified in section 2 of [PHB-ID].
Rd (Reserved) Reserved
A 2-bit field. All bits MUST be set to 0 on transmit. This field A 16-bit field. All bits MUST be set to 0 on transmit. This
MUST be ignored on receipt. field MUST be ignored on receipt.
DSCP (Diffserv Code Point) Generic Aggregate RSVP Reservations January 2007
A 6-bit field containing the DSCP of the PHB from which Diffserv VDstPort (Virtual Destination Port)
resources are to be reserved.
A 16-bit identifier used in the SESSION that remains constant
over the life of the generic aggregate reservation.
Extended vDstPort (Extended Virtual Destination Port) Extended vDstPort (Extended Virtual Destination Port)
A 32-bit identifier used in the SESSION that remains constant A 32-bit identifier used in the SESSION that remains constant
over the life of the generic aggregate reservation. over the life of the generic aggregate reservation.
A sender (or Aggregator) that wishes to narrow the scope of a A sender (or Aggregator) that wishes to narrow the scope of a
SESSION to the sender-receiver pair (or Aggregator-Deaggregator SESSION to the sender-receiver pair (or Aggregator-Deaggregator
pair) SHOULD place its IPv4 address here as a network unique pair) SHOULD place its IPv4 address here as a network unique
identifier. A sender (or Aggregator) that wishes to use a common identifier. A sender (or Aggregator) that wishes to use a common
session with other senders (or Aggregators) in order to use a session with other senders (or Aggregators) in order to use a
shared reservation across senders (or Aggregators) MUST set this shared reservation across senders (or Aggregators) MUST set this
field to all zeros. field to all zeros.
o GENERIC-AGGREGATE-IP6 SESSION object: o GENERIC-AGGREGATE-IP6 SESSION object:
Class = 1 (SESSION) Class = 1 (SESSION)
C-Type = To be allocated by IANA C-Type = To be allocated by IANA
Generic Aggregate RSVP Reservations September 2006
0 7 8 15 16 23 24 31 0 7 8 15 16 23 24 31
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| | | |
+ + + +
| | | |
+ IPv6 DestAddress (16 bytes) + + IPv6 DestAddress (16 bytes) +
| | | |
+ + + +
| | | |
+-------------+-------------+-------------+--+----------+ +-------------+-------------+-------------+-------------+
| Reserved | Flags | vDstPort |Rd| DSCP | | Reserved | Flags | PHB-ID |
+-------------+-------------+-------------+--+----------+ +-------------+-------------+-------------+-------------+
| Reserved | vDstPort |
+-------------+-------------+-------------+-------------+
| | | |
+ + + +
| Extended vDstPort | | Extended vDstPort |
+ + + +
| (16 bytes) | | (16 bytes) |
+ + + +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 7 8 15 16 25 26 31 0 7 8 15 16 25 26 31
Generic Aggregate RSVP Reservations January 2007
IPv6 DestAddress (IPv6 Destination Address) IPv6 DestAddress (IPv6 Destination Address)
IPv6 address of the receiver (or Deaggregator) IPv6 address of the receiver (or Deaggregator)
Reserved Reserved
A 8-bit field. All bits MUST be set to 0 on transmit. This field A 8-bit field. All bits MUST be set to 0 on transmit. This field
MUST be ignored on receipt. MUST be ignored on receipt.
Flags Flags
A 8-bit field. The content and processing of this field are the A 8-bit field. The content and processing of this field are the
same as for the Flags field of the IPv6/UDP SESSION object (see same as for the Flags field of the IPv6/UDP SESSION object (see
[RSVP]) [RSVP])
VDstPort (Virtual Destination Port) PHB-ID (Per Hop Behavior Identification Code)
A 8-bit identifier used in the SESSION that remains constant
over the life of the generic aggregate reservation.
Rd (Reserved) A 16-bit field containing the Per Hop Behavior Identification
Code of the PHB, or of the set of PHBs, from which Diffserv
resources are to be reserved. This field MUST be encoded as
specified in section 2 of [PHB-ID].
Generic Aggregate RSVP Reservations September 2006 Reserved
A 2-bit field. All bits MUST be set to 0 on transmit. This field A 16-bit field. All bits MUST be set to 0 on transmit. This
MUST be ignored on receipt. field MUST be ignored on receipt.
DSCP (Diffserv Code Point) VDstPort (Virtual Destination Port)
A 6-bit field containing the DSCP of the PHB from which Diffserv A 16-bit identifier used in the SESSION that remains constant
resources are to be reserved over the life of the generic aggregate reservation.
Extended vDstPort (Extended Virtual Destination Port) Extended vDstPort (Extended Virtual Destination Port)
A 128-bit identifier used in the SESSION that remains constant A 128-bit identifier used in the SESSION that remains constant
over the life of the generic aggregate reservation. over the life of the generic aggregate reservation.
A sender (or Aggregator) that wishes to narrow the scope of a A sender (or Aggregator) that wishes to narrow the scope of a
SESSION to the sender-receiver pair (or Aggregator-Deaggregator SESSION to the sender-receiver pair (or Aggregator-Deaggregator
pair) SHOULD place its IPv6 address here as a network unique pair) SHOULD place its IPv6 address here as a network unique
identifier. A sender (or Aggregator) that wishes to use a common identifier. A sender (or Aggregator) that wishes to use a common
session with other senders (or Aggregators) in order to use a session with other senders (or Aggregators) in order to use a
shared reservation across senders (or Aggregators) MUST set this shared reservation across senders (or Aggregators) MUST set this
field to all zeros. field to all zeros.
Generic Aggregate RSVP Reservations January 2007
2.2. SESSION-OF-INTEREST (SOI) Class 2.2. SESSION-OF-INTEREST (SOI) Class
o GENERIC-AGG-IP4-SOI object: o GENERIC-AGG-IP4-SOI object:
Class = To be allocated by IANA Class = To be allocated by IANA
C-Type = To be allocated by IANA C-Type = To be allocated by IANA
0 7 8 15 16 23 24 31 0 7 8 15 16 23 24 31
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| | SOI |GEN-AGG-IP4- | | | SOI |GEN-AGG-IP4- |
| Length (bytes) | Class-Num |SOI C-Type | | Length (bytes) | Class-Num |SOI C-Type |
skipping to change at page 11, line 4 skipping to change at page 11, line 31
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
Content of a GENERIC-AGGREGATE-IP4 SESSION Object: Content of a GENERIC-AGGREGATE-IP4 SESSION Object:
This field contains a copy of the Session object of the session This field contains a copy of the Session object of the session
which is of interest for the reservation. In the case of a which is of interest for the reservation. In the case of a
GENERIC-AGG-IP4-SOI, the session of interest conveyed in this GENERIC-AGG-IP4-SOI, the session of interest conveyed in this
field is a GENERIC-AGGREGATE-IP4 SESSION. field is a GENERIC-AGGREGATE-IP4 SESSION.
o GENERIC-AGG-IP6-SOI object: o GENERIC-AGG-IP6-SOI object:
Generic Aggregate RSVP Reservations September 2006
Class = To be allocated by IANA Class = To be allocated by IANA
(same as for GENERIC-AGG-IP4-SOI) (same as for GENERIC-AGG-IP4-SOI)
C-Type = To be allocated by IANA C-Type = To be allocated by IANA
0 7 8 15 16 23 24 31 0 7 8 15 16 23 24 31
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| | SOI |GEN-AGG-IP6- | | | SOI |GEN-AGG-IP6- |
| Length (bytes) | Class-Num |SOI C-Type | | Length (bytes) | Class-Num |SOI C-Type |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| | | |
skipping to change at page 11, line 28 skipping to change at page 12, line 5
| | | |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
Content of a GENERIC-AGGREGATE-IP6 SESSION Object: Content of a GENERIC-AGGREGATE-IP6 SESSION Object:
This field contains a copy of the Session object of the session This field contains a copy of the Session object of the session
which is of interest for the reservation. In the case of a which is of interest for the reservation. In the case of a
GENERIC-AGG-IP6-SOI, the session of interest conveyed in this GENERIC-AGG-IP6-SOI, the session of interest conveyed in this
field is a GENERIC-AGGREGATE-IP6 SESSION. field is a GENERIC-AGGREGATE-IP6 SESSION.
Generic Aggregate RSVP Reservations January 2007
For example, if a SESSION-OF-INTEREST object is used inside an E2E For example, if a SESSION-OF-INTEREST object is used inside an E2E
Resv message (as per the procedures defined in section 4) to indicate Resv message (as per the procedures defined in section 4) to indicate
which generic aggregate IPv4 session the E2E reservation is to be which generic aggregate IPv4 session the E2E reservation is to be
mapped onto, then the GENERIC-AGG-IP4-SOI object will be used and it mapped onto, then the GENERIC-AGG-IP4-SOI object will be used and it
will be encoded like this: will be encoded like this:
0 7 8 15 16 23 24 31 0 7 8 15 16 23 24 31
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| | SOI |GEN-AGG-IP4- | | | SOI |GEN-AGG-IP4- |
| Length (bytes) | Class-Num |SOI C-Type | | Length (bytes) | Class-Num |SOI C-Type |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| IPv4 DestAddress (4 bytes) | | IPv4 DestAddress (4 bytes) |
+-------------+-------------+-------------+--+----------+ +-------------+-------------+-------------+--+----------+
| Reserved | Flags | vDstPort |Rd| DSCP | | Reserved | Flags | PHB-ID |
+-------------+-------------+-------------+--+----------+ +-------------+-------------+-------------+-------------+
| Reserved | vDstPort |
+-------------+-------------+-------------+-------------+
| Extended vDstPort | | Extended vDstPort |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
0 7 8 15 16 23 24 31 0 7 8 15 16 23 24 31
Note that a SESSION-OF-INTEREST object is not a SESSION object in Note that a SESSION-OF-INTEREST object is not a SESSION object in
itself. It does not replace the SESSION object in RSVP messages. It itself. It does not replace the SESSION object in RSVP messages. It
does not modify the usage of the SESSION object in RSVP messages. It does not modify the usage of the SESSION object in RSVP messages. It
simply allows conveying the Session of another RSVP reservation simply allows conveying the Session of another RSVP reservation
inside RSVP signaling messages, for some particular purposes. In the inside RSVP signaling messages, for some particular purposes. In the
context of this document, it is used to convey, inside an E2E RSVP context of this document, it is used to convey, inside an E2E RSVP
message pertaining to an end-to-end reservation, the Session of a message pertaining to an end-to-end reservation, the Session of a
Generic Aggregate RSVP Reservations September 2006
generic aggregate reservation associated with the E2E reservation. generic aggregate reservation associated with the E2E reservation.
Details for the corresponding procedures are specified in section 4. Details for the corresponding procedures are specified in section 4.
3. Processing Rules For Handling Generic Aggregate RSVP Reservations 3. Processing Rules For Handling Generic Aggregate RSVP Reservations
This section presents additions to the Processing Rules presented in This section presents additions to the Processing Rules presented in
[RSVP-PROCESS]. These additions are required in order to properly [RSVP-PROCESS]. These additions are required in order to properly
process the GENERIC-AGGREGATE-IP4 (resp. GENERIC-AGGREGATE-IP6) process the GENERIC-AGGREGATE-IP4 (resp. GENERIC-AGGREGATE-IP6)
SESSION object and the RSVP-AGGREGATE-IP4 (resp. RSVP-AGGREGATE-IP6) SESSION object and the RSVP-AGGREGATE-IP4 (resp. RSVP-AGGREGATE-IP6)
FILTER_SPEC object. Values for referenced error codes can be found in FILTER_SPEC object. Values for referenced error codes can be found in
[RSVP]. As with the other RSVP documents, values for internally [RSVP]. As with the other RSVP documents, values for internally
reported (API) errors are not defined. reported (API) errors are not defined.
When referring to the new GENERIC-AGGREGATE-IP4 and GENERIC- When referring to the new GENERIC-AGGREGATE-IP4 and GENERIC-
AGGREGATE-IP6 SESSION objects, IP version will not be included and AGGREGATE-IP6 SESSION objects, IP version will not be included and
they will be referred to simply as GENERIC-AGGREGATE SESSION, unless they will be referred to simply as GENERIC-AGGREGATE SESSION, unless
a specific distinction between IPv4 and IPv6 is being made. a specific distinction between IPv4 and IPv6 is being made.
Generic Aggregate RSVP Reservations January 2007
When referring to the [RSVP-AGG] RSVP-AGGREGATE-IP4 and When referring to the [RSVP-AGG] RSVP-AGGREGATE-IP4 and
RSVP-AGGREGATE-IP6 SESSION, FILTER_SPEC and SENDER_TEMPLATE objects, RSVP-AGGREGATE-IP6 SESSION, FILTER_SPEC and SENDER_TEMPLATE objects,
IP version will not be included and they will be referred to simply IP version will not be included and they will be referred to simply
as RSVP-AGGREGATE, unless a specific distinction between IPv4 and as RSVP-AGGREGATE, unless a specific distinction between IPv4 and
IPv6 is being made. IPv6 is being made.
3.1. Required Changes to Path and Resv Processing 3.1. Required Changes to Path and Resv Processing
Both RESV and PATH processing will need to be changed to support the Both RESV and PATH processing need to be changed to support the new
new objects. objects.
The following PATH message processing changes are required: The following PATH message processing changes are required:
o When a session is defined using the GENERIC-AGGREGATE SESSION o When a session is defined using the GENERIC-AGGREGATE SESSION
object, only the [RSVP-AGG] RSVP-AGGREGATE SENDER_TEMPLATE may object, only the [RSVP-AGG] RSVP-AGGREGATE SENDER_TEMPLATE may
be used. When this condition is violated in a PATH message be used. When this condition is violated in a PATH message
received by an RSVP end-station, the RSVP end-station SHOULD received by an RSVP end-station, the RSVP end-station SHOULD
report a "Conflicting C-Type" API error to the application. report a "Conflicting C-Type" API error to the application.
When this condition is violated in a PATH message received by When this condition is violated in a PATH message received by
an RSVP router, the RSVP router MUST consider this as a an RSVP router, the RSVP router MUST consider this as a
message formatting error. message formatting error.
o For PATH messages that contain the GENERIC-AGGREGATE SESSION o For PATH messages that contain the GENERIC-AGGREGATE SESSION
object, the VDstPort value, the Extended VDstPort value and object, the VDstPort value, the Extended VDstPort value and
the DSCP value should be recorded (in addition to the the PHB-ID value should be recorded (in addition to the
destination/Deaggregator address and source/aggregator destination/Deaggregator address and source/aggregator
address). These values form part of the recorded state of the address). These values form part of the recorded state of the
session. The DSCP may need to be passed to traffic control; session. The PHB-ID may need to be passed to traffic control;
however the vDstPort and Extended VDstPort are not passed to however the vDstPort and Extended VDstPort are not passed to
Generic Aggregate RSVP Reservations September 2006
traffic control since they do not appear inside the data traffic control since they do not appear inside the data
packets of the corresponding reservation. packets of the corresponding reservation.
The changes to RESV message processing are: The changes to RESV message processing are:
o When a RESV message contains a [RSVP-AGG] RSVP-AGGREGATE o When a RESV message contains a [RSVP-AGG] RSVP-AGGREGATE
FILTER_SPEC, the session MUST be defined using either the FILTER_SPEC, the session MUST be defined using either the
RSVP-AGGREGATE SESSION object (as per [RSVP-AGG]) or the RSVP-AGGREGATE SESSION object (as per [RSVP-AGG]) or the
GENERIC-AGGREGATE SESSION object (as per this document). If GENERIC-AGGREGATE SESSION object (as per this document). If
this condition is not met, an RSVP router or end-station MUST this condition is not met, an RSVP router or end-station MUST
consider that there is a message formatting error. consider that there is a message formatting error.
o When the RSVP-AGGREGATE FILTER_SPEC is used and the SESSION o When the RSVP-AGGREGATE FILTER_SPEC is used and the SESSION
type is GENERIC-AGGREGATE, each node MAY have a data type is GENERIC-AGGREGATE, each node uses data classifier as
classifier installed for the flow: per the following:
* If the node needs to perform fine-grain classification (for * to perform Diffserv classification the node MUST rely on the
example to perform fine-grain policing on ingress at a trust Diffserv data classifier based on the DSCP only. The
relevant DSCP value(s) is the one (are those) associated
with the PHB-ID of the generic aggregate reservation.
Generic Aggregate RSVP Reservations January 2007
* If the node also needs to perform fine-grain classification
(for example to perform fine-grain input policing at a trust
boundary) then the node MUST create a data classifier boundary) then the node MUST create a data classifier
described by the 3-tuple <DestAddress, SrcAddress, DSCP>. described by the 3-tuple <DestAddress, SrcAddress, DSCP>.
The relevant DSCP value(s) is the one (are those) associated
with the PHB-ID of the generic aggregate reservation.
Note that if multiple reservations are established with Note that if multiple generic aggregate reservations are
different Virtual Destination Ports (and/or different established with different Virtual Destination Ports (and/or
Extended Virtual Destination Ports) but with the same different Extended Virtual Destination Ports) but with the
<DestAddress, SrcAddress, DSCP>, then those cannot be same <DestAddress, SrcAddress, PHB-ID>, then those cannot be
distinguished by the classifier. If the router is using the distinguished by the classifier. If the router is using the
classifier for policing purposes, the router will therefore classifier for policing purposes, the router will therefore
police those together and MUST program the policing rate to police those together and MUST program the policing rate to
the sum of the reserved rate across all the corresponding the sum of the reserved rate across all the corresponding
reservations. reservations.
* If the node only needs to perform Diffserv classification
(for example inside the aggregation domain downstream of the
trust boundary) then the node MUST rely on the Diffserv data
classifier based on the DSCP only.
4. Procedures for Aggregation over Generic Aggregate RSVP Reservations 4. Procedures for Aggregation over Generic Aggregate RSVP Reservations
The procedures for aggregation of E2E reservations over generic The procedures for aggregation of E2E reservations over generic
aggregate RSVP reservations are the same as the procedures specified aggregate RSVP reservations are the same as the procedures specified
in [RSVP-AGG] with the exceptions of the procedure changes listed in in [RSVP-AGG] with the exceptions of the procedure changes listed in
this section. this section.
As specified in [RSVP-AGG], the Deaggregator is responsible for As specified in [RSVP-AGG], the Deaggregator is responsible for
mapping a given E2E reservation on a given aggregate reservation. The mapping a given E2E reservation on a given aggregate reservation. The
Deaggregator requests establishment of a new aggregate reservation by Deaggregator requests establishment of a new aggregate reservation by
sending to the Aggregator an E2E PathErr message with an error code sending to the Aggregator an E2E PathErr message with an error code
of NEW-AGGREGATE-NEEDED. In [RSVP-AGG], the Deaggregator conveys the of NEW-AGGREGATE-NEEDED. In [RSVP-AGG], the Deaggregator conveys the
Generic Aggregate RSVP Reservations September 2006
DSCP of the new requested aggregate reservation by including a DCLASS DSCP of the new requested aggregate reservation by including a DCLASS
Object in the E2E PathErr and encoding the corresponding DSCP inside. Object in the E2E PathErr and encoding the corresponding DSCP inside.
This document modifies and extends this procedure. The Deaggregator This document modifies and extends this procedure. The Deaggregator
MUST include in the E2E PathErr message, a SESSION-OF-INTEREST object MUST include in the E2E PathErr message, a SESSION-OF-INTEREST object
which contains the GENERIC-AGGREGATE Session to be used for which contains the GENERIC-AGGREGATE Session to be used for
establishment of the requested generic aggregate reservation. Since establishment of the requested generic aggregate reservation. Since
this GENERIC-AGGREGATE SESSION contains the DSCP, the DCLASS object this GENERIC-AGGREGATE SESSION contains the PHB-ID, the DCLASS object
need not be included in the PathErr message. need not be included in the PathErr message.
Note that the Deaggregator can easily ensure that different Note that the Deaggregator can easily ensure that different
Aggregators use different sessions for their Aggregate Path towards a Aggregators use different sessions for their Aggregate Path towards a
given Deaggregator. This is because the Deaggregator can easily given Deaggregator. This is because the Deaggregator can easily
select VDstPort and/or Extended VDstPort numbers which are different select VDstPort and/or Extended VDstPort numbers which are different
for each Aggregator (for example by using the Aggregator address as for each Aggregator (for example by using the Aggregator address as
the Extended VDstPort) and can communicate those inside the GENERIC- the Extended VDstPort) and can communicate those inside the GENERIC-
AGGREGATE SESSION included in the SESSION-OF-INTEREST object. This AGGREGATE SESSION included in the SESSION-OF-INTEREST object. This
provides an easy solution to establish separate reservations from provides an easy solution to establish separate reservations from
every Aggregator to a given Deaggregator. Conversely, if reservation every Aggregator to a given Deaggregator. Conversely, if reservation
sharing were needed across multiple Aggregators, the Deaggregator sharing were needed across multiple Aggregators, the Deaggregator
Generic Aggregate RSVP Reservations January 2007
could facilitate this by allocating the same VDstPort and Extended could facilitate this by allocating the same VDstPort and Extended
VDstPort to the multiple Aggregators and thus including the same VDstPort to the multiple Aggregators and thus including the same
GENERIC-AGGREGATE SESSION inside the SESSION-OF-INTEREST object in GENERIC-AGGREGATE SESSION inside the SESSION-OF-INTEREST object in
the E2E PathErr messages sent to these Aggregators. The Aggregators the E2E PathErr messages sent to these Aggregators. The Aggregators
could then all establish an Aggregate Path with the same GENERIC- could then all establish an Aggregate Path with the same GENERIC-
AGGREGATE SESSION. AGGREGATE SESSION.
Therefore various sharing scenarios can easily be supported. Policies Therefore various sharing scenarios can easily be supported. Policies
followed by the Deaggregator to determine which aggregators need followed by the Deaggregator to determine which aggregators need
shared or separate reservations are beyond the scope of this document. shared or separate reservations are beyond the scope of this document.
skipping to change at page 15, line 4 skipping to change at page 15, line 37
are extended correspondingly. On receipt of such a message containing are extended correspondingly. On receipt of such a message containing
a SESSION-OF-INTEREST object, the Aggregator MUST trigger a SESSION-OF-INTEREST object, the Aggregator MUST trigger
establishment of a generic aggregate reservation. In particular, it establishment of a generic aggregate reservation. In particular, it
MUST start sending aggregate Path messages with the GENERIC-AGGREGATE MUST start sending aggregate Path messages with the GENERIC-AGGREGATE
SESSION found in the received SESSION-OF-INTEREST object. When an SESSION found in the received SESSION-OF-INTEREST object. When an
RSVP Signaled Preemption Priority Policy Element is contained in the RSVP Signaled Preemption Priority Policy Element is contained in the
received E2E PathErr message, the Aggregator MUST include this object received E2E PathErr message, the Aggregator MUST include this object
in the Aggregate Path for the corresponding generic aggregate in the Aggregate Path for the corresponding generic aggregate
reservation. When other additional objects are contained in the reservation. When other additional objects are contained in the
received E2E PathErr message and those can be unambiguously received E2E PathErr message and those can be unambiguously
Generic Aggregate RSVP Reservations September 2006
interpreted as related to the new needed generic aggregate interpreted as related to the new needed generic aggregate
reservation (as opposed to related to the E2E reservation), the reservation (as opposed to related to the E2E reservation), the
Aggregator SHOULD include those in the Aggregate Path for the Aggregator SHOULD include those in the Aggregate Path for the
corresponding generic aggregate reservation. The Aggregator MUST use corresponding generic aggregate reservation. The Aggregator MUST use
as the Source Address (i.e. as the Aggregator Address in the Sender- as the Source Address (i.e. as the Aggregator Address in the Sender-
Template) for the generic aggregate reservation, the address it uses Template) for the generic aggregate reservation, the address it uses
to identify itself as the PHOP when forwarding the E2E Path messages to identify itself as the PHOP when forwarding the E2E Path messages
corresponding to the E2E PathErr message. corresponding to the E2E PathErr message.
The Deaggregator follows the same procedures as described in [RSVP- The Deaggregator follows the same procedures as described in [RSVP-
AGG] for establishing, maintaining and clearing the aggregate Resv AGG] for establishing, maintaining and clearing the aggregate Resv
state. However, in this document, the Deaggregator MUST use the state. However, a Deaggregator behaving according to the present
generic aggregate reservations and hence use the GENERIC-AGGREGATE specification MUST use the generic aggregate reservations and hence
SESSION specified earlier in this document. use the GENERIC-AGGREGATE SESSION specified earlier in this document.
This document also modifies the procedures of [RSVP-AGG] related to This document also modifies the procedures of [RSVP-AGG] related to
exchange of E2E Resv messages between Deaggregator and Aggregator. exchange of E2E Resv messages between Deaggregator and Aggregator.
The Deaggregator MUST include the new SESSION-OF-INTEREST object in The Deaggregator MUST include the new SESSION-OF-INTEREST object in
the E2E Resv message, in order to indicate to the Aggregator the the E2E Resv message, in order to indicate to the Aggregator the
Generic Aggregate RSVP Reservations January 2007
generic aggregate session to map a given E2E reservation onto. Again, generic aggregate session to map a given E2E reservation onto. Again,
since the GENERIC-AGGREGATE SESSION (included in the SESSION-OF- since the GENERIC-AGGREGATE SESSION (included in the SESSION-OF-
INTEREST object) contains the DSCP, the DCLASS object need not be INTEREST object) contains the PHB-ID, the DCLASS object need not be
included in the E2E Resv message. The Aggregator MUST interpret the included in the E2E Resv message. The Aggregator MUST interpret the
SESSION-OF-INTEREST object in the E2E Resv as indicating which SESSION-OF-INTEREST object in the E2E Resv as indicating which
generic aggregate reservation session the corresponding E2E generic aggregate reservation session the corresponding E2E
reservation is mapped onto. The Aggregator MUST not include the reservation is mapped onto. The Aggregator MUST not include the
SESSION-OF-INTEREST object when sending an E2E Resv upstream towards SESSION-OF-INTEREST object when sending an E2E Resv upstream towards
the sender. the sender.
Based on relevant policy, the Deaggregator may decide at some point Based on relevant policy, the Deaggregator may decide at some point
that an aggregate reservation is no longer needed and should be torn that an aggregate reservation is no longer needed and should be torn
down. In that case, the Deaggregator MUST send an aggregate ResvTear. down. In that case, the Deaggregator MUST send an aggregate ResvTear.
skipping to change at page 16, line 4 skipping to change at page 16, line 37
communicate their respective identity to each other. For example the communicate their respective identity to each other. For example the
Aggregator includes one of its IP addresses in the RSVP HOP object in Aggregator includes one of its IP addresses in the RSVP HOP object in
the E2E Path which is transmitted downstream and received by the the E2E Path which is transmitted downstream and received by the
Deaggregator once it traversed the aggregation region. Similarly, the Deaggregator once it traversed the aggregation region. Similarly, the
Deaggregator identifies itself to the Aggregator by including one of Deaggregator identifies itself to the Aggregator by including one of
its IP addresses in various fields, including the ERROR SPECIFICATION its IP addresses in various fields, including the ERROR SPECIFICATION
of the E2E PathErr message (containing the NEW-AGGREGATE-NEEDED Error of the E2E PathErr message (containing the NEW-AGGREGATE-NEEDED Error
Code) and in the RSVP HOP object of the E2E Resv message. However, Code) and in the RSVP HOP object of the E2E Resv message. However,
[RSVP-AGG] does not discuss which IP addresses are to be selected by [RSVP-AGG] does not discuss which IP addresses are to be selected by
the aggregator and Deaggregator for such purposes. Because these the aggregator and Deaggregator for such purposes. Because these
Generic Aggregate RSVP Reservations September 2006
addresses are intended to identify the Aggregator and Deaggregator addresses are intended to identify the Aggregator and Deaggregator
and not to identify any specific interface on these devices, this and not to identify any specific interface on these devices, this
document RECOMMENDS that the Aggregator and Deaggregator SHOULD use document RECOMMENDS that the Aggregator and Deaggregator SHOULD use
interface-independent addresses (for example a loopback address) interface-independent addresses (for example a loopback address)
whenever they communicate their respective identity to each other. whenever they communicate their respective identity to each other.
This ensures that respective identification of the Aggregator and This ensures that respective identification of the Aggregator and
Deaggregator is not impacted by any interface state change on these Deaggregator is not impacted by any interface state change on these
devices. In turns this results in more stable operations and devices. In turns this results in more stable operations and
considerably reduced RSVP signaling in the aggregation region. For considerably reduced RSVP signaling in the aggregation region. For
example, if interface-independent addresses are used by the example, if interface-independent addresses are used by the
Aggregator and the Deaggregator, then a failure of an interface on Aggregator and the Deaggregator, then a failure of an interface on
these devices may simply result in the rerouting of a given generic these devices may simply result in the rerouting of a given generic
aggregate reservation but will not result in the generic aggregate aggregate reservation but will not result in the generic aggregate
reservation having to be torn down and another one established, nor reservation having to be torn down and another one established, nor
will it result in a change of mapping of E2E reservations on generic will it result in a change of mapping of E2E reservations on generic
aggregate reservations (assuming the Aggregator and Deaggregator aggregate reservations (assuming the Aggregator and Deaggregator
still have reachability after the failure and the Aggregator and still have reachability after the failure and the Aggregator and
Deaggregator are still on the shortest path to the destination). Deaggregator are still on the shortest path to the destination).
Generic Aggregate RSVP Reservations January 2007
However, when identifying themselves to real RSVP neighbors (i.e. However, when identifying themselves to real RSVP neighbors (i.e.
neighbors which are not on the other side of the aggregation region), neighbors which are not on the other side of the aggregation region),
the Aggregator and Deaggregator SHOULD continue using interface- the Aggregator and Deaggregator SHOULD continue using interface-
dependent addresses as per regular [RSVP] procedures. This applies dependent addresses as per regular [RSVP] procedures. This applies
for example when the Aggregator identifies itself downstream as a for example when the Aggregator identifies itself downstream as a
PHOP for the generic aggregate reservation or identifies itself PHOP for the generic aggregate reservation or identifies itself
upstream as a NHOP for an E2E reservation. This also applies when the upstream as a NHOP for an E2E reservation. This also applies when the
Deaggregator identifies itself downstream as a PHOP for the E2E Deaggregator identifies itself downstream as a PHOP for the E2E
reservation or identifies itself upstream as a NHOP for the generic reservation or identifies itself upstream as a NHOP for the generic
aggregate reservation. As part of the processing of generic aggregate aggregate reservation. As part of the processing of generic aggregate
skipping to change at page 16, line 51 skipping to change at page 17, line 32
and Deaggregator) the operation of RSVP should be modeled with the and Deaggregator) the operation of RSVP should be modeled with the
notion that E2E reservations are mapped to aggregate reservations and notion that E2E reservations are mapped to aggregate reservations and
are no longer tied to physical interfaces (as was the case with are no longer tied to physical interfaces (as was the case with
regular RSVP). However, generic aggregate reservations (within the regular RSVP). However, generic aggregate reservations (within the
aggregation region) as well as E2E reservations outside the aggregation region) as well as E2E reservations outside the
aggregation region, retain the model of regular RVSP and remain tied aggregation region, retain the model of regular RVSP and remain tied
to physical interfaces. to physical interfaces.
As discussed above, generic aggregate reservations may be established As discussed above, generic aggregate reservations may be established
edge-to-edge as a result of the establishment of E2E reservations edge-to-edge as a result of the establishment of E2E reservations
(from outside the aggregation region) which are to be aggregated over (from outside the aggregation region) that are to be aggregated over
the aggregation region. However, generic aggregate reservations may the aggregation region. However, generic aggregate reservations may
also be used end-to-end by end-systems directly attached to a also be used end-to-end by end-systems directly attached to a
Diffserv domain, such as PSTN Gateways. In that case, the generic Diffserv domain, such as PSTN Gateways. In that case, the generic
aggregate reservations may be established by the end-systems in aggregate reservations may be established by the end-systems in
Generic Aggregate RSVP Reservations September 2006
response to application-level triggers such as voice call signaling. response to application-level triggers such as voice call signaling.
Alternatively, generic aggregate reservations may also be used edge- Alternatively, generic aggregate reservations may also be used edge-
to-edge to manage bandwidth in a Diffserv cloud even if RSVP is not to-edge to manage bandwidth in a Diffserv cloud even if RSVP is not
used end-to-end. A simple example of such a usage would be the static used end-to-end. A simple example of such a usage would be the static
configuration of a generic aggregate reservation for a certain configuration of a generic aggregate reservation for a certain
bandwidth for traffic from an ingress (Aggregator) router to an bandwidth for traffic from an ingress (Aggregator) router to an
egress (Deaggregator) router. egress (Deaggregator) router.
In this case, the establishment of the generic aggregate reservations In this case, the establishment of the generic aggregate reservations
is controlled by configuration on the Aggregator and on the is controlled by configuration on the Aggregator and on the
Deaggregator. Configuration on the Aggregator triggers generation of Deaggregator. Configuration on the Aggregator triggers generation of
the aggregate Path message and provides sufficient information to the the aggregate Path message and provides sufficient information to the
Aggregator to derive the content of the GENERIC-AGGREGATE SESSION Aggregator to derive the content of the GENERIC-AGGREGATE SESSION
object. This would typically include Deaggregator IP address, DSCP object. This would typically include Deaggregator IP address, PHB-ID
and possibly VDstPort. Configuration on the Deaggregator would and possibly VDstPort. Configuration on the Deaggregator would
instruct the Deaggregator to respond to a received generic aggregate instruct the Deaggregator to respond to a received generic aggregate
Path message and would provide sufficient information to the Path message and would provide sufficient information to the
Deaggregator to control the reservation. This may include bandwidth Deaggregator to control the reservation. This may include bandwidth
to be reserved by the Deaggregator (for a given
Deaggregator/DSCP/VDstPort tuple). Generic Aggregate RSVP Reservations January 2007
to be reserved by the Deaggregator (for a given Deaggregator/PHB-
ID/VDstPort tuple).
In the absence of E2E microflow reservations, the Aggregator can use In the absence of E2E microflow reservations, the Aggregator can use
a variety of policies to set the DSCP of packets passing into the a variety of policies to set the DSCP of packets passing into the
aggregation region and how they are mapped onto generic aggregate aggregation region and how they are mapped onto generic aggregate
reservations, thus determining whether they gain access to the reservations, thus determining whether they gain access to the
resources reserved by the aggregate reservation. These policies are a resources reserved by the aggregate reservation. These policies are a
matter of local configuration, as usual for a device at the edge of a matter of local configuration, as usual for a device at the edge of a
Diffserv cloud. Diffserv cloud.
5. Example Usage Of Multiple Generic Aggregate Reservations Per DSCP 5. Example Usage Of Multiple Generic Aggregate Reservations Per PHB
From a Given Aggregator to a Given Deaggregator From a Given Aggregator to a Given Deaggregator
Let us consider the environment depicted in Figure 2 below. RSVP Let us consider the environment depicted in Figure 2 below. RSVP
aggregation is used to support E2E reservations between Cloud-1, aggregation is used to support E2E reservations between Cloud-1,
Cloud-2 and Cloud-3. Cloud-2 and Cloud-3.
I----------I I----------I I----------I I----------I
I Cloud-1 I I Cloud-2 I I Cloud-1 I I Cloud-2 I
I----------I I----------I I----------I I----------I
| | | |
Agg-Deag-1------------ Agg-Deag-2 Agg-Deag-1------------ Agg-Deag-2
/ \ / \
/ Aggregation | / Aggregation |
| Region | | Region |
| | | |
| ---/ | ---/
\ / \ /
Generic Aggregate RSVP Reservations September 2006
\Agg-Deag-3---------/ \Agg-Deag-3---------/
| |
I----------I I----------I
I Cloud-3 I I Cloud-3 I
I----------I I----------I
Figure 2 : Example Usage of Figure 2 : Example Usage of
Generic Aggregate IP Reservations Generic Aggregate IP Reservations
Let us assume that: Let us assume that:
o the E2E reservations from Cloud-1 to Cloud-3 have a preemption o the E2E reservations from Cloud-1 to Cloud-3 have a preemption
of either P1 or P2 of either P1 or P2
o the E2E reservations from Cloud-2 to Cloud-3 have a preemption o the E2E reservations from Cloud-2 to Cloud-3 have a preemption
of either P1 or P2 of either P1 or P2
Generic Aggregate RSVP Reservations January 2007
o the E2E reservations are only for Voice (which needs to be o the E2E reservations are only for Voice (which needs to be
treated in the aggregation region using the EF PHB) treated in the aggregation region using the EF PHB)
o traffic from the E2E reservations is encapsulated in Aggregate o traffic from the E2E reservations is encapsulated in Aggregate
IP reservations from Aggregator to Deaggregator using GRE IP reservations from Aggregator to Deaggregator using GRE
tunneling ([GRE]). tunneling ([GRE]).
Then, the following generic aggregate RSVP reservations may be Then, the following generic aggregate RSVP reservations may be
established from Agg-Deag-1 to Agg-Deag-3 for aggregation of the end- established from Agg-Deag-1 to Agg-Deag-3 for aggregation of the end-
to-end RSVP reservations: to-end RSVP reservations:
A first generic aggregate reservation for aggregation of Voice A first generic aggregate reservation for aggregation of Voice
reservations from Cloud-1 to Cloud-3 requiring use of P1: reservations from Cloud-1 to Cloud-3 requiring use of P1:
* GENERIC-AGGREGATE-IP4 SESSION: * GENERIC-AGGREGATE-IP4 SESSION:
IPv4 DestAddress= Agg-Deag-3 IPv4 DestAddress= Agg-Deag-3
vDstPort=V1 vDstPort=V1
DSCP=EF PHB-ID=EF
Extended VDstPort= Agg-Deag-1 Extended VDstPort= Agg-Deag-1
* STYLE=FF or SE * STYLE=FF or SE
* IPv4/GPI FILTER_SPEC: * IPv4/GPI FILTER_SPEC:
IPv4 SrcAddress= Agg-Deag-1 IPv4 SrcAddress= Agg-Deag-1
* POLICY_DATA (PREEMPTION_PRI)=P1 * POLICY_DATA (PREEMPTION_PRI)=P1
A second generic aggregate reservation for aggregation of Voice A second generic aggregate reservation for aggregation of Voice
reservations from Cloud-1 to Cloud-3 requiring use of P2: reservations from Cloud-1 to Cloud-3 requiring use of P2:
* GENERIC-AGGREGATE-IP4 SESSION: * GENERIC-AGGREGATE-IP4 SESSION:
Generic Aggregate RSVP Reservations September 2006
IPv4 DestAddress= Agg-Deag-3 IPv4 DestAddress= Agg-Deag-3
vDstPort=V2 vDstPort=V2
DSCP=EF PHB-ID=EF
Extended VDstPort= Agg-Deag-1 Extended VDstPort= Agg-Deag-1
* STYLE=FF or SE * STYLE=FF or SE
* IPv4/GPI FILTER_SPEC: * IPv4/GPI FILTER_SPEC:
IPv4 SrcAddress= Agg-Deag-1 IPv4 SrcAddress= Agg-Deag-1
* POLICY_DATA (PREEMPTION_PRI)=P2 * POLICY_DATA (PREEMPTION_PRI)=P2
where V1 and V2 are arbitrary VDstPort values picked by Agg-Deag-3. where V1 and V2 are arbitrary VDstPort values picked by
Agg-Deag-3.
The following generic aggregate RSVP reservations may be established The following generic aggregate RSVP reservations may be established
from Agg-Deag-2 to Agg-Deag-3 for aggregation of the end-to-end RSVP from Agg-Deag-2 to Agg-Deag-3 for aggregation of the end-to-end RSVP
reservations: reservations:
Generic Aggregate RSVP Reservations January 2007
A third generic aggregate reservation for aggregation of Voice A third generic aggregate reservation for aggregation of Voice
reservations from Cloud-2 to Cloud-3 requiring use of P1: reservations from Cloud-2 to Cloud-3 requiring use of P1:
* GENERIC-AGGREGATE-IP4 SESSION: * GENERIC-AGGREGATE-IP4 SESSION:
IPv4 DestAddress= Agg-Deag-3 IPv4 DestAddress= Agg-Deag-3
vDstPort=V3 vDstPort=V3
DSCP=EF PHB-ID=EF
Extended VDstPort= Agg-Deag-2 Extended VDstPort= Agg-Deag-2
* STYLE=FF or SE * STYLE=FF or SE
* IPv4/GPI FILTER_SPEC: * IPv4/GPI FILTER_SPEC:
IPv4 SrcAddress= Agg-Deag-2 IPv4 SrcAddress= Agg-Deag-2
* POLICY_DATA (PREEMPTION_PRI)=P1 * POLICY_DATA (PREEMPTION_PRI)=P1
A fourth generic aggregate reservation for aggregation of Voice A fourth generic aggregate reservation for aggregation of Voice
reservations from Cloud-2 to Cloud-3 requiring use of P2: reservations from Cloud-2 to Cloud-3 requiring use of P2:
* GENERIC-AGGREGATE-IP4 SESSION: * GENERIC-AGGREGATE-IP4 SESSION:
IPv4 DestAddress= Agg-Deag-3 IPv4 DestAddress= Agg-Deag-3
vDstPort=V4 vDstPort=V4
DSCP=EF PHB-ID=EF
Extended VDstPort= Agg-Deag-2 Extended VDstPort= Agg-Deag-2
* STYLE=FF or SE * STYLE=FF or SE
* IPv4/GPI FILTER_SPEC: * IPv4/GPI FILTER_SPEC:
IPv4 SrcAddress= Agg-Deag-2 IPv4 SrcAddress= Agg-Deag-2
* POLICY_DATA (PREEMPTION_PRI)=P2 * POLICY_DATA (PREEMPTION_PRI)=P2
Generic Aggregate RSVP Reservations September 2006 where V3 and V4 are arbitrary VDstPort values picked by Agg-Deag-3.
where V1 and V4 are arbitrary VDstPort values picked by Agg-Deag-3.
Note that V3 and V4 could be equal to (respectively) V1 and V2 since, Note that V3 and V4 could be equal to (respectively) V1 and V2 since,
in this example, the Extended VDstPort of the GENERIC-AGGREGATE in this example, the Extended VDstPort of the GENERIC-AGGREGATE
Session contains the address of the Deaggregator and, thus, ensures Session contains the address of the Deaggregator and, thus, ensures
that different sessions are used for each Deaggregator. that different sessions are used for each Deaggregator.
6. Security Considerations 6. Security Considerations
In the environments concerned by this document, RSVP messages are In the environments addressed by this document, RSVP messages are
used to control resource reservations for generic aggregate used to control resource reservations for generic aggregate
reservations and may be used to control resource reservations for E2E reservations and may be used to control resource reservations for E2E
reservations being aggregated over the generic aggregate reservations. reservations being aggregated over the generic aggregate
To ensure the integrity of the associated reservation and admission reservations. To ensure the integrity of the associated reservation
control mechanisms, the mechanisms defined in [RSVP-CRYPTO1] and and admission control mechanisms, the RSVP Authentication mechanisms
[RSVP-CRYPTO2] can be used. Those protect RSVP messages integrity
hop-by-hop and provide node authentication, thereby protecting Generic Aggregate RSVP Reservations January 2007
defined in [RSVP-CRYPTO1] and [RSVP-CRYPTO2] may be used. These
protect RSVP message integrity hop-by-hop and provide node
authentication as well as replay protection, thereby protecting
against corruption and spoofing of RSVP messages. These hop-by-hop against corruption and spoofing of RSVP messages. These hop-by-hop
integrity mechanisms can naturally be used to protect the RSVP integrity mechanisms can be naturally used to protect the RSVP
messages used for generic aggregate reservations, to protect RSVP messages used for generic aggregate reservations and to protect RSVP
messages used for E2E reservations outside the aggregation region, or messages used for E2E reservations outside the aggregation region.
for both. These hop-by-hop RSVP integrity mechanisms can also be used These hop-by-hop RSVP integrity mechanisms can also be used to
to protect RSVP messages used for E2E reservations when those transit protect RSVP messages used for E2E reservations when those transit
through the aggregation region. This is because the Aggregator and through the aggregation region. This is because the Aggregator and
Deaggregator behave as RSVP neighbors from the viewpoint of the E2E Deaggregator behave as RSVP neighbors from the viewpoint of the E2E
flows (even if they are not necessarily IP neighbors nor RSVP-TE flows (even if they are not necessarily IP neighbors).
neighbors). It that case, the Aggregator and Deaggregator need to use
a pre-shared secret. Where the dynamic Deaggregator determination [RSVP-CRYPTO1] discusses several approaches for key distribution.
procedure defined in [RSVP-AGG] are used, the Aggregator does not First, the RSVP Authentication shared keys can be distributed
know ahead of time which router is going to act as the Deaggregator. manually. This is the base option and its support is mandated for any
Thus, use of the mechanisms of [RSVP-CRYPTO1] and [RSVP-CRYPTO2] for implementation. However, in some environments, this approach may
protection of RSVP E2E messages (e.g. E2E Path) while they transit become a burden if keys frequently change over time. Alternatively, a
through the aggregation region may require the use of a secret pre- standard key management protocol for secure key distribution can be
shared across the Aggregator and all Deaggregators. used. However, existing key distribution protocols may not be
appropriate in all environments because of the complexity or
operational burden they involve. Finally, [RSVP-CRYPTO1] specifies
how Kerberos [KERBEROS] may be used to generate the RSVP
Authentication keys. Kerberos allows for the use of trusted third
party keying relationships between security principals (RSVP sender
and receivers) where the Kerberos key distribution center (KDC)
establishes an ephemeral session key to be shared between RSVP sender
and receivers.
The use of RSVP Authentication in parts of the network where there
may be one or more IP hops in between two RSVP neighbors raises an
additional challenge. This is because, with some RSVP messages such
as a Path message, an RSVP router does not know the RSVP next hop for
that message at the time of forwarding it. In fact, part of the role
of a Path message is precisely to discover the RSVP next hop (and to
dynamically re-discover it when it changes, say because of a routing
change). Hence, the RSVP router may not know which security
association to use when forwarding such a message. This applies in
particular to the case where RSVP Authentication mechanisms are to be
used for protection of RSVP E2E messages (e.g. E2E Path) while they
transit through an aggregation region and where the dynamic
Deaggregator determination procedure defined in [RSVP-AGG] is used.
This is because the Aggregator and the Deaggregator behave as RSVP
neighbors for the E2E reservation, while there may be one or more IP
hops in between them, and the Aggregator does not know ahead of time
which router is going to act as the Deaggregator.
In that situation, one approach is to share the same RSVP
Authentication shared key across all the RSVP routers of a part of
Generic Aggregate RSVP Reservations January 2007
the network where there may be RSVP neighbors with IP hops in
between. For example, all the Aggregators or Deaggregators of an
aggregation region could share the same RSVP Authentication key,
while different per-neighbor keys could be used between any RSVP
router pair straddling the boundary between two administrative
domains that have agreed to use RSVP signaling.
When the same RSVP Authentication shared key is to be shared among
multiple RSVP neighbors, manual key distribution may be used. For
situations where RSVP is being used for multicast flows, it might
also be possible, in the future, to adapt a multicast key management
method (e.g. from IETF Multicast Security Working Group) for key
distribution with such multicast RSVP usage. For situations where
RSVP is being used for unicast flows within a single administrative
domain, the Kerberos technique described in Section 7 of RFC-2747
might be considered. For situations where RSVP is being used for
unicast flows across domain boundaries, it is not currently clear how
one might provide automated key management. Specification of a
specific automated key management technique is outside the scope
of this document. Operators should consider these key
management issues when contemplating deployment of this
specification.
The RSVP Authentication mechanisms do not provide confidentiality. If
confidentiality is required, IPsec ESP [IPSEC-ESP] may be used,
although it imposes the burden of key distribution. It also faces the
additional issue discussed for key management above in case there can
be IP hops in between RSVP hops. In the future, confidentiality
solutions may be developed for the case where there can be IP hops in
between RSVP hops, perhaps by adapting confidentiality solutions
developed by the IETF MSEC Working Group. Such confidentiality
solutions for RSVP are outside the scope of this document.
Protection against traffic analysis is also not provided by RSVP
Authentication. Since generic aggregate reservations are intended to
reserve resources collectively for a whole set of users or hosts,
malicious snooping of the corresponding RSVP messages could provide
more traffic analysis information than snooping of an E2E
reservation. When RSVP neighbors are directly attached, mechanisms
such as bulk link encryption might be used when protection against
traffic analysis is required. This approach could be used inside the
aggregation region for protection of the generic aggregate
reservations. It may also be used outside the aggregation region for
protection of the E2E reservation. However, it is not applicable to
the protection of E2E reservations while the corresponding E2E RSVP
messages transit through the aggregation region.
Generic Aggregate RSVP Reservations January 2007
When generic aggregate reservations are used for aggregation of E2E When generic aggregate reservations are used for aggregation of E2E
reservations, the security considerations discussed in [RSVP-AGG] reservations, the security considerations discussed in [RSVP-AGG]
apply. apply and are revisited here.
The security considerations discussed in [SIG-NESTED] apply when the First, the loss of an aggregate reservation to an aggressor causes
generic aggregate reservations are used in the presence of IPsec E2E flows to operate unreserved, and the reservation of a great
gateways. excess of bandwidth may result in a denial of service. These issues
are not confined to the extensions defined in the present document:
RSVP itself has them. However, they may be exacerbated here by the
fact that each aggregate reservation typically facilitates
communication for many sessions. Hence compromising one such
aggregate reservation can result in more damage than compromising a
typical E2E reservation. Use of the RSVP Authentication mechanisms to
protect against such attacks has been discussed above.
An additional security consideration specific to RSVP aggregation
involves the modification of the IP protocol number in RSVP Path
messages that traverse an aggregation region. Malicious modification
of the IP protocol number in a Path message would cause the message
to be ignored by all subsequent RSVP devices on its path, preventing
reservations from being made. It could even be possible to correct
the value before it reached the receiver, making it difficult to
detect the attack. Note that in theory, it might also be possible for
a node to modify the IP protocol number for non-RSVP messages as
well, thus interfering with the operation of other protocols. It is
RECOMMENDED that implementations of this specification only support
modification of the IP protocol number for RSVP Path, PathTear, and
ResvConf messages. That is, a general facility for modification of
the IP protocol number SHOULD NOT be made available.
Network operators deploying routers with RSVP aggregation capability
should be aware of the risks of inappropriate modification of the IP
protocol number and should take appropriate steps (physical security,
password protection, etc.) to reduce the risk that a router could be
configured by an attacker to perform malicious modification of the
protocol number.
7. IANA Considerations 7. IANA Considerations
Generic Aggregate RSVP Reservations September 2006 This document requests IANA to modify the RSVP parameters registry,
'Class Names, Class Numbers, and Class Types' subregistry, and assign
two new C-Types under the existing SESSION Class (Class number 1), as
suggested below:
This document requests that IANA allocates two new C-Types under the Class
existing SESSION Class (Class 1) for the two new RSVP objects Number Class Name Reference
defined in section 2.1: GENERIC-AGGREGATE-IP4 SESSION and GENERIC- ------ ----------------------- ---------
AGGREGATE-IP6 SESSION. This allocation is in accordance with [RSVP-
MOD] which defines the default assignment policy as Standards Action
for new Class-Type values under an existing class.
This document also requests that IANA allocates one new Class-Num for Generic Aggregate RSVP Reservations January 2007
the SESSION-OF-INTEREST class, and two new C-Types for the two new
RSVP objects under that class defined in section 2.2: GENERIC-AGG- 1 SESSION [RFC2205]
IP4-SOI and GENERIC-AGG-IP6-SOI. The Class-Num for the SESSION-OF-
INTEREST class is to be allocated in the range from 128 to 183 Class Types or C-Types:
defined in [RSVP-MOD] as to be assigned by Standards Action. In
accordance with [RSVP-MOD], the Class-Type values under the SESSION- xx GENERIC-AGGREGATE-IP4 [RFCXXXX]
OF-INTEREST class are to be allocated according to the following yy GENERIC-AGGREGATE-IP6 [RFCXXXX]
policy:
o C-Type values from 0 through 127 are to be assigned by Standards [Note to IANA and the RFC Editor: Please replace RFCXXXX with the RFC
Action number of this specification. Suggested values: xx=17, yy=18]
o C-Type values from 128 through 191 are to be assigned by Expert
Review This document also requests IANA to modify the RSVP parameters
o C-Type values from 192 through 255 are reserved for Vendor registry, 'Class Names, Class Numbers, and Class Types' subregistry,
Private use and assign one new Class Number for the SESSION-OF-INTEREST class and
o C-Type value 1 is to be allocated to the GENERIC-AGG-IP4-SOI two new C-Types for that class, according to the following table
object defined in this document below:
o C-Type value 2 is to be allocated to the GENERIC-AGG-IP6-SOI
object defined in this document. Class
Number Class Name Reference
------ ----------------------- ---------
zzz SESSION-OF-INTEREST [RFCXXXX]
Class Types or C-Types:
aa GENERIC-AGG-IP4-SOI [RFCXXXX]
bb GENERIC-AGG-IP6-SOI [RFCXXXX]
[Note to IANA and the RFC Editor: Please replace RFCXXXX with the RFC
number of this specification. Suggested values: zzz=132 aa=1, bb=2]
These allocations are in accordance with [RSVP-MOD].
8. Acknowledgments 8. Acknowledgments
This document borrows heavily from [RSVP-AGG]. It also borrows the This document borrows heavily from [RSVP-AGG]. It also borrows the
concepts of Virtual Destination Port and Extended Virtual Destination concepts of Virtual Destination Port and Extended Virtual Destination
Port respectively from [RSVP-IPSEC] and [RSVP-TE]. Port respectively from [RSVP-IPSEC] and [RSVP-TE].
Also, we thank Fred Baker, Roger Levesque, Carol Iturralde, Daniel Also, we thank Fred Baker, Roger Levesque, Carol Iturralde, Daniel
Voce, Anil Agarwal, Alexander Sayenko and Anca Zamfir for their input Voce, Anil Agarwal, Alexander Sayenko and Anca Zamfir for their input
into the content of this document. Thanks to Steve Kent for into the content of this document. Thanks to Steve Kent for
insightful comments on usage of RSVP reservations in IPsec insightful comments on usage of RSVP reservations in IPsec
environments. environments.
Generic Aggregate RSVP Reservations January 2007
Ran Atkinson, Fred Baker, Luc Billot, Pascal Delprat and Eric Vyncke
provided guidance and suggestions for the security considerations
section.
9. Normative References 9. Normative References
[IPSEC-ESP] S. Kent, "IP Encapsulating Security Payload (ESP)", RFC
4303, DECEMBER 2005
[KEYWORDS] "Key words for use in RFCs to Indicate Requirement Levels", [KEYWORDS] "Key words for use in RFCs to Indicate Requirement Levels",
Bradner, RFC2119 Bradner, RFC2119, BCP14
[KERBEROS] Neuman et al., "The Kerberos Network Authentication
Service (V5)", RFC 4120, July 2005.
[PHB-ID] "Per Hop Behavior Identification Codes", Black et al.,
[RSVP] "Resource ReSerVation Protocol (RSVP) -- Version 1 Functional [RSVP] "Resource ReSerVation Protocol (RSVP) -- Version 1 Functional
Specification", Braden et al, RFC2205 Specification", Braden et al, RFC2205
Generic Aggregate RSVP Reservations September 2006
[RSVP-AGG] "Aggregation of RSVP for IPv4 and IPv6 Reservations", [RSVP-AGG] "Aggregation of RSVP for IPv4 and IPv6 Reservations",
Baker et al, RFC3175 Baker et al, RFC3175
[RSVP-CRYPTO1] Baker at al, RSVP Cryptographic Authentication, RFC [RSVP-CRYPTO1] Baker at al, RSVP Cryptographic Authentication, RFC
2747, January 2000. 2747, January 2000.
[RSVP-CRYPTO2] Braden and Zhang, RSVP Cryptographic Authentication - [RSVP-CRYPTO2] Braden and Zhang, RSVP Cryptographic Authentication -
Updated Message Type Value, RFC 3097, April 2001. Updated Message Type Value, RFC 3097, April 2001.
[RSVP-IPSEC] "RSVP Extensions for IPsec Data Flows", Berger et al, [RSVP-IPSEC] "RSVP Extensions for IPsec Data Flows", Berger et al,
skipping to change at page 22, line 33 skipping to change at page 26, line 5
Protocol (RSVP)", Kompella and Lang, RFC 3936, BCP 96 Protocol (RSVP)", Kompella and Lang, RFC 3936, BCP 96
10. Informative References 10. Informative References
[BW-REDUC] "A Resource Reservation Extension for the Reduction of [BW-REDUC] "A Resource Reservation Extension for the Reduction of
andwidth of a Reservation Flow", Polk et al, RFC 4495 andwidth of a Reservation Flow", Polk et al, RFC 4495
[GRE] "Generic Routing Encapsulation (GRE) ", Farinacci et al, RFC [GRE] "Generic Routing Encapsulation (GRE) ", Farinacci et al, RFC
2784 2784
Generic Aggregate RSVP Reservations January 2007
[RSVP-PREEMP] Herzog, S., "Signaled Preemption Priority Policy [RSVP-PREEMP] Herzog, S., "Signaled Preemption Priority Policy
Element", RFC 3181, October 2001. Element", RFC 3181, October 2001.
[RSVP-TE] Awduche et al, RSVP-TE: Extensions to RSVP for LSP Tunnels, [RSVP-TE] Awduche et al, RSVP-TE: Extensions to RSVP for LSP Tunnels,
RFC 3209, December 2001. RFC 3209, December 2001.
[RSVP-TUNNEL] "RSVP Operation Over IP Tunnels", Terzis et al., RFC [RSVP-TUNNEL] "RSVP Operation Over IP Tunnels", Terzis et al., RFC
2746, January 2000. 2746, January 2000.
[SIG-NESTED] "QoS Signaling in a Nested Virtual Private Network", [SIG-NESTED] "QoS Signaling in a Nested Virtual Private Network",
Baker et al, draft-ietf-tsvwg-vpn-signaled-preemption, work in Baker et al, draft-ietf-tsvwg-vpn-signaled-preemption, work in
progress progress
11. Authors' Addresses 11. Authors' Addresses
Francois Le Faucheur Francois Le Faucheur
Cisco Systems, Inc. Cisco Systems, Inc.
Village d'Entreprise Green Side - Batiment T3 Village d'Entreprise Green Side - Batiment T3
400, Avenue de Roumanille 400, Avenue de Roumanille
06410 Biot Sophia-Antipolis 06410 Biot Sophia-Antipolis
Generic Aggregate RSVP Reservations September 2006
France France
Email: flefauch@cisco.com Email: flefauch@cisco.com
Bruce Davie Bruce Davie
Cisco Systems, Inc. Cisco Systems, Inc.
300 Beaver Brook Road 300 Beaver Brook Road
Boxborough, MA 01719 Boxborough, MA 01719
USA USA
Email: bdavie@cisco.com Email: bdavie@cisco.com
skipping to change at page 23, line 30 skipping to change at page 27, line 5
USA USA
Email: pratik.bose@lmco.com Email: pratik.bose@lmco.com
Christou Christou Christou Christou
Booz Allen Hamilton Booz Allen Hamilton
8283 Greensboro Drive 8283 Greensboro Drive
McLean, VA 22102 McLean, VA 22102
USA USA
Email: christou_chris@bah.com Email: christou_chris@bah.com
Generic Aggregate RSVP Reservations January 2007
Michael Davenport Michael Davenport
Booz Allen Hamilton Booz Allen Hamilton
8283 Greensboro Drive 8283 Greensboro Drive
McLean, VA 22102 McLean, VA 22102
USA USA
Email: davenport_michael@bah.com Email: davenport_michael@bah.com
IPR Statements Intellectual Property
mailto:
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
Generic Aggregate RSVP Reservations September 2006
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. this standard. Please address the information to the IETF at ietf-
Please address the information to the IETF at ietf-ipr@ietf.org. ipr@ietf.org.
Disclaimer of Validity Full Copyright Statement
Copyright (C) The Internet Society (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Notice Generic Aggregate RSVP Reservations January 2007
Copyright (C) The Internet Society (2006). This document is subject INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
to the rights, licenses and restrictions contained in BCP 78, and WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
except as set forth therein, the authors retain all their rights.
Appendix A: Example Signaling Flow Appendix A: Example Signaling Flow
This Appendix does not provide additional specification. It only This Appendix does not provide additional specification. It only
illustrates the specification detailed in section 4 through a illustrates the specification detailed in section 4 through a
possible flow of RSVP signaling messages. This flow assumes an possible flow of RSVP signaling messages. This flow assumes an
environment where E2E reservations are aggregated over generic environment where E2E reservations are aggregated over generic
aggregate RSVP reservations. It illustrates a possible RSVP message aggregate RSVP reservations. It illustrates a possible RSVP message
flow that could take place in the successful establishment of a flow that could take place in the successful establishment of a
unicast E2E reservation which is the first between a given pair of unicast E2E reservation which is the first between a given pair of
Aggregator/Deaggregator. Aggregator/Deaggregator.
Aggregator Deaggregator Aggregator Deaggregator
E2E Path E2E Path
-----------> ----------->
(1) (1)
E2E Path E2E Path
Generic Aggregate RSVP Reservations September 2006
-------------------------------> ------------------------------->
(2) (2)
E2E PathErr(New-agg-needed,SOI=GAx) E2E PathErr(New-agg-needed,SOI=GAx)
<---------------------------------- <----------------------------------
E2E PathErr(New-agg-needed,SOI=GAy) E2E PathErr(New-agg-needed,SOI=GAy)
<---------------------------------- <----------------------------------
(3) (3)
AggPath(Session=GAx) AggPath(Session=GAx)
-------------------------------> ------------------------------->
AggPath(Session=GAy) AggPath(Session=GAy)
skipping to change at page 25, line 29 skipping to change at page 29, line 4
E2E Path E2E Path
-----------> ----------->
(5) (5)
AggResv (Session=GAx) AggResv (Session=GAx)
<------------------------------- <-------------------------------
AggResv (Session=GAy) AggResv (Session=GAy)
<------------------------------- <-------------------------------
(6) (6)
AggResvConfirm (Session=GAx) AggResvConfirm (Session=GAx)
------------------------------> ------------------------------>
Generic Aggregate RSVP Reservations January 2007
AggResvConfirm (Session=GAy) AggResvConfirm (Session=GAy)
------------------------------> ------------------------------>
(7) (7)
E2E Resv E2E Resv
<--------- <---------
(8) (8)
E2E Resv (SOI=GAx) E2E Resv (SOI=GAx)
<----------------------------- <-----------------------------
(9) (9)
E2E Resv E2E Resv
<----------- <-----------
(1) The Aggregator forwards E2E Path into the aggregation region (1) The Aggregator forwards E2E Path into the aggregation region
after modifying its IP Protocol Number to RSVP-E2E-IGNORE after modifying its IP Protocol Number to RSVP-E2E-IGNORE
(2) Let's assume no Aggregate Path exists. To be able to accurately (2) Let's assume no Aggregate Path exists. To be able to accurately
update the ADSPEC of the E2E Path, the Deaggregator needs the ADSPEC update the ADSPEC of the E2E Path, the Deaggregator needs the ADSPEC
of Aggregate PATH. In this example the Deaggregator elects to of Aggregate PATH. In this example the Deaggregator elects to
instruct the Aggregator to set up Aggregate Path states for the two instruct the Aggregator to set up Aggregate Path states for the two
supported DSCPs. To do that, the Deaggregator sends two E2E PathErr supported PHB-IDs. To do that, the Deaggregator sends two E2E PathErr
messages with a New-Agg-Needed PathErr code. Both PathErr messages messages with a New-Agg-Needed PathErr code. Both PathErr messages
also contain a SESSION-OF-INTEREST (SOI) object. In the first E2E also contain a SESSION-OF-INTEREST (SOI) object. In the first E2E
PathErr, the SOI contains a GENERIC-AGGREGATE SESSION (GAx) whose PathErr, the SOI contains a GENERIC-AGGREGATE SESSION (GAx) whose
DSCP is set to x. In the second E2E PathErr, the SOI contains a PHB-ID is set to x. In the second E2E PathErr, the SOI contains a
GENERIC-AGGREGATE SESSION (GAy) whose DSCP is set to y. In both GENERIC-AGGREGATE SESSION (GAy) whose PHB-ID is set to y. In both
messages the GENERIC-AGGREGATE SESSION contains an interface- messages the GENERIC-AGGREGATE SESSION contains an interface-
Generic Aggregate RSVP Reservations September 2006
independent Deaggregator address inside the DestAddress and independent Deaggregator address inside the DestAddress and
appropriate values inside the vDstPort and Extended vDstPort fields. appropriate values inside the vDstPort and Extended vDstPort fields.
(3) The Aggregator follows the request from the Deaggregator and (3) The Aggregator follows the request from the Deaggregator and
signals an Aggregate Path for both GENERIC-AGGREGATE Sessions (GAx signals an Aggregate Path for both GENERIC-AGGREGATE Sessions (GAx
and GAy). and GAy).
(4) The Deaggregator takes into account the information contained in (4) The Deaggregator takes into account the information contained in
the ADSPEC from both Aggregate Path and updates the E2E Path ADSPEC the ADSPEC from both Aggregate Path and updates the E2E Path ADSPEC
accordingly. The Deaggregator also modifies the E2E Path IP Protocol accordingly. The Deaggregator also modifies the E2E Path IP Protocol
Number to RSVP before forwarding it. Number to RSVP before forwarding it.
(5) In this example, the Deaggregator elects to immediately proceed (5) In this example, the Deaggregator elects to immediately proceed
with establishment of generic aggregate reservations for both DSCPs. with establishment of generic aggregate reservations for both PHB-IDs.
In effect, the Deaggregator can be seen as anticipating the actual In effect, the Deaggregator can be seen as anticipating the actual
demand of E2E reservations so that resources are available on demand of E2E reservations so that resources are available on
the generic aggregate reservations when the E2E Resv requests arrive, the generic aggregate reservations when the E2E Resv requests arrive,
in order to speed up establishment of E2E reservations. Assume in order to speed up establishment of E2E reservations. Assume
also that the Deaggregator includes the optional Resv Confirm also that the Deaggregator includes the optional Resv Confirm
Request in these Aggregate Resv. Request in these Aggregate Resv.
(6) The Aggregator merely complies with the received ResvConfirm (6) The Aggregator merely complies with the received ResvConfirm
Generic Aggregate RSVP Reservations January 2007
Request and returns the corresponding Aggregate ResvConfirm. Request and returns the corresponding Aggregate ResvConfirm.
(7) The Deaggregator has explicit confirmation that both Aggregate (7) The Deaggregator has explicit confirmation that both Aggregate
Resv are established. Resv are established.
(8) On receipt of the E2E Resv, the Deaggregator applies the mapping (8) On receipt of the E2E Resv, the Deaggregator applies the mapping
policy defined by the network administrator to map the E2E Resv policy defined by the network administrator to map the E2E Resv
onto a generic aggregate reservation. Let's assume that this policy onto a generic aggregate reservation. Let's assume that this policy
is such that the E2E reservation is to be mapped onto the generic is such that the E2E reservation is to be mapped onto the generic
aggregate reservation with DSCP=x. The Deaggregator knows that a aggregate reservation with PHB-ID=x. The Deaggregator knows that a
generic aggregate reservation (GAx) is in place for the corresponding generic aggregate reservation (GAx) is in place for the corresponding
DSCP since (7). The Deaggregator performs admission control of the PHB-ID since (7). The Deaggregator performs admission control of the
E2E Resv onto the generic aggregate Reservation for DSCP=x (GAx). E2E Resv onto the generic aggregate Reservation for PHB-ID=x (GAx).
Assuming that the generic aggregate reservation for DSCP=x (GAx) had Assuming that the generic aggregate reservation for PHB-ID=x (GAx)
been established with sufficient bandwidth to support the E2E Resv, had been established with sufficient bandwidth to support the E2E
the Deaggregator adjusts its counter, tracking the unused bandwidth Resv, the Deaggregator adjusts its counter, tracking the unused
on the generic aggregate reservation and forwards the E2E Resv to the bandwidth on the generic aggregate reservation and forwards the E2E
Aggregator including a SESSION-OF-INTEREST object conveying the Resv to the Aggregator including a SESSION-OF-INTEREST object
selected mapping onto GAx (and hence onto DSCP=x). conveying the selected mapping onto GAx (and hence onto PHB-ID=x).
(9) The Aggregator records the mapping of the E2E Resv onto GAx (and (9) The Aggregator records the mapping of the E2E Resv onto GAx (and
onto DSCP=x). The Aggregator removes the SOI object and forwards the onto PHB-ID=x). The Aggregator removes the SOI object and forwards
E2E Resv towards the sender. the E2E Resv towards the sender.
 End of changes. 123 change blocks. 
263 lines changed or deleted 432 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/