[CCAMP] index field in draft-ietf-ccamp-ethernet-traffic-parameters

["Benoit C Tremblay" <[e-mail]>]

> Hello Dimitri,
> 
> I have further comments on the section decribing the index field.
> 
> 1) There is a reference to an expired draft (draft-minei-diffserv-te-multi-class).  It should be removed.  
> 
> 2) The requirement that "the index field value MUST correspond to at least one of the index values included in the CLASSTYPE object" is a bit problematic as a single CLASSTYPE object can be present in a PATH message and a single classtype can be represented with this object. The requirement would then exclude the possibility to insert multiple bandwidth profile TLVs in the SENDER_TSPEC.  I suggest that this requirement should be conditional to the presence of thhe CLASSTYPE object.  If a CLASSTYPE object is present, then a single BW profile TLV shall be present and the index value must be the CT defined in the CLASSTYPE object.  If no CLASSTYPE object is present, multiple BW profile TLV (up to 8) can be present and the index value either represent a CT (values in [0, 7]) or a predefined set of CT (values in [8, 247]).
> 
> 3) Also, it should be clarified that the 240 pre-defined sets of CTs are not standard.  The following text is proposed to be included :
> "To ensure coherent operation, the network administrator MUST configure exactly the same pre-defined CT sets on all LSRs of the GMPLS domain. Proper configuration needs also to be agreed between administrative domains if this feature is used over UNI. The mean to pre-configured those sets and their definitions are out of scope of this specification. "
> 
> Regards,
> 
> Benoit
> 
> >  <<Picture (Metafile)>> 
> Benoit Tremblay
> Broadband and Systems Research
> Ericsson Canada
> 8400 Décarie    Mount-Royal
> Tel: [phone] x45064
> Cell.: [phone]
> Fax: [phone]
> mailto: [e-mail]
> 
>