Lucas Pardue <lucas@xxxxxxxxxxxxxxx> wrote:
> The work I follow is done on GitHib, where a live editors copy is
> always available. I-Ds are published to capture what the authors
> believe to be a logically complete changeset. The timeliness for
> working through issues don't march to the beat of arbitrary draft
> deadlines. Publishing logically incomplete changesets is a waste of
I think you've just completely undermined your argument for no-expiry :-)
1) Since it's all in github, republishing the "old" document amounts to just
creating a single tag, and pushing that. The effort has gone from
Warren's ~1min, to ~4s to push a button. The WG chairs can even do this.
2) If WG authors can not come to a reasonable minimal increment in less
than 6 months, then I think the relevant WG chairs need to schedule many
more interims. THERE ARE PROBLEMS. Maybe even physical ones.
I also note that the minimal increment might be the adequately describe what
the tusscle is.
Github issue tracking/discussion is useless after two weeks, and multiple
rebases. ADs and appeal bodies are not going to be able to figure it out.
(And I used to rebase projects in CVS)
> time; it can be better to postpone and let a draft expire rather than
> publish something that's broken. Does that mean the document is dead?
> No. It's active as evidenced by the progress of mailing list discussion
> and GitHub activity. But what happens is cycles are wasted by people
> trying to figure this out from plain English statements that are
> cryptic to apply to our tooling and processes.
> Furthermore, I'm surprised nobody has brought up the fact that expiry
> is trivially gamed by anyone that wants to keep an I-D permanent
> alive. No-change keepalive updates are a blot on the archive.
So? If you know how to game the system, then you are an insider.
Many of us are worried about what outsiders do.
{Many of company's marketing person has been caught lying about their products
being an "RFC" by the expiry process. I speak from multiple experience,
including having to go down the hall and rip ... }
--
Michael Richardson <mcr+IETF@xxxxxxxxxxxx> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
Attachment:
signature.asc
Description: PGP signature
