draft-ietf-tsvwg-rsvp-bw-reduction-00.txt   draft-ietf-tsvwg-rsvp-bw-reduction-01.txt 
Internet Engineering Task Force James Polk
Internet Draft Subha Dhesikan
Expiration: August 10th, 2005 Cisco Systems
File: draft-ietf-tsvwg-rsvp-bw-reduction-00.txt
A Resource Reservation Extension for the Reduction of Transport Area Working Group James Polk
Bandwidth of a Reservation Flow Internet Draft Subha Dhesikan
Expiration: March 8th, 2005 Cisco Systems
File: draft-ietf-tsvwg-rsvp-bw-reduction-01.txt September 8th, 2005
February 10th, 2005 A Resource Reservation Protocol Extension for the
Reduction of Bandwidth of a Reservation Flow
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, each author represents that any
patent or other IPR claims of which I am aware have been disclosed, applicable patent or other IPR claims of which he or she is aware
and any of which I become aware will be disclosed, in accordance have been or will be disclosed, and any of which he or she becomes
with RFC 3668. 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 Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as other groups may also distribute working documents as Internet-
Internet-Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference 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.
This Internet-Draft will expire on March 8th, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). All Rights Reserved. Copyright (C) The Internet Society (2005). All Rights Reserved.
Abstract Abstract
This document proposes an extension to the Resource Reservation This document proposes an extension to the Resource Reservation
Protocol (RSVPv1) to reduce the guaranteed bandwidth allocated to an Protocol (RSVPv1) to reduce the guaranteed bandwidth allocated to an
existing reservation. This mechanism can be used to affect existing reservation. This mechanism can be used to affect
individual reservations, aggregate reservations or other forms of individual reservations, aggregate reservations or other forms of
skipping to change at page 2, line 17 skipping to change at page 2, line 17
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1 Conventions . . . . . . . . . . . . . . . . . . . . . . 4 1.1 Conventions . . . . . . . . . . . . . . . . . . . . . . 4
1.2 Changes From Previous Versions . . . . . . . . . . . . . 4 1.2 Changes From Previous Versions . . . . . . . . . . . . . 4
2. Individual Reservation Reduction Scenario . . . . . . . . . . 5 2. Individual Reservation Reduction Scenario . . . . . . . . . . 5
3. RSVP Aggregation Overview . . . . . . . . . . . . . . . . . . 6 3. RSVP Aggregation Overview . . . . . . . . . . . . . . . . . . 6
3.1 RSVP Aggregation Reduction Scenario . . . . . . . . . . . 8 3.1 RSVP Aggregation Reduction Scenario . . . . . . . . . . . 8
4. Requirements for Reservation Reduction . . . . . . . . . . . 9 4. Requirements for Reservation Reduction . . . . . . . . . . . 9
5. RSVP Bandwidth Reduction Solution . . . . . . . . . . . . . . 10 5. RSVP Bandwidth Reduction Solution . . . . . . . . . . . . . . 10
5.1 Partial Preemption Error Code . . . . . . . . . . . . . 10 5.1 Partial Preemption Error Code . . . . . . . . . . . . . 10
5.2 Error Flow Descriptor . . . . . . . . . . . . . . . . . 11 5.2 Error Flow Descriptor . . . . . . . . . . . . . . . . . 11
5.3 Individual Reservation Flow Reduction . . . . . . . . . . 11 5.3 Individual Reservation Flow Reduction . . . . . . . . . 11
5.4 Aggregation Reduction of Individual Flows . . . . . . . . 11 5.4 Aggregation Reduction of Individual Flows . . . . . . . 11
5.5 RSVP Flow Reduction involving IPsec Tunnels . . . . . . . 12 5.5 RSVP Flow Reduction involving IPsec Tunnels . . . . . . 12
6. Backwards Compatibility . . . . . . . . . . . . . . . . . . . 12 6. Backwards Compatibility . . . . . . . . . . . . . . . . . . . 12
7. Security Considerations . . . . . . . . . . . . . . . . . . 13 7. Security Considerations . . . . . . . . . . . . . . . . . . 13
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
Appendix. Walking Through the Solution . . . . . . . . . . . . . 14 Appendix. Walking Through the Solution . . . . . . . . . . . . . 14
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
10.1 Normative References . . . . . . . . . . . . . . . . . . 17 10.1 Normative References . . . . . . . . . . . . . . . . . . 17
10.2 Informational References . . . . . . . . . . . . . . . . 17 10.2 Informational References . . . . . . . . . . . . . . . . 17
11. Author Information . . . . . . . . . . . . . . . . . . . . . 18 11. Author Information . . . . . . . . . . . . . . . . . . . . . 18
skipping to change at page 10, line 25 skipping to change at page 10, line 25
flowspec contained in the ResvErr message indicates the flowspec flowspec contained in the ResvErr message indicates the flowspec
that is reserved and this flowspec may not match or be less than the that is reserved and this flowspec may not match or be less than the
original reservation request. This is defined in section 5.2. original reservation request. This is defined in section 5.2.
A comment about RESV message not using a reliable transport. This A comment about RESV message not using a reliable transport. This
document recommends that ResvErr message be made reliable by document recommends that ResvErr message be made reliable by
implementing mechanisms in [6]. implementing mechanisms in [6].
The current behavior in RSVP requires a ResvTear message to be The current behavior in RSVP requires a ResvTear message to be
transmitted upstream when the ResvErr message is transmitted transmitted upstream when the ResvErr message is transmitted
downstream (per 1). This ResvTear message terminates the downstream (per [1]). This ResvTear message terminates the
reservation in all routers upstream of the router where the failure reservation in all routers upstream of the router where the failure
occurred. This document requires that the ResvTear is only occurred. This document requires that the ResvTear is only
generated when the reservation is to be completely removed. In cases generated when the reservation is to be completely removed. In cases
where the reservation is only to be reduced, routers compliant with where the reservation is only to be reduced, routers compliant with
this specification requires that the ResvTear message MUST NOT be this specification requires that the ResvTear message MUST NOT be
sent. sent.
An appendix has been written to walk through the overall solution to An appendix has been written to walk through the overall solution to
the problems presented in sections 2 and 3. There is mention of the problems presented in sections 2 and 3. There is mention of
this ResvTear transmission behavior within the appendix. this ResvTear transmission behavior within the appendix.
skipping to change at page 17, line 50 skipping to change at page 17, line 50
10.2 Informational References 10.2 Informational References
[9] J. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston, [9] J. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston,
J. Peterson, R. Sparks, M. Handley, and E. Schooler, "SIP: J. Peterson, R. Sparks, M. Handley, and E. Schooler, "SIP:
Session Initiation Protocol", RFC 3261, May 2002. Session Initiation Protocol", RFC 3261, May 2002.
[10] K. Ramakrishnan, S. Floyd, D. Black, "The Addition of Explicit [10] K. Ramakrishnan, S. Floyd, D. Black, "The Addition of Explicit
Congestion Notification (ECN) to IP", RFC 3168, September 2001 Congestion Notification (ECN) to IP", RFC 3168, September 2001
[11] F. Le Faucheur, B. Davie, P. Bose, C. Christou, " Aggregate [11] F. Le Faucheur, B. Davie, P. Bose, C. Christou, " Aggregate
reservations for IPsec Tunnel", draft-lefaucheur-rsvp-ipsec-00, reservations for IPsec Tunnel", draft-lefaucheur-rsvp-ipsec-01,
February 2005, "work in progress" July 2005, "work in progress"
11. Author Information 11. Author Information
James M. Polk James M. Polk
Cisco Systems Cisco Systems
2200 East President George Bush Turnpike 2200 East President George Bush Turnpike
Richardson, Texas 75082 USA Richardson, Texas 75082 USA
Email: jmpolk@cisco.com Email: jmpolk@cisco.com
skipping to change at page 19, line 18 skipping to change at page 19, line 18
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.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
The Expiration date for this Internet Draft is: The Expiration date for this Internet Draft is:
August 10th, 2005 March 8th, 2006
 End of changes. 10 change blocks. 
19 lines changed or deleted 20 lines changed or added

This html diff was produced by rfcdiff 1.28, available from http://www.levkowetz.com/ietf/tools/rfcdiff/