IETF Logo Mail Archive

Re: Reminder: IETF 111 Birds of a Feather (BOF) proposals requested by 28 May

Phillip Hallam-Baker <phill@hallambaker.com> Fri, 07 May 2021 16:41 UTC

Return-Path: <hallam@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 4623D3A2951; Fri, 7 May 2021 09:41:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 I5UILMrls5Em; Fri, 7 May 2021 09:41:19 -0700 (PDT)
Received: from mail-yb1-f180.google.com (mail-yb1-f180.google.com [209.85.219.180]) (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 B5E8E3A2942; Fri, 7 May 2021 09:41:18 -0700 (PDT)
Received: by mail-yb1-f180.google.com with SMTP id r8so12688079ybb.9; Fri, 07 May 2021 09:41:18 -0700 (PDT)
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=deEpEPbpDhcysrIOOWKbvOC+ILZxeuvli6O512sdT94=; b=JxWPyABSa7OPvmCu9ioiB7bR9Im8cJv/rBGusOHT1yompQsCiDLp5sVeSuOnKVJbQj U0mD1Q6pYZQdA7l+bRcxPvE+ef4q51G8n2v/6Qi8qoX++w6M0joCt/jFvaxlnqIOo1eT d8XhZZ1QUzmvwaoxNNwSIgcq9es9chI0GgZ24UbUh/cOOOvFt8wtRwECYR+gAPZpdG00 j2M4V2o5IL4v7zShoV7KZglSQjn39VfYIrQ729NcKBAWT0P6edAJa1tQM1H8NVYF1G4h mLhD7PwPICTnudaZ5HJzXceA4n0wNAGK1tMs2YEEA+fhYvupSeuilfRxz7Imqkttmn59 kbeQ==
X-Gm-Message-State: AOAM532IRF0rzp63jkIh2McABx0FC2cQg7LlYff4GLTixEpJ1RUok+cq HtEI80uH6o1vioRB/AvxhGQ69rfg3qe1ANm+o3A8RIWiNiA=
X-Google-Smtp-Source: ABdhPJxVAS2tAzSjvgsUaCT8+nGRrvnWGZAqpcsW16yF6CM1hsE8RR0EUMQK4+OgqcvFHWyAhl5i4dZKSJLeY0DLHNE=
X-Received: by 2002:a5b:585:: with SMTP id l5mr14160365ybp.213.1620405677563; Fri, 07 May 2021 09:41:17 -0700 (PDT)
MIME-Version: 1.0
References: <AA65C388-6410-4355-ADFF-8FD33AA0A01E@ietf.org>
In-Reply-To: <AA65C388-6410-4355-ADFF-8FD33AA0A01E@ietf.org>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 07 May 2021 12:41:07 -0400
Message-ID: <CAMm+LwgdLSS6NOt0cs8cV6L9Xa_eZui=gV=RwnjqeXo9Dw861g@mail.gmail.com>
Subject: Re: Reminder: IETF 111 Birds of a Feather (BOF) proposals requested by 28 May
To: The IESG <iesg@ietf.org>
Cc: IETF-Announce <ietf-announce@ietf.org>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cda38505c1c01849"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uBWHVpAcKFJF7cCJCzQDK13yVzI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <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: Fri, 07 May 2021 16:41:34 -0000

Is there a process for proposing/announcing virtual bar BOFs?

With QUIC set to be published, there are quite a few folk who are
interested in alternative approaches that meet very different use cases and
take approaches that are outside the QUIC design constraints. So while it
is not necessarily the case that any of that work will ever become a WG or
RG, there is a lot of experience that folk would like to discuss and
socialize.

For example, I have a scheme that is specifically designed for
transactional and streaming Web services that combines the capabilities of
TCP/HTTPS with those of SOAP+WS-Security. In the process, I think I
understand the original design mistake in the SOAP approach. This is
definitely not stuff you would want to support Web Browser use cases but it
is definitely stuff that is relevant to IoT and transactional services.

I am aware of at least three other transports, each optimized for slightly
different cases. This is the sort of thing we would usually meet in the bar
to discuss or hold a formal Bar BOF. It would be good to discuss under NOTE
WELL.



On Fri, May 7, 2021 at 7:28 AM IETF Chair <chair@ietf.org> wrote:

> Hi,
>
> this is a friendly reminder that preliminary proposals for
> Birds-of-a-Feather (BOF) sessions during the upcoming IETF 111 meeting are
> requested by 28 May 2021.
>
> The intention is to allow the IESG and IAB more time to work with BOF
> proponents to clarify and refine proposals ahead of the IETF 111 BOF
> proposal deadline on 11 June 2021.
>
> Instructions for submitting a BOF proposal are available at:
> https://ietf.org/how/bofs/
>
> Please also read https://www.rfc-editor.org/rfc/rfc5434, Considerations
> for Having a Successful Birds-of-a-Feather Session, if you are not familiar
> with it.
>
> BOFs are just one of a number of ways of bringing new work into the IETF.
> If you are considering a BOF request but you are unsure whether to submit
> it, please tell the IESG now by sending an email to iesg@ietf.org, or
> speak to an individual Area Director (
> https://www.ietf.org/about/groups/iesg/members/) about your idea.
>
> Thanks,
> Lars Eggert
> IETF Chair
>
>

v2.23.0 | Report a Bug | By Email