Re: [Fud] Brief update

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Mon, 13 March 2017 14:58 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: fud@ietfa.amsl.com
Delivered-To: fud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D3E212945B for <fud@ietfa.amsl.com>; Mon, 13 Mar 2017 07:58:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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_LOW=-0.7, 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 45UzilaKhEdq for <fud@ietfa.amsl.com>; Mon, 13 Mar 2017 07:58:52 -0700 (PDT)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (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 A4C181294F1 for <fud@ietf.org>; Mon, 13 Mar 2017 07:58:52 -0700 (PDT)
Received: by mail-yw0-x235.google.com with SMTP id v198so60436307ywc.2 for <fud@ietf.org>; Mon, 13 Mar 2017 07:58:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=mVwKo5Qy3waqLzBEiEyB8n2Rh/lF3Cr2z4DTnq6VyMo=; b=qWzYDHbLSpq6nL91Gwbi2l/UxF7urFiIIzsJH0axdUN7jbnDuJN/JXrBp66mY+9LSU rneTciTfeG9cYUSwI1UJWfmb7ogHj9Vz/8GmgQ04xFIeClSQq1n3pK9gxpoUED+LGZmb PgC/DoqWsHfKJbuMzG52oq8UYSK5+/1C0m4WllI/XQlQuJEDMrQVciAwFKqRqI2F/u+c XOAL0S4cSddH7qEe8JENOx9AL/1gj8w7lEW1yqIKYidGKFUW+0HOKWbJQYx8wl3LvKNv xWsMXM397UEb9FQlj7ICQtSrB3x5e7KIqLHkAzF03DUhz6sMac4JqHTAHuCAN5C1MrIl 6P3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=mVwKo5Qy3waqLzBEiEyB8n2Rh/lF3Cr2z4DTnq6VyMo=; b=O4i7/jVqMuUVF68J6yIGeBCUcBdfxUo1rKFIoBp1P8K99SdDy2W4oT8Cvs73k9Cu1C Ze5yFlM9AtBLDIxzHClHmwFfD4im7VndhnyrgK84/XXRx+++DT7Wm43ZAydYjS+3Qiyj TaPZr3xSDhKXQ5z4bZyFVzsuCxoF9Bm+O8wPIL74Y/x7pdPTRBnbaxw6pEaazkGjaJcI /pMCP5GUlDKEqDr8EwY5T2yI4UhlzpowWVIguYdmMx1w5uHfEfJGR8p+jN7nNVK7b8+x CvRbkdNl21evb11J/RClPQiODTyJK3+UipPTRWobm3u9c/Qqg4ovkpdp366+3E/7plqs g/WA==
X-Gm-Message-State: AMke39kCN/WgzFDSkmy8dOOhy3lEluROqT8lT8fhe2TgaiSYlzrNzR78nP8bNKcQfgLxUkM1cWYDvaYHYvgS4g==
X-Received: by 10.37.117.215 with SMTP id q206mr17295065ybc.58.1489417131760; Mon, 13 Mar 2017 07:58:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.77.197 with HTTP; Mon, 13 Mar 2017 07:58:51 -0700 (PDT)
Received: by 10.37.77.197 with HTTP; Mon, 13 Mar 2017 07:58:51 -0700 (PDT)
In-Reply-To: <af0fb520-3ad1-5679-2658-eb74cd3df159@gmx.net>
References: <af0fb520-3ad1-5679-2658-eb74cd3df159@gmx.net>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 13 Mar 2017 09:58:51 -0500
Message-ID: <CAKKJt-caAHF3hQ+xife-fF1yOqYY=efT_8Xv1VJb8sYdGRLzcA@mail.gmail.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Content-Type: multipart/alternative; boundary="001a114bb3480facc2054a9df30d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/fud/5YULcfQUItfaAMScCLo4ia1Xzxg>
Cc: fud@ietf.org
Subject: Re: [Fud] Brief update
X-BeenThere: fud@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: FUD - Firmware Updating Description <fud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fud>, <mailto:fud-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/fud/>
List-Post: <mailto:fud@ietf.org>
List-Help: <mailto:fud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fud>, <mailto:fud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Mar 2017 14:58:55 -0000

Hi, Hannes,

On Mar 13, 2017 09:21, "Hannes Tschofenig" <hannes.tschofenig@gmx.net>
wrote:

Hi all,

you may have seen that the IESG didn't appropriate the BOF for the
Chicago IETF meeting. However, I had received positive signals that
there is interesting in exploring the topic of firmware updates in the
IETF.


I would agree that you have people on the IESG who are interested (and,
although I can't speak for the IAB, I believe some IAB members who support
this as well).

If I were to characterize the discussion on the BOF coordination call, I'd
say that what we needed to see was more of the homework described in
https://tools.ietf.org/html/rfc5434, and especially things like:

   4) Have substantive mailing list discussion.  It is not enough for a
      handful of people to assert that they want a BOF; there needs to
      be broader community interest.  A public mailing list allows ADs
      (and others) to gauge how much interest there really is on a topic
      area, as well as gauge how well the problem statement has been
      scoped, etc.  At this phase of the BOF preparation, the emphasis
      should be on getting agreement on the problem statement;
      discussions about specific solutions tend to be distracting and
      unhelpful.


As a next step I will use the upcoming IETF meeting to schedule a BarBOF
with those interested in such an activity. I was thinking about some
evening during the week. Please use this Google poll to indicate your
interest and your preference:
http://doodle.com/poll/6df6cqwkhpcvfm8f


I don't think FUD is a candidate for TSV sponsorship, but I am interested
in encouraging this work as an IESG member. If it's helpful for people to
grab me for a side conversation in Chicago, please do.

Furthermore, I am producing a specification-style write-up of our
firmware update solution and I hope to have it in a readable form by the
IETF meeting.


Thanks,

Spencer

Ciao
Hannes


_______________________________________________
Fud mailing list
Fud@ietf.org
https://www.ietf.org/mailman/listinfo/fud