Re: [Iasa20] 6635bis

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 26 April 2019 03:54 UTC

Return-Path: <brian.e.carpenter@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 11E4D12028C for <iasa20@ietfa.amsl.com>; Thu, 25 Apr 2019 20:54:24 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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=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 ZpPSdB2rBnhM for <iasa20@ietfa.amsl.com>; Thu, 25 Apr 2019 20:54:22 -0700 (PDT)
Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) (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 7F82A120273 for <iasa20@ietf.org>; Thu, 25 Apr 2019 20:54:22 -0700 (PDT)
Received: by mail-pf1-x42c.google.com with SMTP id j11so965273pff.13 for <iasa20@ietf.org>; Thu, 25 Apr 2019 20:54:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=QiQ8jICHH2tFccROsHAr1dIAkEAGi0HeMpNla735UxE=; b=szW4rbnLAFM8+51QYeKPrdwQc+N7u+hqWwc+nU1mj9DIwb+EpcgXIQIW7vyersuuIi QwEJTH+hcJfyZq+4+xeOWTqxDRUnu1Pp9rTtq38k81HXy9llFDSIZtvbDOF2x8pZ9q5C P4aMjGsr2I/mghDvktOUvwoHwMS/dHDkLrn2BIeQmehLy+3ccywuP/37pxPSC4qTtFrr LZcDGqrqxOfs9LyIp8ysIeijXh3ZLVgU9ovvNc2yql5mBAdtKnnY7E4VvDifu/U1Y9k9 YM3aJt7ulJGjKAxfO4iBbrcE+pXWwV0CC1JftSFVz4A2NpcRzlTIvgvwFlWjJ51E7OHv 0FGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=QiQ8jICHH2tFccROsHAr1dIAkEAGi0HeMpNla735UxE=; b=P0VkZG2rqWrj3G6G//m6B2xXc79sVQ973Gcwtj1aGnqfHpLlc+tSqaA8hevWM6WwpN 3iIRcbCr1tShxeYWMoiyThwy534PYUpXn2rEbb/cAWbjDSju6hSksVY2xKG0JLQi8bxv mj9ILHSHC+5F22ak9AV+luUoS8ernBN4W8Y9LuLr/FO5R/v7mNnjfWuR/D0S58iynxgj df+9DUERj2aTaqtGBK/0sujZLKi2vUwSMyNjpktrW4poJKHuNy5J3NBe6h9EIp15BMVP mzV5bILf0WZoonDgOOsIb4uwknc/2tcIrR9juZHb5ZBd+yem7BJaxheuBB3utFaL+Nby Bakw==
X-Gm-Message-State: APjAAAV523NBgyhnZyZHnQJ5oCksvLnmyjF/FsEC63bgBlDngI/9ILnl hxMUk/d/O/2Ak7eoyEDPVFFYnMBY
X-Google-Smtp-Source: APXvYqwYI5fPuaR/3kTkCAqp8XYyEPio20ZAdoIzzi19ccVEhvmRqEhfKvmBkyDOEQ9pOKvHYIIfAQ==
X-Received: by 2002:a63:cc0a:: with SMTP id x10mr42056794pgf.179.1556250861196; Thu, 25 Apr 2019 20:54:21 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.72.205]) by smtp.gmail.com with ESMTPSA id s79sm47341083pfa.31.2019.04.25.20.54.19 for <iasa20@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Apr 2019 20:54:20 -0700 (PDT)
To: iasa20@ietf.org
References: <20190426033830.AA0842012F4AC9@ary.qy>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <7d0b8774-d040-bcb5-e45c-3c95cf22c442@gmail.com>
Date: Fri, 26 Apr 2019 15:54:16 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <20190426033830.AA0842012F4AC9@ary.qy>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/Fyj8-piL_ASKKEqUPgxQ9uAXOsg>
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: Fri, 26 Apr 2019 03:54:24 -0000

On 26-Apr-19 15:38, John Levine wrote:
> In article <771d3caf-e5d6-4a25-03cc-788a4c37f86b@joelhalpern.com> you write:
>> It would seem quite difficult to have the RFC Editor be an employee of 
>> the LLC.
>> What happens when the IAB / RSOC decides that it wants a different RSEs?
>> How would that employee respond to an RFP, since they already have an 
>> employment agreement with the LLC?
> 
> You write the employment agreement with that in mind.  It's not hard to do.
> 
> I agree with Sean that it makes sense to give the LLC latitude to hire
> or contract with people on whatever terms make sense.

The language already allows that for the RSE case. The language for the
Production Center and the Publisher does not; they are required to be
contracted out. As I said at length, that's consistent with the lightweight
LLC we were initially promised. I really don't see that this WG is allowed
to change it.

    Brian