IANA Numbering Service Operational Requirements Sample Clauses

IANA Numbering Service Operational Requirements. The Operator shall perform the IANA Numbering Service in accordance with the following requirements: Process for handling of requests to the Operator by an RIR:
AutoNDA by SimpleDocs
IANA Numbering Service Operational Requirements the section referencing the “Process for handling of requests to the Operator by an RIR:” shall now be numbered 4.3.1. Additionally, the following section is incorporated as into Article 4.3, to be inserted directly after paragraph 4.3(d):

Related to IANA Numbering Service Operational Requirements

  • Operational Requirements 4 At-Sea Monitors are deployed, in accordance with coverage rates developed by 5 NMFS and as assigned through the Pre-Trip Notification System (PTNS), to 6 vessels. Due to availability of funding, changes in the fishery management, 7 such as emergency closures, court ordered closures, weather, and unforeseen 8 events must remain flexible. Additional funding for sea days may be added to 9 the contract within the scope and maximum allowable sea days. 10 The following items define the operational services to be provided by the 11 contractor under this contract.

  • Functional Requirements Applications must implement controls that protect against known vulnerabilities and threats, including Open Web Application Security Project (OWASP) Top 10 Risks and denial of service (DDOS) attacks.

  • Additional Service Requirements Grantee shall:

  • Additional Requirements for Sleeping Rooms The Contractor shall provide departing Attendees a secured area for storing belongings.

  • Closet/Urinal Requirements 6.1 Employees Closets Urinals 1-5 1 Nil 6-10 1 1 11-20 2 2 21-35 3 4 36-50 4 6 51-75 5 7 76-100 6 8

  • Developer Operating Requirements (a) Developer must comply with all applicable NYISO tariffs and procedures, as amended from time to time.

  • GENERAL OPERATIONAL REQUIREMENTS 12.1 Interference or damage to Distributor's Equipment by Customers: The Trader must, subject to clause 29.1, include in each of its Customer Agreements a requirement that, during the term of the Customer Agreement and until the end of the period ending on the earlier of 6 months after the termination of the Customer Agreement or the date on which a new Customer Agreement is entered into in respect of the relevant ICP, the Customer must not interfere with or damage, and must ensure that its agents and invitees do not interfere with or damage, the Distributor's Equipment without the prior written consent of the Distributor (except to the extent that emergency action has to be taken to protect the health or safety of persons or to prevent damage to property).

  • Procedural and Operational Requirements By accepting and using the Financial Assistance awarded under this Agreement and for this Program Element, LPHA agrees to conduct activities in accordance with the following requirements:

  • Trunk Forecasting Requirements 14.2.1 Initial trunk forecast requirements. At least ninety (90) days before initiating interconnection in a LATA, Alltel shall provide Verizon a two (2)-year traffic forecast that complies with the Verizon Interconnection Trunking Forecast Guide, as revised from time to time. This initial traffic forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Interconnection Trunk groups in the LATA over the next eight (8) quarters.

  • Additional Requirements from Authorized Users An Authorized User may have distinct requirements that must be met by all individuals employed by or working for the Authorized User. The Contractor’s Staff Members will be expected to comply with these requirements as a condition of the placement.

Time is Money Join Law Insider Premium to draft better contracts faster.