Applicant The individual who executed the application for coverage.
Help Desk A help desk for Product support issues (the “Help Desk”) will be available to Customer. Unless specified in an Order, Customer should contact 000.000.0000 to receive a telephone number for the applicable supporting Solutions & Support Center. Customer will appoint one Product administrator and one backup administrator to serve as the primary point of contact regarding maintenance services.
ICANN testing registrar Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement. 1. Registry Operator will use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement approved by the ICANN Board of Directors on 27 June 2013 in registering domain names. A list of such registrars shall be maintained by ICANN on ICANN’s website. 2. (Intentionally omitted. Registry Operator has not included commitments, statements of intent or business plans provided for in its application to ICANN for the TLD.) 3. Registry Operator agrees to perform the following specific public interest commitments, which commitments shall be enforceable by ICANN and through the Public Interest Commitment Dispute Resolution Process established by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/picdrp), which may be revised in immaterial respects by ICANN from time to time (the “PICDRP”). Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PICDRP panel and to be bound by any such determination. a. Registry Operator will include a provision in its Registry-‐Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting Registered Name Holders from distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law, and providing (consistent with applicable law and any related procedures) consequences for such activities including suspension of the domain name. b. Registry Operator will periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats, such as pharming, phishing, malware, and botnets. Registry Operator will maintain statistical reports on the number of security threats identified and the actions taken as a result of the periodic security checks. Registry Operator will maintain these reports for the term of the Agreement unless a shorter period is required by law or approved by ICANN, and will provide them to ICANN upon request. c. Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-‐discrimination by establishing, publishing and adhering to clear registration policies. d. Registry Operator of a “Generic String” TLD may not impose eligibility criteria for registering names in the TLD that limit registrations exclusively to a single person or entity and/or that person’s or entity’s “Affiliates” (as defined in Section 2.9(c) of the Registry Agreement). “Generic String” means a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others.
Classroom Visitation To provide patrons of the District the opportunity to visit classrooms with the least interruption to the teaching process, the following guidelines are set forth: A. All visitors to a school and/or classroom shall obtain the approval of the principal, and if the visit is to a classroom, the time will be arranged after the principal or his designee has conferred with the employee, if possible. B. Whenever possible, the employee shall be afforded the opportunity to confer with the classroom visitor before and/or after the visitation. C. This provision does not apply to administrators and Board of Directors members.
Applicants If the NRMP's investigation of an alleged Match violation by an applicant results in a finding that an applicant has committed a violation of this Agreement, the processing of the applicant's rank order list may be interrupted. The NRMP at its discretion may withdraw the applicant from the SMS Match. If a matched applicant is the subject of a violation investigation, the program to which the applicant matched may not fill the position with another applicant until the NRMP has issued the Final Report or granted a waiver, whichever is earlier. If the violation investigation has not concluded by the start date of training, the program shall begin training the matched applicant unless NRMP has granted a waiver or issued a deferral. The NRMP’s Final Report on the confirmed violation will be delivered to the applicant with copies to: (1) the applicant's medical school official, with a request that the Final Report be placed in the applicant’s permanent file (2) the Educational Commission for Foreign Medical Graduates if the applicant is a graduate of an international medical school (3) the NRMP institutional official and the director of the program to which the applicant matched (4) the NRMP institutional official and the director of the program to which the applicant has applied or switched (if known) (5) the party who originally reported the violation (6) the NRMP Executive Committee (7) the American Board of Medical Specialties (8) the American Osteopathic Association (9) the applicant's residency program director (10) the Federation of State Medical Boards if the applicant is to be permanently identified as a Match violator or permanently barred from future NRMP Matches (11) any parties whom the NRMP has determined are relevant to its investigation (12) state medical licensure boards, if requested by the applicant In addition, the applicant may be barred from subsequent NRMP Matches and/or identified as a Match violator to participating programs for one to three years or permanently, as determined by the NRMP. The applicant also may be barred for one year from accepting an offer of a position or a new training year, regardless of the start date, in any program sponsored by a Match-participating institution, and/or starting a position or a new training year in any program sponsored by a Match-participating institution if training would commence within one year from the date of issuance of the Final Report. Further, any applicant who has been denied a waiver of a binding commitment and who does not accept the matched position may be barred for one year from accepting an offer of a position or a new training year, regardless of the start date, in any program sponsored by a Match- participating institution and/or from starting a position or a new training year in any program sponsored by a Match- participating institution if training would commence within one year from the date of the NRMP's decision on the waiver. The decision conveyed in the Final Report will be displayed in the R3 system Applicant Match History for one to three years or permanently, as determined by the NRMP. Term limits of any sanction(s) imposed for the violation will be included to identify the length of time the action is in effect. The NRMP has sole discretion to determine which of the sanctions described above shall be applied in the event an applicant violates this Agreement. Failure to comply with sanctions levied as a result of a confirmed violation that is final may result in a new investigation and additional sanctions.
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
Searchable Whois Notwithstanding anything else in this Agreement, Registry Operator must offer a searchable Whois service compliant with the requirements described in Section 1.10 of Specification 4 of this Agreement. Registry Operator must make available the services only to authenticated users after they logged in by supplying proper credentials (i.e., user name and password). Registry Operator must issue such credentials exclusively to eligible users and institutions that supply sufficient proof of their legitimate interest in this feature (e.g., law enforcement agencies).
Settlement Website Within ten (10) days from entry of the Preliminary Approval Order, Notice shall be provided on a website at an available settlement URL (such as, for example, xxx.XXxxxxxxxxxxxxxxxxxx.xxx) which shall be obtained, administered and maintained by the Settlement Administrator and shall include the ability to file Claim Forms on- line, provided that such Claim Forms, if signed electronically, will be binding for purposes of applicable law and contain a statement to that effect. The Notice provided on the Settlement Website shall be substantially in the form of Exhibit D hereto.
Post-Observation Conference The teacher and evaluator shall schedule to meet for the post-observation conference as soon as reasonably possible after the formal observation, but not to exceed five school days. The post-observation conference includes a review of the teacher's self-assessment of the observation and the evaluator's evidence of the observation. Both the teacher and the evaluator may contribute evidence to the overall assessment of professional performance during the conference as such conference is intended to be a dialogue between the teacher and evaluator. At the end of the post- observation conference the teacher and evaluator will agree on next steps and sign documentation that the conference has occurred.
DNS name server availability Refers to the ability of a public-‐DNS registered “IP address” of a particular name server listed as authoritative for a domain name, to answer DNS queries from an Internet user. All the public DNS-‐registered “IP address” of all name servers of the domain name being monitored shall be tested individually. If 51% or more of the DNS testing probes get undefined/unanswered results from “DNS tests” to a name server “IP address” during a given time, the name server “IP address” will be considered unavailable.
