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:23 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 0E24D3A1107 for <t2trg@ietfa.amsl.com>; Mon, 20 Dec 2021 09:23:01 -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=unavailable 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 3N3nUDusRM67 for <t2trg@ietfa.amsl.com>; Mon, 20 Dec 2021 09:22:55 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B1223A1104 for <t2trg@irtf.org>; Mon, 20 Dec 2021 09:22:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 505A93917B; Mon, 20 Dec 2021 12:27:21 -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 xfw92if81Lga; Mon, 20 Dec 2021 12:27:20 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 2577339033; Mon, 20 Dec 2021 12:27:20 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1640021240; bh=jvQU7h66SqEO8LHiaiURIYU5CrE/rCUETn74h1qAUUE=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=hPD0UPpuOH2zksSPYEh5e3JFh/EoX+BZkV9/nb+6vpLeZVvR7RQ0ZrsH7jg1EUI2O f6vz4SaJgWhI4lqUnpwQqPEXuH6xsPTWA+Ke8sVCuGCI09byukAp3xOQegGr6ER4iU s8mtcYNFwUe1boWbc4u6Z/Xx6Vd5BZ2k5XLuqIJJxyiR+XDcZmXcIYIXADMuGhbAHN 2uP3ApTMOKuoDRFtf/rvrNS2UNa/QvSK98WFfT8hK/XiUDR78E8EmQETPpl002poO+ GQ/70zwGxXG5IvsS5UotMZ5CWY/smLUX4XqZXjD4C80zfTgQ80ZP6Ikqe0hIpQPX91 YQHaDUZY+Z1Wg==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 4068A1A25; Mon, 20 Dec 2021 12:22:50 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: =?Windows-1252?Q?G=F6ran_Selander?= <goran.selander@ericsson.com>
cc: Carsten Bormann <cabo@tzi.org>, "t2trg@irtf.org" <t2trg@irtf.org>, "core@ietf.org" <core@ietf.org>
In-Reply-To: <AM4PR0701MB2195A52DA79B1E88364BCAD7F47B9@AM4PR0701MB2195.eurprd07.prod.outlook.com>
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>
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:22:50 -0500
Message-ID: <2420.1640020970@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/pg8RP-RvDm7ivmFvEN_8uszsIS0>
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:23:01 -0000

Göran Selander <goran.selander@ericsson.com> wrote:
    GS> Maybe someone else thought about roadmaps, I was more thinking about
    GS> concrete problem statements. If the outcome is a T2TRG draft or a new
    GS> IETF WG draft (or neither) may depend on the problem.

I think of a document that says:

When you have condition1,condition2,condition3,
then a solution like: RFCXXXX suite 1, with RFCYYYY section 4, and use of
RFCZZZZ ... would make sense.

So, I think that the first part of the document is definitely a problem
statement, or perhaps more correctly called an applicability statement.

--
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