Re: [Ips] iSCSI-specific unit attention conditions
Paul Koning <Paul_Koning@dell.com> Mon, 30 March 2009 15:38 UTC
Return-Path: <Paul_Koning@Dell.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 040623A691E for <ips@core3.amsl.com>; Mon, 30 Mar 2009 08:38:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.832
X-Spam-Level:
X-Spam-Status: No, score=-103.832 tagged_above=-999 required=5 tests=[AWL=-1.419, BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4, RCVD_IN_NJABL_RELAY=2.696, 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 QByAv7upqY5a for <ips@core3.amsl.com>; Mon, 30 Mar 2009 08:38:14 -0700 (PDT)
Received: from aussmtpmrkps320.us.dell.com (aussmtpmrkps320.us.dell.com [143.166.224.254]) by core3.amsl.com (Postfix) with ESMTP id 411BC3A67B1 for <ips@ietf.org>; Mon, 30 Mar 2009 08:38:13 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.38,446,1233554400"; d="scan'208";a="392774044"
Received: from unknown (HELO M31.equallogic.com) ([12.110.134.31]) by aussmtpmrkps320.us.dell.com with SMTP; 30 Mar 2009 10:39:11 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <18896.59292.932521.584069@gargle.gargle.HOWL>
Date: Mon, 30 Mar 2009 11:39:08 -0400
From: Paul Koning <Paul_Koning@dell.com>
To: Black_David@emc.com
References: <9FA859626025B64FBC2AF149D97C944A023F8427@CORPUSMX80A.corp.emc.com>
X-Mailer: VM 7.17 under 21.4 (patch 22) "Instant Classic" XEmacs Lucid
X-OriginalArrivalTime: 30 Mar 2009 15:39:07.0682 (UTC) FILETIME=[A9D73020:01C9B14D]
Cc: ips@ietf.org
Subject: Re: [Ips] iSCSI-specific unit attention conditions
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: Mon, 30 Mar 2009 15:38:15 -0000
I am somewhat puzzled by the notion of T10 defining iSCSI things. Did
these things receive any discussion on the IPS list? If not,
shouldn't that happen first?
It seems to me that IPS should ask T10 for iSCSI related changes, not
the other way around. And nothing should be added without a
description of how it is supposed to be used.
paul
- [Ips] iSCSI-specific unit attention conditions Black_David
- Re: [Ips] iSCSI-specific unit attention conditions Paul Koning
- Re: [Ips] iSCSI-specific unit attention conditions Black_David
- Re: [Ips] iSCSI-specific unit attention conditions Paul Koning
- Re: [Ips] iSCSI-specific unit attention conditions Paul Koning
- Re: [Ips] iSCSI-specific unit attention conditions brown_David1
- Re: [Ips] iSCSI-specific unit attention conditions Knight, Frederick
- Re: [Ips] iSCSI-specific unit attention conditions Knight, Frederick
- Re: [Ips] iSCSI-specific unit attention conditions dcuddihy
- Re: [Ips] iSCSI-specific unit attention conditions Paul Koning
- Re: [Ips] iSCSI-specific unit attention conditions Knight, Frederick
- Re: [Ips] iSCSI-specific unit attention conditions Kevin_Marks
- Re: [Ips] iSCSI-specific unit attention conditions Black_David
- Re: [Ips] iSCSI-specific unit attention conditions Bill Galloway
- Re: [Ips] iSCSI-specific unit attention conditions Julian Satran
- Re: [Ips] iSCSI-specific unit attention conditions Ralph Weber