Elkins 26241 USA WV tjw.ietf@gmail.com

gen This memo provides some suggestions for working group chairs in utilizing social media.

Introduction Many working groups in the IETF are focused in their length and direction. There are others which exist for a much longer period of time, especially operations groups among others. With these groups the chairs should make an effort to use other platforms than the datatracker and ietf mailing lists to make work visible.

Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here. DNS terminology is as described in .

Long running working groups There are several long running working groups in the IETF, and the work touches other organizations. DNSOP, HTTPBIS, TLS are just a few. With these groups, the chairs should adopt an approach of "oversharing is a good thing". Currently a number of working groups are using github to store materials, documents being worked on, etc. But these working groups should always be looking for new avenues to promote the documents being working on in the working group.

Using Social Media Currently, there is a tool to pull data from the datatracker API to automate posting into twitter [https://github.com/ietf-github-services/datatracker-tweet]. This has proven useful for working groups. DNSOP has modified this code to automate posting to Mastodon [https://github.com/ietf-wg-dnsop/datatracker-toots]. The Working Group Chairs should take this under consideration for busy, long running working groups.

Normative References Informative References

Acknowledgements Mark Nottingham for the datatracker-tweet code, and for the quote "Busy working groups should over share".