Re: [RAI] RAI processes for handling work effectively

["DRAGE, Keith (Keith)" <[e-mail]>]

As a process experiment, that already exists - what do you think dispatch has been doing for the last few years.

It seems more to me that Harald is raising the question of whether that applies to MMUSIC.

In terms of the current thorny problem that Harald wants to resolve - no it would not have helped at all - he would still have a thorny problem, and it would probably have been shot down at the IETF review stage rather than having the discussion in the working groups.

Keith

________________________________
From: [e-mail] [mailto:[e-mail]] On Behalf Of Spencer Dawkins
Sent: 18 July 2013 15:48
To: Paul Kyzivat
Cc: [e-mail]
Subject: Re: [RAI] RAI processes for handling work effectively

On 7/18/2013 8:55 AM, Paul Kyzivat wrote:
Harald,

What you say makes some sense to me.

But if we were to act on it then I think we need to replace some WGs with review panels. (We have an SDP directorate, but I don't think that is a sufficient replacement for mmusic.) And so we will need some clear processes for review panels. How would we process drafts that would otherwise have been handled through the standanding wg? Would they be AD sponsored? And we may need to schedule meeting sessions for review panels too.

This seems like it would need to be an ietf-wide change, not just RAI. (But maybe we could pilot it in RAI.)

I could be in the rough on this, but if RAI wants to head in that direction, I'd suggest doing so in RAI alone as an http://tools.ietf.org/html/rfc3933 process experiment. That would bypass two frequent sources of failure:

  *   Getting everyone in the entire IETF to agree (at least roughly) to that this is where we all want to go, and
  *   Getting everyone in the entire IETF to agree (at least roughly) to change BCP text for the entire IETF, with no operational experience.

>From RFC 3933:

   The IESG is explicitly authorized to use this mechanism (based on

   Experimental RFCs) to gain experience with proposed changes to BCP

   specifications.  There is no requirement to approve a BCP

   specification for the experiment until the experiment is found to

   have value.



and



   In each case, the IESG's decision to go forward (or not) with a

   procedural experiment, or the steps leading up to one, is expected to

   reflect their judgment of the existence of rough consensus in the

   community.  That judgment may be appealed using the usual procedures,

   but the IESG and the community are reminded that an experimental

   attempt to try something for a fixed period is typically a better

   engineering approach than extended philosophical discussion without

   any experience to back it up.


No one understands the last sentence better than Harald, of course ...

Spencer