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

"Mallikarjun C." <cb_mallikarjun@yahoo.com> Sun, 15 March 2009 00:47 UTC

Return-Path: <cb_mallikarjun@yahoo.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 2141D3A6A07 for <imss@core3.amsl.com>; Sat, 14 Mar 2009 17:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level:
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 V38lgVmGT1jH for <imss@core3.amsl.com>; Sat, 14 Mar 2009 17:47:09 -0700 (PDT)
Received: from web110801.mail.gq1.yahoo.com (web110801.mail.gq1.yahoo.com [67.195.13.224]) by core3.amsl.com (Postfix) with SMTP id 1A92A3A6AAE for <imss@ietf.org>; Sat, 14 Mar 2009 17:47:09 -0700 (PDT)
Received: (qmail 61670 invoked by uid 60001); 15 Mar 2009 00:47:49 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1237078069; bh=GAIMXLVqp3UlWf3e+C6CUEmc6SYP7E9Hs09QcdV3sQs=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=wykAaqcJE389lfwp21sZ/5eup7FHj1ZsJZAnIkk6tkzsM+/+SF8ZpIuyTVhvym0CTH3GXx+tnz+sDZMj8JtPdKV3NtLjmmJEO+TtItjbBEXASxoaJyM8pIssbG8XMV80jgnJxwmJU6ZGOVdEdnTrWUFYsmaPRCvyyNBmbk/k2JA=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=0uA7KGabCCCpbzEP61+2W68L6/gCsh/7uUkCQXk8uRq+4gVLDxeZQ/1qpzNSQAmxuPX4+mMCyIgorhswMD07QFrq9XrCdRwGDjhhX2ad0h9E2az3iYBp9KNdDLheCdr3zQ1iHiMiesI/h3Th7t6moaOMaDMcLwG3UoTt6GaFxe8=;
Message-ID: <348174.61265.qm@web110801.mail.gq1.yahoo.com>
X-YMail-OSG: hFTClzYVM1l3SjOvMBFhQmv7F5ZTDs1P1KaCQjD2iKwd5CMUocctLW4JQrqBuA0vrQBRLQt4aSlQnslqL6.ovVMa2kGFMmDGY4rEnuPYEKjIItW.NNrRerwthYH3ZAE3eya5if3QAc9zqCj15xSlpGqty5rWy5Ia7Z9Qk_fOH.kfG8dV_db7.Fa3MEOAfeuMyE3Mv0fV4wSH7tj2U1vIbB.8gR2kJ2QFWGQpHXBC_7b4kSwgphqkY6uUisi7icVkriTKfsk5cOGEMO2fJ3FVLZePdmg-
Received: from [64.30.124.230] by web110801.mail.gq1.yahoo.com via HTTP; Sat, 14 Mar 2009 17:47:49 PDT
X-Mailer: YahooMailRC/1277.29 YahooMailWebService/0.7.289.1
References: <9FA859626025B64FBC2AF149D97C944A01F736BA@CORPUSMX80A.corp.emc.com>
Date: Sat, 14 Mar 2009 17:47:49 -0700 (PDT)
From: "Mallikarjun C." <cb_mallikarjun@yahoo.com>
To: Black_David@emc.com, ips@ietf.org, rddp@ietf.org
In-Reply-To: <9FA859626025B64FBC2AF149D97C944A01F736BA@CORPUSMX80A.corp.emc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Sun, 15 Mar 2009 17:58:06 -0700
Cc: imss@ietf.org, Black_David@emc.com
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: Sun, 15 Mar 2009 00:47:10 -0000

Hi David,

My recommendation would be to defer the interoperability survey and draft consolidation work for iSCSI.  I do believe however that at least iSCSI SAM-4 compliance work in a backwards compatible fashion is required.  I currently plan to contribute to/author this work, although I unfortunately will not be able to attend the San Francisco meeting in person.

I tend to prefer your option C for the same reasons you cited.  Option B *might be* workable as the next preferred option.  One other suggestion I have is that even with a virtual WG (option C), I believe we will need to move at a relatively slower pace compared to the IPS WG because given the economy, everyone has enough workload on their plates in their companies and has fewer cycles to stay on top of the WG mailing list.  IMHO, this will need to be factored into milestones and such in the planning process.  

Thanks. --
Mallikarjun Chadalapaka 



----- Original Message ----
> From: "Black_David@emc.com" <Black_David@emc.com>
> To: ips@ietf.org; rddp@ietf.org
> Cc: imss@ietf.org; Black_David@emc.com
> Sent: Wednesday, March 11, 2009 4:28:10 PM
> Subject: [Ips] Storage Maintenance (storm) BOF reminder & requests
> 
> 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...            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