Rogue Operator Work Party Meeting Notes – 24 November 2020 The primary discussion of today’s meeting was around the RSSAC037 guiding principles and document organization describing what it means for an RSO to be rogue. Instead of describing specific principles and examples of violating each, it was proposed to describe major activities and examples of rogue behavior in 2 different sections: Objective/Technical/Measureable? This section will pretty much be a summary of actions/examples described in the current document for Guiding principles #2 and #6. Things like changing or removing zone contents, or using alternate protocols. Note that some types of technical behaviors are not easily measured. Subjective/Non-Technical/Unmeasureable This section will be smaller section which references actions that _could_ lead to a rogue operator situation, but are not strict (binary) indicators. The document shall not explicitly define actions that are rogue, but instead describe work party discussions on activities that are undesirable or could be further investigated by the SAPF to determine if they constitute a rogue operator. These would replace the current section titled “Definition of a Rogue Operator”. Paul Hoffman graciously volunteered to draft the first section, and I will draft the second section. As always, assistance, comments, and thoughts to the process are greatly appreciated via the working document as well as via the RSSAC Caucus mail list and work party meetings Steve has created a new Google doc which has RSSAC formatting and can hopefully be accessed fully by ICANN accounts. https://docs.google.com/document/d/1XS2dIl_Sv1f7e4pA19QHnHEmLgRSkgEI2-zD7Tp0... Thank you to all that participated in today’s call and for your input. Ken Renard S&TCD Contractor – ICF Sustaining Base Network Assurance Branch C5ISR Center, Space and Terrestrial Communications Directorate Office: 443-395-7809 kenneth.d.renard.ctr@mail.mil