SORT BY:

LIST ORDER
THREAD
AUTHOR
SUBJECT


SEARCH

IPS HOME


    [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

    Re: iSCSI Naming and Discovery



    
    
    John Hufferd/San Jose/IBM wrote:
    > 
    > David Robinson,
    > I hope you mean  "...an out of band naming issue that need" NOT "to be
    > exposed in the iSCSI protocol.".
    
    Opps, I mistyped and you are correct.
    
    	-David
    > 
    > .
    > .
    > .
    > John L. Hufferd
    > Senior Technical Staff Member (STSM)
    > IBM/SSG San Jose Ca
    > (408) 256-0403, Tie: 276-0403
    > Internet address: hufferd@us.ibm.com
    > 
    > David Robinson <David.Robinson@EBay.Sun.COM>@ece.cmu.edu on 10/06/2000
    > 02:15:53 PM
    > 
    > Sent by:  owner-ips@ece.cmu.edu
    > 
    > To:   ips@ece.cmu.edu
    > cc:
    > Subject:  Re: iSCSI Naming and Discovery
    > 
    > Jim Hafner/Almaden/IBM wrote:
    > > You wrote:
    > > >I would propose that the information required for #1 is the IP address
    > > >and port number as well as an inband representation of the LU.
    > >
    > > I'm still trying to figure out where inband representation of LU is
    > > required in this context.
    > 
    > The confusion is my fault, I confused threads of discussion and read
    > "target" as "LU", you further correctly described that the determination
    > of the LU is an existing SCSI to SCSI function. The partial source of
    > my confusion is others wishing to lookup the LU in a nameservice,
    > not just the target.  But that is an out of band naming issue that
    > need to be exposed in the iSCSI protocol.
    > 
    > [Bunch of stuff I agree with deleted]
    > 
    > > (Sorry if this comes across too strong! -- maybe it's just a bad day!)
    > 
    > Maybe, but then I don't know you that well! :-)
    > 
    > Again, my fault, we are in complete agreement.
    > 
    >      -David
    


Home

Last updated: Tue Sep 04 01:06:47 2001
6315 messages in chronological order