draft-ietf-tsvwg-rsvp-ipsec-01.txt   draft-ietf-tsvwg-rsvp-ipsec-02.txt 
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-01.txt draft-ietf-tsvwg-rsvp-ipsec-02.txt
Generic Aggregate RSVP Reservations Generic Aggregate RSVP Reservations
draft-ietf-tsvwg-rsvp-ipsec-01.txt draft-ietf-tsvwg-rsvp-ipsec-02.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 2, line 22 skipping to change at page 2, line 21
established for a given DSCP from a given source IP address to a established for a given DSCP from a given source IP address to a
given destination IP address. The generic aggregate reservations may given destination IP address. The generic aggregate reservations may
be used to aggregate end-to-end RSVP reservations. This document also be used to aggregate end-to-end RSVP reservations. This document also
defines the procedures for such aggregation. The generic aggregate defines the procedures for such aggregation. The generic aggregate
reservations may also be used end-to-end directly by end-systems reservations may also be used end-to-end directly by end-systems
attached to a Diffserv network. attached to a Diffserv network.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Table Of Content
1. Introduction...................................................3
1.1. Related RFCs and Internet-Drafts..........................5
1.2. Organization Of This Document.............................6
2. Object Definition..............................................6
2.1. SESSION Class.............................................7
2.2. SESSION-OF-INTEREST (SOI) Class..........................10
3. Processing Rules For Handling Generic Aggregate RSVP Reservations
.................................................................11
3.1. Required Changes to Path and Resv Processing.............12
4. Procedures for Aggregation over Generic Aggregate RSVP
Reservations.....................................................13
5. Example Usage Of Multiple Generic Aggregate Reservations Per DSCP
From a Given Aggregator to a Given Deaggregator..................17
6. Security Considerations.......................................19
7. IANA Considerations...........................................20
8. Acknowledgments...............................................20
9. Normative References..........................................20
10. Informative References.......................................21
11. Authors' Addresses...........................................21
Appendix A: Example Signaling Flow...............................23
Specification of Requirements Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
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-
skipping to change at page 6, line 14 skipping to change at page 6, line 36
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 in Section 6 and 7, respectively. discussed in Section 6 and 7, respectively.
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.
1.3. Change History
1.3.1.
Changes From draft-ietf-tsvwg-rsvp-ipsec-00 To draft-ietf-tsvwg-
rsvp-ipsec-01
The most significant changes are:
o added text on pre-established aggregate reservations
o added text on tear-down of aggregate reservations
o modified text describing content of the Extended vDstPort
field
o renamed AGGREGATION-SESSION class into SESSION-OF-INTEREST
class
o added text clarifying which of the new objects may appear in
which message types
o added text to avoid confusion between the Session of a given
reservation and the Session which may be included in the
SESSION-OF-INTEREST object.
o included informative appendix showing an RSVP signalling flow
mirroring the one in RFC3175
1.3.2.
Changes From draft-lefaucheur-rsvp-ipsec-02 To draft-ietf-tsvwg-
rsvp-ipsec-00
The most significant changes are:
o de-correlate the generic aggregate reservations from IPsec
operations, in line with comments from the Security experts
review. This significantly affects (and simplifies
considerably) the document in many places.
o add the notion of Extended Virtual Destination port (reusing
the notion of Extended Tunnel ID of [RSVP-TE]).
o added recommendations on use of IP addresses by Aggregator and
Deaggregator
1.3.3.
Changes From draft-lefaucheur-rsvp-ipsec-01 To draft-lefaucheur-
rsvp-ipsec-02
The most significant changes are:
o added text in section 4.2 about Aggregator/Deaggregator
responsibilities with respect to mapping of end-to-end
reservations onto aggregate reservations. The text also
clarified that DCLASS object is no longer needed in PathErr
message requesting new Aggregate Reservations
o Moved the text discussing details of the procedures to handle
dynamic update of SPI values from Security Considerations
section into a new section 4.4.
o updates to Security Considerations section to start addressing
some comments from Security experts review.
1.3.4.
Changes From draft-lefaucheur-rsvp-ipsec-00 To draft-lefaucheur-
rsvp-ipsec-01
The most significant change is the broadening of the applicability of
the new type of aggregate reservations beyond use for Aggregate
reservations for IPsec tunnels (to environments where IPsec is not
used). This affects the document in multiple places including the
following changes:
o document renamed to "Generic Aggregate RSVP Reservations"
o added a subsection in Introduction to discuss a case where
Generic Aggregate RSVP Reservations are needed in non IPsec
environments
o added text about the fact that the Generic Aggregate
Reservations can be used with IP-in-IP and GRE encapsulation
(in addition to with IPsec AH and ESP)
o added example usage under Section 5 for environment where
IPsec is not used
The other significant changes are:
o added a subsection on the changes of the [RSVP-AGG] procedures
under Section 4
o added explanation about allocation of VDstPort values by
Deaggregator, in that same subsection
o added value of Protocol ID in all example generic aggregate
reservations in Section 5
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 23, line 42 skipping to change at page 22, line 21
USA USA
Email: christou_chris@bah.com Email: christou_chris@bah.com
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
12. IPR Statements IPR Statements
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.
skipping to change at page 24, line 22 skipping to change at page 22, line 45
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-ipr@ietf.org. Please address the information to the IETF at ietf-ipr@ietf.org.
13. Disclaimer of Validity Disclaimer of Validity
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 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.
14. Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). This document is subject Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
APPENDIX 1: 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.
 End of changes. 8 change blocks. 
103 lines changed or deleted 29 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/