Re: RFC Series Editor Resignation

Richard Barnes <rlb@ipv.sx> Wed, 19 June 2019 15:00 UTC

Return-Path: <rlb@ipv.sx>
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 894E71206B1 for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2019 08:00:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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=ipv-sx.20150623.gappssmtp.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 1nGEmPFk0U0L for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2019 08:00:53 -0700 (PDT)
Received: from mail-oi1-x22f.google.com (mail-oi1-x22f.google.com [IPv6:2607:f8b0:4864:20::22f]) (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 1257812051F for <ietf@ietf.org>; Wed, 19 Jun 2019 08:00:46 -0700 (PDT)
Received: by mail-oi1-x22f.google.com with SMTP id w7so10811596oic.3 for <ietf@ietf.org>; Wed, 19 Jun 2019 08:00:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=h8cKX50F/oNnDsgqCj4GkZfYOG2mQSMmu/7xPfWQZUM=; b=RPdkkMIAxp2aiQ2e1e1svTKlYuo6noD/6zvHLGyS3LIUQxB8VpTuxnrjjcw7iBtLLG mKsDLrBW8UXgt53y1rbCgOYXDUPjCg5P3fGv+zBMPi2n8omJePy8nVl8BtcBzVEWeqLV Vsy8Ik6jGYRZkwvvZcVz0Q7PO4OYCuB3oKKfOwiuY70TisWkIHQUovrD2zNSi9v5X9PJ ihrGn5J3QXARjNKHbIE7XhUmnIfES6vbSB5AJSYy2DJCWadg5dXChhUfqhuQ76n2xxWw w95/VFpfFi3SuuQg11QsA0ghU/STJJbafEJySeNzTVeM0m5wEKXs4uYAViXept+Kl58r 9adA==
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=h8cKX50F/oNnDsgqCj4GkZfYOG2mQSMmu/7xPfWQZUM=; b=GD5CvUsE1j7vXJc1zwc701AgcGYRe7ioK+AUaiFlOedBzTfchp/Xnzvq6zWe2qmV1d //1hZyUO6HcmjzBRlpZ3xJjh+HFHs91V9spNTY/EMjK6JQ9gVKuhi2lvPqggVh/VTiDe uVRiCStem9Atd+CNa2m7M4NAo3bZNgxUNzcQ9t3hCCKkY4uTI0rLPDLfRmSsT6HVmC46 dUN+/WqqC4CIfIo1KRvv5t8aH+QcvWoMqFv7pDdGtu+SkSBnltDjRoeQdVov0vlD99pu jG+wMVs3M2oXND0x5U7e1zjNcmGO55UG3y2xm7XJ+TTPzhb7TlwbNUsypN1wthCOeI/m 6sJg==
X-Gm-Message-State: APjAAAU3PSsQ/bJhjQMkTfA7yvOAuJvttypdxoUv6513iNBUMqfFMpK7 wgsrJhfbzafTvgSnXxjHL3QFYYsYV4RK6yg7LhlbIQ==
X-Google-Smtp-Source: APXvYqx3CNuxkP+d4sT5ZII1/zt9JtrQ96iZ+lrSSTLSokWm0R2h7OLxCVpH2ga7vxUUkuFYKKTDmwkU1kRYNDiiTag=
X-Received: by 2002:aca:f1c4:: with SMTP id p187mr2576104oih.149.1560956445224; Wed, 19 Jun 2019 08:00:45 -0700 (PDT)
MIME-Version: 1.0
References: <685B34F6-E0E2-4050-B9DD-615F475F62B7@encrypted.net> <e9d747d0-a708-7bfa-f090-d0454344e782@levkowetz.com> <cc4c0ed5-dd1b-9eda-a294-e8e7c53ccb09@gmail.com> <CAJU8_nV_ReguCcV=pHZYqxH6DNNuqKfVKN7+Sp1sWr1nyaXrcw@mail.gmail.com>
In-Reply-To: <CAJU8_nV_ReguCcV=pHZYqxH6DNNuqKfVKN7+Sp1sWr1nyaXrcw@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
Date: Wed, 19 Jun 2019 11:00:33 -0400
Message-ID: <CAL02cgThZeSw-P-6pLA9JxO-aQwQAFqz5UDHY3=uT7TDfKhE4Q@mail.gmail.com>
Subject: Re: RFC Series Editor Resignation
To: Kyle Rose <krose@krose.org>
Cc: "Stewart Bryant (stewart.bryant@gmail.com)" <stewart.bryant@gmail.com>, IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006dadb4058bae7e2b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qvYYhbBuXb-g-hMl0c-RvCZtBfs>
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, 19 Jun 2019 15:00:58 -0000

People are entitled to comment, but it might be nice not to create
unnecessary drama by micromanaging the RSOC and LLC's contracting process.
The point of delegating administrative support to these groups is to let
them worry about these details.

For my part, this seems like totally normal business.  The parties are
exercising the rights they're entitled to under the contract, to extend /
re-bid or to terminate.  That's why these provisions are in the contract.

It would be more productive to focus on the future, and provide the RSOC
with input on their selection of the next RSE.

--Richard

On Wed, Jun 19, 2019, 10:35 Kyle Rose <krose@krose.org> wrote:

> On Wed, Jun 19, 2019 at 10:26 AM Stewart Bryant <stewart.bryant@gmail.com>
> wrote:
>
>> I really do not think that this is a discussion that should take place
>> in a public forum like this.
>>
>> There is much that both parties may legitimately wish to keep private in
>> situations such as this.
>>
>
> The involved parties are not required to comment, but as this is an event
> that impacts everyone at the IETF, this is 100% appropriate for discussion
> on this forum. I further guarantee that this will be raised at the next
> meeting plenary if adequate explanation for "refining [the] RFP process" is
> not offered beforehand.
>
>