From: Suresh Krishnan <suresh.krishnan@gmail.com>
To: bpf@ietf.org, bpf <bpf@vger.kernel.org>
Subject: Re: [Bpf] Call for WG adoption: draft-thaler-bpf-isa-02
Date: Wed, 18 Oct 2023 21:07:44 -0400 [thread overview]
Message-ID: <1C8A6FD1-1724-4AD3-A6C9-CA2C427FD32E@gmail.com> (raw)
Message-ID: <20231019010744.DZj1UGmK9wfUWIJ4WDVPwy96twEOWYBtyvJ-LRvErzQ@z> (raw)
In-Reply-To: <CA+MHpBoHdG4ptYsdeHaEUNqmyPYYgavWUpMbVW5zzOzUoLUJMw@mail.gmail.com>
Hi all,
This document has now been adopted as a WG item. Dave, please submit the next revision as draft-ietf-bpf-isa-00.
Thanks
Suresh & David
> On Sep 29, 2023, at 10:28 AM, Suresh Krishnan <suresh.krishnan@gmail.com> wrote:
>
> Hi all,
> This draft has been presented at the bpf meetings and has received
> significant feedback both at the meetings and on/off list. Dave has
> published a new revision that addresses all the comments, and has
> requested WG adoption of the draft. This call is being initiated to
> determine whether there is WG consensus towards adoption of
> draft-thaler-bpf-isa-02 as a bpf WG draft. This draft is expected to
> address the WG deliverable
>
> "[PS] the BPF instruction set architecture (ISA) that defines the
> instructions and low-level virtual machine for BPF programs"
>
> The draft is available at
>
> (HTML) https://datatracker.ietf.org/doc/html/draft-thaler-bpf-isa-02
> (Plaintext) https://www.ietf.org/archive/id/draft-thaler-bpf-isa-02.txt
>
> Please state whether or not you're in favor of the adoption by
> replying to this email. If you are not in favor, please also state
> your objections in your response. This adoption call will conclude on
> Friday October 13 2023 (AoE) .
>
> Regards
> Suresh & David
--
Bpf mailing list
Bpf@ietf.org
https://www.ietf.org/mailman/listinfo/bpf
next prev parent reply other threads:[~2023-10-19 1:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 14:28 Call for WG adoption: draft-thaler-bpf-isa-02 Suresh Krishnan
2023-09-29 14:28 ` [Bpf] " Suresh Krishnan
2023-10-19 1:07 ` Suresh Krishnan [this message]
2023-10-19 1:07 ` Suresh Krishnan
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=1C8A6FD1-1724-4AD3-A6C9-CA2C427FD32E@gmail.com \
--to=suresh.krishnan@gmail.com \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).