I think its better to have a more formally defined process that doesn't take
a vote to advance but rather a pre-defined set of milestones which may have
been set by a vote, but which by its very nature is something that requires
a formal commitment in.
I also suggest that this process as its defined has been abused in way to
many instances such that some level of thought of the IETF's Standards
Process is warranted. Its time people were accountable for their actions and
that the process which allows the IETF and IESG to award standards based on
a whim needs to be tightened down so that personalities are no longer
stumbling blocks to achieving IETF standards.
Todd Glassey
----- Original Message -----
From: "Harald Alvestrand" <harald(_at_)alvestrand(_dot_)no>
To: "Lisa Dusseault" <lisa(_at_)osafoundation(_dot_)org>
Cc: "John C Klensin" <john-ietf(_at_)jck(_dot_)com>;
<ietf(_at_)ietf(_dot_)org>; "Keith Moore"
<moore(_at_)network-heretics(_dot_)com>
Sent: Sunday, September 14, 2008 4:17 PM
Subject: Re: Last Call: RFC2183 to obsolete RFC1806
Lisa Dusseault wrote:
On Sep 8, 2008, at 5:06 AM, John C Klensin wrote:
Please reserve Last Calls for situations in which community
input or demonstrations of community consensus are actually
needed.
Perhaps an announcement specifically calling out the approval of the
errata would have been better. I was trying to make sure there was a
public record of the intent or fait accompli of obsoleting RFC1806 --
since errata don't normally have IETF-announce postings associated.
FWIW, I think it's better to err on the side of too many last calls.
If we can make the simple assertion that anything which changes the
status of a standards-track document requires a last call, at least that
class is addressed - this was apparently about altering the status of an
Experimental document, so it's still a judgment call.
Perhaps the feedback can be seen as encouraging writing up an IESG
statement/ guideline saying "we send out a Last Call when...."?
(that guideline should then also include "..... and when we think we
need one".... don't eliminate the ability to use judgment....)
Harald
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf
--------------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.169 / Virus Database: 270.6.21/1671 - Release Date: 9/14/2008
7:16 AM
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf