Re: [admin-discuss] Next steps towards a net zero IETF

Mezgani Ali <ali.mezgani@gmail.com> Tue, 04 April 2023 23:40 UTC

Return-Path: <ali.mezgani@gmail.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 5E7D3C15256B; Tue, 4 Apr 2023 16:40:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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_NONE=-0.0001, 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=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 ji-D7uRKJPOs; Tue, 4 Apr 2023 16:40:30 -0700 (PDT)
Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (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 793D6C151522; Tue, 4 Apr 2023 16:40:30 -0700 (PDT)
Received: by mail-ed1-x533.google.com with SMTP id b20so136831423edd.1; Tue, 04 Apr 2023 16:40:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680651628; x=1683243628; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=DYADwfMf+D9ggSNFkrGRmKfnpcxldcLgPI4ONThQZO0=; b=A/KRVTatr310Innv4cnXG84FSISm2NGVDHJ+FFjYigEmI2HJSw29ZgoHVe5gTaoUnI h2Hwa+Q/obwcVuMf5uA08Tq4rw3UTwqDnbMcn/Tir95AKg1gwbF6erERgGWUj0udKByr bUfHqwwvNzYI+BNDOE8Ew3n0zUdMQXcidJOEiNGfs6B8L2ECMNTfi5S8PmbXBHU31sqW 3T6v5l5c6F4SDgLeyGZADiJU2ftQUzKQwOrfSDe8mtZ3B3gNDNCJMxq+h03cwNFKuYno 7AxeDguxQ229Dk4zfwrqMy2m1NUFEIDnsVngz4zxpDYvM95mbokfVDRSk5nMM/+I8z7C 16vQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680651628; x=1683243628; 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=DYADwfMf+D9ggSNFkrGRmKfnpcxldcLgPI4ONThQZO0=; b=UdfE2p3YReEh6gVGGKmiltsiBtXbSbxtlUHtMu5VVQn+ZArwyawAE1142lm517BBBY C8DpaJNjAt5TqsYP9AeSQvkr1CnBT2wkDzRq4brwVGKrKf+vt79KvGXw3Bp+SHn+JNf9 lY3chpq0ifuw7m61sy0NPhRbWRakaEpFLQbXXaafSQw7W4yO+TkvsNEYOEOlEnV9FHmM 2nu8R4thFxUo4s2QVBazdpdVxHKin5BLz6R0TnzjlwWZcEiD2BnMYdXxlQ8YwBOSc6FP 9UsWI7iOxEbLxbapMqkMu2NXcmfviMGAt5g95LcEpKU/hZd3EEm+q3fecJHy+tSljMdA axLQ==
X-Gm-Message-State: AAQBX9c70CTijwVhI9CBfvpUxJUSBcQfZm27J7U3U7BnW8rGc9sCx95K m0YJe+eJd/MMb9MyNEhur27FjKEQh9Yl9MnguWc=
X-Google-Smtp-Source: AKy350ahtLkEwejk7z8BuMgYJchjFD++j/4S2g9M75d7DyGHMOrUfie0Mn403YnZ/eN3kGZZdDmgN5D4K79ZSmDqTzI=
X-Received: by 2002:a17:907:2446:b0:928:6456:729c with SMTP id yw6-20020a170907244600b009286456729cmr576854ejb.10.1680651627864; Tue, 04 Apr 2023 16:40:27 -0700 (PDT)
MIME-Version: 1.0
References: <13153.1680560012@localhost> <2658CD52-2D36-43E5-973B-39EB713E6A27@eggert.org> <CADnDZ8-666_JE1GHBNKkGw7igozdh4zZdpCJwVyy8cPCoYBqxw@mail.gmail.com>
In-Reply-To: <CADnDZ8-666_JE1GHBNKkGw7igozdh4zZdpCJwVyy8cPCoYBqxw@mail.gmail.com>
From: Mezgani Ali <ali.mezgani@gmail.com>
Date: Tue, 04 Apr 2023 23:40:17 +0000
Message-ID: <CABN_Fg_bED--a=JxYHKXq47QE6od_02w+XoCUTK4xz6HwnyYog@mail.gmail.com>
Subject: Re: [admin-discuss] Next steps towards a net zero IETF
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Cc: Lars Eggert <lars@eggert.org>, Michael Richardson <mcr+ietf@sandelman.ca>, admin-discuss@ietf.org, IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004527f405f88b3324"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YN7ydOdt7hZVsBe5ZHVf_J9bHos>
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: Tue, 04 Apr 2023 23:40:34 -0000

Listen,

Let IETF as is it and go far.

As I saw the IETF got an aspect of IEEE whish are not in favour of Internet
engineers.

Here Am I as IAB reviewer I ask IETF director yo be selective and very
strict on whom must publish and not in this kind named files.

Again, please go away, please go away you migrate the hole IETF into na
existing structure.

Kind regards,

Mezgani Ali
VP of Engineering
https://www.nativelabs.ma/
+212 644 179 451

On Tue, 4 Apr 2023, 23:21 Abdussalam Baryun, <abdussalambaryun@gmail.com>
wrote:

>
>
> On Tue, Apr 4, 2023 at 8:21 AM Lars Eggert <lars@eggert.org> wrote:
>
>> Hi,
>>
>> On 4. Apr 2023, at 01:14, Michael Richardson <mcr+ietf@sandelman.ca>
>> wrote:
>> > Or we could just start with having three f2f meetings per year, with
>> more
>> > slots for informal meetings...
>>
>
> IETF may will need to have a formula as when do we do three f2f or four
> f2f per year, IMHO it depends on the technology/RFCs demands and the number
> of f2f attendance and the accumulated travel distances, and on ietf_data
> analysis per WG and per Area. Furthermore, we need to know if the WG became
> a remote WG_meeting or WG_in_person per IETF meeting (i.e. if more than 10
> persons are attended then it is not remote_WG_meeting).
>
>
>> I just wanted to point out that we're seeing a different push in the IESG
>> from WG chairs, many of which want more WG session time during IETF
>> meetings. That isn't to say that they wouldn't also want more informal
>> time, but there is a tussle here.
>
>
> There are a lot of wasted time because it does not depend on WG
> priorities/activities, the Chair or AD need to discuss priorities of time
> with All participants per WG. In meetings we may see presentations with no
> discussions per f2f meeting, so I think it is a wasted f2f time, also there
> are times in plenary meeting with no discussions per long_presentation. So
> we need shorter presentations for less priority/activities and
> longer_enough presentation for more high priority/productive_discussions.
> Furthermore, our f2f meetings help us (remote and person_attended) make
> better wg_decisions.
>
>
>>
>> Additional tracks and/or longer days and/or full-length Fridays will
>> likely be needed and the community should weigh those against their
>> downsides for in-person and remote attendees.
>>
>
> yes agree, and that needs to be discussed on the list per WG and per Area,
> IMHO, the ietf_Area discussion on that issue is not active per future f2f
> meeting.
>
> Best Wishes,
> AB
>