Brian E Carpenter <brian.e.carpenter@xxxxxxxxx> wrote:
> On 30-Aug-24 09:33, Michael Richardson wrote:
>> Rob Wilton \(rwilton\) <rwilton=40cisco.com@xxxxxxxxxxxxxx> wrote:
>> > 3. Split/migrate the existing IETF process into what must be in the
>> > RFCs/BCP and what moves to webpages (hopefully also incorporating
>> > appropriate IESG statements). If we want to change core parts of the
>> > IETF process, i.e., the parts that are documented in BCPs, then this
>> > may be a time to consider this, but this could also be deferred, to
>> > reduce risk). Moving text to webpages may be quite a lot of work,
mcr> What kind of risks are you thinking here?
mcr> I think that the biggest risk is a 1000 message long debate over minutia
mcr> which pisses off half the community, and we lose the energy to finish :-)
bc> There's another risk, which is why I keep banging on about
bc> https://www.ietf.org/process/informal/: sheer complexity. Cleaning up
bc> RFC 2026 and RFC 2418 will be no means solve the problem. We have
bc> multiple process BCPs, multiple related Informational RFCs, multiple
bc> IESG statements, and multiple bits of folklore.
Wow. That's a lot of links.
I think we need a WG for this work.
It feels to me that we need to:
1. move all the text into wiki pages.
2. move/blend/re-organize.
3. yank text *out* of the wiki into process BCPs as appropriate.
4. consolidate whatever is left.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] mcr@xxxxxxxxxxxx http://www.sandelman.ca/ | ruby on rails [
--
Michael Richardson <mcr+IETF@xxxxxxxxxxxx> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
Attachment:
signature.asc
Description: PGP signature
