Re: [Gendispatch] agenda for gendispatch at ietf116

Jay Daley <exec-director@ietf.org> Sun, 26 March 2023 21:59 UTC

Return-Path: <jay@staff.ietf.org>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5BB7C151536 for <gendispatch@ietfa.amsl.com>; Sun, 26 Mar 2023 14:59:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ietf-org.20210112.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 m0J1vqQf0GEv for <gendispatch@ietfa.amsl.com>; Sun, 26 Mar 2023 14:58:57 -0700 (PDT)
Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) (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 71D5DC14CEFD for <gendispatch@ietf.org>; Sun, 26 Mar 2023 14:58:57 -0700 (PDT)
Received: by mail-pj1-x1032.google.com with SMTP id o6-20020a17090a9f8600b0023f32869993so10020680pjp.1 for <gendispatch@ietf.org>; Sun, 26 Mar 2023 14:58:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf-org.20210112.gappssmtp.com; s=20210112; t=1679867937; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=p/Gs29iDB+ckUXVVDqzNNNNT61Wiyh7XnBwGmcJrIMI=; b=bs7e2u4rPC/epnnR0uXdsknUvAbsW8igMdkNyJUWRGTExznjjUTMku6DPh0PsyA3ik irKXSoIpLrJWq961VNTa8eE371IrRt1NmqavVAmHuYfUibLsIGFttWKWcizY1Wwbw2CL tcS6aIYnZ300fiQRxhpGnCIoMsWtexZCO1Ue6QEP/7ysuu0Dgs7kJ9STJaoxDv+Ho935 tdQBH0S+qbK7NUqcr0h6TbXjsKzlyvttph1tHyRrkuict4d667MvNwHT4PfT3nl3goFl RIoEXdRHKa7TYR02rNTFlZ3bKFuZ8Nsrx6mo3lLOm0+ITixHkm2onMWqEdPZPvORQeJ+ 1Fmg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679867937; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=p/Gs29iDB+ckUXVVDqzNNNNT61Wiyh7XnBwGmcJrIMI=; b=qDKWijnlpVFXX68cjvzEh/kuNNvrYcDeQpfiWzdDGXpwA+Ed96a4Vld8P9H0xvD+nD pytxatpMrlLqeiDSuj312sRl72S+MlcrKHVuA3fUeEKqE+5Q6V1z91HdKxi58hivmoCe /3SwS6qwCIkuirSYKrsJ3QpK2gXpn/YGG3ShBsBt1AVg34lV4edc49qdD6d7+A/GEgTF PFJ/pFOmjGbKT0bxDFE5kKPFAl5MZf+2gCoCN/FfidOYNf/HtCzyJH8fCI+sSxOK+QyV LBprSMAjyKdTOYbGeXDHdojhLlgF7oXcQJn1RTzMbkkxT21iDdyHMWfsPCeBrDePPdJ6 fvEw==
X-Gm-Message-State: AO0yUKXV/DXxK4kK7jPU1g+fvsKmhlZAmILBQ8BPQP7IkJJzNd3Oyhte AsV7PLoWURATPF+7hBT+fR1SM6Fb
X-Google-Smtp-Source: AK7set8bXu04LKcsKdfiLyWbGQAL7vTxenyzMsYagbPsAfGv2KFrOkWKAAcU32+tQ1+x940T4cL5LA==
X-Received: by 2002:a05:6a20:6ca6:b0:db:cfb5:33aa with SMTP id em38-20020a056a206ca600b000dbcfb533aamr8953397pzb.56.1679867936394; Sun, 26 Mar 2023 14:58:56 -0700 (PDT)
Received: from smtpclient.apple (fs85a5b6e1.knge202.ap.nuro.jp. [133.165.182.225]) by smtp.gmail.com with ESMTPSA id d16-20020aa78690000000b005a90f2cce30sm17440182pfo.49.2023.03.26.14.58.54 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 26 Mar 2023 14:58:55 -0700 (PDT)
From: Jay Daley <exec-director@ietf.org>
Message-Id: <C68B9296-F97D-404A-BE81-4DE0FA94EFB5@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_585D7106-9D46-4507-A7C1-0CC016B670D5"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\))
Date: Mon, 27 Mar 2023 06:58:43 +0900
In-Reply-To: <CAChr6SxvrZbcqoEa8AJvrn2BE5-fH=FBvmR67hG63Os7tWiGDw@mail.gmail.com>
Cc: Kirsty Paine <kirsty.ietf@gmail.com>, GENDISPATCH List <gendispatch@ietf.org>, Lars Eggert <lars@eggert.org>, gendispatch-chairs@ietf.org
To: Rob Sayre <sayrer@gmail.com>
References: <CAChr6SzaRiooo+qPxrepsuUKtxHk40Hfu2=4L_57ojkrbcRzpw@mail.gmail.com> <8407FC6E-8A5F-4B03-A83D-2513BFB8698F@eggert.org> <CAChr6Sy8h2q6Nt5859c2RxdZe-wYHW749phePcPHZiJT36WR_A@mail.gmail.com> <CAC9wnY8OS_0HU-J9Yn-gTzEh3C+jZaeyApyZa=2bJS4etn0KcQ@mail.gmail.com> <CAChr6Sw2VVo=yagwLnxdSOXgT0J0K22r9TJgQLLT4iZvafe3Zg@mail.gmail.com> <CAC9wnY_3LL9uzZNGvmZrUA-WJJWNFeGy96cJH2K=MJnDVBno_A@mail.gmail.com> <CAChr6SxvrZbcqoEa8AJvrn2BE5-fH=FBvmR67hG63Os7tWiGDw@mail.gmail.com>
X-Mailer: Apple Mail (2.3731.400.51.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/LFFdlTLdRXY8WKIaCtKSo1sgqC0>
Subject: Re: [Gendispatch] agenda for gendispatch at ietf116
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Mar 2023 21:59:01 -0000

Hi Rob

When I read your messages I was very surprised at the outright rudeness.  It seemed entirely out of context and as if there was some history here that produced your outbursts rather than the discussion in front of us. I fully concur with the chairs' assessment and warning.

Jay

> On 26 Mar 2023, at 15:21, Rob Sayre <sayrer@gmail.com> wrote:
> 
> Hi, ok.
> 
> This seems really escalated.
> 
> I would say I do think the IETF wastes time on procedural issues. Raising that point doesn’t seem remotely rude to me.
> 
> “I don’t care” in this context means “tilting at windmills”, not that I will win a debate or something.
> 
> I think the email client stuff is fair, because I really can’t read it, even when every other line is something I wrote. This is the organization in charge of parsing the stuff.
> 
> Lastly, I only talk about the documents. There’s always a way to make that personal, though.
> 
> In this case, I believe the chairs should let it go. I could forward email, but that’s not cool.
> 
> thanks,
> Rob
> 
> 
> On Sat, Mar 25, 2023 at 22:55 Kirsty Paine <kirsty.ietf@gmail.com <mailto:kirsty.ietf@gmail.com>> wrote:
>> Hi Rob,
>> 
>> It is absolutely fine to think the work should be not be dispatched. However, there are many ways to put that view forward that aren't perceived as disruptive or rude.
>> 
>> The following is not an exhaustive list, but in the interests of us all learning and moving forward, here are some of the things that are not in the spirit of, or appropriate for, gendispatch's discussions:
>> - To say that the idea is "wasting IETF time" or "not worth addressing", when the chairs have given it agenda time. The result of that discussion might be "do not dispatch", but it's not helpful to reach a dispatch outcome, or to the WG, to say the discussion shouldn't happen at all.
>> - To say things like "I don't care", which comes off as dismissive, and doesn't tell us anything about your view on the dispatch question (e.g. plenty of work I don't care about should still be dispatched).
>> - To go in on someone's email client and how it treats URLs; this is very off-topic, and comes off as aggressive (compared to merely asking for the correct URL, which would be appropriate)
>> - To say that someone's way of communicating is "completely incomprehensible" comes off as insulting to that person, and doesn't advance the dispatch discussion - whereas asking for more clarification would advance the discussion, without being rude.
>> 
>> This is not an exhaustive list, but I hope provides some understanding to you and for the benefit of the group. I'm happy to discuss further F2F or over video, where I think it can be easier to understand.
>> 
>> Kirsty
>> 
>> 
>> On Sun, Mar 26, 2023 at 2:38 PM Rob Sayre <sayrer@gmail.com <mailto:sayrer@gmail.com>> wrote:
>>> Hi, noted.
>>> 
>>> No one said anything to me off-list.
>>> 
>>> It should be fine to hold the opinion that the idea proposed here should go nowhere, though.
>>> 
>>> So, yes, could you explain it? What’s wrong here? I just said this topic is not worth spending time on, and kind of a rathole. What’s the problem?
>>> 
>>> sorry for the trouble,
>>> Rob
>>> 
>>> On Sat, Mar 25, 2023 at 22:18 Kirsty Paine <kirsty.ietf@gmail.com <mailto:kirsty.ietf@gmail.com>> wrote:
>>>> Hi Rob,
>>>> 
>>>> The messages you have sent to the gendispatch list this morning are insulting, dismissive, and disruptive to the WG process as per RFC3934. I'll happily explain exactly which parts are not conducive to gendispatching Rich's work with you directly, if that's needed. But as others have indicated, to you on list and then privately to the chairs, this disruption needs to stop; so, per RFC3934, please consider this a public warning.
>>>> 
>>>> To the WG, please excuse the delay in communicating this; I was on a flight, asleep. What a delightful thing to land to...
>>>> 
>>>> Kirsty
>>>> 
>>>> On Sun, Mar 26, 2023 at 12:29 PM Rob Sayre <sayrer@gmail.com <mailto:sayrer@gmail.com>> wrote:
>>>> 
>>>>> Hi Lars,
>>>>> 
>>>>> You are a reasonable person and I have read your code.
>>>>> 
>>>>> I think the IETF would do well to respect running code a bit more. URLs work, don’t break them. The IESG/IAB thing isn’t all roses, but I am not sure what would be better.
>>>>> 
>>>>> Sincerely: “please stop it”,
>>>>> Rob
>>>>> 
>>>>> On Sat, Mar 25, 2023 at 20:17 Lars Eggert <lars@eggert.org <mailto:lars@eggert.org>> wrote:
>>>>>> On 26. Mar 2023, at 11:45, Rob Sayre <sayrer@gmail.com <mailto:sayrer@gmail.com>> wrote:
>>>>>> > I am all for procedural backflips and tolerance, but this one has already been declined, right?
>>>>>> 
>>>>>> I declined the BOF request only because it came in much too late, and not for any other reason. I suggested to the proponents to consider taking the discussion to GENDISPATCH if they wanted a slot at 116.
>>>>>> 
>>>>>> Lars
>>>> 
>>>>> -- 
>>>> 
>>>>> Gendispatch mailing list
>>>>> Gendispatch@ietf.org <mailto:Gendispatch@ietf.org>
>>>>> https://www.ietf.org/mailman/listinfo/gendispatch
> -- 
> Gendispatch mailing list
> Gendispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/gendispatch

-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org