Re: RSE Bid Process

Ted Hardie <ted.ietf@gmail.com> Thu, 04 July 2019 04:12 UTC

Return-Path: <ted.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 1FD391200C7 for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2019 21:12:30 -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 5hW-NFCmTrNw for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2019 21:12:28 -0700 (PDT)
Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (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 ACA32120176 for <ietf@ietf.org>; Wed, 3 Jul 2019 21:12:21 -0700 (PDT)
Received: by mail-io1-xd2c.google.com with SMTP id g20so419332ioc.12 for <ietf@ietf.org>; Wed, 03 Jul 2019 21:12:21 -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=zdbvdkRug3/BJ2zPhywweB2UqVhiXo4OKpjVDXN4rfk=; b=nLol+JB+MBl2xWGQ3Q2HSFLiTQPKCziTeo/58YmwWfnNhCxUFPcq2dQemg9CNkCNc9 SQ/Bt1VL+F8MFG1lsKoBfsLCJ0/UDVmU/wERrPfjBPIBNOdsGt9f4B5tkasXSb4q18YS b+Oc6S9uiS0YrOM5XomlcCIvHbi2p0Db2vtDC7rosUAWlfmcDtKL3btxNvypbUJZSZ7E N8bwlCbfFYeWiuNjMqIySkJC6PVXz5i8VkHa5+IdT9mmDDibKMMzi+37qAfJFEi7cjSi z2COL7vv66slWTVcF3z8drsBOW5snw0OTSaOIgm9KEpMKjkXFk9g+xMHX0ObSNaxLsex w4kw==
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=zdbvdkRug3/BJ2zPhywweB2UqVhiXo4OKpjVDXN4rfk=; b=KbJiEfEDF4o+CmVReMXxaffiXxGpWdm9Pa0OtjqriNl6q1VMN9qjLbWWfaZOuqSCQy ZfavUMKx/X7t5NsEg0SAd09Ul1cqKAeFltOv5tjsrSoGvUzGBbEgXLvWOrNe6JEtB32v RsQy1XQyHynPSVo5K1R7VkJboUs+Qt6mB/xUy7dN2AXbevpuWbUg0ZWcF4Ox1/7A9bAa hX5zEwD2Uhn2sKCKj1dqnJR/qRpnKQeN9DClnMcpKmdrkwvyVNcCusn1DcPdZKBLMkMG kPmhHoidZnwaymqFlrKyGVvno6LFJw0nt7NJaarqB9HgVgHZnr0zJONKRSpa3XZiEuvR gr9A==
X-Gm-Message-State: APjAAAW54oFYb/xTeQGjT4EFiIPH/QmjHmbEFaqw2Rh1YkXoe4u2PzkI FLW43ZPuVYSQAwANxmcwcFPbZWB53jSxdwpw8Ag=
X-Google-Smtp-Source: APXvYqye54DEoYxTLL+Hn10fNhMklBcmEO4UIsS5/KXTDZ1TSlzd1RA9pcmzH02hC8fFKOWxxOHg0uJzBdP5KYDL3K8=
X-Received: by 2002:a6b:e00b:: with SMTP id z11mr5852756iog.27.1562213540810; Wed, 03 Jul 2019 21:12:20 -0700 (PDT)
MIME-Version: 1.0
References: <CA+9kkMALnyeoMJKOgwZ8QP1G+aeSTSBbu4HXAAxdyhcC0K=mDA@mail.gmail.com> <4EC772F3-69D8-4D7E-867E-D1434B4D3EB7@sn3rd.com>
In-Reply-To: <4EC772F3-69D8-4D7E-867E-D1434B4D3EB7@sn3rd.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 03 Jul 2019 21:12:01 -0700
Message-ID: <CA+9kkMBKftmrApL7um0uLe0oy=_ah7aw24XHbxWt+gxYP39rqQ@mail.gmail.com>
Subject: Re: RSE Bid Process
To: Sean Turner <sean@sn3rd.com>
Cc: IETF <ietf@ietf.org>, Internet Architecture Board <iab@iab.org>, rsoc@iab.org
Content-Type: multipart/alternative; boundary="00000000000029d709058cd32f31"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/t6sahwQswLpLnKgNt3qaWHy6cNA>
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 04:12:30 -0000

Howdy,

On Wed, Jul 3, 2019 at 8:12 PM Sean Turner <sean@sn3rd.com> wrote:

> Ted,
>
> > On Jul 3, 2019, at 15:02, Ted Hardie <ted.ietf@gmail.com> wrote:
> >
> > 4) The RFP is issued by the IETF LLC.
> >
> > 5) The RSOC, or a committee formed from within the RSOC, reviews the
> proposals and interviews candidates.  Depending on the number of candidates
> this could involve steps for creating a short list before running
> interviews.
>
> I just want to make sure that when an RFP is issued that it gets in front
> of the right set of eyes.  I am also very likely being pedantic.
>
> Should there be a step for advertising/distributing the RFP?



>   And, if there is, then who is to do that?  Or, Is it implied that
> “issue” means advertise/distribute?


I think in the docs I was working from (mails from Ray, etc.) that was
covered under "is issued by".   Depending on the complexity of the search,
though, there could be several actions underneath that (advertisement,
search firms, etc.)


> And, if it is the case that it is implied then I hope the RSOC will
> provide a list of locations to advertise/distribute notice of the RFP to
> the LLC?
>
> Soliciting potential locations seems like something we could also do
during the public comment period.

regards,

Ted



> spt