IETF Logo Mail Archive

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

Peter Saint-Andre <stpeter@mozilla.com> Fri, 25 June 2021 19:19 UTC

Return-Path: <stpeter@mozilla.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 1C49F3A09D8 for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 12:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level:
X-Spam-Status: No, score=-2.437 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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=mozilla.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 YGpkSK1YOM-w for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 12:19:21 -0700 (PDT)
Received: from mail-il1-x12a.google.com (mail-il1-x12a.google.com [IPv6:2607:f8b0:4864:20::12a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B021F3A09D1 for <rfced-future@iab.org>; Fri, 25 Jun 2021 12:19:21 -0700 (PDT)
Received: by mail-il1-x12a.google.com with SMTP id t12so1880274ile.13 for <rfced-future@iab.org>; Fri, 25 Jun 2021 12:19:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=rBiW+R//qOHc4DwiJfxwgBs0iS8ZXI75HopgkR5xuSs=; b=VPp0I8YrNeoEroh42sxT1Uafxl1QhS4toOY/55e6SghANMp3hqaIiq0Jq+GcYgdRSV KUyXTdqEuLu+Xgvb9pPC77uD6d6uZSvcTD/N1UpTd+Vz+ryl/218U/Qb8Af+Z4d/FapU nfb3CrSl6C8Wevj8xQCLIcmE1EQDpBSLe2rQM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=rBiW+R//qOHc4DwiJfxwgBs0iS8ZXI75HopgkR5xuSs=; b=OsPdcKYT3PNt/8fmJdyqpO6jv7g/ulVUkYJkQv69CtMKZJUdZ3II/3t1ukbeWapD/I fbzdzzaEwAkRbqleT8KPUSwLqG+kBQuYFnKSKKlrpoi4DjDaJyBwRkVVfArVogm351IG 8vJOTYXKWFFPfu7nABfYXArSK4VwdAlEGgnA09zIXruqOOd7+mMxjSFj3pvbLj2NOr2M UtIsqeed8Sc4vFJK7RE/2IlqtMRACiy3fU0LhuFtYt8M45snRBU9d2UboSgPzVabVgf+ LXH6mbwAYTD5pQXggpl2pOq1Xky/WrukcPSL3RHWaMXlm/iXF27YDXcZSwKL3Ip/JxFN XPKg==
X-Gm-Message-State: AOAM531fjS02c/hk1af/gw4swME/Xq1d9sNWw6bVpoCMPlfJArIKyDWB 1M9EQ4pqGeC5T8yQ0Fy4p0blDA==
X-Google-Smtp-Source: ABdhPJwAI4qmVVej0EOgux2lIqxfPVRdhpBhsmozJvUY/EoJ9it8sG3VWjvV9qibdb/z4JYn3UguHg==
X-Received: by 2002:a05:6e02:dcc:: with SMTP id l12mr3833774ilj.80.1624648759996; Fri, 25 Jun 2021 12:19:19 -0700 (PDT)
Received: from dragon.local (c-73-78-113-156.hsd1.co.comcast.net. [73.78.113.156]) by smtp.gmail.com with ESMTPSA id e7sm3951207ili.10.2021.06.25.12.19.18 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 25 Jun 2021 12:19:19 -0700 (PDT)
To: Joel Halpern Direct <jmh.direct@joelhalpern.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>
From: Peter Saint-Andre <stpeter@mozilla.com>
Message-ID: <2d926822-5c68-2279-b197-836534f3c030@mozilla.com>
Date: Fri, 25 Jun 2021 13:19:18 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <3b4b6d91-64e3-d0d7-bcbc-284f29a46fb7@joelhalpern.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/OY0NRSYgl8LRm933VnXP-dbW4Ds>
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 19:19:26 -0000

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

v2.23.0 | Report a Bug | By Email