W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2002

Notes from the IETF/IESG/IAB Plenaries

From: Lisa Dusseault <lisa@xythos.com>
Date: Thu, 21 Nov 2002 20:04:25 -0800
To: "'Webdav WG'" <w3c-dist-auth@w3c.org>
Message-ID: <000001c291dc$3f91fd40$620afea9@xythoslap>

There has been a lot of discussion at this IETF and the last one about
how to "fix" the IETF.  I'd like to pass on some of the things
(complaints, suggestions) I've heard at the plenaries since most of you
are missing this.

 - Documents that go to last call must be higher quality.  There will be
a bigger checklist with more stringent enforcement. Dot all i's.
 - Documents should be in a different format (one that it is easier to
track changes, do algorithmic verification of checklist nits)
 - Don't do research; solve engineering problems.
 - Stay on a tightly defined charter. Use it to say "no" to new work. 
 - Keep charter milestones up to date. [any volunteers for this wg?]
 - Rough consensus doesn't mean "compromise". Don't compromise on good
 - Chairs should be less nice.  Make sure the right thing gets done
rather than that people are happy and there is no conflict.  Enforce
 - Communicate with other WGs/ADs to avoid surprises in last call.
 - IAB needs to talk more about overall complicated architectures.
 - IESG needs to delegate more and identify problems earlier.
 - Transparency is good (and is increasing -- see ID tracker)

Some links for more info:
The ID tracker:
Some IETF 55 presentations: 
Instructions to RFC editors:
A proposal to improve IETF productivity: 
Security mechanisms for the Internet:
Guidelines for writing security considerations:
Toward a quantitative analysis of IETF productivity:
General architectural and policy considerations:
Some internet architectural guidelines and philosophy

Received on Thursday, 21 November 2002 23:04:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:27 UTC