Re: [core] New version of draft-amsuess-core-transport-indication

Carsten Bormann <cabo@tzi.org> Sun, 11 July 2021 20:23 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 B3F4A3A1CED for <core@ietfa.amsl.com>; Sun, 11 Jul 2021 13:23:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 lpFeqH9c7sPz for <core@ietfa.amsl.com>; Sun, 11 Jul 2021 13:23:52 -0700 (PDT)
Received: from gabriel-2.zfn.uni-bremen.de (gabriel-2.zfn.uni-bremen.de [IPv6:2001:638:708:32::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 EDB433A1CE7 for <core@ietf.org>; Sun, 11 Jul 2021 13:23:51 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GNJJH55wVz2xGS; Sun, 11 Jul 2021 22:23:43 +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: <YOnyBHFJ7QSYhJUy@hephaistos.amsuess.com>
Date: Sun, 11 Jul 2021 22:23:43 +0200
Cc: core@ietf.org
X-Mao-Original-Outgoing-Id: 647727823.304139-9b7779af522a5fcca37efa0cea9f6f44
Content-Transfer-Encoding: quoted-printable
Message-Id: <A63F6CAE-2659-4491-B39A-977DD95CE364@tzi.org>
References: <YOnyBHFJ7QSYhJUy@hephaistos.amsuess.com>
To: =?utf-8?Q?Christian_Ams=C3=BCss?= <christian@amsuess.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/yj4T3zLW5GRcXm2_VmqlOPYwlx0>
Subject: Re: [core] New version of draft-amsuess-core-transport-indication
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Jul 2021 20:23:55 -0000

Interesting.  I did a fast skim (more before 111), and my brain got going in two directions:

How important is it for a node to know whether the proxy offered actually is on-origin (not really a proxy)?  I’m trying to think up how one would set up security (DTLS, OSCORE) to that proxy.  Somehow, 2.2 leaves me a bit hungry here (credentials may need to be mutual).

Obviously, knowing that something “is a proxy” doesn’t mean the client can suddenly assume it is less-constrained (e.g., with respect to achievable response-rates and fan-in/fan-outs), power-affluent etc.  
Maybe those semantics go beyond what we would want to indicate via web-linking, but I think we should think more about how to make them available for server/proxy  selection.

Nit:
mechsnisms
but In general
the HTTP provisions the Alt-Svc
separte

Grüße, Carsten