[Rfced-future] BCP or not [was: Consensus check: Issue 22 – new stream for RFC Editor]

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 23 June 2021 22:06 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 3DEFC3A10B8 for <rfced-future@ietfa.amsl.com>; Wed, 23 Jun 2021 15:06:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_DNSWL_BLOCKED=0.001, 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 RCiuVu-CrM3K for <rfced-future@ietfa.amsl.com>; Wed, 23 Jun 2021 15:06:06 -0700 (PDT)
Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (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 048D33A10B7 for <rfced-future@iab.org>; Wed, 23 Jun 2021 15:06:05 -0700 (PDT)
Received: by mail-pj1-x1033.google.com with SMTP id p4-20020a17090a9304b029016f3020d867so2219716pjo.3 for <rfced-future@iab.org>; Wed, 23 Jun 2021 15:06:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=lP23Tv8Vkrl0sCUt1EmXifYbD6cqL0Tyy8ADDkBfPx4=; b=EeeytPcFepe0/BBL5fcxocaho4biOWPcnIy+8Oi4pjLUQy1EHXTO4Uts3O1ynwvylF I0NM+coY1FfTY3aVhAN/wBJO4n+yT0g3UKzmkO+nO7ZjjUUfUnXAWBP67uQ5SmIJv4N+ v3v4tgHgQB0skOTZ2cQka2fLb1ql7nGiNVX3jEJ3NV0CdyxTRrYKg7RnWH1h6YtHeaSI nQH5NpmXqVXDlJODVKbMLpWEAG24blg7UJNFsfLoc7zEAhcY40cXRUPgDHHIh6mRIFgj VXUHO1Xr00ir6Klm4WHrJXBS4Bn0HIgeBbENsSwZmA/gIRhdyt+mhqLMe9fEdNCiUp3d JWoQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=lP23Tv8Vkrl0sCUt1EmXifYbD6cqL0Tyy8ADDkBfPx4=; b=k8ujCWKVjJwca3vPZvILjuYdOmBf623pu7JGIBv8utL3mEBOdzCiGkFzjZjWQ0p2op ANgfcZQutBrdqhs6+uvfv/pelPsTypyXC9w+h/Y2SuFul1nYN7vJJQaNUhRH3xiM+E0e 4Eei6rvi9EOqLOprpIe7GxV4z/cPkZRtd1wqv85mvRoEfDQg6M3bRDHkDU/zDe3eVL88 9MzELysYlBaP7v3T5CnVQdWVJQ3QmbDBJdfdH9qBVRXYmAW/QlKyuksvGa5wvfWzb9OH QCUT3TiGTFDfnr5sTubghupMXw7VN6RhWwjssgANsywo9iOlO/NQCFuqp3Jp/GXWJMvw o+aQ==
X-Gm-Message-State: AOAM530LQ507DRyhvFDTeVRbRlD7ga7ktzXThV2duboB/J1vNqZWXGyg ZJ+enZrbLGqYuqw3CC0wRdJV8CpkrY0UdA==
X-Google-Smtp-Source: ABdhPJxV3TubR1eItP+THA0lVgtqMk9tmVqkFeyQr7qCeDLbrMs3kSfEcxIR2Z4WQwlj1x1nbYy6Ig==
X-Received: by 2002:a17:90a:4812:: with SMTP id a18mr11724545pjh.40.1624485964006; Wed, 23 Jun 2021 15:06:04 -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 u38sm96451pgm.14.2021.06.23.15.06.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 23 Jun 2021 15:06:03 -0700 (PDT)
To: Michael StJohns <msj@nthpermutation.com>, Eliot Lear <lear@lear.ch>, rfced-future@iab.org
References: <7ef10df2-cb21-a95b-b977-286b6d8a8405@lear.ch> <0a8101d76788$0e1af5a0$2a50e0e0$@olddog.co.uk> <fdb50b3a-a0e1-1421-4a4f-733002cfccda@lear.ch> <0ace01d767a5$39001350$ab0039f0$@olddog.co.uk> <7bda1df1-307b-4370-ad94-71af09af12c4@www.fastmail.com> <47618d03-3136-a4db-cd5b-66a1e89216ac@gmail.com> <492d7b65-33b9-e749-3297-85fe6779531c@nthpermutation.com> <16ab1107-6e4c-aaa4-80ef-7675ca05b13a@gmail.com> <a5715a35-5687-621e-e099-c6bda47c698e@lear.ch> <836bbdfd-8e61-ad18-ea8f-ff45331ed66b@nthpermutation.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <9fca165a-ae2a-3a37-65a2-cd7d74f13528@gmail.com>
Date: Thu, 24 Jun 2021 10:05:58 +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: <836bbdfd-8e61-ad18-ea8f-ff45331ed66b@nthpermutation.com>
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/TCbBC3U2slzPaZFELj0X3BWFNV8>
Subject: [Rfced-future] BCP or not [was: 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: Wed, 23 Jun 2021 22:06:07 -0000

This seems like a new issue, hence the subject change.

I don't actually care whether this is a BCP, or the last RFC model issued 
under the existing authority of the IAB, or the first editorial stream RFC approved by the RSAB, or all three of those things. As I said, it's synchronized swimming.

But I do think it's cleaner to make the necessary update to the IAB Charter in a simple separate document. In the end, it will make life simpler (especially if the IAB wants to further update its charter in future).

    Brian

On 24-Jun-21 08:07, Michael StJohns wrote:
> On 6/23/2021 3:43 PM, Eliot Lear wrote:
>> As a matter of history:
>>
>> On 23.06.21 02:22, Brian E Carpenter wrote:
>>> The IAB charter is an IETF BCP, so it can only be updated by an
>>> IETF standards action. It can practically be a one line document
>>> except for boilerplate, but it's gonna have to be done.
>>
>> My personal view: I don't think we should let the tail wag the dog, 
>> nor block this work on a new charter for the IAB.  This document could 
>> just as easily be processed as a BCP; the only issue being that the 
>> IESG would have to approve it.  If we want, we can get both IAB and 
>> IESG assent.  That has been previously done for RFC 7979.
>>
>> It'd require that an IESG member, presumably the chair, sponsor the 
>> doc, and that it go through IETF last call and IESG evaluation.  If 
>> the IESG is unwilling to do this, we could revisit the matter.
>>
>> Eliot
>>
>>
> +1 -
> 
> I'd actually extend this to the ISE and the IRTF for approval as it will 
> affect them as well.
> 
> All of this could be done in parallel rather than serially as the 
> datatracker seems to enforce.
> 
> Mike
> 
>