Union Notification The Union shall be notified of all appointments, hirings, layoffs, transfers, recalls and terminations of employment.
Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-‐level domain name, or (B) block those second-‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment. 6.2.2 Notwithstanding subsection 6.2.1, Registry Operator may proceed with activation of names in the DNS zone without implementation of the measures set forth in Section 6.2.1 only if (A) ICANN determines that the Registry TLD is eligible for this alternative path to activation of names; and (B) Registry Operator blocks all second-‐level domain names identified by ICANN and set forth at <xxxx://xxxxxxxx.xxxxx.xxx/en/announcements-‐and-‐ media/announcement-‐2-‐17nov13-‐en> as such list may be modified by ICANN from time to time. Registry Operator may activate names pursuant to this subsection and later activate names pursuant to subsection 6.2.1. 6.2.3 The sets of names subject to mitigation or blocking pursuant to Sections 6.2.1 and 6.2.2 will be based on ICANN analysis of DNS information including "Day in the Life of the Internet" data maintained by the DNS Operations, Analysis, and Research Center (DNS-‐OARC) <xxxxx://xxx.xxx-‐xxxx.xxx/xxxx/xxxx/xxxx>. 6.2.4 Registry Operator may participate in the development by the ICANN community of a process for determining whether and how these blocked names may be released. 6.2.5 If ICANN determines that the TLD is ineligible for the alternative path to activation of names, ICANN may elect not to delegate the TLD pending completion of the final Name Collision Occurrence Assessment for the TLD, and Registry Operator’s completion of all required mitigation measures. Registry Operator understands that the mitigation measures required by ICANN as a condition to activation of names in the DNS zone for the TLD may include, without limitation, mitigation measures such as those described in Section 3.2 of the New gTLD Name Collision Occurrence Management Plan approved by the ICANN Board New gTLD Program Committee (NGPC) on 7 October 2013 as found at <xxxx://xxx.xxxxx.xxx/en/groups/board/documents/resolutions-‐ new-‐gtld-‐annex-‐1-‐07oct13-‐en.pdf>.
Recall Notification Notice of recall shall be sent to the bargaining unit member by certified mail. The City shall be deemed to have fulfilled its obligation by mailing the recall notice by certified mail, return receipt requested, to the last address provided by the bargaining unit member.
Name Collision Report Handling 6.3.1 During the first two years after delegation of the TLD, Registry Operator’s emergency operations department shall be available to receive reports, relayed by ICANN, alleging demonstrably severe harm from collisions with overlapping use of the names outside of the authoritative DNS. 6.3.2 Registry Operator shall develop an internal process for handling in an expedited manner reports received pursuant to subsection 6.3.1 under which Registry Operator may, to the extent necessary and appropriate, remove a recently activated name from the TLD zone for a period of up to two years in order to allow the affected party to make changes to its systems.
Name Collision Occurrence Management 6.1. No-‐Activation Period. Registry Operator shall not activate any names in the DNS zone for the Registry TLD (except for "NIC") until at least 120 calendar days after the effective date of this agreement. Registry Operator may allocate names (subject to subsection 6.2 below) during this period only if Registry Operator causes registrants to be clearly informed of the inability to activate names until the No-‐Activation Period ends.
Notification of Subsequent Employer Executive hereby agrees that prior to accepting employment with, or agreeing to provide services to, any other Person during any period during which Executive remains subject to any of the covenants set forth in Section 5, Executive shall provide such prospective employer with written notice of such provisions of this Agreement, with a copy of such notice delivered simultaneously to the Company.
Termination for continuing Force Majeure Event Either Party may, by written notice to the other, terminate this Framework Agreement if a Force Majeure Event endures for a continuous period of more than one hundred and twenty (120) Working Days.
Written Notification Failing settlement at this level, the Union shall in writing notify the Employer of the alleged discrepancy and the names of the employees involved, and the period of time that such discrepancy is claimed to cover. Upon receipt of such written notice, the Employer agrees to promptly furnish the representative of the Union wage data pertaining to the alleged wage discrepancy.
Customer Notification By executing this Agreement, the Advisor acknowledges that as required by the Advisers Act the Sub-Advisor has supplied to the Advisor and the Trust copies of the Sub-Advisor’s Form ADV with all exhibits and attachments (including the Sub-Advisor’s statement of financial condition) and will promptly supply to the Advisor copies of all amendments or restatements of such document. Otherwise, the Advisor’s rights under federal law allow termination of this contract without penalty within five business days after entering into this contract. U.S. law also requires the Sub-Advisor to obtain, verify, and record information that identifies each person or entity that opens an account. The Sub-Advisor will ask for the Trust’s legal name, principal place of business address, and Taxpayer Identification or other identification number, and may ask for other identifying information.
NOTICE OF ACCIDENTS 20.01 Tenant shall give notice to Landlord, promptly after Tenant learns thereof, of (i) any accident in or about the Demised Premises for which Landlord might be liable, (ii) all fires in the Demised Premises, (iii) all damages to or defects in the Demised Premises, including the fixtures, equipment and appurtenances thereof, for the repair of which Landlord might be responsible, and (iv) all damage to or defects in any parts or appurtenances of the Building’s sanitary, electrical, heating, ventilating, air-conditioning, elevator and other systems located in or passing through the Demised Premises or any part thereof.
