Loop Reservations 2.9.3.1 For a Mechanized LMU, NTBS may reserve up to ten (10) Loop facilities. For a Manual LMUSI, NTBS may reserve up to three (3) Loop facilities.
2.9.3.2 NTBS may reserve facilities for up to four (4) business days for each facility requested through LMU from the time the LMU information is returned to NTBS. During and prior to NTBS placing an LSR, the reserved facilities are rendered unavailable to other customers, including BellSouth. If NTBS does not submit an LSR for a UNE service on a reserved facility within the four (4)-day reservation timeframe, the reservation of that spare facility will become invalid and the facility will be released.
2.9.3.3 Charges for preordering Manual LMUSI or Mechanized LMU are separate from any charges associated with ordering other services from BellSouth.
2.9.3.4 All LSRs issued for reserved facilities shall reference the facility reservation number as provided by BellSouth. NTBS will not be billed any additional LMU charges for the Loop ordered on such LSR. If, however, NTBS does not reserve facilities upon an initial LMUSI, NTBS’s placement of an order for an advanced data service type facility will incur the appropriate billing charges to include SI and reservation per Exhibit A of this Attachment.
2.9.3.5 Where NTBS has reserved multiple Loop facilities on a single reservation, NTBS may not specify which facility shall be provisioned when submitting the LSR. For those occasions, BellSouth will assign to NTBS, subject to availability, a facility that meets the BellSouth technical standards of the BellSouth type Loop as ordered by NTBS.
Deviations, Reservations, and Omissions 27.1 During the evaluation of Tenders, the following definitions apply:
No reservations We have examined and have no reservations to the Tendering document, including Addenda issued in accordance with Instructions to tenderers (ITT 7);
Reservations for Registry Operations The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD. None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names shall be transferred as specified by ICANN. Registry Operator may self-allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement. Registry Operator may activate in the DNS at All Levels up to one hundred (100) names (plus their IDN variants, where applicable) necessary for the operation or the promotion of the TLD. Registry Operator must act as the Registered Name Holder of such names as that term is defined in the then-current ICANN Registrar Accreditation Agreement (RAA). These activations will be considered Transactions for purposes of Section 6.1 of the Agreement. Registry Operator must either (i) register such names through an ICANN-accredited registrar; or (ii) self-allocate such names and with respect to those names submit to and be responsible to ICANN for compliance with ICANN Consensus Policies and the obligations set forth in Subsections 3.7.7.1 through 3.7.7.12 of the then-current RAA (or any other replacement clause setting out the terms of the registration agreement between a registrar and a registered name holder). At Registry Operator’s discretion and in compliance with all other terms of this Agreement, such names may be released for registration to another person or entity. Registry Operator may withhold from registration or allocate to Registry Operator names (including their IDN variants, where applicable) at All Levels in accordance with Section 2.6 of the Agreement. Such names may not be activated in the DNS, but may be released for registration to another person or entity at Registry Operator’s discretion. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such names that remain withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Upon ICANN’s request, Registry Operator shall provide a listing of all names withheld or allocated to Registry Operator pursuant to Section 2.6 of the Agreement. Registry Operator may self-allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.
MAINTENANCE, REPAIR, AND RULES Tenant will, at Tenant’s sole expense, keep and maintain the Property in a good, clean and sanitary condition and repair during the term of this Agreement and any renewal thereof. Tenant shall be responsible to make all repairs to the Property, fixtures, appliances, and equipment therein that may have been damaged by Tenant’s misuse, waste or neglect, or that of the Tenant’s family or visitors. Tenant agrees that no painting will be done on or about the Property without the prior written consent of Landlord. Tenant shall promptly notify Landlord of any damage, defect or destruction of the Property or in the event of the failure of any of the appliances or equipment. The Landlord will use their best efforts to repair or replace any such damaged or defective areas, appliances or equipment.