Re: [dnssd] SRP: how to remove all published services?

Jonathan Hui <> Fri, 15 September 2023 14:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 15E6DC15106F for <>; Fri, 15 Sep 2023 07:31:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -17.606
X-Spam-Status: No, score=-17.606 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, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vR7y41PXuryp for <>; Fri, 15 Sep 2023 07:31:10 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::52b]) (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 (Postfix) with ESMTPS id 492B3C14EB17 for <>; Fri, 15 Sep 2023 07:31:10 -0700 (PDT)
Received: by with SMTP id 4fb4d7f45d1cf-529fa243739so16484a12.0 for <>; Fri, 15 Sep 2023 07:31:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20230601; t=1694788268; x=1695393068;; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=roksmfysJypwEq2YY4iHvkpGmAQ5U5FrfT5PEdNv1Bo=; b=rrZbGczYDIXZv+IY4DUkZdh+pKkwdFTRfnG4BTo5a80/lsgKpEvZSJDPlt0yHMlTGt iLe+boVcdryo5yPn0OqZmqTtDIlGsTcy8zpGLQQc7zDkPIER0kZisMmdJgecec6VpTL5 dANJd9mUerehvoSgCgetQIxiddWfQDxpP4+TRrnEazqt6pbmVF34WnrUtSppZkrdjkth XRXCPsKRu1pUM/Ow1s1y6KJCtSUcM/JN2rkiNeYPZzwprYe64R9k4VXf6vXn87cP15Z3 hVkvNpS5FJZAMowm2NlNjWKAF5qoo1P6ojS4Dp7NERFt99wb3HeRnI0a5HvRIU7nWgdG SU8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20230601; t=1694788268; x=1695393068; 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=roksmfysJypwEq2YY4iHvkpGmAQ5U5FrfT5PEdNv1Bo=; b=XyawYJCfIHr0dbNtYzpmBrz5TIp0ms4Io4Js+0HWAHu0I1fRvom6IiVIOHdhf0LF1v dP30vq1VfcTB/zOR++xEWQhkGkoNdqmRHqFvpBu6so9iw1d7HI6NyF5Ma2PlRyxvVWla QetjjUfV4Ey6e5n1X4XQyumnf3CnwAMse7WB9nMFRNBjemmUka3E6soPJXg4ZmUjMkUE FMYXF2nJK+BzE9urpnMtqDE7FHxv3+yihxApsXUJ3zGe7ijuXdD5CHXgztBjOcCxny7G +zmHyg9Iw8suziBcA6Nrjw/e9BCMfU1IHpB38e+PLWfyV3Pr45o3e+jB+Lj0Am2EaLK0 Bc/A==
X-Gm-Message-State: AOJu0YxHkdxwDD0XpMJnNfNF8vH3fDBELN9Ih2lF4B/aw7v+Phu4jg4h L86QK+IdE2hnL9dG9Ih/cJ+uKoN4eG5rlSfIj8LN80GsixGRYeWov4g7rw==
X-Google-Smtp-Source: AGHT+IEIpovjZUEYUKeVOU2GLqfGd6DMr9BTRdmiGPLrG2M7nv8NpLjXuBe7qef5aaP8lF6LQ+eS9z5UZnwfW+oPO+4=
X-Received: by 2002:a50:f60c:0:b0:523:b133:57fe with SMTP id c12-20020a50f60c000000b00523b13357femr127059edn.1.1694788268284; Fri, 15 Sep 2023 07:31:08 -0700 (PDT)
MIME-Version: 1.0
References: <DU0P190MB1978B5A8AA3745770E94EEA5FDF6A@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
In-Reply-To: <DU0P190MB1978B5A8AA3745770E94EEA5FDF6A@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
From: Jonathan Hui <>
Date: Fri, 15 Sep 2023 07:30:51 -0700
Message-ID: <>
To: Esko Dijk <>
Cc: "" <>
Content-Type: multipart/alternative; boundary="000000000000b43b92060566a483"
Archived-At: <>
Subject: Re: [dnssd] SRP: how to remove all published services?
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 15 Sep 2023 14:31:12 -0000

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

Jonathan Hui

On Fri, Sep 15, 2023 at 7:17 AM Esko Dijk <>

> A question - in, 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