"Early rebid" (was Re: letters from Ted & Alissa)

Andrew Sullivan <ajs@anvilwalrusden.com> Wed, 03 July 2019 22:14 UTC

Return-Path: <ajs@anvilwalrusden.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 A35B412016D for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2019 15:14:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 (1024-bit key) header.d=yitter.info header.b=NneMYvEr; dkim=pass (1024-bit key) header.d=yitter.info header.b=Ut+q0N1O
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 qyqXBJSvJ5ec for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2019 15:14:48 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF4391200D7 for <ietf@ietf.org>; Wed, 3 Jul 2019 15:14:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id A17ACBCCE5 for <ietf@ietf.org>; Wed, 3 Jul 2019 22:14:47 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1562192087; bh=g7wJuh0BjUHSoDRq9VlXu9AMHV9M+NBtUrkZPN6hPgM=; h=Date:From:To:Subject:References:In-Reply-To:From; b=NneMYvErtN5ndJ2TmLOdxqnOuij9Dtfh8uxjEhhR+OO+2g+359nWO3AsNbF4RfXwS qzSDHkr/wi1CKno3vDobBUn0a8nQiPAGkTH2gge43VCFUgOZsGkvOG4TKptYmroXVg ZJIoxwdR4BNgVRUKGIDJtaRdvRvZlv9rw15y9ESk=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1oG76BaSWbms for <ietf@ietf.org>; Wed, 3 Jul 2019 22:14:46 +0000 (UTC)
Date: Wed, 03 Jul 2019 18:14:45 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1562192086; bh=g7wJuh0BjUHSoDRq9VlXu9AMHV9M+NBtUrkZPN6hPgM=; h=Date:From:To:Subject:References:In-Reply-To:From; b=Ut+q0N1O4cALnHpgD8XMjstezAEaoakovODxOY+xbTRTh9HHNJ/+kAOsSwj9CC4es UJtEsn2ihdda2M906QQ0zb8mS6KqTFsjl6g0RFUn0AyO7FRozti/yEWOUlMu04lcTi pJAC1Qarqxup51bmP7kS6AdbAyhLYtoB5QTI8UOw=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: "Early rebid" (was Re: letters from Ted & Alissa)
Message-ID: <20190703221444.fvweit2qwmo5u4jp@mx4.yitter.info>
References: <CA+9kkMCi=h1W15T-rt3MAu3NHBYdEaycUPw4XhRDBVNL4k_Xrg@mail.gmail.com> <BB4BA38F-B384-46A3-866C-4A61F4C7C681@sobco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <BB4BA38F-B384-46A3-866C-4A61F4C7C681@sobco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QZ2f9ixijQt0kjMB6fphSDgmmVk>
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, 03 Jul 2019 22:14:51 -0000

Hi,

As usual, I'm employed by ISOC but not speaking for it.

On Wed, Jul 03, 2019 at 03:32:44PM -0400, Scott O. Bradner wrote:
> 
> 1/ why did the RSOC decide to a/ rebid the RSE contract 2 years early & b/ decide to tell the world about it a further 
>     2 years earlier

Of all the things that I have found puzzling in this discussion, the
persistence of this description is the one I find strangest.

First, as I understand it, the RSOC is not in a position to "decide"
anything.  In any case, the discussion around IASA 2 made it pretty
clear that there were many moving parts in the RSE relationship, and
that it was going to need to get straightened out.  In such a context,
it is not surprising that we'd expect a revised structure and,
therefore, a revised basis for the contractual arrangement once that
revision was developed.  Yet it is not developed _yet_.

Now, speaking as someone who has a contract that might or might not be
renewed in 2 years' time, I find it _extremely helpful_ to know about
that possibility.  It's an elementary part of good planning to know
when contract events are likely to happen.

So, without any special knowledge and just relying on what is public
and what I know of other discussions around the IETF (again, from
public lists), it seems to me that the RSOC made the only plausible
recommendation under the circumstances: renew the contract now, for a
2 year term.  But moreover, in the interests of transparency, make
sure that everyone understands that there probably will be some new
working basis in a couple years, and that a re-bid would be
appropriate then.  That doesn't make this "early" or a "termination"
or anything like that.  It's just standard good-will practice.  (Also,
given all the accusations of lack of transparency, I find it somewhat
ironic that one main problem was a surfeit of transparency.)

Now, of course, I don't know what was on the mind of the RSOC, and I
think it would be an exceptionally bad precedent for us to start
discussing these sorts of issues on a public list or with anyone not
involved in the contractual chain.  But it seems to me the entire story
is possibly explained in an utterly ordinary way, and that one main
lesson is that complex supervisory arrangements lead to convoluted
communications paths that increase the chances of misunderstanding.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com