Re: [Rfced-future] Fwd: [I18ndir] I18ndir last call review of draft-iab-rfcefdp-rfced-model-11
John C Klensin <john-ietf@jck.com> Wed, 02 March 2022 23:54 UTC
Return-Path: <john-ietf@jck.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 9BC483A0EA4 for <rfced-future@ietfa.amsl.com>; Wed, 2 Mar 2022 15:54:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 GnoUyf6yOCnT for <rfced-future@ietfa.amsl.com>; Wed, 2 Mar 2022 15:54:12 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27C6E3A0E92 for <rfced-future@iab.org>; Wed, 2 Mar 2022 15:54:11 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1nPYnK-000CSD-D9; Wed, 02 Mar 2022 18:54:10 -0500
Date: Wed, 02 Mar 2022 18:54:05 -0500
From: John C Klensin <john-ietf@jck.com>
To: Peter Saint-Andre <stpeter@stpeter.im>, rfced-future@iab.org
Message-ID: <42EA62FFC6D81923D8135C0A@PSB>
In-Reply-To: <0479fcca-2a38-1981-c022-f5df1639549c@stpeter.im>
References: <5231BEDE2E5FB8C502855970@PSB> <46de5830-990a-30bf-57fb-ddbc78cbb1fc@stpeter.im> <3c4497ed-d476-16bc-9aa1-354cd082830e@stpeter.im> <9B6987B47A244C8B58E76C0E@PSB> <0479fcca-2a38-1981-c022-f5df1639549c@stpeter.im>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/mtCSSR57o8Uh3EDZnXZcfSB6WXI>
Subject: Re: [Rfced-future] Fwd: [I18ndir] I18ndir last call review of draft-iab-rfcefdp-rfced-model-11
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, 02 Mar 2022 23:54:17 -0000
--On Wednesday, March 2, 2022 14:51 -0700 Peter Saint-Andre <stpeter@stpeter.im> wrote: > On 3/1/22 8:48 PM, John C Klensin wrote: >> Peter, >> >> My snarky comments, to which Pete responded, were not intended >> for this list because they are about how that directorate is >> organized and how well it is working rather than anything >> being discussed on this list. > > Sorry about that - I forwarded the whole thing to get your > feedback about internationalization on the record, but could > have been more careful about removing matters related to > operation of the i18ndir. No problem. I've done worse --it was really about just keeping the noise down. >... >> That goes in a direction I would recommend against. At >> present (and under the "old" system) the can reach out to, or >> confer with, just about anyone they decide they need to >> consult about just about any issue (I can't think of >> exceptions, but there might be some). If they discover they >> need to pay consulting fees to get the advice they need, > > The text I proposed didn't say anything about paid consulting. I noticed. I just wanted to be sure there was nothing in the document that would exclude that in the unlikely even that it should, in the RPC's judgment and without any ceremony other than sorting out money and contracts with the LLC, be necessary. IMO, if we can do small things that, without creating serious ambiguity, make this document even a bit more future-proof, that is worthwhile. Some of what followed were other examples of that. >> nothing prevents them from >> discussing that with the LLC and asking that the LLC initiate >> whatever procedures are needed. I can see nothing in the new >> model that changes that except that, if the LLC were to decide >> it needs additional substantive advice, the RSAG and/or RSWG >> would be good places to start. > > My personal opinion (no document editor hat on) is that anyone > should be able to talk with anyone they feel they need to talk > with in order to Get Things Done around here. If RPC folks > feel that it'd be helpful to have a chat with someone in or > out of the "RFC community" about internationalization or SVG > or whatever so that they can make informed decisions or > contributions, then have at it. Agreed and I've been trying to say similar things throughout this process. > Perhaps we don't need to say > that explicitly (and it's kind of sad if we think we need to), > but I would not want to end up in a place where RPC folks > think their hands or tongues are tied. They're the one who > have to implement this stuff, after all! Exactly (and concur about the sadness but I'm a tad concerned about a control freak or two getting involved in the RSWG and tying things in knots. So the closer we can get to letting the RPC do their jobs -- again, talking with anyone they need to -- and without saying anything that encourages the RSWG (or RSAB) to meddle into anything but broad principles or otherwise attempt micromanagement, the happier I'll be. >... >> If you think something more is needed in that rather long list >> in Section 4.3, I'd recommend making it far more general. >> Please rewrite what I'm about to say, but I'd think about >> something like: >> >> "Identify topics and issues that they encounter while >> processing documents or carrying out other >> responsibilities on this list for which they lack >> sufficient expertise and identifying and conferring with >> relevant experts as needed." > > Something like that seems appropriate, and closer to what I > had in mind. Good. And unless you or others (particularly Jay) think otherwise, I think that is sufficient to let us omit specific mention of paid consulting or the LLC out -- IMO, that just follows naturally from something like the above. -john
- [Rfced-future] Fwd: [IAB] I18ndir last call revie… Mirja Kuehlewind
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… Martin J. Dürst
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… Eliot Lear
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… Eliot Lear
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… Brian E Carpenter
- Re: [Rfced-future] [IAB] I18ndir last call review… Mirja Kuehlewind
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… Peter Saint-Andre
- [Rfced-future] Fwd: [I18ndir] I18ndir last call r… Peter Saint-Andre
- Re: [Rfced-future] [IAB] I18ndir last call review… Peter Saint-Andre
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… Eliot Lear
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… Brian E Carpenter
- Re: [Rfced-future] [IAB] I18ndir last call review… Jay Daley
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… Peter Saint-Andre
- Re: [Rfced-future] [IAB] I18ndir last call review… Martin J. Dürst
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… Peter Saint-Andre
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… Martin J. Dürst
- Re: [Rfced-future] Fwd: [I18ndir] I18ndir last ca… Peter Saint-Andre
- [Rfced-future] Boilerplate nit [I18ndir last call… Brian E Carpenter
- Re: [Rfced-future] Boilerplate nit [I18ndir last … Martin J. Dürst
- Re: [Rfced-future] Fwd: [I18ndir] I18ndir last ca… Martin J. Dürst
- Re: [Rfced-future] Fwd: [I18ndir] I18ndir last ca… John C Klensin
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… John C Klensin
- Re: [Rfced-future] Fwd: [I18ndir] I18ndir last ca… Eliot Lear
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… Martin J. Dürst
- Re: [Rfced-future] Fwd: [I18ndir] I18ndir last ca… Peter Saint-Andre
- Re: [Rfced-future] Fwd: [I18ndir] I18ndir last ca… Peter Saint-Andre
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… Brian E Carpenter
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… Peter Saint-Andre
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… Peter Saint-Andre
- Re: [Rfced-future] Fwd: [I18ndir] I18ndir last ca… Peter Saint-Andre
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… John C Klensin
- Re: [Rfced-future] Fwd: [I18ndir] I18ndir last ca… John C Klensin
- Re: [Rfced-future] Fwd: [I18ndir] I18ndir last ca… Martin J. Dürst
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… Brian E Carpenter
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… John C Klensin
- Re: [Rfced-future] Fwd: [I18ndir] I18ndir last ca… John C Klensin
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… Peter Saint-Andre
- Re: [Rfced-future] Fwd: [I18ndir] I18ndir last ca… Peter Saint-Andre
- Re: [Rfced-future] Fwd: [I18ndir] I18ndir last ca… Peter Saint-Andre
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… Brian E Carpenter
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… Martin J. Dürst
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… John C Klensin
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… Peter Saint-Andre
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… John C Klensin
- Re: [Rfced-future] Fwd: [IAB] I18ndir last call r… John C Klensin