Re: [IAB] RSOC Apology

[Richard Barnes <rlb@xxxxxx>]

On Wed, Jul 24, 2019 at 3:23 PM Aaron Falk <aaron.falk@xxxxxxxxx> wrote:

On 24 Jul 2019, at 15:11, Ted Hardie wrote:

As the RSOC is responsible to the IAB, I would very much like to hear a similar statement from the IAB, the chair or the IAB’s RSOC program lead, regarding what mistakes were made so the community can consider whether the current arrangements require change before moving forward with finding an interim RSE.

The two comments sent by the IAB already express our regret and discuss one aspect of what we think might need to change. 

(I’m mindful of conserving my minute at the plenary mic so I’m trying to hash this out here...)

Are you saying the the IAB has not erred in this?

Not to speak for Ted, but my understanding as a community member, based on the fact presented, is that the IAB has not erred in their oversight of the RSE.  They have followed the processes established in RFC 6635, and conducted due oversight of the RSE function, via the RSOC.  The RFC++ BoF was misguided, but the IAB acknowledged that more than a year ago.

--Richard

 

The note you point to below discusses the IAB’s regret (not an apology to the community) nor any admission of error. Is there nothing the IAB should have done differently? It’s a long thread so maybe I missed it. That is different as to whether the RFC6635 should change.

--aaron