Re: [dnssd] SRP: how to remove all published services?
Ted Lemon <mellon@fugue.com> Fri, 15 September 2023 14:41 UTC
Return-Path: <mellon@fugue.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 68262C15106F for <dnssd@ietfa.amsl.com>; Fri, 15 Sep 2023 07:41:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=fugue-com.20230601.gappssmtp.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 IB8p4sqrrDVe for <dnssd@ietfa.amsl.com>; Fri, 15 Sep 2023 07:41:15 -0700 (PDT)
Received: from mail-qv1-xf2a.google.com (mail-qv1-xf2a.google.com [IPv6:2607:f8b0:4864:20::f2a]) (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 77ABEC14F73F for <dnssd@ietf.org>; Fri, 15 Sep 2023 07:41:15 -0700 (PDT)
Received: by mail-qv1-xf2a.google.com with SMTP id 6a1803df08f44-656307a52e8so6209116d6.1 for <dnssd@ietf.org>; Fri, 15 Sep 2023 07:41:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20230601.gappssmtp.com; s=20230601; t=1694788874; x=1695393674; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=t5fMhBFJrCljm1GKdGc9wBHOnxEJ9LBCM8ezH5q67V4=; b=HFtgVLrBUCQ7TmqQZgrftANoRiVegMtLcfNkRjm16nX/JBPs4OFFGbAs6t3kQQ9mXr Wypc8Yli3JHf4yRcHkvygu+cekUK5heAHfua27VyeQWEdO+9M4piQHRjzN6KguKqzK92 KspPhz11AgFn7p4DAAvjMu1TOCymP6+GUrcH+iXBTMkB8k8cH5+zXuBGeUKYA3q8UDpq ez3KROY1RtsuyYkeYuaTlFeHlyP98adkFGHBx34jW8K12knMgwQgPxIv4zg2pxcr/j3i QCbPA9vqmGeacbjdfUmPk//zUNnMckdTEXG16wbyGSngqpdqtjkeW8tAgkmzOiFynEae GsaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694788874; x=1695393674; 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=t5fMhBFJrCljm1GKdGc9wBHOnxEJ9LBCM8ezH5q67V4=; b=gdukO3xTi7yyU2sTU6fbtip6PHHdIUmgV1oT7irdaFyznX3bWKgTUhCKQWMA+Og3/O tNLt4Xq5tUcS8RompyNtHubQWOUhwSmdqMGMDhuD4Xo8V0fq1enICSdKTBtUPcTf5cjp BTY/IYLWcLbPuY605kFWzSBttjBhrrHAh8LdFhUcfVBWSw5R8a7vW8oZSyQtC+zbyRyz Dc1RPL9KMtuqiAad400taO+2eq23jXBYyzonolTEJ06KKi/m3Zct0jD6qo+j4t0O5yNC sApXKOePM1onBLKZ6Yn79TL4tpW2GjVrSddsA4GOoPyt1Ljczgk4CisJZL5/S/9dkPbw JVYQ==
X-Gm-Message-State: AOJu0YwiWK8ZwZ/gADN6znu+KwUOBomJ8Dh2I4DnrURE0rbr1cp3PZFN fsy5sbz11W39/kf/U6GML/487Za8zeQmBABXRmkfY4gUHY5G3YibXcY=
X-Google-Smtp-Source: AGHT+IGrc1yEvGDcGATUV4pXRRNyED9AgEDKBT0+tvjwDwwjN3BXPWYX3qYT7RmXuSLMbFw6nSXFZty+yyvk7v7nIdE=
X-Received: by 2002:a0c:b4c9:0:b0:635:f899:660b with SMTP id h9-20020a0cb4c9000000b00635f899660bmr1855928qvf.36.1694788874377; Fri, 15 Sep 2023 07:41:14 -0700 (PDT)
MIME-Version: 1.0
References: <DU0P190MB1978B5A8AA3745770E94EEA5FDF6A@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <CAGwZUDtz86KtOvtxeACGSDP9dSCJdoKGWHQ_5imVwZYQDom4yQ@mail.gmail.com> <CAPt1N1kjMmnVMkkE7hsbnzf-T79GKSrcL3_oC8X_Pm47_xvkbw@mail.gmail.com>
In-Reply-To: <CAPt1N1kjMmnVMkkE7hsbnzf-T79GKSrcL3_oC8X_Pm47_xvkbw@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Fri, 15 Sep 2023 10:40:38 -0400
Message-ID: <CAPt1N1kMPCtvT6KdMzF3mKWJQH7R2mJhUxYsBcU7ADtp2=9Abg@mail.gmail.com>
To: Jonathan Hui <jonhui=40google.com@dmarc.ietf.org>
Cc: Esko Dijk <esko.dijk@iotconsultancy.nl>, "dnssd@ietf.org" <dnssd@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d3c8ce060566c833"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/w432VQc_P9DNJy834XvvCnrQjGs>
Subject: Re: [dnssd] SRP: how to remove all published services?
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: Fri, 15 Sep 2023 14:41:16 -0000
Oh, except the text you quoted says precisely that, so I think we're okay. Thanks, Jonathan. :) On Fri, Sep 15, 2023 at 10:40 AM Ted Lemon <mellon@fugue.com> wrote: > Was the question more "what if the requestor sends a partial remove (host > plus not all services) with lease time zero?" I think the answer is that it > removes all the services, because the other services are pointing to the > host, and the host has to be removed; this means that any remaining > services pointing to that host are simply invalid. We could certainly add a > note clarifying this point, although it's a bit late in the process for > that. > > On Fri, Sep 15, 2023 at 10:31 AM Jonathan Hui <jonhui= > 40google.com@dmarc.ietf.org> wrote: > >> Hi Esko, >> >> I believe this is addressed by the immediately following paragraphs in >> the same section? Specifically: >> >> To support this, when removing services based on the lease time being >> zero, an SRP registrar MUST remove all service instances pointing to >> a host when a host is removed, even if the SRP requestor doesn't list >> them explicitly. If the key lease time is nonzero, the SRP registrar >> MUST NOT delete the KEY records for these SRP requestors. >> >> So there is no need to list all the services that were previously >> registered. >> >> -- >> Jonathan Hui >> >> >> >> On Fri, Sep 15, 2023 at 7:17 AM Esko Dijk <esko.dijk@iotconsultancy.nl> >> wrote: >> >>> A question - in 3.2.5.5.1., Removing all published services, we have: >>> >>> >>> >>> To remove all the services registered to a particular host, the SRP >>> requestor retransmits its most recent update with an Update Lease option >>> that has a LEASE value of zero. >>> >>> >>> >>> I wonder how this exactly works in the following case. If I’ve >>> registered service A, and 10 minutes later registered service B in addition >>> (without mentioning A in the second SRP Update), then both services A and B >>> are actively registered. Now I send the “most recent SRP Update” which has >>> only service B to the SRP registrar, with a LEASE value of zero. >>> >>> Wouldn’t it be that only service B is removed (lease set to 0) while >>> service A stays active? >>> >>> >>> >>> If so, we may need to clarify this text I think. Because it’s not always >>> the “most recent SRP Update” then. >>> >>> (If not so, I’m having trouble understanding how the LEASE value in the >>> SRP Update does apply to all currently registered services….) >>> >>> >>> >>> Esko >>> _______________________________________________ >>> dnssd mailing list >>> dnssd@ietf.org >>> https://www.ietf.org/mailman/listinfo/dnssd >>> >> _______________________________________________ >> dnssd mailing list >> dnssd@ietf.org >> https://www.ietf.org/mailman/listinfo/dnssd >> >
- Re: [dnssd] SRP: how to remove all published serv… Ted Lemon
- [dnssd] SRP: how to remove all published services? Esko Dijk
- Re: [dnssd] SRP: how to remove all published serv… Jonathan Hui
- Re: [dnssd] SRP: how to remove all published serv… Ted Lemon
- Re: [dnssd] SRP: how to remove all published serv… Esko Dijk
- Re: [dnssd] SRP: how to remove all published serv… Ted Lemon