Timo Gerke <[email protected]> wrote: > The Problem: "Not Working Process" in Cluster C430 Currently, a single > document undergoing a late-stage technical overhaul can hold an entire > cluster hostage. In Cluster C430, 24 documents are eady for publication > (in PUB or AUTH48-DONE state) but have been stalled for over five > months because one primary blocker (draft-ietf-tls-rfc8446bis) is > stuck.
Five months is not very long :-)
{"Luxury! My parents used to get us up half an hour before we went to bed..."}
Other clusters have persisted for multiple years!!!
Look at the timeline for ANIMA's https://datatracker.ietf.org/doc/rfc8990/
(That huge gap is MISREF time. It seems that the reference to the cluster
details is gone)
It's a failure of the WG to plan normative references better. It happens.
Given that it's rfc84446bis, the core document of TLS1.3, there probably was
no better plan.
I agree that there ought not be any technical change at AUTH48.
It should all be word smithing.
Sometimes during that editing process, it is revealed that different parties
had different understandings, never explicitely stated.
And the result *is* a kind of technical conflict.
(P1: "I thought A, and I was happy". P2: "I thought B, and I was happy!"
P1: "Changing to B is a technical change!" P2: "Changing to C is even worse!")
The answer ought to be that the AD *returns* the document to the WG to sort out.
I'm pretty sure I've been involved in documents where compromise text went to
the WG for a Consensus Call, and then AUTH48 resumed. I can't recall when.
If compromise text is impossible, then it's a bad situation. Probably no
running code tripped upon what is likely a corner case, unfortunate. But,
still better it happen now than later.
--
Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
** My working hours and your working hours may be different. **
** Please do not feel obligated to reply outside your normal working hours **
signature.asc
Description: PGP signature
-- rswg mailing list -- [email protected] To unsubscribe send an email to [email protected]
