[Ips] Data-In ExpDataSN
yushang <yusunn@gmail.com> Fri, 25 September 2009 06:29 UTC
Return-Path: <yusunn@gmail.com>
X-Original-To: ips@core3.amsl.com
Delivered-To: ips@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4740028C0F3 for <ips@core3.amsl.com>; Thu, 24 Sep 2009 23:29:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.415
X-Spam-Level:
X-Spam-Status: No, score=-0.415 tagged_above=-999 required=5 tests=[AWL=-0.231, BAYES_40=-0.185, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SLNqv9wam5Za for <ips@core3.amsl.com>; Thu, 24 Sep 2009 23:29:39 -0700 (PDT)
Received: from mail-px0-f183.google.com (mail-px0-f183.google.com [209.85.216.183]) by core3.amsl.com (Postfix) with ESMTP id 6F5353A688A for <ips@ietf.org>; Thu, 24 Sep 2009 23:29:39 -0700 (PDT)
Received: by pxi13 with SMTP id 13so2832395pxi.6 for <ips@ietf.org>; Thu, 24 Sep 2009 23:30:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=TLLuF3cexCMYHu1HM5xMN2NVf90x2f7BUJ9nXQ4hQZo=; b=EwTU0422k6LB0cY5OGbhUsDjvGe9+mQsLm/50JZ5KyWlXbn6la+PSnICx2Pz3o2nMK RzhEqmfXEUrQYrGTfzwCFpHqNQFJ5X9Fx9h3ImHTRRvCBP2swa1Hib/w/L7lJgZhIQH0 2qgUH29wbGUaja8lL3lJLWPD4Stqq4vJ4B0E8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=i5cfkcwkEgNtA7n09aF3E6k55ex+CUQBjJ/yXrJoIS1Aw/r7CG5zuVohAtx0ZfNkcn vunrkD5f9MnV0ja7gTgQeXohckaZLIW+dSHBKjLgLTYRC9L0X35+Ic2usHD3LvEhlzb9 /yznHV71liFnegVZVZXWMrv4qOvTxt//bw3lM=
MIME-Version: 1.0
Received: by 10.142.67.5 with SMTP id p5mr349465wfa.286.1253860246297; Thu, 24 Sep 2009 23:30:46 -0700 (PDT)
Date: Fri, 25 Sep 2009 14:30:46 +0800
Message-ID: <298d852f0909242330o15ff44bdg85c0c436ad603755@mail.gmail.com>
From: yushang <yusunn@gmail.com>
To: ips@ietf.org
Content-Type: multipart/alternative; boundary="001636e0ba2a941d2b0474611619"
Subject: [Ips] Data-In ExpDataSN
X-BeenThere: ips@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IP Storage <ips.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ips>
List-Post: <mailto:ips@ietf.org>
List-Help: <mailto:ips-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2009 06:29:40 -0000
Dear all , RFC 3720 says that Data-In/R2T PDU number is acknowledged by ExpDataSN filed of SCSI Response . But if a target choose to send a Data-In PDU with S bit set instead of a SCSI Response . Where to get the ExpDataSN ? There is no such a field in Data-In PDU. Many thanks.
- [Ips] Data-In ExpDataSN yushang
- Re: [Ips] Data-In ExpDataSN Black_David