Re: Last Call: 'Process for the IAB and IESG selection of IAOC members' to BCP

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The IAB+IESG selection draft is a good start at a selection procedure and set of guidelines. It does not address (and I suspect is not intended to address) how ISOC and nomcom appointees to the IAOC relate to the process or what their qualifications might be. I wonder, however, if that is a mistake. One could imagine ISOC coming up with a separate document, and the IETF coming up with a separate set of instructions for the nomcom, but I submit that such is not necessary if we can add few statements to this document.

To be in accordance with RFC 4071, the ISOC and nomcom appointees should be equally distanced from their constituencies - just as the IAB and IESG appointees do not represent the IAB or IESG but rather serve the entire community, the nomcom and ISOC appointees should serve the entire community. In ISOC's case, that is explicitly stated in RFC 4071. In "not representing a constituency but serving the entire community", it seems also that an understanding of both ISOC and IETF are important - it is hard to manage a relationship that one does not understand. This document states that the IAB and IESG appointees

   ... are also expected to be able to understand the
   respective roles and responsibilities of the IETF and ISOC in this
   activity, and be able to articulate these roles within the IETF
   community.

It seems to me that this should also be true of nomcom and ISOC appointees, and by the way, they should be able to explain this to ISOC's other members (organizational, chapter, and individual) as well, and should understand the ramifications of IAOC choices for both IETF and ISOC.

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?




On Jun 10, 2005, at 8:16 AM, The IESG wrote:
The IESG has received a request from the IAB and the IESG to
consider the following document:

- 'Process for the IAB and IESG selection of IAOC members '
   <draft-iab-iesg-iaoc-selection-01.txt> as a BCP

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@xxxxxxxx or ietf@xxxxxxxx mailing lists by 2005-07-07.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-iab-iesg-iaoc-selection -01.txt


_______________________________________________
IETF-Announce mailing list
IETF-Announce@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf-announce


_______________________________________________

Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]