All, As we approach the Buenos Aires meetings, it would be good to consider precisely how we should structure the work before us that leads to the Final Report and Recommendations. Our target completion date is December 20, which allows time for final editing of the document if necessary. Essentially, the ATRT2 will receive 4 "waves of input" to factor into the Final Report and Recommendations: First, input from the Community at our face-to-face meetings in Buenos Aires. Second, public comments in response to our Draft Report and Recommendations. The Reply Comment period will close on December 13. Third, input from ICANN Staff concerning proposed Recommendations and "implementability." Fourth, a draft report from One World Trust that addresses the issue of metrics. It will be critical to consider all these inputs and reshape the Final Report and Recommendations, if necessary. Therefore, I suggest we consider and discuss the following approach to structuring the work. 1. Inputs from Buenos Aires face-to-face meetings with the Community It will be critical to capture inputs that might change the Report and Recommendations while we are in Buenos Aires and reach conclusions about necessary changes. ATRT2 members will need to listen attentively and take notes of points made by Community members that might result in changes to the Report. To the extent that Community members agree with points made in the Report, we need not necessarily focus on those comments for purposes of future editing. For points that may change the Report, I would ask ATRT2 members to circulate their notes and their opinions on those points to the ATRT2 list before we depart Buenos Aires. 2. Inputs from public comments to our Draft Report. To date, no comments have been received. It is very likely that the majority of comments will be received close to the December 13 closing date of the Reply Comment period. The Chair and Vice Chairs have agreed to divide and read the Comments received in full to provide input to the full ATRT2 concerning potential changes to the Report. I believe that the Work Stream Chairs should likewise be prepared to read comments in full that pertain to the subject matter of their respective Work Stream and be prepared to provide input to the full ATRT2 concerning potential changes to their section of the Report. Of course, all ATRT2 members are encouraged to read all the public comments and provide inputs that are likely to change the Report to the ATRT2 list along with their opinions on the inputs from the Community. Since it will be important to provide citations to public comments in the Final Report, I would ask all ATRT2 members who submit input to the ATRT2 list, along with their opinion on why the inputs should change the Report, to include specific quotes and page number citations from the Comments in their emails. This will make any final editing of the Report more efficient for the editors. Given the closing date of December 13, and the target completion date of December 20, it will be important to have all inputs from the comments submitted to the ATRT2 list no later than December 17. 3. Input from ICANN Staff concerning proposed Recommendations and Implementability. Having discussed the timing of these inputs to the ATRT2 with Staff, a request that all such inputs be received no later than the week of December 9 has been made to the Staff to provide sufficient time for consideration before December 20. 4. Input from One World Trust on metrics. ATRT2 likewise has asked One World Trust if it could provide, at a minimum, a draft of its report to ICANN no later than the week of December 9 and One World Trust has indicated that it can accommodate that request. Final ATRT2 conference calls: ATRT2 has two final conference calls scheduled for December 5 and December 19, respectively. While the above represents a significant amount of input and analysis by ATRT2, if we are disciplined and coordinated in our approach to the work, I am confident we can take all of it into consideration and produce a Final Report and Recommendations that we can all support without reservations. Finally, I am attaching tow documents that I had previously sent to the ATRT2 list. One is a draft of "observations" concerning the ATRT2 process and suggestions of how the ATRT process could be improved in the future. The other is a document describing audit techniques that the ICANN Structural Improvements Committee is considering to improve the "Institutional Reviews." ATRT2's observations may be one of the most critical aspects of the ATRT2 Report and I ask you to read the documents and offer your thoughts at our meeting in B.A. Best regards and looking forward to seeing you all soon. Brian