RE: Support (as co-author)

Fatai Zhang <zhangfatai@huawei.com> Mon, 25 November 2019 16:12 UTC

Return-Path: <zhangfatai@huawei.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AB261209D7 for <wgchairs@ietfa.amsl.com>; Mon, 25 Nov 2019 08:12:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4-T730tsYQ-y for <wgchairs@ietfa.amsl.com>; Mon, 25 Nov 2019 08:12:44 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DC041209C6 for <wgchairs@ietf.org>; Mon, 25 Nov 2019 08:12:44 -0800 (PST)
Received: from LHREML713-CAH.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 0A80598524B95894C62E for <wgchairs@ietf.org>; Mon, 25 Nov 2019 16:12:39 +0000 (GMT)
Received: from lhreml713-chm.china.huawei.com (10.201.108.64) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 25 Nov 2019 16:12:38 +0000
Received: from lhreml713-chm.china.huawei.com (10.201.108.64) by lhreml713-chm.china.huawei.com (10.201.108.64) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Mon, 25 Nov 2019 16:12:38 +0000
Received: from DGGEML405-HUB.china.huawei.com (10.3.17.49) by lhreml713-chm.china.huawei.com (10.201.108.64) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Mon, 25 Nov 2019 16:12:38 +0000
Received: from DGGEML530-MBX.china.huawei.com ([169.254.7.100]) by dggeml405-hub.china.huawei.com ([10.3.17.49]) with mapi id 14.03.0439.000; Tue, 26 Nov 2019 00:12:32 +0800
From: Fatai Zhang <zhangfatai@huawei.com>
To: "julien.meuric" <julien.meuric@orange.com>, Benoit Claise <bclaise@cisco.com>
CC: WG Chairs <wgchairs@ietf.org>
Subject: RE: Support (as co-author)
Thread-Topic: Support (as co-author)
Thread-Index: AQHVo6J5I6Q+OTP+o0+mogHW9If16KebfFYAgAAG8ICAAIu+Wg==
Date: Mon, 25 Nov 2019 16:12:32 +0000
Message-ID: <F82A4B6D50F9464B8EBA55651F541CF8ADA5407E@dggeml530-mbx.china.huawei.com>
References: <5871efb6-9fa7-a06a-e201-fb9fba04935e@cisco.com> <CAA=duU2sYzr0OxELyKJ6Zyo7wSJab2bcaMyxbd+DLbQVGn_duw@mail.gmail.com>, <6195_1574697143_5DDBF8B7_6195_354_2_a837b3f1-ef58-32b0-1f5c-b333768935e7@orange.com>
In-Reply-To: <6195_1574697143_5DDBF8B7_6195_354_2_a837b3f1-ef58-32b0-1f5c-b333768935e7@orange.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_F82A4B6D50F9464B8EBA55651F541CF8ADA5407Edggeml530mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/LoWbl2T-SAuGSNSvIesYVQtZS6I>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Nov 2019 16:12:50 -0000

I fully agree with Julien.

At least, a co-author (and a contributor) as a WG member has the right to voice his/her support.

If it does not require the co-authors (and contributors) to respond the WG adoption, there might be quiet on the list (e.g.,no one shows support, but there are many co-authors/co-contributors for a draft), or there would be few members object the adoption, and then it might be difficult for the chairs to judge WG consensus.




________________________________




Thanks
Fatai

发件人: julien.meuric<julien.meuric@orange.com<mailto:julien.meuric@orange.com>>
收件人: Benoit Claise<bclaise@cisco.com<mailto:bclaise@cisco.com>>
抄送: WG Chairs<wgchairs@ietf.org<mailto:wgchairs@ietf.org>>
主题: Re: Support (as co-author)
时间: 2019-11-25 23:52:55

Hi Benoît,

I agree with you that, in the ideal world, being a co-author implies
being a supporter and that a "support as co-author" doesn't have the
exact same value as a support by someone else. However, as Andy
suggests, an explicit support expressed by a co-author at adoption or WG
LC time may help distinguishing:
- co-authors who just approved the use of their (company) name vs. those
who actually follow (at least) the key steps of the documents;
- co-authors who no longer care about a given work their used to be
interested in (e.g., when reaching WG LC) vs. those who still believe is
needs to progress.
What is more, having co-authors involved in a support thread on mailing
lists is also a way to attract readers and trigger responses from other
WG members.

My 2 cents,

Julien


On 25/11/2019 16:27, Andrew G. Malis wrote:
> Benoit,
>
> In some WGs, I have seen the chairs ask for explicit declarations of
> support for adoption or last call, including from co-authors. In such
> a case, it make sense for a co-author to identify themself as such.
>
> Cheers,
> Andy
>
>
> On Mon, Nov 25, 2019 at 10:10 AM Benoit Claise <bclaise@cisco.com
> <mailto:bclaise@cisco.com>> wrote:
>
>     Dear all,
>
>     Along the years, I witnessed a trend, which intensifies with time: "I
>     support the adoption of this draft (as a co-author)."
>     Well, if someone is a co-author, implicitly this person wants the
>     draft
>     to progress. Therefore, such as message carries no weight IMO.
>     Is it time for the WG chairs to start correcting this behaviour,
>     or at
>     least setting the right expectations?
>
>     ex:
>     https://mailarchive.ietf.org/arch/browse/ippm/?q=Adoption%20Call%20for%20draft-ioamteam-ippm-ioam-direct-export
>
>     Regards, Benoit
>
>
>


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.