[CCWG-ACCT] Notes-Recordings-Transcript links for STRESS TESTS Meeting #5 - 29 April
Brenda Brewer
brenda.brewer at icann.org
Wed Apr 29 12:41:09 UTC 2015
Dear all,
The notes, recordings and transcripts for the CCWG Accountability Stress Tests Meeting # 5 on 29
April will be available here: https://community.icann.org/pages/viewpage.action?pageId=52895716
Action Items
ACTION ITEM - Steve to draft paragraph that takes up three or four points that Mathieu identified
ACTION - Steve to provide DIY text
Notes
These high-level notes are designed to help you navigate through content of the call and do not
substitute in any way the transcript.
1 Review red text
Red text on p 11 and 16 - Proposed measure to except ICANN from exceeding mission
Proposed mission statement could be standard of review
It would take reconsideration or IRP to trigger it.
AGREEMENT - New text to be added quoting standard of review
2 Address Mathieu's edits (blue text)
- P3 Stress Test # 9
Spilling Board would be a potential accountability mechanism but never regarded as useful one i.e.
last resort
AGREEMENT - OK with proposed text
- p4 Stress Test #11
Suggestions to remove "mitigation", to use risk mitigation measures", to remove "preventive"
AGREEMENT - risk mitigation
-p7 Stress Test #21
AGREEMENT Ok with following edit "develop appropriate mechanism
- p12 Stress test #13
Standing is available to community.
Is term "appeal" appropriate?
Suggestion to use reconsideration and IRPs
We have not identified different standards of review
--> Discourage different standards
--> Would not recommend putting standards of review in WS1 work
- Suggestion to remove sentence: standards of review may need to be ajdusted sentene and to include
Mathieu's text
- WS1 - WS2 or future Review panels?
AGREEMENT - Remove sentence: standards of review may need to be ajdusted sentene and to include
Mathieu's text.
Frivolous and vexatious: match with what is in the proposal --> frivolous and abusive
Conclusion cell
Suggested text: Proposed measures would reduce risk by supermajority requirements and by dismissla
of frivolous or abusive RR and IRPs
Individual will have standing but expectation that people use it in way that is accountable to
community
- Proposal: Proposed measures would could increase risk of individuals paralyzing ICANN processes,
which is mitigated by dismissal of frivolous or abusive RR and IRPs
- Suggestion to use "overload"
--> Continued usage may paralyze business, not just overload it
--> Improperly impede/interfere
AGREEMENT - Remove overload and use impede - Improved access to review and redress could allow
indivdual to impede ICANN processes, though this is mitigated by dismissal of frivolous or abusive
RR and IRPs
3. Consider adding management abstract paragraph
ACTION ITEM - Steve to draft paragraph that takes up three or four points that Mathieu identified
4. To help manage public comment process, do it yourself guide to prevent additional stress-tests
being added
Do it yourself to guide current proposed and measures making it clear that community powers we are
designing can not prevent external threat (hacker, earthquake etc).
Suggestion to give example of specific concerns and show how that gets translated using buckets we
have
ACTION - Steve to provide DIY text
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/accountability-cross-community/attachments/20150429/161615d9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 92 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/accountability-cross-community/attachments/20150429/161615d9/image001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5035 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/accountability-cross-community/attachments/20150429/161615d9/smime.p7s>
More information about the Accountability-Cross-Community
mailing list