Second IETF 116 HotRFC Talk Solicitation

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Sun, 26 March 2023 03:30 UTC

Return-Path: <spencerdawkins.ietf@gmail.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 27800C151546; Sat, 25 Mar 2023 20:30:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.084
X-Spam-Level:
X-Spam-Status: No, score=-2.084 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_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 CS6DivHNMhoK; Sat, 25 Mar 2023 20:30:20 -0700 (PDT)
Received: from mail-pg1-x536.google.com (mail-pg1-x536.google.com [IPv6:2607:f8b0:4864:20::536]) (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 3EE88C1516E3; Sat, 25 Mar 2023 20:30:20 -0700 (PDT)
Received: by mail-pg1-x536.google.com with SMTP id x37so3305717pga.1; Sat, 25 Mar 2023 20:30:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679801419; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=03LV9wZgiImOsND3J8LDQfcEx+rPdNgQP5haDPZbZao=; b=MhL12WQwwNL1xIoAEiVuXAjSkM9JqWyauwmLvUjGuPrQz0qSojPCc1tTvvbUGSLh8W P3VmdoPV7jb9Y6kZkiLiGupEXjPopkAZL++XgtARn+bY9n6rfJ8oaknj+8OWr6bxx7gK hrl24giS0MLdn6aw8jQICeuaU+28WfoJOFjL23kzceaA42xC8Ivqh5d0H85zvNltl3uR TGxF35byReorOXdFgW0RJLvXn1li1e72hBFOtrZb+7CB0FAnR+UdAvWpYHtMuRTGvU7A UtPfgpqFf47f0ZaWbhjaiuzybM/FZxblPB9djJaLJxms6Nd5xw2eGizdfsTYmYB3Rti1 X3aw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679801419; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=03LV9wZgiImOsND3J8LDQfcEx+rPdNgQP5haDPZbZao=; b=yeTgA6xc+NUGaTtsCSha6V0UAb3epDoPovA4G7MQ2EBt3o4g7UePDRwibQt6WbwZH7 Sve4ovwDPkBUWaSVrrbVgL43tPj80zly45/Lms2RWxrJquRFZvddqB9KrZNu3yubIlwV XrDpUbOs8c92n5QNk1uY8wO6yDlywnRLRKtfAmuKsxuZTCLCPNXG+ngqnXRuL/o+kZJX rL8gHmYP3ZS5RLDOtipoLp6XhEGR1iQ/8X249Zj7CDMvRVdm+/X1GsG8pZ9lGd6wejol +Yb0pLoGdtTyXw5v64+9a7HskOJZ9QPAaK84D4KiC3iLG/zpGkc1X+fnVrlZkID22rnz oFCA==
X-Gm-Message-State: AAQBX9fzxknwYOrB2mGZR/2kzsNbReyjfwtpCAmgds+KiElz+ZIV4csU a6gOfGyqNzytZ8lLQLibBsUIv5KrCQSSadylYsF097C/2NVyww==
X-Google-Smtp-Source: AKy350augPoWa7WtyLPrkCseQAgmXgBvDntCBPUizUOg+g04Ty5ks8EqEekVEiI9225CM1f5tNlF2p0KlSKnz5QzhRA=
X-Received: by 2002:a05:6a00:894:b0:606:a4bd:8dde with SMTP id q20-20020a056a00089400b00606a4bd8ddemr4189441pfj.4.1679801418768; Sat, 25 Mar 2023 20:30:18 -0700 (PDT)
MIME-Version: 1.0
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Sun, 26 Mar 2023 12:29:52 +0900
Message-ID: <CAKKJt-d7t6eXhM+xc6HcrX_nV_OHHMDUuUu-fHvdzZ7kt4Cxdg@mail.gmail.com>
Subject: Second IETF 116 HotRFC Talk Solicitation
To: 116attendees <116attendees@ietf.org>, IETF list <ietf@ietf.org>, IRTF Discuss <irtf-discuss@irtf.org>, WG Chairs <wgchairs@ietf.org>
Cc: HotRFC Coordinators <hotrfc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000dbe43405f7c53e0a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oLXfHtYH4l2ooQC0N8SrNV4MpHA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <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: Sun, 26 Mar 2023 03:30:24 -0000

We have realized that people who crossed the international date line within
the past 24 hours were on a plane when the deadlines to request slots for
this IETF's HotRFC session and provide slides happened.

Because we want to Do The Right Thing, we are accepting late requests until
1500 Japan Standard Time. Any slides must be submitted with your slot
request - otherwise, you'll be speaking with your request showing.

And we're looking forward to tonight's session.

------------------------------

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 else 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 conversations.. 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 purposes, including:

   -

   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 BOF, 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 current hybrid IETF meeting format, we’re going to keep things
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, March 24th, 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, March 25, 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, March 26, at 1800 Japan Standard Time, in
room G302

   -

   All talks will be presented live, whether in-person or via MeetEcho
   -

   Video of the session will be recorded for later viewing.

Spencer Dawkins and Liz Flynn 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/116/sidemeetings.