The call for the New gTLD Subsequent Procedures Working Group will take place on Monday, 19 October 2020 at 20:00 UTC for 90 minutes.

For other places see:


  1. Review Agenda/Updates to Statements of Interest
  2. Meeting with the SSAC re: draft Final Report – highlighted issues:
    1. Root Zone Delegation Rates
    2. How names are constructed: IDNs / Variants / Restricted character combos
    3. DNS Abuse itself and a proxy for other meta issues
    4. Registry Testing / Pre-evaluation process for Back End Operators
    5. TLD Types
    6. Rationale for Rejected SSAC Advice
    7. Name Collision / Interaction with Private TLD proposal
  3. Review draft Final Report Public Comments (time permitting) – to prepare see the Public Comment Review Tool at: and review the following topics:
    1. #32 Limited Challenge/Appeal Mechanism
    2. #9 Registry Voluntary Commitments/Public Interest Commitments
    3. #20 Application Change Requests
    4. #35 Auctions/Private Resolutions
    5. #2 Predictability
    6. #23 Closed Generics
  4. AOB





Apologies:  Maxim Alzoba, Flip Petillion, Anne Aikman-Scalese

Notes/ Action Items

  1. Updates to Statements of Interest: No updates provided.

2. Meeting with the SSAC re: draft Final Report – highlighted issues:

-- SSAC’s Work Party looking at two areas: 1) SSR issues in the draft Final Report; 2) Gap analysis – issues not in the draft Final Report.

a. Root Zone Delegation Rates

SSAC/Rod Rasmussen, Chair:

-- This gets into one of the biggest issues.  Lots of issues were well addressed in SSAC advice.

-- There are some issues that are outstanding around measuring and monitoring: how do you make decisions on when things are not going well?  When and how the metrics are dealt with.

-- Related to that is the concept of the SPIRT.

-- WG/Jeff Neuman, Co-Chair: OCTO recent paper on early warning system.  Technical community couldn’t agree on a solution, objective tests or metrics, so ICANN should just ask.  See Public Comment Forum announcement -- Recommendations for Early Warning for Root Zone Scaling at

-- SSAC/Rod Rasmussen, Chair:

Does the SPIRT provide the overarching framework?  It is more focused on specific issues, not an overarching process.  Could there be an oversight group that could say when things need to slow down?

--WG/Jeff Neuman, Co-Chair: How to incorporate SSR expertise and decision making into the SPIRT.  WG didn’t discuss that as part of the SPIRT role, but it can call experts on issues.  Meant to deal with process issues; and serve as a shepherd on possible policy issues.

-- SSAC/Geoff Houston: OCTO document is just an opinion.  There are contrary views.

-- SSAC/Rod Rasmussen, Chair: SSAC concern is that there might be overarching systemic SSR issues and it’s not clear that the SPIRT is set up to review those types of issues, or is empowered to do something about it.

-- SSAC/Rod Rasmussen, Chair: SSAC concern when it comes to contentious issues, such as root zone delegation, where you could have experts who don’t agree; if these got referred to the SPIRT it’s not clear how the SPIRT would make decisions and what criteria it would use.  SPIRT should not make SSR conclusions/recommendations without the appropriate technical expertise.

-- WG/Jeff Neuman, Co-Chair: The SPIRT is not a decision maker; but to help ICANN understand the potential impacts and make sure that when it comes to making a decision the right parties are involved.  SPIRT could make sure that the experts are involved.

-- SSAC/Rod Rasmussen, Chair: Who would have the authority to slow down delegations?  WG: Ultimately the ICANN Board.  The way we instructed the SPIRT is to make sure we can alert the stakeholders to the possible impacts.  Board wanted that clarified in the comments.  Transparency would be very important.

-- WG/Jeff Neuman, Co-Chair: Could consider having an SSAC liaison.

b. How names are constructed: IDNs / Variants / Restricted character combos

SSAC/Rod Rasmussen, Chair:

-- Interesting things around determining contention sets that from a technical aspect doesn’t make a lot of sense to look at intended use to decide if a string is confusingly similar. 

-- You can look at strings as they are and have some rules around that.

-- Inconsistencies on how plurals were addressed in the prior round.

-- Concerns about SWORD tool.

-- WG/Jeff Neuman, Co-Chair: SWORD tool -- Recommendation was to eliminate it.

-- WG/Jeff Neuman, Co-Chair: Not using intended use for putting things in contention sets and treatment of plurals and singulars; WG was considering doing a study on plurals and singulars – but the plurals were acquired so they went away by consolidation.

-- SSAC/Ram Mohan: On intended use – this should not be considered a defining characteristic on whether a string should be placed in a contention set or not because intended use changes over time.   Also, and expected use may not be how it is used in real life.  Thought it was not a good idea to apply intended use as a defining characteristic, although it could be something to note.

-- SSAC/Rod Rasmussen, Chair: You have the issue where the intended use changes over time and what are the rules for that? 

-- WG/Paul McGrady: Example of .apples – applied for by the Apple Growers Association and say they won’t sell computers, etc.  Could have a side agreement with Apple computers.

-- SSAC/Ram Mohan: What happens if someone registers bad.apples and uses it to talk about bad experiences with Apple computers?  The fundamental thing we are saying it’s a bad idea to have intended use being a defining factor, but could be an identifying factor.  Need to think about how to mitigate the risks, but it not always black and white.

-- WG/Jeff Neuman, Co-Chair: Whether it is the definitive factor or a factor someone won’t be happy if someone registers bad.apples.

c. DNS Abuse itself and a proxy for other meta issues

-- SSAC/Rod Rasmussen, Chair: These are issues that were noted as part of the last expansion as being potential issues with the original delegations.  But the majority of TLDs were okay.  But where there are problems, are those lessons learned?  Does there need to be a PDP?  How does that interact with subsequent rounds?  Is it a gating factor?  There is an engineering concept of being able to do something in a new space.  Are there best practices that would be rolled out for the new gLTDs?  Want to see any issues mitigated up front.  Where is that properly handled?

-- WG/Jeff Neuman, Co-Chair: The abuse that occurs in TLDs now is not because something is new versus old.  It happens because it is a registry or ccTLD that doesn’t take down sites.  Shouldn’t put restrictions on newer TLDs without dealing with older/legacy TLDs.  Needs to be handled on a global level, although GAC didn’t like that the SubPro didn’t make a recommendation on this.  There are a lot of people in the ICANN community that think if we can’t get the legacy players to do something we should put it on the new gTLDs and then make the legacy TLDs adopt the rules in their renewed contracts.  We think the appropriate place is for the GNSO Council to set the policy on DNS abuse.

-- SSAC/Rod Rasmussen, Chair: What were the primary drivers of concentrated abuse?  Pricing? - undoubtedly at 1 cent, poor filtering of bad actors registering names? likely.  Would be really good to have a solid understanding to make good decisions.  Lack of experience for new operators?  Maybe, maybe not.  Lots to know.  Don’t think anyone wants to punish new operators, but we want to make sure things are successful.

-- WG/Donna Austin: The data is important. ICANN has been talking about bad actors for some time, but are yet to provide evidence of what they are talking about. Also important to keep the conversation in perspective: are we talking about DNS abuse or abuse conducted on the Internet?

d. Registry Testing / Pre-evaluation process for Back End Operators

SSAC/Rod Rasmussen, Chair:

-- Idea of having back-end operators prove that they can do it over and over again doesn’t make tons of sense; it becomes interesting when you think about the scaling.  How do you test when you have a lot of concentration with back-end operators handling thousands of TLDs?  What about the next .com?

-- Might want to say that there is a base set of testing and then also testing for special circumstances.

-- WG/Jeff Neuman, Co-Chair: We aren’t trying to say that ICANN is certifying back-end registries.  The way you need to think about the pre-evaluation program is doing the evaluation earlier in time than you would have done it during the application process.  It isn’t a certification or pre-approval.  We do state that if you say you are using a pre-evaluated back-end operator but using new/additional services that the back-end operator wasn’t evaluated for then the back-end operator has to be re-evaluated for those services.

-- SSAC/Rod Rasmussen, Chair: Suggesting that ICANN org could produce an “RSP 101” type of document.  There is the applicant side and the backend side.  Lessons learned.

e. TLD Types

-- SSAC/Rod Rasmussen, Chair: SAC103: One of the things was that it was easy to become a publicly traded company.  There is a concern about bad actors being able to game this.

-- WG/Jeff Neuman, Co-Chair: In general most publicly traded companies have strict requirements/obligations for avoidance of crime; we didn’t ignore it but we didn’t think ICANN could have different regulations for different jurisdictions.

f. Name Collision / Interaction with Private TLD proposal

-- SSAC/Rod Rasmussen, Chair: We continue the work on name collisions.  We are moving forward to try to answer the Board questions.  There is enough time to get that work done before new gTLDs are launched.

-- WG/Jeff Neuman, Co-Chair: There are members of the WG have been debating whether the work of the NCAP should be a dependency for certain elements of the next round.  The NCAP is not making any recommendations as to whether their work should be a dependency for the next round; that would be a decision by the Board.

-- SSAC/Rod Rasmussen, Chair: It is not up to the SSAC or NCAP to make any recommendations concerning whether name collisions should be a dependency for new gTLDs.  We are trying to develop a framework to mitigate risks so that people can make better informed decisions.

-- WG/Jeff Neuman, Co-Chair: .corp, .home, and .mail are not in scope for this WG.  It is a matter of opinion as to what should be the dependencies for the next round.  If something is a dependency we need to decide at what point we need to make a decision?

-- SSAC/Rod Rasmussen, Chair: Outside of our remit too, although the question needs answering.

-- SSAC/Rod Rasmussen, Chair: SAC113 on Private Namespace – that is an ICANN/IETF interaction for creating a name/s that would be reserved from ever being published.  It would have that space for private use.  That is to try to address the issue that people keep picking up names and trying to do that; it would mitigate but not stop that practice.

-- WG/Jeff Neuman, Co-Chair: We know this was talked about as an issue between ICANN/IETF, but it has wider ramifications.  .onion and the satirical paper The Onion.

  • No labels