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.
Distribution Services 3.1. Distributor will have the right, as agent for the Fund, to enter into dealer agreements with responsible investment dealers, and to sell Shares to such investment dealers against orders therefor at the public offering price (as defined below) stated in the Fund’s effective Registration Statement on Form N-2 under the 1940 Act and the Securities Act of 1933, as amended (the “Securities Act”), including the then-current prospectus and statement of additional information (the “Registration Statement”). Upon receipt of an order to purchase Shares from a dealer with whom Distributor has a dealer agreement, Distributor will promptly cause such order to be filled by the Fund. 3.2. Distributor will also have the right, as agent for the Fund, to sell such Shares to the public against orders therefor at the public offering price (as defined below) and in accordance with the Registration Statement. 3.3. Distributor will also have the right to take, as agent for the Fund, all actions which, in Distributor’s reasonable judgment, are necessary to carry into effect the distribution of the Shares. 3.4. The “public offering price” for the Shares of the Fund shall be the net asset value (“NAV”) of the Shares then in effect, plus any applicable sales charge determined in the manner set forth in the Registration Statement or as permitted by the 1940 Act and the rules and regulations promulgated by the SEC or other applicable regulatory agency or self-regulatory organization under the oversight of the SEC. In no event shall any applicable sales charge exceed the maximum sales charge permitted by the Rules of FINRA. 3.5. The NAV of the Shares of the Fund shall be determined in the manner provided in the Registration Statement, and when determined shall be applicable to transactions as provided for in the Registration Statement. The NAV of the Shares shall be calculated by the Fund or by another entity on behalf of the Fund. Distributor shall have no duty to inquire into or liability for the accuracy of the NAV per Share as calculated. 3.6. On every sale, the Fund shall receive the applicable NAV of the Shares promptly, but in no event later than the third business day following the date on which Distributor shall have received an order for the purchase of the Shares. 3.7. Upon receipt of purchase instructions, Distributor will transmit such instructions to the Fund or its transfer agent for the issuance and registration of the Shares purchased. 3.8. Distributor, as agent of and for the account of the Fund, may repurchase the Shares at such prices and upon such terms and conditions as shall be specified in the Registration Statement. 3.9. Distributor shall maintain membership with the National Securities Clearing Corporation (“NSCC”) and any other similar successor organization to sponsor a participant number for the Fund so as to enable the Shares to be traded through FundSERV. The Distributor shall not be responsible for any operational matters associated with FundSERV or networking transactions. 3.10. Distributor will review all proposed advertising materials and sales literature for compliance with Applicable Law and shall file such materials with appropriate regulators as required by current laws and regulations. Distributor agrees to furnish the Fund with any comments provided by regulators with respect to such materials. 3.11. Distributor shall prepare or cause to be prepared reports for the Board of Trustees (the “Board”) of the Fund regarding its activities under this Agreement as reasonably requested by the Board.
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.
Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Freedom 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 Freedom. 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 Freedom (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 Freedom, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Freedom will then have the option of paying the one-time SC rates to place the Loop.
Two-Way Interconnection Trunks 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Ymax, Ymax, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Ymax, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Ymax shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Ymax shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Ymax anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Ymax and Verizon. Ymax’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx- Xxxxxxxxx B.01 during the average time consistent busy hour. Verizon and Xxxx shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Ymax shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Ymax shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Ymax shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Ymax has not notified Verizon that it has corrected such blocking, Verizon may submit to Ymax a Trunk Group Service Request directing Ymax to remedy the blocking. Upon receipt of a Trunk Group Service Request, Ymax will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Ymax will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Ymax will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Ymax fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or bill (and Ymax shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and Ymax’s network, Verizon’s performance in connection with these Two- Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Ymax will route its traffic to Verizon over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Ymax to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between Ymax and the Verizon End Office.
Reserved for Future Use Reserved for Future Use
Dark Fiber 8.1 Access to unbundled Dark Fiber will be provided by Verizon, where existing facilities are available at the requested availability date, in the loop, subloop and interoffice facilities (IOF) portions of the Company's network. Access to Dark Fiber will be provided in accordance with, but only to the extent required by, Applicable Law. Except as otherwise required by Applicable Law, the following terms and conditions apply to Verizon's Dark Fiber offering. 8.2 A “Dark Fiber Loop” consists of continuous fiber optic strand(s) in a Verizon fiber optic cable between the fiber distribution frame, or its functional equivalent, located within a Verizon Wire Center, and Verizon’s main termination point, such as the fiber patch panel located within a Customer premise, and that has not been activated through connection to the electronics that “light” it, and thereby render it capable of carrying Telecommunications Services. In addition to the other terms and conditions of this Agreement, the following terms and conditions also shall apply to Dark Fiber Loops: 8.2.1 Verizon shall be required to provide a Dark Fiber Loop only where (1) one end of the Dark Fiber Loop terminates at Z-Tel's collocation arrangement and (2) the other end terminates at the Customer premise. A CLEC demarcation point shall be established either in the main telco room of a building where a Customer is located or, if the building does not have a main telco room, then at a location to be determined by Verizon. Verizon shall connect a Dark Fiber Loop to the demarcation point by installing a fiber jumper. 8.2.2 Z-Tel may access a Dark Fiber Loop only at a pre-existing hard termination point of such Dark Fiber Loop, and Z-Tel may not access a Dark Fiber Loop at any other point, including, but not limited to, a splice point. Verizon will not introduce additional splice points or open existing splice points to accommodate a CLEC’s request. Unused fibers located in a cable vault or a controlled environment vault, manhole or other location outside the Verizon Wire Center, and not terminated to a fiber patch, are not available to Z-Tel. 8.2.3 A strand shall not be deemed to be continuous if splicing is required to provide fiber continuity between two locations. Dark Fiber will only be offered on a route-direct basis where facilities exist (i.e., no intermediate offices). 8.2.4 Verizon shall perform all work necessary to install a cross connection or a fiber jumper, including, but not limited to, the work necessary to connect a dark fiber to a demarcation point, a fiber distribution frame or a POT bay. 8.2.5 At the Customer premise, unused fibers are not available to Z-Tel pursuant to this Attachment unless such fibers terminate on a fiber patch panel. Unused fibers in a fiber splice point located outside the Customer premise are not available to Z-Tel. 8.2.6 Dark Fiber will be offered to Z-Tel in the condition that it is available in Verizon's network at the time that Z-Tel submits its request (i.e., "as is"). In addition, Verizon shall not be required to convert lit fiber to Dark Fiber for Z-Tel's use. 8.2.7 Spare wavelengths on fiber strands, where Wave Division Multiplexing (WDM) or Dense Wave Division Multiplexing (DWDM) equipment is deployed, are not considered to be spare Dark Fiber Loops and, therefore, will not be offered to Z-Tel as Dark Fiber. 8.2.8 Z-Tel shall be responsible for providing all transmission, terminating and regeneration equipment necessary to light and use Dark Fiber. 8.2.9 Z-Tel may not resell Dark Fiber purchased pursuant to this Attachment to third parties. 8.2.10 In order for Verizon to continue to satisfy its carrier of last resort (COLR) obligations under Applicable Law and/or to preserve the efficiency of its network, Verizon will limit Z-Tel to leasing a maximum of twenty-five percent (25%) of the Dark Fiber in any given segment of Verizon's network during any two-year period. In addition, except as otherwise required by Applicable Law, Verizon may take any of the following actions, notwithstanding anything to the contrary in this Agreement: 8.2.10.1 Revoke Dark Fiber leased to Z-Tel upon a showing of need to the Commission and twelve (12) months' advance written notice to Z-Tel; and 8.2.10.2 Revoke Dark Fiber leased to Z-Tel upon a showing to the Commission that Z-Tel underutilized fiber (less than OC-12) within any twelve (12) month period. 8.2.10.3 Verizon may reserve Dark Fiber for maintenance purposes, or to satisfy Customer orders for fiber related services or for future growth. Verizon reserves and shall not waive, Verizon’s right to claim before the Commission that Verizon should not have to fulfill a Z-Tel order for Dark Fiber because that request would strand an unreasonable amount of fiber capacity, disrupt or degrade service to Customers or carriers other than Z-Tel, or impair a Verizon obligation to serve as a carrier of last resort. 8.2.11 Z-Tel may not reserve Dark Fiber.
Cloud storage DSHS Confidential Information requires protections equal to or greater than those specified elsewhere within this exhibit. Cloud storage of Data is problematic as neither DSHS nor the Contractor has control of the environment in which the Data is stored. For this reason: (1) DSHS Data will not be stored in any consumer grade Cloud solution, unless all of the following conditions are met: (a) Contractor has written procedures in place governing use of the Cloud storage and Contractor attests in writing that all such procedures will be uniformly followed. (b) The Data will be Encrypted while within the Contractor network. (c) The Data will remain Encrypted during transmission to the Cloud. (d) The Data will remain Encrypted at all times while residing within the Cloud storage solution. (e) The Contractor will possess a decryption key for the Data, and the decryption key will be possessed only by the Contractor and/or DSHS. (f) The Data will not be downloaded to non-authorized systems, meaning systems that are not on either the DSHS or Contractor networks. (g) The Data will not be decrypted until downloaded onto a computer within the control of an Authorized User and within either the DSHS or Contractor’s network. (2) Data will not be stored on an Enterprise Cloud storage solution unless either: (a) The Cloud storage provider is treated as any other Sub-Contractor, and agrees in writing to all of the requirements within this exhibit; or, (b) The Cloud storage solution used is FedRAMP certified. (3) If the Data includes protected health information covered by the Health Insurance Portability and Accountability Act (HIPAA), the Cloud provider must sign a Business Associate Agreement prior to Data being stored in their Cloud solution.
Dark Fiber Transport Dark Fiber Transport is defined as Dedicated Transport that consists of unactivated optical interoffice transmission facilities without attached signal regeneration, multiplexing, aggregation or other electronics. Except as set forth in Section 6.9.1 below, BellSouth shall not be required to provide access to Dark Fiber Transport Entrance Facilities pursuant to this Agreement.