Re: letters from Ted & Alissa

"Theodore Ts'o" <tytso@mit.edu> Thu, 04 July 2019 00:30 UTC

Return-Path: <tytso@mit.edu>
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 B8E461200D7 for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2019 17:30:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-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 QjHNPHMHxm5P for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2019 17:30:43 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 9F71812007C for <ietf@ietf.org>; Wed, 3 Jul 2019 17:30:43 -0700 (PDT)
Received: from callcc.thunk.org (guestnat-104-133-0-109.corp.google.com [104.133.0.109] (may be forged)) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x640Udbe006000 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 3 Jul 2019 20:30:39 -0400
Received: by callcc.thunk.org (Postfix, from userid 15806) id D9E7A42002E; Wed, 3 Jul 2019 20:30:38 -0400 (EDT)
Date: Wed, 03 Jul 2019 20:30:38 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Nico Williams <nico@cryptonector.com>
Cc: "Scott O. Bradner" <sob@sobco.com>, IETF <ietf@ietf.org>
Subject: Re: letters from Ted & Alissa
Message-ID: <20190704003038.GA3059@mit.edu>
References: <CA+9kkMCi=h1W15T-rt3MAu3NHBYdEaycUPw4XhRDBVNL4k_Xrg@mail.gmail.com> <BB4BA38F-B384-46A3-866C-4A61F4C7C681@sobco.com> <20190703205108.GD3508@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20190703205108.GD3508@localhost>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3mc9r8Q3Yh_QPJqDROFeN6y3Itg>
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: Thu, 04 Jul 2019 00:30:46 -0000

On Wed, Jul 03, 2019 at 03:51:10PM -0500, Nico Williams wrote:
> Sarah Banks wrote a post that explained some of this.  It was enough
> that I can see how RSOC might *not* have thought that the RSE would take
> early bidding the way she did.  Perhaps it was all a big failure to
> communicate rather than RSOC's failure to understand that it was
> essentially telling the RSE to get lost -- perhaps it was even a failure
> on the RSE's part rather than RSOC's.

What I haven't seen for an explanation was why did the rebid *have* to
happen in 2021.  The answer of "it's was too soon to do it in 2019" is
the best that we've heard from Sarah.  What I don't understand is why
couldn't be 2023?  What was so urgent, what was so terribly defective,
with the reprevious RFP bidding process that we have to do the re-bid
in 2021 and it couldn't wate for 2023?

The only answer when that question was raised, was the following from
Sarah:

    I’m trying to understand why the RSOC is being belittled like
    this. Help me understand. We don’t need an excuse.

Which to my mind, is non-responsive, if not downright defensive.
There also seems to be an strong belief that the RSOC is not obliged
to tell the community anything: "we don't need an excuse".

Perhaps there was some secret personnel reason that couldn't be
disclosed, and so that might be a reason why some of RSOC's decisions
have to be shrouded in secrecy.  However, I read Ted Hardie's e-mail
as saying that he didn't believe that to be the case.

In which case, inquiring minds really do want to know --- what was
causing people to believe this *had* to be done in 2021 versus 2023?
And how long would the bid process the RSOC was imaging would take?
Was it such that the RSOC had to make a recommendation in 2019 so that
the rebid process could be done by 2021?

				- Ted