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

David Schinazi <dschinazi.ietf@gmail.com> Mon, 31 January 2022 19:20 UTC

Return-Path: <dschinazi.ietf@gmail.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 0C8E13A1401 for <dnssd@ietfa.amsl.com>; Mon, 31 Jan 2022 11:20:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 jhxEkYWzEXBv for <dnssd@ietfa.amsl.com>; Mon, 31 Jan 2022 11:20:48 -0800 (PST)
Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (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 5A6793A13FD for <dnssd@ietf.org>; Mon, 31 Jan 2022 11:20:48 -0800 (PST)
Received: by mail-pj1-x1036.google.com with SMTP id g11-20020a17090a7d0b00b001b2c12c7273so471279pjl.0 for <dnssd@ietf.org>; Mon, 31 Jan 2022 11:20:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=uzJTXTfPRqyFQJLWkWOCYjDjrjbpLP2aODXfodtBozc=; b=icVSdskf/ia7WfvF49/6nobVqpQZaU45SWdsKEPXlUmQR3pm170GHpggfMy3HGb8Nq j5lUFwE9Sds9X41kt63szKQ9cqCqKzaEDMaLiihNJMsqfQwhSY00c4mfoECq/KSVYQmj GkTAU2N6R3nRihF+nc07KKtoIPLn3aLYtp7f2nyZdJrMniE3SmedjuEqXxTcYWVt850z z8OPuN1SeFGExZAVkDLZgMW5dG+8I0Qb1EWRK2ZhBfpeHZKk9O/LuDz87nwN6FZsnVex fErW2Rgs57JOT+lQyhQXJeMaeo12OQi1T1iEw3BB/08hWrN+gkIhIJZyPEUY7+Bi26aq QprA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=uzJTXTfPRqyFQJLWkWOCYjDjrjbpLP2aODXfodtBozc=; b=Sc3RZaxin1046j/v5q+LjpQ/SIF1M/tYsuISa7bjXXRSc+SgxGG8Klf9BJ6WPe+5cO mk8aeg/gVUmUKeC0Ewo0b6FoWvdNOc7M8jZ8+d+HrSW9+kQlyGoWyY2I4YZyGnEmX2uu MCcvVrjwNBF40G9G9Rt4xjkbTgwqpzULXTEgbO+k0lj4AqyXz/rL34NlsF8o9qd1BUua /WQJRdR8WDx2LsUOClrexwWDS1wkuafc/skGr46DnzRjebzW47IodHu86KMmEV2E5jOt 6O51OkWaGWsJKAiNoZoUw+jRYJKX2fAFvZkr3wbuSysZIR+C6roW7tUtSvGnEXZDpRLf P0qg==
X-Gm-Message-State: AOAM530femdqATT+TYIpnrcKAfpYIB655JdpWGrEEGT33ssh/Nwgv71e UffZ//oyNxBNJZqNzEGX5drWf3U6JAD/OFk3p9x02OGg
X-Google-Smtp-Source: ABdhPJwdYIgO9ZielFUwjh1er1QrJj+vL4KkYXfVoOPzmBQl5nIC07uyZgk/NfyaGWakrT4treSE9GhtQ/WZlOI+1G4=
X-Received: by 2002:a17:903:28c:: with SMTP id j12mr22548106plr.83.1643656846353; Mon, 31 Jan 2022 11:20:46 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+4Fmfw6KF23ZrKJT9tb8xzy_GxrD4YbTwRPHe41UTNkBg@mail.gmail.com> <CAPt1N1knP7M2PC0-=OYN_g3RJCG4-13XCVW_HxbJ-=Os1c5FKQ@mail.gmail.com> <CAPDSy+4v0U3HJeuJC14zeeNMXhYNj-U0KT81SUNQER83VzPxPw@mail.gmail.com> <2C98ED34-73BD-462D-9540-23D74294CB59@cisco.com> <CAPDSy+5ApnKZ=EhyRc0JwU8mFjz8fMKdg8Or4ap3mkPJGHZWVg@mail.gmail.com> <F80B51C8-2423-4F5F-8F5A-1C9A3F6700AB@cisco.com>
In-Reply-To: <F80B51C8-2423-4F5F-8F5A-1C9A3F6700AB@cisco.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Mon, 31 Jan 2022 11:20:35 -0800
Message-ID: <CAPDSy+4DOeCbVSGS79gSQMKBBZ6nu6vnyxseBg5XHX_0ncVA1w@mail.gmail.com>
To: DNSSD <dnssd@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000075a7af05d6e5aeb6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/tv0Ap2tW26jKb43qazAgCohvg3Q>
Subject: Re: [dnssd] Should DNSSD meet at IETF 113?
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: Mon, 31 Jan 2022 19:20:53 -0000

Hi DNSSD enthusiasts,

Based on the responses received so far, it sounds like no one has a
pressing need to meet at IETF 113.
DNSSD is therefore not going to have a meeting at 113, and we'll schedule
an interim in April or May.

Cheers,
David


On Tue, Jan 18, 2022 at 10:54 PM Eric Vyncke (evyncke) <evyncke@cisco.com>
wrote:

> Which is of course a valid explanation ;-)
>
>
>
> Regards
>
>
>
> -éric
>
>
>
> *From: *David Schinazi <dschinazi.ietf@gmail.com>
> *Date: *Wednesday, 19 January 2022 at 00:26
> *To: *Eric Vyncke <evyncke@cisco.com>
> *Cc: *Ted Lemon <mellon@fugue.com>, DNSSD <dnssd@ietf.org>
> *Subject: *Re: [dnssd] Should DNSSD meet at IETF 113?
>
>
>
> Hi Eric,
>
>
>
> The issue here is that our authors are going to be very busy with their
> day jobs until at least IETF 113, so scheduling an interim before then
> wouldn't help much. We're going to meet after IETF 113 so they get the time
> to work on the documents.
>
>
>
> Thanks,
>
> David
>
>
>
> On Tue, Jan 18, 2022 at 2:02 PM Eric Vyncke (evyncke) <evyncke@cisco.com>
> wrote:
>
> Or should the interim be scheduled before IETF-113 ?
>
>
>
> Just asking, no pressure applied ;-)
>
>
>
> -éric
>
>
>
> *From: *dnssd <dnssd-bounces@ietf.org> on behalf of David Schinazi <
> dschinazi.ietf@gmail.com>
> *Date: *Tuesday, 18 January 2022 at 22:07
> *To: *Ted Lemon <mellon@fugue.com>
> *Cc: *DNSSD <dnssd@ietf.org>
> *Subject: *Re: [dnssd] Should DNSSD meet at IETF 113?
>
>
>
> Thanks Ted,
>
>
>
> This makes sense to me, especially given how easy it's been to schedule
> virtual interims. If anyone would rather meet at IETF 113 because they have
> something time sensitive to discuss, please let the chairs know. If no one
> does so, we won't schedule a meeting at IETF 113, and plan to have an
> interim in April or May.
>
>
>
> David
>
>
>
> On Tue, Jan 18, 2022 at 5:48 AM Ted Lemon <mellon@fugue.com> wrote:
>
> Since nobody has jumped in to respond to this, I will just restate
> publicly what I said privately to David, which is that the March IETF
> meeting comes at a time when I'm just off of a major deadline at
> work (every year, unfortunately), and so from my perspective it would be
> more productive to have an interim a few weeks or a month later, so that I
> have time to update the documents that I owe the working group without
> having to rush to get them done by the meeting cutoff. I realize that I'm
> not the only person whose needs should be weighed here, but my vote is to
> not meet in March, but to instead meet in April or early May.
>
>
>
> On Mon, Jan 10, 2022 at 7:27 PM David Schinazi <dschinazi.ietf@gmail.com>
> wrote:
>
> Hi DNSSD enthusiasts,
>
>
>
> IETF 113 will be a hybrid meeting in Vienna on the week
>
> of 2022-03-21, meaning that it will be possible to both
>
> attend and present both in-person and remotely.
>
>
>
> Does anyone have DNSSD agenda items for that meeting?
>
> If we have enough items, we will schedule a DNSSD meeting.
>
>
>
> Note that the deadline for the chairs to request a session is
>
> 2022-02-04, so we'll need to hear back from you several days
>
> before that.
>
>
>
> Cheers,
>
> David
>
> _______________________________________________
> dnssd mailing list
> dnssd@ietf.org
> https://www.ietf.org/mailman/listinfo/dnssd
>
>