[irtf-discuss] (Second Call) Requests for Conversation (HotRFC session for IETF 115 - talks solicited
Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Fri, 28 October 2022 20:36 UTC
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F29BC14CF0C for <irtf-discuss@ietfa.amsl.com>; Fri, 28 Oct 2022 13:36:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PH31L2A-R9mA for <irtf-discuss@ietfa.amsl.com>; Fri, 28 Oct 2022 13:36:46 -0700 (PDT)
Received: from mail-yw1-x1134.google.com (mail-yw1-x1134.google.com [IPv6:2607:f8b0:4864:20::1134]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7E64C14F720 for <irtf-discuss@irtf.org>; Fri, 28 Oct 2022 13:36:46 -0700 (PDT)
Received: by mail-yw1-x1134.google.com with SMTP id 00721157ae682-36cbcda2157so57411437b3.11 for <irtf-discuss@irtf.org>; Fri, 28 Oct 2022 13:36:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=6MZLk4FkvieXyGK0/WFZyX6i5NXZifBz+8NaOVQyb0Q=; b=Q2Ti4pyDPTFbPnuXFCU5gky2YKgnGEMq8KZknKF61AtZGXgaAe3oCT/lD29ddnOwLl L0eB4GHVjWz89qix0r0L9cC7iUXZA0soExupK02fcEq3zfGXz8cB5zbH+rVppd7p6vNv dvKBBJ9/BqWv+vAO59uPjAnB/DbUjY1aIJYq+3KKQxjmEm/ILO53HszLIuieQLHxwN3n hmA0wC2msUMnpmNdgDd3Y7Q95dYRS71xcvRYNt/ynv8aIIx6sMo2TZ1jkuPxK2f7VgYC BzhArmqaD6pjbIZ1pL9NR445P5UI1bDD+Nl4krlLXlAOMAHRvyipeU3D7RA1iMYI6/AZ QExA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=6MZLk4FkvieXyGK0/WFZyX6i5NXZifBz+8NaOVQyb0Q=; b=bOMSiWvOM5VREXYSGc1XiE5bYPIyVbemwIQcTLMFUc2gYc20fVKr7qZpqzDSB0+nJD oxQeVAhaDDhtBntz2ejDANYJpBpvC3CLubsHYC1zzugmR5fUnRoK+Im4cjv9hVu050L+ XzA1hQY9G3jPFSyq5WS+XVGntWmPvDVx/pIjG9i+3QVNhcxn5aG6JzrFj22d44en2D/d 4pNxa1K7tdnkopPoMotOUr6BeIA1d7cTe6JcJ5BryviVh//7KQjEQqWRCKoJq/ewAHGl tCdes8CbU1tpYx+PtI2MjuVkXSToALj3J8ttBGShyJbpHMWsx34Wb5ZrPB+ymAO+alVM iJzg==
X-Gm-Message-State: ACrzQf2YSQSxHfYenJAmhMR6I1OscMoqtOXeX2VqTh8or+fQsGkKSZc0 tWsn5KVfxFzjnK2by0Pa7wibGGohStL7MuqoBugGhrIpoS4=
X-Google-Smtp-Source: AMsMyM70uGt2ppMsUkYbtvAc6QPjwhcK7e0KzZOe7jtS0soqruPVVBohEVF+8WIaQXa2fndFjsY4z8NWKfP2aa9nqVg=
X-Received: by 2002:a0d:fa41:0:b0:348:7dc3:760a with SMTP id k62-20020a0dfa41000000b003487dc3760amr1245603ywf.106.1666989405419; Fri, 28 Oct 2022 13:36:45 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-cr_H0xfJL4Vabch80psrFkJL4a-w2=HgXtTT96bvN0Cw@mail.gmail.com>
In-Reply-To: <CAKKJt-cr_H0xfJL4Vabch80psrFkJL4a-w2=HgXtTT96bvN0Cw@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Fri, 28 Oct 2022 15:36:19 -0500
Message-ID: <CAKKJt-eO06reQ+jJwrECJH6=ENqDsSFohmo0oAekkkugR8=-pg@mail.gmail.com>
To: IETF Discussion <ietf@ietf.org>, Working Group Chairs <wgchairs@ietf.org>, IRTF Discuss <irtf-discuss@irtf.org>, 115attendees@ietf.org
Content-Type: multipart/alternative; boundary="0000000000005ac00b05ec1e37d6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-discuss/VSHrjbooJAqnsLK-xNWw-jev-yc>
Subject: [irtf-discuss] (Second Call) Requests for Conversation (HotRFC session for IETF 115 - talks solicited
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/irtf-discuss/>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Oct 2022 20:36:51 -0000
We have started receiving slot requests, and adding them to the agenda for IETF 115. But it's not too late to get on the agenda for *your *talk! Do you have an idea, problem space, or proposal that IETFers and IRTFers should hear about? Do you want to propose IETF or IRTF work but aren’t sure if your idea is ready or who will be interested? Agenda requests are now being accepted for the Request for Conversation (HotRFC) lightning talk session. Presenters will have 4 minutes to make their case for collaboration. Interested folks can contact the presenter and continue the discussion after the session. Goals include encouraging brainstorming conversations, helping new work proposers find collaborators, raising awareness of relevant work going on elsewhere, and promoting BarBoFs. Past HotRFC lightning talks have covered a broad range of topics: - Collaboration: proposals for new standards work or new research topics that haven't been discussed elsewhere, potentially relevant research that may be ready for the IETF - Notification: new topics on the agenda in a working group or research group, especially cross-area IETF work - Enlightenment: updates on relevant technologies, industry advances that could affect IETF participants. With strict time limits, concise talks will give viewers a sense of whether they’d like to know more and, importantly, coordinates on how to do so. With the hybrid IETF 115 meeting we’re going to keep things rather simple and permit only live presentations, either on-site or remote via MeetEcho. Slides must be submitted in advance. To request a slot, submit a short abstract to hotrfc@ietf.org no later than Friday, November 4th, 2400 UTC that includes the following - Talk title - Presenter, Affiliation, and whether you’ll be presenting in person or remotely - Short topic abstract (topics should be IETF- or IRTF-related in some way) - What you're looking for (education, collaborators, implementers, etc.) - Coordinates to learn more, contact those involved, participate in existing mailing lists and scheduled meetings, and/or relevant formal or side meetings. - Any relevant drafts or helpful resources you’d like collaborators to look at To provide slides, submit ppt or pdf to hotrfc@ietf.org no later than Saturday, November 5th, 2400 UTC. - Talk abstracts and slides will be posted on the meeting agenda. The agenda will be updated as requests come in. The session will be on Sunday, November 6th, at 1800 UTC in Kensington 1 - All talks will be presented live, whether in-person or via MeetEcho - Video of the session will be recorded for later viewing. Thanks to Spencer Dawkins and Liz Flynn, who will be hosting the session on-site. We hope you’ll tune in. -- the HotRFC team P.s. If you think holding a public side meeting would be useful for people who are interested in your topic, there’s a wiki for that, at https://wiki.ietf.org/meeting/115/sidemeetings.
- [irtf-discuss] Requests for Conversation (HotRFC … Spencer Dawkins at IETF
- [irtf-discuss] (Second Call) Requests for Convers… Spencer Dawkins at IETF