Re: Old directions in social media.

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 07 January 2021 15:47 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C51903A0EF2 for <ietf@ietfa.amsl.com>; Thu, 7 Jan 2021 07:47:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.362
X-Spam-Level:
X-Spam-Status: No, score=-2.362 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, NICE_REPLY_A=-0.262, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 8QJBDw4TnoI3 for <ietf@ietfa.amsl.com>; Thu, 7 Jan 2021 07:47:25 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 351723A0EAD for <ietf@ietf.org>; Thu, 7 Jan 2021 07:47:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4DBVws0CSLz6GVsj; Thu, 7 Jan 2021 07:47:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1610034445; bh=haYMwjlxGf6fWs0Bn67LAuYbf3nfdxZgCpYOCRkyh7E=; h=Subject:To:References:From:Date:In-Reply-To:From; b=l2ulFeGzw3t2grL93rSbLXHkztPtOWS7jRswFnerdAQKRi+daQyoHgklQqHbWLlrY t/DYkuRaijO2X9tbzZqGlL9Q/JiLLFzCHmCO7QE1r5W7X5zMXubKjFXNKB85T7SZwE FmcG0AdWmlpT9lTkRiIzZx0Jq7I6oy4Adef+KJkg=
X-Quarantine-ID: <FyxSeHuNin4S>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (unknown [50.225.209.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4DBVwr008Nz6GVsZ; Thu, 7 Jan 2021 07:47:23 -0800 (PST)
Subject: Re: Old directions in social media.
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <CAMm+Lwg1-pxKU8vMinFDUbVca52VgFzTOOSJMnJjaUJvF6PLew@mail.gmail.com> <519a0e4d-7102-fac8-1517-04c590a80080@network-heretics.com> <CAJU8_nUU0Km_YtgpWbLF-JVQVUXFYvxBNBYbzaLOXBqQyvvUaA@mail.gmail.com> <062d01d6e387$39c46270$ad4d2750$@acm.org> <CAJU8_nWD3MwLs5aVNMi_3LqZysrfjv0N7N3ujV-zhqxiFh3tsA@mail.gmail.com> <788651ca-0c84-7a54-9c48-b962faed635f@network-heretics.com> <CAJU8_nXSE-E2AVrJnqe5ZifR+qGhXscNCFXQRDj_GU1r=hNOyw@mail.gmail.com> <70416f47-7c31-8571-02ce-f95ff386d54f@network-heretics.com> <X/TtgTtl02AMyns8@mit.edu> <AM0PR08MB371623409DE8AB03CC667234FAD00@AM0PR08MB3716.eurprd08.prod.outlook.com> <866b1357-ec50-7765-4277-fd4fba8d793e@network-heretics.com> <AM0PR08MB37166B8E57C293917737D9D6FAD00@AM0PR08MB3716.eurprd08.prod.outlook.com> <d8454121-f6fb-3cbb-3149-656e20efce96@joelhalpern.com> <AM0PR08MB3716C960817BCCFEE4F9F911FAAF0@AM0PR08MB3716.eurprd08.prod.outlook.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <edf8225b-d005-4f99-b96f-41bc49633da3@joelhalpern.com>
Date: Thu, 07 Jan 2021 10:47:22 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <AM0PR08MB3716C960817BCCFEE4F9F911FAAF0@AM0PR08MB3716.eurprd08.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LPHAblvgzyp3NGZAIjo0b-Pjr4k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2021 15:47:27 -0000

I do not see how your reply addressess the question of participating in 
effective cross-area review.

Separatately, the question of "those who actually do the bulk of the 
work" seems misleading.

I at least, I I think all the participants, understand that author teams 
or design teams will usee whatever tools they want.  The issue is what 
is used for WG discussion and resolution of issues.  All WG discussion 
of issues.

Yours,
Joel

On 1/7/2021 5:17 AM, Hannes Tschofenig wrote:
> Hi Joel,
> 
> I fully understand that it is more convenient for you to have everything available in your favorite tool (in this case email).
> But consider also what is easier and more efficient for those who actually do the bulk of the work.
> 
> Ciao
> Hannes
> 
> -----Original Message-----
> From: Joel M. Halpern <jmh@joelhalpern.com>
> Sent: Wednesday, January 6, 2021 10:31 PM
> To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>; ietf@ietf.org
> Subject: Re: Old directions in social media.
> 
> Hannes, I have to disagree about what it takes to participate in cross-area discussions.
> 
> As an example, I have problems with something currently being discussed in the DMM group (whether I am in the rough or the predominating side remains to be seen.  That is not the point of this comment.
> 
> If I had to go through the discussion on the git issues tracker to figure out what was being said and why, it would be MUCH harder to appropriately participate in the discussions.
> 
> Yours,
> Joel
> 
> PS: While I do not typically participate in dmm, I do follow it, and am at least somewhat knowledgeable about the space.  The ability to follow it on the emial list is important to me.
> 
> On 1/6/2021 10:56 AM, Hannes Tschofenig wrote:
>> Keith,
>>
>> for cross area reviews all you need are IETF drafts. I doubt that reviewers are interested in digging through the Github issues, PRs, and mailing list discussions.
>>
>> Regarding "resolving tussles we encourage them, and we produce more
>> and more standards that lack coherence with one another." Note my mail
>> on that topic, see
>> https://mailarchive.ietf.org/arch/msg/ietf/YWTxZEik6gqGod9d5KbAdqNbh3g
>> / Moving all discussions from Github to the mailing list will have no
>> impact on this issue.
>>
>> Ciao
>> Hannes
>>
>> -----Original Message-----
>> From: ietf <ietf-bounces@ietf.org> On Behalf Of Keith Moore
>> Sent: Wednesday, January 6, 2021 1:58 PM
>> To: ietf@ietf.org
>> Subject: Re: Old directions in social media.
>>
>> On 1/6/21 2:56 AM, Hannes Tschofenig wrote:
>>
>>> The good thing is that there is no real problem here. In most working groups a limited number of people actively participate. Those people know how to contribute. For those who just browse through groups from time to time it got more difficult to see where the center of attention currently is.
>>
>> I would claim that what you describe *is* a real problem.   IETF works best when it benefits from a wide range of input, including "cross-area"
>> input and input from generalists.   When working groups consist of a small number of people who do whatever they want in their narrow areas of concern, groups have a greater tendency to work at cross-purposes with one another.
>>
>> And I would claim that we've been seeing the unfortunate results of that for many years now, so that instead of resolving tussles we encourage them, and we produce more and more standards that lack coherence with one another.
>>
>> Keith
>>
>>
>> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
>>
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
>