This page lists the mailing lists used by the IAB for discussion and announcements. Other discussion lists can also be found on the IETF webpage (see https://www.ietf.org/how/lists/discussion/). All non-working group mailing lists, including IAB mailing lists, are listed in the IETF datatracker: https://datatracker.ietf.org/list/nonwg
Besides a small set of IAB maintained discussion lists, the IAB also provides a public mailing list for each Technical Program (see below) and usually creates a separate list for each workshop that is active until the workshop report has been published.
For internal discussion, the IAB uses its email@example.com mailing list. While this list and its archives are not public, everybody is invited to send mail to this address in order to engage in a direct communication with the IAB or to provide feedback to the IAB. This mailing list includes all voting IAB members, the IRTF Chair (Colin Perkins), the IETF Executive Director (Jay Daley), the IETF Director of Communications and Operations (Greg Wood), Secretariat staff (Cindy Morgan, Amy Vezza), the IESG Liaison (Martin Vigoureux), the ISOC Liaisons (Karen O’Donoghue, Olaf Kolkman), and the Tools Liaison (Robert Sparks).
Similarly the IAB Chair can be reached under firstname.lastname@example.org.
The IAB is responsible for the IETF’s liaison management. This responsibility is performed by IAB-selected liaison managers as well as the liaison coordinator role within the IAB. The liaison coordinators can be reached under email@example.com.
IAB mailing lists are moderated using a sergeant-at-arms (SAA) model to ensure there are no inappropriate postings. Inappropriate postings consist of: spam and bulk e-mail; unprofessional commentary, regardless of subject; and mail with content unrelated to technical discussion or other topics related to the IAB and the IETF. The sergeants-at-arms are empowered to restrict a person’s ability to post to the list and to request that a particular discussion thread cease when the content is inappropriate and represents a pattern of abuse. Complaints regarding a decision or action of a list’s SAA should be referred to the IAB chair.
The current sergeants-at-arms for the architecture-discuss list are Tommy Pauly and Jiankang Yao. For program-specific lists, the program chairs act as moderators. The rfc-interest list is moderated by the Temporary RFC Series Project Manager.
IAB discussion lists
- Alias: firstname.lastname@example.org
- To subscribe: https://www.iab.org/mailman/listinfo/architecture-discuss
- Archive: https://mailarchive.ietf.org/arch/browse/architecture-discuss/
The architecture-discuss list serves as a technical discussion forum for all members of the IETF community that are interested in larger architectural issues. It is meant to be an open discussion forum for all long and/or wide range architectural concerns related to the Internet Architecture. In particular, it may be used to discuss and bring forth different points of view on controversial architectural questions. Discussions that drill down and dwell on specifics of individual protocols or technologies are to be discouraged, redirected to appropriate other fora, or re-cast to discussions of broader implications for Internet architecture.
This is an IAB-sponsored activity. IAB members participate as individuals and not representatives of the IAB. Community discussion of IAB activities and programs occurs on architecture-discuss, but messages for IAB business should still be directed to email@example.com.
- To subscribe: https://www.rfc-editor.org/mailman/listinfo/rfc-interest
- Archive: https://www.rfc-editor.org/pipermail/rfc-interest/
This mailing list has been created by the RFC Editor to facilitate community discussion on the RFC series and to make suggestions about RFC Editor functions. The RFC Editor hopes that this mailing list will provide a focal point for input, information, and discussion about the details of the RFC process, as well as an archive to avoid the continual re-hashing of some issues. Topics appropriate to this list may include formatting, tools, style, content, and indexing aspects of the RFC series. It should not be used for discussion of the IETF standards process, general IETF organizational issues, or issues for which the NOTE WELL admonition is needed for IPR reasons.
- To subscribe: https://www.iab.org/mailman/listinfo/i18n-discuss
- Archive: https://mailarchive.ietf.org/arch/browse/i18n-discuss/
This list is for open discussion of internationalization in the Internet architecture.
Program mailing lists
- To subscribe: https://www.iab.org/mailman/listinfo/edm
- Archive: https://mailarchive.ietf.org/arch/browse/edm/
Evolvability, Deployability, & Maintainability (Proposed) Program: The IAB is discussing formation of an IAB program on this topic. For the present this list is for initial informal discussions on Evolvability, Deployability, & Maintainability.
- To subscribe: https://www.iab.org/mailman/listinfo/model-t
- Archive: https://mailarchive.ietf.org/arch/browse/model-t/
The model-t list is for discussions about changes in Internet deployment patterns and their impact on the Internet threat model, and to develop advice for designing, implementing and deploying Internet protocols in ways that account for these changes. Output of the program may eventually contribute to the IETF consensus process if the IETF believes an update to BCP 72/RFC 3552 is warranted and thus ought be consistent with related IETF consensus positions, such as BCP 188 and BCP 200.
- To subscribe: https://www.iab.org/mailman/listinfo/rfced-future
- Archive: https://mailarchive.ietf.org/arch/browse/rfced-future/
This list is for discussion of the further evolution of the RFC Editor model.