<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="script-src 'self'; img-src * cid: data:;">
<style id="x_outgoing-font-settings">
<!--
#x_response_container_BBPPID
{font-family:initial;
font-size:initial;
color:initial}
-->
</style>
<div style="background-color:rgb(255,255,255); line-height:initial">
<div id="x_response_container_BBPPID" dir="auto" style="outline:none">
<div name="x_BB10" id="x_BB10_response_div_BBPPID" dir="auto" style="width:100%">
Agree with George K that if APAC attendance is light for these calls that we should consider whether or not to have calls in this time slot at this point of our process I hate to think that a number of working group members miss these calls at this juncture
because we are sticking to a time slot to accommodate folks that end up not attending. </div>
<div name="x_BB10" id="x_response_div_spacer_BBPPID" dir="auto" style="width:100%">
<br style="display:initial">
</div>
<div id="x_blackberry_signature_BBPPID" name="x_BB10" dir="auto">
<div id="x__signaturePlaceholder_BBPPID" name="x_BB10" dir="auto"></div>
</div>
</div>
<div id="x__original_msg_header_BBPPID" dir="auto">
<table width="100%" style="background-color:white; border-spacing:0px; display:table; outline:none">
<tbody>
<tr>
<td colspan="2" style="padding:initial; font-size:initial; text-align:initial; background-color:rgb(255,255,255)">
<div style="border-right:none; border-bottom:none; border-left:none; border-top:1pt solid rgb(181,196,223); padding:3pt 0in 0in; font-family:Tahoma,"BB Alpha Sans","Slate Pro"; font-size:10pt">
<div id="x_from"><b>From:</b> icann@leap.com</div>
<div id="x_sent"><b>Sent:</b> September 26, 2018 11:19 AM</div>
<div id="x_to"><b>To:</b> nathalie.peregrine@icann.org</div>
<div id="x_cc"><b>Cc:</b> gnso-rpm-wg@icann.org; gnso-secs@icann.org</div>
<div id="x_subject"><b>Subject:</b> Re: [gnso-rpm-wg] Recordings, attendance & AC chat from Review of all Rights Protection Mechanisms (RPMs) PDP Working Group call on Wednesday 26 September 2018</div>
</div>
</td>
</tr>
</tbody>
</table>
<br>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">[resending, as I sent the prior email from an unsubscribed email address]<br>
<br>
The attendance record is not accurate. e.g. my name (George Kirikos)<br>
is missing. Also, Georges Nahitchevansky's first name is missing the<br>
's'. There might be other errors beyond that.<br>
<br>
Also, it seems participation from Asia-Pacific based members was quite<br>
light on this call (which was supposed to be APAC-friendly), if the<br>
(revised) attendance was accurate. Perhaps a different time slot needs<br>
to be considered?<br>
<br>
Sincerely,<br>
<br>
George Kirikos<br>
416-588-0269<br>
<a href="http://www.leap.com/">http://www.leap.com/</a><br>
<br>
On Wed, Sep 26, 2018 at 11:06 AM, Nathalie Peregrine<br>
<nathalie.peregrine@icann.org> wrote:<br>
> Dear all,<br>
><br>
> Please find the attendance and AC Chat attached to this email, and the MP3 &<br>
> AC recording below for the Review of all Rights Protection Mechanisms (RPMs)<br>
> PDP Working Group call held Monday, 26 September 2018 at 12:00 UTC.<br>
> Attendance and recording of the call is also posted on agenda wiki page:<br>
> <a href="https://community.icann.org/x/ZgKNBQ">https://community.icann.org/x/ZgKNBQ</a><br>
><br>
> MP3: <a href="https://audio.icann.org/gnso/gnso-rpm-review-26sep18-en.mp3">https://audio.icann.org/gnso/gnso-rpm-review-26sep18-en.mp3</a><br>
><br>
><br>
><br>
> AC Recording: <a href="https://participate.icann.org/p8ed3wvepp7/">https://participate.icann.org/p8ed3wvepp7/</a><br>
><br>
><br>
><br>
><br>
><br>
> The recordings and transcriptions of the calls are posted on the GNSO Master<br>
> Calendar page: <a href="https://gnso.icann.org/en/group-activities/calendar">https://gnso.icann.org/en/group-activities/calendar</a><br>
> [gnso.icann.org]<br>
><br>
><br>
><br>
> ** Please let me know if your name has been left off the list **<br>
><br>
><br>
><br>
> Mailing list archives: <a href="http://mm.icann.org/pipermail/gnso-rpm-wg/">http://mm.icann.org/pipermail/gnso-rpm-wg/</a><br>
><br>
><br>
><br>
> Main wiki page for the working group: <a href="https://community.icann.org/x/wCWAAw">
https://community.icann.org/x/wCWAAw</a><br>
> [community.icann.org]<br>
><br>
><br>
><br>
> Thank you.<br>
><br>
> Kind Regards,<br>
><br>
> Nathalie<br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> gnso-rpm-wg mailing list<br>
> gnso-rpm-wg@icann.org<br>
> <a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a><br>
_______________________________________________<br>
gnso-rpm-wg mailing list<br>
gnso-rpm-wg@icann.org<br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a><br>
</div>
</span></font><br>
<hr>
<font face="Arial" color="Black" size="1"><br>
Confidentiality Notice:<br>
This communication constitutes an electronic communication within the meaning of the Electronic Communications Privacy Act, 18 U.S.C. Section 2510, and its disclosure is strictly limited to the recipient intended by the sender of this message. This transmission,
and any attachments, may contain confidential attorney-client privileged information and attorney work product. If you are not the intended recipient, any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission
is STRICTLY PROHIBITED. Please contact us immediately by return e-mail or at 404 815 6500, and destroy the original transmission and its attachments without reading or saving in any manner.<br>
</font><br>
<hr>
<font face="Arial" color="Black" size="1"><br>
***DISCLAIMER*** Per Treasury Department Circular 230: Any U.S. federal tax advice contained in this communication (including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding penalties under the Internal
Revenue Code or (ii) promoting, marketing or recommending to another party any transaction or matter addressed herein.<br>
</font>
</body>
</html>