[gnso-rds-pdp-wg] Notes & action items from 22/6 RDS PDP WG meeting

Wed Jun 22 21:01:23 UTC 2016

Chuck,

I did not listen to the recording, for the reasons cited in Kathy's
email....

Greg

On Wed, Jun 22, 2016 at 4:58 PM, Gomes, Chuck <cgomes at verisign.com> wrote:

> Thanks Greg.  I responded to your comments and edits in the attached
> file.
>
>
>
> I have a question for you:  Did you listen to the recording?
>
>
>
> Chuck
>
>
>
> *From:* Greg Shatan [mailto:gregshatanipc at gmail.com]
> *Sent:* Wednesday, June 22, 2016 3:45 PM
> *To:* Gomes, Chuck
> *Cc:* Metalitz, Steven; Marika Konings; gnso-rds-pdp-wg at icann.org
>
> *Subject:* Re: [gnso-rds-pdp-wg] Notes & action items from 22/6 RDS PDP
> WG meeting
>
>
>
> My changes and comments to the proposed document are in the attachment.
>
>
>
> (Counterintuitively, the PDF version is the one with the title beginning
> "Microsoft Word")
>
>
>
> Greg
>
>
>
> On Wed, Jun 22, 2016 at 3:15 PM, Gomes, Chuck <cgomes at verisign.com> wrote:
>
> As I have said to others Steve, it was just an example to provide
> clarification.  Feel free to ignore the example.
>
>
>
> Chuck
>
>
>
> *From:* Metalitz, Steven [mailto:met at msk.com]
> *Sent:* Wednesday, June 22, 2016 1:56 PM
> *To:* Gomes, Chuck; 'Marika Konings'; gnso-rds-pdp-wg at icann.org
>
>
> *Subject:* RE: [gnso-rds-pdp-wg] Notes & action items from 22/6 RDS PDP
> WG meeting
>
>
>
> Thank you Chuck, that is a helpful explanation.  But if the category of
> international treaties applicable to the RDS is a null set, I am not sure
> what we would be accomplishing by requiring compliance with them.
>
>
>
> *[image: image001]*
>
> *Steven J. Metalitz *| *Partner, through his professional corporation*
>
> T: 202.355.7902 | met at msk.com
>
> *Mitchell Silberberg & Knupp* *LLP* | *www.msk.com <http://www.msk.com/>*
>
> 1818 N Street NW, 8th Floor, Washington, DC 20036
>
>
>
> *THE INFORMATION CONTAINED IN THIS E-MAIL MESSAGE IS INTENDED ONLY FOR THE
> PERSONAL AND CONFIDENTIAL USE OF THE DESIGNATED RECIPIENTS.** THIS
> MESSAGE MAY BE AN ATTORNEY-CLIENT COMMUNICATION, AND AS SUCH IS PRIVILEGED
> AND CONFIDENTIAL. IF THE READER OF THIS MESSAGE IS NOT AN INTENDED
> RECIPIENT, YOU ARE HEREBY NOTIFIED THAT ANY REVIEW, USE, DISSEMINATION,
> FORWARDING OR COPYING OF THIS MESSAGE IS STRICTLY PROHIBITED. PLEASE NOTIFY
> US IMMEDIATELY BY REPLY E-MAIL OR TELEPHONE, AND DELETE THE ORIGINAL
> MESSAGE AND ALL ATTACHMENTS FROM YOUR SYSTEM. THANK YOU.*
>
>
>
> *From:* Gomes, Chuck [mailto:cgomes at verisign.com <cgomes at verisign.com>]
> *Sent:* Wednesday, June 22, 2016 12:41 PM
> *To:* Metalitz, Steven; 'Marika Konings'; gnso-rds-pdp-wg at icann.org
> *Subject:* RE: [gnso-rds-pdp-wg] Notes & action items from 22/6 RDS PDP
> WG meeting
>
>
>
> My intent here Steve was very similar to what occurred with the new gTLD
> policy recommendations.  I was trying to make a distinction between local
> or regional laws and international treaties.  The GNSO recommended that
> international laws be applied for new gTLDs and not local or regional laws
> because of the global nature of the Internet.  I don’t know whether there
> are any such laws that would be applicable to the RDS but if there are, I
> would presume that the RDS would need to compliant with them.
>
>
>
> Chuck
>
>
>
> *From:* gnso-rds-pdp-wg-bounces at icann.org [
> mailto:gnso-rds-pdp-wg-bounces at icann.org
> <gnso-rds-pdp-wg-bounces at icann.org>] *On Behalf Of *Metalitz, Steven
> *Sent:* Wednesday, June 22, 2016 10:04 AM
> *To:* 'Marika Konings'; gnso-rds-pdp-wg at icann.org
> *Subject:* Re: [gnso-rds-pdp-wg] Notes & action items from 22/6 RDS PDP
> WG meeting
>
>
>
> Chuck (and colleagues),
>
>
>
> Sorry to have missed last night’s call.
>
>
>
> Question re one of the examples you proposed (in the document we have been
> asked to review) as a “possible requirement ….that would apply to the RDS
> in all circumstances” (item 3(b)(i)(2) of the document):  “The RDS must be
> in compliance with applicable international law.”
>
>
>
> Could you provide an example of what you mean by “international law” in
> this context?
>
>
>
> Thanks, and apologies if this was asked and answered last night, but I did
> not see any mention of it in the notes.
>
>
>
> Steve Metalitz
>
>
>
>
>
> *From:* gnso-rds-pdp-wg-bounces at icann.org [
> mailto:gnso-rds-pdp-wg-bounces at icann.org
> <gnso-rds-pdp-wg-bounces at icann.org>] *On Behalf Of *Marika Konings
> *Sent:* Wednesday, June 22, 2016 2:15 AM
> *To:* gnso-rds-pdp-wg at icann.org
> *Subject:* [gnso-rds-pdp-wg] Notes & action items from 22/6 RDS PDP WG
> meeting
>
>
>
> Dear All,
>
>
>
> Please find below the notes & action items from today’s meeting. You are
> requested to especially take note of the following action item #3 – your
> input on the attached document is requested by Friday 24 June at the latest.
>
>
>
> Best regards,
>
>
>
> Marika
>
>
>
> *Notes RDS PDP WG Meeting – 22 June 2016:*
>
>
>
> *These high-level notes are designed to help PDP WG members navigate
> through the content of the call and are not meant as a substitute for the
> transcript and/or recording. The MP3, transcript, and chat are provided
> separately and are posted on the wiki
> at: https://community.icann.org/x/C4xlAw
> <https://community.icann.org/x/C4xlAw>. *
>
>
>
> 1)   Roll Call / SOI
>
> ·         Roll call will be taken from Adobe Connect
>
> ·         Please remember to state your name before speaking and mute
> your microphones when not speaking.
>
> ·         Audio only: Daniel Nanghaka
>
> ·         Updates to SOI: Maxim Alzoba
>
>
>
> 2. Outreach messages 1 & 2:
>
> ·         Outreach message #1: Review of public comments received - task
> 7.e & f
>
> ·         Refer to draft comment tool - comments received to date have
> been plugged into tool to facilitate WG review
>
> ·         Comments received are posted:
> https://community.icann.org/x/pYxlAw
>
> ·         Draft responses are being drafted for WG review as a starting
> point for recording review and actions taken
>
> ·         Currently 4 items that need draft responses
>
>
>
> *Action item #1*: Leadership team to prepare draft responses for 4 open
> items and share with WG prior to WG F2F meeting in Helsinki
>
> *Action item #2*: Include public comment review tool review as part of
> the agenda for the WG F2F meeting
>
>
>
> ii. Member cooperation in encouraging outreach #2 responses
>
> ·         Appreciate work of lead points of contact
>
> ·         Any questions from lead points of contacts?
>
> ·         Responses have been requested to be submitted no later than the
> F2F WG meeting in Helsinki
>
> ·         Note, additional requirements can still be submitted after the
> F2F WG meeting, but ideally these are received as soon as possible.
>
>
>
> 3. Continue discussion on Task 11: Method for reaching consensus in
> deliberations
>
> ·         Last week initial discussion on work plan task 11 - to agree on
> how to reach consensus in deliberations
>
> ·         Document shared on the screen has been updated following WG
> discussion. Hopefully this will address all the input received, noting that
> there was necessarily agreement amongst all.
>
> ·         No addition of another Initial Report, but commence
> deliberations with big three (users/purposes, data elements, privacy). Not
> start with accuracy and gated access until after deliberations on first
> three. If WG believes outreach is useful after first three and before
> moving on to next two, WG can decide to do so whether it is formal or
> informal to test thinking before moving on to the next questions.
>
> ·         Initial report to be published for public comment after
> completion of work on first five questions.
>
> ·         Formal consensus call only after input on Initial Report
>
> ·         Next step is to organise the possible requirements - to allow
> for tackling them in groups, prerequisites, dependencies, etc. Lisa and
> Susan have commenced this work - WG will have a chance to review and
> comment. Try to get first three done prior to Helsinki, but as this is a
> significant task, it may not be possible to complete this part of the work
> by Helsinki.
>
> ·         See latest version shared during the call with triage in
> progress as of 21 June 2016. Note, no changes to any of the requirements,
> just re-organisation: triage - take requirements and indicate
> pre-requisites/dependencies and which phase it falls into (phases from
> process framework). Also trying to group possible duplicates and similar
> requirements so that these can possibly be deliberated on together. See
> initial grouping key on page 26 and 27 - in no particular order.
>
> ·         Nothing is set in stone, this is a first attempt to organise
> the document. Any comments/input will be welcome.
>
> ·         Advantage of table is that it will allow for sorting according
> to phase or other requirements.
>
> ·         Consider adding a grouping for legal requirements? Note, there
> is currently one titled 'applicable law'. May be necessary to have
> sub-groupings in certain cases.
>
> ·         Idea to start deliberations on something sooner than
> organisation of documents has been finished. See step 3b of document. WG
> asked to identify possible requirements that would apply to RDS in all
> circumstances (see examples identified in document).
>
>
>
> *Action item #3*: share document with mailing list and request feedback
> by Friday 24 June at the latest (see attached).
>
>
>
> 4. Planning for Helsinki meeting
>
> ·         Cross-community session incl. sharing of WG possible
> requirements examples
>
> ·         See https://community.icann.org/x/iyCOAw for latest version of
> presentation. No additional examples received, so for now stick with
> examples identified in original presentation. If WG members want to come
> forward with other examples, they would need to identify those as soona s
> possible.
>
> ·         Agenda for F2F WG meeting
>
> ·         To be updated to reflect current state of work
>
>
>
> 5. Confirm next meeting - F2F meeting in Helsinki: Tuesday June 28, 2016
> 08:00 - 12.00 Hall B
>
> ·         No meetings in the week after the Helsinki meeting, recommence
> on 12 July
>
>
>
> *Marika Konings*
>
> Senior Policy Director & Team Leader for the GNSO, Internet Corporation
> for Assigned Names and Numbers (ICANN)
>
> Email: marika.konings at icann.org
>
>
>
> *Follow the GNSO via Twitter @ICANN_GNSO*
>
> *Find out more about the GNSO by taking our interactive courses
> <http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages
> <http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers>.*
>
>
>
>
> _______________________________________________
> gnso-rds-pdp-wg mailing list
> gnso-rds-pdp-wg at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20160622/4de0305d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 2772 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20160622/4de0305d/image001.gif>