Re: [auth48] [IAB] AUTH48: RFC-to-be 9280 <draft-iab-rfcefdp-rfced-model-13> for your review

Colin Perkins <csp@csperkins.org> Thu, 23 June 2022 21:32 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: auth48archive@ietfa.amsl.com
Delivered-To: auth48archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C395AC15A72A; Thu, 23 Jun 2022 14:32:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=csperkins.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 KSX-l5NZU2Yb; Thu, 23 Jun 2022 14:32:01 -0700 (PDT)
Received: from mx1.mythic-beasts.com (mx1.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3BA9C15A741; Thu, 23 Jun 2022 14:32:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=csperkins.org; s=mythic-beasts-k1; h=Date:Subject:To:From; bh=95Llpa8K/gFHW0B2xNC4c0/MJywYG2NCx/OyiYHrQVc=; b=sOyeKumN92seAOMg8kVZpNu7L0 MhB1+STKvurRQU/tu5Nk/kJ2czkJ30bPLlYhL+kF3oJ8bK3grQKDReAaX9Avz4dCdvO8RrshribGn ySAnhh2N3Dy6CDGqelPGfMy+cDjJF6s5txsbtitdaxqFyO6SWfnlVVfnEVe9dwR7nFOll5EG328lw U5oqHD9i1nNc2cGaxF82fL8uvaFD4k6u7UfQCRkm9D/7qgoJi7Y93GFLRaNGQBh1Saag7gWjcdbuF v+WF/fzrjhUfNzROCzTnR/P7F5dK0eVdsbFYe+X+eOzMsqyQ0EHUFQL9Pqus9iKpFYUL7/lsrr4w3 iMnXoAMQ==;
Received: from [81.187.2.149] (port=44180 helo=[172.28.128.1]) by mailhub-cam-d.mythic-beasts.com with esmtpsa (TLS1.2) tls TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <csp@csperkins.org>) id 1o4UQd-001qVK-Ga; Thu, 23 Jun 2022 22:31:56 +0100
From: Colin Perkins <csp@csperkins.org>
To: Peter Saint-Andre <stpeter@stpeter.im>
Cc: Rebecca VanRheenen <rvanrheenen@amsl.com>, RFC Editor <rfc-editor@rfc-editor.org>, Brian Rosen <br@brianrosen.net>, iab@ietf.org, auth48archive@rfc-editor.org, Eliot Lear <lear@lear.ch>
Date: Thu, 23 Jun 2022 22:31:40 +0100
X-Mailer: MailMate (1.14r5899)
Message-ID: <EB629C93-BD3D-4A67-9014-6EFE6A9FE204@csperkins.org>
In-Reply-To: <59e1bf26-f313-00a7-801d-3a87e40e56a3@stpeter.im>
References: <20220618035859.D4FE015FF6A@rfcpa.amsl.com> <10597e60-58aa-41bb-cfaa-6a88c9843759@stpeter.im> <BA94ED3E-C9F7-4331-A1C6-6AB9E0D8283D@amsl.com> <7f890736-efd0-1e6b-670b-cb64a75785e4@stpeter.im> <83987AE0-5F7F-45AA-98A5-2EBE2DD22E4E@amsl.com> <e2924146-94b0-2294-0990-74e876f86f8b@stpeter.im> <E1C61C97-6D45-41E1-AFC9-2CC65A8EBA84@amsl.com> <59e1bf26-f313-00a7-801d-3a87e40e56a3@stpeter.im>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-BlackCat-Spam-Score: 0
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/VWBkhigbd-KJypvNIbooq3RU3pI>
Subject: Re: [auth48] [IAB] AUTH48: RFC-to-be 9280 <draft-iab-rfcefdp-rfced-model-13> for your review
X-BeenThere: auth48archive@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Archiving AUTH48 exchanges between the RFC Production Center, the authors, and other related parties" <auth48archive.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/auth48archive/>
List-Post: <mailto:auth48archive@rfc-editor.org>
List-Help: <mailto:auth48archive-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jun 2022 21:32:06 -0000


On 23 Jun 2022, at 19:33, Peter Saint-Andre wrote:

> Hi Rebecca,
>
> Thanks for your work on this important document.
>
> Here are a few proposed edits. I would like the Program chairs and the IAB to make sure they are comfortable with these changes before you make these edits.
...
> SECTION 3.1.2.3
>
> The following two sentences are in potential conflict:
>
> 3.1.2.3
>
>    The appointing bodies, i.e., the stream approving bodies (IESG, IAB,
>    IRTF Chair, and ISE), shall determine their own processes for
>    appointing RSAB members (note that processes related to the RSCE are
>    described in Section 5).
>
> 4.4
>
>    *  If there is a conflict with a policy for a particular stream, to
>       help achieve a resolution, the RPC should consult with the
>       relevant stream approving body (such as the IESG or IRSG) and
>       other representatives of the relevant stream as appropriate.
>
> In 3.1.2.3, the IRTF Chair is described as a stream approving body (!), whereas in 4.4 the IRSG is described as a stream approving body. I suggest that we remove mention of stream approving bodies in 3.1.2.3 and make the following change.
>
> OLD
>
>    The appointing bodies, i.e., the stream approving bodies (IESG, IAB,
>    IRTF Chair, and ISE), shall determine their own processes for
>    appointing RSAB members (note that processes related to the RSCE are
>    described in Section 5).
>
> NEW
>
>    The appointing bodies (i.e., IESG, IAB, IRTF Chair, and ISE), shall
>    determine their own processes for appointing RSAB members (note that
>    processes related to the RSCE are described in Section 5).

I agree with this change.

For the IESG and IAB, the same group acts as appointing body for the RSAB and as the stream approving body. That’s not the case for the IRTF, where the appointing body for the RSAB is the IRTF Chair but the stream approving body is the IRSG.

The current text in Section 4.4 looks okay to me. I don’t object to Eliot’s proposed change there, but I also don’t think it’s necessary.

Colin