Securing Block Storage Protocols over IP: RFC 3723 Requirements Update for IPsec v3
draft-ietf-storm-ipsec-ips-update-03

The information below is for an old version of the document
Document Type Active Internet-Draft (storm WG)
Last updated 2013-08-29 (latest revision 2013-07-10)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Yes
Document shepherd David Black
Shepherd write-up Show (last changed 2013-07-10)
IESG IESG state IESG Evaluation::Revised I-D Needed
Telechat date
Needs 4 more YES or NO OBJECTION positions to pass.
Responsible AD Martin Stiemerling
Send notices to storm-chairs@tools.ietf.org, draft-ietf-storm-ipsec-ips-update@tools.ietf.org
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
Storage Maintenance (storm)                                     D. Black
Internet-Draft                                                       EMC
Updates: 3720, 3723, 3821, 3822, 4018, 4172, 4173, 4174, 5040, P. Koning
Intended status: Standards Track                                    Dell
Expires: January 10, 2014                                  July 09, 2013

 Securing Block Storage Protocols over IP: RFC 3723 Requirements Update
                              for IPsec v3
                  draft-ietf-storm-ipsec-ips-update-03

Abstract

   RFC 3723 specifies IPsec requirements for block storage protocols
   over IP (e.g., iSCSI) based on IPsec v2 (RFC 2401 and related RFCs);
   those requirements have subsequently been applied to remote direct
   data placement protocols, e.g., 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.

   [RFC Editor: The "Updates:" list above has been truncated by xml2rfc.
   The complete list is - Updates: 3720, 3723, 3821, 3822, 4018, 4172,
   4173, 4174, 5040, 5041, 5042, 5043, 5044, 5045, 5046, 5047, 5048 (if
   approved) ]

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 10, 2014.

Black & Koning          Expires January 10, 2014                [Page 1]
Internet-Draft                                                 July 2013

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Summary of Changes to RFC 3723  . . . . . . . . . . . . .   3
     1.3.  Other Updated RFCs  . . . . . . . . . . . . . . . . . . .   4
   2.  ESP  Requirements . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Data Origin Authentication and Data Integrity Transforms    6
     2.2.  Confidentiality Transform Requirements  . . . . . . . . .   6
   3.  IKEv1 and IKEv2 Requirements  . . . . . . . . . . . . . . . .   8
     3.1.  Authentication Requirements . . . . . . . . . . . . . . .   9
     3.2.  D-H Group and PRF Requirements  . . . . . . . . . . . . .  10
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   RFC 3723 [RFC3723] specifies IPsec requirements for block storage
   protocols over IP (e.g., iSCSI [RFC3720]) based on IPsec v2 (RFC 2401
   [RFC2401] and related RFCs); those requirements have subsequently
   been applied to remote direct data placement protocols, e.g., RDMAP
   [RFC5040].  This document updates RFC 3723's IPsec requirements to
   IPsec v3 ([RFC4301] and related RFCs) to reflect developments since
   RFC 3723 was published.

   For brevity, this document uses the term "block storage protocols" to
   refer to all protocols to which RFC 3723's requirements apply, see
   Section 1.3 for details.

Black & Koning          Expires January 10, 2014                [Page 2]
Internet-Draft                                                 July 2013
Show full document text