Re: [xrblock] AD evaluation: draft-ietf-xrblock-rtcp-xr-post-repair-loss-count-06

"Huangyihong (Rachel)" <> Thu, 11 December 2014 04:52 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 5E47E1A9043 for <>; Wed, 10 Dec 2014 20:52:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.422
X-Spam-Status: No, score=-1.422 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id kTIu1sBB9NGv for <>; Wed, 10 Dec 2014 20:52:54 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BBF711A8F40 for <>; Wed, 10 Dec 2014 20:52:53 -0800 (PST)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id BMS48922; Thu, 11 Dec 2014 04:52:50 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Thu, 11 Dec 2014 04:52:49 +0000
Received: from ([]) by ([]) with mapi id 14.03.0158.001; Thu, 11 Dec 2014 12:52:38 +0800
From: "Huangyihong (Rachel)" <>
To: Qin Wu <>, Benoit Claise <>, "Romascanu, Dan (Dan)" <>, Alissa Cooper <>
Thread-Topic: [xrblock] AD evaluation: draft-ietf-xrblock-rtcp-xr-post-repair-loss-count-06
Thread-Index: AQHQFBU7NCl2L2xMgkihRruhtLkvNJyIIWKQgAAQ7QCAABasgIAA4+qAgACnPLA=
Date: Thu, 11 Dec 2014 04:52:37 +0000
Message-ID: <>
References: <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "" <>, "" <>
Subject: Re: [xrblock] AD evaluation: draft-ietf-xrblock-rtcp-xr-post-repair-loss-count-06
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 11 Dec 2014 04:52:57 -0000

Hi Qin,

Thanks for your suggestions. It's really helpful to improve the appendix.


发件人: Qin Wu 
发送时间: 2014年12月11日 10:53
收件人: Benoit Claise; Romascanu, Dan (Dan); Huangyihong (Rachel); Alissa Cooper
主题: RE: [xrblock] AD evaluation: draft-ietf-xrblock-rtcp-xr-post-repair-loss-count-06

发件人: Benoit Claise []
发送时间: 2014年12月10日 21:17
收件人: Romascanu, Dan (Dan); Huangyihong (Rachel); Alissa Cooper
抄送:;; Qin Wu
主题: Re: [xrblock] AD evaluation: draft-ietf-xrblock-rtcp-xr-post-repair-loss-count-06

On 10/12/2014 12:56, Romascanu, Dan (Dan) wrote:
>> -----Original Message-----
>> From: xrblock [] On Behalf Of 
>> Huangyihong
>> (Rachel)
>>> = Appendix A =
>>> Doesn't it sort of defeat the purpose of the 6390 template to fill 
>>> out a
>> template with a bunch of links back to the definitions of the fields 
>> in other parts of the document, rather than putting those definitions 
>> directly in the template? I mean, isn't the point of the template to 
>> have all of the information concisely reported in one place?
>>> [Rachel]: I referenced previous RFCs, like [RFC7243] [RFC7294]. But 
>>> it's okay
>> for me to have those definitions directly copied in the template if you want.
>> Well, I guess I did not ask about this for those RFCs, but I would 
>> like to understand better what the point of the template is if all 
>> the templates end up linking the reader back to various sections of the document.
>> [Rachel]: I didn't well involved in the 6390 template usage 
>> discussion. So others please correct me if I'm wrong. But as far as I 
>> remember, it is raised by the OPS AD who thinks we are defining new 
>> metrics while without following the 6390 template. But the drafts of 
>> xrblock are more focus on the RTCP XR report block definition. So 
>> Compromise is made that we use the 6390 template at the appendix for 
>> the metrics. Since most of the definitions in the template have been 
>> specified in the draft, we just simply reference them in the template.
> Hi,
> Rachel's recollection is correct. This discussion happened when the first XRBLOCK documents hit the IESG table after RFC 6390 was published. Qin  was the main editor, Benoit was the OPS AD, Gonzalo was the RAI AD, and I was the document shepherd. Benoit asked to re-use the 6390 template, so that the metrics defined by XRBLOCK are formatted in a similar manner with metrics defined by other WGs in the IETF. The WG wanted that the RFC text keeps compatibility with previous XRBLOCK / RTCP-XR definitions. So we arrived at the solution to include the RFC 6390 style of definition in Annexes, using references in order to avoid duplication.
The primary reason was that the RFC 6390 template definitions in the XRBLOCK documents could be reused when populating the performance metric registry (see

[Qin]: Agree with What both Dan and Benoit said here.
I think it might be helpful to optimize some places for the metrics represented using RFC6390 in the annex, and also it is no harm to add some clarification text in the annex.
e.g., for Units of Measurement, instead of referencing metric definition in some section, you can say something like:
This metric is expressed as a 16-bit unsigned integer value.
Also for measurement timing, besides referencing to specific section, you can also add some text to say:
This metric relies on the sequence number interval to determine measurement timing.
For measurement method of " Unrepaired RTP Packet Loss Count Metric ", you can replace the original text with the following text:

* Method of Measurement or Calculation: See section 3, Unrepaired RTP Packet Loss Count Metric definition. It is directly measured and must be measured for  the primary source RTP packets with no further chance of repair.
For measurement point, you can say something like:
It is measured at the receiving end of the RTP stream.

Regards, Benoit
> Regards,
> Dan
> .