[Gnso-igo-ingo] Reconvened WG on IFRC/ICRC Protections - Agenda - 2 August 2018 @ 14:00 UTC

Sun Aug 5 20:58:11 UTC 2018

Hi David and all,

Thank you for your input.  The only reference to acronyms in the WG's Final
Report are to only point out that they are out of scope per the GNSO
Council's instruction.  They will be addressed in the process of reconciling
GAC Advice with the previous IGO-INGO WG's recommendation among the GNSO,
GAC, and the ICANN Board.

Based on your attachment of the current use of the acronyms in .COM and
.ORG, I'd like to make clear how recommendations of reservation protection
are/will be implemented for full names, especially since these policy
recommendations include legacy gTLDs in addition to New gTLDs.  Should a
name already be registered, it will only become reserved should it follow
the entire domain name lifecycle. Specifically, if a domain expires, follows
the redemption grace period, and enters "Pending Delete" is at which point a
Registry Operator would reserve the domain and no longer be made available
for registration. Reservation implementation should not interfere in normal
domain practices, where already registered by a Registrant not associated
with the protected organization, should that Registrant chose to transfer
from one Registrar to another or to another Registrant. This will be
reconfirmed during the IRT should this WG's recommendations be adopted by
the Council and Board.  Until the reconciliation of recommendations occurs
for acronyms, it's too early to know what that protection outcome will be.

Thank you.

B

Berry A. Cobb

GNSO Policy Consultant

@berrycobb

From: David W. Maher [mailto:dmaher at pir.org] 
Sent: Friday, August 3, 2018 16:00
To: Chuck; mail at berrycobb.com; gnso-igo-ingo at icann.org
Subject: RE: [Gnso-igo-ingo] Reconvened WG on IFRC/ICRC Protections - Agenda
- 2 August 2018 @ 14:00 UTC

Re: acronyms

I'm not sure that this belongs in our Report, but it appears that the
acronyms are not currently protected.

Please note the attached informal survey of .COM and .ORG.

David Maher

From: Gnso-igo-ingo <gnso-igo-ingo-bounces at icann.org> On Behalf Of Chuck
Sent: Friday, August 3, 2018 9:34 AM
To: mail at berrycobb.com; gnso-igo-ingo at icann.org
Subject: Re: [Gnso-igo-ingo] Reconvened WG on IFRC/ICRC Protections - Agenda
- 2 August 2018 @ 14:00 UTC

Thanks Berry.  

Regarding the Finite List:

*	Am I correct that Red Star of David is not on the Finite List?
*	Will it be added?

Regarding the Report of Public Comments:

*	Here are some suggestions for the response to the CPH comments on
page 9: 

*	I think that the word 'assured' should be 'assures'.
*	I suggest changing 'in regards to' to 'in regard to' as suggested in
the spell check.
*	To make the response clearer and more responsive and to make a
couple of minor edits, I suggest rewording it to something like the
following: "The WG understands the concern and would like to clarify the
following: should the recommendations be adopted by the GNSO Council and
Board and subsequently implemented by ICANN Org, the only change to Registry
Agreements will be to the Specification 5 Reserved Names list
(https://www.icann.org/resources/pages/reserved-2013-07-08-en).  Further,
the updated consensus policy regarding the finite list will link to this
list." 
*	Note that this rewording fixed two minor edits that I think were
needed: 1) in the original wording I think 'assured' should be 'assures'; 2)
I changed 'in regards to' to 'regarding' as suggested by the spell checker.

*	On page 10, I don't think the response to the NCSG comments about
Recommendations 3, 4, 5 and 6 is responsive.  Repeating what we said for our
responses to the NCSG comments for Recommendations 1 and 2 doesn't seem
useful here.  It seems to me it would be better to say something like this:
"The WG fully supports the Council's intent to have a finite list, but we
believe that it is important to provide a mechanism to correct errors and
update that list without having to initiate a new PDP.  We believe that the
procedures detailed in these recommendations for making any such changes is
consistent with the Council's intent while at the same time providing a much
timelier means of fixing errors and accommodating verified changes to the
list, i.e., deletions or additions of national society names."

Regarding the Final Report, in Annex A, should we add that participants who
were not members of the original WG were invited to become members of the
Reconvened WG?  This seems like an important point to me.

Chuck

From: Gnso-igo-ingo <gnso-igo-ingo-bounces at icann.org> On Behalf Of
mail at berrycobb.com
Sent: Thursday, August 2, 2018 2:21 PM
To: gnso-igo-ingo at icann.org
Subject: Re: [Gnso-igo-ingo] Reconvened WG on IFRC/ICRC Protections - Agenda
- 2 August 2018 @ 14:00 UTC

Hi All,

Per our discussions today on the last Reconvened WG call, please find
attached the final deliverables. 

1.	Public Comment Review Tool - contains suggested edits from Stephane
(gnso-IGO-INGO-Reconvened-pcrt-20180802.docx)
2.	Final Report - contains all agreed edits from the participants on
the call (gnso-IGO-INGO-Reconvened-final-report-v1.2.docx)
3.	Finite List of RC Identifiers (National Society names
list_v0.9.xlsx)

The WG has until 5 August 2018 @ 23:59 to make any last minute proposals for
changes to the documents.  Also note, that Mary will send out a revised
version of the draft resolution under separate cover.

Thank you.

B

Berry A. Cobb

GNSO Policy Consultant

@berrycobb

From: Gnso-igo-ingo [mailto:gnso-igo-ingo-bounces at icann.org] On Behalf Of
mail at berrycobb.com
Sent: Tuesday, July 31, 2018 22:34
To: gnso-igo-ingo at icann.org
Subject: [Gnso-igo-ingo] Reconvened WG on IFRC/ICRC Protections - Agenda - 2
August 2018 @ 14:00 UTC

Hi All,

Please find below our planned agenda for Thursday's Reconvened WG meeting
for 2 August 2018 at 14:00 UTC.  The public comment period is now closed
with three submissions from the ALAC, RySG/RrSG, and the NCSG
(https://www.icann.org/public-comments/red-cross-protection-initial-2018-06-
21-en). 

This is our planned final call for the Reconvened WG.  Should agreement be
found across the public comments, final report, and draft resolution, the WG
will have until 5 August 2018 @ 23:59 UTC to review the final documents
prior to submission to the GNSO by the Motions and Documents deadline of 6
August 2018.

(0) Roll call, Agenda bash and SOI Updates

(1) Review of submitted public comments (attached,
gnso-IGO-INGO-Reconvened-pcrt-20180731.docx)

(2) Review of Final Report & finite list for outstanding issues (attached,
gnso-IGO-INGO-Reconvened-final-report-v1.1.docx, National Society names
list_v0.8.xlsx)

(3) Review of draft Council resolution (sent via separate email)

(4) Close of call and WG

Thank you.

B

Berry A. Cobb

GNSO Policy Consultant

@berrycobb

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-igo-ingo/attachments/20180805/5f4f21cf/attachment-0001.html>