Re: Result of Consultation on ART/TSV Area Reorganization

S Moonesamy <sm+ietf@elandsys.com> Sat, 30 September 2023 13:21 UTC

Return-Path: <sm@elandsys.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 93EA3C15107C for <ietf@ietfa.amsl.com>; Sat, 30 Sep 2023 06:21:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.704
X-Spam-Level:
X-Spam-Status: No, score=-1.704 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 MzMP1AHAD3lZ for <ietf@ietfa.amsl.com>; Sat, 30 Sep 2023 06:21:19 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AB87C15106C for <ietf@ietf.org>; Sat, 30 Sep 2023 06:21:19 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.176.27]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id 38UDKf4b019533 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 30 Sep 2023 06:21:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1696080076; x=1696166476; i=@elandsys.com; bh=my6qcI000YoqWhuAcKg7GwQHQV3CJmOrO0Hw4B1bErc=; h=Date:To:From:Subject:In-Reply-To:References; b=33GBjUiRPy+iVSIuwxdUQp4s2lM7YQGkkPY90J2TnT84RgIzCt37KC6edLu3M3gRf 51hLAOisNFsm1kDM+Q4eYi3u3flyi9v3blyN58q/ObzkBjSwaf6uOAT/2r/M2Tdg6T QfodJSw2BJXRGvgNBmL8EXMiCSLgzrurEVzsAxCM=
Message-Id: <6.2.5.6.2.20230930044443.0acddad0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 30 Sep 2023 06:20:12 -0700
To: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Result of Consultation on ART/TSV Area Reorganization
In-Reply-To: <7465a7af-cdc4-e9aa-3101-78f53852dcea@network-heretics.com>
References: <CAM4esxQ4uFCA4+jcMAS1NptfM7hYYWBTGedTF1EyGrr+UkCdVg@mail.gmail.com> <A1E3C0AC-B21F-4C54-81C4-0B7F4D7CF6D1@mnot.net> <CAM4esxTd6yN9UP5jci_7gJiEpypjNfz1UA6BfjBHOKnw+_t5hw@mail.gmail.com> <A5EF9F317F813FE4D9888C20@PSB> <eabfd649-af9e-b5e4-5ee5-c700ffe1f2f4@cs.tcd.ie> <7DF7DAC5B9B1B85790E1D263@PSB> <CAGL5yWakh2SseZUUrkj8=4YNwRW+gthfvN0FfV9+W=UD1HB-wA@mail.gmail.com> <7465a7af-cdc4-e9aa-3101-78f53852dcea@network-heretics.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bW2mW85F5d3uZeh2mhQEKvbTU9o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <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: Sat, 30 Sep 2023 13:21:23 -0000

Hi Keith,
At 09:28 AM 29-09-2023, Keith Moore wrote:
>On 9/29/23 12:07, Paul Wouters wrote:
>
>>The question is "will this end up with a more balanced AD
>>workload that reduces publication time of documents".
>
>I don't think that should be anywhere nearly the only question. For 
>example, the quality and relevance of the documents that IETF 
>produces should be at least as much of a concern.    As should the 
>state of the Internet.

There is an expired draft from 2013 {1] about the potential issues 
facing the IETF.  It takes some work to attempt to solve those 
potential issues.  In my short experience, such work cannot be done 
without people.  In my opinion, telling those people that their 
workload is not a problem is far from persuasive.

There is a message which an AD which was posted in 2022. [2]  It's 
not the first time that there is a succession issue in the Transport Area.

Regards,
S. Moonesamy

1. draft-arkko-iesg-crossarea-03
2. https://mailarchive.ietf.org/arch/msg/tsv-area/ZnmpPnahMopFRpJ_vsGjo8yBggA/