Update Root Zone Sample Clauses

Update Root Zone. The Root Zone must be updated to contain appropriate NS, DS and glue records. IANA is notified of a root zone update, performs its mandatory checks and coordinates changes with the root zone partners to ensure the change occurs. The Event Director will authorize a request to IANA for NS, DS and glue record updates in the root, which will be prepared by ICANN staff with technical data provided by the EBERO. While no specific service levels are defined, ICANN’s current understanding is that all root zone parties are both committed to 24x7 response capabilities, and that the timing commitments from those entities will facilitate (barring problems uncovered with mandatory checks) a root zone update within 4 hours of request.
AutoNDA by SimpleDocs

Related to Update Root Zone

  • List of Operator’s Subprocessors [Box 26] [Box 27] [Box 28] [Box 29]

  • 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.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.

  • Recovery Schedule If the initial schedule or any current updates fail to reflect the Work’s actual plan or method of operation, or a contractual milestone date is more than fifteen (15) days behind, Owner may require that a recovery schedule for completion of the remaining Work be submitted. The Recovery Schedule must be submitted within seven (7) calendar days of Owner’s request. The Recovery Schedule shall describe in detail Construction Contractor’s plan to complete the remaining Work by the required Contract milestone date. The Recovery Schedule submitted shall meet the same requirements as the original Construction Schedule. The narrative submitted with the Recovery Schedule should describe in detail all changes that have been made to meet the Contract milestone dates.

  • Reactive Power and Primary Frequency Response 9.6.1 Power Factor Design Criteria

  • Scope of Supply 12.1 The Goods and Related Services to be supplied shall be as specified in the Schedule of Requirements.

  • Estoppel Certificates and Financial Statements a. Estoppel Certificate by Tenant. Tenant, any sublessee or assignee or all of any portion of Tenant's interest under this Lease, will execute, acknowledge and deliver to Landlord, within fifteen (15) days of Landlord's written request, a certificate certifying: i. this Lease is unmodified and in full force and effect (or, if there have been modifications, that the Lease is in full force and effect, as modified, and stating the modifications); ii. the dates, if any, to which Rent, Additional Charges and other sums payable hereunder have been paid; iii. no notice has been received by Tenant of any Default which has not been cured, except as otherwise specified in such certificate, or, if there is an uncured Default, specifying the nature of such; iv. Landlord is not in default hereunder and no event which, with the passing of time, giving of notice, or both, would constitute a default by Landlord hereunder; and v. certifying such other information about the status of the Lease and the Leased Premises as may be required by Landlord. A failure to deliver an estoppel certificate within fifteen (15) days after delivery of a request therefor shall be a conclusive admission that, as of the date of the request for such statement: (w) this Lease is unmodified except as may be represented by Landlord in said request and is in full force and effect, (x) there are no uncured defaults in Landlord's performance, (y) no rent has been paid more than thirty (30) days in advance; and (z) the information regarding the status of the Lease, as represented by Landlord in said request, is true and correct. Any such certificate may be relied upon by any permitted prospective transferee, deed of trust beneficiary or mortgagee of Landlord's interest under this Lease.

  • Minimum Customer Support Requirements for TIPS Sales Vendor shall provide timely and commercially reasonable support for TIPS Sales or as agreed to in the applicable Supplemental Agreement.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Customer Service Standards The Franchising Authority hereby adopts the customer service standards set forth in Part 76, §76.309 of the FCC’s rules and regulations, as amended. The Grantee shall comply in all respects with the customer service requirements established by the FCC.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!