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

"David Laight" <David.Laight@ACULAB.COM> Mon, 17 June 2013 16:30 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 2DDBE21F9CB3 for <sigtran@ietfa.amsl.com>; Mon, 17 Jun 2013 09:30:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.283
X-Spam-Level:
X-Spam-Status: No, score=-2.283 tagged_above=-999 required=5 tests=[AWL=0.316, 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 VdXXoMoEgs38 for <sigtran@ietfa.amsl.com>; Mon, 17 Jun 2013 09:30:50 -0700 (PDT)
Received: from mx0.aculab.com (mx0.aculab.com [213.249.233.131]) by ietfa.amsl.com (Postfix) with SMTP id AC62F21F99D4 for <sigtran@ietf.org>; Mon, 17 Jun 2013 09:30:49 -0700 (PDT)
Received: (qmail 3444 invoked from network); 17 Jun 2013 16:30:39 -0000
Received: from localhost (127.0.0.1) by mx0.aculab.com with SMTP; 17 Jun 2013 16:30:39 -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 01672-04 for <sigtran@ietf.org>; Mon, 17 Jun 2013 17:30:36 +0100 (BST)
Received: (qmail 3386 invoked by uid 599); 17 Jun 2013 16:30:36 -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 17:30:36 +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 17:23:07 +0100
Message-ID: <AE90C24D6B3A694183C094C60CF0A2F6026B7295@saturn3.aculab.com>
In-Reply-To: <20130617160224.GA23895@openss7.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sigtran] Number of links towards a DPC (ITU)
Thread-Index: Ac5rdBU9SQR8U2UJQeec6ZjnYQTSGwAATJ9w
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>
From: "David Laight" <David.Laight@ACULAB.COM>
To: <bidulock@openss7.org>, "Nemana, Satya" <snemana@sonusnet.com>
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: Mon, 17 Jun 2013 16:30:55 -0000

> Satya,
> 
> Nemana, Satya wrote:                    (Mon, 17 Jun 2013 15:27:13)
> > 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.
> 
> So, XXX0 goes to one linkset and XXX1 goes to the other.
> 
> > 2) Once the Linkset is selected, use the full SLS value to select one
> >    of the links in the linkset.
> 
> On the first linkset, the entire SLS is XXX0.  There are only eight
> values here.  On the second linkset, the entire SLS is XXX1.  There
> are only eight values here.  So, 8 links per linkset, 16 links per
> combined linkset.

That just means that the traffic to that destination can only use 8 of
the links in the linkset - even if there are more.
So it might not make much sense to have 16 links in both linksets,
but that doesn't mean that it isn't allowed.

Consider the following network fragment:
Endpoint A has a linksets with 16 links to both B and C (SEP + STP).
Additionally A has routes to SEP D via both B and C.
Traffic to B will use all 16 direct links (backup route via C).
Traffic to D will loadshare between B and C, but will only use
16 of the 32 possible links (ideally 8 via B and 8 via C).

(Wonders what our MTP3 does when configured to evenly distribute
the sls across all the links ...)

	David