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). Client app Server app test1.IRATI “Normal.DIF” 16 test2.IRATI 17 test3.IRATI 18 Shim DIF over 802.1Q, “100” Shim DIF over 802.1Q “110” eth1 VLAN 100 eth1 eth2 VLAN 110 eth1 System 1 System 2 Randomly loses 25% System 3 of packets Figure 6: Scenario for the validation of the retransmission control functionality 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 (remem...
Sample 1
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). Measures: • Personal Data in transfer over SAP internal networks is protected according to SAP Security Policy. • When data is transferred between SAP and its customers, the protection measures for the transferred Personal Data are mutually agreed upon and made part of the relevant agreement. This applies to both physical and network based data transfer. In any case, the Customer assumes responsibility for any data transfer once it is outside of SAP-controlled systems (e.g. data being transmitted outside the firewall of the SAP Data Center).

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

  • Interoffice Transmission Facilities BellSouth shall provide nondiscriminatory access, in accordance with FCC Rule 51.311 and Section 251(c)(3) of the Act, to interoffice transmission facilities on an unbundled basis to <<customer_name>> for the provision of a telecommunications service.

  • 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:

  • No Transmission Service The execution of this LGIA does not constitute a request for, nor the provision of, any transmission service under the CAISO Tariff, and does not convey any right to deliver electricity to any specific customer or point of delivery.

  • Interconnection 2.1.10 Startup Testing and Commissioning

  • 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 CBB to Verizon, CBB, at CBB’s own expense, shall:

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