Re: [Iasa20] 6635bis

"Joel M. Halpern" <jmh@joelhalpern.com> Sat, 27 April 2019 00:30 UTC

Return-Path: <jmh@joelhalpern.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 D1C5E1200C5 for <iasa20@ietfa.amsl.com>; Fri, 26 Apr 2019 17:30:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 I99EWU4363ZR for <iasa20@ietfa.amsl.com>; Fri, 26 Apr 2019 17:29:59 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 E56FD120073 for <iasa20@ietf.org>; Fri, 26 Apr 2019 17:29:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 44rWyt4Yv0zb5jm; Fri, 26 Apr 2019 17:29:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1556324998; bh=AqG9xr768d4EXcfrViFq4H6ywo1R9Nwk/nrN/OiYOns=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=m5W21S4WDoT10tGYbx+JlzplwPtIUtVNnBP68QAkBKexdYXgzdpcJh/bzmv7ySFWo cajjnp/ELSOyU2LDoznsMAzm2N+R88SmLVV7KSTi6FHvgqODP3MtAZZeYobGCFjTlx TvHTQT0lHPmm0cUZ4/jBeAwgk6gnyK9WX02cHvUI=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 44rWyt0K07zb5jg; Fri, 26 Apr 2019 17:29:57 -0700 (PDT)
To: John R Levine <johnl@taugh.com>
Cc: iasa20@ietf.org
References: <20190426211900.555852012FE081@ary.qy> <22f00e3c-faa1-2eb3-ad38-97f6fb743aac@joelhalpern.com> <alpine.OSX.2.21.1904261835490.29589@ary.qy>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <c2a25515-b5cc-13f9-cdf9-058170194d1f@joelhalpern.com>
Date: Fri, 26 Apr 2019 20:29:56 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.21.1904261835490.29589@ary.qy>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/dkGhK7z1udLufE69wh_NI1cFljs>
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: Sat, 27 Apr 2019 00:30:01 -0000

As far as I can tell, the change you propose is not necessary to get the 
LLC working.  This working group was specifically chartered NOT to 
change any policies.  The change you (and Sean if I understand properly) 
are proposing represents a change in policy.

Yes, I disagree with the change in policy.  I think it would be a mistake.

But more importantly, that change is clearly outside of the scope the 
community was told applied to this working group.

If you want to write a separate I-D, and try to find a venue for it, to 
change that policy, you clearly have the right and skills to do so.
But please do not put that substantive change into this I-D (RFC 
revision) that is specifically to make the necessary changes so the LLC 
can do the jobs it needs to do.

Yours,
Joel

On 4/26/19 6:39 PM, John R Levine wrote:
>> What I fail to see is why there is any need to change the wording that 
>> we have on the status of the RSE.  I can imagine that the LLC will 
>> need to continue to exercise care in the handling of the RSE to avoid 
>> accidental changes of status.  As you say John, it is tricky.
>> But I do not see why that should result in any change to the text in 
>> the revision of RFC 6635.
> 
> Assuming we agree that the details of the agreement with the RSE are up 
> to the LLC, I agree.
> 
> But RFC 6635 says "The RFC Production Center function is performed by a 
> paid contractor," and " The RFC Production Center contractor is to be 
> selected through an IASA Request for Proposal (RFP) process as described 
> in Section 4.1." and " The RFC Publisher contractor is to be selected 
> through an IASA RFP process as described in Section 4.1."
> 
> I think the current RFC people are doing a swell job but I would like us 
> to give the LLC the latitude to structure things however makes sense.  
> At this point, we have a contractor which hires its staff but at some 
> point it might make sense for the LLC to hire staff without an 
> intermediary.
> 
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail. https://jl.ly