From ips-bounces@ietf.org Mon Feb 2 09:42:35 2009 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 EB1EE28C238; Mon, 2 Feb 2009 09:42:35 -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 F29903A6B35; Mon, 2 Feb 2009 09:42:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.558 X-Spam-Level: X-Spam-Status: No, score=-6.558 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, 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 WzpfBnwYNb32; Mon, 2 Feb 2009 09:42:34 -0800 (PST) Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id D4FD23A692A; Mon, 2 Feb 2009 09:42:33 -0800 (PST) Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id n12HgD0d021797 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 2 Feb 2009 12:42:13 -0500 (EST) From: Black_David@emc.com Received: from mailhub.lss.emc.com (numailhub.lss.emc.com [10.254.144.16]) by hop04-l1d11-si04.isus.emc.com (Tablus Interceptor); Mon, 2 Feb 2009 12:42:10 -0500 Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com [10.254.64.53]) by mailhub.lss.emc.com (Switch-3.3.2/Switch-3.3.2) with ESMTP id n12Hg9Xp018786; Mon, 2 Feb 2009 12:42:09 -0500 Received: from CORPUSMX80A.corp.emc.com ([10.254.89.201]) by corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 2 Feb 2009 12:42:09 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 2 Feb 2009 12:42:09 -0500 Message-ID: <9FA859626025B64FBC2AF149D97C944A018FFA8A@CORPUSMX80A.corp.emc.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Revised storm (STORage Maintenance) BOF proposal for SF Thread-Index: AcmFXZJr5VfhwDDxRKO6eQANUIj6hw== To: X-OriginalArrivalTime: 02 Feb 2009 17:42:09.0159 (UTC) FILETIME=[92693170:01C9855D] X-EMM-EM: Active Cc: imss@ietf.org, rddp@ietf.org Subject: [Ips] Revised storm (STORage Maintenance) BOF proposal for SF 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 I just sent this in with a request for approval of the BOF. There should be no substantial changes from what I posted earlier, but there is a strong request for a meeting slot later in the week due to a conflicting meeting for the RDDP folks Mon-Wed. --------------------------------------- Proposed Transport Area (TSV) BOF: STORM (STORage Maintenance) Proposed for IETF San Francisco (March 22-27, 2009) The IETF ips (IP Storage) and rddp (Remote Direct Data Placement) working groups have produced a significant number of storage protocols (e.g., iSCSI, iSER, FCIP and iFCP) for which there is significant usage. The time has come to reflect feedback from implementation and usage into updated RFCs. See the initial draft list of work items below for details (expansion of this list during the BOF is a definite possibility). The purpose of the storm BOF is to determine whether a working group should be formed for maintenance and update of these storage-related protocols based primarily on implementation experience. This work is envisioned to encompass: - Implementation-driven revisions and updates to existing protocols (i.e., updated RFCs that match the "running code"). - Interoperability reports as needed for the resulting revised protocols that are appropriate for Draft Standard RFC status. - Minor protocol changes or additions; this is anticipated to include iSCSI features for SAM-4 compliance, some minor iSER corrections/clarifications and an MPA startup change needed to better support MPI applications. The envisioned work **WILL NOT** include wholesale changes to the existing protocol standards. Stability is critical to the usage of these protocols, hence work on version 2 of any of these protocols will be out of scope, period. Backwards compatibility with existing implementations will be a requirement imposed on for all protocol changes and additions. Note that this is a requirement for *implementation* compatibility - if it is the case that an existing RFC says one thing, but all the implementations of that RFC consistently do something different, it would be appropriate for a new RFC to document what the "running code" actually does and deprecate the unused original behavior. Initial draft list of work items: - iSCSI: Combine RFCs 3720 (iSCSI), 3980 (NAA names), 4850 (node architecture key) and 5048 (corrections/clarifications) into one draft, removing features that are not implemented in practice (e.g., markers). - iSCSI: Interoperability report on what has been implemented and is known to interoperate in support of Draft Standard RFC status for the new iSCSI RFC. The decision about whether to target Draft Standard RFC status will be discussed in the BOF in San Francisco - this may entail updates to RFC 3722 [stringprep for iSCSI] and RFC 3723 [security]. - iSCSI: Add features to support SAM-4 (4th version of the SCSI architecture) in a backwards-compatible fashion. iSCSI is currently based on SAM-2. This will be a separate draft from the iSCSI update in the first bullet. - iFCP: The Address Translation mode of iFCP needs to be deprecated (SHOULD NOT implement or use), as there are significant technical problems with its specification, and moreover, only the Address Transparent mode of iFCP is in use. A short draft should be sufficient to do this (i.e., a complete rewrite of RFC 4172 is not anticipated). - RDDP MPA: Good support for MPI applications requires a small update to the startup functionality to allow either end of the connection to initiate. - iSER: Experience with Infiniband implementations suggest a few minor updates to reflect what has been done in practice. 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 expressions of interest and/or work commitment to the items listed above that will be discussed at the BOF. Scheduling Request: While IETF BOFs are scheduled on a time-and-space available basis, there is a conflicting event for the RDDP community (includes MPA and iSER) on Mon-Wed of the IETF San Francisco week. For this reason a Thu or Fri meeting slot is strongly requested for this BOF in order to obtain participation of the RDDP community in addition to the IPS community. ----------------------------------------- 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 From Black_David@emc.com Wed Feb 4 20:25:06 2009 Return-Path: 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 A663D3A6AC2; Wed, 4 Feb 2009 20:25:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.56 X-Spam-Level: X-Spam-Status: No, score=-6.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, 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 kb4AWSkglTFV; Wed, 4 Feb 2009 20:25:05 -0800 (PST) Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id 8AE853A6B45; Wed, 4 Feb 2009 20:25:05 -0800 (PST) Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id n154OiBC020686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 4 Feb 2009 23:24:44 -0500 (EST) Received: from mailhub.lss.emc.com (sesha.lss.emc.com [10.254.144.12]) by hop04-l1d11-si01.isus.emc.com (Tablus Interceptor); Wed, 4 Feb 2009 23:24:35 -0500 Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com [10.254.64.53]) by mailhub.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id n154OZbP001596; Wed, 4 Feb 2009 23:24:35 -0500 (EST) From: Black_David@emc.com Received: from CORPUSMX80A.corp.emc.com ([10.254.89.201]) by corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 4 Feb 2009 23:24:35 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 4 Feb 2009 23:24:33 -0500 Message-ID: <9FA859626025B64FBC2AF149D97C944A019506E9@CORPUSMX80A.corp.emc.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Proposed STORM BOF - draft agenda Thread-Index: AcmHSaW+FB1B/LZCTeKfpiutE7DM/w== To: X-OriginalArrivalTime: 05 Feb 2009 04:24:35.0048 (UTC) FILETIME=[A6609680:01C98749] Cc: imss@ietf.org, rddp@ietf.org Subject: [Ips] Proposed STORM BOF - draft agenda 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: , X-List-Received-Date: Thu, 05 Feb 2009 04:25:07 -0000 A BOF proposal requires an agenda, so I put this together: Proposed Transport Area (TSV) BOF: STORM (STORage Maintenance) Proposed for IETF San Francisco (March 22-27, 2009) BOF chair: David L. Black, EMC (black_david@emc.com) Agenda - Initial Draft ---------------------- Administrivia - Note Well - Purpose of BOF - Mailing list usage (currently using existing ips@ietf.org and rddp@ietf.org lists) Draft charter (there will be one posted prior to the BOF) - Initial presentation and text bashing iSCSI-related work - Consolidated iSCSI RFC - Whether to take iSCSI to Draft Standard status, including implementation report - SAM-4 feature addition FC encapsulation-related work - iFCP Address Translation obsolescence RDDP-related work - MPA startup change for MPI iSER-related work - Clarification arising from InfiniBand use of iSER Any other proposed work items Draft charter: Text bashing, round 2 WG formation discussion 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 ---------------------------------------------------- From Black_David@emc.com Tue Feb 10 16:29:21 2009 Return-Path: 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 815CD3A69F0; Tue, 10 Feb 2009 16:29:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.526 X-Spam-Level: X-Spam-Status: No, score=-6.526 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, 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 H09SXSSk3Fwh; Tue, 10 Feb 2009 16:29:20 -0800 (PST) Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id 4845C3A68F7; Tue, 10 Feb 2009 16:29:19 -0800 (PST) Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id n1B0TMFh015885 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Feb 2009 19:29:22 -0500 (EST) From: Black_David@emc.com Received: from mailhub.lss.emc.com (numailhub.lss.emc.com [10.254.144.15]) by hop04-l1d11-si02.isus.emc.com (Tablus Interceptor); Tue, 10 Feb 2009 19:29:12 -0500 Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com [10.254.64.53]) by mailhub.lss.emc.com (Switch-3.3.2mp/Switch-3.3.2mp) with ESMTP id n1B0TBhd010194; Tue, 10 Feb 2009 19:29:11 -0500 Received: from CORPUSMX80A.corp.emc.com ([10.254.89.201]) by corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 10 Feb 2009 19:29:10 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 10 Feb 2009 19:29:10 -0500 Message-ID: <9FA859626025B64FBC2AF149D97C944A01A049EB@CORPUSMX80A.corp.emc.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: STORM BOF approval Thread-Index: AcmL38HpJfHO5OnnSveUVn0eBrvtOA== To: X-OriginalArrivalTime: 11 Feb 2009 00:29:10.0850 (UTC) FILETIME=[C22D8220:01C98BDF] X-EMM-EM: Active Cc: imss@ietf.org, Black_David@emc.com, rddp@ietf.org Subject: [Ips] STORM BOF approval 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: , X-List-Received-Date: Wed, 11 Feb 2009 00:29:21 -0000 The request to hold the STORM BOF (STORage Maintenance) BOF in San Francisco has been approved. Lars and I have asked for a 2 hour slot on Thursday, with Friday as second choice of day (this is due to a conflicting Mon-Wed event for the RDDP community). Here are the links for the BOF material: - Description: http://www.ietf.org/mail-archive/web/ips/current/msg02669.html - Draft(y) Agenda: http://www.ietf.org/mail-archive/web/ips/current/msg02670.html I'll try to get some discussion about STORM activity started on the IPS and RDDP lists - people have been entirely too polite in replying to me about the BOF in private, leading some IETF observers to interpret no traffic on these lists as lack of interest. In particular, I'm hoping to get some second level scoping (list of things to be done) for work items including the iSCSI revision for Draft Standard (what to leave out), SAM-4 support for iSCSI (what to put in), and iSER revisions based on InfiniBand implementations (what IETF should do vs. leave to the IBTA). I will also be turning the BOF description into a draft WG charter at some point. I expect to be off-line (no email, phone for emergencies only) for about 2 weeks starting late tomorrow - vacation happens to the best of us ... 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 ---------------------------------------------------- From Black_David@emc.com Tue Feb 10 17:52:35 2009 Return-Path: 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 494B63A6883; Tue, 10 Feb 2009 17:52:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.528 X-Spam-Level: X-Spam-Status: No, score=-6.528 tagged_above=-999 required=5 tests=[AWL=0.071, BAYES_00=-2.599, 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 bIhET1dv7u1I; Tue, 10 Feb 2009 17:52:34 -0800 (PST) Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id 5F8723A67FB; Tue, 10 Feb 2009 17:52:34 -0800 (PST) Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id n1B1qaLo020193 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Feb 2009 20:52:36 -0500 (EST) From: Black_David@emc.com Received: from mailhub.lss.emc.com (numailhub.lss.emc.com [10.254.144.16]) by hop04-l1d11-si01.isus.emc.com (Tablus Interceptor); Tue, 10 Feb 2009 20:52:24 -0500 Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com [10.254.64.53]) by mailhub.lss.emc.com (Switch-3.3.2/Switch-3.3.2) with ESMTP id n1B1qOBw019581; Tue, 10 Feb 2009 20:52:24 -0500 Received: from CORPUSMX80A.corp.emc.com ([10.254.89.201]) by corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 10 Feb 2009 20:52:23 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 10 Feb 2009 20:52:22 -0500 Message-ID: <9FA859626025B64FBC2AF149D97C944A01A04A02@CORPUSMX80A.corp.emc.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: STORM BOF date/time determination Thread-Index: AcmL62GuOmAo/IQYSoGRXfP3oljoQw== To: X-OriginalArrivalTime: 11 Feb 2009 01:52:23.0617 (UTC) FILETIME=[62194B10:01C98BEB] X-EMM-EM: Active Cc: imss@ietf.org, Black_David@emc.com, rddp@ietf.org Subject: [Ips] STORM BOF date/time determination 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: , X-List-Received-Date: Wed, 11 Feb 2009 01:52:35 -0000 Someone asked - when will we know whether it's Thu or Fri (Mar 26 or 27) and what time the STORM BOF is? The secretariat should have (or shortly will have) gathered all the inputs for session scheduling for San Francisco. According to this page: http://www.ietf.org/meetings/74/cutoff-dates.html There should be a preliminary agenda for the SF meeting week out this Friday. That preliminary agenda inevitably leads to multiple rounds of " conflicts with , can we swap it with " discussions, even though conflicts are an input to the initial agenda. Some conflicts are inevitably overlooked, forgotten, or not noticed until the initial agenda is published - think of this as a demonstration that IETF session scheduling is at least an NP-Hard problem ;-). The final agenda, with the STORM date, time and room should be published on Mar 2. That's 3+ weeks in advance, so reasonable domestic airfares to SF should still be available. 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 ---------------------------------------------------- From Black_David@emc.com Thu Feb 12 09:22:25 2009 Return-Path: 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 9FD273A6917; Thu, 12 Feb 2009 09:22:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 d2XokbX0qJ-t; Thu, 12 Feb 2009 09:22:24 -0800 (PST) Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id B365D3A685F; Thu, 12 Feb 2009 09:22:24 -0800 (PST) Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id n1CHMS8O017576 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 12 Feb 2009 12:22:28 -0500 (EST) From: Black_David@emc.com Received: from mailhub.lss.emc.com (numailhub.lss.emc.com [10.254.144.16]) by hop04-l1d11-si02.isus.emc.com (Tablus Interceptor); Thu, 12 Feb 2009 12:22:21 -0500 Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com [10.254.64.53]) by mailhub.lss.emc.com (Switch-3.3.2/Switch-3.3.2) with ESMTP id n1CHMB10032249; Thu, 12 Feb 2009 12:22:18 -0500 Received: from CORPUSMX80A.corp.emc.com ([10.254.89.201]) by corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 12 Feb 2009 12:22:16 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 12 Feb 2009 12:22:15 -0500 Message-ID: <9FA859626025B64FBC2AF149D97C944A01A4E9A5@CORPUSMX80A.corp.emc.com> In-Reply-To: <9FA859626025B64FBC2AF149D97C944A01A049EB@CORPUSMX80A.corp.emc.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: STORM BOF: Discussion topics Thread-Index: AcmL38HpJfHO5OnnSveUVn0eBrvtOABVfz1Q X-Priority: 1 Priority: Urgent Importance: high References: <9FA859626025B64FBC2AF149D97C944A01A049EB@CORPUSMX80A.corp.emc.com> To: , X-OriginalArrivalTime: 12 Feb 2009 17:22:16.0612 (UTC) FILETIME=[73BA7640:01C98D36] X-EMM-EM: Active Cc: Black_David@emc.com Subject: [Ips] STORM BOF: Discussion topics 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: , X-List-Received-Date: Thu, 12 Feb 2009 17:22:25 -0000 I wrote: > I'll try to get some discussion about STORM activity started > on the IPS and RDDP lists - people have been entirely too > polite in replying to me about the BOF in private, leading > some IETF observers to interpret no traffic on these lists > as lack of interest. >=20 > In particular, I'm hoping to get > some second level scoping (list of things to be done) > for work items including the iSCSI revision for Draft > Standard (what to leave out), SAM-4 support for iSCSI > (what to put in), and iSER revisions based on InfiniBand > implementations (what IETF should do vs. leave to the > IBTA). Here are three topics that it would be useful to discuss: - As part of pruning the iSCSI spec down to what's been implemented (in order to go for draft standard), what comes out? My list starts with Markers (use iSER/RDDP[iWARP] instead) and SPKM authentication. - What's important/useful about new features from SAM-4. I know that there's interest in the new task management operations, but what else? Anything added here needs a new text key to negotiate it. - Details on the minor fixes to iSER and MPA. People have sent me private mail about these - please send to this list. I'm about to vanish for vacation for two weeks (no email). I'll be back on Feb 26th. For now, I'm inclined to continue using the ips@ietf.org and rddp@ietf.org lists for STORM work rather than create a new list, but this can be changed. 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 ---------------------------------------------------- From Quicksall_iSCSI@bellsouth.net Fri Feb 27 05:56:24 2009 Return-Path: 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 CD01F3A6888; Fri, 27 Feb 2009 05:56:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.184 X-Spam-Level: X-Spam-Status: No, score=-0.184 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, STOX_REPLY_TYPE=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 3evUpWghCsUF; Fri, 27 Feb 2009 05:56:24 -0800 (PST) Received: from fmailhost06.isp.att.net (fmailhost06.isp.att.net [204.127.217.106]) by core3.amsl.com (Postfix) with ESMTP id 15F9B3A67A4; Fri, 27 Feb 2009 05:56:24 -0800 (PST) Received: from ivvtdkv0981 (adsl-80-248-236.jax.bellsouth.net[65.80.248.236]) by isp.att.net (frfwmhc06) with SMTP id <20090227135646H06001dbone>; Fri, 27 Feb 2009 13:56:46 +0000 X-Originating-IP: [65.80.248.236] Message-ID: <6B6C0BBA555F4F90975976B1AEE5B265@IVVTDKV0981> From: "Eddy Quicksall" To: , , References: <9FA859626025B64FBC2AF149D97C944A01A049EB@CORPUSMX80A.corp.emc.com> <9FA859626025B64FBC2AF149D97C944A01A4E9A5@CORPUSMX80A.corp.emc.com> Date: Fri, 27 Feb 2009 08:56:41 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Subject: Re: [Ips] STORM BOF: Discussion topics 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: , X-List-Received-Date: Fri, 27 Feb 2009 13:56:24 -0000 Are there any notes from this BOF? Eddy ----- Original Message ----- From: To: ; Cc: Sent: Thursday, February 12, 2009 12:22 PM Subject: [Ips] STORM BOF: Discussion topics >I wrote: > >> I'll try to get some discussion about STORM activity started >> on the IPS and RDDP lists - people have been entirely too >> polite in replying to me about the BOF in private, leading >> some IETF observers to interpret no traffic on these lists >> as lack of interest. >> >> In particular, I'm hoping to get >> some second level scoping (list of things to be done) >> for work items including the iSCSI revision for Draft >> Standard (what to leave out), SAM-4 support for iSCSI >> (what to put in), and iSER revisions based on InfiniBand >> implementations (what IETF should do vs. leave to the >> IBTA). > > Here are three topics that it would be useful to discuss: > > - As part of pruning the iSCSI spec down to what's been implemented > (in order to go for draft standard), what comes out? My > list starts with Markers (use iSER/RDDP[iWARP] instead) > and SPKM authentication. > > - What's important/useful about new features from SAM-4. I know > that there's interest in the new task management operations, > but what else? Anything added here needs a new text key to > negotiate it. > > - Details on the minor fixes to iSER and MPA. People have sent > me private mail about these - please send to this list. > > I'm about to vanish for vacation for two weeks (no email). > I'll be back on Feb 26th. > > For now, I'm inclined to continue using the ips@ietf.org and > rddp@ietf.org lists for STORM work rather than create a new > list, but this can be changed. > > 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 From Black_David@emc.com Fri Feb 27 08:15:55 2009 Return-Path: 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 DA90C28C16D; Fri, 27 Feb 2009 08:15:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 VGCoyo7mmQzF; Fri, 27 Feb 2009 08:15:54 -0800 (PST) Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id C3AA33A6C2A; Fri, 27 Feb 2009 08:15:54 -0800 (PST) Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id n1RGGER8020840 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 27 Feb 2009 11:16:14 -0500 (EST) From: Black_David@emc.com Received: from mailhub.lss.emc.com (numailhub.lss.emc.com [10.254.144.16]) by hop04-l1d11-si01.isus.emc.com (Tablus Interceptor); Fri, 27 Feb 2009 11:16:02 -0500 Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com [10.254.64.53]) by mailhub.lss.emc.com (Switch-3.3.2/Switch-3.3.2) with ESMTP id n1RGFxAk003899; Fri, 27 Feb 2009 11:15:59 -0500 Received: from CORPUSMX80A.corp.emc.com ([10.254.89.202]) by corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 27 Feb 2009 11:15:59 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 27 Feb 2009 11:15:58 -0500 Message-ID: <9FA859626025B64FBC2AF149D97C944A01C08BB5@CORPUSMX80A.corp.emc.com> In-Reply-To: <6B6C0BBA555F4F90975976B1AEE5B265@IVVTDKV0981> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Ips] STORM BOF: Discussion topics Thread-Index: AcmY4z5VgvowwegrTCOvZi5tuhRRngAExyZw References: <9FA859626025B64FBC2AF149D97C944A01A049EB@CORPUSMX80A.corp.emc.com> <9FA859626025B64FBC2AF149D97C944A01A4E9A5@CORPUSMX80A.corp.emc.com> <6B6C0BBA555F4F90975976B1AEE5B265@IVVTDKV0981> To: , , X-OriginalArrivalTime: 27 Feb 2009 16:15:59.0587 (UTC) FILETIME=[AD6EDB30:01C998F6] X-EMM-EM: Active Subject: Re: [Ips] STORM BOF: Discussion topics 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: , X-List-Received-Date: Fri, 27 Feb 2009 16:15:55 -0000 The BOF is scheduled for Thursday, March 26th, 9:00a - 11:30a at the IETF meetings in San Francisco. Minutes will be sent to the mailing lists and published as part of the IETF meeting proceedings (including on the web site). Everyone who can attend is encouraged to come. Thanks, --David =20 > -----Original Message----- > From: Eddy Quicksall [mailto:Quicksall_iSCSI@bellsouth.net]=20 > Sent: Friday, February 27, 2009 8:57 AM > To: Black, David; ips@ietf.org; rddp@ietf.org > Subject: Re: [Ips] STORM BOF: Discussion topics >=20 > Are there any notes from this BOF? >=20 > Eddy > ----- Original Message -----=20 > From: > To: ; > Cc: > Sent: Thursday, February 12, 2009 12:22 PM > Subject: [Ips] STORM BOF: Discussion topics >=20 >=20 > >I wrote: > >=20 > >> I'll try to get some discussion about STORM activity started > >> on the IPS and RDDP lists - people have been entirely too > >> polite in replying to me about the BOF in private, leading > >> some IETF observers to interpret no traffic on these lists > >> as lack of interest. > >>=20 > >> In particular, I'm hoping to get > >> some second level scoping (list of things to be done) > >> for work items including the iSCSI revision for Draft > >> Standard (what to leave out), SAM-4 support for iSCSI > >> (what to put in), and iSER revisions based on InfiniBand > >> implementations (what IETF should do vs. leave to the > >> IBTA). > >=20 > > Here are three topics that it would be useful to discuss: > >=20 > > - As part of pruning the iSCSI spec down to what's been implemented > > (in order to go for draft standard), what comes out? My > > list starts with Markers (use iSER/RDDP[iWARP] instead) > > and SPKM authentication. > >=20 > > - What's important/useful about new features from SAM-4. I know > > that there's interest in the new task management operations, > > but what else? Anything added here needs a new text key to > > negotiate it. > >=20 > > - Details on the minor fixes to iSER and MPA. People have sent > > me private mail about these - please send to this list. > >=20 > > I'm about to vanish for vacation for two weeks (no email). > > I'll be back on Feb 26th. > >=20 > > For now, I'm inclined to continue using the ips@ietf.org and > > rddp@ietf.org lists for STORM work rather than create a new > > list, but this can be changed. > >=20 > > 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 >=20 >=20 From stevebyan@mac.com Fri Feb 27 09:46:59 2009 Return-Path: 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 70F6028C344 for ; Fri, 27 Feb 2009 09:46:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.98 X-Spam-Level: X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619] 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 fB6ldKKx6bp6 for ; Fri, 27 Feb 2009 09:46:58 -0800 (PST) Received: from asmtpout016.mac.com (asmtpout016.mac.com [17.148.16.91]) by core3.amsl.com (Postfix) with ESMTP id C768B28C33D for ; Fri, 27 Feb 2009 09:46:58 -0800 (PST) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Received: from [10.97.16.86] ([216.240.26.4]) by asmtp016.mac.com (Sun Java(tm) System Messaging Server 6.3-7.03 (built Aug 7 2008; 32bit)) with ESMTPSA id <0KFQ007R3K266S00@asmtp016.mac.com> for ips@ietf.org; Fri, 27 Feb 2009 09:46:56 -0800 (PST) In-reply-to: <9FA859626025B64FBC2AF149D97C944A01A4E9A5@CORPUSMX80A.corp.emc.com> References: <9FA859626025B64FBC2AF149D97C944A01A049EB@CORPUSMX80A.corp.emc.com> <9FA859626025B64FBC2AF149D97C944A01A4E9A5@CORPUSMX80A.corp.emc.com> X-Priority: 1 Message-id: <11C4163C-A869-436B-BE0A-293FA66A1679@mac.com> From: Steve Byan Date: Fri, 27 Feb 2009 12:46:54 -0500 To: IPS X-Mailer: Apple Mail (2.753.1) Subject: Re: [Ips] STORM BOF: Discussion topics 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: , X-List-Received-Date: Fri, 27 Feb 2009 17:46:59 -0000 On Feb 12, 2009, at 12:22 PM, Black_David@emc.com wrote: > I wrote: > >> I'll try to get some discussion about STORM activity started >> on the IPS and RDDP lists - people have been entirely too >> polite in replying to me about the BOF in private, leading >> some IETF observers to interpret no traffic on these lists >> as lack of interest. >> >> In particular, I'm hoping to get >> some second level scoping (list of things to be done) >> for work items including the iSCSI revision for Draft >> Standard (what to leave out), SAM-4 support for iSCSI >> (what to put in), and iSER revisions based on InfiniBand >> implementations (what IETF should do vs. leave to the >> IBTA). > > Here are three topics that it would be useful to discuss: > > - What's important/useful about new features from SAM-4. I know > that there's interest in the new task management operations, > but what else? Anything added here needs a new text key to > negotiate it. Command priority would be useful. Status qualifiers would be nice to have, but I think are less useful than command priority. Best regards, -Steve -- Steve Byan