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

"Romascanu, Dan (Dan)" <> Wed, 10 December 2014 11:56 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 15A961A870D for <>; Wed, 10 Dec 2014 03:56:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id dRgzh2KhSLXG for <>; Wed, 10 Dec 2014 03:56:15 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8372D1A1B3C for <>; Wed, 10 Dec 2014 03:56:15 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.07,552,1413259200"; d="scan'208";a="95736118"
Received: from unknown (HELO ([]) by with ESMTP; 10 Dec 2014 06:56:14 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO ([]) by with ESMTP/TLS/AES128-SHA; 10 Dec 2014 06:56:13 -0500
Received: from ([fe80::6db7:b0af:8480:c126]) by ([]) with mapi id 14.03.0174.001; Wed, 10 Dec 2014 12:56:12 +0100
From: "Romascanu, Dan (Dan)" <>
To: "Huangyihong (Rachel)" <>, Alissa Cooper <>
Thread-Topic: [xrblock] AD evaluation: draft-ietf-xrblock-rtcp-xr-post-repair-loss-count-06
Thread-Index: AQHQFBVJyIiP/LtiFUKbxW222iuoTpyIE7GAgACi2gA=
Date: Wed, 10 Dec 2014 11:56:12 +0000
Message-ID: <>
References: <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ext Benoit Claise <>, "" <>, "" <>
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: Wed, 10 Dec 2014 11:56:17 -0000

> -----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.


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.