IETF Logo Mail Archive

Re: [Secdispatch] IETF117 - Call for topics

Yoav Nir <ynir.ietf@gmail.com> Thu, 22 June 2023 14:40 UTC

Return-Path: <ynir.ietf@gmail.com>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52D85C137393 for <secdispatch@ietfa.amsl.com>; Thu, 22 Jun 2023 07:40:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 4vseXnrgW9Wo for <secdispatch@ietfa.amsl.com>; Thu, 22 Jun 2023 07:40:29 -0700 (PDT)
Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (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 8B2C8C16952D for <secdispatch@ietf.org>; Thu, 22 Jun 2023 07:40:29 -0700 (PDT)
Received: by mail-wm1-x332.google.com with SMTP id 5b1f17b1804b1-3fa23c3e618so12211515e9.0 for <secdispatch@ietf.org>; Thu, 22 Jun 2023 07:40:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687444827; x=1690036827; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=W937ohj299qBv2oTBJll+f+bQEKqY4dyhusKl0d3+9w=; b=mqdn0vtaCZ43XV0rf8aTgWWSKmM+Uf0tippZj9a+J9SPoi+Jg58C7mPR7hwFdz2Apj 6A47f9U3R6pczr5VBygglLR1AO2ueMwy35VUmeJnWikvXlX/TSdGuG2YArvCTm8L1jMz bGklJzYyK+tm6aCk0aF65Zasy4/TwHX9HfN1SgCB2pF0+zrvNH4MekycpB6Lysx7vxDV DK5SBF4VcOLDTB9aDYugVQ814xcv8Gb71HHPYo5tVlxTOHeJNC2j1kJ+PUI3cZIpCAPa DEn3OHgS0PVgU8IsMpo0vq9Kq7y6f4t/5qKQDRzReiDmynlJsv85XuvzbbwtqIHpzF5T wSOQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687444827; x=1690036827; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=W937ohj299qBv2oTBJll+f+bQEKqY4dyhusKl0d3+9w=; b=S0hIWfjodWx8i8zYZ5sZGgf0l6h40zDTatB+vhKFdJ6WQ0E6VgZ++k9CrSJ9uoYWAC fPfm5Lo5e5Ai4CED47RyQIdevtpktdq7+IOIuTnGYjEkhzj2jrsVK7qJ6v/tFqf5FlE3 UZbMPJs6SbCANmQgmo8dr38c1k2QAtnHT2Z9CAsEhgisbuwXf/oBqL0y7B9AGEK62whx HDo5D58XAWTgkGL7ui4kgZkD1imxsk/YFzifzXYoPz2bGi6hl+BbBMuFa+5wYaIPogYE zCmD+PGWshDXoKWzTslg02AakU8rua2CobyVC4iZ4YIwDbCWXTTfcqK3iN4h27c2ocfF 1kbg==
X-Gm-Message-State: AC+VfDwfoygjnqzS5xaK3MfUeCOb/ulbdyqojlW7ueViTw4Y1eGCn1He kYkfN1HIFBStHE2vtfe+Ev4=
X-Google-Smtp-Source: ACHHUZ6LJeFlf+Cpl2wbJLZc6WWsc8CTBW1TEnGVHWSVn7cZ41oAjYgpPSLNcYUdbrF0nA9QThJbZg==
X-Received: by 2002:a05:600c:2501:b0:3f9:baf3:8d05 with SMTP id d1-20020a05600c250100b003f9baf38d05mr5087508wma.14.1687444827148; Thu, 22 Jun 2023 07:40:27 -0700 (PDT)
Received: from smtpclient.apple (84.94.37.215.cable.012.net.il. [84.94.37.215]) by smtp.gmail.com with ESMTPSA id y17-20020a1c4b11000000b003f7f249e7dfsm18137036wma.4.2023.06.22.07.40.26 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Jun 2023 07:40:26 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <54209.1687443106@dyas>
Date: Thu, 22 Jun 2023 17:40:14 +0300
Cc: David Woodhouse <dwmw2@infradead.org>, Rifaat Shekh-Yusef <rifaat.s.ietf@gmail.com>, secdispatch <secdispatch@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1943D5A5-71B2-42CC-8FD8-832CC1971E9D@gmail.com>
References: <CADNypP8D_qp6fPvWkWnw7hDRppHSkaxpTSBtMbcRkE+ZpS+WBw@mail.gmail.com> <3A66635D-6087-4D87-901A-A9C936A01C12@gmail.com> <CADNypP9h7TaC+VnmUihkcq3pWmqzuq3U1E9z4x3F_9PA8Vn8Aw@mail.gmail.com> <5b77f2aa7b39fe8add9bb6459db323609e2671e8.camel@infradead.org> <54209.1687443106@dyas>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3731.600.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/nd93yqoZhxSfUG3RIr9EpxDcWH4>
Subject: Re: [Secdispatch] IETF117 - Call for topics
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jun 2023 14:40:31 -0000


> On 22 Jun 2023, at 17:11, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> David Woodhouse <dwmw2@infradead.org> wrote:
>>> We have two confirmed topics already, and a 3rd is under discussion.
>>> Your topic would be the 4th.   At this point, it is not clear if the
>>> 3rd topic will be on the agenda, so we will keep you posted.
> 
>> If it helps, I'm happy to defer the discussion on
>> https://datatracker.ietf.org/doc/html/draft-woodhouse-cert-best-practice-00
>> to IETF118 in November. I stand a better chance of being able to make
>> it to Prague in person. And I've been sitting on this draft for about 7
>> years already; a few more months won't make any difference.
> 
> I'm not happy to defer... :-)
> getting it dispatched well means that we could have more/better conversations
> in-person in November about the document.

I tend to agree, and that it’s potentially very useful.

I also agree with Stephen Farrell that there ought to be a BOF about hybrid and/or dealing with CRQC, especially after the failure of the adoption call in LAMPS.  If this BOF is happening, or if there’s even a bar BOF at IETF 117 (as long as it’s not in an actual bar - I’ll be remote) I’ll be happy to take it there.

Yoav

v2.23.0 | Report a Bug | By Email