IETF Logo Mail Archive

Re: RSE Bid Process

Patrick McManus <mcmanus@ducksong.com> Thu, 04 July 2019 14:08 UTC

Return-Path: <mcmanus@ducksong.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 2E1E4120046 for <ietf@ietfa.amsl.com>; Thu, 4 Jul 2019 07:08:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ducksong.com header.b=dbbCtfI5; dkim=pass (2048-bit key) header.d=outbound.mailhop.org header.b=WssqzMVs
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 J9P_za0WVw9Q for <ietf@ietfa.amsl.com>; Thu, 4 Jul 2019 07:08:55 -0700 (PDT)
Received: from outbound1g.eu.mailhop.org (outbound1g.eu.mailhop.org [52.28.6.212]) (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 CD2DD120043 for <ietf@ietf.org>; Thu, 4 Jul 2019 07:08:54 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1562249333; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=WW49ljZeJR0Ya4v9WxepELJQhqjyyUN6Y2PIDIsPNowoHWd6KpFq9P1hXnWTkWt4PGYQ2m4sClMSa Mjy0MdzE4uKKGXkgHgnb54b/t855z1ztaoN1NwQYJJHyAU/313w7KNllHfmcfvKVQYZ4h8f8XvZ9aR 1edjRa7D+Fr7JeB+3iZeUjbxjv20MmEmgoe2UBLX3jqbWSeSf42l+G6gv47t1+BgbYPcqA1cuOQNp9 uw5zNMG2PJ+quV8FGj9dyE/zqSnb35rgKyZWH5SauP/K1tIfDsE+aWCsTjzclURBnyU255CiyokjXs gFZZfHKX2k2NpaankLHU5D+58O8rrIA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:dkim-signature:dkim-signature:from; bh=UZo0T/E+CBIfE2iscK2aJdqpmYpa5XpcMGPXxiFA9/0=; b=C3bygOwcjDhgRV2iLWVdyUCd0Ejtr5SwSx5M39brfvVh4BtFWYtLS3MTBKYQXkyJ4TcHY+O83uBhs GpQVvoh/pph/ZEK6AS/jIadJ37In0L8zQb7wHLZgqWkP8czLnSL3f/ojhXfN+FdVqV/yQ5spEjVEay J7p6ilBN3/kzyol5SiTqbK3s2T8YR3hJQxJNZZtPEzbBaRLoEj0esGBk0cHoOUQkARxkuFBC0p4yjS J8d+T0yGP8GHj5Zja1IxIwWWgNRyILCsJEI5yO7ki8Cjq2lut9S2XBkf7ikQKXnl+1ZcF8MuNznvu9 NalIe6cpuUl2+Njbpnz9HMVlsH7GNiQ==
ARC-Authentication-Results: i=1; outbound3.eu.mailhop.org; spf=pass smtp.mailfrom=ducksong.com smtp.remote-ip=209.85.210.44; dmarc=none header.from=ducksong.com; arc=none header.oldest-pass=0;
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ducksong.com; s=duo-1537391512170-ea99bbb3; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:from; bh=UZo0T/E+CBIfE2iscK2aJdqpmYpa5XpcMGPXxiFA9/0=; b=dbbCtfI5/71QVTbAqe1Z3KfjCoipC9oFWZ8QVDYACjZ8HododBtgfOno7HgWkgTzZbLM45SYZXCW9 OkCqK3ufZ26/OwSMm8/flheMY5ZM2C+oDSWA/FPtnKoR/tBldWTLtuFmJR7GguNNCx3xzB+8Z/8wCg Toi+5tpIeIfRFxmI=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:from; bh=UZo0T/E+CBIfE2iscK2aJdqpmYpa5XpcMGPXxiFA9/0=; b=WssqzMVssCse/H6+L2fucguQciOgM5YZ4t3jFuqlF9CgHuBxUKa5lMr6XzarBZB/cYBPyKut6HR0O J6FqwgRBVX0QfWdgrQdLrBoV44wc44TM4zIr5qQN9RzVGfREf/b0ILqXBlnuR5rt1FgxxDVtHMcKz9 R46mwq6mS6yRLpKSrZ8rJfWgQOko7DpliulI+bwr3lEmSk8dNlEbHSWI0ef6wzo4Kv+TMYKb7DoriC mOvukG3Q6GWUkiPa9ubl/Unm51qLtvSpHmXzuVOUpnc1wUpfX3U6z5rqjKYEtbzmo9MXZp4Ra7Rfnb HTPJg/Wupted3dVhVnhVtF96+7OqcRQ==
X-MHO-RoutePath: bWNtYW51cw==
X-MHO-User: 3f7d6bf2-9e65-11e9-817d-159144fdaaa6
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 209.85.210.44
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from mail-ot1-f44.google.com (unknown [209.85.210.44]) by outbound3.eu.mailhop.org (Halon) with ESMTPSA id 3f7d6bf2-9e65-11e9-817d-159144fdaaa6; Thu, 04 Jul 2019 14:08:51 +0000 (UTC)
Received: by mail-ot1-f44.google.com with SMTP id r6so6097480oti.3 for <ietf@ietf.org>; Thu, 04 Jul 2019 07:08:51 -0700 (PDT)
X-Gm-Message-State: APjAAAXEa6xLmHtLbkXLgGSFETWqnSTm636wrXBBqIuMshy53bahNo3k QmGzwaVsFnNoS9Cj/vX6XOws0GT8VHEvo+NuqZA=
X-Google-Smtp-Source: APXvYqyLYrfYm/c4D2fHdNGsfkDIT6gGY3l93bzBZ1S7g9ZhTSbwlMvsYe/Xt5t5g2vr/FF+nmW0MmcVOvUoP0IktZI=
X-Received: by 2002:a9d:7cc7:: with SMTP id r7mr34830625otn.340.1562249330340; Thu, 04 Jul 2019 07:08:50 -0700 (PDT)
MIME-Version: 1.0
References: <CA+9kkMALnyeoMJKOgwZ8QP1G+aeSTSBbu4HXAAxdyhcC0K=mDA@mail.gmail.com> <a5357fbc-ebf5-e148-c88d-f7803cdbcc9b@comcast.net>
In-Reply-To: <a5357fbc-ebf5-e148-c88d-f7803cdbcc9b@comcast.net>
From: Patrick McManus <mcmanus@ducksong.com>
Date: Thu, 04 Jul 2019 10:08:39 -0400
X-Gmail-Original-Message-ID: <CAOdDvNrw5WjjUCDbK7Vn32WyUwA8fNO4O9W0etA5gLZxN_HMMQ@mail.gmail.com>
Message-ID: <CAOdDvNrw5WjjUCDbK7Vn32WyUwA8fNO4O9W0etA5gLZxN_HMMQ@mail.gmail.com>
Subject: Re: RSE Bid Process
To: Michael StJohns <mstjohns@comcast.net>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000062b7a2058cdb8475"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5IqtmSe7g5MAkn-8zS5ABeE-cGY>
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 14:08:57 -0000

On Thu, Jul 4, 2019 at 9:12 AM Michael StJohns <mstjohns@comcast.net> wrote:

> Patrick's note is on point.   Unfortunately, figuring out how to fix those
> relationships,and getting agreement is probably not possible in the next
> 2-3 months.
>

While it would be optimal to have a RSE in place in January, I don't think
its absolutely necessary. The day to day operational work of making the
RFCs flow can be carried out by the RPC. Obviously the remainder of the RSE
portfolio is important, but is less operationally crucial day to day. It
makes sense to me to get the strategy right before starting a new
relationship -- a temporary vacancy is a tolerable cost to pay. This is
triple-y so if the community views this as a defacto 6 year arrangement.

v2.23.0 | Report a Bug | By Email