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

Send Reject PDU when orignal to-be-rejected PDU is not available

To: <ips@xxxxxxxx>
Subject: Send Reject PDU when orignal to-be-rejected PDU is not available
From: HUJason <hzj_wuying@xxxxxxxxxxx>
Date: Wed, 16 Apr 2008 09:58:32 +0800
Delivered-to: ips@xxxxxxxxxxxxxx
Importance: Normal
In-reply-to: <OFA528E763.71479425-ON8525742C.005B02F4-8825742C.005F18F1@xxxxxxxxxx>
References: <4804B03C.6060507@xxxxxxxxxxxx> <OFA528E763.71479425-ON8525742C.005B02F4-8825742C.005F18F1@xxxxxxxxxx>
Sender: ips-bounces@xxxxxxxx

Dears,

I am curently implement iscsi target on a resource-limted device. In my implementation, orignal to-be-rejected PDU is not available when it realised that a Reject should be sent to initiator.

But as RFC3720 said, Target must send back the orignal PDU as the Reject's payload.

So my question is: Why we need to send back the orignal PDU ? Can we simply eliminate it?

Thanks!

Best Regards,

Jason

“七件武器，七种完美” 立刻体验！

_______________________________________________
Ips mailing list
Ips@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ips

Follow-Ups:
- Write residual scenario
  - From: HUJason
- How to deal with PROTOCOL ERROR on iscsi target side
  - From: HUJason
- Re: Send Reject PDU when orignal to-be-rejected PDU is notavailable
  - From: Black_David

References:
- Calculating the VA in iSER header
  - From: Erez Zilber
- Re: Calculating the VA in iSER header
  - From: Mike Ko

Prev by Date: Re: Calculating the VA in iSER header
Next by Date: Re: Send Reject PDU when orignal to-be-rejected PDU is notavailable
Previous by thread: Re: Calculating the VA in iSER header
Next by thread: Re: Send Reject PDU when orignal to-be-rejected PDU is notavailable
Index(es):
- Date
- Thread

[IETF] [Linux iSCSI] [Linux SCSI] [Linux Resources] [Yosemite News] [IETF Announcements] [IETF Discussion] [SCSI]