Re: [dnssd] [core] CoAP resource discovery and DNS-SD

Toerless Eckert <tte@cs.fau.de> Sat, 14 May 2022 00:01 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD9E7C1D34FC; Fri, 13 May 2022 17:01:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.871
X-Spam-Level:
X-Spam-Status: No, score=-0.871 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779] autolearn=no 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 ora_i03xODh6; Fri, 13 May 2022 17:01:29 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (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 84DCAC19E85E; Fri, 13 May 2022 17:01:27 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [131.188.34.51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 80B5858C4AF; Sat, 14 May 2022 02:01:21 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 775344EAEA3; Sat, 14 May 2022 02:01:21 +0200 (CEST)
Date: Sat, 14 May 2022 02:01:21 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Carsten Bormann <cabo@tzi.org>
Cc: core@ietf.org, dnssd@ietf.org
Message-ID: <Yn7xUaU4yzVz+qkd@faui48e.informatik.uni-erlangen.de>
References: <Yn7nnX096f0LdonI@faui48e.informatik.uni-erlangen.de> <C813906A-E7EB-4A69-9E94-14528E49E607@tzi.org> <Yn7rThJtz+VhJsa0@faui48e.informatik.uni-erlangen.de> <9AB469D2-FC4B-4BE2-A8D8-265378B85328@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <9AB469D2-FC4B-4BE2-A8D8-265378B85328@tzi.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/Rg00prL5-ayShnuVTJMViyAdpL0>
Subject: Re: [dnssd] [core] CoAP resource discovery and DNS-SD
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2022 00:01:30 -0000

On Sat, May 14, 2022 at 01:44:06AM +0200, Carsten Bormann wrote:
> On 2022-05-14, at 01:35, Toerless Eckert <tte@cs.fau.de> wrote:
> > 
> > It does not describe how to describe the parameters i was looking for:
> > priority, weight, key=value
> 
> CoRE resource discovery was designed to discover resources, not to emulate specific features of other service discover protocols.
> 
> Can you explain what you are trying to do without phrasing this in DNS-SD terms?

I send a coap resource discovery to ff05::fd and there are three different
nodes replying because they all have this resource. But lets say one of
them is meant to be an emergency backup not to be used when any other is
present (prio=0), the other two are meant to be used primarily (prio=1),
but one of them has a lot more performance to serve the resource, so
the client should stochastically select it with a 9 times higher probability
than the other (w=9) vs. w=1). Aka All three instances are announcing
a weight and priority value in their reply and the client picks the
appropriate one.

Likewise, for other parameters, the client gets replies from multiple
instances, but they resource differs in some details and those are expressed
in those additional parameters.

Cheers
    toerless