Re: [storm] iSER update request from Bob Russell

Lars Eggert <lars.eggert@nokia.com> Sat, 17 October 2009 08:52 UTC

Return-Path: <lars.eggert@nokia.com>
X-Original-To: storm@core3.amsl.com
Delivered-To: storm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC3FC3A68A1 for <storm@core3.amsl.com>; Sat, 17 Oct 2009 01:52:24 -0700 (PDT)
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=[AWL=0.000, 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 IHf5f9nSdUex for <storm@core3.amsl.com>; Sat, 17 Oct 2009 01:52:24 -0700 (PDT)
Received: from mail.fit.nokia.com (mail.fit.nokia.com [195.148.124.195]) by core3.amsl.com (Postfix) with ESMTP id BBA613A6862 for <storm@ietf.org>; Sat, 17 Oct 2009 01:52:23 -0700 (PDT)
Received: from [10.0.1.5] (cs95024.pp.htv.fi [212.90.95.24]) (authenticated bits=0) by mail.fit.nokia.com (8.14.3/8.14.3) with ESMTP id n9H8qCDw005685 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 17 Oct 2009 11:52:12 +0300 (EEST) (envelope-from lars.eggert@nokia.com)
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: multipart/signed; boundary="Apple-Mail-9-436942362"; protocol="application/pkcs7-signature"; micalg="sha1"
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <9FA859626025B64FBC2AF149D97C944A040BF6E1@CORPUSMX80A.corp.emc.com>
Date: Sat, 17 Oct 2009 11:52:12 +0300
Message-Id: <4E07A891-645B-437A-99EB-8CAB99C16184@nokia.com>
References: <E265A5696240423CB3579D112E454FDB@china.huawei.com> <9FA859626025B64FBC2AF149D97C944A040BF6DA@CORPUSMX80A.corp.emc.com> <D8CEBB6AE9D43848BD2220619A43F3263EB434@M31.equallogic.com> <9FA859626025B64FBC2AF149D97C944A040BF6E1@CORPUSMX80A.corp.emc.com>
To: Black_David@emc.com
X-Mailer: Apple Mail (2.1076)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (mail.fit.nokia.com [195.148.124.194]); Sat, 17 Oct 2009 11:52:13 +0300 (EEST)
Cc: "Paul_Koning@Dell.com" <Paul_Koning@Dell.com>, "storm@ietf.org" <storm@ietf.org>
Subject: Re: [storm] iSER update request from Bob Russell
X-BeenThere: storm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Storage Maintenance WG <storm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/storm>, <mailto:storm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/storm>
List-Post: <mailto:storm@ietf.org>
List-Help: <mailto:storm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/storm>, <mailto:storm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Oct 2009 08:52:24 -0000

Hi,

On 2009-10-17, at 4:00, Black_David@emc.com wrote:
> If this is the case, then here (and for any other case
> in which all the implementations diverged from the spec), the new  
> draft
> will need to be very clear that the spec is being revised incompatibly
> *because* all the implementations looked at the old RFC and did  
> something
> different, and it's interoperability with those implementations that
> matters.

let me quickly chime in there, to give some background. If we're  
intending to move iSER forward to Draft/Full Standard, the IESG needs  
to receive an iSER interop report. Features that don't interop (e.g.,  
because they haven't been implemented by a sufficient number of  
stacks) cannot move forward to Draft/Full Standard. So bringing the  
RFC text in line with reality is needed to elevate iSER up the  
Standards Track.

Lars