From nobody Thu Oct 24 11:15:06 2019 Return-Path: X-Original-To: 106attendees@ietfa.amsl.com Delivered-To: 106attendees@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B221C120100; Thu, 24 Oct 2019 11:14:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.997 X-Spam-Level: X-Spam-Status: No, score=-1.997 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_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 6nmxigq34-6p; Thu, 24 Oct 2019 11:14:48 -0700 (PDT) Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (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 43987120044; Thu, 24 Oct 2019 11:14:48 -0700 (PDT) Received: by mail-qt1-x82c.google.com with SMTP id e14so19476466qto.1; Thu, 24 Oct 2019 11:14:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=rMI3h7IIDkuiFhFjjh8rr7SlrdB3qusT/rbhqcVN3Fo=; b=kF2V2o0ocQBUG+Kt3T30TRP9R05E8WRKijIyyHY7UZn3YGEohC3uYJhZEESGES5U3M Z4nB4UKGck1FioJsYi+4/TqDJSy/OwwHX5/so1dL2bhGxSpcf4Ul9dJd9dug6P87u4Gt 61lk/IgNBpE+BxQ2I+3Ykt7S2s2GC6QDSvq3JUtsOiVVPmZJgNKg+1U5xg+gdHvIOm2l e4OGPB2OSVa+OnA+FEUr8IGmZ3KOob9772FULBFZQcACd6yyJkyEQMI7mBMMIsiCAa+Z 5BrMV+P3IdPDS6I6ztLfkRnBwV7OmT0GENHfJ1HNdoMM4L2zJXtGd3Z5EH9O7zZv7IJa MgRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=rMI3h7IIDkuiFhFjjh8rr7SlrdB3qusT/rbhqcVN3Fo=; b=cVtuKvpVI94gysjs9n2IUyRZUhXK++4QI835MqAJjeHTrTZ1yaNJQyr5vR6Pv0W4AD PXbo2I11Upq/P3gocIoVRA+jcyuzVUruVIHW0HATa6wjuxmaKA8O7JG09Fa8LFc+99B8 NTSci1pRiUlNdtncd3dy8wuTvKbaJWucTUmgoPbMTwwH5PU+0z+EQwyfc3haPUo0j16w FqRqKlBU/QgvtYj0iIqi3ikci0IB6uXCu47z8UarH+2oS3QLE8tiTr1H+0LX7zFENm3l l3XUsrymlH6/RjZvVNlsDle48v32OBJkZsYxSVys+RsrCK/qA1Zi6Y4P5iwtKsYLS/mU /qcg== X-Gm-Message-State: APjAAAVhMkuydvIGZVLk33LsvM0TIVUoGM7hpi20SBNstgSF0BCcEkbo bGxJ6b4Woe1EBvfqc2DAgmU= X-Google-Smtp-Source: APXvYqy0cU6g+pIPgxe1s3aLjlKBDDzW8v9yftYcO+mRC7N46PaZslFuzl7It+tnTc1P8NeixdYNNA== X-Received: by 2002:a0c:d983:: with SMTP id y3mr2842090qvj.52.1571940886696; Thu, 24 Oct 2019 11:14:46 -0700 (PDT) Received: from [172.19.32.162] ([2001:4878:a000:3000:1d3a:51d3:33fb:c18c]) by smtp.gmail.com with ESMTPSA id r126sm12452257qke.98.2019.10.24.11.14.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Oct 2019 11:14:45 -0700 (PDT) From: "Aaron Falk" To: "IRTF Discuss" , "IETF WG Chairs" , "IETF Discussion" , 106attendees@ietf.org Date: Thu, 24 Oct 2019 14:14:43 -0400 X-Mailer: MailMate (1.13r5655) Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_MailMate_EF0B9126-ADD4-4575-B129-730B41595A5C_=" Content-Transfer-Encoding: 8bit Archived-At: Subject: [106attendees] CFP: Request for Conversation (HotRFC) lightning talks @ IETF-106 X-BeenThere: 106attendees@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Mailing list of all 106 attendees for official communication <106attendees.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Oct 2019 18:14:52 -0000 --=_MailMate_EF0B9126-ADD4-4575-B129-730B41595A5C_= Content-Type: text/plain; charset="UTF-8"; format=flowed; markup=markdown Content-Transfer-Encoding: 8bit *Do you have an idea, problem space, or proposal that IETFers should hear about? Do you want to propose IETF 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 get 4 minutes and a few slides to make their case for collaboration. Interested folks can continue the discussion afterwards and over the week. Goals include encouraging brainstorming conversations, helping new work ideas to find co-collaborators, raising awareness of relevant work going on elsewhere, and promote BarBoFs. The session will be Sunday, Nov 17, 6-8pm (starting 1 hour after the welcome reception begins). Request a slot by sending a short abstract to hotrfc@ietf.org. See https://www.ietf.org/how/meetings/106/hotrfc/ for more details. Scheduled talks are listed in the [HotRFC agenda page](https://datatracker.ietf.org/doc/agenda-106-hotrfc/). --=_MailMate_EF0B9126-ADD4-4575-B129-730B41595A5C_= Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Do you have an idea, problem space, or proposal that = IETFers should hear about?
Do you want to propose IETF work but aren=E2=80=99t sure if your idea is = ready or who will be interested?

Agenda requests are now being accepted for the Request fo= r Conversation (HotRFC) lightning talk session. Presenters will get 4 min= utes and a few slides to make their case for collaboration. Interested fo= lks can continue the discussion afterwards and over the week. Goals inclu= de encouraging brainstorming conversations, helping new work ideas to fin= d co-collaborators, raising awareness of relevant work going on elsewhere= , and promote BarBoFs.

The session will be Sunday, Nov 17, 6-8pm (starting 1 hou= r after the welcome reception begins).

Request a slot by sending a short abstract to hotrfc@ietf= =2Eorg. See https://www.ietf.org/how/meetings/106/hotrfc/ f= or more details. Scheduled talks are listed in the HotRFC= agenda page.

--=_MailMate_EF0B9126-ADD4-4575-B129-730B41595A5C_=--