Re: Proposed IETF Trust Conflict of Interest Policy for Community Review



On 30/03/16 02:44, Brian E Carpenter wrote:

- Why isn't this aiming to end up being a document subject to IETF
  consensus? I can imagine there may be good or bad reasons for
  either doing this via the IETF process or not doing it via the
  IETF process, but I wondered - it seems like this is not just
  some minor operational thing, and considering these issues and
  aiming to get IETF consensus on how/when to declare conflicts
  of interest could be useful more generally. Is there something
  substantially different about the trust in this respect vs.
  other IETF roles such as chair, author, AD etc?


IANAL, but I think the answer is yes: a Trust does have a very
specific legal status, in a way that the IETF or IAB don't have.
So I think it's normal that the Trust enacts its own CoI policy,
and of course correct that the Trust asks for community input
first.


I can well believe that that's the case, but also not being an
"L" I don't know. Even if so, the trust could decide that they
wanted their scheme to have IETF consensus, which is a separable
question.

OTOH, maybe it'd be good to have a better way to deal with CoI
in general. The former doesn't have to block on the latter though.

Among reasons for a broader consideration of CoI, and not just
as needed for the trust right now, is that we don't currently
have any way for folks to declare such a conflict, (well,
except that IESG members can ballot "recuse" I guess). I've
had a couple of cases where I've told various folks that I
didn't want to be the AD for a WG because I was working on
something related, but there was no way to record that so
that someone looking back could know about it. That said,
figuring out something usable and useful might be a lot of
work.

- Some trustees are selected by nomcom or other bodies. Wouldn't
  those proposing themselves for selection need to say something
  about known conflicts to selecting bodies like nomcom, so that
  we don't select folks who are conflicted out of being useful?
  And doesn't that mean that the list of conflicts needs to be
  public? And why shouldn't it be public? (Or did you intend it
  to be public? I wasn't sure.)


I think it would be good practice to make it public (even if certain
details were kept private). But it isn't just at selection time;
a new CoI could arise anytime, e.g. due to a change of job.


Sure. Mostly I meant that if CoI's are needed as a useful input
for nomcom, then they need to be published. There may be many
other reasons why publishing is good too, but we only really need
one.

In any case, if the trustees work out a process that works for
them and that involves published CoI declarations, then that's
an ok thing for now. If the trustee's scheme works, we might want
to look at adopting a variation of it more widely later on.

Cheers,
S.


    Brian

smime.p7s
Description: S/MIME Cryptographic Signature