IETF Logo Mail Archive

Re: [Iasa20] 6635bis

"John Levine" <johnl@taugh.com> Fri, 26 April 2019 03:38 UTC

Return-Path: <johnl@iecc.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 46CB2120270 for <iasa20@ietfa.amsl.com>; Thu, 25 Apr 2019 20:38:35 -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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=zKSxTDqP; dkim=pass (1536-bit key) header.d=taugh.com header.b=TaQi6zxy
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 z-dSLicwqI-B for <iasa20@ietfa.amsl.com>; Thu, 25 Apr 2019 20:38:33 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 86F19120222 for <iasa20@ietf.org>; Thu, 25 Apr 2019 20:38:33 -0700 (PDT)
Received: (qmail 46955 invoked from network); 26 Apr 2019 03:38:31 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=b769.5cc27d37.k1904; i=johnl-iecc.com@submit.iecc.com; bh=HwL7UovIi1pvXdfNo/SJyvUznsSdWtj9rOeCGQy8R8U=; b=zKSxTDqP75/6MxYomyyVxSMIIYNksa6dSFWrMuiUqdKqFfKSP1To/me4PdTRoE1lG9HcQTkU2QnjMyyedL01Qei7ndaLlxwkHnKVtbyW+0ztpKRWgfnmxw1+4ioIFBzBXs52M60icHxLSQetzuG2dkz47RnKjwmIneBsJfke9QlF3wCK/4tSMGFocXa22SYVvbaOliJaGw6fQ85AJjHeaOTuJHuuW2ntj8HQMQ0y+3Ebv3KdyoJHiy+fczDzM2FP
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=b769.5cc27d37.k1904; olt=johnl-iecc.com@submit.iecc.com; bh=HwL7UovIi1pvXdfNo/SJyvUznsSdWtj9rOeCGQy8R8U=; b=TaQi6zxy/TqDy6wBAZmm/m+VAhP6AXvmilD3sZWoU3PXQQjk0yBdCUn3iMmbSDzQ1K6vJkOC5cjrbY7vqFqY7gvUDEPN45FnQIO7K4y1g5sgTNRlvp22vg1IU2RLTjlpMemfqCLefCEnQNZJA2KVsN6/0iwpcndymNdgUGGGNoIO2jJfJ0RujeezCfvdgDrD2TvhCET7h81BGRR7NsKxIcGbA3jTH6v8zxVOX/aS6GBnl/uoYdR8jlpaRnoi+z5a
Received: from ary.qy ([68.175.130.230]) by imap.iecc.com ([64.57.183.75]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP; 26 Apr 2019 03:38:30 -0000
Received: by ary.qy (Postfix, from userid 501) id AA0842012F4AC9; Thu, 25 Apr 2019 23:38:30 -0400 (EDT)
Date: Thu, 25 Apr 2019 23:38:30 -0400
Message-Id: <20190426033830.AA0842012F4AC9@ary.qy>
From: John Levine <johnl@taugh.com>
To: iasa20@ietf.org
Cc: jmh@joelhalpern.com
In-Reply-To: <771d3caf-e5d6-4a25-03cc-788a4c37f86b@joelhalpern.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/oYWJSL5hwwgtRqCIpFDHZXBTPIE>
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:38:35 -0000

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.

R's,
John

v2.23.0 | Report a Bug | By Email