<div dir="ltr">Hi,<div><br></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><br>Best,</div><div><br></div><div>Rafik</div><div><br><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 </div></div><div dir="auto"><br></div><div dir="auto">Our stance on this is that we don't accept any accreditation<div style="font-family:verdana,sans-serif;display:inline">/a</div><div style="font-family:verdana,sans-serif;display:inline">ccess</div>model that has not been developed by the community.<div style="font-family:verdana,sans-serif;display:inline">Our</div><div style="font-family:verdana,sans-serif;display:inline">very first question should b</div>e<div style="font-family:verdana,sans-serif;display:inline">whet</div><div style="font-family:verdana,sans-serif;display:inline">her we need an accreditation model. We</div><div style="font-family:verdana,sans-serif;display:inline"> </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.</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.</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">Thanks </div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif"><br></div></div><div><br><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 text="#000000" bgcolor="#FFFFFF">
<p><font size="+1"><font face="Lucida Grande">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.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">cheers STeph</font></font><br>
</p>
<div class="m_-4167542296814091604m_6482487677998924652m_-4583685808121013917moz-forward-container"><br>
<br>
-------- Forwarded Message --------
<table class="m_-4167542296814091604m_6482487677998924652m_-4583685808121013917moz-email-headers-table" cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">Subject:
</th>
<td>[Accred-Model] Version 1.7 of the Accreditation and
Access Model</td>
</tr>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">Date: </th>
<td>Fri, 20 Jul 2018 21:12:11 +0000</td>
</tr>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">From: </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></td>
</tr>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">To: </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></td>
</tr>
</tbody>
</table>
<br>
<br>
<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><u></u></p>
<p class="MsoNormal"><u></u> <u></u></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><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Other notable updates to this version 1.7:<u></u><u></u></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal">The
introduction section has been updated.<u></u><u></u></li>
<li class="MsoNormal">Annex A
is now titled “Rationale” and edited accordingly.<u></u><u></u></li>
<li class="MsoNormal">Annex C
is now populated with input from cybersecurity experts.<u></u><u></u></li>
<li class="MsoNormal">Annex F
(verification and compliance for private parties) is now
populated.<u></u><u></u></li>
<li class="MsoNormal">Annex G
is a discussion on accreditation oversight and types.<u></u><u></u></li>
</ul>
<p class="MsoNormal"><u></u> <u></u></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><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Fabricio
Vayra</span></b><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#d6001c"></span></b><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#75787b">|
</span></b><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#d6001c">Perkins
Coie LLP<u></u><u></u></span></b></p>
<p class="MsoNormal"><b><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#75787b">PARTNER<u></u><u></u></span></b></p>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#75787b">D.
+1.202.654.6255<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<br>
<hr>
<font size="1" face="Arial" color="Gray"><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.<br>
</font>
</div>
</div>
_______________________________________________<br>
NCSG-PC mailing list<br>
<a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br>
</blockquote></div></div>
_______________________________________________<br>
NCSG-PC mailing list<br>
<a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br>
</blockquote></div></div></div>