[Gnso-newgtld-wg-wt2] Recordings, Attendance & AC Chat from New gTLD Subsequent Procedures Sub Team ­Track 2 Legal/Regulatory Issues on Thursday, 15 June 2017

[Julie Bisland]

Dear All,



Please find the attendance and recording of the call attached to this email. The AC recording and AC Chat are listed below for the New gTLD Subsequent Procedures Sub Team – Track 2 – Legal/Regulatory Issues held on Thursday, 15 June 2017 at 21:00 UTC.



Adobe Connect recording (audio and visual):    https://participate.icann.org/p3o7u6zn6k2/<https://participate.icann.org/p3o7u6zn6k2/?OWASP_CSRFTOKEN=aef002f837ee5497111fa4719764e9def1225eac61ddd20ef969becbb4c298fd>



The recordings of the calls are posted on the GNSO Master Calendar page:  http://gnso.icann.org/en/group-activities/calendar



** Please let me know if your name has been left off the list **



Mailing list archives: http://mm.icann.org/pipermail/gnso-newgtld-wg-wt2



Agenda Wiki page: https://community.icann.org/x/ExLfAw





Thank you.



Kind regards,



Julie



-------------------------------



Adobe Connect chat transcript for 15 June 2017

  Julie Bisland:Welcome to the New gTLD Subsequent Procedures Sub Team – Track 2 – Legal/Regulatory Issues on Thursday, 15 June 2017 at 21:00 UTC.

  Julie Bisland:Agenda wiki page:  https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_ExLfAw&d=DwIFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=QiF-05YzARosRvTYd84AB_UYInlydmFcjNmBM5XgySw&m=40ASKHPgpT2QHYZuVcUJ-FbQy5N4FW0bpJyHT6x4R3Q&s=u8ZqFF9OiXeRfmPEpWSd8DCJ3LHaLCK5UrhH7dk-gng&e=

  Paul McGrady:Here we are again...

  Michael Flemming:Great to have you Paul!

  Julie Hedlund:Slides are now unsynced.

  Susan Payne:can you remind me what registrant protections covers?

  Paul McGrady:+1 Kristina.  We won't even get it introduced in that timeframe

  Steve Chan:@susan, in brief, things like EBERO, COI

  Phil Buckingham:kristina , what topic would u like to do  one perhaps we could get concensus on at jo burg ?

  Kristina Rosette (Amazon Registry):I get it. But I don't think we can have a meaningful discussion of whether we should have different base agreements until everyone has read and understood the existing RA.  And we'll use the entire 22 minutes just getting through the questions.

  Susan Payne:ah yes, thanks Steve, I was having a mental block

  Kristina Rosette (Amazon Registry):@Phil:  I think vertical integration would be one. Michael's listing of the potential topics is a good idea.

  Steve Chan:Answered in brief, not in detail!

  Kristina Rosette (Amazon Registry):Can we take this to the email list?

  Phil Buckingham:thanks Kristina .  i tend to agree .

  Kristina Rosette (Amazon Registry):Paul's idea is fine, too

  Cheryl Langdon-Orr (CLO):better idea Paul

  Phil Buckingham:Great idea , Paul - thanks .

  Steve Chan:If you take it to the list, those that are not on this call would also be able to participate.

  Susan Payne:vertical integration

  Cheryl Langdon-Orr (CLO):Registrant Protections

  Gg Levine (NABP):Registry/registrar standardization

  Kristina Rosette (Amazon Registry):Vertical integration; and closed generics

  Paul McGrady 2:Closed generics

  Kristina Rosette (Amazon Registry):Given Steve's point, perhaps Steve could identify the top 4 subjects identified here and take to the list so folks not on the call can "vote"

  Steve Chan:Unless there is objection to Kristina's suggestion, staff is happy to execute.

  Michael Flemming:Let us go with Kristina's suggestion.

  Michael Flemming:yes

  Paul McGrady 2:come through soft and a bit fuzzy

  Susan Payne:fine

  Paul McGrady 2:Oops.  I turned up my volume, now he is fine...

  Kristina Rosette (Amazon Registry):The Affiliate definition is in Section 2.9(c) of the Registry Agreement.  Phil's summary of it was correct, but incomplete

  Susan Payne:is it just me or are the answers to 1a and b rather vague and open to interpretation?  has anyone actually be found to be in breach

  Cheryl Langdon-Orr (CLO):indeed Kristina

  Susan Payne:yes agree Kristina

  Kristina Rosette (Amazon Registry):@Susan:  Not that I'm aware of, but Compliance should be asked that.

  Steve Chan:@Susan, Kristina, no, breaches.

  Kristina Rosette (Amazon Registry):I think that there may be more data that we could ask for that Compliance can provide:  how many registry operators are vertically integrated; of that number, how many are within the same corporate family; how many complaints were there against ROs (overall - regardless of whether due to vertical integration); of the complaints referenced in the 1.b answer, how many ROs were those complaints against

  Steve Chan:The less than 10 complaints I believe is for all time, not just a period of time.

  Kristina Rosette (Amazon Registry):@Steve:  Really? That's 10 in 4 years.

  Steve Chan:Happy to confirm Kistina, but that's my understanding.

  Susan Payne:I think it would also be helpful to know how many registries if any have required to conduct remediation in some way.  I think "no breaches" means no formal breach notice but there may have been action require

  Kristina Rosette (Amazon Registry):@Steve: And, to be clear, I'm not doubting the answer, I'm pleasantly surprised

  Steve Chan:@Kristina, :)

  Steve Chan:@Susan, I believe the answer is less than 10 complaints where remediation was required.

  Steve Chan:Of course, if we have follow up questions for Contractual Compliance, staff is happy to ask on the WT's behalf.

  Susan Payne:@Steve, yes I assume so.  but it could actually be zero, which would be quite informative

  Kristina Rosette (Amazon Registry):Can we agree that we'll each read the CC2 comments so we don't need to have Phil (or Michael) read them out?

  Jeff Neuman:Is the question you are asking whether all TLDs should be able to have 1 -3 registrars

  Jeff Neuman:As a PDP Working Group, we do have to respond to all the comments as to how we considered them.  But we do not need to read all of the comments aloud.

  Susan Payne:you might also want to switch registrar, so for the period you switch you would have to have two. limiting just to one would be very restrictive

  Rubens Kuhl:It also comes down to bargaining power in the contract: having more than one gives a brand more negotiating power in the table.

  Kristina Rosette (Amazon Registry):I respectfully disagree with Phil.  I'd like to see us use the 45 minutes in Joburg to work through the comments rather than hone in on one point made by one Commenter on one subpart

  Jeff Neuman:Lets see if we can group the issues into categories of types of comments

  Cheryl Langdon-Orr (CLO):agree Jeff

  Kiran Malancharuvil:Agree with grouping the issues into categories and represnting various groups of views for discussion.  Much easier

  Steve Chan:Nope, that's it

  Paul McGrady 2:Next step: beer

  Steve Chan:you're more generous than i was thinking michael.

  Cheryl Langdon-Orr (CLO):bye for now safe travels to those who are attending JNB meeting

  Kiran Malancharuvil:Coffee for michael

  Kiran Malancharuvil::)

  Kiran Malancharuvil:Thanks all!

  Kristina Rosette (Amazon Registry):@Paul:  Not fair to those of us who have several more hours to go . . . .Safe travels everyone.

  Jeff Neuman:Beer at 7 am.....breafast of champions

  Susan Payne:bed for me

  Heather Forrest:Bye all

  Phil Buckingham:bed  for me


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg-wt2/attachments/20170616/43a246a8/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Track2 15 June 2017.mp3
Type: audio/mpeg
Size: 6999562 bytes
Desc: Track2 15 June 2017.mp3
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg-wt2/attachments/20170616/43a246a8/Track215June2017-0001.mp3>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Attendance TRACK 2 15 June.pdf
Type: application/pdf
Size: 181935 bytes
Desc: Attendance TRACK 2 15 June.pdf
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg-wt2/attachments/20170616/43a246a8/AttendanceTRACK215June-0001.pdf>