Re: [Sigtran] Number of links towards a DPC (ITU)
"David Laight" <David.Laight@ACULAB.COM> Mon, 17 June 2013 09:12 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 5319321F9AA8 for <sigtran@ietfa.amsl.com>;
Mon, 17 Jun 2013 02:12:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Level:
X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[AWL=0.949,
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 Luy6MIFCKyln for
<sigtran@ietfa.amsl.com>; Mon, 17 Jun 2013 02:12:00 -0700 (PDT)
Received: from mx0.aculab.com (mx0.aculab.com [213.249.233.131]) by
ietfa.amsl.com (Postfix) with SMTP id 692CF21F9A7E for <sigtran@ietf.org>;
Mon, 17 Jun 2013 02:11:58 -0700 (PDT)
Received: (qmail 13027 invoked from network); 17 Jun 2013 09:11:48 -0000
Received: from localhost (127.0.0.1) by mx0.aculab.com with SMTP;
17 Jun 2013 09:11:48 -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 09943-09 for
<sigtran@ietf.org>; Mon, 17 Jun 2013 10:11:47 +0100 (BST)
Received: (qmail 12996 invoked by uid 599); 17 Jun 2013 09:11:47 -0000
Received: from unknown (HELO saturn3.Aculab.com) (10.202.163.5) by
mx0.aculab.com (qpsmtpd/0.28) with ESMTP; Mon, 17 Jun 2013 10:11:47 +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: Mon, 17 Jun 2013 10:10:52 +0100
Message-ID: <AE90C24D6B3A694183C094C60CF0A2F6026B7291@saturn3.aculab.com>
In-Reply-To: <20130614215503.GA966@openss7.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sigtran] Number of links towards a DPC (ITU)
Thread-Index: Ac5pSkumDEqOU/BORwqpwaG7Yn4b+QB7Quyg
References: <CAE4qXDFfy+7BycUNrWNGm=Lo4U=WMZH9FDjw1kqWy71nKNbEhw@mail.gmail.com>
<20130614215503.GA966@openss7.org>
From: "David Laight" <David.Laight@ACULAB.COM>
To: <bidulock@openss7.org>, "Arvind Kumar" <arvindverma77@gmail.com>
X-Virus-Scanned: by iCritical at mx0.aculab.com
Cc: 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 09:12:05 -0000
> 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] Number of links towards a DPC (ITU) Arvind Kumar
- Re: [Sigtran] Number of links towards a DPC (ITU) David Laight
- Re: [Sigtran] Number of links towards a DPC (ITU) Brian F. G. Bidulock
- Re: [Sigtran] Number of links towards a DPC (ITU) David Laight
- Re: [Sigtran] Number of links towards a DPC (ITU) Brian F. G. Bidulock
- Re: [Sigtran] Number of links towards a DPC (ITU) David Laight
- Re: [Sigtran] Number of links towards a DPC (ITU) Brian F. G. Bidulock
- Re: [Sigtran] Number of links towards a DPC (ITU) Nemana, Satya
- Re: [Sigtran] Number of links towards a DPC (ITU) Brian F. G. Bidulock
- Re: [Sigtran] Number of links towards a DPC (ITU) David Laight
- Re: [Sigtran] Number of links towards a DPC (ITU) Nemana, Satya
- Re: [Sigtran] Number of links towards a DPC (ITU) David Laight