[storm] Proposed text changes for the connection allocation problem
Michael Ko <mkosjc@gmail.com> Wed, 25 July 2012 00:27 UTC
Return-Path: <mkosjc@gmail.com>
X-Original-To: storm@ietfa.amsl.com
Delivered-To: storm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA45411E8080 for <storm@ietfa.amsl.com>; Tue, 24 Jul 2012 17:27:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kkhnxFen3boO for <storm@ietfa.amsl.com>; Tue, 24 Jul 2012 17:27:02 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6502D21F84DF for <storm@ietf.org>; Tue, 24 Jul 2012 17:27:02 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so119418vbb.31 for <storm@ietf.org>; Tue, 24 Jul 2012 17:27:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=EmQoVL4a2Zt/xiihJX31AxepBhoL8h4O5wljy8M1+EA=; b=OqcQEsUM0f40UYNqoI1W+39OCiSclj83o+iwRIfxZwLFqRomkpC1Un8VD/p0aFUfii r/9re5VLg9k+/xmo0jmkCu9NidU1PYN4SdItFLVp4IAwpSJO9riPN1IXozAyJVnqXeYM +/837dK7f2uu87EISzaTm6DH4LArbaHbqooZLqcxTX0KsPsY6QVGVO6bX6fXgfxjSrzY BOTrm2Z+qf1OtJCViyGOUacOEuFU41T1fZwy7iV7Tv19UvhjOnfJ5ZePHHcWv3+XMfew lkJPEZsPHFcLg/eWzEEEmf3XwuwUCpj/Xz62F2/C3tj+nJ3mtmipnZEv6rquKthNvvhY D/oQ==
MIME-Version: 1.0
Received: by 10.52.173.39 with SMTP id bh7mr7695418vdc.101.1343176021459; Tue, 24 Jul 2012 17:27:01 -0700 (PDT)
Received: by 10.220.92.210 with HTTP; Tue, 24 Jul 2012 17:27:01 -0700 (PDT)
Date: Tue, 24 Jul 2012 17:27:01 -0700
Message-ID: <CAP_=6dLGh8D_0WUeSLcej0QJ4_k2KPtxh_JZBy+HpEizrEjfFA@mail.gmail.com>
From: Michael Ko <mkosjc@gmail.com>
To: storm@ietf.org
Content-Type: multipart/alternative; boundary="bcaec51b9d01a141f104c59c890b"
Subject: [storm] Proposed text changes for the connection allocation problem
X-BeenThere: storm@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 25 Jul 2012 00:27:03 -0000
These are the changes I intend to incorporate into the existing draft to solve the connection allocation problem by using the iSER Hello exchanges. Please comment. 5.1.1 Initiator Behavior original: If the outcome of the iSCSI negotiation is to enable iSER-assisted mode, then on the initiator side, prior to sending the Login Request with the T (Transit) bit set to 1 and the NSG (Next Stage) field set to FullFeaturePhase, the iSCSI Layer MUST request the iSER Layer to allocate the connection resources necessary to support RCaP by invoking the Allocate_Connection_Resources Operational Primitive. replacement: If the outcome of the iSCSI negotiation is to enable iSER-assisted mode, then on the initiator side, prior to sending the Login Request with the T (Transit) bit set to 1 and the NSG (Next Stage) field set to FullFeaturePhase, the iSCSI Layer SHOULD request the iSER Layer to allocate the connection resources necessary to support RCaP by invoking the Allocate_Connection_Resources Operational Primitive. deleted: If the iSER Layer at the initiator is successful in allocating the connection resources necessary to support RCaP, the following events MUST occur in the specified sequence: [The numbered items will be retained but without the numbering.] new: If the iSCSI Layer on the initiator side allocates the connection resources to support RCaP only after it receives the final Login Response PDU from the target, then it may not be able to handle the number of unexpected iSCSI control-type PDUs (as declared by the MaxOutstandingUnexpectedPDUs key from the initiator) that can be sent by the target before the buffer resources are allocated at the initiator side. In this case the iSERHelloRequired key MUST be negotiated to Yes so that the initiator can allocate the connection resources before sending the iSER Hello Message. See section 5.1.3 for more details. 5.1.3 iSER Hello Exchange new: The connection resources can be allocated at the initiator side after it has received the final Login Response PDU from the target. To prevent the potential problem caused by the target sending the number of unexpected iSCSI control-type PDUs as determined by the MaxOustandingUnexpectedPDUs key allowed in the FullFeaturePhase, the iSER Hello exchanges can be used. This allows the initiator to allocate the connection resources before sending the iSER Hello Message. The iSERHelloRequired key is used by the initiator to determine if it is dealing with a target that supports the iSER Hello exchanges. As the iSERHelloRequired key is not defined in [RFC5046], an initiator/target must be able to deal with a target/initiator that does not understand the key or support the iSER Hello exchanges. For a target, if the iSERHelloRequired key is not negotiated, it MUST still respond with the iSER HelloReply Message when it recieves the iSER Hello Message. If the iSERHelloRequired key is negotiated to No or NotUnderstood, a target MAY choose to terminate the connection; otherwise it SHOULD delay sending any unexpected control-type PDUs until one of the following events has occurred: 1. A PDU is received from the initiator after it sends the final Login Response PDU. 2. A system configurable timeout period, say one second, has expired. For an initiator, if the iSERHelloRequired key is negotiated to No or NotUnderstood, it MAY choose to terminate the connection; otherwise it SHOULD do one of the following: 1. Allocate the connection resources before sending the final Login Request PDU. 2. Allocate one or more buffers for receiving unexpected control-type PDUs from the target before sending the final Login Request PDU. This reduces the possibility of the unexpected control-type PDUs causing the RCaP connection to close before the connection resources have been allocated. 10.1.3.4 iSER Protocol Errors original: Conversely, it is a protocol error if the iSER Hello Message is sent by the iSER Layer at the initiator when iSERHelloRequired is negotiated to "No". new: Conversely, if the iSER Hello Message is sent by the iSER Layer at the initiator when iSERHelloRequired is negotiated to "No", the iSER Layer at the target MAY treat this as a protocol error or respond with an iSER HelloReply Message. Mike
- [storm] Proposed text changes for the connection … Michael Ko
- Re: [storm] Proposed text changes for the connect… Black, David
- Re: [storm] Proposed text changes for the connect… Michael Ko
- Re: [storm] Proposed text changes for the connect… Black, David
- Re: [storm] Proposed text changes for the connect… Michael Ko
- [storm] iSER draft progress! Black, David