It seems like the Reset-a line is being used to perform a Hard Reset. The Hard Reset in SAM does not affect the transport layer. So, I do not think that the port needs to get a new IP Address, etc - the second sentence sho\ uld be removed. This should not affect the Ethernet port or the Ethernet connections.
)/Type/Annot/Popup 3 0 R/Page 3>> endobj 6 0 obj <> endobj 7 0 obj <Is a DT device allowed to have two ADT Interconnect ports \(for example, one serial and one Ethernet\)? If this is allowed, this brings up several more questions: - How are interactions between the two ports handled?\ 3;- Is there one ADT Port for both ADT Interconnect ports or one ADT Port per ADT Interconnect port? - Can both ports be active at the same time? - How does the DT device determine which port to send an asynchronous request \(LUN1 command, VHF dat\ a, etc\) on when both ports are supported? - How are things like LUN reset, Reset-a, and Login handled? - How do we handle the initiator aspect - since these are two ports to the same device, and the initiator is implicit, are both treated as the \ same initiator or as two different initiators?
)/Type/Annot/Popup 6 0 R/Page 11>> endobj 9 0 obj <> endobj 10 0 obj <With iADT, is the initiator based on source IP address? or are all source IP Addresses treated as the same initiator? When the library has two IP Addresses which can be used to communicate with the DT device, the library ca\ n failover from one iADT Port to another \(ie, a different Ethernet connector/IP Address\). If the Local Port is listening, does the Local Port need to check the Remote Port \(for know/expected/last IP Address\) before using a new connection? Also, this\ affects how a Login works if a Login is persistent across connections.
)/Type/Annot/Popup 9 0 R/Page 11>> endobj 12 0 obj <> endobj 13 0 obj <Closed should be Disconnected. This requires a Login every time a new connection is made. Is that the intent? I thought the intent was to allow a login to last across connections.
)/Type/Annot/Popup 12 0 R/Page 11>> endobj 15 0 obj <> endobj 16 0 obj <It would be nice to show the reset line, since it is not necessarily on the same connector as Ethernet \(most likely not the same connector from the library side\).
)/Type/Annot/Popup 15 0 R/Page 11>> endobj 18 0 obj <> endobj 19 0 obj <The 13 should be probably be 15 - the next paragraph renumbers figure 9 to figure 15.
)/Type/Annot/Popup 18 0 R/Page 12>> endobj 21 0 obj <> endobj 22 0 obj <Since only one connection is allowed per ADT port, how are race conditions handled. In other words, if both sides issue a Connect at the same time, which one wins?
)/Type/Annot/Popup 21 0 R/Page 20>> endobj 24 0 obj <> endobj 25 0 obj <Should there be a service request to stop listening?
)/Type/Annot/Popup 24 0 R/Page 21>> endobj 27 0 obj <> endobj 28 0 obj <If there are multiple ADT ports listening on the same local port, which ADT port is sent the Connected? Should there be a way for a Listen request to optionally specify a remote port \(specific IP address but allow \ any port on the remote host\)? This would allow an ADT port to specify which remote ADT port it wants to communicate with. This can cause other issues \(such as a a new connection arrives that does not match any ADT Port's requested remote port\). &\ #13;Could broadcast the Connected to all listening port and let the listening port decide which one wants it, but that seems like it could cause a lot of confusion.
)/Type/Annot/Popup 27 0 R/Page 21>> endobj 30 0 obj <> endobj 31 0 obj <what happens to any data that has been received since the last Receive service request.
)/Type/Annot/Popup 30 0 R/Page 23>> endobj 33 0 obj <> endobj 34 0 obj <Is a login required after a Disconnected service indication? if so, when: - always? - sometimes \(based on Reason\)? - never? This affects the ability to keep a login across connections. It would be nice if \ the login stayed valid across a connection, but it is not clear to me if that is allowed or not.
)/Type/Annot/Popup 33 0 R/Page 23>> endobj 36 0 obj <> endobj 37 0 obj <It would be nice to specify if the Local Port and Remote Port are just the IP Address or an IP Address and Port. I seems like sometimes the port is included and sometimes it is not. For example, the Local Port on a Conn\ ect service request needs the IP Address and port, but the Remote Port on a Connect service request states that it is just the IP Address. Since the remote port is assumed to always be 4169, the port could be included for consistency and then the Local P\ ort and Remote Port would always be an IP Address and port.
)/Type/Annot/Popup 36 0 R/Page 26>> endobj 39 0 obj <> endobj 40 0 obj <The reasons listed do not match the reasons in the description of the service indication. Perhaps this should be changed to: "The reason that the connection was disconnected" This way, the list of reasons \ does not need to be updated in two places.
)/Type/Annot/Popup 39 0 R/Page 28>> endobj 42 0 obj <> endobj 43 0 obj <There is a condition here where the IP stack is still listening and there are no accepts. In this case, the other side might issue a Connect service request and get a Connected service indication before this side issues ano\ ther Listen service request. If that happens, one side will be connected while the other is not. This seems like it could cause a problem. One solution would be to close the listening socket after the accept returns a socket. Another solution wo\ uld be to send something on the interface to indicate that both sides acknowledge the socket as being connected. Another option is to ignore this situation and let the normal ADT error recovery handle this as a timeout. The side issuing the Connect r\ equest is connecting to send a frame, and will detect a problem when the ACK for the frame is not received.
)/Type/Annot/Popup 42 0 R/Page 30>> endobj 45 0 obj <> endobj 46 0 obj <since shutdown and close both delete the socket, this should be: After close\(\) or shutdown\(\) returns, the... Also, the connection may close for other reasons \(such as the other side closing the connection o\ r the Ethernet physical connection going away\). So, this should mention that there are other conditions that cause a Disconnected.
)/Type/Annot/Popup 45 0 R/Page 30>> endobj 48 0 obj <> endobj 49 0 obj <The description of shutdown states that it deletes the socket. So, either close\(\) or shutdown\(\) is needed, not both.
)/Type/Annot/Popup 48 0 R/Page 30>> endobj trailer <> %%EOF