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

"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 25 June 2021 20:52 UTC

Return-Path: <jmh@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 3EBB33A0141 for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 13:52:26 -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 WsXrH5fCaWPN for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 13:52:21 -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 B87803A0143 for <rfced-future@iab.org>; Fri, 25 Jun 2021 13:52:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4GBThj3SQfz6G98X; Fri, 25 Jun 2021 13:52:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1624654341; bh=vodiaC4H1rAaavFd9glSzea3CTZHb0G9TbwdvtgBIeU=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=XeurZp4GG3bDRmINBTGICsdMazIvW7J/V6H6KMLJfasNOblN3dFqYMD+7iQW3Yb5S 29MGMYHMtQht7o/Et7R4PdjluEW6QH9hqc/Ev20ZkFmTPWCOmbwr6INIiEYDZFKaog lIv+j5IYhZCMzZtnHYHYl65+GvvvQfhDyZJIsIm8=
X-Quarantine-ID: <LOaaPXx8JUD3>
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)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4GBThh6S1sz6GDyJ; Fri, 25 Jun 2021 13:52:20 -0700 (PDT)
To: 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>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <faf54e3b-5c3c-4a97-f364-47c14c251eed@joelhalpern.com>
Date: Fri, 25 Jun 2021 16:52:19 -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: <2d926822-5c68-2279-b197-836534f3c030@mozilla.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/10z-2RgRU1CN0-7U9wP58PFhFQY>
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 20:52:26 -0000

Hmm.  That does not seem to match reality.  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.)

Yours,
Joel

On 6/25/2021 3:19 PM, Peter Saint-Andre wrote:
> On 6/23/21 3:06 AM, Joel Halpern Direct wrote:
>> I am wondering if we are mixing the concept of stream manager with
>> stream content owner.  The IESG is responsible for the content of the
>> IETF stream.  The IETF Chair or their delegate is the IETF stream
>> manager.  That role is making sure that there are no issues with the
>> practical publication of the stream, including interacting with the RPC.
> 
> I'm not sure that we have a clear definition of the role of a stream
> manager. Bits and pieces are scattered around in RFCs 4844, 4845, 4846,
> 4714, etc.
> 
>> Declaring the RSAB to be the stream manager hurts my head.  That is not
>> a person.  And will create confusion about the role of the RSAB.  WHile
>> the obvious analogy is to declare that the RSAB chair is the stream
>> manager for this new stream, it seems to me that creates confusion since
>> that person is (unless they are the RSE/A) the stream head for some
>> other stream.
> 
> According to https://www.rfc-editor.org/faq/#streamman the stream
> managers are:
> 
> For the IAB stream, the IAB Chair
> For the IETF stream, the IESG
> For the Independent Submissions stream, the ISE
> For the IRTF, the IRSG
> 
> So we already have stream managers that are not natural persons.
> 
> Peter
>