Re: [arch-d] draft-iab-m-ten-workshop
Arnaud Taddei <arnaud.taddei@broadcom.com> Sat, 26 August 2023 12:35 UTC
Return-Path: <arnaud.taddei@broadcom.com>
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 57EE0C14CE4C for <architecture-discuss@ietfa.amsl.com>; Sat, 26 Aug 2023 05:35:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, 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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=broadcom.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 KbYkg77bnZ3o for <architecture-discuss@ietfa.amsl.com>; Sat, 26 Aug 2023 05:35:22 -0700 (PDT)
Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) (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 ED326C14CE2B for <architecture-discuss@ietf.org>; Sat, 26 Aug 2023 05:35:22 -0700 (PDT)
Received: by mail-wm1-x32e.google.com with SMTP id 5b1f17b1804b1-40061928e5aso16038275e9.3 for <architecture-discuss@ietf.org>; Sat, 26 Aug 2023 05:35:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; t=1693053321; x=1693658121; h=mime-version:accept-language:in-reply-to:references:message-id:date :thread-index:thread-topic:subject:cc:to:from:from:to:cc:subject :date:message-id:reply-to; bh=IJkpBSyG0A0wOlRAV1RVMdX938kyqMDUChN47M4dIgc=; b=Juk54XhdYRVYJW9N37CoQZ6e2OalBtJBVuq5+mfrMNVbJpA6onN0y05Hj5AYUsej9t r6gttMx2PE6NUyqxEXYCcXJyk9a/7Ll4kmb32xH4GkAwxTaWJAn1JTLylej/iTb1Ipfo p77gOS6hAjgox5Ms9D5udKoOAlJLc2rn41gy4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693053321; x=1693658121; h=mime-version:accept-language:in-reply-to:references:message-id:date :thread-index:thread-topic:subject:cc:to:from:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=IJkpBSyG0A0wOlRAV1RVMdX938kyqMDUChN47M4dIgc=; b=RyEH3uHEuhjUTRbkbV97rgz9jLghFIDEo8Ki4Ui9RXKnp9Ml1W+EDasMi3oTVGzQfd +fSip/lgA1UTwyjcs5pkiy6vPq/lWFAC886UtO324VM0zr+h32bCzu2phjIaUI73vTcf YoId/vPCh/FY7xklTl+yDeee1Ibezvp2kK3hoEfu621nqbGdPFleOpafmDkYlzzk8HkM 9nZEpk+ycSXzOzaFQu1JS2kx/zURE8HL6qOd0dlPAe0Dbf6B8SqQwaOILUFBQhBaRohq iilkS3Max9ijsOjdDWN78nqGGQ1kl/QCrVIQavuXspjYspdJ00HN7LymJEw1dyAqwxuN M5+A==
X-Gm-Message-State: AOJu0YwVGEcPPSPYV96UrqBdpON4lPbnKwMODAPEPIv0fAXMfI4Ltl/q wr3AkttBiF+lIX3vPDo1LRtoB6UY2Ba9Rzv05FP9O1EB+KUbbobdy5ECvO0uiosguUhaIaTQWF3 5/SZto4N0d/D8n4kU
X-Google-Smtp-Source: AGHT+IHVXuzoLa1LPhbKvyO+OZrrXIcPkfbwk/MU4dDmN2IqphRbvYGj2As+cFFG9kh65byR8nlTZQ==
X-Received: by 2002:a7b:c84a:0:b0:401:b1c6:97e8 with SMTP id c10-20020a7bc84a000000b00401b1c697e8mr4781928wml.36.1693053320704; Sat, 26 Aug 2023 05:35:20 -0700 (PDT)
Received: from LO2P123MB3839.GBRP123.PROD.OUTLOOK.COM ([2603:1026:c06:71::5]) by smtp.gmail.com with ESMTPSA id k21-20020a05600c0b5500b003feea62440bsm4820824wmr.43.2023.08.26.05.35.19 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 26 Aug 2023 05:35:19 -0700 (PDT)
From: Arnaud Taddei <arnaud.taddei@broadcom.com>
To: Wes Hardaker <wjhns1@hardakers.net>
CC: Eliot Lear <lear@lear.ch>, "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>
Thread-Topic: [arch-d] draft-iab-m-ten-workshop
Thread-Index: AWI2Zjk2kF9HqbZ6fiTaIGoGJ/0mukEwODYzQTA4NjNmLmNpbOf+8Did
X-MS-Exchange-MessageSentRepresentingType: 1
Date: Sat, 26 Aug 2023 12:35:19 +0000
Message-ID: <LO2P123MB3839AB183623467AF5DB5DC6F7E2A@LO2P123MB3839.GBRP123.PROD.OUTLOOK.COM>
References: <997f6696-dcd9-9d5d-26f2-3b486cee601b@lear.ch> <LO2P123MB3839473632C02D8D48B940E0F703A@LO2P123MB3839.GBRP123.PROD.OUTLOOK.COM> <ybly1idicva.fsf@wd.hardakers.net>
In-Reply-To: <ybly1idicva.fsf@wd.hardakers.net>
Accept-Language: en-US
X-MS-Has-Attach:
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator:
X-MS-Exchange-Organization-RecordReviewCfmType: 0
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="000000000000ca10070603d2b1a4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/8ZlC97ZntFnkTVgFL1gSQvIECEo>
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: Sat, 26 Aug 2023 12:35:27 -0000
Thanks Wes, so, am back from what were supposed to be holidays as you noticed. Makes all sense to me below. I don’t know if I will be in a position to contribute something to Prague given the (yiiik) work load ahead of me, but will do my best. From: Wes Hardaker <wjhns1@hardakers.net> Date: Monday, 14 August 2023 at 22:32 To: Arnaud Taddei <arnaud.taddei@broadcom.com> Cc: Eliot Lear <lear@lear.ch>, architecture-discuss@ietf.org <architecture-discuss@ietf.org> Subject: Re: [arch-d] draft-iab-m-ten-workshop 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.google.com/url?q=https://www.ietf.org/mailman/listinfo/architecture-discuss&source=gmail-imap&ust=1692649962000000&usg=AOvVaw1P3-8NlroxR4a17yX3UwEd > 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 -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.
- [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