Re: AD evaluation comments on draft-ietf-nsis-rmd-15
"Georgios Karagiannis" <[email protected]> Sat, 27 Feb 2010 20:08:38 +0000
| Newsgroups | gmane.ietf.nsis |
|---|---|
| Message-ID | <[email protected]> |
Hi Jerry See below! On 2/27/2010, "Gerald Ash" <[email protected]> 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. The Bandwidth ID = 17. This parameter is different then the definition of TMOD, since it is specifying bandwidth only, see the particular paragraph in the QSPEC draft: "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. As another example if TMOD is set for TCP traffic, then set r = average rate, b = large, p = large." The bit format of Bandwidth is representing the semantics of the above paragraph. As you can see here the difference in the bit format is that the TMOD Rate-1 (r) field is replaced by the Peak Data Rate-1 (p) field. 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) | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Best regards, Georgios > >> Regarding the "large" values, I will specify them in Section 4.6. > >OK. > >Thanks, >Jerry > > > )