Re: RSE Bid Process

Sean Turner <sean@sn3rd.com> Thu, 04 July 2019 03:12 UTC

Return-Path: <sean@sn3rd.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 E0D8C1202AD for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2019 20:12:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.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 noLxCA7sDsFm for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2019 20:12:42 -0700 (PDT)
Received: from mail-qk1-x729.google.com (mail-qk1-x729.google.com [IPv6:2607:f8b0:4864:20::729]) (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 161F6120176 for <ietf@ietf.org>; Wed, 3 Jul 2019 20:12:42 -0700 (PDT)
Received: by mail-qk1-x729.google.com with SMTP id 201so2408908qkm.9 for <ietf@ietf.org>; Wed, 03 Jul 2019 20:12:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=n6rGaGjDyN9QuEbyFq3QJnnzYAsm0hLUfXIKjvrxKtw=; b=U5D8DcydDDwqjbMwuHPkq9IUm3aA7cqH+vA294AZ0uRMvBMeWfJrFMCVN7lyzAzfNE I5Kj91/Bw0IvIPVpYlS/UtoEnJFgtA4O4zBdmzWBH3roniwq/H4swJzHe1oorNZwbanS oA7Oouh2X4XZ4iioOCoG/5HjJKAaPafnDUVyk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=n6rGaGjDyN9QuEbyFq3QJnnzYAsm0hLUfXIKjvrxKtw=; b=VtL7jiYMeN/C5nLOTvM5DDJnjh+Pw0p+qN9vyHi65m6/8sIZnXKxs+GOKhJD7P2D3Z OMcmVYzuxk/i8cete8MeqpI+35Uha0J8T5ZD6og5DIpkhb4URur5y1epMKfME7QfYK6L Rks8xJ/HUnIyez97PjlWd5y4rKbJ/3joUvGK9JdYi2Ebo6Q6h2L8oZVpsMWcRKUSlihj vRMKJURCXg9jSxLowOncnCYWvy96yjFy15TbeD+wmbqM+qfceDve5qMgwj9Tre0KkDjR F6iVe9qMycL0vMtu3ieBNfZ2h83y2ginDbtNloE2UThdzKSfH92xODDz9T0bQVriqIVJ vCPQ==
X-Gm-Message-State: APjAAAW8sidSpgRpmMZKgdnKrVJ1SEEoHvK+C4xgFohgqS41B8b1NE/6 bWMpVAsN2EiAM0+fVNyy3a5zIw==
X-Google-Smtp-Source: APXvYqzB8Uz6GRRkugaUrk8/Bxo1iC0nKxewsCwESmXwM9DEeM5EizvQ8j9ewamzYtSjy11uJp2Kbw==
X-Received: by 2002:a37:a6c9:: with SMTP id p192mr35091865qke.184.1562209961182; Wed, 03 Jul 2019 20:12:41 -0700 (PDT)
Received: from sn3rd.lan ([75.102.131.36]) by smtp.gmail.com with ESMTPSA id j22sm1699954qtp.0.2019.07.03.20.12.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Jul 2019 20:12:40 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: RSE Bid Process
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <CA+9kkMALnyeoMJKOgwZ8QP1G+aeSTSBbu4HXAAxdyhcC0K=mDA@mail.gmail.com>
Date: Wed, 03 Jul 2019 23:12:39 -0400
Cc: IETF <ietf@ietf.org>, Internet Architecture Board <iab@iab.org>, rsoc@iab.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <4EC772F3-69D8-4D7E-867E-D1434B4D3EB7@sn3rd.com>
References: <CA+9kkMALnyeoMJKOgwZ8QP1G+aeSTSBbu4HXAAxdyhcC0K=mDA@mail.gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SjUwgdhvj71j_EEceXfS3tVR2EA>
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 03:12:44 -0000

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?  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?

spt