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

Wes Hardaker <hardaker@isi.edu> Thu, 04 May 2023 22:49 UTC

Return-Path: <hardaker@isi.edu>
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 57D44C17EA47 for <architecture-discuss@ietfa.amsl.com>; Thu, 4 May 2023 15:49:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
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 XhLG46q6_0VI for <architecture-discuss@ietfa.amsl.com>; Thu, 4 May 2023 15:49:53 -0700 (PDT)
Received: from mx0f-006c3502.gpphosted.com (mx0f-006c3502.gpphosted.com [67.231.155.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3FB8C152DA7 for <architecture-discuss@ietf.org>; Thu, 4 May 2023 15:49:47 -0700 (PDT)
Received: from pps.filterd (m0280943.ppops.net [127.0.0.1]) by mx0e-006c3502.gpphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 344MFJDH024455 for <architecture-discuss@ietf.org>; Thu, 4 May 2023 15:49:47 -0700
Received: from mail-oa1-f72.google.com (mail-oa1-f72.google.com [209.85.160.72]) by mx0e-006c3502.gpphosted.com (PPS) with ESMTPS id 3q8y2fd1py-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for <architecture-discuss@ietf.org>; Thu, 04 May 2023 15:49:46 -0700
Received: by mail-oa1-f72.google.com with SMTP id 586e51a60fabf-19297b852cfso14780511fac.0 for <architecture-discuss@ietf.org>; Thu, 04 May 2023 15:49:46 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683240586; x=1685832586; 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=2uNOxPTBCzo0w1Y2VQqbFmxLCHeWhrXUzEvyIY6OGSU=; b=cuHC4ZaBrg1awLTxTKaEHkmNZ1/HIRXZYA5+IeTbFlKNLwHM6+C1eaUpEWQ+QMFU+O o+9Ki/GW+HDQPWi24M381dRo7wrA8bt3kGMoQ1DnDtuu17e8UQnRM0Vsl/XruX2qwFiu VZ9QcJl1A4PhS2huPoADPfG2xzYDpyDi4GT7GMFp2jWJFPUSXZxZiBBJHUJ/y7ca1rZE qn06f1mfD0vDetZeUhf7uJNnX6rkERe7tkreCyQ5vfraZA5eMLiTCRHkmAmxNTCxLxhh wcgY5C7ilozOkKbTD8UctNtJJ4/p0fu84+8cq8xQEuURSVJka8K063H/bo9f3uC38zgK v6SQ==
X-Gm-Message-State: AC+VfDzDSuInj9o8wzfXTPQVlwNezO24S8JoWXUz0LpFhLg3w7deMTUR EzzlH4cYzYvpHIi/MDaCn/r1KXmGtJmBuzuF1tsP9muFdTFbcy2wCTo8UFB4hxlrvacjls0Mzc8 WGAtBNnb6A08TaypaAR27VoTlEMohRJm44lihjjrs
X-Received: by 2002:a05:622a:1a99:b0:3f2:4c09:268c with SMTP id s25-20020a05622a1a9900b003f24c09268cmr7541239qtc.1.1683238734785; Thu, 04 May 2023 15:18:54 -0700 (PDT)
X-Google-Smtp-Source: ACHHUZ6Hlbn8FAgP+7XF9rBxDXMHdrDKuAhIQB3ok2yQgU9goavGicwcasD01eR07csoRzFFhIwEO5Ag/ZQqJYQM1zE=
X-Received: by 2002:a05:622a:1a99:b0:3f2:4c09:268c with SMTP id s25-20020a05622a1a9900b003f24c09268cmr7541213qtc.1.1683238734469; Thu, 04 May 2023 15:18:54 -0700 (PDT)
MIME-Version: 1.0
References: <168271026305.50065.11855031975777547008@ietfa.amsl.com> <ZFNyKr7ECZOPdNr0@faui48e.informatik.uni-erlangen.de> <9B421F04-2BA9-42B9-9E9F-15BD59BEF37B@kuehlewind.net> <319E5B8B-6CBA-496C-93CA-FA577D252F7D@broadcom.com> <785113C4-388A-4EEA-8A84-204B2C273A0F@kuehlewind.net> <ZFPgb7lm6v5C6hQK@faui48e.informatik.uni-erlangen.de>
In-Reply-To: <ZFPgb7lm6v5C6hQK@faui48e.informatik.uni-erlangen.de>
From: Wes Hardaker <hardaker@isi.edu>
Date: Thu, 04 May 2023 15:18:18 -0700
Message-ID: <CANk3-NDTomFLMZRT6u1ErFnD=DNWTRKYLX=YRjY94tqk+6DZRQ@mail.gmail.com>
To: Toerless Eckert <tte@cs.fau.de>
Cc: Mirja Kuehlewind <ietf@kuehlewind.net>, Arnaud Taddei <arnaud.taddei@broadcom.com>, Internet Architecture Board <iab@iab.org>, architecture-discuss@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d72e6e05fae58ecb"
X-Proofpoint-GUID: lgY9ciES55D468MvxvndhCePz2vnIV6T
X-Proofpoint-ORIG-GUID: lgY9ciES55D468MvxvndhCePz2vnIV6T
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.942,Hydra:6.0.573,FMLib:17.11.170.22 definitions=2023-05-04_13,2023-05-04_01,2023-02-09_01
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 mlxlogscore=570 phishscore=0 spamscore=0 clxscore=1011 adultscore=0 lowpriorityscore=0 bulkscore=0 malwarescore=0 impostorscore=0 mlxscore=0 suspectscore=0 priorityscore=1501 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2303200000 definitions=main-2305040185
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/fp2Pz4ses2YfPCtnDBx9iFuK1I8>
Subject: Re: [arch-d] [IAB] 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 22:49:55 -0000

>
>
>
> Too bad. Isn't the organization such that some first part of the meetings
> is considered public and only the second part IAB private ?


Mirja has already responded about the purpose behind the meetings
(essentially: to inform the IAB and prompt IAB discussions) and the purpose
behind advertising them more widely for people that want to obverse them
(they've always been publicly announced on the IAB agenda page, but others
have said they missed ones they'd be interested in attending).

But I did want to call out one point above: very little of the IAB meetings
are private.  You're just as welcome to come listen to our more
administrative meetings (where we do often discuss what future items should
go into the technical presentations).  The only time we generally dive into
executive sessions is when discussing appointing individuals to roles that
the IAB is responsible for making appointments (eg, liaison managers to
other SDOs).  You're welcome to attend and listen to any of the meetings as
observers, and this has been the case for at least 4 years and was trending
toward that direction even longer I think.
-- 
Wes Hardaker
USC/ISI