Re: [dnssd] DNSSD at 118?
Ted Lemon <mellon@fugue.com> Mon, 18 September 2023 18:27 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 0B798C15106F for <dnssd@ietfa.amsl.com>; Mon, 18 Sep 2023 11:27:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 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_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20230601.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6epqXcLdKfNt for <dnssd@ietfa.amsl.com>; Mon, 18 Sep 2023 11:27:10 -0700 (PDT)
Received: from mail-qv1-xf29.google.com (mail-qv1-xf29.google.com [IPv6:2607:f8b0:4864:20::f29]) (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 ietfa.amsl.com (Postfix) with ESMTPS id CC23CC14F73F for <dnssd@ietf.org>; Mon, 18 Sep 2023 11:27:10 -0700 (PDT)
Received: by mail-qv1-xf29.google.com with SMTP id 6a1803df08f44-65627d499e1so21717676d6.0 for <dnssd@ietf.org>; Mon, 18 Sep 2023 11:27:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20230601.gappssmtp.com; s=20230601; t=1695061629; x=1695666429; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=9xIoST8A6Qvibxg4BA0u5C4rnAe6B88s8Sx8e6+r5DU=; b=rz3/x3SDggrW0G1ZgZhLEUf80UnLwzGc+qHYlJJQPXTxR7tDMHCNnJN7UjJ56Kc9oe A3kCkl7xVyx27Kv6qtE+MqYfJt+QO/YA6Cu6bUJWwAVFETlFeBOKOfxQuVU3ildl7fxe l5LuVYJg5ICvNeQuraLgfTCB/a8wOhcNOUUIZg0RUzqh9I22NPfgQLld8Q9Nh/y9kIFr q83rVQyJs/WubfFSEPp3w/OntnvEblVaKulnlIthP3xpToBl8M26B/+oMb6AULtKdtvA eqMEyj5T0x70Zz5+w49apCCaAofNjRbPQSIzz08FQZ7Bp73jrrU8EDoMAcTlHIqEaark cpHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695061629; x=1695666429; 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=9xIoST8A6Qvibxg4BA0u5C4rnAe6B88s8Sx8e6+r5DU=; b=vgC6S28K8ghzNV5iZ51SjeRgGQIYCP2Z+nuTQKcdOER5c0A2m8L1gM3KYHbNSHSKMr BoOgVxN1X5m1RrblM5Rp+lDKnkqr+wNb/N7wHq3euDolAZ/G/8OTsiy08+L7Djf9M11O p7NnSW2C/F4rJ6GGiXhgewfMtz3+ph+jbEyGOwg+6wWmIzXieeGHL7RAjlApAnATJg4p aC+8LdWjVyhVQF5LOuzI+QdYbk/SSt7PuRVZZPvT++RnQLHpjwdPcAN+xEREP7j4sfj8 yNrbs2wdrPdd7MISPst9pCbtxJt1Oe/LzBtlOZXOMXDmCAkZPXHLPwi+pAeWNS1MyAIU qmNw==
X-Gm-Message-State: AOJu0YwzPTryjEGmRE7ZKtPAk9YADMr+UHS9yPPVwSrRIAXgETEfHFuz YaM/gMnQs6+auhzIt/8WQ55nRktXEyS2EicavlYvtQ==
X-Google-Smtp-Source: AGHT+IGAsxbYgeP5AeY5Jxmcd5fqdW22dwuKPUn3FRzs4Y2j0OL8Xa8087zlk277+krY/9o1TsEEZaneppyKHmR0qsE=
X-Received: by 2002:a0c:de13:0:b0:658:310c:f6ca with SMTP id t19-20020a0cde13000000b00658310cf6camr1810808qvk.42.1695061629376; Mon, 18 Sep 2023 11:27:09 -0700 (PDT)
MIME-Version: 1.0
References: <CAPDSy+51AvTj=1GPNNN=WnAgQz8wF28GDxL0oTaM=8d2iiYwOw@mail.gmail.com> <CAPt1N1mptG30zQH_7BvWuOYAFv7oB4LdgLAhSsy-n9=kpiqBUA@mail.gmail.com> <DU0P190MB197845E60D5CE507CA31BA44FDF7A@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <CAPDSy+4Hf5543Yej06uuxo_4JCv8sJ0VMFvBCd+m943a+MSPrA@mail.gmail.com> <CAPt1N1kQCng2rROyKxP8+vG6HfmR38OS+e=hqFSo_ZHE6pNd0Q@mail.gmail.com> <CAPDSy+5+U7wCk-G1JG=XGONv4FEitscafB_XPmk20uQ9DVSA3A@mail.gmail.com>
In-Reply-To: <CAPDSy+5+U7wCk-G1JG=XGONv4FEitscafB_XPmk20uQ9DVSA3A@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 18 Sep 2023 14:26:58 -0400
Message-ID: <CAPt1N1kmY5ATSRvPd76ztWBvx=4nZf-dWWbjiHziNsZW2Bxzxw@mail.gmail.com>
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: DNSSD <dnssd@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004ab1db0605a64a42"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/9ol0wzzyIkohgom6M5gnVT_eE0E>
Subject: Re: [dnssd] DNSSD at 118?
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.39
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, 18 Sep 2023 18:27:12 -0000
At least 1:30? Op ma 18 sep 2023 om 14:00 schreef David Schinazi <dschinazi.ietf@gmail.com> > Great, thanks. For the official WG session, we have the option of > requesting 1 hour, 1h30, or 2h. Any opinions? > David > > On Sat, Sep 16, 2023 at 5:03 AM Ted Lemon <mellon@fugue.com> wrote: > >> Thanks, David. Sounds good. FWIW, in addition to the IESG work I owe you, >> I just had a brainstorm (in lieu of sleep, I'm afraid) about how to fix >> TSR. So I'm going to publish an update to TSR that I think will finally >> make it work the way it should have in the first place, and will want the >> WG to think about whether I'm right. It might be worth discussing this in >> Prague. >> >> On Thu, Sep 14, 2023 at 1:22 PM David Schinazi <dschinazi.ietf@gmail.com> >> wrote: >> >>> Thanks Esko and Ted, >>> >>> What you're suggesting is definitely not crazy. In my experience, I've >>> found that meetings to edit documents work best with a smaller group (in >>> the case of DNSSD I'd say the editors and implementers) while official >>> working group meetings have a bigger audience and are most useful to get >>> the output of the smaller group shared with the wider group to see if >>> anyone has thoughts, ideas or concerns. Sales pitches are also useful there >>> to get new folks involved in upcoming work. In an ideal world, we can have >>> both in Prague where we first have a smaller side meeting earlier in the >>> week and then have the official WG meeting later in the week. The smaller >>> side meeting would be open to anyone interested but with a goal of >>> participation more than observation. The chairs could help coordinate that >>> if the group thinks this is a good plan. In particular, let us know if >>> anyone is interested in joining the side meeting remotely because >>> organizing VC for those is generally doable but isn't always easy. And for >>> folks planning to attend in-person and interested in the side meeting, let >>> us know what day you're planning on flying in/out to help scheduling. >>> >>> David >>> >>> On Thu, Sep 14, 2023 at 6:51 AM Esko Dijk <esko.dijk@iotconsultancy.nl> >>> wrote: >>> >>>> +1 for the do-actual-work proposal. Side meetings are common at IETF >>>> so we can have those. >>>> >>>> >>>> >>>> > and I certainly don't object to sales pitches and status reports if >>>> people have those as well. >>>> >>>> >>>> >>>> I think giving an intro as to what the open issues or missing parts are >>>> of a solution is still useful. Because not everyone is up to date. It’s >>>> more of an anti-sales-pitch then ;-) >>>> >>>> >>>> >>>> *From:* dnssd <dnssd-bounces@ietf.org> *On Behalf Of * Ted Lemon >>>> *Sent:* Thursday, September 14, 2023 15:41 >>>> *To:* David Schinazi <dschinazi.ietf@gmail.com> >>>> *Cc:* DNSSD <dnssd@ietf.org> >>>> *Subject:* Re: [dnssd] DNSSD at 118? >>>> >>>> >>>> >>>> I think there's a tendency at IETF meetings to present status and sales >>>> pitches, and maybe have some brief—possibly well-informed, possibly >>>> not—discussion. I do not know of a specific thing that needs a status >>>> update at the upcoming IETF, although that could change between now and >>>> November. However, one thing that I wish there were more of at IETFs is >>>> actual work being done, as opposed to status updates and sales pitches. I'm >>>> planning to show up in Prague, as I suspect others are, and I would like to >>>> do some work. I think it would be useful to have an AV setup and a time >>>> slot for that. So if I were to propose agenda items, they would be, perhaps: >>>> >>>> >>>> >>>> - Discussion and document editing on TSR >>>> >>>> - Discussion and document editing on SRP Replication >>>> >>>> - Discussion and document editing on Advertising Proxy et al. >>>> >>>> >>>> >>>> It would be good to have this early in the week, and then do further >>>> collaboration later in the week. I say this because I think a lot of people >>>> wind up effectively taking the week off from work to go to IETF or to >>>> participate in IETF, and so this is a really good opportunity for some >>>> heads-down dedicated work. I guess if we get scheduled on Friday, we could >>>> schedule some meetings in non-WG meeting rooms to prepare for the Friday >>>> session, and that could make the session effective as well. >>>> >>>> >>>> >>>> That said, I am open to the chairs telling me I am crazy, and I >>>> certainly don't object to sales pitches and status reports if people have >>>> those as well. >>>> >>>> >>>> >>>> On Wed, Sep 13, 2023 at 7:05 PM David Schinazi < >>>> dschinazi.ietf@gmail.com> wrote: >>>> >>>> Hi DNSSD enthusiasts, >>>> >>>> >>>> >>>> The chairs have until next Friday to put in a request to have DNSSD >>>> meet at IETF 118 in Prague. Do you think we should meet? If yes, please >>>> send us agenda items - either on the list or directly to the chairs. >>>> >>>> >>>> >>>> Thanks, >>>> >>>> David >>>> >>>> _______________________________________________ >>>> dnssd mailing list >>>> dnssd@ietf.org >>>> https://www.ietf.org/mailman/listinfo/dnssd >>>> >>>> _______________________________________________ > dnssd mailing list > dnssd@ietf.org > https://www.ietf.org/mailman/listinfo/dnssd >
- [dnssd] DNSSD at 118? David Schinazi
- Re: [dnssd] DNSSD at 118? Ted Lemon
- Re: [dnssd] DNSSD at 118? Esko Dijk
- Re: [dnssd] DNSSD at 118? David Schinazi
- Re: [dnssd] DNSSD at 118? Tim Wicinski
- Re: [dnssd] DNSSD at 118? Ted Lemon
- Re: [dnssd] DNSSD at 118? David Schinazi
- Re: [dnssd] DNSSD at 118? Ted Lemon
- Re: [dnssd] DNSSD at 118? Chris Box
- Re: [dnssd] DNSSD at 118? Esko Dijk
- [dnssd] DNSSD document editing side meeting Chris Box
- Re: [dnssd] DNSSD document editing side meeting tjw ietf
- Re: [dnssd] DNSSD document editing side meeting Ted Lemon
- Re: [dnssd] DNSSD document editing side meeting Chris Box