[PANRG] Re: A discussion Tuesday about the future of PANRG
Colin Perkins <csp@csperkins.org> Tue, 21 July 2026 16:02 UTC
Return-Path: <csp@csperkins.org>
X-Original-To: panrg@mail2.ietf.org
Delivered-To: panrg@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 8F45011B8CE5A for <panrg@mail2.ietf.org>; Tue, 21 Jul 2026 09:02:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784649733; bh=fXndw1dMqnyUq6TMxuDus/+bDo5eKB7T0JXJn/sKA1E=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=dMy7Myr4Fw0MkKF150YColaf88cWAfsaqDc8OSlEcOLA8cRhvcgTlyLtxILKIRbRE lXzqkdKfVTMGusU04T0TJXDANPP83fS9Gu5nuHZtzSb9m21QyO6DrTPGDXVnMLR1mY fIujGZH7XgtTEnIRwYtr1Y2F1w/eRZP9hbJyp4BU=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.4
X-Spam-Level:
X-Spam-Status: No, score=-4.4 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=csperkins.org
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4y2WdgYEt_nj for <panrg@mail2.ietf.org>; Tue, 21 Jul 2026 09:02:12 -0700 (PDT)
Received: from mx1.mythic-beasts.com (mx1.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 614AA11B8CE1E for <panrg@irtf.org>; Tue, 21 Jul 2026 09:02:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=csperkins.org; s=mythic-beasts-k1; h=Date:Subject:To:From; bh=UUH/bffCwarWu1SxdFnwtgIF1GHPsIeIqZkqSB+JzAA=; b=XYBIWWq1yay/8w4vT35peRkdQ4 cr9h0tSDNmffZ7fyYTDaNKgvQ2yyMmyhURgC4rtVfj6Exm4rhAOXZjD9tSf2sR+pWMldaNxH37n45 Oe7/tIqDHSKQyRKFqg6pyse5VR6zPRFm9fXsw49AvrWuo/urU/NJ+nOtZWLA8iucX47T8Bjyuq2Ia un3XUX09BoBiwvY8mrrW9PdhWBIC6zL/RhdiwTb9/T86w66hz8c2TA5MVP2jHMZ2jkSwxGbQ/7edj +zwm1qCoCrHTeMbO6vQPb0DD4xT5hSfLLAnHjUgmSxydD8LdI6RndaSau7utaO6rzINpW+84p5hJl HjXuOuvA==;
Received: by mailhub-cam-d.mythic-beasts.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from <csp@csperkins.org>) id 1wmCur-000Sb2-17; Tue, 21 Jul 2026 17:02:05 +0100
From: Colin Perkins <csp@csperkins.org>
To: "Brian Trammell (IETF)" <ietf@trammell.ch>
Date: Tue, 21 Jul 2026 18:01:49 +0200
X-Mailer: MailMate (2.0r6290)
Message-ID: <4C65F8F5-DB3C-46A9-9D2A-469EA84FFA0B@csperkins.org>
In-Reply-To: <0E307180-11CB-4CDE-B52F-BB1F78B029F0@trammell.ch>
References: <0E307180-11CB-4CDE-B52F-BB1F78B029F0@trammell.ch>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_C349D2ED-D2AC-4064-839A-E5FC530AAACC_="
Content-Transfer-Encoding: 8bit
X-BlackCat-Spam-Score: 0
Message-ID-Hash: 7UAQDX4QAZ4TUAKC57VIR2YTGES3EQSR
X-Message-ID-Hash: 7UAQDX4QAZ4TUAKC57VIR2YTGES3EQSR
X-MailFrom: csp@csperkins.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-panrg.irtf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: panrg@irtf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [PANRG] Re: A discussion Tuesday about the future of PANRG
List-Id: " Path Aware Networking (Proposed) Research Group discussion list" <panrg.irtf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/panrg/qrsUFDpxW1O23LfCvRfPGwR1V1A>
List-Archive: <https://mailarchive.ietf.org/arch/browse/panrg>
List-Help: <mailto:panrg-request@irtf.org?subject=help>
List-Owner: <mailto:panrg-owner@irtf.org>
List-Post: <mailto:panrg@irtf.org>
List-Subscribe: <mailto:panrg-join@irtf.org>
List-Unsubscribe: <mailto:panrg-leave@irtf.org>
Hi, Following-up on my comment in the PANRG meeting: broadening the scope of what information is exchanged between the network and endpoints raises the question of what is the scope of the information that can be exchanged? The IETF has tended to limit that to signalling properties of the traffic, e.g., QoS requirements, but it’s also possible to provide information about the specific application used or more broadly. I’d suggest that any rechartering of the group should keep the focus quite narrowly scoped. Cheers, Colin On 19 Jul 2026, at 11:58, Brian Trammell (IETF) wrote: > Greetings, all, > > I’d like to frame the last agenda item for our meeting Tuesday by > reflecting on what > PANRG is and has become, and to ask what we want to do in the future, > > PANRG was chartered nine years ago to create a venue to discuss the > various work > happening on the broader theme of endpoint path awareness around the > IETF. We've > published guidance on things that have already been tried and found to > work > less than perfectly in this space, elaborated a set of open questions > in > path aware networking to guide those discussions, and started on a > formalization > of what a path is and what properties it can have from the endpoint's > perspective. We've also provided a venue to discuss path-aware > reimaginings of > the whole Internet, as well as more targeted cooperative approaches. > > In reviewing how the research and standardization environment > surrounding its > open questions has changed, we see that the various requirements > leading to > work in path aware networks, and routing/transportation cooperative > approaches > more generally, continue to drive work in this space. Some of this > work (e.g. SCONE, > CATS) is standards-ready, but an early stage venue to discuss bringing > research > work toward standards, and bringing standards people to the research, > remains useful > in this area. > > PANRG was chartered to discuss one set of answers to a broader > question: > > **What should endpoints and networks tell each other, and how should > each act on it?** > > SCION, which we have spent much time discussing, is an architecture > that provides > one way of implementing that pattern, a useful testbed for > experimenting with path > aware concepts, and shows that the concept works in real production > networks. > > However, we've noticed that, increasingly, what brings people to PANRG > to speak > is more a focus on the general question, and not the specifics > originally > assumed by our charter. Many of the open questions posed in RFC 9217 > apply to > any approach where endpoints and networks communicate with each other, > and that > general question does not have a home, is not obviously shaped like a > standards > deliverable, and continues to drive a few lines of research, both > industrial and > academic. > > So I’d like to start a discussion about our future with a proposal > to slightly reframe > PANRG's charter to focus on the this question: > > **What should endpoints and networks tell each other, and how should > each act on > it?** > > The RG's two jobs are unchanged: a bridge between the research and > standards > communities, and a place to discuss ideas that are not yet ready for > standardization. > > We would **not** propose to rename the group, and we are **not** > proposing to > take on work that belongs in an existing working group. The point is > to make > explicit that the RG's scope is the endpoint/network interface > broadly, of which > path selection is one part. > > Do we have this right? Is *what should endpoints and networks tell > each other, > and how should each act on it* the right center of gravity for the RG? > Are there > useful restrictions on the proposed scope beyond this? Are there > research > communities doing interesting work in this space that haven't been > represented > here that we should reach out to for future meetings? > > Many thanks, and I look forward to discussion in Tuesday! > > Cheers, > > Brian > _______________________________________________ > Panrg mailing list -- panrg@irtf.org > To unsubscribe send an email to panrg-leave@irtf.org
- [PANRG] A discussion Tuesday about the future of … Brian Trammell (IETF)
- [PANRG] Re: A discussion Tuesday about the future… Colin Perkins