Re: [dnssd] Should DNSSD meet at IETF 110?
Ted Lemon <mellon@fugue.com> Wed, 06 January 2021 12:36 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 8A8563A0688 for <dnssd@ietfa.amsl.com>; Wed, 6 Jan 2021 04:36:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 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] 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 CrCoYp49QlNS for <dnssd@ietfa.amsl.com>; Wed, 6 Jan 2021 04:36:33 -0800 (PST)
Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (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 5E5863A0FD5 for <dnssd@ietf.org>; Wed, 6 Jan 2021 04:36:10 -0800 (PST)
Received: by mail-io1-xd2e.google.com with SMTP id r9so2555859ioo.7 for <dnssd@ietf.org>; Wed, 06 Jan 2021 04:36:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=pRK5oeA+zqySR1h/Ya8NzzhVfdsdaRQJdxfu5lbxCkQ=; b=KMStYbiz2jfux2ERXYFE0OBvEf9suhJZWlUhbmii4F7dwgT9m+5PjlcD4bLq2gqqbM Ga7RLl1Uy5rJUiUrFBf11G0i9wZGBL3zRFpHnthJA6d9bM6YCk5xsCKPL5ujO8Bcjavb y8LjWZONmVrRWmNr/CE9l0ROu/nHETlBBaxx8c/nGuGcx8d7a7YqnE4Sa1DwFDOBCcxh l1X8goiu3PJ2+9yatlnyAGm08+NVS+/Lf5MdTCWbo3cOEj9bwLoWK5/IjC0KQfgFZlI3 Sp8CG0LjEJBApYAF5U5ICgFyd1S+gswG7gynqPNvOifqpDjQS+IWlSn851y2QDb6S5gK xu8g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=pRK5oeA+zqySR1h/Ya8NzzhVfdsdaRQJdxfu5lbxCkQ=; b=qMfG8iGMHtUEn4VxKfMl785E6DADO9PIGr6SvVqo8zOtL9wFrInZNm5q2d2RX9Agtl qvu4jGbE63YTnhkfWqcEzsr2/Z+U91xDFoGemzD+/rkJ6YwRfQrsxJfU8C7YddrKLCqI B836p5bUdMBEaJ0lI2L5SXJgzhSjGqoZHOpuOoXgVh4CwYoTA2oWYpg7KwYvX+chem4m 9/412VRRz0Q89wnb+cRko2ZJWqhVmDJUkJ2xQlJt9ul3cA58V1vE8IJxBgM0h2bkDxyc lTCvkS1DgJZlkAYjiaQnK+SlwnnMllE9EKY8kpGD0GlnvEN3+tW/sN/bZQiWNH3vf+xQ jhEw==
X-Gm-Message-State: AOAM5330xzBqfDaccVefuJwX9gPSfTD0+L5s9gE6Vm+gvEkg64oMXIOZ BT6JXJ6yAmSqdMJHi09AM87a0w==
X-Google-Smtp-Source: ABdhPJxfB9vhSk58NZjBZvh7/wf86a7H/UKfxR3vjv8NRJFgGUlym6ZCSQPcYNI9Y4MmZZBp+hu19A==
X-Received: by 2002:a05:6602:45c:: with SMTP id e28mr2646437iov.196.1609936569667; Wed, 06 Jan 2021 04:36:09 -0800 (PST)
Received: from mithrandir.lan (c-24-91-177-160.hsd1.nh.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id d5sm1939649ilf.33.2021.01.06.04.36.08 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jan 2021 04:36:09 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <F316A125-AE31-4ABE-8D33-40A1EBF6EBA4@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_51F02A31-0008-42B4-95BA-7BB00D68C83D"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.2\))
Date: Wed, 06 Jan 2021 07:36:06 -0500
In-Reply-To: <CAPDSy+7f4V8s7d_w1oJ-MdE3v0c6a_7NwPb8Q-veA6V-KHr0Nw@mail.gmail.com>
Cc: DNSSD <dnssd@ietf.org>, Barbara Stark <bs7652@att.com>
To: David Schinazi <dschinazi.ietf@gmail.com>
References: <CAPDSy+7f4V8s7d_w1oJ-MdE3v0c6a_7NwPb8Q-veA6V-KHr0Nw@mail.gmail.com>
X-Mailer: Apple Mail (2.3654.60.0.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/xgC6gDzeaRKOhEXI-fdNb54jdkg>
Subject: Re: [dnssd] Should DNSSD meet at IETF 110?
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, 06 Jan 2021 12:36:35 -0000
On Jan 6, 2021, at 7:28 AM, David Schinazi <dschinazi.ietf@gmail.com> wrote: > Are there DNSSD topics that you would like to discuss at IETF 110 (early March 2021, virtual)? If yes, please share them here. In particular, the chairs would like to see discussion of those topics on the list to justify scheduling an in-virtual-person meeting. The deadline for requesting a meeting is 1/22, so please start these discussions ASAP so the chairs can make a determination before then. Yes, please. I think you’ve been seeing discussion of the srp draft on the mailing list. We also need to discuss the advertising proxy draft, and hopefully adopt it. We will also be talking about an autonomous replication solution for SRP, which should be ready to discuss in March. It might be good to do anotther DNSSD+Homenet meeting, because then we could talk about the related work going on with stub networks.
- [dnssd] Should DNSSD meet at IETF 110? David Schinazi
- Re: [dnssd] Should DNSSD meet at IETF 110? Ted Lemon