<div>I do agree that we should not accept an access model that has been developed informally, in isolation, by one segment of the community, however it seems very likely that this model (or something very similar to it) will be rolled out during the few weeks that the EPDP team has to develop an initial report. <br></div><div><br></div><div>So I think an annotated version of their model, laying out what should be our objections to it, would be an incredibly useful resource. Better to work on this now and to be able to immediately table it when their proposal is put forward. If you could produce this Stephanie, it would not be in vain... similarly for the annotated temp spec, this would be very helpful.<br></div><div><br></div><div>I think we also need to document somewhere why we think this EPDP is bound for failure (section J, excessive SO/AC participation, etc.) so we can refer back to this in the future when it inevitably happens. One of the issues with the GDPR was that while I know we (or at least Stephanie) had been calling ICANN out for its lack of adherence to the law, there was never a statement I could find, dated a few years in advance, calling for ICANN to comply with the GDPR. I think it would be useful if we prepared a small repository of either the abstentions or a short comment *dated ahead of the first EPDP meeting* that outlined our concerns and fears.<br></div><div><br></div><div>Best wishes, Ayden <br></div><div class="protonmail_signature_block"><div class="protonmail_signature_block-proton protonmail_signature_block-empty"><br></div></div><div><br></div><div>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br></div><div> On 22 July 2018 5:12 AM, Rafik Dammak <rafik.dammak@gmail.com> wrote:<br></div><div> <br></div><blockquote type="cite" class="protonmail_quote"><div dir="ltr"><div>Hi,<br></div><div><br></div><div><div>yes, they can try but there will be pushback. I think there is also the ICANN org UAM in the mix (for which we need to decide if we will respond or not). I won't speculate now but let's see how things will move in EPDP team and in particular for the gating questions first.<br></div><div><br></div><div>Best,<br></div></div><div><br></div><div>Rafik<br></div><div><div><br></div><div class="gmail_quote"><div dir="ltr">Le dim. 22 juil. 2018 à 09:04, farzaneh badii <<a href="mailto:farzaneh.badii@gmail.com">farzaneh.badii@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div dir="auto">Stephanie <br></div></div><div dir="auto"><br></div><div dir="auto"><div>Our stance on this is that we don't accept any accreditation<br></div><div style="font-family:verdana,sans-serif;display:inline">/a<br></div><div style="font-family:verdana,sans-serif;display:inline">ccess<br></div><div>model that has not been developed by the community.<br></div><div style="font-family:verdana,sans-serif;display:inline">Our<br></div><div style="font-family:verdana,sans-serif;display:inline">very first question should b<br></div><div>e<br></div><div style="font-family:verdana,sans-serif;display:inline">whet<br></div><div style="font-family:verdana,sans-serif;display:inline">her we need an accreditation model. We<br></div><div style="font-family:verdana,sans-serif;display:inline"> <br></div><div>provide our own access model when the opportunity arises. But by no means IPC/BC model can be accepted as a done deal or the only model that can be focused on.<br></div></div><div dir="auto"><br></div><div style="font-family:verdana,sans-serif">I think other councilors should be on the same page and if this gets discussed at the council support and bring up this view point.<br></div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">Thanks <br></div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif"><br></div></div><div><div><br></div><div class="gmail_quote"><div dir="ltr">On Sat, Jul 21, 2018 at 7:34 PM Stephanie Perrin <<a href="mailto:stephanie.perrin@mail.utoronto.ca" target="_blank">stephanie.perrin@mail.utoronto.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF"><p><span style="font-size:undefinedpx" class="size"><span style="font-family:Lucida Grande" class="font">as can be seen by the
62 page attachment, the BC and IPC have been busy working on
their accreditation model. We have to focus on this fast, it
will be brought in as a fait accompli to the EPDP as soon as
they can. I will do a markup as soon as I get the markup of
the interim spec done....but we need to know who is on the
EPDP as soon as possible, and start a new EPDP and observer
list.</span></span><br></p><p><span style="font-size:undefinedpx" class="size"><span style="font-family:Lucida Grande" class="font">cheers STeph</span></span><br></p><div class="m_-4167542296814091604m_6482487677998924652m_-4583685808121013917moz-forward-container"><div><br></div><div><br></div><div>-------- Forwarded Message --------<br></div><table class="m_-4167542296814091604m_6482487677998924652m_-4583685808121013917moz-email-headers-table" cellspacing="0" cellpadding="0" border="0"><tbody><tr><th valign="BASELINE" nowrap="" align="RIGHT">Subject:<br></th><td>[Accred-Model] Version 1.7 of the Accreditation and
Access Model<br></td></tr><tr><th valign="BASELINE" nowrap="" align="RIGHT">Date:<br></th><td>Fri, 20 Jul 2018 21:12:11 +0000<br></td></tr><tr><th valign="BASELINE" nowrap="" align="RIGHT">From:<br></th><td>Vayra, Fabricio (Perkins Coie) <a class="m_-4167542296814091604m_6482487677998924652m_-4583685808121013917moz-txt-link-rfc2396E" href="mailto:FVayra@perkinscoie.com" target="_blank"><FVayra@perkinscoie.com></a><br></td></tr><tr><th valign="BASELINE" nowrap="" align="RIGHT">To:<br></th><td>'<a class="m_-4167542296814091604m_6482487677998924652m_-4583685808121013917moz-txt-link-abbreviated" href="mailto:accred-model@icann.org" target="_blank">accred-model@icann.org</a>' <a class="m_-4167542296814091604m_6482487677998924652m_-4583685808121013917moz-txt-link-rfc2396E" href="mailto:accred-model@icann.org" target="_blank"><accred-model@icann.org></a><br></td></tr></tbody></table><div><br></div><div><br></div><div class="m_-4167542296814091604m_6482487677998924652m_-4583685808121013917WordSection1"><p class="MsoNormal">Attached for discussion and additional
comment is version 1.7 of the Accreditation and Access Model. <u></u><br></p><p class="MsoNormal"><u></u> <u></u><br></p><p class="MsoNormal">Note that Section II has been formatted in
a way to mirror the questions posed by ICANN Org in its recent
unified access model discussion paper. This version 1.7 is
meant to advance the very discussion on the critical need for
accreditation and access.<u></u><br></p><p class="MsoNormal"><u></u> <u></u><br></p><p class="MsoNormal">Other notable updates to this version 1.7:<u></u><br></p><ul style="margin-top:0in" type="disc"><li class="MsoNormal">The
introduction section has been updated.<u></u><br></li><li class="MsoNormal">Annex A
is now titled “Rationale” and edited accordingly.<u></u><br></li><li class="MsoNormal">Annex C
is now populated with input from cybersecurity experts.<u></u><br></li><li class="MsoNormal">Annex F
(verification and compliance for private parties) is now
populated.<u></u><br></li><li class="MsoNormal">Annex G
is a discussion on accreditation oversight and types.<u></u><br></li></ul><p class="MsoNormal"><u></u> <u></u><br></p><p class="MsoNormal">Again, thank you to those who made helpful
contributions to advancing this model. We look forward to a
robust discussion and further input.<u></u><br></p><p class="MsoNormal"><u></u> <u></u><br></p><p class="MsoNormal"><b><span style="color:black" class="colour"><span style="font-family:Arial, sans-serif" class="font"><span style="font-size:10pt" class="size">Fabricio
Vayra</span></span></span><span style="color:rgb(214, 0, 28)" class="colour"><span style="font-family:Arial, sans-serif" class="font"><span style="font-size:10pt" class="size"></span></span></span><span style="color:rgb(117, 120, 123)" class="colour"><span style="font-family:Arial, sans-serif" class="font"><span style="font-size:10pt" class="size">| </span></span></span><span style="color:rgb(214, 0, 28)" class="colour"><span style="font-family:Arial, sans-serif" class="font"><span style="font-size:10pt" class="size">Perkins
Coie LLP<u></u></span></span></span></b><br></p><p class="MsoNormal"><b><span style="color:rgb(117, 120, 123)" class="colour"><span style="font-family:Arial, sans-serif" class="font"><span style="font-size:7.5pt" class="size">PARTNER<u></u></span></span></span></b><br></p><p class="MsoNormal"><span style="color:rgb(117, 120, 123)" class="colour"><span style="font-family:Arial, sans-serif" class="font"><span style="font-size:7.5pt" class="size">D.
+1.202.654.6255<u></u></span></span></span><br></p><p class="MsoNormal"><u></u> <u></u><br></p></div><div><br></div><div><hr><span style="font-family:Arial" class="font"><span style="font-size:10px" class="size"><br>NOTICE: This communication may contain privileged or other
confidential information. If you have received it in error,
please advise the sender by reply email and immediately delete
the message and any attachments without copying or disclosing
the contents. Thank you.</span></span></div></div></div><div>_______________________________________________<br></div><div> NCSG-PC mailing list<br></div><div> <a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a><br></div><div> <a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br></div></blockquote></div></div><div>_______________________________________________<br></div><div> NCSG-PC mailing list<br></div><div> <a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a><br></div><div> <a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br></div></blockquote></div></div></div></blockquote><div><br></div>