Re: [rfc-i] New proposal/New SOW comment period

Sarah Banks <sbanks@encrypted.net> Wed, 04 September 2019 03:35 UTC

Return-Path: <sbanks@encrypted.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 760C3120072 for <ietf@ietfa.amsl.com>; Tue, 3 Sep 2019 20:35:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 j8-pEgYn1oc4 for <ietf@ietfa.amsl.com>; Tue, 3 Sep 2019 20:35:04 -0700 (PDT)
Received: from aws.hosed.org (aws.hosed.org [50.16.104.137]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88AEC12008A for <ietf@ietf.org>; Tue, 3 Sep 2019 20:35:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by aws.hosed.org (Postfix) with ESMTP id DA754800AF; Tue, 3 Sep 2019 23:35:03 -0400 (EDT)
X-Virus-Scanned: Debian amavisd-new at aws.hosed.org
Received: from aws.hosed.org ([127.0.0.1]) by localhost (aws.hosed.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hh4VcLjZ3KCd; Tue, 3 Sep 2019 23:35:03 -0400 (EDT)
Received: from [172.16.12.109] (c-73-71-250-98.hsd1.ca.comcast.net [73.71.250.98]) by aws.hosed.org (Postfix) with ESMTPSA id 455468007D; Tue, 3 Sep 2019 23:35:03 -0400 (EDT)
From: Sarah Banks <sbanks@encrypted.net>
Message-Id: <0E44DEC5-936C-4B64-933A-0EE305839969@encrypted.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_BD7EDB3C-13F4-444E-A9EB-86D3E00D86BA"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: [rfc-i] New proposal/New SOW comment period
Date: Tue, 03 Sep 2019 20:35:02 -0700
In-Reply-To: <2ac05112-d2e3-5459-d2be-a115b7df935a@nthpermutation.com>
Cc: Adam Roach <adam@nostrum.com>, rfc-interest@rfc-editor.org, ietf@ietf.org
To: Michael StJohns <msj@nthpermutation.com>
References: <061D2F46-71C3-4260-B203-73B07EB59418@encrypted.net> <5B276430-96A9-44EA-929B-B9C2325AFCA5@encrypted.net> <f9be9982-56f5-bdcc-3b09-13080532ffc5@comcast.net> <D7B6334A-A4EF-4386-905F-86C187E22899@encrypted.net> <00237fc1-e378-322d-87d7-8e6f27907f2a@nthpermutation.com> <17ed6d9f-94b9-ad41-de64-28e4f982d2c9@nostrum.com> <2ac05112-d2e3-5459-d2be-a115b7df935a@nthpermutation.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/H6yRantbDPTS28M6pNUTvbfzKbs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Sep 2019 03:35:07 -0000

Hi,
	<snip>

>> 
>> I suspect that what she means (since I've made similar disclaimers in the past and have seen many others do so as well) is that she's speaking without yet consulting with the RSOC or IAB on the related topics, so as to avoid confusion between her perspective and the consensus position of either of those bodies. If you have a proposal for a better way to phrase that kind of thing, I would love for you to offer it up.
>> 
>> /a
>> 
> Fair point, and I can see that's probably what was meant.
> 
> The problem is that doing that is somewhat an abdication of the responsibility for the SOW.  I would have said something more like:  "Here's my opinion - I'll ask the rest of the RSOC to chime in as well", rather than the "speaking for myself" construct.     Or "I'll make sure the RSOC considers these, but I think I agree with XXXX and disagree with YYY and here's why".
> 

I take the chair role incredibly seriously. I was taught to chair by consensus, and if need be, rough consensus. I am a product manager by day. It's in my DNA to broker consensus. :) So when I send an email speaking for the RSOC, it really is that; it's an email that represents the consensus of the RSOC, whatever it may be, however rough it may be, regardless of my personal opinion on the matter. That said, I am also a community member, and while I agree that sometimes it might be hard to separate "chair of such and such" from "community member", I believe it's totally fair to share my own personal thoughts, without having first vetted them with the RSOC, when they are not damaging to the RSOC or the process. My opinions are just that, and the rest of the RSOC doesn't have to chime in if they don't want to. I appreciate your POV, but this is really a long winded way of me saying that my opinions are my opinions; i'll continue to share them when they're appropriate, and I'll continue to share those opinions in the best way I know how.
> Someone has to be willing to take and manage the commentary - if not Sarah, then who?    (I don't really care who - I just want to know who gets to decide what goes into the next version and how I affect that decision).  
> 

How did we get from "my personal opinion" to "Sarah abdicating responsibility of the SOW?" I don't see the leap, but let me state the obvious. The RSOC opened the comment period, and asked for the feedback to be sent to us. The IAB and SAA asked for it to go to RFCs-interest@. We're adults, we'll read the feedback on both lists and distill it. You are a voice in the community, and your feedback will be weighed along with everyone else's. 

Thanks,
Sarah
> "Success has many fathers, failure is an orphan".  I'd really like this not to be an orphan.
> 
> Later, Mike
> 
> 
>