[Dime] RFC 3588 (Diameter Base Protocol) - Section 2.1.1. SCTP Guidelines

Victor Pascual Avila <victor.pascual.avila@gmail.com> Mon, 26 April 2010 07:54 UTC

Return-Path: <victor.pascual.avila@gmail.com>
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 949CE3A6869 for <dime@core3.amsl.com>; Mon, 26 Apr 2010 00:54:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level:
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001]
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 UD3-msQEKurJ for <dime@core3.amsl.com>; Mon, 26 Apr 2010 00:54:40 -0700 (PDT)
Received: from mail-bw0-f217.google.com (mail-bw0-f217.google.com [209.85.218.217]) by core3.amsl.com (Postfix) with ESMTP id 619A73A6907 for <dime@ietf.org>; Mon, 26 Apr 2010 00:54:38 -0700 (PDT)
Received: by bwz9 with SMTP id 9so1665613bwz.29 for <dime@ietf.org>; Mon, 26 Apr 2010 00:54:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=O0c+4gNI/ywFcsFIxa+Qw2LU1pigwnlPsj6sONx+Uy0=; b=eeaqgIQSyzlZbWFuXH5+g7Ze1RYaLuijfp9FQ89TZrL/d6AaJyqimrkK2r0H1uLoEJ nFXF6bs+1eqRZCPckqZSMqJQYjOBfTP6SWCTu9htqpaT/NeOw/QB+FT9u2TW/aP1/ODm MiAy1HTXdDHhQOUEJQJOomt+spJVCP5ZJoufc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=t34CiGRxhpW8VEtAb72Zh5P2F79S/FN3D+aLB/C/pJZxjD7ypfJkUHc6E9E/YanHVy mwMp06NE8WQtBBwM/UuF0KOZ72C2mzAF/Awfunm7gtf1SnByj8KmnMzEiCfe+WCNf+Bc z/1GtkqSCB8kMftrpEUFTd3flA8ONEuBqyvZA=
MIME-Version: 1.0
Received: by 10.204.162.199 with SMTP id w7mr2305167bkx.211.1272268463121; Mon, 26 Apr 2010 00:54:23 -0700 (PDT)
Received: by 10.204.71.9 with HTTP; Mon, 26 Apr 2010 00:54:23 -0700 (PDT)
Date: Mon, 26 Apr 2010 09:54:23 +0200
Message-ID: <s2v618e24241004260054z7f767689nfba37fbf82b1f030@mail.gmail.com>
From: Victor Pascual Avila <victor.pascual.avila@gmail.com>
To: dime@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: [Dime] RFC 3588 (Diameter Base Protocol) - Section 2.1.1. SCTP Guidelines
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: Mon, 26 Apr 2010 07:54:44 -0000

Hi,

Apologies in case this is not the appropriate list for the question
below-- I'd appreciate pointers to any other list.

RFC 3588 - Section  2.1.1 (SCTP Guidelines) states the following: "To
prevent blocking: All Diameter nodes SHOULD utilize all SCTP streams
available to the association to prevent head-of-the-line blocking."
While RFC 3539 - Section 3.8.1 (Using SCTP Streams to Prevent Head of
Line Blocking) also addresses multi-streaming, it's not clear to me
whether:

a) Diameter transactions need to be mapped into SCTP streams (ie; send
Diameter messages belonging to the same transaction over the same SCTP
stream and messages belonging to different transactions over different
SCTP streams-- as long as there are enough available streams)
b) Ordered vs unordered delivery: for the above mechanism, I
understand TLS would require ordered delivery. When TLS is not used
(say, IPSec is used instead), do we really need ordered delivery?

Thanks in advance for any clarification,
-- 
Victor Pascual Ávila