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

Peter van der Stok <stokcons@bbhmail.nl> Tue, 17 May 2022 08:29 UTC

Return-Path: <stokcons@bbhmail.nl>
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 C5A5FC14F606 for <dnssd@ietfa.amsl.com>; Tue, 17 May 2022 01:29:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_NONE=0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bbhmail.nl
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 TguB2d9JyPkz for <dnssd@ietfa.amsl.com>; Tue, 17 May 2022 01:29:00 -0700 (PDT)
Received: from relay3.hostedemail.com (smtprelay0015.hostedemail.com [216.40.44.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 331E0C14F716 for <dnssd@ietf.org>; Tue, 17 May 2022 01:28:04 -0700 (PDT)
Received: from omf15.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay07.hostedemail.com (Postfix) with ESMTP id 47B55208AB; Tue, 17 May 2022 08:28:03 +0000 (UTC)
Received: from [HIDDEN] (Authenticated sender: stokcons@bbhmail.nl) by omf15.hostedemail.com (Postfix) with ESMTPA id AA76826; Tue, 17 May 2022 08:28:02 +0000 (UTC)
MIME-Version: 1.0
Date: Tue, 17 May 2022 10:28:02 +0200
From: Peter van der Stok <stokcons@bbhmail.nl>
To: Esko Dijk <esko.dijk@iotconsultancy.nl>
Cc: Carsten Bormann <cabo@tzi.org>, Toerless Eckert <tte@cs.fau.de>, core@ietf.org, dnssd@ietf.org
Reply-To: stokcons@bbhmail.nl
Mail-Reply-To: stokcons@bbhmail.nl
In-Reply-To: <DU0P190MB1978F84C3EF1762E81609B24FDCF9@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
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> <Yn7xUaU4yzVz+qkd@faui48e.informatik.uni-erlangen.de> <510DBA42-6057-417E-9613-BD18C37E9EE8@tzi.org> <Yn+8iu6vpWiqnIQU@faui48e.informatik.uni-erlangen.de> <1B438E3C-57C9-41CE-8885-AF37EDDEE106@tzi.org> <DU0P190MB1978F84C3EF1762E81609B24FDCF9@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
Message-ID: <49dca3bdbea065c2b8910e829d193ad6@bbhmail.nl>
X-Sender: stokcons@bbhmail.nl
Organization: vanderstok consultancy
Content-Type: multipart/alternative; boundary="=_00cf50cdc4ee06f85e695dabbea0987e"
X-Stat-Signature: 93ysmu8ep3km9n9s863kqqactpwshosi
X-Rspamd-Server: rspamout04
X-Rspamd-Queue-Id: AA76826
X-Session-Marker: 73746F6B636F6E73406262686D61696C2E6E6C
X-Session-ID: U2FsdGVkX1/0QnudhbtOYdg1tI8MbJ2+6jq84GLra0s=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bbhmail.nl; h=mime-version:date:from:to:cc:subject:reply-to:in-reply-to:references:message-id:content-type; s=key; bh=V5P8uC5UIAvRsvUd2L3t6hdiadQ7q1emtSA3VopXLUY=; b=Rico6Q2hcWqyIWNu2u9H9IspllfYo5/oQ/ipcQrDZelE7bgz1Q7rtthbSq/m6nBr9jszXTJqWlI6uaU31tBsoWODgsz5ualTM4g3l96obFwhEUEA7CVFaS2D8gq7J2O8Q2W9fOgWGCXudg818TltNw6l00Vq2XW/GigvJHadhFU=
X-HE-Tag: 1652776082-327983
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/hjmp_myITSaUoIP5YDpSINwefnA>
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: Tue, 17 May 2022 08:29:04 -0000

  Hi,

In response to below.
The original idea was a full translation of the DNS-SD specto a 
lin-format spec.
That proved unwieldy.
In my memeory, the latest conclusion was that a manual translation from 
resource type type to service was the best solution.
Starting a register for this was rejected.

CHeerio,

Peter

Esko Dijk schreef op 2022-05-16 10:37:

> I also think that defining a standard "conversion" from DNS-SD service 
> to a CoRE Link Format description would be of interest.
> The work of Kerry Lynn that was mentioned ended up in this draft: 
> https://datatracker.ietf.org/doc/html/draft-ietf-core-rd-dns-sd-05
> 
> From what I heard this was complex because the aim was to have a full, 
> bi-directional translation between the two worlds. If you only consider 
> DNS-SD translation to CoRE Link Format the problem becomes much easier.
> For the reverse, CoRE Link Format to DNS-SD translation, I recall you 
> could end up with fairly large and complex DNS descriptions to capture 
> all the CoRE semantics correctly. (author Peter van der Stok knows 
> about this)