Re: [dnssd] SRP: support of SRP message with zero service?

Michael Richardson <mcr@sandelman.ca> Wed, 07 December 2022 13:43 UTC

Return-Path: <mcr@sandelman.ca>
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 DC91DC14CE47 for <dnssd@ietfa.amsl.com>; Wed, 7 Dec 2022 05:43:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.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, 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=sandelman.ca
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 lSpyYPCK36rG for <dnssd@ietfa.amsl.com>; Wed, 7 Dec 2022 05:43:32 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (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 C6904C14CE3D for <dnssd@ietf.org>; Wed, 7 Dec 2022 05:43:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 89C5918010; Wed, 7 Dec 2022 09:10:02 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id oOnYqworZfyo; Wed, 7 Dec 2022 09:09:58 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 5A8961800D; Wed, 7 Dec 2022 09:09:58 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1670422198; bh=PqlmYJXJZfOM9EBQ9xJOloVxJM6zLbOeitfio6jF2wk=; h=From:To:Subject:In-Reply-To:References:Date:From; b=CrjKFc0Dpem1uM4el9CMllikp1Pv6ytsNM9evYwsrTbACI6NR2agiiyRtdC2+nVZQ 7zwOIK0XShgpv+mJZm8WwuhZzVb8znZS5yQx2GvUN/8AR/1Qk+vmaf96gvwUB/XDLb TMVhrws+yjbh/sqhWe4BU5hFAtpMqNbJdec+mW9GvofnGhfE+ix1TCGc0flU0R0D5R yJNzOJxW31VwSpBzaBqDEVpwmgkhR6TCiFXCggI/oPT28ayDeUcwGRhQFfDyXmctIu NWKO+55M2lFN3JaoIJbbUWitIh2o0T38oiR9xVFVMkIpyU22I03TxEx9egRyCUzmhb VgxDJA3HfJd5g==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 4DB743D2; Wed, 7 Dec 2022 08:43:26 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Joe Abley <jabley@hopcount.ca>, DNSSD <dnssd@ietf.org>, Jonathan Hui <jonhui@google.com>
In-Reply-To: <pcoIFft_fVAkTCTGfYktQ5JsusT9IxkLkGO2UO4GgE8lPR4qO1UVBaqZveiXt8bOgDLcxHU6ysTK17_eUs5spbXrgfT4-HBMFt0gbU3e6l0=@hopcount.ca>
References: <CAJ5Rr7ZTujqf3_CR-PY1Kdj1KTFAKQKcPbmZORXOxW+8TMquVw@mail.gmail.com> <CAPt1N1=aPfTpSdVbWTSBVi27SAr_uGwhuG03z6MNGRBdzZyqkg@mail.gmail.com> <DU0P190MB1978503FBF2F9F3853AFC3E6FD1A9@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <CAJ5Rr7azeWtW0ujL6GBQ9QwWbX3Zi5Noroc4fLvcRAC9n5iOsg@mail.gmail.com> <pcoIFft_fVAkTCTGfYktQ5JsusT9IxkLkGO2UO4GgE8lPR4qO1UVBaqZveiXt8bOgDLcxHU6ysTK17_eUs5spbXrgfT4-HBMFt0gbU3e6l0=@hopcount.ca>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7296.1670420606.1@localhost>
Date: Wed, 07 Dec 2022 08:43:26 -0500
Message-ID: <7297.1670420606@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/5XB5VbiB1679VwOKbOj3HkWcOUY>
Subject: Re: [dnssd] SRP: support of SRP message with zero service?
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 07 Dec 2022 13:43:36 -0000

Joe Abley <jabley@hopcount.ca> wrote:
    > A client may have other reasons to want to be able to discover a
    > dynamic (name, address) binding, or may have other means of knowing
    > particular protocols associated with a device beyond service
    > advertisements made by the device.

Exactly, and typically http:// to it might give some status.
(https is a challenge)