Re: [dnssd] SRP: support of SRP message with zero service?
Kangping Dong <wgtdkp@google.com> Wed, 07 December 2022 13:28 UTC
Return-Path: <wgtdkp@google.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 C3520C1526FD for <dnssd@ietfa.amsl.com>; Wed, 7 Dec 2022 05:28:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.597
X-Spam-Level:
X-Spam-Status: No, score=-15.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HK_RANDOM_ENVFROM=0.999, HK_RANDOM_FROM=0.999, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 6l07G3dw7KcC for <dnssd@ietfa.amsl.com>; Wed, 7 Dec 2022 05:28:14 -0800 (PST)
Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (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 0F74DC14F6E7 for <dnssd@ietf.org>; Wed, 7 Dec 2022 05:28:13 -0800 (PST)
Received: by mail-io1-xd31.google.com with SMTP id n63so7301480iod.7 for <dnssd@ietf.org>; Wed, 07 Dec 2022 05:28:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=+Gth/b2nhSytbRLJBFzP36sGFR0PzMcKhWL7qnuUsr0=; b=HtvtxtGRk7ap/z5HPsGojKiY34O0iwXikAwJ6miVW0QW7aqm/OzdWI6Wfy6iYn8Ugi 3g2MhPb9Q8Z7/rDLgQL0AA3fw6g1YJzMesR1oVg/vzXXYv2x7yedCjknTQR4Rd26O18W E/1GMvpSCRY3sXqlaK4HQ64hi6+f3kT4vsBqYq/c8Ca07SJE3Wt6j/oWMnUabjDCgcNn wD/UVh1C2342eV6Jusqdpkx8xGV8ZW8iubfwlKd1Ze2kkELB7f689icQBKEgTZc77Nte JM/LbuFbfyR+fOex5RQi404dPRz79Eos77uHTbPZzs3AskogNKUgCT9lUrvuNlwOBXLS yPpw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=+Gth/b2nhSytbRLJBFzP36sGFR0PzMcKhWL7qnuUsr0=; b=C6+ZZZXA4OQwr0/wGcRLgidbCFvpegMHqP1W2jiKUMUmzA1J0URSJ9sTsmfwZQmb/v MkTC/qQHjUyKBHwUHz96iVOgTHqrV+HoHs896Atsb6PDrInDPUCUb3C0OxvXK4EJ/5yb zJFzbzKBlY5LZxH4PsfbNaqP+N7Wtq7Pp0VfER73zySlrdfu1z8O05Sm4j+6a0KTW5bP C+r224jvHCMuKjbdD7oJTBAGBPpACesPRt4AbuIl8FWCivvJh/sgwcTvFWm4srojl65x sE8xY4zsaiThAB+xnaGLzWFGuPrb+FxA6FLM0bTyPP+nyI6Nrqqgft98lHvpm3nBm9M7 iDJQ==
X-Gm-Message-State: ANoB5pkaLXWh3hINGx2YpW2jquBi5LycLArCd5u9pk1HIVCDoxq5Xexp sscLsrpTZl+7Ly5GcvjLwBpclmeDNPTNGPV0G5aPPw==
X-Google-Smtp-Source: AA0mqf7kFDJy6yMJiYplf1ySq7LIcc0Po0KUPfJJmWF6nwMXKvqaOjTe/0hlrSXm+5OLZa6iTMSr+g/NlFg8zv5oruA=
X-Received: by 2002:a02:cc2a:0:b0:372:bf99:b645 with SMTP id o10-20020a02cc2a000000b00372bf99b645mr35267276jap.278.1670419692887; Wed, 07 Dec 2022 05:28:12 -0800 (PST)
MIME-Version: 1.0
References: <CAJ5Rr7ZTujqf3_CR-PY1Kdj1KTFAKQKcPbmZORXOxW+8TMquVw@mail.gmail.com> <CAPt1N1=aPfTpSdVbWTSBVi27SAr_uGwhuG03z6MNGRBdzZyqkg@mail.gmail.com> <DU0P190MB1978503FBF2F9F3853AFC3E6FD1A9@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <CAJ5Rr7azeWtW0ujL6GBQ9QwWbX3Zi5Noroc4fLvcRAC9n5iOsg@mail.gmail.com> <DU0P190MB197841581AE31FF6A74B4440FD1A9@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <CAPt1N1mtci0R7qH0=yiu0xn5su-PGXhobi+h5dk-_9eCJXrXng@mail.gmail.com>
In-Reply-To: <CAPt1N1mtci0R7qH0=yiu0xn5su-PGXhobi+h5dk-_9eCJXrXng@mail.gmail.com>
From: Kangping Dong <wgtdkp@google.com>
Date: Wed, 07 Dec 2022 21:27:36 +0800
Message-ID: <CAJ5Rr7bEUYNafVYj2g1Vwypk9Tc8QS0RNyyk=KkCvs9K1w-a4w@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>, Esko Dijk <esko.dijk@iotconsultancy.nl>, jabley@hopcount.ca
Cc: "dnssd@ietf.org" <dnssd@ietf.org>, Abtin Keshavarzian <abtink@google.com>, Jonathan Hui <jonhui@google.com>
Content-Type: multipart/alternative; boundary="0000000000006c138f05ef3ce476"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/GN1okyttJ67aFPkSM1flCYCwIL4>
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:28:17 -0000
Thanks Joe, Esko and Ted! Yeah I was thinking of SRP something limited to a constraint network >_< That's a good example that I immediately knows how to connect to my laptop when I get the name (don't need "service advertisements made by the device"). Cheers! BRs, Kangping On Wed, Dec 7, 2022 at 8:55 PM Ted Lemon <mellon@fugue.com> wrote: > Also bear in mind that SRP isn’t just for the constrained device use case. > There may be cases where it’s useful to register a well known name and > unnecessary to advertise a service. E.g. so you can ssh to your laptop by > name. > > Op wo 7 dec. 2022 om 07:52 schreef Esko Dijk <esko.dijk@iotconsultancy.nl> > >> Yes we have, the link to the start of the thread is: >> https://mailarchive.ietf.org/arch/msg/dnssd/01voO6MkMBBvxeInncR6e-3u1bM/ >> >> (somewhat long discussion) >> >> >> >> One use case mentioned also is an SRP client adding or removing an IP >> address in its registration, while keeping its services unchanged. >> >> >> >> Esko >> >> >> >> *From:* Kangping Dong <wgtdkp@google.com> >> *Sent:* Wednesday, December 7, 2022 12:48 >> *To:* Esko Dijk <esko.dijk@iotconsultancy.nl> >> *Cc:* Ted Lemon <mellon@fugue.com>; Abtin Keshavarzian <abtink@google.com>; >> DNSSD <dnssd@ietf.org>; Jonathan Hui <jonhui@google.com> >> *Subject:* Re: SRP: support of SRP message with zero service? >> >> >> >> > Why is it useful to have a hostname and address generally? :) >> >> >> >> If the client knows only the hostname and address, it doesn't know what >> protocol should be used to communicate with the device, so it doesn't seem >> to be useful to >> >> know only the address. One use case in my mind is that a device may >> register a well-known hostname, but didn't find a real case in local >> constraint networks... >> >> >> >> > I recall that we discussed that a device could temporarily not have a >> particular service; and some expectation that in due time a service will >> become available again. >> >> > During this time the device wants to keep its name registered, to show >> that it is still there and functional, and defend its name against >> potential other devices taking that name. >> >> *> *So one use case is deleting its service(s) but keeping the name >> registered. >> >> >> >> Will this encourage devices to always register their hostname even when >> they don't provide any service? Do we have a link to that discussion? @Esko >> Dijk <esko.dijk@iotconsultancy.nl> >> >> >> >> BRs, >> >> Kangping >> >> >> >> >> >> >> >> On Wed, Dec 7, 2022 at 7:32 PM Esko Dijk <esko.dijk@iotconsultancy.nl> >> wrote: >> >> I recall that we discussed that a device could temporarily not have a >> particular service; and some expectation that in due time a service will >> become available again. >> >> During this time the device wants to keep its name registered, to show >> that it is still there and functional, and defend its name against >> potential other devices taking that name. >> >> >> >> So one use case is deleting its service(s) but keeping the name >> registered. >> >> >> >> Regards >> >> Esko >> >> >> >> *From:* Ted Lemon <mellon@fugue.com> >> *Sent:* Wednesday, December 7, 2022 12:15 >> *To:* Kangping Dong <wgtdkp@google.com> >> *Cc:* Abtin Keshavarzian <abtink@google.com>; DNSSD <dnssd@ietf.org>; >> Esko Dijk <esko.dijk@iotconsultancy.nl>; Jonathan Hui <jonhui@google.com> >> *Subject:* Re: SRP: support of SRP message with zero service? >> >> >> >> Why is it useful to have a hostname and address generally? :) >> >> >> >> Op wo 7 dec. 2022 om 06:09 schreef Kangping Dong <wgtdkp@google.com> >> >> Hi, >> >> >> >> Regarding SRP registration, it's unclear if at least one "Service >> Description Instruction" is required in a SRP message when the host is not >> being deleted. >> >> If it's not required to register at least one service, what's the use >> case of registering only the host/address? Any examples? (It doesn't seem >> to be useful >> >> to advertise only the host name and addresses with the Advertising Proxy >> :) >> >> >> >> Thanks! >> >> >> >> >> >> >> >> BRs, >> >> Kangping >> >> _______________________________________________ >> dnssd mailing list >> dnssd@ietf.org >> https://www.ietf.org/mailman/listinfo/dnssd >> >
- [dnssd] SRP: support of SRP message with zero ser… Kangping Dong
- Re: [dnssd] SRP: support of SRP message with zero… Ted Lemon
- Re: [dnssd] SRP: support of SRP message with zero… Esko Dijk
- Re: [dnssd] SRP: support of SRP message with zero… Kangping Dong
- Re: [dnssd] SRP: support of SRP message with zero… Joe Abley
- Re: [dnssd] SRP: support of SRP message with zero… Esko Dijk
- Re: [dnssd] SRP: support of SRP message with zero… Ted Lemon
- Re: [dnssd] SRP: support of SRP message with zero… Kangping Dong
- Re: [dnssd] SRP: support of SRP message with zero… Esko Dijk
- Re: [dnssd] SRP: support of SRP message with zero… Ted Lemon
- Re: [dnssd] SRP: support of SRP message with zero… Michael Richardson