draft-ietf-tsvwg-intserv-multiple-tspec-00.txt		draft-ietf-tsvwg-intserv-multiple-tspec-01.txt
	Network WG James Polk		Network WG James Polk
	Internet-Draft Subha Dhesikan		Internet-Draft Subha Dhesikan
	Expires: January 4, 2012 Cisco Systems		Expires: September 12, 2012 Cisco Systems
	Intended Status: Standards Track (PS) July 4, 2011		Intended Status: Standards Track (PS) March 12, 2012
	Updates: RFC 2205, 2210, & 4495 (if published as an RFC)		Updates: RFC 2205, 2210, & 4495 (if published as an RFC)
	Integrated Services (IntServ) Extension to Allow Signaling of Multiple		Integrated Services (IntServ) Extension to Allow Signaling of Multiple
	Traffic Specifications and Multiple Flow Specifications in RSVPv1		Traffic Specifications and Multiple Flow Specifications in RSVPv1
	draft-ietf-tsvwg-intserv-multiple-tspec-00		draft-ietf-tsvwg-intserv-multiple-tspec-01
	Abstract		Abstract
	This document defines extensions to Integrated Services (IntServ)		This document defines extensions to Integrated Services (IntServ)
	allowing multiple traffic specifications and multiple flow		allowing multiple traffic specifications and multiple flow
	specifications to be conveyed in the same Resource Reservation		specifications to be conveyed in the same Resource Reservation
	Protocol (RSVPv1) reservation message exchange. This ability helps		Protocol (RSVPv1) reservation message exchange. This ability helps
	optimize an agreeable bandwidth through a network between endpoints		optimize an agreeable bandwidth through a network between endpoints
	in a single round trip.		in a single round trip.
	Legal
	This documents and the information contained therein are provided on
	an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
	REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
	IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
	WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
	WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE
	ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
	FOR A PARTICULAR PURPOSE.
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with		This Internet-Draft is submitted in full conformance with the
	the provisions of BCP 78 and BCP 79.		provisions of BCP 78 and 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). Note that other groups may also distribute
	other groups may also distribute working documents as Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	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		This Internet-Draft will expire on Sept 12, 2012.
	http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on January 4, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2012 IETF Trust and the persons identified as the		Copyright (c) 2011 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with		carefully, as they describe your rights and restrictions with
	respect to this document. Code Components extracted from this		respect to this document. Code Components extracted from this
	document must include Simplified BSD License text as described in		document must include Simplified BSD License text as described in
	Section 4.e of the Trust Legal Provisions and are provided without		Section 4.e of the Trust Legal Provisions and are provided without
	warranty as described in the BSD License.		warranty as described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Overview of the Proposal for including multiple TSPECs and		2. Overview of the Proposal for including multiple TSPECs and
	FLOWSPECs . . . . . . . . . . . . 6		FLOWSPECs . . . . . . . . . . . . 6
	3. Multi_TSPEC and MULTI_FLOWSPEC Solution . . . . . . . . . . . 8		3. Multi_TSPEC and MULTI_FLOWSPEC Solution . . . . . . . . . . . 8
	3.1 New MULTI_TSPEC and MULTI-RSPEC Parameters . . . . . . . 9		3.1 New MULTI_TSPEC and MULTI-RSPEC Parameters . . . . . . . 9
	3.2 Multiple TSPEC in a PATH Message . . . . . . . . . . . . 9		3.2 Multiple TSPEC in a PATH Message . . . . . . . . . . . . 9
	3.3 Multiple FLOWSPEC for Controlled Load Service . . . . . . 12		3.3 Multiple FLOWSPEC for Controlled Load Service . . . . . . 12
	skipping to change at page 23, line 38		skipping to change at page 23, line 38
	[RFC2210] J. Wroclawski, "The Use of RSVP with IETF Integrated		[RFC2210] J. Wroclawski, "The Use of RSVP with IETF Integrated
	Services", RFC 2210, September 1997		Services", RFC 2210, September 1997
	[RFC2212] S. Shenker, C. Partridge, R. Guerin, "Specification of		[RFC2212] S. Shenker, C. Partridge, R. Guerin, "Specification of
	Guaranteed Quality of Service", RFC 2212, September 1997		Guaranteed Quality of Service", RFC 2212, September 1997
	[RFC2215] S. Shenker, J. Wroclawski, "General Characterization		[RFC2215] S. Shenker, J. Wroclawski, "General Characterization
	Parameters for Integrated Service Network Elements",		Parameters for Integrated Service Network Elements",
	RFC 2212, September 1997		RFC 2212, September 1997
	[RFC4495] J. Polk, S. Dhesikan, "A Resource Reservation Protocol
	(RSVP) Extension for the Reduction of Bandwidth of a
	Reservation Flow", RFC 4495, May 2006
	[RFC2747] F. Baker, B. Lindell, M. Talwar, " RSVP Cryptographic		[RFC2747] F. Baker, B. Lindell, M. Talwar, " RSVP Cryptographic
	Authentication", RFC2747, January 2000		Authentication", RFC2747, January 2000
	[RFC3097] R. Braden, L. Zhang, "RSVP Cryptographic Authentication --		[RFC3097] R. Braden, L. Zhang, "RSVP Cryptographic Authentication --
	Updated Message Type Value", RFC 3097, April 2001		Updated Message Type Value", RFC 3097, April 2001
			[RFC4495] J. Polk, S. Dhesikan, "A Resource Reservation Protocol
			(RSVP) Extension for the Reduction of Bandwidth of a
			Reservation Flow", RFC 4495, May 2006
	8.2. Informative References		8.2. Informative References
	[IANA] http://www.iana.org/assignments/integ-serv		[IANA] http://www.iana.org/assignments/integ-serv
	Authors' Addresses		Authors' Addresses
	James Polk		James Polk
	3913 Treemont Circle		3913 Treemont Circle
	Colleyville, Texas, USA		Colleyville, Texas, USA
	+1.817.271.3552		+1.817.271.3552
End of changes. 10 change blocks.
	32 lines changed or deleted		15 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/