Re: [arch-d] Side meeting on protocol development, the IETF and Internet consolidation at IETF 114

mark@mcfaddencentral.com Fri, 22 July 2022 15:36 UTC

Return-Path: <mark@mcfaddencentral.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 2D58DC15A722 for <architecture-discuss@ietfa.amsl.com>; Fri, 22 Jul 2022 08:36:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.925
X-Spam-Level:
X-Spam-Status: No, score=-1.925 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 I5ql110-N_9x for <architecture-discuss@ietfa.amsl.com>; Fri, 22 Jul 2022 08:36:05 -0700 (PDT)
Received: from relay.hostedemail.com (smtprelay0012.hostedemail.com [216.40.44.12]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 0B4BAC15791C for <architecture-discuss@ietf.org>; Fri, 22 Jul 2022 08:36:04 -0700 (PDT)
Received: from omf03.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay02.hostedemail.com (Postfix) with ESMTP id E14FE120D20; Fri, 22 Jul 2022 15:36:01 +0000 (UTC)
Received: from [HIDDEN] (Authenticated sender: mark@mcfaddencentral.com) by omf03.hostedemail.com (Postfix) with ESMTPA id 379E56000B; Fri, 22 Jul 2022 15:36:01 +0000 (UTC)
Reply-To: mark@mcfaddencentral.com
From: mark@mcfaddencentral.com
To: 'John C Klensin' <john-ietf@jck.com>
Cc: architecture-discuss@ietf.org
References: <a1e6afde474c52cda2c2c5641cff6d14@mcfaddencentral.com> <7B296F59914407E95BDC59D9@PSB>
In-Reply-To: <7B296F59914407E95BDC59D9@PSB>
Date: Fri, 22 Jul 2022 10:35:59 -0500
Organization: Madison Wisconsin
Message-ID: <01bf01d89de0$bed53ab0$3c7fb010$@mcfaddencentral.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHwyw3eaecxBnCOGUsdI6m0LUnvuAG9wi+OrUw8tXA=
Content-Language: en-us
X-Stat-Signature: 8mbidnpz6cik97zf66zmekoxciwjxqwe
X-Rspamd-Server: rspamout05
X-Rspamd-Queue-Id: 379E56000B
X-Session-Marker: 6D61726B406D6366616464656E63656E7472616C2E636F6D
X-Session-ID: U2FsdGVkX1+IbhBfwrwAGMLflCE/Yvhjztc6QC9qzlc=
X-HE-Tag: 1658504161-784643
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/V4hBkDgX0HJ8gdU31bs0qzOAbGQ>
Subject: Re: [arch-d] Side meeting on protocol development, the IETF and Internet consolidation at IETF 114
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: Fri, 22 Jul 2022 15:36:09 -0000

Hi John,

At first, we were not going to support remote participation, but there seems
to be some interest. So, we are working on that feature.
We are also aware of a possible conflict with DINRG which needs to be
resolved and may require moving the side meeting to a different meeting
slot.

I'll update both the Public Side Meetings page and the mailing list.

mark

Mark McFadden
Madison, Wisconsin
e: mark@mcfaddencentral.com
Tw: McElmside | Fb: Mark McFadden | Skype: McElmside | In: McElmside

-----Original Message-----
From: John C Klensin <john-ietf@jck.com> 
Sent: Friday, July 22, 2022 10:31 AM
To: Mark McFadden <mark@mcfaddencentral.com>
Cc: architecture-discuss@ietf.org
Subject: Re: [arch-d] Side meeting on protocol development, the IETF and
Internet consolidation at IETF 114

Mark,

According to
https://trac.ietf.org/trac/ietf/meeting/wiki/114sidemeetings
there does not appear to be a plan for access to this session by remote
participants.  Is that correct?

   john


--On Thursday, July 21, 2022 09:33 -0500 Mark McFadden
<mark@mcfaddencentral.com> wrote:

> 
> 
> Public Side Meeting: Consolidation
> Protocol development, the IETF and Internet consolidation
> ---------------------------------------------------------
> Thursday, 28 July 1600-1730 local time
> 
> Several recent Internet drafts have discussed aspects of consolidation 
> and how protocol design and consolidation interact. While some of the 
> drafts have had extensive revisions based on discussions on mailing 
> lists, consolidation is not a part of any charter for a Working Group 
> and seldom gets discussed in larger, plenary sessions.  The purpose of 
> this session is to have a brief discussion of some of the important 
> contributions and then a discussion of whether this should be a topic 
> that gets more formal treatment within some part of the IETF, IAB or 
> IRTF. One of the drafts describes consolidation as "the process of 
> increasing control over internet infrastructure and services by a 
> small set of organizations."
> 
> Draft agenda for the meeting:
> -----------------------------
> 1. Introduction, purpose and ground rules for the meeting 2. 
> Characteristics of existing I-Ds that discuss consolidastion 3. 
> Discussion of whether or not consolidation is an appropriate topic 
> within the IETF 4. Assessment and agreement of next steps (e.g. 
> meeting in London at 115) 5. AOB
> 
> The meeting will be chaired by Jim Reid.
> Questions or suggestions can be sent to mark <at> 
> internetpolicyadvisors.com