Re: [Dime] Message mis-sequencing over SCTP

Tom Taylor <tom111.taylor@bell.net> Wed, 31 March 2010 13:50 UTC

Return-Path: <tom111.taylor@bell.net>
X-Original-To: dime@core3.amsl.com
Delivered-To: dime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 68A723A67B6 for <dime@core3.amsl.com>; Wed, 31 Mar 2010 06:50:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.934
X-Spam-Level: *
X-Spam-Status: No, score=1.934 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, MSGID_FROM_MTA_HEADER=0.803]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pz-PHBWpFO0H for <dime@core3.amsl.com>; Wed, 31 Mar 2010 06:50:49 -0700 (PDT)
Received: from blu0-omc3-s37.blu0.hotmail.com (blu0-omc3-s37.blu0.hotmail.com [65.55.116.112]) by core3.amsl.com (Postfix) with ESMTP id 90A8F3A679C for <dime@ietf.org>; Wed, 31 Mar 2010 06:50:49 -0700 (PDT)
Received: from BLU0-SMTP10 ([65.55.116.73]) by blu0-omc3-s37.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 31 Mar 2010 06:51:20 -0700
X-Originating-IP: [74.12.183.53]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP10B5C02EA204511F92B61AD81E0@phx.gbl>
Received: from [192.168.2.11] ([74.12.183.53]) by BLU0-SMTP10.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Wed, 31 Mar 2010 06:51:20 -0700
Date: Wed, 31 Mar 2010 09:51:17 -0400
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Naveen Kottapalli <naveen.sarma@gmail.com>
References: <s2yce72e8461003310636z294f083of823a022c19bf29d@mail.gmail.com>
In-Reply-To: <s2yce72e8461003310636z294f083of823a022c19bf29d@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Mar 2010 13:51:20.0372 (UTC) FILETIME=[3E367F40:01CAD0D9]
Cc: dime@ietf.org
Subject: Re: [Dime] Message mis-sequencing over SCTP
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Mar 2010 13:50:50 -0000

Sounds like a good point. Seems to me the rules should be:

  - use only stream 0 until the Diameter connection has been set up
  - all messages relating to the same session must use the same stream.

That should be added to section 2.1.1.


Naveen Kottapalli wrote:
> Hi,
> 
> Am just wondering whether the mis-sequencing in the delivery of packets when
> SCTP is being used as transport layer would cause any problem.  For example,
> take an association with 5 out-streams to send out the Diameter messages.
> Immediately after sending CEA on stream 0, all other messages are sent over
> other streams like 1, 2, 3, and 4.
> 
> There is a chance that the other Diameter messages will reach the peer
> before the CEA is processed?   Does the existing draft miss the sequencing
> problem over SCTP?
> 
> Yours,
> Naveen.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime