[storm] RFC 7146 on Securing Block Storage Protocols over IP: RFC 3723 Requirements Update for IPsec v3
rfc-editor@rfc-editor.org Fri, 04 April 2014 23:55 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: storm@ietfa.amsl.com
Delivered-To: storm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A77681A031C; Fri, 4 Apr 2014 16:55:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UJSoqG5ALlEc; Fri, 4 Apr 2014 16:55:34 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 8FA8B1A0305; Fri, 4 Apr 2014 16:55:33 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C66A87FC399; Fri, 4 Apr 2014 16:55:22 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20140404235525.C66A87FC399@rfc-editor.org>
Date: Fri, 04 Apr 2014 16:55:22 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/storm/mdbIAmb-eY09vrrf8rhNhKVXtF0
Cc: drafts-update-ref@iana.org, storm@ietf.org, rfc-editor@rfc-editor.org
Subject: [storm] RFC 7146 on Securing Block Storage Protocols over IP: RFC 3723 Requirements Update for IPsec v3
X-BeenThere: storm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Storage Maintenance WG <storm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/storm>, <mailto:storm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/storm/>
List-Post: <mailto:storm@ietf.org>
List-Help: <mailto:storm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/storm>, <mailto:storm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 23:55:38 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7146
Title: Securing Block Storage Protocols over
IP: RFC 3723 Requirements Update for
IPsec v3
Author: D. Black, P. Koning
Status: Standards Track
Stream: IETF
Date: April 2014
Mailbox: david.black@emc.com,
paul_koning@Dell.com
Pages: 18
Characters: 37991
Updates: RFC 3720, RFC 3723, RFC 3821, RFC 3822,
RFC 4018, RFC 4172, RFC 4173, RFC 4174,
RFC 5040, RFC 5041, RFC 5042, RFC 5043,
RFC 5044, RFC 5045, RFC 5046, RFC 5047,
RFC 5048
I-D Tag: draft-ietf-storm-ipsec-ips-update-04.txt
URL: http://www.rfc-editor.org/rfc/rfc7146.txt
RFC 3723 specifies IPsec requirements for block storage protocols
over IP (e.g., Internet Small Computer System Interface (iSCSI))
based on IPsec v2 (RFC 2401 and related RFCs); those requirements
have subsequently been applied to remote direct data placement
protocols, e.g., the Remote Direct Memory Access Protocol (RDMAP).
This document updates RFC 3723's IPsec requirements to IPsec v3 (RFC
4301 and related RFCs) and makes some changes to required algorithms
based on developments in cryptography since RFC 3723 was published.
This document is a product of the STORage Maintenance Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements. Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC