IETF Logo Mail Archive

Re: [Secdispatch] IETF117 - Call for topics

David Woodhouse <dwmw2@infradead.org> Fri, 16 June 2023 07:20 UTC

Return-Path: <BATV+ffaa6323489d449b93e9+7236+infradead.org+dwmw2@casper.srs.infradead.org>
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 25288C151B16 for <secdispatch@ietfa.amsl.com>; Fri, 16 Jun 2023 00:20:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.094
X-Spam-Level:
X-Spam-Status: No, score=-7.094 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=infradead.org
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 Agm1fE7lkMbk for <secdispatch@ietfa.amsl.com>; Fri, 16 Jun 2023 00:20:12 -0700 (PDT)
Received: from casper.infradead.org (casper.infradead.org [IPv6:2001:8b0:10b:1236::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 F0953C151B0F for <secdispatch@ietf.org>; Fri, 16 Jun 2023 00:20:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=MIME-Version:Content-Type:References: In-Reply-To:Date:To:From:Subject:Message-ID:Sender:Reply-To:Cc: Content-Transfer-Encoding:Content-ID:Content-Description; bh=meRW0y78YsPHhNpfjqMcAt8BiGIvJvexRsc/a/nUWAI=; b=lqAIr2OUAJeVO03O2eRxIlhVWw ox6++xrqkO8YaU5lPrzGSmVOiJ6DufYp0EjTXYcTCiNVJc9TJXwH32KYudTGFYj2bUEzUsORSxt2Z pS7svv9U/7DN4JBduJsr03ydONtXIbozzHSkzVKcfiWDEXZYM1qgjc2w5OvT30UKopBsh60x8JpNf YWmgfFEBzqbU1P7EAGORzLypTcF32wktCCCpXH63dDUBy8KbZ1+AgC+uDld0HfI0b/y6J0O4FmOLz 3RlH+yJJ31XJTt1IjLUZ2dJu6pLfuhP0wTftzx+0/r9EbOJMKpGY/LGHhe5E9kk/U6WRXy6XJMUre yW/Z+JAA==;
Received: from [2001:8b0:10b:1:bf9f:3fe9:8c6f:7b00] (helo=u3832b3a9db3152.ant.amazon.com) by casper.infradead.org with esmtpsa (Exim 4.94.2 #2 (Red Hat Linux)) id 1qA3kb-008fM4-O2; Fri, 16 Jun 2023 07:20:05 +0000
Message-ID: <2fa5cb785cea28430b11cb56a9f58a6c83da12e8.camel@infradead.org>
From: David Woodhouse <dwmw2@infradead.org>
To: Rifaat Shekh-Yusef <rifaat.s.ietf@gmail.com>, secdispatch <secdispatch@ietf.org>
Date: Fri, 16 Jun 2023 08:20:05 +0100
In-Reply-To: <CADNypP8D_qp6fPvWkWnw7hDRppHSkaxpTSBtMbcRkE+ZpS+WBw@mail.gmail.com>
References: <CADNypP8D_qp6fPvWkWnw7hDRppHSkaxpTSBtMbcRkE+ZpS+WBw@mail.gmail.com>
Content-Type: multipart/signed; micalg="sha-256"; protocol="application/pkcs7-signature"; boundary="=-qGAbt9ut3WBbBuaAY3I4"
User-Agent: Evolution 3.44.4-0ubuntu1
MIME-Version: 1.0
X-SRS-Rewrite: SMTP reverse-path rewritten from <dwmw2@infradead.org> by casper.infradead.org. See http://www.infradead.org/rpr.html
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/m-QJmFv0ZHuoyPAY4ZVMkEWN9UM>
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: Fri, 16 Jun 2023 07:21:30 -0000

On Thu, 2023-06-15 at 13:45 -0400, Rifaat Shekh-Yusef wrote:
> 
> We have requested a one hour slot for IETF117, which allows us to discuss up to 3 topics.
> Please, let us know as soon as possible if you have topics that you would like to discuss.

I posted here last week in an attempt to start a discussion about best
practices for applications using X.509 client certificates:

https://mailarchive.ietf.org/arch/msg/secdispatch/NT7aZdmTWPWKbeQb4ICmuvkvnyk/

(tl;dr: the lack of consistent support in applications confuses users
and hurts adoption of secure methods of key storage like TPM and
PKCS#11. Having an informational document outlining higher expectations
isn't a panacea but it would help to have something we can reference
when filing bugs.)

I'm utterly unfamiliar with the processes here.

Is it appropriate / useful to respond to your message above, suggesting
we discuss that topic?

v2.23.0 | Report a Bug | By Email