Re: [113attendees] HotRFC at IETF-113 -- 2nd call for participation

Jay Daley <exec-director@ietf.org> Wed, 30 March 2022 11:51 UTC

Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
Subject: Re: [113attendees] HotRFC at IETF-113 -- 2nd call for participation
From: Jay Daley <exec-director@ietf.org>
In-Reply-To: <f78f2a1c-ffc6-5828-0d62-4d717382c017@alvestrand.no>
Date: Wed, 30 Mar 2022 12:51:37 +0100
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C447791C-F40B-4F05-9B02-B1863E1E0F7E@ietf.org>
References: <CAD62q9U=CpSi-4BooQfdM7dc0FMCiqSAyCu-fVe2ckrQP7fmtw@mail.gmail.com> <CAKKJt-dOLf=+9=UmRC5bPUEk-Bj01uBWB8cy4EK02mjwA5yM1g@mail.gmail.c om> <742921.1647943041@dooku> <7B65A69DADBC0BCC329CF059@PSB> <825440.1647955471@dooku> <f78f2a1c-ffc6-5828-0d62-4d717382c017@alvestrand.no>
To: Harald Alvestrand <harald@alvestrand.no>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OkqjiMYxNvCUWv00Wp1J2Ct60AA>
Precedence: list


> On 30/03/2022, at 8:43 AM, Harald Alvestrand <harald@alvestrand.no> wrote:
> 
> 
> On 3/22/22 14:24, Michael Richardson wrote:
>> John C Klensin <john-ietf@jck.com> wrote:
>>     > I actually don't think it interacts much with 2026 although I do wonder
>> 
>> It's not so much that it interacts with 2026,etc. so much as that those
>> documents are wrong.
> 
> RFC 2026 is from 1996, given its extreme age I'd say that it has weathered surprisingly well.
> 
> In my opinion, stuff like HotRFC or *DISPATCH WGs doesn't need to - and *shouldn't* - be embedded in procedure documents. They belong in Tao-type Web pages that can - and will - be changed on a weekly or monthly basis.
> 
> Formal rules, embedded in the "stone" of BCPs, should be the absolute minimum we need to function, and change rarely.
> 
> (I have a bee in my bonnet about those Web page changes being trackable as to what they changed and who authorized the change - but no more formal than putting the sources in a Git-accessible repo would accomplish. Different discussion.)

Do you mean https://github.com/ietf/tao ?

Jay

> 
> 
>> 
>>     > is contributing to general delays and some people's sense that it is
>>     > impossible to get real work done in the IETF in any efficient and
>>     > timely way.
>> 
>> I would say that it's contributing to a sense that people don't know what the
>> flavour of the day is.
>> 
>>     > While, as work-proposing mechanisms, the tone is certainly different
>>     > (especially along the fear of being attacked dimension you mention),
>>     > I'm not sure whether HotRFC is significantly different from the BarBOFs
>>     > of yesteryear.
>> 
>> Actual BarBOFs, in bars with napkins and beer (and no remote things to get in
>> the way), would be before HotRFC :-)
>> 
>> --
>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>>  -= IPv6 IoT consulting =-
>> 
>> 
>> 
> 

-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org

HotRFC at IETF-113 -- 2nd call for participation Aaron Falk
Re: HotRFC at IETF-113 -- 2nd call for participat… Michael Richardson
Re: [113attendees] HotRFC at IETF-113 -- 2nd call… John C Klensin
RE: [113attendees] HotRFC at IETF-113 -- 2nd call… Border, John
Re: [113attendees] HotRFC at IETF-113 -- 2nd call… Michael Richardson
Re: [113attendees] HotRFC at IETF-113 -- 2nd call… Spencer Dawkins at IETF
Re: HotRFC at IETF-113 -- 2nd call for participat… Spencer Dawkins at IETF
Re: [113attendees] HotRFC at IETF-113 -- 2nd call… Harald Alvestrand
Re: [113attendees] HotRFC at IETF-113 -- 2nd call… Jay Daley
Re: [113attendees] HotRFC at IETF-113 -- 2nd call… Brian E Carpenter