Retransmission Control Sample Clauses

Retransmission Control. ‌ The goal of this test is to experimentally validate the behaviour of the retransmission control policy. In order to do so, we use the scenario illustrated in Figure 6. The normal DIF is configured with a QoS cube that enforces reliable in-order delivery of the SDUs carried by the flows. System 3 contains the rina-echo-time server application instance, and System 1 contains the rina-echo-time client application instance, both running in ping mode. In System 2 we configure the Linux netem tool to randomly discard packets from the eth2 Ethernet interface, with a probability of 0.25 (that is one out of four packets). VLAN 100 VLAN 110 System 1 System 2 Randomly loses 25% System 3 of packets When we examine the kernel logs on System 1 right after allocating a flow, we can see that an EFCP instance supporting a reliable flow was created. It has been configured with a retransmission timer (Tr) of 120 ms and a retransmission timeout of 600 ms (this means that EFCP will wait up to 120 ms to receive the acknowledgment of a PDU before retransmitting it). [ [ [ [ [ [ [ [ 627.701299] rina-dtcp(DBG): DTCP SV initialized with dtcp_conf: 627.706672] rina-dtcp(DBG): 627.710705] rina-dtcp(DBG): 627.810601] rina-dtcp(DBG): 627.815581] rina-dtcp(DBG): 627.819728] rina-dtcp(DBG): data_retransmit_max: 5 sndr_credit: snd_rt_wind_edge: rcvr_credit: rcvr_rt_wind_edge: 50 50 50 50 627.827878] rina-dtcp(DBG): Instance ffff8800eac3dd00 created successfully 627.869869] rina-rtimer(DBG): Timer ffff88003003bd20 created [ [ [ [ 627.874314] rina-efcp(DBG): DT SV initialized with: 627.880844] rina-efcp(DBG): 627.884794] rina-efcp(DBG): MFPS: 10000, MFSS: 10000 A: 30, R: 600, TR: 120 627.888402] rina-efcp(DBG): Connection created (Source address 16,Destination address 18, Destination cep-id 0, Source cep-id 0) The behaviour of the retransmission control policy can also be observed by analyzing the output pro- vided by the rina-echo-time application run in client mode. This application shows the round- trip time (RTT) it sees for every packet it sends. The average RTT is about 37 ms, but there are packets that experience a much longer RTT, due to retransmissions. Some packets have RTTs in the order of 160 ms, because they have been retransmitted once (remember that the retransmission timer is configured to 120 ms); others have RTTs in the order of 270 ms, due to the fact that they have been retransmitted twice. SDU size = 20, seq = 5, RTT = 37ms SDU size = 20, seq = 6, RTT = 42ms SDU size ...
AutoNDA by SimpleDocs

Related to Retransmission Control

  • Data Transmission Control Except as necessary for the provision of the Cloud Services in accordance with the Agreement, Personal Data must not be read, copied, modified or removed without authorization during transfer. Where data carriers are physically transported, adequate measures are implemented at SAP to provide the agreed-upon service levels (for example, encryption and lead-lined containers).

  • Transmission encryption All data transmissions of County PHI or PI outside the secure internal network must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as AES. Encryption can be end to end at the network level, or the data files containing PHI can be encrypted. This requirement pertains to any type of PHI or PI in motion such as website access, file transfer, and E-Mail.

  • Data Transmission The procedures for transmitting load obligation data to PJM for DS Supplier’s DS Load shall be as set forth by PJM.

  • Transmission The Custodian and the Fund shall comply with SWIFT’s authentication procedures. The Custodian will act on FT Instructions received via SWIFT provided the instruction is authenticated by the SWIFT system. § Written Instructions. Instructions may be transmitted in an original writing that bears the manual signature of an Authorized Person(s).

  • Transmission Charge The cost for transporting electricity from the generation source to your electric distribution company. For most electric customers who select a new supplier, transmission costs will be included in the charges from your new supplier. The Federal Energy Regulatory Commission regulates retail transmission prices and services. This charge will vary with your source of supply.

  • Loop Transmission Types 3.1 Subject to the conditions set forth in Section 1 of this Attachment, Verizon shall allow CBB to access Loops unbundled from local switching and local transport, in accordance with this Section 3 and the rates and charges provided in the Pricing Attachment. Verizon shall allow CBB access to Loops in accordance with, but only to extent required by, Applicable Law. The available Loop types are as set forth below:

  • Interconnection 2.1 This section applies to linking with suppliers providing public telecommunications transport networks or services in order to allow the users of one supplier to communicate with users of another supplier and to access services provided by another supplier, where specific commitments are undertaken.

  • NYISO and Connecting Transmission Owner Obligations Connecting Transmission Owner and NYISO shall cause the New York State Transmission System and the Connecting Transmission Owner’s Attachment Facilities to be operated, maintained and controlled in a safe and reliable manner in accordance with this Agreement and the NYISO Tariffs. Connecting Transmission Owner and NYISO may provide operating instructions to Developer consistent with this Agreement, NYISO procedures and Connecting Transmission Owner’s operating protocols and procedures as they may change from time to time. Connecting Transmission Owner and NYISO will consider changes to their respective operating protocols and procedures proposed by Developer.

  • 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 Xxxxx’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.

  • Information Transmission The Provider, on behalf of itself and its respective Subsidiaries, shall use commercially reasonable efforts to provide or make available, or cause to be provided or made available, to the Recipient, in accordance with Section 6.1 of the Separation and Distribution Agreement, any Information received or computed by the Provider for the benefit of the Recipient concerning the relevant Service during the Service Period; provided, however, that, except as otherwise agreed to in writing by the Parties (a) the Provider shall not have any obligation to provide, or cause to be provided, Information in any non-standard format, (b) the Provider and its Subsidiaries shall be reimbursed for their reasonable costs in accordance with Section 6.3 of the Separation and Distribution Agreement for creating, gathering, copying, transporting and otherwise providing such Information, and (c) the Provider shall use commercially reasonable efforts to maintain any such Information in accordance with Section 6.4 of the Separation and Distribution Agreement.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!