Hi there. Unfortunately voice quality degradation and background noise both peaked at the same during today's WT4 Registry Services discussion, so let me write here what I would like to have commented during the call. 1) RSEP is an acronym that sometimes is used to refer to the Registry Services Evaluation Policy, sometimes to the Registry Services Evaluation Process. The later is part of the first, but since an applicant is not a registry at time of application to a gTLD, what would be used to evaluate the proposed registry service is the Registry Services Evaluation Process, not the policy. Due to acronym collision, it seems that using only the full form of those two entities would be in order in writing the language. 2) It's good though to remember that there is a consensus policy, and that is not in the SubPro charter to review that policy; so we can't prevent any applicant that has not indicated a proposed registry service in its application to apply to provide it using RSEP in the minute it signs a contract with ICANN and becomes a registry. That's an option we don't need to enumerate in SubPro, because it already exists and will continue to exist. 3) While there are some intermediate steps in RSEP the policy specifying 15-day for the security, stability and competition check, the end-to-end targets that ICANN is aiming at is 20 days for an already existing service and 35 days for a new service. That can be factored both in the decision of application processing and in the applicant decision process of delineating a new service in the application or applying to it afterwards. Rubens