RE: actions related to improving IETF meeting selections

Sheng Jiang <jiangsheng@huawei.com> Mon, 13 June 2016 02:37 UTC

Return-Path: <jiangsheng@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAF2612D0B8 for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2016 19:37:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Level:
X-Spam-Status: No, score=-5.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, 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 o0cKuWKWofG6 for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2016 19:37:48 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D49812B041 for <ietf@ietf.org>; Sun, 12 Jun 2016 19:37:46 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CLV21661; Mon, 13 Jun 2016 02:37:44 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml706-cah.china.huawei.com (10.201.5.182) with Microsoft SMTP Server (TLS) id 14.3.235.1; Mon, 13 Jun 2016 03:37:43 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Mon, 13 Jun 2016 10:37:38 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Melinda Shore <melinda.shore@gmail.com>, "nalini.elkins@insidethestack.com" <nalini.elkins@insidethestack.com>, Ted Lemon <mellon@fugue.com>
Subject: RE: actions related to improving IETF meeting selections
Thread-Topic: actions related to improving IETF meeting selections
Thread-Index: AQHRwY4PPAPCv7SMOEOReVnc8WPAbZ/lHCbggABZigCAACtUgIAABRcAgAADXoCAABKlgIAA3o9g//+MogCAAIcKcA==
Date: Mon, 13 Jun 2016 02:37:37 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B927CA8157B@NKGEML515-MBX.china.huawei.com>
References: <0DAA04D6-03FE-444D-ABF9-4A1CF2F7DFC9@ietf.org> <5D36713D8A4E7348A7E10DF7437A4B927CA81040@NKGEML515-MBX.china.huawei.com> <557685565.1303569.1465745474144.JavaMail.yahoo@mail.yahoo.com> <CAPt1N1nqg9nbkgUGq2GSe7_Pu36aFx8WvX6KopZ0N9Ot9n-ceQ@mail.gmail.com> <312eb527-e0f0-d26f-b653-bcd0a24d8915@gmail.com> <CAPt1N1=Sg6Usxo61McuJnH4v8jPOxy85EjLyqxYtPdwuJ6Kdgw@mail.gmail.com> <909008962.1455653.1465760599679.JavaMail.yahoo@mail.yahoo.com> <5D36713D8A4E7348A7E10DF7437A4B927CA81518@NKGEML515-MBX.china.huawei.com> <ce1c294f-bdc4-d1c9-691f-43a68606be3d@gmail.com>
In-Reply-To: <ce1c294f-bdc4-d1c9-691f-43a68606be3d@gmail.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.99.197]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A0B0205.575E1C79.0009, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 38d40beb4469e91c1464989f84e70b37
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pDDtvL_S5rQkzB4BKSAD5p_Fd_s>
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jun 2016 02:37:50 -0000

>On 6/12/16 5:42 PM, Sheng Jiang wrote:
>> I
>> personally believe it is feasible because the current three meetings per
>> year is actually slowing down many WGs’ pace.
>
>If so, it's because people are choosing not to progress
>work between meetings, where "people" include both chairs
>and editors.

Yes, but it is given that we do not provide the opportunities. The chairs have to do every logistics by themselves with the risk that only key contributors would like to travel for this single WG interim meeting. Actually, even myself, although I think one more meeting would benefit my WG, I don't want to organize it by myself. But it was IETF organizing a secondary meeting, I certainly would like to give a try.

I have been involved in a few standardization bodies, ITU-T, ETSI, BBF, 3GPP.... I don't think IETF should bring the style from them. But I do feel the IETF three meeting per year is a little bit rigid. And I did hear a lot of complain from various people regarding to the slow progress of IETF standardization.

Sheng

>By contrast, W3C is able to progress work
>rather quickly (er, for the most part) and meets only
>once/year.  However, they make heavy use of teleconferences,
>collaboration tools, and mailing lists.
>
> > If you asked the WG chairs the question of how many f2f
>> meetings per year are ideal for their WGs, in my guess, over 1/4 WGs
>> would like to meet more than three times.
>
>I've chaired a bunch of working groups over the years and never
>felt that way, myself.  In a working group I chair currently
>our editors rarely show up at face to face meetings and while
>we're a lot slower than we'd like to be I'd say that has more
>to do with problems that would not be resolved by meeting more
>frequently or by having editors at meetings.
>
>It is a little vexing that in many cases we're being asked
>to accommodate the needs of people who haven't actively
>contributed in the past and who don't show an interest in
>actively contributing in the future.
>
>I chaired an ETSI working group (TIPHON Security) a bunch
>of years ago and don't think that their working style (nor that
>of the ITU-T, or IEEE, or ... ) maps particularly well onto the
>IETF, and consequently that it would be inappropriate to force
>it.  Also note that ETSI and 3GPP (and W3C) and so on have
>designated experts on salary to move work along, and it may
>be worth considering the extent to which they're able to move
>work forward by paying someone else to do it.
>
>The question of the relevance of IETF standards is inseparable from
>the question of their implementation and deployment, I think, and
>the economic model underlying our work is quite different from that
>motivating the work of the big, traditional telecomm standards
>bodies.
>
>Melinda