[Gnso-newgtld-wg] Thoughts on PICs / RVCs (LONG NOTE)

[Jeff Neuman]

Alan,

Thank you for your thoughts.  A couple of comments:


  1.  We use terms like we believe/think, etc. because we are not the ultimate arbiters of the what the ICANN Bylaws allow or don’t allow. So, any statement that comes from us on this topic, while perhaps instructive, is not binding on anyone.



  1.  With respect to being a house of cards, you are in many way correct.  We have built a number of our recommendations off of what happened during the 2012 round and what we would like to see happen in future rounds.  If anything in the new Bylaws fundamentally changes our assumptions, then in some respects, we will have to come back and redo certain things.



  1.  Your first recommendation (of having ICANN choose who the dispute providers can be) may be problematic according to the discussions that we had with Avri and Becky. During that conversation they made it clear that the provider could not be under the control of ICANN.  Whether that means just payment (as in your first recommendation) or choosing a list of providers they would find acceptable is an open question that we cannot solve.



  1.  The main point about the email on PICs/RVCs is that we (the Working Group) still believe that all of our recommendations / implementation guidance that we have worked the past 4-5 years on are still valid.  We believe they all can be implemented for future rounds under the existing bylaws and thus, there are no true fundamental changes that we need to make based on the Board feedback.



  1.  The IRT, working with ICANN Org, will recommend whether that would need to result in changes to the Bylaws, but at this point, we are not in a position to recommend what needs to be done from that standpoint.


I hope that helps.

[cid:image001.png at 01D6D1FD.456BC4B0]
Jeffrey J. Neuman
Founder & CEO
JJN Solutions, LLC
p: +1.202.549.5079
E: jeff at jjnsolutions.com<mailto:jeff at jjnsolutions.com>
http://jjnsolutions.com


From: Alan Greenberg <alan.greenberg at mcgill.ca>
Sent: Saturday, December 12, 2020 1:09 AM
To: Jeff Neuman <jeff at jjnsolutions.com>; gnso-newgtld-wg at icann.org
Subject: Re: [Gnso-newgtld-wg] Thoughts on PICs / RVCs (LONG NOTE)

Jeff,

Sorry for the delay in replying to this message.

I am not at all sure I agree with some of you "principles", but the specific details are not relevant to this message.

However, the fact that I don't fully agree, and that you have used the expression "I/we believe/think" six times in this messages clearly implies some level of uncertainty regarding whether what you believe (or hope?) is how all of this will play out. Moreover, in at least one part of the scenario, you state as a fact something that may not turn out to be the case (see 1st remedy).

There are two remedies that can address these issues:

1. There needs to be an enforceable contractual provision that in the case of PIC/RVC disputes, the Registry must contract with an ICANN identified dispute resolution provider (or one of a pre-selected group of providers). And obviously pay for the process. If the Ry can choose the provider, or simply refuse to do it, the whole thing becomes a sham. I also note that there may be costs associated with setting up the dispute resolution process and ICANN would have to bear that.

2. As noted above, there are a LOT of assumptions, beliefs and hopes in all of this. If any of these prove false, the house of cards collapses and we may be left in the laughable position of ICANN signing contracts which they know will not be enforceable. In the real world, there will always be cases where some contractual terms end up being unenforceable, but it makes no sense at all to have that knowledge before signing and proceed. We must include a recommendation that,  should it turn out that the PIC/RVCs are not fully enforceable, the ICANN Board must take appropriate action to remedy the situation and ensure enforceability, even if that action requires Bylaw amendment.

Alan



At 2020-12-09 03:22 PM, Jeff Neuman wrote:


All,

I know there have been a lot of e-mails on this subject in the last week or so.  I wanted to give you some perspectives that we discussed at the leadership level to see if we can find some common themes and then we can see if any language in our report needs to change (which I am not convinced there will need to be substantial changes).  This is my (Jeff Neuman) summary to move the discussion along.

So, here is where I think we are on principles:



  1.  Existing PICs used as PICs in New Registry Agreements:  We believe that the existing PICs – worded substantially the same as they were in 2012 – are ok under ICANN’s Bylaws as they are sspecifically “grandfathered” in.



  1.  Domain Name Eligibility Rules:  We all seem to be on the same page that eligibility rules for the registration/renewal (but not necessarily usage) can be included in PICs/RVCs under ICANN Bylaws.



  1.  Voluntary Registry Commitments:



     *   Commitments made by Registries without ICANN Enforcement

                                                         i.      Registries and Registrars have reserved their rights to take down domain names for phishing, pharming, malware, and other forms of domain name abuse.  With respect to Registries, some have built these directly in as PICs while others have just built this into their Registry-Registrar Agreements (and some do both).  These types of PICs / RVCs do not seem to present any issue under the ICANN Bylaws (in our view).



                                                       ii.      We also believe that it is fairly common for registries to have policies that allow them to take down any domains used in connection with illegal activity, child exploitation, fraud, the sale of illegal pharmaceuticals, etc.



                                                     iii.      Because these do not require ICANN enforcement, we see no reason how or why this would present an ICANN Bylaw issues.  Conversely, we see no reason why we (through a PDP) would have any ability to restrict the ability of a registry to impose these types of commitments on their registrants (through registrars or directly).  So while we appreciate Kathy’s concern about a Registry’s ability to take down domain names, we do not believe that we are in a position to either require registries to take down names based on content or to prohibit them from doing so either.  Both could be considered forms of regulation (imposing rules on what a registry has to do or what it may not do).



                                                      iv.      Real Example Today.  .gay.  The Registry Operator for .gay (Top Level Design) want to have a safe space for the LGBTQ community.  That community, as most of you know, has historically been the subject of hate speech, violence, bullying, etc.  Having a safe space for the gay community according to the registry is its differentiator and is absolutely necessary.  It has an incredibly strict Rights Protections Policy ( https://www.ohhey.gay/gay-cares) that prevents Registrants from (i) inciting or promoting violence against others, (ii) Bullying, engaging in cyber bullying or inciting others to bully, (iii) Harassing, or encouraging others to harass or harm others, (iv) Stalking, (v) Abusive intent to cause fear or threaten violence, (vi) Hate Speech, (vii) Or activity intended to organize, coordinate, or otherwise enable one of the above.  It also reserves the right to take down any sites that do any of the above at its sole discretion.



     *   Commitments made by Registries that may require ICANN Enforcement in some capacity



Some Registries will want to make voluntary commitments in response to public comments, Government early warnings, objections, GAC Advice, etc. We do not see an issue with having these commitments reflected in Registry Agreements even if they fall outside of ICANN’s core mission IF in the case where the commitment does not fall within ICANN’s mission, neither ICANN itself nor any third party under ICANN’s control is involved in the decision as to whether the commitment itself has been violated.  Where an independent third party finds a violation of the commitment, ICANN should be able to rely on that third party decision and enforce a pre-arranged contractual remedy, which could include sanctions and/or termination of the Registry Agreement.



Examples / Use Cases:



  1.  If an Applicant applies for the TLD “.dictionarywordthatisalsobrandx” and Brand X objects to the application.  Applicant agrees with Brand X that it will not use the TLD in an infringing manner to Brand X.   In exchange for that Agreement, Brand X agrees to drop its Objection IF the Applicant agrees to put this commitment into its Registry Agreement in the form of an RVC.

     *   As a PDP Working Group we have often said that it is our preference for disputes, objections, etc. to be worked out between the parties where this is possible.  This is in line with our desire to see future expansion of the TLD space and encourage innovation and competition.
     *   As a result, this type of private resolution should be encouraged.
     *   The question, however, is whether ICANN could enforce this commitment.
     *   After our discussions with the ICANN Board liaisons and the comments we received by the community, the real concern was that ICANN did not believe it could be put in a decision to make these types of decisions (namely in this case whether Applicant’s use of the TLD violates its commitment to Brand X).
     *   If the Applicant and Brand X agree that any disputes involving their “settlement” are resolved by an independent third party (not ICANN) and the costs are borne by the parties (as opposed to ICANN), this should not present a problem.
     *   If ICANN implements the decision by the independent third party (which the Applicant agreed in its Registry Agreement to allow ICANN to do), this too should not present a Bylaws issue.
     *   The key point here is that ICANN itself is not imposing the restrictions on the Applicant and therefore should not be violating its own Bylaws.



  1.  What if an Applicant applies for .ideaexchange?  The Applicant wants to run the TLD as a place where registrants can put their open source ideas on the Internet and allow others to use their ideas in connection with whatever they want.  Comments are filed by businesses, governments, intellectual property owners and others concerned that this will be a space where users will exchange intellectual property that they do not own.  Lets also assume that the Independent Objector files an objection as well.  Assume Applicant never intended that and agrees that it will have a policy whereby Registrants agree that they will not use the TLD to distribute any intellectual property that is not owned by them.  And the Applicant also reserves the right to take down any names that use the TLD in violation of this policy.  To resolve the comments filed by governments, businesses, etc., the Applicant voluntarily agrees to have an RVC that states this policy and the takedown processes.  Each of the commenters and the Independent Objector agree that this would settle the matter and if documented in the Registry Agreement, they would drop their challenges.

     *   We believe that having these comments resolved in an amicable manner should be encouraged.
     *   Because this new policy has to be documented somewhere, the only real place it can be documented is as an RVC in the Registry Agreement.
     *   ICANN should not be the arbiter of whether there is a violation of this policy. This would certainly arguably be beyond its mission.
     *   However, if the arbiter of any disputes is an independent third party, not paid by ICANN, etc., then this would seemingly be ok even if it is agreed by the Applicant to follow the third party decision and to allow ICANN to impose the appropriate remedy.



Bottom Line:  I believe that so long as ICANN is not the ultimate decision maker in whether a policy that may arguably be outside of its mission, there should be no issues with having new PICs and/or Registry Voluntary Commitments.  If this indeed is the case, then we would just need to add a recommendation that (a) independent third parties must be used to resolved any potential violations of the PICs / RVCs, and (b) Applicants would need to agree in a Registry Agreement to be bound by the decision of the third party and to allow ICANN to impose sanctions / penalties.



[[]]

Jeffrey J. Neuman

Founder & CEO

JJN Solutions, LLC

p: +1.202.549.5079

E: jeff at jjnsolutions.com<mailto:jeff at jjnsolutions.com>

http://jjnsolutions.com<http://jjnsolutions.com/>






_______________________________________________
Gnso-newgtld-wg mailing list
Gnso-newgtld-wg at icann.org<mailto:Gnso-newgtld-wg at icann.org>
https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg
_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy ( https://www.icann.org/privacy/policy) and the website Terms of Service ( https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg/attachments/20201214/8d4e683d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 20537 bytes
Desc: image001.png
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg/attachments/20201214/8d4e683d/image001-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 3852 bytes
Desc: image002.jpg
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg/attachments/20201214/8d4e683d/image002-0001.jpg>