
From ron.even.tlv@gmail.com  Mon Jan  2 02:27:53 2012
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EE7821F8C4B for <xrblock@ietfa.amsl.com>; Mon,  2 Jan 2012 02:27:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7vCEHhU+rwr8 for <xrblock@ietfa.amsl.com>; Mon,  2 Jan 2012 02:27:52 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7B3BC21F8C4C for <xrblock@ietf.org>; Mon,  2 Jan 2012 02:27:52 -0800 (PST)
Received: by eekc14 with SMTP id c14so13985538eek.31 for <xrblock@ietf.org>; Mon, 02 Jan 2012 02:27:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :content-language:thread-index; bh=SqlkkNX3L/aHwD3msxXXG/aRVDLejiFhcf0bQqExvwQ=; b=r4GKKcgRFTScOn0xuKtf0NFPbEKKF9oeuZWCNgo/tjq6hwbdKbY9HcGXpvmncI/HJc Gmx3Uh3slTMdIFsLL6KqLqwLbwQzql5J9mNUE/ZESgQCFHn4oxKCR4EeC0WOVNSKgTV0 QqVxfiXXxzctn4tTPlBDLFVbBQ/1JnsqzKUL8=
Received: by 10.213.34.200 with SMTP id m8mr12637033ebd.139.1325500071655; Mon, 02 Jan 2012 02:27:51 -0800 (PST)
Received: from windows8d787f9 ([109.67.213.220]) by mx.google.com with ESMTPS id a60sm189581716eeb.4.2012.01.02.02.27.48 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 02 Jan 2012 02:27:49 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <xrblock@ietf.org>
References: <9423CDD1-DAB3-4736-BC80-4891375A20B5@ntt-at.com>
In-Reply-To: <9423CDD1-DAB3-4736-BC80-4891375A20B5@ntt-at.com>
Date: Mon, 2 Jan 2012 12:24:26 +0200
Message-ID: <4f0186a5.d4260e0a.49db.5d43@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Content-language: en-us
Thread-index: Acy6uKTjovvup+GDSKuAKj3+Frd62AOf+b6A
Subject: Re: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-meas-identity
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jan 2012 10:27:53 -0000

Hi,
Sorry for the late feedback, I read the draft and except for the editorial
changes that were already discussed have no other comments and support the
publication of the document
Roni Even

> -----Original Message-----
> From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On
> Behalf Of Shida Schubert
> Sent: Thursday, December 15, 2011 1:32 AM
> To: xrblock@ietf.org
> Subject: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-meas-identity
> 
> 
> This is an announcement of XRBLOCK WG last call on "Measurement
> Identity and information Reporting using SDES item and XR Block" prior
> to requesting publication the document as a proposed standard.
> 
> As there is Christmas, This is a two week working group last call so
> please send your comments to the list including nits by the 30th of
> December.
> 
>  If you read the draft and you see no issues, concerns or nits, please
> express the fact that you have no issue progressing the draft on the
> list as well.
> 
>  The latest version can be found here.
> 
> http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp-xr-meas-
> identity/
> 
>  Thanks & Regards
>    Shida Schubert (as WG chair)
> 
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock


From vsingh.ietf@gmail.com  Mon Jan  2 06:48:13 2012
Return-Path: <vsingh.ietf@gmail.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A2B321F84FC for <xrblock@ietfa.amsl.com>; Mon,  2 Jan 2012 06:48:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XZsVx6q6EjNm for <xrblock@ietfa.amsl.com>; Mon,  2 Jan 2012 06:48:12 -0800 (PST)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0C90621F84FA for <xrblock@ietf.org>; Mon,  2 Jan 2012 06:48:11 -0800 (PST)
Received: by wibhj6 with SMTP id hj6so10559401wib.31 for <xrblock@ietf.org>; Mon, 02 Jan 2012 06:48:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=ujil0bcNCYjylLIACTa+UbPME2fa4m0XYAH5K/0OzdY=; b=FFGSj0WURmuWw/hCoAY0GNnRgCFpOSujFzVr2uA1ry8sAfnkSassXtVzzMD4K2hgZb JsOY4tz87QncTLnYdKNJUWu7PaNPvAGO3wdnX9lH1lQViN5h4DmhCmTYfX60aPQXvu0k ujyosLofDMRxKpUA/+065p4NQwN0N3StP12O0=
Received: by 10.180.101.35 with SMTP id fd3mr95863806wib.22.1325515691240; Mon, 02 Jan 2012 06:48:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.83.194 with HTTP; Mon, 2 Jan 2012 06:47:51 -0800 (PST)
In-Reply-To: <4f0186a5.d4260e0a.49db.5d43@mx.google.com>
References: <9423CDD1-DAB3-4736-BC80-4891375A20B5@ntt-at.com> <4f0186a5.d4260e0a.49db.5d43@mx.google.com>
From: Varun Singh <vsingh.ietf@gmail.com>
Date: Mon, 2 Jan 2012 16:47:51 +0200
Message-ID: <CAEbPqrz9_JjhTjf+kUGE_uyckbTMANMr1qX+u0pBKtxpyks8Fw@mail.gmail.com>
To: xrblock@ietf.org
Content-Type: multipart/alternative; boundary=f46d04182552ebabb104b58cab13
Subject: Re: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-meas-identity
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jan 2012 14:48:13 -0000

--f46d04182552ebabb104b58cab13
Content-Type: text/plain; charset=ISO-8859-1

Hi,

Likewise, sorry for the late feedback.

As mentioned in an earlier mail the document needs to clarify how the
interval duration is calculated. Difference between RTP timestamps or
reception times of the packets.

Apart from the above, I have no further comments and support the
publication of the document.

Cheers,
Varun.

On Mon, Jan 2, 2012 at 12:24, Roni Even <ron.even.tlv@gmail.com> wrote:

> Hi,
> Sorry for the late feedback, I read the draft and except for the editorial
> changes that were already discussed have no other comments and support the
> publication of the document
> Roni Even
>
> > -----Original Message-----
> > From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On
> > Behalf Of Shida Schubert
> > Sent: Thursday, December 15, 2011 1:32 AM
> > To: xrblock@ietf.org
> > Subject: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-meas-identity
> >
> >
> > This is an announcement of XRBLOCK WG last call on "Measurement
> > Identity and information Reporting using SDES item and XR Block" prior
> > to requesting publication the document as a proposed standard.
> >
> > As there is Christmas, This is a two week working group last call so
> > please send your comments to the list including nits by the 30th of
> > December.
> >
> >  If you read the draft and you see no issues, concerns or nits, please
> > express the fact that you have no issue progressing the draft on the
> > list as well.
> >
> >  The latest version can be found here.
> >
> > http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp-xr-meas-
> > identity/
> >
> >  Thanks & Regards
> >    Shida Schubert (as WG chair)
> >
> > _______________________________________________
> > xrblock mailing list
> > xrblock@ietf.org
> > https://www.ietf.org/mailman/listinfo/xrblock
>
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock
>



-- 
http://www.netlab.tkk.fi/~varun/

--f46d04182552ebabb104b58cab13
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,<div><br></div><div>Likewise, sorry for the late feedback.</div><div><br=
></div><div>As=A0mentioned in an earlier mail=A0the document needs to clari=
fy how the interval duration is calculated. Difference between RTP timestam=
ps or reception times of the packets.=A0</div>

<div><br></div><div>Apart from the above, I have no further comments and su=
pport the publication of the document.</div><div><br></div><div>Cheers,</di=
v><div>Varun.<br><br><div class=3D"gmail_quote">On Mon, Jan 2, 2012 at 12:2=
4, Roni Even <span dir=3D"ltr">&lt;<a href=3D"mailto:ron.even.tlv@gmail.com=
">ron.even.tlv@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi,<br>
Sorry for the late feedback, I read the draft and except for the editorial<=
br>
changes that were already discussed have no other comments and support the<=
br>
publication of the document<br>
<font color=3D"#888888">Roni Even<br>
</font><div class=3D"im"><br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:xrblock-bounces@ietf.org">xrblock-bounces@ietf=
.org</a> [mailto:<a href=3D"mailto:xrblock-bounces@ietf.org">xrblock-bounce=
s@ietf.org</a>] On<br>
&gt; Behalf Of Shida Schubert<br>
</div><div class=3D"im">&gt; Sent: Thursday, December 15, 2011 1:32 AM<br>
&gt; To: <a href=3D"mailto:xrblock@ietf.org">xrblock@ietf.org</a><br>
&gt; Subject: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-meas-identity<b=
r>
&gt;<br>
&gt;<br>
</div><div><div></div><div class=3D"h5">&gt; This is an announcement of XRB=
LOCK WG last call on &quot;Measurement<br>
&gt; Identity and information Reporting using SDES item and XR Block&quot; =
prior<br>
&gt; to requesting publication the document as a proposed standard.<br>
&gt;<br>
&gt; As there is Christmas, This is a two week working group last call so<b=
r>
&gt; please send your comments to the list including nits by the 30th of<br=
>
&gt; December.<br>
&gt;<br>
&gt; =A0If you read the draft and you see no issues, concerns or nits, plea=
se<br>
&gt; express the fact that you have no issue progressing the draft on the<b=
r>
&gt; list as well.<br>
&gt;<br>
&gt; =A0The latest version can be found here.<br>
&gt;<br>
&gt; <a href=3D"http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp-xr=
-meas-" target=3D"_blank">http://tools.ietf.org/wg/xrblock/draft-ietf-xrblo=
ck-rtcp-xr-meas-</a><br>
&gt; identity/<br>
&gt;<br>
&gt; =A0Thanks &amp; Regards<br>
&gt; =A0 =A0Shida Schubert (as WG chair)<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; xrblock mailing list<br>
&gt; <a href=3D"mailto:xrblock@ietf.org">xrblock@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/xrblock" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/xrblock</a><br>
<br>
_______________________________________________<br>
xrblock mailing list<br>
<a href=3D"mailto:xrblock@ietf.org">xrblock@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/xrblock" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/xrblock</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<a href=3D"http://www.netlab.tkk.fi/~varun/" target=3D"_blank">http://www.n=
etlab.tkk.fi/~varun/</a><br>
</div>

--f46d04182552ebabb104b58cab13--

From csp@csperkins.org  Tue Jan  3 10:05:07 2012
Return-Path: <csp@csperkins.org>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 563901F0C41 for <xrblock@ietfa.amsl.com>; Tue,  3 Jan 2012 10:05:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ti4qzoRNgM9U for <xrblock@ietfa.amsl.com>; Tue,  3 Jan 2012 10:05:06 -0800 (PST)
Received: from lon1-msapost-3.mail.demon.net (lon1-msapost-3.mail.demon.net [195.173.77.182]) by ietfa.amsl.com (Postfix) with ESMTP id 21C171F0C3E for <xrblock@ietf.org>; Tue,  3 Jan 2012 10:05:06 -0800 (PST)
Received: from starkperkins.demon.co.uk ([80.176.158.71] helo=[192.168.0.30]) by lon1-post-3.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1Ri8iz-0005hQ-e0 for xrblock@ietf.org; Tue, 03 Jan 2012 18:05:04 +0000
From: Colin Perkins <csp@csperkins.org>
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/alternative; boundary="Apple-Mail=_9E51F2A1-78B7-4628-AFC9-C937512801D3"
Date: Tue, 3 Jan 2012 18:04:35 +0000
In-Reply-To: <CAEbPqrz9_JjhTjf+kUGE_uyckbTMANMr1qX+u0pBKtxpyks8Fw@mail.gmail.com>
To: xrblock@ietf.org
References: <9423CDD1-DAB3-4736-BC80-4891375A20B5@ntt-at.com> <4f0186a5.d4260e0a.49db.5d43@mx.google.com> <CAEbPqrz9_JjhTjf+kUGE_uyckbTMANMr1qX+u0pBKtxpyks8Fw@mail.gmail.com>
Message-Id: <969ECD1F-47AA-43A6-B979-40401072DE9B@csperkins.org>
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-meas-identity
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jan 2012 18:05:07 -0000

--Apple-Mail=_9E51F2A1-78B7-4628-AFC9-C937512801D3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi,

[again, apologies for the late feedback]

I sent some comments regarding this draft to the list on 19 December. I =
support publication once those comments have been taken into account.

Colin



On 2 Jan 2012, at 14:47, Varun Singh wrote:
> Hi,
>=20
> Likewise, sorry for the late feedback.
>=20
> As mentioned in an earlier mail the document needs to clarify how the =
interval duration is calculated. Difference between RTP timestamps or =
reception times of the packets.=20
>=20
> Apart from the above, I have no further comments and support the =
publication of the document.
>=20
> Cheers,
> Varun.
>=20
> On Mon, Jan 2, 2012 at 12:24, Roni Even <ron.even.tlv@gmail.com> =
wrote:
> Hi,
> Sorry for the late feedback, I read the draft and except for the =
editorial
> changes that were already discussed have no other comments and support =
the
> publication of the document
> Roni Even
>=20
> > -----Original Message-----
> > From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On
> > Behalf Of Shida Schubert
> > Sent: Thursday, December 15, 2011 1:32 AM
> > To: xrblock@ietf.org
> > Subject: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-meas-identity
> >
> >
> > This is an announcement of XRBLOCK WG last call on "Measurement
> > Identity and information Reporting using SDES item and XR Block" =
prior
> > to requesting publication the document as a proposed standard.
> >
> > As there is Christmas, This is a two week working group last call so
> > please send your comments to the list including nits by the 30th of
> > December.
> >
> >  If you read the draft and you see no issues, concerns or nits, =
please
> > express the fact that you have no issue progressing the draft on the
> > list as well.
> >
> >  The latest version can be found here.
> >
> > http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp-xr-meas-
> > identity/
> >
> >  Thanks & Regards
> >    Shida Schubert (as WG chair)
> >
> > _______________________________________________
> > xrblock mailing list
> > xrblock@ietf.org
> > https://www.ietf.org/mailman/listinfo/xrblock
>=20
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock
>=20
>=20
>=20
> --=20
> http://www.netlab.tkk.fi/~varun/
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock



--=20
Colin Perkins
http://csperkins.org/




--Apple-Mail=_9E51F2A1-78B7-4628-AFC9-C937512801D3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Hi,<div><br></div><div>[again, apologies for the late =
feedback]</div><div><br></div><div>I sent some comments regarding this =
draft to the list on 19 December. I support publication once those =
comments have been taken into =
account.</div><div><br></div><div>Colin</div><div><br></div><div><br></div=
><div><br><div><div>On 2 Jan 2012, at 14:47, Varun Singh =
wrote:</div><blockquote type=3D"cite">Hi,<div><br></div><div>Likewise, =
sorry for the late feedback.</div><div><br></div><div>As&nbsp;mentioned =
in an earlier mail&nbsp;the document needs to clarify how the interval =
duration is calculated. Difference between RTP timestamps or reception =
times of the packets.&nbsp;</div>

<div><br></div><div>Apart from the above, I have no further comments and =
support the publication of the =
document.</div><div><br></div><div>Cheers,</div><div>Varun.<br><br><div =
class=3D"gmail_quote">On Mon, Jan 2, 2012 at 12:24, Roni Even <span =
dir=3D"ltr">&lt;<a =
href=3D"mailto:ron.even.tlv@gmail.com">ron.even.tlv@gmail.com</a>&gt;</spa=
n> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
Sorry for the late feedback, I read the draft and except for the =
editorial<br>
changes that were already discussed have no other comments and support =
the<br>
publication of the document<br>
<font color=3D"#888888">Roni Even<br>
</font><div class=3D"im"><br>
&gt; -----Original Message-----<br>
&gt; From: <a =
href=3D"mailto:xrblock-bounces@ietf.org">xrblock-bounces@ietf.org</a> =
[mailto:<a =
href=3D"mailto:xrblock-bounces@ietf.org">xrblock-bounces@ietf.org</a>] =
On<br>
&gt; Behalf Of Shida Schubert<br>
</div><div class=3D"im">&gt; Sent: Thursday, December 15, 2011 1:32 =
AM<br>
&gt; To: <a href=3D"mailto:xrblock@ietf.org">xrblock@ietf.org</a><br>
&gt; Subject: [xrblock] WGLC for =
draft-ietf-xrblock-rtcp-xr-meas-identity<br>
&gt;<br>
&gt;<br>
</div><div><div></div><div class=3D"h5">&gt; This is an announcement of =
XRBLOCK WG last call on "Measurement<br>
&gt; Identity and information Reporting using SDES item and XR Block" =
prior<br>
&gt; to requesting publication the document as a proposed standard.<br>
&gt;<br>
&gt; As there is Christmas, This is a two week working group last call =
so<br>
&gt; please send your comments to the list including nits by the 30th =
of<br>
&gt; December.<br>
&gt;<br>
&gt; &nbsp;If you read the draft and you see no issues, concerns or =
nits, please<br>
&gt; express the fact that you have no issue progressing the draft on =
the<br>
&gt; list as well.<br>
&gt;<br>
&gt; &nbsp;The latest version can be found here.<br>
&gt;<br>
&gt; <a =
href=3D"http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp-xr-meas-"=
 =
target=3D"_blank">http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp=
-xr-meas-</a><br>
&gt; identity/<br>
&gt;<br>
&gt; &nbsp;Thanks &amp; Regards<br>
&gt; &nbsp; &nbsp;Shida Schubert (as WG chair)<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; xrblock mailing list<br>
&gt; <a href=3D"mailto:xrblock@ietf.org">xrblock@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/xrblock" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/xrblock</a><br>
<br>
_______________________________________________<br>
xrblock mailing list<br>
<a href=3D"mailto:xrblock@ietf.org">xrblock@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/xrblock" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/xrblock</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- =
<br><a href=3D"http://www.netlab.tkk.fi/~varun/" =
target=3D"_blank">http://www.netlab.tkk.fi/~varun/</a><br>
</div>
_______________________________________________<br>xrblock mailing =
list<br><a =
href=3D"mailto:xrblock@ietf.org">xrblock@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/xrblock<br></blockquote></div><br><div =
apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Arial; font-size: 9px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Lucida Sans Typewriter'; font-size: 9px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; color: rgb(0, 0, 0); =
font-family: 'Lucida Sans Typewriter'; font-size: 9px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; -webkit-text-decorations-in-effect: none; =
text-indent: 0px; -webkit-text-size-adjust: auto; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; color: rgb(0, 0, 0); font-family: 'Lucida Sans Typewriter'; =
font-size: 9px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; =
-webkit-text-decorations-in-effect: none; text-indent: 0px; =
-webkit-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; color: rgb(0, 0, 0); font-family: 'Lucida Sans Typewriter'; =
font-size: 9px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; =
-webkit-text-decorations-in-effect: none; text-indent: 0px; =
-webkit-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"khtml-block-placeholder"></div><div>--&nbsp;</div><div></div><div=
>Colin Perkins</div><div><a =
href=3D"http://csperkins.org/">http://csperkins.org/</a></div></span></spa=
n></span><br class=3D"Apple-interchange-newline"></span><br =
class=3D"Apple-interchange-newline"></span>
</div>
<br></div></body></html>=

--Apple-Mail=_9E51F2A1-78B7-4628-AFC9-C937512801D3--

From eckelcu@cisco.com  Mon Jan  9 15:44:34 2012
Return-Path: <eckelcu@cisco.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F08B021F846F for <xrblock@ietfa.amsl.com>; Mon,  9 Jan 2012 15:44:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.389
X-Spam-Level: 
X-Spam-Status: No, score=-6.389 tagged_above=-999 required=5 tests=[AWL=0.210,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jvFh4iIoAxbb for <xrblock@ietfa.amsl.com>; Mon,  9 Jan 2012 15:44:34 -0800 (PST)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id A07CB21F8469 for <xrblock@ietf.org>; Mon,  9 Jan 2012 15:44:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=4009; q=dns/txt; s=iport; t=1326152668; x=1327362268; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=wn7kHLdYl1HJtDMoHNV1Qbb7PA3qY5+gp4bHgk0J1QM=; b=a/sX9U0PDapmuLMShZPsBimWPvNt0cvYc7C1SVDOjVPPrzng6uaqnP/b pa2M6I9TxH5Zhhyqg4cwfz0G88twkRbfzbZn8JH3f2mykcQYqZCIRXMw4 JppEQI2OwXnzuG1O4r10Ef5Uv2LDX+khC9b3k2h1XyFrBsruiW3TQgTTp M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnQAAFZ7C0+rRDoH/2dsb2JhbAA5CpwXkD2BBYFyAQEBBAEBAQ8BHQotBxcEAgEIDgMEAQELBhcBBgEmHwkIAQEEARIIARmHYJd9AZ5ViFaCWGMEiDmXRodj
X-IronPort-AV: E=Sophos;i="4.71,483,1320624000"; d="scan'208";a="24552277"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-2.cisco.com with ESMTP; 09 Jan 2012 23:44:28 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q09NiSxD009493; Mon, 9 Jan 2012 23:44:28 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 9 Jan 2012 15:44:28 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 9 Jan 2012 15:44:27 -0800
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C061CAE5D@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <72811F84379848C1A4BD21CCFFAE4FDB@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [xrblock] Fw: I-D Action:draft-wu-xrblock-rtcp-xr-quality-monitoring-08.txt
Thread-Index: AczHb8QvlpVifleJRkWjSw+yG7f3EQHsnjUA
References: <72811F84379848C1A4BD21CCFFAE4FDB@china.huawei.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Qin Wu" <bill.wu@huawei.com>, <xrblock@ietf.org>
X-OriginalArrivalTime: 09 Jan 2012 23:44:28.0102 (UTC) FILETIME=[A03EE660:01CCCF28]
Subject: Re: [xrblock] Fw: I-D Action:draft-wu-xrblock-rtcp-xr-quality-monitoring-08.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jan 2012 23:44:35 -0000

(As an individual)

Hi Qin,
=20
I read the draft and have the following comments:

Section 3.2.1-3, the descriptions of segment type, media type, and MoS
type are not consistent. Section 3.2.1 is missing the media type, and
the length of the MoS type field is not consistent.

Section 3.2.2, I agree with the editor's note that additional
information on the sub stream id field is needed.

Section 3.2.3, it is not clear to me how the Channel identifier will be
used. With 4 bits, you can identify the channel, but how do you express
how many channels there are. For example, don't you need to be able to
say, this is channel 2 of 5, or 1 or 2, etc.? Is the assumption that you
will always have a segment for each channel; therefore, the number of
channels is always defined implicitly by the number of channel segments?

As a general comment, I too would like to hear comments from those who
are doing application MoS calculations.

Cheers,
Charles

> -----Original Message-----
> From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On
> Behalf Of Qin Wu
> Sent: Friday, December 30, 2011 7:53 PM
> To: xrblock@ietf.org
> Subject: [xrblock] Fw: I-D Action:draft-wu-xrblock-rtcp-xr-quality-
> monitoring-08.txt
>=20
> One more update to QoE metric reporting draft.
>  http://www.ietf.org/internet-drafts/draft-wu-xrblock-rtcp-xr-quality-
> monitoring-08.txt
>=20
> This draft defines three segment type to support the following three
> different cases:
> 1. multimedia session where each type of media are sent in a separate
>    RTP stream or the layered video session where each layer video are
> sent in a separate RTP
>    stream.
> 2. the layered video session where multi-layer video are carried in
the
> same RTP stream
> 3. the multi-channel audio session where multi-channel voice data are
> carried in the same RTP stream
>=20
> Comparing with the first case, the second and third cases more focus
on
> application specific MoS value reporting
> and but deal with the situation where the case 1 canot  deal with.
>=20
> Comments and suggestions are welcome. It will be good to also hear the
> opinion from people
> who are doing VOIP application MoS calculation.
>=20
> Regards!
> -Qin
> ----- Original Message -----
> From: <internet-drafts@ietf.org>
> To: <i-d-announce@ietf.org>
> Sent: Saturday, December 31, 2011 11:38 AM
> Subject: I-D Action:
draft-wu-xrblock-rtcp-xr-quality-monitoring-08.txt
>=20
>=20
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >
> > Title           : RTCP XR Blocks for QoE metric reporting
> > Author(s)       : Geoff Hunt
> >                          Alan Clark
> >                          Qin Wu
> >                          Roland Schott
> >                          Glen Zorn
> > Filename        : draft-wu-xrblock-rtcp-xr-quality-monitoring-08.txt
> > Pages           : 18
> > Date            : 2011-12-30
> >
> >   This document defines an RTCP XR Report Block and associated SDP
> >   parameters that allow the reporting of QoE metrics for use in a
> range
> >   of RTP applications.
> >
> >
> > A URL for this Internet-Draft is:
> >
http://www.ietf.org/internet-drafts/draft-wu-xrblock-rtcp-xr-quality-
> monitoring-08.txt
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > This Internet-Draft can be retrieved at:
> > ftp://ftp.ietf.org/internet-drafts/draft-wu-xrblock-rtcp-xr-quality-
> monitoring-08.txt
> >
> > _______________________________________________
> > I-D-Announce mailing list
> > I-D-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > Internet-Draft directories: http://www.ietf.org/shadow.html
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock

From bill.wu@huawei.com  Mon Jan  9 21:06:41 2012
Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6774C1F0C53 for <xrblock@ietfa.amsl.com>; Mon,  9 Jan 2012 21:06:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.135
X-Spam-Level: 
X-Spam-Status: No, score=-6.135 tagged_above=-999 required=5 tests=[AWL=0.464,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PK1J9KpIFk5Y for <xrblock@ietfa.amsl.com>; Mon,  9 Jan 2012 21:06:40 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 9D6DF21F8552 for <xrblock@ietf.org>; Mon,  9 Jan 2012 21:06:39 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LXK00HWAGUJ8U@szxga03-in.huawei.com> for xrblock@ietf.org; Tue, 10 Jan 2012 13:06:19 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LXK00A1JGUIO0@szxga03-in.huawei.com> for xrblock@ietf.org; Tue, 10 Jan 2012 13:06:19 +0800 (CST)
Received: from szxeml205-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGF38791; Tue, 10 Jan 2012 13:05:55 +0800
Received: from SZXEML411-HUB.china.huawei.com (10.82.67.138) by szxeml205-edg.china.huawei.com (172.24.2.57) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 10 Jan 2012 13:05:51 +0800
Received: from w53375q (10.138.41.130) by szxeml411-hub.china.huawei.com (10.82.67.138) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 10 Jan 2012 13:05:47 +0800
Date: Tue, 10 Jan 2012 13:05:46 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, xrblock@ietf.org
Message-id: <59256B09E4E044F690F331D509000F8F@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <72811F84379848C1A4BD21CCFFAE4FDB@china.huawei.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C061CAE5D@xmb-sjc-234.amer.cisco.com>
Subject: Re: [xrblock] Fw: I-D Action:draft-wu-xrblock-rtcp-xr-quality-monitoring-08.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jan 2012 05:06:41 -0000

Hi, Charles:
Thank for your detailed review, please see my replies inline.
----- Original Message ----- 
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Qin Wu" <bill.wu@huawei.com>; <xrblock@ietf.org>
Sent: Tuesday, January 10, 2012 7:44 AM
Subject: RE: [xrblock] Fw: I-D Action:draft-wu-xrblock-rtcp-xr-quality-monitoring-08.txt


(As an individual)

Hi Qin,
 
I read the draft and have the following comments:

Section 3.2.1-3, the descriptions of segment type, media type, and MoS
type are not consistent. Section 3.2.1 is missing the media type, and
the length of the MoS type field is not consistent.

[Qin]: Unlike Multi-layer per SSRC segment and Multi-Channel per SSRC segment,
single stream per SSRC segment applies to all the media types or all the applications.
Thefore in the format of single stream per SSRC segment, we don't allocate one bit to 
distinguish between different media type.

As for the length of the MoS type field,  I am not sure I catch your comment.
since we allocate 4 bit for MoS type in all three type of segments we defined in this document.

Section 3.2.2, I agree with the editor's note that additional
information on the sub stream id field is needed.

[Qin]: I think the movtiation to define Sub stream identifier is to identify each layer using SSID from base layer, 
enhancement layer 1, enhancement layer 2, etc since SSRC is not sufficient to identify each of them when they 
share the same SSRC.

Maybe we can directly assign each layer with the integer value from 0 to n using the following mapping:
SSID     SSID description
 0           base layer
1            enhancement layer 1
2            enhancement layer 2
...............
n            enhancement layer n


Section 3.2.3, it is not clear to me how the Channel identifier will be
used. With 4 bits, you can identify the channel, but how do you express
how many channels there are. For example, don't you need to be able to
say, this is channel 2 of 5, or 1 or 2, etc.? Is the assumption that you
will always have a segment for each channel; therefore, the number of
channels is always defined implicitly by the number of channel segments?

[Qin]: That's a good question.
I think the number of channel should be indicated in SDP signaling to each associated RTP payload type.
One example is RFC3640 "RTP Payload Format for Transport of MPEG-4 Elementary Streams"
Please see the section 3.3.1 of RFC3640
"
3.3.  Usage of this Specification

3.3.1.  General


The general form of an rtpmap attribute is:

   a=rtpmap:<payload type> <encoding name>/<clock rate>[/<encoding
             parameters>]

   For audio streams, <encoding parameters> specifies the number of
   audio channels: 2 for stereo material (see RFC 2327 [5]) and 1 for
   mono.
"
.

As a general comment, I too would like to hear comments from those who
are doing application MoS calculations.

Cheers,
Charles

> -----Original Message-----
> From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On
> Behalf Of Qin Wu
> Sent: Friday, December 30, 2011 7:53 PM
> To: xrblock@ietf.org
> Subject: [xrblock] Fw: I-D Action:draft-wu-xrblock-rtcp-xr-quality-
> monitoring-08.txt
> 
> One more update to QoE metric reporting draft.
>  http://www.ietf.org/internet-drafts/draft-wu-xrblock-rtcp-xr-quality-
> monitoring-08.txt
> 
> This draft defines three segment type to support the following three
> different cases:
> 1. multimedia session where each type of media are sent in a separate
>    RTP stream or the layered video session where each layer video are
> sent in a separate RTP
>    stream.
> 2. the layered video session where multi-layer video are carried in
the
> same RTP stream
> 3. the multi-channel audio session where multi-channel voice data are
> carried in the same RTP stream
> 
> Comparing with the first case, the second and third cases more focus
on
> application specific MoS value reporting
> and but deal with the situation where the case 1 canot  deal with.
> 
> Comments and suggestions are welcome. It will be good to also hear the
> opinion from people
> who are doing VOIP application MoS calculation.
> 
> Regards!
> -Qin
> ----- Original Message -----
> From: <internet-drafts@ietf.org>
> To: <i-d-announce@ietf.org>
> Sent: Saturday, December 31, 2011 11:38 AM
> Subject: I-D Action:
draft-wu-xrblock-rtcp-xr-quality-monitoring-08.txt
> 
> 
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >
> > Title           : RTCP XR Blocks for QoE metric reporting
> > Author(s)       : Geoff Hunt
> >                          Alan Clark
> >                          Qin Wu
> >                          Roland Schott
> >                          Glen Zorn
> > Filename        : draft-wu-xrblock-rtcp-xr-quality-monitoring-08.txt
> > Pages           : 18
> > Date            : 2011-12-30
> >
> >   This document defines an RTCP XR Report Block and associated SDP
> >   parameters that allow the reporting of QoE metrics for use in a
> range
> >   of RTP applications.
> >
> >
> > A URL for this Internet-Draft is:
> >
http://www.ietf.org/internet-drafts/draft-wu-xrblock-rtcp-xr-quality-
> monitoring-08.txt
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > This Internet-Draft can be retrieved at:
> > ftp://ftp.ietf.org/internet-drafts/draft-wu-xrblock-rtcp-xr-quality-
> monitoring-08.txt
> >
> > _______________________________________________
> > I-D-Announce mailing list
> > I-D-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > Internet-Draft directories: http://www.ietf.org/shadow.html
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock

From vsingh.ietf@gmail.com  Wed Jan 11 04:09:54 2012
Return-Path: <vsingh.ietf@gmail.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73D5A21F8319 for <xrblock@ietfa.amsl.com>; Wed, 11 Jan 2012 04:09:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MEiqyECA6Ait for <xrblock@ietfa.amsl.com>; Wed, 11 Jan 2012 04:09:53 -0800 (PST)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2E1A121F8531 for <xrblock@ietf.org>; Wed, 11 Jan 2012 04:09:52 -0800 (PST)
Received: by bkwq16 with SMTP id q16so553447bkw.31 for <xrblock@ietf.org>; Wed, 11 Jan 2012 04:09:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; bh=8E3VncdXpNy0Ex+zmCH+XI9q3JCgUEbpAWFP9+zyt5s=; b=iDvP/fE9x6Zmfqewed2g4dnQXr9712kbQqLaB3pyx33/RbWVhKE5XfNxfOfwJQ9J7p xHztt1svZzYwoGhXbCQ1E/MvLrVajvnv4SH+RhTVhy/kbou6grD18rlelVCftaG+iwMv fkFqBDISCz3FcE0w1SNUpG3zB9H+CBwQ0Dboo=
Received: by 10.204.152.219 with SMTP id h27mr9673529bkw.75.1326283776756; Wed, 11 Jan 2012 04:09:36 -0800 (PST)
MIME-Version: 1.0
Received: by 10.205.121.10 with HTTP; Wed, 11 Jan 2012 04:09:15 -0800 (PST)
From: Varun Singh <vsingh.ietf@gmail.com>
Date: Wed, 11 Jan 2012 14:09:15 +0200
Message-ID: <CAEbPqrz05RAbaq7sNb+W09pZSJedn=iEW2Sf_BR3mRho5c=Tdg@mail.gmail.com>
To: xrblock@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [xrblock] Upcoming changes in draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jan 2012 12:09:54 -0000

Hi,

I am sending the updates to mailing list so that the discussion can
take place before I post an updated draft.

in -01, Section 1. Last para of introduction:
   Complementary to or instead of the indication which packets were
   discarded, an XR block is defined to indicate the number of bytes
   discarded, per interval or for the duration of the session, similar
   to other XR report blocks.

Adding to that para in -02:
   Alternatively, if the sender keeps a
   history of the size of the packets reported in the measurement
   interval then the sender can calculate the number of bytes discarded
   from the information in the discard RLE block.

- is this extra clarification needed?

in -01, end of section 4.:
   The 'number of bytes discarded' is a 32-bit unsigned integer value
   indicating the total number of bytes discarded (I=11), or the number
   of bytes discarded since the last RTCP XR Bytes Discarded block was
   sent (I=10), or bytes discarded in a measurement interval (I=01)
   [I-D.ietf-xrblock-rtcp-xr-meas-identity].

   Bytes Discarded Report Blocks SHOULD be sent in conjunction with an
   RTCP RR as a compound RTCP packet.

Updated it to:
   The 'number of bytes discarded' is a 32-bit unsigned integer value
   indicating the total number of bytes discarded.  If the XR block is
   not preceded by a measurement identity block
   [I-D.ietf-xrblock-rtcp-xr-meas-identity] then the value indicates the
   bytes lost from from the start of the session (I=11), or the number
   of bytes discarded since the last RTCP XR Bytes Discarded block was
   received (I=10).

   If the XR block follows a measurement identity block
   [I-D.ietf-xrblock-rtcp-xr-meas-identity] in an RTCP RR packet then
   the cumulative (I=11) and interval (I=10) correspond to the values in
   the measurement block.

   Bytes Discarded Report Blocks SHOULD be sent in conjunction with an
   RTCP RR as a compound RTCP packet.

- clarified what the sender could do if the measurement interval is
absent/present in the RTCP packet.
Note at the moment there are no normative keywords in the text.

Possible clarification that can be added to the first para:
When the measurement block is absent, the sender SHOULD calculate the
duration of the interval using the RTP timestamps of the last reported
HSN and current HSN. If an RTCP RR packet is lost in between then the
assumption is wrong and the receiver SHOULD use the measurement block
for indicating precise durations.


Cheers,
Varun

-- 
http://www.netlab.tkk.fi/~varun/

From eckelcu@cisco.com  Wed Jan 11 10:50:35 2012
Return-Path: <eckelcu@cisco.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3346611E807A for <xrblock@ietfa.amsl.com>; Wed, 11 Jan 2012 10:50:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.399
X-Spam-Level: 
X-Spam-Status: No, score=-6.399 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9RplME0xQvac for <xrblock@ietfa.amsl.com>; Wed, 11 Jan 2012 10:50:34 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 8DE5511E8073 for <xrblock@ietf.org>; Wed, 11 Jan 2012 10:50:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=7036; q=dns/txt; s=iport; t=1326307833; x=1327517433; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=RB8NhEWIXINXjC/09tFHFkpNENaMLaVzp4QPF+bw02A=; b=NA2VtKXFyoc8Q0R+qXtOw1EUtiAyw+ix2jOJjt85zFrE7ry/n1dXQ7Ko Ktmoc4yMSPmMMB4Qe2Fi13hllxsToOpYzL38gmLFMrmbAJrNHnZUWS2N1 PocUvH1O3tDUC07SeyQAjIUxJ3j/8ylp1Rpowb810tComxm7k9BRCLt5e 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqUAANbYDU+rRDoI/2dsb2JhbAA5CpxDkEOBBYFyAQEBAwEBAQEPAR0KLQcQBwQCAQgOAwQBAQsGFwEGASYfCQgBAQQBEggBGYdYCJkPAZ5GiGCCWmMEiDqXS4dk
X-IronPort-AV: E=Sophos;i="4.71,494,1320624000"; d="scan'208";a="24772192"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 11 Jan 2012 18:50:33 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q0BIoW58001719; Wed, 11 Jan 2012 18:50:33 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 11 Jan 2012 10:50:32 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 11 Jan 2012 10:50:32 -0800
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C061CB40C@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <59256B09E4E044F690F331D509000F8F@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [xrblock] Fw: I-D Action:draft-wu-xrblock-rtcp-xr-quality-monitoring-08.txt
Thread-Index: AczPVapvMP6wXRIpRpS4KNaVR9o7AwBOtX5w
References: <72811F84379848C1A4BD21CCFFAE4FDB@china.huawei.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C061CAE5D@xmb-sjc-234.amer.cisco.com> <59256B09E4E044F690F331D509000F8F@china.huawei.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Qin Wu" <bill.wu@huawei.com>, <xrblock@ietf.org>
X-OriginalArrivalTime: 11 Jan 2012 18:50:32.0902 (UTC) FILETIME=[E5AC6E60:01CCD091]
Subject: Re: [xrblock] Fw: I-D Action:draft-wu-xrblock-rtcp-xr-quality-monitoring-08.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jan 2012 18:50:35 -0000

One more comment inline.

> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]
> Sent: Monday, January 09, 2012 9:06 PM
> To: Charles Eckel (eckelcu); xrblock@ietf.org
> Subject: Re: [xrblock] Fw: I-D
Action:draft-wu-xrblock-rtcp-xr-quality-
> monitoring-08.txt
>=20
> Hi, Charles:
> Thank for your detailed review, please see my replies inline.
> ----- Original Message -----
> From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <xrblock@ietf.org>
> Sent: Tuesday, January 10, 2012 7:44 AM
> Subject: RE: [xrblock] Fw: I-D
Action:draft-wu-xrblock-rtcp-xr-quality-
> monitoring-08.txt
>=20
>=20
> (As an individual)
>=20
> Hi Qin,
>=20
> I read the draft and have the following comments:
>=20
> Section 3.2.1-3, the descriptions of segment type, media type, and MoS
> type are not consistent. Section 3.2.1 is missing the media type, and
> the length of the MoS type field is not consistent.
>=20
> [Qin]: Unlike Multi-layer per SSRC segment and Multi-Channel per SSRC
> segment,
> single stream per SSRC segment applies to all the media types or all
> the applications.
> Thefore in the format of single stream per SSRC segment, we don't
> allocate one bit to
> distinguish between different media type.
>=20
> As for the length of the MoS type field,  I am not sure I catch your
> comment.
> since we allocate 4 bit for MoS type in all three type of segments we
> defined in this document.

I was assuming the intent was for the segment structures defined in
sections 3.2.1 - 3.2.3 to share the same exact format for the fields up
to and including the CAlg field. =20
This could be achieved by allocating space for the Media Type field for
the single stream per SSC segment even though would not be used.

Cheers,
Charles
=20
> Section 3.2.2, I agree with the editor's note that additional
> information on the sub stream id field is needed.
>
> [Qin]: I think the movtiation to define Sub stream identifier is to
> identify each layer using SSID from base layer,
> enhancement layer 1, enhancement layer 2, etc since SSRC is not
> sufficient to identify each of them when they
> share the same SSRC.
>=20
> Maybe we can directly assign each layer with the integer value from 0
> to n using the following mapping:
> SSID     SSID description
>  0           base layer
> 1            enhancement layer 1
> 2            enhancement layer 2
> ...............
> n            enhancement layer n
>=20
>=20
> Section 3.2.3, it is not clear to me how the Channel identifier will
be
> used. With 4 bits, you can identify the channel, but how do you
express
> how many channels there are. For example, don't you need to be able to
> say, this is channel 2 of 5, or 1 or 2, etc.? Is the assumption that
> you
> will always have a segment for each channel; therefore, the number of
> channels is always defined implicitly by the number of channel
> segments?
>=20
> [Qin]: That's a good question.
> I think the number of channel should be indicated in SDP signaling to
> each associated RTP payload type.
> One example is RFC3640 "RTP Payload Format for Transport of MPEG-4
> Elementary Streams"
> Please see the section 3.3.1 of RFC3640
> "
> 3.3.  Usage of this Specification
>=20
> 3.3.1.  General
>=20
>=20
> The general form of an rtpmap attribute is:
>=20
>    a=3Drtpmap:<payload type> <encoding name>/<clock rate>[/<encoding
>              parameters>]
>=20
>    For audio streams, <encoding parameters> specifies the number of
>    audio channels: 2 for stereo material (see RFC 2327 [5]) and 1 for
>    mono.
> "
> .
>=20
> As a general comment, I too would like to hear comments from those who
> are doing application MoS calculations.
>=20
> Cheers,
> Charles
>=20
> > -----Original Message-----
> > From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On
> > Behalf Of Qin Wu
> > Sent: Friday, December 30, 2011 7:53 PM
> > To: xrblock@ietf.org
> > Subject: [xrblock] Fw: I-D Action:draft-wu-xrblock-rtcp-xr-quality-
> > monitoring-08.txt
> >
> > One more update to QoE metric reporting draft.
> >  http://www.ietf.org/internet-drafts/draft-wu-xrblock-rtcp-xr-
> quality-
> > monitoring-08.txt
> >
> > This draft defines three segment type to support the following three
> > different cases:
> > 1. multimedia session where each type of media are sent in a
separate
> >    RTP stream or the layered video session where each layer video
are
> > sent in a separate RTP
> >    stream.
> > 2. the layered video session where multi-layer video are carried in
> the
> > same RTP stream
> > 3. the multi-channel audio session where multi-channel voice data
are
> > carried in the same RTP stream
> >
> > Comparing with the first case, the second and third cases more focus
> on
> > application specific MoS value reporting
> > and but deal with the situation where the case 1 canot  deal with.
> >
> > Comments and suggestions are welcome. It will be good to also hear
> the
> > opinion from people
> > who are doing VOIP application MoS calculation.
> >
> > Regards!
> > -Qin
> > ----- Original Message -----
> > From: <internet-drafts@ietf.org>
> > To: <i-d-announce@ietf.org>
> > Sent: Saturday, December 31, 2011 11:38 AM
> > Subject: I-D Action:
> draft-wu-xrblock-rtcp-xr-quality-monitoring-08.txt
> >
> >
> > >
> > > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> > >
> > > Title           : RTCP XR Blocks for QoE metric reporting
> > > Author(s)       : Geoff Hunt
> > >                          Alan Clark
> > >                          Qin Wu
> > >                          Roland Schott
> > >                          Glen Zorn
> > > Filename        : draft-wu-xrblock-rtcp-xr-quality-monitoring-
> 08.txt
> > > Pages           : 18
> > > Date            : 2011-12-30
> > >
> > >   This document defines an RTCP XR Report Block and associated SDP
> > >   parameters that allow the reporting of QoE metrics for use in a
> > range
> > >   of RTP applications.
> > >
> > >
> > > A URL for this Internet-Draft is:
> > >
> http://www.ietf.org/internet-drafts/draft-wu-xrblock-rtcp-xr-quality-
> > monitoring-08.txt
> > >
> > > Internet-Drafts are also available by anonymous FTP at:
> > > ftp://ftp.ietf.org/internet-drafts/
> > >
> > > This Internet-Draft can be retrieved at:
> > > ftp://ftp.ietf.org/internet-drafts/draft-wu-xrblock-rtcp-xr-
> quality-
> > monitoring-08.txt
> > >
> > > _______________________________________________
> > > I-D-Announce mailing list
> > > I-D-Announce@ietf.org
> > > https://www.ietf.org/mailman/listinfo/i-d-announce
> > > Internet-Draft directories: http://www.ietf.org/shadow.html
> > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> > _______________________________________________
> > xrblock mailing list
> > xrblock@ietf.org
> > https://www.ietf.org/mailman/listinfo/xrblock

From bill.wu@huawei.com  Wed Jan 11 18:05:16 2012
Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A22E01F0C38 for <xrblock@ietfa.amsl.com>; Wed, 11 Jan 2012 18:05:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.089
X-Spam-Level: 
X-Spam-Status: No, score=-6.089 tagged_above=-999 required=5 tests=[AWL=0.510,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pvSUbT0YH8rr for <xrblock@ietfa.amsl.com>; Wed, 11 Jan 2012 18:05:15 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 6E5E721F858D for <xrblock@ietf.org>; Wed, 11 Jan 2012 18:05:15 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LXN00HAWXSB63@szxga03-in.huawei.com> for xrblock@ietf.org; Thu, 12 Jan 2012 10:04:59 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LXN00FYFXSAY9@szxga03-in.huawei.com> for xrblock@ietf.org; Thu, 12 Jan 2012 10:04:58 +0800 (CST)
Received: from szxeml205-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGG42655; Thu, 12 Jan 2012 10:04:56 +0800
Received: from SZXEML409-HUB.china.huawei.com (10.82.67.136) by szxeml205-edg.china.huawei.com (172.24.2.57) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 12 Jan 2012 10:04:49 +0800
Received: from w53375q (10.138.41.130) by szxeml409-hub.china.huawei.com (10.82.67.136) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 12 Jan 2012 10:04:48 +0800
Date: Thu, 12 Jan 2012 10:04:47 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, xrblock@ietf.org
Message-id: <D958174CA04F4B43845EB939947A705C@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <72811F84379848C1A4BD21CCFFAE4FDB@china.huawei.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C061CAE5D@xmb-sjc-234.amer.cisco.com> <59256B09E4E044F690F331D509000F8F@china.huawei.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C061CB40C@xmb-sjc-234.amer.cisco.com>
Subject: Re: [xrblock] Fw: I-DAction:draft-wu-xrblock-rtcp-xr-quality-monitoring-08.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jan 2012 02:05:16 -0000

Hi,
----- Original Message ----- 
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Qin Wu" <bill.wu@huawei.com>; <xrblock@ietf.org>
Sent: Thursday, January 12, 2012 2:50 AM
Subject: Re: [xrblock] Fw: I-DAction:draft-wu-xrblock-rtcp-xr-quality-monitoring-08.txt


> One more comment inline.
> 
>> -----Original Message-----
>> From: Qin Wu [mailto:bill.wu@huawei.com]
>> Sent: Monday, January 09, 2012 9:06 PM
>> To: Charles Eckel (eckelcu); xrblock@ietf.org
>> Subject: Re: [xrblock] Fw: I-D
> Action:draft-wu-xrblock-rtcp-xr-quality-
>> monitoring-08.txt
>> 
>> Hi, Charles:
>> Thank for your detailed review, please see my replies inline.
>> ----- Original Message -----
>> From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
>> To: "Qin Wu" <bill.wu@huawei.com>; <xrblock@ietf.org>
>> Sent: Tuesday, January 10, 2012 7:44 AM
>> Subject: RE: [xrblock] Fw: I-D
> Action:draft-wu-xrblock-rtcp-xr-quality-
>> monitoring-08.txt
>> 
>> 
>> (As an individual)
>> 
>> Hi Qin,
>> 
>> I read the draft and have the following comments:
>> 
>> Section 3.2.1-3, the descriptions of segment type, media type, and MoS
>> type are not consistent. Section 3.2.1 is missing the media type, and
>> the length of the MoS type field is not consistent.
>> 
>> [Qin]: Unlike Multi-layer per SSRC segment and Multi-Channel per SSRC
>> segment,
>> single stream per SSRC segment applies to all the media types or all
>> the applications.
>> Thefore in the format of single stream per SSRC segment, we don't
>> allocate one bit to
>> distinguish between different media type.
>> 
>> As for the length of the MoS type field,  I am not sure I catch your
>> comment.
>> since we allocate 4 bit for MoS type in all three type of segments we
>> defined in this document.
> 
> I was assuming the intent was for the segment structures defined in
> sections 3.2.1 - 3.2.3 to share the same exact format for the fields up
> to and including the CAlg field.  

[Qin]: That is a good point if we need to include single stream per SSRC segment
with other segment types using the common format in the same draft. But these different 
segment type will not be present in the same XR Block since they deal with different use case
and has distinct usage.

> This could be achieved by allocating space for the Media Type field for
> the single stream per SSC segment even though would not be used.

[Qin]: I like this proposal if we agree one draft is sufficient to 
address the single milestones.

> Cheers,
> Charles
> 
>> Section 3.2.2, I agree with the editor's note that additional
>> information on the sub stream id field is needed.
>>
>> [Qin]: I think the movtiation to define Sub stream identifier is to
>> identify each layer using SSID from base layer,
>> enhancement layer 1, enhancement layer 2, etc since SSRC is not
>> sufficient to identify each of them when they
>> share the same SSRC.
>> 
>> Maybe we can directly assign each layer with the integer value from 0
>> to n using the following mapping:
>> SSID     SSID description
>>  0           base layer
>> 1            enhancement layer 1
>> 2            enhancement layer 2
>> ...............
>> n            enhancement layer n
>> 
>> 
>> Section 3.2.3, it is not clear to me how the Channel identifier will
> be
>> used. With 4 bits, you can identify the channel, but how do you
> express
>> how many channels there are. For example, don't you need to be able to
>> say, this is channel 2 of 5, or 1 or 2, etc.? Is the assumption that
>> you
>> will always have a segment for each channel; therefore, the number of
>> channels is always defined implicitly by the number of channel
>> segments?
>> 
>> [Qin]: That's a good question.
>> I think the number of channel should be indicated in SDP signaling to
>> each associated RTP payload type.
>> One example is RFC3640 "RTP Payload Format for Transport of MPEG-4
>> Elementary Streams"
>> Please see the section 3.3.1 of RFC3640
>> "
>> 3.3.  Usage of this Specification
>> 
>> 3.3.1.  General
>> 
>> 
>> The general form of an rtpmap attribute is:
>> 
>>    a=rtpmap:<payload type> <encoding name>/<clock rate>[/<encoding
>>              parameters>]
>> 
>>    For audio streams, <encoding parameters> specifies the number of
>>    audio channels: 2 for stereo material (see RFC 2327 [5]) and 1 for
>>    mono.
>> "
>> .
>> 
>> As a general comment, I too would like to hear comments from those who
>> are doing application MoS calculations.
>> 
>> Cheers,
>> Charles
>> 
>> > -----Original Message-----
>> > From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On
>> > Behalf Of Qin Wu
>> > Sent: Friday, December 30, 2011 7:53 PM
>> > To: xrblock@ietf.org
>> > Subject: [xrblock] Fw: I-D Action:draft-wu-xrblock-rtcp-xr-quality-
>> > monitoring-08.txt
>> >
>> > One more update to QoE metric reporting draft.
>> >  http://www.ietf.org/internet-drafts/draft-wu-xrblock-rtcp-xr-
>> quality-
>> > monitoring-08.txt
>> >
>> > This draft defines three segment type to support the following three
>> > different cases:
>> > 1. multimedia session where each type of media are sent in a
> separate
>> >    RTP stream or the layered video session where each layer video
> are
>> > sent in a separate RTP
>> >    stream.
>> > 2. the layered video session where multi-layer video are carried in
>> the
>> > same RTP stream
>> > 3. the multi-channel audio session where multi-channel voice data
> are
>> > carried in the same RTP stream
>> >
>> > Comparing with the first case, the second and third cases more focus
>> on
>> > application specific MoS value reporting
>> > and but deal with the situation where the case 1 canot  deal with.
>> >
>> > Comments and suggestions are welcome. It will be good to also hear
>> the
>> > opinion from people
>> > who are doing VOIP application MoS calculation.
>> >
>> > Regards!
>> > -Qin
>> > ----- Original Message -----
>> > From: <internet-drafts@ietf.org>
>> > To: <i-d-announce@ietf.org>
>> > Sent: Saturday, December 31, 2011 11:38 AM
>> > Subject: I-D Action:
>> draft-wu-xrblock-rtcp-xr-quality-monitoring-08.txt
>> >
>> >
>> > >
>> > > A New Internet-Draft is available from the on-line Internet-Drafts
>> > directories.
>> > >
>> > > Title           : RTCP XR Blocks for QoE metric reporting
>> > > Author(s)       : Geoff Hunt
>> > >                          Alan Clark
>> > >                          Qin Wu
>> > >                          Roland Schott
>> > >                          Glen Zorn
>> > > Filename        : draft-wu-xrblock-rtcp-xr-quality-monitoring-
>> 08.txt
>> > > Pages           : 18
>> > > Date            : 2011-12-30
>> > >
>> > >   This document defines an RTCP XR Report Block and associated SDP
>> > >   parameters that allow the reporting of QoE metrics for use in a
>> > range
>> > >   of RTP applications.
>> > >
>> > >
>> > > A URL for this Internet-Draft is:
>> > >
>> http://www.ietf.org/internet-drafts/draft-wu-xrblock-rtcp-xr-quality-
>> > monitoring-08.txt
>> > >
>> > > Internet-Drafts are also available by anonymous FTP at:
>> > > ftp://ftp.ietf.org/internet-drafts/
>> > >
>> > > This Internet-Draft can be retrieved at:
>> > > ftp://ftp.ietf.org/internet-drafts/draft-wu-xrblock-rtcp-xr-
>> quality-
>> > monitoring-08.txt
>> > >
>> > > _______________________________________________
>> > > I-D-Announce mailing list
>> > > I-D-Announce@ietf.org
>> > > https://www.ietf.org/mailman/listinfo/i-d-announce
>> > > Internet-Draft directories: http://www.ietf.org/shadow.html
>> > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>> > _______________________________________________
>> > xrblock mailing list
>> > xrblock@ietf.org
>> > https://www.ietf.org/mailman/listinfo/xrblock
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock
>

From bill.wu@huawei.com  Wed Jan 11 19:10:48 2012
Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAC2F21F85E9 for <xrblock@ietfa.amsl.com>; Wed, 11 Jan 2012 19:10:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.373
X-Spam-Level: 
X-Spam-Status: No, score=-5.373 tagged_above=-999 required=5 tests=[AWL=-0.259, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, J_CHICKENPOX_46=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sABtIX5ntVwJ for <xrblock@ietfa.amsl.com>; Wed, 11 Jan 2012 19:10:47 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id DCB7D21F8531 for <xrblock@ietf.org>; Wed, 11 Jan 2012 19:10:46 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LXO002VN0TOP2@szxga05-in.huawei.com> for xrblock@ietf.org; Thu, 12 Jan 2012 11:10:36 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LXO00D590TOKD@szxga05-in.huawei.com> for xrblock@ietf.org; Thu, 12 Jan 2012 11:10:36 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGJ79285; Thu, 12 Jan 2012 11:10:29 +0800
Received: from SZXEML415-HUB.china.huawei.com (10.82.67.154) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 12 Jan 2012 11:10:21 +0800
Received: from w53375q (10.138.41.130) by szxeml415-hub.china.huawei.com (10.82.67.154) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 12 Jan 2012 11:10:22 +0800
Date: Thu, 12 Jan 2012 11:10:21 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: zhangyx@sttri.com.cn, xrblock <xrblock@ietf.org>
Message-id: <2357BBAA4B31411C8872DB1BDBE0E4AA@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: multipart/alternative; boundary="Boundary_(ID_PhFt9tw4VPROen1kYV1K4w)"
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <3443917.11991324352385354.JavaMail.root@ent12>
Subject: Re: [xrblock] (Bursts and Gaps) Open issue 2: potential metrics blockextension
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jan 2012 03:10:48 -0000

--Boundary_(ID_PhFt9tw4VPROen1kYV1K4w)
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: base64

SGksDQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KPkZyb206IHpoYW5neXhAc3R0cmku
Y29tLmNuIA0KPlRvOiB4cmJsb2NrIA0KPlNlbnQ6IFR1ZXNkYXksIERlY2VtYmVyIDIwLCAyMDEx
IDExOjM5IEFNDQo+U3ViamVjdDogW3hyYmxvY2tdIChCdXJzdHMgYW5kIEdhcHMpIE9wZW4gaXNz
dWUgMjogcG90ZW50aWFsIG1ldHJpY3MgYmxvY2tleHRlbnNpb24NCg0KDQo+SGksIGZvbGtzOiAN
Cj5Gb2xsb3dpbmcgdGhlIG1haWxpbmcgbGlzdCBkaXNjdXNzaW9uIHJlZ2FyZGluZyB3aGV0aGVy
IHBvdGVudGlhbCBtZXRyaWNzIGlzIG5lZWRlZCBpbiB0aGUgQnVyc3RzIGFuZCBHYXBzIGRyYWZ0
cyANCj5odHRwOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIveHJibG9jay9jdXJyZW50
L21zZzAwMTM5Lmh0bWwgDQo+V2UgaGF2ZSBicmllZmx5IGRpc2N1c3NlZCB0aGVzZSBwb3RlbnRp
YWwgbWV0cmljcyB0aGF0IGNvdWxkIGJlIGFkZGVkIHRvIGJ1cnN0IGdhcCBtZXRyaWNzLCBwcm9w
b3NlZCBieSBBbGFuIGluIHRoZSBUYWlwZWkgbWVldGluZy4gDQo+VW5mb3J0dW50ZWx5IHRoaXMg
aXNzdWUgaGFkbid0IGJlZW4gY29uY2x1ZGVkIGluIHRoZSBJRVRGIDgyIG1lZXRpbmcuIA0KIA0K
PkZvciB0aGUgd2F5IGZvcndhcmQgdG8gYnVyc3QgZ2FwIGRpc2NhcmQgZHJhZnQgYW5kIGJ1cnN0
IGdhcCBsb3NzIGRyYWZ0LCB3ZSBsaWtlIHRvIGRpc2N1c3MgdGhlIHJlbGF0aW9uIGJldHdlZW4g
DQo+dGhlc2UgcG90ZW50aWFsIGV4dGVuc2lvbiBhbmQgYnVyc3QgZ2FwIGRyYWZ0cyBhbmQgZGVj
aWRlIHdoaWNoIHNob3VsZCBiZSBpbmNsdWRlZCBhbmQgd2hpY2ggbm90LiANCiANCj5hLiBNYXgg
YnVyc3QgbGVuZ3RoDQo+SW4gdGhlIG1lZXRpbmcsIHdlIHdlcmUgYXNrZWQgdG8gY2xhcmlmeSBy
dW4tbGVuZ3RoIGJlIHVzZWQgZm9yIGNhbGN1bGF0aW5nIG1heCBidXJzdC4gQWZ0ZXIgcmVhZGlu
ZyBkcmFmdC1pZXRmLXhyYmxvY2stcnRjcC14ci1kaXNjYXJkLXJsZS1tZXRyaWNzLCANCj53ZSBh
cmUgYXdhcmUgdGhhdCB0aGUgZGlmZmVyZW5jZSBiZXR3ZWVuIHJsZSBkaXNjYXJkIGFuZCBidXJz
dCBnYXAgZGlzY2FyZCBoYXMgYmVlbiB3ZWxsIGNsYXJpZmllZCBpbiB0aGUgaW50cm9kdWN0aW9u
IHNlY3Rpb24gb2YgZHJhZnQtaWV0Zi14cmJsb2NrLXJ0Y3AteHItZGlzY2FyZC1ybGUtbWV0cmlj
cy4gDQo+QWxzbyB3ZSBiZWxpZXZlIHJ1biBsZW5ndGggZW5jb2RpbmcgZGlzY2FyZCBpcyBvbmUg
d2F5IHRvIGNhbGN1YWx0ZSBtYXggYnVyc3QgbGVuZ3RoLiANCiANCj5JbiB0aGUgYnVyc3QgZ2Fw
IGRpc2NhcmQgZHJhZnQsIGlmIHRoZXJlIGFyZSA0IGJ1cnN0IGFuZCA1IGdhcHMsICBidXJzdCBn
YXAgZGlzY2FyZCBtZXRyaWMgYmxvY2sgY2FuIGJlIHVzZWQgdG8gcmVwb3J0IHN1bSBvZiBidXJz
dCBkdXJhdGlvbnMgYW5kIHNxdWFyZXMgb2YgYnVyc3QgZHVyYXRpb25zLiBIb3dldmVyIA0KPkhv
d2V2ZXIgbm9uZSBvZiB0aGVzZSBtZXRyaWNzIGFyZSB1c2VkIHRvIHJlcG9ydCBNYXggYnVyc3Qg
bGVuZ3RoLiBJdCBpcyB0cnVlIHRoYXQgTWF4IGJ1cnN0IGxlbmd0aCByZXByZXNlbnRzIHRoZSDi
gJx3b3JzdOKAnSBwZXJpb2QgZnJvbSBhIFFvRSBwZXJzcGVjdGl2ZSAsSG93ZXZlciBJIHRoaW5r
IE1heCBidXJzdCBsZW5naCBzaG91bGQgbm90IGJlID5wYXJ0IG9mIGJ1cnN0IGdhcCBkaXNjYXJk
IG1ldHJpYyBibG9jayBvciBidXJzdCBnYXAgbG9zcyBtZXRyaWMgYmxvY2suIFNpbmNlIHdlIHVz
ZSB0aHJlc2hvbGQgdG8gZGl2aWRlIFJUUCBzdHJlYW0gaW50byBnYXAgYW5kIGJ1cnN0LiBBbGwg
dGhlIG90aGVyIG1ldHJpYyB3ZSBpbmNsdWRlIGluIHRoZSBidXJzdCBnYXAgZGlzY2FyZCBhbmQg
YnVyc3QgZ2FwID5sb3NzIGFyZSB1c2VkIHRvIGNhbGN1bGF0ZSBidXJzdCBsb3NzIHJhdGUsIGdh
cCBsb3NzIHJhdGUsIGJ1cnN0IGRpc2NhcmQgcmF0ZSwgZ2FwIGRpc2NhcmQgcmF0ZSwgYnVyc3Qg
ZHVyYXRpb24gbWVhbiwgYnVyc3QgZHVyYXRpb24gZGV2LiBVc2UgYnVyc3QgZHJ1YXRpb24gbWVh
biBhbmQgYnVyc3QgZHVyYXRpb24gZGV2LCB3ZSBjYW4gaW5kaWNhdGUgPmVzdGltYXRlIA0KPmhv
dyBsYXJnZSB0aGUgbWF4IGJ1cnN0IGxlbmd0aCBpcy4gU28gTWF4IGJ1cnN0IGxlbmd0aCBpcyBu
b3QgbmVlZGVkIGluIHRoZSBidXJzdCBnYXAgZHJhZnRzLiANCg0KW1Fpbl06IEkgYWdyZWUgTUFY
IGJ1cnN0IGxlbmdoIGNhbiBiZSByb3VnaGx5IGVzdGltYXRlZCB1c2luZyBidXJzdCBkdXJhdGlv
biBtZWFuIGFuZCBkZXZpYXRpb24uIEJ1dCBpZiB3ZSBsb29rIGZvciBtb3JlIHByZWNpc2UgbWVh
c3VyZW1lbnQgZm9yIE1heCBidXJzdCBsZW5ndGgsIHdlIHNob3VsZCByZWx5IG9uIExvc3MgUkxF
IHJlcG9ydA0KYW5kIER1cGxpY2F0aW9uIFJMRSByZXBvcnQgYW5kIERpc2NhcmQgUkxFIHJlcG9y
dC4gSSBhbSBub3Qgc3VyZSB3ZSBjYW4gY2FsY3VsYXRlIE1heCBidXJzdCBkdXJhdGlvbiAgc2lt
cGx5IGJhc2VkIG9uIERpc2NhcmQgUkxFIHJlcG9ydC4NCkJ1dCB5b3UgYXJlIHJpZ2h0LCBzaW5j
ZSB3ZSBoYXZlIG1hbnkgd2F5cyhkaXJlY3Qgd2F5IG9yIGluZGlyZWN0IHdheSApIHRvIG1lYXN1
cmUgTWF4IGJ1cnN0IGxlbmd0aCwgSSBhZ3JlZSBpdCBhZGQgY29tcGxleGl0eSB0byBCdXJzdCBn
YXAgZGlzY2FyZCBkcmFmdCBpZiBhZGRpbmcgdGhpcyBtZXRyaWMgaW50byBidXJzdCBnYXAgZGlz
Y2FyZCBkcmFmdC4NCg0KPmIuIEF2ZXJhZ2UgYnVyc3QgDQo+SW4gdGhlIG1lZXRpbmcsIHdlIHdl
cmUgYWxzbyBhc2tlZCB0byBjbGFyaWZ5IHdoZXRoZXIgdGhlcmUgaXMgYSBuZWVkIHRvIGFkZCBh
dmVyYWdlIGJ1cnN0LiBPdXIgYW5zd2VyIGlzIG5vLCBhcyB3ZSBleHBsYWluZWQgIGluIHRoZSAo
YSksIHRoZSBtZXRyaWNzIGluY2x1ZGVkIGluIHRoZSBidXJzdCBnYXAgbG9zcyBhbmQgYnVyc3Qg
Z2FwIGRpc2NhcmQgDQogPndpbGwgYmUgZmluYWxseSB1c2VkIHRvIGNhbGN1bGF0ZSBidXJzdCBk
dXJhdGlvbiBtZWFuIGFuZCBidXJzdCBkdXJhdGlvbiB2YXJpYW5jZS4gVGhlcmVmb3JlIEF2ZXJh
Z2UgYnVyc3QgY2FuIGJlIGVzdGltYXRlZCB1c2luZyBidXJzdCBkdXJhdGlvbiBtZWFuLiB3ZSBk
b24ndCBuZWVkIHRvIGFkZCBhdmVyYWdlIGJ1cnN0IGludG8gdGhlIGV4aXN0aW5nID5kcmFmdC1p
ZXRmLXJ0Y3AteHItYnVyc3QtZ2FwLWRpc2NhcmQgYW5kIGRyYWZ0LWlldGYtcnRjcC14ci1idXJz
dC1nYXAtbG9zcywgaW5zdGVhZCwgd2Ugc2hvdWxkIHB1dCBpbnRvIGEgbmV3IHNlcGFyYXRlIG1l
dHJpYyBibG9ja3MuIFRoZXNlIG5ldyBzZXBhcmF0ZSBtZXRyaWMgYmxvY2tzIGhhdmUgYWxyZWFk
eSBiZWVuIGRlZmluZWQgaW4gdGhlID5kcmFmdC16b3JuLXhyYmxvY2stYWwtc3RhdCwgaS5lLiwg
QnVyc3QvR2FwIERpc2NhcmQgU3VtbWFyeSBTdGF0aXN0aWNzIEJsb2NrIGFuZCBCdXJzdC9HYXAg
TG9zcyBTdW1tYXJ5IFN0YXRpc3RpY3MgQmxvY2suIA0KDQpbUWluXTogWWVzLCBkcmFmdC16b3Ju
LXhyYmxvY2stYWwtc3RhdCBzcGVjaWZpZXMgb25lIG5ldyBYUiBCbG9jayxpLmUuLA0KQnVyc3Qv
R2FwIERpc2NhcmQgU3VtbWFyeSBTdGF0aXN0aWNzIEJsb2NrDQpCdXJzdCBkdXJhdGlvbiBNZWFu
ICBjb250YWluZWQgaW4gdGhpcyBYUiBCbG9jayBjYW4gYmUgdXNlZCB0byByZXBvcnQgQXZlcmFn
ZSBidXJzdCBkdXJhdGlvbiB2YWx1ZS4gU28gSSBhZ3JlZSBpdCBpcyByZWR1bmRhbnQgZm9yIGJ1
cnN0IGdhcCBkcmFmdHMgdG8gaW5jbHVkZSBhdmVyYWdlIGJ1cnN0IGludG8gcmVsYXRlZCBYUiBC
bG9jayAuDQogDQo+Yy5UaW1lIFNpbmNlIExhc3QgQnVyc3QgDQo+T24gdGhlIGxpc3QsIEFsYW4g
cHJvcG9zZWQgdG8gYWRkIHRpbWUgc2luY2UgbGFzdCBidXJzdCBpbnRvIGJ1cnN0IGdhcCBkcmFm
dCwgdGhlIHJlYXNvbiBwcm92aWRlZCBieSBoaW0gaXMgaXQgaXMgaGVscGZ1bCB0byBrbm93IHdo
ZW4gdGhlIGxhc3Qgc3Vic3RhbnRpYWwgbG9zcy9kaXNjYXJkIGJ1cnN0IG9jY3VycmVkIHJlbGF0
aXZlIHRvIHRoZSByZXBvcnQgdGltZS4gDQo+V2UgYWdyZWUgaXQgaXMgdXNlZnVsLiBIb3dldmVy
IHdlIHJlYWxpemUgaXQgaXMgbm90IGVhc3kgZm9yIHVzIHRvIGRpcmVjdGx5IG1lYXN1cmUgVGlt
ZSBzaW5jZSBsYXN0IGJ1cnN0IGlmIHdlIHJlbHkgb24gUkxFIGRpc2NhcmQgYW5kIGRvbid0IGtl
ZXAgdHJhY2sgb2YgcGFja2V0cyBzZXF1ZW5jZSBudW1iZXIgIGluIHRoZSBpbnRlcnZhbCANCj5v
bmUgd2F5IHRvIGNhbGN1bGF0ZSB0aGlzIG1ldHJpYyBpcyB0byByZWx5IG9uIHJ1biBsZW5ndGgg
ZW5jb2RpbmcgZGlzY2FyZCBtZXRyaWMgaW4gdGhlIGRyYWZ0LWlldGYteHJibG9jay1ydGNwLXhy
LWRpc2NhcmQtcmxlLW1ldHJpY3MuIE9uIHRoZSBvdGhlciBoYW5kLCB0aGUgZGF0YSB3ZSBjYXJy
aWVkIGluIHRoZSBidXJzdCBnYXAgZHJhZnRzIGFyZSBhbGwgPnVzZWQgdG8gY2FsY3VsYXRlIHN0
YXRpc3RpY3Mgc3VtbWFyeSBvZiBidXJzdCBnYXAsIGhvd2V2ZXIgdGltZSBzaW5jZSBsYXN0IGJ1
cnN0IGlzIG5vdCB1c2VkIHRvIGNhbGN1bGF0ZSBzdGF0aXN0aWNzIHN1bW1hcnkgb2YgYnVyc3Qg
Z2FwLCB0aGVyZWZvcmUgdGltZSBzaW5jZSBsYXN0IGJ1cnN0IGlzIG5vdCBwYXJ0IG9mIGJ1cnN0
IGdhcCBkcmFmdCBhbmQgPnRoZXJlZm9yZSBpcyBub3QgbmVlZGVkLiANCg0KW1Fpbl06IEFnYWlu
LCB5b3UgY2FuIG5vdCBkaXJlY3RseSBtZWFzdXJlIHRoZSBUaW1lIFNpbmNlIGxhc3QgQnVyc3Qg
c2ltcGx5IGJhc2VkIG9uIGRpc2NhcmQgUkxFIHJlcG9ydCwgeW91IGFsc28gbmVlZCB0byBvYnNl
cnZlIGVhY2ggcGFja2V0IGR1cmluZyBtZWFzdXJtZW50IGludGVydmFsLCBpLmUuLCByZWx5aW5n
IG9uIHRoZSBwZXItcGFja2V0IGluZm9ybWF0aW9uIGNvbnRhaW5lZCBpbiBMb3NzIFJMRSwgRHVw
bGljYXRlIFJMRSByZXBvcnQuIGJ1dCBwZXIgcGFja2V0IGluZm9ybWF0aW9uIGRvZXNuJ3QgaW5j
bHVkZSBhbnkgdGltZSByZWxhdGVkIGluZm9ybWF0aW9uLiBXaGF0IHlvdSBjYW4gZG8gaXMgdG8g
bG9jYXRlIHRoZSBmaXJzdCBwYWNrZXQgc3F1ZW5jZSBudW1iZXIgb2YgbGFzdCBidXJzdCwgYW5k
IHRoZW4geW91IGNhbiB1c2Ugc3luY2hyb25pemF0aW9uIGluZm9ybWF0aW9uIGNhcnJpZWQgaW4g
dGhhdCBwYWNrZXQgaGVhZGVyIHRvIHJvdWdobHkgZXN0aW1hdGUgVGltZSBzaW5jZSBMYXN0IEJ1
cnN0LiBJIGFtIG5vdCBzdXJlIHdlIGhhdmUgc3VjaCBhdXRvbWF0aWMgbWVhc3VybWVudCB0b29s
IHRvIHJlcG9ydCBUaW1lIHNpbmNlIExhc3QgQnVyc3QgZGlyZWN0bHkuIElmIG5vLCB0aGVuIGl0
IGlzIHRvbyBtdWNoIGNvbXBsaWNhdGVkIHRvIGNhbGN1bGF0ZSB0aGlzIG1ldHJpYy4gDQogDQo+
VGhlcmVmb3JlIG15IGNvbmNsdXNpb24gaXMgZWFjaCBvZiB0aGVtIGFyZSB2ZXJ5IHVzZWZ1bC4g
SG93ZXZlciBpdCBpcyBub3QgYSBnb29kIGlkZWEgdG8gcHV0IHRoZW0gYWxsIGludG8gYnVyc3Qg
Z2FwIGRyYWZ0cyBzaW5jZSBzb21lIG9mIHRoZW0gY2FuIGJlIGVzdGltYXRlZCBpbXBsaWNpdGVs
eShlLmcuLCBNYXggYnVyc3QgbGVuZ3RoLCBBdnJhZ2UgPmJ1cnN0KSwgc29tZSBvZiB0aGVtIGlz
IG5vdCBlYXN5IHRvIGNhbGN1bGF0ZSBhbmQgbm90IGhhcyB0aGUgc2FtZSBwdXJwb3NlIGFzIG90
aGVyIG1lYXN1cmVtZW50IHJlc3VsdHMgaW5jbHVkZWQgaW4gdGhlIGJ1cnN0IGdhcCBkaXNjYXJk
IGFuZCBsb3NzLiANCg0KW1Fpbl06IEFncmVlLg0KDQo+VGhhdCdzIHdoYXQgd2UgdW5kZXJzdGFu
ZGluZyB0byB0aGVzZSBwb3RlbnRpYWwgbWV0cmljcyBibG9jayBleHRlbnNpb24sIGxldCBtZSBr
bm93IGlmIHlvdSBoYXZlIGRpZmZlcmVudCBvcGluaW9uLiANCiANCj5SZWdhcmRzISANCj5TdW5z
aGluZSBhbmQgSmluZyANCj5TaGFuZ2hhaSBSZXNlYXJjaCBJbnN0aXR1dGUgb2YgQ2hpbmEgVGVs
ZWNvbSANCiANCg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ==

--Boundary_(ID_PhFt9tw4VPROen1kYV1K4w)
Content-type: text/html; charset=UTF-8
Content-transfer-encoding: base64

77u/PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9u
YWwvL0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0
PXV0Zi04IiBodHRwLWVxdWl2PUNvbnRlbnQtVHlwZT4NCjxNRVRBIG5hbWU9R0VORVJBVE9SIGNv
bnRlbnQ9Ik1TSFRNTCA4LjAwLjYwMDEuMTkxNzAiPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+
DQo8Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPkhpLDwvRElWPg0KPERJVj4tLS0tLSBPcmln
aW5hbCBNZXNzYWdlIC0tLS0tIDxCUj4mZ3Q7RnJvbTogPEEgDQpocmVmPSJtYWlsdG86emhhbmd5
eEBzdHRyaS5jb20uY24iPnpoYW5neXhAc3R0cmkuY29tLmNuPC9BPiA8QlI+Jmd0O1RvOiB4cmJs
b2NrIA0KPEJSPiZndDtTZW50OiBUdWVzZGF5LCBEZWNlbWJlciAyMCwgMjAxMSAxMTozOSBBTTxC
Uj4mZ3Q7U3ViamVjdDogW3hyYmxvY2tdIA0KKEJ1cnN0cyBhbmQgR2FwcykgT3BlbiBpc3N1ZSAy
OiBwb3RlbnRpYWwgbWV0cmljcyBibG9ja2V4dGVuc2lvbjwvRElWPg0KPERJVj48Rk9OVCBzaXpl
PTIgZmFjZT3lrovkvZM+PC9GT05UPiZuYnNwOzwvRElWPjxGT05UIHNpemU9MiBmYWNlPeWui+S9
kz4NCjxESVY+PEJSPjxGT05UIHNpemU9MyBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPiZndDtIaSwg
Zm9sa3M6IDxCUj4mZ3Q7Rm9sbG93aW5nIA0KdGhlIG1haWxpbmcgbGlzdCBkaXNjdXNzaW9uIHJl
Z2FyZGluZyB3aGV0aGVyIHBvdGVudGlhbCBtZXRyaWNzIGlzIG5lZWRlZCBpbiB0aGUgDQpCdXJz
dHMgYW5kIEdhcHMgZHJhZnRzIDxCUj4mZ3Q7PC9GT05UPjxBIA0KaHJlZj0iaHR0cDovL3d3dy5p
ZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL3hyYmxvY2svY3VycmVudC9tc2cwMDEzOS5odG1sIj48
Rk9OVCANCnNpemU9MyANCmZhY2U9IlRpbWVzIE5ldyBSb21hbiI+aHR0cDovL3d3dy5pZXRmLm9y
Zy9tYWlsLWFyY2hpdmUvd2ViL3hyYmxvY2svY3VycmVudC9tc2cwMDEzOS5odG1sPC9GT05UPjwv
QT48Rk9OVCANCnNpemU9MyBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPiA8QlI+Jmd0O1dlIGhhdmUg
YnJpZWZseSBkaXNjdXNzZWQgdGhlc2UgcG90ZW50aWFsIA0KbWV0cmljcyB0aGF0IGNvdWxkIGJl
IGFkZGVkIHRvIGJ1cnN0IGdhcCBtZXRyaWNzLCBwcm9wb3NlZCBieSBBbGFuIGluIHRoZSBUYWlw
ZWkgDQptZWV0aW5nLiA8QlI+Jmd0O1VuZm9ydHVudGVseSB0aGlzIGlzc3VlIGhhZG4ndCBiZWVu
IGNvbmNsdWRlZCBpbiB0aGUgSUVURiA4MiANCm1lZXRpbmcuIDxCUj4mbmJzcDs8QlI+Jmd0O0Zv
ciB0aGUgd2F5IGZvcndhcmQgdG8gYnVyc3QgZ2FwIGRpc2NhcmQgZHJhZnQgYW5kIA0KYnVyc3Qg
Z2FwIGxvc3MgZHJhZnQsIHdlIGxpa2UgdG8gZGlzY3VzcyB0aGUgcmVsYXRpb24gYmV0d2VlbiA8
QlI+Jmd0O3RoZXNlIA0KcG90ZW50aWFsIGV4dGVuc2lvbiBhbmQgYnVyc3QgZ2FwIGRyYWZ0cyBh
bmQgZGVjaWRlIHdoaWNoIHNob3VsZCBiZSBpbmNsdWRlZCBhbmQgDQp3aGljaCBub3QuIDxCUj4m
bmJzcDs8QlI+Jmd0O2EuIE1heCBidXJzdCBsZW5ndGg8QlI+Jmd0O0luIHRoZSBtZWV0aW5nLCB3
ZSB3ZXJlIA0KYXNrZWQgdG8gY2xhcmlmeSBydW4tbGVuZ3RoIGJlIHVzZWQgZm9yIGNhbGN1bGF0
aW5nIG1heCBidXJzdC4gQWZ0ZXIgcmVhZGluZyANCmRyYWZ0LWlldGYteHJibG9jay1ydGNwLXhy
LWRpc2NhcmQtcmxlLW1ldHJpY3MsIDxCUj4mZ3Q7d2UgYXJlIGF3YXJlIHRoYXQgdGhlIA0KZGlm
ZmVyZW5jZSBiZXR3ZWVuIHJsZSBkaXNjYXJkIGFuZCBidXJzdCBnYXAgZGlzY2FyZCBoYXMgYmVl
biB3ZWxsIGNsYXJpZmllZCBpbiANCnRoZSBpbnRyb2R1Y3Rpb24gc2VjdGlvbiBvZiBkcmFmdC1p
ZXRmLXhyYmxvY2stcnRjcC14ci1kaXNjYXJkLXJsZS1tZXRyaWNzLiANCjxCUj4mZ3Q7QWxzbyB3
ZSBiZWxpZXZlIHJ1biBsZW5ndGggZW5jb2RpbmcgZGlzY2FyZCBpcyBvbmUgd2F5IHRvIGNhbGN1
YWx0ZSBtYXggDQpidXJzdCBsZW5ndGguIDxCUj4mbmJzcDs8QlI+Jmd0O0luIHRoZSBidXJzdCBn
YXAgZGlzY2FyZCBkcmFmdCwgaWYgdGhlcmUgYXJlIDQgDQpidXJzdCBhbmQgNSBnYXBzLCZuYnNw
OyBidXJzdCBnYXAgZGlzY2FyZCBtZXRyaWMgYmxvY2sgY2FuIGJlIHVzZWQgdG8gcmVwb3J0IHN1
bSANCm9mIGJ1cnN0IGR1cmF0aW9ucyBhbmQgc3F1YXJlcyBvZiBidXJzdCBkdXJhdGlvbnMuIEhv
d2V2ZXIgPEJSPiZndDtIb3dldmVyIG5vbmUgDQpvZiB0aGVzZSBtZXRyaWNzIGFyZSB1c2VkIHRv
IHJlcG9ydCBNYXggYnVyc3QgbGVuZ3RoLiBJdCBpcyB0cnVlIHRoYXQgTWF4IGJ1cnN0IA0KbGVu
Z3RoIHJlcHJlc2VudHMgdGhlIOKAnHdvcnN04oCdIHBlcmlvZCBmcm9tIGEgUW9FIHBlcnNwZWN0
aXZlICxIb3dldmVyIEkgdGhpbmsgTWF4IA0KYnVyc3QgbGVuZ2ggc2hvdWxkIG5vdCBiZSAmZ3Q7
cGFydCBvZiBidXJzdCBnYXAgZGlzY2FyZCBtZXRyaWMgYmxvY2sgb3IgYnVyc3QgDQpnYXAgbG9z
cyBtZXRyaWMgYmxvY2suIFNpbmNlIHdlIHVzZSB0aHJlc2hvbGQgdG8gZGl2aWRlIFJUUCBzdHJl
YW0gaW50byBnYXAgYW5kIA0KYnVyc3QuIEFsbCB0aGUgb3RoZXIgbWV0cmljIHdlIGluY2x1ZGUg
aW4gdGhlIGJ1cnN0IGdhcCBkaXNjYXJkIGFuZCBidXJzdCBnYXAgDQomZ3Q7bG9zcyBhcmUgdXNl
ZCB0byBjYWxjdWxhdGUgYnVyc3QgbG9zcyByYXRlLCBnYXAgbG9zcyByYXRlLCBidXJzdCBkaXNj
YXJkIA0KcmF0ZSwgZ2FwIGRpc2NhcmQgcmF0ZSwgYnVyc3QgZHVyYXRpb24gbWVhbiwgYnVyc3Qg
ZHVyYXRpb24gZGV2LiBVc2UgYnVyc3QgDQpkcnVhdGlvbiBtZWFuIGFuZCBidXJzdCBkdXJhdGlv
biBkZXYsIHdlIGNhbiBpbmRpY2F0ZSAmZ3Q7ZXN0aW1hdGUgPEJSPiZndDtob3cgDQpsYXJnZSB0
aGUgbWF4IGJ1cnN0IGxlbmd0aCBpcy4gU28gTWF4IGJ1cnN0IGxlbmd0aCBpcyBub3QgbmVlZGVk
IGluIHRoZSBidXJzdCANCmdhcCBkcmFmdHMuIDwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6
ZT0zIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9O
VCBzaXplPTMgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj5bUWluXTogSSBhZ3JlZSBNQVggYnVyc3Qg
bGVuZ2ggY2FuIGJlIA0Kcm91Z2hseSBlc3RpbWF0ZWQgdXNpbmcgYnVyc3QgZHVyYXRpb24gbWVh
biBhbmQgZGV2aWF0aW9uLiZuYnNwO0J1dCBpZiB3ZSBsb29rIA0KZm9yIG1vcmUgcHJlY2lzZSZu
YnNwO21lYXN1cmVtZW50IGZvciBNYXggYnVyc3QgbGVuZ3RoLCB3ZSZuYnNwO3Nob3VsZCByZWx5
IA0Kb24mbmJzcDtMb3NzIFJMRSByZXBvcnQ8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9
MyBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPmFuZCZuYnNwO0R1cGxpY2F0aW9uIFJMRSByZXBvcnQg
YW5kIA0KRGlzY2FyZCBSTEUgcmVwb3J0LiBJIGFtIG5vdCBzdXJlIHdlIGNhbiBjYWxjdWxhdGUg
TWF4IGJ1cnN0IA0KZHVyYXRpb24mbmJzcDs8L0ZPTlQ+PEZPTlQgc2l6ZT0zIGZhY2U9IlRpbWVz
IE5ldyBSb21hbiI+Jm5ic3A7c2ltcGx5IGJhc2VkIG9uIA0KRGlzY2FyZCBSTEUgcmVwb3J0Ljwv
Rk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0zIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+QnV0
IHlvdSBhcmUgcmlnaHQsIHNpbmNlIHdlIGhhdmUgbWFueSANCndheXMoZGlyZWN0IHdheSBvciBp
bmRpcmVjdCB3YXkgKSB0byBtZWFzdXJlIE1heCBidXJzdCBsZW5ndGgsIEkgYWdyZWUgaXQgYWRk
IA0KY29tcGxleGl0eSB0byBCdXJzdCBnYXAgZGlzY2FyZCBkcmFmdCBpZiBhZGRpbmcgdGhpcyBt
ZXRyaWMgaW50byBidXJzdCBnYXAgDQpkaXNjYXJkIGRyYWZ0LjwvRk9OVD48L0RJVj4NCjxESVY+
PEJSPjxGT05UIHNpemU9MyBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPiZndDtiLiBBdmVyYWdlIGJ1
cnN0IDxCUj4mZ3Q7SW4gdGhlIA0KbWVldGluZywgd2Ugd2VyZSBhbHNvIGFza2VkIHRvIGNsYXJp
Znkgd2hldGhlciB0aGVyZSBpcyBhIG5lZWQgdG8gYWRkIGF2ZXJhZ2UgDQpidXJzdC4gT3VyIGFu
c3dlciBpcyBubywgYXMgd2UgZXhwbGFpbmVkJm5ic3A7IGluIHRoZSAoYSksIHRoZSBtZXRyaWNz
IGluY2x1ZGVkIA0KaW4gdGhlIGJ1cnN0IGdhcCBsb3NzIGFuZCBidXJzdCBnYXAgZGlzY2FyZCA8
QlI+Jm5ic3A7Jmd0O3dpbGwgYmUgZmluYWxseSB1c2VkIA0KdG8gY2FsY3VsYXRlIGJ1cnN0IGR1
cmF0aW9uIG1lYW4gYW5kIGJ1cnN0IGR1cmF0aW9uIHZhcmlhbmNlLiBUaGVyZWZvcmUgQXZlcmFn
ZSANCmJ1cnN0IGNhbiBiZSBlc3RpbWF0ZWQgdXNpbmcgYnVyc3QgZHVyYXRpb24gbWVhbi4gd2Ug
ZG9uJ3QgbmVlZCB0byBhZGQgYXZlcmFnZSANCmJ1cnN0IGludG8gdGhlIGV4aXN0aW5nICZndDtk
cmFmdC1pZXRmLXJ0Y3AteHItYnVyc3QtZ2FwLWRpc2NhcmQgYW5kIA0KZHJhZnQtaWV0Zi1ydGNw
LXhyLWJ1cnN0LWdhcC1sb3NzLCBpbnN0ZWFkLCB3ZSBzaG91bGQgcHV0IGludG8gYSBuZXcgc2Vw
YXJhdGUgDQptZXRyaWMgYmxvY2tzLiBUaGVzZSBuZXcgc2VwYXJhdGUgbWV0cmljIGJsb2NrcyBo
YXZlIGFscmVhZHkgYmVlbiBkZWZpbmVkIGluIHRoZSANCiZndDtkcmFmdC16b3JuLXhyYmxvY2st
YWwtc3RhdCwgaS5lLiwgQnVyc3QvR2FwIERpc2NhcmQgU3VtbWFyeSBTdGF0aXN0aWNzIEJsb2Nr
IA0KYW5kIEJ1cnN0L0dhcCBMb3NzIFN1bW1hcnkgU3RhdGlzdGljcyBCbG9jay4gPC9GT05UPjwv
RElWPg0KPERJVj48Rk9OVCBzaXplPTMgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj48L0ZPTlQ+Jm5i
c3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9MyBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPltRaW5d
OiBZZXMsIGRyYWZ0LXpvcm4teHJibG9jay1hbC1zdGF0IA0Kc3BlY2lmaWVzIG9uZSBuZXcgWFIg
QmxvY2ssaS5lLiw8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9MyBmYWNlPSJUaW1lcyBO
ZXcgUm9tYW4iPjxTVFJPTkc+QnVyc3QvR2FwIERpc2NhcmQgU3VtbWFyeSANClN0YXRpc3RpY3Mg
QmxvY2s8L1NUUk9ORz48L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9MyBmYWNlPSJUaW1l
cyBOZXcgUm9tYW4iPkJ1cnN0IGR1cmF0aW9uIA0KTWVhbiZuYnNwOyZuYnNwO2NvbnRhaW5lZCBp
biB0aGlzIFhSIEJsb2NrIGNhbiBiZSB1c2VkIHRvIHJlcG9ydCBBdmVyYWdlIGJ1cnN0IA0KZHVy
YXRpb24gdmFsdWUuIFNvIEkgYWdyZWUmbmJzcDtpdCBpcyByZWR1bmRhbnQgZm9yIGJ1cnN0IGdh
cCBkcmFmdHMgdG8gaW5jbHVkZSANCmF2ZXJhZ2UgYnVyc3QgaW50byByZWxhdGVkIFhSIEJsb2Nr
Jm5ic3A7LjxCUj4mbmJzcDs8QlI+Jmd0O2MuVGltZSBTaW5jZSBMYXN0IA0KQnVyc3QgPEJSPiZn
dDtPbiB0aGUgbGlzdCwgQWxhbiBwcm9wb3NlZCB0byBhZGQgdGltZSBzaW5jZSBsYXN0IGJ1cnN0
IGludG8gYnVyc3QgDQpnYXAgZHJhZnQsIHRoZSByZWFzb24gcHJvdmlkZWQgYnkgaGltIGlzIGl0
IGlzIGhlbHBmdWwgdG8ga25vdyB3aGVuIHRoZSBsYXN0IA0Kc3Vic3RhbnRpYWwgbG9zcy9kaXNj
YXJkIGJ1cnN0IG9jY3VycmVkIHJlbGF0aXZlIHRvIHRoZSByZXBvcnQgdGltZS4gPEJSPiZndDtX
ZSANCmFncmVlIGl0IGlzIHVzZWZ1bC4gSG93ZXZlciB3ZSByZWFsaXplIGl0IGlzIG5vdCBlYXN5
IGZvciB1cyB0byBkaXJlY3RseSBtZWFzdXJlIA0KVGltZSBzaW5jZSBsYXN0IGJ1cnN0IGlmIHdl
IHJlbHkgb24gUkxFIGRpc2NhcmQgYW5kIGRvbid0IGtlZXAgdHJhY2sgb2YgcGFja2V0cyANCnNl
cXVlbmNlIG51bWJlciZuYnNwOyBpbiB0aGUgaW50ZXJ2YWwgPEJSPiZndDtvbmUgd2F5IHRvIGNh
bGN1bGF0ZSB0aGlzIG1ldHJpYyANCmlzIHRvIHJlbHkgb24gcnVuIGxlbmd0aCBlbmNvZGluZyBk
aXNjYXJkIG1ldHJpYyBpbiB0aGUgDQpkcmFmdC1pZXRmLXhyYmxvY2stcnRjcC14ci1kaXNjYXJk
LXJsZS1tZXRyaWNzLiBPbiB0aGUgb3RoZXIgaGFuZCwgdGhlIGRhdGEgd2UgDQpjYXJyaWVkIGlu
IHRoZSBidXJzdCBnYXAgZHJhZnRzIGFyZSBhbGwgJmd0O3VzZWQgdG8gY2FsY3VsYXRlIHN0YXRp
c3RpY3Mgc3VtbWFyeSANCm9mIGJ1cnN0IGdhcCwgaG93ZXZlciB0aW1lIHNpbmNlIGxhc3QgYnVy
c3QgaXMgbm90IHVzZWQgdG8gY2FsY3VsYXRlIHN0YXRpc3RpY3MgDQpzdW1tYXJ5IG9mIGJ1cnN0
IGdhcCwgdGhlcmVmb3JlIHRpbWUgc2luY2UgbGFzdCBidXJzdCBpcyBub3QgcGFydCBvZiBidXJz
dCBnYXAgDQpkcmFmdCBhbmQgJmd0O3RoZXJlZm9yZSBpcyBub3QgbmVlZGVkLiZuYnNwOzwvRk9O
VD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0zIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+PC9GT05U
PiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBzaXplPTMgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj5b
UWluXTogQWdhaW4sIHlvdSBjYW4gbm90IGRpcmVjdGx5IA0KbWVhc3VyZSB0aGUgVGltZSBTaW5j
ZSBsYXN0IEJ1cnN0IHNpbXBseSBiYXNlZCBvbiBkaXNjYXJkIFJMRSByZXBvcnQsIHlvdSBhbHNv
IA0KbmVlZCB0byBvYnNlcnZlIGVhY2ggcGFja2V0IGR1cmluZyBtZWFzdXJtZW50IGludGVydmFs
LCBpLmUuLCByZWx5aW5nIG9uIHRoZSANCnBlci1wYWNrZXQgaW5mb3JtYXRpb24gY29udGFpbmVk
IGluIExvc3MgUkxFLCBEdXBsaWNhdGUgUkxFIHJlcG9ydC4mbmJzcDtidXQgcGVyIA0KcGFja2V0
IGluZm9ybWF0aW9uIGRvZXNuJ3QgaW5jbHVkZSBhbnkgdGltZSByZWxhdGVkJm5ic3A7aW5mb3Jt
YXRpb24uIFdoYXQgeW91IA0KY2FuIGRvIGlzIHRvIGxvY2F0ZSB0aGUgZmlyc3QgcGFja2V0IHNx
dWVuY2UgbnVtYmVyIG9mIGxhc3QgYnVyc3QsIGFuZCB0aGVuIHlvdSANCmNhbiB1c2Ugc3luY2hy
b25pemF0aW9uIGluZm9ybWF0aW9uIGNhcnJpZWQgaW4gdGhhdCBwYWNrZXQgaGVhZGVyIHRvIHJv
dWdobHkgDQplc3RpbWF0ZSBUaW1lIHNpbmNlIExhc3QgQnVyc3QuIEkgYW0gbm90IHN1cmUgd2Ug
aGF2ZSBzdWNoIGF1dG9tYXRpYyBtZWFzdXJtZW50IA0KdG9vbCB0byByZXBvcnQgVGltZSBzaW5j
ZSBMYXN0IEJ1cnN0IGRpcmVjdGx5LiBJZiBubywgdGhlbiBpdCBpcyB0b28gbXVjaCANCmNvbXBs
aWNhdGVkIHRvIGNhbGN1bGF0ZSB0aGlzIG1ldHJpYy4gPC9GT05UPjwvRElWPg0KPERJVj48Rk9O
VCBzaXplPTMgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj4mbmJzcDs8QlI+Jmd0O1RoZXJlZm9yZSBt
eSBjb25jbHVzaW9uIA0KaXMgZWFjaCBvZiB0aGVtIGFyZSB2ZXJ5IHVzZWZ1bC4gSG93ZXZlciBp
dCBpcyBub3QgYSBnb29kIGlkZWEgdG8gcHV0IHRoZW0gYWxsIA0KaW50byBidXJzdCBnYXAgZHJh
ZnRzIHNpbmNlIHNvbWUgb2YgdGhlbSBjYW4gYmUgZXN0aW1hdGVkIGltcGxpY2l0ZWx5KGUuZy4s
IE1heCANCmJ1cnN0IGxlbmd0aCwgQXZyYWdlICZndDtidXJzdCksIHNvbWUgb2YgdGhlbSBpcyBu
b3QgZWFzeSB0byBjYWxjdWxhdGUgYW5kIG5vdCANCmhhcyB0aGUgc2FtZSBwdXJwb3NlIGFzIG90
aGVyIG1lYXN1cmVtZW50IHJlc3VsdHMgaW5jbHVkZWQgaW4gdGhlIGJ1cnN0IGdhcCANCmRpc2Nh
cmQgYW5kIGxvc3MuIDwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0zIGZhY2U9IlRpbWVz
IE5ldyBSb21hbiI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBzaXplPTMgZmFjZT0i
VGltZXMgTmV3IFJvbWFuIj5bUWluXTogQWdyZWUuPC9ESVY+DQo8RElWPjxCUj4mZ3Q7VGhhdCdz
IHdoYXQgd2UgdW5kZXJzdGFuZGluZyB0byB0aGVzZSBwb3RlbnRpYWwgbWV0cmljcyBibG9jayAN
CmV4dGVuc2lvbiwgbGV0IG1lIGtub3cgaWYgeW91IGhhdmUgZGlmZmVyZW50IG9waW5pb24uIDxC
Uj4mbmJzcDs8QlI+Jmd0O1JlZ2FyZHMhIA0KPEJSPiZndDtTdW5zaGluZSBhbmQgSmluZyA8QlI+
Jmd0O1NoYW5naGFpIFJlc2VhcmNoIEluc3RpdHV0ZSBvZiBDaGluYSBUZWxlY29tIA0KPEJSPjwv
Rk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPjxCUj4tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLTwvRk9OVD48L0RJVj48L0JPRFk+PC9IVE1MPg0K

--Boundary_(ID_PhFt9tw4VPROen1kYV1K4w)--

From internet-drafts@ietf.org  Thu Jan 12 00:53:44 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93A3F21F84E2; Thu, 12 Jan 2012 00:53:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.563
X-Spam-Level: 
X-Spam-Status: No, score=-102.563 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5pel8nycpa49; Thu, 12 Jan 2012 00:53:44 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E0B121F84DA; Thu, 12 Jan 2012 00:53:44 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20120112085344.2469.95564.idtracker@ietfa.amsl.com>
Date: Thu, 12 Jan 2012 00:53:44 -0800
Cc: xrblock@ietf.org
Subject: [xrblock] I-D Action: draft-ietf-xrblock-rtcp-xr-meas-identity-02.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jan 2012 08:53:44 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Metric Blocks for use with RTCP's Ext=
ended Report Framework Working Group of the IETF.

	Title           : Measurement Identity and information Reporting using SDE=
S item and XR Block
	Author(s)       : Geoff Hunt
                          Alan Clark
                          Qin Wu
	Filename        : draft-ietf-xrblock-rtcp-xr-meas-identity-02.txt
	Pages           : 14
	Date            : 2012-01-12

   This document defines a RTCP SDES item and a RTCP XR Block carrying
   parameters which identify a measurement, to which one or more other
   RTCP XR Report Blocks may refer.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-xrblock-rtcp-xr-meas-identit=
y-02.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-xrblock-rtcp-xr-meas-identity=
-02.txt


From bill.wu@huawei.com  Thu Jan 12 01:06:10 2012
Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 417B121F85A4 for <xrblock@ietfa.amsl.com>; Thu, 12 Jan 2012 01:06:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.103
X-Spam-Level: 
X-Spam-Status: No, score=-6.103 tagged_above=-999 required=5 tests=[AWL=0.496,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C2jWKFnsy-Y8 for <xrblock@ietfa.amsl.com>; Thu, 12 Jan 2012 01:06:09 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 6CDF321F85A3 for <xrblock@ietf.org>; Thu, 12 Jan 2012 01:06:09 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LXO002VYH7ZN2@szxga05-in.huawei.com> for xrblock@ietf.org; Thu, 12 Jan 2012 17:04:47 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LXO00FG2H7BS6@szxga05-in.huawei.com> for xrblock@ietf.org; Thu, 12 Jan 2012 17:04:47 +0800 (CST)
Received: from szxeml202-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGG76280; Thu, 12 Jan 2012 17:04:45 +0800
Received: from SZXEML407-HUB.china.huawei.com (10.82.67.94) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 12 Jan 2012 17:04:35 +0800
Received: from w53375q (10.138.41.130) by szxeml407-hub.china.huawei.com (10.82.67.94) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 12 Jan 2012 17:04:38 +0800
Date: Thu, 12 Jan 2012 17:04:37 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: xrblock@ietf.org
Message-id: <C941638AF7644FF1BF51AAF755353D35@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
Subject: [xrblock] Fw: I-D Action:draft-ietf-xrblock-rtcp-xr-meas-identity-02.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jan 2012 09:06:10 -0000

On 12 January 2012, at 4:53 PM, Internet-Drafts@ietf.org wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of
> the Metric Blocks for use with RTCP's Extended Report Framework Working Group of the IETF.
> 
> Title           : Measurement Identity and information Reporting using SDES item and XR Block
> Author(s)       : Geoff Hunt
>                          Alan Clark
>                          Qin Wu
> Filename        : draft-ietf-xrblock-rtcp-xr-meas-identity-02.txt
> Pages           : 14
> Date            : 2012-01-12
> 
>   This document defines a RTCP SDES item and a RTCP XR Block carrying
>   parameters which identify a measurement, to which one or more other
>   RTCP XR Report Blocks may refer.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-xrblock-rtcp-xr-meas-identity-02.txt


[Qin]: This version adresses the comments that came from WG last call and last 
Taipei XRblock meeting. Thank for all the people who spends time reviewing this document.

From shida@ntt-at.com  Thu Jan 12 03:54:54 2012
Return-Path: <shida@ntt-at.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDD9421F8513 for <xrblock@ietfa.amsl.com>; Thu, 12 Jan 2012 03:54:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.661
X-Spam-Level: 
X-Spam-Status: No, score=-101.661 tagged_above=-999 required=5 tests=[AWL=0.604, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z8JgW+bsS391 for <xrblock@ietfa.amsl.com>; Thu, 12 Jan 2012 03:54:54 -0800 (PST)
Received: from gator465.hostgator.com (gator465.hostgator.com [69.56.174.130]) by ietfa.amsl.com (Postfix) with ESMTP id 6D20221F850B for <xrblock@ietf.org>; Thu, 12 Jan 2012 03:54:54 -0800 (PST)
Received: from [125.195.61.4] (port=55821 helo=[192.168.1.10]) by gator465.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <shida@ntt-at.com>) id 1RlH34-00051y-Pb for xrblock@ietf.org; Thu, 12 Jan 2012 03:34:19 -0600
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Shida Schubert <shida@ntt-at.com>
X-Priority: 3
In-Reply-To: <C941638AF7644FF1BF51AAF755353D35@china.huawei.com>
Date: Thu, 12 Jan 2012 18:34:17 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <10BD1A67-BDF4-46BC-A874-2981E1154465@ntt-at.com>
References: <C941638AF7644FF1BF51AAF755353D35@china.huawei.com>
To: xrblock@ietf.org
X-Mailer: Apple Mail (2.1251.1)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator465.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ntt-at.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: flh1ajp004.tky.mesh.ad.jp ([192.168.1.10]) [125.195.61.4]:55821
X-Source-Auth: shida@agnada.com
X-Email-Count: 4
X-Source-Cap: c3NoaWRhO3NzaGlkYTtnYXRvcjQ2NS5ob3N0Z2F0b3IuY29t
Subject: Re: [xrblock] I-D Action:draft-ietf-xrblock-rtcp-xr-meas-identity-02.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jan 2012 11:54:54 -0000

All;

 To those who provided comments during WGLC,=20
please make sure that the comments are reflected=20
in the version below.=20

 Many Thanks
  Shida (as chair)

On Jan 12, 2012, at 6:04 PM, Qin Wu wrote:

> On 12 January 2012, at 4:53 PM, Internet-Drafts@ietf.org wrote:
>=20
>> A New Internet-Draft is available from the on-line Internet-Drafts =
directories. This draft is a work item of
>> the Metric Blocks for use with RTCP's Extended Report Framework =
Working Group of the IETF.
>>=20
>> Title           : Measurement Identity and information Reporting =
using SDES item and XR Block
>> Author(s)       : Geoff Hunt
>>                         Alan Clark
>>                         Qin Wu
>> Filename        : draft-ietf-xrblock-rtcp-xr-meas-identity-02.txt
>> Pages           : 14
>> Date            : 2012-01-12
>>=20
>>  This document defines a RTCP SDES item and a RTCP XR Block carrying
>>  parameters which identify a measurement, to which one or more other
>>  RTCP XR Report Blocks may refer.
>>=20
>> A URL for this Internet-Draft is:
>> =
http://www.ietf.org/internet-drafts/draft-ietf-xrblock-rtcp-xr-meas-identi=
ty-02.txt
>=20
>=20
> [Qin]: This version adresses the comments that came from WG last call =
and last=20
> Taipei XRblock meeting. Thank for all the people who spends time =
reviewing this document.
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock


From csp@csperkins.org  Sat Jan 14 15:16:29 2012
Return-Path: <csp@csperkins.org>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E689C21F84F5 for <xrblock@ietfa.amsl.com>; Sat, 14 Jan 2012 15:16:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CtFRDq9bPdej for <xrblock@ietfa.amsl.com>; Sat, 14 Jan 2012 15:16:29 -0800 (PST)
Received: from anchor-msapost-3.mail.demon.net (anchor-msapost-3.mail.demon.net [195.173.77.166]) by ietfa.amsl.com (Postfix) with ESMTP id 2067D21F84F6 for <xrblock@ietf.org>; Sat, 14 Jan 2012 15:16:29 -0800 (PST)
Received: from starkperkins.demon.co.uk ([80.176.158.71] helo=[192.168.0.30]) by anchor-post-3.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1RmCpo-00012B-mO; Sat, 14 Jan 2012 23:16:28 +0000
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Colin Perkins <csp@csperkins.org>
X-Priority: 3
In-Reply-To: <10BD1A67-BDF4-46BC-A874-2981E1154465@ntt-at.com>
Date: Sat, 14 Jan 2012 23:16:26 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <E7DA1070-420B-4A72-817A-E8898EF99E76@csperkins.org>
References: <C941638AF7644FF1BF51AAF755353D35@china.huawei.com> <10BD1A67-BDF4-46BC-A874-2981E1154465@ntt-at.com>
To: Shida Schubert <shida@ntt-at.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: xrblock@ietf.org
Subject: Re: [xrblock] I-D Action:draft-ietf-xrblock-rtcp-xr-meas-identity-02.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jan 2012 23:16:30 -0000

Looks okay to me.
Colin

On 12 Jan 2012, at 09:34, Shida Schubert wrote:

>=20
> All;
>=20
> To those who provided comments during WGLC,=20
> please make sure that the comments are reflected=20
> in the version below.=20
>=20
> Many Thanks
>  Shida (as chair)
>=20
> On Jan 12, 2012, at 6:04 PM, Qin Wu wrote:
>=20
>> On 12 January 2012, at 4:53 PM, Internet-Drafts@ietf.org wrote:
>>=20
>>> A New Internet-Draft is available from the on-line Internet-Drafts =
directories. This draft is a work item of
>>> the Metric Blocks for use with RTCP's Extended Report Framework =
Working Group of the IETF.
>>>=20
>>> Title           : Measurement Identity and information Reporting =
using SDES item and XR Block
>>> Author(s)       : Geoff Hunt
>>>                        Alan Clark
>>>                        Qin Wu
>>> Filename        : draft-ietf-xrblock-rtcp-xr-meas-identity-02.txt
>>> Pages           : 14
>>> Date            : 2012-01-12
>>>=20
>>> This document defines a RTCP SDES item and a RTCP XR Block carrying
>>> parameters which identify a measurement, to which one or more other
>>> RTCP XR Report Blocks may refer.
>>>=20
>>> A URL for this Internet-Draft is:
>>> =
http://www.ietf.org/internet-drafts/draft-ietf-xrblock-rtcp-xr-meas-identi=
ty-02.txt
>>=20
>>=20
>> [Qin]: This version adresses the comments that came from WG last call =
and last=20
>> Taipei XRblock meeting. Thank for all the people who spends time =
reviewing this document.
>> _______________________________________________
>> xrblock mailing list
>> xrblock@ietf.org
>> https://www.ietf.org/mailman/listinfo/xrblock
>=20
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock



--=20
Colin Perkins
http://csperkins.org/




From bill.wu@huawei.com  Mon Jan 16 23:44:04 2012
Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6F9321F85EF for <xrblock@ietfa.amsl.com>; Mon, 16 Jan 2012 23:44:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.185
X-Spam-Level: 
X-Spam-Status: No, score=-6.185 tagged_above=-999 required=5 tests=[AWL=0.414,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cAnfTZVggZCR for <xrblock@ietfa.amsl.com>; Mon, 16 Jan 2012 23:44:03 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 4EFF521F85EE for <xrblock@ietf.org>; Mon, 16 Jan 2012 23:44:03 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LXX00CKNMRWT6@szxga03-in.huawei.com> for xrblock@ietf.org; Tue, 17 Jan 2012 15:43:08 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LXX00MB0MRHO1@szxga03-in.huawei.com> for xrblock@ietf.org; Tue, 17 Jan 2012 15:43:08 +0800 (CST)
Received: from szxeml209-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGJ10777; Tue, 17 Jan 2012 15:43:07 +0800
Received: from SZXEML417-HUB.china.huawei.com (10.82.67.156) by szxeml209-edg.china.huawei.com (172.24.2.184) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 17 Jan 2012 15:42:47 +0800
Received: from w53375q (10.138.41.130) by szxeml417-hub.china.huawei.com (10.82.67.156) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 17 Jan 2012 15:42:47 +0800
Date: Tue, 17 Jan 2012 15:42:46 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Varun Singh <vsingh.ietf@gmail.com>, xrblock@ietf.org
Message-id: <54DEF8D9713A4424933422B86EAD700D@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <CAEbPqrz05RAbaq7sNb+W09pZSJedn=iEW2Sf_BR3mRho5c=Tdg@mail.gmail.com>
Subject: Re: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jan 2012 07:44:05 -0000

Hi, Varun:
I read your proposed change, please see my comments inline.
----- Original Message ----- 
From: "Varun Singh" <vsingh.ietf@gmail.com>
To: <xrblock@ietf.org>
Sent: Wednesday, January 11, 2012 8:09 PM
Subject: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02


> Hi,
> 
> I am sending the updates to mailing list so that the discussion can
> take place before I post an updated draft.
> 
> in -01, Section 1. Last para of introduction:
>   Complementary to or instead of the indication which packets were
>   discarded, an XR block is defined to indicate the number of bytes
>   discarded, per interval or for the duration of the session, similar
>   to other XR report blocks.
> 
> Adding to that para in -02:
>   Alternatively, if the sender keeps a
>   history of the size of the packets reported in the measurement
>   interval then the sender can calculate the number of bytes discarded
>   from the information in the discard RLE block.
> 
> - is this extra clarification needed?

[Qin]: I think you don't need maintain the size for each packet, you only need to maintain
the total size for all the received packet before the next packet is coming. 

> 
> in -01, end of section 4.:
>   The 'number of bytes discarded' is a 32-bit unsigned integer value
>   indicating the total number of bytes discarded (I=11), or the number
>   of bytes discarded since the last RTCP XR Bytes Discarded block was
>   sent (I=10), or bytes discarded in a measurement interval (I=01)
>   [I-D.ietf-xrblock-rtcp-xr-meas-identity].
> 
>   Bytes Discarded Report Blocks SHOULD be sent in conjunction with an
>   RTCP RR as a compound RTCP packet.
> 
> Updated it to:
>   The 'number of bytes discarded' is a 32-bit unsigned integer value
>   indicating the total number of bytes discarded.  If the XR block is
>   not preceded by a measurement identity block
>   [I-D.ietf-xrblock-rtcp-xr-meas-identity] then the value indicates the
>   bytes lost from from the start of the session (I=11), or the number
>   of bytes discarded since the last RTCP XR Bytes Discarded block was
>   received (I=10).
> 
>   If the XR block follows a measurement identity block
>   [I-D.ietf-xrblock-rtcp-xr-meas-identity] in an RTCP RR packet then
>   the cumulative (I=11) and interval (I=10) correspond to the values in
>   the measurement block.
> 
>   Bytes Discarded Report Blocks SHOULD be sent in conjunction with an
>   RTCP RR as a compound RTCP packet.

[Qin]: Does Bytes Discarded Report Blocks rely on measurement identity block or
RTCP RR to calculate measurement interval? It is not clear to me.
If measurement identity block is present, Does Bytes Discarded Report Blocks
need to be sent with an RTCP RR?


> - clarified what the sender could do if the measurement interval is
> absent/present in the RTCP packet.
> Note at the moment there are no normative keywords in the text.
> 
> Possible clarification that can be added to the first para:
> When the measurement block is absent, the sender SHOULD calculate the
> duration of the interval using the RTP timestamps of the last reported
> HSN and current HSN. If an RTCP RR packet is lost in between then the
> assumption is wrong and the receiver SHOULD use the measurement block
> for indicating precise durations.

[Qin]: How do you guarantee the measurment information block will be sent to the receiever when RTCP RR is lost?
Are you assuming the measurment information block and RTCP RR will be sent in the separate compound RTCP  packet?

> 
> Cheers,
> Varun
> 
> -- 
> http://www.netlab.tkk.fi/~varun/
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock

From vsingh.ietf@gmail.com  Tue Jan 17 02:40:35 2012
Return-Path: <vsingh.ietf@gmail.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 039F921F8532 for <xrblock@ietfa.amsl.com>; Tue, 17 Jan 2012 02:40:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fXwIhVsSW3Ox for <xrblock@ietfa.amsl.com>; Tue, 17 Jan 2012 02:40:30 -0800 (PST)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0FF8221F852F for <xrblock@ietf.org>; Tue, 17 Jan 2012 02:40:28 -0800 (PST)
Received: by wics10 with SMTP id s10so2105113wic.31 for <xrblock@ietf.org>; Tue, 17 Jan 2012 02:40:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=pyWjEkQILI1MA9gwHQnwjUIqd1/gYkdMzCJdWR8wCAs=; b=tbSiUOluDO1jxdB+Vs75WxxdOmuJTMDWXJ7oyI16dJghmZJ/WFVKKmw+fkD4XjLG9s jWeSXr5LeC2ZAS60nvRO/fwu9KDpxbTfXUeNTwMlNsYKAGn6xE9lfzz3NBghNOfX5lAT q9OSMVP0moU/PxuN5Ryl3+9jieA6Bcqy69Ubs=
Received: by 10.180.103.2 with SMTP id fs2mr26888483wib.21.1326796828203; Tue, 17 Jan 2012 02:40:28 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.62.147 with HTTP; Tue, 17 Jan 2012 02:40:07 -0800 (PST)
In-Reply-To: <54DEF8D9713A4424933422B86EAD700D@china.huawei.com>
References: <CAEbPqrz05RAbaq7sNb+W09pZSJedn=iEW2Sf_BR3mRho5c=Tdg@mail.gmail.com> <54DEF8D9713A4424933422B86EAD700D@china.huawei.com>
From: Varun Singh <vsingh.ietf@gmail.com>
Date: Tue, 17 Jan 2012 12:40:07 +0200
Message-ID: <CAEbPqrxUWFv642yVSQrnTuFBSeVFwk3pVQBGbmGqVfB+zqgxjw@mail.gmail.com>
To: Qin Wu <bill.wu@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: xrblock@ietf.org
Subject: Re: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jan 2012 10:40:35 -0000

Hi Qin,

Comments inline.

On Tue, Jan 17, 2012 at 09:42, Qin Wu <bill.wu@huawei.com> wrote:
> Hi, Varun:
> I read your proposed change, please see my comments inline.
> ----- Original Message -----
> From: "Varun Singh" <vsingh.ietf@gmail.com>
> To: <xrblock@ietf.org>
> Sent: Wednesday, January 11, 2012 8:09 PM
> Subject: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-=
rle-metrics-02
>
>
>> Hi,
>>
>> I am sending the updates to mailing list so that the discussion can
>> take place before I post an updated draft.
>>
>> in -01, Section 1. Last para of introduction:
>> =A0 Complementary to or instead of the indication which packets were
>> =A0 discarded, an XR block is defined to indicate the number of bytes
>> =A0 discarded, per interval or for the duration of the session, similar
>> =A0 to other XR report blocks.
>>
>> Adding to that para in -02:
>> =A0 Alternatively, if the sender keeps a
>> =A0 history of the size of the packets reported in the measurement
>> =A0 interval then the sender can calculate the number of bytes discarded
>> =A0 from the information in the discard RLE block.
>>
>> - is this extra clarification needed?
>
> [Qin]: I think you don't need maintain the size for each packet, you only=
 need to maintain
> the total size for all the received packet before the next packet is comi=
ng.
>

The receiver needs to maintain the total size (for interval and for
cumulative). However, the extra paragraph is to show that discarded
bytes can also be calculated from the Discard RLE encoding--if the
sender maintains the size of the sent packets. It can then add up the
size of packets marked in the RLE block using a lookup table.

>>
>> in -01, end of section 4.:
>> =A0 The 'number of bytes discarded' is a 32-bit unsigned integer value
>> =A0 indicating the total number of bytes discarded (I=3D11), or the numb=
er
>> =A0 of bytes discarded since the last RTCP XR Bytes Discarded block was
>> =A0 sent (I=3D10), or bytes discarded in a measurement interval (I=3D01)
>> =A0 [I-D.ietf-xrblock-rtcp-xr-meas-identity].
>>
>> =A0 Bytes Discarded Report Blocks SHOULD be sent in conjunction with an
>> =A0 RTCP RR as a compound RTCP packet.
>>
>> Updated it to:
>> =A0 The 'number of bytes discarded' is a 32-bit unsigned integer value
>> =A0 indicating the total number of bytes discarded. =A0If the XR block i=
s
>> =A0 not preceded by a measurement identity block
>> =A0 [I-D.ietf-xrblock-rtcp-xr-meas-identity] then the value indicates th=
e
>> =A0 bytes lost from from the start of the session (I=3D11), or the numbe=
r
>> =A0 of bytes discarded since the last RTCP XR Bytes Discarded block was
>> =A0 received (I=3D10).
>>
>> =A0 If the XR block follows a measurement identity block
>> =A0 [I-D.ietf-xrblock-rtcp-xr-meas-identity] in an RTCP RR packet then
>> =A0 the cumulative (I=3D11) and interval (I=3D10) correspond to the valu=
es in
>> =A0 the measurement block.
>>
>> =A0 Bytes Discarded Report Blocks SHOULD be sent in conjunction with an
>> =A0 RTCP RR as a compound RTCP packet.
>
> [Qin]: Does Bytes Discarded Report Blocks rely on measurement identity bl=
ock or
> RTCP RR to calculate measurement interval? It is not clear to me.

If the discard block follows a measurement identity block then it must
use the measurement
information in the block. If the measurement identity block is not
present then it should use
the HSN (Seq No., RTP timestamp) in the previous RR containing the block an=
d
the current RR to calculate the measurement interval. However, if the
information
from the previous RR is not available then the sender should ignore
the discard block.

> If measurement identity block is present, Does Bytes Discarded Report Blo=
cks
> need to be sent with an RTCP RR?
>
No. I can replace the last line with this:

If the receiver sends the Bytes Discarded Report Block without the
measurement identity block then the discard block SHOULD be sent in
conjunction with an RTCP RR as a compound RTCP packet.


>
>> - clarified what the sender could do if the measurement interval is
>> absent/present in the RTCP packet.
>> Note at the moment there are no normative keywords in the text.
>>
>> Possible clarification that can be added to the first para:
>> When the measurement block is absent, the sender SHOULD calculate the
>> duration of the interval using the RTP timestamps of the last reported
>> HSN and current HSN. If an RTCP RR packet is lost in between then the
>> assumption is wrong and the receiver SHOULD use the measurement block
>> for indicating precise durations.
>
> [Qin]: How do you guarantee the measurment information block will be sent=
 to the receiever when RTCP RR is lost?

There is no guarantee. What I meant to say is that if the packet is
lost then the above assumption is wrong and the only way to overcome
the challenge is that the receiver should use the measurement block.

The question however is do we need to add such a clarification?

> Are you assuming the measurment information block and RTCP RR will be sen=
t in the separate compound RTCP =A0packet?


>
>>
>> Cheers,
>> Varun
>>
>> --
>> http://www.netlab.tkk.fi/~varun/
>> _______________________________________________
>> xrblock mailing list
>> xrblock@ietf.org
>> https://www.ietf.org/mailman/listinfo/xrblock



--=20
http://www.netlab.tkk.fi/~varun/

From eckelcu@cisco.com  Tue Jan 17 12:47:00 2012
Return-Path: <eckelcu@cisco.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20C6D21F8489 for <xrblock@ietfa.amsl.com>; Tue, 17 Jan 2012 12:47:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.428
X-Spam-Level: 
X-Spam-Status: No, score=-4.428 tagged_above=-999 required=5 tests=[AWL=-1.829, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gyVgzmoElKyn for <xrblock@ietfa.amsl.com>; Tue, 17 Jan 2012 12:46:59 -0800 (PST)
Received: from bgl-iport-2.cisco.com (bgl-iport-2.cisco.com [72.163.197.26]) by ietfa.amsl.com (Postfix) with ESMTP id E13C321F8486 for <xrblock@ietf.org>; Tue, 17 Jan 2012 12:46:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=2452; q=dns/txt; s=iport; t=1326833219; x=1328042819; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=q2wXkrMLEDsELr3xtUK2K0Ph5SEGCTjnlQcYtTlY4sk=; b=MezJxMzdeyKDUxDkxfqcS3F4Gm+o5YiPJlWFfOEl9111URpDyzhAOgmD dKibkIjbx6cVB8FOnnRFPpQ+fuew3H77hPFpIDQQ95iAx3XFuFv07PRGc EKlJEOiyv0ZpcPaZ00hDC60CY/QhpG1Y9/vzbwnUBDsStB5oxM9sMwj2j w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqAEAN/cFU9Io8UY/2dsb2JhbAA6AQmsQ4ILgXIBAQEEAQEBDwEdCjQLDAQCAQgOAwQBAQEKBhcBBgEmHwkIAQEEARACCAEZh2CZAgGeQ4hdAR8wMwIBAUICAgQBAwcBAQMNAQIDAQIBAQgBAQEBAj0MChowgWhXFgEBAQKCR2MEiDufOBw
X-IronPort-AV: E=Sophos;i="4.71,525,1320624000";  d="scan'208";a="3604846"
Received: from vla196-nat.cisco.com (HELO bgl-core-1.cisco.com) ([72.163.197.24]) by bgl-iport-2.cisco.com with ESMTP; 17 Jan 2012 20:46:54 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by bgl-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id q0HKjK3p023168; Tue, 17 Jan 2012 20:46:53 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 17 Jan 2012 12:46:50 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 17 Jan 2012 12:46:49 -0800
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C062838B3@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E7DA1070-420B-4A72-817A-E8898EF99E76@csperkins.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [xrblock] I-DAction:draft-ietf-xrblock-rtcp-xr-meas-identity-02.txt
Thread-Index: AczTEo4i6o/bgB5dQTqVOWYiO8teDgCRoJlQ
References: <C941638AF7644FF1BF51AAF755353D35@china.huawei.com><10BD1A67-BDF4-46BC-A874-2981E1154465@ntt-at.com> <E7DA1070-420B-4A72-817A-E8898EF99E76@csperkins.org>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Colin Perkins" <csp@csperkins.org>, "Shida Schubert" <shida@ntt-at.com>
X-OriginalArrivalTime: 17 Jan 2012 20:46:50.0634 (UTC) FILETIME=[233456A0:01CCD559]
Cc: xrblock@ietf.org
Subject: Re: [xrblock] I-DAction:draft-ietf-xrblock-rtcp-xr-meas-identity-02.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jan 2012 20:47:00 -0000

My comments were all addressed as well.

Charles

> -----Original Message-----
> From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On
> Behalf Of Colin Perkins
> Sent: Saturday, January 14, 2012 3:16 PM
> To: Shida Schubert
> Cc: xrblock@ietf.org
> Subject: Re: [xrblock] I-DAction:draft-ietf-xrblock-rtcp-xr-meas-
> identity-02.txt
>=20
> Looks okay to me.
> Colin
>=20
> On 12 Jan 2012, at 09:34, Shida Schubert wrote:
>=20
> >
> > All;
> >
> > To those who provided comments during WGLC,
> > please make sure that the comments are reflected
> > in the version below.
> >
> > Many Thanks
> >  Shida (as chair)
> >
> > On Jan 12, 2012, at 6:04 PM, Qin Wu wrote:
> >
> >> On 12 January 2012, at 4:53 PM, Internet-Drafts@ietf.org wrote:
> >>
> >>> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This draft is a work item of
> >>> the Metric Blocks for use with RTCP's Extended Report Framework
> Working Group of the IETF.
> >>>
> >>> Title           : Measurement Identity and information Reporting
> using SDES item and XR Block
> >>> Author(s)       : Geoff Hunt
> >>>                        Alan Clark
> >>>                        Qin Wu
> >>> Filename        : draft-ietf-xrblock-rtcp-xr-meas-identity-02.txt
> >>> Pages           : 14
> >>> Date            : 2012-01-12
> >>>
> >>> This document defines a RTCP SDES item and a RTCP XR Block
carrying
> >>> parameters which identify a measurement, to which one or more
other
> >>> RTCP XR Report Blocks may refer.
> >>>
> >>> A URL for this Internet-Draft is:
> >>> http://www.ietf.org/internet-drafts/draft-ietf-xrblock-rtcp-xr-
> meas-identity-02.txt
> >>
> >>
> >> [Qin]: This version adresses the comments that came from WG last
> call and last
> >> Taipei XRblock meeting. Thank for all the people who spends time
> reviewing this document.
> >> _______________________________________________
> >> xrblock mailing list
> >> xrblock@ietf.org
> >> https://www.ietf.org/mailman/listinfo/xrblock
> >
> > _______________________________________________
> > xrblock mailing list
> > xrblock@ietf.org
> > https://www.ietf.org/mailman/listinfo/xrblock
>=20
>=20
>=20
> --
> Colin Perkins
> http://csperkins.org/
>=20
>=20
>=20
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock

From bill.wu@huawei.com  Tue Jan 17 17:34:46 2012
Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A29C1F0C53 for <xrblock@ietfa.amsl.com>; Tue, 17 Jan 2012 17:34:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.202
X-Spam-Level: 
X-Spam-Status: No, score=-6.202 tagged_above=-999 required=5 tests=[AWL=0.397,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qECFwNnHQmev for <xrblock@ietfa.amsl.com>; Tue, 17 Jan 2012 17:34:44 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 8F0251F0C40 for <xrblock@ietf.org>; Tue, 17 Jan 2012 17:34:43 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LXZ00AY30DST1@szxga05-in.huawei.com> for xrblock@ietf.org; Wed, 18 Jan 2012 09:34:40 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LXZ00LC60DSUN@szxga05-in.huawei.com> for xrblock@ietf.org; Wed, 18 Jan 2012 09:34:40 +0800 (CST)
Received: from szxeml202-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGJ61649; Wed, 18 Jan 2012 09:34:17 +0800
Received: from SZXEML424-HUB.china.huawei.com (10.82.67.163) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 18 Jan 2012 09:34:11 +0800
Received: from w53375q (10.138.41.130) by szxeml424-hub.china.huawei.com (10.82.67.163) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 18 Jan 2012 09:34:07 +0800
Date: Wed, 18 Jan 2012 09:34:06 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Varun Singh <vsingh.ietf@gmail.com>
Message-id: <58EA66C004CC42338DB85F9C032C1CC3@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <CAEbPqrz05RAbaq7sNb+W09pZSJedn=iEW2Sf_BR3mRho5c=Tdg@mail.gmail.com> <54DEF8D9713A4424933422B86EAD700D@china.huawei.com> <CAEbPqrxUWFv642yVSQrnTuFBSeVFwk3pVQBGbmGqVfB+zqgxjw@mail.gmail.com>
Cc: xrblock@ietf.org
Subject: Re: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jan 2012 01:34:46 -0000

Hi, Varun:
Please see my followup comments.

Regards!
-Qin
----- Original Message ----- 
From: "Varun Singh" <vsingh.ietf@gmail.com>
To: "Qin Wu" <bill.wu@huawei.com>
Cc: <xrblock@ietf.org>
Sent: Tuesday, January 17, 2012 6:40 PM
Subject: Re: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02


Hi Qin,

Comments inline.

On Tue, Jan 17, 2012 at 09:42, Qin Wu <bill.wu@huawei.com> wrote:
> Hi, Varun:
> I read your proposed change, please see my comments inline.
> ----- Original Message -----
> From: "Varun Singh" <vsingh.ietf@gmail.com>
> To: <xrblock@ietf.org>
> Sent: Wednesday, January 11, 2012 8:09 PM
> Subject: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02
>
>
>> Hi,
>>
>> I am sending the updates to mailing list so that the discussion can
>> take place before I post an updated draft.
>>
>> in -01, Section 1. Last para of introduction:
>> Complementary to or instead of the indication which packets were
>> discarded, an XR block is defined to indicate the number of bytes
>> discarded, per interval or for the duration of the session, similar
>> to other XR report blocks.
>>
>> Adding to that para in -02:
>> Alternatively, if the sender keeps a
>> history of the size of the packets reported in the measurement
>> interval then the sender can calculate the number of bytes discarded
>> from the information in the discard RLE block.
>>
>> - is this extra clarification needed?
>
> [Qin]: I think you don't need maintain the size for each packet, you only need to maintain
> the total size for all the received packet before the next packet is coming.
>

The receiver needs to maintain the total size (for interval and for
cumulative). However, the extra paragraph is to show that discarded
bytes can also be calculated from the Discard RLE encoding--if the
sender maintains the size of the sent packets. It can then add up the
size of packets marked in the RLE block using a lookup table.

[Qin]: Who calculates the size of packets? the reciever of dicard RLE block or the sender of byte dicarded block?
My understanding is it should be  the sender of byte dicarded block that calculates the size of packets.
Your bytes discarded block should always be sent with dicard RLE block in the same compound RTCP packet. 

Otherwise,  if the the reciever of dicard RLE block calculates the size of packets,
 the reciever of discard RLE block will be hard to calculate the size of packet if any discard RLE block is lost? 

>>
>> in -01, end of section 4.:
>> The 'number of bytes discarded' is a 32-bit unsigned integer value
>> indicating the total number of bytes discarded (I=11), or the number
>> of bytes discarded since the last RTCP XR Bytes Discarded block was
>> sent (I=10), or bytes discarded in a measurement interval (I=01)
>> [I-D.ietf-xrblock-rtcp-xr-meas-identity].
>>
>> Bytes Discarded Report Blocks SHOULD be sent in conjunction with an
>> RTCP RR as a compound RTCP packet.
>>
>> Updated it to:
>> The 'number of bytes discarded' is a 32-bit unsigned integer value
>> indicating the total number of bytes discarded. If the XR block is
>> not preceded by a measurement identity block
>> [I-D.ietf-xrblock-rtcp-xr-meas-identity] then the value indicates the
>> bytes lost from from the start of the session (I=11), or the number
>> of bytes discarded since the last RTCP XR Bytes Discarded block was
>> received (I=10).
>>
>> If the XR block follows a measurement identity block
>> [I-D.ietf-xrblock-rtcp-xr-meas-identity] in an RTCP RR packet then
>> the cumulative (I=11) and interval (I=10) correspond to the values in
>> the measurement block.
>>
>> Bytes Discarded Report Blocks SHOULD be sent in conjunction with an
>> RTCP RR as a compound RTCP packet.
>
> [Qin]: Does Bytes Discarded Report Blocks rely on measurement identity block or
> RTCP RR to calculate measurement interval? It is not clear to me.

If the discard block follows a measurement identity block then it must
use the measurement
information in the block. If the measurement identity block is not
present then it should use
the HSN (Seq No., RTP timestamp) in the previous RR containing the block and
the current RR to calculate the measurement interval. However, if the
information
from the previous RR is not available then the sender should ignore
the discard block.

[Qin]: That makes sense to me.


> If measurement identity block is present, Does Bytes Discarded Report Blocks
> need to be sent with an RTCP RR?
>
No. I can replace the last line with this:

If the receiver sends the Bytes Discarded Report Block without the
measurement identity block then the discard block SHOULD be sent in
conjunction with an RTCP RR as a compound RTCP packet.

[Qin]: Looks good to me.

>
>> - clarified what the sender could do if the measurement interval is
>> absent/present in the RTCP packet.
>> Note at the moment there are no normative keywords in the text.
>>
>> Possible clarification that can be added to the first para:
>> When the measurement block is absent, the sender SHOULD calculate the
>> duration of the interval using the RTP timestamps of the last reported
>> HSN and current HSN. If an RTCP RR packet is lost in between then the
>> assumption is wrong and the receiver SHOULD use the measurement block
>> for indicating precise durations.
>
> [Qin]: How do you guarantee the measurment information block will be sent to the receiever when RTCP RR is lost?

There is no guarantee. What I meant to say is that if the packet is
lost then the above assumption is wrong and the only way to overcome
the challenge is that the receiver should use the measurement block.


The question however is do we need to add such a clarification?

[Qin] What about measurement block is also lost? I think if any clarification is needed,
that should be how to deal with these failure cases.

> Are you assuming the measurment information block and RTCP RR will be sent in the separate compound RTCP packet?


>
>>
>> Cheers,
>> Varun
>>
>> --
>> http://www.netlab.tkk.fi/~varun/
>> _______________________________________________
>> xrblock mailing list
>> xrblock@ietf.org
>> https://www.ietf.org/mailman/listinfo/xrblock



-- 
http://www.netlab.tkk.fi/~varun/

From vsingh.ietf@gmail.com  Wed Jan 18 04:12:17 2012
Return-Path: <vsingh.ietf@gmail.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D73C21F87FB for <xrblock@ietfa.amsl.com>; Wed, 18 Jan 2012 04:12:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eZIPkczcvYCX for <xrblock@ietfa.amsl.com>; Wed, 18 Jan 2012 04:12:16 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2E80321F87FA for <xrblock@ietf.org>; Wed, 18 Jan 2012 04:12:16 -0800 (PST)
Received: by werp11 with SMTP id p11so1570013wer.31 for <xrblock@ietf.org>; Wed, 18 Jan 2012 04:12:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=60h5I8a4cfLhyQxvS/SXUFNWqiFv5jOGmc4dCEYfDRk=; b=N39nDHj1Ki9Kex9HnRvfQ1tsiuRx3PBp/vEiJIYfs+D6BAuP/8x4+1eeSQ1/0TUWPS YVucnwxgzeGKcd/JnqMO6+vWdpgs6FtBYEaYUeP459qayE6FOz7Qe8rvs+HMenJjeutw NQLIzZeMBeMLie23KIX8Tj1xYjrKguwf3BP1k=
Received: by 10.216.136.20 with SMTP id v20mr9381206wei.14.1326888735343; Wed, 18 Jan 2012 04:12:15 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.62.147 with HTTP; Wed, 18 Jan 2012 04:11:54 -0800 (PST)
In-Reply-To: <58EA66C004CC42338DB85F9C032C1CC3@china.huawei.com>
References: <CAEbPqrz05RAbaq7sNb+W09pZSJedn=iEW2Sf_BR3mRho5c=Tdg@mail.gmail.com> <54DEF8D9713A4424933422B86EAD700D@china.huawei.com> <CAEbPqrxUWFv642yVSQrnTuFBSeVFwk3pVQBGbmGqVfB+zqgxjw@mail.gmail.com> <58EA66C004CC42338DB85F9C032C1CC3@china.huawei.com>
From: Varun Singh <vsingh.ietf@gmail.com>
Date: Wed, 18 Jan 2012 14:11:54 +0200
Message-ID: <CAEbPqrw+jv_AcsA1NQwhUKfRTzUmqieLueGM5AhY69G9iEcTDA@mail.gmail.com>
To: Qin Wu <bill.wu@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: xrblock@ietf.org
Subject: Re: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jan 2012 12:12:17 -0000

Hi Qin,

responses inline. I have snipped the comments that were marked OK.

Cheers,
Varun

On Wed, Jan 18, 2012 at 03:34, Qin Wu <bill.wu@huawei.com> wrote:
> Hi, Varun:
> Please see my followup comments.
>
> Regards!
> -Qin

>>> Hi,
>>>
>>> I am sending the updates to mailing list so that the discussion can
>>> take place before I post an updated draft.
>>>
>>> in -01, Section 1. Last para of introduction:
>>> Complementary to or instead of the indication which packets were
>>> discarded, an XR block is defined to indicate the number of bytes
>>> discarded, per interval or for the duration of the session, similar
>>> to other XR report blocks.
>>>
>>> Adding to that para in -02:
>>> Alternatively, if the sender keeps a
>>> history of the size of the packets reported in the measurement
>>> interval then the sender can calculate the number of bytes discarded
>>> from the information in the discard RLE block.
>>>
>>> - is this extra clarification needed?
>>
>> [Qin]: I think you don't need maintain the size for each packet, you onl=
y need to maintain
>> the total size for all the received packet before the next packet is com=
ing.
>>
>
> The receiver needs to maintain the total size (for interval and for
> cumulative). However, the extra paragraph is to show that discarded
> bytes can also be calculated from the Discard RLE encoding--if the
> sender maintains the size of the sent packets. It can then add up the
> size of packets marked in the RLE block using a lookup table.
>
> [Qin]: Who calculates the size of packets? the reciever of dicard RLE blo=
ck or the sender of byte dicarded block?
> My understanding is it should be =A0the sender of byte dicarded block tha=
t calculates the size of packets.
> Your bytes discarded block should always be sent with dicard RLE block in=
 the same compound RTCP packet.
>

Bytes discarded is a complementary mechanism to Discard RLE. It is up
to the implementer to choose from: packets discarded, bytes discarded,
discarded RLE (for their use-case). Discarded RLE is like a superset
and with it the sender can calculate packets and bytes discarded (if
it knows the size of the packets). So there is no need to send bytes
discarded and RLE together. In Sec 5
(http://tools.ietf.org/html/draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-=
01#section-5.1)
there is clarification for media receivers and media senders.

>>
>>> - clarified what the sender could do if the measurement interval is
>>> absent/present in the RTCP packet.
>>> Note at the moment there are no normative keywords in the text.
>>>
>>> Possible clarification that can be added to the first para:
>>> When the measurement block is absent, the sender SHOULD calculate the
>>> duration of the interval using the RTP timestamps of the last reported
>>> HSN and current HSN. If an RTCP RR packet is lost in between then the
>>> assumption is wrong and the receiver SHOULD use the measurement block
>>> for indicating precise durations.
>>
>> [Qin]: How do you guarantee the measurment information block will be sen=
t to the receiever when RTCP RR is lost?
>
> There is no guarantee. What I meant to say is that if the packet is
> lost then the above assumption is wrong and the only way to overcome
> the challenge is that the receiver should use the measurement block.
>
>
> The question however is do we need to add such a clarification?
>
> [Qin] What about measurement block is also lost? I think if any clarifica=
tion is needed,
> that should be how to deal with these failure cases.


Case 1: XR Block + RTCP RR =3D the media sender can use previous RTCP
report to calculate interval
Case 2: XR Block + Measurement Identity =3D the media sender can use the
interval information from the meas id.
In all other cases, ignore the XR block.

Cheers,
Varun

From bill.wu@huawei.com  Wed Jan 18 18:01:27 2012
Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D203521F84B3 for <xrblock@ietfa.amsl.com>; Wed, 18 Jan 2012 18:01:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.217
X-Spam-Level: 
X-Spam-Status: No, score=-6.217 tagged_above=-999 required=5 tests=[AWL=0.382,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2n26Ev+M900t for <xrblock@ietfa.amsl.com>; Wed, 18 Jan 2012 18:01:27 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id A2C5121F84AA for <xrblock@ietf.org>; Wed, 18 Jan 2012 18:01:26 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LY000FNMW8XNS@szxga05-in.huawei.com> for xrblock@ietf.org; Thu, 19 Jan 2012 10:00:33 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LY0007YLW8XUT@szxga05-in.huawei.com> for xrblock@ietf.org; Thu, 19 Jan 2012 10:00:33 +0800 (CST)
Received: from szxeml212-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGK47071; Thu, 19 Jan 2012 09:59:33 +0800
Received: from SZXEML424-HUB.china.huawei.com (10.82.67.163) by szxeml212-edg.china.huawei.com (172.24.2.181) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 19 Jan 2012 09:59:27 +0800
Received: from w53375q (10.138.41.130) by szxeml424-hub.china.huawei.com (10.82.67.163) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 19 Jan 2012 09:59:24 +0800
Date: Thu, 19 Jan 2012 09:59:21 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Varun Singh <vsingh.ietf@gmail.com>
Message-id: <F2E27ABE99474D4EA46C65D578BA35B5@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <CAEbPqrz05RAbaq7sNb+W09pZSJedn=iEW2Sf_BR3mRho5c=Tdg@mail.gmail.com> <54DEF8D9713A4424933422B86EAD700D@china.huawei.com> <CAEbPqrxUWFv642yVSQrnTuFBSeVFwk3pVQBGbmGqVfB+zqgxjw@mail.gmail.com> <58EA66C004CC42338DB85F9C032C1CC3@china.huawei.com> <CAEbPqrw+jv_AcsA1NQwhUKfRTzUmqieLueGM5AhY69G9iEcTDA@mail.gmail.com>
Cc: xrblock@ietf.org
Subject: Re: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2012 02:01:27 -0000

Hi, Varun:
Please see one more additional comment below.
----- Original Message ----- 
From: "Varun Singh" <vsingh.ietf@gmail.com>
To: "Qin Wu" <bill.wu@huawei.com>
Cc: <xrblock@ietf.org>
Sent: Wednesday, January 18, 2012 8:11 PM
Subject: Re: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02


Hi Qin,

responses inline. I have snipped the comments that were marked OK.

Cheers,
Varun

On Wed, Jan 18, 2012 at 03:34, Qin Wu <bill.wu@huawei.com> wrote:
> Hi, Varun:
> Please see my followup comments.
>
> Regards!
> -Qin

>>> Hi,
>>>
>>> I am sending the updates to mailing list so that the discussion can
>>> take place before I post an updated draft.
>>>
>>> in -01, Section 1. Last para of introduction:
>>> Complementary to or instead of the indication which packets were
>>> discarded, an XR block is defined to indicate the number of bytes
>>> discarded, per interval or for the duration of the session, similar
>>> to other XR report blocks.
>>>
>>> Adding to that para in -02:
>>> Alternatively, if the sender keeps a
>>> history of the size of the packets reported in the measurement
>>> interval then the sender can calculate the number of bytes discarded
>>> from the information in the discard RLE block.
>>>
>>> - is this extra clarification needed?
>>
>> [Qin]: I think you don't need maintain the size for each packet, you only need to maintain
>> the total size for all the received packet before the next packet is coming.
>>
>
> The receiver needs to maintain the total size (for interval and for
> cumulative). However, the extra paragraph is to show that discarded
> bytes can also be calculated from the Discard RLE encoding--if the
> sender maintains the size of the sent packets. It can then add up the
> size of packets marked in the RLE block using a lookup table.
>
> [Qin]: Who calculates the size of packets? the reciever of dicard RLE block or the sender of byte dicarded block?
> My understanding is it should be the sender of byte dicarded block that calculates the size of packets.
> Your bytes discarded block should always be sent with dicard RLE block in the same compound RTCP packet.
>

Bytes discarded is a complementary mechanism to Discard RLE. It is up
to the implementer to choose from: packets discarded, bytes discarded,
discarded RLE (for their use-case). Discarded RLE is like a superset
and with it the sender can calculate packets and bytes discarded (if
it knows the size of the packets). So there is no need to send bytes
discarded and RLE together. In Sec 5
(http://tools.ietf.org/html/draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-01#section-5.1)
there is clarification for media receivers and media senders.

[Qin]: What if dicard RLE block is lost? I think if any dicard RLE block is lost, this will prevent you keeping on
calculating the total byte lost or packet lost. How do you deal with this case?

>>
>>> - clarified what the sender could do if the measurement interval is
>>> absent/present in the RTCP packet.
>>> Note at the moment there are no normative keywords in the text.
>>>
>>> Possible clarification that can be added to the first para:
>>> When the measurement block is absent, the sender SHOULD calculate the
>>> duration of the interval using the RTP timestamps of the last reported
>>> HSN and current HSN. If an RTCP RR packet is lost in between then the
>>> assumption is wrong and the receiver SHOULD use the measurement block
>>> for indicating precise durations.
>>
>> [Qin]: How do you guarantee the measurment information block will be sent to the receiever when RTCP RR is lost?
>
> There is no guarantee. What I meant to say is that if the packet is
> lost then the above assumption is wrong and the only way to overcome
> the challenge is that the receiver should use the measurement block.
>
>
> The question however is do we need to add such a clarification?
>
> [Qin] What about measurement block is also lost? I think if any clarification is needed,
> that should be how to deal with these failure cases.


Case 1: XR Block + RTCP RR = the media sender can use previous RTCP
report to calculate interval
Case 2: XR Block + Measurement Identity = the media sender can use the
interval information from the meas id.
In all other cases, ignore the XR block.

[Qin]: Looks reasonable to me.

Cheers,
Varun

From internet-drafts@ietf.org  Wed Jan 18 22:52:23 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EDF421F86B2; Wed, 18 Jan 2012 22:52:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gBE6TS7GmiWj; Wed, 18 Jan 2012 22:52:22 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4191511E8076; Wed, 18 Jan 2012 22:52:06 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20120119065206.30562.61410.idtracker@ietfa.amsl.com>
Date: Wed, 18 Jan 2012 22:52:06 -0800
Cc: xrblock@ietf.org
Subject: [xrblock] I-D Action: draft-ietf-xrblock-rtcp-xr-burst-gap-loss-01.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2012 06:52:23 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Metric Blocks for use with RTCP's Ext=
ended Report Framework Working Group of the IETF.

	Title           : RTCP XR Report Block for Burst/Gap Loss metric Reporting
	Author(s)       : Geoff Hunt
                          Alan Clark
                          Sunshine Zhang
                          Jing Zhao
                          Qin Wu
	Filename        : draft-ietf-xrblock-rtcp-xr-burst-gap-loss-01.txt
	Pages           : 17
	Date            : 2012-01-18

   This document defines an RTCP XR Report Block that allows the
   reporting of Burst and Gap Loss metrics for use in a range of RTP
   applications.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-xrblock-rtcp-xr-burst-gap-lo=
ss-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-xrblock-rtcp-xr-burst-gap-los=
s-01.txt


From internet-drafts@ietf.org  Wed Jan 18 22:57:42 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20FD321F8592; Wed, 18 Jan 2012 22:57:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.533
X-Spam-Level: 
X-Spam-Status: No, score=-102.533 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uk6pKJra8A8J; Wed, 18 Jan 2012 22:57:41 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 867FA21F857F; Wed, 18 Jan 2012 22:57:41 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20120119065741.31747.42048.idtracker@ietfa.amsl.com>
Date: Wed, 18 Jan 2012 22:57:41 -0800
Cc: xrblock@ietf.org
Subject: [xrblock] I-D Action: draft-ietf-xrblock-rtcp-xr-burst-gap-discard-01.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2012 06:57:42 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Metric Blocks for use with RTCP's Ext=
ended Report Framework Working Group of the IETF.

	Title           : RTCP XR Report Block for Burst/Gap Discard metric Report=
ing
	Author(s)       : Geoff Hunt
                          Alan Clark
                          Rachel Huang
                          Qin Wu
	Filename        : draft-ietf-xrblock-rtcp-xr-burst-gap-discard-01.txt
	Pages           : 16
	Date            : 2012-01-18

   This document defines an RTCP XR Report Block that allows the
   reporting of Burst and Gap Discard metrics for use in a range of RTP
   applications.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-xrblock-rtcp-xr-burst-gap-di=
scard-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-xrblock-rtcp-xr-burst-gap-dis=
card-01.txt


From vsingh.ietf@gmail.com  Wed Jan 18 23:50:12 2012
Return-Path: <vsingh.ietf@gmail.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70A7021F85D6 for <xrblock@ietfa.amsl.com>; Wed, 18 Jan 2012 23:50:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iEIm7uNez52D for <xrblock@ietfa.amsl.com>; Wed, 18 Jan 2012 23:50:11 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 12FD921F85CC for <xrblock@ietf.org>; Wed, 18 Jan 2012 23:50:10 -0800 (PST)
Received: by wgbdq11 with SMTP id dq11so3011772wgb.13 for <xrblock@ietf.org>; Wed, 18 Jan 2012 23:50:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=xLVnCAgDcpPucd0WNSQel3PYR58yGixu/VwoAO3gkes=; b=xHL1N5/jRQcgEYYjoN89o1zckDLwUZfpFu6gQHKdb2M5rIvPxEO/InEd4VAUs8Df/7 c3FVieSCeqZd7VAlFs7h+WH7Yrj9ZHCJz9ySB8iBTLngaUz8LDVNTsIYvqcJ4fdJjnfd HfL7TW3a3xZ5ss5uRSkcDzEFNRPm4indinw0g=
Received: by 10.180.82.5 with SMTP id e5mr36496790wiy.18.1326959410212; Wed, 18 Jan 2012 23:50:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.62.147 with HTTP; Wed, 18 Jan 2012 23:49:49 -0800 (PST)
In-Reply-To: <F2E27ABE99474D4EA46C65D578BA35B5@china.huawei.com>
References: <CAEbPqrz05RAbaq7sNb+W09pZSJedn=iEW2Sf_BR3mRho5c=Tdg@mail.gmail.com> <54DEF8D9713A4424933422B86EAD700D@china.huawei.com> <CAEbPqrxUWFv642yVSQrnTuFBSeVFwk3pVQBGbmGqVfB+zqgxjw@mail.gmail.com> <58EA66C004CC42338DB85F9C032C1CC3@china.huawei.com> <CAEbPqrw+jv_AcsA1NQwhUKfRTzUmqieLueGM5AhY69G9iEcTDA@mail.gmail.com> <F2E27ABE99474D4EA46C65D578BA35B5@china.huawei.com>
From: Varun Singh <vsingh.ietf@gmail.com>
Date: Thu, 19 Jan 2012 09:49:49 +0200
Message-ID: <CAEbPqrzZzn=oBgai3=1sk4CT-8GMRtnZ=+aSrokrSL=oZZgnkQ@mail.gmail.com>
To: Qin Wu <bill.wu@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: xrblock@ietf.org
Subject: Re: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2012 07:50:12 -0000

Hi Qin,

comment inline.

On Thu, Jan 19, 2012 at 03:59, Qin Wu <bill.wu@huawei.com> wrote:
> Hi, Varun:
> Please see one more additional comment below.
> ----- Original Message -----
> From: "Varun Singh" <vsingh.ietf@gmail.com>
> To: "Qin Wu" <bill.wu@huawei.com>
> Cc: <xrblock@ietf.org>
> Sent: Wednesday, January 18, 2012 8:11 PM
> Subject: Re: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02
>
>
> Hi Qin,
>
> responses inline. I have snipped the comments that were marked OK.
>
> Cheers,
> Varun
>
> On Wed, Jan 18, 2012 at 03:34, Qin Wu <bill.wu@huawei.com> wrote:
>> Hi, Varun:
>> Please see my followup comments.
>>
>> Regards!
>> -Qin
>
>>>> Hi,
>>>>
>>>> I am sending the updates to mailing list so that the discussion can
>>>> take place before I post an updated draft.
>>>>
>>>> in -01, Section 1. Last para of introduction:
>>>> Complementary to or instead of the indication which packets were
>>>> discarded, an XR block is defined to indicate the number of bytes
>>>> discarded, per interval or for the duration of the session, similar
>>>> to other XR report blocks.
>>>>
>>>> Adding to that para in -02:
>>>> Alternatively, if the sender keeps a
>>>> history of the size of the packets reported in the measurement
>>>> interval then the sender can calculate the number of bytes discarded
>>>> from the information in the discard RLE block.
>>>>
>>>> - is this extra clarification needed?
>>>
>>> [Qin]: I think you don't need maintain the size for each packet, you only need to maintain
>>> the total size for all the received packet before the next packet is coming.
>>>
>>
>> The receiver needs to maintain the total size (for interval and for
>> cumulative). However, the extra paragraph is to show that discarded
>> bytes can also be calculated from the Discard RLE encoding--if the
>> sender maintains the size of the sent packets. It can then add up the
>> size of packets marked in the RLE block using a lookup table.
>>
>> [Qin]: Who calculates the size of packets? the reciever of dicard RLE block or the sender of byte dicarded block?
>> My understanding is it should be the sender of byte dicarded block that calculates the size of packets.
>> Your bytes discarded block should always be sent with dicard RLE block in the same compound RTCP packet.
>>
>
> Bytes discarded is a complementary mechanism to Discard RLE. It is up
> to the implementer to choose from: packets discarded, bytes discarded,
> discarded RLE (for their use-case). Discarded RLE is like a superset
> and with it the sender can calculate packets and bytes discarded (if
> it knows the size of the packets). So there is no need to send bytes
> discarded and RLE together. In Sec 5
> (http://tools.ietf.org/html/draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-01#section-5.1)
> there is clarification for media receivers and media senders.
>
> [Qin]: What if dicard RLE block is lost?
>

I do not think the media sender can with 100% certainty detect that an
RLE block was lost. If the receiver sends an RLE block for every
interval then the media sender could detect a missing interval from
the sequence numbers that were not reported in the RLE. However, which
XR blocks are reported in an interval depends on the
implementation/logic at the receiver. For instance, if all packets are
received then there is no need to send the RLE block. Moreover, if all
packets are discarded then sending the RLE block has high overhead and
the receiver may use the Packets Discarded XR Block.

>[Qin]: I think if any dicard RLE block is lost, this will prevent you keeping on
> calculating the total byte lost or packet lost. How do you deal with this case?

To know an RTCP feedback packet is lost, the media sender would have
received a new RTCP feedback packet. The media sender may use the
information in the new RTCP report to react to congestion/scheduling.
In the case of monitoring or storing metrics it is a problem because
the media sender or the middlebox has a no information for the missing
interval and could mark the bytes/packet discarded in the interval as
"not enough information".


-- 
http://www.netlab.tkk.fi/~varun/

From zhaojing@sttri.com.cn  Thu Jan 19 00:30:32 2012
Return-Path: <zhaojing@sttri.com.cn>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1B7321F867C for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 00:30:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.991
X-Spam-Level: *
X-Spam-Status: No, score=1.991 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_NJABL_PROXY=1.643]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uR7upLn7Dy7h for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 00:30:32 -0800 (PST)
Received: from corp.21cn.com (corp.forptr.21cn.com [121.14.129.37]) by ietfa.amsl.com (Postfix) with ESMTP id E9B0E21F8604 for <xrblock@ietf.org>; Thu, 19 Jan 2012 00:30:30 -0800 (PST)
Received: from ip?218.2.129.2? (entas8.inner-hermes.com [10.27.101.8]) by corp.21cn.com (HERMES) with ESMTP id EA4ACAC03A for <xrblock@ietf.org>; Thu, 19 Jan 2012 16:30:24 +0800 (CST)
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_IP: wmail.10.27.101.8.1548099946
HMM_SOURCE_TYPE: WEBMAIL
Received: from ip<218.2.129.2> ([218.2.129.2]) by 21CN-ent8(Yuwen filter gate 10.27.101.8) with ESMTP id 1326961825.10292 for xrblock@ietf.org ; Thu Jan 19 16:30:28 2012
0/X-Total-Score: 3:
X-FILTER-SCORE: to=<xrblock@ietf.org>, score=<1326961828M/MM5MuZ9q/5zeYMM9MMqMDBBOB8GkMDOgt/BBkBBMBB> 
Date: Thu, 19 Jan 2012 16:30:24 +0800 (CST)
From: zhaojing@sttri.com.cn
To: xrblock <xrblock@ietf.org>
Message-ID: <14878230.5711326961824918.JavaMail.root@ent11>
MIME-Version: 1.0
Content-Type: multipart/mixed;  boundary="----=_Part_619_29833215.1326961824691"
HMM_WEBCLN_IP: 218.2.129.2
X-HERMES-SENDMODE: normal
Subject: [xrblock] Update of Burst Gap related drafts
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2012 08:30:32 -0000

------=_Part_619_29833215.1326961824691
Content-Type: text/html;charset=UTF-8
Content-Transfer-Encoding: base64

PGh0bWw+CiA8aGVhZD48L2hlYWQ+CiA8Ym9keT4KICA8ZGl2PgogICA8Zm9udCBmYWNlPSJUaW1l
cyBOZXcgUm9tYW4iPkhpOjwvZm9udD4gCiAgPC9kaXY+IAogIDxkaXY+CiAgIDxmb250IGZhY2U9
IlRpbWVzIE5ldyBSb21hbiI+UWluIGFuZCB1cyBoYXZlIHdvcmtlZCBvdXQgdGhlIHJldmlzaW9u
IG9mIEJ1cnN0IGdhcCByZWxhdGVkIGRyYWZ0cy4gVGhlIG5ldyB1cGRhdGVzJm5ic3A7YXJlIGF2
YWlsYWJsZSBhdDo8L2ZvbnQ+IAogIDwvZGl2PiAKICA8ZGl2PgogICA8Zm9udCBmYWNlPSJUaW1l
cyBOZXcgUm9tYW4iPmEuIEJ1cnN0IEdhcCBMb3NzIERyYWZ0PC9mb250PiAKICA8L2Rpdj4gCiAg
PGRpdj4KICAgPGZvbnQgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj48YSBocmVmPSJodHRwOi8vdG9v
bHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLXhyYmxvY2stcnRjcC14ci1idXJzdC1nYXAtbG9z
cy0wMSI+aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi14cmJsb2NrLXJ0Y3At
eHItYnVyc3QtZ2FwLWxvc3MtMDE8L2E+PC9mb250PiAKICA8L2Rpdj4gCiAgPGRpdj4KICAgPGZv
bnQgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj5iLiBCdXJzdCBHYXAgRGlzY2FyZCBEcmFmdDwvZm9u
dD4gCiAgPC9kaXY+IAogIDxkaXY+CiAgIDxmb250IGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+PGEg
aHJlZj0iaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi14cmJsb2NrLXJ0Y3At
eHItYnVyc3QtZ2FwLWRpc2NhcmQtMDEiPmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0
LWlldGYteHJibG9jay1ydGNwLXhyLWJ1cnN0LWdhcC1kaXNjYXJkLTAxPC9hPjwvZm9udD4gCiAg
PC9kaXY+IAogIDxkaXY+CiAgIDxmb250IGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+QWxzbyB3ZSB1
cGRhdGUgU3VtbWFyeSBTdGF0aXN0aWNzIE1ldHJpY3MgUmVwb3J0aW5nIGRyYWZ0KGkuZS4sZHJh
ZnQtem9ybi14cmJsb2NrLXJ0Y3AteHItYWwtc3RhdCk8L2ZvbnQ+IAogIDwvZGl2PiAKICA8ZGl2
PgogICA8Zm9udCBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPnRvIGdldCBhbGlnbm1lbnQgd2l0aCB0
aGUgYWJvdmUgdHdvIGRyYWZ0cy48L2ZvbnQ+IAogIDwvZGl2PiAKICA8ZGl2PgogICA8Zm9udCBm
YWNlPSJUaW1lcyBOZXcgUm9tYW4iPjwvZm9udD4gCiAgPC9kaXY+IAogIDxkaXY+CiAgIDxmb250
IGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+V2UgYmVsaWV2ZSB0aGVzZSBkcmFmdHMgaGF2ZSByZXNs
b3ZlZCB0aGUgY29tbWVudHMgcmFpc2VkIGluIHRoZSBUYWlwZWkgbWVldGluZyBhbmQgbGlrZSB0
byBzZWUgdGhlbTwvZm9udD4gCiAgPC9kaXY+IAogIDxkaXY+CiAgIDxmb250IGZhY2U9IlRpbWVz
IE5ldyBSb21hbiI+bW92ZSBmb3J3YXJkLjwvZm9udD4gCiAgPC9kaXY+IAogIDxkaXY+CiAgIDxm
b250IGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+PC9mb250PiAKICA8L2Rpdj4gCiAgPGRpdj4KICAg
PGZvbnQgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj5DaGVlcnMhPC9mb250PgogIDwvZGl2PiAKICA8
ZGl2PgogICA8Zm9udCBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPkppbmcgPC9mb250PmFuZCBTdW5z
aGluZQogIDwvZGl2PiAKICA8ZGl2PgogICBTaGFuZyBSZXNlYXJjaCBJbnN0aXR1dGUgb2YgQ2hp
bmEgVGVsZWNvbQogIDwvZGl2PgogPC9ib2R5Pgo8L2h0bWw+
------=_Part_619_29833215.1326961824691--


From bill.wu@huawei.com  Thu Jan 19 00:42:12 2012
Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7E6021F84CE for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 00:42:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.231
X-Spam-Level: 
X-Spam-Status: No, score=-6.231 tagged_above=-999 required=5 tests=[AWL=0.368,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TCMWrnJHQUAw for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 00:42:11 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id EB46321F84B8 for <xrblock@ietf.org>; Thu, 19 Jan 2012 00:42:10 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LY1004AJES8KX@szxga04-in.huawei.com> for xrblock@ietf.org; Thu, 19 Jan 2012 16:40:56 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LY100LF2ES7I3@szxga04-in.huawei.com> for xrblock@ietf.org; Thu, 19 Jan 2012 16:40:56 +0800 (CST)
Received: from szxeml201-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGM96167; Thu, 19 Jan 2012 16:40:55 +0800
Received: from SZXEML405-HUB.china.huawei.com (10.82.67.60) by szxeml201-edg.china.huawei.com (172.24.2.39) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 19 Jan 2012 16:40:47 +0800
Received: from w53375q (10.138.41.130) by szxeml405-hub.china.huawei.com (10.82.67.60) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 19 Jan 2012 16:40:50 +0800
Date: Thu, 19 Jan 2012 16:40:49 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: xrblock@ietf.org
Message-id: <A7739442AE754F4DA0784A19ECEC7B86@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <20120119070400.1374.48525.idtracker@ietfa.amsl.com>
Subject: Re: [xrblock] I-D Action: draft-zorn-xrblock-rtcp-xr-al-stat-04.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2012 08:42:12 -0000

Hi,
A minor update to draft-zorn-xrblock-rtcp-xr-al-stat which is used to get consistent with Burst Gap related draft.
This draft missed the discussion due to presentation timeout  in the last IETF meeting. However this draft provides calculation method
for the derived metric listed in the two burst gap related draft and also defines RTCP XR packet format to carry these derived 
metric.
I like to see WG adopt this draft as work item or adopt a milestone to link to this draft. 
Any review and comments are welcome.

Regards!
-Qin
----- Original Message ----- 
From: <internet-drafts@ietf.org>
To: <i-d-announce@ietf.org>
Sent: Thursday, January 19, 2012 3:04 PM
Subject: I-D Action: draft-zorn-xrblock-rtcp-xr-al-stat-04.txt


> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> Title           : RTCP XR for Summary Statistics Metrics Reporting
> Author(s)       : Glen Zorn
>                          Roland Schott
>                          Qin Wu
>                          Rachel Huang
> Filename        : draft-zorn-xrblock-rtcp-xr-al-stat-04.txt
> Pages           : 15
> Date            : 2012-01-18
> 
>   This document defines three RTCP XR Report Blocks and associated SDP
>   parameters that allows the reporting of loss, duplication and discard
>   summary statistics metrics for use in a range of RTP applications.
> 
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-zorn-xrblock-rtcp-xr-al-stat-04.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-zorn-xrblock-rtcp-xr-al-stat-04.txt
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>

From bill.wu@huawei.com  Thu Jan 19 01:07:35 2012
Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73BC321F86A5 for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 01:07:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.245
X-Spam-Level: 
X-Spam-Status: No, score=-6.245 tagged_above=-999 required=5 tests=[AWL=0.354,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ycYCTHOnfDJd for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 01:07:34 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 0C57F21F86A9 for <xrblock@ietf.org>; Thu, 19 Jan 2012 01:07:34 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LY100EJRFZNCN@szxga03-in.huawei.com> for xrblock@ietf.org; Thu, 19 Jan 2012 17:07:00 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LY100AEWFZNGW@szxga03-in.huawei.com> for xrblock@ietf.org; Thu, 19 Jan 2012 17:06:59 +0800 (CST)
Received: from szxeml210-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGM97895; Thu, 19 Jan 2012 17:06:59 +0800
Received: from SZXEML410-HUB.china.huawei.com (10.82.67.137) by szxeml210-edg.china.huawei.com (172.24.2.183) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 19 Jan 2012 17:06:52 +0800
Received: from w53375q (10.138.41.130) by szxeml410-hub.china.huawei.com (10.82.67.137) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 19 Jan 2012 17:06:47 +0800
Date: Thu, 19 Jan 2012 17:06:46 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Varun Singh <vsingh.ietf@gmail.com>
Message-id: <668E248B26E8402DA6E07957B288A094@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <CAEbPqrz05RAbaq7sNb+W09pZSJedn=iEW2Sf_BR3mRho5c=Tdg@mail.gmail.com> <54DEF8D9713A4424933422B86EAD700D@china.huawei.com> <CAEbPqrxUWFv642yVSQrnTuFBSeVFwk3pVQBGbmGqVfB+zqgxjw@mail.gmail.com> <58EA66C004CC42338DB85F9C032C1CC3@china.huawei.com> <CAEbPqrw+jv_AcsA1NQwhUKfRTzUmqieLueGM5AhY69G9iEcTDA@mail.gmail.com> <F2E27ABE99474D4EA46C65D578BA35B5@china.huawei.com> <CAEbPqrzZzn=oBgai3=1sk4CT-8GMRtnZ=+aSrokrSL=oZZgnkQ@mail.gmail.com>
Cc: xrblock@ietf.org
Subject: Re: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2012 09:07:35 -0000

Hi, Varun:
----- Original Message ----- 
From: "Varun Singh" <vsingh.ietf@gmail.com>
To: "Qin Wu" <bill.wu@huawei.com>
Cc: <xrblock@ietf.org>
Sent: Thursday, January 19, 2012 3:49 PM
Subject: Re: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02


> Hi Qin,
> 
> comment inline.
> 
> On Thu, Jan 19, 2012 at 03:59, Qin Wu <bill.wu@huawei.com> wrote:
>> Hi, Varun:
>> Please see one more additional comment below.
>> ----- Original Message -----
>> From: "Varun Singh" <vsingh.ietf@gmail.com>
>> To: "Qin Wu" <bill.wu@huawei.com>
>> Cc: <xrblock@ietf.org>
>> Sent: Wednesday, January 18, 2012 8:11 PM
>> Subject: Re: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02
>>
>>
>> Hi Qin,
>>
>> responses inline. I have snipped the comments that were marked OK.
>>
>> Cheers,
>> Varun
>>
>> On Wed, Jan 18, 2012 at 03:34, Qin Wu <bill.wu@huawei.com> wrote:
>>> Hi, Varun:
>>> Please see my followup comments.
>>>
>>> Regards!
>>> -Qin
>>
>>>>> Hi,
>>>>>
>>>>> I am sending the updates to mailing list so that the discussion can
>>>>> take place before I post an updated draft.
>>>>>
>>>>> in -01, Section 1. Last para of introduction:
>>>>> Complementary to or instead of the indication which packets were
>>>>> discarded, an XR block is defined to indicate the number of bytes
>>>>> discarded, per interval or for the duration of the session, similar
>>>>> to other XR report blocks.
>>>>>
>>>>> Adding to that para in -02:
>>>>> Alternatively, if the sender keeps a
>>>>> history of the size of the packets reported in the measurement
>>>>> interval then the sender can calculate the number of bytes discarded
>>>>> from the information in the discard RLE block.
>>>>>
>>>>> - is this extra clarification needed?
>>>>
>>>> [Qin]: I think you don't need maintain the size for each packet, you only need to maintain
>>>> the total size for all the received packet before the next packet is coming.
>>>>
>>>
>>> The receiver needs to maintain the total size (for interval and for
>>> cumulative). However, the extra paragraph is to show that discarded
>>> bytes can also be calculated from the Discard RLE encoding--if the
>>> sender maintains the size of the sent packets. It can then add up the
>>> size of packets marked in the RLE block using a lookup table.
>>>
>>> [Qin]: Who calculates the size of packets? the reciever of dicard RLE block or the sender of byte dicarded block?
>>> My understanding is it should be the sender of byte dicarded block that calculates the size of packets.
>>> Your bytes discarded block should always be sent with dicard RLE block in the same compound RTCP packet.
>>>
>>
>> Bytes discarded is a complementary mechanism to Discard RLE. It is up
>> to the implementer to choose from: packets discarded, bytes discarded,
>> discarded RLE (for their use-case). Discarded RLE is like a superset
>> and with it the sender can calculate packets and bytes discarded (if
>> it knows the size of the packets). So there is no need to send bytes
>> discarded and RLE together. In Sec 5
>> (http://tools.ietf.org/html/draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-01#section-5.1)
>> there is clarification for media receivers and media senders.
>>
>> [Qin]: What if dicard RLE block is lost?
>>
> 
> I do not think the media sender can with 100% certainty detect that an
> RLE block was lost. If the receiver sends an RLE block for every
> interval then the media sender could detect a missing interval from
> the sequence numbers that were not reported in the RLE. However, which
> XR blocks are reported in an interval depends on the
> implementation/logic at the receiver. For instance, if all packets are
> received then there is no need to send the RLE block. Moreover, if all
> packets are discarded then sending the RLE block has high overhead and
> the receiver may use the Packets Discarded XR Block.

[Qin]: No doubt about this.
my point is if any discard RLE block is lost, the media sender can not calculate the  accumulative total byte discard from  the lost discard RLE block.

But if the media receiver generate byte discard block and discard RLE block, you don't
have such issue since byte dicard block can be generated by media receiver based on associated discard RLE 
block which has not been sent.

Another issue I am thinking is are you assuming each discarded data packet you are tracking is equally size packet, otherwise, how do
you calculate the total discared packet size.


>>[Qin]: I think if any dicard RLE block is lost, this will prevent you keeping on
>> calculating the total byte lost or packet lost. How do you deal with this case?

> To know an RTCP feedback packet is lost, the media sender would have
> received a new RTCP feedback packet. The media sender may use the
> information in the new RTCP report to react to congestion/scheduling.
> In the case of monitoring or storing metrics it is a problem because
> the media sender or the middlebox has a no information for the missing
> interval and could mark the bytes/packet discarded in the interval as
> "not enough information".

[Qin]: That's a good point. That is to say monitoring and congestion control has different requirements for gathering
statistics information and dealing with these information.

> 
> -- 
> http://www.netlab.tkk.fi/~varun/
>

From bill.wu@huawei.com  Thu Jan 19 01:15:33 2012
Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D443C21F86B3 for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 01:15:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.956
X-Spam-Level: 
X-Spam-Status: No, score=-5.956 tagged_above=-999 required=5 tests=[AWL=0.042,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_24=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fCLDPaYC1vWG for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 01:15:33 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 67BFE21F86B2 for <xrblock@ietf.org>; Thu, 19 Jan 2012 01:15:32 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LY100ENGGBV1I@szxga03-in.huawei.com> for xrblock@ietf.org; Thu, 19 Jan 2012 17:14:19 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LY100A73GBLGW@szxga03-in.huawei.com> for xrblock@ietf.org; Thu, 19 Jan 2012 17:14:19 +0800 (CST)
Received: from szxeml213-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGM98430; Thu, 19 Jan 2012 17:14:17 +0800
Received: from SZXEML414-HUB.china.huawei.com (10.82.67.153) by szxeml213-edg.china.huawei.com (172.24.2.30) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 19 Jan 2012 17:14:09 +0800
Received: from w53375q (10.138.41.130) by SZXEML414-HUB.china.huawei.com (10.82.67.153) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 19 Jan 2012 17:14:43 +0800
Date: Thu, 19 Jan 2012 17:14:03 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: zhaojing@sttri.com.cn, xrblock <xrblock@ietf.org>
Message-id: <D7DE4D0D99CF4CE8B587C789E0EB985E@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: multipart/alternative; boundary="Boundary_(ID_LdVBz+8isqESJDaJCF8CZw)"
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <14878230.5711326961824918.JavaMail.root@ent11>
Subject: Re: [xrblock] Update of Burst Gap related drafts
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2012 09:15:34 -0000

--Boundary_(ID_LdVBz+8isqESJDaJCF8CZw)
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: 7BIT

Hi,Jing and Sunshine:
I agree the proposed change in the burst gap loss draft addresses the comments in the last meeting.
Also the proposed change in the burst gap discard looks good to me since burst gap discard
block is decoupled from burst gap loss block and does not need to rely on burst gap loss block
to calculate derived metric. That's a big benefit I can see.

Regards!
-Qin
  ----- Original Message ----- 
  From: zhaojing@sttri.com.cn 
  To: xrblock 
  Sent: Thursday, January 19, 2012 4:30 PM
  Subject: [xrblock] Update of Burst Gap related drafts


  Hi: 
  Qin and us have worked out the revision of Burst gap related drafts. The new updates are available at: 
  a. Burst Gap Loss Draft 
  http://tools.ietf.org/html/draft-ietf-xrblock-rtcp-xr-burst-gap-loss-01 
  b. Burst Gap Discard Draft 
  http://tools.ietf.org/html/draft-ietf-xrblock-rtcp-xr-burst-gap-discard-01 
  Also we update Summary Statistics Metrics Reporting draft(i.e.,draft-zorn-xrblock-rtcp-xr-al-stat) 
  to get alignment with the above two drafts. 
  We believe these drafts have resloved the comments raised in the Taipei meeting and like to see them 
  move forward. 
  Cheers! 
  Jing and Sunshine 
  Shang Research Institute of China Telecom 


------------------------------------------------------------------------------


  _______________________________________________
  xrblock mailing list
  xrblock@ietf.org
  https://www.ietf.org/mailman/listinfo/xrblock

--Boundary_(ID_LdVBz+8isqESJDaJCF8CZw)
Content-type: text/html; charset=UTF-8
Content-transfer-encoding: base64

77u/PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9u
YWwvL0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0
PXV0Zi04IiBodHRwLWVxdWl2PUNvbnRlbnQtVHlwZT4NCjxNRVRBIG5hbWU9R0VORVJBVE9SIGNv
bnRlbnQ9Ik1TSFRNTCA4LjAwLjYwMDEuMTkxNzAiPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+
DQo8Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPkhpLEppbmcgYW5kIFN1bnNoaW5lOjwvRElW
Pg0KPERJVj5JJm5ic3A7YWdyZWUgdGhlIHByb3Bvc2VkIGNoYW5nZSBpbiB0aGUgYnVyc3QgZ2Fw
IGxvc3MgZHJhZnQgYWRkcmVzc2VzIHRoZSANCmNvbW1lbnRzIGluIHRoZSBsYXN0IG1lZXRpbmcu
PC9ESVY+DQo8RElWPkFsc28gdGhlIHByb3Bvc2VkIGNoYW5nZSBpbiB0aGUgYnVyc3QgZ2FwIGRp
c2NhcmQgbG9va3MgZ29vZCB0byBtZSBzaW5jZSANCmJ1cnN0IGdhcCBkaXNjYXJkPC9ESVY+DQo8
RElWPmJsb2NrIGlzIGRlY291cGxlZCBmcm9tIGJ1cnN0IGdhcCBsb3NzIGJsb2NrIGFuZCBkb2Vz
IG5vdCBuZWVkIHRvIHJlbHkgb24gDQpidXJzdCBnYXAgbG9zcyBibG9jazwvRElWPg0KPERJVj50
byBjYWxjdWxhdGUgZGVyaXZlZCBtZXRyaWMuIFRoYXQncyBhIGJpZyBiZW5lZml0IEkgY2FuIHNl
ZS48L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPlJlZ2FyZHMhPC9ESVY+DQo8RElWPi1R
aW48L0RJVj4NCjxCTE9DS1FVT1RFIA0Kc3R5bGU9IkJPUkRFUi1MRUZUOiAjMDAwMDAwIDJweCBz
b2xpZDsgUEFERElORy1MRUZUOiA1cHg7IFBBRERJTkctUklHSFQ6IDBweDsgTUFSR0lOLUxFRlQ6
IDVweDsgTUFSR0lOLVJJR0hUOiAwcHgiPg0KICA8RElWIHN0eWxlPSJGT05UOiA5cHQg5a6L5L2T
Ij4tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIDwvRElWPg0KICA8RElWIHN0eWxlPSJGT05U
OiA5cHQg5a6L5L2TOyBCQUNLR1JPVU5EOiAjZTRlNGU0OyBmb250LWNvbG9yOiBibGFjayI+PEI+
RnJvbTo8L0I+IA0KICA8QSB0aXRsZT16aGFvamluZ0BzdHRyaS5jb20uY24gDQogIGhyZWY9Im1h
aWx0bzp6aGFvamluZ0BzdHRyaS5jb20uY24iPnpoYW9qaW5nQHN0dHJpLmNvbS5jbjwvQT4gPC9E
SVY+DQogIDxESVYgc3R5bGU9IkZPTlQ6IDlwdCDlrovkvZMiPjxCPlRvOjwvQj4gPEEgdGl0bGU9
eHJibG9ja0BpZXRmLm9yZyANCiAgaHJlZj0ibWFpbHRvOnhyYmxvY2tAaWV0Zi5vcmciPnhyYmxv
Y2s8L0E+IDwvRElWPg0KICA8RElWIHN0eWxlPSJGT05UOiA5cHQg5a6L5L2TIj48Qj5TZW50Ojwv
Qj4gVGh1cnNkYXksIEphbnVhcnkgMTksIDIwMTIgNDozMCANClBNPC9ESVY+DQogIDxESVYgc3R5
bGU9IkZPTlQ6IDlwdCDlrovkvZMiPjxCPlN1YmplY3Q6PC9CPiBbeHJibG9ja10gVXBkYXRlIG9m
IEJ1cnN0IEdhcCANCiAgcmVsYXRlZCBkcmFmdHM8L0RJVj4NCiAgPERJVj48QlI+PC9ESVY+DQog
IDxESVY+PEZPTlQgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj5IaTo8L0ZPTlQ+IDwvRElWPg0KICA8
RElWPjxGT05UIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+UWluIGFuZCB1cyBoYXZlIHdvcmtlZCBv
dXQgdGhlIHJldmlzaW9uIG9mIA0KICBCdXJzdCBnYXAgcmVsYXRlZCBkcmFmdHMuIFRoZSBuZXcg
dXBkYXRlcyZuYnNwO2FyZSBhdmFpbGFibGUgYXQ6PC9GT05UPiA8L0RJVj4NCiAgPERJVj48Rk9O
VCBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPmEuIEJ1cnN0IEdhcCBMb3NzIERyYWZ0PC9GT05UPiA8
L0RJVj4NCiAgPERJVj48Rk9OVCBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPjxBIA0KICBocmVmPSJo
dHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLXhyYmxvY2stcnRjcC14ci1idXJz
dC1nYXAtbG9zcy0wMSI+aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi14cmJs
b2NrLXJ0Y3AteHItYnVyc3QtZ2FwLWxvc3MtMDE8L0E+PC9GT05UPiANCiAgPC9ESVY+DQogIDxE
SVY+PEZPTlQgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj5iLiBCdXJzdCBHYXAgRGlzY2FyZCBEcmFm
dDwvRk9OVD4gPC9ESVY+DQogIDxESVY+PEZPTlQgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj48QSAN
CiAgaHJlZj0iaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi14cmJsb2NrLXJ0
Y3AteHItYnVyc3QtZ2FwLWRpc2NhcmQtMDEiPmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2Ry
YWZ0LWlldGYteHJibG9jay1ydGNwLXhyLWJ1cnN0LWdhcC1kaXNjYXJkLTAxPC9BPjwvRk9OVD4g
DQogIDwvRElWPg0KICA8RElWPjxGT05UIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+QWxzbyB3ZSB1
cGRhdGUgU3VtbWFyeSBTdGF0aXN0aWNzIE1ldHJpY3MgDQogIFJlcG9ydGluZyBkcmFmdChpLmUu
LGRyYWZ0LXpvcm4teHJibG9jay1ydGNwLXhyLWFsLXN0YXQpPC9GT05UPiA8L0RJVj4NCiAgPERJ
Vj48Rk9OVCBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPnRvIGdldCBhbGlnbm1lbnQgd2l0aCB0aGUg
YWJvdmUgdHdvIA0KICBkcmFmdHMuPC9GT05UPiA8L0RJVj4NCiAgPERJVj48Rk9OVCBmYWNlPSJU
aW1lcyBOZXcgUm9tYW4iPjwvRk9OVD48L0RJVj4NCiAgPERJVj48Rk9OVCBmYWNlPSJUaW1lcyBO
ZXcgUm9tYW4iPldlIGJlbGlldmUgdGhlc2UgZHJhZnRzIGhhdmUgcmVzbG92ZWQgdGhlIA0KICBj
b21tZW50cyByYWlzZWQgaW4gdGhlIFRhaXBlaSBtZWV0aW5nIGFuZCBsaWtlIHRvIHNlZSB0aGVt
PC9GT05UPiA8L0RJVj4NCiAgPERJVj48Rk9OVCBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPm1vdmUg
Zm9yd2FyZC48L0ZPTlQ+IDwvRElWPg0KICA8RElWPjxGT05UIGZhY2U9IlRpbWVzIE5ldyBSb21h
biI+PC9GT05UPjwvRElWPg0KICA8RElWPjxGT05UIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+Q2hl
ZXJzITwvRk9OVD4gPC9ESVY+DQogIDxESVY+PEZPTlQgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj5K
aW5nIDwvRk9OVD5hbmQgU3Vuc2hpbmUgPC9ESVY+DQogIDxESVY+U2hhbmcgUmVzZWFyY2ggSW5z
dGl0dXRlIG9mIENoaW5hIFRlbGVjb20gPC9ESVY+DQogIDxQPg0KICA8SFI+DQoNCiAgPFA+PC9Q
Pl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPEJSPnhyYmxv
Y2sgbWFpbGluZyANCiAgbGlzdDxCUj54cmJsb2NrQGlldGYub3JnPEJSPmh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8veHJibG9jazxCUj48L0JMT0NLUVVPVEU+PC9CT0RZPjwv
SFRNTD4NCg==

--Boundary_(ID_LdVBz+8isqESJDaJCF8CZw)--

From shida@ntt-at.com  Thu Jan 19 03:59:19 2012
Return-Path: <shida@ntt-at.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7082921F8573 for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 03:59:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.851
X-Spam-Level: 
X-Spam-Status: No, score=-99.851 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jZ+nvglI1PbE for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 03:59:19 -0800 (PST)
Received: from gator465.hostgator.com (gator465.hostgator.com [69.56.174.130]) by ietfa.amsl.com (Postfix) with ESMTP id 0BCC321F8572 for <xrblock@ietf.org>; Thu, 19 Jan 2012 03:59:18 -0800 (PST)
Received: from [125.197.253.88] (port=52588 helo=[192.168.1.18]) by gator465.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <shida@ntt-at.com>) id 1RnqeD-00039S-7i for xrblock@ietf.org; Thu, 19 Jan 2012 05:59:17 -0600
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1251.1)
From: Shida Schubert <shida@ntt-at.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C06283BBB@xmb-sjc-234.amer.cisco.com>
Date: Thu, 19 Jan 2012 20:58:57 +0900
Content-Transfer-Encoding: 7bit
Message-Id: <31A44220-52DD-44AF-B931-5C50D888E26E@ntt-at.com>
References: <340EB250-499C-45C1-871E-936A2D0783A3@ntt-at.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C06283BBB@xmb-sjc-234.amer.cisco.com>
To: xrblock <xrblock@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator465.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ntt-at.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: fl1-125-197-253-88.tky.mesh.ad.jp ([192.168.1.18]) [125.197.253.88]:52588
X-Source-Auth: shida@agnada.com
X-Email-Count: 1
X-Source-Cap: c3NoaWRhO3NzaGlkYTtnYXRvcjQ2NS5ob3N0Z2F0b3IuY29t
Subject: [xrblock] Poll for progressing the QoE
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2012 11:59:19 -0000

All;

Although a poll for draft-wu-xrblock-rtcp-xr-quality-monitoring ended in
favor of adopting the draft, the comments provided by Colin are worth
noting as we move forward.

I do have some questions which I think will help us clarify 
the way forward. 

A. There are three segment types defined (1. each media 
   sent in separate RTP stream, 2. Layered video session, 
   3. Multi-channel audio) in the draft,  do we see a need for 
   all three right now or in near  future (say next 12 months) ? 

B. OR are we happy with only covering one for now (Likely 
   the 1. as I understand people are most interested in the 1.) 
   and create a draft when there is a real need for 2. and 3.?

C. If answer is yes to question A., do we want to see the 
   draft split into three as Colin proposed or have them all 
   defined in single draft as it currently is. 

I asked the AD if we can split the drafts into 3 drafts under 
single milestone but I want to make sure we do that after 
we agree as a WG that we need all three segment types 
RIGHT NOW before we do so. 

We have a lot of new items that people are interested in 
working on that are not covered in our milestones, so I 
want to make sure we focus on items that are "MUST 
have" rather than "MAY need it in future" or "NICE to have". 

Regards
 Shida

From vsingh.ietf@gmail.com  Thu Jan 19 04:04:11 2012
Return-Path: <vsingh.ietf@gmail.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC0D621F8636 for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 04:04:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BxCUPz+T6iQw for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 04:04:10 -0800 (PST)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by ietfa.amsl.com (Postfix) with ESMTP id 4CD6221F8634 for <xrblock@ietf.org>; Thu, 19 Jan 2012 04:04:10 -0800 (PST)
Received: by wgbgn7 with SMTP id gn7so4652590wgb.1 for <xrblock@ietf.org>; Thu, 19 Jan 2012 04:04:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=KK0AcxzOtzmDhrZRgiZhXcBVH54ZGqofS1kW9NOvT/g=; b=XN+AxxtMaIUUYtv4p3vf1TpzeeG0R1kqwWQuswSa4pFVkcS9QknRPSg7Q1/0WeWquM gGobZoepOh4mVhuM92IrReU3hsDilAt4YK1jntaUv46cCKWm08KTT/Pk2Z7YRFBYbIZ7 YAUA08zYSQq69m6AE/kaAIIFf8wkAZz+fuJfc=
Received: by 10.180.104.5 with SMTP id ga5mr37967046wib.21.1326974648180; Thu, 19 Jan 2012 04:04:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.62.147 with HTTP; Thu, 19 Jan 2012 04:03:48 -0800 (PST)
In-Reply-To: <668E248B26E8402DA6E07957B288A094@china.huawei.com>
References: <CAEbPqrz05RAbaq7sNb+W09pZSJedn=iEW2Sf_BR3mRho5c=Tdg@mail.gmail.com> <54DEF8D9713A4424933422B86EAD700D@china.huawei.com> <CAEbPqrxUWFv642yVSQrnTuFBSeVFwk3pVQBGbmGqVfB+zqgxjw@mail.gmail.com> <58EA66C004CC42338DB85F9C032C1CC3@china.huawei.com> <CAEbPqrw+jv_AcsA1NQwhUKfRTzUmqieLueGM5AhY69G9iEcTDA@mail.gmail.com> <F2E27ABE99474D4EA46C65D578BA35B5@china.huawei.com> <CAEbPqrzZzn=oBgai3=1sk4CT-8GMRtnZ=+aSrokrSL=oZZgnkQ@mail.gmail.com> <668E248B26E8402DA6E07957B288A094@china.huawei.com>
From: Varun Singh <vsingh.ietf@gmail.com>
Date: Thu, 19 Jan 2012 14:03:48 +0200
Message-ID: <CAEbPqrwSE_mOcXEJKm_GqnAxpK98F26TVUAO623MwpocGsx5LQ@mail.gmail.com>
To: Qin Wu <bill.wu@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: xrblock@ietf.org
Subject: Re: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2012 12:04:11 -0000

Hi Qin,

Comments inline

Cheers,
Varun

>>> On Wed, Jan 18, 2012 at 03:34, Qin Wu <bill.wu@huawei.com> wrote:
>>>> Hi, Varun:
>>>> Please see my followup comments.
>>>>
>>>> Regards!
>>>> -Qin
>>>
>>>>>> Hi,
>>>>>>
>>>>>> I am sending the updates to mailing list so that the discussion can
>>>>>> take place before I post an updated draft.
>>>>>>
>>>>>> in -01, Section 1. Last para of introduction:
>>>>>> Complementary to or instead of the indication which packets were
>>>>>> discarded, an XR block is defined to indicate the number of bytes
>>>>>> discarded, per interval or for the duration of the session, similar
>>>>>> to other XR report blocks.
>>>>>>
>>>>>> Adding to that para in -02:
>>>>>> Alternatively, if the sender keeps a
>>>>>> history of the size of the packets reported in the measurement
>>>>>> interval then the sender can calculate the number of bytes discarded
>>>>>> from the information in the discard RLE block.
>>>>>>
>>>>>> - is this extra clarification needed?
>>>>>
>>>>> [Qin]: I think you don't need maintain the size for each packet, you =
only need to maintain
>>>>> the total size for all the received packet before the next packet is =
coming.
>>>>>
>>>>
>>>> The receiver needs to maintain the total size (for interval and for
>>>> cumulative). However, the extra paragraph is to show that discarded
>>>> bytes can also be calculated from the Discard RLE encoding--if the
>>>> sender maintains the size of the sent packets. It can then add up the
>>>> size of packets marked in the RLE block using a lookup table.
>>>>
>>>> [Qin]: Who calculates the size of packets? the reciever of dicard RLE =
block or the sender of byte dicarded block?
>>>> My understanding is it should be the sender of byte dicarded block tha=
t calculates the size of packets.
>>>> Your bytes discarded block should always be sent with dicard RLE block=
 in the same compound RTCP packet.
>>>>
>>>
>>> Bytes discarded is a complementary mechanism to Discard RLE. It is up
>>> to the implementer to choose from: packets discarded, bytes discarded,
>>> discarded RLE (for their use-case). Discarded RLE is like a superset
>>> and with it the sender can calculate packets and bytes discarded (if
>>> it knows the size of the packets). So there is no need to send bytes
>>> discarded and RLE together. In Sec 5
>>> (http://tools.ietf.org/html/draft-ietf-xrblock-rtcp-xr-discard-rle-metr=
ics-01#section-5.1)
>>> there is clarification for media receivers and media senders.
>>>
>>> [Qin]: What if dicard RLE block is lost?
>>>
>>
>> I do not think the media sender can with 100% certainty detect that an
>> RLE block was lost. If the receiver sends an RLE block for every
>> interval then the media sender could detect a missing interval from
>> the sequence numbers that were not reported in the RLE. However, which
>> XR blocks are reported in an interval depends on the
>> implementation/logic at the receiver. For instance, if all packets are
>> received then there is no need to send the RLE block. Moreover, if all
>> packets are discarded then sending the RLE block has high overhead and
>> the receiver may use the Packets Discarded XR Block.
>
> [Qin]: No doubt about this.
> my point is if any discard RLE block is lost, the media sender can not ca=
lculate the =A0accumulative total byte discard from =A0the lost discard RLE=
 block.
>
> But if the media receiver generate byte discard block and discard RLE blo=
ck, you don't
> have such issue since byte dicard block can be generated by media receive=
r based on associated discard RLE
> block which has not been sent.
>

Well this would be only true if the discard RLE and discarded bytes
are sent separately. If they are sent together (in a compound RTCP)
and the feedback message is lost then the media sender would not know.

As an implementer a solution may be (there may be other alternatives):
The discard RLE carries sequence numbers from overlapping intervals,
i.e., begin_seq and end_seq of the RLE block are different from the
current reporting interval (HSN_previous, HSN_current) and then you do
not have to worry about a loss of an intermediate RTCP packet but this
will increase the size of the packet depending on the length of the
reporting intervals.

> Another issue I am thinking is are you assuming each discarded data packe=
t you are tracking is equally size packet, otherwise, how do
> you calculate the total discared packet size.

No, and this is why I was proposing to add the additional paragraph in
the Introduction: (copying from above, see original mail for exact
details)

Adding to that para in -02:
Alternatively, if the sender keeps a
history of the size of the packets reported in the measurement
interval then the sender can calculate the number of bytes discarded
from the information in the discard RLE block.


>
>
>>>[Qin]: I think if any dicard RLE block is lost, this will prevent you ke=
eping on
>>> calculating the total byte lost or packet lost. How do you deal with th=
is case?
>
>> To know an RTCP feedback packet is lost, the media sender would have
>> received a new RTCP feedback packet. The media sender may use the
>> information in the new RTCP report to react to congestion/scheduling.
>> In the case of monitoring or storing metrics it is a problem because
>> the media sender or the middlebox has a no information for the missing
>> interval and could mark the bytes/packet discarded in the interval as
>> "not enough information".
>
> [Qin]: That's a good point. That is to say monitoring and congestion cont=
rol has different requirements for gathering
> statistics information and dealing with these information.
>

Yes and this may be true for all the XR blocks.

From csp@csperkins.org  Thu Jan 19 07:30:04 2012
Return-Path: <csp@csperkins.org>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 736A821F85F0 for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 07:30:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.074
X-Spam-Level: 
X-Spam-Status: No, score=-103.074 tagged_above=-999 required=5 tests=[AWL=0.525, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ht+mzQJIvRjM for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 07:30:03 -0800 (PST)
Received: from lon1-msapost-1.mail.demon.net (lon1-msapost-1.mail.demon.net [195.173.77.180]) by ietfa.amsl.com (Postfix) with ESMTP id BD91A21F85EF for <xrblock@ietf.org>; Thu, 19 Jan 2012 07:30:03 -0800 (PST)
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]) by lon1-post-1.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1RntwA-0007eb-Yc; Thu, 19 Jan 2012 15:30:02 +0000
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <14878230.5711326961824918.JavaMail.root@ent11>
Date: Thu, 19 Jan 2012 15:29:59 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <A93B6F8E-6EFC-421B-A07A-641692240EA9@csperkins.org>
References: <14878230.5711326961824918.JavaMail.root@ent11>
To: zhaojing@sttri.com.cn
X-Mailer: Apple Mail (2.1251.1)
Cc: xrblock <xrblock@ietf.org>
Subject: Re: [xrblock] Update of Burst Gap related drafts
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2012 15:30:04 -0000

On 19 Jan 2012, at 08:30, zhaojing@sttri.com.cn wrote:
> Qin and us have worked out the revision of Burst gap related drafts. =
The new updates are available at:
> a. Burst Gap Loss Draft
> =
http://tools.ietf.org/html/draft-ietf-xrblock-rtcp-xr-burst-gap-loss-01
> b. Burst Gap Discard Draft
> =
http://tools.ietf.org/html/draft-ietf-xrblock-rtcp-xr-burst-gap-discard-01=


Looking at the changes in burst-gap-discard metrics draft-01, it seems =
that the Threshold field is removed, but nothing is added to replace it. =
Given this change, how are bursts defined? The draft suggests, but does =
not seem to require the Gmin parameter from RFC 3611 is used, but what =
value for Gmin?

Colin



--=20
Colin Perkins
http://csperkins.org/




From bill.wu@huawei.com  Thu Jan 19 17:09:51 2012
Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 285F021F858F for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 17:09:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.258
X-Spam-Level: 
X-Spam-Status: No, score=-6.258 tagged_above=-999 required=5 tests=[AWL=0.341,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LJV8cuaXLCRY for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 17:09:47 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id CAE0421F8597 for <xrblock@ietf.org>; Thu, 19 Jan 2012 17:09:46 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LY200LRAOK41X@szxga03-in.huawei.com> for xrblock@ietf.org; Fri, 20 Jan 2012 09:09:40 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LY200LBROJT4O@szxga03-in.huawei.com> for xrblock@ietf.org; Fri, 20 Jan 2012 09:09:40 +0800 (CST)
Received: from szxeml210-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGN17926; Fri, 20 Jan 2012 09:09:40 +0800
Received: from SZXEML421-HUB.china.huawei.com (10.82.67.160) by szxeml210-edg.china.huawei.com (172.24.2.183) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 20 Jan 2012 09:09:32 +0800
Received: from w53375q (10.138.41.130) by szxeml421-hub.china.huawei.com (10.82.67.160) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 20 Jan 2012 09:09:33 +0800
Date: Fri, 20 Jan 2012 09:09:30 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Colin Perkins <csp@csperkins.org>, zhaojing@sttri.com.cn
Message-id: <18C6D212597C452591D7E0930777A147@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <14878230.5711326961824918.JavaMail.root@ent11> <A93B6F8E-6EFC-421B-A07A-641692240EA9@csperkins.org>
Cc: xrblock <xrblock@ietf.org>
Subject: Re: [xrblock] Update of Burst Gap related drafts
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jan 2012 01:09:51 -0000

Hi,
----- Original Message ----- 
From: "Colin Perkins" <csp@csperkins.org>
To: <zhaojing@sttri.com.cn>
Cc: "xrblock" <xrblock@ietf.org>
Sent: Thursday, January 19, 2012 11:29 PM
Subject: Re: [xrblock] Update of Burst Gap related drafts


> On 19 Jan 2012, at 08:30, zhaojing@sttri.com.cn wrote:
>> Qin and us have worked out the revision of Burst gap related drafts. The new updates are available at:
>> a. Burst Gap Loss Draft
>> http://tools.ietf.org/html/draft-ietf-xrblock-rtcp-xr-burst-gap-loss-01
>> b. Burst Gap Discard Draft
>> http://tools.ietf.org/html/draft-ietf-xrblock-rtcp-xr-burst-gap-discard-01
> 
> Looking at the changes in burst-gap-discard metrics draft-01, it seems that the Threshold field is removed, but nothing is added to replace it. Given this change, how are bursts defined? The draft suggests, but does not seem to require the Gmin parameter from RFC 3611 is used, but what value for Gmin?

[Qin]: Good point, I think Threshold should be put back rather than defining any new replacement since Threshold is used to differentiate burst from gap. 

> Colin
> 
> 
> 
> -- 
> Colin Perkins
> http://csperkins.org/
> 
> 
> 
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock

From zhaojing@sttri.com.cn  Thu Jan 19 17:28:40 2012
Return-Path: <zhaojing@sttri.com.cn>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AFD221F85CE for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 17:28:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.247
X-Spam-Level: *
X-Spam-Status: No, score=1.247 tagged_above=-999 required=5 tests=[AWL=0.744,  BAYES_00=-2.599, HTML_MESSAGE=0.001, HTML_NONELEMENT_30_40=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_NJABL_PROXY=1.643]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gKtBdTl+BJh2 for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 17:28:39 -0800 (PST)
Received: from corp.21cn.com (corp.forptr.21cn.com [121.14.129.35]) by ietfa.amsl.com (Postfix) with ESMTP id 7DEE721F858F for <xrblock@ietf.org>; Thu, 19 Jan 2012 17:28:39 -0800 (PST)
Received: from ip?218.2.129.2? (entas5.inner-hermes.com [10.27.101.5]) by corp.21cn.com (HERMES) with ESMTP id 828B63E4032; Fri, 20 Jan 2012 09:28:35 +0800 (CST)
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_IP: wmail.10.27.101.5.186694014
HMM_SOURCE_TYPE: WEBMAIL
Received: from ip<218.2.129.2> ([218.2.129.2]) by 21CN-entas5(Yuwen filter gate 10.27.101.5) with ESMTP id 1327022915.22776 for bill.wu@huawei.com ; Fri Jan 20 09:28:36 2012
0/X-Total-Score: 3:
X-FILTER-SCORE: to=<bill.wu@huawei.comcsp@csperkins.orgxrblock@ietf.org>, score=<1327022916scssVssUsS5IcVUzt7ssIsWII3IInIPcsW3neVCIIsII> 
Date: Fri, 20 Jan 2012 09:28:35 +0800 (CST)
From: zhaojing@sttri.com.cn
To: Qin Wu <bill.wu@huawei.com>, Colin Perkins <csp@csperkins.org>
Message-ID: <23359800.3941327022915704.JavaMail.root@ent8>
MIME-Version: 1.0
Content-Type: multipart/mixed;  boundary="----=_Part_440_32908860.1327022915323"
HMM_WEBCLN_IP: 218.2.129.2
X-HERMES-SENDMODE: normal
Cc: xrblock <xrblock@ietf.org>
Subject: Re: [xrblock] Update of Burst Gap related drafts
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jan 2012 01:28:40 -0000

------=_Part_440_32908860.1327022915323
Content-Type: text/html;charset=UTF-8
Content-Transfer-Encoding: base64

PGh0bWw+CiA8aGVhZD48L2hlYWQ+CiA8Ym9keT4KICA8ZGl2PgogICBBZ3JlZS4gVGhhdCBpcyB0
aGUgaXNzdWUgd2UgbmVlZCB0byBmaXguCiAgPC9kaXY+IAogIDxkaXY+CiAgICZuYnNwOwogIDwv
ZGl2PiAKICA8ZGl2PgogICAtSmluZwogIDwvZGl2PiAKICA8ZGl2PgogICAmZ3Q7LS0tLS0tLS0t
LS0tLS0tLS0tIOWOn+Wni+mCruS7tiAtLS0tLS0tLS0tLS0tLS0tLS0KICAgPGJyIC8+CiAgIDxi
ciAvPiZndDvlj5Hku7bkurrvvJpRaW4gV3UgCiAgIDxiaWxsIHd1PSIiIGh1YXdlaT0iIiBjb209
IiI+CiAgICA8YnIgLz4mZ3Q75pe244CA6Ze077yaMjAxMi8wMS8yMCAwOTowOTozMCDmmJ/mnJ/k
upQKICAgIDxiciAvPiZndDvmlLbku7bkurrvvJpDb2xpbiBQZXJraW5zIAogICAgPGNzcCBjc3Bl
cmtpbnM9IiIgb3JnPSIiPgogICAgICwgemhhb2ppbmdAc3R0cmkuY29tLmNuCiAgICAgPGJyIC8+
Jmd0O+aKhOmAgeS6uu+8mnhyYmxvY2sgCiAgICAgPHhyYmxvY2sgaWV0Zj0iIiBvcmc9IiI+CiAg
ICAgIDxiciAvPiZndDvkuLvjgIDpopjvvJpSZTogW3hyYmxvY2tdIFVwZGF0ZSBvZiBCdXJzdCBH
YXAgcmVsYXRlZCBkcmFmdHMKICAgICAgPGJyIC8+CiAgICAgIDxiciAvPiZndDtIaSwgLS0tLS0g
T3JpZ2luYWwgTWVzc2FnZSAtLS0tLSAKICAgICA8L3hyYmxvY2s+CiAgICA8L2NzcD4KICAgPC9i
aWxsPgogIDwvZGl2PiAKICA8ZGl2PgogICAmZ3Q7RnJvbTogJnF1b3Q7Q29saW4gUGVya2lucyZx
dW90OyAKICAgPGNzcCBjc3BlcmtpbnM9IiIgb3JnPSIiPgogICAgVG86IAogICAgPHpoYW9qaW5n
IHN0dHJpPSIiIGNvbT0iIiBjbj0iIj4KICAgICBDYzogJnF1b3Q7eHJibG9jayZxdW90OyAKICAg
IDwvemhhb2ppbmc+CiAgIDwvY3NwPgogIDwvZGl2PiAKICA8ZGl2PgogICA8eHJibG9jayBpZXRm
PSIiIG9yZz0iIj4KICAgICZndDtTZW50OiBUaHVyc2RheSwgSmFudWFyeSAxOSwgMjAxMiAxMToy
OSBQTSAKICAgPC94cmJsb2NrPgogIDwvZGl2PiAKICA8ZGl2PgogICAmZ3Q7U3ViamVjdDogUmU6
IFt4cmJsb2NrXSBVcGRhdGUgb2YgQnVyc3QgR2FwIHJlbGF0ZWQgZHJhZnRzIAogIDwvZGl2PiAK
ICA8ZGl2PgogICAmZ3Q7IE9uIDE5IEphbiAyMDEyLCBhdCAwODozMCwgemhhb2ppbmdAc3R0cmku
Y29tLmNuIHdyb3RlOgogIDwvZGl2PiAKICA8ZGl2PgogICAmbmJzcDsmZ3Q7Jmd0OyZndDsgUWlu
IGFuZCB1cyBoYXZlIHdvcmtlZCBvdXQgdGhlIHJldmlzaW9uIG9mIEJ1cnN0IGdhcCByZWxhdGVk
IGRyYWZ0cy4gVGhlIG5ldyB1cGRhdGVzIGFyZSBhdmFpbGFibGUgYXQ6CiAgPC9kaXY+IAogIDxk
aXY+CiAgICZuYnNwOyZndDsmZ3Q7Jmd0OyBhLiBCdXJzdCBHYXAgTG9zcyBEcmFmdCAKICA8L2Rp
dj4gCiAgPGRpdj4KICAgJmd0OyZndDsmZ3Q7IGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2Ry
YWZ0LWlldGYteHJibG9jay1ydGNwLXhyLWJ1cnN0LWdhcC1sb3NzLTAxICZndDsmZ3Q7IGIuIEJ1
cnN0IEdhcCBEaXNjYXJkIERyYWZ0IAogIDwvZGl2PiAKICA8ZGl2PgogICAmZ3Q7Jmd0OyZndDsg
CiAgIDxhIGhyZWY9Imh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYteHJibG9j
ay1ydGNwLXhyLWJ1cnN0LWdhcC1kaXNjYXJkLTAxIj5odHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRt
bC9kcmFmdC1pZXRmLXhyYmxvY2stcnRjcC14ci1idXJzdC1nYXAtZGlzY2FyZC0wMTwvYT4gCiAg
PC9kaXY+IAogIDxkaXY+CiAgICZuYnNwOwogIDwvZGl2PiAKICA8ZGl2PgogICAmZ3Q7TG9va2lu
ZyBhdCB0aGUgY2hhbmdlcyBpbiBidXJzdC1nYXAtZGlzY2FyZCBtZXRyaWNzIGRyYWZ0LTAxLCBp
dCBzZWVtcyB0aGF0IHRoZSBUaHJlc2hvbGQgZmllbGQgaXMgcmVtb3ZlZCwgYnV0IG5vdGhpbmcg
aXMgYWRkZWQgdG8gcmVwbGFjZSBpdC4gJmd0O0dpdmVuIHRoaXMgY2hhbmdlLCBob3cgYXJlIGJ1
cnN0cyBkZWZpbmVkPyBUaGUgZHJhZnQgc3VnZ2VzdHMsIGJ1dCBkb2VzIG5vdCBzZWVtIHRvIHJl
cXVpcmUgdGhlIEdtaW4gcGFyYW1ldGVyIGZyb20gUkZDIDM2MTEgaXMgdXNlZCwgYnV0ICZndDt3
aGF0IHZhbHVlIGZvciBHbWluPwogIDwvZGl2PiAKICA8ZGl2PgogICAmbmJzcDsKICA8L2Rpdj4g
CiAgPGRpdj4KICAgJm5ic3A7W1Fpbl06IEdvb2QgcG9pbnQsIEkgdGhpbmsgVGhyZXNob2xkIHNo
b3VsZCBiZSBwdXQgYmFjayByYXRoZXIgdGhhbiBkZWZpbmluZyBhbnkgbmV3IHJlcGxhY2VtZW50
IHNpbmNlIFRocmVzaG9sZCBpcyB1c2VkIHRvIGRpZmZlcmVudGlhdGUgYnVyc3QgZnJvbSBnYXAu
IAogIDwvZGl2PiAKICA8ZGl2PgogICAmbmJzcDsKICA8L2Rpdj4gCiAgPGRpdj4KICAgJm5ic3A7
CiAgPC9kaXY+IAogIDxkaXY+CiAgICZndDsmZ3Q7IENvbGluIAogIDwvZGl2PiAKICA8ZGl2Pgog
ICAmZ3Q7Jmd0OyAmZ3Q7ICZndDsgJmd0OyAtLSAmZ3Q7IENvbGluIFBlcmtpbnMgJmd0OyBodHRw
Oi8vY3NwZXJraW5zLm9yZy8gJmd0OwogIDwvZGl2PiAKICA8ZGl2PgogICAmbmJzcDsmZ3Q7Jmd0
OyAmZ3Q7ICZndDsgX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18gCiAgPC9kaXY+IAogIDxkaXY+CiAgICZndDsmZ3Q7IHhyYmxvY2sgbWFpbGluZyBsaXN0ICZn
dDsgCiAgIDxhIGhyZWY9Im1haWx0bzp4cmJsb2NrQGlldGYub3JnIj54cmJsb2NrQGlldGYub3Jn
PC9hPiAKICA8L2Rpdj4gCiAgPGRpdj4KICAgJmd0OyZndDsgaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby94cmJsb2NrIAogIDwvZGl2PgogPC9ib2R5Pgo8L2h0bWw+
------=_Part_440_32908860.1327022915323--


From internet-drafts@ietf.org  Thu Jan 19 18:03:30 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF22E21F85B6; Thu, 19 Jan 2012 18:03:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.573
X-Spam-Level: 
X-Spam-Status: No, score=-102.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vulicChBIVMj; Thu, 19 Jan 2012 18:03:29 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08B9221F8599; Thu, 19 Jan 2012 18:03:08 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20120120020308.20461.59777.idtracker@ietfa.amsl.com>
Date: Thu, 19 Jan 2012 18:03:08 -0800
Cc: xrblock@ietf.org
Subject: [xrblock] I-D Action: draft-ietf-xrblock-rtcp-xr-burst-gap-discard-02.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jan 2012 02:03:30 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Metric Blocks for use with RTCP's Ext=
ended Report Framework Working Group of the IETF.

	Title           : RTCP XR Report Block for Burst/Gap Discard metric Report=
ing
	Author(s)       : Geoff Hunt
                          Alan Clark
                          Rachel Huang
                          Qin Wu
	Filename        : draft-ietf-xrblock-rtcp-xr-burst-gap-discard-02.txt
	Pages           : 16
	Date            : 2012-01-19

   This document defines an RTCP XR Report Block that allows the
   reporting of Burst and Gap Discard metrics for use in a range of RTP
   applications.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-xrblock-rtcp-xr-burst-gap-di=
scard-02.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-xrblock-rtcp-xr-burst-gap-dis=
card-02.txt


From bill.wu@huawei.com  Thu Jan 19 18:11:16 2012
Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5133E21F85C6 for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 18:11:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.269
X-Spam-Level: 
X-Spam-Status: No, score=-6.269 tagged_above=-999 required=5 tests=[AWL=0.330,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3JyUnENQrDzJ for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 18:11:15 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 7E0C721F85CE for <xrblock@ietf.org>; Thu, 19 Jan 2012 18:11:15 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LY2000TRREQQA@szxga04-in.huawei.com> for xrblock@ietf.org; Fri, 20 Jan 2012 10:11:14 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LY20022RREQOM@szxga04-in.huawei.com> for xrblock@ietf.org; Fri, 20 Jan 2012 10:11:14 +0800 (CST)
Received: from szxeml201-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGN19875; Fri, 20 Jan 2012 10:11:06 +0800
Received: from SZXEML418-HUB.china.huawei.com (10.82.67.157) by szxeml201-edg.china.huawei.com (172.24.2.39) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 20 Jan 2012 10:10:51 +0800
Received: from w53375q (10.138.41.130) by szxeml418-hub.china.huawei.com (10.82.67.157) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 20 Jan 2012 10:10:53 +0800
Date: Fri, 20 Jan 2012 10:10:52 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: xrblock@ietf.org
Message-id: <AC2B0F2F891E4882A5D78139210A1E61@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
Subject: [xrblock] Fw: I-D Action:draft-ietf-xrblock-rtcp-xr-burst-gap-discard-02.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jan 2012 02:11:16 -0000

> On 20 January 2012, at 10:03 AM, Internet-Drafts@ietf.org wrote:
 
> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Metric Blocks for use with RTCP's Extended Report Framework Working Group of the IETF.
> 
> Title           : RTCP XR Report Block for Burst/Gap Discard metric Reporting
> Author(s)       : Geoff Hunt
>                          Alan Clark
>                          Rachel Huang
>                          Qin Wu
> Filename        : draft-ietf-xrblock-rtcp-xr-burst-gap-discard-02.txt
> Pages           : 16
> Date            : 2012-01-19
> 
>   This document defines an RTCP XR Report Block that allows the
>   reporting of Burst and Gap Discard metrics for use in a range of RTP
>   applications.
> 
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-xrblock-rtcp-xr-burst-gap-discard-02.txt
> 

[Qin]: One minor update to address Colin's comments on the list.

From bill.wu@huawei.com  Thu Jan 19 18:32:04 2012
Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90F1721F84FC for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 18:32:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.279
X-Spam-Level: 
X-Spam-Status: No, score=-6.279 tagged_above=-999 required=5 tests=[AWL=0.320,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d63CseV6WHZc for <xrblock@ietfa.amsl.com>; Thu, 19 Jan 2012 18:32:03 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 229EB21F84F6 for <xrblock@ietf.org>; Thu, 19 Jan 2012 18:32:03 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LY20096JSDE2N@szxga04-in.huawei.com> for xrblock@ietf.org; Fri, 20 Jan 2012 10:32:02 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LY20021XSDAOM@szxga04-in.huawei.com> for xrblock@ietf.org; Fri, 20 Jan 2012 10:32:02 +0800 (CST)
Received: from szxeml209-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGL20601; Fri, 20 Jan 2012 10:31:59 +0800
Received: from SZXEML410-HUB.china.huawei.com (10.82.67.137) by szxeml209-edg.china.huawei.com (172.24.2.184) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 20 Jan 2012 10:31:46 +0800
Received: from w53375q (10.138.41.130) by szxeml410-hub.china.huawei.com (10.82.67.137) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 20 Jan 2012 10:31:49 +0800
Date: Fri, 20 Jan 2012 10:31:48 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Varun Singh <vsingh.ietf@gmail.com>
Message-id: <148184857F6741A6831B722743949B3C@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <CAEbPqrz05RAbaq7sNb+W09pZSJedn=iEW2Sf_BR3mRho5c=Tdg@mail.gmail.com> <54DEF8D9713A4424933422B86EAD700D@china.huawei.com> <CAEbPqrxUWFv642yVSQrnTuFBSeVFwk3pVQBGbmGqVfB+zqgxjw@mail.gmail.com> <58EA66C004CC42338DB85F9C032C1CC3@china.huawei.com> <CAEbPqrw+jv_AcsA1NQwhUKfRTzUmqieLueGM5AhY69G9iEcTDA@mail.gmail.com> <F2E27ABE99474D4EA46C65D578BA35B5@china.huawei.com> <CAEbPqrzZzn=oBgai3=1sk4CT-8GMRtnZ=+aSrokrSL=oZZgnkQ@mail.gmail.com> <668E248B26E8402DA6E07957B288A094@china.huawei.com> <CAEbPqrwSE_mOcXEJKm_GqnAxpK98F26TVUAO623MwpocGsx5LQ@mail.gmail.com>
Cc: xrblock@ietf.org
Subject: Re: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jan 2012 02:32:04 -0000

Hi,
----- Original Message ----- 
>From: "Varun Singh" <vsingh.ietf@gmail.com>
>To: "Qin Wu" <bill.wu@huawei.com>
>Cc: <xrblock@ietf.org>
>Sent: Thursday, January 19, 2012 8:03 PM
>Subject: Re: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02


>Hi Qin,

>Comments inline

>Cheers,
>Varun

>>>> On Wed, Jan 18, 2012 at 03:34, Qin Wu <bill.wu@huawei.com> wrote:
>>>>> Hi, Varun:
>>>>> Please see my followup comments.
>>>>>
>>>>> Regards!
>>>>> -Qin
>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I am sending the updates to mailing list so that the discussion can
>>>>>>> take place before I post an updated draft.
>>>>>>>
>>>>>>> in -01, Section 1. Last para of introduction:
>>>>>>> Complementary to or instead of the indication which packets were
>>>>>>> discarded, an XR block is defined to indicate the number of bytes
>>>>>>> discarded, per interval or for the duration of the session, similar
>>>>>>> to other XR report blocks.
>>>>>>>
>>>>>>> Adding to that para in -02:
>>>>>>> Alternatively, if the sender keeps a
>>>>>>> history of the size of the packets reported in the measurement
>>>>>>> interval then the sender can calculate the number of bytes discarded
>>>>>>> from the information in the discard RLE block.
>>>>>>>
>>>>>>> - is this extra clarification needed?
>>>>>>
>>>>>> [Qin]: I think you don't need maintain the size for each packet, you only need to maintain
>>>>>> the total size for all the received packet before the next packet is coming.
>>>>>>
>>>>>
>>>>> The receiver needs to maintain the total size (for interval and for
>>>>> cumulative). However, the extra paragraph is to show that discarded
>>>>> bytes can also be calculated from the Discard RLE encoding--if the
>>>>> sender maintains the size of the sent packets. It can then add up the
>>>> size of packets marked in the RLE block using a lookup table.
>>>>>>
>>>>> [Qin]: Who calculates the size of packets? the reciever of dicard RLE block or the sender of byte dicarded block?
>>>>> My understanding is it should be the sender of byte dicarded block that calculates the size of packets.
>>>>> Your bytes discarded block should always be sent with dicard RLE block in the same compound RTCP packet.
>>>> Bytes discarded is a complementary mechanism to Discard RLE. It is up
>>>> to the implementer to choose from: packets discarded, bytes discarded,
>>>> discarded RLE (for their use-case). Discarded RLE is like a superset
>>>> and with it the sender can calculate packets and bytes discarded (if
>>>> it knows the size of the packets). So there is no need to send bytes
>>>> discarded and RLE together. In Sec 5
>>>> (http://tools.ietf.org/html/draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-01#section-5.1)
>>>> there is clarification for media receivers and media senders.
>>>>
>>>> [Qin]: What if dicard RLE block is lost?
>>>>
>>>
>>> I do not think the media sender can with 100% certainty detect that an
>> RLE block was lost. If the receiver sends an RLE block for every
>>> interval then the media sender could detect a missing interval from
>>> the sequence numbers that were not reported in the RLE. However, which
>>> XR blocks are reported in an interval depends on the
>>> implementation/logic at the receiver. For instance, if all packets are
>>> received then there is no need to send the RLE block. Moreover, if all
>>> packets are discarded then sending the RLE block has high overhead and
>>> the receiver may use the Packets Discarded XR Block.
>>
>> [Qin]: No doubt about this.
>> my point is if any discard RLE block is lost, the media sender can not calculate the accumulative total byte discard from the lost discard RLE block.
>>
>> But if the media receiver generate byte discard block and discard RLE block, you don't
>> have such issue since byte dicard block can be generated by media receiver based on associated discard RLE
>> block which has not been sent.
>>

>Well this would be only true if the discard RLE and discarded bytes
>are sent separately. If they are sent together (in a compound RTCP)
>and the feedback message is lost then the media sender would not know.

[Qin]: It doesn't matter if any discard RLE or discared byte RTCP XR block is lost.
Since the media receiver always know how many byte of media packet are discarded if media 
receiver is responsible for calculating byte discarded for the received media packet during the 
measurement interval. 

But if media sender is responsible for calcuating the byte discared, that will be different.

>As an implementer a solution may be (there may be other alternatives):
>The discard RLE carries sequence numbers from overlapping intervals,
>i.e., begin_seq and end_seq of the RLE block are different from the
>current reporting interval (HSN_previous, HSN_current) and then you do
>not have to worry about a loss of an intermediate RTCP packet but this
>will increase the size of the packet depending on the length of the
>reporting intervals.


> Another issue I am thinking is are you assuming each discarded data packet you are tracking is equally size packet, otherwise, how do
> you calculate the total discared packet size.

>No, and this is why I was proposing to add the additional paragraph in
>the Introduction: (copying from above, see original mail for exact
>details)

>Adding to that para in -02:
>Alternatively, if the sender keeps a
>history of the size of the packets reported in the measurement
>interval then the sender can calculate the number of bytes discarded
>from the information in the discard RLE block.

[Qin]: How does the sender know each discarded packet size? Isn't the sender signaled by the media receiver since only
terminal knows each discarded packet size.
Also I think that's a disadvantage if you ask media sender to calcuate byte discard.
If the media receiver calculate byte discard, you don't require media receiver to keep a history of the size of the packet.

>>>>[Qin]: I think if any dicard RLE block is lost, this will prevent you keeping on
>>>> calculating the total byte lost or packet lost. How do you deal with this case?
>>
>>> To know an RTCP feedback packet is lost, the media sender would have
>>> received a new RTCP feedback packet. The media sender may use the
>>> information in the new RTCP report to react to congestion/scheduling.
>>> In the case of monitoring or storing metrics it is a problem because
>>> the media sender or the middlebox has a no information for the missing
>>> interval and could mark the bytes/packet discarded in the interval as
>>> "not enough information".
>>
>> [Qin]: That's a good point. That is to say monitoring and congestion control has different requirements for gathering
>> statistics information and dealing with these information.
>>

>>Yes and this may be true for all the XR blocks.

[Qin]: Agree.

From vsingh.ietf@gmail.com  Fri Jan 20 04:26:35 2012
Return-Path: <vsingh.ietf@gmail.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AF7121F84B2 for <xrblock@ietfa.amsl.com>; Fri, 20 Jan 2012 04:26:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rSUeT24Qkteu for <xrblock@ietfa.amsl.com>; Fri, 20 Jan 2012 04:26:34 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1015C21F84A6 for <xrblock@ietf.org>; Fri, 20 Jan 2012 04:26:33 -0800 (PST)
Received: by werp11 with SMTP id p11so460067wer.31 for <xrblock@ietf.org>; Fri, 20 Jan 2012 04:26:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=TzYChh37TPWyppIzzHYWxNBbA1ya/kUS3wTnnXc+B/c=; b=c+f9hzDuGETxktp8IOBvyt0LvMzrOPgObDWfRsA4grSF0zpiVD9du+4k0BaAkjYGnP DaNJATpcFAr6Z5A1x+00ttkbe9hMhTVkgQE+TfoQGIUHV5go9GLcSe812Czb2uQY/C/I 5EYuSf7DFmt1E38JS8875V28cu6ElHZJdNXTw=
Received: by 10.216.137.210 with SMTP id y60mr608672wei.14.1327062392182; Fri, 20 Jan 2012 04:26:32 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.62.147 with HTTP; Fri, 20 Jan 2012 04:26:11 -0800 (PST)
In-Reply-To: <148184857F6741A6831B722743949B3C@china.huawei.com>
References: <CAEbPqrz05RAbaq7sNb+W09pZSJedn=iEW2Sf_BR3mRho5c=Tdg@mail.gmail.com> <54DEF8D9713A4424933422B86EAD700D@china.huawei.com> <CAEbPqrxUWFv642yVSQrnTuFBSeVFwk3pVQBGbmGqVfB+zqgxjw@mail.gmail.com> <58EA66C004CC42338DB85F9C032C1CC3@china.huawei.com> <CAEbPqrw+jv_AcsA1NQwhUKfRTzUmqieLueGM5AhY69G9iEcTDA@mail.gmail.com> <F2E27ABE99474D4EA46C65D578BA35B5@china.huawei.com> <CAEbPqrzZzn=oBgai3=1sk4CT-8GMRtnZ=+aSrokrSL=oZZgnkQ@mail.gmail.com> <668E248B26E8402DA6E07957B288A094@china.huawei.com> <CAEbPqrwSE_mOcXEJKm_GqnAxpK98F26TVUAO623MwpocGsx5LQ@mail.gmail.com> <148184857F6741A6831B722743949B3C@china.huawei.com>
From: Varun Singh <vsingh.ietf@gmail.com>
Date: Fri, 20 Jan 2012 14:26:11 +0200
Message-ID: <CAEbPqrwanaE7=rvezufae_=XrYPeCqNNth-kGzPzUnK2nRfANQ@mail.gmail.com>
To: Qin Wu <bill.wu@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: xrblock@ietf.org
Subject: Re: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jan 2012 12:26:35 -0000

Hi Qin,

I will make the changes that we have discussed and submit a new draft.
If it is not clear in the new draft, then we can reopen the
discussion.


Regards,
Varun

On Fri, Jan 20, 2012 at 04:31, Qin Wu <bill.wu@huawei.com> wrote:
> Hi,
> ----- Original Message -----
>>From: "Varun Singh" <vsingh.ietf@gmail.com>
>>To: "Qin Wu" <bill.wu@huawei.com>
>>Cc: <xrblock@ietf.org>
>>Sent: Thursday, January 19, 2012 8:03 PM
>>Subject: Re: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02
>
>
>>Hi Qin,
>
>>Comments inline
>
>>Cheers,
>>Varun
>
>>>>> On Wed, Jan 18, 2012 at 03:34, Qin Wu <bill.wu@huawei.com> wrote:
>>>>>> Hi, Varun:
>>>>>> Please see my followup comments.
>>>>>>
>>>>>> Regards!
>>>>>> -Qin
>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I am sending the updates to mailing list so that the discussion can
>>>>>>>> take place before I post an updated draft.
>>>>>>>>
>>>>>>>> in -01, Section 1. Last para of introduction:
>>>>>>>> Complementary to or instead of the indication which packets were
>>>>>>>> discarded, an XR block is defined to indicate the number of bytes
>>>>>>>> discarded, per interval or for the duration of the session, similar
>>>>>>>> to other XR report blocks.
>>>>>>>>
>>>>>>>> Adding to that para in -02:
>>>>>>>> Alternatively, if the sender keeps a
>>>>>>>> history of the size of the packets reported in the measurement
>>>>>>>> interval then the sender can calculate the number of bytes discarded
>>>>>>>> from the information in the discard RLE block.
>>>>>>>>
>>>>>>>> - is this extra clarification needed?
>>>>>>>
>>>>>>> [Qin]: I think you don't need maintain the size for each packet, you only need to maintain
>>>>>>> the total size for all the received packet before the next packet is coming.
>>>>>>>
>>>>>>
>>>>>> The receiver needs to maintain the total size (for interval and for
>>>>>> cumulative). However, the extra paragraph is to show that discarded
>>>>>> bytes can also be calculated from the Discard RLE encoding--if the
>>>>>> sender maintains the size of the sent packets. It can then add up the
>>>>> size of packets marked in the RLE block using a lookup table.
>>>>>>>
>>>>>> [Qin]: Who calculates the size of packets? the reciever of dicard RLE block or the sender of byte dicarded block?
>>>>>> My understanding is it should be the sender of byte dicarded block that calculates the size of packets.
>>>>>> Your bytes discarded block should always be sent with dicard RLE block in the same compound RTCP packet.
>>>>> Bytes discarded is a complementary mechanism to Discard RLE. It is up
>>>>> to the implementer to choose from: packets discarded, bytes discarded,
>>>>> discarded RLE (for their use-case). Discarded RLE is like a superset
>>>>> and with it the sender can calculate packets and bytes discarded (if
>>>>> it knows the size of the packets). So there is no need to send bytes
>>>>> discarded and RLE together. In Sec 5
>>>>> (http://tools.ietf.org/html/draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-01#section-5.1)
>>>>> there is clarification for media receivers and media senders.
>>>>>
>>>>> [Qin]: What if dicard RLE block is lost?
>>>>>
>>>>
>>>> I do not think the media sender can with 100% certainty detect that an
>>> RLE block was lost. If the receiver sends an RLE block for every
>>>> interval then the media sender could detect a missing interval from
>>>> the sequence numbers that were not reported in the RLE. However, which
>>>> XR blocks are reported in an interval depends on the
>>>> implementation/logic at the receiver. For instance, if all packets are
>>>> received then there is no need to send the RLE block. Moreover, if all
>>>> packets are discarded then sending the RLE block has high overhead and
>>>> the receiver may use the Packets Discarded XR Block.
>>>
>>> [Qin]: No doubt about this.
>>> my point is if any discard RLE block is lost, the media sender can not calculate the accumulative total byte discard from the lost discard RLE block.
>>>
>>> But if the media receiver generate byte discard block and discard RLE block, you don't
>>> have such issue since byte dicard block can be generated by media receiver based on associated discard RLE
>>> block which has not been sent.
>>>
>
>>Well this would be only true if the discard RLE and discarded bytes
>>are sent separately. If they are sent together (in a compound RTCP)
>>and the feedback message is lost then the media sender would not know.
>
> [Qin]: It doesn't matter if any discard RLE or discared byte RTCP XR block is lost.
> Since the media receiver always know how many byte of media packet are discarded if media
> receiver is responsible for calculating byte discarded for the received media packet during the
> measurement interval.
>
> But if media sender is responsible for calcuating the byte discared, that will be different.
>
>>As an implementer a solution may be (there may be other alternatives):
>>The discard RLE carries sequence numbers from overlapping intervals,
>>i.e., begin_seq and end_seq of the RLE block are different from the
>>current reporting interval (HSN_previous, HSN_current) and then you do
>>not have to worry about a loss of an intermediate RTCP packet but this
>>will increase the size of the packet depending on the length of the
>>reporting intervals.
>
>
>> Another issue I am thinking is are you assuming each discarded data packet you are tracking is equally size packet, otherwise, how do
>> you calculate the total discared packet size.
>
>>No, and this is why I was proposing to add the additional paragraph in
>>the Introduction: (copying from above, see original mail for exact
>>details)
>
>>Adding to that para in -02:
>>Alternatively, if the sender keeps a
>>history of the size of the packets reported in the measurement
>>interval then the sender can calculate the number of bytes discarded
>>from the information in the discard RLE block.
>
> [Qin]: How does the sender know each discarded packet size? Isn't the sender signaled by the media receiver since only
> terminal knows each discarded packet size.
> Also I think that's a disadvantage if you ask media sender to calcuate byte discard.
> If the media receiver calculate byte discard, you don't require media receiver to keep a history of the size of the packet.
>
>>>>>[Qin]: I think if any dicard RLE block is lost, this will prevent you keeping on
>>>>> calculating the total byte lost or packet lost. How do you deal with this case?
>>>
>>>> To know an RTCP feedback packet is lost, the media sender would have
>>>> received a new RTCP feedback packet. The media sender may use the
>>>> information in the new RTCP report to react to congestion/scheduling.
>>>> In the case of monitoring or storing metrics it is a problem because
>>>> the media sender or the middlebox has a no information for the missing
>>>> interval and could mark the bytes/packet discarded in the interval as
>>>> "not enough information".
>>>
>>> [Qin]: That's a good point. That is to say monitoring and congestion control has different requirements for gathering
>>> statistics information and dealing with these information.
>>>
>
>>>Yes and this may be true for all the XR blocks.
>
> [Qin]: Agree.



-- 
http://www.netlab.tkk.fi/~varun/

From eckelcu@cisco.com  Fri Jan 20 14:20:45 2012
Return-Path: <eckelcu@cisco.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15F2521F864D for <xrblock@ietfa.amsl.com>; Fri, 20 Jan 2012 14:20:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.355
X-Spam-Level: 
X-Spam-Status: No, score=-6.355 tagged_above=-999 required=5 tests=[AWL=0.244,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1eYC2hZvEZeu for <xrblock@ietfa.amsl.com>; Fri, 20 Jan 2012 14:20:44 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 7671221F8648 for <xrblock@ietf.org>; Fri, 20 Jan 2012 14:20:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=620; q=dns/txt; s=iport; t=1327098044; x=1328307644; h=mime-version:content-transfer-encoding:subject:date: message-id:from:to; bh=6Jkn1sq1Hv/DWDV5CHgwvyGbhaojYqyECpV2AvUmJMw=; b=RoUNY+HCNI8VNfEHVRKNAoeYOKmksNTOeAp6f6Lurkytje/IrfZN/yIS /wZwqtfR9fAH0dPXBckQE0C3ewOmHkCiePEzsJeXNU72ASzmChvADq8qC S5u9RHWXxIgHVxG0rhH8dzkUNdrKbBP/VdTUCtnkqsmplJdzo0U5pC22S E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAAHoGU+rRDoI/2dsb2JhbABDrgqBBYF0AQQSAR0KUQEqBhgHVwEEGxqHYphygScBni2JCoI5YwSIPJ9J
X-IronPort-AV: E=Sophos;i="4.71,545,1320624000"; d="scan'208";a="26263635"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 20 Jan 2012 22:20:44 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q0KMKi0e028939 for <xrblock@ietf.org>; Fri, 20 Jan 2012 22:20:44 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 20 Jan 2012 14:20:43 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 20 Jan 2012 14:20:47 -0800
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C06343C6B@xmb-sjc-234.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WGLC for draft-ietf-xrblock-rtcp-xr-delay
Thread-Index: AczXwcIWLqsmIBPwQSirCUqvGlSbyg==
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: <xrblock@ietf.org>
X-OriginalArrivalTime: 20 Jan 2012 22:20:44.0120 (UTC) FILETIME=[C0435580:01CCD7C1]
Subject: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-delay
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jan 2012 22:20:45 -0000

(As WG Co-Chair)

This is an announcement of XRBLOCK WG last call on "RTCP XR Report Block
for Delay metric Reporting" prior to requesting publication of the
document as a proposed standard.=20

This is a two week working group last call. Please send your comments,
including nits, to the list by the 3rd of February.=20

If you read the draft and you see no issues, concerns, or nits, please
express the fact that you have no issue progressing the draft on the
list as well.=20

The latest version can be found here:
http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp-xr-delay/

Cheers,
Charles

From ron.even.tlv@gmail.com  Sat Jan 28 02:01:21 2012
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B075A21F853F for <xrblock@ietfa.amsl.com>; Sat, 28 Jan 2012 02:01:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[AWL=0.350,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3SallV0g-NMZ for <xrblock@ietfa.amsl.com>; Sat, 28 Jan 2012 02:01:21 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id C675D21F8533 for <xrblock@ietf.org>; Sat, 28 Jan 2012 02:01:20 -0800 (PST)
Received: by eekc1 with SMTP id c1so814045eek.31 for <xrblock@ietf.org>; Sat, 28 Jan 2012 02:01:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :content-language; bh=qjqKW1xivd+45uz3Jhx2qQoZWGUX1xRd9lTV6MBcpiQ=; b=LCe8pVQyAEujGGmgy+VmeG64AlSS+M/x7ZI4FHQv2ycXtWxkzSqnGOcFLIG2CfA1sH WSQaraM0tmlq6nIjMSVFetut4aHRwp4Jcc4aeIV7a8vqWfTGfP6vbV9rD81RIJz3YO5J KUw65nnmEaBOi4G6q8tldOELxAu88OjCVH2Bo=
Received: by 10.14.11.152 with SMTP id 24mr3282139eex.100.1327744879979; Sat, 28 Jan 2012 02:01:19 -0800 (PST)
Received: from windows8d787f9 ([109.67.208.29]) by mx.google.com with ESMTPS id e12sm41369545eea.5.2012.01.28.02.01.16 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 28 Jan 2012 02:01:17 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Charles Eckel \(eckelcu\)'" <eckelcu@cisco.com>, <xrblock@ietf.org>
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C06343C6B@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C06343C6B@xmb-sjc-234.amer.cisco.com>
Date: Sat, 28 Jan 2012 11:57:18 +0200
Message-ID: <4f23c76d.8c1b0e0a.5804.122a@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AczXwcIWLqsmIBPwQSirCUqvGlSbygF4Whrw
Content-Language: en-us
Subject: Re: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-delay
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Jan 2012 10:01:21 -0000

Hi,
I read  the draft and have no issues
Roni Even

> -----Original Message-----
> From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On
> Behalf Of Charles Eckel (eckelcu)
> Sent: Saturday, January 21, 2012 12:21 AM
> To: xrblock@ietf.org
> Subject: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-delay
> 
> (As WG Co-Chair)
> 
> This is an announcement of XRBLOCK WG last call on "RTCP XR Report
> Block for Delay metric Reporting" prior to requesting publication of
> the document as a proposed standard.
> 
> This is a two week working group last call. Please send your comments,
> including nits, to the list by the 3rd of February.
> 
> If you read the draft and you see no issues, concerns, or nits, please
> express the fact that you have no issue progressing the draft on the
> list as well.
> 
> The latest version can be found here:
> http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp-xr-delay/
> 
> Cheers,
> Charles
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock


From bill.wu@huawei.com  Sat Jan 28 18:52:15 2012
Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4665321F847F for <xrblock@ietfa.amsl.com>; Sat, 28 Jan 2012 18:52:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.289
X-Spam-Level: 
X-Spam-Status: No, score=-6.289 tagged_above=-999 required=5 tests=[AWL=0.310,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id miDMFH6ZenPY for <xrblock@ietfa.amsl.com>; Sat, 28 Jan 2012 18:52:13 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 8589321F842D for <xrblock@ietf.org>; Sat, 28 Jan 2012 18:52:13 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYJ00C0IHAUMQ@szxga05-in.huawei.com> for xrblock@ietf.org; Sun, 29 Jan 2012 10:52:07 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYJ00IJ1HAU6R@szxga05-in.huawei.com> for xrblock@ietf.org; Sun, 29 Jan 2012 10:52:06 +0800 (CST)
Received: from szxeml201-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGP46177; Sun, 29 Jan 2012 10:52:05 +0800
Received: from SZXEML424-HUB.china.huawei.com (10.82.67.163) by szxeml201-edg.china.huawei.com (172.24.2.39) with Microsoft SMTP Server (TLS) id 14.1.323.3; Sun, 29 Jan 2012 10:51:54 +0800
Received: from w53375q (10.138.41.130) by szxeml424-hub.china.huawei.com (10.82.67.163) with Microsoft SMTP Server (TLS) id 14.1.323.3; Sun, 29 Jan 2012 10:52:00 +0800
Date: Sun, 29 Jan 2012 10:51:59 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Varun Singh <vsingh.ietf@gmail.com>
Message-id: <2F08B302F22941BAB8EF057FDE2931A9@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <CAEbPqrz05RAbaq7sNb+W09pZSJedn=iEW2Sf_BR3mRho5c=Tdg@mail.gmail.com> <54DEF8D9713A4424933422B86EAD700D@china.huawei.com> <CAEbPqrxUWFv642yVSQrnTuFBSeVFwk3pVQBGbmGqVfB+zqgxjw@mail.gmail.com> <58EA66C004CC42338DB85F9C032C1CC3@china.huawei.com> <CAEbPqrw+jv_AcsA1NQwhUKfRTzUmqieLueGM5AhY69G9iEcTDA@mail.gmail.com> <F2E27ABE99474D4EA46C65D578BA35B5@china.huawei.com> <CAEbPqrzZzn=oBgai3=1sk4CT-8GMRtnZ=+aSrokrSL=oZZgnkQ@mail.gmail.com> <668E248B26E8402DA6E07957B288A094@china.huawei.com> <CAEbPqrwSE_mOcXEJKm_GqnAxpK98F26TVUAO623MwpocGsx5LQ@mail.gmail.com> <148184857F6741A6831B722743949B3C@china.huawei.com> <CAEbPqrwanaE7=rvezufae_=XrYPeCqNNth-kGzPzUnK2nRfANQ@mail.gmail.com>
Cc: xrblock@ietf.org
Subject: Re: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Jan 2012 02:52:15 -0000

Great, thank for taking my comments into account.

Regards!
-Qin
----- Original Message ----- 
From: "Varun Singh" <vsingh.ietf@gmail.com>
To: "Qin Wu" <bill.wu@huawei.com>
Cc: <xrblock@ietf.org>
Sent: Friday, January 20, 2012 8:26 PM
Subject: Re: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02


> Hi Qin,
> 
> I will make the changes that we have discussed and submit a new draft.
> If it is not clear in the new draft, then we can reopen the
> discussion.
> 
> 
> Regards,
> Varun
> 
> On Fri, Jan 20, 2012 at 04:31, Qin Wu <bill.wu@huawei.com> wrote:
>> Hi,
>> ----- Original Message -----
>>>From: "Varun Singh" <vsingh.ietf@gmail.com>
>>>To: "Qin Wu" <bill.wu@huawei.com>
>>>Cc: <xrblock@ietf.org>
>>>Sent: Thursday, January 19, 2012 8:03 PM
>>>Subject: Re: [xrblock] Upcoming changes indraft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02
>>
>>
>>>Hi Qin,
>>
>>>Comments inline
>>
>>>Cheers,
>>>Varun
>>
>>>>>> On Wed, Jan 18, 2012 at 03:34, Qin Wu <bill.wu@huawei.com> wrote:
>>>>>>> Hi, Varun:
>>>>>>> Please see my followup comments.
>>>>>>>
>>>>>>> Regards!
>>>>>>> -Qin
>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I am sending the updates to mailing list so that the discussion can
>>>>>>>>> take place before I post an updated draft.
>>>>>>>>>
>>>>>>>>> in -01, Section 1. Last para of introduction:
>>>>>>>>> Complementary to or instead of the indication which packets were
>>>>>>>>> discarded, an XR block is defined to indicate the number of bytes
>>>>>>>>> discarded, per interval or for the duration of the session, similar
>>>>>>>>> to other XR report blocks.
>>>>>>>>>
>>>>>>>>> Adding to that para in -02:
>>>>>>>>> Alternatively, if the sender keeps a
>>>>>>>>> history of the size of the packets reported in the measurement
>>>>>>>>> interval then the sender can calculate the number of bytes discarded
>>>>>>>>> from the information in the discard RLE block.
>>>>>>>>>
>>>>>>>>> - is this extra clarification needed?
>>>>>>>>
>>>>>>>> [Qin]: I think you don't need maintain the size for each packet, you only need to maintain
>>>>>>>> the total size for all the received packet before the next packet is coming.
>>>>>>>>
>>>>>>>
>>>>>>> The receiver needs to maintain the total size (for interval and for
>>>>>>> cumulative). However, the extra paragraph is to show that discarded
>>>>>>> bytes can also be calculated from the Discard RLE encoding--if the
>>>>>>> sender maintains the size of the sent packets. It can then add up the
>>>>>> size of packets marked in the RLE block using a lookup table.
>>>>>>>>
>>>>>>> [Qin]: Who calculates the size of packets? the reciever of dicard RLE block or the sender of byte dicarded block?
>>>>>>> My understanding is it should be the sender of byte dicarded block that calculates the size of packets.
>>>>>>> Your bytes discarded block should always be sent with dicard RLE block in the same compound RTCP packet.
>>>>>> Bytes discarded is a complementary mechanism to Discard RLE. It is up
>>>>>> to the implementer to choose from: packets discarded, bytes discarded,
>>>>>> discarded RLE (for their use-case). Discarded RLE is like a superset
>>>>>> and with it the sender can calculate packets and bytes discarded (if
>>>>>> it knows the size of the packets). So there is no need to send bytes
>>>>>> discarded and RLE together. In Sec 5
>>>>>> (http://tools.ietf.org/html/draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-01#section-5.1)
>>>>>> there is clarification for media receivers and media senders.
>>>>>>
>>>>>> [Qin]: What if dicard RLE block is lost?
>>>>>>
>>>>>
>>>>> I do not think the media sender can with 100% certainty detect that an
>>>> RLE block was lost. If the receiver sends an RLE block for every
>>>>> interval then the media sender could detect a missing interval from
>>>>> the sequence numbers that were not reported in the RLE. However, which
>>>>> XR blocks are reported in an interval depends on the
>>>>> implementation/logic at the receiver. For instance, if all packets are
>>>>> received then there is no need to send the RLE block. Moreover, if all
>>>>> packets are discarded then sending the RLE block has high overhead and
>>>>> the receiver may use the Packets Discarded XR Block.
>>>>
>>>> [Qin]: No doubt about this.
>>>> my point is if any discard RLE block is lost, the media sender can not calculate the accumulative total byte discard from the lost discard RLE block.
>>>>
>>>> But if the media receiver generate byte discard block and discard RLE block, you don't
>>>> have such issue since byte dicard block can be generated by media receiver based on associated discard RLE
>>>> block which has not been sent.
>>>>
>>
>>>Well this would be only true if the discard RLE and discarded bytes
>>>are sent separately. If they are sent together (in a compound RTCP)
>>>and the feedback message is lost then the media sender would not know.
>>
>> [Qin]: It doesn't matter if any discard RLE or discared byte RTCP XR block is lost.
>> Since the media receiver always know how many byte of media packet are discarded if media
>> receiver is responsible for calculating byte discarded for the received media packet during the
>> measurement interval.
>>
>> But if media sender is responsible for calcuating the byte discared, that will be different.
>>
>>>As an implementer a solution may be (there may be other alternatives):
>>>The discard RLE carries sequence numbers from overlapping intervals,
>>>i.e., begin_seq and end_seq of the RLE block are different from the
>>>current reporting interval (HSN_previous, HSN_current) and then you do
>>>not have to worry about a loss of an intermediate RTCP packet but this
>>>will increase the size of the packet depending on the length of the
>>>reporting intervals.
>>
>>
>>> Another issue I am thinking is are you assuming each discarded data packet you are tracking is equally size packet, otherwise, how do
>>> you calculate the total discared packet size.
>>
>>>No, and this is why I was proposing to add the additional paragraph in
>>>the Introduction: (copying from above, see original mail for exact
>>>details)
>>
>>>Adding to that para in -02:
>>>Alternatively, if the sender keeps a
>>>history of the size of the packets reported in the measurement
>>>interval then the sender can calculate the number of bytes discarded
>>>from the information in the discard RLE block.
>>
>> [Qin]: How does the sender know each discarded packet size? Isn't the sender signaled by the media receiver since only
>> terminal knows each discarded packet size.
>> Also I think that's a disadvantage if you ask media sender to calcuate byte discard.
>> If the media receiver calculate byte discard, you don't require media receiver to keep a history of the size of the packet.
>>
>>>>>>[Qin]: I think if any dicard RLE block is lost, this will prevent you keeping on
>>>>>> calculating the total byte lost or packet lost. How do you deal with this case?
>>>>
>>>>> To know an RTCP feedback packet is lost, the media sender would have
>>>>> received a new RTCP feedback packet. The media sender may use the
>>>>> information in the new RTCP report to react to congestion/scheduling.
>>>>> In the case of monitoring or storing metrics it is a problem because
>>>>> the media sender or the middlebox has a no information for the missing
>>>>> interval and could mark the bytes/packet discarded in the interval as
>>>>> "not enough information".
>>>>
>>>> [Qin]: That's a good point. That is to say monitoring and congestion control has different requirements for gathering
>>>> statistics information and dealing with these information.
>>>>
>>
>>>>Yes and this may be true for all the XR blocks.
>>
>> [Qin]: Agree.
> 
> 
> 
> -- 
> http://www.netlab.tkk.fi/~varun/

From shida@ntt-at.com  Sun Jan 29 02:23:08 2012
Return-Path: <shida@ntt-at.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1219B21F852A for <xrblock@ietfa.amsl.com>; Sun, 29 Jan 2012 02:23:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.618
X-Spam-Level: 
X-Spam-Status: No, score=-101.618 tagged_above=-999 required=5 tests=[AWL=-0.646, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, MISSING_HEADERS=1.292, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 68OvPzwN9USf for <xrblock@ietfa.amsl.com>; Sun, 29 Jan 2012 02:23:07 -0800 (PST)
Received: from gator465.hostgator.com (gator465.hostgator.com [69.56.174.130]) by ietfa.amsl.com (Postfix) with ESMTP id 68B8521F84A1 for <xrblock@ietf.org>; Sun, 29 Jan 2012 02:23:07 -0800 (PST)
Received: from [125.198.20.177] (port=64345 helo=[192.168.1.24]) by gator465.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <shida@ntt-at.com>) id 1RrRua-0003dD-Vo for xrblock@ietf.org; Sun, 29 Jan 2012 04:23:05 -0600
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1251.1)
From: Shida Schubert <shida@ntt-at.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C06343C6B@xmb-sjc-234.amer.cisco.com>
Date: Sun, 29 Jan 2012 19:23:03 +0900
Cc: xrblock <xrblock@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <B94A3D7E-5E61-4710-9AE0-416B8EF83DEB@ntt-at.com>
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C06343C6B@xmb-sjc-234.amer.cisco.com>
X-Mailer: Apple Mail (2.1251.1)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator465.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ntt-at.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: fl1-125-198-20-177.tky.mesh.ad.jp ([192.168.1.24]) [125.198.20.177]:64345
X-Source-Auth: shida.schubert@tingle.jp
X-Email-Count: 1
X-Source-Cap: c3NoaWRhO3NzaGlkYTtnYXRvcjQ2NS5ob3N0Z2F0b3IuY29t
Subject: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-delay (Ending on Feb 3)
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Jan 2012 10:23:08 -0000

Folks;

 The WGLC for this draft is ending in less than a week 
and we have only received one feedback. I highly 
encourage people to read the draft and provide comments 
or if you have read the current version already and you found 
no issue express it on the list. 

 Many Thanks
  Shida (As Co-Chair)

On Jan 21, 2012, at 7:20 AM, Charles Eckel (eckelcu) wrote:

> (As WG Co-Chair)
> 
> This is an announcement of XRBLOCK WG last call on "RTCP XR Report Block
> for Delay metric Reporting" prior to requesting publication of the
> document as a proposed standard. 
> 
> This is a two week working group last call. Please send your comments,
> including nits, to the list by the 3rd of February. 
> 
> If you read the draft and you see no issues, concerns, or nits, please
> express the fact that you have no issue progressing the draft on the
> list as well. 
> 
> The latest version can be found here:
> http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp-xr-delay/
> 
> Cheers,
> Charles
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock


From vsingh.ietf@gmail.com  Sun Jan 29 03:59:50 2012
Return-Path: <vsingh.ietf@gmail.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23E8621F84FB for <xrblock@ietfa.amsl.com>; Sun, 29 Jan 2012 03:59:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g6iPx3+m+mmK for <xrblock@ietfa.amsl.com>; Sun, 29 Jan 2012 03:59:49 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0555D21F8505 for <xrblock@ietf.org>; Sun, 29 Jan 2012 03:59:48 -0800 (PST)
Received: by werm10 with SMTP id m10so2961936wer.31 for <xrblock@ietf.org>; Sun, 29 Jan 2012 03:59:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=references:from:in-reply-to:mime-version:date:message-id:subject:to :cc:content-type; bh=M0WbNrRGcEIr8RlrL7UKiHqVGprm0QmvcrTM28JcWXg=; b=k6MMEX9VPMyDPob2MsPoPdGucX1Iz4kKuTLxnibfbtAWGSkU4fHpJ8qi7PLICEg2DB Ad9gJsC/DFhMOy2wDj8lPq61kQm1OvlL8TJaDVBEumjrwNSQUA1CAFFCsXhHBgey5xvb vXdwdfaTCbBB1KvWbWz8hftcmYDpMXEaVeVhI=
Received: by 10.216.137.210 with SMTP id y60mr5689819wei.14.1327838387908; Sun, 29 Jan 2012 03:59:47 -0800 (PST)
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C06343C6B@xmb-sjc-234.amer.cisco.com> <B94A3D7E-5E61-4710-9AE0-416B8EF83DEB@ntt-at.com>
From: Varun Singh <vsingh.ietf@gmail.com>
In-Reply-To: <B94A3D7E-5E61-4710-9AE0-416B8EF83DEB@ntt-at.com>
Mime-Version: 1.0 (1.0)
Date: Sun, 29 Jan 2012 12:59:50 +0100
Message-ID: <-897358013425672429@unknownmsgid>
To: Shida Schubert <shida@ntt-at.com>
Content-Type: multipart/alternative; boundary=0016e6d645696e311804b7a977f5
Cc: xrblock <xrblock@ietf.org>
Subject: Re: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-delay (Ending on Feb 3)
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Jan 2012 11:59:50 -0000

--0016e6d645696e311804b7a977f5
Content-Type: text/plain; charset=ISO-8859-1

Hi,

There is a nit:

 Interval Metric flag (I): 2 bit

      This field is used to indicate whether the Basic Loss/Discard
      metrics ...


Replace Basic loss/discard metric with delay metric.


Otherwise the draft looks okay.

Cheers,
Varun


On Jan 29, 2012, at 11:23, Shida Schubert <shida@ntt-at.com> wrote:


Folks;

The WGLC for this draft is ending in less than a week
and we have only received one feedback. I highly
encourage people to read the draft and provide comments
or if you have read the current version already and you found
no issue express it on the list.

Many Thanks
 Shida (As Co-Chair)

On Jan 21, 2012, at 7:20 AM, Charles Eckel (eckelcu) wrote:

(As WG Co-Chair)


This is an announcement of XRBLOCK WG last call on "RTCP XR Report Block

for Delay metric Reporting" prior to requesting publication of the

document as a proposed standard.


This is a two week working group last call. Please send your comments,

including nits, to the list by the 3rd of February.


If you read the draft and you see no issues, concerns, or nits, please

express the fact that you have no issue progressing the draft on the

list as well.


The latest version can be found here:

http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp-xr-delay/


Cheers,

Charles

_______________________________________________

xrblock mailing list

xrblock@ietf.org

https://www.ietf.org/mailman/listinfo/xrblock


_______________________________________________
xrblock mailing list
xrblock@ietf.org
https://www.ietf.org/mailman/listinfo/xrblock

--0016e6d645696e311804b7a977f5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<html><head></head><body bgcolor=3D"#FFFFFF"><div><br>Hi,</div><div><br></d=
iv><div>There is a nit:<br><pre class=3D"newpage" style=3D"margin-top:0px;m=
argin-bottom:0px"><font class=3D"Apple-style-span" face=3D"Helvetica"><span=
 class=3D"Apple-style-span" style=3D"white-space:normal">=A0Interval Metric=
 flag (I): 2 bit

      This field is used to indicate whether the Basic Loss/Discard
      metrics ...</span></font></pre><pre class=3D"newpage" style=3D"margin=
-top:0px;margin-bottom:0px"><font class=3D"Apple-style-span" face=3D"Helvet=
ica"><span class=3D"Apple-style-span" style=3D"white-space:normal"><br></sp=
an></font></pre>
<pre class=3D"newpage" style=3D"margin-top:0px;margin-bottom:0px"><font cla=
ss=3D"Apple-style-span" face=3D"Helvetica"><span class=3D"Apple-style-span"=
 style=3D"white-space:normal">Replace Basic loss/discard metric with delay =
metric.=A0</span></font></pre>
</div><div><br></div><div>Otherwise the draft looks okay.=A0</div><div><br>=
</div><div>Cheers,</div><div>Varun</div><div><br></div><div><br>On Jan 29, =
2012, at 11:23, Shida Schubert &lt;<a href=3D"mailto:shida@ntt-at.com">shid=
a@ntt-at.com</a>&gt; wrote:<br>
<br></div><div></div><blockquote type=3D"cite"><div><span></span><br><span>=
Folks;</span><br><span></span><br><span> The WGLC for this draft is ending =
in less than a week </span><br><span>and we have only received one feedback=
. I highly </span><br>
<span>encourage people to read the draft and provide comments </span><br><s=
pan>or if you have read the current version already and you found </span><b=
r><span>no issue express it on the list. </span><br><span></span><br><span>=
 Many Thanks</span><br>
<span> =A0Shida (As Co-Chair)</span><br><span></span><br><span>On Jan 21, 2=
012, at 7:20 AM, Charles Eckel (eckelcu) wrote:</span><br><span></span><br>=
<blockquote type=3D"cite"><span>(As WG Co-Chair)</span><br></blockquote><bl=
ockquote type=3D"cite">
<span></span><br></blockquote><blockquote type=3D"cite"><span>This is an an=
nouncement of XRBLOCK WG last call on &quot;RTCP XR Report Block</span><br>=
</blockquote><blockquote type=3D"cite"><span>for Delay metric Reporting&quo=
t; prior to requesting publication of the</span><br>
</blockquote><blockquote type=3D"cite"><span>document as a proposed standar=
d. </span><br></blockquote><blockquote type=3D"cite"><span></span><br></blo=
ckquote><blockquote type=3D"cite"><span>This is a two week working group la=
st call. Please send your comments,</span><br>
</blockquote><blockquote type=3D"cite"><span>including nits, to the list by=
 the 3rd of February. </span><br></blockquote><blockquote type=3D"cite"><sp=
an></span><br></blockquote><blockquote type=3D"cite"><span>If you read the =
draft and you see no issues, concerns, or nits, please</span><br>
</blockquote><blockquote type=3D"cite"><span>express the fact that you have=
 no issue progressing the draft on the</span><br></blockquote><blockquote t=
ype=3D"cite"><span>list as well. </span><br></blockquote><blockquote type=
=3D"cite">
<span></span><br></blockquote><blockquote type=3D"cite"><span>The latest ve=
rsion can be found here:</span><br></blockquote><blockquote type=3D"cite"><=
span><a href=3D"http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp-xr=
-delay/">http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp-xr-delay/=
</a></span><br>
</blockquote><blockquote type=3D"cite"><span></span><br></blockquote><block=
quote type=3D"cite"><span>Cheers,</span><br></blockquote><blockquote type=
=3D"cite"><span>Charles</span><br></blockquote><blockquote type=3D"cite"><s=
pan>_______________________________________________</span><br>
</blockquote><blockquote type=3D"cite"><span>xrblock mailing list</span><br=
></blockquote><blockquote type=3D"cite"><span><a href=3D"mailto:xrblock@iet=
f.org">xrblock@ietf.org</a></span><br></blockquote><blockquote type=3D"cite=
"><span><a href=3D"https://www.ietf.org/mailman/listinfo/xrblock">https://w=
ww.ietf.org/mailman/listinfo/xrblock</a></span><br>
</blockquote><span></span><br><span>_______________________________________=
________</span><br><span>xrblock mailing list</span><br><span><a href=3D"ma=
ilto:xrblock@ietf.org">xrblock@ietf.org</a></span><br><span><a href=3D"http=
s://www.ietf.org/mailman/listinfo/xrblock">https://www.ietf.org/mailman/lis=
tinfo/xrblock</a></span><br>
</div></blockquote></body></html>

--0016e6d645696e311804b7a977f5--

From kevin.gross@avanw.com  Sun Jan 29 16:19:11 2012
Return-Path: <kevin.gross@avanw.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C897F21F84E4 for <xrblock@ietfa.amsl.com>; Sun, 29 Jan 2012 16:19:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.334
X-Spam-Level: 
X-Spam-Status: No, score=0.334 tagged_above=-999 required=5 tests=[AWL=0.207,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gAQ2PNiXqV-g for <xrblock@ietfa.amsl.com>; Sun, 29 Jan 2012 16:19:11 -0800 (PST)
Received: from oproxy7-pub.bluehost.com (oproxy7.bluehost.com [IPv6:2605:dc00:100:2::a7]) by ietfa.amsl.com (Postfix) with SMTP id F2FC521F84E0 for <xrblock@ietf.org>; Sun, 29 Jan 2012 16:19:10 -0800 (PST)
Received: (qmail 16444 invoked by uid 0); 30 Jan 2012 00:19:10 -0000
Received: from unknown (HELO host291.hostmonster.com) (74.220.215.91) by oproxy7.bluehost.com with SMTP; 30 Jan 2012 00:19:10 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avanw.com; s=default;  h=Content-Type:To:From:Subject:Message-ID:Date:References:In-Reply-To:MIME-Version; bh=+FC9qeRijxrJTyhvm/BjnI6eOhrHw5oZn2d2lQMvukE=;  b=ItwQbThFGap46/cKTf9xnRxRizqCDQKkGRr1gNORci7VWleHufju79Kdd6j8tr++dWyu56ibq3yrg61VWn7RlmIif5Z58yhxyFePLf9pMWu8Vc9jspN0SZOxjmv93kya;
Received: from mail-we0-f172.google.com ([74.125.82.172]) by host291.hostmonster.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from <kevin.gross@avanw.com>) id 1Rrexh-0004HB-Rh for xrblock@ietf.org; Sun, 29 Jan 2012 17:19:10 -0700
Received: by werm10 with SMTP id m10so3290165wer.31 for <xrblock@ietf.org>; Sun, 29 Jan 2012 16:19:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.180.105.129 with SMTP id gm1mr22999588wib.1.1327882748469; Sun, 29 Jan 2012 16:19:08 -0800 (PST)
Received: by 10.223.97.10 with HTTP; Sun, 29 Jan 2012 16:19:08 -0800 (PST)
In-Reply-To: <B94A3D7E-5E61-4710-9AE0-416B8EF83DEB@ntt-at.com>
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C06343C6B@xmb-sjc-234.amer.cisco.com> <B94A3D7E-5E61-4710-9AE0-416B8EF83DEB@ntt-at.com>
Date: Sun, 29 Jan 2012 17:19:08 -0700
Message-ID: <CALw1_Q02jTNOZPKbiOkgJBMkWOnHFmKtLDBiQjjPr8v5UPnfTg@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: xrblock <xrblock@ietf.org>
Content-Type: multipart/alternative; boundary=f46d0418262686a02c04b7b3cb24
X-Identified-User: {1416:host291.hostmonster.com:avanwcom:avanw.com} {sentby:smtp auth 74.125.82.172 authed with kevin.gross@avanw.com}
Subject: Re: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-delay (Ending on Feb 3)
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jan 2012 00:19:11 -0000

--f46d0418262686a02c04b7b3cb24
Content-Type: text/plain; charset=ISO-8859-1

I would like to suggest that milliseconds are too crude a measurement for
modern IP networks. IP forwarding is accomplished in a small number of
microseconds by current hardware. Many applications operate locally and are
not significantly burdened by the speed of light. Live media and financial
processing applications do take advantage of this performance and would
benefit from improved resolution in these metrics. I would suggest
microsecond precision would be minimally adequate.

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


On Sun, Jan 29, 2012 at 3:23 AM, Shida Schubert <shida@ntt-at.com> wrote:

>
> Folks;
>
>  The WGLC for this draft is ending in less than a week
> and we have only received one feedback. I highly
> encourage people to read the draft and provide comments
> or if you have read the current version already and you found
> no issue express it on the list.
>
>  Many Thanks
>  Shida (As Co-Chair)
>
> On Jan 21, 2012, at 7:20 AM, Charles Eckel (eckelcu) wrote:
>
> > (As WG Co-Chair)
> >
> > This is an announcement of XRBLOCK WG last call on "RTCP XR Report Block
> > for Delay metric Reporting" prior to requesting publication of the
> > document as a proposed standard.
> >
> > This is a two week working group last call. Please send your comments,
> > including nits, to the list by the 3rd of February.
> >
> > If you read the draft and you see no issues, concerns, or nits, please
> > express the fact that you have no issue progressing the draft on the
> > list as well.
> >
> > The latest version can be found here:
> > http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp-xr-delay/
> >
> > Cheers,
> > Charles
> > _______________________________________________
> > xrblock mailing list
> > xrblock@ietf.org
> > https://www.ietf.org/mailman/listinfo/xrblock
>
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock
>

--f46d0418262686a02c04b7b3cb24
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I would like to suggest that milliseconds are too crude a measurement for m=
odern IP networks. IP forwarding is accomplished in a small number of micro=
seconds by current hardware. Many applications operate locally and are not =
significantly burdened by the speed of light. Live media and financial proc=
essing applications do take advantage of this performance and would benefit=
 from improved resolution in these metrics. I would suggest microsecond pre=
cision would be minimally adequate.<div>
<br clear=3D"all">Kevin Gross<br><div>+1-303-447-0517</div><div>Media Netwo=
rk Consultant<br><div>AVA Networks -=A0<a href=3D"http://www.avanw.com/" ta=
rget=3D"_blank">www.AVAnw.com</a>,=A0<a href=3D"http://www.X192.org" target=
=3D"_blank">www.X192.org</a></div>
</div>
<br><br><div class=3D"gmail_quote">On Sun, Jan 29, 2012 at 3:23 AM, Shida S=
chubert <span dir=3D"ltr">&lt;<a href=3D"mailto:shida@ntt-at.com">shida@ntt=
-at.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Folks;<br>
<br>
=A0The WGLC for this draft is ending in less than a week<br>
and we have only received one feedback. I highly<br>
encourage people to read the draft and provide comments<br>
or if you have read the current version already and you found<br>
no issue express it on the list.<br>
<br>
=A0Many Thanks<br>
 =A0Shida (As Co-Chair)<br>
<br>
On Jan 21, 2012, at 7:20 AM, Charles Eckel (eckelcu) wrote:<br>
<br>
&gt; (As WG Co-Chair)<br>
&gt;<br>
&gt; This is an announcement of XRBLOCK WG last call on &quot;RTCP XR Repor=
t Block<br>
&gt; for Delay metric Reporting&quot; prior to requesting publication of th=
e<br>
&gt; document as a proposed standard.<br>
&gt;<br>
&gt; This is a two week working group last call. Please send your comments,=
<br>
&gt; including nits, to the list by the 3rd of February.<br>
&gt;<br>
&gt; If you read the draft and you see no issues, concerns, or nits, please=
<br>
&gt; express the fact that you have no issue progressing the draft on the<b=
r>
&gt; list as well.<br>
&gt;<br>
&gt; The latest version can be found here:<br>
&gt; <a href=3D"http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp-xr=
-delay/" target=3D"_blank">http://tools.ietf.org/wg/xrblock/draft-ietf-xrbl=
ock-rtcp-xr-delay/</a><br>
&gt;<br>
&gt; Cheers,<br>
&gt; Charles<br>
&gt; _______________________________________________<br>
&gt; xrblock mailing list<br>
&gt; <a href=3D"mailto:xrblock@ietf.org">xrblock@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/xrblock" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/xrblock</a><br>
<br>
_______________________________________________<br>
xrblock mailing list<br>
<a href=3D"mailto:xrblock@ietf.org">xrblock@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/xrblock" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/xrblock</a><br>
</blockquote></div><br></div>

--f46d0418262686a02c04b7b3cb24--

From bill.wu@huawei.com  Sun Jan 29 23:52:02 2012
Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B984B21F85EC for <xrblock@ietfa.amsl.com>; Sun, 29 Jan 2012 23:52:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.298
X-Spam-Level: 
X-Spam-Status: No, score=-6.298 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BtO2H4aA2+7f for <xrblock@ietfa.amsl.com>; Sun, 29 Jan 2012 23:52:02 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 3314821F85E9 for <xrblock@ietf.org>; Sun, 29 Jan 2012 23:52:01 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYL00735PUFPL@szxga05-in.huawei.com> for xrblock@ietf.org; Mon, 30 Jan 2012 15:51:51 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYL002A2PUB58@szxga05-in.huawei.com> for xrblock@ietf.org; Mon, 30 Jan 2012 15:51:51 +0800 (CST)
Received: from szxeml214-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGP63664; Mon, 30 Jan 2012 15:51:50 +0800
Received: from SZXEML410-HUB.china.huawei.com (10.82.67.137) by szxeml214-edg.china.huawei.com (172.24.2.29) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 30 Jan 2012 15:51:24 +0800
Received: from w53375q (10.138.41.130) by szxeml410-hub.china.huawei.com (10.82.67.137) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 30 Jan 2012 15:51:48 +0800
Date: Mon, 30 Jan 2012 15:51:47 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Varun Singh <vsingh.ietf@gmail.com>, Shida Schubert <shida@ntt-at.com>
Message-id: <3FDFA9D20B5B48A79F1100014F2720E6@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: multipart/alternative; boundary="Boundary_(ID_QgmUgIxOsG/qlHWJld90gA)"
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C06343C6B@xmb-sjc-234.amer.cisco.com> <B94A3D7E-5E61-4710-9AE0-416B8EF83DEB@ntt-at.com> <-897358013425672429@unknownmsgid>
Cc: xrblock <xrblock@ietf.org>
Subject: Re: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-delay (Ending on Feb 3)
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jan 2012 07:52:02 -0000

--Boundary_(ID_QgmUgIxOsG/qlHWJld90gA)
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

Agree, will fix this.
  ----- Original Message ----- 
  From: Varun Singh 
  To: Shida Schubert 
  Cc: xrblock 
  Sent: Sunday, January 29, 2012 7:59 PM
  Subject: Re: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-delay (Ending on Feb 3)



  Hi,


  There is a nit:

 Interval Metric flag (I): 2 bit

      This field is used to indicate whether the Basic Loss/Discard
      metrics ...Replace Basic loss/discard metric with delay metric. 

  Otherwise the draft looks okay. 


  Cheers,
  Varun



  On Jan 29, 2012, at 11:23, Shida Schubert <shida@ntt-at.com> wrote:



    Folks;

    The WGLC for this draft is ending in less than a week 
    and we have only received one feedback. I highly 
    encourage people to read the draft and provide comments 
    or if you have read the current version already and you found 
    no issue express it on the list. 

    Many Thanks
     Shida (As Co-Chair)

    On Jan 21, 2012, at 7:20 AM, Charles Eckel (eckelcu) wrote:


      (As WG Co-Chair)



      This is an announcement of XRBLOCK WG last call on "RTCP XR Report Block

      for Delay metric Reporting" prior to requesting publication of the

      document as a proposed standard. 



      This is a two week working group last call. Please send your comments,

      including nits, to the list by the 3rd of February. 



      If you read the draft and you see no issues, concerns, or nits, please

      express the fact that you have no issue progressing the draft on the

      list as well. 



      The latest version can be found here:

      http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp-xr-delay/



      Cheers,

      Charles

      _______________________________________________

      xrblock mailing list

      xrblock@ietf.org

      https://www.ietf.org/mailman/listinfo/xrblock


    _______________________________________________
    xrblock mailing list
    xrblock@ietf.org
    https://www.ietf.org/mailman/listinfo/xrblock



------------------------------------------------------------------------------


  _______________________________________________
  xrblock mailing list
  xrblock@ietf.org
  https://www.ietf.org/mailman/listinfo/xrblock

--Boundary_(ID_QgmUgIxOsG/qlHWJld90gA)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19170">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV>Agree, will fix this.</DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
  <DIV style="FONT: 9pt &#23435;&#20307;">----- Original Message ----- </DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> 
  <A title=vsingh.ietf@gmail.com href="mailto:vsingh.ietf@gmail.com">Varun 
  Singh</A> </DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;"><B>To:</B> <A title=shida@ntt-at.com 
  href="mailto:shida@ntt-at.com">Shida Schubert</A> </DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;"><B>Cc:</B> <A title=xrblock@ietf.org 
  href="mailto:xrblock@ietf.org">xrblock</A> </DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;"><B>Sent:</B> Sunday, January 29, 2012 7:59 PM</DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;"><B>Subject:</B> Re: [xrblock] WGLC for 
  draft-ietf-xrblock-rtcp-xr-delay (Ending on Feb 3)</DIV>
  <DIV><BR></DIV>
  <DIV><BR>Hi,</DIV>
  <DIV><BR></DIV>
  <DIV>There is a nit:<BR><PRE style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px" class=newpage><FONT class=Apple-style-span face=Helvetica><SPAN style="WHITE-SPACE: normal" class=Apple-style-span>&nbsp;Interval Metric flag (I): 2 bit

      This field is used to indicate whether the Basic Loss/Discard
      metrics ...</SPAN></FONT></PRE><PRE style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px" class=newpage><FONT class=Apple-style-span face=Helvetica><SPAN style="WHITE-SPACE: normal" class=Apple-style-span><BR></SPAN></FONT></PRE><PRE style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px" class=newpage><FONT class=Apple-style-span face=Helvetica><SPAN style="WHITE-SPACE: normal" class=Apple-style-span>Replace Basic loss/discard metric with delay metric.&nbsp;</SPAN></FONT></PRE></DIV>
  <DIV><BR></DIV>
  <DIV>Otherwise the draft looks okay.&nbsp;</DIV>
  <DIV><BR></DIV>
  <DIV>Cheers,</DIV>
  <DIV>Varun</DIV>
  <DIV><BR></DIV>
  <DIV><BR>On Jan 29, 2012, at 11:23, Shida Schubert &lt;<A 
  href="mailto:shida@ntt-at.com">shida@ntt-at.com</A>&gt; wrote:<BR><BR></DIV>
  <DIV></DIV>
  <BLOCKQUOTE type="cite">
    <DIV><SPAN></SPAN><BR><SPAN>Folks;</SPAN><BR><SPAN></SPAN><BR><SPAN>The WGLC 
    for this draft is ending in less than a week </SPAN><BR><SPAN>and we have 
    only received one feedback. I highly </SPAN><BR><SPAN>encourage people to 
    read the draft and provide comments </SPAN><BR><SPAN>or if you have read the 
    current version already and you found </SPAN><BR><SPAN>no issue express it 
    on the list. </SPAN><BR><SPAN></SPAN><BR><SPAN>Many 
    Thanks</SPAN><BR><SPAN>&nbsp;Shida (As 
    Co-Chair)</SPAN><BR><SPAN></SPAN><BR><SPAN>On Jan 21, 2012, at 7:20 AM, 
    Charles Eckel (eckelcu) wrote:</SPAN><BR><SPAN></SPAN><BR>
    <BLOCKQUOTE type="cite"><SPAN>(As WG Co-Chair)</SPAN><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><SPAN>This is an announcement of XRBLOCK WG last 
      call on "RTCP XR Report Block</SPAN><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><SPAN>for Delay metric Reporting" prior to 
      requesting publication of the</SPAN><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><SPAN>document as a proposed standard. 
    </SPAN><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><SPAN>This is a two week working group last call. 
      Please send your comments,</SPAN><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><SPAN>including nits, to the list by the 3rd of 
      February. </SPAN><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><SPAN>If you read the draft and you see no issues, 
      concerns, or nits, please</SPAN><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><SPAN>express the fact that you have no issue 
      progressing the draft on the</SPAN><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><SPAN>list as well. </SPAN><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><SPAN>The latest version can be found 
      here:</SPAN><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><SPAN><A 
      href="http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp-xr-delay/">http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp-xr-delay/</A></SPAN><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><SPAN></SPAN><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><SPAN>Cheers,</SPAN><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><SPAN>Charles</SPAN><BR></BLOCKQUOTE>
    <BLOCKQUOTE 
      type="cite"><SPAN>_______________________________________________</SPAN><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><SPAN>xrblock mailing list</SPAN><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><SPAN><A 
      href="mailto:xrblock@ietf.org">xrblock@ietf.org</A></SPAN><BR></BLOCKQUOTE>
    <BLOCKQUOTE type="cite"><SPAN><A 
      href="https://www.ietf.org/mailman/listinfo/xrblock">https://www.ietf.org/mailman/listinfo/xrblock</A></SPAN><BR></BLOCKQUOTE><SPAN></SPAN><BR><SPAN>_______________________________________________</SPAN><BR><SPAN>xrblock 
    mailing list</SPAN><BR><SPAN><A 
    href="mailto:xrblock@ietf.org">xrblock@ietf.org</A></SPAN><BR><SPAN><A 
    href="https://www.ietf.org/mailman/listinfo/xrblock">https://www.ietf.org/mailman/listinfo/xrblock</A></SPAN><BR></DIV></BLOCKQUOTE>
  <P>
  <HR>

  <P></P>_______________________________________________<BR>xrblock mailing 
  list<BR>xrblock@ietf.org<BR>https://www.ietf.org/mailman/listinfo/xrblock<BR></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_QgmUgIxOsG/qlHWJld90gA)--

From bill.wu@huawei.com  Sun Jan 29 23:53:23 2012
Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF9FC21F85F0 for <xrblock@ietfa.amsl.com>; Sun, 29 Jan 2012 23:53:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.864
X-Spam-Level: 
X-Spam-Status: No, score=-5.864 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e6WRH0U0uo0F for <xrblock@ietfa.amsl.com>; Sun, 29 Jan 2012 23:53:22 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 977DF21F85EF for <xrblock@ietf.org>; Sun, 29 Jan 2012 23:53:22 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYL00GOSPU1TB@szxga03-in.huawei.com> for xrblock@ietf.org; Mon, 30 Jan 2012 15:51:38 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYL00FMGPU1CC@szxga03-in.huawei.com> for xrblock@ietf.org; Mon, 30 Jan 2012 15:51:37 +0800 (CST)
Received: from szxeml214-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGP63619; Mon, 30 Jan 2012 15:51:36 +0800
Received: from SZXEML403-HUB.china.huawei.com (10.82.67.35) by szxeml214-edg.china.huawei.com (172.24.2.29) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 30 Jan 2012 15:51:09 +0800
Received: from w53375q (10.138.41.130) by szxeml403-hub.china.huawei.com (10.82.67.35) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 30 Jan 2012 15:51:31 +0800
Date: Mon, 30 Jan 2012 15:51:31 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Kevin Gross <kevin.gross@avanw.com>, xrblock <xrblock@ietf.org>
Message-id: <C49ED29691C543D38064457E3E71E37F@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: multipart/alternative; boundary="Boundary_(ID_ZGUQxZQ87jkQYirU9eXe4w)"
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C06343C6B@xmb-sjc-234.amer.cisco.com> <B94A3D7E-5E61-4710-9AE0-416B8EF83DEB@ntt-at.com> <CALw1_Q02jTNOZPKbiOkgJBMkWOnHFmKtLDBiQjjPr8v5UPnfTg@mail.gmail.com>
Subject: Re: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-delay (Ending on Feb 3)
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jan 2012 07:53:24 -0000

--Boundary_(ID_ZGUQxZQ87jkQYirU9eXe4w)
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

Hi, Kevin:
The round trip delay metric defined in the draft-ietf-xrblock-rtcp-xr-delay is determined using RTCP SR/RR in RFC3550.
according to the following formula:
round-trip delay = (A - LSR - DLSR)
or using RTCP RRTR/DLRR in RFC3611 according to the following formula:
round -trip delay=(A-LRR-DLRR)

The measurement method for round trip delay is defined in the section 6.4.1 or figure 2 of RFC3550.

With the current measurement method defined in the RFC3550, microsecond precision requirement is hard to be satisifed, since
the measurement precision of the delay metric is limited to far less than the Minimum precision of LSR or DLSR in the above formula. The LSR and DLSR precision
is 1/2^16 second that is greater than 1 microsecond.

Hope this clarifies.


Regards!
-Qin
----- Original Message ----- 
  From: Kevin Gross 
  To: xrblock 
  Sent: Monday, January 30, 2012 8:19 AM
  Subject: Re: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-delay (Ending on Feb 3)


  I would like to suggest that milliseconds are too crude a measurement for modern IP networks. IP forwarding is accomplished in a small number of microseconds by current hardware. Many applications operate locally and are not significantly burdened by the speed of light. Live media and financial processing applications do take advantage of this performance and would benefit from improved resolution in these metrics. I would suggest microsecond precision would be minimally adequate.

  Kevin Gross

  +1-303-447-0517
  Media Network Consultant

  AVA Networks - www.AVAnw.com, www.X192.org



  On Sun, Jan 29, 2012 at 3:23 AM, Shida Schubert <shida@ntt-at.com> wrote:


    Folks;

     The WGLC for this draft is ending in less than a week
    and we have only received one feedback. I highly
    encourage people to read the draft and provide comments
    or if you have read the current version already and you found
    no issue express it on the list.

     Many Thanks
     Shida (As Co-Chair)

    On Jan 21, 2012, at 7:20 AM, Charles Eckel (eckelcu) wrote:

    > (As WG Co-Chair)
    >
    > This is an announcement of XRBLOCK WG last call on "RTCP XR Report Block
    > for Delay metric Reporting" prior to requesting publication of the
    > document as a proposed standard.
    >
    > This is a two week working group last call. Please send your comments,
    > including nits, to the list by the 3rd of February.
    >
    > If you read the draft and you see no issues, concerns, or nits, please
    > express the fact that you have no issue progressing the draft on the
    > list as well.
    >
    > The latest version can be found here:
    > http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp-xr-delay/
    >
    > Cheers,
    > Charles
    > _______________________________________________
    > xrblock mailing list
    > xrblock@ietf.org
    > https://www.ietf.org/mailman/listinfo/xrblock

    _______________________________________________
    xrblock mailing list
    xrblock@ietf.org
    https://www.ietf.org/mailman/listinfo/xrblock





------------------------------------------------------------------------------


  _______________________________________________
  xrblock mailing list
  xrblock@ietf.org
  https://www.ietf.org/mailman/listinfo/xrblock

--Boundary_(ID_ZGUQxZQ87jkQYirU9eXe4w)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19170">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV>Hi, Kevin:</DIV>
<DIV>The round trip delay metric defined in the draft-ietf-xrblock-rtcp-xr-delay 
is determined using RTCP SR/RR in RFC3550.</DIV>
<DIV>according to the following formula:</DIV>
<DIV>round-trip&nbsp;delay&nbsp;= (A - LSR - DLSR)
<DIV>or using RTCP RRTR/DLRR in RFC3611 according to the following 
formula:</DIV>
<DIV>round -trip delay=(A-LRR-DLRR)</DIV></DIV>
<DIV><FONT size=2 face=&#23435;&#20307;></FONT>&nbsp;</DIV>
<DIV>The measurement method for round trip delay&nbsp;is defined in the section 
6.4.1 or figure 2 of RFC3550.</DIV>
<DIV><FONT size=2 face=&#23435;&#20307;></FONT>&nbsp;</DIV>
<DIV>With the current measurement method defined in the RFC3550, microsecond 
precision requirement is hard to be satisifed, since</DIV>
<DIV>the measurement precision of the delay metric is limited to far less than 
the <SPAN class=st>Minimum precision of LSR or DLSR in the above formula. The 
LSR and DLSR precision</SPAN></DIV>
<DIV><SPAN class=st>is 1/2^16 second that is greater than 1 
microsecond.</SPAN></DIV>
<DIV><SPAN class=st><FONT size=2 face=&#23435;&#20307;></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=st>Hope this clarifies.</SPAN></DIV>
<DIV><FONT size=2 face=&#23435;&#20307;></FONT>&nbsp;</DIV>
<DIV><FONT size=2 face=&#23435;&#20307;></FONT>&nbsp;</DIV>
<DIV>Regards!</DIV>
<DIV>-Qin</DIV>
<DIV>----- Original Message ----- </DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
  <DIV style="FONT: 9pt &#23435;&#20307;; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> 
  <A title=kevin.gross@avanw.com href="mailto:kevin.gross@avanw.com">Kevin 
  Gross</A> </DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;"><B>To:</B> <A title=xrblock@ietf.org 
  href="mailto:xrblock@ietf.org">xrblock</A> </DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;"><B>Sent:</B> Monday, January 30, 2012 8:19 AM</DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;"><B>Subject:</B> Re: [xrblock] WGLC for 
  draft-ietf-xrblock-rtcp-xr-delay (Ending on Feb 3)</DIV>
  <DIV><BR></DIV>I would like to suggest that milliseconds are too crude a 
  measurement for modern IP networks. IP forwarding is accomplished in a small 
  number of microseconds by current hardware. Many applications operate locally 
  and are not significantly burdened by the speed of light. Live media and 
  financial processing applications do take advantage of this performance and 
  would benefit from improved resolution in these metrics. I would suggest 
  microsecond precision would be minimally adequate.
  <DIV><BR clear=all>Kevin Gross<BR>
  <DIV>+1-303-447-0517</DIV>
  <DIV>Media Network Consultant<BR>
  <DIV>AVA Networks -&nbsp;<A href="http://www.avanw.com/" 
  target=_blank>www.AVAnw.com</A>,&nbsp;<A href="http://www.X192.org" 
  target=_blank>www.X192.org</A></DIV></DIV><BR><BR>
  <DIV class=gmail_quote>On Sun, Jan 29, 2012 at 3:23 AM, Shida Schubert <SPAN 
  dir=ltr>&lt;<A href="mailto:shida@ntt-at.com">shida@ntt-at.com</A>&gt;</SPAN> 
  wrote:<BR>
  <BLOCKQUOTE 
  style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" 
  class=gmail_quote><BR>Folks;<BR><BR>&nbsp;The WGLC for this draft is ending 
    in less than a week<BR>and we have only received one feedback. I 
    highly<BR>encourage people to read the draft and provide comments<BR>or if 
    you have read the current version already and you found<BR>no issue express 
    it on the list.<BR><BR>&nbsp;Many Thanks<BR>&nbsp;Shida (As 
    Co-Chair)<BR><BR>On Jan 21, 2012, at 7:20 AM, Charles Eckel (eckelcu) 
    wrote:<BR><BR>&gt; (As WG Co-Chair)<BR>&gt;<BR>&gt; This is an announcement 
    of XRBLOCK WG last call on "RTCP XR Report Block<BR>&gt; for Delay metric 
    Reporting" prior to requesting publication of the<BR>&gt; document as a 
    proposed standard.<BR>&gt;<BR>&gt; This is a two week working group last 
    call. Please send your comments,<BR>&gt; including nits, to the list by the 
    3rd of February.<BR>&gt;<BR>&gt; If you read the draft and you see no 
    issues, concerns, or nits, please<BR>&gt; express the fact that you have no 
    issue progressing the draft on the<BR>&gt; list as well.<BR>&gt;<BR>&gt; The 
    latest version can be found here:<BR>&gt; <A 
    href="http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp-xr-delay/" 
    target=_blank>http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp-xr-delay/</A><BR>&gt;<BR>&gt; 
    Cheers,<BR>&gt; Charles<BR>&gt; 
    _______________________________________________<BR>&gt; xrblock mailing 
    list<BR>&gt; <A href="mailto:xrblock@ietf.org">xrblock@ietf.org</A><BR>&gt; 
    <A href="https://www.ietf.org/mailman/listinfo/xrblock" 
    target=_blank>https://www.ietf.org/mailman/listinfo/xrblock</A><BR><BR>_______________________________________________<BR>xrblock 
    mailing list<BR><A href="mailto:xrblock@ietf.org">xrblock@ietf.org</A><BR><A 
    href="https://www.ietf.org/mailman/listinfo/xrblock" 
    target=_blank>https://www.ietf.org/mailman/listinfo/xrblock</A><BR></BLOCKQUOTE></DIV><BR></DIV>
  <P>
  <HR>

  <P></P>_______________________________________________<BR>xrblock mailing 
  list<BR>xrblock@ietf.org<BR>https://www.ietf.org/mailman/listinfo/xrblock<BR></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_ZGUQxZQ87jkQYirU9eXe4w)--

From internet-drafts@ietf.org  Mon Jan 30 04:49:43 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3E4C21F86C3; Mon, 30 Jan 2012 04:49:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.586
X-Spam-Level: 
X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jVHmN4C7Fv+c; Mon, 30 Jan 2012 04:49:41 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B92E821F86C2; Mon, 30 Jan 2012 04:49:39 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20120130124939.12860.25709.idtracker@ietfa.amsl.com>
Date: Mon, 30 Jan 2012 04:49:39 -0800
Cc: xrblock@ietf.org
Subject: [xrblock] I-D Action: draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jan 2012 12:49:43 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Metric Blocks for use with RTCP's Ext=
ended Report Framework Working Group of the IETF.

	Title           : Real-time Transport Control Protocol (RTCP) Extension Re=
port (XR) for Run Length Encoding of Discarded Packets
	Author(s)       : Joerg Ott
                          Varun Singh
                          Igor D.D. Curcio
	Filename        : draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02.txt
	Pages           : 11
	Date            : 2012-01-30

   The Real-time Transport Control Protocol (RTCP) is used in
   conjunction with the Real-time Transport Protocol (RTP) in to provide
   a variety of short-term and long-term reception statistics.  The
   available reporting may include aggregate information across longer
   periods of time as well as individual packet reporting.  This
   document specifies a per-packet report metric capturing individual
   packets discarded from the jitter buffer after successful reception.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-xrblock-rtcp-xr-discard-rle-=
metrics-02.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-xrblock-rtcp-xr-discard-rle-m=
etrics-02.txt


From csp@csperkins.org  Mon Jan 30 13:59:43 2012
Return-Path: <csp@csperkins.org>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6877311E80C9 for <xrblock@ietfa.amsl.com>; Mon, 30 Jan 2012 13:59:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5P+HZ9sDkVyo for <xrblock@ietfa.amsl.com>; Mon, 30 Jan 2012 13:59:42 -0800 (PST)
Received: from lon1-msapost-1.mail.demon.net (lon1-msapost-1.mail.demon.net [195.173.77.180]) by ietfa.amsl.com (Postfix) with ESMTP id 5243D11E80C8 for <xrblock@ietf.org>; Mon, 30 Jan 2012 13:59:42 -0800 (PST)
Received: from starkperkins.demon.co.uk ([80.176.158.71] helo=[192.168.0.30]) by lon1-post-1.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1RrzGH-0004Zb-Wb; Mon, 30 Jan 2012 21:59:41 +0000
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C06343C6B@xmb-sjc-234.amer.cisco.com>
Date: Mon, 30 Jan 2012 21:59:40 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <B9F89C20-8778-4B13-A6BE-482F90B63069@csperkins.org>
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C06343C6B@xmb-sjc-234.amer.cisco.com>
To: Charles Eckel (eckelcu) <eckelcu@cisco.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: xrblock@ietf.org
Subject: Re: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-delay
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jan 2012 21:59:43 -0000

On 20 Jan 2012, at 22:20, Charles Eckel (eckelcu) wrote:
> This is an announcement of XRBLOCK WG last call on "RTCP XR Report =
Block for Delay metric Reporting" prior to requesting publication of the =
document as a proposed standard.=20
>=20
> This is a two week working group last call. Please send your comments,
> including nits, to the list by the 3rd of February.=20
>=20
> If you read the draft and you see no issues, concerns, or nits, please
> express the fact that you have no issue progressing the draft on the
> list as well.=20
>=20
> The latest version can be found here:
> http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp-xr-delay/


In general, this looks fine. I have some minor comments:

- Reference [MEASI] is required to be sent by Section 3, and so should =
be a normative reference.

- Section 3.2, clarify that the block MUST be ignored if the block =
length is different to 3 (since this is invalid).

- Section 3.2, since many of the metrics are calculated based on SR/RR =
values, it might make sense to report them in 1/65536 of a second units, =
rather than in milliseconds, to match the definition of the LSR and DLSR =
fields in RTCP SR/RR packets (and avoid rounding errors).


I also noticed a number of editorial issues:

- The Title and Abstract should both expand "RTCP XR Report Block" to =
"RTP Control Protocol (RTCP) Extended Report (XR) Block".=20

- This has a dependency on the monarch draft, and so should wait in the =
RFC Editor queue until that's complete. This should possibly be a =
normative dependency, which would require moving reference [MONARCH] =
into Section 8.1, and updating Section 1.1 to remove "(work in =
progress)" since this would wait for monarch.

- The subsection headings in Sections 1 and 2 serve little purpose, and =
could be removed.=20



--=20
Colin Perkins
http://csperkins.org/




From bill.wu@huawei.com  Mon Jan 30 19:25:31 2012
Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB40321F8768 for <xrblock@ietfa.amsl.com>; Mon, 30 Jan 2012 19:25:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.274
X-Spam-Level: 
X-Spam-Status: No, score=-6.274 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BRvEVSyrF9FC for <xrblock@ietfa.amsl.com>; Mon, 30 Jan 2012 19:25:30 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 60BBA21F8766 for <xrblock@ietf.org>; Mon, 30 Jan 2012 19:25:30 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYN008G783ZOR@szxga03-in.huawei.com> for xrblock@ietf.org; Tue, 31 Jan 2012 11:23:59 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYN00CLM83QPO@szxga03-in.huawei.com> for xrblock@ietf.org; Tue, 31 Jan 2012 11:23:59 +0800 (CST)
Received: from szxeml202-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGQ34865; Tue, 31 Jan 2012 11:23:59 +0800
Received: from SZXEML422-HUB.china.huawei.com (10.82.67.161) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 31 Jan 2012 11:23:54 +0800
Received: from w53375q (10.138.41.130) by szxeml422-hub.china.huawei.com (10.82.67.161) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 31 Jan 2012 11:23:54 +0800
Date: Tue, 31 Jan 2012 11:23:53 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Colin Perkins <csp@csperkins.org>, Charles Eckel <eckelcu@cisco.com>
Message-id: <06BFD971AB244E54BDE0D8221782BC9C@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C06343C6B@xmb-sjc-234.amer.cisco.com> <B9F89C20-8778-4B13-A6BE-482F90B63069@csperkins.org>
Cc: xrblock@ietf.org
Subject: Re: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-delay
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jan 2012 03:25:31 -0000

Hi, Colin:
----- Original Message ----- 
From: "Colin Perkins" <csp@csperkins.org>
To: "Charles Eckel" <eckelcu@cisco.com>
Cc: <xrblock@ietf.org>
Sent: Tuesday, January 31, 2012 5:59 AM
Subject: Re: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-delay


> On 20 Jan 2012, at 22:20, Charles Eckel (eckelcu) wrote:
>> This is an announcement of XRBLOCK WG last call on "RTCP XR Report Block for Delay metric Reporting" prior to requesting publication of the document as a proposed standard. 
>> 
>> This is a two week working group last call. Please send your comments,
>> including nits, to the list by the 3rd of February. 
>> 
>> If you read the draft and you see no issues, concerns, or nits, please
>> express the fact that you have no issue progressing the draft on the
>> list as well. 
>> 
>> The latest version can be found here:
>> http://tools.ietf.org/wg/xrblock/draft-ietf-xrblock-rtcp-xr-delay/
> 
> 
> In general, this looks fine. I have some minor comments:
> 
> - Reference [MEASI] is required to be sent by Section 3, and so should be a normative reference.

[Qin]: Okay.

> - Section 3.2, clarify that the block MUST be ignored if the block length is different to 3 (since this is invalid).

[Qin]: Good point and will do this in the update.

> - Section 3.2, since many of the metrics are calculated based on SR/RR values, it might make sense to report them in 1/65536 of a second units, rather than in milliseconds, to match the definition of the LSR and DLSR fields in RTCP SR/RR packets (and avoid rounding errors).

[Qin]: That's a good proposal unless we have better measurement method than that using SR/RR. 
In that case, the report value can be simply calculated by (A-LSR)*65536-DLSR.

> 
> I also noticed a number of editorial issues:
> 
> - The Title and Abstract should both expand "RTCP XR Report Block" to "RTP Control Protocol (RTCP) Extended Report (XR) Block". 

[Qin]: Okay.

> - This has a dependency on the monarch draft, and so should wait in the RFC Editor queue until that's complete. This should possibly be a normative dependency, which would require moving reference [MONARCH] into Section 8.1, and updating Section 1.1 to remove "(work in progress)" since this would wait for monarch.

[Qin]: Fair.

> - The subsection headings in Sections 1 and 2 serve little purpose, and could be removed. 

[Qin]: Agree.

> 
> 
> -- 
> Colin Perkins
> http://csperkins.org/
> 
> 
> 
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock

From shida@ntt-at.com  Mon Jan 30 21:34:30 2012
Return-Path: <shida@ntt-at.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1774621F8514 for <xrblock@ietfa.amsl.com>; Mon, 30 Jan 2012 21:34:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.942
X-Spam-Level: 
X-Spam-Status: No, score=-101.942 tagged_above=-999 required=5 tests=[AWL=0.323, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pMNcd9pLZKPH for <xrblock@ietfa.amsl.com>; Mon, 30 Jan 2012 21:34:29 -0800 (PST)
Received: from gator465.hostgator.com (gator465.hostgator.com [69.56.174.130]) by ietfa.amsl.com (Postfix) with ESMTP id 81BE121F8537 for <xrblock@ietf.org>; Mon, 30 Jan 2012 21:34:29 -0800 (PST)
Received: from [125.198.20.177] (port=54243 helo=[192.168.1.24]) by gator465.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <shida@ntt-at.com>) id 1Rs6MN-0005gH-80 for xrblock@ietf.org; Mon, 30 Jan 2012 23:34:27 -0600
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1251.1)
From: Shida Schubert <shida@ntt-at.com>
In-Reply-To: <31A44220-52DD-44AF-B931-5C50D888E26E@ntt-at.com>
Date: Tue, 31 Jan 2012 14:34:25 +0900
Content-Transfer-Encoding: 7bit
Message-Id: <C6926E01-77F1-4622-B636-6A2F3A5A9D35@ntt-at.com>
References: <340EB250-499C-45C1-871E-936A2D0783A3@ntt-at.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C06283BBB@xmb-sjc-234.amer.cisco.com> <31A44220-52DD-44AF-B931-5C50D888E26E@ntt-at.com>
To: xrblock <xrblock@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator465.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ntt-at.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: fl1-125-198-20-177.tky.mesh.ad.jp ([192.168.1.24]) [125.198.20.177]:54243
X-Source-Auth: shida@agnada.com
X-Email-Count: 1
X-Source-Cap: c3NoaWRhO3NzaGlkYTtnYXRvcjQ2NS5ob3N0Z2F0b3IuY29t
Subject: Re: [xrblock] Poll for progressing the QoE
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jan 2012 05:34:30 -0000

All;

 I need to see what WG thinks on the matter below for 
us to progress the QoE milestone. 

 If you have no opinions on the matter, please indicate 
it as well. 

 Many Thanks
  Shida

On Jan 19, 2012, at 8:58 PM, Shida Schubert wrote:

> 
> All;
> 
> Although a poll for draft-wu-xrblock-rtcp-xr-quality-monitoring ended in
> favor of adopting the draft, the comments provided by Colin are worth
> noting as we move forward.
> 
> I do have some questions which I think will help us clarify 
> the way forward. 
> 
> A. There are three segment types defined (1. each media 
>   sent in separate RTP stream, 2. Layered video session, 
>   3. Multi-channel audio) in the draft,  do we see a need for 
>   all three right now or in near  future (say next 12 months) ? 
> 
> B. OR are we happy with only covering one for now (Likely 
>   the 1. as I understand people are most interested in the 1.) 
>   and create a draft when there is a real need for 2. and 3.?
> 
> C. If answer is yes to question A., do we want to see the 
>   draft split into three as Colin proposed or have them all 
>   defined in single draft as it currently is. 
> 
> I asked the AD if we can split the drafts into 3 drafts under 
> single milestone but I want to make sure we do that after 
> we agree as a WG that we need all three segment types 
> RIGHT NOW before we do so. 
> 
> We have a lot of new items that people are interested in 
> working on that are not covered in our milestones, so I 
> want to make sure we focus on items that are "MUST 
> have" rather than "MAY need it in future" or "NICE to have". 
> 
> Regards
> Shida
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock


From zhaojing@sttri.com.cn  Tue Jan 31 01:10:45 2012
Return-Path: <zhaojing@sttri.com.cn>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92E2021F874F for <xrblock@ietfa.amsl.com>; Tue, 31 Jan 2012 01:10:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.263
X-Spam-Level: *
X-Spam-Status: No, score=1.263 tagged_above=-999 required=5 tests=[AWL=0.738,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, SARE_RECV_IP_218078=1.666]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SBlXSNf3CvvZ for <xrblock@ietfa.amsl.com>; Tue, 31 Jan 2012 01:10:43 -0800 (PST)
Received: from corp.21cn.com (corp.forptr.21cn.com [121.14.129.40]) by ietfa.amsl.com (Postfix) with ESMTP id BD94A21F85F1 for <xrblock@ietf.org>; Tue, 31 Jan 2012 01:10:41 -0800 (PST)
Received: from ip?218.80.215.132? (entas7.inner-hermes.com [10.27.101.7]) by corp.21cn.com (HERMES) with ESMTP id 1CC671A4838; Tue, 31 Jan 2012 17:10:31 +0800 (CST)
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_IP: wmail.10.27.101.7.312905614
HMM_SOURCE_TYPE: WEBMAIL
Received: from ip<218.80.215.132> ([218.80.215.132]) by 21CN-ent7(Yuwen filter gate 10.27.101.7) with ESMTP id 1328001031.30539 for bill.wu@huawei.com ; Tue Jan 31 17:10:36 2012
0/X-Total-Score: 3:
X-FILTER-SCORE: to=<bill.wu@huawei.comxrblock@ietf.org>, score=<1328001036kb71p/6HHkHHbHH7HH1HtCpS78YZAAhAApAASAA7ABCh> 
Date: Tue, 31 Jan 2012 17:10:30 +0800 (CST)
From: zhaojing@sttri.com.cn
To: Qin Wu <bill.wu@huawei.com>, xrblock <xrblock@ietf.org>
Message-ID: <5161211.151328001031222.JavaMail.root@ent8>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_Part_15_28794541.1328001030970"
HMM_WEBCLN_IP: 218.80.215.132
X-HERMES-SENDMODE: normal
Subject: Re: [xrblock] I-D Action: draft-zorn-xrblock-rtcp-xr-al-stat-04.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jan 2012 09:10:45 -0000

------=_Part_15_28794541.1328001030970
Content-Type: text/html;charset=UTF-8
Content-Transfer-Encoding: base64

PGh0bWw+CiA8aGVhZD48L2hlYWQ+CiA8Ym9keT4KICA8ZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9O
VC1TSVpFOiAxOXB4Ij4KICAgIEhpLCZuYnNwO1FpbjoKICAgPC9kaXY+IAogICA8ZGl2IHN0eWxl
PSJGT05ULVNJWkU6IDE5cHgiPgogICAgSSZuYnNwO2hhdmUmbmJzcDtyZXZpZXcmbmJzcDtkcmFm
dC16b3JuLXhyYmxvY2stcnRjcC14ci1hbC1zdGF0Jm5ic3A7YW5kJm5ic3A7aGF2ZSZuYnNwO3R3
byZuYnNwO2NvbW1lbnRzLgogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTlw
eCI+CiAgICAmbmJzcDsKICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE5cHgi
PgogICAgMS5UaGlzJm5ic3A7ZHJhZnQmbmJzcDtzcGVjaWZpZXMmbmJzcDt0aHJlZSZuYnNwO25l
dyZuYnNwO1hSJm5ic3A7QmxvY2tzLiZuYnNwO1RoZSZuYnNwO2ZpcnN0Jm5ic3A7dHdvJm5ic3A7
YXJlJm5ic3A7bGlua2VkJm5ic3A7dG8mbmJzcDtidXJzdCZuYnNwO2dhcCZuYnNwOwogICA8L2Rp
dj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+CiAgICBsb3NzJm5ic3A7ZHJhZnQm
bmJzcDthbmQmbmJzcDtidXJzdCZuYnNwO2dhcCZuYnNwO2Rpc2NhcmQmbmJzcDtkcmFmdC4mbmJz
cDtJJm5ic3A7YWdyZWUmbmJzcDt3aXRoJm5ic3A7eW91Jm5ic3A7dGhhdCZuYnNwO3RoZXNlJm5i
c3A7dHdvJm5ic3A7WFImbmJzcDtibG9ja3MKICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05U
LVNJWkU6IDE5cHgiPgogICAgZGVmaW5lJm5ic3A7Y2FsY3VsYXRpb24mbmJzcDttZXRob2QmbmJz
cDtmb3ImbmJzcDt0aGUmbmJzcDtkZXJpdmVkJm5ic3A7bWV0cmljcyZuYnNwO21lbnRpb25lZCZu
YnNwO2luJm5ic3A7dGhlJm5ic3A7YnVyc3QmbmJzcDtnYXAmbmJzcDtkcmFmdHMuCiAgIDwvZGl2
PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgIGFuZCZuYnNwO2FyZSZuYnNw
O3R3byZuYnNwO21vc3QmbmJzcDtpbXBvcnRhbnQmbmJzcDttZXRyaWMmbmJzcDtibG9ja3MmbmJz
cDt3aGljaCZuYnNwO3RoZSZuYnNwO2J1cnN0Jm5ic3A7Z2FwJm5ic3A7ZHJhZnRzJm5ic3A7Y291
bnQmbmJzcDtvbi4mbmJzcDsKICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE5
cHgiPgogICAgTXkmbmJzcDtxdWVzdGlvbiZuYnNwO2lzJm5ic3A7d2hvJm5ic3A7c2VuZHMmbmJz
cDt0aGVzZSZuYnNwO3R3byZuYnNwO1hSJm5ic3A7YmxvY2tzPwogICA8L2Rpdj4gCiAgIDxkaXYg
c3R5bGU9IkZPTlQtU0laRTogMTlweCI+CiAgICAmbmJzcDsKICAgPC9kaXY+IAogICA8ZGl2IHN0
eWxlPSJGT05ULVNJWkU6IDE5cHgiPgogICAgMi4mbmJzcDtUaGUmbmJzcDt0aGlyZCZuYnNwO1hS
Jm5ic3A7QmxvY2smbmJzcDtkZWZpbmVkJm5ic3A7aW4mbmJzcDt0aGlzJm5ic3A7ZHJhZnQmbmJz
cDtpcyZuYnNwO1N0YXRpc3RpY3MmbmJzcDtTdW1tYXJ5Jm5ic3A7QmxvY2smbmJzcDtmb3IKICAg
PC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPgogICAgJm5ic3A7QXBwbGlj
YXRpb24mbmJzcDtMYXllciZuYnNwO0xvc3MvRHVwbGljYXRpb24uJm5ic3A7SSZuYnNwO3RoaW5r
Jm5ic3A7dGhpcyZuYnNwO1hSJm5ic3A7QmxvY2smbmJzcDtpcyZuYnNwO2xpbmtlZCZuYnNwO3Rv
Jm5ic3A7SS9QL0ImbmJzcDtmcmFtZSZuYnNwO3N0YXRpc3RpY3MuCiAgIDwvZGl2PiAKICAgPGRp
diBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgIFRoaXMmbmJzcDttZXRyaWMmbmJzcDtibG9j
a3MmbmJzcDtjYW4mbmJzcDt0ZWxsJm5ic3A7dXMmbmJzcDt3aGljaCZuYnNwO2ZyYW1lJm5ic3A7
dHlwZXMmbmJzcDt3ZXJlJm5ic3A7YWZmZWN0ZWQmbmJzcDthbmQmbmJzcDtpcyZuYnNwO3RoZXJl
Zm9yZSZuYnNwO2EmbmJzcDt1c2VmdWwmbmJzcDttZXRyaWMKICAgPC9kaXY+IAogICA8ZGl2IHN0
eWxlPSJGT05ULVNJWkU6IDE5cHgiPgogICAgJm5ic3A7dG8mbmJzcDtmb3JtJm5ic3A7YW4mbmJz
cDthY2N1cmF0ZSZuYnNwO2Fzc2Vzc21lbnQmbmJzcDtvZiZuYnNwO3VzZXImbmJzcDtxdWFsaXR5
Jm5ic3A7b2YmbmJzcDtleHBlcmllbmNlLiZuYnNwO0hvd2V2ZXImbmJzcDtpdCZuYnNwO2lzJm5i
c3A7bm90Jm5ic3A7Y2xlYXImbmJzcDt0byZuYnNwO21lJm5ic3A7CiAgIDwvZGl2PiAKICAgPGRp
diBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgIGhvdyZuYnNwO2RvJm5ic3A7eW91Jm5ic3A7
Y2FsY3VsYXRlJm5ic3A7TnVtYmVyJm5ic3A7b2YmbmJzcDtmcmFtZXMmbmJzcDtleHBlY3RlZD8m
bmJzcDtJc24ndCZuYnNwO21vcmUmbmJzcDtlYXNpZXImbmJzcDt0byZuYnNwO2NhbGN1bGF0ZSZu
YnNwO2hvdyZuYnNwO21hbnkmbmJzcDtmcmFtZXMmbmJzcDthcmUmbmJzcDtyZWNlaXZlZAogICA8
L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+CiAgICByYW50aGVyJm5ic3A7
dGhhbiZuYnNwO2dhdGhlcmluZyZuYnNwO3RoZSZuYnNwO251bWJlciZuYnNwO29mJm5ic3A7ZnJh
bWUmbmJzcDtleHBlY3RlZD8KICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE5
cHgiPgogICAgQW5vdGhlciZuYnNwO2NvbW1lbnQmbmJzcDtpcyZuYnNwO2lzbid0Jm5ic3A7aXQm
bmJzcDt1c2VmdWwmbmJzcDt0byZuYnNwO2NvbGxlY3QmbmJzcDtob3cmbmJzcDttYW55Jm5ic3A7
ZGlmZmVyZW50Jm5ic3A7dHlwZSZuYnNwO29mJm5ic3A7ZnJhbWVzJm5ic3A7d2VyZSZuYnNwO2Rp
c2NhcmRlZCZuYnNwOwogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+
CiAgICBieSZuYnNwO3RoZSZuYnNwO21lZGlhJm5ic3A7cmVjaWV2ZXI/CiAgIDwvZGl2PiAKICAg
PGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgICZuYnNwOwogICA8L2Rpdj4gCiAgIDxk
aXYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+CiAgICBDaGVlcnMhCiAgIDwvZGl2PiAKICAgPGRp
diBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgIFpoYW9KaW5nCiAgIDwvZGl2PiAKICAgPGRp
diBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgIC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0KICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPgogICAgLS0tLS0m
bmJzcDtPcmlnaW5hbCZuYnNwO01lc3NhZ2UmbmJzcDstLS0tLSZuYnNwOwogICA8L2Rpdj4gCiAg
IDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+CiAgICBGcm9tOiZuYnNwOyZxdW90O1FpbiZu
YnNwO1d1JnF1b3Q7Jm5ic3A7Jmx0O2JpbGwud3VAaHVhd2VpLmNvbSZndDsKICAgPC9kaXY+IAog
ICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPgogICAgVG86Jm5ic3A7Jmx0O3hyYmxvY2tA
aWV0Zi5vcmcmZ3Q7CiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij4K
ICAgIFNlbnQ6Jm5ic3A7VGh1cnNkYXksJm5ic3A7SmFudWFyeSZuYnNwOzE5LCZuYnNwOzIwMTIm
bmJzcDs0OjQwJm5ic3A7UE0KICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE5
cHgiPgogICAgU3ViamVjdDombmJzcDtSZTombmJzcDtbeHJibG9ja10mbmJzcDtJLUQmbmJzcDtB
Y3Rpb246Jm5ic3A7ZHJhZnQtem9ybi14cmJsb2NrLXJ0Y3AteHItYWwtc3RhdC0wNC50eHQKICAg
PC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPgogICAgJm5ic3A7CiAgIDwv
ZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgICZuYnNwOwogICA8L2Rp
dj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+CiAgICAmZ3Q7Jm5ic3A7SGksCiAg
IDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgICZndDsmbmJzcDtB
Jm5ic3A7bWlub3ImbmJzcDt1cGRhdGUmbmJzcDt0byZuYnNwO2RyYWZ0LXpvcm4teHJibG9jay1y
dGNwLXhyLWFsLXN0YXQmbmJzcDt3aGljaCZuYnNwO2lzJm5ic3A7dXNlZCZuYnNwO3RvJm5ic3A7
Z2V0Jm5ic3A7Y29uc2lzdGVudCZuYnNwO3dpdGgmbmJzcDtCdXJzdCZuYnNwO0dhcCZuYnNwO3Jl
bGF0ZWQmbmJzcDtkcmFmdC4KICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE5
cHgiPgogICAgJmd0OyZuYnNwO1RoaXMmbmJzcDtkcmFmdCZuYnNwO21pc3NlZCZuYnNwO3RoZSZu
YnNwO2Rpc2N1c3Npb24mbmJzcDtkdWUmbmJzcDt0byZuYnNwO3ByZXNlbnRhdGlvbiZuYnNwO3Rp
bWVvdXQmbmJzcDsmbmJzcDtpbiZuYnNwO3RoZSZuYnNwO2xhc3QmbmJzcDtJRVRGJm5ic3A7bWVl
dGluZy4mbmJzcDtIb3dldmVyJm5ic3A7dGhpcyZuYnNwO2RyYWZ0Jm5ic3A7cHJvdmlkZXMmbmJz
cDtjYWxjdWxhdGlvbiZuYnNwO21ldGhvZAogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQt
U0laRTogMTlweCI+CiAgICAmZ3Q7Jm5ic3A7Zm9yJm5ic3A7dGhlJm5ic3A7ZGVyaXZlZCZuYnNw
O21ldHJpYyZuYnNwO2xpc3RlZCZuYnNwO2luJm5ic3A7dGhlJm5ic3A7dHdvJm5ic3A7YnVyc3Qm
bmJzcDtnYXAmbmJzcDtyZWxhdGVkJm5ic3A7ZHJhZnQmbmJzcDthbmQmbmJzcDthbHNvJm5ic3A7
ZGVmaW5lcyZuYnNwO1JUQ1AmbmJzcDtYUiZuYnNwO3BhY2tldCZuYnNwO2Zvcm1hdCZuYnNwO3Rv
Jm5ic3A7Y2FycnkmbmJzcDt0aGVzZSZuYnNwO2Rlcml2ZWQmbmJzcDsKICAgPC9kaXY+IAogICA8
ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPgogICAgJmd0OyZuYnNwO21ldHJpYy4KICAgPC9k
aXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPgogICAgJmd0OyZuYnNwO0kmbmJz
cDtsaWtlJm5ic3A7dG8mbmJzcDtzZWUmbmJzcDtXRyZuYnNwO2Fkb3B0Jm5ic3A7dGhpcyZuYnNw
O2RyYWZ0Jm5ic3A7YXMmbmJzcDt3b3JrJm5ic3A7aXRlbSZuYnNwO29yJm5ic3A7YWRvcHQmbmJz
cDthJm5ic3A7bWlsZXN0b25lJm5ic3A7dG8mbmJzcDtsaW5rJm5ic3A7dG8mbmJzcDt0aGlzJm5i
c3A7ZHJhZnQuJm5ic3A7CiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4
Ij4KICAgICZndDsmbmJzcDtBbnkmbmJzcDtyZXZpZXcmbmJzcDthbmQmbmJzcDtjb21tZW50cyZu
YnNwO2FyZSZuYnNwO3dlbGNvbWUuCiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpF
OiAxOXB4Ij4KICAgICZndDsmbmJzcDsKICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJ
WkU6IDE5cHgiPgogICAgJmd0OyZuYnNwO1JlZ2FyZHMhCiAgIDwvZGl2PiAKICAgPGRpdiBzdHls
ZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgICZndDsmbmJzcDstUWluCiAgIDwvZGl2PiAKICAgPGRp
diBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgICZndDsmbmJzcDstLS0tLSZuYnNwO09yaWdp
bmFsJm5ic3A7TWVzc2FnZSZuYnNwOy0tLS0tJm5ic3A7CiAgIDwvZGl2PiAKICAgPGRpdiBzdHls
ZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgICZndDsmbmJzcDtGcm9tOiZuYnNwOyZsdDtpbnRlcm5l
dC1kcmFmdHNAaWV0Zi5vcmcmZ3Q7CiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpF
OiAxOXB4Ij4KICAgICZndDsmbmJzcDtUbzombmJzcDsmbHQ7aS1kLWFubm91bmNlQGlldGYub3Jn
Jmd0OwogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+CiAgICAmZ3Q7
Jm5ic3A7U2VudDombmJzcDtUaHVyc2RheSwmbmJzcDtKYW51YXJ5Jm5ic3A7MTksJm5ic3A7MjAx
MiZuYnNwOzM6MDQmbmJzcDtQTQogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTog
MTlweCI+CiAgICAmZ3Q7Jm5ic3A7U3ViamVjdDombmJzcDtJLUQmbmJzcDtBY3Rpb246Jm5ic3A7
ZHJhZnQtem9ybi14cmJsb2NrLXJ0Y3AteHItYWwtc3RhdC0wNC50eHQKICAgPC9kaXY+IAogICA8
ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPgogICAgJmd0OyZuYnNwOwogICA8L2Rpdj4gCiAg
IDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+CiAgICAmZ3Q7Jm5ic3A7CiAgIDwvZGl2PiAK
ICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgICZndDsmZ3Q7Jm5ic3A7CiAgIDwv
ZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgICZndDsmZ3Q7Jm5ic3A7
QSZuYnNwO05ldyZuYnNwO0ludGVybmV0LURyYWZ0Jm5ic3A7aXMmbmJzcDthdmFpbGFibGUmbmJz
cDtmcm9tJm5ic3A7dGhlJm5ic3A7b24tbGluZSZuYnNwO0ludGVybmV0LURyYWZ0cyZuYnNwO2Rp
cmVjdG9yaWVzLgogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+CiAg
ICAmZ3Q7Jmd0OyZuYnNwOwogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTlw
eCI+CiAgICAmZ3Q7Jmd0OyZuYnNwO1RpdGxlJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7OiZuYnNwO1JUQ1AmbmJzcDtYUiZu
YnNwO2ZvciZuYnNwO1N1bW1hcnkmbmJzcDtTdGF0aXN0aWNzJm5ic3A7TWV0cmljcyZuYnNwO1Jl
cG9ydGluZwogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+CiAgICAm
Z3Q7Jmd0OyZuYnNwO0F1dGhvcihzKSZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOzombmJzcDtHbGVuJm5ic3A7Wm9ybgogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZP
TlQtU0laRTogMTlweCI+CiAgICAmZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwO1JvbGFuZCZuYnNwO1NjaG90dAogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9
IkZPTlQtU0laRTogMTlweCI+CiAgICAmZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwO1FpbiZuYnNwO1d1CiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9O
VC1TSVpFOiAxOXB4Ij4KICAgICZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7UmFjaGVsJm5ic3A7SHVhbmcKICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJG
T05ULVNJWkU6IDE5cHgiPgogICAgJmd0OyZndDsmbmJzcDtGaWxlbmFtZSZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzombmJzcDtkcmFmdC16b3JuLXhyYmxv
Y2stcnRjcC14ci1hbC1zdGF0LTA0LnR4dAogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQt
U0laRTogMTlweCI+CiAgICAmZ3Q7Jmd0OyZuYnNwO1BhZ2VzJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7OiZuYnNwOzE1CiAg
IDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgICZndDsmZ3Q7Jm5i
c3A7RGF0ZSZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOzombmJzcDsyMDEyLTAxLTE4CiAgIDwvZGl2PiAKICAgPGRp
diBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgICZndDsmZ3Q7Jm5ic3A7CiAgIDwvZGl2PiAK
ICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgICZndDsmZ3Q7Jm5ic3A7Jm5ic3A7
Jm5ic3A7VGhpcyZuYnNwO2RvY3VtZW50Jm5ic3A7ZGVmaW5lcyZuYnNwO3RocmVlJm5ic3A7UlRD
UCZuYnNwO1hSJm5ic3A7UmVwb3J0Jm5ic3A7QmxvY2tzJm5ic3A7YW5kJm5ic3A7YXNzb2NpYXRl
ZCZuYnNwO1NEUAogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+CiAg
ICAmZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwO3BhcmFtZXRlcnMmbmJzcDt0aGF0Jm5ic3A7YWxs
b3dzJm5ic3A7dGhlJm5ic3A7cmVwb3J0aW5nJm5ic3A7b2YmbmJzcDtsb3NzLCZuYnNwO2R1cGxp
Y2F0aW9uJm5ic3A7YW5kJm5ic3A7ZGlzY2FyZAogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZP
TlQtU0laRTogMTlweCI+CiAgICAmZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwO3N1bW1hcnkmbmJz
cDtzdGF0aXN0aWNzJm5ic3A7bWV0cmljcyZuYnNwO2ZvciZuYnNwO3VzZSZuYnNwO2luJm5ic3A7
YSZuYnNwO3JhbmdlJm5ic3A7b2YmbmJzcDtSVFAmbmJzcDthcHBsaWNhdGlvbnMuCiAgIDwvZGl2
PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgICZndDsmZ3Q7Jm5ic3A7CiAg
IDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgICZndDsmZ3Q7Jm5i
c3A7CiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgICZndDsm
Z3Q7Jm5ic3A7QSZuYnNwO1VSTCZuYnNwO2ZvciZuYnNwO3RoaXMmbmJzcDtJbnRlcm5ldC1EcmFm
dCZuYnNwO2lzOgogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+CiAg
ICAmZ3Q7Jmd0OyAKICAgIDxhIHN0eWxlPSJGT05ULVNJWkU6IDE4cHgiIGhyZWY9Imh0dHA6Ly93
d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LXpvcm4teHJibG9jay1ydGNwLXhyLWFs
LXN0YXQtMDQudHh0Ij5odHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC16
b3JuLXhyYmxvY2stcnRjcC14ci1hbC1zdGF0LTA0LnR4dDwvYT4KICAgPC9kaXY+IAogICA8ZGl2
IHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPgogICAgJmd0OyZndDsmbmJzcDsKICAgPC9kaXY+IAog
ICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPgogICAgJmd0OyZndDsmbmJzcDtJbnRlcm5l
dC1EcmFmdHMmbmJzcDthcmUmbmJzcDthbHNvJm5ic3A7YXZhaWxhYmxlJm5ic3A7YnkmbmJzcDth
bm9ueW1vdXMmbmJzcDtGVFAmbmJzcDthdDoKICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05U
LVNJWkU6IDE5cHgiPgogICAgJmd0OyZndDsmbmJzcDtmdHA6Ly9mdHAuaWV0Zi5vcmcvaW50ZXJu
ZXQtZHJhZnRzLwogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+CiAg
ICAmZ3Q7Jmd0OyZuYnNwOwogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTlw
eCI+CiAgICAmZ3Q7Jmd0OyZuYnNwO1RoaXMmbmJzcDtJbnRlcm5ldC1EcmFmdCZuYnNwO2NhbiZu
YnNwO2JlJm5ic3A7cmV0cmlldmVkJm5ic3A7YXQ6CiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0i
Rk9OVC1TSVpFOiAxOXB4Ij4KICAgICZndDsmZ3Q7Jm5ic3A7ZnRwOi8vZnRwLmlldGYub3JnL2lu
dGVybmV0LWRyYWZ0cy9kcmFmdC16b3JuLXhyYmxvY2stcnRjcC14ci1hbC1zdGF0LTA0LnR4dAog
ICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+CiAgICAmZ3Q7Jmd0OyZu
YnNwOwogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+CiAgICAmZ3Q7
Jmd0OyZuYnNwO19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
CiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgICZndDsmZ3Q7
Jm5ic3A7SS1ELUFubm91bmNlJm5ic3A7bWFpbGluZyZuYnNwO2xpc3QKICAgPC9kaXY+IAogICA8
ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPgogICAgJmd0OyZndDsmbmJzcDtJLUQtQW5ub3Vu
Y2VAaWV0Zi5vcmcKICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPgog
ICAgJmd0OyZndDsgCiAgICA8YSBzdHlsZT0iRk9OVC1TSVpFOiAxOHB4IiBocmVmPSJodHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ktZC1hbm5vdW5jZSI+aHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pLWQtYW5ub3VuY2U8L2E+CiAgIDwvZGl2PiAKICAg
PGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgICZndDsmZ3Q7IEludGVybmV0LURyYWZ0
IGRpcmVjdG9yaWVzOiAKICAgIDxhIHN0eWxlPSJGT05ULVNJWkU6IDE4cHgiIGhyZWY9Imh0dHA6
Ly93d3cuaWV0Zi5vcmcvc2hhZG93Lmh0bWwiPmh0dHA6Ly93d3cuaWV0Zi5vcmcvc2hhZG93Lmh0
bWw8L2E+CiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij4KICAgICZn
dDsmZ3Q7Jm5ic3A7b3ImbmJzcDtmdHA6Ly9mdHAuaWV0Zi5vcmcvaWV0Zi8xc2hhZG93LXNpdGVz
LnR4dAogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+CiAgICAmZ3Q7
Jmd0OwogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+CiAgICAmZ3Q7
Jm5ic3A7X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KICAg
PC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPgogICAgJmd0OyZuYnNwO3hy
YmxvY2smbmJzcDttYWlsaW5nJm5ic3A7bGlzdAogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZP
TlQtU0laRTogMTlweCI+CiAgICAmZ3Q7Jm5ic3A7eHJibG9ja0BpZXRmLm9yZwogICA8L2Rpdj4g
CiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+CiAgICAmZ3Q7IAogICAgPGEgc3R5bGU9
IkZPTlQtU0laRTogMThweCIgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby94cmJsb2NrIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3hyYmxv
Y2s8L2E+CiAgIDwvZGl2PgogIDwvZGl2PgogPC9ib2R5Pgo8L2h0bWw+
------=_Part_15_28794541.1328001030970--


From glenzorn@gmail.com  Tue Jan 31 05:25:02 2012
Return-Path: <glenzorn@gmail.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D027721F8679 for <xrblock@ietfa.amsl.com>; Tue, 31 Jan 2012 05:25:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.849
X-Spam-Level: 
X-Spam-Status: No, score=-3.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q81zMx22giPD for <xrblock@ietfa.amsl.com>; Tue, 31 Jan 2012 05:25:02 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 37F4A21F8663 for <xrblock@ietf.org>; Tue, 31 Jan 2012 05:25:02 -0800 (PST)
Received: by yenm3 with SMTP id m3so2561218yen.31 for <xrblock@ietf.org>; Tue, 31 Jan 2012 05:25:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=2DYlW5/4cu14lmEbbamZ6pV2Nqyoje2qM8aqBcVejwA=; b=u4EQotEjrBqHTLUeqO5BBN4b6Xkx7PLcXYoGPrW2VPC/Vq8FJdpFuDKQn1SLe0af9h FcCXjUt/e3HbzAaxY7k1p4IkYAWkM1ZUg25GZDUA312MHsH0UId9lqe3QzTPfSvsQgRz hEHNOWNi6bC+E7ozpA45EcUR2SLGKA3XcqKps=
Received: by 10.236.37.132 with SMTP id y4mr34733206yha.10.1328016301844; Tue, 31 Jan 2012 05:25:01 -0800 (PST)
Received: from [192.168.1.98] (ppp-124-120-57-235.revip2.asianet.co.th. [124.120.57.235]) by mx.google.com with ESMTPS id p63sm38922096yhj.22.2012.01.31.05.24.58 (version=SSLv3 cipher=OTHER); Tue, 31 Jan 2012 05:25:00 -0800 (PST)
Message-ID: <4F27EBA7.705@gmail.com>
Date: Tue, 31 Jan 2012 20:24:55 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Shida Schubert <shida@ntt-at.com>
References: <340EB250-499C-45C1-871E-936A2D0783A3@ntt-at.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C06283BBB@xmb-sjc-234.amer.cisco.com> <31A44220-52DD-44AF-B931-5C50D888E26E@ntt-at.com> <C6926E01-77F1-4622-B636-6A2F3A5A9D35@ntt-at.com>
In-Reply-To: <C6926E01-77F1-4622-B636-6A2F3A5A9D35@ntt-at.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: xrblock <xrblock@ietf.org>
Subject: Re: [xrblock] Poll for progressing the QoE
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jan 2012 13:25:02 -0000

On 1/31/2012 12:34 PM, Shida Schubert wrote:
> 
> All;
> 
>  I need to see what WG thinks on the matter below for 
> us to progress the QoE milestone. 

Not at all.

> 
>  If you have no opinions on the matter, please indicate 
> it as well. 
> 
>  Many Thanks
>   Shida
> 
> On Jan 19, 2012, at 8:58 PM, Shida Schubert wrote:
> 
>>
>> All;
>>
>> Although a poll for draft-wu-xrblock-rtcp-xr-quality-monitoring ended in
>> favor of adopting the draft, the comments provided by Colin are worth
>> noting as we move forward.

No.  As you state yourself above, the consensus of the WG is to adopt
the draft.  Adopt it.  As for Colin's comments being "worth noting",
that's all they are, until the draft is adopted.

>>
>> I do have some questions which I think will help us clarify 
>> the way forward. 

The way forward is not to go backward.  Adopt the draft.

>>
>> A. There are three segment types defined (1. each media 
>>   sent in separate RTP stream, 2. Layered video session, 
>>   3. Multi-channel audio) in the draft,  do we see a need for 
>>   all three right now or in near  future (say next 12 months) ? 
>>
>> B. OR are we happy with only covering one for now (Likely 
>>   the 1. as I understand people are most interested in the 1.) 
>>   and create a draft when there is a real need for 2. and 3.?
>>
>> C. If answer is yes to question A., do we want to see the 
>>   draft split into three as Colin proposed or have them all 
>>   defined in single draft as it currently is. 
>>
>> I asked the AD if we can split the drafts into 3 drafts under 
>> single milestone but I want to make sure we do that after 
>> we agree as a WG that we need all three segment types 
>> RIGHT NOW before we do so. 

Nonsense.  If, AFTER the draft is adopted as a WG document, the WG
decides to split it into 3 or 4 drafts or chop it into confetti, that is
their privilege.

>>
>> We have a lot of new items that people are interested in 
>> working on that are not covered in our milestones, so I 
>> want to make sure we focus on items that are "MUST 
>> have" rather than "MAY need it in future" or "NICE to have". 
>>
>> Regards
>> Shida
>> _______________________________________________
>> xrblock mailing list
>> xrblock@ietf.org
>> https://www.ietf.org/mailman/listinfo/xrblock
> 
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock


From hs@123.org  Tue Jan 31 05:39:44 2012
Return-Path: <hs@123.org>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0317321F854E for <xrblock@ietfa.amsl.com>; Tue, 31 Jan 2012 05:39:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level: 
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NKNV+n2M2Y33 for <xrblock@ietfa.amsl.com>; Tue, 31 Jan 2012 05:39:43 -0800 (PST)
Received: from mo-p05-ob6.rzone.de (mo-p05-ob6.rzone.de [IPv6:2a01:238:20a:202:53f5::1]) by ietfa.amsl.com (Postfix) with ESMTP id E29F621F8539 for <xrblock@ietf.org>; Tue, 31 Jan 2012 05:39:42 -0800 (PST)
X-RZG-AUTH: :JH8HfU+kYd9xQ6m0ynnj9hHxvZXYXks+pm8dQxa2PdmCs29qNyJDXGPSHqedfmnO
X-RZG-CLASS-ID: mo05
Received: from [192.168.1.249] ([213.218.5.34]) by smtp.strato.de (jimi mo46) (RZmta 27.6 DYNA|AUTH) with ESMTPA id D021d5o0VCt5oK for <xrblock@ietf.org>; Tue, 31 Jan 2012 14:39:30 +0100 (MET)
Message-ID: <4F27EF11.1030403@123.org>
Date: Tue, 31 Jan 2012 14:39:29 +0100
From: Hendrik Scholz <hs@123.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111229 Thunderbird/9.0
MIME-Version: 1.0
To: xrblock@ietf.org
References: <E7B79540-9CB5-4E4F-B32B-5FB9960398B4@ntt-at.com><B2982C71-420E-40B7-8695-244CDFFFD02E@csperkins.org><EB081EC32D2C472384E8E66322A9D5FA@china.huawei.com><1CDE2461-9768-47DA-9EF8-E81EDFB82681@csperkins.org> <F25E4B7A3DFF4113979EE38D4ECDF2C9@china.huawei.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C060CA30C@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C060CA30C@xmb-sjc-234.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [xrblock] Call for adopting xr-quality-monitoring-06 as WG item
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jan 2012 13:39:44 -0000

Hi!

I do not have any bias towards splitting the draft again.
In the end somebody requiring only a part
(e.g. Single Stream per SSRC Segment) would not have to
implement the other two options when sending out reports.

Coming from the standardization point of view my question
would be if we even know what people would use to
implement anything beyond domain-internal statistics (e.g.
SLAs). Clearly there are lots of combinations which might
yield irrelevant or wrong results.
Anybody who wants to use the reports would have to define
which algorithms are allowed for the specific use case.
I assume that this would be done outside the draft and some
operators might even define the allowed algorithms in their
service level agreements.

Btw: The Calculation Algorithm is sometimes referred to
as CALg and not CAlg as it should.

Cheers,
 Hendrik

-- 
Hendrik Scholz <hs@123.org>

From zhaojing@sttri.com.cn  Tue Jan 31 17:24:22 2012
Return-Path: <zhaojing@sttri.com.cn>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EDBD21F8450 for <xrblock@ietfa.amsl.com>; Tue, 31 Jan 2012 17:24:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.378
X-Spam-Level: **
X-Spam-Status: No, score=2.378 tagged_above=-999 required=5 tests=[AWL=-0.746,  BAYES_50=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, SARE_RECV_IP_218078=1.666]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N1Qk6smBHHN2 for <xrblock@ietfa.amsl.com>; Tue, 31 Jan 2012 17:24:21 -0800 (PST)
Received: from corp.21cn.com (corp.forptr.21cn.com [121.14.129.40]) by ietfa.amsl.com (Postfix) with ESMTP id 97F7B21F844A for <xrblock@ietf.org>; Tue, 31 Jan 2012 17:24:19 -0800 (PST)
Received: from ip?218.80.215.132? (entas7.inner-hermes.com [10.27.101.7]) by corp.21cn.com (HERMES) with ESMTP id 2858D1A484B; Wed,  1 Feb 2012 09:24:12 +0800 (CST)
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_IP: wmail.10.27.101.7.1021024556
HMM_SOURCE_TYPE: WEBMAIL
Received: from ip<218.80.215.132> ([218.80.215.132]) by 21CN-ent7(Yuwen filter gate 10.27.101.7) with ESMTP id 1328059447.30129 for shida@ntt-at.com ; Wed Feb  1 09:24:18 2012
X-FILTER-SCORE: to=<shida@ntt-at.comxrblock@ietf.org>, score=<1328059458udHEufGwh6RdddddHddEddx6kU2EOIbtxxxxx6xxkxxU> 
Date: Wed, 1 Feb 2012 09:24:07 +0800 (CST)
From: zhaojing@sttri.com.cn
To: Shida Schubert <shida@ntt-at.com>, xrblock <xrblock@ietf.org>
Message-ID: <26098421.13561328059452312.JavaMail.root@ent8>
MIME-Version: 1.0
Content-Type: multipart/mixed;  boundary="----=_Part_1175_20397511.1328059447043"
HMM_WEBCLN_IP: 218.80.215.132
X-HERMES-SENDMODE: normal
Subject: Re: [xrblock] Poll for progressing the QoE
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2012 01:24:22 -0000

------=_Part_1175_20397511.1328059447043
Content-Type: text/html;charset=UTF-8
Content-Transfer-Encoding: base64

PGh0bWw+CiA8aGVhZD48L2hlYWQ+CiA8Ym9keT4KICA8ZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9O
VC1TSVpFOiAxOHB4Ij4KICAgIEkmbmJzcDtoYXZlJm5ic3A7bm8mbmJzcDtzdHJvbmcmbmJzcDtv
cGluaW9uJm5ic3A7b24mbmJzcDt3aGljaCZuYnNwO3dheSZuYnNwO3RvJm5ic3A7Zm9sbG93Lgog
ICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMThweCI+CiAgICBCdXQmbmJzcDtJ
Jm5ic3A7Y2FuJm5ic3A7c2VlJm5ic3A7dGhlJm5ic3A7MXN0Jm5ic3A7c2VnbWVudCZuYnNwO3R5
cGUmbmJzcDtjYW4mbmJzcDtiZSZuYnNwO3dpZGVseSZuYnNwO3N1cHBvcnRlZAogICA8L2Rpdj4g
CiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMThweCI+CiAgICBieSZuYnNwO3ZhcmlvdXMmbmJz
cDthcHBsaWNhdGlvbnMmbmJzcDthbmQmbmJzcDt1c2VkLiZuYnNwO1RoZSZuYnNwO290aGVyJm5i
c3A7dHdvJm5ic3A7YXJlJm5ic3A7Y29tcGxlbWVudGFyeQogICA8L2Rpdj4gCiAgIDxkaXYgc3R5
bGU9IkZPTlQtU0laRTogMThweCI+CiAgICB0byZuYnNwO3RoZSZuYnNwO2ZpcnN0Jm5ic3A7b25l
LiZuYnNwO0VzcGVjaWFsbHkmbmJzcDt0aGUmbmJzcDttdWx0aS1jaGFubmVsJm5ic3A7YXVkaW8m
bmJzcDtzZWdtZW50Jm5ic3A7dHlwZSwKICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJ
WkU6IDE4cHgiPgogICAgd291bGRuJ3QmbmJzcDtWT0lQJm5ic3A7aW1wbGVtZW50ZXImbmJzcDts
aWtlJm5ic3A7dG8mbmJzcDtzZWUmbmJzcDt0aGlzJm5ic3A7YmUmbmJzcDtzdGFuZGFyZGl6ZWQm
bmJzcDthcyZuYnNwO2JlaW5nCiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAx
OHB4Ij4KICAgIG1lYXN1cmVtZW50Jm5ic3A7dG9vbCZuYnNwO2ZvciZuYnNwO3N0ZXJlbyZuYnNw
O2F1ZGlvJm5ic3A7YXBwbGljYXRpb24/CiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1T
SVpFOiAxOHB4Ij4KICAgICZuYnNwOwogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0la
RTogMThweCI+CiAgICBDaGVlcnMhCiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpF
OiAxOHB4Ij4KICAgIEppbmdaaGFvCiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpF
OiAxOHB4Ij4KICAgIC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQog
ICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMThweCI+CiAgICAmbmJzcDsKICAg
PC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE4cHgiPgogICAgLS0tLS0mbmJzcDtP
cmlnaW5hbCZuYnNwO01lc3NhZ2UmbmJzcDstLS0tLQogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9
IkZPTlQtU0laRTogMThweCI+CiAgICBGcm9tOiZuYnNwOyZxdW90O1NoaWRhJm5ic3A7U2NodWJl
cnQmcXVvdDsmbmJzcDsmbHQ7c2hpZGFAbnR0LWF0LmNvbSZndDsKICAgPC9kaXY+IAogICA8ZGl2
IHN0eWxlPSJGT05ULVNJWkU6IDE4cHgiPgogICAgVG86Jm5ic3A7JnF1b3Q7eHJibG9jayZxdW90
OyZuYnNwOyZsdDt4cmJsb2NrQGlldGYub3JnJmd0OwogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9
IkZPTlQtU0laRTogMThweCI+CiAgICBTZW50OiZuYnNwO1R1ZXNkYXksJm5ic3A7SmFudWFyeSZu
YnNwOzMxLCZuYnNwOzIwMTImbmJzcDsxOjM0Jm5ic3A7UE0KICAgPC9kaXY+IAogICA8ZGl2IHN0
eWxlPSJGT05ULVNJWkU6IDE4cHgiPgogICAgU3ViamVjdDombmJzcDtSZTombmJzcDtbeHJibG9j
a10mbmJzcDtQb2xsJm5ic3A7Zm9yJm5ic3A7cHJvZ3Jlc3NpbmcmbmJzcDt0aGUmbmJzcDtRb0UK
ICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE4cHgiPgogICAgJm5ic3A7CiAg
IDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOHB4Ij4KICAgICZuYnNwOwogICA8
L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMThweCI+CiAgICAmZ3Q7CiAgIDwvZGl2
PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOHB4Ij4KICAgICZndDsmbmJzcDtBbGw7CiAg
IDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOHB4Ij4KICAgICZndDsKICAgPC9k
aXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE4cHgiPgogICAgJmd0OyZuYnNwO0kmbmJz
cDtuZWVkJm5ic3A7dG8mbmJzcDtzZWUmbmJzcDt3aGF0Jm5ic3A7V0cmbmJzcDt0aGlua3MmbmJz
cDtvbiZuYnNwO3RoZSZuYnNwO21hdHRlciZuYnNwO2JlbG93Jm5ic3A7Zm9yCiAgIDwvZGl2PiAK
ICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOHB4Ij4KICAgICZndDsmbmJzcDt1cyZuYnNwO3Rv
Jm5ic3A7cHJvZ3Jlc3MmbmJzcDt0aGUmbmJzcDtRb0UmbmJzcDttaWxlc3RvbmUuCiAgIDwvZGl2
PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOHB4Ij4KICAgICZndDsKICAgPC9kaXY+IAog
ICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE4cHgiPgogICAgJmd0OyZuYnNwO0lmJm5ic3A7eW91
Jm5ic3A7aGF2ZSZuYnNwO25vJm5ic3A7b3BpbmlvbnMmbmJzcDtvbiZuYnNwO3RoZSZuYnNwO21h
dHRlciwmbmJzcDtwbGVhc2UmbmJzcDtpbmRpY2F0ZQogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9
IkZPTlQtU0laRTogMThweCI+CiAgICAmZ3Q7Jm5ic3A7aXQmbmJzcDthcyZuYnNwO3dlbGwuCiAg
IDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOHB4Ij4KICAgICZndDsKICAgPC9k
aXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE4cHgiPgogICAgJmd0OyZuYnNwO01hbnkm
bmJzcDtUaGFua3MKICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE4cHgiPgog
ICAgJmd0OyZuYnNwOyZuYnNwO1NoaWRhCiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1T
SVpFOiAxOHB4Ij4KICAgICZndDsKICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6
IDE4cHgiPgogICAgJmd0OyZuYnNwO09uJm5ic3A7SmFuJm5ic3A7MTksJm5ic3A7MjAxMiwmbmJz
cDthdCZuYnNwOzg6NTgmbmJzcDtQTSwmbmJzcDtTaGlkYSZuYnNwO1NjaHViZXJ0Jm5ic3A7d3Jv
dGU6CiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOHB4Ij4KICAgICZndDsK
ICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE4cHgiPgogICAgJmd0OyZndDsK
ICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE4cHgiPgogICAgJmd0OyZndDsm
bmJzcDtBbGw7CiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOHB4Ij4KICAg
ICZndDsmZ3Q7CiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOHB4Ij4KICAg
ICZndDsmZ3Q7Jm5ic3A7QWx0aG91Z2gmbmJzcDthJm5ic3A7cG9sbCZuYnNwO2ZvciZuYnNwO2Ry
YWZ0LXd1LXhyYmxvY2stcnRjcC14ci1xdWFsaXR5LW1vbml0b3JpbmcmbmJzcDtlbmRlZCZuYnNw
O2luCiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOHB4Ij4KICAgICZndDsm
Z3Q7Jm5ic3A7ZmF2b3ImbmJzcDtvZiZuYnNwO2Fkb3B0aW5nJm5ic3A7dGhlJm5ic3A7ZHJhZnQs
Jm5ic3A7dGhlJm5ic3A7Y29tbWVudHMmbmJzcDtwcm92aWRlZCZuYnNwO2J5Jm5ic3A7Q29saW4m
bmJzcDthcmUmbmJzcDt3b3J0aAogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTog
MThweCI+CiAgICAmZ3Q7Jmd0OyZuYnNwO25vdGluZyZuYnNwO2FzJm5ic3A7d2UmbmJzcDttb3Zl
Jm5ic3A7Zm9yd2FyZC4KICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE4cHgi
PgogICAgJmd0OyZndDsKICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE4cHgi
PgogICAgJmd0OyZndDsmbmJzcDtJJm5ic3A7ZG8mbmJzcDtoYXZlJm5ic3A7c29tZSZuYnNwO3F1
ZXN0aW9ucyZuYnNwO3doaWNoJm5ic3A7SSZuYnNwO3RoaW5rJm5ic3A7d2lsbCZuYnNwO2hlbHAm
bmJzcDt1cyZuYnNwO2NsYXJpZnkKICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6
IDE4cHgiPgogICAgJmd0OyZndDsmbmJzcDt0aGUmbmJzcDt3YXkmbmJzcDtmb3J3YXJkLgogICA8
L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMThweCI+CiAgICAmZ3Q7Jmd0OwogICA8
L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMThweCI+CiAgICAmZ3Q7Jmd0OyZuYnNw
O0EuJm5ic3A7VGhlcmUmbmJzcDthcmUmbmJzcDt0aHJlZSZuYnNwO3NlZ21lbnQmbmJzcDt0eXBl
cyZuYnNwO2RlZmluZWQmbmJzcDsoMS4mbmJzcDtlYWNoJm5ic3A7bWVkaWEKICAgPC9kaXY+IAog
ICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE4cHgiPgogICAgJmd0OyZndDsmbmJzcDsmbmJzcDsm
bmJzcDtzZW50Jm5ic3A7aW4mbmJzcDtzZXBhcmF0ZSZuYnNwO1JUUCZuYnNwO3N0cmVhbSwmbmJz
cDsyLiZuYnNwO0xheWVyZWQmbmJzcDt2aWRlbyZuYnNwO3Nlc3Npb24sCiAgIDwvZGl2PiAKICAg
PGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOHB4Ij4KICAgICZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5i
c3A7My4mbmJzcDtNdWx0aS1jaGFubmVsJm5ic3A7YXVkaW8pJm5ic3A7aW4mbmJzcDt0aGUmbmJz
cDtkcmFmdCwmbmJzcDsmbmJzcDtkbyZuYnNwO3dlJm5ic3A7c2VlJm5ic3A7YSZuYnNwO25lZWQm
bmJzcDtmb3IKICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE4cHgiPgogICAg
Jmd0OyZndDsmbmJzcDsmbmJzcDsmbmJzcDthbGwmbmJzcDt0aHJlZSZuYnNwO3JpZ2h0Jm5ic3A7
bm93Jm5ic3A7b3ImbmJzcDtpbiZuYnNwO25lYXImbmJzcDsmbmJzcDtmdXR1cmUmbmJzcDsoc2F5
Jm5ic3A7bmV4dCZuYnNwOzEyJm5ic3A7bW9udGhzKSZuYnNwOz8KICAgPC9kaXY+IAogICA8ZGl2
IHN0eWxlPSJGT05ULVNJWkU6IDE4cHgiPgogICAgJmd0OyZndDsKICAgPC9kaXY+IAogICA8ZGl2
IHN0eWxlPSJGT05ULVNJWkU6IDE4cHgiPgogICAgJmd0OyZndDsmbmJzcDtCLiZuYnNwO09SJm5i
c3A7YXJlJm5ic3A7d2UmbmJzcDtoYXBweSZuYnNwO3dpdGgmbmJzcDtvbmx5Jm5ic3A7Y292ZXJp
bmcmbmJzcDtvbmUmbmJzcDtmb3ImbmJzcDtub3cmbmJzcDsoTGlrZWx5CiAgIDwvZGl2PiAKICAg
PGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOHB4Ij4KICAgICZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5i
c3A7dGhlJm5ic3A7MS4mbmJzcDthcyZuYnNwO0kmbmJzcDt1bmRlcnN0YW5kJm5ic3A7cGVvcGxl
Jm5ic3A7YXJlJm5ic3A7bW9zdCZuYnNwO2ludGVyZXN0ZWQmbmJzcDtpbiZuYnNwO3RoZSZuYnNw
OzEuKQogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMThweCI+CiAgICAmZ3Q7
Jmd0OyZuYnNwOyZuYnNwOyZuYnNwO2FuZCZuYnNwO2NyZWF0ZSZuYnNwO2EmbmJzcDtkcmFmdCZu
YnNwO3doZW4mbmJzcDt0aGVyZSZuYnNwO2lzJm5ic3A7YSZuYnNwO3JlYWwmbmJzcDtuZWVkJm5i
c3A7Zm9yJm5ic3A7Mi4mbmJzcDthbmQmbmJzcDszLj8KICAgPC9kaXY+IAogICA8ZGl2IHN0eWxl
PSJGT05ULVNJWkU6IDE4cHgiPgogICAgJmd0OyZndDsKICAgPC9kaXY+IAogICA8ZGl2IHN0eWxl
PSJGT05ULVNJWkU6IDE4cHgiPgogICAgJmd0OyZndDsmbmJzcDtDLiZuYnNwO0lmJm5ic3A7YW5z
d2VyJm5ic3A7aXMmbmJzcDt5ZXMmbmJzcDt0byZuYnNwO3F1ZXN0aW9uJm5ic3A7QS4sJm5ic3A7
ZG8mbmJzcDt3ZSZuYnNwO3dhbnQmbmJzcDt0byZuYnNwO3NlZSZuYnNwO3RoZQogICA8L2Rpdj4g
CiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMThweCI+CiAgICAmZ3Q7Jmd0OyZuYnNwOyZuYnNw
OyZuYnNwO2RyYWZ0Jm5ic3A7c3BsaXQmbmJzcDtpbnRvJm5ic3A7dGhyZWUmbmJzcDthcyZuYnNw
O0NvbGluJm5ic3A7cHJvcG9zZWQmbmJzcDtvciZuYnNwO2hhdmUmbmJzcDt0aGVtJm5ic3A7YWxs
CiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOHB4Ij4KICAgICZndDsmZ3Q7
Jm5ic3A7Jm5ic3A7Jm5ic3A7ZGVmaW5lZCZuYnNwO2luJm5ic3A7c2luZ2xlJm5ic3A7ZHJhZnQm
bmJzcDthcyZuYnNwO2l0Jm5ic3A7Y3VycmVudGx5Jm5ic3A7aXMuCiAgIDwvZGl2PiAKICAgPGRp
diBzdHlsZT0iRk9OVC1TSVpFOiAxOHB4Ij4KICAgICZndDsmZ3Q7CiAgIDwvZGl2PiAKICAgPGRp
diBzdHlsZT0iRk9OVC1TSVpFOiAxOHB4Ij4KICAgICZndDsmZ3Q7Jm5ic3A7SSZuYnNwO2Fza2Vk
Jm5ic3A7dGhlJm5ic3A7QUQmbmJzcDtpZiZuYnNwO3dlJm5ic3A7Y2FuJm5ic3A7c3BsaXQmbmJz
cDt0aGUmbmJzcDtkcmFmdHMmbmJzcDtpbnRvJm5ic3A7MyZuYnNwO2RyYWZ0cyZuYnNwO3VuZGVy
CiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOHB4Ij4KICAgICZndDsmZ3Q7
Jm5ic3A7c2luZ2xlJm5ic3A7bWlsZXN0b25lJm5ic3A7YnV0Jm5ic3A7SSZuYnNwO3dhbnQmbmJz
cDt0byZuYnNwO21ha2UmbmJzcDtzdXJlJm5ic3A7d2UmbmJzcDtkbyZuYnNwO3RoYXQmbmJzcDth
ZnRlcgogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMThweCI+CiAgICAmZ3Q7
Jmd0OyZuYnNwO3dlJm5ic3A7YWdyZWUmbmJzcDthcyZuYnNwO2EmbmJzcDtXRyZuYnNwO3RoYXQm
bmJzcDt3ZSZuYnNwO25lZWQmbmJzcDthbGwmbmJzcDt0aHJlZSZuYnNwO3NlZ21lbnQmbmJzcDt0
eXBlcwogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMThweCI+CiAgICAmZ3Q7
Jmd0OyZuYnNwO1JJR0hUJm5ic3A7Tk9XJm5ic3A7YmVmb3JlJm5ic3A7d2UmbmJzcDtkbyZuYnNw
O3NvLgogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMThweCI+CiAgICAmZ3Q7
Jmd0OwogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMThweCI+CiAgICAmZ3Q7
Jmd0OyZuYnNwO1dlJm5ic3A7aGF2ZSZuYnNwO2EmbmJzcDtsb3QmbmJzcDtvZiZuYnNwO25ldyZu
YnNwO2l0ZW1zJm5ic3A7dGhhdCZuYnNwO3Blb3BsZSZuYnNwO2FyZSZuYnNwO2ludGVyZXN0ZWQm
bmJzcDtpbgogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMThweCI+CiAgICAm
Z3Q7Jmd0OyZuYnNwO3dvcmtpbmcmbmJzcDtvbiZuYnNwO3RoYXQmbmJzcDthcmUmbmJzcDtub3Qm
bmJzcDtjb3ZlcmVkJm5ic3A7aW4mbmJzcDtvdXImbmJzcDttaWxlc3RvbmVzLCZuYnNwO3NvJm5i
c3A7SQogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMThweCI+CiAgICAmZ3Q7
Jmd0OyZuYnNwO3dhbnQmbmJzcDt0byZuYnNwO21ha2UmbmJzcDtzdXJlJm5ic3A7d2UmbmJzcDtm
b2N1cyZuYnNwO29uJm5ic3A7aXRlbXMmbmJzcDt0aGF0Jm5ic3A7YXJlJm5ic3A7JnF1b3Q7TVVT
VAogICA8L2Rpdj4gCiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMThweCI+CiAgICAmZ3Q7Jmd0
OyZuYnNwO2hhdmUmcXVvdDsmbmJzcDtyYXRoZXImbmJzcDt0aGFuJm5ic3A7JnF1b3Q7TUFZJm5i
c3A7bmVlZCZuYnNwO2l0Jm5ic3A7aW4mbmJzcDtmdXR1cmUmcXVvdDsmbmJzcDtvciZuYnNwOyZx
dW90O05JQ0UmbmJzcDt0byZuYnNwO2hhdmUmcXVvdDsuCiAgIDwvZGl2PiAKICAgPGRpdiBzdHls
ZT0iRk9OVC1TSVpFOiAxOHB4Ij4KICAgICZndDsmZ3Q7CiAgIDwvZGl2PiAKICAgPGRpdiBzdHls
ZT0iRk9OVC1TSVpFOiAxOHB4Ij4KICAgICZndDsmZ3Q7Jm5ic3A7UmVnYXJkcwogICA8L2Rpdj4g
CiAgIDxkaXYgc3R5bGU9IkZPTlQtU0laRTogMThweCI+CiAgICAmZ3Q7Jmd0OyZuYnNwO1NoaWRh
CiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOHB4Ij4KICAgICZndDsmZ3Q7
Jm5ic3A7X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KICAg
PC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE4cHgiPgogICAgJmd0OyZndDsmbmJz
cDt4cmJsb2NrJm5ic3A7bWFpbGluZyZuYnNwO2xpc3QKICAgPC9kaXY+IAogICA8ZGl2IHN0eWxl
PSJGT05ULVNJWkU6IDE4cHgiPgogICAgJmd0OyZndDsmbmJzcDt4cmJsb2NrQGlldGYub3JnCiAg
IDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOHB4Ij4KICAgICZndDsmZ3Q7IAog
ICAgPGEgc3R5bGU9IkZPTlQtU0laRTogMTZweCIgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby94cmJsb2NrIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL3hyYmxvY2s8L2E+CiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAx
OHB4Ij4KICAgICZndDsKICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE4cHgi
PgogICAgJmd0OyZuYnNwO19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fCiAgIDwvZGl2PiAKICAgPGRpdiBzdHlsZT0iRk9OVC1TSVpFOiAxOHB4Ij4KICAgICZn
dDsmbmJzcDt4cmJsb2NrJm5ic3A7bWFpbGluZyZuYnNwO2xpc3QKICAgPC9kaXY+IAogICA8ZGl2
IHN0eWxlPSJGT05ULVNJWkU6IDE4cHgiPgogICAgJmd0OyZuYnNwO3hyYmxvY2tAaWV0Zi5vcmcK
ICAgPC9kaXY+IAogICA8ZGl2IHN0eWxlPSJGT05ULVNJWkU6IDE4cHgiPgogICAgJmd0OyAKICAg
IDxhIHN0eWxlPSJGT05ULVNJWkU6IDE2cHgiIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8veHJibG9jayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby94cmJsb2NrPC9hPgogICA8L2Rpdj4KICA8L2Rpdj4KIDwvYm9keT4KPC9odG1sPg==
------=_Part_1175_20397511.1328059447043--


From bill.wu@huawei.com  Tue Jan 31 18:30:44 2012
Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 487DC11E80B6 for <xrblock@ietfa.amsl.com>; Tue, 31 Jan 2012 18:30:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.281
X-Spam-Level: 
X-Spam-Status: No, score=-6.281 tagged_above=-999 required=5 tests=[AWL=0.317,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pT33+xkG+qUg for <xrblock@ietfa.amsl.com>; Tue, 31 Jan 2012 18:30:42 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 7539011E80B8 for <xrblock@ietf.org>; Tue, 31 Jan 2012 18:30:41 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYP0023A0A6ZK@szxga05-in.huawei.com> for xrblock@ietf.org; Wed, 01 Feb 2012 10:30:06 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYP0097M0A5MW@szxga05-in.huawei.com> for xrblock@ietf.org; Wed, 01 Feb 2012 10:30:06 +0800 (CST)
Received: from szxeml214-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGR34152; Wed, 01 Feb 2012 10:30:03 +0800
Received: from SZXEML402-HUB.china.huawei.com (10.82.67.32) by szxeml214-edg.china.huawei.com (172.24.2.29) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 01 Feb 2012 10:29:34 +0800
Received: from w53375q (10.138.41.130) by szxeml402-hub.china.huawei.com (10.82.67.32) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 01 Feb 2012 10:29:57 +0800
Date: Wed, 01 Feb 2012 10:29:56 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: zhaojing@sttri.com.cn, xrblock <xrblock@ietf.org>
Message-id: <F68BB6988B0E4540AC4FE8C9438EA506@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: multipart/alternative; boundary="Boundary_(ID_JXFhwqz/Dy6Be6a1mKYXpA)"
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <5161211.151328001031222.JavaMail.root@ent8>
Subject: Re: [xrblock] I-D Action: draft-zorn-xrblock-rtcp-xr-al-stat-04.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2012 02:30:44 -0000

--Boundary_(ID_JXFhwqz/Dy6Be6a1mKYXpA)
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: 7BIT

Hi, Jing:
Thank for taking time to review this document. Please see my replies inline below.

Regards!
-Qin
  ----- Original Message ----- 
  From: zhaojing@sttri.com.cn 
  To: Qin Wu ; xrblock 
  Sent: Tuesday, January 31, 2012 5:10 PM
  Subject: Re: Re: [xrblock] I-D Action: draft-zorn-xrblock-rtcp-xr-al-stat-04.txt


  Hi, Qin: 
  I have review draft-zorn-xrblock-rtcp-xr-al-stat and have two comments. 
   
  1.This draft specifies three new XR Blocks. The first two are linked to burst gap  
  loss draft and burst gap discard draft. I agree with you that these two XR blocks 
  define calculation method for the derived metrics mentioned in the burst gap drafts. 
  and are two most important metric blocks which the burst gap drafts count on.  
  My question is who sends these two XR blocks? 
[Qin]: There are two cases:
a. The media receiver sends these two new XR Blocks (i.e., Burst/Gap Loss Summsary Statistics Block
and Burst/Gap Discard Summsary Statistics Block in the draft-zorn-xrblock-rtcp-xr-al-stat)
b. The media sender sends these two new XR Blocks.
If the media receiver is responsible for sending, the media receiver need to first calculate basic direct metrics(i.e.,Burst/Gap Loss 
and Burst/Gap discard) defined in the draft-ietf-xrblock-rtcp-xr-burst-gap-loss and draft-ietf-xrblock-rtcp-xr-burst-gap-discard and then use these basic
metrics to calculate burst gap summary statistics defined in the draft-zorn-xrblock-rtcp-xr-al-stat.

If the media sender is responsible for sending, the implicit assumption is the media sender has already received the Burst/Gap Loss 
and Burst/Gap discard defined in draft-ietf-xrblock-rtcp-xr-burst-gap-loss and draft-ietf-xrblock-rtcp-xr-burst-gap-discard. The media sender
can use recieved the Burst/Gap Loss and Burst/Gap discard to calculate burst gap summary statistics defined in the draft-zorn-xrblock-rtcp-xr-al-stat.
   
  2. The third XR Block defined in this draft is Statistics Summary Block for 
   Application Layer Loss/Duplication. I think this XR Block is linked to I/P/B frame statistics. 
  This metric blocks can tell us which frame types were affected and is therefore a useful metric 
   to form an accurate assessment of user quality of experience. 

[Qin]:  Exactly.

  However it is not clear to me  
  how do you calculate Number of frames expected?

[Qin]:  The metrics we defined in this XR Block is not easy to be captured. You should look into RTP packet or deep parse RTP packet.
Fortunately these metrics reflect end to end performance at the service level and therefore we can measure them at the user end point, e.g., from
decoder or demuxer.
   Isn't more easier to calculate how many frames are received 
  ranther than gathering the number of frame expected? 

[Qin]: your are right, if we measure these metrics at the user end point, it is more easy to gather the number of frames received
than the number of frames expected since it is easy for the user end point to know how many frames received.  I will fix this in the update.

>Another comment is isn't it useful to collect how many different type of frames were discarded  by the media reciever? 

[Qin]: That's a good point. But this is only useful in the case where only the receiver is allowed to discard impaired frames.
I propose to add this metric into the new version. Thanks.
  Cheers! 
  ZhaoJing 
  ---------------------------- 
  ----- Original Message -----  
  From: "Qin Wu" <bill.wu@huawei.com> 
  To: <xrblock@ietf.org> 
  Sent: Thursday, January 19, 2012 4:40 PM 
  Subject: Re: [xrblock] I-D Action: draft-zorn-xrblock-rtcp-xr-al-stat-04.txt 
   
   
  > Hi, 
  > A minor update to draft-zorn-xrblock-rtcp-xr-al-stat which is used to get consistent with Burst Gap related draft. 
  > This draft missed the discussion due to presentation timeout  in the last IETF meeting. However this draft provides calculation method 
  > for the derived metric listed in the two burst gap related draft and also defines RTCP XR packet format to carry these derived  
  > metric. 
  > I like to see WG adopt this draft as work item or adopt a milestone to link to this draft.  
  > Any review and comments are welcome. 
  >  
  > Regards! 
  > -Qin 
  > ----- Original Message -----  
  > From: <internet-drafts@ietf.org> 
  > To: <i-d-announce@ietf.org> 
  > Sent: Thursday, January 19, 2012 3:04 PM 
  > Subject: I-D Action: draft-zorn-xrblock-rtcp-xr-al-stat-04.txt 
  >  
  >  
  >>  
  >> A New Internet-Draft is available from the on-line Internet-Drafts directories. 
  >>  
  >> Title           : RTCP XR for Summary Statistics Metrics Reporting 
  >> Author(s)       : Glen Zorn 
  >>                          Roland Schott 
  >>                          Qin Wu 
  >>                          Rachel Huang 
  >> Filename        : draft-zorn-xrblock-rtcp-xr-al-stat-04.txt 
  >> Pages           : 15 
  >> Date            : 2012-01-18 
  >>  
  >>   This document defines three RTCP XR Report Blocks and associated SDP 
  >>   parameters that allows the reporting of loss, duplication and discard 
  >>   summary statistics metrics for use in a range of RTP applications. 
  >>  
  >>  
  >> A URL for this Internet-Draft is: 
  >> http://www.ietf.org/internet-drafts/draft-zorn-xrblock-rtcp-xr-al-stat-04.txt 
  >>  
  >> Internet-Drafts are also available by anonymous FTP at: 
  >> ftp://ftp.ietf.org/internet-drafts/ 
  >>  
  >> This Internet-Draft can be retrieved at: 
  >> ftp://ftp.ietf.org/internet-drafts/draft-zorn-xrblock-rtcp-xr-al-stat-04.txt 
  >>  
  >> _______________________________________________ 
  >> I-D-Announce mailing list 
  >> I-D-Announce@ietf.org 
  >> https://www.ietf.org/mailman/listinfo/i-d-announce 
  >> Internet-Draft directories: http://www.ietf.org/shadow.html 
  >> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt 
  >> 
  > _______________________________________________ 
  > xrblock mailing list 
  > xrblock@ietf.org 
  > https://www.ietf.org/mailman/listinfo/xrblock 

--Boundary_(ID_JXFhwqz/Dy6Be6a1mKYXpA)
Content-type: text/html; charset=UTF-8
Content-transfer-encoding: base64

77u/PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9u
YWwvL0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0
PXV0Zi04IiBodHRwLWVxdWl2PUNvbnRlbnQtVHlwZT4NCjxNRVRBIG5hbWU9R0VORVJBVE9SIGNv
bnRlbnQ9Ik1TSFRNTCA4LjAwLjYwMDEuMTkxNzAiPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+
DQo8Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPkhpLCBKaW5nOjwvRElWPg0KPERJVj5UaGFu
ayBmb3IgdGFraW5nIHRpbWUgdG8gcmV2aWV3IHRoaXMgZG9jdW1lbnQuIFBsZWFzZSBzZWUgbXkg
cmVwbGllcyBpbmxpbmUgDQpiZWxvdy48L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPlJl
Z2FyZHMhPC9ESVY+DQo8RElWPi1RaW48L0RJVj4NCjxCTE9DS1FVT1RFIA0Kc3R5bGU9IkJPUkRF
Ui1MRUZUOiAjMDAwMDAwIDJweCBzb2xpZDsgUEFERElORy1MRUZUOiA1cHg7IFBBRERJTkctUklH
SFQ6IDBweDsgTUFSR0lOLUxFRlQ6IDVweDsgTUFSR0lOLVJJR0hUOiAwcHgiIA0KZGlyPWx0cj4N
CiAgPERJViBzdHlsZT0iRk9OVDogOXB0IOWui+S9kyI+PEZPTlQgc2l6ZT0zPi0tLS0tIE9yaWdp
bmFsIE1lc3NhZ2UgLS0tLS0gDQogIDwvRk9OVD48L0RJVj4NCiAgPERJViBzdHlsZT0iRk9OVDog
OXB0IOWui+S9kzsgQkFDS0dST1VORDogI2U0ZTRlNDsgZm9udC1jb2xvcjogYmxhY2siPjxGT05U
IA0KICBzaXplPTM+RnJvbTogPC9GT05UPjxBIHRpdGxlPXpoYW9qaW5nQHN0dHJpLmNvbS5jbiAN
CiAgaHJlZj0ibWFpbHRvOnpoYW9qaW5nQHN0dHJpLmNvbS5jbiI+PEZPTlQgDQogIHNpemU9Mz56
aGFvamluZ0BzdHRyaS5jb20uY248L0ZPTlQ+PC9BPjxGT05UIHNpemU9Mz4gPC9GT05UPjwvRElW
Pg0KICA8RElWIHN0eWxlPSJGT05UOiA5cHQg5a6L5L2TIj48Rk9OVCBzaXplPTM+VG86IDwvRk9O
VD48QSB0aXRsZT1iaWxsLnd1QGh1YXdlaS5jb20gDQogIGhyZWY9Im1haWx0bzpiaWxsLnd1QGh1
YXdlaS5jb20iPjxGT05UIHNpemU9Mz5RaW4gV3U8L0ZPTlQ+PC9BPjxGT05UIHNpemU9Mz4gOyAN
CiAgPC9GT05UPjxBIHRpdGxlPXhyYmxvY2tAaWV0Zi5vcmcgaHJlZj0ibWFpbHRvOnhyYmxvY2tA
aWV0Zi5vcmciPjxGT05UIA0KICBzaXplPTM+eHJibG9jazwvRk9OVD48L0E+PEZPTlQgc2l6ZT0z
PiA8L0ZPTlQ+PC9ESVY+DQogIDxESVYgc3R5bGU9IkZPTlQ6IDlwdCDlrovkvZMiPjxGT05UIHNp
emU9Mz5TZW50OiBUdWVzZGF5LCBKYW51YXJ5IDMxLCAyMDEyIDU6MTAgDQogIFBNPC9GT05UPjwv
RElWPg0KICA8RElWIHN0eWxlPSJGT05UOiA5cHQg5a6L5L2TIj48Rk9OVCBzaXplPTM+U3ViamVj
dDogUmU6IFJlOiBbeHJibG9ja10gSS1EIEFjdGlvbjogDQogIGRyYWZ0LXpvcm4teHJibG9jay1y
dGNwLXhyLWFsLXN0YXQtMDQudHh0PC9GT05UPjwvRElWPg0KICA8RElWPjxCUj48L0RJVj4NCiAg
PERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCBzaXplPTM+SGksJm5ic3A7UWluOiA8
L0ZPTlQ+PC9ESVY+DQogIDxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+PEZPTlQgDQogIHNp
emU9Mz5JJm5ic3A7aGF2ZSZuYnNwO3JldmlldyZuYnNwO2RyYWZ0LXpvcm4teHJibG9jay1ydGNw
LXhyLWFsLXN0YXQmbmJzcDthbmQmbmJzcDtoYXZlJm5ic3A7dHdvJm5ic3A7Y29tbWVudHMuIA0K
ICA8L0ZPTlQ+PC9ESVY+DQogIDxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+PEZPTlQgc2l6
ZT0zPiA8L0ZPTlQ+PC9ESVY+DQogIDxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+PEZPTlQg
DQogIHNpemU9Mz4xLlRoaXMmbmJzcDtkcmFmdCZuYnNwO3NwZWNpZmllcyZuYnNwO3RocmVlJm5i
c3A7bmV3Jm5ic3A7WFImbmJzcDtCbG9ja3MuJm5ic3A7VGhlJm5ic3A7Zmlyc3QmbmJzcDt0d28m
bmJzcDthcmUmbmJzcDtsaW5rZWQmbmJzcDt0byZuYnNwO2J1cnN0Jm5ic3A7Z2FwJm5ic3A7IA0K
ICA8L0ZPTlQ+PC9ESVY+DQogIDxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+PEZPTlQgDQog
IHNpemU9Mz5sb3NzJm5ic3A7ZHJhZnQmbmJzcDthbmQmbmJzcDtidXJzdCZuYnNwO2dhcCZuYnNw
O2Rpc2NhcmQmbmJzcDtkcmFmdC4mbmJzcDtJJm5ic3A7YWdyZWUmbmJzcDt3aXRoJm5ic3A7eW91
Jm5ic3A7dGhhdCZuYnNwO3RoZXNlJm5ic3A7dHdvJm5ic3A7WFImbmJzcDtibG9ja3MgDQogIDwv
Rk9OVD48L0RJVj4NCiAgPERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCANCiAgc2l6
ZT0zPmRlZmluZSZuYnNwO2NhbGN1bGF0aW9uJm5ic3A7bWV0aG9kJm5ic3A7Zm9yJm5ic3A7dGhl
Jm5ic3A7ZGVyaXZlZCZuYnNwO21ldHJpY3MmbmJzcDttZW50aW9uZWQmbmJzcDtpbiZuYnNwO3Ro
ZSZuYnNwO2J1cnN0Jm5ic3A7Z2FwJm5ic3A7ZHJhZnRzLiANCiAgPC9GT05UPjwvRElWPg0KICA8
RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPjxGT05UIA0KICBzaXplPTM+YW5kJm5ic3A7YXJl
Jm5ic3A7dHdvJm5ic3A7bW9zdCZuYnNwO2ltcG9ydGFudCZuYnNwO21ldHJpYyZuYnNwO2Jsb2Nr
cyZuYnNwO3doaWNoJm5ic3A7dGhlJm5ic3A7YnVyc3QmbmJzcDtnYXAmbmJzcDtkcmFmdHMmbmJz
cDtjb3VudCZuYnNwO29uLiZuYnNwOyANCiAgPC9GT05UPjwvRElWPg0KICA8RElWIHN0eWxlPSJG
T05ULVNJWkU6IDE5cHgiPjxGT05UIA0KICBzaXplPTM+TXkmbmJzcDtxdWVzdGlvbiZuYnNwO2lz
Jm5ic3A7d2hvJm5ic3A7c2VuZHMmbmJzcDt0aGVzZSZuYnNwO3R3byZuYnNwO1hSJm5ic3A7Ymxv
Y2tzPyANCiAgPC9GT05UPjwvRElWPjwvQkxPQ0tRVU9URT4NCjxESVYgc3R5bGU9IkZPTlQtU0la
RTogMTlweDsgTUFSR0lOLVJJR0hUOiAwcHgiIGRpcj1sdHI+PEZPTlQgc2l6ZT0zPltRaW5dOiAN
ClRoZXJlIGFyZSB0d28gY2FzZXM6PC9GT05UPjwvRElWPg0KPERJViBzdHlsZT0iRk9OVC1TSVpF
OiAxOXB4OyBNQVJHSU4tUklHSFQ6IDBweCIgZGlyPWx0cj48Rk9OVCBzaXplPTM+YS4gVGhlIA0K
bWVkaWEgcmVjZWl2ZXIgc2VuZHMgdGhlc2UgdHdvIG5ldyBYUiBCbG9ja3MgKGkuZS4sIEJ1cnN0
L0dhcCBMb3NzIFN1bW1zYXJ5IA0KU3RhdGlzdGljcyBCbG9jazxCUj5hbmQgQnVyc3QvR2FwJm5i
c3A7RGlzY2FyZCBTdW1tc2FyeSBTdGF0aXN0aWNzIEJsb2NrIGluIHRoZSANCmRyYWZ0LXpvcm4t
eHJibG9jay1ydGNwLXhyLWFsLXN0YXQpPEJSPmIuIFRoZSBtZWRpYSBzZW5kZXIgc2VuZHMgdGhl
c2UgdHdvIG5ldyANClhSIEJsb2Nrcy48L0ZPTlQ+PC9ESVY+DQo8RElWIHN0eWxlPSJGT05ULVNJ
WkU6IDE5cHg7IE1BUkdJTi1SSUdIVDogMHB4IiBkaXI9bHRyPjxGT05UIHNpemU9Mz5JZiB0aGUg
DQptZWRpYSByZWNlaXZlciBpcyByZXNwb25zaWJsZSBmb3Igc2VuZGluZywgdGhlIG1lZGlhIHJl
Y2VpdmVyIG5lZWQgdG8gZmlyc3QgDQpjYWxjdWxhdGUgYmFzaWMgZGlyZWN0IG1ldHJpY3MoaS5l
LixCdXJzdC9HYXAgTG9zcyANCjxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweDsgTUFSR0lOLVJJ
R0hUOiAwcHgiIGRpcj1sdHI+PEZPTlQgc2l6ZT0zPmFuZCANCkJ1cnN0L0dhcCBkaXNjYXJkKTwv
Rk9OVD4gPC9GT05UPjxGT05UIHNpemU9Mz5kZWZpbmVkIDwvRk9OVD48Rk9OVCBzaXplPTM+aW4g
dGhlIA0KZHJhZnQtaWV0Zi14cmJsb2NrLXJ0Y3AteHItYnVyc3QtZ2FwLWxvc3MgYW5kIA0KZHJh
ZnQtaWV0Zi14cmJsb2NrLXJ0Y3AteHItYnVyc3QtZ2FwLWRpc2NhcmQgYW5kIHRoZW4gdXNlIHRo
ZXNlIA0KYmFzaWM8L0ZPTlQ+PC9ESVY+PC9ESVY+DQo8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5
cHg7IE1BUkdJTi1SSUdIVDogMHB4IiBkaXI9bHRyPjxGT05UIHNpemU9Mz5tZXRyaWNzIHRvIA0K
Y2FsY3VsYXRlIGJ1cnN0IGdhcCBzdW1tYXJ5IHN0YXRpc3RpY3MgZGVmaW5lZCBpbiB0aGUgDQpk
cmFmdC16b3JuLXhyYmxvY2stcnRjcC14ci1hbC1zdGF0LjwvRk9OVD48L0RJVj4NCjxESVYgc3R5
bGU9IkZPTlQtU0laRTogMTlweDsgTUFSR0lOLVJJR0hUOiAwcHgiIGRpcj1sdHI+PEZPTlQgDQpz
aXplPTM+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4OyBN
QVJHSU4tUklHSFQ6IDBweCIgZGlyPWx0cj48Rk9OVCBzaXplPTM+SWYgdGhlIA0KbWVkaWEgc2Vu
ZGVyIGlzIHJlc3BvbnNpYmxlIGZvciBzZW5kaW5nLCB0aGUgaW1wbGljaXQgYXNzdW1wdGlvbiBp
cyB0aGUgbWVkaWEgDQpzZW5kZXIgaGFzIGFscmVhZHkgcmVjZWl2ZWQgdGhlIEJ1cnN0L0dhcCBM
b3NzIDwvRk9OVD48L0RJVj4NCjxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweDsgTUFSR0lOLVJJ
R0hUOiAwcHgiIGRpcj1sdHI+PEZPTlQgc2l6ZT0zPmFuZCANCkJ1cnN0L0dhcCBkaXNjYXJkIGRl
ZmluZWQgaW4gZHJhZnQtaWV0Zi14cmJsb2NrLXJ0Y3AteHItYnVyc3QtZ2FwLWxvc3MgYW5kIA0K
ZHJhZnQtaWV0Zi14cmJsb2NrLXJ0Y3AteHItYnVyc3QtZ2FwLWRpc2NhcmQuIFRoZSBtZWRpYSBz
ZW5kZXI8L0ZPTlQ+PC9ESVY+DQo8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5cHg7IE1BUkdJTi1S
SUdIVDogMHB4IiBkaXI9bHRyPjxGT05UIHNpemU9Mz5jYW4gdXNlIA0KcmVjaWV2ZWQgdGhlIEJ1
cnN0L0dhcCBMb3NzIDxGT05UIHNpemU9Mz5hbmQgQnVyc3QvR2FwIGRpc2NhcmQgdG8gY2FsY3Vs
YXRlIA0KYnVyc3QgZ2FwIHN1bW1hcnkgc3RhdGlzdGljcyBkZWZpbmVkIGluIHRoZSANCmRyYWZ0
LXpvcm4teHJibG9jay1ydGNwLXhyLWFsLXN0YXQuPC9GT05UPjwvRk9OVD48L0RJVj4NCjxCTE9D
S1FVT1RFIA0Kc3R5bGU9IkJPUkRFUi1MRUZUOiAjMDAwMDAwIDJweCBzb2xpZDsgUEFERElORy1M
RUZUOiA1cHg7IFBBRERJTkctUklHSFQ6IDBweDsgTUFSR0lOLUxFRlQ6IDVweDsgTUFSR0lOLVJJ
R0hUOiAwcHgiIA0KZGlyPWx0cj4NCiAgPERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48Rk9O
VCBzaXplPTM+IDwvRk9OVD48L0RJVj4NCiAgPERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48
Rk9OVCANCiAgc2l6ZT0zPjIuJm5ic3A7VGhlJm5ic3A7dGhpcmQmbmJzcDtYUiZuYnNwO0Jsb2Nr
Jm5ic3A7ZGVmaW5lZCZuYnNwO2luJm5ic3A7dGhpcyZuYnNwO2RyYWZ0Jm5ic3A7aXMmbmJzcDtT
dGF0aXN0aWNzJm5ic3A7U3VtbWFyeSZuYnNwO0Jsb2NrJm5ic3A7Zm9yIA0KICA8L0ZPTlQ+PC9E
SVY+DQogIDxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+PEZPTlQgDQogIHNpemU9Mz4mbmJz
cDtBcHBsaWNhdGlvbiZuYnNwO0xheWVyJm5ic3A7TG9zcy9EdXBsaWNhdGlvbi4mbmJzcDtJJm5i
c3A7dGhpbmsmbmJzcDt0aGlzJm5ic3A7WFImbmJzcDtCbG9jayZuYnNwO2lzJm5ic3A7bGlua2Vk
Jm5ic3A7dG8mbmJzcDtJL1AvQiZuYnNwO2ZyYW1lJm5ic3A7c3RhdGlzdGljcy4gDQogIDwvRk9O
VD48L0RJVj4NCiAgPERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCANCiAgc2l6ZT0z
PlRoaXMmbmJzcDttZXRyaWMmbmJzcDtibG9ja3MmbmJzcDtjYW4mbmJzcDt0ZWxsJm5ic3A7dXMm
bmJzcDt3aGljaCZuYnNwO2ZyYW1lJm5ic3A7dHlwZXMmbmJzcDt3ZXJlJm5ic3A7YWZmZWN0ZWQm
bmJzcDthbmQmbmJzcDtpcyZuYnNwO3RoZXJlZm9yZSZuYnNwO2EmbmJzcDt1c2VmdWwmbmJzcDtt
ZXRyaWMgDQogIDwvRk9OVD48L0RJVj4NCiAgPERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48
Rk9OVCANCiAgc2l6ZT0zPiZuYnNwO3RvJm5ic3A7Zm9ybSZuYnNwO2FuJm5ic3A7YWNjdXJhdGUm
bmJzcDthc3Nlc3NtZW50Jm5ic3A7b2YmbmJzcDt1c2VyJm5ic3A7cXVhbGl0eSZuYnNwO29mJm5i
c3A7ZXhwZXJpZW5jZS4mbmJzcDs8L0ZPTlQ+PC9ESVY+DQogIDxESVYgc3R5bGU9IkZPTlQtU0la
RTogMTlweCI+PEZPTlQgc2l6ZT0zPjwvRk9OVD4mbmJzcDs8L0RJVj48L0JMT0NLUVVPVEU+DQo8
RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiIGRpcj1sdHI+PEZPTlQgc2l6ZT0zPltRaW5dOiZu
YnNwOyANCkV4YWN0bHkuPC9GT05UPjwvRElWPg0KPEJMT0NLUVVPVEUgDQpzdHlsZT0iQk9SREVS
LUxFRlQ6ICMwMDAwMDAgMnB4IHNvbGlkOyBQQURESU5HLUxFRlQ6IDVweDsgUEFERElORy1SSUdI
VDogMHB4OyBNQVJHSU4tTEVGVDogNXB4OyBNQVJHSU4tUklHSFQ6IDBweCIgDQpkaXI9bHRyPg0K
ICA8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPjxGT05UIHNpemU9Mz48L0ZPTlQ+Jm5ic3A7
PC9ESVY+DQogIDxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+PEZPTlQgDQogIHNpemU9Mz5I
b3dldmVyJm5ic3A7aXQmbmJzcDtpcyZuYnNwO25vdCZuYnNwO2NsZWFyJm5ic3A7dG8mbmJzcDtt
ZSZuYnNwOyANCiAgPC9GT05UPjwvRElWPg0KICA8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5cHgi
PjxGT05UIA0KICBzaXplPTM+aG93Jm5ic3A7ZG8mbmJzcDt5b3UmbmJzcDtjYWxjdWxhdGUmbmJz
cDtOdW1iZXImbmJzcDtvZiZuYnNwO2ZyYW1lcyZuYnNwO2V4cGVjdGVkPzwvRk9OVD48L0RJVj4N
CiAgPERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCBzaXplPTM+PC9GT05UPiZuYnNw
OzwvRElWPjwvQkxPQ0tRVU9URT4NCjxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCIgZGlyPWx0
cj48Rk9OVCBzaXplPTM+W1Fpbl06Jm5ic3A7IFRoZSBtZXRyaWNzIHdlIA0KZGVmaW5lZCBpbiB0
aGlzIFhSIEJsb2NrIGlzIG5vdCBlYXN5IHRvIGJlIGNhcHR1cmVkLiBZb3Ugc2hvdWxkIGxvb2sg
aW50byBSVFAgDQpwYWNrZXQgb3IgZGVlcCBwYXJzZSBSVFAgcGFja2V0LjwvRk9OVD48L0RJVj4N
CjxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCIgZGlyPWx0cj48Rk9OVCBzaXplPTM+Rm9ydHVu
YXRlbHkgdGhlc2UgbWV0cmljcyANCnJlZmxlY3QgZW5kIHRvIGVuZCBwZXJmb3JtYW5jZSBhdCB0
aGUgc2VydmljZSBsZXZlbCBhbmQgdGhlcmVmb3JlIHdlIGNhbiBtZWFzdXJlIA0KdGhlbSBhdCB0
aGUgdXNlciBlbmQgcG9pbnQsIGUuZy4sIGZyb208L0ZPTlQ+PC9ESVY+DQo8RElWIHN0eWxlPSJG
T05ULVNJWkU6IDE5cHgiIGRpcj1sdHI+PEZPTlQgc2l6ZT0zPmRlY29kZXIgb3IgDQpkZW11eGVy
LjwvRk9OVD48L0RJVj4NCjxCTE9DS1FVT1RFIA0Kc3R5bGU9IkJPUkRFUi1MRUZUOiAjMDAwMDAw
IDJweCBzb2xpZDsgUEFERElORy1MRUZUOiA1cHg7IFBBRERJTkctUklHSFQ6IDBweDsgTUFSR0lO
LUxFRlQ6IDVweDsgTUFSR0lOLVJJR0hUOiAwcHgiIA0KZGlyPWx0cj4NCiAgPERJViBzdHlsZT0i
Rk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCANCiAgc2l6ZT0zPiZuYnNwO0lzbid0Jm5ic3A7bW9yZSZu
YnNwO2Vhc2llciZuYnNwO3RvJm5ic3A7Y2FsY3VsYXRlJm5ic3A7aG93Jm5ic3A7bWFueSZuYnNw
O2ZyYW1lcyZuYnNwO2FyZSZuYnNwO3JlY2VpdmVkIA0KICA8L0ZPTlQ+PC9ESVY+DQogIDxESVYg
c3R5bGU9IkZPTlQtU0laRTogMTlweCI+PEZPTlQgDQogIHNpemU9Mz5yYW50aGVyJm5ic3A7dGhh
biZuYnNwO2dhdGhlcmluZyZuYnNwO3RoZSZuYnNwO251bWJlciZuYnNwO29mJm5ic3A7ZnJhbWUm
bmJzcDtleHBlY3RlZD8gDQogIDwvRk9OVD48L0RJVj4NCiAgPERJViBzdHlsZT0iRk9OVC1TSVpF
OiAxOXB4Ij48Rk9OVCBzaXplPTM+PC9GT05UPiZuYnNwOzwvRElWPjwvQkxPQ0tRVU9URT4NCjxE
SVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCIgZGlyPWx0cj48Rk9OVCBzaXplPTM+W1Fpbl06IHlv
dXIgYXJlIHJpZ2h0LCBpZiB3ZSANCm1lYXN1cmUgdGhlc2UgbWV0cmljcyBhdCB0aGUgdXNlciBl
bmQgcG9pbnQsIGl0IGlzIG1vcmUgZWFzeSB0byBnYXRoZXIgdGhlIA0KbnVtYmVyIG9mIGZyYW1l
cyByZWNlaXZlZDwvRk9OVD48L0RJVj4NCjxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCIgZGly
PWx0cj48Rk9OVCBzaXplPTM+dGhhbiB0aGUgbnVtYmVyIG9mIGZyYW1lcyANCmV4cGVjdGVkIHNp
bmNlIGl0IGlzIGVhc3kgZm9yIHRoZSB1c2VyIGVuZCBwb2ludCB0byBrbm93IGhvdyBtYW55IGZy
YW1lcyANCnJlY2VpdmVkLiZuYnNwOyZuYnNwO0kgd2lsbCBmaXggdGhpcyBpbiB0aGUgdXBkYXRl
LjwvRk9OVD48L0RJVj4NCjxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCIgZGlyPWx0cj48Rk9O
VCBzaXplPTM+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4
OyBNQVJHSU4tUklHSFQ6IDBweCIgZGlyPWx0cj48Rk9OVCANCnNpemU9Mz4mZ3Q7QW5vdGhlciZu
YnNwO2NvbW1lbnQmbmJzcDtpcyZuYnNwO2lzbid0Jm5ic3A7aXQmbmJzcDt1c2VmdWwmbmJzcDt0
byZuYnNwO2NvbGxlY3QmbmJzcDtob3cmbmJzcDttYW55Jm5ic3A7ZGlmZmVyZW50Jm5ic3A7dHlw
ZSZuYnNwO29mJm5ic3A7ZnJhbWVzJm5ic3A7d2VyZSZuYnNwO2Rpc2NhcmRlZCZuYnNwOyANCjwv
Rk9OVD48Rk9OVCBzaXplPTM+YnkmbmJzcDt0aGUmbmJzcDttZWRpYSZuYnNwO3JlY2lldmVyPyA8
L0ZPTlQ+PC9ESVY+DQo8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiIGRpcj1sdHI+PEZPTlQg
c2l6ZT0zPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCIg
ZGlyPWx0cj48Rk9OVCBzaXplPTM+W1Fpbl06Jm5ic3A7VGhhdCdzJm5ic3A7YSBnb29kIA0KcG9p
bnQuIEJ1dCB0aGlzIGlzIG9ubHkgdXNlZnVsIGluIHRoZSBjYXNlIHdoZXJlIG9ubHkgdGhlIHJl
Y2VpdmVyIGlzIGFsbG93ZWQgdG8gDQpkaXNjYXJkIGltcGFpcmVkIGZyYW1lcy48L0ZPTlQ+PC9E
SVY+DQo8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiIGRpcj1sdHI+PEZPTlQgc2l6ZT0zPkkg
cHJvcG9zZSB0byBhZGQgdGhpcyBtZXRyaWMgDQppbnRvIHRoZSBuZXcgdmVyc2lvbi4gVGhhbmtz
LjwvRk9OVD48L0RJVj4NCjxCTE9DS1FVT1RFIA0Kc3R5bGU9IkJPUkRFUi1MRUZUOiAjMDAwMDAw
IDJweCBzb2xpZDsgUEFERElORy1MRUZUOiA1cHg7IFBBRERJTkctUklHSFQ6IDBweDsgTUFSR0lO
LUxFRlQ6IDVweDsgTUFSR0lOLVJJR0hUOiAwcHgiIA0KZGlyPWx0cj4NCiAgPERJViBzdHlsZT0i
Rk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCBzaXplPTM+Q2hlZXJzISA8L0ZPTlQ+PC9ESVY+DQogIDxE
SVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+PEZPTlQgc2l6ZT0zPlpoYW9KaW5nIDwvRk9OVD48
L0RJVj4NCiAgPERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCBzaXplPTM+LS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLSANCiAgPC9GT05UPjwvRElWPg0KICA8RElWIHN0eWxlPSJG
T05ULVNJWkU6IDE5cHgiPjxGT05UIA0KICBzaXplPTM+LS0tLS0mbmJzcDtPcmlnaW5hbCZuYnNw
O01lc3NhZ2UmbmJzcDstLS0tLSZuYnNwOyA8L0ZPTlQ+PC9ESVY+DQogIDxESVYgc3R5bGU9IkZP
TlQtU0laRTogMTlweCI+PEZPTlQgDQogIHNpemU9Mz5Gcm9tOiZuYnNwOyJRaW4mbmJzcDtXdSIm
bmJzcDsmbHQ7YmlsbC53dUBodWF3ZWkuY29tJmd0OyA8L0ZPTlQ+PC9ESVY+DQogIDxESVYgc3R5
bGU9IkZPTlQtU0laRTogMTlweCI+PEZPTlQgc2l6ZT0zPlRvOiZuYnNwOyZsdDt4cmJsb2NrQGll
dGYub3JnJmd0OyANCiAgPC9GT05UPjwvRElWPg0KICA8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5
cHgiPjxGT05UIA0KICBzaXplPTM+U2VudDombmJzcDtUaHVyc2RheSwmbmJzcDtKYW51YXJ5Jm5i
c3A7MTksJm5ic3A7MjAxMiZuYnNwOzQ6NDAmbmJzcDtQTSANCiAgPC9GT05UPjwvRElWPg0KICA8
RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPjxGT05UIA0KICBzaXplPTM+U3ViamVjdDombmJz
cDtSZTombmJzcDtbeHJibG9ja10mbmJzcDtJLUQmbmJzcDtBY3Rpb246Jm5ic3A7ZHJhZnQtem9y
bi14cmJsb2NrLXJ0Y3AteHItYWwtc3RhdC0wNC50eHQgDQogIDwvRk9OVD48L0RJVj4NCiAgPERJ
ViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCBzaXplPTM+IDwvRk9OVD48L0RJVj4NCiAg
PERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCBzaXplPTM+IDwvRk9OVD48L0RJVj4N
CiAgPERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCBzaXplPTM+Jmd0OyZuYnNwO0hp
LCA8L0ZPTlQ+PC9ESVY+DQogIDxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+PEZPTlQgDQog
IHNpemU9Mz4mZ3Q7Jm5ic3A7QSZuYnNwO21pbm9yJm5ic3A7dXBkYXRlJm5ic3A7dG8mbmJzcDtk
cmFmdC16b3JuLXhyYmxvY2stcnRjcC14ci1hbC1zdGF0Jm5ic3A7d2hpY2gmbmJzcDtpcyZuYnNw
O3VzZWQmbmJzcDt0byZuYnNwO2dldCZuYnNwO2NvbnNpc3RlbnQmbmJzcDt3aXRoJm5ic3A7QnVy
c3QmbmJzcDtHYXAmbmJzcDtyZWxhdGVkJm5ic3A7ZHJhZnQuIA0KICA8L0ZPTlQ+PC9ESVY+DQog
IDxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+PEZPTlQgDQogIHNpemU9Mz4mZ3Q7Jm5ic3A7
VGhpcyZuYnNwO2RyYWZ0Jm5ic3A7bWlzc2VkJm5ic3A7dGhlJm5ic3A7ZGlzY3Vzc2lvbiZuYnNw
O2R1ZSZuYnNwO3RvJm5ic3A7cHJlc2VudGF0aW9uJm5ic3A7dGltZW91dCZuYnNwOyZuYnNwO2lu
Jm5ic3A7dGhlJm5ic3A7bGFzdCZuYnNwO0lFVEYmbmJzcDttZWV0aW5nLiZuYnNwO0hvd2V2ZXIm
bmJzcDt0aGlzJm5ic3A7ZHJhZnQmbmJzcDtwcm92aWRlcyZuYnNwO2NhbGN1bGF0aW9uJm5ic3A7
bWV0aG9kIA0KICA8L0ZPTlQ+PC9ESVY+DQogIDxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+
PEZPTlQgDQogIHNpemU9Mz4mZ3Q7Jm5ic3A7Zm9yJm5ic3A7dGhlJm5ic3A7ZGVyaXZlZCZuYnNw
O21ldHJpYyZuYnNwO2xpc3RlZCZuYnNwO2luJm5ic3A7dGhlJm5ic3A7dHdvJm5ic3A7YnVyc3Qm
bmJzcDtnYXAmbmJzcDtyZWxhdGVkJm5ic3A7ZHJhZnQmbmJzcDthbmQmbmJzcDthbHNvJm5ic3A7
ZGVmaW5lcyZuYnNwO1JUQ1AmbmJzcDtYUiZuYnNwO3BhY2tldCZuYnNwO2Zvcm1hdCZuYnNwO3Rv
Jm5ic3A7Y2FycnkmbmJzcDt0aGVzZSZuYnNwO2Rlcml2ZWQmbmJzcDsgDQogIDwvRk9OVD48L0RJ
Vj4NCiAgPERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCBzaXplPTM+Jmd0OyZuYnNw
O21ldHJpYy4gPC9GT05UPjwvRElWPg0KICA8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPjxG
T05UIA0KICBzaXplPTM+Jmd0OyZuYnNwO0kmbmJzcDtsaWtlJm5ic3A7dG8mbmJzcDtzZWUmbmJz
cDtXRyZuYnNwO2Fkb3B0Jm5ic3A7dGhpcyZuYnNwO2RyYWZ0Jm5ic3A7YXMmbmJzcDt3b3JrJm5i
c3A7aXRlbSZuYnNwO29yJm5ic3A7YWRvcHQmbmJzcDthJm5ic3A7bWlsZXN0b25lJm5ic3A7dG8m
bmJzcDtsaW5rJm5ic3A7dG8mbmJzcDt0aGlzJm5ic3A7ZHJhZnQuJm5ic3A7IA0KICA8L0ZPTlQ+
PC9ESVY+DQogIDxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+PEZPTlQgDQogIHNpemU9Mz4m
Z3Q7Jm5ic3A7QW55Jm5ic3A7cmV2aWV3Jm5ic3A7YW5kJm5ic3A7Y29tbWVudHMmbmJzcDthcmUm
bmJzcDt3ZWxjb21lLiANCiAgPC9GT05UPjwvRElWPg0KICA8RElWIHN0eWxlPSJGT05ULVNJWkU6
IDE5cHgiPjxGT05UIHNpemU9Mz4mZ3Q7Jm5ic3A7IDwvRk9OVD48L0RJVj4NCiAgPERJViBzdHls
ZT0iRk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCBzaXplPTM+Jmd0OyZuYnNwO1JlZ2FyZHMhIDwvRk9O
VD48L0RJVj4NCiAgPERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCBzaXplPTM+Jmd0
OyZuYnNwOy1RaW4gPC9GT05UPjwvRElWPg0KICA8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5cHgi
PjxGT05UIA0KICBzaXplPTM+Jmd0OyZuYnNwOy0tLS0tJm5ic3A7T3JpZ2luYWwmbmJzcDtNZXNz
YWdlJm5ic3A7LS0tLS0mbmJzcDsgDQogIDwvRk9OVD48L0RJVj4NCiAgPERJViBzdHlsZT0iRk9O
VC1TSVpFOiAxOXB4Ij48Rk9OVCANCiAgc2l6ZT0zPiZndDsmbmJzcDtGcm9tOiZuYnNwOyZsdDtp
bnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcmZ3Q7IDwvRk9OVD48L0RJVj4NCiAgPERJViBzdHlsZT0i
Rk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCANCiAgc2l6ZT0zPiZndDsmbmJzcDtUbzombmJzcDsmbHQ7
aS1kLWFubm91bmNlQGlldGYub3JnJmd0OyA8L0ZPTlQ+PC9ESVY+DQogIDxESVYgc3R5bGU9IkZP
TlQtU0laRTogMTlweCI+PEZPTlQgDQogIHNpemU9Mz4mZ3Q7Jm5ic3A7U2VudDombmJzcDtUaHVy
c2RheSwmbmJzcDtKYW51YXJ5Jm5ic3A7MTksJm5ic3A7MjAxMiZuYnNwOzM6MDQmbmJzcDtQTSAN
CiAgPC9GT05UPjwvRElWPg0KICA8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPjxGT05UIA0K
ICBzaXplPTM+Jmd0OyZuYnNwO1N1YmplY3Q6Jm5ic3A7SS1EJm5ic3A7QWN0aW9uOiZuYnNwO2Ry
YWZ0LXpvcm4teHJibG9jay1ydGNwLXhyLWFsLXN0YXQtMDQudHh0IA0KICA8L0ZPTlQ+PC9ESVY+
DQogIDxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+PEZPTlQgc2l6ZT0zPiZndDsmbmJzcDsg
PC9GT05UPjwvRElWPg0KICA8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPjxGT05UIHNpemU9
Mz4mZ3Q7Jm5ic3A7IDwvRk9OVD48L0RJVj4NCiAgPERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4
Ij48Rk9OVCBzaXplPTM+Jmd0OyZndDsmbmJzcDsgPC9GT05UPjwvRElWPg0KICA8RElWIHN0eWxl
PSJGT05ULVNJWkU6IDE5cHgiPjxGT05UIA0KICBzaXplPTM+Jmd0OyZndDsmbmJzcDtBJm5ic3A7
TmV3Jm5ic3A7SW50ZXJuZXQtRHJhZnQmbmJzcDtpcyZuYnNwO2F2YWlsYWJsZSZuYnNwO2Zyb20m
bmJzcDt0aGUmbmJzcDtvbi1saW5lJm5ic3A7SW50ZXJuZXQtRHJhZnRzJm5ic3A7ZGlyZWN0b3Jp
ZXMuIA0KICA8L0ZPTlQ+PC9ESVY+DQogIDxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+PEZP
TlQgc2l6ZT0zPiZndDsmZ3Q7Jm5ic3A7IDwvRk9OVD48L0RJVj4NCiAgPERJViBzdHlsZT0iRk9O
VC1TSVpFOiAxOXB4Ij48Rk9OVCANCiAgc2l6ZT0zPiZndDsmZ3Q7Jm5ic3A7VGl0bGUmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDs6Jm5ic3A7UlRDUCZuYnNwO1hSJm5ic3A7Zm9yJm5ic3A7U3VtbWFyeSZuYnNwO1N0YXRpc3Rp
Y3MmbmJzcDtNZXRyaWNzJm5ic3A7UmVwb3J0aW5nIA0KICA8L0ZPTlQ+PC9ESVY+DQogIDxESVYg
c3R5bGU9IkZPTlQtU0laRTogMTlweCI+PEZPTlQgDQogIHNpemU9Mz4mZ3Q7Jmd0OyZuYnNwO0F1
dGhvcihzKSZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzombmJzcDtH
bGVuJm5ic3A7Wm9ybiANCiAgPC9GT05UPjwvRElWPg0KICA8RElWIHN0eWxlPSJGT05ULVNJWkU6
IDE5cHgiPjxGT05UIA0KICBzaXplPTM+Jmd0OyZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDtSb2xhbmQmbmJzcDtTY2hvdHQgDQogIDwvRk9OVD48L0RJVj4NCiAg
PERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCANCiAgc2l6ZT0zPiZndDsmZ3Q7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7UWluJm5ic3A7V3UgDQogIDwv
Rk9OVD48L0RJVj4NCiAgPERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCANCiAgc2l6
ZT0zPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7UmFj
aGVsJm5ic3A7SHVhbmcgDQogIDwvRk9OVD48L0RJVj4NCiAgPERJViBzdHlsZT0iRk9OVC1TSVpF
OiAxOXB4Ij48Rk9OVCANCiAgc2l6ZT0zPiZndDsmZ3Q7Jm5ic3A7RmlsZW5hbWUmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDs6Jm5ic3A7ZHJhZnQtem9ybi14
cmJsb2NrLXJ0Y3AteHItYWwtc3RhdC0wNC50eHQgDQogIDwvRk9OVD48L0RJVj4NCiAgPERJViBz
dHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCANCiAgc2l6ZT0zPiZndDsmZ3Q7Jm5ic3A7UGFn
ZXMmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDs6Jm5ic3A7MTUgDQogIDwvRk9OVD48L0RJVj4NCiAgPERJViBzdHlsZT0iRk9O
VC1TSVpFOiAxOXB4Ij48Rk9OVCANCiAgc2l6ZT0zPiZndDsmZ3Q7Jm5ic3A7RGF0ZSZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOzombmJzcDsyMDEyLTAxLTE4IA0KICA8L0ZPTlQ+PC9ESVY+DQogIDxESVYgc3R5bGU9
IkZPTlQtU0laRTogMTlweCI+PEZPTlQgc2l6ZT0zPiZndDsmZ3Q7Jm5ic3A7IDwvRk9OVD48L0RJ
Vj4NCiAgPERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCANCiAgc2l6ZT0zPiZndDsm
Z3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7VGhpcyZuYnNwO2RvY3VtZW50Jm5ic3A7ZGVmaW5lcyZuYnNw
O3RocmVlJm5ic3A7UlRDUCZuYnNwO1hSJm5ic3A7UmVwb3J0Jm5ic3A7QmxvY2tzJm5ic3A7YW5k
Jm5ic3A7YXNzb2NpYXRlZCZuYnNwO1NEUCANCiAgPC9GT05UPjwvRElWPg0KICA8RElWIHN0eWxl
PSJGT05ULVNJWkU6IDE5cHgiPjxGT05UIA0KICBzaXplPTM+Jmd0OyZndDsmbmJzcDsmbmJzcDsm
bmJzcDtwYXJhbWV0ZXJzJm5ic3A7dGhhdCZuYnNwO2FsbG93cyZuYnNwO3RoZSZuYnNwO3JlcG9y
dGluZyZuYnNwO29mJm5ic3A7bG9zcywmbmJzcDtkdXBsaWNhdGlvbiZuYnNwO2FuZCZuYnNwO2Rp
c2NhcmQgDQogIDwvRk9OVD48L0RJVj4NCiAgPERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48
Rk9OVCANCiAgc2l6ZT0zPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7c3VtbWFyeSZuYnNwO3N0
YXRpc3RpY3MmbmJzcDttZXRyaWNzJm5ic3A7Zm9yJm5ic3A7dXNlJm5ic3A7aW4mbmJzcDthJm5i
c3A7cmFuZ2UmbmJzcDtvZiZuYnNwO1JUUCZuYnNwO2FwcGxpY2F0aW9ucy4gDQogIDwvRk9OVD48
L0RJVj4NCiAgPERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCBzaXplPTM+Jmd0OyZn
dDsmbmJzcDsgPC9GT05UPjwvRElWPg0KICA8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPjxG
T05UIHNpemU9Mz4mZ3Q7Jmd0OyZuYnNwOyA8L0ZPTlQ+PC9ESVY+DQogIDxESVYgc3R5bGU9IkZP
TlQtU0laRTogMTlweCI+PEZPTlQgDQogIHNpemU9Mz4mZ3Q7Jmd0OyZuYnNwO0EmbmJzcDtVUkwm
bmJzcDtmb3ImbmJzcDt0aGlzJm5ic3A7SW50ZXJuZXQtRHJhZnQmbmJzcDtpczogDQogIDwvRk9O
VD48L0RJVj4NCiAgPERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCBzaXplPTM+Jmd0
OyZndDsgPC9GT05UPjxBIA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxOHB4IiANCiAgaHJlZj0iaHR0
cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtem9ybi14cmJsb2NrLXJ0Y3At
eHItYWwtc3RhdC0wNC50eHQiPjxGT05UIA0KICBzaXplPTM+aHR0cDovL3d3dy5pZXRmLm9yZy9p
bnRlcm5ldC1kcmFmdHMvZHJhZnQtem9ybi14cmJsb2NrLXJ0Y3AteHItYWwtc3RhdC0wNC50eHQ8
L0ZPTlQ+PC9BPjxGT05UIA0KICBzaXplPTM+IDwvRk9OVD48L0RJVj4NCiAgPERJViBzdHlsZT0i
Rk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCBzaXplPTM+Jmd0OyZndDsmbmJzcDsgPC9GT05UPjwvRElW
Pg0KICA8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPjxGT05UIA0KICBzaXplPTM+Jmd0OyZn
dDsmbmJzcDtJbnRlcm5ldC1EcmFmdHMmbmJzcDthcmUmbmJzcDthbHNvJm5ic3A7YXZhaWxhYmxl
Jm5ic3A7YnkmbmJzcDthbm9ueW1vdXMmbmJzcDtGVFAmbmJzcDthdDogDQogIDwvRk9OVD48L0RJ
Vj4NCiAgPERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCANCiAgc2l6ZT0zPiZndDsm
Z3Q7Jm5ic3A7ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy8gPC9GT05UPjwvRElW
Pg0KICA8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPjxGT05UIHNpemU9Mz4mZ3Q7Jmd0OyZu
YnNwOyA8L0ZPTlQ+PC9ESVY+DQogIDxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+PEZPTlQg
DQogIHNpemU9Mz4mZ3Q7Jmd0OyZuYnNwO1RoaXMmbmJzcDtJbnRlcm5ldC1EcmFmdCZuYnNwO2Nh
biZuYnNwO2JlJm5ic3A7cmV0cmlldmVkJm5ic3A7YXQ6IA0KICA8L0ZPTlQ+PC9ESVY+DQogIDxE
SVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+PEZPTlQgDQogIHNpemU9Mz4mZ3Q7Jmd0OyZuYnNw
O2Z0cDovL2Z0cC5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtem9ybi14cmJsb2NrLXJ0
Y3AteHItYWwtc3RhdC0wNC50eHQgDQogIDwvRk9OVD48L0RJVj4NCiAgPERJViBzdHlsZT0iRk9O
VC1TSVpFOiAxOXB4Ij48Rk9OVCBzaXplPTM+Jmd0OyZndDsmbmJzcDsgPC9GT05UPjwvRElWPg0K
ICA8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPjxGT05UIA0KICBzaXplPTM+Jmd0OyZndDsm
bmJzcDtfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXyANCiAg
PC9GT05UPjwvRElWPg0KICA8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPjxGT05UIA0KICBz
aXplPTM+Jmd0OyZndDsmbmJzcDtJLUQtQW5ub3VuY2UmbmJzcDttYWlsaW5nJm5ic3A7bGlzdCA8
L0ZPTlQ+PC9ESVY+DQogIDxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+PEZPTlQgc2l6ZT0z
PiZndDsmZ3Q7Jm5ic3A7SS1ELUFubm91bmNlQGlldGYub3JnIA0KICA8L0ZPTlQ+PC9ESVY+DQog
IDxESVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+PEZPTlQgc2l6ZT0zPiZndDsmZ3Q7IDwvRk9O
VD48QSANCiAgc3R5bGU9IkZPTlQtU0laRTogMThweCIgDQogIGhyZWY9Imh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vaS1kLWFubm91bmNlIj48Rk9OVCANCiAgc2l6ZT0zPmh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaS1kLWFubm91bmNlPC9GT05UPjwv
QT48Rk9OVCANCiAgc2l6ZT0zPiA8L0ZPTlQ+PC9ESVY+DQogIDxESVYgc3R5bGU9IkZPTlQtU0la
RTogMTlweCI+PEZPTlQgc2l6ZT0zPiZndDsmZ3Q7IEludGVybmV0LURyYWZ0IGRpcmVjdG9yaWVz
OiANCiAgPC9GT05UPjxBIHN0eWxlPSJGT05ULVNJWkU6IDE4cHgiIGhyZWY9Imh0dHA6Ly93d3cu
aWV0Zi5vcmcvc2hhZG93Lmh0bWwiPjxGT05UIA0KICBzaXplPTM+aHR0cDovL3d3dy5pZXRmLm9y
Zy9zaGFkb3cuaHRtbDwvRk9OVD48L0E+PEZPTlQgc2l6ZT0zPiA8L0ZPTlQ+PC9ESVY+DQogIDxE
SVYgc3R5bGU9IkZPTlQtU0laRTogMTlweCI+PEZPTlQgDQogIHNpemU9Mz4mZ3Q7Jmd0OyZuYnNw
O29yJm5ic3A7ZnRwOi8vZnRwLmlldGYub3JnL2lldGYvMXNoYWRvdy1zaXRlcy50eHQgDQogIDwv
Rk9OVD48L0RJVj4NCiAgPERJViBzdHlsZT0iRk9OVC1TSVpFOiAxOXB4Ij48Rk9OVCBzaXplPTM+
Jmd0OyZndDsgPC9GT05UPjwvRElWPg0KICA8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPjxG
T05UIA0KICBzaXplPTM+Jmd0OyZuYnNwO19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fIDwvRk9OVD48L0RJVj4NCiAgPERJViBzdHlsZT0iRk9OVC1TSVpFOiAx
OXB4Ij48Rk9OVCANCiAgc2l6ZT0zPiZndDsmbmJzcDt4cmJsb2NrJm5ic3A7bWFpbGluZyZuYnNw
O2xpc3QgPC9GT05UPjwvRElWPg0KICA8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPjxGT05U
IHNpemU9Mz4mZ3Q7Jm5ic3A7eHJibG9ja0BpZXRmLm9yZyANCiAgPC9GT05UPjwvRElWPg0KICA8
RElWIHN0eWxlPSJGT05ULVNJWkU6IDE5cHgiPjxGT05UIHNpemU9Mz4mZ3Q7IDwvRk9OVD48QSAN
CiAgc3R5bGU9IkZPTlQtU0laRTogMThweCIgDQogIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3Jn
L21haWxtYW4vbGlzdGluZm8veHJibG9jayI+PEZPTlQgDQogIHNpemU9Mz5odHRwczovL3d3dy5p
ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3hyYmxvY2s8L0ZPTlQ+PC9BPjxGT05UIHNpemU9Mz4g
DQogIDwvRk9OVD48L0RJVj48L0JMT0NLUVVPVEU+PC9CT0RZPjwvSFRNTD4NCg==

--Boundary_(ID_JXFhwqz/Dy6Be6a1mKYXpA)--
