IETF Logo Mail Archive

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

"David Laight" <David.Laight@ACULAB.COM> Mon, 17 June 2013 10:54 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 63EFF21F88EA for <sigtran@ietfa.amsl.com>; Mon, 17 Jun 2013 03:54:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.125
X-Spam-Level:
X-Spam-Status: No, score=-2.125 tagged_above=-999 required=5 tests=[AWL=0.474, 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 TZkB+eWjZ8Am for <sigtran@ietfa.amsl.com>; Mon, 17 Jun 2013 03:54:00 -0700 (PDT)
Received: from mx0.aculab.com (mx0.aculab.com [213.249.233.131]) by ietfa.amsl.com (Postfix) with SMTP id E782021F9BBB for <sigtran@ietf.org>; Mon, 17 Jun 2013 03:53:21 -0700 (PDT)
Received: (qmail 623 invoked from network); 17 Jun 2013 10:53:02 -0000
Received: from localhost (127.0.0.1) by mx0.aculab.com with SMTP; 17 Jun 2013 10:53:02 -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 26592-08 for <sigtran@ietf.org>; Mon, 17 Jun 2013 11:53:01 +0100 (BST)
Received: (qmail 597 invoked by uid 599); 17 Jun 2013 10:53:01 -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 11:53:01 +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 11:52:03 +0100
Message-ID: <AE90C24D6B3A694183C094C60CF0A2F6026B7292@saturn3.aculab.com>
In-Reply-To: <20130617101828.GA17340@openss7.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sigtran] Number of links towards a DPC (ITU)
Thread-Index: Ac5rRAkB0CpFwTMlSUG/dAr5dMBqFwAAg1mg
References: <CAE4qXDFfy+7BycUNrWNGm=Lo4U=WMZH9FDjw1kqWy71nKNbEhw@mail.gmail.com> <20130614215503.GA966@openss7.org> <AE90C24D6B3A694183C094C60CF0A2F6026B7291@saturn3.aculab.com> <20130617101828.GA17340@openss7.org>
From: "David Laight" <David.Laight@ACULAB.COM>
To: <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: Mon, 17 Jun 2013 10:54:09 -0000

> > 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.
> 
> I don't know where you got that idea.

>From deciding not to do it when fixing our mtp3 routing rules!

Q.704 section 2.3 states that the routing is based on information
from the routing label - normally the sls and dpc.
With 2 linksets of 16 links the 'normal' link assignment could use
one bit of the sls to select between the linksets and the low bit
of the dpc and the other 3 bits of the sls to select one of the
16 links in the linkset.
This would be perfectly valid.

> See Figure A.3/Q.705.  Count the
> number of links possible in a linkset (not a combined linkset).
> 8 links per A linkset, 4 links per B/D linkset.

Q.705 A is only an example mesh network.
The appendix is describing the routing under fault conditions.

	David

v2.8.7 | Report a Bug | By Email