Re: LUN field in R2T

[Julian Satran <Julian_Satran@xxxxxxxxxx>]

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

Sears_Bill@xxxxxxx

01/02/08 11:57 PM

To	<ips@xxxxxxxx>
cc
Subject	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
Ips@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ips

_______________________________________________
Ips mailing list
Ips@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ips