Re: LUN field in R2T
Julian Satran <[email protected]> Thu, 3 Jan 2008 14:41:32 +0530
| Newsgroups | gmane.ietf.ips |
|---|---|
| Message-ID | <OF8D1DE537.DC30EE1A-ON652573C5.0031D1BD-652573C5.00327ECA@il.ibm.com> |
Your interpretation is more liberal than the text says. The reason for requiring a LUN field in the first place was to remove the requirement for a target-wide unique TTT and enable distributed targets that do not require coordination. The reason LUN was chosen to tag the R2T is that it may simplify routing of the data to the appropriate destination. But since it is called LUN some zealous initiator may check (although it is not mandated) the LUN validity versus a list obtained otherwise - so I would not go for a very liberal interpretation. Julo [email protected] 01/02/08 11:57 PM To <[email protected]> cc Subject [Ips] LUN field in R2T Just a quick clarification: 10.8.5. Target Transfer Tag [...]The Target Transfer Tag and LUN are copied in the outgoing data PDUs and are only used by the target. Does this mean that the LUN field in the R2T does not need to contain the actual LUN number specified by the SCSI write? Since the field is ?only used by the target? I assume this text means that the target may place anything it wants in the LUN field of the R2T and have it echoed back by the initiator. _______________________________________________ Ips mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ips _______________________________________________ Ips mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ips