draft-ietf-tsvwg-rsvp-ipsec-04.txt   draft-ietf-tsvwg-rsvp-ipsec-05.txt 
Generic Aggregate RSVP Reservations January 2007 Generic Aggregate RSVP Reservations February 2007
Internet Draft Francois Le Faucheur Internet Draft Francois Le Faucheur
Bruce Davie Intended status: Proposed Standards 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-04.txt draft-ietf-tsvwg-rsvp-ipsec-05.txt
Expires: July 2007 January 2007 Expires: August 13, 2007 February 13, 2007
Generic Aggregate Resource ReSerVation Protocol (RSVP) Reservations Generic Aggregate Resource ReSerVation Protocol (RSVP) Reservations
draft-ietf-tsvwg-rsvp-ipsec-04.txt draft-ietf-tsvwg-rsvp-ipsec-05.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 Resource ReSerVation Protocol (RSVP) RFC3175 defines aggregate Resource ReSerVation Protocol (RSVP)
reservations allowing resources to be reserved in a Diffserv network reservations allowing resources to be reserved in a Diffserv network
for a given Per Hop Behavior (PHB), or given set of PHBs, from a for a given Per Hop Behavior (PHB), or given set of PHBs, from a
given source to a given destination. [RSVP-AGG] also defines how end- given source to a given destination. RFC3175 also defines how end-to-
Generic Aggregate RSVP Reservations January 2007 Generic Aggregate RSVP Reservations February 2007
to-end RSVP reservations can be aggregated onto such aggregate end RSVP reservations can be aggregated onto such aggregate
reservations when transiting through a Diffserv cloud. There are reservations when transiting through a Diffserv cloud. There are
situations where multiple such aggregate reservations are needed for situations where multiple such aggregate reservations are needed for
the same source IP address, destination IP address and PHB (or set of the same source IP address, destination IP address and PHB (or set of
PHBs). However, this is not supported by the aggregate reservations PHBs). However, this is not supported by the aggregate reservations
defined in [RSVP-AGG]. In order to support this, the present document defined in RFC3175. In order to support this, the present document
defines a more flexible type of aggregate RSVP reservations, referred defines a more flexible type of aggregate RSVP reservations, referred
to as generic aggregate reservation. Multiple such generic aggregate to as generic aggregate reservation. Multiple such generic aggregate
reservations can be established for a given PHB (or set of PHBs) from reservations can be established for a given PHB (or set of PHBs) from
a given source IP address to a given destination IP address. The a given source IP address to a given destination IP address. The
generic aggregate reservations may be used to aggregate end-to-end generic aggregate reservations may be used to aggregate end-to-end
RSVP reservations. This document also defines the procedures for such RSVP reservations. This document also defines the procedures for such
aggregation. The generic aggregate reservations may also be used end- aggregation. The generic aggregate reservations may also be used end-
to-end directly by end-systems attached to a Diffserv network. to-end directly by end-systems attached to a Diffserv network.
Copyright Notice
Copyright (C) The Internet Society (2007).
Table Of Content Table Of Content
1. Introduction...................................................3 1. Introduction...................................................3
1.1. Related IETF Documents....................................6 1.1. Related IETF Documents....................................6
1.2. Organization Of This Document.............................6 1.2. Organization Of This Document.............................6
2. Object Definition..............................................7 2. Object Definition..............................................7
2.1. SESSION Class.............................................8 2.1. SESSION Class.............................................7
2.2. SESSION-OF-INTEREST (SOI) Class..........................11 2.2. SESSION-OF-INTEREST (SOI) Class..........................10
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.............13 3.1. Extensions to Path and Resv Processing...................13
4. Procedures for Aggregation over Generic Aggregate RSVP 4. Procedures for Aggregation over Generic Aggregate RSVP
Reservations.....................................................14 Reservations.....................................................14
5. Example Usage Of Multiple Generic Aggregate Reservations Per PHB 5. Example Usage Of Multiple Generic Aggregate Reservations Per PHB
From a Given Aggregator to a Given Deaggregator..................18 From a Given Aggregator to a Given Deaggregator..................18
6. Security Considerations.......................................20 6. Security Considerations.......................................20
7. IANA Considerations...........................................23 7. IANA Considerations...........................................23
8. Acknowledgments...............................................24 8. Acknowledgments...............................................24
9. Normative References..........................................25 9. Normative References..........................................24
10. Informative References.......................................25 10. Informative References.......................................25
11. Authors' Addresses...........................................26 11. Authors' Addresses...........................................25
Appendix A: Example Signaling Flow...............................28 Appendix A: Example Signaling Flow...............................27
Terminology
In this document, the key words "MUST", "MUST NOT", "REQUIRED", Requirements Language
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
Generic Aggregate RSVP Reservations January 2007 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119.
"OPTIONAL" in this document are to be interpreted as described in Generic Aggregate RSVP Reservations February 2007
[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 4, line 4 skipping to change at page 3, line 47
--> = 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 Per Hop Behavior (PHB) from which Diffserv resources are DSCP of the Per Hop Behavior (PHB) from which Diffserv resources are
Generic Aggregate RSVP Reservations January 2007
to be reserved. For example, in the case of IPv4, the SESSION object to be reserved. For example, in the case of IPv4, the SESSION object
is specified as: is specified as:
o Class = SESSION, o Class = SESSION,
C-Type = RSVP-AGGREGATE-IP4 C-Type = RSVP-AGGREGATE-IP4
Generic Aggregate RSVP Reservations February 2007
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| 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:
skipping to change at page 4, line 50 skipping to change at page 4, line 44
IP address and PHB (or set of PHBs). One example is where E2E IP address and PHB (or set of PHBs). One example is where E2E
reservations using different preemption priorities (as per [RSVP- reservations using different preemption priorities (as per [RSVP-
PREEMP]) need to be aggregated through a Diffserv cloud using the PREEMP]) need to be aggregated through a Diffserv cloud using the
same PHB. Using multiple aggregate reservations for the same PHB same PHB. Using multiple aggregate reservations for the same PHB
allows enforcement of the different preemption priorities within the allows enforcement of the different preemption priorities within the
aggregation region. In turn this allows more efficient management of aggregation region. In turn this allows more efficient management of
the Diffserv resources and in period of resource shortage allows to the Diffserv resources and in period of resource shortage allows to
sustain a larger number of E2E reservations with higher preemption sustain a larger number of E2E reservations with higher preemption
priorities. priorities.
For example, [SIG-NESTED] discusses in details how end-to-end RSVP For example, [SIG-NESTED] discusses in detail 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 PHB), each with parallel generic aggregate reservations (for the same PHB), each with
Generic Aggregate RSVP Reservations January 2007
different preemption priorities, can be used to efficiently support different preemption priorities, can be used to efficiently support
the preemption priorities of end-to-end reservations. the preemption priorities of end-to-end reservations.
This document addresses this requirement for multiple aggregate This document addresses this requirement for multiple aggregate
reservations for the same PHB (or same set of PHBs), by defining a reservations for the same PHB (or same set of PHBs), by defining a
Generic Aggregate RSVP Reservations February 2007
more flexible type of aggregate RSVP reservations, referred to as more flexible type of aggregate RSVP reservations, referred to as
generic aggregate reservations. This is achieved primarily by adding generic aggregate reservations. This is achieved primarily by adding
the notions of a Virtual Destination Port and of an Extended Virtual the notions of a Virtual Destination Port and of an Extended Virtual
Destination Port in the RSVP Session object. 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
skipping to change at page 6, line 4 skipping to change at page 5, line 50
indication of whether the Diffserv resources belong to a single PHB indication of whether the Diffserv resources belong to a single PHB
or to a set of PHBs. It also facilitates handling of situations where or to a set of PHBs. It also facilitates handling of situations where
a generic aggregate reservation spans two (or more) Diffserv domains a generic aggregate reservation spans two (or more) Diffserv domains
which use different DSCP values for the same Diffserv PHB (or set of 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 PHBs) from which resources are reserved. This is because the PHB-ID
allows conveying of the PHB (or set of PHBs) independently of what 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). 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.
Generic Aggregate RSVP Reservations February 2007
1.1. Related IETF Documents 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.
skipping to change at page 7, line 5 skipping to change at page 6, line 50
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 discussed The Security Considerations and the IANA Considerations are 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.
Generic Aggregate RSVP Reservations February 2007
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)
skipping to change at page 8, line 5 skipping to change at page 7, line 51
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)
Generic Aggregate RSVP Reservations February 2007
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 | PHB-ID | | Reserved | Flags | PHB-ID |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| Reserved | vDstPort | | Reserved | vDstPort |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
skipping to change at page 9, line 5 skipping to change at page 8, line 48
A 16-bit field containing the Per Hop Behavior Identification A 16-bit field containing the Per Hop Behavior Identification
Code of the PHB, or of the set of PHBs, from which Diffserv Code of the PHB, or of the set of PHBs, from which Diffserv
resources are to be reserved. This field MUST be encoded as resources are to be reserved. This field MUST be encoded as
specified in section 2 of [PHB-ID]. specified in section 2 of [PHB-ID].
Reserved Reserved
A 16-bit field. All bits MUST be set to 0 on transmit. This A 16-bit field. All bits MUST be set to 0 on transmit. This
field MUST be ignored on receipt. field MUST be ignored on receipt.
Generic Aggregate RSVP Reservations January 2007
VDstPort (Virtual Destination Port) VDstPort (Virtual Destination Port)
Generic Aggregate RSVP Reservations February 2007
A 16-bit identifier used in the SESSION that remains constant A 16-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.
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
skipping to change at page 10, line 5 skipping to change at page 9, line 50
| | | |
+ + + +
| 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)
Generic Aggregate RSVP Reservations February 2007
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])
skipping to change at page 11, line 5 skipping to change at page 10, line 47
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
Generic Aggregate RSVP Reservations February 2007
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 12, line 5 skipping to change at page 11, line 50
| | | |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
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
Generic Aggregate RSVP Reservations February 2007
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) |
+-------------+-------------+-------------+--+----------+ +-------------+-------------+-------------+--+----------+
skipping to change at page 12, line 40 skipping to change at page 12, line 37
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 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 extensions to the processing of RSVP messages
[RSVP-PROCESS]. These additions are required in order to properly required by [RSVP] and presented in [RSVP-PROCESS]. These extensions
process the GENERIC-AGGREGATE-IP4 (resp. GENERIC-AGGREGATE-IP6) are required in order to properly process the GENERIC-AGGREGATE-IP4
SESSION object and the RSVP-AGGREGATE-IP4 (resp. RSVP-AGGREGATE-IP6) (resp. GENERIC-AGGREGATE-IP6) SESSION object and the RSVP-AGGREGATE-
FILTER_SPEC object. Values for referenced error codes can be found in IP4 (resp. RSVP-AGGREGATE-IP6) FILTER_SPEC object. Values for
[RSVP]. As with the other RSVP documents, values for internally referenced error codes can be found in [RSVP]. As with the other RSVP
reported (API) errors are not defined. documents, values for internally 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
Generic Aggregate RSVP Reservations February 2007
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. Extensions to Path and Resv Processing
Both RESV and PATH processing need to be changed to support the new
objects.
The following PATH message processing changes are required: The following PATH message processing changes are defined:
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 PHB-ID 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 PHB-ID 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
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 following changes to RESV message processing are defined:
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 uses data classifier as type is GENERIC-AGGREGATE, each node uses data classifier as
per the following: per the following:
* to perform Diffserv classification the node MUST rely on the * to perform Diffserv classification the node MUST rely on the
Diffserv data classifier based on the DSCP only. The Diffserv data classifier based on the DSCP only. The
relevant DSCP value(s) is the one (are those) associated relevant DSCP value(s) is the one (are those) associated
with the PHB-ID of the generic aggregate reservation. 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 * If the node also needs to perform fine-grain classification
(for example to perform fine-grain input policing at a trust (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>.
Generic Aggregate RSVP Reservations February 2007
The relevant DSCP value(s) is the one (are those) associated The relevant DSCP value(s) is the one (are those) associated
with the PHB-ID of the generic aggregate reservation. with the PHB-ID of the generic aggregate reservation.
Note that if multiple generic aggregate reservations are Note that if multiple generic aggregate reservations are
established with different Virtual Destination Ports (and/or established with different Virtual Destination Ports (and/or
different Extended Virtual Destination Ports) but with the different Extended Virtual Destination Ports) but with the
same <DestAddress, SrcAddress, PHB-ID>, 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
skipping to change at page 15, line 4 skipping to change at page 14, line 51
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
Generic Aggregate RSVP Reservations February 2007
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.
The Deaggregator MAY also include in the E2E PathErr message (with an The Deaggregator MAY also include in the E2E PathErr message (with an
error code of NEW-AGGREGATE-NEEDED) additional RSVP objects which are error code of NEW-AGGREGATE-NEEDED) additional RSVP objects which are
to be used for establishment of the new needed generic aggregate to be used for establishment of the new needed generic aggregate
skipping to change at page 16, line 4 skipping to change at page 15, line 52
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, a Deaggregator behaving according to the present state. However, a Deaggregator behaving according to the present
specification MUST use the generic aggregate reservations and hence specification MUST use the generic aggregate reservations and hence
use the GENERIC-AGGREGATE 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 PHB-ID, 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
Generic Aggregate RSVP Reservations February 2007
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.
On receipt of the aggregate ResvTear, the Aggregator SHOULD send an On receipt of the aggregate ResvTear, the Aggregator SHOULD send an
skipping to change at page 17, line 5 skipping to change at page 16, line 52
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
Generic Aggregate RSVP Reservations February 2007
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
reservations, interior routers (i.e. routers within the aggregation reservations, interior routers (i.e. routers within the aggregation
region) SHOULD continue using interface-dependent addresses as per region) SHOULD continue using interface-dependent addresses as per
regular [RSVP] procedures. regular [RSVP] procedures.
skipping to change at page 18, line 4 skipping to change at page 17, line 51
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, PHB-ID 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
Generic Aggregate RSVP Reservations January 2007
to be reserved by the Deaggregator (for a given Deaggregator/PHB- to be reserved by the Deaggregator (for a given Deaggregator/PHB-
ID/VDstPort tuple). 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
Generic Aggregate RSVP Reservations February 2007
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 PHB 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
skipping to change at page 19, line 5 skipping to change at page 18, line 48
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)
Generic Aggregate RSVP Reservations February 2007
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:
skipping to change at page 20, line 5 skipping to change at page 19, line 54
* POLICY_DATA (PREEMPTION_PRI)=P2 * POLICY_DATA (PREEMPTION_PRI)=P2
where V1 and V2 are arbitrary VDstPort values picked by where V1 and V2 are arbitrary VDstPort values picked by
Agg-Deag-3. 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 RSVP Reservations February 2007
* GENERIC-AGGREGATE-IP4 SESSION: * GENERIC-AGGREGATE-IP4 SESSION:
IPv4 DestAddress= Agg-Deag-3 IPv4 DestAddress= Agg-Deag-3
vDstPort=V3 vDstPort=V3
PHB-ID=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
skipping to change at page 21, line 4 skipping to change at page 20, line 51
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 addressed 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 being aggregated over the generic aggregate
reservations. To ensure the integrity of the associated reservation reservations. To ensure the integrity of the associated reservation
and admission control mechanisms, the RSVP Authentication mechanisms and admission control mechanisms, the RSVP Authentication mechanisms
Generic Aggregate RSVP Reservations January 2007
defined in [RSVP-CRYPTO1] and [RSVP-CRYPTO2] may be used. These defined in [RSVP-CRYPTO1] and [RSVP-CRYPTO2] may be used. These
protect RSVP message integrity hop-by-hop and provide node protect RSVP message integrity hop-by-hop and provide node
authentication as well as replay protection, thereby protecting authentication as well as replay protection, thereby protecting
Generic Aggregate RSVP Reservations February 2007
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 be naturally used to protect the RSVP integrity mechanisms can be naturally used to protect the RSVP
messages used for generic aggregate reservations and to protect RSVP messages used for generic aggregate reservations and to protect RSVP
messages used for E2E reservations outside the aggregation region. messages used for E2E reservations outside the aggregation region.
These hop-by-hop RSVP integrity mechanisms can also be used to These hop-by-hop RSVP integrity mechanisms can also be used 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). flows (even if they are not necessarily IP neighbors).
[RSVP-CRYPTO1] discusses several approaches for key distribution. [RSVP-CRYPTO1] discusses several approaches for key distribution.
First, the RSVP Authentication shared keys can be distributed First, the RSVP Authentication shared keys can be distributed
manually. This is the base option and its support is mandated for any manually. This is the base option and its support is mandated for any
implementation. However, in some environments, this approach may implementation. However, in some environments, this approach may
become a burden if keys frequently change over time. Alternatively, a become a burden if keys frequently change over time. Alternatively, a
standard key management protocol for secure key distribution can be standard key management protocol for secure key distribution can be
used. However, existing key distribution protocols may not be used. However, existing key distribution protocols may not be
appropriate in all environments because of the complexity or appropriate in all environments because of the complexity or
operational burden they involve. Finally, [RSVP-CRYPTO1] specifies operational burden they involve.
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 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 may be one or more IP hops in between two RSVP neighbors raises an
additional challenge. This is because, with some RSVP messages such 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 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 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 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 dynamically re-discover it when it changes, say because of a routing
change). Hence, the RSVP router may not know which security change). Hence, the RSVP router may not know which security
association to use when forwarding such a message. This applies in association to use when forwarding such a message. This applies in
skipping to change at page 22, line 4 skipping to change at page 21, line 47
used for protection of RSVP E2E messages (e.g. E2E Path) while they used for protection of RSVP E2E messages (e.g. E2E Path) while they
transit through an aggregation region and where the dynamic transit through an aggregation region and where the dynamic
Deaggregator determination procedure defined in [RSVP-AGG] is used. Deaggregator determination procedure defined in [RSVP-AGG] is used.
This is because the Aggregator and the Deaggregator behave as RSVP This is because the Aggregator and the Deaggregator behave as RSVP
neighbors for the E2E reservation, while there may be one or more IP 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 hops in between them, and the Aggregator does not know ahead of time
which router is going to act as the Deaggregator. which router is going to act as the Deaggregator.
In that situation, one approach is to share the same RSVP In that situation, one approach is to share the same RSVP
Authentication shared key across all the RSVP routers of a part of 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 the network where there may be RSVP neighbors with IP hops in
between. For example, all the Aggregators or Deaggregators of an between. For example, all the Aggregators or Deaggregators of an
aggregation region could share the same RSVP Authentication key, aggregation region could share the same RSVP Authentication key,
while different per-neighbor keys could be used between any RSVP while different per-neighbor keys could be used between any RSVP
router pair straddling the boundary between two administrative router pair straddling the boundary between two administrative
domains that have agreed to use RSVP signaling. domains that have agreed to use RSVP signaling.
When the same RSVP Authentication shared key is to be shared among When the same RSVP Authentication shared key is to be shared among
multiple RSVP neighbors, manual key distribution may be used. For multiple RSVP neighbors, manual key distribution may be used. For
Generic Aggregate RSVP Reservations February 2007
situations where RSVP is being used for multicast flows, it might situations where RSVP is being used for multicast flows, it might
also be possible, in the future, to adapt a multicast key management also be possible, in the future, to adapt a multicast key management
method (e.g. from IETF Multicast Security Working Group) for key method (e.g. from IETF Multicast Security Working Group) for key
distribution with such multicast RSVP usage. For situations where distribution with such multicast RSVP usage. For situations where
RSVP is being used for unicast flows within a single administrative RSVP is being used for unicast flows across domain boundaries, it is
domain, the Kerberos technique described in Section 7 of RFC-2747 not currently clear how one might provide automated key
might be considered. For situations where RSVP is being used for management. Specification of a specific automated key management
unicast flows across domain boundaries, it is not currently clear how technique is outside the scope of this document. Operators should
one might provide automated key management. Specification of a consider these key management issues when contemplating deployment of
specific automated key management technique is outside the scope this specification.
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 The RSVP Authentication mechanisms do not provide confidentiality. If
confidentiality is required, IPsec ESP [IPSEC-ESP] may be used, confidentiality is required, IPsec ESP [IPSEC-ESP] may be used,
although it imposes the burden of key distribution. It also faces the although it imposes the burden of key distribution. It also faces the
additional issue discussed for key management above in case there can additional issue discussed for key management above in case there can
be IP hops in between RSVP hops. In the future, confidentiality 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 solutions may be developed for the case where there can be IP hops in
between RSVP hops, perhaps by adapting confidentiality solutions between RSVP hops, perhaps by adapting confidentiality solutions
developed by the IETF MSEC Working Group. Such confidentiality developed by the IETF MSEC Working Group. Such confidentiality
solutions for RSVP are outside the scope of this document. solutions for RSVP are outside the scope of this document.
skipping to change at page 23, line 5 skipping to change at page 22, line 42
more traffic analysis information than snooping of an E2E more traffic analysis information than snooping of an E2E
reservation. When RSVP neighbors are directly attached, mechanisms reservation. When RSVP neighbors are directly attached, mechanisms
such as bulk link encryption might be used when protection against such as bulk link encryption might be used when protection against
traffic analysis is required. This approach could be used inside the traffic analysis is required. This approach could be used inside the
aggregation region for protection of the generic aggregate aggregation region for protection of the generic aggregate
reservations. It may also be used outside the aggregation region for reservations. It may also be used outside the aggregation region for
protection of the E2E reservation. However, it is not applicable to protection of the E2E reservation. However, it is not applicable to
the protection of E2E reservations while the corresponding E2E RSVP the protection of E2E reservations while the corresponding E2E RSVP
messages transit through the aggregation region. 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 and are revisited here. apply and are revisited here.
First, the loss of an aggregate reservation to an aggressor causes First, the loss of an aggregate reservation to an aggressor causes
E2E flows to operate unreserved, and the reservation of a great E2E flows to operate unreserved, and the reservation of a great
excess of bandwidth may result in a denial of service. These issues excess of bandwidth may result in a denial of service. These issues
are not confined to the extensions defined in the present document: are not confined to the extensions defined in the present document:
RSVP itself has them. However, they may be exacerbated here by the RSVP itself has them. However, they may be exacerbated here by the
fact that each aggregate reservation typically facilitates fact that each aggregate reservation typically facilitates
communication for many sessions. Hence compromising one such communication for many sessions. Hence compromising one such
aggregate reservation can result in more damage than compromising a aggregate reservation can result in more damage than compromising a
typical E2E reservation. Use of the RSVP Authentication mechanisms to typical E2E reservation. Use of the RSVP Authentication mechanisms to
protect against such attacks has been discussed above. protect against such attacks has been discussed above.
Generic Aggregate RSVP Reservations February 2007
An additional security consideration specific to RSVP aggregation An additional security consideration specific to RSVP aggregation
involves the modification of the IP protocol number in RSVP Path involves the modification of the IP protocol number in RSVP Path
messages that traverse an aggregation region. Malicious modification messages that traverse an aggregation region. Malicious modification
of the IP protocol number in a Path message would cause the message 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 to be ignored by all subsequent RSVP devices on its path, preventing
reservations from being made. It could even be possible to correct reservations from being made. It could even be possible to correct
the value before it reached the receiver, making it difficult to the value before it reached the receiver, making it difficult to
detect the attack. Note that in theory, it might also be possible for 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 a node to modify the IP protocol number for non-RSVP messages as
well, thus interfering with the operation of other protocols. It is well, thus interfering with the operation of other protocols. It is
skipping to change at page 24, line 5 skipping to change at page 23, line 40
This document requests IANA to modify the RSVP parameters registry, This document requests IANA to modify the RSVP parameters registry,
'Class Names, Class Numbers, and Class Types' subregistry, and assign 'Class Names, Class Numbers, and Class Types' subregistry, and assign
two new C-Types under the existing SESSION Class (Class number 1), as two new C-Types under the existing SESSION Class (Class number 1), as
suggested below: suggested below:
Class Class
Number Class Name Reference Number Class Name Reference
------ ----------------------- --------- ------ ----------------------- ---------
Generic Aggregate RSVP Reservations January 2007
1 SESSION [RFC2205] 1 SESSION [RFC2205]
Class Types or C-Types: Class Types or C-Types:
xx GENERIC-AGGREGATE-IP4 [RFCXXXX] xx GENERIC-AGGREGATE-IP4 [RFCXXXX]
yy GENERIC-AGGREGATE-IP6 [RFCXXXX] yy GENERIC-AGGREGATE-IP6 [RFCXXXX]
[Note to IANA and the RFC Editor: Please replace RFCXXXX with the RFC [Note to IANA and the RFC Editor: Please replace RFCXXXX with the RFC
number of this specification. Suggested values: xx=17, yy=18] number of this specification. Suggested values: xx=17, yy=18]
This document also requests IANA to modify the RSVP parameters This document also requests IANA to modify the RSVP parameters
registry, 'Class Names, Class Numbers, and Class Types' subregistry, registry, 'Class Names, Class Numbers, and Class Types' subregistry,
Generic Aggregate RSVP Reservations February 2007
and assign one new Class Number for the SESSION-OF-INTEREST class and and assign one new Class Number for the SESSION-OF-INTEREST class and
two new C-Types for that class, according to the following table two new C-Types for that class, according to the following table
below: below:
Class Class
Number Class Name Reference Number Class Name Reference
------ ----------------------- --------- ------ ----------------------- ---------
zzz SESSION-OF-INTEREST [RFCXXXX] zzz SESSION-OF-INTEREST [RFCXXXX]
skipping to change at page 25, line 5 skipping to change at page 24, line 39
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 Ran Atkinson, Fred Baker, Luc Billot, Pascal Delprat and Eric Vyncke
provided guidance and suggestions for the security considerations provided guidance and suggestions for the security considerations
section. section.
9. Normative References 9. Normative References
[IPSEC-ESP] S. Kent, "IP Encapsulating Security Payload (ESP)", RFC [IPSEC-ESP] S. Kent, "IP Encapsulating Security Payload (ESP)", RFC
4303, DECEMBER 2005 4303, December 2005.
[KEYWORDS] "Key words for use in RFCs to Indicate Requirement Levels",
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., [PHB-ID] "Per Hop Behavior Identification Codes", Black et al.,
RFC3140, June 2001.
[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 February 2007
[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,
RFC2207 RFC2207.
[RSVP-PROCESS] "Resource ReSerVation Protocol (RSVP) -- Version 1
Message Processing Rules", Braden et al, RFC2209
[RSVP-MOD] "Procedures for Modifying the Resource reSerVation [RSVP-MOD] "Procedures for Modifying the Resource reSerVation
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 Bandwidth 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-PROCESS] "Resource ReSerVation Protocol (RSVP) -- Version 1
Message Processing Rules", Braden et al, RFC2209.
[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 February 2007
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 27, line 5 skipping to change at page 26, line 30
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
Intellectual Property 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 February 2007
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. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2007). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
D
i
c
s
l
a
m
i
r
e
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, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
Generic Aggregate RSVP Reservations January 2007
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
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.
Generic Aggregate RSVP Reservations February 2007
Aggregator Deaggregator Aggregator Deaggregator
E2E Path E2E Path
-----------> ----------->
(1) (1)
E2E Path E2E Path
-------------------------------> ------------------------------->
(2) (2)
E2E PathErr(New-agg-needed,SOI=GAx) E2E PathErr(New-agg-needed,SOI=GAx)
<---------------------------------- <----------------------------------
skipping to change at page 29, line 4 skipping to change at page 28, line 35
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 PHB-IDs. To do that, the Deaggregator sends two E2E PathErr supported PHB-IDs. To do that, the Deaggregator sends two E2E PathErr
Generic Aggregate RSVP Reservations February 2007
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
PHB-ID 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 PHB-ID 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-
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
skipping to change at page 30, line 4 skipping to change at page 29, line 35
(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 PHB-IDs. 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 PHB-ID=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
PHB-ID 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 PHB-ID=x (GAx). E2E Resv onto the generic aggregate Reservation for PHB-ID=x (GAx).
Assuming that the generic aggregate reservation for PHB-ID=x (GAx) Assuming that the generic aggregate reservation for PHB-ID=x (GAx)
had been established with sufficient bandwidth to support the E2E had been established with sufficient bandwidth to support the E2E
Resv, the Deaggregator adjusts its counter, tracking the unused Resv, the Deaggregator adjusts its counter, tracking the unused
bandwidth on the generic aggregate reservation and forwards the E2E bandwidth on the generic aggregate reservation and forwards the E2E
Resv to the Aggregator including a SESSION-OF-INTEREST object Resv to the Aggregator including a SESSION-OF-INTEREST object
conveying the selected mapping onto GAx (and hence onto PHB-ID=x). conveying the selected mapping onto GAx (and hence onto PHB-ID=x).
Generic Aggregate RSVP Reservations February 2007
(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 PHB-ID=x). The Aggregator removes the SOI object and forwards onto PHB-ID=x). The Aggregator removes the SOI object and forwards
the E2E Resv towards the sender. the E2E Resv towards the sender.
Expires: August 13, 2007
 End of changes. 90 change blocks. 
147 lines changed or deleted 138 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/