Re: AD evaluation comments on draft-ietf-nsis-rmd-15

Hi Jerry

Please see in line!

On 2/26/2010, "Gerald Ash" <[email protected]> wrote:

>Hi Georgios,
> 
>>>1. Section 4.1.1 (http://tools.ietf.org/html/draft-ietf-nsis-rmd-15#section-4.1.1) defines
>>> a <bandwidth> parameter, which appears is intended to replace the mandatory TMOD
>>> parameter for use in the RMD-QOSM.  The QSPEC specifies in Section 3.1.1. 
>>>(http://tools.ietf.org/html/draft-ietf-nsis-qspec-24#section-3.3.1) 
>>>"   The <Traffic Model> (TMOD) parameter is mandatory for the QNI to
>>>   include in the initiator QSPEC and mandatory for downstream QNEs to
>>>   interpret. "
>>>and
>>>"   All 5 of the sub-parameters MUST be included in the TMOD parameter.
>>>  The TMOD parameter can be set to describe the traffic source.  If,
>>>   for example, TMOD is set to specify bandwidth only, then set r = peak
>>>   rate = p, b = large, m = large. "
>>> 
>>> Hence the RMD-QOSM MUST use the TMOD parameter and can use it to
>>> specify "bandwidth" only, as per the second statement above (recall that the second
>>> statement was specifically included with RMD-QOSM in mind).  The <bandwidth>
>>> parameter is therefore unnecessary in RMD-QOSM.
>
>> Georgios: Thanks! You are right, but we still need that IANA assigns the
>> <Bandwidth> parameter. In order to satisfy your comment, we will
>> redefine the <Bandwidth> parameter in the following way:
>
>>  The bit format used for the <Bandwidth> parameter is identical to the
>>  bit format of the <TMOD-1> parameter format specified in [QSP-T] but the
>>  fields are set in the following way:
>>   o  TMOD Rate-1 (r)= Peak Data Rate-1 (p)
>>   o  TMOD Size-1 (b) = large
>>   o  Minimum Policed Unit-1 (m) = large
> 
>It wouldn't be appropriate to have IANA specify the values of the sub-parameters of TMOD-1.  I suggest that you define these TMOD-1 sub-parameter values in Section 4.1.1, and remove references to a new "<bandwidth>" parameter.  You might also want to specify a specific value for "large".

Georgios: I do not think that IANA will specify the values TMOD-1
sub-parameter values.

---------------

The bandwidth parameter is just the translation of the T-MOD parameter to
the bandwidth paramter. I will include the following information in the
draft:

   The bit format used for the <Bandwidth> parameter is shown below and
   it is a translation of the <TMOD-1> parameter, see [QSP-T], to
   specify bandwidth only, by setting, see [QSP-T]:
     o  TMOD Rate-1 (r)= Peak Data Rate-1 (p)
     o  TMOD Size-1 (b) = large
     o  Minimum Policed Unit-1 (m) = large

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |1|E|0|r|  Bandwidth ID         |r|r|r|r|          5            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Peak Data Rate-1 (p) (32-bit IEEE floating point number)     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  TMOD Size-1 (b) (32-bit IEEE floating point number)          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Peak Data Rate-1 (p) (32-bit IEEE floating point number)     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Minimum Policed Unit-1 (m) (32-bit unsigned integer)         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Maximum Packet Size-1 (MPS) (32-bit unsigned integer)        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

------------------------------------------

Regarding the "large" values, I will specify them in Section 4.6.

Best regards,
Georgios


> 
>Thanks,
>Jerry 
> 
> 
> 
>
>
>      )