On 19 Jun 2018, at 20:48, Aikman-Scalese, Anne <AAikman@lrrc.com> wrote:
Rubens,
See comments inline. If these issues are not raised in the Initial Report, the discussions that occurred in Work Track 4 are not accurately reflected. (See especially the mp3 of the November 30 call and my follow up emails in January and February citing to the exact minute of the mp3 recording.)
Anne, while you are focused on the report, I referred to the actual substantive discussions in WT4. I'll let staff and co-chairs answer anything related to the report, which was not the focus of my responses.
2. Disclosure of New Services at the Time of Application. Regarding the portion of the draft report that deals with disclosure of new services at the time of application, Question 23 of the existing application requires that all new services proposed be described, including any security and stability issues that may be associated with that. The initial draft report skipped over this issue that was clearly raised in Work Track 4 and talked about the flexibility to propose new services either at the application stage or later on in the RSEP process (even if known at the time of application). As mentioned, there are “trade-offs” here in relation to opportunities for Objections and Evaluations and these should be highlighted for public comment.
Actually, it is quite the opposite. What is said there is that applicants would be able to disclose services at application time even if not submitting them to evaluation, increasing opportunity for Objections. There is no point in arguing this difference of opinion further. The 2012 round application Question 23 REQUIRES disclosure of all services at the time of application. This is not optional “would be able” disclosure. That’s why the draft does not reflect the discussion in Work Track 4.
I mentioned above how the WT4 outcome described how it could be done, not how 2012 round was done, which is only part of the report.
The draft says it’s optional and does not highlight the issue discussed in Work Track 4 which I have raised and documented multiple times.
It's actually silent on that, and others also didn't take that language as saying that, as you probably remember.
3. Aggregated Technical and Financial Evaluations. There was discussion in Work Track 4 about not putting applications that propose new and innovative services at a disadvantage as to timing of contract award based on the fact that these could not be processed as quickly. The purpose of the new gTLD program is innovation. Again, there are “trade-offs” here. This question falls into the category of items as to which there has been no coordination among the Work Tracks. While this may not have been the responsibility of Work Track 4 per se, that does not mean it is not a concern and does not mean it was not discussed. I am not the only person in the Work Track who mentioned this problem.
There is a fundamental difference between evaluation processing and results publishing. WT4 only addressed the first part; if a result is ready but due to the application sequencing it's publishing is not yet timely, then it won't be published. The process is not meant to be a waterfall, but a series of parallel efforts that have some control points, and any fairness issue is address at those control points. I and others expressed concern about the effect of this aggregation on time of processing applications in Work Track 4.
Actually not; only in Registry Services other have mentioned that, regarding aggregation of evaluations. Rubens