Re: [Rfced-future] Model proposal
"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 08 July 2020 02:34 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 468113A0FD6 for <rfced-future@ietfa.amsl.com>; Tue, 7 Jul 2020 19:34:09 -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 1aA6xiPWd8GM for <rfced-future@ietfa.amsl.com>; Tue, 7 Jul 2020 19:34:07 -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 CFC593A0FD5 for <rfced-future@iab.org>; Tue, 7 Jul 2020 19:34:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4B1jzz4mh6z6GJhF; Tue, 7 Jul 2020 19:34:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1594175647; bh=iupHqxYzUdMWyP/ym3a5CBLDj/RxA5LRUolUYMwVn/8=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=bPzonGtjOnmNa3x0Yzf9oyJaEW4ZqcKOPNDbtDrcXzOWSiEddWyvvTMiXwOr+seS8 frPzC5UjL9IJvq0AU8QfWgrbcRjayHyYWil6C8kU8UdCumlzEzEbueMtiLHLaYNSQ6 8HvYMj3pwGIzWfGA0RfB+RAWAf3EN8A9EkshfwZ0=
X-Quarantine-ID: <4GET2g5du88j>
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 4B1jzz19Ctz6GH3v; Tue, 7 Jul 2020 19:34:07 -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> <3acbbd58-82cc-095d-d8da-db231d63bede@joelhalpern.com> <CABcZeBMPD5KNeZMM44hMvgf5eDS3A2b+0=31sNmow14yV8S1Yw@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <8f0d34f3-ea99-e83e-b9a8-e5f407084b50@joelhalpern.com>
Date: Tue, 07 Jul 2020 22:34:05 -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: <CABcZeBMPD5KNeZMM44hMvgf5eDS3A2b+0=31sNmow14yV8S1Yw@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/tcCUokb3tQ7LeM_ynH3VSHVeF3Y>
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 02:34:09 -0000
Thank you for clarifying Eric. Maybe our differences are more in the words we use to describe things, rather than the substance. Yours, Joel On 7/7/2020 10:27 PM, Eric Rescorla wrote: > > > On Tue, Jul 7, 2020 at 5:06 PM Joel M. Halpern <jmh@joelhalpern.com > <mailto:jmh@joelhalpern.com>> wrote: > > I guess I have two differences with your description. > > > We may be able to chalk this up to bad writing on my part. > > One aspect is that we actually hire the lawyer(s) on a long term basis. > We do not hire them "when we need advice". > > > Agreed. I think that if we have an expert that requires regular deep > engagement with us, we should retain them on a long term basis. > > > 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. > > > I think I agree with this as well. When I was a consultant and when I've > hired consultants, often what we've wanted is precisely this kind of > outside strategy perspective. > > -Ekr > > > 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> > > <mailto: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>> > > <mailto: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