Dear All,

To Paul’s question, although this does not concern a required vote per the ICANN Bylaws, the Council does typically take formal decisions by means of a motion and vote. Paul is correct that previous communications on this topic to the Board have been handled through correspondence (non-objection approach), but as this represents a decision and a direction that the Council is aiming to convey to the Board, including a number of conditions, it may want to consider doing this through a motion? At the end of the day, however, this is a decision for Council to make. A draft motion is available, but if there is a general preference to convey the Council’s position to the Board via a letter, the Council could consider that path as well.

In relation to the next small team meeting (Tuesday 18 October at 14.00 UTC.), please find hereby the proposed agenda:

1. Welcome
2. Update on ICANN org – Registrar engagement regarding sending data disclosure request via encrypted email to participating registrars and future API
3. Outstanding items in addendum for review:
   1. Whois Disclosure System data collection & reporting
   2. Section 3 – recommendation to GNSO Council
   3. Other?
4. Timeline next steps:
   1. 20 October – Council meeting – update to Council on status of work and direction of thinking
   2. 25 October at 14.00 UTC – EPDP Phase 2 small team meeting to consider Council feedback and any outstanding issues on the addendum
   3. 26-4 November – schedule additional meetings as needed
   4. By 7 November at the latest – submit final version of addendum to GNSO Council
   5. 17 November – GNSO Council consideration of small team addendum
5. AOB

If there are any further outstanding items that should be added to agenda item #3, please share these with the list.

Best regards,

Marika