[Gnso-newgtld-wg] Notes and Action Items - New gTLD Subsequent Procedures PDP WG - 15 August 2019

Thu Aug 15 22:09:05 UTC 2019

Dear Working Group members,

Please see below the notes from the meeting today, 15 August 2019. These high-level notes are designed to help WG members navigate through the content of the call and are not a substitute for the recording, transcript, or the chat, which will be posted at: https://community.icann.org/display/NGSPP/2019-08-15+New+gTLD+Subsequent+Procedures+PDP.

Kind regards,

Julie

Julie Hedlund, Policy Director

Notes and Action Items:

Actions:

High-Level Agreements:
-- ACTION: Include a note in brackets by Reserved Names [“Unavailable Names, referred to in 2012 AGB as “Reserved Names”]
-- ACTION: Re: Comments generally support updating Schedule 5 to include the measures for Letter/Letter Two-Character ASCII Labels to Avoid Confusion with Corresponding Country Codes adopted by the ICANN Board on 8 November 2016.  Add a footnote to reference that there is ongoing discussion with the Board.

Notes:

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

2. Review of summary document – See: https://docs.google.com/document/d/1Q6_DxsCvSA_3B7ArncO2U4tWNY3vH7Wi4nINrouR4AI/edit?usp=sharing [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1Q6-5FDxsCvSA-5F3B7ArncO2U4tWNY3vH7Wi4nINrouR4AI_edit-3Fusp-3Dsharing&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=H5kutv0ahojxNmKWimrIQcybyWGVq4y7EV3jI1rhaFo&s=mddDmMlghwJWXtI3Sd7vjpw2GhnkadaZeNHNCRTc4vA&e=>
a. Reserved Names (page 4)

-- Two types of reserved names – top level and second level.
-- Not talking about Geographic Names (WT5), IGO/INGO (waiting for input from implementation), Red Cross/Red Crescent.

Discussion:
-- Make a note to put the deliberations in this section once they are complete.

High-Level Agreements:
-- General support reserving the names for Public Technical Identifiers.
-- General support reserving Special-Use Domain Names through IETF RFC 6761.
-- General support updating Schedule 5 to include the measures for Letter/Letter Two Character ASCII Labels etc.

Discussion:
-- Question: Shouldn’t we distinguish between “ineligible” strings and “reserve” for other parties? Answer: Helpful to make this distinction.  Reserved for non-use by anyone, or reserved for use by a particular, designated party.
-- Question: Is there any difference in the degree of protection between the top level and the second level?  Answer: If it is reserved at the top level it is reserved from application so you can’t apply for it.  Some names at the second level nobody may have, some are for the registry operator, and some for use by certain people.
-- In the AGB ICANN uses “reserved” – think of them as unavailable at the top level.
-- Should we add the new terms that we use instead of “WHOIS” such as “RDAP”.
-- ACTION: Include a note in brackets by Reserved Names [“Unavailable Names, referred to in 2012 AGB as “Reserved Names”]
-- ACTION: Add a foot note to reference that there is ongoing discussion with the Board.

Outstanding Items—New Ideas/Concerns/Divergence:
-- Question: Do we envision that these lists would never change?  Answer: Think they would be subject to review.
-- RySG: New Idea – If ICANN knows a level will not be delegated it should not be possible to apply for that label.  If not reserved,

Currency Codes Proposal (Christopher Wilkinson):
-- ISO 4217 Currency Codes.
-- “Reserve until such time that there is clear agreement with the international Central Banks (e.g. through IMF or BIS) as to whether these codes could be delegated and to which entities, not excluding themselves”
-- These platforms could result in seriously destabilizing aspects of the international financial systems.
-- Why protect the 3-letter country codes but not the currency codes?

Discussion:
-- Application includes identifying purposes.  And objections can be raised.  So, if for a financial purpose, we are likely to see GAC early warning and certain requirements applied.  Particularly with highly regulated services.
-- What is the damage?
-- Most likely GAC member will raise concerns.
-- Talked a few weeks ago about applicant freedom of expression.  Agreed that it is an important goal.
-- To protect a form a speech it should be the most narrow restriction.
-- Question: Is reserving them the least restrictive means, or does national law address this.
-- Not on solid ground to be taking preventative action unless there’s a clear risk of confusion.
-- Helpful to create two lists: 1) no one can have 2) special use case to apply.  Where do currency codes fall? That’s a judgement call.
-- Currency codes are pretty obscure. Many are not widely used.

Reserved Names and the Second Level:
-- Valideus: concern – 5 letter/letter 2 character ASCII labels remain reserved because they are IGO acronyms [so not sure we need to address them here]

Reserved Names at the Top Level:
Remove reservation of two-character letter-number combination:
-- Huge list of organizations oppose – confusion with country code.  This might belong in top level.
-- Substantial number of commenters that were not in favor, but also some supporting but taking measures to avoid confusion.
-- ACTION: Say that we allow it but should be taken up in the string confusion analysis.
-- If we allow any two-letter combination then that would water down the identification of ccTLDs.  Would a sublist of two-character TLD which match any ccTLD work?
-- Theme of potential for confusion.  Could be opportunity to pick up any of those similarity checks.  Recommendation that there need to be strong similarity checks.  Only 0 and 1 could cause confusion. Also 1, l, and capital i.
-- Given that the potential problem is so limited, and we haven’t as yet identified a likely risk of confusion, isn’t the best way to handle this through a Module 3 objection ground.

Voluntary reservation of up to 100 strings at the second level for the operation or the promotion of the TLD:
-- Registry can reserve unlimited number of strings, these are for the registry for its own use.
-- One of the reason for a request for more than 100 names is that the average big city has more than 100 names.  Geos had to reserve names during Sunrise to deliver to the local governments.
-- What is the origin of the number of 100?  How will it be used?  Came from informal discussion in ICANN.  Registries often establish cites to promote a name and they will use a second level TLD for that.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg/attachments/20190815/f4f6e733/attachment-0001.html>