|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: iscsi : changes involving tgt portal group tag.
- To: IPS Reflector <ips@ece.cmu.edu>
- Subject: RE: iscsi : changes involving tgt portal group tag.
- From: "KRUEGER,MARJORIE (HP-Roseville,ex1)" <marjorie_krueger@hp.com>
- Date: Tue, 12 Mar 2002 19:12:47 -0500
- Content-Type: multipart/alternative;boundary="----_=_NextPart_001_01C1CA23.CE538250"
- Sender: owner-ips@ece.cmu.edu
Perhaps we should discuss this in Minneapolis. I agree with
Santosh, TPG should be added to the login message to verify that this is the
intended target port. I don't see how that is interpreted as "discovery
territory", since it's just the initiator explicitly identifying the intended
target port. Currently a login contains initiator and target names, and
initiator port number (ISID), so adding target port number is consistent.
There's still room in the login header, and this wouldn't break any current
implementations. Why is this a problem?
Marjorie Krueger Networked Storage
Architecture Networked Storage Solutions Org. Hewlett-Packard tel: +1
916 785 2656 fax: +1 916 785 0391 email: marjorie_krueger@hp.com
I
did not hear compelling arguments for it and it drags us even more into
discovery teritory - Julo
| Santosh Rao
<santoshr@cup.hp.com> Sent by: santoshr@hpcuhe.cup.hp.com
12-03-02 21:04 Please respond to Santosh Rao
| To:
Julian Satran/Haifa/IBM@IBMIL cc:
IPS Reflector <ips@ece.cmu.edu> Subject:
Re: iscsi : changes involving tgt portal group
tag.
|
What is the closure on this issue ? Will the Target Portal Group
Tag be a part of the login request ?
- Santosh
>
(assuming we have the TPGT in the Login Request PDU),
--
################################## Santosh Rao Software Design
Engineer, HP-UX iSCSI Driver Team, Hewlett Packard, Cupertino. email
: santoshr@cup.hp.com Phone :
408-447-3751 ##################################
Home
Last updated: Tue Mar 12 23:18:32 2002
9079 messages in chronological order
|