Re: [xrblock] Fw: I-D Action: draft-ietf-xrblock-rtcp-xr-jb-02.txt

> >> Is the "jitter buffer rate" field useless? If not, why is an
> >> equivalent not included in the new draft? It seems like if the
> >> plan is to have these new report blocks replace the old ones, they
> >> should at least contain the same data...
> >
> > [Qin]: JB draft focus on reporting How jitter buffers are capable of
> > automatically adjusting to changes in delay rather than changs in
> > rate. That is say jb metrics are measured in millisecond while jitter
> > buffer rate is measured in unit from 0 to 15.
> 
> Who cares?

[Qin]: My point, jitter buffer rate does not belong to jitter buffer metric for delay.

>> Also jitter buffer rate
> > is more like configuration parameter that is only applied to adaptive
> > jitter buffer and doesn't look to me a mandotary feature that need to
> > be supported for the implementation.
> 
> So as it stands, in order to report the jitter buffer rate, an 
> implementation would be required to send the VoIP Metrics Report Block 
> even if it was not a VoIP application.  It seems like you're OK w/that; 
> is it also the consensus of the WG?

[Qin]: See above.
I don't know why you think jitter buffer rate is so much important?
> ...
> 
>>> I'm still waiting for  someone to define "nominal" in this context
> >> (hint: this
> >>
> >> jitter buffer nominal delay (JB nominal): 16 bits This is the
> >> current nominal jitter buffer delay in milliseconds, which
> >> corresponds to the nominal jitter buffer delay for packets that
> >> arrive exactly on time. This parameter MUST be provided for both
> >> fixed and adaptive jitter buffer implementations.
> >>
> >> does not contain a definition ;-)
> >
> > [Qin]: As I clarified to Kevin, implementation specific time window
> > will tell us what the exactly on time means. the jitter buffer can be
> > considered as a time window with one side (the early side) aligned
> > with the recent minimum delay and the other side (the late side)
> > representing the maximum permissible delay before a packet would be
> > discarded.
> >
> > So nominal just means packets arrive within the time wondow and can
> > be successully played out.
> 
> OK, but what is the difference between this and jitter buffer maximum 
> delay, then?

[Qin]: It seems I had clarified this to you on the list more than once.
Please look into the draft and my previous comments. The difference is they have different reference point,i.e.,
jitter buffer maximum delay will be measured based on the earliest arriving packet rathen than the packet
arrives on time.
> 
> 
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock