[Secdispatch] Re: [Alldispatch] IETF-Wide Dispatch – Call for topics

Carsten Bormann <cabo@tzi.org> Mon, 03 June 2024 15:56 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17B9DC180B6E; Mon, 3 Jun 2024 08:56:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
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 LK6gJapJq2Bg; Mon, 3 Jun 2024 08:56:31 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (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 78A9CC1840D2; Mon, 3 Jun 2024 08:56:27 -0700 (PDT)
Received: from eduroam-0016.wlan.uni-bremen.de (eduroam-0016.wlan.uni-bremen.de [134.102.16.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4VtJHX590VzDCdR; Mon, 3 Jun 2024 17:56:24 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <4780b9da32294f9ea7294a91c59802f6@huawei.com>
Date: Mon, 03 Jun 2024 17:56:24 +0200
X-Mao-Original-Outgoing-Id: 739122984.198632-3a2fd4759ab64014d4f4bd5cd391cc83
Content-Transfer-Encoding: quoted-printable
Message-Id: <234DBF8C-563E-4386-85F8-45F5EBF0BBD0@tzi.org>
References: <4780b9da32294f9ea7294a91c59802f6@huawei.com>
To: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
X-MailFrom: cabo@tzi.org
X-Mailman-Rule-Hits: max-recipients
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-size; news-moderation; no-subject; digests; suspicious-header
Message-ID-Hash: 3ASL267AXD3SO7X7CKRZWAWWCADSOC7G
X-Message-ID-Hash: 3ASL267AXD3SO7X7CKRZWAWWCADSOC7G
X-Mailman-Approved-At: Mon, 03 Jun 2024 08:59:48 -0700
CC: "Alldispatch@ietf.org" <Alldispatch@ietf.org>, secdispatch <secdispatch@ietf.org>, "dispatch@ietf.org" <dispatch@ietf.org>, "gendispatch@ietf.org" <gendispatch@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "ops-area@ietf.org" <ops-area@ietf.org>, "witarea@ietf.org" <witarea@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Secdispatch] Re: [Alldispatch] IETF-Wide Dispatch – Call for topics
List-Id: Security Dispatch <secdispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/mmrsZz92MyHpVp-cVnqbK-cIccA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Owner: <mailto:secdispatch-owner@ietf.org>
List-Post: <mailto:secdispatch@ietf.org>
List-Subscribe: <mailto:secdispatch-join@ietf.org>
List-Unsubscribe: <mailto:secdispatch-leave@ietf.org>

Hi ALLDISPATCH chairs,

> On 2024-05-31, at 04:12, Pengshuping (Peng Shuping) <pengshuping@huawei.com> wrote:
> 
> Please, take a look at the following SecDispatch Wiki for more information about what we are looking for when you submit your request: https://wiki.ietf.org/group/secdispatch

I’m not sure that I have included all items from this list in the original request [1] and the ensuing discussion.

[1]: https://mailarchive.ietf.org/arch/msg/alldispatch/OIecq3rv9HJA-SFC66d6bF6iUyE

So let me briefly do this here:

	• pointers to a draft(s)

[0]: https://www.ietf.org/archive/id/draft-bormann-gendispatch-with-expert-review-00.html

	• pointers to ongoing/prior discussions

See the thread at [1], plus the previous discussion e.g., at [2].

[2]: https://mailarchive.ietf.org/arch/msg/core/BENVbgmF0px40GPW-zlA4nHI8So

	• pointers to implementations

The “implementation” is in the draft [0], but there are also workarounds in [1a], [1b], [1c] in the form of common boilerplate:

[1a]: https://datatracker.ietf.org/doc/html/draft-ietf-core-oscore-edhoc-11#section-8.3-3
[1b]: https://datatracker.ietf.org/doc/html/draft-ietf-ace-revoked-token-notification-07#section-14.4-3
[1c]: https://datatracker.ietf.org/doc/html/draft-ietf-ace-revoked-token-notification-07#section-14.5-3 

	• pointers to any other background materials

One example for why we’d want to involve the designated expert even after IESG review is the registry defined in [2a] (see [2d] for some more technical details, which in turn are refined in [2b] and [2c]).

[2a]: https://www.rfc-editor.org/rfc/rfc7252.html#section-12.2
[2b]: https://www.rfc-editor.org/rfc/rfc7252.html#section-5.4.1
[2c]: https://www.rfc-editor.org/rfc/rfc7252.html#section-5.4.2
[2d]: https://www.rfc-editor.org/rfc/rfc7252.html#section-5.4.6

	• summarizing prior engagement with existing WGs

The most obvious WG is CoRE, but other WGs are also using registries with similar properties (see ACE above).

	• summarizing who would want to advance this work

Chairs and authors from CoRE and ACE

	• desired next steps

Choose a venue to progress [0]

	• desired time for discussion

10 minutes.

Note that the request is specifically for the proposal in [0]; the thread at [1] also contains additional suggestions that do not yet have such full proposals, but might very well merit separate discussion after some further development.

Grüße, Carsten