|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: iSCSI: scope of keysThis key must be sent on the first login request on every connection - it is part of the session identity. Julo "Eddy Quicksall" <Eddy_Quicksall@iV To: Julian Satran/Haifa/IBM@IBMIL, ivity.com> <ips@ece.cmu.edu> cc: 18-12-01 17:25 Subject: RE: iSCSI: scope of keys IO means "only during login". It does not mean "connection only". 13 TargetName Use: IO by initiator ALL by target, Declarative This key must be provided by the initiator of the TCP connection to the remote endpoint in the first login request ... So, here is a case where it is session wide ... so IO cannot mean "connection only" (I assume that since TargetName is not LO, then it must be ok to send this key for each connection). Eddy -----Original Message----- From: Julian Satran [mailto:Julian_Satran@il.ibm.com] Sent: Friday, December 14, 2001 3:50 PM To: ips@ece.cmu.edu Subject: Re: iSCSI: scope of keys Eddy, I think the text says it - but if people love headers better I can add it (some voices needed). Julo "Eddy Quicksall" <Eddy_Quicksall@ivivity.com> Sent by: owner-ips@ece.cmu.edu 14-12-01 22:12 To: "ips@ece. cmu. edu \(E-mail\)" <ips@ece.cmu.edu> cc: Subject: iSCSI: scope of keys Would it make sense to add a "scope" to each key definition? The IO and LO "use:" labels almost do that but not in all cases. For example: SW = Session wide CO = Connection only Use: IO Who can send: Initiator Scope: SW Key=<value> Eddy
Home Last updated: Thu Dec 20 14:17:47 2001 8169 messages in chronological order |