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

"Nemana, Satya" <snemana@sonusnet.com> Mon, 17 June 2013 15:28 UTC

Return-Path: <snemana@sonusnet.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 9178321F9D15 for <sigtran@ietfa.amsl.com>; Mon, 17 Jun 2013 08:28:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.734
X-Spam-Level:
X-Spam-Status: No, score=-4.734 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_LOLITA1=1.865, RCVD_IN_DNSWL_MED=-4]
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 oh-bmqhf0f3r for <sigtran@ietfa.amsl.com>; Mon, 17 Jun 2013 08:28:40 -0700 (PDT)
Received: from p01c11o141.mxlogic.net (p01c11o141.mxlogic.net [208.65.144.64]) by ietfa.amsl.com (Postfix) with ESMTP id AA79E21F99BA for <sigtran@ietf.org>; Mon, 17 Jun 2013 08:28:40 -0700 (PDT)
Received: from unknown [69.147.176.212] (EHLO USMA-EX-HUB2.sonusnet.com) by p01c11o141.mxlogic.net(mxl_mta-7.1.0-3) with ESMTP id 82b2fb15.2ab720439940.170344.00-590.423605.p01c11o141.mxlogic.net (envelope-from <snemana@sonusnet.com>); Mon, 17 Jun 2013 09:28:40 -0600 (MDT)
X-MXL-Hash: 51bf2b2867d25837-5f21614165ab7a0537be8c72d8fe11df23a4a1e0
Received: from unknown [69.147.176.212] (EHLO USMA-EX-HUB2.sonusnet.com) by p01c11o141.mxlogic.net(mxl_mta-7.1.0-3) over TLS secured channel with ESMTP id 4da2fb15.0.169611.00-378.421669.p01c11o141.mxlogic.net (envelope-from <snemana@sonusnet.com>); Mon, 17 Jun 2013 09:27:28 -0600 (MDT)
X-MXL-Hash: 51bf2ae0451abc5b-1390d0838d2cc29a39d691ae8d0dd80bfe7a327d
Received: from USMA-EX-MB2.sonusnet.com ([fe80::c51d:eb9c:bce7:e4b0]) by USMA-EX-HUB2.sonusnet.com ([2002:42cb:5a11::42cb:5a11]) with mapi id 14.02.0342.003; Mon, 17 Jun 2013 11:27:14 -0400
From: "Nemana, Satya" <snemana@sonusnet.com>
To: David Laight <David.Laight@ACULAB.COM>, "bidulock@openss7.org" <bidulock@openss7.org>, Arvind Kumar <arvindverma77@gmail.com>
Thread-Topic: [Sigtran] Number of links towards a DPC (ITU)
Thread-Index: AQHOaUna7moZqh9SiEy2tkMshtODDpk55ZsAgAAk7sA=
Date: Mon, 17 Jun 2013 15:27:13 +0000
Message-ID: <A4C75474DC72BC44A5517224ED0604C5021E01E8@USMA-EX-MB2.sonusnet.com>
References: <CAE4qXDFfy+7BycUNrWNGm=Lo4U=WMZH9FDjw1kqWy71nKNbEhw@mail.gmail.com> <20130614215503.GA966@openss7.org> <AE90C24D6B3A694183C094C60CF0A2F6026B7291@saturn3.aculab.com>
In-Reply-To: <AE90C24D6B3A694183C094C60CF0A2F6026B7291@saturn3.aculab.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.128.99.157]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-AnalysisOut: [v=2.0 cv=Q/1lFfKa c=1 sm=1 a=ed0SwufR/ZNkx8DvM7kK7A==:17 a]
X-AnalysisOut: [=eXd16KwrWoYA:10 a=nMr1u6ZHNpMA:10 a=URNJFqk9g_oA:10 a=BLc]
X-AnalysisOut: [eEmwcHowA:10 a=kj9zAlcOel0A:10 a=xqWC_Br6kY4A:10 a=kUVcWBO]
X-AnalysisOut: [SAAAA:8 a=eEvZEOzEWDkA:10 a=48vgC7mUAAAA:8 a=cEINi2uUAAAA:]
X-AnalysisOut: [8 a=Kf1CyEA6pIUcmrYzPy8A:9 a=CjuIK1q_8ugA:10 a=lZB815dzVvQ]
X-AnalysisOut: [A:10 a=bI6W1tgPgz0A:10 a=z80G4o-e6zBCHj4T:21 a=D_Z_BvsWtpu]
X-AnalysisOut: [FkGRk:21]
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <snemana@sonusnet.com>
X-SOURCE-IP: [69.147.176.212]
Cc: "sigtran@ietf.org" <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: Mon, 17 Jun 2013 15:28:45 -0000

My 2 cents.
The ITU spec may not say this, but why not do this.
1) Use the LSB to select the linkset within a combined linkset.
2) Once the Linkset is selected, use the full SLS value to select one of the links in the linkset.
In this way, we can still have 16 links in each linkset and combined linkset can have 32 links and still loadshare across all the links.
Each linkset will still have 16 of the SLS values so, there won't be any issues of un-even loadsharing even if some links go down in the route to the final destination.

Regards,
Satya



-----Original Message-----
From: sigtran-bounces@ietf.org [mailto:sigtran-bounces@ietf.org] On Behalf Of David Laight
Sent: 17 June 2013 10:11
To: bidulock@openss7.org; Arvind Kumar
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Number of links towards a DPC (ITU)

> ITU has a 4-bit SLS and a 4 bit SLC.  The SLS and SLC is shared under 
> ITU and ITU does not do SLS rotation.  Therefore, because 1 bit is 
> used for link-set selection, there can only be 8 links in a linkset 
> (16 links in a combined linkset).

In ITU each linkset can have 16 links.
Brian is right in that MTP3 only has a 4 bit SLS value to select the destination link, so traffic to a specific destination will only use a maximum of 16 links even if there are routes by 2 adjacents and there are 16 links in the linkset to each.

If you have two linksets with 16 links each, the routing rules for different destinations could be arranged to use different links in order to utilise all 32 links.

> ANSI has an 8-bit SLS and a 5-bit SLC.  The SLS and SLC are not shared 
> and ANSI does SLS rotation.  Therefore, it is possible to have 32 
> links in a linkset (64 links in a combined linkset).  Using the old 
> 5-bit SLS it was only possible to have 16 links in a linkset and 32 
> links in a combined linkset because 1 of the 5 bits was used for 
> linkset selection within a combined linkset.

ANSI only has 4 bits for the SLC (not 5), so a linkset is limited to 16 links.
However the larger SLS value (8 bits, 5 in some earlier versions) means that MTP3 can loadshare between more links.

It also isn't quite right to say that one of the bits is used for linkset selection. If some of the links are down, the sls that would be assigned to the 'down' links are evenly spread across all of the working links, not just assigned to the working links in their original linkset (this might be a config option since the ANSI and ITU specs differ here.)

An endsystem ITU MTP3 may have more SLS bits available, so could loadshare between more than 16 links.

	David



_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www.ietf.org/mailman/listinfo/sigtran