Re: [core] DNS-SD service types for CoRE-RD (Re: AD review of draft-ietf-core-resource-directory-23)

Christian Amsüss <christian@amsuess.com> Mon, 09 March 2020 09:07 UTC

Return-Path: <christian@amsuess.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 309993A0AC7 for <core@ietfa.amsl.com>; Mon, 9 Mar 2020 02:07:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.623
X-Spam-Level:
X-Spam-Status: No, score=-1.623 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.274, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XXJRrwKAwrzq for <core@ietfa.amsl.com>; Mon, 9 Mar 2020 02:07:49 -0700 (PDT)
Received: from prometheus.amsuess.com (alt.prometheus.amsuess.com [IPv6:2a01:4f8:190:3064::3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 494F53A092C for <core@ietf.org>; Mon, 9 Mar 2020 02:07:48 -0700 (PDT)
Received: from poseidon-mailhub.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bd]) by prometheus.amsuess.com (Postfix) with ESMTPS id E292640029; Mon, 9 Mar 2020 10:07:45 +0100 (CET)
Received: from poseidon-mailbox.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bf]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id F02F9DB; Mon, 9 Mar 2020 10:07:44 +0100 (CET)
Received: from hephaistos.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:f957:fc1b:6dc1:8d4b]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 98EEA148; Mon, 9 Mar 2020 10:07:44 +0100 (CET)
Received: (nullmailer pid 1412080 invoked by uid 1000); Mon, 09 Mar 2020 09:06:20 -0000
Date: Mon, 09 Mar 2020 10:06:19 +0100
From: Christian Amsüss <christian@amsuess.com>
To: Ted Lemon <mellon@fugue.com>
Cc: Carsten Bormann <cabo@tzi.org>, "core@ietf.org" <core@ietf.org>
Message-ID: <20200309090619.GB1182799@hephaistos.amsuess.com>
References: <481f9820-bcea-af6a-d5c4-d713be24d43d@isode.com> <20191119125733.GA8007@hephaistos.amsuess.com> <c29e70d4-7d81-4c89-ad81-62a6132fb3df@www.fastmail.com> <4C059F03-BB42-498D-9B75-A08BEA274416@tzi.org> <20200302145539.GA568382@hephaistos.amsuess.com> <F0CB7B96-4872-4EC4-A874-C110DC5AF2EA@tzi.org> <A3B3F66A-821C-4101-877B-DD87990DE87D@fugue.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="8GpibOaaTibBMecb"
Content-Disposition: inline
In-Reply-To: <A3B3F66A-821C-4101-877B-DD87990DE87D@fugue.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/1MnL-Sa8uHvKI3Bom4pKca6JXfc>
Subject: Re: [core] DNS-SD service types for CoRE-RD (Re: AD review of draft-ietf-core-resource-directory-23)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 09 Mar 2020 09:07:51 -0000

Hello Ted, Carsten and group,

thanks for your input; I take from it that DNS-SD discovered secure RD
access is realistic, and that while there are several ways to use it,
those are not specific to RD and thus we don't have specific security
guidance.

For the common usage of RD that I personally expect, UDP will be the
predominant usage pattern, and the other protocols could still be
entered into the registry when actually needed -- that would make the
whole thing simpler here as it's only a single new type. Text proposals
for both versions (coap/coaps/coap+tcp/coaps+tcp[1,2,3] and
coap-only[4,5,6]) are currently in the editors' copy branches, diffs and
issue tracker.

Given that what was previously discussed in the WG all points to
many-services, I'll merge and submit the four-protocol variety this
evening before cut-off, but if there are seconds for the argument for
simplicity in limited initial choice (with the option to extend without
RFC through IANA registration), I'd be happy to go with that.

Kind regards
Christian

[1]: https://core-wg.github.io/resource-directory/dnssd-moreprotos/draft-ietf-core-resource-directory.html
[2]: https://github.com/core-wg/resource-directory/pull/230/files
[3]: https://github.com/core-wg/resource-directory/pull/230
[4]: https://core-wg.github.io/resource-directory/dnssd-nomoreprotos/draft-ietf-core-resource-directory.html
[5]: https://github.com/core-wg/resource-directory/pull/231/files
[6]: https://github.com/core-wg/resource-directory/pull/231

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom