Re: [Rfced-future] Issue 143: RSAB mailing list archives
Eliot Lear <lear@lear.ch> Tue, 11 January 2022 07:33 UTC
Return-Path: <lear@lear.ch>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0EFE3A1C37 for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 23:33:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.803
X-Spam-Level:
X-Spam-Status: No, score=-2.803 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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.714, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=lear.ch
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11BU_MHP62vS for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 23:33:53 -0800 (PST)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF3D83A1C39 for <rfced-future@iab.org>; Mon, 10 Jan 2022 23:33:52 -0800 (PST)
Received: from [IPV6:2001:420:c0c0:1011::3] ([IPv6:2001:420:c0c0:1011:0:0:0:3]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 20B7Xmo9127642 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Tue, 11 Jan 2022 08:33:49 +0100
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1641886429; bh=JwI/u7Wri3gza6aaR7AooGDZkyW7gG7UolAPuD+wOXY=; h=Date:To:Cc:References:From:Subject:In-Reply-To:From; b=SisF9EG6pB95FTxKXCAv5sACuAZE7D46n0OZ8OZPIBI34kKNe60wVPZWnohFp9XvY bUVrF3XRAHVfliOP11GcBcxkh6C34aFysHMgVXk8QKYRnE1+7J25Zj/F7WWEsYCvmt t/plR3hIRIHVt6gd5pH5jU3INGl4Jpmb4NjhDC7k=
Message-ID: <bcbf4eb8-67e3-63aa-2e70-88cb74d8d3b0@lear.ch>
Date: Tue, 11 Jan 2022 08:33:47 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.1
Content-Language: en-US
To: Lars Eggert <lars@eggert.org>
Cc: rfced-future@iab.org
References: <3e1fe494-c86b-5181-6afb-128b05fec882@stpeter.im> <48043fa8-eb37-2f97-942c-500492664bb0@gmail.com> <e708572f-b678-f60c-ab84-c48e039926a7@stpeter.im> <95dd0e5a-c5f4-09d1-98b4-327978e21316@gmail.com> <1846FA24-9631-4622-9EE6-B0D4A2B505C3@kuehlewind.net> <CANk3-NCkDCqz2m5X0aLGXKYttZ3U8LK-YppsyHYK6TT0RDYgHw@mail.gmail.com> <8a648870-03ec-b4c2-426b-357022e94c05@cs.tcd.ie> <548366C9-4581-4D4F-8638-7A5F7B754D13@eggert.org> <CANk3-NA1+-46Q0QkV_cr7SNB_nKU3+vEqqK7dMtwmf12Efyaog@mail.gmail.com> <203C6967-5A21-4100-8A5A-EB64E67B33EC@eggert.org> <CANk3-NAVzQ3MGd21mBTTW31DZPtipDa6xyE4LLhUdxi1fT60sw@mail.gmail.com> <88E57876-7139-46C7-A150-4A52319F2014@eggert.org>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <88E57876-7139-46C7-A150-4A52319F2014@eggert.org>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------8ZFWy2cpaVaEvgNkDa9BS9jm"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/LpJSNQh2WZnUsR3KcQhVuYeksSs>
Subject: Re: [Rfced-future] Issue 143: RSAB mailing list archives
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jan 2022 07:33:58 -0000
Lars, Adding to what Martin just wrote... On 11.01.22 08:10, Lars Eggert wrote: > so maybe my understanding about the new model is off, but: I have > understood the proposed structure to be such that the RSAB really > doesn't have a lot of leeway when it comes to not approving proposals > by the RSWG, especially not without immediately needing to take the > discussion back to the RSWG in such cases. In other words, I'm > struggling to come up with examples where significant discussions > would happen inside the RSAB only. In general, yes conversation to happen in the RSWG, but there reasons why the RSAB members might discuss matters among themselves, particularly when it comes to implementation of policies. For example, “I believe I am running into an issue with the RPC over how they are implementing this new tool- we don't have permissions or the states we need”, so that they can reflect that back to the RPC. That may not even entail any changes to policy, but simply to implementation. If someone later sees this discussion and decides that the RSAB has missed that indeed there is a policy issue, they can raise it in the RSWG, but only if the list is publicly archived. That is- having the list archived publicly can help keep the community informed about policy implementation. While there is indeed a trust motivation, as you have mentioned, and having things open and transparent *mig**ht *help with that, what we cannot do is stop all potential bad behavior. We should be careful just how far we go. Eliot
- [Rfced-future] Issue 143: RSAB mailing list archi… Peter Saint-Andre
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Salz, Rich
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Eric Rescorla
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Michael StJohns
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Salz, Rich
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Brian E Carpenter
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Peter Saint-Andre
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Brian E Carpenter
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Mirja Kuehlewind
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Lars Eggert
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Wes Hardaker
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Brian E Carpenter
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Stephen Farrell
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Lars Eggert
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Martin Thomson
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Salz, Rich
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Wes Hardaker
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Brian E Carpenter
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Lars Eggert
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Eliot Lear
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Wes Hardaker
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Lars Eggert
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Martin J. Dürst
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Eliot Lear
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Mirja Kuehlewind
- Re: [Rfced-future] Issue 143: RSAB mailing list a… Peter Saint-Andre
- Re: [Rfced-future] Issue 143: RSAB mailing list a… John C Klensin