Thanks for the note Muthuraman! How about reamaining parameters like MaxRecvDataSegmentLeng**th,TargetAlias?
We don't need to support above text requests? & Do you have any idea on how an initiator could send a blank text request to target because spec says initiator should send at least a blank text request when target sends an asynchronous PDU with an event of parameter negotiation on a specific text key? Thanks Vamsi On Thursday, September 12, 2013, Muthuraman wrote: > Hi Vamsi, > > I think we only specify the TargetName on FFP. > > If Text Req has "<TargetName=>" then target will send reply as > TargetName=<Session-Target-Iqn-name> > if Text Req has "<TargetName="Name of Target">" then target will send > reply as TargetName=<Session-Target-IQN-Name> > > If you want to know more info then refer the iSWAT tool descriptions. > > Regards, > Muthuraman > > > On Tue, Sep 10, 2013 at 4:47 PM, vamsi > <[email protected]<javascript:_e({}, 'cvml', > '[email protected]');> > > wrote: > >> Hello Open-iSCSI members, >> >> I have few queries on text request/response. >> >> 1. What are all possible text keys that could be send as part of >> individual text request(apart from sendtargets)? According to my RFC study >> following are the possible text keys that could be send as part of text >> request, please correct my understanding >> >> >> Ø *Text keys that can be used during login or full feature phase (All)* >> >> 1. InitiatorAlias(**Declarative ) >> >> 2. MaxRecvDataSegmentLeng**th (Declarative ) >> >> 3. TargetAddress (Declarative ) >> >> 4. TargetAlias(**Declarative ) >> >> 5. TargetName(**Declarative) - Target can send this in any stage >> >> Ø *Text keys that can be send only in full feature phase (FFPO)* >> >> 1. SendTargets >> >> 2. Vendor specific text requests >> >> 2. Under what circumstances do we need to support issuing text >> request(Apart from sendtargets text key) to a target in normal session(i.e. >> In full feature phase) with error recovery level 0 support. >> >> I would appreciate answers to these queries, thanks >> >> Thanks, >> Vamsi >> >> -- >> You received this message because you are subscribed to the Google Groups >> "open-iscsi" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:_e({}, >> 'cvml', 'open-iscsi%[email protected]');>. >> To post to this group, send email to >> [email protected]<javascript:_e({}, 'cvml', >> '[email protected]');> >> . >> Visit this group at http://groups.google.com/group/open-iscsi. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Regards, > Muthuraman > > -- > You received this message because you are subscribed to the Google Groups > "open-iscsi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:_e({}, > 'cvml', 'open-iscsi%[email protected]');>. > To post to this group, send email to > [email protected]<javascript:_e({}, 'cvml', > '[email protected]');> > . > Visit this group at http://groups.google.com/group/open-iscsi. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/groups/opt_out.
