![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
It seems to me that what would be required to do so would be three statements:
ISOC's appointees do not represent ISOC, in the same way that IAB and IESG appointees do not represent the IAB or IESG. They serve the entire community.
Nomcom appointees do not represent a subclass of all IETF participants, in the same way that IAB and IESG appointees do not represent the IAB or IESG. They serve the entire community.
Since the IAOC manages the relationship between ISOC and the IETF, direct understanding of both IETF and ISOC is of value in all appointees.
Is there any reason the document shouldn't say that?
regards,
Geoff
`
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.