IETF Logo Mail Archive

Re: [storm] DDP messages ordering

<Paul_Koning@Dell.com> Tue, 08 September 2015 14:40 UTC

Return-Path: <Paul_Koning@dell.com>
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 D77961B44C2 for <storm@ietfa.amsl.com>; Tue, 8 Sep 2015 07:40:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.011
X-Spam-Level:
X-Spam-Status: No, score=-7.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, 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 YGcu989oliMV for <storm@ietfa.amsl.com>; Tue, 8 Sep 2015 07:40:07 -0700 (PDT)
Received: from ausxipps301.us.dell.com (ausxipps301.us.dell.com [143.166.148.223]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE1271B4475 for <storm@ietf.org>; Tue, 8 Sep 2015 07:40:07 -0700 (PDT)
DomainKey-Signature: s=smtpout; d=dell.com; c=nofws; q=dns; h=X-LoopCount0:X-IronPort-AV:From:To:CC:Subject: Thread-Topic:Thread-Index:Date:Message-ID:References: In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:x-originating-ip: Content-Type:Content-ID:Content-Transfer-Encoding: MIME-Version:Return-Path; b=AL1b6edVjTwhJ93qosoe0ZMkGOt14BaxcmQ7v4nArrZmP9T617ox7o+g Fi4+mQ9ijXFQqMskLR/umI/+/PO8Qd99sG6gxCmZP0KteBg1rnVcMwOWS XhXVqmC/vphiPlS1uNzY2nbGmcFiiaGJUeDWCbb5QB87kXq4qVWoXMd7q M=;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1441723208; x=1473259208; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=8+LgcMhm0mjg3d47q7meSE/c/dfv9rgWfHjo7a2bsKs=; b=dnw+fQ5G2WglX0CIRnEcqgh2lHS3/jMBg0WUFTDSQ6uzz5wK2PN9y/u3 4zCDU4R+MKfLo1dthhbl98pJIALX2YhJ4uchpnp+lzqkQ6WJ/thP7T1Xv bk+CcuO6KjbjSIgg+HN8mFv9wBF+LGUS5YW01D2b3OhCjPD2g6lM3LgbR 4=;
X-LoopCount0: from 10.175.216.251
X-IronPort-AV: E=Sophos;i="5.17,490,1437454800"; d="scan'208";a="701669100"
From: Paul_Koning@Dell.com
To: tom@talpey.com
Thread-Topic: [storm] DDP messages ordering
Thread-Index: AdDqHUWNk/8QkGT5SXeSvBvi6thoNgATXO+AAADbpYA=
Date: Tue, 08 Sep 2015 14:40:04 +0000
Message-ID: <BCD9788C-90AC-4141-8E26-AC32ACD0CCC0@dell.com>
References: <HE1PR02MB0652BA180545E2D5E21AB8FEF9530@HE1PR02MB0652.eurprd02.prod.outlook.com> <55EEED81.2060508@talpey.com>
In-Reply-To: <55EEED81.2060508@talpey.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.177.90.68]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E1D815404F571D41B7812A811F0D78FB@dell.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/storm/nUxeRuvYIbtWfuHjTEDZiudU7z0>
Cc: storm@ietf.org
Subject: Re: [storm] DDP messages ordering
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 08 Sep 2015 14:40:14 -0000

> On Sep 8, 2015, at 10:15 AM, Tom Talpey <tom@talpey.com> wrote:
> 
> On 9/8/2015 6:02 AM, Elena Gurevich wrote:
>> ...
>> Does this mean that transmitter MUST not interleave DDM segments related
>> to consequent DDP messages ?
> 
> It depends on what you mean by "the transmitter". It's certainly
> possible that network delivery and TCP retransmission can reorder
> segments.

No, it isn't.  TCP provides two services: (1) ordered delivery, and (2) guaranteed delivery or report of failure to do so.

Network delivery and TCP retransmission will NOT reorder the data delivered by TCP to the layer above.

	paul

v2.23.0 | Report a Bug | By Email