Re: [xrblock] downref in draft-ietf-xrblock-rtcp-xr-decodability-06.txt

Qin Wu <bill.wu@huawei.com> Wed, 16 January 2013 01:03 UTC

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 9489F21F8692 for <xrblock@ietfa.amsl.com>; Tue, 15 Jan 2013 17:03:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.392
X-Spam-Level:
X-Spam-Status: No, score=-4.392 tagged_above=-999 required=5 tests=[AWL=0.454, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mv4mjkz6Z9dW for <xrblock@ietfa.amsl.com>; Tue, 15 Jan 2013 17:03:49 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1CCA621F868F for <xrblock@ietf.org>; Tue, 15 Jan 2013 17:03:48 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AOU66477; Wed, 16 Jan 2013 01:03:47 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 16 Jan 2013 01:03:36 +0000
Received: from SZXEML451-HUB.china.huawei.com (10.82.67.194) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 16 Jan 2013 01:03:45 +0000
Received: from w53375 (10.138.41.149) by szxeml451-hub.china.huawei.com (10.82.67.194) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 16 Jan 2013 09:03:39 +0800
Message-ID: <197A785F37FE4581837C568980DE1830@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, xrblock@ietf.org
References: <9904FB1B0159DA42B0B887B7FA8119CA0611E4@AZ-FFEXMB04.global.avaya.com>
Date: Wed, 16 Jan 2013 09:03:39 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Originating-IP: [10.138.41.149]
X-CFilter-Loop: Reflected
Subject: Re: [xrblock] downref in draft-ietf-xrblock-rtcp-xr-decodability-06.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, 16 Jan 2013 01:03:50 -0000

Good catch, I agree with your point.
I think it is more straightforward to change RFC6709 as Informationtive.

Regards!
-Qin
----- Original Message ----- 
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <xrblock@ietf.org>
Sent: Tuesday, January 15, 2013 10:06 PM
Subject: [xrblock] downref in draft-ietf-xrblock-rtcp-xr-decodability-06.txt


> Editors of draft-ietf-xrblock-rtcp-xr-decodability-06.txt,
> 
> While preparing the write-up draft-ietf-xrblock-rtcp-xr-decodability-06.txt for submission to the IESG I ran in a similar downref problem as with the summary statistics I-D, probably introduced in the last rounds of edits. [RFC6709] is now referred to as a Normative Reference, which results in a downref, as 6709 is an Informational RFC. Can you also look at this issue? 
> 
> Note that downrefs are OK, but we must be sure that this is what we want to do, and call these explicitly in the write-ups, which will lead to being called explicitly in the IETF Last Calls. 
> 
> My take as a contributor is that RFC 6709 provides a generic guidance and as such the reference to it may be Informative, but other people may have different opinions. 
> 
> Thanks and Regards,
> 
> Dan
> 
> 
> 
> 
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock
>