Dear all, as you know, WA 4 is working on a list of contingencies that we need to address when working on accountability mechanisms. This work is still in progress and we will surely discuss the individual items on the list in Frankfurt to then make a determination as to whether the list is complete and whether all items that are currently on the list are in scope of our work. While this work is going on, we recommend that either WA4 or other individuals start going through the list of contingencies (as well as contingencies that you think should be on the list, which are not yet there) and start analyzing whether these contingencies are already being taken care of by existing accountability mechanisms or work previously done by ICANN (and its community). Such analysis will help us to better understand whether the list is complete and accurate. The outcome of this analysis can be the following: - A determination is made that the contingency is adequately addressed by an existing mechanism. In this case, we would conclude that no further work needs to be done on this item by this group and write a rationale to explain this. - A determination is made that the contingency is not adequately addressed by an existing mechanism. In this case, we would need to define what is missing and write that as part of our report. As we move on, we will then see what needs there are and analyze those. As an outcome of that analysis, we will potentially need to amend one or multiple existing accountability mechanisms or, where that proves insufficient or not feasible, establish new accountability mechanisms. Ideally, we would be able to cluster additional demand to ensure that we need to make as few changes / inventions as possible by coming up with responses that each cover multiple issues. We will discuss this during tomorrow’s call, but we would like to encourage you to review the current list and pick one or more contingencies that you would volunteer to work on. Thanks, Mathieu, León and Thomas