Re: [imss] [Ips] Storage Maintenance (storm) BOF reminder & requests

Lars Eggert <lars.eggert@nokia.com> Thu, 12 March 2009 09:35 UTC

Return-Path: <lars.eggert@nokia.com>
X-Original-To: imss@core3.amsl.com
Delivered-To: imss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DFBEC3A67CC; Thu, 12 Mar 2009 02:35:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.995
X-Spam-Level:
X-Spam-Status: No, score=-1.995 tagged_above=-999 required=5 tests=[AWL=0.605, BAYES_00=-2.599, NO_RELAYS=-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 vHaeHAPNVcz8; Thu, 12 Mar 2009 02:35:47 -0700 (PDT)
Received: from mail.fit.nokia.com (unknown [IPv6:2001:2060:40:1::123]) by core3.amsl.com (Postfix) with ESMTP id 2B2203A63D3; Thu, 12 Mar 2009 02:35:46 -0700 (PDT)
Received: from [IPv6:2001:2060:40:2:219:e3ff:fe06:dc74] ([IPv6:2001:2060:40:2:219:e3ff:fe06:dc74]) (authenticated bits=0) by mail.fit.nokia.com (8.14.3/8.14.3) with ESMTP id n2C9a9eQ011568 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 12 Mar 2009 11:36:10 +0200 (EET) (envelope-from lars.eggert@nokia.com)
Message-Id: <341DF3E8-58A4-46B3-9324-1B6DCB549D6E@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: Black_David@emc.com
In-Reply-To: <9FA859626025B64FBC2AF149D97C944A01F736BA@CORPUSMX80A.corp.emc.com>
Content-Type: multipart/signed; boundary=Apple-Mail-102-845332165; micalg=sha1; protocol="application/pkcs7-signature"
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Thu, 12 Mar 2009 11:36:09 +0200
References: <9FA859626025B64FBC2AF149D97C944A01F736BA@CORPUSMX80A.corp.emc.com>
X-Mailer: Apple Mail (2.930.3)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (mail.fit.nokia.com [IPv6:2001:2060:40:1::123]); Thu, 12 Mar 2009 11:36:10 +0200 (EET)
X-Virus-Scanned: ClamAV 0.94.2/9098/Thu Mar 12 09:20:36 2009 on fit.nokia.com
X-Virus-Status: Clean
X-Mailman-Approved-At: Thu, 12 Mar 2009 08:05:45 -0700
Cc: "imss@ietf.org" <imss@ietf.org>, "ips@ietf.org" <ips@ietf.org>, "rddp@ietf.org" <rddp@ietf.org>
Subject: Re: [imss] [Ips] Storage Maintenance (storm) BOF reminder & requests
X-BeenThere: imss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Internet and Management Support for Storage Working Group <imss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/imss>, <mailto:imss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imss>
List-Post: <mailto:imss@ietf.org>
List-Help: <mailto:imss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imss>, <mailto:imss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Mar 2009 09:35:49 -0000

FYI, the IESG is in the process of figuring out if a more useful  
remote participation mechanism can be set up for SF than our usual  
audio streaming and jabber room. If that can be done, STORM may want  
to make use of it, given that some of your key folks won't be attending.

On 2009-3-12, at 1:28, Black_David@emc.com wrote:

> This is a reminder that the Storage Maintenance BOF will
> be held in about 2 weeks at the IETF meetings in San Francisco.
> Please plan to attend if you're interested:
>
> THURSDAY, March 26, 2009
> Continental 1&2  	TSV  	storm  	 Storage Maintenance BOF
>
> The BOF description is at:
> http://www.ietf.org/mail-archive/web/ips/current/msg02669.html
>
> The initial agenda is here:
> http://www.ietf.org/mail-archive/web/ips/current/msg02670.html
>
> I'm going to go upload that initial agenda as the BOF agenda,
> and it can be bashed at the meeting.
>
> The primary purpose of this BOF is to answer two questions:
> (1) What storage maintenance work (IP Storage, Remote Direct
> 	Data Placement) should be done?
> (2) Should an IETF Working Group be formed to undertake that
> 	work?
>
> Everyone gets to weigh in on these decisions, even those who
> can't attend the BOF meeting.  Anyone who thinks that there is
> work that should be done, and who cannot come to the BOF meeting
> should say so on the IPS or RDDP mailing lists (and it'd be a
> good idea for those who can come to do this).  As part of the
> email, please indicate how you're interested in helping (author
> or co-author of specific drafts, promise to review and comment
> on specific drafts).
>
> Here's a summary of the initial draft list of work items:
> - iSCSI: Combine RFCs into one document, removing unused features.
> - iSCSI: Interoperability report on what has been implemented and
> 	interoperates in support of Draft Standard status for iSCSI.
> - iSCSI: Add backwards-compatible features to support SAM-4.
> - iFCP: The Address Translation mode of iFCP needs to be deprecated.
> - RDDP MPA: Small startup update for MPI application support.
> - iSER: A few minor updates based on InfiniBand experience.
>
> Additional work (e.g., updated/improved iSNS for iSCSI, MIB changes,
> updated ipsec security profile [i.e., IKEv2-based]) is possible if
> there's interest.
>
> There are (at least) four possible outcomes:
> (A) None of this work needs to be done.
> (B) There are some small work items that make sense.  Individual
> 	drafts with a draft shepherd (i.e., David Black) will
> 	suffice.
> (C) A working group is needed to undertake more complex work
> 	items and reach consensus on design issues.  The WG can
> 	be "virtual" and operate mostly via the mailing list
> 	until/unless controversial/contentious issues arise.
> (D) There is a lot of complex work that is needed, and a WG
> 	that will plan to meet at every IETF meeting should be
> 	formed.
>
> Please note that the IETF "rough consensus" process requires a
> working group in practice to be effective.  This makes outcome
> (C) look attractive to me, as:
> - I'm coming under increasing pressure to limit travel, and
> 	the next two IETF meetings after San Francisco are not
> 	in the US.
> - I'd rather have the "rough consensus" process available and
> 	not need it than need it and not have it available.
>
> Setting an example for how to express interest ...
>
> ---------------
> I think that the iSCSI single RFC and interoperability report are
> good ideas, but I want to see a bunch of people expressing interest
> in these, as significant effort is involved.  It might make sense
> to do the single iSCSI RFC but put off the interoperability report
> (the resulting RFC would remain at Proposed Standard rather than
> going to Draft Standard), as I'm not hearing about major iSCSI
> interoperability issues.
>
> I think the latter four items (SAM-4 for iSCSI, deprecate iFCP
> address translation, MPI fix to MPA and iSER fixes) should all
> be done.
>
> I plan to author the iFCP address translation deprecation draft,
> and review all other drafts.
>
> I think that a virtual WG should be formed that plans to do its
> work primarily via the mailing list.  I believe the SAM-4 work
> by itself is complex enough to need a working group - I would
> expect design issues to turn up at least there and in determining
> whether to remove certain iSCSI features, but I'm cautiously
> optimistic that the mailing list is sufficient to work these
> issues out (and concerned that travel restrictions are likely to
> force use of the mailing list).
>
> -----------------
>
> Ok, who wants to go next?
>
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> black_david@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------
> _______________________________________________
> Ips mailing list
> Ips@ietf.org
> https://www.ietf.org/mailman/listinfo/ips