IETF Logo Mail Archive

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

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Tue, 15 January 2013 14:06 UTC

Return-Path: <dromasca@avaya.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 6F7FB21F88F7 for <xrblock@ietfa.amsl.com>; Tue, 15 Jan 2013 06:06:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.918
X-Spam-Level:
X-Spam-Status: No, score=-102.918 tagged_above=-999 required=5 tests=[AWL=-0.319, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 YNZH1we6xE8M for <xrblock@ietfa.amsl.com>; Tue, 15 Jan 2013 06:06:33 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id A864521F86E7 for <xrblock@ietf.org>; Tue, 15 Jan 2013 06:06:29 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai4KAAEvoFCHCzI1/2dsb2JhbABEgX9twGmBAQeCIAEBAxIoUQEVFRRCJgEEGxqHaAGaBYQrjGSPHZF+YQOcCYo2gm+CGQ
X-IronPort-AV: E=Sophos;i="4.80,759,1344225600"; d="scan'208";a="44417174"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 15 Jan 2013 08:55:03 -0500
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 15 Jan 2013 08:41:03 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.02.0318.004; Tue, 15 Jan 2013 09:06:37 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: downref in draft-ietf-xrblock-rtcp-xr-decodability-06.txt
Thread-Index: Ac3zJ9edIP4k8t09RuCVcwrHVR0CNw==
Date: Tue, 15 Jan 2013 14:06:37 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA0611E4@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [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: Tue, 15 Jan 2013 14:06:35 -0000

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

v2.23.0 | Report a Bug | By Email