How the NFSv4 working group "meets" - what are the options...

Given recent comments on the WG alias about how the work of the NFSv4
working group “works” needs to be addressed.  I am starting a separate
thread such that all working group members might benefit from a reminder of
what resources are available to accomplish the work of the working group.

First, the brief, “marketing” message of how the IETF accomplishes work is
here:


https://www.ietf.org/how/



However, the more fruitful reference is from RFC 2418 “IETF Working Group
Guidelines and Procedures”

I have included a quote from that RFC below for reference.



As working group co-chair, I always assume that the working group is
meeting at the main IETF meetings.  While I have in the past suggested that
the WG work under the assumption that it would “not” meet, the consensus at
the time that this position was inappropriate.  Therefore, we always plan
to meet.

However, the NFSv4 working group does not always meet and I am required, as
a working group co-chair, provide an agenda well in advance of the
meeting.  I have queried the working group for an agenda to build that
content and secondarily query working group members about their planned
participation at an upcoming meeting.

Given the small numbers of active participants, all it takes is the absence
of 2 member of the active core to make it difficult to have an effective
face to face meeting at the IETF meeting.  Case in point is the most recent
IETF 105 meeting and there were 11 participants. Four of these are active
authors/editors and the remaining participants were there for
administrative support or general interest.  My point is if 2 of those 4
individuals were missing – it would have been significantly less
productive.  That could be perfectly fine to have small numbers but it is
obviously prudent to plan ahead to ensure that the meeting is a good use of
everyone’s time and a good use of the space utilized during the broader
IETF meeting – space is a premium.

As for other meetings, conference calls, interim meetings, and other
working group meetings are all perfectly fine.  As the quoted text below
indicates, these meetings can occur as long as there is broad knowledge of
the meeting, it is open to participation, and that minutes are collected
and reported out.  The co-chairs do not have to be present for these
alternative working group meetings – our responsibility is that the minutes
are collected and reported broadly.  So, if there is going to be working
group meeting, notify enough in advance, invite everyone, take minutes and
record them.



Spencer


https://www.rfc-editor.org/rfc/rfc2418.txt





3.1. Session planning



   For coordinated, structured WG interactions, the Chair(s) MUST

   publish a draft agenda well in advance of the actual session. The

   agenda should contain at least:



   - The items for discussion;

   - The estimated time necessary per item; and

   - A clear indication of what documents the participants will need to

     read before the session in order to be well prepared.



   Publication of the working group agenda shall include sending a copy

   of the agenda to the working group mailing list and to

   [email protected].



   All working group actions shall be taken in a public forum, and wide

   participation is encouraged. A working group will conduct much of its

   business via electronic mail distribution lists but may meet

   periodically to discuss and review task status and progress, to

   resolve specific issues and to direct future activities.  IETF

   Plenary meetings are the primary venue for these face-to-face working

   group sessions, and it is common (though not required) that active

   "interim" face-to-face meetings, telephone conferences, or video

   conferences may also be held.  Interim meetings are subject to the

   same rules for advance notification, reporting, open participation,

   and process, which apply to other working group meetings.



   All working group sessions (including those held outside of the IETF

   meetings) shall be reported by making minutes available.  These

   minutes should include the agenda for the session, an account of the

   discussion including any decisions made, and a list of attendees. The

   Working Group Chair is responsible for insuring that session minutes

   are written and distributed, though the actual task may be performed

   by someone designated by the Working Group Chair. The minutes shall

   be submitted in printable ASCII text for publication in the IETF

   Proceedings, and for posting in the IETF Directories and are to be

   sent to: [email protected]

_______________________________________________
nfsv4 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nfsv4