IETF Logo Mail Archive

Re: [dnssd] DNS-SD TXT question (for ANIMA use).

Stuart Cheshire <cheshire@apple.com> Tue, 03 May 2022 22:54 UTC

Return-Path: <cheshire@apple.com>
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 BE47BC159A1D; Tue, 3 May 2022 15:54:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.675
X-Spam-Level:
X-Spam-Status: No, score=-7.675 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.575, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 H1IEOgBSCIpJ; Tue, 3 May 2022 15:54:09 -0700 (PDT)
Received: from rn-mailsvcp-ppex-lapp24.apple.com (rn-mailsvcp-ppex-lapp24.rno.apple.com [17.179.253.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A059C159A1C; Tue, 3 May 2022 15:54:08 -0700 (PDT)
Received: from pps.filterd (rn-mailsvcp-ppex-lapp24.rno.apple.com [127.0.0.1]) by rn-mailsvcp-ppex-lapp24.rno.apple.com (8.16.1.2/8.16.1.2) with SMTP id 243MjxGf005955; Tue, 3 May 2022 15:54:02 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=content-type : mime-version : subject : from : in-reply-to : date : cc : content-transfer-encoding : message-id : references : to; s=20180706; bh=QGMRaHoQdPXaKJKgBLP5lz2+J9mueQvG4/OeO5Yga7Q=; b=wF1hbBcbyCJYyqlFIgCzLHGaW/LKmjYd91SlYL7a6AOXsf/QNcur0sVsBZV1R9DegEN5 njCfPdti+efKc5qdd5kca2S0cUSAOZxb08hHXCKdnAVBuE1j4lpDIuax94ciGzdY1nEb jBaTttioJgi+yxxskMBIcJjsLBfWqVJueq6ngFCWG8rUCGJF74jky4jBjlPCMvboDSdh 6gbGsNpZjaE1rss7CtoclZ4F6IJ/nv956yGOyD27tUsKUZVenQ/8oNde7piZmhSuoyIj f/W+jKzKvqtJx4PodxURTGGdeIo7097H1RVx2sm93/h9RZpvVrSt8Nmh8YRWKpD1z7Sj 1Q==
Received: from rn-mailsvcp-mta-lapp02.rno.apple.com (rn-mailsvcp-mta-lapp02.rno.apple.com [10.225.203.150]) by rn-mailsvcp-ppex-lapp24.rno.apple.com with ESMTP id 3fs2q92y97-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 03 May 2022 15:54:02 -0700
Received: from rn-mailsvcp-mmp-lapp03.rno.apple.com (rn-mailsvcp-mmp-lapp03.rno.apple.com [17.179.253.16]) by rn-mailsvcp-mta-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.18.20220407 64bit (built Apr 7 2022)) with ESMTPS id <0RBB0045RWY2WKK0@rn-mailsvcp-mta-lapp02.rno.apple.com>; Tue, 03 May 2022 15:54:02 -0700 (PDT)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp03.rno.apple.com by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.16.20220118 64bit (built Jan 18 2022)) id <0RBB00000WXAVZ00@rn-mailsvcp-mmp-lapp03.rno.apple.com>; Tue, 03 May 2022 15:54:02 -0700 (PDT)
X-Va-A:
X-Va-T-CD: f531f8d8b46e434c6cc260b03cd4b544
X-Va-E-CD: 5e8a9f335c3c252345ab9eb67f3b376b
X-Va-R-CD: 223e1706eefc6a455ebae3f65b4dc5f0
X-Va-CD: 0
X-Va-ID: 414271d5-b7a9-4ee2-85bf-d0838296543b
X-V-A:
X-V-T-CD: f531f8d8b46e434c6cc260b03cd4b544
X-V-E-CD: 5e8a9f335c3c252345ab9eb67f3b376b
X-V-R-CD: 223e1706eefc6a455ebae3f65b4dc5f0
X-V-CD: 0
X-V-ID: 13b90b0a-14ee-4fc2-b596-e4865020b3cc
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.486, 18.0.858 definitions=2022-05-03_09:2022-05-02, 2022-05-03 signatures=0
Received: from [17.11.99.7] (unknown [17.11.99.7]) by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.16.20220118 64bit (built Jan 18 2022)) with ESMTPSA id <0RBB0020BWY1PI00@rn-mailsvcp-mmp-lapp03.rno.apple.com>; Tue, 03 May 2022 15:54:02 -0700 (PDT)
Content-type: text/plain; charset="utf-8"
MIME-version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Stuart Cheshire <cheshire@apple.com>
In-reply-to: <YnGE13ujQHIF3uYi@faui48e.informatik.uni-erlangen.de>
Date: Tue, 03 May 2022 15:54:01 -0700
Cc: "touch@strayalpha.com" <touch@strayalpha.com>, dnssd@ietf.org, anima@ietf.org
Content-transfer-encoding: quoted-printable
Message-id: <BDEB1FD7-BE1F-4284-A183-43E4AE7A3A79@apple.com>
References: <Ym6j/8qhEzvqNw2V@faui48e.informatik.uni-erlangen.de> <BECA0397-5B8B-4DAB-8706-D5727F86F73A@strayalpha.com> <YnFyCwHUSu67Uio7@faui48e.informatik.uni-erlangen.de> <97BE76F7-FA1B-4693-B410-4314C4F56964@apple.com> <YnGE13ujQHIF3uYi@faui48e.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.486, 18.0.858 definitions=2022-05-03_09:2022-05-02, 2022-05-03 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/JwvYfdPjk4KeWy5WBt_r2BuhlvU>
Subject: Re: [dnssd] DNS-SD TXT question (for ANIMA use).
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, 03 May 2022 22:54:11 -0000

On 3 May 2022, at 12:39, Toerless Eckert <tte@cs.fau.de> wrote:

> The service name would not be CoAP, but e.g.: brski.rjp (service point for boostrapping of
> key infras). The TXT proto= key would need to be a list of 1 or more protocol variations,
> if those protocol variations happen to be able to (or need to) operate across the same
> UDP or TCP port - which is something that could happen for protocols operating on top
> of COAP or HTTP. For example proto=est-coap,cmp-coap, if we have two coap protocols, such as
> one based on EST (rfc7030), and one based on CMP, both able to operate across the same
> COAP (UDP) port. Service is the same, just encoding of transactions and data-structures
> differs.
> 
> Would that be appropriate ?

You can’t have a dot in the service name, but otherwise this looks good.

Stuart Cheshire

v2.23.0 | Report a Bug | By Email