Re: [103attendees] HotRFC topics

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Tue, 30 October 2018 22:48 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: 103attendees@ietfa.amsl.com
Delivered-To: 103attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7590127133; Tue, 30 Oct 2018 15:48:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 0zUJykZgLUk4; Tue, 30 Oct 2018 15:48:39 -0700 (PDT)
Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (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 8AC00124BE5; Tue, 30 Oct 2018 15:48:38 -0700 (PDT)
Received: by mail-lj1-x22e.google.com with SMTP id a28-v6so9990269ljd.6; Tue, 30 Oct 2018 15:48:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/rj0ObnS7H4qOfrxS7Krjq+kOVvoW7/jo0ydB/QEYRM=; b=I1wK4pZgj1D1erEKYh/HbPcktylv6tOAIs8dgGOp1rJPhjenY6pUow603cosVnhoBa tlxQ/+4GSOWvhlSl8QZedLd2sK8D+FGonchqvhkRm9U5o7NACjCdyKGZs5W57yz8ZS/F W4kiAIEvnk8ySd64IPPOiYBAvMLTmJTuWjHZRfw61i5juCAFSnhWD3vzU/YvKAcFzA7k AYXv/7fgMSTH6iuAacHp9iqxzhAgqvzzAUbsgvQ1ESUYpLvAoL2fQMRu+vXMeUjbNosk a//HabvcvFvh1BPg+9vkraLXeCYIsuPBDqJv6AMKTpRdhI6lWvHRmCg2yU6Kwk1kThIr 6utA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/rj0ObnS7H4qOfrxS7Krjq+kOVvoW7/jo0ydB/QEYRM=; b=mSWPx2lOl9b5Q7kDXO4riJ4zQ/kBnFa7pyzuaN9Wh5Sk08dj4+z5ht90rZdQvxnrLV EbRg3vkgVOuC1xf40LKfQ/uejbJK7GLMCSesWKtNiesNE5IZxXO1toLH49mwtN+2cA1k wFLPI7GpTzxlm6ma9eul1KY46ksE363upNY5BQjGX6eyD3Jnfzph5ogJUdqRGHxb3p00 5SlMWJb184SFvV70yy3gTeyxfOuBG2UdZDI4ucLOWTh6IxSaBSPh5wCmEesO7z6dD96/ iBVw/Xn600zVdZl1BI7UEluI1Eu8kzbusMY+2tmhyOFlC9/NA98bMIosfoOW0xRqoJgy Wrow==
X-Gm-Message-State: AGRZ1gJ0qRN2l1TiDC6IVvs318Phg4EZa/JVzyeQz2j5ve0GQdomg/bM /Vz+UrQz1sygt4Xgru+mNIn1qIs4QSFXrghFa/U=
X-Google-Smtp-Source: AJdET5eALUUeygGrXy+WVym6/k+pkbR5qiLLguSARMH2IBRKMv3q3hIeiciUH18Z580d7IWbftdQ0d1qLja7DUhWX+M=
X-Received: by 2002:a2e:117:: with SMTP id 23-v6mr343692ljb.131.1540939716629; Tue, 30 Oct 2018 15:48:36 -0700 (PDT)
MIME-Version: 1.0
References: <882716F4-65E4-4C18-BF2A-F72F43F2393F@gmail.com> <BN3PR11MB0242B28D57690CBE0FD7B45990F30@BN3PR11MB0242.namprd11.prod.outlook.com> <D797E61F-BE35-4EFB-B1D4-3EE428D95133@gmail.com> <830FA0B1-AE38-4139-9C07-44DE8C0BE2B0@gmail.com> <20181030203655.GV45914@kduck.kaduk.org>
In-Reply-To: <20181030203655.GV45914@kduck.kaduk.org>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 30 Oct 2018 17:48:25 -0500
Message-ID: <CAKKJt-dRRdJu9Yakmqtcnt52qHSnhwTk1fdo9L7MjanwE7Y=iA@mail.gmail.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: joel jaeggli <joelja@gmail.com>, Aaron Falk <aaron.falk@gmail.com>, WG Chairs <wgchairs@ietf.org>, 103attendees@ietf.org, IETF list <ietf@ietf.org>, "Border, John" <John.Border@hughes.com>
Content-Type: multipart/alternative; boundary="0000000000006e1aaf057979fc7b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/103attendees/fqdgGkHClMwDvrhj0MvqgBf6IE8>
Subject: Re: [103attendees] HotRFC topics
X-BeenThere: 103attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list of IETF 103 attendees that have opted in on this list <103attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/103attendees>, <mailto:103attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/103attendees/>
List-Post: <mailto:103attendees@ietf.org>
List-Help: <mailto:103attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/103attendees>, <mailto:103attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Oct 2018 22:48:41 -0000

Just to add one point ...

On Tue, Oct 30, 2018 at 3:38 PM Benjamin Kaduk <kaduk@mit.edu> wrote:

> On Tue, Oct 30, 2018 at 01:31:27PM -0700, joel jaeggli wrote:
> >
> >
> > > On Oct 29, 2018, at 13:07, Aaron Falk <aaron.falk@gmail.com> wrote:
> > >
> > > It was not in Montreal. My understanding is that the Meetecho contract
> did not require rooms (or just our room) to be setup by Sunday evening.
> > >
> > Meetecho does cover Sunday tutorials / program events. but is not
> generally intended to cover after-hours / informal type events.  As this
> now appears on the agenda it appears to be edging out of the informal
> state, so possibly this is something we should raise via the iesg.
>
> The IESG had discussed making HotRFC a part of the regular agenda for this
> meeting, but ended up leaving it marked as an experiment, to get a bit more
> experience with the level of attendance and presentations we can expect.
> It seems likely that if/when it migrates from an experiment to a part of
> the regular agenda, remote access would be available (if not before then).


In conversations with Aaron Falk for the first HotRFC at IETF 101, the
initial theory was that HotRFC was letting anyone in the community say
"here's a topic, here's where it's being discussed, if you're interested,
follow me out of the room and we'll talk". March was a long time ago, but I
don't remember many, if any, questions/answers after each presenter, but
that's not surprising with 5-minute slots, which I believe are currently
now 4 minutes long (sorry, I'm sending e-mail while packing, so not
checking this).

Providing MeetEcho didn't seem useful for 4-minute slots, if someone was
not onsite and couldn't participate in any of the informal follow-up
afterwards. A remote attendee could see the titles, see the slides, and
follow-up on whatever looked interesting by e-mail, even if we didn't
provide real-time audio and video feeds.

There could easily be other theories, but please think about whether
changes will make HotRFC more heavy-weight, while people are thinking about
improvements.

Aaron did get a request for someone who wanted to present remotely at IETF
101, but NO ONE could follow that person out of the room for follow-up,
because they weren't in England. If "remote participation" also means
"remote presenters", that's also something to think about.

But we didn't have HotRFC before a year ago, so I'm sure improvements are
possible.

Travel safely,

Spencer