Re: call for ideas: tail-heavy IETF process

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>>>>> "Thomas" == Thomas Narten <narten@xxxxxxxxxx> writes:
    Thomas> The current cycle too often seems to be more like "new
    Thomas> version posted". Wait if anyone reviews. Some reviews
    Thomas> eventually, maybe. Oh, IETF meeting coming, time for a
    Thomas> revision. But with meeting approaching, there are a zillion
    Thomas> docs and cycles are limited.  Rather haphazard, with too
    Thomas> many documents effectively only being revised once per
    Thomas> meeting cycle.

I would like to suggest that the IESG Review be done in public on the WG
mailing list.    I've been a WG co-chair for just over a year now, and
I'm truly astounded by what happens behind the scenes.  

It's not the substance, it's the quantity, and the lack of WG view of
it.   I think that this substantially and quite negatively contributes
to the "fix it during IESG review", and therefore to the IESG workload.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@xxxxxxxxxxxx  http://www.sandelman.ca/        |   ruby on rails    [ 
	


Attachment: pgpsOGmLHkbAJ.pgp
Description: PGP signature


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]