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

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 04 November 2019 03:57 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 93539120888 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Sun, 3 Nov 2019 19:57:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.499
X-Spam-Level:
X-Spam-Status: No, score=-4.499 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, URIBL_BLOCKED=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 BgGJ0k1iB0j3 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Sun, 3 Nov 2019 19:57:01 -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 B414F120877 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Sun, 3 Nov 2019 19:57:01 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 189D8F406CC; Sun, 3 Nov 2019 19:56:47 -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 F1016F406CC for <rfc-interest@rfc-editor.org>; Sun, 3 Nov 2019 19:56:45 -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 yi3j_7aeazQQ for <rfc-interest@rfc-editor.org>; Sun, 3 Nov 2019 19:56:43 -0800 (PST)
Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) by rfc-editor.org (Postfix) with ESMTPS id 5116AF406CB for <rfc-interest@rfc-editor.org>; Sun, 3 Nov 2019 19:56:43 -0800 (PST)
Received: by mail-pl1-x632.google.com with SMTP id w8so7011695plq.5 for <rfc-interest@rfc-editor.org>; Sun, 03 Nov 2019 19:56:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=6MrhOmtKejORQS1RWP5QIa6UrTTzI9BRsIVFn6qiuxY=; b=dV8ZJ0zToMuK+b1Zgb0h1QQN0mNRdLemLI7jDAZ99NdvzlEPd7pY5BJ/ffzuwntY2V ecpyLO6QnjR4+ZlNn0xFBn8Bjsq6B1d76GcxyMooibqc3GGmmP2YY2H7i8FU9jk1ByZW MNgpL/OveBbgPg18ehVxUBGj7BKzD9PxDpr8S39fa56nK3SOMjCxA6bSTPv1Iz6zDmCH munyBK1uZBySkNNhctSb6qtHvH4Sd35JLQyDYxIC5tjTx+3le4/n0FsoqhfTVeFuYqD4 wwfdvrNa7goEJMiAq6ESMHe8a41NN74yiNYFN37s1cYCXaBmI3cYIRsAnToXCDV+70Qk 0YVg==
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:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=6MrhOmtKejORQS1RWP5QIa6UrTTzI9BRsIVFn6qiuxY=; b=NvZ9k50Z9NElCHFbhBc7tOCkieI9lvsuQhYLcrhnonR5J/z5uICEA5g6GsJO7dpg3X Ll8P1BJLORJR/aBqdIjeBniPQgxzIMK8NzTR2EFf9XIiI92U0qbTrtE3m37Vf5WwFktI miyAMAgPOseZjS1PzJqZjAvuJ7W3oSfN9tsjGV6pnRzR0eoZ8tc911zPUJnFvnVSa7aK Mf4TPjMUpG6wYtQub3dbb0lV/QYyDJn720CWQVkXGXGpY5NweBdBUZlfKJLfHirPtqJ1 d3EQlO+DQzjcRYwc0mFditrE/15rUlDxou0lLi0kPXLpWls9mGbWpSHvJXJpRREVcozK yWiA==
X-Gm-Message-State: APjAAAXBMaVkgd/dtqriHP4dUjn1PZ+VyXLHvhPexXDqIpoyq5Z3YTRq SroHYHNJFJYerS/XlQFxUtelRfud
X-Google-Smtp-Source: APXvYqy9M6NwUL7f8j0o8JmVSf3HsGUNB/p0Sm9Ryj6PuYge+iGXX1erH1QQdfM6VuMV8T514/8GlA==
X-Received: by 2002:a17:902:ba94:: with SMTP id k20mr25225184pls.312.1572839815490; Sun, 03 Nov 2019 19:56:55 -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 b17sm15486539pfr.17.2019.11.03.19.56.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 03 Nov 2019 19:56:54 -0800 (PST)
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Randy Bush <randy@psg.com>
References: <6.2.5.6.2.20191103002732.12192ec0@elandnews.com> <eca1b2a3-0686-e86d-dd08-139a651b8dfe@gmail.com> <m2o8xs4kwq.wl-randy@psg.com> <b0cbe095-5cfc-65c1-8905-0fd916732df6@joelhalpern.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <b04ade65-dd7e-7533-198a-5da535e9b4f5@gmail.com>
Date: Mon, 04 Nov 2019 16:56:49 +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: <b0cbe095-5cfc-65c1-8905-0fd916732df6@joelhalpern.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>
Cc: rfc-interest@rfc-editor.org
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>

On 04-Nov-19 12:37, Joel M. Halpern wrote:
> Somebody has to appoint the chairs.  Somebody has to serve as an appeals 
> / support / resolution chain for the discussion.  Somebody has to take 
> responsibility for confirming when an agreement is reached, and then 
> finding a way for the community to act on that agreement.*
> 
> We have relatively few structures for doing this.  Saying that the 
> chairs and structure shall appear from thin air seems rather unlikely.
> 
> As I stated on the call I was on, I am not happy with this path.  I am 
> merely less unhappy with it than I am with any other path I have heard 
> suggested or have imagined.

Indeed. So in answer to a question from SM:

>> Does neutrality mean not expressing any opinion in public about this matter?

I would expect individual IAB members to have, and express, opinions.
But I think that when such a process is launched, the IAB as a committee
should undertake to *not* express an opinion during the process of
discussion and consensus formation.

Related to that, and again in answer to SM:

>> Would shared 
>> affiliation be considered as a conflict of interest?

I don't really think so. Many of us have multiple affiliations.
But when the topic is finding community consensus on the way
forward for the RFC series, we need all viewpoints and all
affiliations represented. Certainly I'd expect people to disclose
their affiliations.

> Some of the discussion of the proposal has been helpful.  But wishes for 
> magical better answers do not help anyone.

Agreed.
   Brian

> 
> Yours,
> Joel
> 
> *Yes, I am being optimistic.  The alternative is to watch the whole 
> structure collapse.  I prefer to try to improve it.
> 
> On 11/3/2019 6:09 PM, Randy Bush wrote:
>>> 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.
>>
>> given how we got to the current situation, that is definitely in
>> question.
>>
>>> If not the IAB, what other host would you suggest?
>>
>> it may not be clear to all that it needs a host.
>>
>> randy
>> _______________________________________________
>> 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
> 
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest