IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 24 June 2021 20:35 UTC

Return-Path: <brian.e.carpenter@gmail.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 823F03A2A44 for <rfced-future@ietfa.amsl.com>; Thu, 24 Jun 2021 13:35:09 -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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.338, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 GED-Fab_lD0F for <rfced-future@ietfa.amsl.com>; Thu, 24 Jun 2021 13:35:08 -0700 (PDT)
Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (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 066B53A2A42 for <rfced-future@iab.org>; Thu, 24 Jun 2021 13:35:07 -0700 (PDT)
Received: by mail-pj1-x102e.google.com with SMTP id s17-20020a17090a8811b029016e89654f93so6647882pjn.1 for <rfced-future@iab.org>; Thu, 24 Jun 2021 13:35:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=hfm7NrvZ/gFeJhGjhdiee0hlGnZLicQG4qUPBmxNsdM=; b=Jo4QBf6bMUuJxTRmW77lQVRdcVo2TektFXfgmQ08Iyqxp6/VojwcXuqUYLNWatez7f WGOT3zLQn63bn2iLFSvLY0Ic5l+eD5BNIqpWQUL0Qt8BXte6IHnV/lD4T39U3ht7SYi5 NK34+TOqGIEm3i7OrVZ0ZAN+/DrsnQrQERNv0OYwBDiY3ofwpGNyvlzFSBvAUfvyqMS9 mEiANGSfrPmtfDoQhDw6I+R5JeNrLjAdkeH4z1MrtjFDmYUh4kF4RV7UDp5UWqmYit+j bzZOgHv/NaK0iT/7wGIIIyUa5aXAm7TqJI7d23dF/lceUkyy7RBTO7cFBpRjWB1Uff8n 9KbQ==
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=hfm7NrvZ/gFeJhGjhdiee0hlGnZLicQG4qUPBmxNsdM=; b=LYgG4C/+gM/fO7LYgEyBviHCBv/ZGi5x8jx1s0fK4nUjiAdfxs6y8S3KsV0/s8M8Oc 2TIE+CUQyx8ev554zgmIeA1qmM8y5/0Lj4THWES9ZVFrxGLIa2vaCgMSXbpcAyxAqCbk Xx1cBVpo5y2sTdko+1lppRAVlbJQmSMl60SlW6EVAq2WoQxw9Fk2NC2Qxrkbhm3MQ+di ncYm4OJ3wT9l6DTBbxAvqGuQgPMw7gD11Bk5qbvYjmg4v4xBLfhcPVl8te5+zTODMpIk 1ifmFPHYXKFSuKjqHySCNrlJu5+iClqXgWhUYT3uto6VWTNn3KF1ErDMYPm4inVO8NXz DD+w==
X-Gm-Message-State: AOAM532C3lZE3+yIoqU1/Y7VrJxs/WOVjlbGvJepHKAIJFpYjjL4CkgE pVe6ezNjsNPdBciDBM1ulCI=
X-Google-Smtp-Source: ABdhPJyfDiL9rO3JSVXhCEU+bHcPtKk5coaUFmcRwNIUd0/8LvxpgY/62iTyoq1DwL0JuaDdbN1cLA==
X-Received: by 2002:a17:902:c18d:b029:127:9c3d:6e93 with SMTP id d13-20020a170902c18db02901279c3d6e93mr3969159pld.73.1624566907012; Thu, 24 Jun 2021 13:35:07 -0700 (PDT)
Received: from ?IPv6:2406:e003:100d:901:80b2:5c79:2266:e431? ([2406:e003:100d:901:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id u24sm3833933pfm.156.2021.06.24.13.35.03 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 24 Jun 2021 13:35:06 -0700 (PDT)
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, Lars Eggert <lars@eggert.org>
Cc: rfced-future@iab.org, Joel Halpern Direct <jmh.direct@joelhalpern.com>, Jay Daley <jay@ietf.org>, Eliot Lear <lear@lear.ch>
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> <9fdeb823-9470-00a8-b1b1-91630b996c8c@gmail.com> <351774DB-C6DC-439F-9B5C-FB427EC9F6FE@ietf.org> <ac1aea74-da8e-405d-2a73-fbc6fc97ce24@gmail.com> <D1D7247E-6F03-475A-88F4-50E45A8B6F0E@eggert.org> <0a778f3b-c32e-abba-6e7f-305387adf3ad@it.aoyama.ac.jp>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <0d91a5c0-8dd5-cbe8-2ff9-c5b3fed3cbb2@gmail.com>
Date: Fri, 25 Jun 2021 08:35:01 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <0a778f3b-c32e-abba-6e7f-305387adf3ad@it.aoyama.ac.jp>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/IIhencS8MPnrcNXwx-aAIzQL6r4>
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: Thu, 24 Jun 2021 20:35:10 -0000

On 24-Jun-21 20:57, Martin J. Dürst wrote:
> Hello Lars, others,
> 
> On 2021-06-24 17:46, Lars Eggert wrote:
>> Hi,
>>
>> On 2021-6-24, at 7:57, Brian E Carpenter <brian.e.carpenter@gmail.com> 
wrote:
>>> As somebody else said, this stream by its very nature is going to be special and even self-referential. The notion we have of a stream being a 
client of the RFC Series just doesn't apply, so the normal notion of a stream manager doesn't apply**. But surely we need someone to act as progress chaser and nit resolver when a document has left the RSAB and is inside the RPC? And who will that be if it's not the RSEA?
>>
>> I still remain unconvinced that we even need a new stream. I may be in 
the rough, but I would be OK with using the IAB stream and leaving the IAB a role here.
> 
> What would that role be exactly? Giving the label "IAB stream" to these 

> documents without actually being able to approve or decline any of them?

I think that's exactly the problem. The IAB stream labels documents as
representing the IAB's opinion, and would imply that the IAB is
approving the RSAB's opinion, which is not the new model at all.

   Brian

v2.23.0 | Report a Bug | By Email