[dnssd] Updates on Service Registration Protocol and Advertising Proxy documents
Ted Lemon <mellon@fugue.com> Wed, 14 July 2021 13:47 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 D850A3A177A
for <dnssd@ietfa.amsl.com>; Wed, 14 Jul 2021 06:47:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 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_BLOCKED=0.001, SPF_HELO_NONE=0.001,
SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001]
autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44])
by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id pLJ3vltzv8yV for <dnssd@ietfa.amsl.com>;
Wed, 14 Jul 2021 06:47:27 -0700 (PDT)
Received: from mail-ot1-x329.google.com (mail-ot1-x329.google.com
[IPv6:2607:f8b0:4864:20::329])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 379C03A1776
for <dnssd@ietf.org>; Wed, 14 Jul 2021 06:47:26 -0700 (PDT)
Received: by mail-ot1-x329.google.com with SMTP id
w8-20020a0568304108b02904b3da3d49e5so2537360ott.1
for <dnssd@ietf.org>; Wed, 14 Jul 2021 06:47:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=fugue-com.20150623.gappssmtp.com; s=20150623;
h=mime-version:from:date:message-id:subject:to;
bh=wXV1mEbMVqv4MIr6hQUqYwZ9UOoT5drT/OOg3kZOY1M=;
b=MUjXS+Z1jKrO6kzjBv2JTcuFuYO1OJ+Oy04e37YdWFEYxj20eRVxCbG2aMVAgK1/cS
qzCGpbJuZ9AZ+WtuaXRdyCQZ1+AjckEfVW6VNVoyKF9mXPIiUFGuqTflFrQzaS2pRtwt
3Ad0aJ0ls8JqEInN+V/fBul4OxbixjXa+fG4tNgso+HoH3m6wtY0z4URR/1rLMrO3AvK
0iy+BGeVzSheBWsQ6mUoIMnFP2vEMPnZ6MkpBW6qH0WfUUbth5RZqh9ApBAu/X09jtfy
KxTl4Bx9zoMrZvinufcWIkS2+cnIjjgkaDbHULpTFNufzYaVZTHAFVCaInvc93twoRvK
D+ZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
bh=wXV1mEbMVqv4MIr6hQUqYwZ9UOoT5drT/OOg3kZOY1M=;
b=MbPcysKBZzWpuCwncDKtE4JDdI62FAbH/kGaTWpyzAdtE+ahECc3Z6VNXIMuS2fsBo
WFm+OTnUGYuHlyUY6Jp0qBORLQhZ+s1zxpCejBle+v9/iWl25bkaiYDRB9To6iv4NXC4
LYkMJPpgnckY1GXVvp5IfFN8prMR0zNoX15ijACC90+BHKpWxgM8RNXdRqJ2Qj5eU7OP
DeJCLZRFlu6DlWolRV/GHvNsFgo4iTFzW35ItZXXY/M/HJ1Vn9P27u6aS2sSqWpTglKQ
1t6rIg11wVgUX73UGt76+W2W08UUaR3ZqtZLPrqVA1O1HyslRomqA4NXhsXvoJGL/5RI
zqoA==
X-Gm-Message-State: AOAM532j63JMa1D/7zSrWPH6BS7NZy4T+8ZutrcnQvLVCmUKshyK7Qnt
UvYLzNmBN3pjmK2CtW1QTCeUNdPGOKzlRmB38edSt2BFjkA=
X-Google-Smtp-Source: ABdhPJzsO5dKCgGV2dr0X/2JzjRIoyz/v4LExRYlO3cPSNCjYtd3965MRYFIUbwBqvG/6RILqnQwoVRmt03LiDGnjls=
X-Received: by 2002:a9d:6453:: with SMTP id m19mr8326751otl.63.1626270445664;
Wed, 14 Jul 2021 06:47:25 -0700 (PDT)
Received: from 649336022844 named unknown by gmailapi.google.com with
HTTPREST; Wed, 14 Jul 2021 06:47:25 -0700
Mime-Version: 1.0
X-Mailer: Superhuman Desktop (2021-07-13T22:05:53Z)
X-Superhuman-ID: kr3jf65c.d4ded10c-e09f-4755-9255-b77f96301386
X-Superhuman-Draft-ID: draft0053dd00e30bd512
From: Ted Lemon <mellon@fugue.com>
X-Superhuman-Thread-ID: draft0007aa64f578b41c
Date: Wed, 14 Jul 2021 06:47:25 -0700
Message-ID: <CAPt1N1mHFQGTLXZLDfRtSdYaqR2r_WcUE2fL0q=KMYh==mSkCg@mail.gmail.com>
To: dnssd <dnssd@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000390f8a05c71598d1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/fRkYHIuHfa1wocbZvyVFq1R0GRY>
Subject: [dnssd] Updates on Service Registration Protocol and Advertising
Proxy documents
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Jul 2021 13:47:30 -0000
I’ve posted updates to the SRP and Advertising Proxy documents. There are only two minor changes to SRP—I think it’s ready for last call at this point. Advertising Proxy is still a work in progress. I added a section that talks about a different way of handling mDNS conflicts. I think this merits further discussion. My previous ask for the working group was to adopt it as a work item; I think there was reasonable support for this in the meeting, but I don’t think a call for adoption has happened yet. In addition to these two documents, I’ve written two other documents in anticipation of the upcoming meeting. Unfortunately I finished them later than I’d intended, and they weren’t able to get through legal review in time to post. Legal review will probably happen next week, and hopefully I’ll be cleared to post them, although that’s never guaranteed. The two documents are: - a 20-page specification for a SRP replication protocol, which is useful for situations where for example you have one or more stub networks to connect to an infrastructure network such as a home network, and you need to provide some reliability but don't have a way to set up a reliable primary name server - A 10-page specification for ad-hoc DNS-SD zone discovery using mDNS, so that a piece of ad-hoc infrastructure such as an SRP replication zone can be made available for DNS and DNS Push queries, reducing the need for multicast service discovery for such a zone These are both things that we've implemented in the latest seed release of TVos, which runs on HomePod Mini and the most recent Apple TV hardware. I don't consider either of these to be done—there are open questions on both, and I think it would really help to have more people looking at the work and thinking about those open questions. If we can get consensus on solutions, and that consensus isn't compatible with the current implementations, I think that's fine—in the case of TVos, firmware updates are easy and encouraged, so there shouldn't be issues with needing to support legacy implementations. (If you are tempted to update your devices to try out the new functionality, talk to me privately first!) For the upcoming meeting, if chairs are willing, I'd like to quickly discuss a WGLC for SRP, and the call for adoption for the advertising proxy document. I'd also like to talk about open problems in the advertising proxy document, and if time permits I'd like to talk about the SRP Replication work and the ad-hoc zone discovery work. I'd like to see both of these documents adopted by the working group if possible, but I think a call for adoption on the 27th would be premature since people likely won't have had time to review the documents.