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

I think we need to have a phone call to discuss this whole thing.

Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com <http://www.avanw.com/>, www.X192.org

On Mon, Jan 14, 2013 at 8:27 PM, Qin Wu <bill.wu@huawei.com> wrote:

> **
> Hi,Kevin:
> I like to make some additioal clarification to your question.
> I think the packet arrives exactly on time, is also referred to the packet
> that has nominal delay.
>  So we have two ways to address this.
> a. It is more like implementation specific issue,e.g., rely on timing
> information in the headers of previous
> packet and current packet or rely on time window to determine this. So we
> can leave this to the specific
>  implemenations.
>
> b. we can explain the packet that arrives exactly on time as the packet
> that has nominal delay.
> The nominal delay can either be choosen as the jitter buffer delay for the
> packet with minimal delay(i.e.,
> the reference packet is choosen as the packet with minmal delay) or
> average delay for all the packets that arrives
> within the implementation specific time window during the measurement
> interval.
> I am not sure we should details to talk about this, but If we take (b),
> we prefer to add the following sentence in the draft to say:
> "Note that the reference packet is generally selected as the packet
>  with minimum delay based on the most common criterion (see Sections 1<http://tools.ietf.org/html/rfc6798#section-1> and
> 5.1 of [RFC5481 <http://tools.ietf.org/html/rfc5481>]).
> "
> Let me know what you think about this.
>
> Regards!
> -Qin
>
> ----- Original Message -----
> *From:* Qin Wu <bill.wu@huawei.com>
> *To:* Kevin Gross <kevin.gross@avanw.com>
> *Cc:* xrblock <xrblock@ietf.org>
> *Sent:* Monday, January 14, 2013 8:46 AM
> *Subject:* Re: [xrblock] Fw: I-D Action:
> draft-ietf-xrblock-rtcp-xr-jb-02.txt
>
> Kevin:
> As I clarified to you in the previous email, "implemention specific time
> window" described in Burst Gap drafts will be used to identify a "packet
> that arrives exactly on time".
> That is to say, if the receiving packet falls within  implemention
> specific time window and can be sucessfully playout, such packet will be
> regarded as packet that arrives exactly on time.
> Hope this clarifies.
>
> Regards!
> -Qin
>
> ----- Original Message -----
> *From:* Kevin Gross <kevin.gross@avanw.com>
> *To:* Qin Wu <bill.wu@huawei.com>
> *Cc:* xrblock <xrblock@ietf.org>
> *Sent:* Sunday, January 13, 2013 6:04 AM
> *Subject:* Re: offlist//Re: [xrblock] Fw: I-D Action:
> draft-ietf-xrblock-rtcp-xr-jb-02.txt
>
> Qin,
>
> Of the jitter buffer delay metric, the draft currently says "It is
> calculated based on the difference between the receipt time and the
> playout time for the packet that arrives exactly on time."
>
> My issue is that I don't know how to identify a "packet that arrives
> exactly on time".
>
> Kevin Gross
> +1-303-447-0517
> Media Network Consultant
> AVA Networks - www.AVAnw.com, www.X192.org
>
>  ------------------------------
>
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock
>
>