IETF Logo Mail Archive

Re: [T2TRG] [core] Quick Doodle T2TRG security topics (Re: New topic for T2TRG?)

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 20 December 2021 17:58 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: t2trg@ietfa.amsl.com
Delivered-To: t2trg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EFB33A040B for <t2trg@ietfa.amsl.com>; Mon, 20 Dec 2021 09:58:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, 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=sandelman.ca
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 pdQTDlLI6lW5 for <t2trg@ietfa.amsl.com>; Mon, 20 Dec 2021 09:58:22 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 612D73A03F7 for <t2trg@irtf.org>; Mon, 20 Dec 2021 09:58:22 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 351523954C; Mon, 20 Dec 2021 13:02:49 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id pX6SVaKXpo6Y; Mon, 20 Dec 2021 13:02:47 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id C683C3953B; Mon, 20 Dec 2021 13:02:47 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1640023367; bh=erBC2O8pf0gMgwa3VHIlLr8YrvgYK9qKf+++UPohdJA=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=uQZ+aRdyiczsCdztvHmoGZoyO7bIgqOR61fUzh08G3e/cj59fXO3OHzpbQd2D1xVm efurqLelY8cLYOMtlHKl++4A7aG6B4bxWaYwzTA+iME0RjZFq93unO6jA8/4aQMeT4 MUtAH0nq2EExEriKMuSf38/WzP1KzZWcCl8uGAlh/hN7thtQUd2yjgM9iqc184lmqW VMwCPnjCkd+4j6SnS/FFwNV6AHmZIdwzmAx1KPegTbrpipxHiy4VP7WPoPjBo4QTMc Ukj9MgNf0eSx+lImu9fMaimeBmlfrMC01JG5yRiYMiCZTfTXcG/veMBjoDDBrClsyE rXlViPv/SjAqQ==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id CA4EA1A25; Mon, 20 Dec 2021 12:58:17 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Carsten Bormann <cabo@tzi.org>
cc: "Apple Inc." <goran.selander@ericsson.com>, "t2trg@irtf.org" <t2trg@irtf.org>, "core@ietf.org" <core@ietf.org>
In-Reply-To: <EDAA4FFE-3B99-4F13-AB09-EA5E89ECB7A8@tzi.org>
References: <YYkUABLfpU/SRaxX@hephaistos.amsuess.com> <YYqfI38dg8035RLn@hephaistos.amsuess.com> <YZPGVxFc7AvdYXNB@hephaistos.amsuess.com> <AM4PR0701MB21955D1AB35A1A335B5EFDD0F4669@AM4PR0701MB2195.eurprd07.prod.outlook.com> <97ED3090-7BBA-4ED8-B50B-26C5AC863EB5@tzi.org> <25576.1640012067@localhost> <AM4PR0701MB2195A52DA79B1E88364BCAD7F47B9@AM4PR0701MB2195.eurprd07.prod.outlook.com> <2420.1640020970@localhost> <EDAA4FFE-3B99-4F13-AB09-EA5E89ECB7A8@tzi.org>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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-sha512"; protocol="application/pgp-signature"
Date: Mon, 20 Dec 2021 12:58:17 -0500
Message-ID: <13383.1640023097@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/crSGpRhjD_JM4k4B_JIsyGhuHDE>
Subject: Re: [T2TRG] [core] Quick Doodle T2TRG security topics (Re: New topic for T2TRG?)
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF Thing-to-Thing Research Group <t2trg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/t2trg>, <mailto:t2trg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/t2trg/>
List-Post: <mailto:t2trg@irtf.org>
List-Help: <mailto:t2trg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/t2trg>, <mailto:t2trg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Dec 2021 17:58:28 -0000

Carsten Bormann <cabo@tzi.org> wrote:
    >>
    >> applicability statement.

    > That word is taken (Section 3.2 of RFC 2026), so please don’t use it
    > unless you actually do mean this (rather unsuccessful) form of
    > specification.

    > https://datatracker.ietf.org/doc/html/rfc2026#section-3.2

I think that I really do mean this word in exactly the context given.
I agree that they have often been unused or ill-applied, but also often do
work.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email