IETF Logo Mail Archive

Re: [Bpf] IETF BPF working group draft charter

Christoph Hellwig <hch@infradead.org> Wed, 31 May 2023 03:47 UTC

Return-Path: <BATV+b81a8c9a6d22e8bb2302+7220+infradead.org+hch@bombadil.srs.infradead.org>
X-Original-To: bpf@ietfa.amsl.com
Delivered-To: bpf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0814DC14CE40 for <bpf@ietfa.amsl.com>; Tue, 30 May 2023 20:47:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.086
X-Spam-Level:
X-Spam-Status: No, score=-7.086 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, 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 (2048-bit key) header.d=infradead.org
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 pYEbpbkcmAIh for <bpf@ietfa.amsl.com>; Tue, 30 May 2023 20:47:43 -0700 (PDT)
Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:3::133]) (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 46BEDC14CE33 for <bpf@ietf.org>; Tue, 30 May 2023 20:47:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=In-Reply-To:Content-Type:MIME-Version :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=zVbhNCZE0akM4TMQAplqYgu5nBRjcZJqi1ar0ws/0o8=; b=F67HbLSa0QsRlettVzdXy1/fnw xNjGV0yAOm6x1OUONrpXWwLJ3zvTMQdUpQmfQE6I2CWym/UPev4rtXdch0lqXdPWYZD03P30l7ce+ norAd6fSsqjinmG+EedzE4HVnyn0BaurGtxyd3y3XayrvJDvicRYfW0rvqohlVnY+0Sp7KOzY8F1T iVnUK0KjHEQreHb04emYkALj2jFZCSNKfLAw7kmjk34L5Z2ReLtXUzu3+y8c6AuY7BzXXEoAeTZ5V +fQLZzG0/K1NMhUb+j0ye3mnABbXt0kkObbZHsphTex0KBqgA9X5RMsupfrVOXuOe0kUjdGdxB558 MlsoJukQ==;
Received: from hch by bombadil.infradead.org with local (Exim 4.96 #2 (Red Hat Linux)) id 1q4Co7-00FwmS-2B; Wed, 31 May 2023 03:47:31 +0000
Date: Tue, 30 May 2023 20:47:31 -0700
From: Christoph Hellwig <hch@infradead.org>
To: Dave Thaler <dthaler@microsoft.com>
Cc: David Vernet <void@manifault.com>, "Jose E. Marchesi" <jemarch@gnu.org>, Christoph Hellwig <hch@infradead.org>, Michael Richardson <mcr+ietf@sandelman.ca>, "bpf@ietf.org" <bpf@ietf.org>, bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>, Erik Kline <ek.ietf@gmail.com>, "Suresh Krishnan (sureshk)" <sureshk@cisco.com>
Message-ID: <ZHbDU6E6CmGT5wD+@infradead.org>
References: <87r0rdy26o.fsf@gnu.org> <PH7PR21MB3878B869D69FD35FA718AF5DA37FA@PH7PR21MB3878.namprd21.prod.outlook.com> <20230523163200.GD20100@maniforge> <18272.1684864698@localhost> <20230523202827.GA33347@maniforge> <ZG8R3JgOPHo7xn61@infradead.org> <87y1lclnui.fsf@gnu.org> <PH7PR21MB38781A9FBC44A275FDF3D5F6A347A@PH7PR21MB3878.namprd21.prod.outlook.com> <20230526165511.GA1209625@maniforge> <PH7PR21MB3878E80B01C2AA8273131D7CA347A@PH7PR21MB3878.namprd21.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <PH7PR21MB3878E80B01C2AA8273131D7CA347A@PH7PR21MB3878.namprd21.prod.outlook.com>
X-SRS-Rewrite: SMTP reverse-path rewritten from <hch@infradead.org> by bombadil.infradead.org. See http://www.infradead.org/rpr.html
Archived-At: <https://mailarchive.ietf.org/arch/msg/bpf/3Oio6dAedzt3MWOtbF3_Xrws6W0>
Subject: Re: [Bpf] IETF BPF working group draft charter
X-BeenThere: bpf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion of BPF/eBPF standardization efforts within the IETF <bpf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bpf>, <mailto:bpf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bpf/>
List-Post: <mailto:bpf@ietf.org>
List-Help: <mailto:bpf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bpf>, <mailto:bpf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 May 2023 03:49:12 -0000

On Fri, May 26, 2023 at 05:01:57PM +0000, Dave Thaler wrote:
> In an email last week to the list I mentioned Informational as a possibility.
> I don't have a strong preference, but I have a weak preference for Proposed
> Standard status.
> 
> As an implementer, I would want to make sure that ebpf-for-windows,
> PREVAIL, and uBPF all do the same thing, ideally matching Linux for everything
> the former projects support, to allow using consistent tooling.

This would be even more important for any of the potential NVMe use
cases.  Compared to even ebpf-for-windows it is a fairly niche use case,
and the last thing we'd need was our own ABI and toolchain.

v2.46.0 | Report a Bug | By Email | System Status