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

Victor Pascual Avila <victor.pascual.avila@gmail.com> Mon, 03 May 2010 10:27 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 8555028C119 for <dime@core3.amsl.com>; Mon, 3 May 2010 03:27:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.082
X-Spam-Level:
X-Spam-Status: No, score=-1.082 tagged_above=-999 required=5 tests=[AWL=-1.083, 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 fNm6LRF6Ui-q for <dime@core3.amsl.com>; Mon, 3 May 2010 03:27:04 -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 994EA3A6C26 for <dime@ietf.org>; Mon, 3 May 2010 03:27:02 -0700 (PDT)
Received: by bwz9 with SMTP id 9so1285859bwz.29 for <dime@ietf.org>; Mon, 03 May 2010 03:26:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=0aq+YhLMRzFVTpAI5Hi/4htGGgrERnkzQBpi/DlAIkI=; b=PpEFPXesPhLqMDnu6tSZ7V+h9Kq2lcGLDHf0lzGdW/baOBDhvpssi40+RNs3T2B/SQ yGxKbNjnY+f3cfgyhyQ+a4gbeClt8b1S0BjiwKzj6FBh+CPVJr4yMJEckhlThR9G6HHz sQwV7MeAr/ec4qNawIFL8WYEOARceLA021aA0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=oPR4Tm9EG0fgyECrfJmKCjVnshe1mLj0YgHeKjq2p185TfOxmfZYD/EwC5ldPmWw74 gmD0cjEBqM1+ZGTv7MklTsqotDLGKsO0581XdjdJ571CHYD/0rHV0/U4l8d1qHofBrI2 Os8V4gKzLW7ueqqix0FLLHwKaf0mJ86BIQXSU=
MIME-Version: 1.0
Received: by 10.204.126.88 with SMTP id b24mr9588106bks.79.1272882404784; Mon, 03 May 2010 03:26:44 -0700 (PDT)
Received: by 10.204.71.9 with HTTP; Mon, 3 May 2010 03:26:44 -0700 (PDT)
In-Reply-To: <s2v618e24241004260054z7f767689nfba37fbf82b1f030@mail.gmail.com>
References: <s2v618e24241004260054z7f767689nfba37fbf82b1f030@mail.gmail.com>
Date: Mon, 03 May 2010 12:26:44 +0200
Message-ID: <v2x618e24241005030326x810b6d7fr977d506896c9802e@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: Re: [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, 03 May 2010 10:27:05 -0000

Any opinions? Is the below worth to be clarified in 3588bis?

Thanks,
-Victor

On Mon, Apr 26, 2010 at 9:54 AM, Victor Pascual Avila
<victor.pascual.avila@gmail.com> wrote:
> 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
>



-- 
Victor Pascual Ávila