Re: [irsg] reception not useful for WG chairs

Marie-Jose Montpetit <marie@mjmontpetit.com> Mon, 06 May 2019 15:09 UTC

Return-Path: <marie@mjmontpetit.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 27C551201AF for <wgchairs@ietfa.amsl.com>; Mon, 6 May 2019 08:09:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mjmontpetit-com.20150623.gappssmtp.com
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 goHM3ZLyB3pK for <wgchairs@ietfa.amsl.com>; Mon, 6 May 2019 08:09:17 -0700 (PDT)
Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74A7F120203 for <wgchairs@ietf.org>; Mon, 6 May 2019 08:09:10 -0700 (PDT)
Received: by mail-qt1-x829.google.com with SMTP id d13so15086550qth.5 for <wgchairs@ietf.org>; Mon, 06 May 2019 08:09:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mjmontpetit-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=OzQyxZB4EjQE1yt752AnS/0QsOE24856cnIvTtX6gTY=; b=F329kqH0uGzfkvsko7FDPJgYGLRmH1cQcYHasK17F3AZXNwt9qbdizyVZrS7u/c5b8 eiORSoc0FOhiIeuFmTvpoFJJmOJUBiqsNPaGCL80BXtoRY+3gJCyJyVewCxKo+gleoGA +t8Sf0I4ZMlWPmlhYzViIyTTmWl9TFr5W9Sv/vH9p7WuHX0y821+5hQY6aIYRpbbVPTa Q57EXZR7eobExoRdbvowfTovZFPrTit5Hjw2wN2ujvdBpjzX9mQCwvfZleAVe7xGYM64 pKafbGZxWZ5MD6+IxAOOLEbNuAIbPFAXhaQmuHO37lRod8/g2ziAn5TufV55812z57Y/ tAxw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=OzQyxZB4EjQE1yt752AnS/0QsOE24856cnIvTtX6gTY=; b=IXABu3cPlMCgxUxP7vAftLJ+rTKPECbppryFeCnEx8KRtHrWK5tIwIssgs8K7mq3UH x9Ic4wJ1hwMLP4ltf8n48eYOF55J0Y1blsUhkstvQo+PKweJavfe3LFMAY6JweQyZZFT 2nyUeFhLXqGInwsbqEzrr7yFk8s2pR1eAsd3JmDbqZQlc9+CZUSJ+PC9GhM6LwEayuc7 5hoc7Okmyt/3luSshKtdy9juq9vRT7a3yKwAzwvOFtOZSVCT70vj3jEIPcZzy56I0z1f feGoOEHQfwp+80wkknclHlM/K48Zc8XCCcTYg/d1QrQ34tMYI3roibrBbUHf8goPvmfc 5ktQ==
X-Gm-Message-State: APjAAAUGrN0cj5fj+UBrm24VSM2lAaHHB8A0TDOg/6vzxXiv8KaWRxBI DTd0NBK2TCnzh8VB2KZKObKIUQ==
X-Google-Smtp-Source: APXvYqw3Bh/c3S8JeufsFDi6yrCHnHnidXzC1w+1lAHfwkAxVWpbVXeQkcXq4JC7auI4P6GX+C0giQ==
X-Received: by 2002:aed:2196:: with SMTP id l22mr22085830qtc.226.1557155349466; Mon, 06 May 2019 08:09:09 -0700 (PDT)
Received: from heidi-lamarr.fios-router.home (pool-173-48-150-213.bstnma.fios.verizon.net. [173.48.150.213]) by smtp.gmail.com with ESMTPSA id x125sm3771659qkd.6.2019.05.06.08.09.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 May 2019 08:09:07 -0700 (PDT)
From: Marie-Jose Montpetit <marie@mjmontpetit.com>
Message-Id: <2493376E-3A12-4023-8EA8-F5712338718A@mjmontpetit.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8A0A4182-60EA-4C56-9FE7-EE3AF5371F66"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: [irsg] reception not useful for WG chairs
Date: Mon, 06 May 2019 11:09:06 -0400
In-Reply-To: <20190506145757.GC19509@kduck.mit.edu>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "wgchairs@ietf.org" <wgchairs@ietf.org>, "iab@iab.org" <iab@iab.org>, The IESG <iesg-secretary@ietf.org>
To: Benjamin Kaduk <kaduk@mit.edu>
References: <FFCF22D3-9D23-4B4F-A9B3-F8AA22A09CC0@isoc.org> <56EE9746-6023-4458-B7C2-0C7B4D879BD7@gmail.com> <4A95BA014132FF49AE685FAB4B9F17F66B3B367D@sjceml521-mbs.china.huawei.com> <CE03DB3D7B45C245BCA0D2432779493630556890@MX307CL04.corp.emc.com> <1756.1557154162@localhost> <20190506145757.GC19509@kduck.mit.edu>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/n6csop6-Ma8Zj73eaRdBcW3kY4s>
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, 06 May 2019 15:09:22 -0000

Well it seems this begs for an informal meeting of chairs. Right now the WGs chairs have a dinner and us RG chairs have ours. And there is the Wednesday lunch but it is not really a networking event  (and I am not criticizing it - it made me recognize the usefulness of github) . Maybe we need an informal meeting? The Systers have a cross WG/RG meeting that is successful. And I usually host a cross-WG/RG party but it’s not enough. Maybe a Sunday meeting at the time of the newcomers and ahead of the general get together would be good?  I would welcome cross-fertilization between IRTF-chairs and IETF-chairs.

Just a Monday morning idea!

Marie-Jose Montpetit, Ph.D.
Affiliate, MIT Media Laboratory
mariejo@mit.edu
marie@mjmontpetit.com
+1-781-526-2661
@SocialTVMIT



> On May 6, 2019, at 10:57 AM, Benjamin Kaduk <kaduk@mit.edu> wrote:
> 
> On Mon, May 06, 2019 at 10:49:22AM -0400, Michael Richardson wrote:
>> 
>> I'm hearing that the Sunday Reception is inadequate for WG chairs to
>> catch up with Area Directors, and that many people would like some structured
>> time in which to be able to do that.
>> 
>> Personally, I've found the reception to be very much useless for awhile.
>> Long food lines, and then food which I don't really like.  I've been skipping
>> it, or showing up at the very end just to say hi.
>> And now we schedule the HotRFC more or less on top of the end of the
>> reception.
> 
> IIRC we got some explicit feedback that overlapping HotRFC with the tail
> end of the reception was a feature.
> 
> -Ben
>