Re: [Rfced-future] Model proposal
"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 08 July 2020 00:06 UTC
Return-Path: <jmh@joelhalpern.com>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 817573A0C8E for <rfced-future@ietfa.amsl.com>; Tue, 7 Jul 2020 17:06:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 8qPW1UDbA7s4 for <rfced-future@ietfa.amsl.com>; Tue, 7 Jul 2020 17:06:43 -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 CDACF3A0C94 for <rfced-future@iab.org>; Tue, 7 Jul 2020 17:06:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4B1fjv5MHpz6GFP2; Tue, 7 Jul 2020 17:06:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1594166803; bh=q5Re8uz6hsuRwpuz3QQonCB/HXqM0kJdt/GAr70Gvzs=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=YBrG7dace1XnHrcXwAavNjNUJcDyfsuoAhv2ElWFWiJuwxnRGZIQD4KYDXxP3ybup MVfkkCQ6ouYdse46ddzm/38nDsBBCq/bZiClGGj2RQ63QJPQ8a3R3UAF5TpuOhTMeY oXUnwPRRmmzH0eERhxPG2i5hKFoly/v1LZat3YLo=
X-Quarantine-ID: <uBYrbl5oOJ2x>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (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 4B1fjv131hz6GF1Q; Tue, 7 Jul 2020 17:06:43 -0700 (PDT)
To: Eric Rescorla <ekr@rtfm.com>
Cc: rfced-future@iab.org
References: <d4d1cd2d-6df2-4cb4-b63a-f9bba45b48c0@www.fastmail.com> <51b72823-f2a2-29bd-bd88-f63e13522387@gmail.com> <d1f33279-0656-4caa-81e7-aa665d3a4acb@www.fastmail.com> <CABcZeBMdrfjy+kqQ20MS_1fZrNddff+ycwau5VdC5qAFQN2qVA@mail.gmail.com> <20200707174930.GP3100@localhost> <CABcZeBMGxE6+29_BfNEANjZVJ=0UKFYM+pCp_ECsDw6e2aFMwQ@mail.gmail.com> <37d1d244-ae3f-26db-11c7-d4fcfd25a747@gmail.com> <CABcZeBML64rxVC_wmrDoEbkgVu0+6w=4AoQhz-Pg+OiMwEK+9A@mail.gmail.com> <398cb364-1592-f63e-da02-45b08baf1c00@joelhalpern.com> <CABcZeBPfOkrnpZh4X+XZOaoGb8ATC9PYaTp9T4cn5GR=SgwGwg@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <3acbbd58-82cc-095d-d8da-db231d63bede@joelhalpern.com>
Date: Tue, 07 Jul 2020 20:06:41 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <CABcZeBPfOkrnpZh4X+XZOaoGb8ATC9PYaTp9T4cn5GR=SgwGwg@mail.gmail.com>
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/rfced-future/eROCC6PHkvbSHNbcqpkOfFYDYEE>
Subject: Re: [Rfced-future] Model proposal
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jul 2020 00:06:46 -0000
I guess I have two differences with your description. One aspect is that we actually hire the lawyer(s) on a long term basis. We do not hire them "when we need advice". The other is that in the area of direction for the RFC Series, I think that we need the expertise in helping us ask the right questions on an ongoing basis, not just answering questions when needed. Yours, Joel On 7/7/2020 7:37 PM, Eric Rescorla wrote: > > > On Tue, Jul 7, 2020 at 4:14 PM Joel M. Halpern <jmh@joelhalpern.com > <mailto:jmh@joelhalpern.com>> wrote: > > We keep a lawyer on retainer. > So the difference becomes that we are looking for someone who will be > - more engaged in understanding and helping direct the community (the > lawyers explicit do not direct) > - have more ongoing activities, although quite possibly less than > heretofore > > > > Well, I'm not sure about the "we" here, as I'm arguing that we should > not in fact be looking for this. > > Rather, I am arguing that the community should drive strategy > (potentially with some structure like Martin proposed) and that to the > extent to which we need someone with specific expertise in the areas > Brian has flagged, we should hire someone to advise us, in much the same > way we do for legal advice. > > -Ekr > > Sounds like you are actually arguing for a senior, respected, > contractor. With a long term relationship. > > Yours, > Joel > > On 7/7/2020 6:18 PM, Eric Rescorla wrote: > > > > > > On Tue, Jul 7, 2020 at 3:11 PM Brian E Carpenter > > <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com> > <mailto:brian.e.carpenter@gmail.com > <mailto:brian.e.carpenter@gmail.com>>> wrote: > > > > > Sorry, I should have been more clear. I think this is a proper > > subject for IESG and IAB consideration, made somewhat more > difficult > > by anchoring on a historical five author limit that had (at > least to > > me) a fairly unclear rationale. > > > > Absolutely I think that community discussion and rough > consensus is > > appropriate for this and other strategy or policy issues. My > concern > > is that this needs to be facilitated and informed by someone with > > relevant knowledge and experience in the > > editing/publishing/library/archival world and that is not us. > > > > > > Stipulating for the moment that this is true, I don't really see > how you > > get from there to "and this person needs to be in charge of the > > process". To give an example that I think I also gave on the most > recent > > virtual call, we often have to do things that require a bunch of > > relevant expertise in the legal world, and that's not us, but > address > > that problem by engaging a lawyer and asking their opinion. Why > doesn't > > that work here? > > > > -Ekr > > > > > > > > > > > > > > >
- [Rfced-future] Model proposal Martin Thomson
- Re: [Rfced-future] Model proposal Brian E Carpenter
- Re: [Rfced-future] Model proposal Martin Thomson
- Re: [Rfced-future] Model proposal Eric Rescorla
- Re: [Rfced-future] Model proposal Joel M. Halpern
- Re: [Rfced-future] Model proposal Nico Williams
- Re: [Rfced-future] Model proposal Christian Huitema
- Re: [Rfced-future] Model proposal Eric Rescorla
- Re: [Rfced-future] Model proposal Eric Rescorla
- Re: [Rfced-future] Model proposal Adam Roach
- Re: [Rfced-future] Model proposal Brian E Carpenter
- Re: [Rfced-future] Model proposal Eric Rescorla
- Re: [Rfced-future] Model proposal Nico Williams
- Re: [Rfced-future] Model proposal Stephen Farrell
- Re: [Rfced-future] Model proposal Brian E Carpenter
- Re: [Rfced-future] Model proposal Joel M. Halpern
- Re: [Rfced-future] Model proposal Eric Rescorla
- Re: [Rfced-future] Model proposal Larry Masinter
- Re: [Rfced-future] Model proposal Joel M. Halpern
- Re: [Rfced-future] Model proposal Nico Williams
- Re: [Rfced-future] Model proposal Nico Williams
- Re: [Rfced-future] Model proposal Eric Rescorla
- Re: [Rfced-future] Model proposal Joel M. Halpern
- Re: [Rfced-future] Model proposal Brian E Carpenter
- Re: [Rfced-future] Model proposal S Moonesamy
- Re: [Rfced-future] Model proposal Martin J. Dürst
- Re: [Rfced-future] Model proposal Mirja Kuehlewind
- Re: [Rfced-future] Model proposal Nico Williams
- Re: [Rfced-future] Model proposal Russ Housley
- Re: [Rfced-future] Model proposal Scott O. Bradner
- Re: [Rfced-future] Model proposal Scott O. Bradner
- Re: [Rfced-future] Model proposal Russ Housley
- Re: [Rfced-future] Model proposal Eliot Lear
- Re: [Rfced-future] Model proposal Christian Huitema
- Re: [Rfced-future] Model proposal Brian E Carpenter
- Re: [Rfced-future] Model proposal Martin Thomson
- Re: [Rfced-future] Model proposal Brian E Carpenter
- Re: [Rfced-future] Model proposal Nico Williams
- Re: [Rfced-future] Model proposal Eliot Lear
- Re: [Rfced-future] Model proposal Brian E Carpenter
- Re: [Rfced-future] Model proposal Brian E Carpenter