Return-Path: <owner-ips-outgoing@ece.cmu.edu>
X-Sieve: cmu-sieve 2.0
Return-Path: <owner-ips-outgoing@ece.cmu.edu>
Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h4NKGS301162
	for <ipsml@ece.cmu.edu>; Fri, 23 May 2003 16:16:28 -0400 (EDT)
Received: by bache.ece.cmu.edu (Postfix, from userid 953)
	id A260089; Fri, 23 May 2003 16:16:27 -0400 (EDT)
Received: from sos.ece.cmu.edu (SOS.ECE.CMU.EDU [128.2.129.27])
	by bache.ece.cmu.edu (Postfix) with ESMTP
	id 024FD7A; Fri, 23 May 2003 16:16:19 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix)
	id DFBE6894F; Fri, 23 May 2003 16:16:03 -0400 (EDT)
Received: from hazard.ece.cmu.edu (HAZARD.ECE.CMU.EDU [128.2.129.24])
	by sos.ece.cmu.edu (Postfix) with ESMTP id CF79C893D
	for <ips-outgoing@sos.ece.cmu.edu>; Fri, 23 May 2003 16:16:03 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix)
	id AE70297; Fri, 23 May 2003 16:16:03 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id 91BC599; Fri, 23 May 2003 16:16:03 -0400 (EDT)
Received: from sos.ece.cmu.edu (SOS.ECE.CMU.EDU [128.2.129.27])
	by hazard.ece.cmu.edu (Postfix) with ESMTP id CC3C097
	for <ips-outgoing@ece.cmu.edu>; Fri, 23 May 2003 16:16:00 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix, from userid 363)
	id A0CA78950; Fri, 23 May 2003 16:16:00 -0400 (EDT)
X-Original-To: ips@sos.ece.cmu.edu
Received: from hazard.ece.cmu.edu (HAZARD.ECE.CMU.EDU [128.2.129.24])
	by sos.ece.cmu.edu (Postfix) with ESMTP id 972D2893D
	for <ips@sos.ece.cmu.edu>; Fri, 23 May 2003 16:15:58 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix)
	id 318B697; Fri, 23 May 2003 16:15:58 -0400 (EDT)
Delivered-To: ips@ece.cmu.edu
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id 1083A99; Fri, 23 May 2003 16:15:58 -0400 (EDT)
Received: from palrel13.hp.com (palrel13.hp.com [156.153.255.238])
	by hazard.ece.cmu.edu (Postfix) with ESMTP id 23B4997
	for <ips@ece.cmu.edu>; Fri, 23 May 2003 16:15:55 -0400 (EDT)
Received: from xparelay1.ptp.hp.com (xparelay1.ptp.hp.com [15.1.28.62])
	by palrel13.hp.com (Postfix) with ESMTP
	id 9D3E91C01388; Fri, 23 May 2003 13:15:54 -0700 (PDT)
Received: from xpabh3.ptp.hp.com (xpabh3.ptp.hp.com [15.1.28.63])
	by xparelay1.ptp.hp.com (Postfix) with ESMTP
	id 394F7100557C; Fri, 23 May 2003 13:15:54 -0700 (PDT)
Received: by xpabh3.ptp.hp.com with Internet Mail Service (5.5.2655.55)
	id <JWGMTMNL>; Fri, 23 May 2003 13:15:54 -0700
Message-ID: <6BD67FFB937FD411A04F00D0B74FE878102F61EC@xrose06.rose.hp.com>
From: "KRUEGER,MARJORIE (HP-Roseville,ex1)" <marjorie.krueger@hp.com>
To: "'Eddy Quicksall'" <eddy_quicksall@ivivity.com>,
   "Ips@Ece.Cmu.Edu (ips@ece.cmu.edu)" <ips@ece.cmu.edu>
Subject: RE: iSCSI: TargetPortalGroupTag for discovery
Date: Fri, 23 May 2003 13:15:53 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C32168.1C3E5BB0"
Sender: owner-ips@ece.cmu.edu
Precedence: bulk
X-Spam-Status: No, hits=-11.3 required=5.0
	tests=BAYES_10,HTML_60_70,HTML_FONT_COLOR_BLUE,
	      HTML_FONT_FACE_ODD,ORIGINAL_MESSAGE
	version=2.50
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C32168.1C3E5BB0
Content-Type: text/plain

I think the wording in the spec says TargetPortalGroupTag should be included
in the Login response.  It seems that a discovery session where multiple
targets are being serviced by the same IP address is a case where
TargetPortalGroupTag need not be reported?  The intent behind reporting
TargetPortalGroupTag is directed towards Full Feature Sessions so that the
initiator can verify that it's discovery information is still valid.
-----Original Message-----
From: Eddy Quicksall [mailto:eddy_quicksall@ivivity.com] 
Sent: Friday, May 23, 2003 1:03 PM
To: Ips@Ece.Cmu.Edu (ips@ece.cmu.edu)
Subject: iSCSI: TargetPortalGroupTag for discovery


I have a question regarding the determination of the Target Portal Group Tag
during a discovery session when the TargetName is not supplied.
 
The TargetPortalGroupTag must be reported in the first Login Response for
all session types. But without the TargetName, how does the network entity
determine which Target Portal Group Tag to report if two different targets
in the network entity are using the same IP Address/TCP Port?
 
Eddy
 

------_=_NextPart_001_01C32168.1C3E5BB0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 6.00.2722.900" name=3DGENERATOR>
<META content=3D"Microsoft Word 10" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C32144.BA8D9700" rel=3DFile-List><!--[if gte =
mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
  </w:Compatibility>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>@font-face {
	font-family: Verdana;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; =
mso-header-margin: .5in; mso-footer-margin: .5in; mso-paper-source: 0; =
}
P.MsoNormal {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Verdana; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-bidi-font-family: =
"Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Verdana; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-bidi-font-family: =
"Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Verdana; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-bidi-font-family: =
"Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial; mso-bidi-font-family: Arial; =
mso-style-type: personal-compose; mso-style-noshow: yes; =
mso-ansi-font-size: 10.0pt; mso-bidi-font-size: 10.0pt; =
mso-ascii-font-family: Arial; mso-hansi-font-family: Arial
}
SPAN.SpellE {
	mso-style-name: ""; mso-spl-e: yes
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]--></HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in" vLink=3Dpurple =
link=3Dblue>
<DIV><SPAN class=3D587440620-23052003><FONT face=3DGeorgia =
color=3D#0000ff size=3D2>I=20
think the wording in the spec says TargetPortalGroupTag <EM>should</EM> =
be=20
included in the Login response.&nbsp; It seems that a discovery session =

where&nbsp;multiple targets are being&nbsp;serviced by the same&nbsp;IP =
address=20
is a case where TargetPortalGroupTag need not be reported?&nbsp; The =
intent=20
behind reporting TargetPortalGroupTag is directed towards Full Feature =
Sessions=20
so that the initiator can verify that it's discovery information is =
still=20
valid.</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> =
Eddy Quicksall=20
  [mailto:eddy_quicksall@ivivity.com] <BR><B>Sent:</B> Friday, May 23, =
2003 1:03=20
  PM<BR><B>To:</B> Ips@Ece.Cmu.Edu (ips@ece.cmu.edu)<BR><B>Subject:</B> =
iSCSI:=20
  TargetPortalGroupTag for discovery<BR><BR></FONT></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I have a question =
regarding the=20
  determination of the Target Portal Group Tag during a discovery =
session when=20
  the TargetName is not supplied.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The =
TargetPortalGroupTag must be=20
  reported in the first Login Response for all session types. But =
without the=20
  TargetName, how does the network entity determine which Target Portal =
Group=20
  Tag to report if two different targets in the network entity are =
using the=20
  same IP Address/TCP Port?<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-no-proof: =
yes">Eddy</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DVerdana size=3D2><SPAN=20
  style=3D"FONT-SIZE: =
10pt"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTM=
L>

------_=_NextPart_001_01C32168.1C3E5BB0--