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

Michael StJohns <mstjohns@comcast.net> Tue, 10 September 2019 22:45 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 20132120854 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 10 Sep 2019 15:45:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.997
X-Spam-Level:
X-Spam-Status: No, score=-4.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, 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 (message has been altered)" 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 z3mJuRRPnc2R for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 10 Sep 2019 15:45:28 -0700 (PDT)
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 7FEB7120805 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Tue, 10 Sep 2019 15:45:28 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id A9EF5B81498; Tue, 10 Sep 2019 15:45:25 -0700 (PDT)
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 32000B81427 for <rfc-interest@rfc-editor.org>; Tue, 10 Sep 2019 15:45:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
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 o_hCB8KKeqW5 for <rfc-interest@rfc-editor.org>; Tue, 10 Sep 2019 15:45:23 -0700 (PDT)
Received: from resqmta-po-04v.sys.comcast.net (resqmta-po-04v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:163]) by rfc-editor.org (Postfix) with ESMTPS id 2C5CFB81423 for <rfc-interest@rfc-editor.org>; Tue, 10 Sep 2019 15:45:23 -0700 (PDT)
Received: from resomta-po-05v.sys.comcast.net ([96.114.154.229]) by resqmta-po-04v.sys.comcast.net with ESMTP id 7nBsiDJH8fDlH7ot0iYRgM; 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=DkQJKgDvcjON5UIkEfnxHaGwPZTSkew/WObvVj31QKMM7regQ/cscDWVpV/mSnj2b lNk+f4J4FfHdk3ZgqiBXJD3mpf8WRQXghBNYbT/l9+fskvUzYz7y74nswUmdzW79cg pZhrGD0Fll9MPXkDnQfn65p0oo4/QGhx9VtrEcHmVGBx6lKnpx6A/Ot1ex5WK7IrVk bKBqwicI39OQ0cAXdiJL6BhNZ2Ti0V/KAUVOtPqx8AbnixDP+eyWCBPx3YmvNq0tRx Qe0xIH3xVS/xhbRVW6IiO+fiajZ6OkONOjzMgNf16N3HHT03H8qLvjDC3qpQH76f7R PqkZ+J5XikwcA==
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
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-Language: en-US
Subject: Re: [rfc-i] Try this: was Re: New proposal/New SOW comment period
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-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

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

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest