Hiya, On 03/05/2019 19:55, Deen, Glenn (NBCUniversal) wrote: > > The LLC Board manages a budget, oversees the Executive director, and > worries about getting sponsors to contribute funding to the IETF. > It is not engaged in setting IETF technical direction in any way. > It's the actual work of the IETF that I'm far more concerned about > COI. Fair point. Though the potential conflicts that might be likely for LLC board members might qualitatively differ from those that'd be most tricky for IESG or IAB (or WG chairs or document authors). And it could be that the potential conflicts for LLC board members are better understood generally? > COI would seem much more relevant for IAB and IESG and even the > NOMCOM itself which actually have the ability to set or influence > IETF decisions and direction. Yet we do not require any public > disclosure of COI from any of those positions. Perhaps we ought? I'd be for discussing it (and for it). But even if we don't (immediately), there's nothing wrong with the LLC board getting ahead of the game and providing a good example for the other laggards:-) > It seems we are proposing setting a much far higher bar for an > administrative body than we do for the actual working bodies of the > IETF. I hope not a higher-bar than for other bodies (in the longer term). But given the LLC is new, we do have the chance to raise the bar some, so no harm to do that. And perhaps declaring potential CoIs is more run of the mill for LLC-board-like entities? Cheers, S. > > glenn  > > > > >
Attachment:
0x5AB2FAF17B172BEA.asc
Description: application/pgp-keys
Attachment:
signature.asc
Description: OpenPGP digital signature
