Alternative to draft-ash-mpls-diffserv-te-class-types-00.txt ?

["Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>]

Hi! As far as I understand, this draft attempts to combine
multitude of user traffic requirements (DiffServ class, CAC,
preemption priorities...) into one logical construct by 
introducing (/building on) the concept of Class-Type. 

Personally, I feel the same goal can be achieved, without
introducing a new concept.

My primary concerns, with the proposed solutions are:
----------------------------------------------------
	1. The proposed solution builds on the concept
	of Class-Type, which is based on a _one of the_
	solutions to DS-TE.
		a. Personally, I think the concept of 
		Class-Type some how crept into the DS-TE-REQTS
		draft from one of the DS-TE solutions.

		b. From the recent posting, I sense that the
		new revision of DS-TE-REQTS will remove the 
		Class-Type as a requirement.
	
		c. The draft under discussion, itself indicates
		that there are better alternatives to solve the
		IGP scalability problem without introducing 
		Class-Type. [ex: Per-Class BW accounting /
		IGP-ALTERNATIVES/the upcoming 'unified' DS-TE
		approach(?)]

	2. This draft attempts to standardize the different
	user requirements into 6 Class Types, based on current
	experience.
		a. User's requirement may not fit into one of 
		predefined 6 Class-Types

		b. I am not sure whether, this information need
		to be standardized. [Service Provider-1's "Gold
		Service" may be same as Service Provide-2's 
		"Bronze Service -and it does not matter!]
		
Alternative:
------------
	Scalability:
	~~~~~~~~~~~
	The DS-TE scalability issue can be handled by the some
	of the existing DS-TE proposals (kompella,ash,boyel..)

	User friendly specification of traffic parameters:
	~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
	One can always define a MIB table, inline with ATM's UPC
	contract tables. 

	In this approach, user can define a _named_ template, that 
	captures traffic characteristics like (as defined in the 
	draft):
		a. DiffServ/queueing priority Pubs
		b. QoS classes (?)
		c. MPLS/CAC priority classes
		d. restoration priority classes
		e. preemption priority classes
		... ... ...

	This allows the user to define his own "Class-Type", 
	from the individual parameters.

Thanks,
sanjay
	
	
	

> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Tuesday, November 20, 2001 7:14 AM
> Cc: te-wg@ops.ietf.org
> Subject: I-D ACTION:draft-ash-mpls-diffserv-te-class-types-00.txt
> 
> 
> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> 
> 
> 	Title		: Proposed MPLS/DiffServ TE Class Types
> 	Author(s)	: J. Ash et al.
> 	Filename	: draft-ash-mpls-diffserv-te-class-types-00.txt
> 	Pages		: 
> 	Date		: 19-Nov-01
> 	
> Service Provider requirements for support of DiffServ aware 
> MPLS Traffic
> Engineering (MPLS-DS-TE) are presented in [MPLS-DS-TE-REQ].  
> This initiative includes the definition of MPLS-DiffServ-TE 
> class types (CTs), wherein CTs are defined as aggregations of 
> individual service classes.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ash-mpls-diffserv-te
> -class-types-00.txt
> 
> To remove yourself from the IETF Announcement list, send a message to 
> ietf-announce-request with the word unsubscribe in the body 
> of the message.
> 
> Internet-Drafts are also available by anonymous FTP. Login 
> with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ash-mpls-diffserv-te-class-types-00.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html 
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE 
> /internet-drafts/draft-ash-mpls-diffserv-te-class-types-00.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant 
> mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 		
> 		
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>