Re: [Bpf] Lars Eggert's No Objection on charter-ietf-bpf-00-03: (with COMMENT)

Erik Kline <ek.ietf@gmail.com> Sun, 28 May 2023 04:29 UTC

Return-Path: <ek.ietf@gmail.com>
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 CC910C14F73F; Sat, 27 May 2023 21:29:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.096 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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=gmail.com
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 klEkgft9qyFQ; Sat, 27 May 2023 21:29:42 -0700 (PDT)
Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 293A2C14F6EC; Sat, 27 May 2023 21:29:42 -0700 (PDT)
Received: by mail-vs1-xe29.google.com with SMTP id ada2fe7eead31-4396800545aso2525083137.1; Sat, 27 May 2023 21:29:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685248181; x=1687840181; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=68+hhEIbX0IUxWKCMlYc3+I32xiHAyzdZ5ns1+d3Izc=; b=PPyoKhNKteuiEK4Mgy28+7puruwrFtfSOPJe0QEmeJXYUaMuao6PpXNuQvDvoJxKIi mZ2qzOocux0PSUHWVeo3JWobMpzsC9Q3W6iseUfD1Ux5K67eW0Hm7O2PvKL6/CwDtS7M NugONa08Fe8HJpC085gTNJBQX4zu3x5nIFAZIEpIEGm7zctDo+uMm27hizaPg91oW12v 7y9YueiFPXiW2uZAzIdJ67E/gwtGmAA/Omu0UKnz7UMBAE0L70k8s24uYjhAeNGXywNp vFc9aqSE1dtU8Tvc0p13VJRKjqlPpCTHQ4VVvyuOOAYoUpGW9mUCRa3w9cK4Usi8tfDc 6nVg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685248181; x=1687840181; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=68+hhEIbX0IUxWKCMlYc3+I32xiHAyzdZ5ns1+d3Izc=; b=WK17NYdLWtb3KNe/1RrLNJeiKg7VGPovo/lcxHkT87jFMLvnwMM/uqJZTyNh05qZ07 k3GRQGNFvDQsCE9ZEOwssrFktHb4d3CYeVkC1PSrPH1jW7kfdSFogQb+EKRwaHcCMJNy FsqZHihRzdbKiBfZTjROYWIBqP1X5IIBLr/iKbsAcsWNe2oso15Y47Jvg2QeRE9VmfXv jMDEBoXtdJzKLry+NE+z15T9NI3A3UAUUYKu9uj5kE/RIoS4AmTlJ8OwyAgp4Bt5DY4b c3xR1oOflxVB3n88LKKlLRj7AybSzJT0QDOcrVvj0GlbbYqhvCL1cHDl5Vkng+5CsRkC xgzA==
X-Gm-Message-State: AC+VfDxQ3TzB5ARBOGSwKNhSiww1Fkdp8YUeAPZPnkrSLijiutIB6mFJ qMG5y4gWbX0Oo8QLlDlbJQ8Y1RZcxoV+2k1dJ9Hve2Jv
X-Google-Smtp-Source: ACHHUZ7j6ONuQkUOki9WSlxMR5SDnsf9BsLOeiwKbv7H8VhY7Q97Z7xKCqqvhKvs7hX7FAZ743atqtXDCEAhMFvd9i4=
X-Received: by 2002:a05:6102:508a:b0:437:d9e9:ebe5 with SMTP id bl10-20020a056102508a00b00437d9e9ebe5mr1535349vsb.10.1685248180764; Sat, 27 May 2023 21:29:40 -0700 (PDT)
MIME-Version: 1.0
References: <168500511284.50925.18281220900779690232@ietfa.amsl.com>
In-Reply-To: <168500511284.50925.18281220900779690232@ietfa.amsl.com>
From: Erik Kline <ek.ietf@gmail.com>
Date: Sat, 27 May 2023 21:29:29 -0700
Message-ID: <CAMGpriV=g=nMyJA89Vmm0wnNf5AKYo+25b1FadA4jyxRwN4AFQ@mail.gmail.com>
To: Lars Eggert <lars@eggert.org>
Cc: The IESG <iesg@ietf.org>, bpf-chairs@ietf.org, bpf@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/bpf/pN357LOFg42KujOccaDVv6lPofk>
Subject: Re: [Bpf] Lars Eggert's No Objection on charter-ietf-bpf-00-03: (with COMMENT)
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: Sun, 28 May 2023 04:29:45 -0000

On Thu, May 25, 2023 at 1:58 AM Lars Eggert via Datatracker
<noreply@ietf.org> wrote:
>
> Lars Eggert has entered the following ballot position for
> charter-ietf-bpf-00-03: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/charter-ietf-bpf/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> # GEN AD review of charter-ietf-bpf-00-03
>
> CC @larseggert
>
> ## Comments
>
> ### "BPF", paragraph 4
> ```
>   The working group shall not adopt new work until these
>   documents have progressed to working group last call.
> ```
> Why WG LC and not IESG approval as usual?

Seemed more expedient, I suppose, but: changed to IESG approval.

> ### Inclusive language
>
> Found terminology that should be reviewed for inclusivity; see
> https://www.rfc-editor.org/part2/#inclusive_language for background and more
> guidance:
>
>  * Term `native`; alternatives might be `built-in`, `fundamental`, `ingrained`,
>    `intrinsic`, `original`

None of these terms seem to improve readability.

> ## Nits
>
> All comments below are about very minor potential issues that you may choose to
> address in some way - or ignore - as you see fit. Some were flagged by
> automated tools (via https://github.com/larseggert/ietf-reviewtool) so there
> will likely be some false positives. There is no need to let me know what you
> did with these suggestions.
>
> ### Typos
>
> #### "BPF", paragraph 4
> ```
> - The bpf working group is initially tasked with documenting the existing
> -     ^^^
> + The BPF working group is initially tasked with documenting the existing
> +     ^^^
> ```
>
> #### "BPF", paragraph 4
> ```
> - documents have progressed to working group last call.
> -                 ^^^^ ^^
> + documents have completed working group last call.
> +                +++ ^ ^
> ```
>
> #### "BPF", paragraph 15
> ```
> - The bpf working group shall actively engage the eBPF Foundation
> -     ^^^
> + The BPF working group shall actively engage the eBPF Foundation
> +     ^^^
> ```
>
> #### "BPF", paragraph 16
> ```
> - eBPF that are useful to the wider internet community and not operating
> -                                   ^
> - or otherwise platform specific.
> -                      ^
> + eBPF that are useful to the wider Internet community and not operating-system
> +                                   ^                                   +++++++
> + or otherwise platform-specific.
> +                      ^
> ```

Done.

> ## Notes
>
> This review is in the ["IETF Comments" Markdown format][ICMF], You can use the
> [`ietf-comments` tool][ICT] to automatically convert this review into
> individual GitHub issues. Review generated by the [`ietf-reviewtool`][IRT].
>
> [ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md
> [ICT]: https://github.com/mnot/ietf-comments
> [IRT]: https://github.com/larseggert/ietf-reviewtool
>
>
>