
From arvindverma77@gmail.com  Fri Jun 14 01:39:31 2013
Return-Path: <arvindverma77@gmail.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 B2BB621F9BFE for <sigtran@ietfa.amsl.com>; Fri, 14 Jun 2013 01:39:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 cAiyiD1J5IPf for <sigtran@ietfa.amsl.com>; Fri, 14 Jun 2013 01:39:30 -0700 (PDT)
Received: from mail-oa0-x236.google.com (mail-oa0-x236.google.com [IPv6:2607:f8b0:4003:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id 82D4821F9C07 for <sigtran@ietf.org>; Fri, 14 Jun 2013 01:39:28 -0700 (PDT)
Received: by mail-oa0-f54.google.com with SMTP id o6so380915oag.13 for <sigtran@ietf.org>; Fri, 14 Jun 2013 01:39:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=r6F4eYTqNutPAVRLkElsshz/UHYE5r0xlAV+/PFqxe8=; b=x3KQzs2x3kQuhVlL7Tr8NXonrYNVPk/eJv4iCXMiSXgvrW5OL7vXvDG+EEjcZ3LX8X 9lX3TMfRke+2xavUKLEIctQ9sujvxFBszTbnJQ2Sz2mjm7SCyFkFSfDpOynhcUAC/qkq qRIgu2ne1l5eV1ps7KufD0x2FK28EZJ6urA+525OtAnWgmrVME32PykfHk/JYhmLDU7H TyK/ednAcK+DLO4jXvurp09xoYXaIC1sQZb381zry26NJkQIdFTjlI8J62qTlNfSA5cI zVsG3xj5pUspHL0Owg6qpCU7/C0iQXpeNtjpL4pn2/vXJqzbYFp0OAVk3OozFvtS72v3 c1yw==
MIME-Version: 1.0
X-Received: by 10.60.174.83 with SMTP id bq19mr819528oec.80.1371199167925; Fri, 14 Jun 2013 01:39:27 -0700 (PDT)
Received: by 10.76.93.40 with HTTP; Fri, 14 Jun 2013 01:39:27 -0700 (PDT)
Date: Fri, 14 Jun 2013 14:09:27 +0530
Message-ID: <CAE4qXDFfy+7BycUNrWNGm=Lo4U=WMZH9FDjw1kqWy71nKNbEhw@mail.gmail.com>
From: Arvind Kumar <arvindverma77@gmail.com>
To: sigtran@ietf.org
Content-Type: multipart/alternative; boundary=089e0115f6c65210a904df192f5a
Subject: [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: Fri, 14 Jun 2013 08:39:31 -0000

--089e0115f6c65210a904df192f5a
Content-Type: text/plain; charset=ISO-8859-1

Hi All,

Would appreciate if somebody help me,
I have SS7 Stack with multiple OPC, I would like to create multiple
linksets towards a single destination (suppose 2000).

How many links are possible in all the link-sets. I know there is no
limitation of number of link-sets, but as I  understood, towards a given
destination the maximum number of links depends upon maximum value of SLS.

For ITU it could be 16.
But my doubt is I have mutiple OPCs for my SS7 Stack, could number of
links  be possible
= number of OPCs * 16


Please comment.
 Regards,


On Sun, May 5, 2013 at 12:30 AM, <sigtran-request@ietf.org> wrote:

> If you have received this digest without all the individual message
> attachments you will need to update your digest options in your list
> subscription.  To do so, go to
>
> https://www.ietf.org/mailman/listinfo/sigtran
>
> Click the 'Unsubscribe or edit options' button, log in, and set "Get
> MIME or Plain Text Digests?" to MIME.  You can set this option
> globally for all the list digests you receive at this point.
>
>
>
> Send Sigtran mailing list submissions to
>         sigtran@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://www.ietf.org/mailman/listinfo/sigtran
> or, via email, send a message with subject or body 'help' to
>         sigtran-request@ietf.org
>
> You can reach the person managing the list at
>         sigtran-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Sigtran digest..."
>
>
> Today's Topics:
>
>    1. Abort chunk in SCTP (Norah Jones)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 4 May 2013 06:50:12 +0000
> From: Norah Jones <nh.jones01@gmail.com>
> To: sigtran@ietf.org
> Subject: [Sigtran] Abort chunk in SCTP
> Message-ID: <abcd1234abc123ab12a0000000335000020000005002@gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> I am using LKSCTP in my project, one sometime I see that by box receives
> About chunk from the peer. Now question is what are the possibilities for
> which we can receive abort chunk from remote.
>
>
> Thanks,
> Norah Jones
>
>
>
>
> ------------------------------
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www.ietf.org/mailman/listinfo/sigtran
>
>
> End of Sigtran Digest, Vol 102, Issue 1
> ***************************************
>

--089e0115f6c65210a904df192f5a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>Hi All,<br></div><br></div><div>Would appreciate=
 if somebody help me,<br></div><div>I have SS7 Stack with multiple OPC, I w=
ould like to create multiple linksets towards a single destination (suppose=
 2000).<br>


<br></div><div>How many links are possible in all the link-sets. I know=20
there is no limitation of number of link-sets, but as I=A0 understood,=20
towards a given destination the maximum number of links depends upon=20
maximum value of SLS.<br>
<br></div><div>For ITU it could be 16.<br></div><div>But my doubt is I have=
 mutiple OPCs for my SS7 Stack, could number of links=A0 be possible <br></=
div><div>=3D number of OPCs * 16<br><br><br></div><div>Please comment.<br>

</div>
Regards,<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Su=
n, May 5, 2013 at 12:30 AM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:sigtra=
n-request@ietf.org" target=3D"_blank">sigtran-request@ietf.org</a>&gt;</spa=
n> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">If you have received this digest without all=
 the individual message<br>
attachments you will need to update your digest options in your list<br>
subscription. =A0To do so, go to<br>
<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sigtran" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/sigtran</a><br>
<br>
Click the &#39;Unsubscribe or edit options&#39; button, log in, and set &qu=
ot;Get<br>
MIME or Plain Text Digests?&quot; to MIME. =A0You can set this option<br>
globally for all the list digests you receive at this point.<br>
<br>
<br>
<br>
Send Sigtran mailing list submissions to<br>
=A0 =A0 =A0 =A0 <a href=3D"mailto:sigtran@ietf.org">sigtran@ietf.org</a><br=
>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
=A0 =A0 =A0 =A0 <a href=3D"https://www.ietf.org/mailman/listinfo/sigtran" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/sigtran</a><br>
or, via email, send a message with subject or body &#39;help&#39; to<br>
=A0 =A0 =A0 =A0 <a href=3D"mailto:sigtran-request@ietf.org">sigtran-request=
@ietf.org</a><br>
<br>
You can reach the person managing the list at<br>
=A0 =A0 =A0 =A0 <a href=3D"mailto:sigtran-owner@ietf.org">sigtran-owner@iet=
f.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than &quot;Re: Contents of Sigtran digest...&quot;<br>
<br>
<br>
Today&#39;s Topics:<br>
<br>
=A0 =A01. Abort chunk in SCTP (Norah Jones)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sat, 4 May 2013 06:50:12 +0000<br>
From: Norah Jones &lt;<a href=3D"mailto:nh.jones01@gmail.com">nh.jones01@gm=
ail.com</a>&gt;<br>
To: <a href=3D"mailto:sigtran@ietf.org">sigtran@ietf.org</a><br>
Subject: [Sigtran] Abort chunk in SCTP<br>
Message-ID: &lt;<a href=3D"mailto:abcd1234abc123ab12a0000000335000020000005=
002@gmail.com">abcd1234abc123ab12a0000000335000020000005002@gmail.com</a>&g=
t;<br>
Content-Type: text/plain; charset=3D&quot;utf-8&quot;<br>
<br>
Hi,<br>
<br>
I am using LKSCTP in my project, one sometime I see that by box receives Ab=
out chunk from the peer. Now question is what are the possibilities for whi=
ch we can receive abort chunk from remote.<br>
<br>
<br>
Thanks,<br>
Norah Jones<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Sigtran mailing list<br>
<a href=3D"mailto:Sigtran@ietf.org">Sigtran@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sigtran" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/sigtran</a><br>
<br>
<br>
End of Sigtran Digest, Vol 102, Issue 1<br>
***************************************<br>
</blockquote></div><br></div></div>

--089e0115f6c65210a904df192f5a--

From David.Laight@ACULAB.COM  Fri Jun 14 01:50:20 2013
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 98BF221F9AEF for <sigtran@ietfa.amsl.com>; Fri, 14 Jun 2013 01:50:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.702
X-Spam-Level: 
X-Spam-Status: No, score=-0.702 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BAD_LINEBREAK=0.5, MIME_QP_LONG_LINE=1.396]
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 1vM8GeevE9Ft for <sigtran@ietfa.amsl.com>; Fri, 14 Jun 2013 01:50:16 -0700 (PDT)
Received: from mx0.aculab.com (mx0.aculab.com [213.249.233.131]) by ietfa.amsl.com (Postfix) with SMTP id AE24D21F9ADE for <sigtran@ietf.org>; Fri, 14 Jun 2013 01:50:15 -0700 (PDT)
Received: (qmail 17556 invoked from network); 14 Jun 2013 08:50:14 -0000
Received: from localhost (127.0.0.1) by mx0.aculab.com with SMTP; 14 Jun 2013 08:50:14 -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 15197-10 for <sigtran@ietf.org>; Fri, 14 Jun 2013 09:50:12 +0100 (BST)
Received: (qmail 17538 invoked by uid 599); 14 Jun 2013 08:50:12 -0000
Received: from unknown (HELO saturn3.Aculab.com) (10.202.163.5) by mx0.aculab.com (qpsmtpd/0.28) with ESMTP; Fri, 14 Jun 2013 09:50:12 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CE68DC.18988BC5"
Date: Fri, 14 Jun 2013 09:49:35 +0100
Message-ID: <AE90C24D6B3A694183C094C60CF0A2F6026B728F@saturn3.aculab.com>
In-Reply-To: <CAE4qXDFfy+7BycUNrWNGm=Lo4U=WMZH9FDjw1kqWy71nKNbEhw@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sigtran] Number of links towards a DPC (ITU)
Thread-Index: Ac5o2rwj0Cqtr0DvTRuYc775v/ic/wAAIDlg
References: <CAE4qXDFfy+7BycUNrWNGm=Lo4U=WMZH9FDjw1kqWy71nKNbEhw@mail.gmail.com>
From: "David Laight" <David.Laight@ACULAB.COM>
To: "Arvind Kumar" <arvindverma77@gmail.com>, <sigtran@ietf.org>
X-Virus-Scanned: by iCritical at mx0.aculab.com
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: Fri, 14 Jun 2013 08:50:20 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CE68DC.18988BC5
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

ss7 allows 16 signalling links in all linksets (for ITI and ANSI), so =
with multiple OPC you can

have 16 signalling links to a single destination for each OPC.

However your ss7 stack might have restrictions on the number of =
supported signalling links

since processing a FISU every 6 byte times isn=92t for the faint =
hearted!

=20

Cards that support 64 signalling links (spread over 8 E1/t1 links) are =
available.

=20

                David

=20

From: sigtran-bounces@ietf.org [mailto:sigtran-bounces@ietf.org] On =
Behalf Of Arvind Kumar
Sent: 14 June 2013 09:39
To: sigtran@ietf.org
Subject: [Sigtran] Number of links towards a DPC (ITU)

=20

Hi All,

=20

Would appreciate if somebody help me,

I have SS7 Stack with multiple OPC, I would like to create multiple =
linksets towards a single destination (suppose 2000).

How many links are possible in all the link-sets. I know there is no =
limitation of number of link-sets, but as I  understood, towards a given =
destination the maximum number of links depends upon maximum value of =
SLS.

For ITU it could be 16.

But my doubt is I have mutiple OPCs for my SS7 Stack, could number of =
links  be possible=20

=3D number of OPCs * 16



Please comment.

Regards,

=20

On Sun, May 5, 2013 at 12:30 AM, <sigtran-request@ietf.org> wrote:

If you have received this digest without all the individual message
attachments you will need to update your digest options in your list
subscription.  To do so, go to

https://www.ietf.org/mailman/listinfo/sigtran

Click the 'Unsubscribe or edit options' button, log in, and set "Get
MIME or Plain Text Digests?" to MIME.  You can set this option
globally for all the list digests you receive at this point.



Send Sigtran mailing list submissions to
        sigtran@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://www.ietf.org/mailman/listinfo/sigtran
or, via email, send a message with subject or body 'help' to
        sigtran-request@ietf.org

You can reach the person managing the list at
        sigtran-owner@ietf.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Sigtran digest..."


Today's Topics:

   1. Abort chunk in SCTP (Norah Jones)


----------------------------------------------------------------------

Message: 1
Date: Sat, 4 May 2013 06:50:12 +0000
From: Norah Jones <nh.jones01@gmail.com>
To: sigtran@ietf.org
Subject: [Sigtran] Abort chunk in SCTP
Message-ID: <abcd1234abc123ab12a0000000335000020000005002@gmail.com>
Content-Type: text/plain; charset=3D"utf-8"

Hi,

I am using LKSCTP in my project, one sometime I see that by box receives =
About chunk from the peer. Now question is what are the possibilities =
for which we can receive abort chunk from remote.


Thanks,
Norah Jones




------------------------------

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


End of Sigtran Digest, Vol 102, Issue 1
***************************************

=20


=0D=0A
=0D=
------_=_NextPart_001_01CE68DC.18988BC5
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1252"><meta name=3DGenerator content=3D"Microsoft Word =
12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>ss7 allows 16 signalling links in all linksets (for ITI and ANSI), so =
with multiple OPC you can<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>have 16 signalling links to a single destination for each =
OPC.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>However your ss7 stack might have restrictions on the number of =
supported signalling links<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>since processing a FISU every 6 byte times isn=92t for the faint =
hearted!<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Cards that support 64 signalling links (spread over 8 E1/t1 links) =
are available.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
David<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
sigtran-bounces@ietf.org [mailto:sigtran-bounces@ietf.org] <b>On Behalf =
Of </b>Arvind Kumar<br><b>Sent:</b> 14 June 2013 09:39<br><b>To:</b> =
sigtran@ietf.org<br><b>Subject:</b> [Sigtran] Number of links towards a =
DPC (ITU)<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><div><p =
class=3DMsoNormal>Hi All,<o:p></o:p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Would appreciate if somebody help =
me,<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>I have SS7 Stack with multiple OPC, I =
would like to create multiple linksets towards a single destination =
(suppose 2000).<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>How many links are possible in all the =
link-sets. I know there is no limitation of number of link-sets, but as =
I&nbsp; understood, towards a given destination the maximum number of =
links depends upon maximum value of SLS.<o:p></o:p></p></div><div><p =
class=3DMsoNormal>For ITU it could be 16.<o:p></o:p></p></div><div><p =
class=3DMsoNormal>But my doubt is I have mutiple OPCs for my SS7 Stack, =
could number of links&nbsp; be possible <o:p></o:p></p></div><div><p =
class=3DMsoNormal style=3D'margin-bottom:12.0pt'>=3D number of OPCs * =
16<br><br><o:p></o:p></p></div><div><p class=3DMsoNormal>Please =
comment.<o:p></o:p></p></div><p =
class=3DMsoNormal>Regards,<o:p></o:p></p><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>On Sun, May 5, 2013 at 12:30 AM, &lt;<a =
href=3D"mailto:sigtran-request@ietf.org" =
target=3D"_blank">sigtran-request@ietf.org</a>&gt; =
wrote:<o:p></o:p></p><p class=3DMsoNormal>If you have received this =
digest without all the individual message<br>attachments you will need =
to update your digest options in your list<br>subscription. &nbsp;To do =
so, go to<br><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/sigtran" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/sigtran</a><br><b=
r>Click the 'Unsubscribe or edit options' button, log in, and set =
&quot;Get<br>MIME or Plain Text Digests?&quot; to MIME. &nbsp;You can =
set this option<br>globally for all the list digests you receive at this =
point.<br><br><br><br>Send Sigtran mailing list submissions to<br>&nbsp; =
&nbsp; &nbsp; &nbsp; <a =
href=3D"mailto:sigtran@ietf.org">sigtran@ietf.org</a><br><br>To =
subscribe or unsubscribe via the World Wide Web, visit<br>&nbsp; &nbsp; =
&nbsp; &nbsp; <a href=3D"https://www.ietf.org/mailman/listinfo/sigtran" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/sigtran</a><br>or=
, via email, send a message with subject or body 'help' to<br>&nbsp; =
&nbsp; &nbsp; &nbsp; <a =
href=3D"mailto:sigtran-request@ietf.org">sigtran-request@ietf.org</a><br>=
<br>You can reach the person managing the list at<br>&nbsp; &nbsp; =
&nbsp; &nbsp; <a =
href=3D"mailto:sigtran-owner@ietf.org">sigtran-owner@ietf.org</a><br><br>=
When replying, please edit your Subject line so it is more =
specific<br>than &quot;Re: Contents of Sigtran =
digest...&quot;<br><br><br>Today's Topics:<br><br>&nbsp; &nbsp;1. Abort =
chunk in SCTP (Norah =
Jones)<br><br><br>-------------------------------------------------------=
---------------<br><br>Message: 1<br>Date: Sat, 4 May 2013 06:50:12 =
+0000<br>From: Norah Jones &lt;<a =
href=3D"mailto:nh.jones01@gmail.com">nh.jones01@gmail.com</a>&gt;<br>To: =
<a href=3D"mailto:sigtran@ietf.org">sigtran@ietf.org</a><br>Subject: =
[Sigtran] Abort chunk in SCTP<br>Message-ID: &lt;<a =
href=3D"mailto:abcd1234abc123ab12a0000000335000020000005002@gmail.com">ab=
cd1234abc123ab12a0000000335000020000005002@gmail.com</a>&gt;<br>Content-T=
ype: text/plain; charset=3D&quot;utf-8&quot;<br><br>Hi,<br><br>I am =
using LKSCTP in my project, one sometime I see that by box receives =
About chunk from the peer. Now question is what are the possibilities =
for which we can receive abort chunk from =
remote.<br><br><br>Thanks,<br>Norah =
Jones<br><br><br><br><br>------------------------------<br><br>__________=
_____________________________________<br>Sigtran mailing list<br><a =
href=3D"mailto:Sigtran@ietf.org">Sigtran@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/sigtran" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/sigtran</a><br><b=
r><br>End of Sigtran Digest, Vol 102, Issue =
1<br>***************************************<o:p></o:p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></div>
<br>=
<FONT face=3DTahoma color=3D#484830 size=3D2></FONT>=0D=0A
<DIV><FONT face=3DTahoma color=3D#484830 size=3D1>Registered Address Lakeside, Br=
amley Road, Mount Farm, Milton Keynes, MK1 1PT, UK<BR>Registration No: 13973=
86 (Wales)</FONT></DIV>=0D=0A
<DIV><FONT face=3DArial color=3D#008000 size=3D2><FONT face=3DWebdings size=3D5>=0D=0A
<P align=3Dcenter><FONT face=3DArial color=3D#008000><FONT size=3D1><FONT face=3DWebd=
ings>P<STRONG> </STRONG></FONT><STRONG>Please consider the environment and d=
on't print this e-mail unless you really need to</STRONG></FONT></FONT></P><=
/FONT></FONT></DIV>
<br>=
</body></h=
tml>
------_=_NextPart_001_01CE68DC.18988BC5--

From bidulock@openss7.org  Fri Jun 14 14:55:13 2013
Return-Path: <bidulock@openss7.org>
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 A0CB221F9ABA for <sigtran@ietfa.amsl.com>; Fri, 14 Jun 2013 14:55:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 cGsRABKF72Pz for <sigtran@ietfa.amsl.com>; Fri, 14 Jun 2013 14:55:09 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) by ietfa.amsl.com (Postfix) with ESMTP id E343921F9A93 for <sigtran@ietf.org>; Fri, 14 Jun 2013 14:55:07 -0700 (PDT)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id r5ELt4A0028622; Fri, 14 Jun 2013 15:55:04 -0600
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id r5ELt4Ju002763; Fri, 14 Jun 2013 15:55:04 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id r5ELt4ff002762; Fri, 14 Jun 2013 15:55:04 -0600
Date: Fri, 14 Jun 2013 15:55:03 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Arvind Kumar <arvindverma77@gmail.com>
Message-ID: <20130614215503.GA966@openss7.org>
Mail-Followup-To: Arvind Kumar <arvindverma77@gmail.com>, sigtran@ietf.org
References: <CAE4qXDFfy+7BycUNrWNGm=Lo4U=WMZH9FDjw1kqWy71nKNbEhw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAE4qXDFfy+7BycUNrWNGm=Lo4U=WMZH9FDjw1kqWy71nKNbEhw@mail.gmail.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
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
Reply-To: bidulock@openss7.org
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: Fri, 14 Jun 2013 21:55:13 -0000

Arvind,

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).

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.

So, there are two considerations: SLS and SLC size.  The most links in a
link set is restricted by the size of the SLC (the number of signalling
links that can be identified between two signalling point  codes);
however, the combined linkset is also restricted by the SLS size (over
how many distinct signalling links can the traffic be distributed).

That said, signalling links are identified by the 3-tuple PC-PC-SLC.
Just because you have multiple PCs on a signalling point does not
necessarily increase the number of signalling links that it can support.
So, if you have 4 PCs, it does not necessarily mean that you can support
4 times as many signalling links.  It is common, for example on a class
5 switch, to provide 1 primary PC that is used in management messages on
signalling links and 3 additional ones (in our example) that are only
aliases (that is, messages can be routed to them but they do not
participate in signalling link management messages).

Some stacks; however, are also capable of supporting multiple signalling
points.  In which case, each primary PC can act as a completely
independent signalling point with its own set of signalling links.  SS7
network operators do no like connecting to systems where multiple
independent signalling points are implemented on the same hardware.

If you need a lot of signalling links for capacity, broadband (or
better, M2PA) signalling links can be used.  In the case of M2PA, the
signalling capacity is not dependent on the number of signalling links
and only a pair of signalling links is required (and recommended).

--brian

Arvind Kumar wrote:                        (Fri, 14 Jun 2013 14:09:27)
>    Hi All,
>    Would appreciate if somebody help me,
>    I have SS7 Stack with multiple OPC, I would like to create multiple
>    linksets towards a single destination (suppose 2000).
>    How many links are possible in all the link-sets. I know there is no
>    limitation of number of link-sets, but as I  understood, towards a
>    given destination the maximum number of links depends upon maximum
>    value of SLS.
>    For ITU it could be 16.
>    But my doubt is I have mutiple OPCs for my SS7 Stack, could number of
>    links  be possible
>    = number of OPCs * 16
>    Please comment.

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

From David.Laight@ACULAB.COM  Mon Jun 17 02:12:05 2013
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




From bidulock@openss7.org  Mon Jun 17 03:18:55 2013
Return-Path: <bidulock@openss7.org>
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 6B99621F885A for <sigtran@ietfa.amsl.com>; Mon, 17 Jun 2013 03:18:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 YjFyAL6Xkqtg for <sigtran@ietfa.amsl.com>; Mon, 17 Jun 2013 03:18:47 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) by ietfa.amsl.com (Postfix) with ESMTP id A534D21F9BBD for <sigtran@ietf.org>; Mon, 17 Jun 2013 03:18:37 -0700 (PDT)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id r5HAISgH012824; Mon, 17 Jun 2013 04:18:29 -0600
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id r5HAIS5h017813; Mon, 17 Jun 2013 04:18:28 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id r5HAIS5h017812; Mon, 17 Jun 2013 04:18:28 -0600
Date: Mon, 17 Jun 2013 04:18:28 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: David Laight <David.Laight@ACULAB.COM>
Message-ID: <20130617101828.GA17340@openss7.org>
Mail-Followup-To: David Laight <David.Laight@ACULAB.COM>, Arvind Kumar <arvindverma77@gmail.com>, sigtran@ietf.org
References: <CAE4qXDFfy+7BycUNrWNGm=Lo4U=WMZH9FDjw1kqWy71nKNbEhw@mail.gmail.com> <20130614215503.GA966@openss7.org> <AE90C24D6B3A694183C094C60CF0A2F6026B7291@saturn3.aculab.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <AE90C24D6B3A694183C094C60CF0A2F6026B7291@saturn3.aculab.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
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
Reply-To: bidulock@openss7.org
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:18:56 -0000

David,

David Laight wrote:                         (Mon, 17 Jun 2013 10:10:52)
> 
> 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.

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

> 
> 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.
>

Pardon, SLC is 4 bits, but there are still 16 links per linkset,
32 links per combined linkset.

> 
> 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.)

It is quite right to say that 1 bit is used for linkset selection,
as it says in 7.3/T1.111.5.

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

From David.Laight@ACULAB.COM  Mon Jun 17 03:54:08 2013
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.
>=20
> 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




From bidulock@openss7.org  Mon Jun 17 06:01:31 2013
Return-Path: <bidulock@openss7.org>
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 3ECC921F9BA6 for <sigtran@ietfa.amsl.com>; Mon, 17 Jun 2013 06:01:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 lu3sl4Wb4aOw for <sigtran@ietfa.amsl.com>; Mon, 17 Jun 2013 06:01:26 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) by ietfa.amsl.com (Postfix) with ESMTP id 7DF0F21F9BAD for <sigtran@ietf.org>; Mon, 17 Jun 2013 06:01:25 -0700 (PDT)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id r5HD149h013520; Mon, 17 Jun 2013 07:01:04 -0600
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id r5HD14Tl020281; Mon, 17 Jun 2013 07:01:04 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id r5HD12Be020280; Mon, 17 Jun 2013 07:01:02 -0600
Date: Mon, 17 Jun 2013 07:01:02 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: David Laight <David.Laight@ACULAB.COM>
Message-ID: <20130617130102.GA20124@openss7.org>
Mail-Followup-To: David Laight <David.Laight@ACULAB.COM>, Arvind Kumar <arvindverma77@gmail.com>, sigtran@ietf.org
References: <CAE4qXDFfy+7BycUNrWNGm=Lo4U=WMZH9FDjw1kqWy71nKNbEhw@mail.gmail.com> <20130614215503.GA966@openss7.org> <AE90C24D6B3A694183C094C60CF0A2F6026B7291@saturn3.aculab.com> <20130617101828.GA17340@openss7.org> <AE90C24D6B3A694183C094C60CF0A2F6026B7292@saturn3.aculab.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <AE90C24D6B3A694183C094C60CF0A2F6026B7292@saturn3.aculab.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
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
Reply-To: bidulock@openss7.org
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 13:01:31 -0000

David,

David Laight wrote:                                        (Mon, 17 Jun 2013 11:52:03)
> 
> >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.

Routing not linkset selection.  It is not valid because it does
not lead to an even loadsharing over links.

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

The network in the figure (using a fixed bit position for
linkset selection) is the common practice for ITU.

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

From snemana@sonusnet.com  Mon Jun 17 08:28:45 2013
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 th=
e links in the linkset.
In this way, we can still have 16 links in each linkset and combined linkse=
t 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 is=
sues 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=20
> ITU and ITU does not do SLS rotation.  Therefore, because 1 bit is=20
> used for link-set selection, there can only be 8 links in a linkset=20
> (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 destin=
ation 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 differen=
t 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=20
> and ANSI does SLS rotation.  Therefore, it is possible to have 32=20
> links in a linkset (64 links in a combined linkset).  Using the old=20
> 5-bit SLS it was only possible to have 16 links in a linkset and 32=20
> links in a combined linkset because 1 of the 5 bits was used for=20
> linkset selection within a combined linkset.

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

It also isn't quite right to say that one of the bits is used for linkset s=
election. 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 jus=
t 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

From bidulock@openss7.org  Mon Jun 17 09:02:41 2013
Return-Path: <bidulock@openss7.org>
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 2B20521F9D4E for <sigtran@ietfa.amsl.com>; Mon, 17 Jun 2013 09:02:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 9m0M2pNdCcoG for <sigtran@ietfa.amsl.com>; Mon, 17 Jun 2013 09:02:36 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) by ietfa.amsl.com (Postfix) with ESMTP id E70B921F9D4D for <sigtran@ietf.org>; Mon, 17 Jun 2013 09:02:34 -0700 (PDT)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id r5HG2OR0014639; Mon, 17 Jun 2013 10:02:25 -0600
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id r5HG2OVR024115; Mon, 17 Jun 2013 10:02:24 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id r5HG2OWx024114; Mon, 17 Jun 2013 10:02:24 -0600
Date: Mon, 17 Jun 2013 10:02:24 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Nemana, Satya" <snemana@sonusnet.com>
Message-ID: <20130617160224.GA23895@openss7.org>
Mail-Followup-To: "Nemana, Satya" <snemana@sonusnet.com>, David Laight <David.Laight@ACULAB.COM>, Arvind Kumar <arvindverma77@gmail.com>, "sigtran@ietf.org" <sigtran@ietf.org>
References: <CAE4qXDFfy+7BycUNrWNGm=Lo4U=WMZH9FDjw1kqWy71nKNbEhw@mail.gmail.com> <20130614215503.GA966@openss7.org> <AE90C24D6B3A694183C094C60CF0A2F6026B7291@saturn3.aculab.com> <A4C75474DC72BC44A5517224ED0604C5021E01E8@USMA-EX-MB2.sonusnet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <A4C75474DC72BC44A5517224ED0604C5021E01E8@USMA-EX-MB2.sonusnet.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: "sigtran@ietf.org" <sigtran@ietf.org>, Arvind Kumar <arvindverma77@gmail.com>
Subject: Re: [Sigtran] Number of links towards a DPC (ITU)
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: bidulock@openss7.org
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:02:41 -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.

> 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.

Nope.  See above.

> 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.

Each linkset has 8 values.

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

From David.Laight@ACULAB.COM  Mon Jun 17 09:30:55 2013
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,
>=20
> 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.
>=20
> So, XXX0 goes to one linkset and XXX1 goes to the other.
>=20
> > 2) Once the Linkset is selected, use the full SLS value to select =
one
> >    of the links in the linkset.
>=20
> 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




From snemana@sonusnet.com  Mon Jun 17 09:33:01 2013
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 598F621F9D5B for <sigtran@ietfa.amsl.com>; Mon, 17 Jun 2013 09:33:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.667
X-Spam-Level: 
X-Spam-Status: No, score=-5.667 tagged_above=-999 required=5 tests=[AWL=0.933,  BAYES_00=-2.599, 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 d9xv9GdYuLI2 for <sigtran@ietfa.amsl.com>; Mon, 17 Jun 2013 09:32:56 -0700 (PDT)
Received: from p01c12o147.mxlogic.net (p01c12o147.mxlogic.net [208.65.145.70]) by ietfa.amsl.com (Postfix) with ESMTP id 3178921F9D59 for <sigtran@ietf.org>; Mon, 17 Jun 2013 09:32:56 -0700 (PDT)
Received: from unknown [69.147.176.212] (EHLO p01c12o147.mxlogic.net) by p01c12o147.mxlogic.net(mxl_mta-7.1.0-3) with ESMTP id 83a3fb15.2b900024c940.49520.00-563.128648.p01c12o147.mxlogic.net (envelope-from <snemana@sonusnet.com>);  Mon, 17 Jun 2013 10:32:56 -0600 (MDT)
X-MXL-Hash: 51bf3a38158f096f-beacd19056774e1f19fff65bc612cf5cbb5b216b
Received: from unknown [69.147.176.212] by p01c12o147.mxlogic.net(mxl_mta-7.1.0-3) with SMTP id 23a3fb15.0.49258.00-290.128535.p01c12o147.mxlogic.net (envelope-from <snemana@sonusnet.com>);  Mon, 17 Jun 2013 10:32:55 -0600 (MDT)
X-MXL-Hash: 51bf3a373c9c02f9-ac4781b80e2a122abd06eb84a00f7f6cd0e21012
Received: from USMA-EX-MB2.sonusnet.com ([fe80::c51d:eb9c:bce7:e4b0]) by usma-ex-hub1.sonusnet.com ([2002:42cb:5a10::42cb:5a10]) with mapi id 14.02.0342.003; Mon, 17 Jun 2013 12:32:40 -0400
From: "Nemana, Satya" <snemana@sonusnet.com>
To: "bidulock@openss7.org" <bidulock@openss7.org>
Thread-Topic: [Sigtran] Number of links towards a DPC (ITU)
Thread-Index: AQHOaUna7moZqh9SiEy2tkMshtODDpk55ZsAgAAk7sCAAE4NAP//vR5Q
Date: Mon, 17 Jun 2013 16:32:38 +0000
Message-ID: <A4C75474DC72BC44A5517224ED0604C5021E027A@USMA-EX-MB2.sonusnet.com>
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>
In-Reply-To: <20130617160224.GA23895@openss7.org>
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=N7ee4RBB 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=cEINi2uUAAAA:8 a=48vgC7mUAAAA:]
X-AnalysisOut: [8 a=a6fo64wWiTr0pSnFoWUA:9 a=CjuIK1q_8ugA:10 a=bI6W1tgPgz0]
X-AnalysisOut: [A:10 a=lZB815dzVvQA:10 a=2-Lalao49Y0AC7gj:21 a=BuuLCEouOlo]
X-AnalysisOut: [9H5Ax: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>, Arvind Kumar <arvindverma77@gmail.com>
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:33:01 -0000

Yeah, I got it wrong.
My idea was to use the SLS but still generate enough SLS for the linkset lo=
cally.
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 link=
s.


-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]=20
Sent: 17 June 2013 17:02
To: Nemana, Satya
Cc: David Laight; Arvind Kumar; sigtran@ietf.org
Subject: Re: [Sigtran] Number of links towards a DPC (ITU)

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.

> In this way, we can still have 16 links in each linkset and combined=20
> linkset can have 32 links and still loadshare across all the links.

Nope.  See above.

> Each linkset will still have 16 of the SLS values so, there won't be=20
> any issues of un-even loadsharing even if some links go down in the=20
> route to the final destination.

Each linkset has 8 values.

--
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

From David.Laight@ACULAB.COM  Tue Jun 18 02:16:47 2013
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



