Re: [Rfced-future] Consensus check: Issue 22 – new stream for RFC Editor

Joel Halpern Direct <jmh.direct@joelhalpern.com> Fri, 25 June 2021 21:29 UTC

Return-Path: <jmh.direct@joelhalpern.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 9546F3A09F9 for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 14:29:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level:
X-Spam-Status: No, score=-2.438 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, NICE_REPLY_A=-0.338, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 rnW23jilYIaw for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 14:29:15 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 4B15E3A09F5 for <rfced-future@iab.org>; Fri, 25 Jun 2021 14:29:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4GBVWG61CYz6GHfH; Fri, 25 Jun 2021 14:29:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1624656554; bh=oFplPM/Up33NGp6QEsCAPDEyvuTkIzuBpusVWttn5SI=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=S+6bwR1LQ8LP5tTuJ1+4SXirIoWG43lr30AjUMQv8274cFcbLNVeITLMH0lruMJfV mAUZNgHtCiLJkcAZDbhqVN1wO+sEOaodob4aJZvha+XJF2pnE/BVnCqBgBP69CLVnW 7Yr3/dip3v2ScldJ/3athbB00ljadxUDZ4SpIsW4=
X-Quarantine-ID: <wCWBIQTnJ6oB>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.23.64] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (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 maila2.tigertech.net (Postfix) with ESMTPSA id 4GBVWG0tpyz6GFQl; Fri, 25 Jun 2021 14:29:14 -0700 (PDT)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Peter Saint-Andre <stpeter@mozilla.com>
Cc: rfced-future@iab.org
References: <3f4c264e-4639-4d6b-cf22-0a2be503decc@joelhalpern.com> <3D3EC062-7B1A-43C4-99D5-A204A4565ECE@ietf.org> <cf2921d8-fd1f-d9c9-da72-ff760eda347c@lear.ch> <3b4b6d91-64e3-d0d7-bcbc-284f29a46fb7@joelhalpern.com> <2d926822-5c68-2279-b197-836534f3c030@mozilla.com> <faf54e3b-5c3c-4a97-f364-47c14c251eed@joelhalpern.com> <55602726-93b9-d03c-447c-9d4b9ede5397@mozilla.com> <34f4e8eb-3c81-6cb0-5cf1-ee3ab3b6cc5f@gmail.com>
From: Joel Halpern Direct <jmh.direct@joelhalpern.com>
Message-ID: <d9d7116f-1603-4c5c-116a-176659aa418f@joelhalpern.com>
Date: Fri, 25 Jun 2021 17:29:12 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <34f4e8eb-3c81-6cb0-5cf1-ee3ab3b6cc5f@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/Sza6xQ6y-_yVAd-hm2LwZvttFyU>
Subject: Re: [Rfced-future] Consensus check: Issue 22 – new stream for RFC Editor
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: Fri, 25 Jun 2021 21:29:20 -0000

If those are the stream managers, then we need a different description 
for the makeup of the RSAB.  It would be rather odd if the IESG sent 
different people at different times to the RSAB activities.  Presumably 
we hope for some limited degree of continuity.

Yours,
Joel

On 6/25/2021 5:26 PM, Brian E Carpenter wrote:
> On 26-Jun-21 08:55, Peter Saint-Andre wrote:
>> On 6/25/21 2:52 PM, Joel M. Halpern wrote:
>>> Hmm.  That does not seem to match reality.
>>
>> Well, then we should align documentation with reality. ;-)
> 
> How about
> 
>    the IESG (represented by any AD) and the IRSG (normally represented by the IRTF Chair)
> 
>       Brian
> 
>>
>>> The IESG and IRSG do not
>>> attend the stream managers meetings.  From everything I have ever
> been
>>> told about, the IRTF chair and the IETF chair have historically attended
>>> those meetings.  And made practical decisions.  (I am sure that for
>>> major items the IETF Chair checks with the IESG.  The IRSG serves
> at the
>>> pleasure of the IRTF chair, so whether he (the IRTF Chair) checks with
>>> them is presumably up to him.)
>>
>> Right.
>>
>> Peter
>>
>