Re: [Sigtran] Number of links towards a DPC (ITU)

"David Laight" <David.Laight@ACULAB.COM> Tue, 18 June 2013 09:16 UTC

Return-Path: <David.Laight@ACULAB.COM>
X-Original-To: sigtran@ietfa.amsl.com
Delivered-To: sigtran@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68D2521F8904 for <sigtran@ietfa.amsl.com>; Tue, 18 Jun 2013 02:16:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.362
X-Spam-Level:
X-Spam-Status: No, score=-2.362 tagged_above=-999 required=5 tests=[AWL=0.237, BAYES_00=-2.599]
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 k+gt4F-HVA9T for <sigtran@ietfa.amsl.com>; Tue, 18 Jun 2013 02:16:27 -0700 (PDT)
Received: from mx0.aculab.com (mx0.aculab.com [213.249.233.131]) by ietfa.amsl.com (Postfix) with SMTP id 20A4421E8085 for <sigtran@ietf.org>; Tue, 18 Jun 2013 02:16:25 -0700 (PDT)
Received: (qmail 7681 invoked from network); 18 Jun 2013 09:16:22 -0000
Received: from localhost (127.0.0.1) by mx0.aculab.com with SMTP; 18 Jun 2013 09:16:22 -0000
Received: from mx0.aculab.com ([127.0.0.1]) by localhost (mx0.aculab.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 02378-09 for <sigtran@ietf.org>; Tue, 18 Jun 2013 10:16:21 +0100 (BST)
Received: (qmail 7345 invoked by uid 599); 18 Jun 2013 09:16:14 -0000
Received: from unknown (HELO saturn3.Aculab.com) (10.202.163.5) by mx0.aculab.com (qpsmtpd/0.28) with ESMTP; Tue, 18 Jun 2013 10:16:14 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 18 Jun 2013 09:57:30 +0100
Message-ID: <AE90C24D6B3A694183C094C60CF0A2F6026B7296@saturn3.aculab.com>
In-Reply-To: <A4C75474DC72BC44A5517224ED0604C5021E027A@USMA-EX-MB2.sonusnet.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sigtran] Number of links towards a DPC (ITU)
Thread-Index: AQHOaUna7moZqh9SiEy2tkMshtODDpk55ZsAgAAk7sCAAE4NAP//vR5QgAEXrGA=
References: <CAE4qXDFfy+7BycUNrWNGm=Lo4U=WMZH9FDjw1kqWy71nKNbEhw@mail.gmail.com> <20130614215503.GA966@openss7.org> <AE90C24D6B3A694183C094C60CF0A2F6026B7291@saturn3.aculab.com> <A4C75474DC72BC44A5517224ED0604C5021E01E8@USMA-EX-MB2.sonusnet.com> <20130617160224.GA23895@openss7.org> <A4C75474DC72BC44A5517224ED0604C5021E027A@USMA-EX-MB2.sonusnet.com>
From: "David Laight" <David.Laight@ACULAB.COM>
To: "Nemana, Satya" <snemana@sonusnet.com>, <bidulock@openss7.org>
X-Virus-Scanned: by iCritical at mx0.aculab.com
Cc: Arvind Kumar <arvindverma77@gmail.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Number of links towards a DPC (ITU)
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 09:16:48 -0000

> Yeah, I got it wrong.
> My idea was to use the SLS but still generate enough SLS for the linkset locally.
> But this would cause the problem of mis-sequencing when links go down.
> But that seems to be the only other alternative of using the entire 32 links.

For locally generated traffic the local ISUP/SCCP could generate
more than 4 bits of sls (it probably generates 8 bits for ANSI
and mtp3 masks them for ITU) so MTP3 could loadshare over all
32 links - but your mtp3 is unlikely to behave that way.

If the traffic is TCAP/SCCP and 'route on GT' and you have
2 (or more) 'next hop' destination SCCP systems you can get
the TCAP traffic to use all 32 links.

Similarly 'class 0' SCCP traffic (order not guaranteed)
probably has an SLS assigned sequentially by SCCP.
The local MTP3 could safely reassign the SLS so that it
could use all 32 (or more) links in a combined linkset.

We have some other configurations that can loadshare over
32 links.

	David