Re: [Iasa20] 6635bis

Bob Hinden <bob.hinden@gmail.com> Sun, 28 April 2019 02:43 UTC

Return-Path: <bob.hinden@gmail.com>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFE85120178 for <iasa20@ietfa.amsl.com>; Sat, 27 Apr 2019 19:43:34 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 DJyFlA5oQG2f for <iasa20@ietfa.amsl.com>; Sat, 27 Apr 2019 19:43:32 -0700 (PDT)
Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) (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 99879120159 for <iasa20@ietf.org>; Sat, 27 Apr 2019 19:43:32 -0700 (PDT)
Received: by mail-wr1-x42f.google.com with SMTP id t17so10158399wrw.13 for <iasa20@ietf.org>; Sat, 27 Apr 2019 19:43:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=hz+Qjee2QMCBW5C9uXYGB0yAUrIa9R2r+l1YdVCTEm0=; b=RYIVA/r0BrTHo8WgTW4DDIbCarqFjjd6A8TvQpqcn5QjH5p7xZr4Vuiu4nEM4IirLw C0rpGo1lFZT3H1Ssx98dhJA50j6/IPTwihBOOFmPI+qQjn+ni2Jqz7xtiLO9CvkKwAfL +kwYQ6xOcMPCFQlHjLeFyhrLdyd3mCdKu2GKTcYkBb78RBZD1MJxZZ8xZ/vguXACsaEC TNxB6FMV2C0w7Oz1Fr/ydETiKe5qU5hK0CCC8tNjmd2vpCdQEHGz/K7RYpPRKBng/TCO HO9FdnqQPaPCCeoQnPsSwAFj1fie+e+oIXY0T69DYDDJYho8Oo/dtVwQPP28NJMVIcTE EerQ==
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=hz+Qjee2QMCBW5C9uXYGB0yAUrIa9R2r+l1YdVCTEm0=; b=QhsX7eN5akanCgHCHbV6N1BBtlsvFVilP/vkNK6jqogRqiNQjDH0FwyiGJGbZIFQ9W vxLIf9tKrxMmXxvnnaQbU7Vs6OtgNpXB/irtXVWbaHaNB+KHu8lYhpUwUeL1GnOSB+r8 tsCuzmwUgVBJqX4OjJ/foMFX9Hb+O2lrAcQR2hkaUheicBCKJYMfxD8qNFnWIBCGKEMb uKA31nGMBEb6wv1g3GgQ50RE4IOJM6z+aBSYAzsSL3a49tcRoQG5q2hWx7pk6iXphGE8 IVksGWdV+jaqD9RpZhQUat/8VNOmuzhhKSyjgxStPWpxsc10Ko4+7ejoRB+ULcA04q0h 1HXw==
X-Gm-Message-State: APjAAAXwKnqBEBMpZQ/dp7lFOGrR5CmEnBJ8dAluMXxSd6JmungdOqlz WgV/8pKTIYROOCBWG6XpB46/vvcY
X-Google-Smtp-Source: APXvYqzwkdSLRYoSZfDxXr+HkSLosWjgeK2MvBIbR3uh4+UEEONVAcOHNaS8SgNge4iE0jvT+a6Z2g==
X-Received: by 2002:adf:9e86:: with SMTP id a6mr26840220wrf.178.1556419410860; Sat, 27 Apr 2019 19:43:30 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:ef0b:5e:a1af:76ab:19ff? ([2601:647:5a00:ef0b:5e:a1af:76ab:19ff]) by smtp.gmail.com with ESMTPSA id d4sm29894258wrv.42.2019.04.27.19.43.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 27 Apr 2019 19:43:29 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <40d9048e-f744-a6cf-de56-a444f2787fef@gmail.com>
Date: Sat, 27 Apr 2019 19:43:25 -0700
Cc: Bob Hinden <bob.hinden@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <08102CCA-47F3-475A-A2A5-0E62B5BF3038@gmail.com>
References: <20190426211900.555852012FE081@ary.qy> <22f00e3c-faa1-2eb3-ad38-97f6fb743aac@joelhalpern.com> <alpine.OSX.2.21.1904261835490.29589@ary.qy> <c2a25515-b5cc-13f9-cdf9-058170194d1f@joelhalpern.com> <alpine.OSX.2.21.1904262033390.29815@ary.qy> <2F643707-45C2-4088-8D0F-A1F0F1238D86@akamai.com> <CAL02cgQFXPXgeFiayehWmpCDND1gS0LmAzRo8COKLvspNNPh7A@mail.gmail.com> <40d9048e-f744-a6cf-de56-a444f2787fef@gmail.com>
To: "iasa20@ietf.org" <iasa20@ietf.org>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/iwmVseLpstvPURwPrwVjgmZouck>
Subject: Re: [Iasa20] 6635bis
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions relating to reorganising the IETF administrative structures in the so called “IASA 2.0” project. <iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>, <mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>, <mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Apr 2019 02:43:35 -0000

Hi,

A few comments on this thread.

The RFC Editor services are broken into several parts.  There is the RFC Editor, a person doing that job with independent authority, and the Production Center where the actual editing, document production, online publication, and archiving is done.

The Production Center work is done by many people with a range of skills, full and part time editors, managers, software development, and IT support.  It’s large enough that it need staff services like HR.   People doing that job require specific training how RFCs are produced, the rules for what they look like, and the specific tools that they use to do their job.  I am probably understating this.

In my direct experience having been very involved in the hiring of two RFC Editors and the transition of this work from ISI, its very specialized.  We typically don’t get a lot of qualified bidders.   

The individual fulfilling the RFC Editor job could be a contractor or direct employee, but the kind of person who is capable of doing that job that you want to hire, will have a strong opinion which form of employment they will want.   The leverage is with the candidate, not the LLC.

Given the size and complexity of the Production Center activity, it would be a major undertaking to bring into the LLC.  The LLC would have to hire and train people capable of doing the work, provide them benefits, have managers to mange them, provide employee services for them, etc., etc.   We were very fortunate in the move from ISI that several of the key personal moved with the work.  It’s not clear that would happen again.

I think that if the LLC is seriously thinking of moving the Production Center activity inside of the IETF LLC, they don’t understand this activity.   As others have said, it would grow the amount of staff needed by the LLC significantly and turn it into a medium size company with all that entails.

Bob