Re: [dispatch] Slight correction on minutes related to BARE

Kirsty Paine <kirsty.ietf@gmail.com> Tue, 26 July 2022 08:17 UTC

Return-Path: <kirsty.ietf@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AF00C15A722 for <dispatch@ietfa.amsl.com>; Tue, 26 Jul 2022 01:17:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Um6TmNahoq4O for <dispatch@ietfa.amsl.com>; Tue, 26 Jul 2022 01:17:52 -0700 (PDT)
Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (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 99C89C15A724 for <dispatch@ietf.org>; Tue, 26 Jul 2022 01:17:52 -0700 (PDT)
Received: by mail-pj1-x102e.google.com with SMTP id b7-20020a17090a12c700b001f20eb82a08so16601472pjg.3 for <dispatch@ietf.org>; Tue, 26 Jul 2022 01:17:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=SuOQuDpVUEnDhioI6tujDWgr1MhLr9sPXuez4VKX0O8=; b=Ze34hZq4YXn1ofAojnuqO1Gy48lVpLgID5beD3PEDwFiDysfMhyu7Qw4aGAkKKoqgH D8ocW8+YVbqnVSzFaFRzCUvyqFSxuOOGJNGMuq2gMPbNmdPyanKbZeQnjQaOS78RE1pr 3Le1dr9lizBGPWiF2jbfTLmbPp1Fv/e2ZnOzk5kCszP+akv24UhYrGl/kxuFUAnTePsp jBxEYwzmsztadTaQoLyhFrUzPxH+apMSkmv0oNLIZ0OKKX1HG8Xz//t5IAQ9jxBehFjy TTWog+WHiT7J8EB3YghbLSr5JXKfmUvHNPamiB3z8gXJoN/skRXbbJfyZphMkBvNO87M QTVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=SuOQuDpVUEnDhioI6tujDWgr1MhLr9sPXuez4VKX0O8=; b=gL9OdOLfM4JeN0YbOq6ZznduBRfa/j3+i8ljdiwohIsgyWoh4Tk2I2dJXLEvkLgY3m uFmJomS1M5qUUlo5yNAR00BDGGXrqe7QzLRF522x7407uwkjc8+SsngPQdCDp9g4YUHX Pd82iXNjziXdwuqdYO8bNBG4lrPn9s5LWYSDSErwU6yv4q57GrQe8ES3EVM8ovLwfBtN lhxJI4c40hJDKm8W2LI2vmb29jkREH1MjvG7dFx4B/59SFHeCLchOEHPzbHKqJfLLn95 WBzBQfmxoLaQLAlvk23g3m/KpkETBD9+j7FXlmRsAZeIK/xh5cw/dp3zFHs62t1WR85Y DFNg==
X-Gm-Message-State: AJIora+duwiTiTDlCeiIoKv9VYBv8pkZcLy/+ojiQjy4zMnXFv6Wsh4l 3lNQCRvprsIDEkjZC2HZPQHcWbckg2qLIDj5FZ/qqjFOlKqfxA==
X-Google-Smtp-Source: AGRyM1uY3jk0Im564hjcfR8uJejNlVue+VeiVNTdya4JN97YAIBmRAwpp9Edqay4UMz6ONjIcYv8mIeNdMIgZYFXJes=
X-Received: by 2002:a17:90b:1d91:b0:1f0:7824:1297 with SMTP id pf17-20020a17090b1d9100b001f078241297mr35552575pjb.126.1658823471991; Tue, 26 Jul 2022 01:17:51 -0700 (PDT)
MIME-Version: 1.0
References: <e228c409-d739-c123-7aaf-10e3349ef076@iii.ca>
In-Reply-To: <e228c409-d739-c123-7aaf-10e3349ef076@iii.ca>
From: Kirsty Paine <kirsty.ietf@gmail.com>
Date: Tue, 26 Jul 2022 09:17:41 +0100
Message-ID: <CAC9wnY_qhmECgC6QmvUAMKrjkzSbopA4dkEcjnLHSFv8xf0sbg@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Cc: "dispatch@ietf.org" <dispatch@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cb10be05e4b0ef74"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/D5d2f9rwmfrmO7Uw9QmAz04W7oA>
Subject: Re: [dispatch] Slight correction on minutes related to BARE
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2022 08:17:53 -0000

Hi Cullen,

Thanks for the feedback! We will update the minutes accordingly and also
watch the YouTube recording to get the fullest accuracy, and I'll also edit
the chair summary to be less ambiguous.

I'm also sorry to hear the audio in the room was not good, especially
alongside the other technical issues you and other participants faced.
Between the chairs, we also had some connectivity issues and therefore
difficulty checking minutes consistently throughout the session - before
the next time, we will think of better contingency plans for these and
other potential issues for a smoother session at IETF 115.

Thanks again,

Kirsty


On Mon, Jul 25, 2022 at 6:52 PM Cullen Jennings <fluffy@iii.ca> wrote:

>
> I think the minutes did not quite capture my input. I think we should
> have a small WG to write a standard that solves this problem. I don't
> care if the solution is BARE, or the TLS encoding, or slightly different
> MLS, or something else. Perhaps even have a bakeoff between them.
>
> I think the chair summary of saying only one company wanted this is not
> accurate. I was clear I would also want to use something like this in my
> drafts vs reinventing the wheel each time.
>
> It was really hard to understand what the remote chairs were saying in
> for the people in the room so my apologies for not catching this when
> you made your summary at the end.
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>