The RSSAC held a working session to develop the "Requirements for Measurements of the Local Perspective on the Root Server System." The main debate was over whether the data (results from the tool) should be made publicly available. If the tool is primarily for root server operators then the team should drop the recursive operator language. Likewise, there were concerns over the [[RFC]] language used around “data repository users should publish their results.” RSOs just using it for their own needs may hesitate if they know their results will be published elsewhere. Public availability may be fine for researchers. [[Wes Hardaker]] suggested that there could be a button on the results page that says “publish results;” he has had good results with this type of button on a DNSSEC checking tool. Thus, he argued results publication should be opt-in, not opt-out. Conversely, [[Brad Verd]] argued that data results should be shared in exchange for using the service and that the notice that users can opt out can be included at the beginning or end of the process. [[Paul Hoffman]] reminded the group to emphasize that the tool is for information, not giving best/good evaluations or determinations.
+
The RSSAC held a working session to develop the "Requirements for Measurements of the Local Perspective on the Root Server System." The main debate was over whether the data (results from the tool) should be made publicly available. If the tool is primarily for root server operators then the team should drop the recursive operator language. Likewise, there were concerns over the [[RFC]] language used around “data repository users should publish their results.” RSOs just using it for their own needs may hesitate if they know their results will be published elsewhere. Public availability may be fine for researchers. [[Wes Hardaker]] suggested that there could be a button on the results page that says “publish results;” he has had good results with this type of button on a [[DNSSEC]] checking tool. Thus, he argued results publication should be opt-in, not opt-out. Conversely, [[Brad Verd]] argued that data results should be shared in exchange for using the service and that the notice that users can opt-out can be included at the beginning or end of the process. [[Paul Hoffman]] reminded the group to emphasize that the tool is for information, not giving best/good evaluations or determinations.