[rddp] Storm WG: Progress update

Black_David@emc.com Thu, 14 May 2009 23:28 UTC

Return-Path: <Black_David@emc.com>
X-Original-To: rddp@core3.amsl.com
Delivered-To: rddp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 94AEB3A6BCE; Thu, 14 May 2009 16:28:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.501
X-Spam-Level:
X-Spam-Status: No, score=-6.501 tagged_above=-999 required=5 tests=[AWL=0.098, 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 sRFvyePpcSU7; Thu, 14 May 2009 16:28:37 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id 9BABB3A686C; Thu, 14 May 2009 16:28:37 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id n4ENU8C5008145 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 14 May 2009 19:30:09 -0400 (EDT)
From: Black_David@emc.com
Received: from mailhub.lss.emc.com (nagas.lss.emc.com [10.254.144.15]) by hop04-l1d11-si03.isus.emc.com (Tablus Interceptor); Thu, 14 May 2009 19:30:02 -0400
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 n4ENU15t021979; Thu, 14 May 2009 19:30:01 -0400
Received: from CORPUSMX80A.corp.emc.com ([10.254.89.202]) by corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 14 May 2009 19:30:01 -0400
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, 14 May 2009 19:29:01 -0400
Message-ID: <9FA859626025B64FBC2AF149D97C944A02B76719@CORPUSMX80A.corp.emc.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Storm WG: Progress update
Thread-Index: AcnU68MKP8w1/43XSuCjAymoGT4jUA==
To: storm@ietf.org
X-OriginalArrivalTime: 14 May 2009 23:30:01.0384 (UTC) FILETIME=[E6F2BA80:01C9D4EB]
X-EMM-EM: Active
Cc: imss@ietf.org, ips@ietf.org, Black_David@emc.com, rddp@ietf.org
Subject: [rddp] Storm WG: Progress update
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rddp>, <mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rddp>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rddp>, <mailto:rddp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 May 2009 23:28:38 -0000

Progress is being made on the proposed storm WG - I plan to
post a new version of the proposed charter next week.  There
have been a few minor changes:
- The new iSCSI features work needs to include appropriate
	updates to the iSCSI MIB.
- Similarly, deprecating iFCP Address Translation mode
	will need to include an update to the iFCP MIB.
- It's useful to reference RFC 3723 for security and state
	that changes are not planned.

This is also a good time to remind people to subscribe to the
storm@ietf.org mailing list.  Once the WG is formed, cross-posting
to the other mailing lists will cease.  To subscribe, please
visit: https://www.ietf.org/mailman/listinfo/storm .  Also,
this is another reminder that the rddp@ietf.org list will be
shut down in favor of the storm@ietf.org mailing list in the
near future.

In addition, I've run into a minor hiccup involving access to
T10 (SCSI) and T11 (Fibre Channel) standards documents.  The
INCITS access rules changed recently to prohibit general
public access to final drafts of approved standards (access is
available to anyone whose company belongs to T10 or T11).  This
is not as big a problem as it might appear, because our primary
need in IETF is access to working drafts that remain publicly
accessible.

An important specific example is that part of the iSCSI update
work to SAM-4 is to specify a number of new task management
functions, including QUERY TASK.  It turns out that T10 has made
a minor, but important, change to QUERY TASK in their ongoing
SAM-5 work and hence the appropriate base document for this iSCSI
work appears to be revision 1 of SAM-5, which is publicly
accessible.  There are a number of other examples in which the
current working draft of the standard is an appropriate reference
document for the proposed storm WG work.

This should not be mistaken for a complete answer - some access
will be needed to final drafts of standards (e.g., those referenced
by RFCs that are to be updated).  A means for providing this
access to IETF participants has been worked out with T10.  I
expect the corresponding means to work with T11, but I need
to finish double-checking that before explaining how it'll work.

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
----------------------------------------------------