Proposed Working Group: STORM (STORage Maintenance) Transport (TSV) Area Proposed Charter (First Draft) ----------------------------------------------------------- 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; this work may include: - 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. Backwards compatibility is required. Significant changes to the existing protocol standards are out of scope, including any work on version 2 of any of these protocols. Stability is critical to the usage of these protocols, so 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 all implementations of a protocol have done something different than what the RFC specifies, it is 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. - FCIP: IP Protocol number 133 was allocated to a precursor of the FCIP protocol in 2000, but this allocated number is not used by FCIP. It may be possible to return this IP Protocol number to IANA for future reallocation. - 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. It is intended to do this with a short document that updates RFC 4172 (i.e., not via a complete rewrite of RFC 4172). - 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. Actual Goals and Milestones will be determined at the BOF.