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

Hannes Tschofenig <[email protected]> Sat, 27 Feb 2010 22:58:21 +0200
Newsgroups gmane.ietf.nsis
Message-ID <[email protected]>
Btw, for the Diameter work we specified a separate "Bandwidth" AVP since 
folks thought it was too complicated to specify bandwidth with the TMOD 
parameter.

See Bandwidth AVP in http://www.ietf.org/rfc/rfc5624.txt

Ciao
Hannes

Hannes Tschofenig wrote:
> Agree with Jerry.
>
> A minor note: The question we got during the review of the DIME 
> documents was: "What is large? State the value."
> This refers to the values in:
>
> >     o  TMOD Size-1 (b) = large
> >     o  Minimum Policed Unit-1 (m) = large
>
> Ciao
> Hannes
>
> Gerald Ash wrote:
>> Georgios,
>>  
>> See below.
>>  
>> > 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)        |
>> >   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> Just to be clear, the "Bandwidth ID" = 1, which is the same value as 
>> the TMOD-1 parameter ID (= 1), as already assigned by IANA.  It is 
>> not necessary to define another QSPEC parameter ID.  What you are 
>> calling the "<bandwidth> parameter" is actually the TMOD-1 parameter 
>> with particular values.  Once again, it is required that all 
>> NSIS/NSLP/QOSM implementations send the TMOD-1 parameter in their 
>> QSPEC's.
>> > Regarding the "large" values, I will specify them in Section 4.6.
>>  
>> OK.
>>  
>> Thanks,
>> Jerry
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> nsis mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/nsis
>>   
>
> _______________________________________________
> nsis mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/nsis