Re: [arch-d] IAB Technical Discussion on Fragmentation: 2023-05-03

Arnaud Taddei <arnaud.taddei@broadcom.com> Tue, 02 May 2023 12:25 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 26C09C1524BC for <architecture-discuss@ietfa.amsl.com>; Tue, 2 May 2023 05:25:37 -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, 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, 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 JRGLkHhhTBey for <architecture-discuss@ietfa.amsl.com>; Tue, 2 May 2023 05:25:33 -0700 (PDT)
Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (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 7C2E6C1522D3 for <architecture-discuss@ietf.org>; Tue, 2 May 2023 05:25:06 -0700 (PDT)
Received: by mail-ed1-x52b.google.com with SMTP id 4fb4d7f45d1cf-50bc570b4a3so4210513a12.1 for <architecture-discuss@ietf.org>; Tue, 02 May 2023 05:25:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; t=1683030304; x=1685622304; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=Py5gVkWd+kkcZVQvA6g1v3sSCuea1sroMWMHYFz+h0Y=; b=EOx78SdzXi2CqpMh9Ez26M2F+cjtEHePvTcO/sI/gPLs28OlNezXnptr/Zd7to9Cdu qpRW9hrrVE4CFCfWSTddDBpMm3kHM59dUkA3JrkwArHv6w8uZUaIUx+khHLMhOiVF6eM HsnVPPw5q+l9+AkAxaOySI78ehLsURALh236A=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683030304; x=1685622304; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Py5gVkWd+kkcZVQvA6g1v3sSCuea1sroMWMHYFz+h0Y=; b=jeqStu8bYHq4Ren9+HHor1TGwHPbpPbhpInuzIKPR6U0DomLK4NeWaPaQwDOT3SDt+ 9rBE0Ne+1PPbJVgbAk3Y+ml4bYbOruosX60lXy12WbxqG1uqdr1X3GH/k/f/fboUS75e /qR1Ix6lBV+tZ6lz13nbutMBBqP8MbLmKuC9wtpJU9qalX1Nu9CSV5+eQjuN0vN96wby V4Ts96iJUi5DicxEBTYX+6c+BMhan1lcfDuIN5l9VdRpiS2aZhLnGIdukYPz/qRJN1+o 7DnMkdcj/D7MvkHsA8kMq43MLJHklnPpEUXTtdlSU/kgcj4wodvnNXhTIE32QYlUaVd4 E8tg==
X-Gm-Message-State: AC+VfDynUDHEVIj4uVV/hhrXeJmij/z8E/IV3KU80MaI3lOzREfzitRg y0h+hmI1lxv/E79AXiD8cEbB2+aBzw5NDzKCxrn8jEdz2EVVvsuACPK+dSTA1S8dEhPjpUgTm+1 Vp3mfwjguX/xyx9cJ
X-Google-Smtp-Source: ACHHUZ4/xZWY+nIK3KCyXA2QBDV1BNxWnJISg6TYg4SeVRP1zT/6OWLisb3F/UJ7yXTyaePTSUPHuw==
X-Received: by 2002:aa7:cf97:0:b0:50b:cadd:21db with SMTP id z23-20020aa7cf97000000b0050bcadd21dbmr3475958edx.10.1683030303960; Tue, 02 May 2023 05:25:03 -0700 (PDT)
Received: from smtpclient.apple ([2a00:7580:60:1224:1ca0:ca3a:243e:ad7b]) by smtp.gmail.com with ESMTPSA id g24-20020a50ee18000000b0050690bc07a3sm12985696eds.18.2023.05.02.05.25.01 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 May 2023 05:25:02 -0700 (PDT)
From: Arnaud Taddei <arnaud.taddei@broadcom.com>
Message-Id: <8E0CAC56-A64E-443F-864E-35A824C600DB@broadcom.com>
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
Date: Tue, 02 May 2023 14:24:51 +0200
In-Reply-To: <CB03498A-20A1-482B-A088-B032391DBBA2@lastpresslabel.com>
Cc: Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org>, architecture-discuss@ietf.org, iab@iab.org
To: Dominique Lazanski <dml@lastpresslabel.com>
References: <680069303.5441.1683023514937@appsuite-gw2.open-xchange.com> <CB03498A-20A1-482B-A088-B032391DBBA2@lastpresslabel.com>
X-Mailer: Apple Mail (2.3731.500.231)
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="0000000000006fee8005fab507fd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/Pv2D3M7DZrqNShFO2JonuM7k_fA>
Subject: Re: [arch-d] IAB Technical Discussion on Fragmentation: 2023-05-03
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: Tue, 02 May 2023 12:25:37 -0000

Ok 
Unless I missed an email, a week notice for such a meeting is too short. Will be there though but pure coincidence
There is a general lack of context and and there is no definition of the term fragmentation nor the scope, nor the goal
Just to read the few references listed in this thread takes a lot of time 
The PNIF doesn’t provide definition, just a framework with no definiton
The WEF document is old 2015 but at least provides some definitions / categorisation
To align with Vittorio and Dominique, as the ITU was mentioned, like the ITU should stay in its box, the IETF should stay in its box too

> On 2 May 2023, at 13:02, Dominique Lazanski <dml@lastpresslabel.com> wrote:
> 
> I agree with you, Vittorio, and to take that one step further, I continue to be disappointed in the lack of leadership and technical vision for the Internet from the IAB. Where is the clear statement of 3-5 year view? Is it just going to be “encrypt all things all the time” without discussion or any nuance? 
> 
> I’m also looking forward to understanding how fragmentation is defined. Personally, I’m disappointed in the lack of discussion on technical consolidation too. 
> 
> The ongoing issue with the I* is that though there is solid proof for the success of the multistakeholder model, there is a lack of consistent leadership at the top. It’s the same old, same old. We need some fresh thinking. 
> 
> Dominique 
> 
> 
>> 
>> On 2 May 2023, at 11:38, Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org> wrote:
>> 
>> 
>>  
>>> Il 28/04/2023 23:54 CEST Andrew G. Malis <agmalis@gmail.com> ha scritto:
>>>  
>>>  
>>> Bob,
>>>  
>>> I also had the same initial thought. And I've even got an RFC discussing pseudowire fragmentation, so I was looking forward to an IP fragmentation discussion!
>> I guess this is part of the current, extensive effort by the I* organisations (mostly ISOC and ICANN) to counter any renewed proposals for a different governance structure for the key technical resources of the Internet, i.e. names and numbers (did anyone say ITU?).
>>  
>> However, there is some ambiguity on whether this also extends to regulation at the application layer, like the recent efforts in Europe to establish rules that would force the global Internet industry to tailor their services to specific European norms (this may go as far, to give you an example of a current discussion, to require AI models to be able to forget all information they learned about a specific European citizen, which of course is not technically easy; but it also includes pro-competition measures against walled gardens, requirements for large online information platforms, and, more controversially, proposals to mandate the screening of personal messages for CSAM).
>>  
>> I am curious to see how the IAB defines "fragmentation" - this is an ongoing discussion at the already mentioned IGF PNIF - and thus what is the scope of this "technical discussion". Personally, I would encourage the IAB to stay out of the latter set of problems, as there is almost nothing technical in them - it's all about policy, values, interests and compromises.
>>  
>> Ciao,
>> --
>> 
>> Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
>> vittorio.bertola@open-xchange.com <mailto:vittorio.bertola@open-xchange.com> 
>> Office @ Via Treviso 12, 10144 Torino, Italy
>> _______________________________________________
>> Architecture-discuss mailing list
>> Architecture-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/architecture-discuss
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.google.com/url?q=https://www.ietf.org/mailman/listinfo/architecture-discuss&source=gmail-imap&ust=1683630182000000&usg=AOvVaw2kgBotBa8wDm6ikhU4Bzs3


-- 
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.