Re: [Rfced-future] [IAB] Welcome to the RFC Editor Future Development Program

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 01 April 2020 02:17 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 90BD23A1064 for <rfced-future@ietfa.amsl.com>; Tue, 31 Mar 2020 19:17:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level:
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 9SQj1mQc6Iwp for <rfced-future@ietfa.amsl.com>; Tue, 31 Mar 2020 19:17:52 -0700 (PDT)
Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (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 93B2F3A1028 for <rfced-future@iab.org>; Tue, 31 Mar 2020 19:17:49 -0700 (PDT)
Received: by mail-pg1-x52e.google.com with SMTP id g32so5295481pgb.6 for <rfced-future@iab.org>; Tue, 31 Mar 2020 19:17:49 -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=I8Py/8s/7AhmNiNQgE2G6r40XenRaFT59/7hf7X6w5w=; b=gNEccdHVoNlWAVF4k+CbEYIBMPgeF8nRlPOQP5TLa0GF23XjQEdZr3h8mC+qGRAJ0d vKgNUktChta1SN9PvdN6tpIfUUC9CD5vf8gHzsyiOyj5y6Xkb99hZ4DwrPAcRfkIkzlR nzpSj/bAciW0FhYQNrfPyk37qwW1dnvl0JIMB/cPEryoGiIRNVEhGModFVq3jQJaJUSt G1v1kbrCTjqchcLJe+axhwDP9YOkIZpvZ/OFnO4vKDDLTjzpB516lCdg4Hsm9RV8ea4c kcQ2ObjQDu01eyjYNuIQcnKkXGrywrjJ3s48PFR37hAg+LnFaUp1Oj9wJ55HI6vvZ31z J1kA==
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=I8Py/8s/7AhmNiNQgE2G6r40XenRaFT59/7hf7X6w5w=; b=ZEdxg6UnCdPQCIKYxQKZWHI9gqkQHlujGqQdN3tk+v/bzTxwsVQ18bufRYigLgyA74 t5YX5HxpzkxBtKpS61BLojeJyfhJITb9xsA9gcpsWHRRDfr6duMVblqoWA6hfWvTs/AH h3eekipDPub8qnAroNoH2nKtXJhZXv6G6+viH180rQVpZCsNp1hPM3Z602xg2W6TMpLm Le3eft6sUFmbBK2PM79A56p+0RdV/JUK4U3iWyZbYsFQtJPTaZFx7Rt/FGUcWT/5H9zm iLGqfwx+hi5a/lgw0t1wyKjlC3Fe7TQCM6R5Ekj7nVtqxWPxTnIkD7PyhxOxeOxlDQJq IoBw==
X-Gm-Message-State: ANhLgQ03WfkpW1U0vP1Iwv3bs8FSSSGKEVe25JTt0D13wjmZanUb/yxB B3UOjsEfhTiLTb4dlt4o069RtYwz
X-Google-Smtp-Source: ADFU+vtrZvNgQWMcttALq2YOcThFmz+VChNsq9xjVDk5v1IvBMSGp3kmOKHOX3r9WtH2W2qlPdGwLw==
X-Received: by 2002:a63:7f18:: with SMTP id a24mr20434749pgd.178.1585707468631; Tue, 31 Mar 2020 19:17:48 -0700 (PDT)
Received: from [192.168.178.30] ([165.84.25.143]) by smtp.gmail.com with ESMTPSA id v4sm368513pfb.31.2020.03.31.19.17.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 31 Mar 2020 19:17:48 -0700 (PDT)
To: Mark Nottingham <mnot@mnot.net>
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>, Eliot Lear <lear=40cisco.com@dmarc.ietf.org>, rfced-future@iab.org
References: <97B63B78-0D49-4007-B8A2-101FB7849C0F@cisco.com> <CAA=duU0_pr_56HTR5vZg+AK981rkvGrMGFFi-UHgW4L=6=6mwg@mail.gmail.com> <D6A290EE-72E5-46A7-BA25-085CC2AAE35C@cisco.com> <0E6D83F8D11D8C1B9B7237B7@PSB> <73C27FFD-BD81-4CF3-9D9D-845DE9544A36@cisco.com> <097a60d7-2229-b849-1ca3-1f6d298cceed@nthpermutation.com> <yblpncthb1n.fsf@w7.hardakers.net> <ad40f5c1-5551-3e3e-9bc3-164ec3368b68@gmail.com> <16726C73-09AB-4F61-8C00-8224E3EF6F1B@mnot.net> <E9B2BFA7-4EFE-4608-AB00-42B46C4503E7@cisco.com> <326aa371-82ad-da59-d873-f4e08cd6c3bb@joelhalpern.com> <0934cdca-7ff4-f43e-2e5f-66ed2939232f@gmail.com> <E7935877-BF2B-469F-9204-47CA2EB70670@mnot.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <f11d16f0-b1ae-13ca-0f57-938e647f35b3@gmail.com>
Date: Wed, 01 Apr 2020 15:17:43 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <E7935877-BF2B-469F-9204-47CA2EB70670@mnot.net>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/AsljvjQ02zEuoPr_NXjbO4r9qT8>
Subject: Re: [Rfced-future] [IAB] Welcome to the RFC Editor Future Development Program
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, 01 Apr 2020 02:17:58 -0000

On 01-Apr-20 13:14, Mark Nottingham wrote:
> [ I'm moving iab@ to bcc:, as most IAB members are already here, and I'm sure they'll appreciate the reduction in duplication. ]
> 
> Hi Brian,
> 
>> On 1 Apr 2020, at 7:09 am, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>
>>> My preference is 
>>> that we define the job such that it is clearly the RFC Editor's job to 
>>> lead that discussion / process.
>>
>> I very strongly agree with that, but to my mind that requires that we agree
>> on the principle that the RFC Editor is autonomous and the series is not
>> controlled by the IETF or, except at a very abstract level, by the IAB.
> 
> I don't see how that follows. We have plenty of people who lead discussions and processes in this community, and yet they still have oversight, checks and balances. There may be reasons for exempting the RSE from them, but declaring that special status as a presumption seems odd in a program with our scope.

I won't repeat what I said in https://www.ietf.org/archive/id/draft-carpenter-request-for-comments-01.txt, but I will assume you've read it.

Of course, being autonomous shouldn't mean exemption from checks and balances. However, in the case of the RSE (and unlike most of our activities), it really isn't clear which community should implement those checks and balances. And the evidence from the IAOC and the RSOC is that we aren't very good at designing oversight functions. I think that's our biggest challenge.

    Brian