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

Carsten Bormann <cabo@tzi.org> Fri, 13 May 2022 23:44 UTC

Return-Path: <cabo@tzi.org>
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 74BA6C1D34EA; Fri, 13 May 2022 16:44:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 c4_G1ZJlOprw; Fri, 13 May 2022 16:44:15 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::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 9A41FC1D34E8; Fri, 13 May 2022 16:44:11 -0700 (PDT)
Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4L0QGG6DFdzDCbG; Sat, 14 May 2022 01:44:06 +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: <Yn7rThJtz+VhJsa0@faui48e.informatik.uni-erlangen.de>
Date: Sat, 14 May 2022 01:44:06 +0200
Cc: core@ietf.org, dnssd@ietf.org
X-Mao-Original-Outgoing-Id: 674178246.499711-9e9338d894e3cf90f43d2a0605854b6c
Content-Transfer-Encoding: quoted-printable
Message-Id: <9AB469D2-FC4B-4BE2-A8D8-265378B85328@tzi.org>
References: <Yn7nnX096f0LdonI@faui48e.informatik.uni-erlangen.de> <C813906A-E7EB-4A69-9E94-14528E49E607@tzi.org> <Yn7rThJtz+VhJsa0@faui48e.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/9teC3FOwEE_TYiuFGqNzAUqYTgc>
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: Fri, 13 May 2022 23:44:17 -0000

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?

Grüße, Carsten