Rest Stops Sample Clauses

Rest Stops. ‌ There shall be a minimum of one (1) twenty (20) minute comfort stop during each two (2) hours of travel. The twenty (20) minutes of such comfort stops shall be deemed part of travel time. Time beyond the twenty (20) minutes, if any, shall not be deemed part of the travel time.
Rest Stops. The Employer agrees that where an Artist is required to travel by means of bus the Artist will have a one hour rest stop for every 4 hours of travel and a 20 minute rest stop for every 2 hours of travel.

Related to Rest Stops

  • Surgery Services and Mastectomy Related Treatment This plan provides benefits for mastectomy surgery and mastectomy-related services in accordance with the Women’s Health and Cancer Rights Act of 1998 and Rhode Island General Law 27-20-29 et seq. For the member receiving mastectomy-related benefits, coverage will be provided in a manner determined in consultation with the attending physician, physician assistant, or an advance practice registered nurse and the patient, for: • all stages of reconstruction of the breast on which the mastectomy was performed; • surgery and reconstruction of the other breast to produce a symmetrical appearance; • prostheses; and • treatment of physical complications at all stages of the mastectomy, including lymphedema. See the Summary of Medical Benefits for the amount you pay.

  • Country Club Membership Employer agrees to reimburse Executive for reasonable country club membership dues, in accordance with Employer’s policy.

  • Dark Fiber Loop 2.8.4.1 Dark Fiber Loop is an unused optical transmission facility, without attached signal regeneration, multiplexing, aggregation or other electronics, from the demarcation point at an End User’s premises to the End User’s serving wire center. Dark Fiber Loops may be strands of optical fiber existing in aerial or underground structure. BellSouth will not provide line terminating elements, regeneration or other electronics necessary for AFN to utilize Dark Fiber Loops.

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Onvoy’s own expense, shall: 2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment. 2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.

  • EPP Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF) including all successor standards, modifications or additions thereto relating to the provisioning and management of domain names using the Extensible Provisioning Protocol (EPP) in conformance with RFCs 5910, 5730, 5731, 5732 (if using host objects), 5733 and 5734. If Registry Operator implements Registry Grace Period (RGP), it will comply with RFC 3915 and its successors. If Registry Operator requires the use of functionality outside the base EPP RFCs, Registry Operator must document EPP extensions in Internet-­‐Draft format following the guidelines described in RFC 3735. Registry Operator will provide and update the relevant documentation of all the EPP Objects and Extensions supported to ICANN prior to deployment.