Re: [Iot-onboarding] Tell us about your BOF proposals

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 18 December 2018 16:42 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: iot-onboarding@ietfa.amsl.com
Delivered-To: iot-onboarding@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 172C3130EDE for <iot-onboarding@ietfa.amsl.com>; Tue, 18 Dec 2018 08:42:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level:
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[GB_ABOUTYOU=0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 QjGHgiD-VQqB for <iot-onboarding@ietfa.amsl.com>; Tue, 18 Dec 2018 08:42:55 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E72C8130F15 for <iot-onboarding@ietf.org>; Tue, 18 Dec 2018 08:42:54 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id A6B072008C for <iot-onboarding@ietf.org>; Tue, 18 Dec 2018 11:42:47 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id C77CBB5D; Tue, 18 Dec 2018 11:42:53 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id C52DF2BA for <iot-onboarding@ietf.org>; Tue, 18 Dec 2018 11:42:53 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: iot-onboarding@ietf.org
In-Reply-To: <C3A738F8-3922-492A-92A4-856B60271D29@ietf.org>
References: <C3A738F8-3922-492A-92A4-856B60271D29@ietf.org>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Tue, 18 Dec 2018 11:42:53 -0500
Message-ID: <1836.1545151373@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-onboarding/6anT9tNhW4GLmbmFJEBuCGAt-sM>
Subject: Re: [Iot-onboarding] Tell us about your BOF proposals
X-BeenThere: iot-onboarding@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <iot-onboarding.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iot-onboarding>, <mailto:iot-onboarding-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iot-onboarding/>
List-Post: <mailto:iot-onboarding@ietf.org>
List-Help: <mailto:iot-onboarding-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iot-onboarding>, <mailto:iot-onboarding-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2018 16:42:57 -0000

I think that we should propose a non-WG forming BOF for IETF104.

I would very much like to see some presentations on what exists, with a focus
on commonality of requirements or commonality of mechanisms.  
The idea would be see if we can identify groups or concerns.

BRSKI, at least, needs to have some applicability statements written for it
if it is going to be useful outside of the ANIMA ACP.  And of course there
is the consumer situation and/or the promicuous Registrar situation.
(I'd like a different term though)


IETF Chair <chair@ietf.org> wrote:
    > For those interested in bringing new work or new ideas to the IETF, we
    > are now accepting proposals for "Birds of a Feather” (BOF) sessions at
    > IETF 104. Instructions for submitting your proposal are available at
    > https://ietf.org/iesg/bof-procedures.html. Please also read
    > https://tools.ietf.org/html/rfc5434, Considerations for Having a
    > Successful Birds-of-a-Feather Session, if you are not familiar with
    > it. IETF 104 will take place March 23-29 in Prague, Czech Republic.

    > If you are working on a BOF request but you’re not quite ready to
    > submit it, please tell the IESG now by sending an email to
    > iesg@ietf.org to get advance help with the request. We have a number of
    > ways of bringing new work into the IETF and BOFs are just one of them,
    > so please talk to the IESG or an individual area director
    > (https://ietf.org/iesg/members.html) about your idea if you’re thinking
    > about proposing a BOF.

    > Thanks, Alissa Cooper IETF Chair


    > ----------------------------------------------------
    > Alternatives:

    > ----------------------------------------------------

-- 
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-