Re: [arch-d] draft-iab-m-ten-workshop
Wes Hardaker <wjhns1@hardakers.net> Mon, 14 August 2023 20:32 UTC
Return-Path: <wjhns1@hardakers.net>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B945C15DD44 for <architecture-discuss@ietfa.amsl.com>; Mon, 14 Aug 2023 13:32:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 (1024-bit key) header.d=hardakers.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 bUBOa3NSzmdU for <architecture-discuss@ietfa.amsl.com>; Mon, 14 Aug 2023 13:32:26 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [107.220.113.177]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 6F2A0C152577 for <architecture-discuss@ietf.org>; Mon, 14 Aug 2023 13:32:26 -0700 (PDT)
Received: from localhost (unknown [10.0.0.9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.hardakers.net (Postfix) with ESMTPSA id 0C7F120693; Mon, 14 Aug 2023 13:32:26 -0700 (PDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.hardakers.net 0C7F120693
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardakers.net; s=default; t=1692045146; bh=CWmXUJDGfvpf9GSvDJUAwFvPfiA2Ohx22ia7d4r5/vA=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=J0PfjqbsaKS3NA3qscfVwbMr1TiYUgaM65cZgb/GNBUDFwoCgkPrSwuKRDhdaZ90X qBJTmqATsIIBJVyysAeqptGL07EykLxTmIgkibaCPoorsXqOO29GhCgqQ0qOSLtw5P AFLvSAz1eOErzT+8e4d/JL/TLtY9ZPGk4dJyryww=
From: Wes Hardaker <wjhns1@hardakers.net>
To: Arnaud Taddei <arnaud.taddei=40broadcom.com@dmarc.ietf.org>
Cc: Eliot Lear <lear@lear.ch>, "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>
References: <997f6696-dcd9-9d5d-26f2-3b486cee601b@lear.ch> <LO2P123MB3839473632C02D8D48B940E0F703A@LO2P123MB3839.GBRP123.PROD.OUTLOOK.COM>
Date: Mon, 14 Aug 2023 13:32:25 -0700
In-Reply-To: <LO2P123MB3839473632C02D8D48B940E0F703A@LO2P123MB3839.GBRP123.PROD.OUTLOOK.COM> (Arnaud Taddei's message of "Tue, 25 Jul 2023 13:30:48 +0000")
Message-ID: <ybly1idicva.fsf@wd.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/IeYiN7rPoAKj1N784itiEUqJOFs>
Subject: Re: [arch-d] draft-iab-m-ten-workshop
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Aug 2023 20:32:30 -0000
Arnaud Taddei <arnaud.taddei=40broadcom.com@dmarc.ietf.org> writes: Hi Arnaud, > To start with I don’t know what is it that I am doing wrong that I > don’t see any notification of such reports being published, though I > thought I put myself on all the right mailing lists. One of the important ones is architecture-discuss, which is where many discussions occur about IAB (and other) related efforts, including workshops: https://www.ietf.org/mailman/listinfo/architecture-discuss > I cannot judge if it represents what had been expressed or if more > non-neutral interpretation were added as I was not there. As I responded to Elliot, we did add some clarification at the top of the document about what the contents of the workshop report contains. > I remember I arrived too late for participation in this workshop but > really regret not being able to attend. I certainly regret having your voice in the room, and hope that if/when/etc future discussions occur you'll be able to add your voice to the dialog. It is a difficult problem space and determining the right balance between operations and privacy is far from solved, as the viewpoints are still very divergent. > I think a few opportunities were missed and this is mostly because the > representativity of who should have been in this workshop was > unbalanced. [entirely IMHO, but I believe many agree with me]: the IETF has always struggled to find the right balance of protocol design experts vs the operators that will hopefully deploy the results in the future. There have been many cases where the IETF has tried to attract operators to WG and Area meetings (opsarea being one, for example) and the success of those approaches have come in waves. It's a concerning challenge precisely because of some of the items discussed in the workshop, such as operator overload, as well as discussed in more recent threads within the IETF, such as travel funding being more difficult to come by. I'll end with one final point: as I said in the note to Eliot, the purpose of an IAB workshop is to *start* a discussion and we would like nothing more than follow-on work to continue after the workshop is over. So, please do consider publishing drafts/etc and other work that will further the discussion! As I said, it's not an easy problem and certainly we're far from done discussing it and to continue we need more ideas and potential directions well documented. -- Wes Hardaker USC/ISI
- [arch-d] draft-iab-m-ten-workshop Eliot Lear
- Re: [arch-d] draft-iab-m-ten-workshop Arnaud Taddei
- Re: [arch-d] draft-iab-m-ten-workshop Wes Hardaker
- Re: [arch-d] draft-iab-m-ten-workshop Wes Hardaker
- Re: [arch-d] draft-iab-m-ten-workshop Hesham ElBakoury
- Re: [arch-d] draft-iab-m-ten-workshop Wes Hardaker
- Re: [arch-d] draft-iab-m-ten-workshop Arnaud Taddei
- Re: [arch-d] draft-iab-m-ten-workshop Arnaud Taddei
- Re: [arch-d] draft-iab-m-ten-workshop Arnaud Taddei
- Re: [arch-d] draft-iab-m-ten-workshop Hesham ElBakoury
- Re: [arch-d] draft-iab-m-ten-workshop Salz, Rich
- Re: [arch-d] draft-iab-m-ten-workshop Arnaud Taddei
- Re: [arch-d] draft-iab-m-ten-workshop Hesham ElBakoury