Re: [Rats] Meeting culture ... Re: CoTS and CoRIM

Hannes Tschofenig <hannes.tschofenig@gmx.net> Thu, 04 January 2024 12:12 UTC

Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: rats@ietfa.amsl.com
Delivered-To: rats@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A685C14F5FF for <rats@ietfa.amsl.com>; Thu, 4 Jan 2024 04:12:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.104 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=gmx.net
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 vq2pxnEf3ZZI for <rats@ietfa.amsl.com>; Thu, 4 Jan 2024 04:12:19 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED458C14F619 for <rats@ietf.org>; Thu, 4 Jan 2024 04:12:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=s31663417; t=1704370326; x=1704975126; i=hannes.tschofenig@gmx.net; bh=gG3oaMV97z7FxzC2X/RktKgGFJFjqF2NhDW8LpzN5KA=; h=X-UI-Sender-Class:Date:Subject:To:References:From:In-Reply-To; b=nt7l2NhTOf+7zaO7LPEHjEibjlH6/lHbCNARcCwIrsoVlTIf+0CDVrQ7eyFM1r9i GKy4JT6nYXVFaftpobCYui9dEXZ4QT40jT7ZTLbqIYnsfJ/O5oNL2ue2OT/F8NYeP buIfTR5eeRoidyFyVQF98mVtPJp+VRbPajyOey33TbBHPFcZ7tVPzhDPES/kM3jHE /P0q5+jXmJqqvRywJG5DWT7Bhu5VH8M9cOE1CcpbzPGJjGc3LRAE4cHGPPonvCEEV deY1fJLaifx5ZO+I8xdmMNQ5tZfxD1G3oiiKh2a4Tj2iNHlRsmOx45NqO3E9PFCEa E3aRZgqLfqmhXFaU9g==
X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a
Received: from [172.16.254.186] ([185.176.157.173]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MWASY-1rj4fc28MM-00Xd5B; Thu, 04 Jan 2024 13:12:06 +0100
Message-ID: <f19e57ee-a936-43ed-b19f-ba32c24cc40a@gmx.net>
Date: Thu, 04 Jan 2024 13:12:05 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, Michael Richardson <mcr+ietf@sandelman.ca>, 'Yogesh Deshpande' <Yogesh.Deshpande@arm.com>, rats@ietf.org
References: <005701da2e02$6acec900$406c5b00$@gmx.net> <84e6047b-b87b-4053-8e5a-fb2c8347defc@tu-dresden.de> <AM6PR08MB43257B9CB8ECD1BF6768D2138E8CA@AM6PR08MB4325.eurprd08.prod.outlook.com> <013001da2e8d$bf3c08a0$3db419e0$@gmx.net> <AM6PR08MB43255B8E2ECC1FE657AF325E8E8CA@AM6PR08MB4325.eurprd08.prod.outlook.com> <01c601da2e9f$0f402230$2dc06690$@gmx.net> <091b0c2f-2d12-0391-c060-8dc870d41706@sit.fraunhofer.de> <11606.1702576249@localhost> <25e47b4a-200b-4050-bd90-9303bac2da8e@gmx.net> <a9f17401-620c-c5d4-9923-5e98d191b1a4@sit.fraunhofer.de> <c4791ff0-1685-4108-801a-6beca3e90a76@gmx.net> <e6f6c5a8-6489-78f9-c170-acee447c48e5@sit.fraunhofer.de>
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <e6f6c5a8-6489-78f9-c170-acee447c48e5@sit.fraunhofer.de>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:neqxz2jEYxzPrDN42+7pVT3h2jSFF4MnyH3humcz/K2pp2LDwS+ +59SGJ1YhVI8DcFb5H4uWonlghhS815ghb5ulYqhJqDqRnt1bQ/8t6VbcHkXg45oHcPKg+1 1yLao1hxO2OpVaNZqYbcD19qU3uzmB8sc8dSVVtKMMhLN1H2JxgD6GEYlffse3rt2dBBpyr kyVJ5Y8UonIexq/rtesxA==
UI-OutboundReport: notjunk:1;M01:P0:j0Xbww4GBhU=;5UQHPxgz0jzTrbJAyZF+Wh8Mx97 12Y7HZ9R4VAI0PnTR9XndQO7PujbFE7SoGrsiTTkOrhfwjNuQ7H8H1X+f98Zll8ni4Mvws3uo cD3hvPemooy5NoqwWIyDTlgCukqeS3zPVaSta745mNXP/HmVvzFVHRBmscdCp3bAX4CtSos+S P6ArRXcG6Jza5pyugkc04BmV65Kay90NiTD2UvymPaPM5iqNTCqlTkVjZDK7RHe6RqFVAeF5k 3HPLQzvR/l25grmT3NJPTeUWEgs75NR8nsBZa3xQvhA8VkzT1H+U0iZwHqCHwSI9Ub+kvNQz7 xQhWGypYD9IFnUybdVk3AwjlHZGY+KYO4xNnI6Is+FlhNNhcC0tzABYZUgL4GANgB2bxnnEg2 9PIYEXtq7/a4LBXb2SaMTkFbYKk5aZ7i3Z84teedwmjUaZ+4RVyYd0XRYBn4kIAFn6MXBLRet lQuB8Wr1Zg9qDmhKjw+ZqYv82Pz/FxY9C7NDNrepc34VimAMsk/i+6AVKQDy54CVSawyNu+5Z qnIuRwVv/yIgmtguVqbxOdFv8gYi2j2qxng0PKeqEjCTJpgdqD+f8yyyxftGdLkqSSJ79h/yf vWELZuBwi5Qfs58nEw4Y5G0LZwMdoQ0fnUJVU9A4XwhOPyvzA1qBfPEsosAzTAx0mrX8BO9Rp qlnEkgBSjd0eKJm2KHSvv0VJSPSclrI2vi7EhSbAZjpAdpwomsAQO4goRqpBm7JCvkCiBo/bQ Aq9zs+Kul7sHWd+7NvwJdJkS2vptyfH8h48bFMC9TK9zYC6JTX1ItIxvtg3eQxKF+xIZODV5Y kALR2+pOLSrd0cavo/JXu6jwI8xMEbJt9UkHPDPcW88D58adedliTunkBLBvKePi25pPC8Ftv TB3u2KEEA5YHBGnX6P8LjW8RB2PXnymu5w7WJHeZdwpyA8uTOBK+2D8PUwM94Mgt0NUFpsYr4 9pldvF0WPNYNBSjtTJs9WVQjEjQ=
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/W15YLsv98Ylx7-Zv6Wm9SS2WeMU>
Subject: Re: [Rats] Meeting culture ... Re: CoTS and CoRIM
X-BeenThere: rats@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Remote ATtestation procedureS <rats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rats>, <mailto:rats-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rats/>
List-Post: <mailto:rats@ietf.org>
List-Help: <mailto:rats-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rats>, <mailto:rats-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jan 2024 12:12:20 -0000

Hi Henk,


we seem to have different views about how work in the IETF should be done.


That's not a problem since there is most likely no right or wrong answer
here.


Let me share my view nevertheless: when an individual draft becomes a
working group item discussions have to be made in public giving as many
participants as possible a chance to provide input.


To have useful meetings, you need to

  - find a date that maximizes participation,

  - announce the meeting well in advance,

  - post an agenda,

  - produce meeting minutes (which capture, at a minimum, the action
items), and

  - give participants time to resolve their action items


As we know, it is almost impossible to fulfill this list with weekly
meetings since the participants are super busy and do not manage to work
on their action items in such a short period of time (sometimes not even
within a several month timeframe for trivial tasks).

I do, however, understand the challenge to regularly sync up with
co-authors and other interested parties and at the same time to meet the
requirements outlined by the IESG for holding official meetings.

I don't have a good suggestion either and this topic should probably be
brought up with the IESG (or at least with the chairs).


Ciao
Hannes


Am 03.01.2024 um 17:11 schrieb Henk Birkholz:
> On 03.01.24 17:02, Hannes Tschofenig wrote:
>> Hi Henk,
>>
>>
>> the discussion started when Yogesh suggested I bring my comments up in
>> one of those meetings.
>>
>>
>> I am suggesting instead to schedule official virtual interim meetings to
>> discuss the many topics the group has to deal with. During the IETF f2f
>> meetings there is just not enough time to go into any level of detail.
>> Since I am not one of the RATS chairs I can only propose it.
>
> Decisions in virtual interim meetings require WG consensus. The CoRIM
> dezign meetings are targeting the steps before that, I think: to
> create contributions and proposals that than can be discussed in WG
> virtual interim meetings.
>
> I am not saying that WG virtual interim meetings are not useful! But
> agendas will most likely not be exclusive to CoRIM, as any WG work
> item can be part of an WG virtual interim meetings. The weekly CoRIM
> meetings that Yogesh announced are just a place for contributors to
> align contributions and proposals in order to expedite document
> progress. In other words, they are content-focus work meetings and and
> not about updates and reports to the WG.
>
>>
>>
>> Ciao
>>
>> Hannes
>>
>>
>> Am 03.01.2024 um 14:46 schrieb Henk Birkholz:
>>> TL;DR
>>> A few individuals meet on Wednesdays to work on TCG Dice Endorsement
>>> documents & IETF CoRIM documents (primarily IETF, atm) to work on
>>> contributions collaboratively.
>>>
>>>
>>> Hi Hannes,
>>>
>>> yes, you are correct. That is why MCR accidentally send a typo. We are
>>> actually calling them dezign meetings, due to that reason.
>>>
>>> Sorry - over the change of years I also kinda lost track about what
>>> problem we are trying to solve here in this thread.
>>>
>>> These meetings are orchestrated by individuals and have no official
>>> IETF or TCG flavor to it (although, if non-TCG members are present we
>>> cannot work on TCG projects due to by-laws), but nevertheless we
>>> thought it would be nice to announce those meetings and render them
>>> open to any interested party in support of transparent goal-driven
>>> collaboration.
>>>
>>> Hannes, if that was a mistake, we apologize! Alas, I am uncertain what
>>> to derive from your comments. Could you please clarify?
>>>
>>>
>>> Viele Grüße,
>>>
>>> Henk
>>>
>>> On 03.01.24 14:33, Hannes Tschofenig wrote:
>>>> Hi Michael,
>>>>
>>>>
>>>> Am 14.12.2023 um 18:50 schrieb Michael Richardson:
>>>>> Henk Birkholz <henk.birkholz@sit.fraunhofer.de> wrote:
>>>>>      > And these types of meetings are quite usual
>>>>> editors/contributors
>>>>>      > meetings - as we had, for example, with the RATS architecture
>>>>> starting
>>>>>      > with the formation of the RATS WG. I am pretty sure that is
>>>>> a-okay as
>>>>>
>>>>> Agreed: these are design team meetings, and the results are subject
>>>>> to WG consensus.
>>>>
>>>> Unfortunately, those are not design team meetings either. There is
>>>> guidance also on design team meetings and none of that guidance is
>>>> followed by these meetings.
>>>>
>>>> Here is the IESG DT statement:
>>>> https://www.ietf.org/about/groups/iesg/statements/design-teams/
>>>>
>>>>
>>>> The working group chairs could create design teams, schedule interim
>>>> meetings, and do all sorts of other things. Unfortunately, they didn't
>>>> do so.
>>>>
>>>>
>>>>>
>>>>> That ideally happens because new I-Ds are posted, and the diffs
>>>>> include
>>>>> high-level review of changes, and introduction to controversial
>>>>> issues onto
>>>>> the ML.
>>>>>
>>>>> I think that what annoyed Hannes was the way that his suggestions
>>>>> seemed to
>>>>> be subject to design team veto (and dismissal), rather than
>>>>> consideration.
>>>>
>>>> In OAuth and SCITT the IESG noted that we have to be more inclusive
>>>> when
>>>> it comes to our meeting culture. They were correct in their criticism.
>>>> Everyone should, on a regular basis, think about how we could involve
>>>> more people in our discussions.
>>>>
>>>> The work in IETF groups benefits from broader involvement and you only
>>>> get those if you keep the entire group informed about the work.
>>>>
>>>>
>>>> Ciao
>>>> Hannes
>>>>
>>>>>
>>>>> --
>>>>> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT
>>>>> consulting )
>>>>>             Sandelman Software Works Inc, Ottawa and Worldwide
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> RATS mailing list
>>>>> RATS@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/rats
>>>
>>> _______________________________________________
>>> RATS mailing list
>>> RATS@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rats
>
> _______________________________________________
> RATS mailing list
> RATS@ietf.org
> https://www.ietf.org/mailman/listinfo/rats