Re: Try this: was Re: New proposal/New SOW comment period

Michael StJohns <mstjohns@comcast.net> Tue, 10 September 2019 22:45 UTC

Return-Path: <mstjohns@comcast.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 AB2F0120074 for <ietf@ietfa.amsl.com>; Tue, 10 Sep 2019 15:45:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=comcast.net
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 bPrJAAS6GYJC for <ietf@ietfa.amsl.com>; Tue, 10 Sep 2019 15:45:22 -0700 (PDT)
Received: from resqmta-po-02v.sys.comcast.net (resqmta-po-02v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:161]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C03C01207FE for <ietf@ietf.org>; Tue, 10 Sep 2019 15:45:22 -0700 (PDT)
Received: from resomta-po-05v.sys.comcast.net ([96.114.154.229]) by resqmta-po-02v.sys.comcast.net with ESMTP id 7o90ibBhXgMI77ot0i7g43; Tue, 10 Sep 2019 22:45:22 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1568155522; bh=V3mwVi7cpQjQgfy2v6PPTEIhii//1AbHde/rbj6DEXU=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=UrKQSVIwrYCXbV4QF2WAoKAWo0jZmqaHUyBlkqLHrKaPUZFZERwZNUFhzBmyrp3GD 3IpL/cXHj/wwRMZZ1bOE/pCrb1dVSTIKj9WH9DV0Xf4BWCpuzz5Wjl33Uh1vpztXyK URvJYxxkLAo4hguytPplNrdeCtMtQ7ita5LYaQVlGDPFSXkFvsQD7wlN2rlLtn1yLx MNXagY9eVQaJf+0qBzRPO4m2n9KRTCTD2q34cSWEAwY8jF7K7iSR+wx2g3u8uZfxL9 jatgUqfk6goyBsc+2jRW6E8GRurymeWoYn8NANsz+FTU6yL9v/cJ2ETPo48f5p1icD 3S+xli6nD+HiA==
Received: from [172.26.12.99] ([67.132.193.197]) by resomta-po-05v.sys.comcast.net with ESMTPSA id 7osfi1QM3GpNH7osfie9sq; Tue, 10 Sep 2019 22:45:17 +0000
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedufedrtddugddufecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvghsihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesthekredttdefjeenucfhrhhomhepofhitghhrggvlhcuufhtlfhohhhnshcuoehmshhtjhhohhhnshestghomhgtrghsthdrnhgvtheqnecukfhppeeijedrudefvddrudelfedrudeljeenucfrrghrrghmpehhvghloheplgdujedvrddviedruddvrdellegnpdhinhgvthepieejrddufedvrdduleefrdduleejpdhmrghilhhfrhhomhepmhhsthhjohhhnhhssegtohhmtggrshhtrdhnvghtpdhrtghpthhtoheprhhftgdqihhnthgvrhgvshhtsehrfhgtqdgvughithhorhdrohhrghdprhgtphhtthhopehivghtfhesihgvthhfrdhorhhgnecuvehluhhsthgvrhfuihiivgeptd
X-Xfinity-VMeta: sc=0;st=legit
Subject: Re: Try this: was Re: New proposal/New SOW comment period
To: ietf@ietf.org, rfc-interest@rfc-editor.org
References: <ec715385-93ca-ddf0-f9b1-d0e4ae1666fe@nthpermutation.com> <CAL02cgTqDTXgG1bU1DGBkdQ7XwV=2ryJzQU1QD8yNba-7ngk3A@mail.gmail.com> <44cbe750-e030-69d7-54ba-5eaeccc5f512@gmail.com> <CABcZeBNw8c17F0bvcSJoS4R=dk_KoSx1jWkEnupUUps6k8UcGg@mail.gmail.com> <CAL02cgS88fD7BkrE4T0A+S99xN-b4JZDm4yu2nLAb3oiG50S4g@mail.gmail.com> <1dbc8dbe-d883-a433-8dc4-247ac1760152@joelhalpern.com>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <395d6e71-02d7-bd80-01c4-2d8ccde204ea@comcast.net>
Date: Tue, 10 Sep 2019 18:45:00 -0400
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: <1dbc8dbe-d883-a433-8dc4-247ac1760152@joelhalpern.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MxLhcNYkG8oF04E45h2m0RqcbFg>
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: Tue, 10 Sep 2019 22:45:25 -0000

On 9/10/2019 5:10 PM, Joel M. Halpern wrote:
> Maybe I misunderstood the RSOC message.
> I thought they had indicated that they were NOT trying to hire an RSE 
> as defined by RFC 6635 and its details.  Rather, as I understood them, 
> they were hiring someone in a temporary capacity (explicitly NOT an 
> acting RSE) to keep the series running while the community decides 
> what it wants. 

Hi Joel -

I found/find the RSOC message somewhat mixed.  On one hand we have what 
was in the emails (from Ted and the RSOC) and the pre-amble to the SOW 
that says "temporary, non-RSE" and then there's the experience and 
deliverables in the draft SOW which have no more than a playing card's 
thickness difference from the deliverables in the SOW under which 
Heather was hired.  As far as I can tell (IMHO) RSOC's draft SOW mostly 
takes away the authorities of the RSE while leaving most if not all of 
the responsibilities.   I did ask how these two positions differed and 
which responsibilities should be removed to make the difference clear - 
Sarah asked me to propose text, so I did albeit not in the way she might 
have expected.

   I re-wrote that SOW - especially the preamble - to reflect a more 
acting RSE model which made sure that there was an identified 
"responsible person" for all of the current RSE responsiblities. If the 
RSOC and the IAB want something that's distinctly not an acting RSE, 
they're probably going to need a substantially different SOW and a much 
more constrained set of responsibilities/deliverables as well as an 
explanation of who gets the authority and responsibility over the 
remaining set (if any).

I clipped out the rest of your text as it applies equally well to 
arguing for/against a 6635 centric model and I want to think about it a 
bit more.

later, Mike