Re: [Rfced-future] Issue 143: RSAB mailing list archives
John C Klensin <john@jck.com> Wed, 12 January 2022 06:40 UTC
Return-Path: <john@jck.com>
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 5D1043A0965 for <rfced-future@ietfa.amsl.com>; Tue, 11 Jan 2022 22:40:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 KJoRSqGN40Uz for <rfced-future@ietfa.amsl.com>; Tue, 11 Jan 2022 22:40:14 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97B083A0961 for <rfced-future@iab.org>; Tue, 11 Jan 2022 22:40:13 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john@jck.com>) id 1n7XIk-0001aG-3R; Wed, 12 Jan 2022 01:40:06 -0500
Date: Wed, 12 Jan 2022 01:39:59 -0500
From: John C Klensin <john@jck.com>
To: Peter Saint-Andre <stpeter@stpeter.im>, Eliot Lear <lear@lear.ch>, Lars Eggert <lars@eggert.org>
cc: rfced-future@iab.org
Message-ID: <377EA54FAAB4901B067FD497@PSB>
In-Reply-To: <6bb37c5a-6645-3af5-526a-48103cfad4d3@stpeter.im>
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> <bcbf4eb8-67e3-63aa-2e70-88cb74d8d3b0@lear.ch> <6bb37c5a-6645-3af5-526a-48103cfad4d3@stpeter.im>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/ZBTGwMtpDht4XFzqMfw2mk8rMWA>
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: Wed, 12 Jan 2022 06:40:19 -0000
--On Tuesday, January 11, 2022 17:41 -0700 Peter Saint-Andre <stpeter@stpeter.im> wrote: > On 1/11/22 12:33 AM, Eliot Lear wrote: >> 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. > > There's another piece here as well: working through feedback > received in the community calls for comment. "Constituency X > seems to be concerned about Aspect Y of Proposal Z; do we > think this rises to the level of something that could harm the > RFC Series as a whole and should one of us ballot CONCERN?" > Having a public archive of such discussions could be quite > valuable. And, of course, if the RSAB is involved in the RSCE selection process in any way, even just the selection of the selection committee as some of us have proposed, that would be another category of discussions that should probably be kept private. More generally (apologies if this has been said already), nothing we say or do is going to prevent the stream managers from having a private conversation (in person, on line, or in email), or even a conversation that involves their representatives if those are different. Personally, I would prefer to have the fact of those discussed be recorded, made public, minuted, and held in the presence of the RSCE (unless they are about the RSCE) and and ED (unless they are about them) even if the content is not public rather than having the fact of such a discussion kept secret and maybe key people kept out unnecessarily. And the latter is all I think we would accomplish by demanding that such discussions not occur. So, public mailing list, minutes, encouragement to make as much public (and in those minutes) as possible, but provision for private/meetings executive sessions if needed (and, if necessary, a private mailing list), the fact, topics, and, where relevant, conclusions of such sessions to be be in those public minutes and mailing list archives even if the contents of the discussions are not. john
- [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