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

Hesham ElBakoury <helbakoury@gmail.com> Sat, 06 May 2023 00:05 UTC

Return-Path: <helbakoury@gmail.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 A32DCC17CEA9 for <architecture-discuss@ietfa.amsl.com>; Fri, 5 May 2023 17:05:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level:
X-Spam-Status: No, score=-2.093 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_BLOCKED=0.001, 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=unavailable 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 dwQciyarwzoD for <architecture-discuss@ietfa.amsl.com>; Fri, 5 May 2023 17:05:48 -0700 (PDT)
Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (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 DEFFEC17CEB1 for <architecture-discuss@ietf.org>; Fri, 5 May 2023 17:05:48 -0700 (PDT)
Received: by mail-pg1-x529.google.com with SMTP id 41be03b00d2f7-51f1b6e8179so1605282a12.3 for <architecture-discuss@ietf.org>; Fri, 05 May 2023 17:05:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683331548; x=1685923548; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=1kMKiCo9Yf89ejC/2LKVoVN6W77qQKs2Oa44YZ2NQSo=; b=honakQodmj64OyFyTJqAycqrdh7O+dyFRc0pgfiSPnsI69DGMojiIcTgVTulBziFjE EekLlN1Zot7IMHMuqmQPEuVrBkDdYVk9SM0uYrAXyqQ0TrIsWJcMH2rxDvsOZfTWhk1Z WV5Nk46/wEV0QqBHA18CbLN24yJTkwietJmeA3BWHuREgYEiIaMycF+Cihk5PglBTKob W9NpPV630rfuwtqQH+38K4fS+iZVsBFlGN2HkVtPXkJ5SUvf5jYePsQQ9s3LSV1qz9yN F6m19czWT++MNc/fY/j9W61D+vFL+Q4qzfVe3Itz7+uSSCb0uJ5UpQdd580mufJsi9l6 gXZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683331548; x=1685923548; 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=1kMKiCo9Yf89ejC/2LKVoVN6W77qQKs2Oa44YZ2NQSo=; b=FaSvh+Qz9uALNKBVp4+T14AnfgPDwxBVLQI5lS4XsnhvJt+JiULBIHUGT3843FTqSJ U6dF1zcCTG/2ABuwtXIRaVEDQ8tvOgX7w8fp49fzfCoZfTertIN/a9Ack44J2myXUUgY z1JACc3nBA6DZHU+71SfoyT9twBKQWya496V2fywZ2igSNzJwLo0RFVd7X5GsmNhJHa0 N4jSy/Oh6qtb2Adxcw4Zj0LAVztt5uv1ppsWYs+YK1O5OuONp/EZfaH0gNdBy74CmCe0 drlmCTdVIxYimZWaNrN+D7HmYxcW5v3hDYTbXkjn9QDsiyH9enQ1lv5cmJItNBM7l9wb xCjQ==
X-Gm-Message-State: AC+VfDxOt6JazWH02jdMdYnVAFGDgDXPfxs/CnKuM+f2pIRvm/cjUubh jpEpz2JfaK1OATYWDWjdvODhACC/20rXO2AS6RxAyECz0Pw=
X-Google-Smtp-Source: ACHHUZ6ok7xd8UK0dLG2OxZay59BMNYWUnHKkxgHEU7XLJU5qUw5p+52bLCI7fx3GDmDAtgi8Iqr/Mh/Fu3Rt+D9Rbg=
X-Received: by 2002:a17:90b:1d87:b0:23e:fc9c:930 with SMTP id pf7-20020a17090b1d8700b0023efc9c0930mr3045871pjb.36.1683331548005; Fri, 05 May 2023 17:05:48 -0700 (PDT)
MIME-Version: 1.0
References: <168271026305.50065.11855031975777547008@ietfa.amsl.com> <CABcZeBPQRCg_9P20TVf=t-6+h7xvmgOWjAJ3oQc5BUJ14VvBrA@mail.gmail.com> <99b74fec-5f3b-d7be-fd4e-1c300b1d85d1@gmail.com> <1B995EBE-ECDB-4FCC-8ECD-57BE24182FD5@gmail.com> <CAA=duU2=-0i6BqXWWqFS+-Gu+K9KBoRVRDRPAoojj5p4eeDWWg@mail.gmail.com> <680069303.5441.1683023514937@appsuite-gw2.open-xchange.com> <CACsn0cmtewbqPA5aku70eeqvcCSYH8wFU0VzpWS90KaW-UHVdg@mail.gmail.com>
In-Reply-To: <CACsn0cmtewbqPA5aku70eeqvcCSYH8wFU0VzpWS90KaW-UHVdg@mail.gmail.com>
From: Hesham ElBakoury <helbakoury@gmail.com>
Date: Fri, 05 May 2023 17:05:36 -0700
Message-ID: <CAFvDQ9o8Aq_pwxhcJE-qbfKd8-jzFkGUgYAOEYrhcm8_5r5ViA@mail.gmail.com>
To: Watson Ladd <watsonbladd@gmail.com>
Cc: Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org>, IAB IAB <iab@iab.org>, architecture-discuss@ietf.org
Content-Type: multipart/alternative; boundary="000000000000f549f805fafb2a83"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/0ZK7eEk13DYnRPT7Jyh7Wds9kmA>
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: Sat, 06 May 2023 00:05:52 -0000

Akash Kapur had an Essay that was published by  Wall Street Journal
<https://www.wsj.com/articles/the-rising-threat-of-digital-nationalism-11572620577>
in
Nov 2019. The title of the essay is "*The Rising Threat of Digital
Nationalism".* This essay said:
"Nicholas Negroponte, a co-founder of the MIT Media Lab, once said that
national law had no place in cyberlaw. That view seems increasingly
anachronistic. Across the world, nation-states have been responding to a
series of crises on the internet (some real, some overstated) by asserting
their authority and claiming various forms of digital sovereignty. A
network that once seemed to effortlessly defy regulation is being
relentlessly, and often ruthlessly, domesticated."

Hesham




On Fri, May 5, 2023, 4:10 PM Watson Ladd <watsonbladd@gmail.com> wrote:

> On Tue, May 2, 2023, 3:38 AM 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.
>
> I seem to remember two WGs facing hostility due to policy and values
> issues: ohai and privacypass, and then the W3C has had its own issues
> with the Privacy Sandbox. So I don't think we can ignore these
> supratechnical issues entirely if participants are saying we should or
> shouldn't charter based on them. Also, ODoH, etc.
>
> This isn't new: we saw these sorts of issues in the 1990's with
> encryption, the 2010's post Snowden where the choices of what to
> standardize had a political valence.  Putting our head in the sand
> when participants are discussing these issues and bringing them up as
> reasons to standardize or not strikes me as counterproductive. It's
> also worth remembering that there is no protocol police: you can
> deploy any application to do anything on the net, and provided it
> doesn't cause problems for the rest of the network, or really problems
> for anyone who sits between you and the other users, it works. As a
> result standardization isn't really able to do anything more than say
> "no, that's a bad idea", but isn't able to actually stop it.
>
> The fact that the Internet is permissionless and implementation
> precedes standardization is good: it creates a dynamic environment
> that has tremendously benefited everyone involved, and has prevented
> rent-seekers who would like to stop investing and innovating and
> instead charge tolls.  That wasn't just a policy choice, but a result
> of technical decisions that enabled a decentralized network with
> distributed namespaces, as well as norms around interconnection, and I
> think that's more than just ISOC. And it also means that what the
> future of the Internet is is not controlled by the IETF but rather
> shaped by commercial forces and responses to emerging
> needs+technologies.
>
> Sincerely,
> Watson
>
> >
> > Ciao,
> >
> > --
> >
> > Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
> > 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.ietf.org/mailman/listinfo/architecture-discuss
>