Re: [xrblock] Transport of I.D-xrblock-rtcp-xr-qoe style quality datain IPFIX

>> Also it seems you give a range for each RTPMOSClass as follows:
>>
>> rtpMOSClass 1: MoS value < 3.10
>> rtpMOSClass 2:  3.10<=MoS value<3.60
>> rtpMOSClass 3:  3.60<=MoS value<4.03
>> rtpMOSClass 4:  4.03<=MoS value< 4.34
>> rtpMOSCalss 5: 4.34<= MoS value<=5
>>
>> I am wondering what the rationale is for such range allocation. which reference are you based on?
> 
> This is based on ITU-T G.107 (table B.1) referring to the perceived user 
> experience.

[Qin]: Make sense.
Table B.1 is a good example to see translation between MoS value and Rating value.

>> Lastly why should the rtpMoSClass choose 'number of seconds' as unit?
> 
> In order to calculate a MOS value multiple seconds worth of data have
> to be present to begin with (TM Forum claims 8-10 seconds).
> The data format is flexible in regards to as many seconds worth of
> data are transported in a single IPFIX record.
> Systems may use fixed time slices (e.g. one record for 30 seconds
> worth of stream data) or one record per (variable length) stream/call.
> An IPFIX mediator/collector or any data warehouse should be able
> to aggregate the data a) from multiple records belonging to a
> single streams and b) multiple records belonging to multiple streams.
> 
> What unit were you thinking of?

[Qin]: I thought rtpMoSClass has no unit and 'Number of seconds the monitored stream'
should be regarded as a new information element in parallel with rtpMoSClass rather than
one attribute of rtpMoSClass. am I wrong?
> 
> Thanks for your feedback,
>  Hendrik
> 
> -- 
> Hendrik Scholz <hs@123.org>
> 
> 
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock