December 2016 - Gnso-newgtld-wg-wt4

Re: [Gnso-newgtld-wg-wt4] Consensus Call 1: Technical Capability to be evaluated after application, before contract signing
by Roger D Carney Dec. 16, 2016

Dec. 16, 2016

Good Morning, Just following along with a few of the questions/ideas Jeff raised. Are we trying to create an application process that does not take technical considerations into account until the TLD has been basically “awarded” to a single applicant? I think that would create a situation where many applicants would not understand the technical expertise and/or true costs needed to run a registry until after contention sets have been resolved and they will get to that spot and say “oh that is too hard” or “oh that is too expensive.” I think the technical questions and the discussions with the registry service providers are needed for Registry Operators to understand the true complexities and costs of running a TLD and realistically should be done prior to applying. And it seems like waiting to do this until after contention set resolution could be costly to the applicants and process. Thanks Roger From: gnso-newgtld-wg-wt4-bounces(a)icann.org [mailto:gnso-newgtld-wg-wt4-bounces@icann.org] On Behalf Of Rubens Kuhl Sent: Friday, December 16, 2016 6:20 AM To: Jeff Neuman <jeff.neuman(a)comlaude.com> Cc: gnso-newgtld-wg-wt4(a)icann.org Subject: Re: [Gnso-newgtld-wg-wt4] Consensus Call 1: Technical Capability to be evaluated after application, before contract signing On Dec 16, 2016, at 9:23 AM, Jeff Neuman <jeff.neuman(a)comlaude.com<mailto:jeff.neuman@comlaude.com>> wrote: The other question I have on the language is on the interaction with contention resolution (assuming there is one or more application windows or rounds). With your change, in theory we could have a situation where a prevailing registry in contention resolution may not pass a technical evaluation. Should there be a time limit on demonstrating its capabilities? It's already specified by ICANN that there is a time limit between being approved and signing a contract. It would fall within that time limit to either secure an approved RSP or get technical evaluation approval, or request an extension to ICANN to get such approval. If it is unable to demonstrate that, what do you do? Can get kind of messy? That's why there was also a question in Hyderabad, reflected in the slides, of what should happen in the case, but people seemed not interested in discussing it. We also have some similar situations right now like applicants not passing background screening, failing to pay the auction bid or simply failing to send the signed agreement to ICANN. I prefer thinking what happens even in corner cases such as this, but in this case the existing mechanism of allowing some time to sign and possibly grant an extension to that seems enough to handle it. Should we state that in the case of contention resolution it needs to be prior to the completion of such contention resolution? . The feedback in Hyderabad was the opposite of that: that only after contention resolution should the quest for technical capability begin, because it was only at that point that the applicant would be sure of having secured the TLD. Otherwise, many applicants have to secure contracts while only one will become a registry. That's exactly the issue this is trying to address. Rubens Jeffrey J. Neuman Senior Vice President |Valideus USA | Com Laude USA 1751 Pinnacle Drive, Suite 600 Mclean, VA 22102, United States E: jeff.neuman(a)valideus.com<mailto:jeff.neuman@valideus.com> or jeff.neuman(a)comlaude.com<mailto:jeff.neuman@comlaude.com> T: +1.703.635.7514 M: +1.202.549.5079 @Jintlaw From: Rubens Kuhl [mailto:rubensk@nic.br] Sent: Friday, December 16, 2016 10:47 AM To: Jeff Neuman <jeff.neuman(a)comlaude.com<mailto:jeff.neuman@comlaude.com>> Cc: gnso-newgtld-wg-wt4(a)icann.org<mailto:gnso-newgtld-wg-wt4@icann.org> Subject: Re: [Gnso-newgtld-wg-wt4] Consensus Call 1: Technical Capability to be evaluated after application, before contract signing Jeff, It would speed-up the process to reach both milestones of contract signing and TLD delegation, since the technical infrastructure won't have to be evaluated and delegation readiness will already be known. It will also allow applicants to choose a Registry Services Provider when they see fit; if they prefer selecting it before applying it would be their choice, if they prefer shopping for a provider after securing the TLD, they could too. It still keeps the freedom to use a completely new infrastructure and have it evaluated, a liberty that can be useful now that there is one open-source gTLD registry system available: http://domainincite.com/21147-google-could-shake-up-the-registry-market-wit… . (Previously, CoCCA had sources available but was not license-free to gTLD registries, only to ccTLD registries). But anticipating something from the implementation phase, I think it will make sense to have technical evaluation charged as a separate cost item for applicants, in order to benefit most of the applicants with the cost reduction potential of the RSP program. But that's a definition not in the table for now, just a side note for us to get back within the IRT for this policy. Rubens On Dec 16, 2016, at 7:25 AM, Jeff Neuman <jeff.neuman(a)comlaude.com<mailto:jeff.neuman@comlaude.com>> wrote: Rubens, If we had a Registry Services Provider pre-approval process, how would that process interact with the policy you have stated below? Jeffrey J. Neuman Senior Vice President |Valideus USA | Com Laude USA 1751 Pinnacle Drive, Suite 600 Mclean, VA 22102, United States E: jeff.neuman(a)valideus.com<mailto:jeff.neuman@valideus.com> or jeff.neuman(a)comlaude.com<mailto:jeff.neuman@comlaude.com> T: +1.703.635.7514 M: +1.202.549.5079 @Jintlaw -----Original Message----- From: gnso-newgtld-wg-wt4-bounces(a)icann.org<mailto:gnso-newgtld-wg-wt4-bounces@icann.org> [mailto:gnso-newgtld-wg-wt4-bounces@icann.org] On Behalf Of Rubens Kuhl Sent: Thursday, December 15, 2016 8:32 PM To: gnso-newgtld-wg-wt4(a)icann.org<mailto:gnso-newgtld-wg-wt4@icann.org> Subject: [Gnso-newgtld-wg-wt4] Consensus Call 1: Technical Capability to be evaluated after application, before contract signing Hi All. For those on our call, you know we issued our first consensus call, based on an sensation of consensus on this during the full WG F2F meeting in Hyderabad. No consensus calls are final since they can be changed if new information arises or when it goes to the full WG, but we would like those to be strong guidances for other WTs and the full WG of where are we headed to. Consensus calls will go for at least two readings; considering the non-optimal attendance we will refrain from issuing the 2nd reading for this item for a while so further discussion can arise. The idea is to change one specific recommendation from the original policy, which was Recommendation 7: “Applicants must be able to demonstrate their technical capability to run a registry operation for the purpose that the applicant sets out. “ Possible changed language: “Applicants must be able demonstrate their technical capability to run a registry operation for the purpose that the applicant sets out, but will only be required to do so at contract-signing time, after passing other criteria and/or approvals and prevailing in contention set(s), if any.” Rationale: In the 2012-rounds applicants were required to contract, or internally develop, technical capability prior to applying. This was a burden for applicants that were required to pay a one-time or recurring fee to get access to such technical capability and in most cases made applicants stick to their originally contracted back-end provider due to time-to-market concerns. 2012-round showed that technical capabilities are somewhat easily contracted in the market for affordable prices. What changed from 2007 that supports the change: It was not foreseen that the registry service provider market would achieve the level of maturity and commoditization that is now seen; only a small percentage (that we can gather and publish in the final version) of applicants used their own internal back-end infrastructure. Portfolio applicants were not really thought of. Possible alternatives: - Keeping the original recommendation as it was - Moving the technical evaluation to some other point in the application lifecycle For discussion, comments, opposition... I will note that a rough consensus doesn't require unanimity, but even a single opposition with a compelling rationale can change a consensus call, so please don't take popularity of lack of thereof as criteria. We want to achieve the best possible result in adding the combined expertise of the group, which includes listening to every opinion. Best, Rubens _______________________________________________ Gnso-newgtld-wg-wt4 mailing list Gnso-newgtld-wg-wt4(a)icann.org<mailto:Gnso-newgtld-wg-wt4@icann.org> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt4

2 1

Consensus Call 1: Technical Capability to be evaluated after application, before contract signing
by Rubens Kuhl Dec. 16, 2016

Dec. 16, 2016

Hi All. For those on our call, you know we issued our first consensus call, based on an sensation of consensus on this during the full WG F2F meeting in Hyderabad. No consensus calls are final since they can be changed if new information arises or when it goes to the full WG, but we would like those to be strong guidances for other WTs and the full WG of where are we headed to. Consensus calls will go for at least two readings; considering the non-optimal attendance we will refrain from issuing the 2nd reading for this item for a while so further discussion can arise. The idea is to change one specific recommendation from the original policy, which was Recommendation 7: “Applicants must be able to demonstrate their technical capability to run a registry operation for the purpose that the applicant sets out. “ Possible changed language: “Applicants must be able demonstrate their technical capability to run a registry operation for the purpose that the applicant sets out, but will only be required to do so at contract-signing time, after passing other criteria and/or approvals and prevailing in contention set(s), if any.” Rationale: In the 2012-rounds applicants were required to contract, or internally develop, technical capability prior to applying. This was a burden for applicants that were required to pay a one-time or recurring fee to get access to such technical capability and in most cases made applicants stick to their originally contracted back-end provider due to time-to-market concerns. 2012-round showed that technical capabilities are somewhat easily contracted in the market for affordable prices. What changed from 2007 that supports the change: It was not foreseen that the registry service provider market would achieve the level of maturity and commoditization that is now seen; only a small percentage (that we can gather and publish in the final version) of applicants used their own internal back-end infrastructure. Portfolio applicants were not really thought of. Possible alternatives: - Keeping the original recommendation as it was - Moving the technical evaluation to some other point in the application lifecycle For discussion, comments, opposition... I will note that a rough consensus doesn't require unanimity, but even a single opposition with a compelling rationale can change a consensus call, so please don't take popularity of lack of thereof as criteria. We want to achieve the best possible result in adding the combined expertise of the group, which includes listening to every opinion. Best, Rubens

2 4

Discussion theme: sequence and method for financial evaluation
by Rubens Kuhl Dec. 15, 2016

Dec. 15, 2016

• AGB clearly overlooked different business models in 2012-round • Revenue-generating or self-sustainable registry (profit or non-profit) • Cost-center registry (typical of brands, possibly causes) • Besides different financial goals, single-application evaluation overlooked the possibility of an applicant winning so many TLDs to the point of not being able to run them (gaming the system) • Rec. 8: “Applicants must be able to demonstrate their financial and organisational operational capability.” • Possible Language: “Applicants must be able to demonstrate their financial and organisational operational capability in tandem for all currently-owned and applied-for TLDs that would be part of a single registry family.” • Financial Evaluation would still be gating and be done prior to contention set resolution

1 0

Discussion theme: Technical Evaluation to be performed as aggregated / consolidated as feasible
by Rubens Kuhl Dec. 15, 2016

Dec. 15, 2016

Hi All, Besides the consensus call I have already posted, we discussed two themes in the last WT4 call. I'll post them in different messages for easier ongoing discussion. Technical Evaluation to be performed as aggregated / consolidated as feasible • Consolidation is not fully tied with back-end certification, could apply to applications from the same applicant, but can be an enabler • Possible Language: “Technical Evaluation may be aggregated and/or consolidated to the maximum extent possible that generate process efficiencies, including both different applications from the same applicant and different applications sharing a common technical infrastructure” Ideas ? This is a discussion that will likely have some overlap with WT1, but that can be reconciliated by the full WG. The idea is to also explore possibilities that may or may not fall into some kind of registry service provider program (previously known as accreditation or certification). Rubens

1 0

Next WT4 meeting
by Rubens Kuhl Dec. 15, 2016

Dec. 15, 2016

(sorry for the incomplete message sent before) Hi there. We had yesterday a WT4 call where even though it was postponed from last week, we still had a somewhat low attendance. Considering next week this could be even harder due to holidays, if you plan to be at the next call please answer the following Doodle poll: http://doodle.com/poll/kdqibbhv74b264bb If you are not attending we will be glad to know that too. Thanks, Rubens WT4 co-chair

1 0

Next WT4 meeting
by Rubens Kuhl Dec. 15, 2016

Dec. 15, 2016

Hi there. We had yesterday

1 0

Recording, Attendance & AC Chat from New gTLD Subsequent Procedures Sub Team Track 4 IDNs/Technical & Operations call
by Michelle DeSmyter Dec. 14, 2016

Dec. 14, 2016

Dear All, Please find the attendance and recording of the call attached to this email and the AC Chat below for the New gTLD Subsequent Procedures Sub Team – Track 4 – IDNs/Technical & Operations held on Wednesday, 14 December 2016 at 20:00 UTC. The recordings of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/en/group-activities/calendar<http://gnso.icann.org/en/group-activities/calendar#nov> ** Please let me know if your name has been left off the list ** Mailing list archives: http://mm.icann.org/pipermail/gnso-newgtld-wg-wt4 Wiki page: https://community.icann.org/x/K6HDAw Thank you. Kind regards, Michelle ------------------------------- Adobe Connect chat transcript for 14 December 2016 Michelle DeSmyter:Dear All, Welcome to the New gTLD Subsequent Procedures Sub Team – Track 4 – IDNs/Technical & Operations call on Wednesday, 14 December 2016 at 20:00 UTC. Michelle DeSmyter:Meeting page: https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_… Julie Hedlund:That sounds fine -- thanks! Phil Buckingham:rubens - you are very faint . Could you speak up avri doria:idoegraphic cs. non ideographic avri doria:? Phil Buckingham:me too - re headphones . but still faint avri doria:might want to consider adding ", if any" at the end of the stmt. Cheryl Langdon-Orr (CLO):good point Avri avri doria:i think we need two reading, both on calls to close a consensus call. Cheryl Langdon-Orr (CLO):yes the rationale is important on this proposed recommendation Phil Buckingham:this is a catch 22 , since the technical costs/ so contractual relationship with the backend provider will need be incurred and the costs put in the financial model for evaluation . Cheryl Langdon-Orr (CLO):thx Avri Phil Buckingham:no audio Phil Buckingham:thanks Cheryl avri doria:wee have to learn to speak again on AC. hard to do i know, i almost forgot how. Steve Chan:@Phil, we are happy to provide a dial out if you'd care to join! Phil Buckingham:point taken , Avri Steve Chan:If I recall, part of why every application was considered indivudually overall was related to principles of fairness? Kurt would probably be able to fact check that statement. Kurt Pritz:I have a bad connection. and did not hear the question Kurt Pritz:can you repeat. ? or skip me? Phil Buckingham:Totally agree Kurt. and nobody knew who was going to apply , how many portfolio players would submit multiple applications using the same model Rubens Kuhl:Kurt, that was Steve question from the chat above. Cheryl Langdon-Orr (CLO):chat above from Steve Phil Buckingham:the financial model was templated / standardised . It wont work for Round 2 . Each applicant's financial model needs to treat separately , evaluated , due diligence accordingly Phil Buckingham:Agreed Alan . Alot more . Steve Chan:@Rubens, I tried to note that the report acknowledges those challenges to some degree, but apparently i made that point ineffectively Steve Chan:So not just about inefficiency... ************************************************************************************************************************************************** Action Items/Discussion Notes 14 December 1. Hyderabad recap [slide 5 of the slide deck] -- Support for IDN 1-character was pictogram (Japanese or Korean), but opposition was not to Latin and Cyrillic, but use a more generic term. -- Probably would be good to use generic terms for all of them. -- Only those that represent 1 word. -- On support for IDN Variant TLDS -- Staff have had preliminary discussions with Sarmad Hussain on staff. He could provide background or a status update on the program. >From the Chat: avri doria: idoegraphic cs. non ideographic 2. Consensus call 1: Technical capability to be assessed at contract signing time [slide 7 in the slide deck] Possible language: "Applicants must be able to demonstrate their technical capability to run a registry operation for the purpose that the applicant sets out, but will only be required to do so at contract-signing time, after passing other criteria and/or approvals and prevailing in contention set(s), [if any]." -- If we do a consensus call over email should have the full story documented and presented to be taken into account. -- Today's discussion is just a temperature taking, not a consensus call. -- Explaining why the change is being made is important. Good to lay out those conditions, which will help this make sense. -- The financial model and testing the technical model are two different things. >From the chat: avri doria: might want to consider adding ", if any" at the end of the stmt. Cheryl Langdon-Orr (CLO): good point Avri avri doria: i think we need two reading, both on calls to close a consensus call. Cheryl Langdon-Orr (CLO): yes the rationale is important on this proposed recommendation Phil Buckingham: this is a catch 22 , since the technical costs/ so contractual relationship with the backend provider will need be incurred and the costs put in the financial model for evaluation. Cheryl Langdon-Orr (CLO): thx Avri 3. Discussion: Technical evaluation of applications to be performed as aggregated as feasible [slide 9 from the slide deck] -- During the evaluation process there wasn't a realization of how the market would evolve with respect to backend providers . -- It was thought at the outset that individual applications needed to be evaluated in the absense of knowing that the backend marketplace would be established. Things didn't work out as predicted. >From the Chat: Steve Chan: If I recall, part of why every application was considered indivudually overall was related to principles of fairness? Kurt would probably be able to fact check that statement. Phil Buckingham: Totally agree Kurt. and nobody knew who was going to apply , how many portfolio players would submit multiple applications using the same model 4. Discussion: Timing and method for Financial Evaluation [slide 10 from the slide deck] -- Could have speculative applications. The financial models are going to vary even more if the price goes down. -- Look at the program implementation report that staff produced. There were inefficiencies from treating every application individually. >From the chat: Phil Buckingham: the financial model was templated / standardised . It wont work for Round 2 . Each applicant's financial model needs to treat separately , evaluated , due diligence accordingly Agreed Alan . Alot more . Steve Chan: @Rubens, I tried to note that the report acknowledges those challenges to some degree, but apparently i made that point ineffectively. So not just about inefficiency...

1 0

Meeting starts in 7 minutes
by Rubens Kuhl Dec. 14, 2016

Dec. 14, 2016

Hi All, Just a reminder that meeting #5 of this work track is starting in 7 minutes, at 2000 UTC. Rubens

3 2

Actions/Discussion Notes: Work Track 4 SubTeam Meeting 14 December
by Julie Hedlund Dec. 14, 2016

Dec. 14, 2016

Dear Sub Team Members, Please see below the action items and discussion notes captured by staff from the meeting on 14 December. These high-level notes are designed to help Work Track Sub Team members navigate through the content of the call and are not meant to be a substitute for the recording. Please also see the recording on the meetings page at: https://community.icann.org/display/NGSPP/Work+Track+4+Meetings. Note also that the referenced slides for today’s meeting are attached. Best regards, Julie Julie Hedlund, Policy Director Action Items/Discussion Notes 14 December 1. Hyderabad recap [slide 5 of the slide deck] -- Support for IDN 1-character was pictogram (Japanese or Korean), but opposition was not to Latin and Cyrillic, but use a more generic term. -- Probably would be good to use generic terms for all of them. -- Only those that represent 1 word. -- On support for IDN Variant TLDS -- Staff have had preliminary discussions with Sarmad Hussain on staff. He could provide background or a status update on the program. >From the Chat: avri doria: idoegraphic cs. non ideographic 2. Consensus call 1: Technical capability to be assessed at contract signing time [slide 7 in the slide deck] Possible language: "Applicants must be able to demonstrate their technical capability to run a registry operation for the purpose that the applicant sets out, but will only be required to do so at contract-signing time, after passing other criteria and/or approvals and prevailing in contention set(s), [if any]." -- If we do a consensus call over email should have the full story documented and presented to be taken into account. -- Today's discussion is just a temperature taking, not a consensus call. -- Explaining why the change is being made is important. Good to lay out those conditions, which will help this make sense. -- The financial model and testing the technical model are two different things. >From the chat: avri doria: might want to consider adding ", if any" at the end of the stmt. Cheryl Langdon-Orr (CLO): good point Avri avri doria: i think we need two reading, both on calls to close a consensus call. Cheryl Langdon-Orr (CLO): yes the rationale is important on this proposed recommendation Phil Buckingham: this is a catch 22 , since the technical costs/ so contractual relationship with the backend provider will need be incurred and the costs put in the financial model for evaluation. Cheryl Langdon-Orr (CLO): thx Avri 3. Discussion: Technical evaluation of applications to be performed as aggregated as feasible [slide 9 from the slide deck] -- During the evaluation process there wasn't a realization of how the market would evolve with respect to backend providers . -- It was thought at the outset that individual applications needed to be evaluated in the absense of knowing that the backend marketplace would be established. Things didn't work out as predicted. >From the Chat: Steve Chan: If I recall, part of why every application was considered indivudually overall was related to principles of fairness? Kurt would probably be able to fact check that statement. Phil Buckingham: Totally agree Kurt. and nobody knew who was going to apply , how many portfolio players would submit multiple applications using the same model 4. Discussion: Timing and method for Financial Evaluation [slide 10 from the slide deck] -- Could have speculative applications. The financial models are going to vary even more if the price goes down. -- Look at the program implementation report that staff produced. There were inefficiencies from treating every application individually. >From the chat: Phil Buckingham: the financial model was templated / standardised . It wont work for Round 2 . Each applicant's financial model needs to treat separately , evaluated , due diligence accordingly Agreed Alan . Alot more . Steve Chan: @Rubens, I tried to note that the report acknowledges those challenges to some degree, but apparently i made that point ineffectively. So not just about inefficiency...

1 0

Work Track 4 agenda for 14 Dec 2016
by Rubens Kuhl Dec. 12, 2016

Dec. 12, 2016

Dear WT4 members, The call for the New gTLD Subsequent Procedures Sub Team – Track 4 - IDNs/Technical & Operations will take place on Wednesday, 14 December 2016 at 20:00 UTC, 12:00 PST, 15:00 EST, 20:00 London, 21:00 CET. For other times: http://tinyurl.com/hsjzcqf <http://tinyurl.com/hsjzcqf> The proposed agenda is as follows: 1. Welcome 2. SOIs 3. Hyderabad recap 4. Consensus call 1: Technical capability to be assessed at contract signing time 5. Discussion: Technical evaluation of applications to be performed as aggregated as feasible 5. Discussion: Timing and method for Financial Evaluation Adobe Connect room: https://participate.icann.org/newgtldsubteams/ <https://participate.icann.org/newgtldsubteams/> You can connect your audio by following instructions in the pop up in the AC room, or use the Connect Me option that was sent in the calendar invitation. Best, Rubens

1 0