Node Set-up Clause Samples

Node Set-up. Upon joining the Council, a Member will work with ▇▇▇▇▇▇’s DevOps team to finalize a plan for operating its Node. A Member will be required to manage its Node independently within 90 days of joining the Council. When the member is not independently operating a node, ▇▇▇▇▇▇ may set up a Node on behalf of such Member and such Member will accept shared control with Hedera of such Node (a Node under such shared control, a “Transitional Node.”) ▇▇▇▇▇▇, and not the Member, will be responsible for the costs or IT support relating to the management of a Transitional Node. During any period in which a Member has a Transitional Node, the Member will not be eligible to receive any of the fees and/or rewards described in paragraph B.5 below. Members shall provide Hedera with the current location (minimally region and country) where their node is operating. Members shall provide updates to Hedera within 90 days of a change in hosting location. Hedera may publish the location of Hedera nodes operating on Mainnet along with the attribution of members to their specific node.
View SourceView Similar (20)
Node Set-up. The Participant will be required to set-up and manage its MainNet Transition Program Participant’s Node independently no later than three (3) months after MainNet Launch Date.
View Source
Node Set-up. Upon joining the Council, a Member will work with Hedera’s DevOps team to finalize a plan for operating its Node. A Member will be required to manage its Node independently no later than twelve (12) months after joining the Council. If it appears that the Member’s Node will not be operational within 90 days after joining the Council, Hedera may set up a Node on behalf of such Member and such Member will accept shared control with Hedera of such Node (a Node under such shared control, a “Transitional Node.”) Hedera, and not the Member, will be responsible for the costs or IT support relating to the management of a Transitional Node. During any period in which a Member has a Transitional Node, the Member will not be eligible to receive any of the fees and/or payments described in paragraph B.5 below.
View Source

Related to Node Set-up

  • OGS Centralized Contract Terms and Conditions have been renumbered as depicted in the following chart: Current Amended Section Title 4.25 4.26 Severability 4.26 4.27 Entire Agreement

  • Compressed Work Week The Company and Union recognize the concept of the compressed work week. It is further understood that the compressed work week conditions will apply only to those departments that are on the compressed work week.

  • Shared Transport The Shared Transport Network Element (“Shared Transport”) provides the collective interoffice transmission facilities shared by various Carriers (including Qwest) between end-office switches and between end-office switches and local tandem switches within the Local Calling Area. Shared Transport uses the existing routing tables resident in Qwest switches to carry the End User Customer’s originating and terminating local/extended area service interoffice Local traffic on the Qwest interoffice message trunk network. CLEC traffic will be carried on the same transmission facilities between end- office switches, between end-office switches and tandem switches and between tandem switches on the same network facilities that Qwest uses for its own traffic. Shared Transport does not include use of tandem switches or transport between tandem switches and end-office switches for Local Calls that originate from end users served by non- Qwest Telecommunications Carriers (“Carrier(s)”) which terminate to QLSP End Users.

  • Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks. 6.1.1 As used in this Section 6, “Traffic Rate” means the applicable Reciprocal Compensation Traffic rate, Measured Internet Traffic rate, intrastate Switched Exchange Access Service rate, interstate Switched Exchange Access Service rate, or intrastate/interstate Tandem Transit Traffic rate, as provided in the Pricing Attachment, an applicable Tariff, or, for Measured Internet Traffic, the FCC Internet Order. 6.1.2 If the originating Party passes CPN on ninety-five percent (95%) or more of its calls, the receiving Party shall ▇▇▇▇ the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. For any remaining (up to 5%) calls without CPN information, the receiving Party shall ▇▇▇▇ the originating Party for such traffic at the Traffic Rate applicable to each relevant minute of traffic, in direct proportion to the minutes of use of calls passed with CPN information. 6.1.3 If the originating Party passes CPN on less than ninety-five percent (95%) of its calls and the originating Party chooses to combine Reciprocal Compensation Traffic and Toll Traffic on the same trunk group, the receiving Party shall ▇▇▇▇ the higher of its interstate Switched Exchange Access Service rates or its intrastate Switched Exchange Access Services rates for all traffic that is passed without CPN, unless the Parties agree that other rates should apply to such traffic. 6.2 At such time as a receiving Party has the capability, on an automated basis, to use such CPN to classify traffic delivered over Interconnection Trunks by the other Party by Traffic Rate type (e.g., Reciprocal Compensation Traffic/Measured Internet Traffic, intrastate Switched Exchange Access Service, interstate Switched Exchange Access Service, or intrastate/interstate Tandem Transit Traffic), such receiving Party shall ▇▇▇▇ the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. If the receiving Party lacks the capability, on an automated basis, to use CPN information on an automated basis to classify traffic delivered by the other Party by Traffic Rate type, the originating Party will supply Traffic Factor 1 and Traffic Factor

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.