T10/03-186r2 SAS-1.1 Transport layer retries
|
|
- Roy Webster
- 5 years ago
- Views:
Transcription
1 To: T10 Technical Committee From: Rob Elliott, HP and Jim Jones, Quantum Date: 28 July 2003 Subject: T10/03-186r1 SAS-1.1 Transport layer retries T10/03-186r2 SAS-1.1 Transport layer retries Revision History Revision 0 (6 May 2003) first revision Revision 1 (2 July 2003) added more details Revision 2 (28 July 2003) incorporated comments from July SAS working group meeting. Related Documents sas-r05 Serial Attached SCSI revision 5 sas1r00 Serial Attached SCSI revision r1 SAS-1.1 Transport layer retries ladders Overview In SAS-1, errors transmitting frames result in either the logical unit terminating the command with CHECK CONDITION status, or the application client aborting the command. Possible errors are: Page 1 of 10
2 Figure 1. Error cases Depending on the type of frame, different things happen in SAS-1.0: Page 2 of 10
3 1. Frame arrives OK; ACK arrives OK 2. Frame arrives with CRC error; NAK arrives OK 3. Frame arrives OK; ACK lost 4. Frame arrives with CRC error; NAK lost (double error) COMMAND or TASK (I to T) Target runs the command after sending ACK. Target idle after sending NAK. Initiator sees the NAK and can resend the command. Target runs the command after sending ACK. I to T direction hung interlocked. Initiator detects ACK/NAK timeout in 1 ms. T to I direction could deliver DATA, XFER_RDY, or RESPONSE frames in that time. Initiator cannot tell between frame lost w/o using QUERY TASK. Target idle after sending NAK. I to T direction hung interlocked. Initiator detects ACK/NAK timeout in 1 ms. Initiator can resend cmd later. Initiator cannot tell between frame lost w/o using QUERY TASK. 5. Frame lost Target idle. I to T direction hung interlocked. Initiator detects ACK/NAK timeout in 1 ms. Initiator can resend cmd later. Initiator cannot tell between frame lost w/o using QUERY TASK. XFER_RDY (T to I) Initiator replies with write DATA frame(s). Target terminates command. timeout in 1 ms. I to T direction could deliver write DATA frames in that time. Target cannot tell between frame lost. timeout in 1 ms. Target cannot tell between frame lost. timeout in 1 ms. Target terminates cmd. Target cannot tell between frame lost. Table 1. SAS-1.0 behavior RESPONSE (T to I) Both finish the command. Initiator can reuse tag after evidence of target progression. Target can resend with retransmit=1. timeout in 1 ms. I to T direction not supposed to deliver new command with the same tag yet. Target resends with retransmit=1 in a new connection. timeout in 1 ms. Target resends with retransmit=1 in new connection. timeout in 1 ms. Target resends with retransmit=1 in new connection. T10/03-186r2 SAS-1.1 Transport layer retries read DATA (T to I) Move on to more data or RESPONSE (or XFER_RDY for bidi commands) Target terminates command Subsequent ACKs/NAKs for by the target. Target ACK/NAK timeout. Target terminates cmd. Subsequent ACKs/NAKs for by the target. Initiator sees data offset gap. Target ACK/NAK timeout. Target terminates command. Initiator aborts cmd because of gap (if subseq. DATA frames) Subsequent ACK/NAKs for by the target. Initiator sees data offset gap. Target ACK/NAK timeout. Target terminates command. Initiator aborts cmd because of gap. write DATA (I to T) Move on to more data, XFER_RDY, or RESPONSE (or read DATA for bidi commands) Initiator aborts command Subsequent ACK/NAKs for by the initiator. Initiator ACK/NAK timeout. Initiator aborts cmd. Subsequent ACK/NAKs for by the initiator. Initiator ACK/NAK timeout. Initiator aborts cmd. Target terminates command because of gap (if subseq. DATA frames). Initiator Response Timeout may occur causing target to terminate cmd. Subsequent ACK/NAKs for by the initiator. Initiator ACK/NAK timeout. Initiator aborts cmd. Target terminates command because of gap (if subseq. DATA frames). Initiator Response Timeout may occur causing target to terminate cmd. Page 3 of 10
4 Proposed enhancements Some backup applications will fail the whole backup if any of their commands are terminated with CHECK CONDITION. A way to retransmit frames is desirable. These special recovery features are not always wanted; per-logical unit controls are needed. Tape drives would implement these features; disk drives probably would not. A Mode page per LUN to enable/disable special recovery mode (not the Enable Modify Data Pointers bit in the Disconnect- Reconnect mode page) would be added. RESPONSE problems If target gets a NAK, resend as in SAS-1.0 (with Retransmit=1). Retransmit=1 isn t strictly necessary since the target didn t see anything; but it helps logic analyzers. If target detects an ACK/NAK timeout, resend as in SAS-1.0 (with Retransmit=1) Target shall retry RESPONSE problems at least one time. COMMAND or TASK problems If initiator gets a NAK, resend as in SAS-1.0 If initiator detects a RESPONSE frame before it gets an ACK for a command, an ACK was lost. Treat the command as successful. Still close the connection with ACK/NAK Timeout, but do nothing more. If initiator detects an XFER_RDY or read DATA frame (for a COMMAND frame, not for a TASK frame) before it gets an ACK for a command, an ACK was lost. Treat the command as successfully received. Still close the connection with ACK/NAK Timeout, but start servicing the XFER_RDY or read DATA. If initiator detects an ACK/NAK timeout, close connection with ACK/NAK Timeout and send QUERY TASK in a new connection to see if the command is running in the target: o If FUNCTION SUCCEEDED, then assume it s running fine. If first burst is enabled, start sending write DATA frames. o If FUNCTION COMPLETE, then resend the command. o Continue watching for a RESPONSE frame while running QUERY TASK. o o If a RESPONSE shows up, don t try to abort the command and don t report it as aborted to the application client. if QUERY TASK is not supported, initiator will have to use ABORT TASK and try to abort the command (it may get a RESPONSE anyway). Logical units behind target ports supporting transport layer retries shall support QUERY TASK. XFER_RDY problems If target gets a NAK, resend with Retransmit=1 and a new TPTT. Retransmit=1 isn t strictly necessary since the initiator didn t see anything, but it helps logic analyzers. New TPTT isn t strictly necessary since the old one isn t being used - however, this seems simpler If target detects an ACK/NAK timeout, resend with Retransmit=1 and a new TPTT Target shall retry XFER_RDY problems at least one time. If target sees write DATA frames before seeing an ACK for the XFER_RDY, target discards them Write DATA frames in response to an XFER_RDY with Retransmit=1 do not themselves have Retransmit=1 Target shall change Target Port Transfer Tag between XFER_RDYs (either retransmitted or normal) Initiator can continue sending data for the previous XFER_RDY when a new one arrives for the same command (same tag), but must not send data for the new XFER_RDY until it is done sending for the previous. Once it sends a data frame for the new XFER_RDY, no more data frames for the old are allowed. This applies to both Retransmit=1 or Retransmit=0 cases. The target can reuse the first TPTT when it sees a data frame with the second TPTT. Page 4 of 10
5 If initiator receives an XFER_RDY with Retransmit=0 but it is already servicing an XFER_RDY, it should assume an error and abort the command. This is more likely a bug than a single bit error worth recovering from. Write DATA problems Set Retry Data Frames=1 bit in XFER_RDY to tell the initiator to retry write DATA frames that encounter errors. Only target ports supporting transport layer retries would set this bit (and only if their mode page is thus enabled). If initiator gets a NAK, resend that write DATA frame and all that followed. It shall go back to the last XFER_RDY base offset. (An ACK/NAK balance point might also work, but XFER_RDY will be easier for targets to handle. Going back to the frame in error rather than the ACK/NAK balance point is risky because a lost ACK or NAK could point to the wrong frame.) If initiator detects an ACK/NAK timeout, resend all write DATA frames since the last XFER_RDY base offset. (Last ACK/NAK balance point could work but not allowed) Each resent write DATA frame has the correct Data Offset No use of the Retransmit bit for write DATA frames First resent write DATA frame has Changing Data Pointer=1 If an ACK (rather than a NAK) was lost, the target doesn t know and may follow with a RESPONSE or XFER_RDY that surprises the initiator (in a subsequent connection) o If resent write DATA frames cross a RESPONSE frame, initiator has to accept the RESPONSE and complete the command without worrying about the missing ACK for its earlier write DATA frame. The target discards subsequent write data frames since they have a o now-unknown tag and TPTT. Easiest if initiator has to stop sending frames for the command after receiving a RESPONSE. If resent write DATA frames cross an XFER_RDY, initiator has to accept the XFER_RDY. Target shall use a different Target Port Transfer Tag for the XFER_RDY to help differentiate them. Proposal: initiator has to stop sending write DATA frames for the old XFER_RDY before sending any write DATA frames for the new XFER_RDY.. Receiving a RESPONSE frame or XFER_RDY does NOT serve as a link layer ACK for the outbound direction - an ACK/NAK timeout must still occur. The inbound frame must be ACKed and honored, though (the T to I direction does not timeout). Target shall not abort a command when it sees a relative offset error. Target shall start discarding data after the gap until it gets a frame with Changing Data Pointer=1 (unlike the initiator on read data gaps, target does not have the option of storing bad data in the wrong place). Target may discard resent data up to the gap if it chooses (rather than overwriting). Read DATA problems If target gets a NAK, it shall resend that read DATA frame and all that followed. It shall go back to a ACK/NAK balance point (probably but not necessarily the last one) rather than retry starting from the read DATA frame it thinks was NAKed, because a lost ACK or NAK while pipelining could mean it mismatched the NAK. If target detects an ACK/NAK timeout, it shall resend all read DATA frames since the last ACK/NAK balance point. If target gets a NAK, it should stop sending read DATA frames. No use of Retransmit bit for read DATA frames Set the Changing Data Pointer bit to 1 when the target is going back to an earlier data offset Target frames shall be monotonically increasing after Changing Data Pointer=1 Initiator shall not abort a command when it sees a relative offset error. Initiator may start discarding data after the gap until it gets a frame with Changing Data Pointer=1 (or it may store the data at the wrong offsets, or it may store the data at the correct offsets). Initiator may discard resent data up to the gap if it chooses (rather than overwriting). Target shall retry Read DATA problems at least one time. Page 5 of 10
6 New bits for target ports supporting transport layer retries Keep the Retransmit bit in the SSP frame header (byte 10 bit 1). SAS-1.0 only allowed this bit be used for RESPONSE frames. SAS-1.1 also allow it for XFER_RDY frames New Changing Data Pointer bit for DATA frames (both read DATA and write DATA frames) (byte 10 bit 0) 1 = the data offset is being set to a non-monotonically increasing value. (it must always go backwards) New Retry Data Frames bit for XFER_RDY frames only (byte 9 bit 2) The initiator has permission to retry write DATA frames that encounter NAKs or ACK/NAK timeouts Add the Protocol-Specific Logical Unit mode page (18h) (new to SAS): Optimized Recovery bit (located anywhere) 1 = the device server in the logical unit instructs the target port to: o set XFER_RDY frame header Retry Data Frames bit to 1 o retry read DATA frames that fail o accept write DATA frames with Changing Data Pointer = 1 T10/03-186r2 SAS-1.1 Transport layer retries Transition If the target sends an XFER_RDY with Retry Data Frames set to 1 to an initiator that doesn t understand it: If the initiator checks reserved fields, it will abort the command. If it determines it is aborting every one of its write commands, it might be prudent to ignore the reserved field. If the initiator is SAS-1.1 cognizant but does not support the feature, SAS-1.1 will require it to ignore the field and investigate why the mode page is set wrong. If the initiator does not check reserved fields, it will ignore it and never try to retry. If it encounters an ACK/NAK timeout or a NAK, it will abort the command. If the initiator sends Changing Data Pointer=1 to a SAS-1 target: If the target checks reserved fields, it will abort the command. This should only happen after an error, so that s how SAS-1 behaved anyway. If the target does not check reserved fields, it will ignore it, detect a relative offset error, and abort the command. This should only happen after an error, so that s how SAS-1 behaved anyway. If the target sends Changing Data Pointer=1 to a SAS-1 initiator: If the initiator checks reserved fields, it will abort the command. This should only happen after an error, so that s how SAS-1 behaved anyway. If the initiator does not check reserved fields, it will ignore it, detect a relative offset error, and abort the command. This should only happen after an error, so that s how SAS-1 behaved anyway. Page 6 of 10
7 Detailed proposal in standardese 9.2 SSP transport layer SSP frame format Table 92 defines the SSP frame format. T10/03-186r2 SAS-1.1 Transport layer retries Table 92 SSP frame format Byte\Bit to 9 as is to n as is RETRY DATA FRAMES RETRANSMIT CHANGING DATA POINTER... The RETRY DATA FRAMES bit is set to one for XFER_RDY frames under certain conditions (see 9.2.4) and shall be set to zero for all other frame types. This bit indicates the SSP initiator port may retry write DATA frames that fail. The RETRANSMIT bit is set to one for RESPONSE frames and XFER_RDY frames under certain conditions (see ) and shall be set to zero for all other frame types. This bit indicates the frame is a retransmission after the SSP target port failed in its previous attempt to transmit the frame. The CHANGING DATA POINTER bit is set to one for DATA frames under certain conditions (see 9.2.4) and shall be set to zero for all other frame types. This bit indicates the frame is a retransmission after the SSP target port failed in its previous attempt to transmit this or a subsequent frame and the data offset field is not sequentiall increasing SSP transport layer handling of link layer errors Transport layer handling of link layer errors overview If an SSP initiator port is exchanging frames with a logical unit that supports transport layer retries, it shall follow the rules in If it has reached its retry limit or is exchanging frames with a logical unit that does not support transport layer retries, it shall follow the rules in Logical units supporting transport layer retries shall: a) support the QUERY TASK task management function; and b) select a different value for the TARGET PORT TRANSFER TAG field in an XFER_RDY frame than that used in the previous XFER_RDY frame Transport layer retries COMMAND frame If an SSP initiator port transmits a COMMAND frame and does not receive an ACK or NAK (e.g., times out, or the connection is broken) it shall close the connection with DONE (ACK/NAK TIMEOUT) and transmit a QUERY TASK task management function in the next connection to determine whether the command was received. If QUERY TASK returns a TASK MANAGEMENT FUNCTION SUCCEEDED response, the SSP initiator port shall assume the COMMAND frame was ACKed. If QUERY TASK returns a TASK MANAGEMENT FUNCTION COMPLETE response, and neither an XFER_RDY frame nor a RESPONSE frame has been received for that I_T_L_Q nexus, the SSP initiator port shall assume the command was NAKed or lost and may reuse the tag (see ). Page 7 of 10
8 If an XFER_RDY frame or RESPONSE frame arrives before QUERY TASK completes, the SSP initiator shall assume the COMMAND frame was successfully received and the command is being processed (i.e., the XFER_RDY frame or RESPONSE frame is honored) TASK frame If an SSP initiator port transmits a TASK frame and does not receive an ACK or NAK (e.g., times out, or the connection is broken) it shall retransmit the TASK frame in a new connection (see ) XFER_RDY frame If an SSP target port transmits an XFER_RDY frame and does not receive an ACK or NAK (e.g., times out, or the connection is broken), it shall close the connection with DONE (ACK/NAK TIMEOUT) and retransmit the XFER_RDY frame with the RETRANSMIT bit set to one and with a different TARGET PORT TRANSFER TAG. If an SSP target port transmits an XFER_RDY frame and receives a NAK, it shall retransmit the XFER_RDY frame with the RETRANSMIT bit set to one and with a different TARGET PORT TRANSFER TAG. If an SSP initiator port receives an XFER_RDY frame with the RETRANSMIT bit set to one while it is still processing the previous XFER_RDY frame for that command, it should stop processing the previous XFER_RDY frame (i.e., stop sending write DATA frames) and start servicing the new XFER_RDY frame. The SSP initiator port shall not send any write DATA frames for the old XFER_RDY after sending a write DATA frame for the new XFER_RDY. The SSP target port may reuse the TARGET PORT TRANSFER TAG value from the first XFER_RDY frame when it receives a write DATA frame for the new XFER_RDY frame DATA frame If an SSP target port transmits a read DATA frame and does not receive an ACK or NAK (e.g., times out, or the connection is broken), it shall close the connection with DONE (ACK/NAK TIMEOUT) and retransmit all the read DATA frames since one of the previous ACK/NAK balance points. If an SSP target port transmits a read DATA frame and receives a NAK, it shall retransmit all the read DATA frames since one of the previous ACK/NAK balance points. If an SSP initiator port transmits a write DATA frame and does not receive an ACK or NAK (e.g., times out, or the connection is broken), it shall close the connection with DONE (ACK/NAK TIMEOUT) and retransmit all the write DATA frames for the XFER_RDY. If it receives an XFER_RDY or RESPONSE frame for the command, it shall process the XFER_RDY or RESPONSE frame and should stop sending the retransmitted write DATA frames (but it may continue transmitting them). It shall not send a write DATA frame for the old XFER_RDY after sending a write DATA frame for the new XFER_RDY. If an SSP initiator port transmits a write DATA frame and receives a NAK, it shall retransmit all the write DATA frames for the XFER_RDY. In all cases, the first retransmitted read DATA frame shall have its CHANGING DATA POINTER bit set to one; subsequent read DATA frames shall have their CHANGING DATA POINTER bits set to zero RESPONSE frame If an SSP target port transmits a RESPONSE frame and does not receive an ACK or NAK (e.g., times out, or the connection is broken), it shall close the connection with DONE (ACK/NAK TIMEOUT) and retransmit the RESPONSE frame with the RETRANSMIT bit set to one in a new connection. It shall do this at least one time. Page 8 of 10
9 If an SSP target port transmits a RESPONSE frame and receives a NAK, it shall retry transmitting the RESPONSE frame at least one time (see ). If an SSP initiator port receives a RESPONSE frame with a RETRANSMIT bit set to one, and it has previously received a RESPONSE frame for the same I_T_L_Q nexus, it shall discard the extra RESPONSE frame. If it has not previously received the RESPONSE frame, it shall treat it as the valid RESPONSE frame (see ) No transport layer retries COMMAND frame If an SSP initiator port transmits a COMMAND frame and does not receive an ACK or NAK (e.g., times out, or the connection is broken) it shall close the connection with DONE (ACK/NAK TIMEOUT) and transmit a QUERY TASK task management function in the next connection to determine whether the command was received. If QUERY TASK returns a TASK MANAGEMENT FUNCTION SUCCEEDED response, the SSP initiator port shall assume the COMMAND frame was ACKed. If QUERY TASK returns a TASK MANAGEMENT FUNCTION COMPLETE response, and a RESPONSE frame has not yet been received for that I_T_L_Q nexus, the SSP initiator port shall assume the command was NAKed or lost and may reuse the tag (see ) TASK frame If an SSP initiator port transmits a TASK frame and does not receive an ACK or NAK (e.g., times out, or the connection is broken) it shall retransmit the TASK frame in a new connection (see ) XFER_RDY frame If an SSP target port transmits an XFER_RDY frame and does not receive an ACK or NAK (e.g., times out, or the connection is broken), it shall close the connection with DONE (ACK/NAK TIMEOUT) and return a CHECK CONDITION status for that command with a sense key of ABORTED COMMAND and an additional sense code of ACK/NAK TIMEOUT (see ). If an SSP target port transmits an XFER_RDY frame and receives a NAK, it shall return a CHECK CONDITION status for that command with a sense key of ABORTED COMMAND and an additional sense code of NAK RECEIVED (see ) DATA frame If an SSP target port transmits a read DATA frame and does not receive an ACK or NAK (e.g., times out, or the connection is broken), it shall close the connection with DONE (ACK/NAK TIMEOUT) and return a CHECK CONDITION status for that command with a sense key of ABORTED COMMAND and an additional sense code of ACK/NAK TIMEOUT (see ). If an SSP target port transmits a read DATA frame and receives a NAK, it shall return a CHECK CONDITION status for that command with a sense key of ABORTED COMMAND and an additional sense code of NAK RECEIVED (see ). If an SSP initiator port transmits a write DATA frame and does not receive an ACK or NAK (e.g., times out, or the connection is broken), it shall close the connection with DONE (ACK/NAK TIMEOUT) and abort the command (see ). If an SSP initiator port transmits a write DATA frame and receives a NAK, it shall abort the command (see ) RESPONSE frame Page 9 of 10
10 If an SSP target port transmits a RESPONSE frame and does not receive an ACK or NAK (e.g., times out, or the connection is broken), it shall close the connection with DONE (ACK/NAK TIMEOUT) and retransmit try transmitting the RESPONSE frame with the RETRANSMIT bit set to one again in a new connection. It shall do this at least one time. The RETRANSMIT bit shall be set to one on each of the retries (see ). If an SSP target port transmits a RESPONSE frame and receives a NAK, it shall retransmit retry transmitting the RESPONSE frame at least one time (see ). If an SSP initiator port receives a RESPONSE frame with a RETRANSMIT bit set to one, and it has previously received a RESPONSE frame for the same I_T_L_Q nexus, it shall discard the extra RESPONSE frame. If it has not previously received the RESPONSE frame, it shall treat it as the valid RESPONSE frame (see ) ST (transport layer for SSP ports) state machines [state machine modifications go here] Page 10 of 10
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 information03-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 informationT10/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 informationT10/03-229r1 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: 11 August 2003 Subject: T10/03-229r1 SAS-1.1 Transport Layer Retries ladder diagrams
More informationItem 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 information12 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 informationSERIAL 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 information17 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 information9 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 informationT10/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 information04-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 informationOverview 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 information04-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 information04-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 information16 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 information17 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 information04-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 information8 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 information04-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 information04-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 informationReliable 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 information03-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 information10.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 information7 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 informationRevision 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 information24 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 informationRevision 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 informationSerial 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 informationThe 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 information6 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 informationT10/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 informationT r0 SAS Port Control State Diagram Update
1.1 Transport layer state diagrams 1.1.1 Overview The PC state machines interface with the link layer connection state machine(s) ( the SAS link end point connection state SS link state machines) and the
More informationBasic 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 informationADT 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 information03-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 informationRevision 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 informationNo book chapter for this topic! Slides are posted online as usual Homework: Will be posted online Due 12/6
Announcements No book chapter for this topic! Slides are posted online as usual Homework: Will be posted online Due 12/6 Copyright c 2002 2017 UMaine School of Computing and Information S 1 / 33 COS 140:
More informationAnnouncements. No book chapter for this topic! Slides are posted online as usual Homework: Will be posted online Due 12/6
Announcements No book chapter for this topic! Slides are posted online as usual Homework: Will be posted online Due 12/6 Copyright c 2002 2017 UMaine Computer Science Department 1 / 33 1 COS 140: Foundations
More informationSERIAL 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 informationLixia Zhang M. I. T. Laboratory for Computer Science December 1985
Network Working Group Request for Comments: 969 David D. Clark Mark L. Lambert Lixia Zhang M. I. T. Laboratory for Computer Science December 1985 1. STATUS OF THIS MEMO This RFC suggests a proposed protocol
More information4 July r1 SAS-2 Enable and disable zoning
To: T10 Technical Committee From: Rob Elliott, HP (elliott@hp.com) Date: 4 July 2006 Subject: 06-281r1 SAS-2 Enable and disable zoning Revision history Revision 0 (15 June 2006) First revision Revision
More informationTable 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 informationChapter 11 Data Link Control 11.1
Chapter 11 Data Link Control 11.1 Copyright The McGraw-Hill Companies, Inc. Permission required for reproduction or display. 11-1 FRAMING The data link layer needs to pack bits into frames, so that each
More informationClass 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 information2 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 informationELEN Network Fundamentals Lecture 15
ELEN 4017 Network Fundamentals Lecture 15 Purpose of lecture Chapter 3: Transport Layer Reliable data transfer Developing a reliable protocol Reliability implies: No data is corrupted (flipped bits) Data
More informationTo: 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 informationOverview 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 informationNetwork Protocols. Sarah Diesburg Operating Systems CS 3430
Network Protocols Sarah Diesburg Operating Systems CS 3430 Protocol An agreement between two parties as to how information is to be transmitted A network protocol abstracts packets into messages Physical
More informationHP 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 informationOpenLCB Technical Note. Datagram Transport. 1 Introduction. 2 Annotations to the Standard. 2.1 Introduction. 2.2 Intended Use
OpenLCB Technical Note Datagram Transport Feb 6, 2016 Adopted 5 10 15 20 25 1 Introduction This Technical Note contains informative discussion and background for the corresponding OpenLCB Datagram Transport
More informationChapter 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 informationUnit 2.
Unit 2 Unit 2 Topics Covered: 1. PROCESS-TO-PROCESS DELIVERY 1. Client-Server 2. Addressing 2. IANA Ranges 3. Socket Addresses 4. Multiplexing and Demultiplexing 5. Connectionless Versus Connection-Oriented
More informationChapter 3: Transport Layer
Chapter 3: Transport Layer Chapter goals: understand principles behind transport layer services: multiplexing/demultiplex ing reliable data transfer flow control congestion control instantiation and implementation
More informationTable 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 informationTCP: Flow and Error Control
1 TCP: Flow and Error Control Required reading: Kurose 3.5.3, 3.5.4, 3.5.5 CSE 4213, Fall 2006 Instructor: N. Vlajic TCP Stream Delivery 2 TCP Stream Delivery unlike UDP, TCP is a stream-oriented protocol
More informationCRC. Implementation. Error control. Software schemes. Packet errors. Types of packet errors
CRC Implementation Error control An Engineering Approach to Computer Networking Detects all single bit errors almost all 2-bit errors any odd number of errors all bursts up to M, where generator length
More informationThe 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 informationThe GBN sender must respond to three types of events:
Go-Back-N (GBN) In a Go-Back-N (GBN) protocol, the sender is allowed to transmit several packets (when available) without waiting for an acknowledgment, but is constrained to have no more than some maximum
More informationCMSC 417. Computer Networks Prof. Ashok K Agrawala Ashok Agrawala. October 11, 2018
CMSC 417 Computer Networks Prof. Ashok K Agrawala 2018 Ashok Agrawala Message, Segment, Packet, and Frame host host HTTP HTTP message HTTP TCP TCP segment TCP router router IP IP packet IP IP packet IP
More informationReliable Transport I: Concepts and TCP Protocol
Reliable Transport I: Concepts and TCP Protocol Brad Karp UCL Computer Science CS 3035/GZ01 29 th October 2013 Part I: Transport Concepts Layering context Transport goals Transport mechanisms 2 Context:
More informationHCA Tech Note 220: Using the SmartHome Insteon Hub
HCA Tech Note 220: Using the SmartHome Insteon Hub The Insteon Hub and the older 2412N are interesting products but they are not a 2413 PowerLinc with a network connection in a box. They are much different
More informationERROR AND FLOW CONTROL. Lecture: 10 Instructor Mazhar Hussain
ERROR AND FLOW CONTROL Lecture: 10 Instructor Mazhar Hussain 1 FLOW CONTROL Flow control coordinates the amount of data that can be sent before receiving acknowledgement It is one of the most important
More informationPRIMARY-BACKUP REPLICATION
PRIMARY-BACKUP REPLICATION Primary Backup George Porter Nov 14, 2018 ATTRIBUTION These slides are released under an Attribution-NonCommercial-ShareAlike 3.0 Unported (CC BY-NC-SA 3.0) Creative Commons
More informationAdd 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 informationCS 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 informationThe Data Link Layer Chapter 3
The Data Link Layer Chapter 3 Data Link Layer Design Issues Error Detection and Correction Elementary Data Link Protocols Sliding Window Protocols Example Data Link Protocols Revised: August 2011 & February
More informationTCP : 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 informationAnalyzation 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 informationOutline. CS5984 Mobile Computing
CS5984 Mobile Computing Dr. Ayman Abdel-Hamid Computer Science Department Virginia Tech Outline Review Transmission Control Protocol (TCP) Based on Behrouz Forouzan, Data Communications and Networking,
More information10.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 informationr5 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 informationCS419: 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 information22 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 informationCOMPUTER NETWORK. Homework #2. Due Date: April 12, 2017 in class
Computer Network Homework#2 COMPUTER NETWORK Homework #2 Due Date: April 12, 2017 in class Question 1 Suppose a process in Host C has a UDP socket with port number 6789. Suppose both Host A and Host B
More informationiscsi Error Recovery Mallikarjun Chadalapaka Randy Haagens Julian Satran London, 6-7 Aug 2001
iscsi Error Recovery Mallikarjun Chadalapaka Randy Haagens Julian Satran London, 6-7 Aug 2001 Why do we care? Error statistics an attempt to extrapolate (innovatively) from an experiment conducted at Stanford:
More informationChapter 11 Data Link Control 11.1
Chapter 11 Data Link Control 11.1 Copyright The McGraw-Hill Companies, Inc. Permission required for reproduction or display. 11-1 1 FRAMING The data link layer needs to pack bits into frames,, so that
More informationECE 435 Network Engineering Lecture 9
ECE 435 Network Engineering Lecture 9 Vince Weaver http://web.eece.maine.edu/~vweaver vincent.weaver@maine.edu 2 October 2018 Announcements HW#4 was posted, due Thursday 1 HW#3 Review md5sum/encryption,
More informationCS43: Computer Networks Reliable Data Transfer. Kevin Webb Swarthmore College October 5, 2017
CS43: Computer Networks Reliable Data Transfer Kevin Webb Swarthmore College October 5, 2017 Agenda Today: General principles of reliability Next time: details of one concrete, very popular protocol: TCP
More informationCS 43: Computer Networks. 16: Reliable Data Transfer October 8, 2018
CS 43: Computer Networks 16: Reliable Data Transfer October 8, 2018 Reading Quiz Lecture 16 - Slide 2 Last class We are at the transport-layer protocol! provide services to the application layer interact
More informationInternet 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 information04-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 informationChapter 11 Data Link Control 11.1
Chapter 11 Data Link Control 11.1 Copyright The McGraw-Hill Companies, Inc. Permission required for reproduction or display. 11-1 FRAMING The data link layer needs to pack bits into frames, so that each
More informationUNIT IV -- TRANSPORT LAYER
UNIT IV -- TRANSPORT LAYER TABLE OF CONTENTS 4.1. Transport layer. 02 4.2. Reliable delivery service. 03 4.3. Congestion control. 05 4.4. Connection establishment.. 07 4.5. Flow control 09 4.6. Transmission
More informationQuickBooks 2006 Network Installation Guide
QuickBooks 2006 Network Installation Guide Intuit 2/28/06 QuickBooks 2006 has a new way of managing company data that may require some changes in the way you install and configure the software for network
More information03-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 informationChapter 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 informationXP: Backup Your Important Files for Safety
XP: Backup Your Important Files for Safety X 380 / 1 Protect Your Personal Files Against Accidental Loss with XP s Backup Wizard Your computer contains a great many important files, but when it comes to
More informationChapter 3: Transport Layer. Chapter 3 Transport Layer. Chapter 3 outline. Transport services and protocols
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 informationTransport 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 informationReliable Transport I: Concepts and TCP Protocol
Reliable Transport I: Concepts and TCP Protocol Stefano Vissicchio UCL Computer Science COMP0023 Today Transport Concepts Layering context Transport goals Transport mechanisms and design choices TCP Protocol
More informationComputer 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 information04-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 informationNWEN 243. Networked Applications. Layer 4 TCP and UDP
NWEN 243 Networked Applications Layer 4 TCP and UDP 1 About the second lecturer Aaron Chen Office: AM405 Phone: 463 5114 Email: aaron.chen@ecs.vuw.ac.nz Transport layer and application layer protocols
More informationAll page numbers refer to the printed page number, not the PDF page number.
SPI-3 Revision 10 Letter Ballot Comments 28 October 1999 by Rob Elliott, Compaq Computer Corporation All page numbers refer to the printed page number, not the PDF page number. The first three comments
More informationLecture 10: Transpor Layer Principles of Reliable Data Transfer
Lecture 10: Transpor Layer Principles of Reliable Data Transfer COMP 332, Spring 2018 Victoria Manfredi Acknowledgements: materials adapted from Computer Networking: A Top Down Approach 7 th edition: 1996-2016,
More informationSTEVEN R. BAGLEY PACKETS
STEVEN R. BAGLEY PACKETS INTRODUCTION Talked about how data is split into packets Allows it to be multiplexed onto the network with data from other machines But exactly how is it split into packets and
More informationRelated 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 informationChapter 3. The Data Link Layer. Wesam A. Hatamleh
Chapter 3 The Data Link Layer The Data Link Layer Data Link Layer Design Issues Error Detection and Correction Elementary Data Link Protocols Sliding Window Protocols Example Data Link Protocols The Data
More informationDraft Minutes Automation/Drive Interface (ADI) Working Group Ad Hoc Teleconference T10/03-151r0 26 March :00 AM 10:00 AM PST
Draft Minutes Automation/Drive Interface (ADI) Working Group Ad Hoc Teleconference T10/03-151r0 26 March 2003 8:00 AM 10:00 AM PST Conference Call Information: Hosted by: Quantum Toll Free: (800) 668-7083
More information