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

  • Transmission Control In-transit: We make HTTPS encryption (also referred to as SSL or TLS) available on every one of its login interfaces and for free on every customer site hosted on the HubSpot products. Our HTTPS implementation uses industry standard algorithms and certificates. At-rest: We store user passwords following policies that follow industry standard practices for security. We have implemented technologies to ensure that stored data is encrypted at rest.

  • 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).

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

  • Transmission Service Point-To-Point Transmission Service provided under Part II of the Tariff on a firm and non-firm basis.

  • Merchant Transmission Facilities “Controllable A.C. Merchant Transmission Facilities” shall mean transmission facilities that (1) employ technology which Transmission Provider reviews and verifies will permit control of the amount and/or direction of power flow on such facilities to such extent as to effectively enable the controllable facilities to be operated as if they were direct current transmission facilities, and

  • 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 Facilities The NTO owns certain transmission facilities over which the ISO will have day-to-day operational control to maintain these facilities in a reliable state, as defined by the Reliability Rules and all other applicable reliability rules, standards and criteria, and in accordance with the ISO Tariffs, ISO Related Agreements and ISO Procedures (“ISO Operational Control”). These NTO facilities shall be classified as “NTO Transmission Facilities Under ISO Operational Control,” and are listed in Appendix A-1 of this Agreement. The NTO also will be responsible for providing notification to the ISO with respect to actions related to certain other transmission facilities. These facilities shall be classified as “NTO Transmission Facilities Requiring ISO Notification,” and are listed in Appendix A-2 of this Agreement. Transmission facilities may be added to, or deleted from, the lists of facilities provided in Appendices A-1 and A-2 herein by mutual written agreement of the ISO and the NTO owning and controlling such facilities. Currently listed facilities will be posted on the ISO’s OASIS.

  • Transmission System The facilities controlled or operated by the Transmission Provider within the PJM Region that are used to provide transmission service under Part II and Part III of the Tariff.

  • 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).

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