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

David Schinazi <dschinazi.ietf@gmail.com> Tue, 18 January 2022 23:26 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 6CB573A12EF for <dnssd@ietfa.amsl.com>; Tue, 18 Jan 2022 15:26:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, 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 v--2N0NaEEGX for <dnssd@ietfa.amsl.com>; Tue, 18 Jan 2022 15:26:04 -0800 (PST)
Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (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 869FC3A12F5 for <dnssd@ietf.org>; Tue, 18 Jan 2022 15:26:04 -0800 (PST)
Received: by mail-pj1-x1031.google.com with SMTP id hv15so749865pjb.5 for <dnssd@ietf.org>; Tue, 18 Jan 2022 15:26:04 -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 :cc; bh=S10A1LKrC51VBNRKQFj4CS6J6p/GjRyp0ahdCZbaxWg=; b=pQC7bxw5BH3kB/TycZMjFHGI4dMrKJ+QWcUF1+VAP7q9D9Qm2VrnqlRQJQo/Vhlmb0 VgnIXP6AZwt/VLedjmW86DG7mszRgmwC7TfyXUG3rrU+QPOhiGcU9GWBvpftVrTt4uKQ ixDjITYOYrlY3m4jzE5DkRW6K9hmn0HCkXHOfonCkb539rbKlg7ODlBHOlxeoaZFTDF5 bNctJTAmi0uI6jgaWSMyIo7n9iF40WLk/D9VtcpS6uQbjZdUlYvYO+vD6gPXuFiOSLFY p05VjhQdsXuWMpFY2TozG/753YqlcqK9uHRNjT5r7+BuYxfyOUstKaUvs44LrsQCwmCG l+Eg==
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:cc; bh=S10A1LKrC51VBNRKQFj4CS6J6p/GjRyp0ahdCZbaxWg=; b=Uko8pBX1OVGXve7ucz3EzdwR42Av3Xdya8LEhYaONU5zNGGqL5OdNAo3+UZaCY+T7f kCIA7W32yY0DolvZtejUMTS63zE0dA9JX3wZ7NNEGWfLq8A1+YDNJO6dSM4ou1mUV5mk 5HGLoYHHj1LcUQmtRUSHG1g+kWujiUi5xX/wHZKQNpc7eUzFJdX+uIb6WybZ6f14Jzkk BhBSrq+X2CZegehQCbT/ebVxBiSe26JqOslpUYm3hZ6F+s+xsqkqAMmVZseXFL58iHrJ usyalGhCE7mEWOJJoR2KnJwcKsNjyHIWJUTaby97rpBFILCCsRCce9fwvg/oG7CGOlZl jaiQ==
X-Gm-Message-State: AOAM531BV1pL8aXTc/QUkEB/2egYD/DvXzX+fkSAe4m7Uib/ejYAklK2 tAWzs8hjcGDruWdrrBMDe92kVunssddYsa6m4z8=
X-Google-Smtp-Source: ABdhPJz06UAdHQatXUzqGImicQdh2VyoHuosmrgT8c3kdyIbnOCDu5VNFVur5ThGYH9nnOPQldJVP9uKBXKS0wAsmAc=
X-Received: by 2002:a17:902:ec8b:b0:14a:3eb9:9c54 with SMTP id x11-20020a170902ec8b00b0014a3eb99c54mr29509495plg.110.1642548362929; Tue, 18 Jan 2022 15:26:02 -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>
In-Reply-To: <2C98ED34-73BD-462D-9540-23D74294CB59@cisco.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Tue, 18 Jan 2022 15:25:51 -0800
Message-ID: <CAPDSy+5ApnKZ=EhyRc0JwU8mFjz8fMKdg8Or4ap3mkPJGHZWVg@mail.gmail.com>
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
Cc: Ted Lemon <mellon@fugue.com>, DNSSD <dnssd@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b2e9e005d5e39719"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/GPMjjnlkvb-bwK8HFn0GmndxF6o>
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: Tue, 18 Jan 2022 23:26:10 -0000

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
>
>