IETF Logo Mail Archive

Re: [Can] Clean copy CAN charter updated

Jari Arkko <jari.arkko@piuha.net> Thu, 16 February 2023 20:50 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: can@ietfa.amsl.com
Delivered-To: can@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 336FCC169515 for <can@ietfa.amsl.com>; Thu, 16 Feb 2023 12:50:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.104
X-Spam-Level:
X-Spam-Status: No, score=-1.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 A5UpbzksAKWA for <can@ietfa.amsl.com>; Thu, 16 Feb 2023 12:50:28 -0800 (PST)
Received: from p130.piuha.net (unknown [IPv6:2001:14b8:1829::130]) by ietfa.amsl.com (Postfix) with ESMTP id EDD73C15C533 for <can@ietf.org>; Thu, 16 Feb 2023 12:50:27 -0800 (PST)
Received: from smtpclient.apple (ppp-94-66-57-43.home.otenet.gr [94.66.57.43]) by p130.piuha.net (Postfix) with ESMTPSA id 68276660133; Thu, 16 Feb 2023 22:50:22 +0200 (EET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <023701d93f1d$a7dde940$f799bbc0$@olddog.co.uk>
Date: Thu, 16 Feb 2023 22:50:19 +0200
Cc: can@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <BE9A49B7-BFF9-4AD1-BC2F-85EFA20B7E03@piuha.net>
References: <023701d93f1d$a7dde940$f799bbc0$@olddog.co.uk>
To: Adrian Farrel <adrian@olddog.co.uk>, jgs@juniper.net
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/can/YzGs0JLYTlwlPzS7e7x6qyPrUsQ>
Subject: Re: [Can] Clean copy CAN charter updated
X-BeenThere: can@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: CAN- Computing-Aware Networking <can.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/can>, <mailto:can-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/can/>
List-Post: <mailto:can@ietf.org>
List-Help: <mailto:can-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/can>, <mailto:can-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2023 20:50:30 -0000

Adrian and all:

I reviewed your charter version. I think it looks quite reasonable. I liked the framing of the three first paragraphs in particular. It is great that the co-interest from two areas is recognized in the charter. The fifth paragraph nicely makes the model concrete by focusing on overlays. That assumption (and declaring underlay service-awareness out of scope) lets us avoid a lot of issues! 

(As an aside, and this is not a criticism of this charter, but IETF charter deliverables tend to be a bit waterfall style from problems to architectures to solutions. Wondering if there’s room for more incremental small-improvement-at-a-time style. But maybe that’s for the hackathons.)

Jari

v2.23.0 | Report a Bug | By Email