IETF Logo Mail Archive

RE: RFC Series Editor Resignation

"Roni Even (A)" <roni.even@huawei.com> Thu, 27 June 2019 06:06 UTC

Return-Path: <roni.even@huawei.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 728F3120137 for <ietf@ietfa.amsl.com>; Wed, 26 Jun 2019 23:06:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 hObH4Cvb5_lQ for <ietf@ietfa.amsl.com>; Wed, 26 Jun 2019 23:06:14 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 93685120127 for <ietf@ietf.org>; Wed, 26 Jun 2019 23:06:14 -0700 (PDT)
Received: from lhreml706-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 338358F177DF8F3A0053 for <ietf@ietf.org>; Thu, 27 Jun 2019 07:06:12 +0100 (IST)
Received: from lhreml712-chm.china.huawei.com (10.201.108.63) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 27 Jun 2019 07:06:11 +0100
Received: from lhreml712-chm.china.huawei.com (10.201.108.63) by lhreml712-chm.china.huawei.com (10.201.108.63) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Thu, 27 Jun 2019 07:06:11 +0100
Received: from DGGEMM403-HUB.china.huawei.com (10.3.20.211) by lhreml712-chm.china.huawei.com (10.201.108.63) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Thu, 27 Jun 2019 07:06:11 +0100
Received: from DGGEMM526-MBX.china.huawei.com ([169.254.8.116]) by DGGEMM403-HUB.china.huawei.com ([10.3.20.211]) with mapi id 14.03.0439.000; Thu, 27 Jun 2019 14:06:08 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: Sarah B <sbanks@encrypted.net>, IETF Discussion <ietf@ietf.org>
Subject: RE: RFC Series Editor Resignation
Thread-Topic: RFC Series Editor Resignation
Thread-Index: AQHVJikcvJZ89zMwnUmJa+NZ2rvccKavDe4w
Date: Thu, 27 Jun 2019 06:06:08 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD18D3A5CF@dggemm526-mbx.china.huawei.com>
References: <685B34F6-E0E2-4050-B9DD-615F475F62B7@encrypted.net>
In-Reply-To: <685B34F6-E0E2-4050-B9DD-615F475F62B7@encrypted.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.202.60]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MvOEQ30Hloe8jpSYM6xDiGRLfLk>
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, 27 Jun 2019 06:06:17 -0000

I tried to follow the long email threads that followed this announcement. I do not think we need to figure out who is right and what we should have done, maybe only as a lesson learned . 
In my view, this is a case of not being right but being smart and I hope that RSOC took into consideration that the result of this decision will be the resignation of the RSE and has a plan.
I also hope that RSOC/IAB/... and whoever is involved in the processing of getting a new RSE will do it in a timely manner since having an RSE is important for us.

Having said that I would like to thank Heather for the work she has done as an authors of a couple of RFC.

Roni Even 

-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Sarah B
Sent: Wednesday, June 19, 2019 1:56 AM
To: IETF Discussion
Subject: RFC Series Editor Resignation

Hello,
	The RSOC, as required every two years, recently undertook a review of the RFC Series Editor contract, the base term of which is scheduled to end this year.   Although the RSOC had recommended renewing the RFC Series Editor (RSE) contract for another two years, and then put the contract back out to bid in 2021 expressly for the purposes of refining our RFP process, Heather Flanagan, the current RFC Series Editor (RSE), has informed the RSOC, IAB, and IETF LLC that she does not intend to renew the RSE contract, which is set to conclude at the end of this calendar year. She has indicated that she is willing to work through a transition period in the first months of next year, to support a smooth hand-over of duties to a new RSE.
	The RSOC and IAB are grateful for that courtesy and for Heather's many years of service as RSE.  We look forward to working with her during the transition process, which will result in a Request For Proposals, as has been the case during other contract awards. We hope that the community joins us in expressing their appreciation of her work on behalf of the community and in working to ensure a smooth transition.

Kind regards,
Sarah Banks
For the RSOC, in coordination with the IAB

v2.23.0 | Report a Bug | By Email