From ips-bounces@ietf.org Wed Nov 5 22:50:37 2008 Return-Path: X-Original-To: ips-archive@optimus.ietf.org Delivered-To: ietfarch-ips-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 12C503A6946; Wed, 5 Nov 2008 22:50:37 -0800 (PST) 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 D41B93A6998 for ; Wed, 5 Nov 2008 08:05:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 SYXFIGK6nENv for ; Wed, 5 Nov 2008 08:05:36 -0800 (PST) Received: from yx-out-1718.google.com (yx-out-1718.google.com [74.125.44.153]) by core3.amsl.com (Postfix) with ESMTP id 52AA93A69F7 for ; Wed, 5 Nov 2008 08:05:36 -0800 (PST) Received: by yx-out-1718.google.com with SMTP id 34so31624yxf.70 for ; Wed, 05 Nov 2008 08:05:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=; b=JIybRixMlxmy2cF5E8oAJYF2mZ7czwbVCyR1t8KYm73EsksxdbeUeZ1XCyD26OsX9L ynlAs/1/OfH1WVn47ShCbMvMqMKBKH5j8DVzwLGLahyAlLrUnCOgQ5u3En5F897ZwyoM WtRuJmWVjpONyYXvUGNzB7WwEIb6SFQhDYsDQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=TF1rMOmlUOxpCeLYm2B89aqhj/PmoqeU2rMpi1X6LsxGJc7XD/Sbjo0WgyvLSRDKAV APzHRVoh+T9/1OHA/d6Rt+Fa8P09jNLwBeWVCKbRSMDX9uf2zwOXYdVqXCEg6tL3raI9 u2U8H9Vm9GG0xiUJVxoMEG2yoJX07aBn9ZwVs= Received: by 10.142.180.19 with SMTP id c19mr510522wff.322.1225901133156; Wed, 05 Nov 2008 08:05:33 -0800 (PST) Received: by 10.142.13.17 with HTTP; Wed, 5 Nov 2008 08:05:33 -0800 (PST) Message-ID: Date: Wed, 5 Nov 2008 18:05:33 +0200 From: "Erez Zilber" To: ips@core3.amsl.com MIME-Version: 1.0 Content-Disposition: inline Subject: [Ips] timeout for R2T PDUs? X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org _______________________________________________ Ips mailing list Ips@ietf.org https://www.ietf.org/mailman/listinfo/ips From ips-bounces@ietf.org Wed Nov 5 23:25:23 2008 Return-Path: X-Original-To: ips-archive@optimus.ietf.org Delivered-To: ietfarch-ips-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5483C3A6969; Wed, 5 Nov 2008 23:25:23 -0800 (PST) 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 00FE83A6969 for ; Wed, 5 Nov 2008 23:25:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.466 X-Spam-Level: X-Spam-Status: No, score=-2.466 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599] 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 zYlf8ErJ31U1 for ; Wed, 5 Nov 2008 23:25:22 -0800 (PST) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.224]) by core3.amsl.com (Postfix) with ESMTP id 75DAC3A6946 for ; Wed, 5 Nov 2008 23:25:20 -0800 (PST) Received: by rv-out-0506.google.com with SMTP id b25so459249rvf.49 for ; Wed, 05 Nov 2008 23:24:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=+3OpADYjsEGsi+EJKDsem4cIf9YzyF+Y2WKmTq9baRQ=; b=T4ThPpU9Gbr4sTkfLygTNklq7nszMJWTPzuAR19/pHyNaHw0WG10tpkaUhc/UMfgkW 4MM7vmBnm+203hCEjPUu6rBS+tjHvDUWUCU27n/pQM8zDHgP/EqfxAHU9XfAg+I2eHkz zprR4MCCQMOwsJF3Eg6U4LCJ+wyL5LlO6fWR0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=rZHGHhuFH+I4E0AyO3ayC0dEB84xk03LWcyK9JvU6HX+c9HA/3VrIDacoCBqrw/+Ty WczdexGwKfDBA6XwR5n1TK8keL1sb/c+Ll0tWjeua4PpOqMfUunnh3BAuKV7rMQzKIP7 7xZ66lsAYyQrNEOFsX9iIO5Aeu+xqkq4D+ie0= Received: by 10.141.136.19 with SMTP id o19mr985952rvn.230.1225956274495; Wed, 05 Nov 2008 23:24:34 -0800 (PST) Received: by 10.141.91.21 with HTTP; Wed, 5 Nov 2008 23:24:34 -0800 (PST) Message-ID: Date: Thu, 6 Nov 2008 09:24:34 +0200 From: "Erez Zilber" To: ips@ietf.org MIME-Version: 1.0 Content-Disposition: inline Subject: [Ips] timeout for R2T PDUs? X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org Hi, I couldn't find an answer to the following question in iSCSI spec: During the execution of a WRITE command, an R2T PDU is sent from the target to the initiator. What should happen if a bug in the initiator causes it not to send the data-out PDU? Is there any timeout that will allow the target to abort this command? Thanks, Erez _______________________________________________ Ips mailing list Ips@ietf.org https://www.ietf.org/mailman/listinfo/ips From ips-bounces@ietf.org Thu Nov 6 01:20:01 2008 Return-Path: X-Original-To: ips-archive@optimus.ietf.org Delivered-To: ietfarch-ips-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD6A13A69C4; Thu, 6 Nov 2008 01:20:01 -0800 (PST) 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 BC9033A69C4 for ; Thu, 6 Nov 2008 01:19:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 lugzhdoIiFLn for ; Thu, 6 Nov 2008 01:19:59 -0800 (PST) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175]) by core3.amsl.com (Postfix) with ESMTP id F07E33A69E8 for ; Thu, 6 Nov 2008 01:19:58 -0800 (PST) Received: by wf-out-1314.google.com with SMTP id 27so565359wfd.31 for ; Thu, 06 Nov 2008 01:19:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=RsTEuH//QFGul2fRpHXafVXTugUtmnreiF39DqnOO0M=; b=kl9GLge/fW9V6Wd1w72jUSsgZxzS5hk5uN6HwzFCgcwdx4WQ5/eVEMiEvG3N+4dqJx 411/uKs7/h3WRN4g48N4YPbFdg3Bvn5sPJ3+FK5M+cxvmZt2DWRrcjbLThxgfvIxJ5yP b04b6vWFf21SEjNUd3TLNf/nCgSnQPd2dmxPk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=gre0vLVt9VF7GFqgUblKC38tbYNUUIXHerdJquuTYZWkjdcL8043zjUcfMB+s0SBYR +M/3KHBaarDg0LzS80qKyLZjYXFm7UumZ5Ee3+TUFHNu3kUz7F+g/dmpNmX2nllYG+W4 YdMQJwvaiz43xZwtrIwUElrRVkTJ2XG+c4lSs= Received: by 10.142.214.11 with SMTP id m11mr344013wfg.279.1225963191782; Thu, 06 Nov 2008 01:19:51 -0800 (PST) Received: by 10.142.204.14 with HTTP; Thu, 6 Nov 2008 01:19:51 -0800 (PST) Message-ID: <8c87b47c0811060119i355671b7tef114a7f879ea44d@mail.gmail.com> Date: Thu, 6 Nov 2008 14:49:51 +0530 From: "Deva Ranganathan" To: "Erez Zilber" In-Reply-To: <8c87b47c0811060116s7cd827f2o820649d1ab08ddbd@mail.gmail.com> MIME-Version: 1.0 References: <8c87b47c0811060116s7cd827f2o820649d1ab08ddbd@mail.gmail.com> Cc: ips@ietf.org Subject: Re: [Ips] timeout for R2T PDUs? X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1417519460==" Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org --===============1417519460== Content-Type: multipart/alternative; boundary="----=_Part_23435_32276753.1225963191766" ------=_Part_23435_32276753.1225963191766 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Thu, Nov 6, 2008 at 2:46 PM, Deva Ranganathan wrote: > Erez, > > I think that this s a target implementation issue wherein the > implementation can choose the timeout depending on the availability of > resources and the software architecture. A target also has a NOP-IN sent > periodically and can use this to cleanup the stale resources as well. > > thanks > > Deva > HCL Technologies. > > > > On Thu, Nov 6, 2008 at 12:54 PM, Erez Zilber wrote: > >> Hi, >> >> I couldn't find an answer to the following question in iSCSI spec: >> >> During the execution of a WRITE command, an R2T PDU is sent from the >> target to the initiator. What should happen if a bug in the initiator >> causes it not to send the data-out PDU? Is there any timeout that will >> allow the target to abort this command? >> >> Thanks, >> Erez >> _______________________________________________ >> Ips mailing list >> Ips@ietf.org >> https://www.ietf.org/mailman/listinfo/ips >> > > ------=_Part_23435_32276753.1225963191766 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On Thu, Nov 6, 2008 at 2:46 PM, Deva Ranganathan <deva.ranganathan@gmail.com> wrote:
Erez,
 
I think that this s a target implementation issue wherein the implementation can choose the timeout  depending on the availability of resources  and the software architecture. A target also has a NOP-IN sent periodically and can use this to cleanup  the stale resources as well.
 
thanks
 
Deva
HCL Technologies.


 
On Thu, Nov 6, 2008 at 12:54 PM, Erez Zilber <erezzi.list@gmail.com> wrote:
Hi,

I couldn't find an answer to the following question in iSCSI spec:

During the execution of a WRITE command, an R2T PDU is sent from the
target to the initiator. What should happen if a bug in the initiator
causes it not to send the data-out PDU? Is there any timeout that will
allow the target to abort this command?

Thanks,
Erez
_______________________________________________
Ips mailing list
Ips@ietf.org
https://www.ietf.org/mailman/listinfo/ips


------=_Part_23435_32276753.1225963191766-- --===============1417519460== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ips mailing list Ips@ietf.org https://www.ietf.org/mailman/listinfo/ips --===============1417519460==-- From ips-bounces@ietf.org Thu Nov 6 05:11:02 2008 Return-Path: X-Original-To: ips-archive@optimus.ietf.org Delivered-To: ietfarch-ips-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 83D9D3A6992; Thu, 6 Nov 2008 05:11:02 -0800 (PST) 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 C98EA3A6992 for ; Thu, 6 Nov 2008 05:11:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.598 X-Spam-Level: X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] 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 V9LL6FVtjDp9 for ; Thu, 6 Nov 2008 05:11:00 -0800 (PST) Received: from mtagate8.de.ibm.com (mtagate8.de.ibm.com [195.212.29.157]) by core3.amsl.com (Postfix) with ESMTP id 9B1713A67F0 for ; Thu, 6 Nov 2008 05:11:00 -0800 (PST) Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate8.de.ibm.com (8.13.8/8.13.8) with ESMTP id mA6D9Y45540506 for ; Thu, 6 Nov 2008 13:09:34 GMT Received: from d12av02.megacenter.de.ibm.com (d12av02.megacenter.de.ibm.com [9.149.165.228]) by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id mA6D9YDW3694842 for ; Thu, 6 Nov 2008 14:09:34 +0100 Received: from d12av02.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av02.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id mA6D9YRp030486 for ; Thu, 6 Nov 2008 14:09:34 +0100 Received: from d12mc102.megacenter.de.ibm.com (d12mc102.megacenter.de.ibm.com [9.149.167.114]) by d12av02.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id mA6D9YaA030473 for ; Thu, 6 Nov 2008 14:09:34 +0100 In-Reply-To: <8c87b47c0811060119i355671b7tef114a7f879ea44d@mail.gmail.com> References: <8c87b47c0811060116s7cd827f2o820649d1ab08ddbd@mail.gmail.com> <8c87b47c0811060119i355671b7tef114a7f879ea44d@mail.gmail.com> To: "Deva Ranganathan" MIME-Version: 1.0 X-KeepSent: D31AFFD4:C22E4AE9-852574F9:004811FC; type=4; name=$KeepSent X-Mailer: Lotus Notes Build V85_09252008 September 25, 2008 From: Julian Satran Message-ID: Date: Thu, 6 Nov 2008 08:09:32 -0500 X-MIMETrack: Serialize by Router on D12MC102/12/M/IBM(Release 8.0.1|February 07, 2008) at 06/11/2008 15:09:34, Serialize complete at 06/11/2008 15:09:34 Cc: ips@ietf.org Subject: Re: [Ips] time-out for R2T PDUs? X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0983382183==" Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org This is a multipart message in MIME format. --===============0983382183== Content-Type: multipart/alternative; boundary="=_alternative 0048481B852574F9_=" This is a multipart message in MIME format. --=_alternative 0048481B852574F9_= Content-Type: text/plain; charset="US-ASCII" Correct - there is no standard time-out. Regards, Julo From: "Deva Ranganathan" To: "Erez Zilber" Cc: ips@ietf.org Date: 06/11/2008 04:20 Subject: Re: [Ips] timeout for R2T PDUs? On Thu, Nov 6, 2008 at 2:46 PM, Deva Ranganathan < deva.ranganathan@gmail.com> wrote: Erez, I think that this s a target implementation issue wherein the implementation can choose the timeout depending on the availability of resources and the software architecture. A target also has a NOP-IN sent periodically and can use this to cleanup the stale resources as well. thanks Deva HCL Technologies. On Thu, Nov 6, 2008 at 12:54 PM, Erez Zilber wrote: Hi, I couldn't find an answer to the following question in iSCSI spec: During the execution of a WRITE command, an R2T PDU is sent from the target to the initiator. What should happen if a bug in the initiator causes it not to send the data-out PDU? Is there any timeout that will allow the target to abort this command? Thanks, Erez _______________________________________________ Ips mailing list Ips@ietf.org https://www.ietf.org/mailman/listinfo/ips _______________________________________________ Ips mailing list Ips@ietf.org https://www.ietf.org/mailman/listinfo/ips --=_alternative 0048481B852574F9_= Content-Type: text/html; charset="US-ASCII" Correct - there is no standard time-out. Regards, Julo


From: "Deva Ranganathan" <deva.ranganathan@gmail.com>
To: "Erez Zilber" <erezzi.list@gmail.com>
Cc: ips@ietf.org
Date: 06/11/2008 04:20
Subject: Re: [Ips] timeout for R2T PDUs?
On Thu, Nov 6, 2008 at 2:46 PM, Deva Ranganathan <deva.ranganathan@gmail.com> wrote:
Erez,
 
I think that this s a target implementation issue wherein the implementation can choose the timeout  depending on the availability of resources  and the software architecture. A target also has a NOP-IN sent periodically and can use this to cleanup  the stale resources as well.
 
thanks
 
Deva
HCL Technologies.



On Thu, Nov 6, 2008 at 12:54 PM, Erez Zilber <erezzi.list@gmail.com> wrote:
Hi,

I couldn't find an answer to the following question in iSCSI spec:

During the execution of a WRITE command, an R2T PDU is sent from the
target to the initiator. What should happen if a bug in the initiator
causes it not to send the data-out PDU? Is there any timeout that will
allow the target to abort this command?

Thanks,
Erez
_______________________________________________
Ips mailing list
Ips@ietf.org
https://www.ietf.org/mailman/listinfo/ips

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

--=_alternative 0048481B852574F9_=-- --===============0983382183== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ips mailing list Ips@ietf.org https://www.ietf.org/mailman/listinfo/ips --===============0983382183==-- From ips-bounces@ietf.org Thu Nov 6 07:15:42 2008 Return-Path: X-Original-To: ips-archive@optimus.ietf.org Delivered-To: ietfarch-ips-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 058B43A68D1; Thu, 6 Nov 2008 07:15:42 -0800 (PST) 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 BEABC3A68D1 for ; Thu, 6 Nov 2008 07:15:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 IC6LpUMQj50m for ; Thu, 6 Nov 2008 07:15:40 -0800 (PST) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by core3.amsl.com (Postfix) with ESMTP id C46E83A6834 for ; Thu, 6 Nov 2008 07:15:39 -0800 (PST) Received: by yw-out-2324.google.com with SMTP id 3so299082ywj.49 for ; Thu, 06 Nov 2008 07:14:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=05GRaOsJ85LoEF5gHTDuQfXoH5is1HIHPE3Knf1WRy0=; b=jQugcaQLYrKjrQ60j/RGNI7h/LATTPRC3zFN8SBf3GBQnrAsEJ6e3OBNu/bl4U0l7V tuhPlXhrP4FAw56TaSpbmDyS+vNLM3tYiLBqT8cGgPm0Ooa9xEAmzd0AGUWW16UNHBe8 z9P25f5GsB1UK9QvCYG1QX4p8UR5mvcJkZpZc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=sqY/8I6jgGh2+qu5TMVCFC41jVmiPd14Vsj//H/R9qQ++TfwjCEBPDJK5lY/xSLKYD XNF9707cj3ab5gkLVyAAX/9/y2ft0ms/8/l6MBwVYuh0qfuWd73DoAo+ZgoMAqu6Ty9Y WnyUJ3oGXbj9ksnqXjb7ek/P5Ino00EEtEDxI= Received: by 10.143.8.11 with SMTP id l11mr505681wfi.178.1225984483162; Thu, 06 Nov 2008 07:14:43 -0800 (PST) Received: by 10.142.13.17 with HTTP; Thu, 6 Nov 2008 07:14:43 -0800 (PST) Message-ID: Date: Thu, 6 Nov 2008 17:14:43 +0200 From: "Erez Zilber" To: "Julian Satran" In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline References: <8c87b47c0811060116s7cd827f2o820649d1ab08ddbd@mail.gmail.com> <8c87b47c0811060119i355671b7tef114a7f879ea44d@mail.gmail.com> Cc: ips@ietf.org Subject: Re: [Ips] time-out for R2T PDUs? X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org There could be a situation in which NOP-IN PDUs from the target are sent successfully to the initiator, but some bug causes the initiator not to send the data-out PDU. According to what you say, the target may decide that it can't wait anymore and logout, right? Thanks, Erez On Thu, Nov 6, 2008 at 3:09 PM, Julian Satran wrote: > Correct - there is no standard time-out. Regards, Julo > > > From: "Deva Ranganathan" > To: "Erez Zilber" > Cc: ips@ietf.org > Date: 06/11/2008 04:20 > Subject: Re: [Ips] timeout for R2T PDUs? > ________________________________ > > > > > On Thu, Nov 6, 2008 at 2:46 PM, Deva Ranganathan > wrote: > Erez, > > I think that this s a target implementation issue wherein the implementation > can choose the timeout depending on the availability of resources and the > software architecture. A target also has a NOP-IN sent periodically and can > use this to cleanup the stale resources as well. > > thanks > > Deva > HCL Technologies. > > > > On Thu, Nov 6, 2008 at 12:54 PM, Erez Zilber wrote: > Hi, > > I couldn't find an answer to the following question in iSCSI spec: > > During the execution of a WRITE command, an R2T PDU is sent from the > target to the initiator. What should happen if a bug in the initiator > causes it not to send the data-out PDU? Is there any timeout that will > allow the target to abort this command? > > Thanks, > Erez > _______________________________________________ > Ips mailing list > Ips@ietf.org > https://www.ietf.org/mailman/listinfo/ips > > _______________________________________________ > Ips mailing list > Ips@ietf.org > https://www.ietf.org/mailman/listinfo/ips > > > _______________________________________________ Ips mailing list Ips@ietf.org https://www.ietf.org/mailman/listinfo/ips From ips-bounces@ietf.org Thu Nov 6 07:32:12 2008 Return-Path: X-Original-To: ips-archive@optimus.ietf.org Delivered-To: ietfarch-ips-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 324023A6981; Thu, 6 Nov 2008 07:32:12 -0800 (PST) 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 26AB13A68C1 for ; Thu, 6 Nov 2008 07:32:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.598 X-Spam-Level: X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] 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 j-FECNhthRoA for ; Thu, 6 Nov 2008 07:32:10 -0800 (PST) Received: from mtagate8.de.ibm.com (mtagate8.de.ibm.com [195.212.29.157]) by core3.amsl.com (Postfix) with ESMTP id B1F103A6849 for ; Thu, 6 Nov 2008 07:32:09 -0800 (PST) Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate8.de.ibm.com (8.13.8/8.13.8) with ESMTP id mA6FV7sl617770 for ; Thu, 6 Nov 2008 15:31:07 GMT Received: from d12av06.megacenter.de.ibm.com (d12av06.megacenter.de.ibm.com [9.149.165.230]) by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id mA6FV7O84165732 for ; Thu, 6 Nov 2008 16:31:07 +0100 Received: from d12av06.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av06.megacenter.de.ibm.com (8.13.1/8.13.3) with ESMTP id mA6FV6if006568 for ; Thu, 6 Nov 2008 16:31:06 +0100 Received: from d12mc102.megacenter.de.ibm.com (d12mc102.megacenter.de.ibm.com [9.149.167.114]) by d12av06.megacenter.de.ibm.com (8.13.1/8.12.11) with ESMTP id mA6FV65E006560 for ; Thu, 6 Nov 2008 16:31:06 +0100 In-Reply-To: References: <8c87b47c0811060116s7cd827f2o820649d1ab08ddbd@mail.gmail.com> <8c87b47c0811060119i355671b7tef114a7f879ea44d@mail.gmail.com> To: "Erez Zilber" MIME-Version: 1.0 X-KeepSent: FFDF794E:92D4D3FA-852574F9:0054E919; type=4; name=$KeepSent X-Mailer: Lotus Notes Build V85_09252008 September 25, 2008 From: Julian Satran Message-ID: Date: Thu, 6 Nov 2008 10:31:02 -0500 X-MIMETrack: Serialize by Router on D12MC102/12/M/IBM(Release 8.0.1|February 07, 2008) at 06/11/2008 17:31:06, Serialize complete at 06/11/2008 17:31:06 Cc: ips@ietf.org Subject: Re: [Ips] time-out for R2T PDUs? X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1176055621==" Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org This is a multipart message in MIME format. --===============1176055621== Content-Type: multipart/alternative; boundary="=_alternative 00553BF7852574F9_=" This is a multipart message in MIME format. --=_alternative 00553BF7852574F9_= Content-Type: text/plain; charset="US-ASCII" The target may try to finish the command with a "check condition" or some connection recovery before resorting to the big hammer. Julo From: "Erez Zilber" To: Julian Satran/Haifa/IBM@IBMIL Cc: "Deva Ranganathan" , ips@ietf.org Date: 06/11/2008 10:15 Subject: Re: [Ips] time-out for R2T PDUs? There could be a situation in which NOP-IN PDUs from the target are sent successfully to the initiator, but some bug causes the initiator not to send the data-out PDU. According to what you say, the target may decide that it can't wait anymore and logout, right? Thanks, Erez On Thu, Nov 6, 2008 at 3:09 PM, Julian Satran wrote: > Correct - there is no standard time-out. Regards, Julo > > > From: "Deva Ranganathan" > To: "Erez Zilber" > Cc: ips@ietf.org > Date: 06/11/2008 04:20 > Subject: Re: [Ips] timeout for R2T PDUs? > ________________________________ > > > > > On Thu, Nov 6, 2008 at 2:46 PM, Deva Ranganathan > wrote: > Erez, > > I think that this s a target implementation issue wherein the implementation > can choose the timeout depending on the availability of resources and the > software architecture. A target also has a NOP-IN sent periodically and can > use this to cleanup the stale resources as well. > > thanks > > Deva > HCL Technologies. > > > > On Thu, Nov 6, 2008 at 12:54 PM, Erez Zilber wrote: > Hi, > > I couldn't find an answer to the following question in iSCSI spec: > > During the execution of a WRITE command, an R2T PDU is sent from the > target to the initiator. What should happen if a bug in the initiator > causes it not to send the data-out PDU? Is there any timeout that will > allow the target to abort this command? > > Thanks, > Erez > _______________________________________________ > Ips mailing list > Ips@ietf.org > https://www.ietf.org/mailman/listinfo/ips > > _______________________________________________ > Ips mailing list > Ips@ietf.org > https://www.ietf.org/mailman/listinfo/ips > > > --=_alternative 00553BF7852574F9_= Content-Type: text/html; charset="US-ASCII" The target may try to finish the command with a "check condition" or some connection recovery before resorting  to the big hammer.

Julo


From: "Erez Zilber" <erezzi.list@gmail.com>
To: Julian Satran/Haifa/IBM@IBMIL
Cc: "Deva Ranganathan" <deva.ranganathan@gmail.com>, ips@ietf.org
Date: 06/11/2008 10:15
Subject: Re: [Ips] time-out for R2T PDUs?




There could be a situation in which NOP-IN PDUs from the target are
sent successfully to the initiator, but some bug causes the initiator
not to send the data-out PDU. According to what you say, the target
may decide that it can't wait anymore and logout, right?

Thanks,
Erez

On Thu, Nov 6, 2008 at 3:09 PM, Julian Satran <Julian_Satran@il.ibm.com> wrote:
> Correct - there is no standard time-out. Regards, Julo
>
>
> From: "Deva Ranganathan" <deva.ranganathan@gmail.com>
> To: "Erez Zilber" <erezzi.list@gmail.com>
> Cc: ips@ietf.org
> Date: 06/11/2008 04:20
> Subject: Re: [Ips] timeout for R2T PDUs?
> ________________________________
>
>
>
>
> On Thu, Nov 6, 2008 at 2:46 PM, Deva Ranganathan
> <deva.ranganathan@gmail.com> wrote:
> Erez,
>
> I think that this s a target implementation issue wherein the implementation
> can choose the timeout  depending on the availability of resources  and the
> software architecture. A target also has a NOP-IN sent periodically and can
> use this to cleanup  the stale resources as well.
>
> thanks
>
> Deva
> HCL Technologies.
>
>
>
> On Thu, Nov 6, 2008 at 12:54 PM, Erez Zilber <erezzi.list@gmail.com> wrote:
> Hi,
>
> I couldn't find an answer to the following question in iSCSI spec:
>
> During the execution of a WRITE command, an R2T PDU is sent from the
> target to the initiator. What should happen if a bug in the initiator
> causes it not to send the data-out PDU? Is there any timeout that will
> allow the target to abort this command?
>
> Thanks,
> Erez
> _______________________________________________
> Ips mailing list
> Ips@ietf.org
> https://www.ietf.org/mailman/listinfo/ips
>
> _______________________________________________
> Ips mailing list
> Ips@ietf.org
> https://www.ietf.org/mailman/listinfo/ips
>
>
>

--=_alternative 00553BF7852574F9_=-- --===============1176055621== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ips mailing list Ips@ietf.org https://www.ietf.org/mailman/listinfo/ips --===============1176055621==-- From ips-bounces@ietf.org Thu Nov 6 07:53:20 2008 Return-Path: X-Original-To: ips-archive@optimus.ietf.org Delivered-To: ietfarch-ips-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 068F93A6A53; Thu, 6 Nov 2008 07:53:20 -0800 (PST) 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 85DD83A6A2E for ; Thu, 6 Nov 2008 07:53:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 OoKKDPMAjowX for ; Thu, 6 Nov 2008 07:53:16 -0800 (PST) Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.187]) by core3.amsl.com (Postfix) with ESMTP id 712F03A6A2B for ; Thu, 6 Nov 2008 07:53:16 -0800 (PST) Received: by rn-out-0910.google.com with SMTP id m7so511323rnd.18 for ; Thu, 06 Nov 2008 07:53:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=ITryRsTQQ2NjgVWhT+0BVGOCgFrTkslPrcTK1/+1+5w=; b=RQn/l9qxojIDGwsxG9e0a7T0Auc3dHiKl0T4p9tx+dxDXJrckp6QoT/ETlcxhKEXSk XSRjP8IB1pC9RLfLbVTJZgqhj6aqfojPEXg4sYiJss9XdZID711/YOhI94UD7sySSDah /FOMquU2uWlRZ6socyl5yDo19kEBUvM/rdCBw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=CHkC7fSOgoEkmN0o5vGfpIpotJ7GzwDEYR8IXPEyq0db8dJ/70/4vvwB3T5giGOCPg 2Tg3+W6CM0fx56Zt6kmNyCWyx2lWdCgCvyRonnyNEL+KqmzGOiL+XxVJIVjkVH/xvtwE OY+iZpbtqBYaVSy0bkWcQkx061XGoKZ+k4MS8= Received: by 10.142.103.2 with SMTP id a2mr521314wfc.164.1225986792153; Thu, 06 Nov 2008 07:53:12 -0800 (PST) Received: by 10.142.13.17 with HTTP; Thu, 6 Nov 2008 07:53:12 -0800 (PST) Message-ID: Date: Thu, 6 Nov 2008 17:53:12 +0200 From: "Erez Zilber" To: "Julian Satran" In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline References: <8c87b47c0811060116s7cd827f2o820649d1ab08ddbd@mail.gmail.com> <8c87b47c0811060119i355671b7tef114a7f879ea44d@mail.gmail.com> Cc: ips@ietf.org Subject: Re: [Ips] time-out for R2T PDUs? X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org Got it. Thanks. Erez On Thu, Nov 6, 2008 at 5:31 PM, Julian Satran wrote: > The target may try to finish the command with a "check condition" or some > connection recovery before resorting to the big hammer. > > Julo > > > From: > "Erez Zilber" > To: Julian Satran/Haifa/IBM@IBMIL > Cc: "Deva Ranganathan" , ips@ietf.org > Date: 06/11/2008 10:15 > Subject: Re: [Ips] time-out for R2T PDUs? > ________________________________ > > > There could be a situation in which NOP-IN PDUs from the target are > sent successfully to the initiator, but some bug causes the initiator > not to send the data-out PDU. According to what you say, the target > may decide that it can't wait anymore and logout, right? > > Thanks, > Erez > > On Thu, Nov 6, 2008 at 3:09 PM, Julian Satran > wrote: >> Correct - there is no standard time-out. Regards, Julo >> >> >> From: "Deva Ranganathan" >> To: "Erez Zilber" >> Cc: ips@ietf.org >> Date: 06/11/2008 04:20 >> Subject: Re: [Ips] timeout for R2T PDUs? >> ________________________________ >> >> >> >> >> On Thu, Nov 6, 2008 at 2:46 PM, Deva Ranganathan >> wrote: >> Erez, >> >> I think that this s a target implementation issue wherein the >> implementation >> can choose the timeout depending on the availability of resources and >> the >> software architecture. A target also has a NOP-IN sent periodically and >> can >> use this to cleanup the stale resources as well. >> >> thanks >> >> Deva >> HCL Technologies. >> >> >> >> On Thu, Nov 6, 2008 at 12:54 PM, Erez Zilber >> wrote: >> Hi, >> >> I couldn't find an answer to the following question in iSCSI spec: >> >> During the execution of a WRITE command, an R2T PDU is sent from the >> target to the initiator. What should happen if a bug in the initiator >> causes it not to send the data-out PDU? Is there any timeout that will >> allow the target to abort this command? >> >> Thanks, >> Erez >> _______________________________________________ >> Ips mailing list >> Ips@ietf.org >> https://www.ietf.org/mailman/listinfo/ips >> >> _______________________________________________ >> Ips mailing list >> Ips@ietf.org >> https://www.ietf.org/mailman/listinfo/ips >> >> >> > > > _______________________________________________ Ips mailing list Ips@ietf.org https://www.ietf.org/mailman/listinfo/ips From junjunto1990@livingeconomics.org Fri Nov 7 08:31:23 2008 Return-Path: X-Original-To: ietfarch-ips-archive@core3.amsl.com Delivered-To: ietfarch-ips-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7EA6B3A69B8 for ; Fri, 7 Nov 2008 08:31:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -12.464 X-Spam-Level: X-Spam-Status: No, score=-12.464 tagged_above=-999 required=5 tests=[BAYES_80=2, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, GB_I_LETTER=-2, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_BR=0.955, HELO_EQ_DSL=1.129, HOST_EQ_BR=1.295, HTML_EXTRA_CLOSE=2.809, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_3=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1, SARE_UNI=0.591, TVD_RCVD_IP=1.931, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] 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 HSieHWi11p0d for ; Fri, 7 Nov 2008 08:31:22 -0800 (PST) Received: from 200-138-52-106.ctame705.dsl.brasiltelecom.net.br (200-138-132-57.ctame705.dsl.brasiltelecom.net.br [200.138.132.57]) by core3.amsl.com (Postfix) with ESMTP id 350EE3A6B58 for ; Fri, 7 Nov 2008 08:31:20 -0800 (PST) To: Subject: invoice From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20081107163121.350EE3A6B58@core3.amsl.com> Date: Fri, 7 Nov 2008 08:31:20 -0800 (PST)
Click Here!
About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

?2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 98052
From rians@mhs.ch Fri Nov 7 15:21:31 2008 Return-Path: X-Original-To: ietfarch-ips-archive@core3.amsl.com Delivered-To: ietfarch-ips-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 62DF328C14F for ; Fri, 7 Nov 2008 15:21:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -47.927 X-Spam-Level: X-Spam-Status: No, score=-47.927 tagged_above=-999 required=5 tests=[BAYES_60=1, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, GB_I_LETTER=-2, HELO_DYNAMIC_IPADDR2=4.395, HTML_EXTRA_CLOSE=2.809, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_3=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_UNI=0.591, TVD_RCVD_IP=1.931, URIBL_BLACK=20, URIBL_JP_SURBL=10, USER_IN_WHITELIST=-100] 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 6X-ADQNbyGFz for ; Fri, 7 Nov 2008 15:21:30 -0800 (PST) Received: from 75-40-22-161.lightspeed.plcnca.sbcglobal.net (75-40-22-161.lightspeed.plcnca.sbcglobal.net [75.40.22.161]) by core3.amsl.com (Postfix) with ESMTP id 7C3F028C103 for ; Fri, 7 Nov 2008 15:21:29 -0800 (PST) To: Subject: order From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20081107232130.7C3F028C103@core3.amsl.com> Date: Fri, 7 Nov 2008 15:21:29 -0800 (PST)
Click Here!
About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

?2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 98052
From ips-bounces@ietf.org Tue Nov 11 01:02:56 2008 Return-Path: X-Original-To: ips-archive@optimus.ietf.org Delivered-To: ietfarch-ips-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A9E183A6974; Tue, 11 Nov 2008 01:02:56 -0800 (PST) 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 5C1B03A68F3 for ; Tue, 11 Nov 2008 01:02:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 WZJpOTLNYA8b for ; Tue, 11 Nov 2008 01:02:54 -0800 (PST) Received: from col0-omc4-s12.col0.hotmail.com (col0-omc4-s12.col0.hotmail.com [65.55.34.214]) by core3.amsl.com (Postfix) with ESMTP id 137D73A6AF2 for ; Tue, 11 Nov 2008 01:02:54 -0800 (PST) Received: from COL108-W21 ([65.55.34.200]) by col0-omc4-s12.col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 11 Nov 2008 01:02:51 -0800 Message-ID: X-Originating-IP: [218.185.19.242] From: Ken Sandars To: , Date: Tue, 11 Nov 2008 20:02:51 +1100 Importance: Normal In-Reply-To: References: <8c87b47c0811060116s7cd827f2o820649d1ab08ddbd@mail.gmail.com> <8c87b47c0811060119i355671b7tef114a7f879ea44d@mail.gmail.com> MIME-Version: 1.0 X-OriginalArrivalTime: 11 Nov 2008 09:02:51.0673 (UTC) FILETIME=[46D0E090:01C943DC] Cc: ips@ietf.org Subject: Re: [Ips] time-out for R2T PDUs? X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1213633693==" Sender: ips-bounces@ietf.org Errors-To: ips-bounces@ietf.org --===============1213633693== Content-Type: multipart/alternative; boundary="_33416548-8381-4f2d-a6f1-9e5769ff59e7_" --_33416548-8381-4f2d-a6f1-9e5769ff59e7_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Erez=2C Another option the target has is the recovery R2T as an attempt to provoke = the initiator into action. Cheers Ken > Date: Thu=2C 6 Nov 2008 17:53:12 +0200 > From: erezzi.list@gmail.com > To: Julian_Satran@il.ibm.com > CC: ips@ietf.org > Subject: Re: [Ips] time-out for R2T PDUs? >=20 > Got it. Thanks. >=20 > Erez >=20 > On Thu=2C Nov 6=2C 2008 at 5:31 PM=2C Julian Satran wrote: > > The target may try to finish the command with a "check condition" or so= me > > connection recovery before resorting to the big hammer. > > > > Julo > > > > > > From: > > "Erez Zilber" > > To: Julian Satran/Haifa/IBM@IBMIL > > Cc: "Deva Ranganathan" =2C ips@ietf.org > > Date: 06/11/2008 10:15 > > Subject: Re: [Ips] time-out for R2T PDUs? > > ________________________________ > > > > > > There could be a situation in which NOP-IN PDUs from the target are > > sent successfully to the initiator=2C but some bug causes the initiator > > not to send the data-out PDU. According to what you say=2C the target > > may decide that it can't wait anymore and logout=2C right? > > > > Thanks=2C > > Erez > > > > On Thu=2C Nov 6=2C 2008 at 3:09 PM=2C Julian Satran > > wrote: > >> Correct - there is no standard time-out. Regards=2C Julo > >> > >> > >> From: "Deva Ranganathan" > >> To: "Erez Zilber" > >> Cc: ips@ietf.org > >> Date: 06/11/2008 04:20 > >> Subject: Re: [Ips] timeout for R2T PDUs? > >> ________________________________ > >> > >> > >> > >> > >> On Thu=2C Nov 6=2C 2008 at 2:46 PM=2C Deva Ranganathan > >> wrote: > >> Erez=2C > >> > >> I think that this s a target implementation issue wherein the > >> implementation > >> can choose the timeout depending on the availability of resources an= d > >> the > >> software architecture. A target also has a NOP-IN sent periodically an= d > >> can > >> use this to cleanup the stale resources as well. > >> > >> thanks > >> > >> Deva > >> HCL Technologies. > >> > >> > >> > >> On Thu=2C Nov 6=2C 2008 at 12:54 PM=2C Erez Zilber > >> wrote: > >> Hi=2C > >> > >> I couldn't find an answer to the following question in iSCSI spec: > >> > >> During the execution of a WRITE command=2C an R2T PDU is sent from the > >> target to the initiator. What should happen if a bug in the initiator > >> causes it not to send the data-out PDU? Is there any timeout that will > >> allow the target to abort this command? > >> > >> Thanks=2C > >> Erez > >> _______________________________________________ > >> Ips mailing list > >> Ips@ietf.org > >> https://www.ietf.org/mailman/listinfo/ips > >> > >> _______________________________________________ > >> Ips mailing list > >> Ips@ietf.org > >> https://www.ietf.org/mailman/listinfo/ips > >> > >> > >> > > > > > > > _______________________________________________ > Ips mailing list > Ips@ietf.org > https://www.ietf.org/mailman/listinfo/ips _________________________________________________________________ Time for change? Find your ideal job with SEEK. http://a.ninemsn.com.au/b.aspx?URL=3Dhttp%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau= %2F%3Ftracking%3Dsk%3Atl%3Ask%3Anine%3A0%3Ahottag%3Achange&_t=3D757263783&_= r=3DSEEK_tagline&_m=3DEXT= --_33416548-8381-4f2d-a6f1-9e5769ff59e7_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Erez=2C

Another option the target has is the recovery R2T as an a= ttempt to provoke the initiator into action.

Cheers
Ken

&g= t=3B Date: Thu=2C 6 Nov 2008 17:53:12 +0200
>=3B From: erezzi.list@gma= il.com
>=3B To: Julian_Satran@il.ibm.com
>=3B CC: ips@ietf.org>=3B Subject: Re: [Ips] time-out for R2T PDUs?
>=3B
>=3B Got = it. Thanks.
>=3B
>=3B Erez
>=3B
>=3B On Thu=2C Nov 6= =2C 2008 at 5:31 PM=2C Julian Satran <=3BJulian_Satran@il.ibm.com>=3B w= rote:
>=3B >=3B The target may try to finish the command with a "che= ck condition" or some
>=3B >=3B connection recovery before resorting= to the big hammer.
>=3B >=3B
>=3B >=3B Julo
>=3B >= =3B
>=3B >=3B
>=3B >=3B From:
>=3B >=3B "Erez Zilber" = <=3Berezzi.list@gmail.com>=3B
>=3B >=3B To: Julian Satran/Haifa/= IBM@IBMIL
>=3B >=3B Cc: "Deva Ranganathan" <=3Bdeva.ranganathan@gm= ail.com>=3B=2C ips@ietf.org
>=3B >=3B Date: 06/11/2008 10:15
&g= t=3B >=3B Subject: Re: [Ips] time-out for R2T PDUs?
>=3B >=3B ____= ____________________________
>=3B >=3B
>=3B >=3B
>=3B &g= t=3B There could be a situation in which NOP-IN PDUs from the target are>=3B >=3B sent successfully to the initiator=2C but some bug causes th= e initiator
>=3B >=3B not to send the data-out PDU. According to wha= t you say=2C the target
>=3B >=3B may decide that it can't wait anym= ore and logout=2C right?
>=3B >=3B
>=3B >=3B Thanks=2C
>= =3B >=3B Erez
>=3B >=3B
>=3B >=3B On Thu=2C Nov 6=2C 2008 a= t 3:09 PM=2C Julian Satran <=3BJulian_Satran@il.ibm.com>=3B
>=3B &= gt=3B wrote:
>=3B >=3B>=3B Correct - there is no standard time-out= . Regards=2C Julo
>=3B >=3B>=3B
>=3B >=3B>=3B
>=3B &= gt=3B>=3B From: "Deva Ranganathan" <=3Bdeva.ranganathan@gmail.com>=3B=
>=3B >=3B>=3B To: "Erez Zilber" <=3Berezzi.list@gmail.com>=3B=
>=3B >=3B>=3B Cc: ips@ietf.org
>=3B >=3B>=3B Date: 06/11= /2008 04:20
>=3B >=3B>=3B Subject: Re: [Ips] timeout for R2T PDUs?=
>=3B >=3B>=3B ________________________________
>=3B >=3B&g= t=3B
>=3B >=3B>=3B
>=3B >=3B>=3B
>=3B >=3B>=3B>=3B >=3B>=3B On Thu=2C Nov 6=2C 2008 at 2:46 PM=2C Deva Ranganatha= n
>=3B >=3B>=3B <=3Bdeva.ranganathan@gmail.com>=3B wrote:
&= gt=3B >=3B>=3B Erez=2C
>=3B >=3B>=3B
>=3B >=3B>=3B I = think that this s a target implementation issue wherein the
>=3B >= =3B>=3B implementation
>=3B >=3B>=3B can choose the timeout dep= ending on the availability of resources and
>=3B >=3B>=3B the
= >=3B >=3B>=3B software architecture. A target also has a NOP-IN sent = periodically and
>=3B >=3B>=3B can
>=3B >=3B>=3B use this= to cleanup the stale resources as well.
>=3B >=3B>=3B
>=3B = >=3B>=3B thanks
>=3B >=3B>=3B
>=3B >=3B>=3B Deva
&= gt=3B >=3B>=3B HCL Technologies.
>=3B >=3B>=3B
>=3B >= =3B>=3B
>=3B >=3B>=3B
>=3B >=3B>=3B On Thu=2C Nov 6=2C = 2008 at 12:54 PM=2C Erez Zilber <=3Berezzi.list@gmail.com>=3B
>=3B= >=3B>=3B wrote:
>=3B >=3B>=3B Hi=2C
>=3B >=3B>=3B>=3B >=3B>=3B I couldn't find an answer to the following question in= iSCSI spec:
>=3B >=3B>=3B
>=3B >=3B>=3B During the execu= tion of a WRITE command=2C an R2T PDU is sent from the
>=3B >=3B>= =3B target to the initiator. What should happen if a bug in the initiator>=3B >=3B>=3B causes it not to send the data-out PDU? Is there any = timeout that will
>=3B >=3B>=3B allow the target to abort this com= mand?
>=3B >=3B>=3B
>=3B >=3B>=3B Thanks=2C
>=3B >= =3B>=3B Erez
>=3B >=3B>=3B _____________________________________= __________
>=3B >=3B>=3B Ips mailing list
>=3B >=3B>=3B I= ps@ietf.org
>=3B >=3B>=3B https://www.ietf.org/mailman/listinfo/ip= s
>=3B >=3B>=3B
>=3B >=3B>=3B ___________________________= ____________________
>=3B >=3B>=3B Ips mailing list
>=3B >= =3B>=3B Ips@ietf.org
>=3B >=3B>=3B https://www.ietf.org/mailman/= listinfo/ips
>=3B >=3B>=3B
>=3B >=3B>=3B
>=3B >=3B= >=3B
>=3B >=3B
>=3B >=3B
>=3B >=3B
>=3B _______= ________________________________________
>=3B Ips mailing list
>= =3B Ips@ietf.org
>=3B https://www.ietf.org/mailman/listinfo/ips
Find your ideal job with SEEK Time for change? = --_33416548-8381-4f2d-a6f1-9e5769ff59e7_-- --===============1213633693== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ips mailing list Ips@ietf.org https://www.ietf.org/mailman/listinfo/ips --===============1213633693==-- From jonster@altell.net Thu Nov 27 05:39:07 2008 Return-Path: X-Original-To: ietfarch-ips-archive@core3.amsl.com Delivered-To: ietfarch-ips-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 17C213A6832 for ; Thu, 27 Nov 2008 05:39:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.981 X-Spam-Level: X-Spam-Status: No, score=-15.981 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_EQ_TR=0.935, HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RDNS_NONE=0.1, SARE_HTML_A_BODY=0.742, SARE_HTML_IMG_ONLY=1.666, TVD_SPACE_RATIO=2.219, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] 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 bY4Sr9DU35fJ for ; Thu, 27 Nov 2008 05:39:06 -0800 (PST) Received: from al-kor.com.tr (unknown [88.230.42.205]) by core3.amsl.com (Postfix) with SMTP id 4A9E43A68A2 for ; Thu, 27 Nov 2008 05:39:04 -0800 (PST) To: Subject: Delivery Status Notification (Failure) From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20081127133905.4A9E43A68A2@core3.amsl.com> Date: Thu, 27 Nov 2008 05:39:04 -0800 (PST) Click here to view as a webpage From lhernand@aisd.net Thu Nov 27 09:54:57 2008 Return-Path: X-Original-To: ietfarch-ips-archive@core3.amsl.com Delivered-To: ietfarch-ips-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 916A028C159 for ; Thu, 27 Nov 2008 09:54:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.399 X-Spam-Level: X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_99=3.5, HELO_EQ_DYNAMIC=1.144, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1, SARE_HTML_A_BODY=0.742, SARE_HTML_IMG_ONLY=1.666, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_PH_SURBL=1.787, URIBL_SBL=20, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] 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 Q7hH3KGwi5lf for ; Thu, 27 Nov 2008 09:54:57 -0800 (PST) Received: from host220-116-dynamic.59-82-r.retail.telecomitalia.it (host220-116-dynamic.59-82-r.retail.telecomitalia.it [82.59.116.220]) by core3.amsl.com (Postfix) with SMTP id DC8FA28C12C for ; Thu, 27 Nov 2008 09:54:55 -0800 (PST) To: Subject: RE: Order 69017 From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20081127175455.DC8FA28C12C@core3.amsl.com> Date: Thu, 27 Nov 2008 09:54:55 -0800 (PST) Click here From mario.tombolininn@agrileasing.it Thu Nov 27 11:34:55 2008 Return-Path: X-Original-To: ietfarch-ips-archive@core3.amsl.com Delivered-To: ietfarch-ips-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 58D5A3A6A46 for ; Thu, 27 Nov 2008 11:34:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -35.445 X-Spam-Level: X-Spam-Status: No, score=-35.445 tagged_above=-999 required=5 tests=[BAYES_99=3.5, GB_I_LETTER=-2, HELO_EQ_DE=0.35, HELO_EQ_DSL=1.129, HTML_EXTRA_CLOSE=2.809, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] 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 lGJv6b3CGauH for ; Thu, 27 Nov 2008 11:34:54 -0800 (PST) Received: from e176186185.adsl.alicedsl.de (e176186185.adsl.alicedsl.de [85.176.186.185]) by core3.amsl.com (Postfix) with SMTP id 181093A6A3E for ; Thu, 27 Nov 2008 11:34:51 -0800 (PST) To: Subject: your value arises so high From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20081127193453.181093A6A3E@core3.amsl.com> Date: Thu, 27 Nov 2008 11:34:51 -0800 (PST)
About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 98052
From orporas@abacusinfo.com Sat Nov 29 20:44:38 2008 Return-Path: X-Original-To: ietfarch-ips-archive@core3.amsl.com Delivered-To: ietfarch-ips-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 34BA73A67F0 for ; Sat, 29 Nov 2008 20:44:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -42.757 X-Spam-Level: X-Spam-Status: No, score=-42.757 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_RELAY_NODNS=1.451, GB_I_LETTER=-2, HTML_EXTRA_CLOSE=2.809, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RDNS_NONE=0.1, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, USER_IN_WHITELIST=-100] 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 VukA41HKSteC for ; Sat, 29 Nov 2008 20:44:32 -0800 (PST) Received: from anb.com.sa (unknown [93.177.170.110]) by core3.amsl.com (Postfix) with SMTP id 81DFA3A68F1 for ; Sat, 29 Nov 2008 20:44:29 -0800 (PST) To: Subject: mass kidnapping From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20081130044431.81DFA3A68F1@core3.amsl.com> Date: Sat, 29 Nov 2008 20:44:29 -0800 (PST)
About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 98052
From josh@allengooch.com Sun Nov 30 23:21:49 2008 Return-Path: X-Original-To: ietfarch-ips-archive@core3.amsl.com Delivered-To: ietfarch-ips-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D99463A6905 for ; Sun, 30 Nov 2008 23:21:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -33.574 X-Spam-Level: X-Spam-Status: No, score=-33.574 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, GB_I_LETTER=-2, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_RU=0.595, HOST_EQ_RU=0.875, HTML_EXTRA_CLOSE=2.809, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, USER_IN_WHITELIST=-100] 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 Fpq5SrBy82cS for ; Sun, 30 Nov 2008 23:21:49 -0800 (PST) Received: from ppp91-76-43-19.pppoe.mtu-net.ru (ppp91-76-43-19.pppoe.mtu-net.ru [91.76.43.19]) by core3.amsl.com (Postfix) with SMTP id D72083A6896 for ; Sun, 30 Nov 2008 23:21:47 -0800 (PST) To: Subject: Smokeless tobacco - true and lies From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20081201072147.D72083A6896@core3.amsl.com> Date: Sun, 30 Nov 2008 23:21:47 -0800 (PST)
About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 98052