IETF Logo Mail Archive

[core] discovery of Join-Proxy/Registrar by pledge (was Re: Join-proxy information in the RD (Re: CoRE WG Virtual Interim 2022-09-14))

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 14 September 2022 22:12 UTC

Return-Path: <mcr@sandelman.ca>
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 C8F84C14F72A; Wed, 14 Sep 2022 15:12:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 osgFRr4MxVPV; Wed, 14 Sep 2022 15:12:04 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (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 65F49C14F72D; Wed, 14 Sep 2022 15:12:03 -0700 (PDT)
Received: from dooku.sandelman.ca (dynamic-077-183-081-112.77.183.pool.telefonica.de [77.183.81.112]) by relay.sandelman.ca (Postfix) with ESMTPS id 525851F480; Wed, 14 Sep 2022 22:12:01 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 54D471A0248; Thu, 15 Sep 2022 00:12:00 +0200 (CEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Christian =?iso-8859-1?Q?Ams=FCss?= <christian@amsuess.com>, anima@ietf.org, "core@ietf.org WG (core@ietf.org)" <core@ietf.org>
In-reply-to: <YyH8C73McJ/DHKRy@hephaistos.amsuess.com>
References: <91614672-0629-f10f-9bcc-ad922d4045be@ri.se> <483507C3-9E25-4450-99D4-6FE7FA56266E@tzi.org> <22189.1663100544@dooku> <YyH8C73McJ/DHKRy@hephaistos.amsuess.com>
Comments: In-reply-to Christian =?iso-8859-1?Q?Ams=FCss?= <christian@amsuess.com> message dated "Wed, 14 Sep 2022 18:06:35 +0200."
X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 27.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 15 Sep 2022 00:12:00 +0200
Message-ID: <33230.1663193520@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/yVBIYBowbtR3DY4dW4sdoA2QCWo>
Subject: [core] discovery of Join-Proxy/Registrar by pledge (was Re: Join-proxy information in the RD (Re: CoRE WG Virtual Interim 2022-09-14))
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: Wed, 14 Sep 2022 22:12:08 -0000

Christian Amsüss <christian@amsuess.com> wrote:
    > * Similarly, the query for ?rt=brski.jp returns a resource, when it is
    > actually asking for a transport endpoint. Moreover, there *are*
    > resources available that the pledge likely will need to discover (any
    > of the brski.rv/vs/es). Before I can make any good statements or
    > suggesions here, how is it currenlty envisioned that the pledge will
    > find these resources?

This is an interesting situation.
I actually think that we've probably got this wrong!
We should not ever do rt=brski.jp.
We should be doing instead rt=brski*, as you say, because it's the rv/vs/es
that we really are looking for.   So it should look like:

~~~~
  REQ: GET coap://[FF02::FD]/.well-known/core?rt=brski*

  RES: 2.05 Content
  <coaps://[2001:db8:0:abcd::52]:join-port/.well-known/brski/rv>;rt=brski.rv;ct=836,
  <coaps://[2001:db8:0:abcd::52]:join-port/.well-known/brski/vs>;rt=brski.vs;ct="50 60",
  <coaps://[2001:db8:0:abcd::52]:join-port/.well-known/brski/es>;rt=brski.es;ct="50 60",
~~~~

It would be nice if we could get back:
  <coaps://[2001:db8:0:abcd::52]:join-port/.well-known/est/sren>;ct=287

as well, but I don't know how/if we can ask for rt=est* as well as rt=brski*
in a single operation.  This is in section 6.1.1 of the -12.

Maybe we just don't need brski.jp *AT ALL*
The Join Proxy should answer as if it was the Registrar, with coaps: at the front.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email