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

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Mon, 04 February 2013 09:45 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 80BA321F85B1 for <xrblock@ietfa.amsl.com>; Mon, 4 Feb 2013 01:45:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.405
X-Spam-Level:
X-Spam-Status: No, score=-103.405 tagged_above=-999 required=5 tests=[AWL=0.194, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 48l601oNeSTX for <xrblock@ietfa.amsl.com>; Mon, 4 Feb 2013 01:45:00 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 1B6E121F841A for <xrblock@ietf.org>; Mon, 4 Feb 2013 01:45:00 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAJoQA1HGmAcF/2dsb2JhbABFgmu7ZxZzgh4BAQEBAwEBAQ8oNBcEAgEIDQQEAQELFAkHJwsUCQgCBAESCBqHbQELoViccASQXmEDklqJQIo7gneCJA
X-IronPort-AV: E=Sophos;i="4.84,541,1355115600"; d="scan'208";a="387294643"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 04 Feb 2013 04:44:28 -0500
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 04 Feb 2013 04:43:58 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.02.0328.009; Mon, 4 Feb 2013 04:45:13 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Huangyihong (Rachel)" <rachel.huang@huawei.com>, Qin Wu <bill.wu@huawei.com>, "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: [xrblock] downref in draft-ietf-xrblock-rtcp-xr-decodability-06.txt
Thread-Index: AQHN88DrLd7+Y1nZuU2Vg/jnP6OsaJhkd45QgAUYtzA=
Date: Mon, 04 Feb 2013 09:45:12 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA0803D7@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA0611E4@AZ-FFEXMB04.global.avaya.com> <197A785F37FE4581837C568980DE1830@china.huawei.com> <9904FB1B0159DA42B0B887B7FA8119CA0619C9@AZ-FFEXMB04.global.avaya.com> <51E6A56BD6A85142B9D172C87FC3ABBB45718EB8@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <51E6A56BD6A85142B9D172C87FC3ABBB45718EB8@nkgeml501-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Mon, 04 Feb 2013 09:45:01 -0000

Hi Rachel,

Yes, my comment was addressed. 

We are waiting for the confirmation from Glen Zorn (as an author of the document) that all appropriate IPR disclosures required for full conformance with the provisions of BCP 78 and BCP 79 have been filled in order to progress this document (submit to the IESG). 

Thanks and Regards,

Dan




> -----Original Message-----
> From: Huangyihong (Rachel) [mailto:rachel.huang@huawei.com]
> Sent: Friday, February 01, 2013 5:55 AM
> To: Romascanu, Dan (Dan); Qin Wu; xrblock@ietf.org
> Subject: RE: [xrblock] downref in draft-ietf-xrblock-rtcp-xr-
> decodability-06.txt
> 
> Hi Dan,
> 
> Does version 07 address your comments?
> 
> Best Regards!
> Rachel
> 
> -----Original Message-----
> From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On
> Behalf Of Romascanu, Dan (Dan)
> Sent: Wednesday, January 16, 2013 4:10 PM
> To: Qin Wu; xrblock@ietf.org
> Subject: Re: [xrblock] downref in draft-ietf-xrblock-rtcp-xr-
> decodability-06.txt
> 
> Hi Qin,
> 
> Please submit an updated version with this change.
> 
> If anybody sees a problem, please say.
> 
> Thanks and Regards,
> 
> Dan
> 
> 
> 
> 
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com]
> > Sent: Wednesday, January 16, 2013 3:04 AM
> > To: Romascanu, Dan (Dan); xrblock@ietf.org
> > Subject: Re: [xrblock] downref in draft-ietf-xrblock-rtcp-xr-
> > decodability-06.txt
> >
> > 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
> > >
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock