Difference between revisions of "IESG Liaison"

From IAB Wiki
Jump to navigation Jump to search
m (Whardaker moved page IESGLiaison to IESG Liaison: typo)
(→‎Passing of Information: Expand clarification on things the liaison doesn't need to report)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Purpose ==
== Purpose ==


The [[IESG]] and the IAB have a close working relationship that requires joint meetings and discussions.  There are two members of the IAB that sit on the IESG, the first being the IAB chair as a de-facto member of the IESG, but does not take part in decisions made by the IESG (here after referred to as the IESG Liaison)They act primarily as an observer and occasionally offer IAB relevant perspectives as needed.  They may choose to participate in some of the IESG non-standards-activities work activities for the general improvement of the IETF.
The [[IESG]] and the IAB have a close working relationship that requires joint meetings and discussions.  There are two members of the IAB that sit on the IESG: the IAB chair and the IESG Liaison.  The IAB chair is a de-facto member of the IESG, but does not take part in decisions made by the IESG.  The IAB Liaison acts primarily as an observer and occasionally offers IAB relevant perspectives when needed.  They may choose to participate in some of the IESG non-standards-activities work activities for the general improvement of the IETF.


=== Attendance ===
=== Attendance ===
Line 10: Line 10:
*  IESG meetings at IETF conferences
*  IESG meetings at IETF conferences
*  the IESG retreat
*  the IESG retreat
*  the iabiesg jabber channel
*  the IESG chat channel
*  the iesg jabber channel
*  the IESG mailing list
 
Note that the IESG chat channel currently use Slack, but this could change in the future.


The IESG Liaison will not attend:
The IESG Liaison will not attend:
Line 21: Line 23:


The IESG Liaison is expected to capture information of interest to the IAB at IESG events and pass that back to the IAB via the IAB list(s) or at IAB meetings.  Although this is likely to be done by the IAB chair as well, the IESG Liaison serves as a neutral third-party to double check that all relevant information is indeed reported and to accurately summarize the opinions of the IESG.
The IESG Liaison is expected to capture information of interest to the IAB at IESG events and pass that back to the IAB via the IAB list(s) or at IAB meetings.  Although this is likely to be done by the IAB chair as well, the IESG Liaison serves as a neutral third-party to double check that all relevant information is indeed reported and to accurately summarize the opinions of the IESG.
IESG Liaisons should use their judgement on what to report and how to report it. It is normally not necessary to report every detail of the day-to-day progress of documents unless the document or related discussions were of note to the IAB. Likewise, it is not necessary to report information already reported to the IAB though different channels, such as working group, plenary, or other public meetings; proposed new working group charters; BoF requests; etc. Examples of relevant information to report include material changes to IETF processes, work likely to impact the IAB's view of the Internet architecture, or information impacting the IETF's relationship with other organizations.
At the time of this writing, the most recent IESG Liaison sent informal summaries to the IAB list prior to most IAB business meetings, as well as occasional "breaking news" emails when things of especial interest to the IAB happened between meetings. Future Liaisons, in consultation with fellow IAB members, might choose different approaches.
Since the introduction of Slack as the IETF chat channel, the IESG has increased the use of the IESG chat channel for substantive discussion. The IESG Liaison is urged to pay more attention to the chats than might have been necessary in the past.
=== Liaison Selection and Transition ===
The IESG Liaison is typically selected in the IAB meeting at the beginning of the March IETF meeting.
If a new Liaison is selected, that person immediately takes over for the role and should plan to attend the IESG meetings during that IETF meeting. At the time of this writing, the IESG usually meets on the Sunday of an IETF meeting, plus 2 to 3 breakfast meetings during the week. The new Liaison should work with the Secretariat to subscribe to the IESG calendar, mai list, and group chat channels.

Latest revision as of 16:57, 20 March 2022

Purpose

The IESG and the IAB have a close working relationship that requires joint meetings and discussions. There are two members of the IAB that sit on the IESG: the IAB chair and the IESG Liaison. The IAB chair is a de-facto member of the IESG, but does not take part in decisions made by the IESG. The IAB Liaison acts primarily as an observer and occasionally offers IAB relevant perspectives when needed. They may choose to participate in some of the IESG non-standards-activities work activities for the general improvement of the IETF.

Attendance

The IESG Liaison is expected to attend:

  • weekly IESG meetings
  • IESG meetings at IETF conferences
  • the IESG retreat
  • the IESG chat channel
  • the IESG mailing list

Note that the IESG chat channel currently use Slack, but this could change in the future.

The IESG Liaison will not attend:

  • any IESG executive sessions
  • any other IESG confidential discussions

Passing of Information

The IESG Liaison is expected to capture information of interest to the IAB at IESG events and pass that back to the IAB via the IAB list(s) or at IAB meetings. Although this is likely to be done by the IAB chair as well, the IESG Liaison serves as a neutral third-party to double check that all relevant information is indeed reported and to accurately summarize the opinions of the IESG.

IESG Liaisons should use their judgement on what to report and how to report it. It is normally not necessary to report every detail of the day-to-day progress of documents unless the document or related discussions were of note to the IAB. Likewise, it is not necessary to report information already reported to the IAB though different channels, such as working group, plenary, or other public meetings; proposed new working group charters; BoF requests; etc. Examples of relevant information to report include material changes to IETF processes, work likely to impact the IAB's view of the Internet architecture, or information impacting the IETF's relationship with other organizations.

At the time of this writing, the most recent IESG Liaison sent informal summaries to the IAB list prior to most IAB business meetings, as well as occasional "breaking news" emails when things of especial interest to the IAB happened between meetings. Future Liaisons, in consultation with fellow IAB members, might choose different approaches.

Since the introduction of Slack as the IETF chat channel, the IESG has increased the use of the IESG chat channel for substantive discussion. The IESG Liaison is urged to pay more attention to the chats than might have been necessary in the past.

Liaison Selection and Transition

The IESG Liaison is typically selected in the IAB meeting at the beginning of the March IETF meeting.

If a new Liaison is selected, that person immediately takes over for the role and should plan to attend the IESG meetings during that IETF meeting. At the time of this writing, the IESG usually meets on the Sunday of an IETF meeting, plus 2 to 3 breakfast meetings during the week. The new Liaison should work with the Secretariat to subscribe to the IESG calendar, mai list, and group chat channels.