Dear all, The Working Group co-chairs periodically review the group’s meeting times with staff. You may recall that this group previously held its fourth rotating meeting at a different time (viz. 0300 UTC) which, while making it much easier for APAC-based participants as it meant that one out of every four Working Group calls would take place during working hours in that region, also made it extremely difficult for EMEA-based members to participate. The current rotating time of 1200 UTC was a compromise of sorts, as it falls within EMEA working hours without being overly late (relatively speaking) for APAC – although please note that, in contrast to the previous rotating time of 0300 UTC, 1200 UTC actually means the call takes place after working hours in APAC (e.g. 8 p.m. in Singapore/HK and 10 p.m. in parts of Australia). In either case, the Working Group’s regular meeting time of 1700 UTC makes attending three out of four meetings very difficult for APAC-based members (1700 UTC time is 5 a.m. in Singapore/HK and 7 a.m. in Melbourne). As the GNSO’s rules are designed to facilitate broad and diverse representation and participation, all PDP Working Groups (with the current exception of the new Expedited PDP on the Temporary Specification relating to WHOIS data) use a rotating meeting schedule, with actual times determined by the circumstances of each group and set by that group’s leadership team. This is in accordance with the GNSO Working Group Guidelines, which prescribe that “scheduling tools should follow the preference of the majority and accommodate those that are in different time zones. Alternating meeting times should be considered as an option if the same members of the WG are always ‘inconvenienced’ by a standing meeting time.” Staff will work with Kathy, Brian and Phil to see if the current rotating time should be changed, but for now we thought this background information may be helpful. Thanks and cheers Mary, Julie & Ariel From: gnso-rpm-wg <gnso-rpm-wg-bounces@icann.org> on behalf of "Nahitchevansky, Georges" <ghn@kilpatricktownsend.com> Date: Wednesday, September 26, 2018 at 11:34 To: George Kirikos <icann@leap.com>, Nathalie Peregrine <nathalie.peregrine@icann.org> Cc: gnso-rpm-wg <gnso-rpm-wg@icann.org>, gnso-SECS <gnso-secs@icann.org> Subject: 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 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. From: icann@leap.com Sent: September 26, 2018 11:19 AM To: nathalie.peregrine@icann.org Cc: gnso-rpm-wg@icann.org; gnso-secs@icann.org Subject: 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 [resending, as I sent the prior email from an unsubscribed email address] The attendance record is not accurate. e.g. my name (George Kirikos) is missing. Also, Georges Nahitchevansky's first name is missing the 's'. There might be other errors beyond that. Also, it seems participation from Asia-Pacific based members was quite light on this call (which was supposed to be APAC-friendly), if the (revised) attendance was accurate. Perhaps a different time slot needs to be considered? Sincerely, George Kirikos 416-588-0269 http://www.leap.com/ [leap.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.leap.com_&d=DwMFAg&c...> On Wed, Sep 26, 2018 at 11:06 AM, Nathalie Peregrine <nathalie.peregrine@icann.org> wrote:
Dear all,
Please find the attendance and AC Chat attached to this email, and the MP3 & AC recording below for the Review of all Rights Protection Mechanisms (RPMs) PDP Working Group call held Monday, 26 September 2018 at 12:00 UTC. Attendance and recording of the call is also posted on agenda wiki page: https://community.icann.org/x/ZgKNBQ
MP3: https://audio.icann.org/gnso/gnso-rpm-review-26sep18-en.mp3 [audio.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__audio.icann.org_gnso_gn...>
AC Recording: https://participate.icann.org/p8ed3wvepp7/
The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: https://gnso.icann.org/en/group-activities/calendar [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_group...> [gnso.icann.org]
** Please let me know if your name has been left off the list **
Mailing list archives: http://mm.icann.org/pipermail/gnso-rpm-wg/
Main wiki page for the working group: https://community.icann.org/x/wCWAAw [community.icann.org]
Thank you.
Kind Regards,
Nathalie
_______________________________________________ gnso-rpm-wg mailing list gnso-rpm-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-rpm-wg
gnso-rpm-wg mailing list gnso-rpm-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-rpm-wg ________________________________ Confidentiality Notice: 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. ________________________________ ***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.