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

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Fri, 06 September 2019 14:17 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
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 D3B97120C02 for <ietf@ietfa.amsl.com>; Fri, 6 Sep 2019 07:17:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) 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 ChF2Txw9puRT for <ietf@ietfa.amsl.com>; Fri, 6 Sep 2019 07:17:44 -0700 (PDT)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADBC7120C37 for <ietf@ietf.org>; Fri, 6 Sep 2019 07:17:43 -0700 (PDT)
Received: by mail-lj1-x22d.google.com with SMTP id y23so6146225lje.9 for <ietf@ietf.org>; Fri, 06 Sep 2019 07:17:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PBek1BZVb/GOXm1yKo/L0wV+hYwbQKaFzm0R8Qb42o0=; b=f3szxmyGiuJ9O2kHrPdC1gQRcbLwJE/Wh1mvgIlFe2dMZkkCUAly3KZb/JJfsw4GoX caZD0wtniEGuuI7tG1rYwbgVSmQCZQ+VWioZJE2GPbImMjtKx9cwMxJXvkcGC17reXXM tjJ84jD1bm2uoXifQa9cesmh1tzUhwHCzoNpaiDunYTNvCzox5eL921KM/I4igO68HPx 3qSEXq+ZVAxb3eYxN47Pw5x0e1MxM4s8E05pSWe8v6Cyrv6nDjbqQ6BPDRxhVmUmqj4H 59pbyvRvvRhPCZnQQ9u0VRqStSYcP0nFfuJ2U9laUkUb3VE6vxKF/+AwRZNE7OcWxfSY t5IQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PBek1BZVb/GOXm1yKo/L0wV+hYwbQKaFzm0R8Qb42o0=; b=lL+u9tAD04CsU0K+bmyGZtu4QNwSRyAkr5R3c0ZoGL7Ejvb33cbW1IXRdgXp8YXRlU Glmq7h4BRjGpZpGzXVOg566D0ibIKx9pqrN3PuVYdUaHKbhKID7arHaf2YQFuooxkYp5 NrCuFphI7MowpBkw1GRPrvilqjDPrm4I4+uwkuAZO0k4DZd/FyEiE2PUGl/MqF8T2U69 fSX0li0Bxlp9XbQ0EX8vA6nfntr2xcTAtyxwhZOWePed4IhQBqgzpWwBglNabqKL1KiR 8i3eykslSMqHvBJ8etImUt3goj4HdjUvpSY4vX8/C1+2cjTyxO03wOgP/vN3dnxkMKBH 1zrw==
X-Gm-Message-State: APjAAAVKE0s/gikUUj8N4x40HhB8ZS1gGqfHii+fHYUSawvEa+Mr+YeO XOup+ELvS1vtAenjagW9ZtrVBO11H5YBepilv3w=
X-Google-Smtp-Source: APXvYqxIQTVCrSCMhZgHrK3aEMTmTEnQrC3jhCtwKeCDxtAQF9yb97KZhchteVLcJnIWjMiQiWjWAYeRdDhqzVNH9Zk=
X-Received: by 2002:a2e:85d7:: with SMTP id h23mr6156374ljj.129.1567779461825; Fri, 06 Sep 2019 07:17:41 -0700 (PDT)
MIME-Version: 1.0
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> <887FE348-A7EF-413C-B5F4-5A7910CAE762@encrypted.net> <68c20034-b6d1-fe3f-ccab-d0be7c5c50c2@comcast.net> <F053268C-D31B-4620-A342-E99837C75182@encrypted.net>
In-Reply-To: <F053268C-D31B-4620-A342-E99837C75182@encrypted.net>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Fri, 06 Sep 2019 09:17:14 -0500
Message-ID: <CAKKJt-f98ahOnMS16yE4oz1gP4uK6DzMwBkjif2gUiRC6a5F9Q@mail.gmail.com>
Subject: Re: [rfc-i] New proposal/New SOW comment period
To: Sarah Banks <sbanks@encrypted.net>
Cc: Michael StJohns <mstjohns@comcast.net>, rfc-interest@rfc-editor.org, IETF list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e8887b0591e3194c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zT1k8IGQpakFvXEDkDt1RPg0rVU>
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: Fri, 06 Sep 2019 14:17:47 -0000

For what it's worth ...

On Thu, Sep 5, 2019 at 10:39 AM Sarah Banks <sbanks@encrypted.net> wrote:

> Hi Mike,
>
> [deleted down to]

> You have basically three classes of deliverables:   One-time (or one-time
> with phases - finish the V3 transition for example); recurring (e.g.
> quarterly project reports), and continuous (technical expertise as needed,
> RPC oversight etc).  Only the first two allow for a reasonable fixed price
> bid.  The last one is going to need something like "For approx 10 hours a
> week, plus full time 3 weeks out of each year commit to provide technical
> expertise in the following areas to the extent possible for the allotted
> hours; increases or reductions in negotiated time commitments may be made
> by mutual written consent".
>
>
> I wasn't trying to be facetious, simply acknowledging that you've stated
> your opinion. We'll review all the comments that come in, and thank you for
> sharing it. I'm not sure how else to put it, but I also acknowledge that it
> sounds cheeky, even though that's not at all how I mean it to be.
>

I'm not a likely candidate to bid on the temporary position, but I have
been a consultant working under contracts since 2016, and I've been looking
at this thread and trying to imagine what likely candidates must be
thinking about whether, and how, to provide bids.

Mike's three-way split seems very helpful to me (and I'm not surprised,
because he has much more experience bidding on contracts than I do).

And I recognize that "do the right thing" is better as guidance than as a
contract deliverable.

Thanks,

Spencer