Re: [dnssd] Should DNSSD meet at IETF 120?

David Schinazi <> Fri, 26 April 2024 22:36 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6EFFFC1654EC for <>; Fri, 26 Apr 2024 15:36:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Status: No, score=-2.095 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 47hlkEKC2Bgn for <>; Fri, 26 Apr 2024 15:36:44 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::529]) (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 956EDC15108E for <>; Fri, 26 Apr 2024 15:36:44 -0700 (PDT)
Received: by with SMTP id 4fb4d7f45d1cf-571c22d9de4so3620452a12.3 for <>; Fri, 26 Apr 2024 15:36:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20230601; t=1714171003; x=1714775803;; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=PqkQ6lKbDdJP2L+nar/EsMqRynLTzznm/UPjC/hf/Hs=; b=E9uYfyOXDaSxNNbpDTMDpj6k4tElQL/PmJzXjwzbICvJdEOlunt+2w5OkCjt+VDjqI +9TGZL36YFSinxlN/NtZ3AxVNhvFSGg5Ftcttxfio0aI58tkCiZlpU43c4Sit+9bkpf/ 6+RMRQq2IkAoGW8e3sskP92LqVa8VNa0hNBBX17WaBW/p+kXZhlcc5stGBFBuFrh+vyS UG3Ul3ab82fjLZE47zpRymugMRMtXlTgJqHcSFdGAlA78gaTq6LrjFgGiqLXBZ52QU+x 5qr89iWkLH+gCJse47EANZ3+ZAkCBcPG4o5M5b4KUlzGE1Zkt1qrnplkPvrALwKEfTnh JBbA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20230601; t=1714171003; x=1714775803; 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=PqkQ6lKbDdJP2L+nar/EsMqRynLTzznm/UPjC/hf/Hs=; b=pCMPi37ioDATz68M8vDMFnTb62FWyX9ieaQpxGTPKhNK+ctpp1GKA26W2fJXUVlUPb V7QkOkV/U0APYGMZ3mAS/WxmpvjtPm7iSGdfr1G5acOhV6RQw4Lj5FfMYzf2it/uEdQ+ Igi/Mqtk8iqMAIX7yVIFtJbYfK/KtWoqak8ADbAKe8XeHzfVzmrPZ6AzXNqB1VMpqaCH jCXL7HfbbaMrGylnGjWKxhz+J/l0+K2FQvITqEhPtZxH36xJF4d1ObX4GCEl6qEb/+jK kI2SJoyGkpc/VCVeB5Hbwi9nwEzsBSyMYHWLY4T4rwg0toE9nwl4ine0Kfe0PkeudhgJ Wamg==
X-Gm-Message-State: AOJu0YzuHoti7ulxkDKZzB44deSc1Yml9Do6FmBOOCylQb4ryK0wngOw rqgWOoo3poH/pbfOITQc3I9+4s4rxlVDBe4cs7b0Kutfc15w4MhEdXlWuVbjOzHII2f0Ow0ivn9 V8b3X88nISfajPw4oRrE2bqy2ed2OQw==
X-Google-Smtp-Source: AGHT+IHAWrpsOfuLjTg35SrdEzsTV42v4OZpxqwxHHjjDywcsNFMSrVrsWcjq9Eqpy1Mo0JGR6Ui/pRt0/Bq0RJmmcE=
X-Received: by 2002:a17:906:7f03:b0:a52:6435:ef09 with SMTP id d3-20020a1709067f0300b00a526435ef09mr2836846ejr.76.1714171002626; Fri, 26 Apr 2024 15:36:42 -0700 (PDT)
MIME-Version: 1.0
References: <> <>
In-Reply-To: <>
From: David Schinazi <>
Date: Fri, 26 Apr 2024 15:36:31 -0700
Message-ID: <>
To: Ted Lemon <>
Cc: DNSSD <>
Content-Type: multipart/alternative; boundary="000000000000b22c250617078993"
Archived-At: <>
Subject: Re: [dnssd] Should DNSSD meet at IETF 120?
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, 26 Apr 2024 22:36:48 -0000

Thanks Ted! Do you have a rough estimate of how much time you'd like for
each of these?
As usual, we'll focus meeting time on adopted items before considering
individual drafts or other topics.


On Fri, Apr 26, 2024 at 2:06 PM Ted Lemon <> wrote:

> I think so. We actually have at least four things I want to talk about:
> 1. A report/discussion on the EDNS(0) TSR update and implementation
> 2. A discussion about compressing SRP updates for constrained networks
> (has suddenly become topical)
> 3. DNS Push additional data update (has also suddenly become topical)
> 4. Updated Advertising Proxy document (stretch goal)
> A fifth topic that's sort of crossover between DNSSD and SNAC is automatic
> centralization of SRP/DNSSD on home/SOHO networks. This has become a hot
> topic for home routers and it would be nice if we had a way for home
> routers to announce that they can act as centralized DNSSD servers and for
> SNAC routers to take advantage of the centralized SRP/DNSSD service. This
> last bit is nothing new—it's on the SNAC charter—but I've had people asking
> me more urgently than had previously been the case to figure out how to do
> this, so...
> On Fri, Apr 26, 2024 at 4:50 PM David Schinazi <>
> wrote:
>> Hi DNSSD enthusiasts,
>> Planning for IETF 120 has started. The chairs are wondering whether DNSSD
>> should meet at IETF 120 in Vancouver this July. Please share requests for
>> agenda items (including expected durations) in response to this email. If
>> there are sufficient requests, we will schedule a session. The requested
>> length will also depend on the agenda requests we receive.
>> Additionally, we would like to hear feedback about our session at IETF
>> 119 in Brisbane. As a reminder, we tried something new by having a joint
>> session with SNAC. We're interested in any thoughts you might have about
>> that experiment. In particular, is this something that we should consider
>> repeating?
>> Thanks,
>> David
>> _______________________________________________
>> dnssd mailing list