Re: [Bpf] Roman Danyliw's No Objection on charter-ietf-bpf-00-04: (with COMMENT)

Erik Kline <ek.ietf@gmail.com> Thu, 22 June 2023 00:05 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 EA662C14CE33; Wed, 21 Jun 2023 17:05:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 R0U5Gy4ybdMI; Wed, 21 Jun 2023 17:05:55 -0700 (PDT)
Received: from mail-vk1-xa35.google.com (mail-vk1-xa35.google.com [IPv6:2607:f8b0:4864:20::a35]) (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 1E637C14CE2E; Wed, 21 Jun 2023 17:05:55 -0700 (PDT)
Received: by mail-vk1-xa35.google.com with SMTP id 71dfb90a1353d-4718bc88afdso74797e0c.0; Wed, 21 Jun 2023 17:05:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687392354; x=1689984354; 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=2F8IkjAiBobu9q1pc+6HZtnQbrsiCHI5edV7SYT9R50=; b=X2i+QYtVhg6/qeq4MwNv21qhmC4hR9fwZUc3CMmSi7CQC63UpzIUY1qbzg1SWmzuKF HO0Na/6UqBW5HyUsq9+kNSW22MTExrvJSNPklCnZapKSBA5yAHwkEsbrp01KmtkQFJnK vVFVmyZiXraS0OuzG++HOtbx9MFl/r4PSg7P0zSaJdmhaqPABgqWSa4i3fSX9uWKwBUO bP41toxc4oqo0KsywTWYLdIDRAtR0y/WW//PO+6Sbh26Ow6XzpB0vIW8/O5/6IZAouWi EUtdwoPiUgZX+lTSU2CW2Fpufx/uKMiLVjfIAT33Gr16Dw7SnxMBmmlZcJMHm7OUXphi 35kw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687392354; x=1689984354; 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=2F8IkjAiBobu9q1pc+6HZtnQbrsiCHI5edV7SYT9R50=; b=UfHrTs3ly7ZMzmQFbBT4Kfbj71zPswL3T2jvUOVlSbmGwfFQqTl+GTMrRaKJj57D+l DmmF2zkB9efeW22D9oX6uStU1qfwithnGu1XvlB351Fv0YvRKeXD+EduMb2FZ6PK8I8C AuM47klLFczQu2d+i6AohM62ocly48i7EdBvFEBkXI80jg3Xv4/Yr/MNHUA+NIw/LTKF jwDMv0lQbsgOX6YFJvbdhQYOV2NwlxAUBqwPC3CY3PTg4G+XKh5ROyAF6IwZ366QheZD Ulb5M54xwkFyHuWPMpHF1H/qoA4s53sWNa2X4nX/EYHHOWjwvnuNxjejdUJPaa+6fnoa 7EOA==
X-Gm-Message-State: AC+VfDzLI7AMXBy5+HyUJ+r7zBHfwD6AxadFjQ5eA0zcaTInsIOaEBNa 6P1a+B4UI4c75fPr9qWj+UcJkkiAWoRxSzUv3v6eO9XF
X-Google-Smtp-Source: ACHHUZ5J05+WBC3Kz8hxKHoKgUeT3ga7lvc/h3IbSb5ojkPFzn1vUlEgdOGk0WQCEF/Rs4pWJpQvg7i8F/r5UGd5zzE=
X-Received: by 2002:a1f:3f07:0:b0:440:4946:fac with SMTP id m7-20020a1f3f07000000b0044049460facmr5115291vka.4.1687392353972; Wed, 21 Jun 2023 17:05:53 -0700 (PDT)
MIME-Version: 1.0
References: <168735869689.62925.2170507560905258435@ietfa.amsl.com>
In-Reply-To: <168735869689.62925.2170507560905258435@ietfa.amsl.com>
From: Erik Kline <ek.ietf@gmail.com>
Date: Wed, 21 Jun 2023 17:05:42 -0700
Message-ID: <CAMGpriWwy2PSFiDAcEtE+VGmaErG_t-pUfowhBbz_h-AA4-UOQ@mail.gmail.com>
To: Roman Danyliw <rdd@cert.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/hkrqrFziRllI9-ohIMOBaU0-0lM>
Subject: Re: [Bpf] Roman Danyliw's No Objection on charter-ietf-bpf-00-04: (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: Thu, 22 Jun 2023 00:05:59 -0000

Thanks.  Murray had similar feedback the first time around.  My
personal preference is to let the chairs sort out reasonable time
estimates for the charter-defined milestones, though I've taken a stab
at the first big objective.

This working group is necessarily a bit different, at least at the
outset: there's going to be some period where the two communities
figure out a working style (some source text edited in the kernel
tree, some other text in other repos, etc -- the combined output, of
course, in the datatracker).  I wanted to give time for this to shake
out.

On Wed, Jun 21, 2023 at 7:44 AM Roman Danyliw via Datatracker
<noreply@ietf.org> wrote:
>
> Roman Danyliw has entered the following ballot position for
> charter-ietf-bpf-00-04: 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:
> ----------------------------------------------------------------------
>
> There are a number of proposed document which don't appear to corresponding
> milestones.  Consider if they should be enumerated.
>
>
>