RE: actions related to improving IETF meeting selections

Sheng Jiang <jiangsheng@huawei.com> Mon, 13 June 2016 01:42 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 1A04C12B02B for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2016 18:42:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.646
X-Spam-Level:
X-Spam-Status: No, score=-5.646 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 gB_cw6FeRe8a for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2016 18:42:38 -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 044CC12D625 for <ietf@ietf.org>; Sun, 12 Jun 2016 18:42:36 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml707-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CQR18209; Mon, 13 Jun 2016 01:42:34 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml707-cah.china.huawei.com (10.201.5.199) with Microsoft SMTP Server (TLS) id 14.3.235.1; Mon, 13 Jun 2016 02:42:33 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Mon, 13 Jun 2016 09:42:27 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "nalini.elkins@insidethestack.com" <nalini.elkins@insidethestack.com>, Ted Lemon <mellon@fugue.com>, Melinda Shore <melinda.shore@gmail.com>
Subject: RE: actions related to improving IETF meeting selections
Thread-Topic: actions related to improving IETF meeting selections
Thread-Index: AQHRwY4PPAPCv7SMOEOReVnc8WPAbZ/lHCbggABZigCAACtUgIAABRcAgAADXoCAABKlgIAA3o9g
Date: Mon, 13 Jun 2016 01:42:28 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B927CA81518@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>
In-Reply-To: <909008962.1455653.1465760599679.JavaMail.yahoo@mail.yahoo.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: multipart/alternative; boundary="_000_5D36713D8A4E7348A7E10DF7437A4B927CA81518NKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090204.575E0F8B.0012, 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: 3a0224cd11d45dccc8d6cfba1c84c58e
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qB4LP3vzH_enNJfn54wTODXcwDI>
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 01:42:41 -0000

Hi, Nalini, Melinda & Ted,

Although there are meetings in various regions for IETF awareness, they are not really IETF meetings. The secondary meetings in my mind are actually working meetings first. That’s why Ted said it “would require a lot of regular IETFers to sign on and get support for going”. I personally believe it is feasible because the current three meetings per year is actually slowing down many WGs’ pace. It is one of the reasons that IETF’s standardization work is slow. Some 3GPP WGs could meet almost 10 times per year! Of course, not every WG need extra meetings. The requirements from various WGs are different. But it is never discussed! 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.  But WG chairs are lacking of logistics for f2f interim meetings. It is also difficult to get contributors to travel for a single WG interim meetings. But if there are 20 WGs interim meetings together, it may be a different story. I don’t think we will lose the key contributors for those active WGs in such meetings, although there may be less “steady” audience. This may give the chance for both accelerating WG’s work and serving diversity purposes. Also, participants may have more time to discuss new works or more details, giving more relax on the total agenda. The scale of such meetings could be much smaller, I guess, like 300 participants. It would give more flexibility and agility, too.

Best regards,

Sheng

From: nalini.elkins@insidethestack.com [mailto:nalini.elkins@insidethestack.com]
Sent: Monday, June 13, 2016 3:43 AM
To: Ted Lemon; Melinda Shore; Sheng Jiang
Cc: ietf
Subject: Re: actions related to improving IETF meeting selections



>Yes, there would have to be work to do.

Today, there are meetings in various regions for IETF awareness.  At times,  ISOC chapters and /or NOGs are quite involved.   We also have quite a bit of activity at remote hubs (or community hubs) or whatever we are calling them.

I would like to hear from Sheng about what his ideas are for these "secondary" meetings.   Of course, then, we need to be clear about what the goals of such activities are and to coordinate well with other existing activities.

Nalini


On Sun, Jun 12, 2016 at 2:24 PM, Melinda Shore <melinda.shore@gmail.com<mailto:melinda.shore@gmail.com>> wrote:

On 6/12/16 10:06 AM, Ted Lemon wrote:

This is a great idea, but would require a lot of regular IETFers to sign
on and get support for going to those meetings.

I'm not sure it's a great idea.  IETF meetings are working
meetings, not conferences, and I'm not sure that having
additional meetings for people who are not active contributors
without the presence of chairs and document editors is going
to be productive, either in terms of the primary goal of
moving documents along or in terms of a secondary goal
of broadening the participant base.

Melinda