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

Arnaud Taddei <arnaud.taddei@broadcom.com> Wed, 03 May 2023 07:09 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 91D69C1519AF for <architecture-discuss@ietfa.amsl.com>; Wed, 3 May 2023 00:09:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.995
X-Spam-Level:
X-Spam-Status: No, score=-1.995 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, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 esllcCXfUcJr for <architecture-discuss@ietfa.amsl.com>; Wed, 3 May 2023 00:09:41 -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 4F75AC151998 for <architecture-discuss@ietf.org>; Wed, 3 May 2023 00:09:40 -0700 (PDT)
Received: by mail-wm1-x32e.google.com with SMTP id 5b1f17b1804b1-3f178da21b5so30868275e9.3 for <architecture-discuss@ietf.org>; Wed, 03 May 2023 00:09:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; t=1683097778; x=1685689778; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=Ilq0G9g7kvwHZuO4otE9do3JEzumER3MK1P0WMDGeyI=; b=YD330u/F/BMoK3QkcaBcIriRb0lqQhnqfCZw8Btf9iuuPlVts5ck4EO9eDLxlsSkG4 rPMzm0/uCiztVQQxEjv+ap6b2WEYcxvgGZnP83dqk0clFjKK54thjLcmZksyQYR9rfiN EgILF6p/Jk1//oTylNcZjZor9JN6Kdb8q56TI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683097778; x=1685689778; 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=Ilq0G9g7kvwHZuO4otE9do3JEzumER3MK1P0WMDGeyI=; b=I69CJHv8oSsOV77MRBKDJtAuuGTOaDdmpvSDzIsa2jzbsVVXH4WOX/KxeuC4PQ0UMr oNiwanfLxLsKYhf22rTw+UTMp2ZeS7Fyc72F2Rl98cHX9kulqVIAggZX0tbL/sAag+x7 hQQwNy3v2nBYBdeUD+7XjbXIDpfp4c4nMs9DDDm7eWxgjSRXEVKCLkcGmX5QAn+LznkM YMV5E+vA74L/2hF4JQu4QgBjXXGPy6z0pflwogISgc67Unxvoypp3JH5NWLKihMy2qZU wzcLjM6tlGHSmxqDz4WKsRThyio+WEocaldJtHwuD10iQaTkx9LVremD3kVpqJzIUsAW 0RNA==
X-Gm-Message-State: AC+VfDyNWKVv+3+QHyr8+PyeGk70P+vrOG9N6gUPllBydPfnerVGWmss JAF2ndVOdPmcEYdr2vUgF1RTAHE1I4EI+WJj64jhu2Teeh1+qVof9u+CuE1I6jUHpKIzhyiIOwn X/wRSWa+VvEQQHEUFv2M2zRWhx0s+a5+k
X-Google-Smtp-Source: ACHHUZ4jW78iqxyOVDEOMWou+a0B42mf+9u7E4iIFRZ+stPkjOkCJ5Qq931mJbqLUohoyuz+SIl1dA==
X-Received: by 2002:a7b:cd09:0:b0:3f2:507f:25a4 with SMTP id f9-20020a7bcd09000000b003f2507f25a4mr13920804wmj.30.1683097778319; Wed, 03 May 2023 00:09:38 -0700 (PDT)
Received: from smtpclient.apple ([2a01:e0a:b16:f660:e081:d1f0:40db:3429]) by smtp.gmail.com with ESMTPSA id x8-20020a1c7c08000000b003f24f245f57sm906804wmc.42.2023.05.03.00.09.37 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 May 2023 00:09:37 -0700 (PDT)
From: Arnaud Taddei <arnaud.taddei@broadcom.com>
Message-Id: <0C1DA372-6E26-48E6-B65F-54766AD8519B@broadcom.com>
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
Date: Wed, 03 May 2023 09:09:26 +0200
In-Reply-To: <B27A0278-E940-4E9F-9B3A-202FB9CCC6E5@kuehlewind.net>
Cc: Eric Rescorla <ekr@rtfm.com>, architecture-discuss@ietf.org, Internet Architecture Board <iab@iab.org>
To: Mirja Kuehlewind <ietf@kuehlewind.net>
References: <168271026305.50065.11855031975777547008@ietfa.amsl.com> <CABcZeBPQRCg_9P20TVf=t-6+h7xvmgOWjAJ3oQc5BUJ14VvBrA@mail.gmail.com> <B27A0278-E940-4E9F-9B3A-202FB9CCC6E5@kuehlewind.net>
X-Mailer: Apple Mail (2.3731.500.231)
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="0000000000003b193b05fac4bdaa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/WOC6SRQtgieZ1C4E-y8L8m0FqIE>
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: Wed, 03 May 2023 07:09:45 -0000

Hi Mirja, that is helpful context for new comers like me. 

I can only encourage you to pursue in this line of publishing in advance what is happening. 

And yes for the minutes as probably there cannot be consistent attendance compatible with business life too. 

So the possibility to read offline will certainly help. 




> On 3 May 2023, at 07:52, Mirja Kuehlewind <ietf@kuehlewind.net> wrote:
> 
> Hi Ekr, hi all,
> 
> Thanks for your interest!
> 
> The IAB is dedicating normally one of our weekly calls for a technical discussions. We do this already since more than a year but just recently decided to announce it more explicitly on architecture discuss mailing list (instead of only in the agenda on the IAB website) as we received feedback from the community that some of the topics may be of interest for observers. The topic this time is not meant to be special in anyway, it has just been the first announcement of this kind.
> 
> The technical discussions cover a wide range of topics that are usually proposed by one IAB member who then organises some invited speakers to join and set the stage for all other IAB members. We announced this already at IETF-112 in IAB Open (see some past topics on side 10 https://datatracker.ietf.org/meeting/112/materials/slides-112-iabopen-welcome-and-status-update-04 <https://www.google.com/url?q=https://datatracker.ietf.org/meeting/112/materials/slides-112-iabopen-welcome-and-status-update-04&source=gmail-imap&ust=1683697970000000&usg=AOvVaw3wWQqS6oT_0DlRiaJtC_G4>) and you can also find more information about past sessions in the minutes.
> 
> Having invited technical talks as part of our call is not new to the IAB, it’s only that we, since last year, try to do it more regularly once per month. Usually these sessions are for information to the IAB to understand an on-going discussion and its background better and may or may not be a starting point for further discussion. That's also why we thought it could be interesting for a wider audience to join and listen.
> 
> The IAB itself usually doesn’t have much more information than a title and some speaker names. There may or may not have been some internal discussion on the mailing list in a previous call but again it's mainly to learn. As such I'd rather recommend people to join as observer if they also want to learn something about the topic, than people how may be already working on the topic and know the background (if you happen to have time). Of course we will also publish minutes afterwards which usually also provide a good overview about what was presented.
> 
> Mirja
> 
> P.S.: To maybe explicitly relate to your question, Ekr, I believe it is by now already clear from the mailing list discussion that this is not about IP fragmentation...
> 
>  
> 
>> On 28. Apr 2023, at 21:39, Eric Rescorla <ekr@rtfm.com> wrote:
>> 
>> Can you provide some more information on what aspect of "fragmentation" this will be addressing?
>> 
>> On Fri, Apr 28, 2023 at 12:35 PM IAB Executive Administrative Manager <execd@iab.org <mailto:execd@iab.org>> wrote:
>>> All members of the community are welcome to attend IAB teleconferences as observers. Observers are not invited to participate in the discussion.
>>> 
>>> The next IAB teleconference will be held on Wednesday, 2023-05-03 from 0700-0800 PDT (1400-1500 UTC). The agenda and Webex information is at the bottom of this message.
>>> 
>>> 
>>> IAB Technical Discussion: 2023-05-03
>>> 
>>> 0700-0800 US/Canada Pacific 
>>> 0800-0900 US/Canada Mountain 
>>> 0900-1000 US/Canada Central 
>>> 1000-1100 US/Canada Eastern 
>>> 1400-1500 UTC
>>> 1500-1600 United Kingdom 
>>> 1600-1700 Germany 
>>> 1700-1800 Finland 
>>> 1930-2030 India
>>> 2200-2300 (next day) China 
>>> 
>>> Webex: <⁨https://ietf.webex.com/ietf/j.php?MTID=m92c425d161e1be552b21d6b84b1c09f6 <https://www.google.com/url?q=https://ietf.webex.com/ietf/j.php?MTID%3Dm92c425d161e1be552b21d6b84b1c09f6&source=gmail-imap&ust=1683697970000000&usg=AOvVaw0lUI3Za6ciSB4iscjrTPqz>⁩>
>>> 
>>> Call-in toll number (US/Canada): 1-650-479-3208 
>>> 
>>> Access code: 644 905 221 
>>> 
>>> Meeting password: 1@Bmeet
>>> 
>>> 
>>> 1. Administrivia (Cindy) - <5 mins (Public)
>>> 
>>>   1.1. Attendance 
>>> 
>>>   1.2. Agenda bash and announcements 
>>> 
>>>   1.3. Meeting Minutes 
>>> 
>>>   1.4. Action Item Review - 5 mins
>>> 
>>> 
>>> 2. Technical Discussion: Fragmentation (with Sheetal Kumar, 
>>>     Konstantinos Komaitis, David Frautschy) - 50 mins (Public)
>>> 
>>> Information about remote participation:
>>> https://ietf.webex.com/ietf/j.php?MTID=m92c425d161e1be552b21d6b84b1c09f6 <https://www.google.com/url?q=https://ietf.webex.com/ietf/j.php?MTID%3Dm92c425d161e1be552b21d6b84b1c09f6&source=gmail-imap&ust=1683697970000000&usg=AOvVaw0lUI3Za6ciSB4iscjrTPqz>
>>> 
>>> 
>>> 
>>> --
>>> A calendar subscription for all IAB meetings is available at
>>> https://calendar.google.com/calendar/ical/ietf.org_k88jdeojmvn249q37ain3ojepc%40group.calendar.google.com/public/basic.ics <https://www.google.com/url?q=https://calendar.google.com/calendar/ical/ietf.org_k88jdeojmvn249q37ain3ojepc%2540group.calendar.google.com/public/basic.ics&source=gmail-imap&ust=1683697970000000&usg=AOvVaw3tvblkyAM7OKyf4zwIm3mq>
>>> 
>>> _______________________________________________
>>> Architecture-discuss mailing list
>>> Architecture-discuss@ietf.org <mailto:Architecture-discuss@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/architecture-discuss <https://www.google.com/url?q=https://www.ietf.org/mailman/listinfo/architecture-discuss&source=gmail-imap&ust=1683697970000000&usg=AOvVaw2Pr8W0z8qDfOlhSYti6IWc>
>> _______________________________________________
>> 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=1683697970000000&usg=AOvVaw2Pr8W0z8qDfOlhSYti6IWc


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