<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.MsoNoSpacing, li.MsoNoSpacing, div.MsoNoSpacing
{mso-style-priority:1;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle29
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle30
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle31
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle32
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle33
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle34
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle35
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle36
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle37
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle38
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle39
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle40
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle41
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle42
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle43
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle44
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Dear All,<o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Please find the attendance of the call attached to this email and the MP3 recording below for the Review of all Rights Protection Mechanisms (RPMs) in
all gTLDs PDP Working Group call held on Wednesday, 28 September 2016 at 16:00 UTC. Attendance of the call is posted on agenda wiki page:
</span><a href="https://community.icann.org/x/QAu4Aw"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">https://community.icann.org/x/QAu4Aw</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:15.6pt">
<b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">MP3:</span></b><span class="MsoHyperlink"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#111111;text-decoration:none">
<a href="http://audio.icann.org/gnso/gnso-rpm-review-28sep16-en.mp3">http://audio.icann.org/gnso/gnso-rpm-review-28sep16-en.mp3</a><o:p></o:p></span></span></p>
<p style="line-height:15.6pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page:</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">
</span><a href="http://gnso.icann.org/en/group-activities/calendar"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">http://gnso.icann.org/en/group-activities/calendar</span></a><span style="color:#1F497D"><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">** Please let me know if your name has been left off the list **<o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Mailing list archives: </span><a href="http://mm.icann.org/pipermail/gnso-rpm-wg/"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;background:white">http://mm.icann.org/pipermail/gnso-rpm-wg/</span></a><span style="color:black"><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Wiki page: </span><a href="https://community.icann.org/x/rhiOAw"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">https://community.icann.org/x/rhiOAw</span></a><span style="color:black"><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Thank you.<o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Kind regards,<o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Terri Agnew<o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">-------------------------------<o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Adobe Connect chat
</span></u></b><b><u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">transcript for 28 September 2016:<o:p></o:p></span></u></b></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoNoSpacing">Terri Agnew: Welcome to the Review of all Rights Protection Mechanisms (RPMs) in all gTLDs PDP Working Group held on Wednesday, 28 September 2016 at 16:00 UTC for 60 minutes.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Terri Agnew: agenda wiki page: https://community.icann.org/x/QAu4Aw<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">George Kirikos: Hi folks.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">George Kirikos: It looks like the layout of the room was adjusted slightly?<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">David Tait: Hi George, yes there have been some updates to add additional functionality to the AC rooms<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Steve Levy: Hi all!<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Paul Tattersfield: Hi everyone<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Greg Shatan: Nice new room! I can still smell the paint.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Yuri Chumak: hi<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Ankur Raheja: Hello<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Kathy Kleiman: But do you like the color, Greg?<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Greg Shatan: So many shades of gray.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Maxim Alzoba (FAITID): Hello all<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Kathy Kleiman: oh dear.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Greg Shatan: We will need to provide color with our chat colors. And with our comments.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Georges Nahitchevansky: Who was in charge of the paint job<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Kathy Kleiman: indeed, color commentary... <o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">George Kirikos: A theme selector would be nice....perhaps aqua.....<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Greg Shatan: I want to rock and roll all night, and ICANN every day.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Greg Shatan: Custom skins for Adobe Connect rooms!<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Mary Wong: Ack, earworm!!!<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Greg Shatan: @Mary, sorry...:-)<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Mary Wong: :)<o:p></o:p></p>
<p class="MsoNoSpacing">----------------------------------------------------- (09/28/2016 11:07) -----------------------------------------------------
<o:p></o:p></p>
<p class="MsoNoSpacing">Terri Agnew: everyone can turn the slides themselves<o:p></o:p></p>
<p class="MsoNoSpacing">----------------------------------------------------- (09/28/2016 11:09) -----------------------------------------------------
<o:p></o:p></p>
<p class="MsoNoSpacing">Terri Agnew: Please remember to mute when not speaking<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): yep.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Paul Keating: Hello all. Sorry I am late.<o:p></o:p></p>
<p class="MsoNoSpacing">----------------------------------------------------- (09/28/2016 11:11) -----------------------------------------------------
<o:p></o:p></p>
<p class="MsoNoSpacing">Paul McGrady: Sorry to be tardy. Good m/a/e.<o:p></o:p></p>
<p class="MsoNoSpacing">----------------------------------------------------- (09/28/2016 11:12) -----------------------------------------------------
<o:p></o:p></p>
<p class="MsoNoSpacing">George Kirikos: Is there a reason for the English bias in the notice? (Given the large number of registrants from China, are they getting adequate notice? Are the Chinese registrars translating into Chinese?)<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Griffin Barnett: I believe it is required (not optional) to provide the notice in English and the language of the registration agreement<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Maxim Alzoba (FAITID): How to say .... lot's of potential registrants were freaked out due to the text and did not realise that they are not doing wrong things ... it would be nice to have more non-legal persons friendly text
<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Mary Wong: The TMCH Requirements provide the following: "The Claims Notice MUST be provided by the registrar to the potential domain name registrant in English and SHOULD be provided by the
registrar to the potential domain name registrant in the language of the registration agreement."<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">George Kirikos: Do we have any stats on whether the registrars are following the "should" advice? Or are they cutting costs, and ignoring the suggestion?<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Mary Wong: So whether there is a Chinese version depends on whether the registration agrement is in Chinese (which may well be the case if the registrar is a Chinese-based registrar).<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Philip Corwin: Slide 4 notes that Notice must be provided in English and, preferably, language of registration agreement<o:p></o:p></p>
<p class="MsoNoSpacing">----------------------------------------------------- (09/28/2016 11:16) -----------------------------------------------------
<o:p></o:p></p>
<p class="MsoNoSpacing">George Kirikos: 46.8% of registrants are from China for new gTLDs, so perhaps the "should" can be replaced by "must" https://ntldstats.com/country<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): One interesting note was that the original policy was that a Registry had to run a Sunrise OR a Claims Period, but not both.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): THat changed after GAC Advice<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">George Kirikos: (might even be higher than 46.8%, depending on the 17.9% of proxy registrations)<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): We need to decide whether to formally codify both into the policy (or not)<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Mary Wong: @George, we (staff) don't know at this point if the aggregate numbers for Claims Notices sent are available broken down into different languages. Note that the official working language at ICANN is English, so the official
notice (as provided for in the TMCH Requirements) is provided in English. I don't believe we provide an official translation in multiple languages.<o:p></o:p></p>
<p class="MsoNoSpacing">----------------------------------------------------- (09/28/2016 11:19) -----------------------------------------------------
<o:p></o:p></p>
<p class="MsoNoSpacing">George Kirikos: That's surprising that there's no official translation, given that one of the justifications for the new gTLDs program was for IDNS, and "lesser served" countries in general.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Maxim Alzoba (FAITID): than, given that most people on the planet do not read English ... I think big share of those notices were not understood
<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): @George, perhaps that's a policy recommendation; (Namely, we should have formal translations done in at least the 6 UN languages)/<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">George Kirikos: +1 Jeff<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Mary Wong: All, for Slide 10, the "either type of registration activity" quoted refers to both legitimate registrations and cybersquatting activity.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Maxim Alzoba (FAITID): +1 for chilling effect<o:p></o:p></p>
<p class="MsoNoSpacing">----------------------------------------------------- (09/28/2016 11:22) -----------------------------------------------------
<o:p></o:p></p>
<p class="MsoNoSpacing">Griffin Barnett: agree that official translations of the claims notice language in at least the 6 UN languages would be helpful<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">George Kirikos: How many registration attempts didn't trigger a claims notice? (i.e. is XX million+ total registration attempts, but 1.8 million triggered a Claims Notice?)<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): And today Donuts announced a new DPML Plus service<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">George Kirikos: (and of those that didn't trigger a claims notice, what % (presumably higher than 6.3%) went on to complete the domain name registration?)<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Mary Wong: @George, I think we can only get that total number if all registrars agree to provide that information.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): http://www.donuts.domains/services/dpml-plus/dpml-plus-overview<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">George Kirikos: @Mary: We'd need those kinds of figures, to determine whether or not the 6.3% is indeed a "chilling effect"<o:p></o:p></p>
<p class="MsoNoSpacing">----------------------------------------------------- (09/28/2016 11:26) -----------------------------------------------------
<o:p></o:p></p>
<p class="MsoNoSpacing">Philip Corwin: I'm confused about Donuts' DPML service. Slide says that mark registered in TMCH can be blocked, but also says that blocked mark need not be an exact match of the TMCH registered mark. How broad is the potential scope
of blocking?<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Maxim Alzoba (FAITID): this kind of extra protection will prevent those parties from obtaining their matching domains, the way we see now with IGOs ...<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Mary Wong: @George, we don't disagree - but I doubt we can get all the data so as to be a reliable figure. Perhaps we can compare the number of Claims Notices issued and the number that proceeded nevertheless (per the Analysis Group's
data) with the total number of registrations?<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): Can we add the question of whether both Sunrise AND Claims should continue to apply or whether we stick with the original policy which was Sunrise OR Claims<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Philip Corwin: My recollection is that TM+50 not being used much<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Paul Tattersfield: It’s probably a helpful chill, developing a (non-infringing) business on a domain where there is also a larger brand in an unrelated sector is a serious headache and it doesn’t go away with tine. If possible choosing
a unique name is a far better route.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Paul Tattersfield: time<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Mary Wong: @Phil, on the breadth of a DPML block, the operative word used by these registries is "contains" the TM. I believe they also include substituions (e.g. numbers for characters).<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Maxim Alzoba (FAITID): given the amount of generic names registered as TMs- extra protection will make future TLDs usless<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Kathy Kleiman: Looking at the Additional Questions and Issues from the Charter, perhaps the key question is: are the TM Claims Services policies fair and balanced as adopted and as used?<o:p></o:p></p>
<p class="MsoNoSpacing">----------------------------------------------------- (09/28/2016 11:30) -----------------------------------------------------
<o:p></o:p></p>
<p class="MsoNoSpacing">Steve Levy: I feel balance is an important consideration given the huge number of cybersquatted domains compared with the lower number of generic domains claimaed curing sunrise by trademark owners<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">George Kirikos: Do we have any stats on what percentage of the claims notices get triggered in different time periods? (e.g. first 10 days of GA, vs. 80th-90th days of GA) Perhaps that would help determine where the "sweet spot" is,
in terms of picking an optimal time period for the claims notice period.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Paul Keating: Perhaps organizing them by category. TMCH procedureal issues, Rights protections, etc.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Rebecca Tushnet: It seems to me a problem with data collection is that registries aren't required to let ICANN inspect--subject to confidentiality agreements--the actual attempts that triggered matches/notices. Without being able to
audit a sample there is just no way to make any kind of informed judgment about whether these are true positives or false positives, or what percentage of each we might be getting.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Statton Hammock: I don't think the first and last are NOT the same. One asks for an opinion, the other asks for facts.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Mary Wong: @Rebecca, that is the staff concern - that any data we get from registrars will likely be incomplete and thus not as accurate or helpful as we may need.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Rebecca Tushnet: So can contracts with registries be changed to allow such audits in the future, again subject to confidentiality obligations?<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): Rebecca - I think you meant registrars in your point. Registries do not have the information you point out (Namely, whether registrations were attempted but decided not to proceed) . That is the registrar
level<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Rebecca Tushnet: And by allow I mean "require access to"<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">John McElwaine: @jscott Agree with that approach <o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Rebecca Tushnet: Sorry, registrars<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Petter Rindforth: agree <o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">khouloud Dawahi: yes<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Kathy Kleiman: @J.Scott: What slide are you looking at now? Tx.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Philip Corwin: @Steve Levy--what is factual basis for statement that there is "huge number of cybersquatted domains"? UDRPs constitute less than 1/100 of all registered gTLD domains.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Maxim Alzoba (FAITID): Even adding "if you do not understand the text = please click this URL in 6 UN languages will help"<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Beth Allegretti: + 1 Caroline<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Bret Fausett, Uniregistry: I like the suggestion of changing the text of the notice.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): Yes, I will go after<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): because my question is semi different topic<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">George Kirikos: Here's what the TM Claims Notice looks, for one registrar (Tucows/OpenSRS): https://kb.opensrs.com/22964-domains/188131-trademark-claims-notifications<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Vaibhav Aggarwal: HI I am In Sorry for being late kept waiting on the older link only to realise that the Talk is in a new Room :-)<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Kristine Dorrain - Amazon Registry: Thanks. all. I have to bail. Will listen to the rest this afternoon.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">George Kirikos: (scroll down a couple of pages, to see what the registrant sees)<o:p></o:p></p>
<p class="MsoNoSpacing">----------------------------------------------------- (09/28/2016 11:37) -----------------------------------------------------
<o:p></o:p></p>
<p class="MsoNoSpacing">Kathy Kleiman: @Mary and David: Could you add Jeff's question to the right?<o:p></o:p></p>
<p class="MsoNoSpacing">----------------------------------------------------- (09/28/2016 11:39) -----------------------------------------------------
<o:p></o:p></p>
<p class="MsoNoSpacing">Mary Wong: Done!<o:p></o:p></p>
<p class="MsoNoSpacing">----------------------------------------------------- (09/28/2016 11:41) -----------------------------------------------------
<o:p></o:p></p>
<p class="MsoNoSpacing">Ivett Paulovics: Sorry for being late<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Ivett Paulovics: Hi everyone<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): We need to decide also from a policy perspective as to whether to codify tM plus 0<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): 50<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">George Kirikos: Interestingly, for Tucows/OpenSRS "You cannot enable Contact Privacy for domains that match marks in the Clearinghouse." I wonder if other registrars do the same, to mitigate risk.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): that was not a GNSO policy<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): That was a Board addition after consultation<o:p></o:p></p>
<p class="MsoNoSpacing">----------------------------------------------------- (09/28/2016 11:44) -----------------------------------------------------
<o:p></o:p></p>
<p class="MsoNoSpacing">Greg Shatan: A more "conversational" notice could make sense. Would "Abandon Hope, All Ye Who Enter Here" be too harsh for a claims notice? It translates nicely into Italian.<o:p></o:p></p>
<p class="MsoNoSpacing">----------------------------------------------------- (09/28/2016 11:45) -----------------------------------------------------
<o:p></o:p></p>
<p class="MsoNoSpacing">George Kirikos: Thanks for pointing out that list, Kathy.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Kathy Kleiman: @Greg, Dante's words may not be welcoming to registrants :-)<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Mary Wong: @Paul M, that language was in the TMCH Requirements. We haven't (David and I) seen an actual Claims Notice but we can ask.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">J. Scott Evans: @Greg ah hahahahahahaha<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Kathy Kleiman: How do we encourage fair use and discourage infringing use?<o:p></o:p></p>
<p class="MsoNoSpacing">----------------------------------------------------- (09/28/2016 11:48) -----------------------------------------------------
<o:p></o:p></p>
<p class="MsoNoSpacing">Kathy Kleiman: blame us!<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">George Kirikos: Perhaps the Claims Notice should only be triggered if the prospective registrant is in the same country as the mark. e.g. US Mark would show to a US Registrant, but not to a Canadian registrant. Pakistani mark wouldn't
show to a US registrant.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Kathy Kleiman: we did try to create a balanced notice...<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Greg Shatan: Agree with Paul, the notice does need to be firmly stated enough to put the potential registrant on notice.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Kathy Kleiman: +1 Paul!<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Greg Shatan: The balance may be right -- it may be the legalistic language that needs fixing.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Lori Schulman: Kathy just explained the problem in a nutshell. How do we balance the message?<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Kathy Kleiman: for those reading the chat room later - the 10 most frequently downloaded trademark strings in claims service data - smart, forex, hotel, one, love, cloud, nyc, london, abc, luxury<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Philip Corwin: @Paul--I wasn't advocating any particular "softening" language at this time, just some thinking about whether language can be made a tad less legalistic and thereby clearer for average registrant. Agree that some intended
registration may be very infringing, while others would not -- often dependent on registrant intent raher than the TMCH-registered mark.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): I also believe that a number of notices may be been sent as part of an error from a particular registrar<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Steve Levy: Sorry, have to log off now but will continue on the phone line.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Phil Marano (Mayer Brown): Should we explore the possibility / likelihood that potential registrants who ultimately decline to register domain names upon receipt of a claims notification, are simply seeking to reverse engineer the Clearinghouse
database through a multitude of queries and attempted registrations?<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Mary Wong: @Phil M, how would we do that, though?<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Greg Shatan: Phil, that's an interesting point. And could skew the data.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Phil Marano (Mayer Brown): @Mary: Not sure, open to any thoughts of course.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">George Kirikos: I wonder if the 93.7% figure might be overstated, if some of the domain names that triggered Claims Notices were also Premium Domains?<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">George Kirikos: e.g. "smart" or "hotel" might be $50,000/yr domains.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Kathy Kleiman: @Mary and David: could you include Beth's question re: language and translation?<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): I do believe it is overstated<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Mary Wong: The Technical Requirements say "SHOULD" (for language of registration agreement)<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Maxim Alzoba (FAITID): the only language of Registry Agreement is English
<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">John McElwaine: @Phil I was about to mention that . We cannot assume that every purported "registrant" is actually trying to register a domain name.
<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Greg Shatan: Can we find out what the more popular local registrars are doing, in fact? There can't be that many.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">George Kirikos: Plus, if 10 people were deterred from registering Hotel.TLD, it doesn't mean the string doesn't get registered --- the 11th person might (smartly) recognize the term can be used for non-infringing sites, and she/he goes
ahead with the registration.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Greg Shatan: It's the end-user registration agreement, not the Registry Agreement. I assume if I'm sitting in China and uising a Chinese registrar, the registration agreement is highly likely to be in Chinese.<o:p></o:p></p>
<p class="MsoNoSpacing">----------------------------------------------------- (09/28/2016 11:55) -----------------------------------------------------
<o:p></o:p></p>
<p class="MsoNoSpacing">George Kirikos: Perhaps "human rights" refers to Free Speech?<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Statton Hammock: Agree J. Scott<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Mary Wong: We will add this - but, again, that depends on registrars agreeing to provide that information, and we may not also get all to respond.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): Every PDP is now being asked about Human Rights<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Mary Wong: (this = questions/data about language of registration agreements)<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Greg Shatan: There's the CCWG-Accountability WS2 Subgroup on Human Rights<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): Seems to be a popular addition<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): And those that added the Human Rights language are never in these groups :)<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): Stephanie Perrin I believe on the Council always wanted to add this language<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">George Kirikos: I'm in favour of Article 24: http://www.un.org/en/universal-declaration-human-rights/ (right to rest and leisure) :-)<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Greg Shatan: I'm in there too, We are in the "messy" stage of the multistakeholder process. This too shall pass (it almost always does.)<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Jeff Neuman (Com Laude): I have to drop.....Bye all<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Mary Wong: "1. Are recent and strong ICANN work seeking to understand and incorporate Human Rights into the policy considerations of ICANN relevant to the UDRP or any of the RPMs?"<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Paul McGrady: @George K: love it! "Everyone has the right to rest and leisure, including reasonable limitation of working hours and periodic holidays with pay."<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Paul Tattersfield: breach of natural justice is important
<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Paul McGrady: I am very concerned about just cherry picking one human right to apply here.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Paul McGrady: This is a morass we should not allow ourselves to get trapped in. This is the work of that WS2 Subgroup.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Paul Keating: J Sc ott: The EU certainly DOES have fair use. It is in 4Ibis of the EC Regulation on Trademarks<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Paul McGrady: Article 27(2) "(2) Everyone has the right to the protection of the moral and material interests resulting from any scientific, literary or artistic production of which he is the author."<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Mary Wong: @Greg, as noted, these were community suggestions made to ICANN, unedited by staff.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Bret Fausett, Uniregistry: I would invite people who are knowledgable of, sensitive to, and passionate about "human rights in the DNS" look at the work of the working group, and every working group, and tell us if what the group is
doing impacts the issues. I am open to this issue, but I don't know enough about it to have an opinion one way or another.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Vaibhav Aggarwal: Where are v going with this on TMCH ?<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Paul Tattersfield: Its relevant for refiling UDRPs<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Vaibhav Aggarwal: This is the not the Statge <o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Vaibhav Aggarwal: Guys<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Vaibhav Aggarwal: I am confused<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Vaibhav Aggarwal: This is TMCH - Just a Repository<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Vaibhav Aggarwal: an Agency<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Vaibhav Aggarwal: Takes Iformation form one Source and Sends it to other<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Vaibhav Aggarwal: thats it<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Greg Shatan: Umbrella with broken spokes and bum handle...<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Mary Wong: Note that all these questions are community-made. The Charter states that "The issues that are listed here reflect the suggestions that have been made
to date by the community regarding improvements or modifications to the RPM(s) in question and should form part
of the discussions of the PDP Working Group. The Working Group may decide to address all, some or even additional
issues to these."<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Paul Keating: do NOT strike. It should be kept but agree dealt with last.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Vaibhav Aggarwal: @Greg ha ha ha<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Bret Fausett, Uniregistry: I wouldn't strike it, J. Scott. Let's just defer this.
<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Bret Fausett, Uniregistry: Maybe just a change of terminology.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Paul Keating: If it is an umbrella question it impacts all of the various points.
<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Greg Shatan: Maybe by then the WS2 subgroup on HR will be finished with its work.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Paul McGrady: WS2 HR is supposed to be done well ahead of us.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Kathy Kleiman: +1 Paul<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Terri Agnew: The call for the Review of all Rights Protection Mechanisms (RPMs) in all gTLDs PDP Working Group is scheduled for Wednesday, 05 October 2016 at 17:00 UTC for 60 minutes.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Kathy Kleiman: Each umbrella question should be evaluated with each RPM - as appropriate<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Greg Shatan: And don't foreget to update your Adobe Connect link.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">George Kirikos: Bye folks.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Maxim Alzoba (FAITID): bye all<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Kathy Kleiman: Tx J. Scott and All<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Greg Shatan: Bye all.<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Georges Nahitchevansky: Bye everyone<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Elizabeth Featherman: bye all!<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Vaibhav Aggarwal: Thanks Team<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Vaibhav Aggarwal: ciao<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Paul Tattersfield: bye everyone<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing">Philip Corwin: Ciao<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
</body>
</html>