
From nobody Mon Oct  2 14:28:16 2017
Return-Path: <ben@nostrum.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 0AA551348D8; Mon,  2 Oct 2017 14:28:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j8uFEPEEYmw1; Mon,  2 Oct 2017 14:28:13 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 413F21348D6; Mon,  2 Oct 2017 14:28:10 -0700 (PDT)
Received: from [10.0.1.82] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v92LS879000827 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 2 Oct 2017 16:28:09 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.82]
From: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_0AA2513A-9F3C-499D-9657-61A48E9A88B4"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Message-Id: <99303AB6-D5EE-44EC-B515-DCB7966DADA6@nostrum.com>
Date: Mon, 2 Oct 2017 16:28:07 -0500
To: draft-ietf-xrblock-rtcweb-rtcp-xr-metrics.all@ietf.org, xrblock@ietf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xrblock/pKAGOeHlo_v6vbQXKlZuCDpFQ8E>
Subject: [xrblock] AD Evaluation of draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-06
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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 Oct 2017 21:28:15 -0000

--Apple-Mail=_0AA2513A-9F3C-499D-9657-61A48E9A88B4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

This is my AD Evaluation of =
draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-06. I would like to resolve at =
least the substantive comments prior to IETF LC.

Thanks!

Ben.
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=
=80=94

Substantive:

- General: If I understand correctly, this document lists and describes =
XR metrics that a WebRTC application might choose to negotiate and =
expose via the WebRTC API. It does not define any new XR metrics. That =
brings up two questions:

1) Why is this specific to WebRTC? For the most parts, all the arguments =
here would apply to any sort of RTP endpoint.

2) Why is this standards track? This sort of material is typically =
informational, or occasionally a BCP. There are a small number of 2119 =
keywords, but I=E2=80=99m not sure they are needed or appropriate. =
(Specifics below.) My initial instinct is that this should be =
informational.

- General: This needs an IANA considerations section, even if it just =
contains the statement to the effect of =E2=80=9CThis document makes no =
requests for IANA=E2=80=9D.

- 1, last paragraph: =E2=80=9C The document also creates a registry =
containing identifiers from the metrics reported in the RTCP Sender, =
Receiver, and Extended Reports.=E2=80=9D

It doesn=E2=80=99t actually do that. I understand from the shepherd=E2=80=99=
s report that this was intentionally removed.

=E2=80=94 =E2=80=9CAll identifiers proposed in this document are =
RECOMMENDED to be implemented by an endpoint.  An endpoint MAY choose =
not to expose an identifier if it does not implement the corresponding =
RTCP Report. =E2=80=9C

Does the =E2=80=9CRECOMMENDED=E2=80=9D apply to all endpoints or just =
WebRTC endpoints? If the latter, doesn=E2=80=99t that requirement belong =
(or need to update) some requirement from an RTCWEB (maybe rtp-usage) =
document, or even the API itself? (I suspect that this draft does not =
have standing to state this normatively.) What is meant by =E2=80=9CMAY =
choose not to expose=E2=80=9D. Is that talking about via the WebRTC API? =
If so, isn=E2=80=99t that up to the API definition? (That is, it =
shouldn=E2=80=99t be normative here.)

-2: If this document keeps the normative keywords, please use the =
updated boilerplate from RFC 8174. (I note that there are at least some =
uncapitalized =E2=80=9Cmay=E2=80=9Ds that do not seem normative.)

- 5.2.2, last paragraph: =E2=80=9CThe following metrics can also be =
considered=E2=80=A6=E2=80=9D
Be considered by whom? Implementors? API designers?

- 6, first paragraph: =E2=80=9CIn practice the application MUST be able =
to query the statistic identifiers on both an incoming (remote) and =
outgoing (local) media stream.=E2=80=9D
What does the MUST requirement apply to? The WebRTC API? This seems more =
like a statement of fact that =E2=80=9C the application needs to be =
able=E2=80=A6=E2=80=9D

-8: "Therefore encryption procedures, such as the ones suggested for a =
Secure RTCP (SRTCP), need to be used.=E2=80=9D
The text should describe the reasons encryption is needed. Also, is this =
a new normative requirement, or a restatement of an existing =
requirement?

Editorial:

-1, paragraph 1:" If sufficient information (metrics or statistics) are =
provided to the applications, it can attempt to improve the media =
quality. =E2=80=9C

s / =E2=80=9Care provided=E2=80=9D / =E2=80=9Cis provided=E2=80=9D
s / applications / application

-3, 2nd paragraph: It would help to clarify that the references to =
section 5 and 6 are to this document, not RFC 3611.

=E2=80=94 3rd paragraph: "At the moment=E2=80=A6=E2=80=9D
Please clarify that is at the time of writing (not reading)

-5, 2nd paragraph: =E2=80=9C Application impact metrics mainly collect =
the information in the viewpoint of application =E2=80=A6 =E2=80=9C
s / in / from
Also, please expand =E2=80=9CFEC=E2=80=9D on first mention.

- 5.1.1, first paragraph: =E2=80=9C Duplicate packets may be a result of =
network delays, which causes the sender to retransmit the original =
packets.=E2=80=9D
s/ :delays, which=E2=80=9D / =E2=80=9Cdelays that=E2=80=9D

=E2=80=94 last paragraph: "For those RTCWEB services with jitter =
buffer=E2=80=A6=E2=80=9D
s/buffer/buffers

- 5.1.2, first paragraph:
First sentence is a comma splice.
 =E2=80=94 =E2=80=9Csome transitory nature of the impairments=E2=80=9D
Should this say =E2=80=9Cthe transitory nature of some impairments=E2=80=9D=
?
=E2=80=94 =E2=80=9C Distributed burst provides a higher subjective =
quality=E2=80=9D
=E2=80=9CBurst distribution =E2=80=A6=E2=80=9D?
=E2=80=94 Last paragraph: =E2=80=9C Hence, if WebRTC application=E2=80=9D
Missing article (or should application be plural?)

- 5.2.1, title: Should =E2=80=9CDiscard=E2=80=9D be =E2=80=9CDiscarded=E2=80=
=9D?

-7: Please clarify that this is at the time of this writing.










--Apple-Mail=_0AA2513A-9F3C-499D-9657-61A48E9A88B4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJZ0q9oAAoJEIBWSmyV89QN7EMQAJRa7eB9+FOqxLUckmtpJeFb
8EM3KnDMv5EyXpTnWP6+Xi2UGyjBk0WHQWoCHjJQThwGDwaN70yu+feAAV1CFJex
zg7gFBC+QNMUQbedk7X8RupphCR6q5SyjCCkbwbx9YGBxN+qKtRGPyPowrKjzVKU
ZkVJxLFYqS+0CTImFu1ore6mcZu3dTNx67DSJV2adf08PMYBJm2YDJbLdilvvQlL
rTNeNlaQX98Hx8meRlujU0txnaI5Z61D1gleM9fpqBoJiQk7nsyndowRvNrmO614
XsBqslsCWUMIa5IxDE9yrzVvPqUQJ7NDojyXhUcrBMLX2PfHia9A1JSR3QizWOMw
4fj7KlQal4Lx8y+Ia4cS11XfxaCTxmBNOcBBm2l72CmHi1p59sUw2mGXOQ17McWS
4tMcoaVFuxM1aBY44uHH6+5R+jyXyAVoMTYfCACEkI3GxzRlIWGieO2dVZlNEUyL
O/A5f1L6xGuLnd28WI9KZ/OTZkeiOlnTh0/VMb/7UsOCpr0jLtO2yfTEJ76tcmfp
xRp26MSewMAFMaOa915YeVvUjC5vOhfrOqwkO796syfBPD70hUWaFN0m+iUhyjHc
yfmWnPvZSXApIuX52RKSyJLflM2P20tSalEy3Gnz49oXFmAkElCZZY3bY46LTR32
Q4KSs+5FIxOk5o3XN977
=utyA
-----END PGP SIGNATURE-----

--Apple-Mail=_0AA2513A-9F3C-499D-9657-61A48E9A88B4--


From nobody Sun Oct  8 06:11:36 2017
Return-Path: <varun@callstats.io>
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 9BC581342C2 for <xrblock@ietfa.amsl.com>; Sun,  8 Oct 2017 06:11:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=callstats.io
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dqNovcsno41T for <xrblock@ietfa.amsl.com>; Sun,  8 Oct 2017 06:11:31 -0700 (PDT)
Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BDA3134226 for <xrblock@ietf.org>; Sun,  8 Oct 2017 06:11:31 -0700 (PDT)
Received: by mail-lf0-x233.google.com with SMTP id l23so17787147lfk.10 for <xrblock@ietf.org>; Sun, 08 Oct 2017 06:11:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=callstats.io; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=Lfe8DyFg05RL/W7rNX2K6wUb6Ck36MZlXzFgjobwdYU=; b=ej51b/H+idy86KOw4mCqkS6YYELbpQr8s73yTPHWni67+9Xmkiq8sx/t1DWThFnnRi prpuWnr/JnsLclvud9WcrToJ7qk2u5nM839HXl8LgSahs3pfsh/UlgCgpOZV/NazEwtJ ZbN7Yd953Mgm5hj8lpgedcH6Asoq6WyO40tCQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Lfe8DyFg05RL/W7rNX2K6wUb6Ck36MZlXzFgjobwdYU=; b=h1bTZDY1c/cGm7mMpPbzRCHNtRriifz6/BLhDfE81xMSZQ8OggYPij6DDV+b7Pb19y fySYczdF44DsV+ht1ONktlTVudFtNmazUAD+s1KtGbJQS16HFYNWQhzcv1RaZLu4MxyR dNKNI6eLyrmh3TypYRo4iQo+YZ35OsAIhtQdy+hlnlD829Wl9j/rYRf/bKVOqaZDGra9 rkkj947XpQaOmXug2Ge1MjE8AkoJFmXxD0fjgjiv2m/qDBy0nVMBiO8JKnRyEuXkwVDU 4zQJcArobqUoo3XQR17gmRgcuieuiDy/VpVAaFGfoAxOwrq0qAl2cUKNaYSmY0pR2md4 Ff/w==
X-Gm-Message-State: AMCzsaWJtIpMUBujectMQjzT0cPeYg9H/I1tTfY1oX0QHcuN+98PHj2y IzM0OHcQz5bMPj8OuZEzO8FjD1/lsVLYhdHkdnmncw==
X-Google-Smtp-Source: AOwi7QCHxC5muOlIOvjwMkbl4RlpFCU5M39RejAyAO565MaV+9rXq4l4qw1PJpIOnEttHvturA9lDHkNvGy+Ae1FzIM=
X-Received: by 10.46.4.153 with SMTP id a25mr3390939ljf.4.1507468289315; Sun, 08 Oct 2017 06:11:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.33.10 with HTTP; Sun, 8 Oct 2017 06:11:08 -0700 (PDT)
In-Reply-To: <99303AB6-D5EE-44EC-B515-DCB7966DADA6@nostrum.com>
References: <99303AB6-D5EE-44EC-B515-DCB7966DADA6@nostrum.com>
From: Varun Singh <varun@callstats.io>
Date: Sun, 8 Oct 2017 06:11:08 -0700
Message-ID: <CACHXSv7E+NhU_dvd63k57RfrVOAPoSFuOK8+-bRwsJTAcZ_ixQ@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Cc: draft-ietf-xrblock-rtcweb-rtcp-xr-metrics.all@ietf.org,  xrblock <xrblock@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/xrblock/uXMwz8XDVjy21VCcCTxBqOFQ6fM>
Subject: Re: [xrblock] AD Evaluation of draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-06
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 08 Oct 2017 13:11:34 -0000

Hi Ben,

See inline.

On Tue, Oct 3, 2017 at 12:28 AM, Ben Campbell <ben@nostrum.com> wrote:
> Hi,
>
> This is my AD Evaluation of draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-06.=
 I would like to resolve at least the substantive comments prior to IETF LC=
.
>
> Thanks!
>
> Ben.
> =E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=
=E2=80=94
>
> Substantive:
>
> - General: If I understand correctly, this document lists and describes X=
R metrics that a WebRTC application might choose to negotiate and expose vi=
a the WebRTC API. It does not define any new XR metrics. That brings up two=
 questions:
>
> 1) Why is this specific to WebRTC? For the most parts, all the arguments =
here would apply to any sort of RTP endpoint.
>

This draft was created initially as an input to RTCWEB and later as an
input to WebRTC Statistics API. Hence the use of WebRTC in the title
and the introduction. We could add to the introduction: "In general,
the metrics listed in this document can be exposed by any real-time
communications endpoint." Or something along those lines


> 2) Why is this standards track? This sort of material is typically inform=
ational, or occasionally a BCP. There are a small number of 2119 keywords, =
but I=E2=80=99m not sure they are needed or appropriate. (Specifics below.)=
 My initial instinct is that this should be informational.
>

The reason until recently (perhaps still exist) is that this was an
input from the IETF to W3C, I am not sure if there was an official
liaison statements sent to them? nonetheless, the W3C Statistics API
document needed a specification needed (a specification in any
standards body would suffice) for metrics to be accepted into the W3C
document.

In practice, it helped that I was the co-author of both the IETF and
W3C document and hence was able to make the case for the metrics in
W3C.

> - General: This needs an IANA considerations section, even if it just con=
tains the statement to the effect of =E2=80=9CThis document makes no reques=
ts for IANA=E2=80=9D.
>
> - 1, last paragraph: =E2=80=9C The document also creates a registry conta=
ining identifiers from the metrics reported in the RTCP Sender, Receiver, a=
nd Extended Reports.=E2=80=9D

This should be removed. Thanks for pointing this out.

>
> It doesn=E2=80=99t actually do that. I understand from the shepherd=E2=80=
=99s report that this was intentionally removed.
>
> =E2=80=94 =E2=80=9CAll identifiers proposed in this document are RECOMMEN=
DED to be implemented by an endpoint.  An endpoint MAY choose not to expose=
 an identifier if it does not implement the corresponding RTCP Report. =E2=
=80=9C
>
> Does the =E2=80=9CRECOMMENDED=E2=80=9D apply to all endpoints or just Web=
RTC endpoints? If the latter, doesn=E2=80=99t that requirement belong (or n=
eed to update) some requirement from an RTCWEB (maybe rtp-usage) document, =
or even the API itself? (I suspect that this draft does not have standing t=
o state this normatively.) What is meant by =E2=80=9CMAY choose not to expo=
se=E2=80=9D. Is that talking about via the WebRTC API? If so, isn=E2=80=99t=
 that up to the API definition? (That is, it shouldn=E2=80=99t be normative=
 here.)
>

It should be applicable to any endpoint, although it is pertinent or
timely for the WebRTC endpoint to expose these.
The purpose of the statement was to highlight that if the
middlebox/endpoint sends RTCP XRs then it should expose the data
available via the API.

I am open to changing to a non-normative lower case guidance if that
would be more suitable, although if this document is making
recommendations to the W3C document -- wouldn't we keep the uppercase?

co-authors, what do you think?

> -2: If this document keeps the normative keywords, please use the updated=
 boilerplate from RFC 8174. (I note that there are at least some uncapitali=
zed =E2=80=9Cmay=E2=80=9Ds that do not seem normative.)
>

depending on the above, we should fix these to uppercase.

> - 5.2.2, last paragraph: =E2=80=9CThe following metrics can also be consi=
dered=E2=80=A6=E2=80=9D
> Be considered by whom? Implementors? API designers?
>

Both.

> - 6, first paragraph: =E2=80=9CIn practice the application MUST be able t=
o query the statistic identifiers on both an incoming (remote) and outgoing=
 (local) media stream.=E2=80=9D
> What does the MUST requirement apply to? The WebRTC API? This seems more =
like a statement of fact that =E2=80=9C the application needs to be able=E2=
=80=A6=E2=80=9D
>

correct, "needs to" is better.

> -8: "Therefore encryption procedures, such as the ones suggested for a Se=
cure RTCP (SRTCP), need to be used.=E2=80=9D
> The text should describe the reasons encryption is needed. Also, is this =
a new normative requirement, or a restatement of an existing requirement?
>

I believe it is restatement alluding to the guidance in the
corresponding RTCP XRs.

> Editorial:
>
> -1, paragraph 1:" If sufficient information (metrics or statistics) are p=
rovided to the applications, it can attempt to improve the media quality. =
=E2=80=9C
>
> s / =E2=80=9Care provided=E2=80=9D / =E2=80=9Cis provided=E2=80=9D
> s / applications / application
>
> -3, 2nd paragraph: It would help to clarify that the references to sectio=
n 5 and 6 are to this document, not RFC 3611.
>
> =E2=80=94 3rd paragraph: "At the moment=E2=80=A6=E2=80=9D
> Please clarify that is at the time of writing (not reading)
>
> -5, 2nd paragraph: =E2=80=9C Application impact metrics mainly collect th=
e information in the viewpoint of application =E2=80=A6 =E2=80=9C
> s / in / from
> Also, please expand =E2=80=9CFEC=E2=80=9D on first mention.
>
> - 5.1.1, first paragraph: =E2=80=9C Duplicate packets may be a result of =
network delays, which causes the sender to retransmit the original packets.=
=E2=80=9D
> s/ :delays, which=E2=80=9D / =E2=80=9Cdelays that=E2=80=9D
>
> =E2=80=94 last paragraph: "For those RTCWEB services with jitter buffer=
=E2=80=A6=E2=80=9D
> s/buffer/buffers
>
> - 5.1.2, first paragraph:
> First sentence is a comma splice.
>  =E2=80=94 =E2=80=9Csome transitory nature of the impairments=E2=80=9D
> Should this say =E2=80=9Cthe transitory nature of some impairments=E2=80=
=9D?
> =E2=80=94 =E2=80=9C Distributed burst provides a higher subjective qualit=
y=E2=80=9D
> =E2=80=9CBurst distribution =E2=80=A6=E2=80=9D?
> =E2=80=94 Last paragraph: =E2=80=9C Hence, if WebRTC application=E2=80=9D
> Missing article (or should application be plural?)
>
> - 5.2.1, title: Should =E2=80=9CDiscard=E2=80=9D be =E2=80=9CDiscarded=E2=
=80=9D?
>
> -7: Please clarify that this is at the time of this writing.
>

Thanks for your feedback and suggestions, we will fix these.

Regards,
Varun


--=20
Founder, CEO, callstats.io
http://www.callstats.io

Interested in networking, media quality, and diagnostics.
We are hiring!: www.callstats.io/jobs/


From nobody Mon Oct  9 22:56:30 2017
Return-Path: <rachel.huang@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 54ACB13219F; Mon,  9 Oct 2017 22:56:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2YUQ-aY5cvoa; Mon,  9 Oct 2017 22:56:26 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46B6F1320D8; Mon,  9 Oct 2017 22:56:25 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml709-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DXG01332; Tue, 10 Oct 2017 05:56:23 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml709-cah.china.huawei.com (10.201.108.32) with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 10 Oct 2017 06:56:22 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.199]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Tue, 10 Oct 2017 13:56:16 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: Varun Singh <varun@callstats.io>, Ben Campbell <ben@nostrum.com>
CC: "draft-ietf-xrblock-rtcweb-rtcp-xr-metrics.all@ietf.org" <draft-ietf-xrblock-rtcweb-rtcp-xr-metrics.all@ietf.org>, xrblock <xrblock@ietf.org>
Thread-Topic: [xrblock] AD Evaluation of draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-06
Thread-Index: AQHTO8VfsJtQ+zH+8kexJpju540EL6LZcCcAgAMFGOA=
Date: Tue, 10 Oct 2017 05:56:15 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB9C59E3ED@nkgeml513-mbx.china.huawei.com>
References: <99303AB6-D5EE-44EC-B515-DCB7966DADA6@nostrum.com> <CACHXSv7E+NhU_dvd63k57RfrVOAPoSFuOK8+-bRwsJTAcZ_ixQ@mail.gmail.com>
In-Reply-To: <CACHXSv7E+NhU_dvd63k57RfrVOAPoSFuOK8+-bRwsJTAcZ_ixQ@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.134.153.152]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090206.59DC6107.006C, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.1.199, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 370afb36fc3efbfb8515e93a700a4da6
Archived-At: <https://mailarchive.ietf.org/arch/msg/xrblock/yqeqM8l8LRaSevEZLxPX6xibByE>
Subject: Re: [xrblock] AD Evaluation of draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-06
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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 Oct 2017 05:56:28 -0000

SGkNCg0KUGxlYXNlIHNlZSBpbmxpbmUuDQoNCkJSLA0KUmFjaGVsDQoNCj4gLS0tLS1PcmlnaW5h
bCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogVmFydW4gU2luZ2ggW21haWx0bzp2YXJ1bkBjYWxsc3Rh
dHMuaW9dDQo+IFNlbnQ6IFN1bmRheSwgT2N0b2JlciAwOCwgMjAxNyA5OjExIFBNDQo+IFRvOiBC
ZW4gQ2FtcGJlbGwNCj4gQ2M6IGRyYWZ0LWlldGYteHJibG9jay1ydGN3ZWItcnRjcC14ci1tZXRy
aWNzLmFsbEBpZXRmLm9yZzsgeHJibG9jaw0KPiBTdWJqZWN0OiBSZTogW3hyYmxvY2tdIEFEIEV2
YWx1YXRpb24gb2YNCj4gZHJhZnQtaWV0Zi14cmJsb2NrLXJ0Y3dlYi1ydGNwLXhyLW1ldHJpY3Mt
MDYNCj4gDQo+IEhpIEJlbiwNCj4gDQo+IFNlZSBpbmxpbmUuDQo+IA0KPiBPbiBUdWUsIE9jdCAz
LCAyMDE3IGF0IDEyOjI4IEFNLCBCZW4gQ2FtcGJlbGwgPGJlbkBub3N0cnVtLmNvbT4gd3JvdGU6
DQo+ID4gSGksDQo+ID4NCj4gPiBUaGlzIGlzIG15IEFEIEV2YWx1YXRpb24gb2YgZHJhZnQtaWV0
Zi14cmJsb2NrLXJ0Y3dlYi1ydGNwLXhyLW1ldHJpY3MtMDYuIEkNCj4gd291bGQgbGlrZSB0byBy
ZXNvbHZlIGF0IGxlYXN0IHRoZSBzdWJzdGFudGl2ZSBjb21tZW50cyBwcmlvciB0byBJRVRGIExD
Lg0KPiA+DQo+ID4gVGhhbmtzIQ0KPiA+DQo+ID4gQmVuLg0KPiA+IOKAlOKAlOKAlOKAlOKAlOKA
lOKAlOKAlOKAlA0KPiA+DQo+ID4gU3Vic3RhbnRpdmU6DQo+ID4NCj4gPiAtIEdlbmVyYWw6IElm
IEkgdW5kZXJzdGFuZCBjb3JyZWN0bHksIHRoaXMgZG9jdW1lbnQgbGlzdHMgYW5kIGRlc2NyaWJl
cyBYUg0KPiBtZXRyaWNzIHRoYXQgYSBXZWJSVEMgYXBwbGljYXRpb24gbWlnaHQgY2hvb3NlIHRv
IG5lZ290aWF0ZSBhbmQgZXhwb3NlIHZpYQ0KPiB0aGUgV2ViUlRDIEFQSS4gSXQgZG9lcyBub3Qg
ZGVmaW5lIGFueSBuZXcgWFIgbWV0cmljcy4gVGhhdCBicmluZ3MgdXAgdHdvDQo+IHF1ZXN0aW9u
czoNCj4gPg0KPiA+IDEpIFdoeSBpcyB0aGlzIHNwZWNpZmljIHRvIFdlYlJUQz8gRm9yIHRoZSBt
b3N0IHBhcnRzLCBhbGwgdGhlIGFyZ3VtZW50cyBoZXJlDQo+IHdvdWxkIGFwcGx5IHRvIGFueSBz
b3J0IG9mIFJUUCBlbmRwb2ludC4NCj4gPg0KPiANCj4gVGhpcyBkcmFmdCB3YXMgY3JlYXRlZCBp
bml0aWFsbHkgYXMgYW4gaW5wdXQgdG8gUlRDV0VCIGFuZCBsYXRlciBhcyBhbiBpbnB1dCB0bw0K
PiBXZWJSVEMgU3RhdGlzdGljcyBBUEkuIEhlbmNlIHRoZSB1c2Ugb2YgV2ViUlRDIGluIHRoZSB0
aXRsZSBhbmQgdGhlDQo+IGludHJvZHVjdGlvbi4gV2UgY291bGQgYWRkIHRvIHRoZSBpbnRyb2R1
Y3Rpb246ICJJbiBnZW5lcmFsLCB0aGUgbWV0cmljcyBsaXN0ZWQgaW4NCj4gdGhpcyBkb2N1bWVu
dCBjYW4gYmUgZXhwb3NlZCBieSBhbnkgcmVhbC10aW1lIGNvbW11bmljYXRpb25zIGVuZHBvaW50
LiIgT3INCj4gc29tZXRoaW5nIGFsb25nIHRob3NlIGxpbmVzDQo+IA0KPiANCj4gPiAyKSBXaHkg
aXMgdGhpcyBzdGFuZGFyZHMgdHJhY2s/IFRoaXMgc29ydCBvZiBtYXRlcmlhbCBpcyB0eXBpY2Fs
bHkgaW5mb3JtYXRpb25hbCwNCj4gb3Igb2NjYXNpb25hbGx5IGEgQkNQLiBUaGVyZSBhcmUgYSBz
bWFsbCBudW1iZXIgb2YgMjExOSBrZXl3b3JkcywgYnV0IEnigJltIG5vdA0KPiBzdXJlIHRoZXkg
YXJlIG5lZWRlZCBvciBhcHByb3ByaWF0ZS4gKFNwZWNpZmljcyBiZWxvdy4pIE15IGluaXRpYWwg
aW5zdGluY3QgaXMgdGhhdA0KPiB0aGlzIHNob3VsZCBiZSBpbmZvcm1hdGlvbmFsLg0KPiA+DQo+
IA0KPiBUaGUgcmVhc29uIHVudGlsIHJlY2VudGx5IChwZXJoYXBzIHN0aWxsIGV4aXN0KSBpcyB0
aGF0IHRoaXMgd2FzIGFuIGlucHV0IGZyb20gdGhlDQo+IElFVEYgdG8gVzNDLCBJIGFtIG5vdCBz
dXJlIGlmIHRoZXJlIHdhcyBhbiBvZmZpY2lhbCBsaWFpc29uIHN0YXRlbWVudHMgc2VudCB0bw0K
PiB0aGVtPyBub25ldGhlbGVzcywgdGhlIFczQyBTdGF0aXN0aWNzIEFQSSBkb2N1bWVudCBuZWVk
ZWQgYSBzcGVjaWZpY2F0aW9uDQo+IG5lZWRlZCAoYSBzcGVjaWZpY2F0aW9uIGluIGFueSBzdGFu
ZGFyZHMgYm9keSB3b3VsZCBzdWZmaWNlKSBmb3IgbWV0cmljcyB0byBiZQ0KPiBhY2NlcHRlZCBp
bnRvIHRoZSBXM0MgZG9jdW1lbnQuDQo+IA0KPiBJbiBwcmFjdGljZSwgaXQgaGVscGVkIHRoYXQg
SSB3YXMgdGhlIGNvLWF1dGhvciBvZiBib3RoIHRoZSBJRVRGIGFuZCBXM0MNCj4gZG9jdW1lbnQg
YW5kIGhlbmNlIHdhcyBhYmxlIHRvIG1ha2UgdGhlIGNhc2UgZm9yIHRoZSBtZXRyaWNzIGluIFcz
Qy4NCj4gDQo+ID4gLSBHZW5lcmFsOiBUaGlzIG5lZWRzIGFuIElBTkEgY29uc2lkZXJhdGlvbnMg
c2VjdGlvbiwgZXZlbiBpZiBpdCBqdXN0IGNvbnRhaW5zDQo+IHRoZSBzdGF0ZW1lbnQgdG8gdGhl
IGVmZmVjdCBvZiDigJxUaGlzIGRvY3VtZW50IG1ha2VzIG5vIHJlcXVlc3RzIGZvciBJQU5B4oCd
Lg0KPiA+DQo+ID4gLSAxLCBsYXN0IHBhcmFncmFwaDog4oCcIFRoZSBkb2N1bWVudCBhbHNvIGNy
ZWF0ZXMgYSByZWdpc3RyeSBjb250YWluaW5nDQo+IGlkZW50aWZpZXJzIGZyb20gdGhlIG1ldHJp
Y3MgcmVwb3J0ZWQgaW4gdGhlIFJUQ1AgU2VuZGVyLCBSZWNlaXZlciwgYW5kDQo+IEV4dGVuZGVk
IFJlcG9ydHMu4oCdDQo+IA0KPiBUaGlzIHNob3VsZCBiZSByZW1vdmVkLiBUaGFua3MgZm9yIHBv
aW50aW5nIHRoaXMgb3V0Lg0KPiANCj4gPg0KPiA+IEl0IGRvZXNu4oCZdCBhY3R1YWxseSBkbyB0
aGF0LiBJIHVuZGVyc3RhbmQgZnJvbSB0aGUgc2hlcGhlcmTigJlzIHJlcG9ydCB0aGF0DQo+IHRo
aXMgd2FzIGludGVudGlvbmFsbHkgcmVtb3ZlZC4NCj4gPg0KPiA+IOKAlCDigJxBbGwgaWRlbnRp
ZmllcnMgcHJvcG9zZWQgaW4gdGhpcyBkb2N1bWVudCBhcmUgUkVDT01NRU5ERUQgdG8gYmUNCj4g
PiBpbXBsZW1lbnRlZCBieSBhbiBlbmRwb2ludC4gIEFuIGVuZHBvaW50IE1BWSBjaG9vc2Ugbm90
IHRvIGV4cG9zZSBhbg0KPiA+IGlkZW50aWZpZXIgaWYgaXQgZG9lcyBub3QgaW1wbGVtZW50IHRo
ZSBjb3JyZXNwb25kaW5nIFJUQ1AgUmVwb3J0LiDigJwNCj4gPg0KPiA+IERvZXMgdGhlIOKAnFJF
Q09NTUVOREVE4oCdIGFwcGx5IHRvIGFsbCBlbmRwb2ludHMgb3IganVzdCBXZWJSVEMNCj4gPiBl
bmRwb2ludHM/IElmIHRoZSBsYXR0ZXIsIGRvZXNu4oCZdCB0aGF0IHJlcXVpcmVtZW50IGJlbG9u
ZyAob3IgbmVlZCB0bw0KPiA+IHVwZGF0ZSkgc29tZSByZXF1aXJlbWVudCBmcm9tIGFuIFJUQ1dF
QiAobWF5YmUgcnRwLXVzYWdlKSBkb2N1bWVudCwgb3INCj4gPiBldmVuIHRoZSBBUEkgaXRzZWxm
PyAoSSBzdXNwZWN0IHRoYXQgdGhpcyBkcmFmdCBkb2VzIG5vdCBoYXZlIHN0YW5kaW5nDQo+ID4g
dG8gc3RhdGUgdGhpcyBub3JtYXRpdmVseS4pIFdoYXQgaXMgbWVhbnQgYnkg4oCcTUFZIGNob29z
ZSBub3QgdG8NCj4gPiBleHBvc2XigJ0uIElzIHRoYXQgdGFsa2luZyBhYm91dCB2aWEgdGhlIFdl
YlJUQyBBUEk/IElmIHNvLCBpc27igJl0IHRoYXQNCj4gPiB1cCB0byB0aGUgQVBJIGRlZmluaXRp
b24/IChUaGF0IGlzLCBpdCBzaG91bGRu4oCZdCBiZSBub3JtYXRpdmUgaGVyZS4pDQo+ID4NCj4g
DQo+IEl0IHNob3VsZCBiZSBhcHBsaWNhYmxlIHRvIGFueSBlbmRwb2ludCwgYWx0aG91Z2ggaXQg
aXMgcGVydGluZW50IG9yIHRpbWVseSBmb3IgdGhlDQo+IFdlYlJUQyBlbmRwb2ludCB0byBleHBv
c2UgdGhlc2UuDQo+IFRoZSBwdXJwb3NlIG9mIHRoZSBzdGF0ZW1lbnQgd2FzIHRvIGhpZ2hsaWdo
dCB0aGF0IGlmIHRoZSBtaWRkbGVib3gvZW5kcG9pbnQNCj4gc2VuZHMgUlRDUCBYUnMgdGhlbiBp
dCBzaG91bGQgZXhwb3NlIHRoZSBkYXRhIGF2YWlsYWJsZSB2aWEgdGhlIEFQSS4NCj4gDQo+IEkg
YW0gb3BlbiB0byBjaGFuZ2luZyB0byBhIG5vbi1ub3JtYXRpdmUgbG93ZXIgY2FzZSBndWlkYW5j
ZSBpZiB0aGF0IHdvdWxkIGJlDQo+IG1vcmUgc3VpdGFibGUsIGFsdGhvdWdoIGlmIHRoaXMgZG9j
dW1lbnQgaXMgbWFraW5nIHJlY29tbWVuZGF0aW9ucyB0byB0aGUNCj4gVzNDIGRvY3VtZW50IC0t
IHdvdWxkbid0IHdlIGtlZXAgdGhlIHVwcGVyY2FzZT8NCj4gDQo+IGNvLWF1dGhvcnMsIHdoYXQg
ZG8geW91IHRoaW5rPw0KDQpbUmFjaGVsXTogVGhlIHNlbnRlbmNlcyBhcmUgbWVhbnQgZm9yIFdl
YlJUQyBlbmRwb2ludHMsIGJ1dCBzdXJlbHksIGl0IGlzIGFwcGxpY2FibGUgdG8gYW55IGVuZHBv
aW50cy4gUlRQLXVzYWdlIGRvY3VtZW50IGp1c3QgZGVzY3JpYmVzIFJUQ1AgU1IgYW5kIFJSLCBh
bmQgbGVhdmVzIFJUQ1AgWFIgdW5kaXNjdXNzZWQuIFRoYXQncyBhbHNvIHBhcnQgb2YgdGhlIHJl
YXNvbiB3aHkgd2UgaGF2ZSB0aGlzIGRyYWZ0LiBTbyBJIHRoaW5rIGl0J3MgYmV0dGVyIHRvIGtl
ZXAgdGhlIHVwcGVyY2FzZS4gQnV0IG1heWJlIHNvbWUgbW9kaWZpY2F0aW9uIG9mIHRoZSBzZW50
ZW5jZXMgc2hvdWxkIGJlIG1hZGUgdG8gbWFrZSBpdCBjbGVhciB0aGF0IHRoaXMgaXMgbWFraW5n
IHJlY29tbWVuZGF0aW9ucyB0byB3ZWJSVEMgYXBwbGljYXRpb25zLiBIb3cgYWJvdXQNCiINCldl
YlJUQyBlbmRwb2ludHMgYXJlIFJFQ09NTUVOREVEIHRvIGltcGxlbWVudCBhbGwgdGhlIG1ldHJp
Y3MgcHJvcG9zZWQgaW4gdGhpcyBkb2N1bWVudC4gQW4gZW5kcG9pbnQgTUFZIGNob29zZSBub3Qg
dG8gZXhwb3NlIGFuIGlkZW50aWZpZXIgaWYgaXQgZG9lcyBub3QgaW1wbGVtZW50IHRoZSBjb3Jy
ZXNwb25kaW5nIFJUQ1AgUmVwb3J0Lg0KIg0KPw0KDQpCUiwNClJhY2hlbA0K


From nobody Thu Oct 12 14:51:51 2017
Return-Path: <ben@nostrum.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 28D0C1344AD; Thu, 12 Oct 2017 14:51:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.878
X-Spam-Level: 
X-Spam-Status: No, score=-1.878 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yA7L_7tElJXa; Thu, 12 Oct 2017 14:51:46 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9FC2133071; Thu, 12 Oct 2017 14:51:46 -0700 (PDT)
Received: from [10.0.1.75] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v9CLpg2O047636 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 12 Oct 2017 16:51:43 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.75]
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Ben Campbell <ben@nostrum.com>
X-Mailer: iPad Mail (15A421)
In-Reply-To: <CACHXSv7E+NhU_dvd63k57RfrVOAPoSFuOK8+-bRwsJTAcZ_ixQ@mail.gmail.com>
Date: Thu, 12 Oct 2017 16:51:42 -0500
Cc: draft-ietf-xrblock-rtcweb-rtcp-xr-metrics.all@ietf.org, xrblock <xrblock@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <17BE8BAC-64E3-4A11-B3F0-C54E3D05244E@nostrum.com>
References: <99303AB6-D5EE-44EC-B515-DCB7966DADA6@nostrum.com> <CACHXSv7E+NhU_dvd63k57RfrVOAPoSFuOK8+-bRwsJTAcZ_ixQ@mail.gmail.com>
To: Varun Singh <varun@callstats.io>
Archived-At: <https://mailarchive.ietf.org/arch/msg/xrblock/cs2P3pIwtI45t8skjzCpkO25640>
Subject: Re: [xrblock] AD Evaluation of draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-06
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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 Oct 2017 21:51:49 -0000

>=20
> On Oct 8, 2017, at 8:11 AM, Varun Singh <varun@callstats.io> wrote:
>=20
> Hi Ben,
>=20
> See inline.
>=20
>> On Tue, Oct 3, 2017 at 12:28 AM, Ben Campbell <ben@nostrum.com> wrote:
>> Hi,
>>=20
>> This is my AD Evaluation of draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-06.=
 I would like to resolve at least the substantive comments prior to IETF LC.=

>>=20
>> Thanks!
>>=20
>> Ben.
>> =E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=
=80=94
>>=20
>> Substantive:
>>=20
>> - General: If I understand correctly, this document lists and describes X=
R metrics that a WebRTC application might choose to negotiate and expose via=
 the WebRTC API. It does not define any new XR metrics. That brings up two q=
uestions:
>>=20
>> 1) Why is this specific to WebRTC? For the most parts, all the arguments h=
ere would apply to any sort of RTP endpoint.
>>=20
>=20
> This draft was created initially as an input to RTCWEB and later as an
> input to WebRTC Statistics API. Hence the use of WebRTC in the title
> and the introduction. We could add to the introduction: "In general,
> the metrics listed in this document can be exposed by any real-time
> communications endpoint." Or something along those lines
>=20
>=20
>> 2) Why is this standards track? This sort of material is typically inform=
ational, or occasionally a BCP. There are a small number of 2119 keywords, b=
ut I=E2=80=99m not sure they are needed or appropriate. (Specifics below.) M=
y initial instinct is that this should be informational.
>>=20
>=20
> The reason until recently (perhaps still exist) is that this was an
> input from the IETF to W3C, I am not sure if there was an official
> liaison statements sent to them? nonetheless, the W3C Statistics API
> document needed a specification needed (a specification in any
> standards body would suffice) for metrics to be accepted into the W3C
> document.

To make sure I understand:That API document will reference this one? Do they=
 require that specification to be standards track?

Was there discussion in xrblock about standards track verses BCP?

>=20
> In practice, it helped that I was the co-author of both the IETF and
> W3C document and hence was able to make the case for the metrics in
> W3C.

Is that case already made? That is, does the need for a published RFC still e=
xist?

>=20
>> - General: This needs an IANA considerations section, even if it just con=
tains the statement to the effect of =E2=80=9CThis document makes no request=
s for IANA=E2=80=9D.
>>=20
>> - 1, last paragraph: =E2=80=9C The document also creates a registry conta=
ining identifiers from the metrics reported in the RTCP Sender, Receiver, an=
d Extended Reports.=E2=80=9D
>=20
> This should be removed. Thanks for pointing this out.
>=20
>>=20
>> It doesn=E2=80=99t actually do that. I understand from the shepherd=E2=80=
=99s report that this was intentionally removed.
>>=20
>> =E2=80=94 =E2=80=9CAll identifiers proposed in this document are RECOMMEN=
DED to be implemented by an endpoint.  An endpoint MAY choose not to expose a=
n identifier if it does not implement the corresponding RTCP Report. =E2=80=9C=

>>=20
>> Does the =E2=80=9CRECOMMENDED=E2=80=9D apply to all endpoints or just Web=
RTC endpoints? If the latter, doesn=E2=80=99t that requirement belong (or ne=
ed to update) some requirement from an RTCWEB (maybe rtp-usage) document, or=
 even the API itself? (I suspect that this draft does not have standing to s=
tate this normatively.) What is meant by =E2=80=9CMAY choose not to expose=E2=
=80=9D. Is that talking about via the WebRTC API? If so, isn=E2=80=99t that u=
p to the API definition? (That is, it shouldn=E2=80=99t be normative here.)
>>=20
>=20
> It should be applicable to any endpoint, although it is pertinent or
> timely for the WebRTC endpoint to expose these.
> The purpose of the statement was to highlight that if the
> middlebox/endpoint sends RTCP XRs then it should expose the data
> available via the API.
>=20
> I am open to changing to a non-normative lower case guidance if that
> would be more suitable, although if this document is making
> recommendations to the W3C document -- wouldn't we keep the uppercase?

In general, 2119 keywords are better used when we are talking about interope=
rability issues in a protocol. I suggest switching to lower case unless ther=
e=E2=80=99s some reason to believe the W3C won=E2=80=99t pay attention unles=
s it=E2=80=99s in all-caps. (I don=E2=80=99t think that=E2=80=99s usually th=
e case.)

>=20
> co-authors, what do you think?
>=20
>> -2: If this document keeps the normative keywords, please use the updated=
 boilerplate from RFC 8174. (I note that there are at least some uncapitaliz=
ed =E2=80=9Cmay=E2=80=9Ds that do not seem normative.)
>>=20
>=20
> depending on the above, we should fix these to uppercase.
>=20
>> - 5.2.2, last paragraph: =E2=80=9CThe following metrics can also be consi=
dered=E2=80=A6=E2=80=9D
>> Be considered by whom? Implementors? API designers?
>>=20
>=20
> Both.
>=20
>> - 6, first paragraph: =E2=80=9CIn practice the application MUST be able t=
o query the statistic identifiers on both an incoming (remote) and outgoing (=
local) media stream.=E2=80=9D
>> What does the MUST requirement apply to? The WebRTC API? This seems more l=
ike a statement of fact that =E2=80=9C the application needs to be able=E2=80=
=A6=E2=80=9D
>>=20
>=20
> correct, "needs to" is better.
>=20
>> -8: "Therefore encryption procedures, such as the ones suggested for a Se=
cure RTCP (SRTCP), need to be used.=E2=80=9D
>> The text should describe the reasons encryption is needed. Also, is this a=
 new normative requirement, or a restatement of an existing requirement?
>>=20
>=20
> I believe it is restatement alluding to the guidance in the
> corresponding RTCP XRs.
>=20
>> Editorial:
>>=20
>> -1, paragraph 1:" If sufficient information (metrics or statistics) are p=
rovided to the applications, it can attempt to improve the media quality. =E2=
=80=9C
>>=20
>> s / =E2=80=9Care provided=E2=80=9D / =E2=80=9Cis provided=E2=80=9D
>> s / applications / application
>>=20
>> -3, 2nd paragraph: It would help to clarify that the references to sectio=
n 5 and 6 are to this document, not RFC 3611.
>>=20
>> =E2=80=94 3rd paragraph: "At the moment=E2=80=A6=E2=80=9D
>> Please clarify that is at the time of writing (not reading)
>>=20
>> -5, 2nd paragraph: =E2=80=9C Application impact metrics mainly collect th=
e information in the viewpoint of application =E2=80=A6 =E2=80=9C
>> s / in / from
>> Also, please expand =E2=80=9CFEC=E2=80=9D on first mention.
>>=20
>> - 5.1.1, first paragraph: =E2=80=9C Duplicate packets may be a result of n=
etwork delays, which causes the sender to retransmit the original packets.=E2=
=80=9D
>> s/ :delays, which=E2=80=9D / =E2=80=9Cdelays that=E2=80=9D
>>=20
>> =E2=80=94 last paragraph: "For those RTCWEB services with jitter buffer=E2=
=80=A6=E2=80=9D
>> s/buffer/buffers
>>=20
>> - 5.1.2, first paragraph:
>> First sentence is a comma splice.
>> =E2=80=94 =E2=80=9Csome transitory nature of the impairments=E2=80=9D
>> Should this say =E2=80=9Cthe transitory nature of some impairments=E2=80=9D=
?
>> =E2=80=94 =E2=80=9C Distributed burst provides a higher subjective qualit=
y=E2=80=9D
>> =E2=80=9CBurst distribution =E2=80=A6=E2=80=9D?
>> =E2=80=94 Last paragraph: =E2=80=9C Hence, if WebRTC application=E2=80=9D=

>> Missing article (or should application be plural?)
>>=20
>> - 5.2.1, title: Should =E2=80=9CDiscard=E2=80=9D be =E2=80=9CDiscarded=E2=
=80=9D?
>>=20
>> -7: Please clarify that this is at the time of this writing.
>>=20
>=20
> Thanks for your feedback and suggestions, we will fix these.
>=20
> Regards,
> Varun
>=20
>=20
> --=20
> Founder, CEO, callstats.io
> http://www.callstats.io
>=20
> Interested in networking, media quality, and diagnostics.
> We are hiring!: www.callstats.io/jobs/


From nobody Thu Oct 12 14:56:19 2017
Return-Path: <ben@nostrum.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 D3C7A132941; Thu, 12 Oct 2017 14:56:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level: 
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eLPAcMB76YSs; Thu, 12 Oct 2017 14:56:17 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 219771321A0; Thu, 12 Oct 2017 14:56:17 -0700 (PDT)
Received: from [10.0.1.75] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v9CLu8T8048458 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 12 Oct 2017 16:56:09 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.75]
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Ben Campbell <ben@nostrum.com>
X-Mailer: iPad Mail (15A421)
In-Reply-To: <51E6A56BD6A85142B9D172C87FC3ABBB9C59E3ED@nkgeml513-mbx.china.huawei.com>
Date: Thu, 12 Oct 2017 16:56:08 -0500
Cc: Varun Singh <varun@callstats.io>, "draft-ietf-xrblock-rtcweb-rtcp-xr-metrics.all@ietf.org" <draft-ietf-xrblock-rtcweb-rtcp-xr-metrics.all@ietf.org>,  xrblock <xrblock@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F77A95BC-3638-4CFC-8455-CCB1BA61B217@nostrum.com>
References: <99303AB6-D5EE-44EC-B515-DCB7966DADA6@nostrum.com> <CACHXSv7E+NhU_dvd63k57RfrVOAPoSFuOK8+-bRwsJTAcZ_ixQ@mail.gmail.com> <51E6A56BD6A85142B9D172C87FC3ABBB9C59E3ED@nkgeml513-mbx.china.huawei.com>
To: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/xrblock/6m74J69VYu725z03fdTGCXjXPu8>
Subject: Re: [xrblock] AD Evaluation of draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-06
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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 Oct 2017 21:56:19 -0000

> On Oct 10, 2017, at 12:56 AM, Huangyihong (Rachel) <rachel.huang@huawei.co=
m> wrote:
>=20
> Hi
>=20
> Please see inline.
>=20
> BR,
> Rachel
>=20
>> -----Original Message-----
>> From: Varun Singh [mailto:varun@callstats.io]
>> Sent: Sunday, October 08, 2017 9:11 PM
>> To: Ben Campbell
>> Cc: draft-ietf-xrblock-rtcweb-rtcp-xr-metrics.all@ietf.org; xrblock
>> Subject: Re: [xrblock] AD Evaluation of
>> draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-06
>>=20
>> Hi Ben,
>>=20
>> See inline.
>>=20
>>> On Tue, Oct 3, 2017 at 12:28 AM, Ben Campbell <ben@nostrum.com> wrote:
>>> Hi,
>>>=20
>>> This is my AD Evaluation of draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-06=
. I
>> would like to resolve at least the substantive comments prior to IETF LC.=

>>>=20
>>> Thanks!
>>>=20
>>> Ben.
>>> =E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=
=E2=80=94
>>>=20
>>> Substantive:
>>>=20
>>> - General: If I understand correctly, this document lists and describes X=
R
>> metrics that a WebRTC application might choose to negotiate and expose vi=
a
>> the WebRTC API. It does not define any new XR metrics. That brings up two=

>> questions:
>>>=20
>>> 1) Why is this specific to WebRTC? For the most parts, all the arguments=
 here
>> would apply to any sort of RTP endpoint.
>>>=20
>>=20
>> This draft was created initially as an input to RTCWEB and later as an in=
put to
>> WebRTC Statistics API. Hence the use of WebRTC in the title and the
>> introduction. We could add to the introduction: "In general, the metrics l=
isted in
>> this document can be exposed by any real-time communications endpoint." O=
r
>> something along those lines
>>=20
>>=20
>>> 2) Why is this standards track? This sort of material is typically infor=
mational,
>> or occasionally a BCP. There are a small number of 2119 keywords, but I=E2=
=80=99m not
>> sure they are needed or appropriate. (Specifics below.) My initial instin=
ct is that
>> this should be informational.
>>>=20
>>=20
>> The reason until recently (perhaps still exist) is that this was an input=
 from the
>> IETF to W3C, I am not sure if there was an official liaison statements se=
nt to
>> them? nonetheless, the W3C Statistics API document needed a specification=

>> needed (a specification in any standards body would suffice) for metrics t=
o be
>> accepted into the W3C document.
>>=20
>> In practice, it helped that I was the co-author of both the IETF and W3C
>> document and hence was able to make the case for the metrics in W3C.
>>=20
>>> - General: This needs an IANA considerations section, even if it just co=
ntains
>> the statement to the effect of =E2=80=9CThis document makes no requests f=
or IANA=E2=80=9D.
>>>=20
>>> - 1, last paragraph: =E2=80=9C The document also creates a registry cont=
aining
>> identifiers from the metrics reported in the RTCP Sender, Receiver, and
>> Extended Reports.=E2=80=9D
>>=20
>> This should be removed. Thanks for pointing this out.
>>=20
>>>=20
>>> It doesn=E2=80=99t actually do that. I understand from the shepherd=E2=80=
=99s report that
>> this was intentionally removed.
>>>=20
>>> =E2=80=94 =E2=80=9CAll identifiers proposed in this document are RECOMME=
NDED to be
>>> implemented by an endpoint.  An endpoint MAY choose not to expose an
>>> identifier if it does not implement the corresponding RTCP Report. =E2=80=
=9C
>>>=20
>>> Does the =E2=80=9CRECOMMENDED=E2=80=9D apply to all endpoints or just We=
bRTC
>>> endpoints? If the latter, doesn=E2=80=99t that requirement belong (or ne=
ed to
>>> update) some requirement from an RTCWEB (maybe rtp-usage) document, or
>>> even the API itself? (I suspect that this draft does not have standing
>>> to state this normatively.) What is meant by =E2=80=9CMAY choose not to
>>> expose=E2=80=9D. Is that talking about via the WebRTC API? If so, isn=E2=
=80=99t that
>>> up to the API definition? (That is, it shouldn=E2=80=99t be normative he=
re.)
>>>=20
>>=20
>> It should be applicable to any endpoint, although it is pertinent or time=
ly for the
>> WebRTC endpoint to expose these.
>> The purpose of the statement was to highlight that if the middlebox/endpo=
int
>> sends RTCP XRs then it should expose the data available via the API.
>>=20
>> I am open to changing to a non-normative lower case guidance if that woul=
d be
>> more suitable, although if this document is making recommendations to the=

>> W3C document -- wouldn't we keep the uppercase?
>>=20
>> co-authors, what do you think?
>=20
> [Rachel]: The sentences are meant for WebRTC endpoints, but surely, it is a=
pplicable to any endpoints. RTP-usage document just describes RTCP SR and RR=
, and leaves RTCP XR undiscussed. That's also part of the reason why we have=
 this draft. So I think it's better to keep the uppercase. But maybe some mo=
dification of the sentences should be made to make it clear that this is mak=
ing recommendations to webRTC applications. How about
> "
> WebRTC endpoints are RECOMMENDED to implement all the metrics proposed in t=
his document. An endpoint MAY choose not to expose an identifier if it does n=
ot implement the corresponding RTCP Report.
> "

My concern is that it can be problematic to add normative requirements to th=
ings that already exist without updating those things. Otherwise, implemento=
rs may not learn about the new requirements. That is, they may not realize t=
hey need to even read this document.=20

Would it make sense to ask for a reference to this from rtp-usage?

Ben.=


From nobody Mon Oct 30 03:45:09 2017
Return-Path: <marvin.zhenghui@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 0683613F97B for <xrblock@ietfa.amsl.com>; Mon, 30 Oct 2017 03:45:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r21nCD0tfSeM for <xrblock@ietfa.amsl.com>; Mon, 30 Oct 2017 03:44:59 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44A2D13F672 for <xrblock@ietf.org>; Mon, 30 Oct 2017 03:44:59 -0700 (PDT)
Received: from 172.18.9.243 (EHLO lhreml705-cah.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DSS10143; Mon, 30 Oct 2017 05:44:58 -0500 (CDT)
Received: from DGGEMI401-HUB.china.huawei.com (10.3.17.134) by lhreml705-cah.china.huawei.com (10.201.108.46) with Microsoft SMTP Server (TLS) id 14.3.361.1; Mon, 30 Oct 2017 10:44:57 +0000
Received: from DGGEMI509-MBS.china.huawei.com ([169.254.2.159]) by dggemi401-hub.china.huawei.com ([10.3.17.134]) with mapi id 14.03.0361.001; Mon, 30 Oct 2017 18:44:54 +0800
From: "Zhenghui (Marvin)" <marvin.zhenghui@huawei.com>
To: "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: New Version Notification for draft-zheng-xrblock-effective-loss-index-00.txt
Thread-Index: AQHTUWElwWYdEPiXGE6Y0xJT62LVRaL8NOlg
Date: Mon, 30 Oct 2017 10:44:53 +0000
Message-ID: <F8F4995E43962F4996B280E9678CED0001FAC9DD@dggemi509-mbs.china.huawei.com>
References: <150935557383.3511.9896803073809476506.idtracker@ietfa.amsl.com>
In-Reply-To: <150935557383.3511.9896803073809476506.idtracker@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.135.87.2]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/xrblock/1RQQwvv5LW5Gag4xulrZaSUuBJ0>
Subject: [xrblock] FW: New Version Notification for draft-zheng-xrblock-effective-loss-index-00.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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 Oct 2017 10:45:05 -0000

SGVsbG8gWFIgQkxPQ0sgRm9sa3MsDQoNCkp1c3QgZm9yIHlvdXIgaW5mb3JtYXRpb24sIEkndmUg
c3VibWl0dGVkIGEgbmV3IHhyYmxvY2sgZHJhZnQuDQoNCkJlc3QgUmVnYXJkcywNClpoZW5naHVp
IChNYXJ2aW4pDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGludGVybmV0
LWRyYWZ0c0BpZXRmLm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10gDQpTZW50
OiBNb25kYXksIE9jdG9iZXIgMzAsIDIwMTcgNToyNiBQTQ0KVG86IFJvbmcgR3UgPGd1cm9uZ19j
bWNjQG91dGxvb2suY29tPjsgUWluIFd1IDxiaWxsLnd1QGh1YXdlaS5jb20+OyBaaGVuZ2h1aSAo
TWFydmluKSA8bWFydmluLnpoZW5naHVpQGh1YXdlaS5jb20+OyBSb25pIEV2ZW4gPHJvbmkuZXZl
bkBodWF3ZWkuY29tPg0KU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFm
dC16aGVuZy14cmJsb2NrLWVmZmVjdGl2ZS1sb3NzLWluZGV4LTAwLnR4dA0KDQoNCkEgbmV3IHZl
cnNpb24gb2YgSS1ELCBkcmFmdC16aGVuZy14cmJsb2NrLWVmZmVjdGl2ZS1sb3NzLWluZGV4LTAw
LnR4dA0KaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBIdWkgWmhlbmcgYW5kIHBv
c3RlZCB0byB0aGUgSUVURiByZXBvc2l0b3J5Lg0KDQpOYW1lOgkJZHJhZnQtemhlbmcteHJibG9j
ay1lZmZlY3RpdmUtbG9zcy1pbmRleA0KUmV2aXNpb246CTAwDQpUaXRsZToJCVJUUCBDb250cm9s
IFByb3RvY29sIChSVENQKSBFeHRlbmRlZCBSZXBvcnQgKFhSKSBCbG9jayBmb3IgRWZmZWN0aXZl
IExvc3MgSW5kZXggUmVwb3J0aW5nDQpEb2N1bWVudCBkYXRlOgkyMDE3LTEwLTMwDQpHcm91cDoJ
CUluZGl2aWR1YWwgU3VibWlzc2lvbg0KUGFnZXM6CQkxMQ0KVVJMOiAgICAgICAgICAgIGh0dHBz
Oi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC16aGVuZy14cmJsb2NrLWVmZmVj
dGl2ZS1sb3NzLWluZGV4LTAwLnR4dA0KU3RhdHVzOiAgICAgICAgIGh0dHBzOi8vZGF0YXRyYWNr
ZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LXpoZW5nLXhyYmxvY2stZWZmZWN0aXZlLWxvc3MtaW5kZXgv
DQpIdG1saXplZDogICAgICAgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXpoZW5n
LXhyYmxvY2stZWZmZWN0aXZlLWxvc3MtaW5kZXgtMDANCkh0bWxpemVkOiAgICAgICBodHRwczov
L2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9odG1sL2RyYWZ0LXpoZW5nLXhyYmxvY2stZWZmZWN0
aXZlLWxvc3MtaW5kZXgtMDANCg0KDQpBYnN0cmFjdDoNCiAgIFRoaXMgZG9jdW1lbnQgZGVmaW5l
cyBhIG5ldyBtZXRyaWMgZm9yIFJUUCBhcHBsaWNhdGlvbnMgdG8gbWVhc3VyZQ0KICAgdGhlIGVm
ZmVjdGl2ZW5lc3Mgb2Ygc3RyZWFtIHJlcGFpciBtZWFucywgYW5kIGFuIFJUUCBDb250cm9sIFBy
b3RvY29sDQogICAoUlRDUCkgRXh0ZW5kZWQgUmVwb3J0IChYUikgQmxvY2sgdG8gcmVwb3J0IHRo
ZSBtZXRyaWMuDQoNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICANCg0KDQpQbGVhc2Ugbm90ZSB0
aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJt
aXNzaW9uIHVudGlsIHRoZSBodG1saXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFpbGFibGUg
YXQgdG9vbHMuaWV0Zi5vcmcuDQoNClRoZSBJRVRGIFNlY3JldGFyaWF0DQoNCg==

