T10/03-229r1 SAS-1.1 Transport layer retries ladder diagrams

Size: px
Start display at page:

Download "T10/03-229r1 SAS-1.1 Transport layer retries ladder diagrams"

Transcription

1 To: T10 Technical Committee From: Jim Jones, Quantum and Rob Elliott, HP Date: 11 August 2003 Subject: T10/03-229r1 SAS-1.1 Transport Layer Retries ladder diagrams Revision History Revision 1 (11 August 2003) second revision Revision 0 (25 June 2003) first revision Related Documents sas-r05 - Serial Attached SCSI revision r2 - SAS-1.1 Transport Layer Retries Overview This presents ladder diagrams for all the error recovery cases in Conventions: DATA means resend the DATA frame For certain frame types, the RETRANSMIT bit is set to 1 when retransmitting. 1 of 28

2 RESPONSE Frame NAK Received RESPONSE NAK NAK received for RESPONSE Frame - resend RESPONSE Frame with RETRANSMIT=1 RESPONSE Tag is not ready for reuse (this could still be lost) The RETRANSMIT bit is not strictly necessary here; it doesn t help the initiator. It helps debugging with logic analyzers. 2 of 28

3 RESPONSE Frame Lost RESPONSE /NAK timeout (/NAK TIMEOUT) resend RESPONSE Frame with RETRANSMIT=1 _ACCEPT but ignore since RETRANSMIT=1 Tag is not ready for reuse (this could still be lost) RESPONSE 3 of 28

4 RESPONSE Frame NAK Lost RESPONSE NAK /NAK timeout (/NAK TIMEOUT) resend RESPONSE Frame with RETRANSMIT=1 _ACCEPT RESPONSE Tag is not ready for reuse (this could still be lost) 4 of 28

5 RESPONSE Frame Not Delivered RESPONSE /NAK timeout (/NAK TIMEOUT) resend RESPONSE Frame with RETRANSMIT=1 _ACCEPT RESPONSE Tag is not ready for reuse (this could still be lost) 5 of 28

6 COMMAND Frame NAK Received Same as in SAS-1 COMMAND NAK received for COMMAND Frame - resend COMMAND Frame NAK COMMAND 6 of 28

7 COMMAND Frame lost (command running, but target hasn t sent a frame yet). If first burst is enabled, the initiator can start sending the first burst data after running query task,. Same as in SAS-1 COMMAND /NAK timeout (/NAK TIMEOUT) _ACCEPT QUERY TASK Command active at target RESPONSE of FUNCTION SUCCEEDED 7 of 28

8 COMMAND Frame Lost, target processes command returning RESPONSE, XFER_RDY, or DATA The initiator still runs (/NAK Timeout) and has to participate in a new connection at some point. These pictures just show what the transport layer deals with. COMMAND Command completed successfully RESPONSE Tag is not ready for reuse (this could still be lost) Write COMMAND Command active at target XFER_RDY Read COMMAND Command active at target DATA 8 of 28

9 COMMAND Frame NAK Lost (command not running) COMMAND NAK /NAK timeout (/NAK TIMEOUT) _ACCEPT QUERY TASK Command not active at target - initiator can resend the command RESPONSE of FUNCTION COMPLETE COMMAND 9 of 28

10 COMMAND Frame Not Delivered COMMAND /NAK timeout (/NAK TIMEOUT) _ACCEPT QUERY TASK Command not active at target - initiator can resend the command RESPONSE of FUNCTION COMPLETE COMMAND 10 of 28

11 Task Frame NAK Received Same as in SAS-1 TASK NAK received for TASK Frame - resend TASK Frame NAK TASK 11 of 28

12 TASK Frame lost - resend Same as in SAS-1 TASK /NAK timeout (/NAK TIMEOUT) Initiator can resend the TASK Frame _ACCEPT TASK 12 of 28

13 TASK Frame Lost, target processes TASK Frame returning RESPONSE The initiator still runs (/NAK Timeout). TASK Task Management Function completed successfully RESPONSE Tag is not ready for reuse (this could still be lost) /NAK timeout (/NAK TIMEOUT) 13 of 28

14 TASK Frame NAK Lost Same as in SAS-1 TASK NAK /NAK timeout (/NAK TIMEOUT) _ACCEPT Initiator can resend the TASK Frame TASK 14 of 28

15 XFER_RDY Frame NAK Received SAS-1.0: target aborts command XFER_RDY RO=000, TPTT=123, Retry DATA Frames=1 NAK NAK received for XFER_RDY Frame - resend XFER_RDY Frame with RETRANSMIT=1 and new TPTT XFER_RDY RO=000, TPTT=124, Retry DATA Frames=1 15 of 28

16 XFER_RDY Frame Lost SAS-1.0: target aborts command, Retry DATA Frames=1 XFER_RDY RO=000, TPTT=123, Retry DATA Frames=1 DATA RO=000, TPTT=123 DATA RO=100, TPTT=123 DATA RO=200, TPTT=123 DATA RO=300, TPTT=123 DATA RO=400, TPTT=123 (000) (100) (200) (300) (400) Data ed but discarded /NAK timeout (/NAK TIMEOUT) resend XFER_RDY Frame with RETRANSMIT=1 and a new TPTT _ACCEPT Could still send more data for TPTT=123; ignored by the target. No more sent once TPTT=124 is used XFER_RDY RO=000, TPTT=124, Retry DATA Frames=1 DATA RO=000, TPTT=124 DATA RO=100, TPTT=124 DATA RO=200, TPTT=124 DATA RO=300, TPTT=124 DATA RO=400, TPTT=124 Initiator must stop sending frames for a tag after it s the RESPONSE frame Target can reuse TPTT=123 when data for TPTT=124 is received (000) (100) (200) (300) (400) 16 of 28

17 XFER_RDY Frame NAK Lost XFER_RDY RO=000, TPTT=123, Retry DATA Frames=1 NAK /NAK timeout (/NAK TIMEOUT) resend XFER_RDY Frame with RETRANSMIT=1 and new TPTT _ACCEPT XFER_RDY RO=000, TPTT=124, Retry DATA Frames=1 17 of 28

18 XFER_RDY Frame Not Delivered XFER_RDY RO=000, TPTT=123, Retry DATA Frames=1 /NAK timeout (/NAK TIMEOUT) resend XFER_RDY Frame with RETRANSMIT=1 and new TPTT _ACCEPT XFER_RDY RO=000, TPTT=124, Retry DATA Frames=1 18 of 28

19 Write DATA Frame NAK Received XFER_RDY RO=000, TPTT=123, Retry DATA Frames=1 DATA RO=000, TPTT=123 DATA RO=100, TPTT=123 DATA RO=200, TPTT=123 DATA RO=300, TPTT=123 DATA RO=400, TPTT=123 Go back to the beginning of XFER_RDY. No need to close connection (000) (100) (200) NAK (300) (400) DATA RO=000, TPTT=123, Changing Data Pointer=1 DATA RO=100, TPTT=123 DATA RO=200, TPTT=123 DATA RO=300, TPTT=123 DATA RO=400, TPTT=123 (000) (100) (200) (300) (400) 19 of 28

20 Write DATA Frame Lost XFER_RDY RO=000, TPTT=123, Retry DATA Frames=1 DATA RO=000, TPTT=123 DATA RO=100, TPTT=123 DATA RO=200, TPTT=123 DATA RO=300, TPTT=123 DATA RO=400, TPTT=123 (000) (100) (200) (300) (400) /NAK timeout (/NAK TIMEOUT) Go back to the beginning of XFER_RDY. DATA RO=000, TPTT=123, Changing Data Pointer = 1 DATA RO=100, TPTT=123 DATA RO=200, TPTT=123 DATA RO=300, TPTT=123 DATA RO=400, TPTT=123 _ACCEPT (000) (100) (200) (300) (400) 20 of 28

21 Write DATA Frame NAK Lost XFER_RDY RO=000, TPTT=123, Retry DATA Frames=1 DATA RO=000, TPTT=123 DATA RO=100, TPTT=123 DATA RO=200, TPTT=123 DATA RO=300, TPTT=123 DATA RO=400, TPTT=123 /NAK timeout (/NAK TIMEOUT) Go back to the beginning of XFER_RDY. DATA RO=000, TPTT=123, Changing Data Pointer = 1 DATA RO=100, TPTT=123 DATA RO=200, TPTT=123 DATA RO=300, TPTT=123 DATA RO=400, TPTT=123 (000) (100) (200) NAK (300) (400) _ACCEPT (000) (100) (200) (300) (400) DATA 400 is unexpected due to the gap, and shall be discarded by the target transport layer even though the link layer s it. Changing Data Pointer=1 signals that the target can go back and start accepting data again. It might internally discard the new writes up to the gap, or rewrite. 21 of 28

22 Write DATA Frame Not Delivered XFER_RDY RO=000, TPTT=123, Retry DATA Frames=1 DATA RO=000, TPTT=123 DATA RO=100, TPTT=123 DATA RO=200, TPTT=123 DATA RO=300, TPTT=123 DATA RO=400, TPTT=123 /NAK timeout (/NAK TIMEOUT) Go back to the beginning of XFER_RDY. (000) (100) (200) (400) DATA 400 is unexpected due to the gap, and shall be discarded by the target transport layer even though the link layer s it. DATA RO=000, TPTT=123, Changing Data Pointer = 1 DATA RO=100, TPTT=123 DATA RO=200, TPTT=123 DATA RO=300, TPTT=123 DATA RO=400, TPTT=123 _ACCEPT (000) (100) (200) Changing Data Pointer=1 signals that the target can go back and start accepting data again. It might internally discard the new writes up to the gap, or rewrite. (300) (400) 22 of 28

23 Write DATA Frame Lost crossing RESPONSE XFER_RDY RO=000, TPTT=123, Retry DATA Frames=1 DATA RO=000, TPTT=123 DATA RO=100, TPTT=123 DATA RO=200, TPTT=123 DATA RO=300, TPTT=123 DATA RO=400, TPTT=123 (000) (100) (200) (300) (400) Target cannot reuse TPTT=123 yet Command is done, but an was apparently missed RESPONSE /NAK timeout (/NAK TIMEOUT) Initiator should stop transmitting data on receipt of RESPONSE. Target can reuse TPTT=123 after receipt of next command. 23 of 28

24 Write DATA Frame Lost crossing XFER_RDY XFER_RDY RO=000, TPTT=123, Retry DATA Frames=1 DATA RO=000, TPTT=123 DATA RO=100, TPTT=123 DATA RO=200, TPTT=123 DATA RO=300, TPTT=123 DATA RO=400, TPTT=123 (000) (100) (200) (300) The XFER_RDY burst is done, but an was apparently missed because another XFER_RDY just arrived (400) Target cannot reuse TPTT=123 yet XFER_RDY RO=500, TPTT=124, Retry DATA Frames = 1 /NAK timeout (/NAK TIMEOUT) Initiator must stop servicing the old XFER_RDY burst before sending data frames for TPTT=124. _ACCEPT DATA RO=500, TPTT=124 DATA RO=600, TPTT=124 Target can now reuse TPTT=123 when data frames for TPTT=124 arrive DATA RO=700, TPTT=124 DATA RO=800, TPTT=124 DATA RO=900, TPTT=124 (500) (600) (700) (800) (900) 24 of 28

25 Read DATA Frame NAK Received DATA RO=000 DATA RO=100 Although DATA 400 is ed, the transport layer is not happy with the RO gap. For this logical unit, it does not abort the command, however; it could discard DATA 400 When DATA with Changing Data Pointer=1 arrives, the initiator resumes accepting read DATA at the correct destination (000) (100) (200) NAK (300) (400) (000) (100) (200) (300) (400) DATA RO=200 DATA RO=300 DATA RO=400 Need to resend data from any previous /NAK balance point DATA RO=000, Changing Data Pointer=1 DATA RO=100 DATA RO=200 DATA RO=300 DATA RO= of 28

26 Read DATA Frame Lost DATA RO=000 DATA RO=100 (000) (100) (200) DATA RO=200 DATA RO=300 DATA RO=400 (300) (400) /NAK timeout (/NAK TIMEOUT) _ACCEPT Got 4 s, but target doesn t know what was lost (an or NAK, or which one since the last /NAK balance point). Must restart from last /NAK balance state (RO=000 here). Initiator honors Changing Data Pointer=1 from this logical unit (000) (100) (200) DATA RO=000, Changing Data Pointer=1 DATA RO=100 DATA RO=200 DATA RO=300 DATA RO=400 (300) (400) 26 of 28

27 Read DATA Frame NAK Lost DATA RO=000 DATA RO=100 (000) (100) (200) DATA RO=200 DATA RO=300 DATA RO=400 NAK (300) (400) /NAK timeout (/NAK TIMEOUT) _ACCEPT Got 4 s, but don t know what was lost. Must restart from last /NAK balance state (RO=000 here). Initiator honors Changing Data Pointer=1 from this logical unit (000) (100) (200) DATA RO=000, Changing Data Pointer=1 DATA RO=100 DATA RO=200 DATA RO=300 DATA RO=400 (300) (400) 27 of 28

28 Read DATA Frame Not Delivered Initiator shall not abort the command just because it detected an RO gap. It could discard all the data after the gap. No need to start NAKing. (000) (100) (200) (400) DATA RO=000 DATA RO=100 DATA RO=200 DATA RO=300 DATA RO=400 /NAK timeout (/NAK TIMEOUT) _ACCEPT Got 4 s, but don t know what was lost. Must restart from last /NAK balance state (RO=000 here). Changing Data Pointer indicates the initiator can modify its data pointers and resume accepting data (000) (100) (200) DATA RO=000, Changing Data Pointer=1 DATA RO=100 DATA RO=200 DATA RO=300 DATA RO=400 (300) (400) 28 of 28

T10/03-229r0 SAS-1.1 Transport layer retries ladder diagrams

T10/03-229r0 SAS-1.1 Transport layer retries ladder diagrams To: T10 Technical Committee From: Jim Jones, Quantum (jim.jones@quantum.com) and Rob Elliott, HP (elliott@hp.com) Date: 25 June 2003 Subject: T10/03-229r0 SAS-1.1 Transport Layer Retries ladder diagrams

More information

T10/03-186r2 SAS-1.1 Transport layer retries

T10/03-186r2 SAS-1.1 Transport layer retries To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) and Jim Jones, Quantum (jim.jones@quantum.com) Date: 28 July 2003 Subject: T10/03-186r1 SAS-1.1 Transport layer retries T10/03-186r2 SAS-1.1

More information

03-186r5 SAS-1.1 Transport layer retries 13 January 2004

03-186r5 SAS-1.1 Transport layer retries 13 January 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 13 January 2004 Subject: 03-186r5 SAS-1.1 Transport layer retries Revision history Revision 0 (6 May 2003) first revision Revision

More information

03-186r3r3 SAS-1.1 Transport layer retries 25 October 2003

03-186r3r3 SAS-1.1 Transport layer retries 25 October 2003 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 25 October 2003 Subject: 03-186r3r3 SAS-1.1 Transport layer retries Revision history Revision 0 (6 May 2003) first revision Revision

More information

12 January r1 SAS2: ST_TTS retransmitted DATA frames

12 January r1 SAS2: ST_TTS retransmitted DATA frames To: T10 Technical Committee From: Bob Sheffield (Robert.L.Sheffield@intel.com) Date: 12 January 2007 Subject: 06-371r1 SAS2: ST_TTS retransmitted DATA frames Revision history Revision 0 (20 July 2006)

More information

SERIAL ATTACHED SCSI (SAS) CONSORTIUM

SERIAL ATTACHED SCSI (SAS) CONSORTIUM SERIAL ATTACHED SCSI (SAS) CONSORTIUM Clause 8 SAS SPL Target Error Handling Test Suite Version0.3 Technical Document Last Updated: 6 September 2011 Serial Attached SCSI Consortium 121 Technology Drive,

More information

Item 2) In clause PL_OC2:Overall_Control state frame transmission cancellations: change the text to be as follows:

Item 2) In clause PL_OC2:Overall_Control state frame transmission cancellations: change the text to be as follows: a Maxtor Corporation 500 McCarthy Boulevard Milpitas, CA 95035 USA To: T10 SAS Protocol Working Group Contact: Mark Evans Phone: 408-894-5310 Email: mark_evans@maxtor.com Date: 23 February 2004 Subject:

More information

17 March r1 SAM-4 SAS-2 QUERY UNIT ATTENTION task management function

17 March r1 SAM-4 SAS-2 QUERY UNIT ATTENTION task management function To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 17 March 2007 Subject: 07-067r1 SAM-4 SAS-2 QUERY UNIT ATTENTION task management function Revision history Revision 0 (13 February

More information

9 January r0 SAS-2 SPC-4 Enabling and disabling Transport Layer Retries

9 January r0 SAS-2 SPC-4 Enabling and disabling Transport Layer Retries To: T10 Technical Committee From: Chris Martin (chris.martin@hp.com) and Rob Elliott, HP (elliott@hp.com) Date: 9 January 2007 Subject: 07-027r0 SAS-2 SPC-4 Enabling and disabling Transport Layer Retries

More information

04-340r1 SAS-1.1 OPEN_REJECT BAD DESTINATION handling 24 December 2004

04-340r1 SAS-1.1 OPEN_REJECT BAD DESTINATION handling 24 December 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 24 December 2004 Subject: 04-340r1 SAS-1.1 OPEN_REJECT BAD DESTINATION handling Revision history Revision 0 (18 October 2004) First

More information

04-340r0 SAS-1.1 OPEN_REJECT BAD DESTINATION handling 18 October 2004

04-340r0 SAS-1.1 OPEN_REJECT BAD DESTINATION handling 18 October 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 18 October 2004 Subject: 04-340r0 SAS-1.1 OPEN_REJECT BAD DESTINATION handling Revision history Revision 0 (18 October 2004) First

More information

17 March r1 SAM-4 SAS-2 QUERY TASK SET task management function

17 March r1 SAM-4 SAS-2 QUERY TASK SET task management function 17 March 2007 07-066r1 SAM-4 SAS-2 QUERY ASK SE task management function o: 10 echnical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 17 March 2007 Subject: 07-066r1 SAM-4 SAS-2 QUERY ASK SE task

More information

T10/02-230r1. Maxtor Corporation 500 McCarthy Boulevard Milpitas, CA USA

T10/02-230r1. Maxtor Corporation 500 McCarthy Boulevard Milpitas, CA USA Maxtor Corporation 500 McCarthy Boulevard Milpitas, CA 95035 USA To: Serial Attached SCSI Protocol Working Group From: Mark Evans Phone: 408-894-5310 Email: mark_evans@maxtor.com Date: 08 July 2002 Subject:

More information

Revision 6: Red text Incorporate comments from January 5, 2004 conference call. Minor wording changes.

Revision 6: Red text Incorporate comments from January 5, 2004 conference call. Minor wording changes. To: INCITS T10 Committee From: Susan Gray, Quantum Date: January, 5, 2004 Document Number: T10/03-355r6 Subject: ADT Section 4.7.1.3 1 Revision History Revision 6: Red text Incorporate comments from January

More information

6 June r0 SAM-4 SCSI Initiator Port and Target Port capabilities attributes

6 June r0 SAM-4 SCSI Initiator Port and Target Port capabilities attributes 6 June 2007 07-263r0 SAM-4 SCSI Initiator Port and Target Port capabilities attributes To: T10 Technical Committee From: Rob Elliott (elliott@hp.com) Date: 6 June 2007 Subject: 07-263r0 SAM-4 SCSI Initiator

More information

04-372r0 SAM-4 SPC-3 SAS-1.1 I_T NEXUS LOSS task management function 5 November 2004

04-372r0 SAM-4 SPC-3 SAS-1.1 I_T NEXUS LOSS task management function 5 November 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 5 November 2004 Subject: 04-372r0 SAM-4 SPC-3 SAS-1.1 I_T NEXUS LOSS task management function Revision history Revision 0 (5 November

More information

ADT Frame Format Notes (Paul Suhler) ADI ADT Frame Format Proposal (Rod Wideman)

ADT Frame Format Notes (Paul Suhler) ADI ADT Frame Format Proposal (Rod Wideman) To: INCITS T10 Membership From: Paul Entzel, Quantum Date: 11 November 2002 Document: T10/02-329r2 Subject: Proposed frame format for ADT 1 Related Documents T10/02-233r0 T10/02-274r0 ADT Frame Format

More information

04-172r1 SAS-2 More counters 11 September 2005

04-172r1 SAS-2 More counters 11 September 2005 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 11 September 2005 Subject: 04-172r1 SAS-2 More ers Revision history Revision 0 (21 June 2004) First revision Revision 1 (11 September

More information

04-372r1 SAM-4 SPC-4 SAS-1.1 I_T NEXUS RESET task management function 13 November 2004

04-372r1 SAM-4 SPC-4 SAS-1.1 I_T NEXUS RESET task management function 13 November 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 13 November 2004 Subject: 04-372r1 SAM-4 SPC-4 SAS-1.1 I_T NEXUS RESET task management function Revision history Revision 0 (5 November

More information

2 May r2 SAS-2 WWN-based Attached Device Name for SATA

2 May r2 SAS-2 WWN-based Attached Device Name for SATA To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 2 May 2007 Subject: 06-476r2 SAS-2 WWN-based Attached Device Name for SATA Revision history Revision 0 (31 October 2006) First revision

More information

7 April r0 SAS-2 SMP function result for incomplete descriptor lists

7 April r0 SAS-2 SMP function result for incomplete descriptor lists 7 April 2007 07-176r0 SAS-2 SMP function result for incomplete descriptor lists To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 7 April 2007 Subject: 07-176r0 SAS-2 SMP function

More information

04-247r0 SAS-1.1 XL6 and idle dwords 8 September 2004

04-247r0 SAS-1.1 XL6 and idle dwords 8 September 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 8 September 2004 Subject: 04-247r0 SAS-1.1 XL6 and idle dwords Revision history Revision 0 (8 September 2004) First revision Related

More information

03-346r2 SAS-1.1 Pathway recovery priority corrections 3 November 2003

03-346r2 SAS-1.1 Pathway recovery priority corrections 3 November 2003 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 3 November 2003 Subject: 03-346r2 SAS-1.1 Pathway recovery priority corrections Revision history Revision 0 (22 October 2003) First

More information

Table 21. OOB signal transmitter requirements Idle time minimum. maximum 175 ns

Table 21. OOB signal transmitter requirements Idle time minimum. maximum 175 ns To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 28 June 2002 Subject: T10/02-198r4 SAS OOB timing T10/02-198r4 SAS OOB timing Revision History Revision 0 (20 May 2002) first revision

More information

8 January r3 SAS-2 More counters

8 January r3 SAS-2 More counters 8 January 2006 04-172r3 SAS-2 More ers To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 8 January 2006 Subject: 04-172r3 SAS-2 More ers Revision history Revision 0 (21 June 2004)

More information

Reliable Transport : Fundamentals of Computer Networks Bill Nace

Reliable Transport : Fundamentals of Computer Networks Bill Nace Reliable Transport 14-740: Fundamentals of Computer Networks Bill Nace Material from Computer Networking: A Top Down Approach, 6 th edition. J.F. Kurose and K.W. Ross Administration Stuff is due HW #1

More information

22 March r1 FCP-4 QUERY TASK task management function

22 March r1 FCP-4 QUERY TASK task management function To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 22 March 2007 Subject: 07-072r1 FCP-4 QUERY TASK task management function Revision history Revision 0 (14 February 2007) First revision

More information

Overview The OOB timing requirements need to be more precise, listing the transmit burst time and specifying receiver tolerances.

Overview The OOB timing requirements need to be more precise, listing the transmit burst time and specifying receiver tolerances. To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 19 June 2002 Subject: T10/02-198r3 SAS OOB timing T10/02-198r3 SAS OOB timing Revision History Revision 0 (20 May 2002) first revision

More information

Serial Attached SCSI Comparison to Fibre Channel with FCP

Serial Attached SCSI Comparison to Fibre Channel with FCP Serial Attached SCSI Comparison to Fibre Channel with FCP by Rob Elliott HP Industry Standard Servers Server Storage Advanced Technology elliott@hp.com http://www.hp.com 30 September 2003 Notice These

More information

The flow of data must not be allowed to overwhelm the receiver

The flow of data must not be allowed to overwhelm the receiver Data Link Layer: Flow Control and Error Control Lecture8 Flow Control Flow and Error Control Flow control refers to a set of procedures used to restrict the amount of data that the sender can send before

More information

04-352r0 SAS-1.1 Phy test functions for SMP 29 October 2004

04-352r0 SAS-1.1 Phy test functions for SMP 29 October 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 29 October 2004 Subject: 04-352r0 SAS-1.1 Phy test functions for SMP Revision history Revision 0 (29 October 2004) First revision

More information

10.1 REVIEW QUESTIONS

10.1 REVIEW QUESTIONS CHAPTER 10 Data Link Control 10.1 REVIEW QUESTIONS 1. Transmission means to put a signal on a line. Communication is a meaningful and orderly relationship between devices that send and receive data. 3.

More information

04-075r0 SBC-2 Obsolete more features 27 February 2004

04-075r0 SBC-2 Obsolete more features 27 February 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 27 February 200 Subject: 0-075r0 SBC-2 Obsolete more features Revision history Revision 0 (27 February 200) First revision Related

More information

TCP : Fundamentals of Computer Networks Bill Nace

TCP : Fundamentals of Computer Networks Bill Nace TCP 14-740: Fundamentals of Computer Networks Bill Nace Material from Computer Networking: A Top Down Approach, 6 th edition. J.F. Kurose and K.W. Ross Administrivia Lab #1 due now! Reminder: Paper Review

More information

Table 21. OOB signal transmitter requirements Idle time minimum. maximum 175 ns

Table 21. OOB signal transmitter requirements Idle time minimum. maximum 175 ns To: T10 Technical Committee From: Rob Elliott (elliott@hp.com) and Thomas Grieff (thomas.grieff@hp.com), HP Date: 18 July 2002 Subject: T10/02-198r6 SAS OOB timing T10/02-198r6 SAS OOB timing Revision

More information

1 Overview. 2 Storage device LBA translation error. T10/ revision 1

1 Overview. 2 Storage device LBA translation error. T10/ revision 1 Date: June 30, 2003 To: T10 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: End-to-End Error Cases 1 Overview As part of the discussion on end-to-end data protection the question of what errors

More information

file:///c:/users/hpguo/dropbox/website/teaching/fall 2017/CS4470/H...

file:///c:/users/hpguo/dropbox/website/teaching/fall 2017/CS4470/H... 1 of 9 11/26/2017, 11:28 AM Homework 3 solutions 1. A window holds bytes 2001 to 5000. The next byte to be sent is 3001. Draw a figure to show the situation of the window after the following two events:

More information

Overview of Store-and-Forward Expander Device Operation

Overview of Store-and-Forward Expander Device Operation Overview of Store-and-Forward Expander Device Operation Bob Sheffield Storage 11 September 2006 1 Objectives General concept Basic elements Connections SSP flow model STP flow model SMP extensions SSP

More information

Revision history Revision 0 (9 October 2002) first revision Revision 1 (6 November 2002) Incorporated comments from CAP WG.

Revision history Revision 0 (9 October 2002) first revision Revision 1 (6 November 2002) Incorporated comments from CAP WG. To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 6 November 2002 Subject: T10/02-404r1 SAM-3 Data In Size and Sense Data Size for Execute Command Revision history Revision 0 (9

More information

Related Documents ses2r00 - SCSI Enclosure Services - 2 revision r0 - SES-2 INVOP for Threshold In page

Related Documents ses2r00 - SCSI Enclosure Services - 2 revision r0 - SES-2 INVOP for Threshold In page To: T10 Technical Committee From: Dennis Spicher (dennis.spicher@hp.com) and Rob Elliott, HP (elliott@hp.com) Date: 18 July 00 Subject: Revision History Revision 0 (8 June 00) first revision Revision 1

More information

Revision 1: Correct editorial issues identified at the 22 September 2003 working group conference call.

Revision 1: Correct editorial issues identified at the 22 September 2003 working group conference call. To: From: INCITS T10 Committee Paul Entzel, Quantum Date: 20 October 2003 Document: Subject: T10/03-322r2 Transport protocol service extensions for ADT. 1 Revision History Revision 0: Initial revision.

More information

10.2 SCSI application layer

10.2 SCSI application layer 2 November 2007 07-479r0 SAS-2 Phy test pattern transmitter controls To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 2 November 2007 Subject: 07-479r0 SAS-2 Phy test pattern transmitter

More information

To: T10 Membership T10/97-184R4 Subject: Use of Class 2 for Fibre Channel Tapes From: Date: 23-Oct-1997

To: T10 Membership T10/97-184R4 Subject: Use of Class 2 for Fibre Channel Tapes From: Date: 23-Oct-1997 To: T10 Membership T10/97-184R4 Subject: Use of Class 2 for Fibre Channel Tapes From: Date: 23-Oct-1997 This paper describes the use of the Fibre Channel Class 2 protocol

More information

03-351r1 SAM-3 SPC-3 Task Attributes VPD page 11 December 2003

03-351r1 SAM-3 SPC-3 Task Attributes VPD page 11 December 2003 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 11 December 2003 Subject: 03-351r1 SAM-3 SPC-3 Task Attributes VPD page Revision history Revision 0 (14 October 2003) First revision

More information

10 May r1 SAM-4 TASK ABORTED status clarifications

10 May r1 SAM-4 TASK ABORTED status clarifications 10 May 2007 06-026r1 SAM-4 TASK ABORTED status clarifications To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 10 May 2007 Subject: 06-026r1 SAM-4 TASK ABORTED status clarifications

More information

Class 3 Error Detection and Recovery for Sequential Access Devices Preliminary ANSI T10 Working Document R22

Class 3 Error Detection and Recovery for Sequential Access Devices Preliminary ANSI T10 Working Document R22 Class 3 Error Detection and Recovery for Sequential Access Devices Preliminary ANSI T10 Working Document 97-189R22 Scope Problems exist in PLDA in detecting and correcting error conditions on sequential

More information

07-416r1 T10 USB Queuing Transport (UQT) study group introduction. by Rob Elliott, HP 25 September 2007

07-416r1 T10 USB Queuing Transport (UQT) study group introduction. by Rob Elliott, HP 25 September 2007 07-416r1 T10 USB Queuing Transport (UQT) study group introduction by Rob Elliott, HP 25 September 2007 USB and other external desktop interfaces USB dominates the market - 6.2 billion USB ports shipped

More information

16 July r1 SAS-2 Add device slot numbering fields to DISCOVER

16 July r1 SAS-2 Add device slot numbering fields to DISCOVER 16 July 2008 08-183r1 SAS-2 Add device slot numbering fields to DISCOVER To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 16 July 2008 Subject: 08-183r1 SAS-2 Add device slot numbering

More information

Internet transport-layer protocols. Transport services and protocols. Sending and receiving. Connection-oriented (TCP) Connection-oriented

Internet transport-layer protocols. Transport services and protocols. Sending and receiving. Connection-oriented (TCP) Connection-oriented Transport services and protocols Internet -layer protocols logical communication between processes protocols run in end systems send side: breaks app messages into segments, passes to layer rcv side: reassembles

More information

Chapter 3 Transport Layer

Chapter 3 Transport Layer Chapter 3 Transport Layer Lec 9: Reliable Data Transfer Computer Networking: A Top Down Approach 6 th edition Jim Kurose, Keith Ross Addison-Wesley March 2012 All material copyright 1996-2012 J.F Kurose

More information

Reliable Data Transfer

Reliable Data Transfer Reliable Data Transfer Kai Shen Reliable Data Transfer What is reliable data transfer? guaranteed arrival no error in order delivery Why is it difficult? unreliable underlying communication channel, which

More information

HP LTO Ultrium Tape Drives Technical Reference Manual Volume 3: Host Interface Guide

HP LTO Ultrium Tape Drives Technical Reference Manual Volume 3: Host Interface Guide HP LTO Ultrium Tape Drives Technical Reference Manual Volume : Host Interface Guide LTO drives Abstract This is one of five volumes that document HP LTO Ultrium tape drives (Fibre Channel and SAS). This

More information

Add the following section to REPORT SUPPORTED OPERATION CODES command.

Add the following section to REPORT SUPPORTED OPERATION CODES command. Page 1 of 7 Self Describing Cmd Timouts.fm/05-284r4 November 8, 2006 To: INCITS Technical Committee T10 From: Kevin Butt, IBM Date: November 8, 2006 12:48 pm Document: T10/05-284r4 Subject: SPC-4: Self

More information

T10/06-119r0 SAS-2 BREAK_REPLY 28 February 2006

T10/06-119r0 SAS-2 BREAK_REPLY 28 February 2006 T10/06-119r0 SAS-2 _REPLY 28 February 2006 To: T10 Technical Committee From: Timothy Hoglund, LSI Logic Date: 28 February 2006 Subject: Serial Attached SCSI - 2 (SAS-2) Revision History Revision 0 (28

More information

Chapter III: Transport Layer

Chapter III: Transport Layer Chapter III: Transport Layer UG3 Computer Communications & Networks (COMN) Myungjin Lee myungjin.lee@ed.ac.uk Slides copyright of Kurose and Ross rdt2.0 has a fatal flaw! what happens if ACK/NAK corrupted?

More information

03-344r2 SPC-3 SAM-3 Report all initiator and target ports 30 December 2003

03-344r2 SPC-3 SAM-3 Report all initiator and target ports 30 December 2003 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 0 December 200 Subject: 0-44r2 SPC- SAM- Report all initiator and target ports Revision history Revision 0 (6 October 200) First

More information

Chapter 3 outline. 3.5 connection-oriented transport: TCP segment structure reliable data transfer flow control connection management

Chapter 3 outline. 3.5 connection-oriented transport: TCP segment structure reliable data transfer flow control connection management Chapter 3 outline 3.1 transport-layer services 3.2 multiplexing and demultiplexing 3.3 connectionless transport: UDP 3.4 principles of reliable data transfer 3.5 connection-oriented transport: TCP segment

More information

2 September r0 SAT-2 ATA PASS-THROUGH sense data format

2 September r0 SAT-2 ATA PASS-THROUGH sense data format To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 2 September 2008 Subject: 08-344r0 SAT-2 ATA PASS-THROUGH sense data format Revision history Revision 0 (2 September 2008) First

More information

SERIAL ATTACHED SCSI (SAS) CONSORTIUM

SERIAL ATTACHED SCSI (SAS) CONSORTIUM SERIAL ATTACHED SCSI (SAS) CONSORTIUM Clause 6 SAS SPL Link Layer Test Suite Version 1.3 Technical Document Last Updated: 6 September 2011 Serial Attached SCSI Consortium 121 Technology Drive, Suite 2

More information

Revision history Related documents Overview Suggested changes to SAT Approved references

Revision history Related documents Overview Suggested changes to SAT Approved references To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) and Jeff Wolford, HP (jeff.wolford@hp.com) Date: 10 Dec 2007 Subject: 07-200r3 SAT-2 WRITE LONG to WRITE UNCORRECTABLE EXT Revision history

More information

24 October r2 SAS-2 Support multiple STP affiliations

24 October r2 SAS-2 Support multiple STP affiliations 24 October 2006 06-188r2 SAS-2 Support multiple STP affiliations To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 24 October 2006 Subject: 06-188r2 SAS-2 Support multiple STP affiliations

More information

r5 09 December 2008

r5 09 December 2008 08-249 r5 09 December 2008 To: T10 SAS Protocol Working Group From: Brian Day and George Penokie Subject: SAS 2.+ SPL: 08-249 Link Layer Power Management Revision History Revision 0 - Initial draft Revision

More information

RSC Part III: Transport Layer 3. TCP

RSC Part III: Transport Layer 3. TCP RSC Part III: Transport Layer 3. TCP Redes y Servicios de Comunicaciones Universidad Carlos III de Madrid These slides are, mainly, part of the companion slides to the book Computer Networking: A Top Down

More information

CS 162 Operating Systems and Systems Programming Professor: Anthony D. Joseph Spring Lecture 21: Network Protocols (and 2 Phase Commit)

CS 162 Operating Systems and Systems Programming Professor: Anthony D. Joseph Spring Lecture 21: Network Protocols (and 2 Phase Commit) CS 162 Operating Systems and Systems Programming Professor: Anthony D. Joseph Spring 2003 Lecture 21: Network Protocols (and 2 Phase Commit) 21.0 Main Point Protocol: agreement between two parties as to

More information

Basic Reliable Transport Protocols

Basic Reliable Transport Protocols Basic Reliable Transport Protocols Do not be alarmed by the length of this guide. There are a lot of pictures. You ve seen in lecture that most of the networks we re dealing with are best-effort : they

More information

16 June 2007 e07129r1 ATA8-ACS Endianness clarifications

16 June 2007 e07129r1 ATA8-ACS Endianness clarifications 16 June 2007 e07129r1 ATA8-ACS Endianness clarifications To: T13 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 16 June 2007 Subject: e07129r1 ATA8-ACS Endianness clarifications Revision

More information

CS 3516: Advanced Computer Networks

CS 3516: Advanced Computer Networks Welcome to CS 3516: Advanced Computer Networks Prof. Yanhua Li Time: 9:00am 9:50am M, T, R, and F Location: Fuller 320 Fall 2017 A-term 1 Some slides are originally from the course materials of the textbook

More information

The Transport Layer: TCP & Reliable Data Transfer

The Transport Layer: TCP & Reliable Data Transfer The Transport Layer: TCP & Reliable Data Transfer Smith College, CSC 249 February 15, 2018 1 Chapter 3: Transport Layer q TCP Transport layer services: v Multiplexing/demultiplexing v Connection management

More information

05-023r0 SAS-1.1 Connector figures 23 December 2004

05-023r0 SAS-1.1 Connector figures 23 December 2004 To: T10 Technical Committee From: Jerry Kachlic, Molex (Jerry.Kachlic@molex.com) and Rob Elliott, HP (elliott@hp.com) Date: 23 December 2004 Subject: 05-023r0 SAS-1.1 Connector figures Revision history

More information

Lecture 5: Flow Control. CSE 123: Computer Networks Alex C. Snoeren

Lecture 5: Flow Control. CSE 123: Computer Networks Alex C. Snoeren Lecture 5: Flow Control CSE 123: Computer Networks Alex C. Snoeren Pipelined Transmission Sender Receiver Sender Receiver Ignored! Keep multiple packets in flight Allows sender to make efficient use of

More information

Computer Networking. Reliable Transport. Reliable Transport. Principles of reliable data transfer. Reliable data transfer. Elements of Procedure

Computer Networking. Reliable Transport. Reliable Transport. Principles of reliable data transfer. Reliable data transfer. Elements of Procedure Computer Networking Reliable Transport Prof. Andrzej Duda duda@imag.fr Reliable Transport Reliable data transfer Data are received ordered and error-free Elements of procedure usually means the set of

More information

Chapter 3 Transport Layer

Chapter 3 Transport Layer Chapter 3 Transport Layer A note on the use of these Powerpoint slides: We re making these slides freely available to all (faculty, students, readers). They re in PowerPoint form so you see the animations;

More information

Revision 2: Updated the error recovery tables. Incorporate input from February 23, 2004 teleconference.

Revision 2: Updated the error recovery tables. Incorporate input from February 23, 2004 teleconference. To: INCITS T10 Committee From: Susan Gray, Quantum Date: February 23, 2004 Document Number: T10/04-056r2 Subject: ADT Link service error recovery 1 Revision History Revision 2: Updated the error recovery

More information

04-082r0 SBC-2 Replace Notch and Partition mode page with READ CAPACITY 5 March 2004

04-082r0 SBC-2 Replace Notch and Partition mode page with READ CAPACITY 5 March 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 5 March 2004 Subject: 04-082r0 SBC-2 Replace Notch and Partition mode page with READ CAPACITY Revision history Revision 0 (5 March

More information

Question. Reliable Transport: The Prequel. Don t parse my words too carefully. Don t be intimidated. Decisions and Their Principles.

Question. Reliable Transport: The Prequel. Don t parse my words too carefully. Don t be intimidated. Decisions and Their Principles. Question How many people have not yet participated? Reliable Transport: The Prequel EE122 Fall 2012 Scott Shenker http://inst.eecs.berkeley.edu/~ee122/ Materials with thanks to Jennifer Rexford, Ion Stoica,

More information

Revisions. Introduction. Proposal

Revisions. Introduction. Proposal To: INCITS Technical Committee T10 From: Kevin Butt Date: Printed Monday, January 07, 2008 6:31 pm Document: T10/08-025r1 Persistent Reservations - Team Revisions 1. 08-025r0 Initial revision (10 December

More information

Lecture 5. Transport Layer. Transport Layer 1-1

Lecture 5. Transport Layer. Transport Layer 1-1 Lecture 5 Transport Layer Transport Layer 1-1 Agenda The Transport Layer (TL) Introduction to TL Protocols and Services Connectionless and Connection-oriented Processes in TL Unreliable Data Transfer User

More information

03-344r4 SPC-3 SAM-3 Report all initiator and target ports 9 February 2004

03-344r4 SPC-3 SAM-3 Report all initiator and target ports 9 February 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 9 February 2004 Subject: 0-44r4 SPC- SAM- Report all initiator and target ports Revision history Revision 0 (6 October 200) First

More information

03-240r2 SAS-1.1 Internal wide connector and cable 28 April 2004

03-240r2 SAS-1.1 Internal wide connector and cable 28 April 2004 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 28 April 2004 Subject: 03-240r2 SAS-1.1 Internal wide connector and cable Revision history Revision 0 (2 July 2003) First revision

More information

MatrixDTLS Developer s Guide

MatrixDTLS Developer s Guide MatrixDTLS Developer s Guide Electronic versions are uncontrolled unless directly accessed from the QA Document Control system. Printed version are uncontrolled except when stamped with VALID COPY in red.

More information

Transport services and protocols. Chapter 3 outline. Internet transport-layer protocols Chapter 3 outline. Multiplexing/demultiplexing

Transport services and protocols. Chapter 3 outline. Internet transport-layer protocols Chapter 3 outline. Multiplexing/demultiplexing Chapter 3 outline 3.1 Transport-layer services 3.2 Multiplexing and demultiplexing 3.3 Connectionless : UDP 3.4 Principles of reliable data transfer 3.5 Connection-oriented : TCP segment structure reliable

More information

02-360r3 SAS spinup 25 October 2002

02-360r3 SAS spinup 25 October 2002 To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 25 October 2002 Subject: 02-360r3 SAS spinup Revision Histy Revision 0 (10 September 2002) First revision Revision 1 (13 October

More information

CS419: Computer Networks. Lecture 10, Part 2: Apr 11, 2005 Transport: TCP mechanics (RFCs: 793, 1122, 1323, 2018, 2581)

CS419: Computer Networks. Lecture 10, Part 2: Apr 11, 2005 Transport: TCP mechanics (RFCs: 793, 1122, 1323, 2018, 2581) : Computer Networks Lecture 10, Part 2: Apr 11, 2005 Transport: TCP mechanics (RFCs: 793, 1122, 1323, 2018, 2581) TCP as seen from above the socket The TCP socket interface consists of: Commands to start

More information

26 April r0 SAT-2 WRITE LONG to WRITE UNCORRECTABLE EXT

26 April r0 SAT-2 WRITE LONG to WRITE UNCORRECTABLE EXT 26 April 2007 07-200r0 SAT-2 WRITE LONG to WRITE UNCORRECTABLE EXT To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) and Jeff Wolford, HP (jeff.wolford@hp.com) Date: 26 April 2007 Subject:

More information

Computer Communication Networks Midterm Review

Computer Communication Networks Midterm Review Computer Communication Networks Midterm Review ICEN/ICSI 416 Fall 2018 Prof. Aveek Dutta 1 Instructions The exam is closed book, notes, computers, phones. You can use calculator, but not one from your

More information

CS519: Computer Networks. Lecture 5, Part 4: Mar 29, 2004 Transport: TCP congestion control

CS519: Computer Networks. Lecture 5, Part 4: Mar 29, 2004 Transport: TCP congestion control : Computer Networks Lecture 5, Part 4: Mar 29, 2004 Transport: TCP congestion control TCP performance We ve seen how TCP the protocol works Sequencing, receive window, connection setup and teardown And

More information

The Transport Layer Reliability

The Transport Layer Reliability The Transport Layer Reliability CS 3, Lecture 7 http://www.cs.rutgers.edu/~sn4/3-s9 Srinivas Narayana (slides heavily adapted from text authors material) Quick recap: Transport Provide logical communication

More information

CMSC 332 Computer Networks Reliable Data Transfer

CMSC 332 Computer Networks Reliable Data Transfer CMSC 332 Computer Networks Reliable Data Transfer Professor Szajda Last Time Multiplexing/Demultiplexing at the Transport Layer. How do TCP and UDP differ? UDP gives us virtually bare-bones access to the

More information

04-218r5 SAT SPC-3 INQUIRY contents 30 October 2004

04-218r5 SAT SPC-3 INQUIRY contents 30 October 2004 To: T10 Technical Committee From: Rob Elliott (elliott@hp.com) and Wayne Bellamy, HP (wayne.bellamy@hp.com) Date: 30 October 2004 Subject: 04-218r5 SAT SPC-3 INQUIRY contents Revision history Revision

More information

CMPE 150/L : Introduction to Computer Networks. Chen Qian Computer Engineering UCSC Baskin Engineering Lecture 8

CMPE 150/L : Introduction to Computer Networks. Chen Qian Computer Engineering UCSC Baskin Engineering Lecture 8 CMPE 150/L : Introduction to Computer Networks Chen Qian Computer Engineering UCSC Baskin Engineering Lecture 8 1 A lot of students have been having difficulty seeing the HTTP packets generated when navigating

More information

Lecture 11: Transport Layer Reliable Data Transfer and TCP

Lecture 11: Transport Layer Reliable Data Transfer and TCP Lecture 11: Transport Layer Reliable Data Transfer and TCP COMP 332, Spring 2018 Victoria Manfredi Acknowledgements: materials adapted from Computer Networking: A Top Down Approach 7 th edition: 1996-2016,

More information

Chapter 3: Transport Layer Part A

Chapter 3: Transport Layer Part A Chapter 3: Transport Layer Part A Course on Computer Communication and Networks, CTH/GU The slides are adaptation of the slides made available by the authors of the course s main textbook 3: Transport

More information

Transport Layer Marcos Vieira

Transport Layer Marcos Vieira Transport Layer 2014 Marcos Vieira Transport Layer Transport protocols sit on top of network layer and provide Application-level multiplexing ( ports ) Error detection, reliability, etc. UDP User Datagram

More information

CSC 4900 Computer Networks: Reliable Data Transport

CSC 4900 Computer Networks: Reliable Data Transport CSC 4900 Computer Networks: Reliable Data Transport Professor Henry Carter Fall 2017 Last Time Multiplexing/Demultiplexing at the Transport Layer. How do TCP and UDP differ? UDP gives us virtually bare-bones

More information

CSC 401 Data and Computer Communications Networks

CSC 401 Data and Computer Communications Networks CSC 401 Data and Computer Communications Networks Transport Layer Pipelined Reliable Data Transfer Protocols: Go-Back-N and Selective Repeat Sec 3.4.2-3.4.3 Prof. Lina Battestilli Fall 2017 Transport Layer

More information

Analyzation of Automatic Repeat Request (ARQ) Protocols

Analyzation of Automatic Repeat Request (ARQ) Protocols RESEARCH ARTICLE OPEN ACCESS Analyzation of Automatic Repeat Request (ARQ) Protocols 1 Jeshvina.S, 2 Sneha.P, 3 Saraanya.S Final year BCA, Dept of Computer Science New Horizon College Kasturinagar, Bangalore

More information

Chapter 3 Transport Layer

Chapter 3 Transport Layer Chapter 3 Transport Layer Reti degli Elaboratori Canale AL Prof.ssa Chiara Petrioli a.a. 2013/2014 We thank for the support material Prof. Kurose-Ross All material copyright 1996-2012 J.F Kurose and K.W.

More information

Chapter 3 Transport Layer

Chapter 3 Transport Layer Chapter 3 Transport Layer A note on the use of these ppt slides: We re making these slides freely available to all (faculty, students, readers). They re in PowerPoint form so you can add, modify, and delete

More information

rdt2.0 has a fatal flaw!

rdt2.0 has a fatal flaw! rdt2. has a fatal flaw! rdt2.1:, handles garbled ACK/NAKs what happens if ACK/NAK corrupted? doesn t know what happened at! can t just retransmit: possible duplicate handling duplicates: retransmits current

More information

Overview This proposes topics and text for an InfiniBand annex for the SCSI over RDMA (SRP) standard.

Overview This proposes topics and text for an InfiniBand annex for the SCSI over RDMA (SRP) standard. To: From: T10 Technical Committee Greg Pellegrino (Greg.Pellegrino@compaq.com) and Rob Elliott, Compaq Computer Corporation (Robert.Elliott@compaq.com) Date: 19 June 2001 Subject: SRP InfiniBand annex

More information