Content Comparison

...

Actions: 

• 16 Sep 2015: Assignees to modify the wording of this recommendation  
• 22 Sep 2015: Ariel Liang to email this recommendation to the IANA-issues mailing list to encourage members to propose modified wording. 
  
  

...

• 09 Sep 2015: 
  • It seems to be a standard practice as it is reflected in the way that working groups and the Board conduct their work. 
  • It is uncertain whether all participants explicitly declare and update existing or potential conflicts-of-interests. This request doesn't seem to be included in the CCWG-Accountability Report. 
• 16 Sep 2015: 
  
  • The wording of this recommendation seems to be a bit over-reaching. We may not want to have all members to declare conflicts of interests during every single vote. We, however, expect members to update their conflicts of interests regularly. 
  • Re conflicts of interests updates, it seems that every community group has some type of rules (e.g. SOIs in GNSO, ALAC) that are appropriate to what they are doing. 
  • Conflict of interests issues will be dealt with by CCWG-Accountability WS2? 
• 22 Sep 2015: 
  
  • Members' conflicts of interests should be updated if their status change (with regard to their work and other potential areas of conflict of interests). 
• 06 Jun 2016: 
  

  •  At-Large Community has already established the practice of updating SOIs before elections and selections

  • Some ICANN community groups require members to update their SOIs whenever a meeting takes place (more than requested in the recommendation) (e.g. every GNSO council member states changes to their SOIs, if any, at the beginning of every Council meeting); however, there is limitation to expand this practice in every stakeholder group (e.g. ccNSO);

  • ALAC to follow GNSO’s example to require members to update their SOIs and state changes, if any, before every ALAC meeting as a standing agenda item