Dear Ken, Thank you for providing the summary of the core writing group meeting as well as the agenda for the next Rogue RSO work party meeting. Just a minor correction on the start time of the next meeting: The next Rogue RSO work party meeting is on Tuesday, 23 February 2021 at 1400 UTC. Best, Ozan Sahin Policy Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Telephone: +90 212 999 6218 Mobile: +90 533 641 0007 Skype: ozan.sahin.icann www.icann.org<applewebdata://021EB1F1-F6B6-443A-908F-419605BF3A61/www.icann.org> From: rssac-caucus <rssac-caucus-bounces@icann.org> on behalf of Ken Renard via rssac-caucus <rssac-caucus@icann.org> Reply-To: Ken Renard <kdrenard2@gmail.com> Date: 21 February 2021 Sunday 18:36 To: RSSAC Caucus <rssac-caucus@icann.org> Subject: [RSSAC Caucus] Rogue Operator Work Party: writing team summary and agenda for meeting on 23 Feb The core writing team for the Rogue Operator Work Party met on 17 February. We discussed the following: 1. While the primary audience is a future governance body, we expect some casual readers (the word "rogue" will attract curious minds). 2. The section on "Damage that can be done by a rogue operator" was reduced and moved to the introduction, setting the tone for "why we care" about rogue operators 3. The background section is largely technical and may not be necessary for the discussion and audience. We plan to reduce this section to only the technical information needed to understand the rest of the document. 4. Objective examples of Rogue behavior. Added descriptive title to each example for document flow and readability. These titles are suggestions and we are looking for refinement. 5. Wes added text in the description of subjective examples of rogue operators that separated rogue organizations versus rogue individuals. 6. Subjective example #3 was reworded to move emphasis from "making statements" to "reducing the trust in the RSS". We might need more descriptive text here. Agenda for meeting on 23 February 2021: 1. Review latest changes to document 2. Discussion of new text, sections 3. Detection of rogue operators -- what (if anything) should we say? (“It’s hard to do”) 4. Recommendations section The document is at: https://docs.google.com/document/d/1XS2dIl_Sv1f7e4pA19QHnHEmLgRSkgEI2-zD7Tp0... [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1XS2dIl_Sv1f7e...> We encourage you to review and provide comments in the document, on this mail list, or at the next meeting on 23 February 2021 at 1300 UTC -Ken Renard