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

Arnaud Taddei <arnaud.taddei@broadcom.com> Thu, 04 May 2023 06:45 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 91997C151543 for <architecture-discuss@ietfa.amsl.com>; Wed, 3 May 2023 23:45: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, 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_DNSWL_NONE=-0.0001, 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 lt7S7OBpOeES for <architecture-discuss@ietfa.amsl.com>; Wed, 3 May 2023 23:45:30 -0700 (PDT)
Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (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 93855C14CE31 for <architecture-discuss@ietf.org>; Wed, 3 May 2023 23:45:29 -0700 (PDT)
Received: by mail-wm1-x32b.google.com with SMTP id 5b1f17b1804b1-3f315712406so50144315e9.0 for <architecture-discuss@ietf.org>; Wed, 03 May 2023 23:45:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; t=1683182728; x=1685774728; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=fnsdjydgvJIIMhvO7JcHiZMbW/4UH6pI/RkWLQCENjE=; b=PhFu4oH9cipsHm7ojgiVMd6WoTz6jcu84n06I10GKg0Z6OOKw8EF1qN7gs2DezNVap M10r7geGGxU04t5LNMrff+pEkoxuVukBnNDINnYkRb+o5pGlA0zFfQsBQgfP6kfaHYMf wedauMRSiOIi0dTYkYUefDlpgoIg3lBeejSsI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683182728; x=1685774728; 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=fnsdjydgvJIIMhvO7JcHiZMbW/4UH6pI/RkWLQCENjE=; b=b3n2FVpMIRUBdwo5cOg4AorV0RDOJOQEA+aHjZNNBY0FJPGk2VLuDDr3sdYTZOc94R gKBTopJrCLvAElE2im9e4PahOjIPAB0XZd6G8ERj+oedt6wuH7Ey5ZcpndtS4kQZGLK2 58CL9swx02Q7BWQX3GUEBtj6k0YSAVhGKqIlSA+ZAVg3mzliJva4fK7W7HLlT+QaadqK FqE9O5EkI8RYMDHoTPo+2NNVn6ivTfM7uAUA8RwhkQ7UuGOimLTg2J8CFseamMSEFGKF +IJVX2v2fH6o15Wf+Szge7rqErafEIRPu+P/4Gsq8XY522AQ9+V994yDltNxZWVsBlEa OH6w==
X-Gm-Message-State: AC+VfDwW0noBZgaT061I74atVfPV+01wzk6hIp2Ylkle95niEXfVp7a+ aDFzbrjnpDUVwoH8+qP+du+j4PGzcDi7kkF0VsDJOrmluDUdYAZ8jZ6HucNcboutqJvBbIPGp5w 6dICoX7YloHUavCCr
X-Google-Smtp-Source: ACHHUZ4B6p9TS4uQFo+WSpPOOg/WzleF3NeoWS9tUZu/QOp7ITRblBlLA5hw7YLey1oikUKjyR1kSg==
X-Received: by 2002:a05:600c:3ac5:b0:3f1:96a8:3560 with SMTP id d5-20020a05600c3ac500b003f196a83560mr3228084wms.10.1683182728056; Wed, 03 May 2023 23:45:28 -0700 (PDT)
Received: from smtpclient.apple ([2a01:e0a:b16:f660:d192:ea7f:faee:6964]) by smtp.gmail.com with ESMTPSA id p1-20020a05600c204100b003f0a6a1f969sm3826284wmg.46.2023.05.03.23.45.27 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 May 2023 23:45:27 -0700 (PDT)
From: Arnaud Taddei <arnaud.taddei@broadcom.com>
Message-Id: <BA65524C-998A-4B4D-8D78-5BDCC76B8DEE@broadcom.com>
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
Date: Thu, 04 May 2023 08:45:16 +0200
In-Reply-To: <5fb41d7a-dbc0-b802-fdfb-3daae9ebfa49@gmail.com>
Cc: Vittorio Bertola <vittorio.bertola@open-xchange.com>, Mirja Kuehlewind <ietf@kuehlewind.net>, Internet Architecture Board <iab@iab.org>, architecture-discuss@ietf.org
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <168271026305.50065.11855031975777547008@ietfa.amsl.com> <CABcZeBPQRCg_9P20TVf=t-6+h7xvmgOWjAJ3oQc5BUJ14VvBrA@mail.gmail.com> <B27A0278-E940-4E9F-9B3A-202FB9CCC6E5@kuehlewind.net> <0C1DA372-6E26-48E6-B65F-54766AD8519B@broadcom.com> <327867555.16482.1683128195510@appsuite-gw2.open-xchange.com> <5fb41d7a-dbc0-b802-fdfb-3daae9ebfa49@gmail.com>
X-Mailer: Apple Mail (2.3731.500.231)
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="000000000000a0c10305fad884b6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/5Fx--xTkcWwwsD4qHy6wme58xuw>
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: Thu, 04 May 2023 06:45:34 -0000

Both presentations were interesting to me and I learnt a few things so it was helpful (including the rules, so I hope this is ok to share here if not tell me)

However I am really surprised on the positions regarding private sector. Like if the private sector had some choices, very strange. 

Just without really thinking about it and listing a few forces:

Compliancy is imposed by administrations (national, regional, etc.) on companies and this is a big source of what we call here ‘hyper-regionalisation’ instead of fragmentation. This is mostly law fare that is imposing technical constraints by ripple effects on all sorts of dimensions (security, international data transfer, localisation, logging, networking, cloud tenants, etc.)
This is not an enterprise choice
Security is itself imposing defences that for a long time, as the name will indicate a sign of fragmentation, are under the ‘perimeter defence’ principle moving to new … ‘words’ like Zero Trust.  
This is not an enterprise choice
Clouds are by their nature destroying one part of interoperability. e.g. in the general case (you can always have some luck with peering) you can’t leverage 2 components that sit on 2 cloud providers because of the network topology underlying will create latency. 
This is not an enterprise choice: Enterprises hate it because it leads to vendor lock-in
Centralisation of offers in a few hands which creates its own fragmentation "by gravitation"
This is not an enterprise choice + e.g. the EU is now putting language irt ‘concentration’ in its laws
… To be continued, discussed … 

Agree with Vittorio and Brian in general and especially on ‘dual-use’, and again, as the other SDOs should stay in their box, same to IETF. 

Just that from the last IETF 116 I learnt we moved from End to End principle, to Edge to Edge, which is in itself a new source of fragmentation perhaps?

Probably just 0.02 swiss franks


> On 3 May 2023, at 23:12, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> On 04-May-23 03:36, Vittorio Bertola wrote:
> 
> Thanks for sending your view of the meeting. On one point:
> 
>> I thought that we were in favour of privacy and end-user control, not against! 
> 
> It certainly depends on who you mean by "we". We, the IETF, and by implication the IAB, are to some extent the victims of the tussle here. Yes, we believe that making the Internet work better includes providing technology for private end-to-end communication. We work to specify such technology. But I think you'll find that this is dual-use technology. It can be used to create walled gardens as well as to protect individual rights. I think that the dual-use analogy probably extends to most of the technology of concern here.
> 
> You are correct that the IAB and the IETF need to watch out here and, I believe, need to steer clear of taking sides about how our dual-use technology is applied. ISOC might want to get into that morass, but we here should stay out of it, IMHO.
> 
> Regards
>    Brian


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