Re: [dnssd] DNSSD at 118?
Tim Wicinski <tjw.ietf@gmail.com> Thu, 14 September 2023 17:48 UTC
Return-Path: <tjw.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 3C485C14F726 for <dnssd@ietfa.amsl.com>; Thu, 14 Sep 2023 10:48:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=gmail.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 gKuoWvqc87bO for <dnssd@ietfa.amsl.com>; Thu, 14 Sep 2023 10:48:35 -0700 (PDT)
Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 4AB38C14F721 for <dnssd@ietf.org>; Thu, 14 Sep 2023 10:48:35 -0700 (PDT)
Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-986d8332f50so177253966b.0 for <dnssd@ietf.org>; Thu, 14 Sep 2023 10:48:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1694713713; x=1695318513; 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=BKPVU/rGlBhVqqsx82ONJxlBU2IRu3HqzM3SiyWjI1w=; b=HzONB96RyTAxg2cuTYVlmE+0wWtuC7/XeuH8XXP+HHUWFsJ/TBOneTNmgdHauvjvYJ pdnIzxCYT8uFr5cLSq5ZUodMIXdBY1bP4LwUeKDfkrXoCDQ+EowJi0VJ/JkB2cThS2PE 3t9FND91tUDevcEZd9ZHtZXmllkl+uS7FXUTktbAf8dlno0fqGQFVvmlXztXOcz++lHX rnv3bWm+IKKOpsBaQ42dgvJmGJkm853tpCBhXybPOZm432/FMm/rvhCmTsaV20n8csye dT+26c+AaK2R8xLzUk+n/EKv+o13bmq9OmL/wlyI0r8etndxuHc5eZwQxR2TFlM/lHm1 ZHvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694713713; x=1695318513; 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=BKPVU/rGlBhVqqsx82ONJxlBU2IRu3HqzM3SiyWjI1w=; b=XwFWBWton2bnefx5xYxG+mNkVtxwpNWYcRvsGFn84iVFwiYyQ6NdcK5JUR3O+W4JE0 D8hwvNTDN5mYV3Oq/tC7mD5+lNEySSnbYBN4h6KACgSHK59drRYnMqZ6RmFk5uIzfAIf S4CxsTwI/GMe0aMd2UUPdIzFtAIxBStpD7I0YaIeHTKYFDzv8h+A5icSnmQ3p+eyOqNO oH9pzN8okkUbmp/t/Y8j3xDbtFh6bYIqhAbuhepUfWoz59LI9549NmNnXIKInQimp5Qw Wb9IvLMAalhpLONUkXkogOI9Svjla2fvry82LM/U1Tjrbz9byhJIFOmqQD49ri1fTZbF j3tg==
X-Gm-Message-State: AOJu0Yy39I3nPYsait2S4XjMwKjOgoO4DYOSBL18eLwUKB2XAvRYU0Ja q6DEyu4PwZ+XhNdraABh1kyPzr+YiNzyIeGF9gRl8fld
X-Google-Smtp-Source: AGHT+IH+zSQVfPtc7iFFDdY7ejFHRU7QhlIGmIaEZ9Z77PmE8lWkwQz8Uh41FiWfXUGDTN184vENLGsasf7a750MHEs=
X-Received: by 2002:a17:906:10dc:b0:9a2:28dc:4168 with SMTP id v28-20020a17090610dc00b009a228dc4168mr5691336ejv.61.1694713713302; Thu, 14 Sep 2023 10:48:33 -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>
In-Reply-To: <CAPDSy+4Hf5543Yej06uuxo_4JCv8sJ0VMFvBCd+m943a+MSPrA@mail.gmail.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Thu, 14 Sep 2023 13:48:21 -0400
Message-ID: <CADyWQ+HBaC0K+ku=wcVhuFJUFhHs-quLmcw3K591ZKs5r_UcTw@mail.gmail.com>
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: Esko Dijk <esko.dijk@iotconsultancy.nl>, Ted Lemon <mellon@fugue.com>, DNSSD <dnssd@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e0a0b906055548da"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/ykzuPxttwTSuay7C-qyXa3YDfEI>
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: Thu, 14 Sep 2023 17:48:36 -0000
I won't be in Prague but I am Ok with a side meeting if 1) there is audio for listening and 2) a chat channel. I don't need to hear myself speak (and y'all don't need to hear me speak), but composing comments in a chat channel is very useful. In exchange, I will agree to do some work tim 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