Re: [core] Using SVCB with OSCORE/EDHOC

Carsten Bormann <cabo@tzi.org> Sun, 26 March 2023 15:41 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E287C151B24 for <core@ietfa.amsl.com>; Sun, 26 Mar 2023 08:41:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 y85OMAjNAAGi for <core@ietfa.amsl.com>; Sun, 26 Mar 2023 08:41:21 -0700 (PDT)
Received: from smtp.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (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 9D3B3C151B0D for <core@ietf.org>; Sun, 26 Mar 2023 08:41:19 -0700 (PDT)
Received: from [172.16.0.242] (fs85a5b6e1.knge202.ap.nuro.jp [133.165.182.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.uni-bremen.de (Postfix) with ESMTPSA id 4Pl0Xq6G7zzDCbZ; Sun, 26 Mar 2023 17:41:15 +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: <ZCAywSGXT9Yv16ZC@hephaistos.amsuess.com>
Date: Mon, 27 Mar 2023 00:41:12 +0900
Cc: "core@ietf.org WG (core@ietf.org)" <core@ietf.org>
X-Mao-Original-Outgoing-Id: 701538071.9406379-154400a4d8983aea0f5b8c0b789a4b1d
Content-Transfer-Encoding: quoted-printable
Message-Id: <CA78D163-0DEE-4771-8367-A38F3CE5E7FD@tzi.org>
References: <ZCAywSGXT9Yv16ZC@hephaistos.amsuess.com>
To: Christian Amsüss <christian@amsuess.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/ZrlMuJppJYcL1TUsiS5-NR-DTaY>
Subject: Re: [core] Using SVCB with OSCORE/EDHOC
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Mar 2023 15:41:26 -0000

>  the rabbit hole of SVCB[1].

I wonder if we can defuse the complexity of this by defining the actual data model.
Of course, SVCB, as is, needs to carry 40 years of DNS baggage, but it should be possible to decode this and turn it into data that an EDHOC/OSCORE implementation would want to use.

Grüße, Carsten