From: David Vernet <void@manifault.com>
To: lsf-pc@lists.linux-foundation.org
Cc: bpf@vger.kernel.org, bpf@ietf.org, dthaler1968@googlemail.com,
alexei.starovoitov@gmail.com, hch@infradead.org
Subject: [LSF/MM/BPF TOPIC] BPF IETF Standardization
Date: Tue, 2 Jan 2024 17:01:59 -0600 [thread overview]
Message-ID: <20240102230159.GA1682@maniforge> (raw)
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
Hello,
I would like to give an update on the latest regarding the BPF IETF
standardization efforts, and to discuss what I believe will be the long
term standardization roadmap. We're making good headway on standardizing
the BPF ISA, but there's a lot more that we'll eventually need to
formalize and standardize in the BPF ecosystem, and I think it would be
beneficial to discuss and hear folks' perspective on things.
Thanks,
David
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: David Vernet <void@manifault.com>
To: lsf-pc@lists.linux-foundation.org
Cc: bpf@vger.kernel.org, bpf@ietf.org, dthaler1968@googlemail.com,
alexei.starovoitov@gmail.com, hch@infradead.org
Subject: [Bpf] [LSF/MM/BPF TOPIC] BPF IETF Standardization
Date: Tue, 2 Jan 2024 17:01:59 -0600 [thread overview]
Message-ID: <20240102230159.GA1682@maniforge> (raw)
Message-ID: <20240102230159.aardznWvYBzBmEnK3PV6lgaKs2THmw-JcPbwqt2Hy8c@z> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 435 bytes --]
Hello,
I would like to give an update on the latest regarding the BPF IETF
standardization efforts, and to discuss what I believe will be the long
term standardization roadmap. We're making good headway on standardizing
the BPF ISA, but there's a lot more that we'll eventually need to
formalize and standardize in the BPF ecosystem, and I think it would be
beneficial to discuss and hear folks' perspective on things.
Thanks,
David
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 76 bytes --]
--
Bpf mailing list
Bpf@ietf.org
https://www.ietf.org/mailman/listinfo/bpf
next reply other threads:[~2024-01-02 23:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 23:01 David Vernet [this message]
2024-01-02 23:01 ` [Bpf] [LSF/MM/BPF TOPIC] BPF IETF Standardization David Vernet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240102230159.GA1682@maniforge \
--to=void@manifault.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=dthaler1968@googlemail.com \
--cc=hch@infradead.org \
--cc=lsf-pc@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox