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

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Mon, 04 February 2013 10:52 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 A608921F843A for <xrblock@ietfa.amsl.com>; Mon, 4 Feb 2013 02:52:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.411
X-Spam-Level:
X-Spam-Status: No, score=-103.411 tagged_above=-999 required=5 tests=[AWL=0.188, 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 sPE-KFM3kMmx for <xrblock@ietfa.amsl.com>; Mon, 4 Feb 2013 02:52:17 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id CBA4B21F8439 for <xrblock@ietf.org>; Mon, 4 Feb 2013 02:52:16 -0800 (PST)
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 04 Feb 2013 05:52:57 -0500
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by co300216-co-erhwest-out.avaya.com with ESMTP; 04 Feb 2013 05:51:09 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.02.0328.009; Mon, 4 Feb 2013 05:52:01 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Glen Zorn <glenzorn@gmail.com>
Thread-Topic: [xrblock] downref in draft-ietf-xrblock-rtcp-xr-decodability-06.txt
Thread-Index: AQHN88DrLd7+Y1nZuU2Vg/jnP6OsaJhkd45QgAUYtzCAAGICgP//rU+A
Date: Mon, 04 Feb 2013 10:52:01 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA080442@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> <9904FB1B0159DA42B0B887B7FA8119CA0803D7@AZ-FFEXMB04.global.avaya.com> <510F8E53.8050601@gmail.com>
In-Reply-To: <510F8E53.8050601@gmail.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
Cc: "xrblock@ietf.org" <xrblock@ietf.org>
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 10:52:17 -0000

Thanks, Glen. 

The submission template for the write-up that WG chairs must fill when submitting WG documents to the IESG is available at http://www.ietf.org/iesg/template/doc-writeup.txt. 

It includes the question: 

(7) Has each author confirmed that any and all appropriate IPR
disclosures required for full conformance with the provisions of BCP 78
and BCP 79 have already been filed. If not, explain why.

So my reading is that while the text that you quote includes a commitment that all authors 'have made or will make all disclosures ...' at the moment of the submission to the IESG a dull confirmation that these disclosures have been filled is required. 

This is the reason why we (as chairs) need to ask for your explicit confirmation now. 

Can you provide the same confirmation also for draft-xrblock-ietf-rtcp-xr-summary?

Regards,

Dan




> -----Original Message-----
> From: Glen Zorn [mailto:glenzorn@gmail.com]
> Sent: Monday, February 04, 2013 12:33 PM
> To: Romascanu, Dan (Dan)
> Cc: Huangyihong (Rachel); Qin Wu; xrblock@ietf.org; glenzorn@gmail.com
> Subject: Re: [xrblock] downref in draft-ietf-xrblock-rtcp-xr-
> decodability-06.txt
> 
> On 02/04/2013 04:45 PM, Romascanu, Dan (Dan) wrote:
> > 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).
> 
> BCP 79 says:
> 
> 3.2.  Rights and Permissions
> 
> 3.2.1.  All Contributions
> 
> _By submission of a Contribution_, each person actually submitting the
>     Contribution, and each named co-Contributor,is _deemed to agree___
> to
>     the following terms and conditions, on his or her own behalf, and on
>     behalf of the organizations the Contributor represents or is
>     sponsored by (if any) when submitting the Contribution.
> 
>     A. The Contributor represents that he or she has made or will
>        promptly make all disclosures required by Section 6.1.1 of this
>        document.
> 
>     B. The Contributor represents that there are no limits to the
>        Contributor's ability to make the grants, acknowledgments and
>        agreements herein that are reasonably and personally known to the
>        Contributor.
> 
>     C. If the Contribution is an Internet-Draft, this agreement must be
>        acknowledged, by including in the "Status of this Memo" section
> on
>        the first page of the Contribution, the appropriate notices
>        described in Section 5 of [RFC3978].
> 
> So for the 9th time (and counting!), yes, all appropriate IPR
> disclosures required for full conformance with the provisions of BCP 78
> and BCP 79 have been filed.
> 
> ...