IETF Logo Mail Archive

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

Ted Lemon <mellon@fugue.com> Fri, 13 May 2022 23:23 UTC

Return-Path: <mellon@fugue.com>
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 5E623C19E872 for <core@ietfa.amsl.com>; Fri, 13 May 2022 16:23:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20210112.gappssmtp.com
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 TwSSuAsW8sA3 for <core@ietfa.amsl.com>; Fri, 13 May 2022 16:23:18 -0700 (PDT)
Received: from mail-oa1-x2b.google.com (mail-oa1-x2b.google.com [IPv6:2001:4860:4864:20::2b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 9743BC19E870 for <core@ietf.org>; Fri, 13 May 2022 16:23:18 -0700 (PDT)
Received: by mail-oa1-x2b.google.com with SMTP id 586e51a60fabf-edf9ddb312so12327744fac.8 for <core@ietf.org>; Fri, 13 May 2022 16:23:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ChmHrEMSqPmf9pP42hoXlkBKhMJaV9kGtxeFSQbVa4Y=; b=AY0tjmgtKUY3GRqy3728RXa6PoM5rLQUNQTZsTxIqbY0eaOU/SjUYkpxStpkWhDKwG gi+9RjetBhzmoXujLxiGbByuLjYEspEQWOIX1W5gX7CA7y7f7iR5h7AgoAzBtG1ICkrY 26YySVCrjiZhrccCFPoAiciQAuQyrrDeYJmATdwmo808Vya2htR1adW64t52HgTJb2jI vS8PKopNd32yodHYq3xygCTsKz6CAv3tjDLzXISp7jyah1qMP0pgAyWHqcngUOvA4KPc Q2MMRxpn15XQQwFyvONGzryAfq5LKZYeS/QD7VNaS9Rk9Gy3DTkIvP1fDN9lbNzSx/ZZ I0pA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ChmHrEMSqPmf9pP42hoXlkBKhMJaV9kGtxeFSQbVa4Y=; b=Y3UkhHUPWM1xCv1S/azzIwspY4RnUp7A1e+A0krSVbpNreBDmG3Ca3soRX2uX5i12z rWuJ43Cz0fRsKnBAwFyg5eJ62L0UCvVqoRUDTg2zpX2R3rmOpa2D7WIyz8xhQJqbAo1w BlYaj69UR6hOOXSuBqD5w2GCi3Hve8EfbLfU7dypzN/MzwywGZyAJnqQXpW5NkC8ys8g l0mdqgZf4D9XRgE/IE7atXpW5h4vqnybrfeDhTfTuCkYrz6qUOdtauSk8QoWwsg/VhEo fWKAQCHE3pdtmxC2cXtWJ4UaCwI74sCQVv29rMQtsFmV+k8p5Q6ubN4A2+cHO6jtbtdT pTGQ==
X-Gm-Message-State: AOAM532gq5a4VkoxnvsvpXfOmC83JxVvkGJMmCGtyiUgZWmC2QSWGYy2 eSgiVNCSjlmT4Rkh/yveqbMS2m7fBPTSgOtpvNM0I589MN9a5A==
X-Google-Smtp-Source: ABdhPJzJk23zDNNyyWDo92cPQKSAXLpigSXb18Ds23iUIKEzPJwreok1rnjcMMNJUmTp/kprGc1bPby9uf0tpIpULZc=
X-Received: by 2002:a05:6870:1710:b0:ec:94dc:5406 with SMTP id h16-20020a056870171000b000ec94dc5406mr3594856oae.209.1652484197173; Fri, 13 May 2022 16:23:17 -0700 (PDT)
MIME-Version: 1.0
References: <Yn7nnX096f0LdonI@faui48e.informatik.uni-erlangen.de>
In-Reply-To: <Yn7nnX096f0LdonI@faui48e.informatik.uni-erlangen.de>
From: Ted Lemon <mellon@fugue.com>
Date: Fri, 13 May 2022 19:22:41 -0400
Message-ID: <CAPt1N1n7Pd7yZ1jzBGMWCv-Vkf1iT_nLPmHrNYvDkwVjE7QmhA@mail.gmail.com>
To: Toerless Eckert <tte@cs.fau.de>
Cc: core@ietf.org, dnssd@ietf.org
Content-Type: multipart/alternative; boundary="00000000000091e7aa05deecf501"
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/IY1VZtp9GH7nuyNj2kMELWrEfpU>
Subject: Re: [core] [dnssd] CoAP resource discovery and DNS-SD
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.34
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: Fri, 13 May 2022 23:23:19 -0000

We were never able to figure that out either. The mapping from Core RD in
particular to DNS-SD is something that the DNS-SD working group actually
pursued for a while (Kerry Lynn worked on this pretty heavily for about a
year).

On Fri, May 13, 2022 at 7:20 PM Toerless Eckert <tte@cs.fau.de> wrote:

> Dear CoAP WG
>
> I am trying to figure out how to use CoAP discovery as specified in RFC7252
> (and expanded in rfc6690 and rfc7390),  but i can not figure out how
> one would encode basic parameters of a resource, such as those supported
> in DNS-SD, rfc6763:
>
> When discovering more than one instance of a resource, such as possible,
> when using multicast discovery as on rfc7252, clients will have to figure
> out,
> which instance of a resource to select. DNS-SSD has priority and weight
> parameters associated with each instance. How would one describe/encode
> such instance and weight ?
>
> When discovering one or more instance via DNS-SD, the discoering client
> may further select the best instance in terms of interoperability,
> functionality
> and performance based on one or more key=value property pairs describing
> the instance. How is this done in CoAP ?
>
> Thanks a lot!
>
> Toerless
>
> _______________________________________________
> dnssd mailing list
> dnssd@ietf.org
> https://www.ietf.org/mailman/listinfo/dnssd
>

v2.23.0 | Report a Bug | By Email