Re: [Ips] data exceeds MaxBurstLength

<Paul_Koning@Dell.com> Thu, 29 March 2012 15:30 UTC

Return-Path: <Paul_Koning@Dell.com>
X-Original-To: ips@ietfa.amsl.com
Delivered-To: ips@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49A1F21E8218 for <ips@ietfa.amsl.com>; Thu, 29 Mar 2012 08:30:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.599
X-Spam-Level:
X-Spam-Status: No, score=-108.599 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 v2MR2UfR6rMU for <ips@ietfa.amsl.com>; Thu, 29 Mar 2012 08:30:31 -0700 (PDT)
Received: from ausxipps301.us.dell.com (ausxipps301.us.dell.com [143.166.148.223]) by ietfa.amsl.com (Postfix) with ESMTP id 8BDC021E813B for <ips@ietf.org>; Thu, 29 Mar 2012 08:30:31 -0700 (PDT)
X-Loopcount0: from 10.170.28.41
From: Paul_Koning@Dell.com
To: yusunn@gmail.com, ips@ietf.org
Date: Thu, 29 Mar 2012 10:30:20 -0500
Thread-Topic: [Ips] data exceeds MaxBurstLength
Thread-Index: Ac0NvyB27RQnvw69TO21nxFYAxNkUAAAZmeg
Message-ID: <09787EF419216C41A903FD14EE5506DD0313C73940@AUSX7MCPC103.AMER.DELL.COM>
References: <CAHHgPeN7dKUix0hekSvoY9siBLd=u032w6vgyO2gBHsRLo_xxg@mail.gmail.com>
In-Reply-To: <CAHHgPeN7dKUix0hekSvoY9siBLd=u032w6vgyO2gBHsRLo_xxg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Ips] data exceeds MaxBurstLength
X-BeenThere: ips@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IP Storage <ips.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ips>, <mailto:ips-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ips>
List-Post: <mailto:ips@ietf.org>
List-Help: <mailto:ips-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Mar 2012 15:30:32 -0000

It's covered by the general rules on protocol errors.  A reasonable reaction would be for the receiving node to close the connection (and probably log the protocol error using whatever logging machinery it has available).

	paul

-----Original Message-----
From: ips-bounces@ietf.org [mailto:ips-bounces@ietf.org] On Behalf Of yushang
Sent: Thursday, March 29, 2012 11:17 AM
To: ips@ietf.org
Subject: [Ips] data exceeds MaxBurstLength

Hi dear all,
If the transmitter (initiator or target) transfer some data exceeds the value MaxBurstLength specified . What shold happen ? It seems rfc3720 do not provide a clause for this situation . Thanks in advance .
_______________________________________________
Ips mailing list
Ips@ietf.org
https://www.ietf.org/mailman/listinfo/ips