Re: [rfc-i] Comments on draft-flanagan-rseme-01

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 03 November 2019 19:16 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B26F11200CC for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Sun, 3 Nov 2019 11:16:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.5
X-Spam-Level:
X-Spam-Status: No, score=-4.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (body has been altered)" 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 u1j23n7-sbK2 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Sun, 3 Nov 2019 11:16:21 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4255312008C for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Sun, 3 Nov 2019 11:16:21 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 25494F406F3; Sun, 3 Nov 2019 11:16:07 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 5665AF406F3 for <rfc-interest@rfc-editor.org>; Sun, 3 Nov 2019 11:16:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jqMzpZS_78_i for <rfc-interest@rfc-editor.org>; Sun, 3 Nov 2019 11:16:04 -0800 (PST)
Received: from mail-pl1-x636.google.com (mail-pl1-x636.google.com [IPv6:2607:f8b0:4864:20::636]) by rfc-editor.org (Postfix) with ESMTPS id 48F4BF406D5 for <rfc-interest@rfc-editor.org>; Sun, 3 Nov 2019 11:16:04 -0800 (PST)
Received: by mail-pl1-x636.google.com with SMTP id p13so6651289pll.4 for <rfc-interest@rfc-editor.org>; Sun, 03 Nov 2019 11:16:18 -0800 (PST)
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=chnTbQehMBp4Rd7SZRL9fZWxKEULoOPs7WG3aGmXTbA=; b=WpqimB0deyPQLcsNQ4tWqJUx1bCIEPt+iocrS0q34O0wAea/3UafrH0ZY70ZQ+ofJ8 O502j7L50NM78AiP/STfS5FFATFYQkZ2Bff6lPiYAyuEjB/QZfinSiAtgaXmHDprdYiz NJaZfpItwpolZpYyodmiBnkjGLHvYMzOjClK9sFizTQ/hppXY4suqleo38nvbCM8VVgK fGRnVe6dx+IUSS/Rn+6hmJP/sdeDH+HcYziLt7oA3OBxvVCV1yVyWfQ33oyBoBZqJ29Q elIu6Ll6lg19MXp8U+ndW25wMCqNRoKhzb908v/SE1uEg4mSgHwG+QuP5ioqb3mW1i0F +Osg==
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=chnTbQehMBp4Rd7SZRL9fZWxKEULoOPs7WG3aGmXTbA=; b=EmgOJdG1Oa12zOTf4vCAOr2Tt93NheDQhiNMiL06uwyq/6+/Tuni5hWtg1QVzLX0oa 5FitjcK3auUI3gCr9AgQdvPj4Y50h75QTxCeYilRaAhyTW0WDcuOVV13UccfiuY7wF4Y jsaLmC49mef3TAQA7LQbFYnXpe6SMYnK8UQxn94w8KMqRtFnwyEmHB4GQM/eXxvx3lF7 KM6XimIMfdFHi7C6JJxw7H2C8fDLUhRP0SJH0/a9ZaZOwAwM/flFDtief7ZRZQNgzZq3 sDM1ExiB6dxKRw6RNetFzKxQEdnmpUFuPJvFxwQ6XSdB1WPWXBN9OUzTws/Sp1bPsvOY MavQ==
X-Gm-Message-State: APjAAAXBPojEH4+1lrD/JdfZUiUJwH7nOB0u8FUzgbGDhtZPOf6Warj+ ZOnqKEEv2XDwV8v4x0ifcEy96oB4
X-Google-Smtp-Source: APXvYqzxh7010ZutEjVcgmHdEyBcTMrZ0fwiLzfjCqV/v8M2jScRI9KGesys3x5mwVeTPEdsXmLauw==
X-Received: by 2002:a17:902:8506:: with SMTP id bj6mr8408563plb.342.1572808577163; Sun, 03 Nov 2019 11:16:17 -0800 (PST)
Received: from [192.168.178.30] (46.137.69.111.dynamic.snap.net.nz. [111.69.137.46]) by smtp.gmail.com with ESMTPSA id b18sm12623528pfi.157.2019.11.03.11.16.15 for <rfc-interest@rfc-editor.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 03 Nov 2019 11:16:16 -0800 (PST)
To: rfc-interest@rfc-editor.org
References: <6.2.5.6.2.20191103002732.12192ec0@elandnews.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <eca1b2a3-0686-e86d-dd08-139a651b8dfe@gmail.com>
Date: Mon, 04 Nov 2019 08:16:15 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <6.2.5.6.2.20191103002732.12192ec0@elandnews.com>
Content-Language: en-US
Subject: Re: [rfc-i] Comments on draft-flanagan-rseme-01
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Hi SM,

On 03-Nov-19 20:54, S Moonesamy wrote:
> Hi Heather,
> 
> Thanks for hosting the three virtual meetings to discuss about the 
> future of the RFC Series.  I read draft-flanagan-rseme-01 and I have 
> a few comments about it.
> 
> A few weeks ago, I was looking into the IAB programs.  Some of them 
> are far from successful.  The program which is relevant to the RFC 
> Series showed signs of communication difficulties during the 
> discussions on the RFC Series Editor matter.  If I understood 
> draft-flanagan-rseme-01 correctly, the proposed fix for that is to 
> have past IAB or IETF chairs lead a new IAB program.  I did not find 
> anything in the draft to explain why that is considered as good choices.

As for whether an IAB "program" is a good choice, I think it's only
a question of wording, since the IAB "program" concept is not defined
by rules but only by how the IAB chooses to run it. So the issue of
principle here is whether the IAB should be the host for the activity
at all.

The question behind that, which I hope will be discussed frankly, is
whether the community trusts the IAB to act as the host for this with
the necessary neutrality and open-mindedness. If not the IAB, what
other host would you suggest?

Also I remind everybody that the NomCom is open for comments and 6 IAB
seats are under review.

As for whether past I* chairs should be involved, I think the argument
was that we need people who have a broad view of the issues, and past
I* people would qualify. I don't think the argument was any deeper than
that.

> The draft proposes that there should be clear conflict of interest 
> statements by the persons chairing the new group.  The BCP 25 model 
> does not provide any guidance about conflict of interest.  How will 
> the new group work out what should be in those statements when the statements?

We aren't talking about the kind of financial conflict of interest
that is of concern in corporate boards etc. So I think it's a matter
of common sense that doesn't need working out or formal rules.

Regards
   Brian


> 
> Regards,
> S. Moonesamy
> 
> _______________________________________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
> 
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest