From mailnull@www1.ietf.org  Mon Jun  2 05:00:22 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28664
	for <sigtran-archive@odin.ietf.org>; Mon, 2 Jun 2003 05:00:22 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h528xu025551
	for sigtran-archive@odin.ietf.org; Mon, 2 Jun 2003 04:59:56 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h528xYB25528;
	Mon, 2 Jun 2003 04:59:35 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h528uaB25417
	for <sigtran@optimus.ietf.org>; Mon, 2 Jun 2003 04:56:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28539
	for <sigtran@ietf.org>; Mon, 2 Jun 2003 04:56:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ml5b-00018Y-00
	for sigtran@ietf.org; Mon, 02 Jun 2003 04:54:47 -0400
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ml5W-00017i-00
	for sigtran@ietf.org; Mon, 02 Jun 2003 04:54:42 -0400
Received: from axes-mach01.axes-mach01.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h528trwA003774;
	Mon, 2 Jun 2003 03:55:55 -0500 (CDT)
Received: from axsppc60 by axes-mach01.axes-mach01.usa.alcatel.com (8.9.3+Sun/SMI-SVR4)
	id NAA26240; Mon, 2 Jun 2003 13:24:11 -0500 (GMT)
Message-ID: <001501c32908$5327cba0$6e01ff0a@axes>
From: "Rohan Pascal S Goveas" <rohanp@axes-mach01.usa.alcatel.com>
To: "Tom George" <Tom.George@alcatel.com>, <sigtran@ietf.org>
References: <OFDF766AEF.2F870E99-ON85256D12.0056A3A2@nc.tekelec.com> <3EB83B33.CBE5DE83@alcatel.com> <3ED7DA57.ED453D62@alcatel.com>
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
Date: Mon, 2 Jun 2003 18:40:05 +0530
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

All,
 See inline for  comment on point number 2.
-Rohan

----- Original Message -----
From: Tom George <Tom.George@alcatel.com>
To: <sigtran@ietf.org>
Sent: Saturday, May 31, 2003 3:55 AM
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8


> Here is how I think I should fix this:
>
> 1. Delete the sentence in 4.2.1
> "M2PA SHOULD ignore the FSN and BSN contained in a Link Status message."
> There is no harm in using those fields, as long as they are used
> appropriately. This will also fix the inconsistency David Lehmann
> pointed out.
>
> 2. In 4.1.4, M2PA should resynchronize its sequence numbers after PO the
> same way MTP2 does. In the case of Q.703 Figure 13 sheet 7, the BSNR
> would come from the LS Processor Recovered message instead of the first
> MSU/FISU as in MTP2.
>
>>>>>>>
>>>>< ROHAN >  In my opinion it is may be wrong to take the BSNR from the LS
Processor Recovered message.
           In case of Q.703 the BSNR is taken from MSU/ FISU. The MSU/FISU
is sent only after a Local Processor     Outage is ended and a Continue or
Flush is received.
          M2PA as such does not explicitly say that a Flush or Continue
should be sent for the Procesor Outage to be ended as in Q.703. Now suppose
in case the end point sends a LS Processor Outage followed by a  Flush
command the end which receives the LS Processor Outage recovered will take
the BSNR from this message and starts T7 for messges which are flushed or
discarded although these messages are already flushed form the remotes
Receive buffer.
  I  think we can have a option of sending a Empty User data message in
additon to Processor Outage Ended and the BSNR will be taken from the Emty
User data message rather than the LS Processor Recovered. Sending of Empty
User data message can be based on Flush or Continue command from MTP3.
>>>><ROHAN>>>
>>>>>>

> 3. The statement in 4.2.1
> "For message types other than User Data, the Forward Sequence Number is
> set to the FSN of the last User Data message sent."
> needs some qualification. After PO, it is set as in item 2 above.
>
> 3. "Flush buffers" is going to mean about the same in M2PA as it does in
> MTP2. It will have to apply to both M2PA and SCTP buffers.
>
> 4. "Continue" after PO will mean that M2PA starts receiving and
> processing the messages that were buffered and not acknowledged during
> PO.
>
> tomG.
>
>
> Long ago Jeff Craig wrote:
> > > page 29, 4.2.1:
> > >
> > >     "M2PA SHOULD ignore the FSN and BSN contained in a Link Status
> > >     message."
> > >
> > >     This sentence contradicts Q.703 Figure 13, Sheet 7 of 7, which
> > >     indicates that the BSN of the M2PA LSPR should be used by the
> > >     recipient to set the initial FSN upon exiting remote processor
> > >     outage condition.
> > >
> > >     M2PA differs from MTP2 in that both sides buffer user data
> > >     received during processor outage. This difference needs to be
> > >     explained in detail in the draft. Processing of the buffered
> > >     messages needs to be explained for the cases of both FLUSH and
> > >     RESUME. As it stands now, the draft contradicts Q.703 and
> > >     does not explain how the M2PA peers keep sequence numbers
> > >     synchronized when existing from the processor outage condition.
> >
> > I think you are right here, too. I will need to think about this one.
>
> --
> * Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
> * 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
> * Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
> * I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
> * to advertise or represent its position,  operations, or activities. *
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>

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



From mailnull@www1.ietf.org  Mon Jun  2 07:43:42 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02192
	for <sigtran-archive@odin.ietf.org>; Mon, 2 Jun 2003 07:43:42 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h52BhDU05422
	for sigtran-archive@odin.ietf.org; Mon, 2 Jun 2003 07:43:13 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h52BgoB05345;
	Mon, 2 Jun 2003 07:42:51 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h52BdiB05164
	for <sigtran@optimus.ietf.org>; Mon, 2 Jun 2003 07:39:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02047;
	Mon, 2 Jun 2003 07:39:42 -0400 (EDT)
From: jeffrey.craig@tekelec.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MndV-0001os-00; Mon, 02 Jun 2003 07:37:57 -0400
Received: from [198.89.32.2] (helo=domino2.nc.tekelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MndU-0001oc-00; Mon, 02 Jun 2003 07:37:56 -0400
Received: from domino4.nc.tekelec.com ([198.89.40.9])
          by domino2.nc.tekelec.com (Lotus Domino Release 5.0.12)
          with ESMTP id 2003060207382596:48380 ;
          Mon, 2 Jun 2003 07:38:25 -0400 
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
To: Tom George <Tom.George@alcatel.com>
Cc: sigtran@ietf.org, sigtran-admin@ietf.org
X-Mailer: Lotus Notes Release 5.0.7  March 21, 2001
Message-ID: <OF1530AF8C.FC72A6D0-ON85256D39.003FF19D@nc.tekelec.com>
Date: Mon, 2 Jun 2003 07:38:53 -0400
MIME-Version: 1.0
X-MIMETrack: Serialize by Router on Domino4/Raleigh/TEKELEC(Release 5.0.12  |February 13, 2003) at
 06/02/2003 07:38:54 AM,
	Itemize by SMTP Server on Domino2/Raleigh/TEKELEC(Release 5.0.12  |February
 13, 2003) at 06/02/2003 07:38:26 AM,
	Serialize by Router on Domino2/Raleigh/TEKELEC(Release 5.0.12  |February 13, 2003) at
 06/02/2003 07:39:02 AM,
	Serialize complete at 06/02/2003 07:39:02 AM
Content-type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


Hello Tom,

Your changes sound good to me.

Regards,

Jeff



                                                                                                                                  
                      Tom George                                                                                                  
                      <Tom.George@alca         To:      sigtran@ietf.org                                                          
                      tel.com>                 cc:                                                                                
                      Sent by:                 Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8                                  
                      sigtran-admin@ie                                                                                            
                      tf.org                                                                                                      
                                                                                                                                  
                                                                                                                                  
                      05/30/03 06:25                                                                                              
                      PM                                                                                                          
                                                                                                                                  
                                                                                                                                  




Here is how I think I should fix this:

1. Delete the sentence in 4.2.1
"M2PA SHOULD ignore the FSN and BSN contained in a Link Status message."
There is no harm in using those fields, as long as they are used
appropriately. This will also fix the inconsistency David Lehmann
pointed out.

2. In 4.1.4, M2PA should resynchronize its sequence numbers after PO the
same way MTP2 does. In the case of Q.703 Figure 13 sheet 7, the BSNR
would come from the LS Processor Recovered message instead of the first
MSU/FISU as in MTP2.

3. The statement in 4.2.1
"For message types other than User Data, the Forward Sequence Number is
set to the FSN of the last User Data message sent."
needs some qualification. After PO, it is set as in item 2 above.

3. "Flush buffers" is going to mean about the same in M2PA as it does in
MTP2. It will have to apply to both M2PA and SCTP buffers.

4. "Continue" after PO will mean that M2PA starts receiving and
processing the messages that were buffered and not acknowledged during
PO.

tomG.


Long ago Jeff Craig wrote:
> > page 29, 4.2.1:
> >
> >     "M2PA SHOULD ignore the FSN and BSN contained in a Link Status
> >     message."
> >
> >     This sentence contradicts Q.703 Figure 13, Sheet 7 of 7, which
> >     indicates that the BSN of the M2PA LSPR should be used by the
> >     recipient to set the initial FSN upon exiting remote processor
> >     outage condition.
> >
> >     M2PA differs from MTP2 in that both sides buffer user data
> >     received during processor outage. This difference needs to be
> >     explained in detail in the draft. Processing of the buffered
> >     messages needs to be explained for the cases of both FLUSH and
> >     RESUME. As it stands now, the draft contradicts Q.703 and
> >     does not explain how the M2PA peers keep sequence numbers
> >     synchronized when existing from the processor outage condition.
>
> I think you are right here, too. I will need to think about this one.

--
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
* I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
* to advertise or represent its position,  operations, or activities. *
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
 https://www1.ietf.org/mailman/listinfo/sigtran




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



From mailnull@www1.ietf.org  Mon Jun  2 09:56:26 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07448
	for <sigtran-archive@odin.ietf.org>; Mon, 2 Jun 2003 09:56:26 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h52Du0115666
	for sigtran-archive@odin.ietf.org; Mon, 2 Jun 2003 09:56:00 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h52DtPB15626;
	Mon, 2 Jun 2003 09:55:27 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h52DphB15379
	for <sigtran@optimus.ietf.org>; Mon, 2 Jun 2003 09:51:43 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07275;
	Mon, 2 Jun 2003 09:51:38 -0400 (EDT)
Message-Id: <200306021351.JAA07275@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sigtran@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Mon, 02 Jun 2003 09:51:37 -0400
Subject: [Sigtran] I-D ACTION:draft-ietf-sigtran-v5ua-04.txt
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Signaling Transport Working Group of the IETF.

	Title		: V5.2-User Adaption Layer (V5UA)
	Author(s)	: E. Weilandt, N. Khanchandani, S. Rao
	Filename	: draft-ietf-sigtran-v5ua-04.txt
	Pages		: 22
	Date		: 2003-6-2
	
This document defines a mechanism for backhauling of V5.2 messages
over IP using the Stream Control Transmission Protocol (SCTP). This
protocol may be used between a Signaling Gateway (SG) and a Media
Gateway controller (MGC). It is assumed that the SG receives V5.2 sig-
naling over a standard V5.2 interface.

This document builds on top of the ISDN User Adaptation Layer Protocol
(RFC 3057). It defines all necessary extensions to the IUA Protocol
needed for the V5UA protocol implementation.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sigtran-v5ua-04.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-sigtran-v5ua-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sigtran-v5ua-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-6-2100847.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sigtran-v5ua-04.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sigtran-v5ua-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-6-2100847.I-D@ietf.org>

--OtherAccess--

--NextPart--


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



From mailnull@www1.ietf.org  Mon Jun  2 16:53:21 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23480
	for <sigtran-archive@odin.ietf.org>; Mon, 2 Jun 2003 16:53:20 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h52Kqsb20339
	for sigtran-archive@odin.ietf.org; Mon, 2 Jun 2003 16:52:54 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h52KqaB20328;
	Mon, 2 Jun 2003 16:52:37 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h52KnvB20169
	for <sigtran@optimus.ietf.org>; Mon, 2 Jun 2003 16:49:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23412
	for <sigtran@ietf.org>; Mon, 2 Jun 2003 16:49:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MwDw-0006IF-00
	for sigtran@ietf.org; Mon, 02 Jun 2003 16:48:08 -0400
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MwDr-0006I7-00
	for sigtran@ietf.org; Mon, 02 Jun 2003 16:48:03 -0400
Received: from alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h52KnJwA003486;
	Mon, 2 Jun 2003 15:49:19 -0500 (CDT)
Message-ID: <3EDBB84F.31FA454E@alcatel.com>
Date: Mon, 02 Jun 2003 15:49:19 -0500
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
CC: sigtran@ietf.org
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
References: <OFDF766AEF.2F870E99-ON85256D12.0056A3A2@nc.tekelec.com> <3EB83B33.CBE5DE83@alcatel.com> <3ED7DA57.ED453D62@alcatel.com> <001501c32908$5327cba0$6e01ff0a@axes>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

The LS PR should be sent in M2PA under the same circumstances as the
MSU/FISU in Q.703. (If that is not clear enough, maybe I should change
the wording in 4.1.4.)

I did not explicitly mention the Flush/Continue because you need to
follow the MTP2 procedures. 

I am wary of using an empty User Data message at the end of PO to
indicate the BSNR. As I stated in a message last week, the receiver will
not be able to tell if the empty UD message was sent before or after the
LS PR. 

tomG.

Rohan Pascal S Goveas wrote:
> 
> All,
>  See inline for  comment on point number 2.
> -Rohan
> 
> ----- Original Message -----
> From: Tom George <Tom.George@alcatel.com>
> To: <sigtran@ietf.org>
> Sent: Saturday, May 31, 2003 3:55 AM
> Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
> 
> > Here is how I think I should fix this:
> >
> > 1. Delete the sentence in 4.2.1
> > "M2PA SHOULD ignore the FSN and BSN contained in a Link Status message."
> > There is no harm in using those fields, as long as they are used
> > appropriately. This will also fix the inconsistency David Lehmann
> > pointed out.
> >
> > 2. In 4.1.4, M2PA should resynchronize its sequence numbers after PO the
> > same way MTP2 does. In the case of Q.703 Figure 13 sheet 7, the BSNR
> > would come from the LS Processor Recovered message instead of the first
> > MSU/FISU as in MTP2.
> >
> >>>>>>>
> >>>>< ROHAN >  In my opinion it is may be wrong to take the BSNR from the LS
> Processor Recovered message.
>            In case of Q.703 the BSNR is taken from MSU/ FISU. The MSU/FISU
> is sent only after a Local Processor     Outage is ended and a Continue or
> Flush is received.
>           M2PA as such does not explicitly say that a Flush or Continue
> should be sent for the Procesor Outage to be ended as in Q.703. Now suppose
> in case the end point sends a LS Processor Outage followed by a  Flush
> command the end which receives the LS Processor Outage recovered will take
> the BSNR from this message and starts T7 for messges which are flushed or
> discarded although these messages are already flushed form the remotes
> Receive buffer.
>   I  think we can have a option of sending a Empty User data message in
> additon to Processor Outage Ended and the BSNR will be taken from the Emty
> User data message rather than the LS Processor Recovered. Sending of Empty
> User data message can be based on Flush or Continue command from MTP3.
> >>>><ROHAN>>>
> >>>>>>
> 
> > 3. The statement in 4.2.1
> > "For message types other than User Data, the Forward Sequence Number is
> > set to the FSN of the last User Data message sent."
> > needs some qualification. After PO, it is set as in item 2 above.
> >
> > 3. "Flush buffers" is going to mean about the same in M2PA as it does in
> > MTP2. It will have to apply to both M2PA and SCTP buffers.
> >
> > 4. "Continue" after PO will mean that M2PA starts receiving and
> > processing the messages that were buffered and not acknowledged during
> > PO.
> >
> > tomG.
> >
> >
> > Long ago Jeff Craig wrote:
> > > > page 29, 4.2.1:
> > > >
> > > >     "M2PA SHOULD ignore the FSN and BSN contained in a Link Status
> > > >     message."
> > > >
> > > >     This sentence contradicts Q.703 Figure 13, Sheet 7 of 7, which
> > > >     indicates that the BSN of the M2PA LSPR should be used by the
> > > >     recipient to set the initial FSN upon exiting remote processor
> > > >     outage condition.
> > > >
> > > >     M2PA differs from MTP2 in that both sides buffer user data
> > > >     received during processor outage. This difference needs to be
> > > >     explained in detail in the draft. Processing of the buffered
> > > >     messages needs to be explained for the cases of both FLUSH and
> > > >     RESUME. As it stands now, the draft contradicts Q.703 and
> > > >     does not explain how the M2PA peers keep sequence numbers
> > > >     synchronized when existing from the processor outage condition.
> > >
> > > I think you are right here, too. I will need to think about this one.
> >
> > --
> > * Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
> > * 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
> > * Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
> > * I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
> > * to advertise or represent its position,  operations, or activities. *
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> >

-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
* I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
* to advertise or represent its position,  operations, or activities. *
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Tue Jun  3 14:15:48 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17792
	for <sigtran-archive@odin.ietf.org>; Tue, 3 Jun 2003 14:15:48 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h53IFME11358
	for sigtran-archive@odin.ietf.org; Tue, 3 Jun 2003 14:15:22 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h53IErB11171;
	Tue, 3 Jun 2003 14:14:53 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h53I8aB10388
	for <sigtran@optimus.ietf.org>; Tue, 3 Jun 2003 14:08:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17395
	for <sigtran@ietf.org>; Tue, 3 Jun 2003 14:08:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NGBI-0001FZ-00
	for sigtran@ietf.org; Tue, 03 Jun 2003 14:06:44 -0400
Received: from [143.209.238.79] (helo=auds955.usa.alcatel.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NGBC-0001Ep-00
	for sigtran@ietf.org; Tue, 03 Jun 2003 14:06:38 -0400
Received: from alcatel.com (localhost [127.0.0.1])
	by auds955.usa.alcatel.com (8.12.9/8.12.9) with ESMTP id h53I7tTG007611;
	Tue, 3 Jun 2003 13:07:55 -0500 (CDT)
Message-ID: <3EDCE3FB.EBE160E6@alcatel.com>
Date: Tue, 03 Jun 2003 13:07:55 -0500
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: sigtran@ietf.org
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
References: <OFDF766AEF.2F870E99-ON85256D12.0056A3A2@nc.tekelec.com> <3EB83B33.CBE5DE83@alcatel.com> <3ED7DA57.ED453D62@alcatel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Here are the details on how I took care of this. 

tomG.

Tom George wrote:
> 
> Here is how I think I should fix this:
> 
> 1. Delete the sentence in 4.2.1
> "M2PA SHOULD ignore the FSN and BSN contained in a Link Status message."
> There is no harm in using those fields, as long as they are used
> appropriately. This will also fix the inconsistency David Lehmann
> pointed out.

I deleted it.

> 
> 2. In 4.1.4, M2PA should resynchronize its sequence numbers after PO the
> same way MTP2 does. In the case of Q.703 Figure 13 sheet 7, the BSNR
> would come from the LS Processor Recovered message instead of the first
> MSU/FISU as in MTP2.

After this sentence:
"When the local processor outage condition ends, M2PA SHALL send a Link
Status Processor Recovered message to its peer. "

I added:
"The BSN value in this
message is used by the peer to resynchronize its sequence numbers, if
this is required by MTP2."


> 
> 3. The statement in 4.2.1
> "For message types other than User Data, the Forward Sequence Number is
> set to the FSN of the last User Data message sent."
> needs some qualification. After PO, it is set as in item 2 above.

On further review, this is almost identical to the wording in Q.703
section 5.2.1 last sentence. I think this is OK as it stands, and it is
understood that there are exceptions for initialization and
resynchronization.

> 
> 3. "Flush buffers" is going to mean about the same in M2PA as it does in
> MTP2. It will have to apply to both M2PA and SCTP buffers.

There is one difference between M2PA and MTP2 flushing. In MTP2, the
Flush command goes from LSC to TXC (Q.703 Figure 8 sheet 13). TXC
removes all of the MSUs from the RTB and TB. 

In M2PA, some of the messages that would have been kept in the RTB/TB in
MTP2 were transmitted by SCTP and are buffered at the receiving end.
These messages should be flushed, too. 

So I added this to 4.1.4 (just before "In other respects..."):
"If M2PA receives a Flush command from MTP3, M2PA SHALL discard the
incoming messages that were queued and unacknowledged during the
processor outage condition."


> 
> 4. "Continue" after PO will mean that M2PA starts receiving and
> processing the messages that were buffered and not acknowledged during
> PO.

Right after the paragraph about Flush, I added:
"If M2PA receives a Continue command from MTP3, M2PA SHALL begin
processing the incoming messages that were queued and unacknowledged
during the processor outage condition."





> 
> tomG.
> 
> Long ago Jeff Craig wrote:
> > > page 29, 4.2.1:
> > >
> > >     "M2PA SHOULD ignore the FSN and BSN contained in a Link Status
> > >     message."
> > >
> > >     This sentence contradicts Q.703 Figure 13, Sheet 7 of 7, which
> > >     indicates that the BSN of the M2PA LSPR should be used by the
> > >     recipient to set the initial FSN upon exiting remote processor
> > >     outage condition.
> > >
> > >     M2PA differs from MTP2 in that both sides buffer user data
> > >     received during processor outage. This difference needs to be
> > >     explained in detail in the draft. Processing of the buffered
> > >     messages needs to be explained for the cases of both FLUSH and
> > >     RESUME. As it stands now, the draft contradicts Q.703 and
> > >     does not explain how the M2PA peers keep sequence numbers
> > >     synchronized when existing from the processor outage condition.
> >
> > I think you are right here, too. I will need to think about this one.

-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
* I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
* to advertise or represent its position,  operations, or activities. *
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Tue Jun  3 14:31:46 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18628
	for <sigtran-archive@odin.ietf.org>; Tue, 3 Jun 2003 14:31:46 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h53IVLm13553
	for sigtran-archive@odin.ietf.org; Tue, 3 Jun 2003 14:31:21 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h53IUuB13414;
	Tue, 3 Jun 2003 14:30:56 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h53IR4B12724
	for <sigtran@optimus.ietf.org>; Tue, 3 Jun 2003 14:27:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18398
	for <sigtran@ietf.org>; Tue, 3 Jun 2003 14:26:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NGT9-0001WO-00
	for sigtran@ietf.org; Tue, 03 Jun 2003 14:25:11 -0400
Received: from [143.209.238.79] (helo=auds955.usa.alcatel.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NGT8-0001UY-00
	for sigtran@ietf.org; Tue, 03 Jun 2003 14:25:10 -0400
Received: from alcatel.com (localhost [127.0.0.1])
	by auds955.usa.alcatel.com (8.12.9/8.12.9) with ESMTP id h53IQSTG010023;
	Tue, 3 Jun 2003 13:26:28 -0500 (CDT)
Message-ID: <3EDCE854.F4955841@alcatel.com>
Date: Tue, 03 Jun 2003 13:26:28 -0500
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: sigtran@ietf.org
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
References: <OFDF766AEF.2F870E99-ON85256D12.0056A3A2@nc.tekelec.com> <3EB83B33.CBE5DE83@alcatel.com> <3ED7DA57.ED453D62@alcatel.com> <3EDCE3FB.EBE160E6@alcatel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

I just clarified some of the wording in 4.1.4 to answer some obvious
questions. Here is the revised text.

tomG.

----------------------------------
4.1.4 Processor Outage

The Link Status Processor Outage message replaces the SIPO message of
MTP2. Unlike MTP2, the message SHOULD NOT be transmitted
continuously. M2PA SHALL send a Link Status Processor Outage message
to its peer at the beginning of a processor outage condition where
MTP2 would send SIPO. M2PA MAY send additional Link Status Processor
Outage messages as long as that condition persists. 

When the local processor outage condition ends, M2PA SHALL send a Link
Status Processor Recovered message to its peer. This message is used
to signal in the end of the processor outage condition, instead of an
MSU or FISU as in MTP2. The BSN value in this message is used by the
peer to resynchronize its sequence numbers, if this is required by
MTP2.

While in a local processor outage condition:

   (a) Any User Data messages received from the peer MUST NOT be
       acknowledged and MUST be buffered.

   (b) M2PA SHOULD continue to acknowledge User Data messages received
       and accepted by MTP3 before the local processor outage.

While there is a remote processor outage condition:

   (a) Any User Data messages received from the peer after the Link
       Status Processor Outage MUST NOT be acknowledged and MUST be
       buffered.

   (b) M2PA SHOULD continue to acknowledge User Data messages received
       and accepted by MTP3 before the remote processor outage.

If M2PA receives a Flush command from MTP3, M2PA SHALL discard the
incoming messages that were queued and unacknowledged during the
processor outage condition. Furthermore, M2PA SHALL discard messages
in the transmit and retransmit queues as required by MTP2. 

If M2PA receives a Continue command from MTP3, M2PA SHALL begin
processing the incoming messages that were queued and unacknowledged
during the processor outage condition.

In other respects, M2PA SHOULD follow the same procedures as MTP2 in
processor outage.
------------------------------------



-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
* I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
* to advertise or represent its position,  operations, or activities. *
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Tue Jun  3 16:22:10 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23459
	for <sigtran-archive@odin.ietf.org>; Tue, 3 Jun 2003 16:22:09 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h53KLhF25516
	for sigtran-archive@odin.ietf.org; Tue, 3 Jun 2003 16:21:43 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h53KLGB25501;
	Tue, 3 Jun 2003 16:21:18 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h53KIYB25376
	for <sigtran@optimus.ietf.org>; Tue, 3 Jun 2003 16:18:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23370
	for <sigtran@ietf.org>; Tue, 3 Jun 2003 16:18:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NID6-0002Ux-00
	for sigtran@ietf.org; Tue, 03 Jun 2003 16:16:44 -0400
Received: from web12801.mail.yahoo.com ([216.136.174.36])
	by ietf-mx with smtp (Exim 4.12)
	id 19NID5-0002Uu-00
	for sigtran@ietf.org; Tue, 03 Jun 2003 16:16:43 -0400
Message-ID: <20030603201829.33448.qmail@web12801.mail.yahoo.com>
Received: from [208.255.120.2] by web12801.mail.yahoo.com via HTTP; Tue, 03 Jun 2003 13:18:29 PDT
Date: Tue, 3 Jun 2003 13:18:29 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
To: sigtran@ietf.org
In-Reply-To: <3EDCE854.F4955841@alcatel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tom,

[..snip..]
> If M2PA receives a Flush command from MTP3, M2PA
> SHALL discard the
> incoming messages that were queued and
> unacknowledged during the
> processor outage condition. Furthermore, M2PA SHALL
> discard messages
> in the transmit and retransmit queues as required by
> MTP2. 
[TOLGA]So also messages sent after local processor
outage ended but received before LSPR will be
discarded(?). How are they going to be retransmitted?


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Tue Jun  3 19:00:20 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28973
	for <sigtran-archive@odin.ietf.org>; Tue, 3 Jun 2003 19:00:19 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h53MxvR04826
	for sigtran-archive@odin.ietf.org; Tue, 3 Jun 2003 18:59:57 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h53MxXB04811;
	Tue, 3 Jun 2003 18:59:34 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h53MudB04714
	for <sigtran@optimus.ietf.org>; Tue, 3 Jun 2003 18:56:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28876
	for <sigtran@ietf.org>; Tue, 3 Jun 2003 18:56:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NKg1-0003eA-00
	for sigtran@ietf.org; Tue, 03 Jun 2003 18:54:45 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[m1K+M1dhobvGIZbqobFpjXd+iBBj0kFd])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NKg0-0003e7-00
	for sigtran@ietf.org; Tue, 03 Jun 2003 18:54:44 -0400
Received: from ns.pigworks.openss7.net (IDENT:Q+yZcobEHOx94oA/K6153Gv/8jTZrZHa@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h53MuWF10851;
	Tue, 3 Jun 2003 16:56:32 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h53MuVe11653;
	Tue, 3 Jun 2003 16:56:31 -0600
Date: Tue, 3 Jun 2003 16:56:31 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
Message-ID: <20030603165631.A11452@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <3EDCE854.F4955841@alcatel.com> <20030603201829.33448.qmail@web12801.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030603201829.33448.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Tue, Jun 03, 2003 at 01:18:29PM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

In SS7 flushed messages are never retransmitted.  This
is because they are old and stagnant by the time the
Flush_buffers is issued and must be dicareded.

--brian

Tolga Asveren wrote:                                                                 (Tue, 03 Jun 2003 13:18:29)
> Tom,
> 
> [..snip..]
> > If M2PA receives a Flush command from MTP3, M2PA
> > SHALL discard the
> > incoming messages that were queued and
> > unacknowledged during the
> > processor outage condition. Furthermore, M2PA SHALL
> > discard messages
> > in the transmit and retransmit queues as required by
> > MTP2. 
> [TOLGA]So also messages sent after local processor
> outage ended but received before LSPR will be
> discarded(?). How are they going to be retransmitted?
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
> http://calendar.yahoo.com
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Wed Jun  4 06:55:38 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10919
	for <sigtran-archive@odin.ietf.org>; Wed, 4 Jun 2003 06:55:38 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h54AtFT03325
	for sigtran-archive@odin.ietf.org; Wed, 4 Jun 2003 06:55:15 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54AstB03277;
	Wed, 4 Jun 2003 06:54:55 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54ApuB03164
	for <sigtran@optimus.ietf.org>; Wed, 4 Jun 2003 06:51:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10859
	for <sigtran@ietf.org>; Wed, 4 Jun 2003 06:51:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NVqD-0000Z2-00
	for sigtran@ietf.org; Wed, 04 Jun 2003 06:50:01 -0400
Received: from web12807.mail.yahoo.com ([216.136.174.42])
	by ietf-mx with smtp (Exim 4.12)
	id 19NVqC-0000Yw-00
	for sigtran@ietf.org; Wed, 04 Jun 2003 06:50:00 -0400
Message-ID: <20030604105149.84515.qmail@web12807.mail.yahoo.com>
Received: from [208.255.120.2] by web12807.mail.yahoo.com via HTTP; Wed, 04 Jun 2003 03:51:49 PDT
Date: Wed, 4 Jun 2003 03:51:49 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
To: sigtran@ietf.org
In-Reply-To: <20030603165631.A11452@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Tolga,
> 
> In SS7 flushed messages are never retransmitted. 
> This
> is because they are old and stagnant by the time the
> Flush_buffers is issued and must be dicareded.
[TOLGA] Yes, but should we qualify also messages sent
after local processor outage ended but received on the
other side before LSPR (because they are sent on
different streams) as "old"?
> 
> --brian
> 
> Tolga Asveren wrote:                                
>                                 (Tue, 03 Jun 2003
> 13:18:29)
> > Tom,
> > 
> > [..snip..]
> > > If M2PA receives a Flush command from MTP3, M2PA
> > > SHALL discard the
> > > incoming messages that were queued and
> > > unacknowledged during the
> > > processor outage condition. Furthermore, M2PA
> SHALL
> > > discard messages
> > > in the transmit and retransmit queues as
> required by
> > > MTP2. 
> > [TOLGA]So also messages sent after local processor
> > outage ended but received before LSPR will be
> > discarded(?). How are they going to be
> retransmitted?
> > 
> > 
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Calendar - Free online calendar with sync
> to Outlook(TM).
> > http://calendar.yahoo.com
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Wed Jun  4 12:19:41 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29551
	for <sigtran-archive@odin.ietf.org>; Wed, 4 Jun 2003 12:19:41 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h54GJFM31213
	for sigtran-archive@odin.ietf.org; Wed, 4 Jun 2003 12:19:15 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54GIvB31190;
	Wed, 4 Jun 2003 12:18:58 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54GF8B30974
	for <sigtran@optimus.ietf.org>; Wed, 4 Jun 2003 12:15:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29380
	for <sigtran@ietf.org>; Wed, 4 Jun 2003 12:15:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nat1-00057R-00
	for sigtran@ietf.org; Wed, 04 Jun 2003 12:13:15 -0400
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nat1-00057O-00
	for sigtran@ietf.org; Wed, 04 Jun 2003 12:13:15 -0400
Received: from [172.16.1.40] (helo=ccpu00251)
	by smtp.ccpu.com with smtp (Exim 4.20 #1 (Debian))
	id 19Naug-0002d3-7y
	for <sigtran@ietf.org>; Wed, 04 Jun 2003 09:14:58 -0700
Reply-To: <umesh@ccpu.com>
From: "Umesh Vats" <umesh@ccpu.com>
To: <sigtran@ietf.org>
Date: Wed, 4 Jun 2003 09:18:07 -0700
Message-ID: <ACEMIJONPBBPDLOKCABHAEICCAAA.umesh@ccpu.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] M3UA : Multiple SGPs in SG
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

I have some queries for the case, where an SG comprises of three SGPs
and connected with 4 ASPs.

Each ASP is connected with each SGP.
So the list of associtions is :

 SGP1 : ASP1 (Assoc1), ASP2 (Assoc2), ASP3 (Assoc3), ASP4 (Assoc4)
 SGP2 : ASP1 (Assoc5), ASP2 (Assoc6), ASP3 (Assoc7), ASP4 (Assoc8)
 SGP3 : ASP1 (Assoc9), ASP2 (Assoc10), ASP3 (Assoc11), ASP4 (Assoc12)

1. AS in n+k redundancy mode : Suppose we configure n as 3.
                   Now suppose ASP1 goes ACTIVE for all three SGPs.
                   Does this mean that :

                   n=3 limit is reached and AS should be made active.(e.g.
                   this may mean that ASP is capable handling traffic
                   otherwise it would have gone ACTIVE only via one SGP)
                                     OR
                   n=1 limit is reached. At least two more ASPs need to
                   go ACTIVE via any of the SGPs in SG before AS can go
                   ACTIVE on SG.


2. AS in override mode : Suppose an application server is being served by
all
                   4 ASPs in override mode. Does this mean that,

                   at any given time, each SGP will have at the most one ASP
                   ACTIVE for an AS
                                      OR
                   at any given time, an SG (combining all SGPs) will have
at
                   the most one ASP ACTIVE for an AS


Umesh Vats

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



From mailnull@www1.ietf.org  Wed Jun  4 12:33:48 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00023
	for <sigtran-archive@odin.ietf.org>; Wed, 4 Jun 2003 12:33:48 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h54GXNp31937
	for sigtran-archive@odin.ietf.org; Wed, 4 Jun 2003 12:33:23 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54GX1B31908;
	Wed, 4 Jun 2003 12:33:01 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54GRYB31684
	for <sigtran@optimus.ietf.org>; Wed, 4 Jun 2003 12:27:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29756
	for <sigtran@ietf.org>; Wed, 4 Jun 2003 12:27:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nb53-0005DZ-00
	for sigtran@ietf.org; Wed, 04 Jun 2003 12:25:41 -0400
Received: from web12805.mail.yahoo.com ([216.136.174.40])
	by ietf-mx with smtp (Exim 4.12)
	id 19Nb53-0005DW-00
	for sigtran@ietf.org; Wed, 04 Jun 2003 12:25:41 -0400
Message-ID: <20030604162730.86070.qmail@web12805.mail.yahoo.com>
Received: from [208.255.120.2] by web12805.mail.yahoo.com via HTTP; Wed, 04 Jun 2003 09:27:30 PDT
Date: Wed, 4 Jun 2003 09:27:30 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
To: sigtran@ietf.org
In-Reply-To: <ACEMIJONPBBPDLOKCABHAEICCAAA.umesh@ccpu.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Umesh,

--- Umesh Vats <umesh@ccpu.com> wrote:
> I have some queries for the case, where an SG
> comprises of three SGPs
> and connected with 4 ASPs.
> 
> Each ASP is connected with each SGP.
> So the list of associtions is :
> 
>  SGP1 : ASP1 (Assoc1), ASP2 (Assoc2), ASP3 (Assoc3),
> ASP4 (Assoc4)
>  SGP2 : ASP1 (Assoc5), ASP2 (Assoc6), ASP3 (Assoc7),
> ASP4 (Assoc8)
>  SGP3 : ASP1 (Assoc9), ASP2 (Assoc10), ASP3
> (Assoc11), ASP4 (Assoc12)
> 
> 1. AS in n+k redundancy mode : Suppose we configure
> n as 3.
>                    Now suppose ASP1 goes ACTIVE for
> all three SGPs.
>                    Does this mean that :
> 
>                    n=3 limit is reached and AS
> should be made active.(e.g.
>                    this may mean that ASP is capable
> handling traffic
>                    otherwise it would have gone
> ACTIVE only via one SGP)
>                                      OR
>                    n=1 limit is reached. At least
> two more ASPs need to
>                    go ACTIVE via any of the SGPs in
> SG before AS can go
>                    ACTIVE on SG.
[TOLGA]The second one. So, one has to have 3 ACTIVE
ASPs for a SGP.
> 
> 
> 2. AS in override mode : Suppose an application
> server is being served by
> all
>                    4 ASPs in override mode. Does
> this mean that,
> 
>                    at any given time, each SGP will
> have at the most one ASP
>                    ACTIVE for an AS
>                                       OR
>                    at any given time, an SG
> (combining all SGPs) will have
> at
>                    the most one ASP ACTIVE for an AS
>
[TOLGA]The first one. In general, from ASP traffic
management point of view, the peers are ASPs and SGPs.



> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Wed Jun  4 13:47:18 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03300
	for <sigtran-archive@odin.ietf.org>; Wed, 4 Jun 2003 13:47:18 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h54Hkrv05496
	for sigtran-archive@odin.ietf.org; Wed, 4 Jun 2003 13:46:53 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54HkZB05477;
	Wed, 4 Jun 2003 13:46:36 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54HhvB05373
	for <sigtran@optimus.ietf.org>; Wed, 4 Jun 2003 13:43:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03210
	for <sigtran@ietf.org>; Wed, 4 Jun 2003 13:43:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NcGx-00066d-00
	for sigtran@ietf.org; Wed, 04 Jun 2003 13:42:03 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[0jDAnIah9FQOwsisPCx1kqv3TaSFeJi7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NcGv-00066S-00
	for sigtran@ietf.org; Wed, 04 Jun 2003 13:42:01 -0400
Received: from ns.pigworks.openss7.net (IDENT:JTrCUZt6z+RgQYp79+H7XrGEebVgU0X4@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h54HhoF27395;
	Wed, 4 Jun 2003 11:43:50 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h54HhoW25874;
	Wed, 4 Jun 2003 11:43:50 -0600
Date: Wed, 4 Jun 2003 11:43:50 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
Message-ID: <20030604114350.B25664@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030603165631.A11452@openss7.org> <20030604105149.84515.qmail@web12807.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030604105149.84515.qmail@web12807.mail.yahoo.com>; from tolga_asveren@yahoo.com on Wed, Jun 04, 2003 at 03:51:49AM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

Yes.

--brian

Tolga Asveren wrote:                                                                 (Wed, 04 Jun 2003 03:51:49)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > In SS7 flushed messages are never retransmitted. 
> > This
> > is because they are old and stagnant by the time the
> > Flush_buffers is issued and must be dicareded.
> [TOLGA] Yes, but should we qualify also messages sent
> after local processor outage ended but received on the
> other side before LSPR (because they are sent on
> different streams) as "old"?
> > 
> > --brian
> > 
> > Tolga Asveren wrote:                                
> >                                 (Tue, 03 Jun 2003
> > 13:18:29)
> > > Tom,
> > > 
> > > [..snip..]
> > > > If M2PA receives a Flush command from MTP3, M2PA
> > > > SHALL discard the
> > > > incoming messages that were queued and
> > > > unacknowledged during the
> > > > processor outage condition. Furthermore, M2PA
> > SHALL
> > > > discard messages
> > > > in the transmit and retransmit queues as
> > required by
> > > > MTP2. 
> > > [TOLGA]So also messages sent after local processor
> > > outage ended but received before LSPR will be
> > > discarded(?). How are they going to be
> > retransmitted?
> > > 
> > > 
> > > __________________________________
> > > Do you Yahoo!?
> > > Yahoo! Calendar - Free online calendar with sync
> > to Outlook(TM).
> > > http://calendar.yahoo.com
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
> http://calendar.yahoo.com
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Wed Jun  4 13:59:37 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03637
	for <sigtran-archive@odin.ietf.org>; Wed, 4 Jun 2003 13:59:37 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h54HxCR05933
	for sigtran-archive@odin.ietf.org; Wed, 4 Jun 2003 13:59:12 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54HwpB05915;
	Wed, 4 Jun 2003 13:58:51 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54Hu7B05865
	for <sigtran@optimus.ietf.org>; Wed, 4 Jun 2003 13:56:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03505
	for <sigtran@ietf.org>; Wed, 4 Jun 2003 13:56:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NcSi-0006BR-00
	for sigtran@ietf.org; Wed, 04 Jun 2003 13:54:12 -0400
Received: from web12804.mail.yahoo.com ([216.136.174.39])
	by ietf-mx with smtp (Exim 4.12)
	id 19NcSh-0006BO-00
	for sigtran@ietf.org; Wed, 04 Jun 2003 13:54:11 -0400
Message-ID: <20030604175601.74616.qmail@web12804.mail.yahoo.com>
Received: from [208.255.120.2] by web12804.mail.yahoo.com via HTTP; Wed, 04 Jun 2003 10:56:01 PDT
Date: Wed, 4 Jun 2003 10:56:01 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
To: sigtran@ietf.org
In-Reply-To: <20030604114350.B25664@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Tolga,
> 
> Yes.
[TOLGA]But why? They are sent after local processor
outage has ended. The sending side will keep timeout
information for such a message (T7) and because it
won't be acknowledged, link will be dropped.
> 
> --brian
> 
> Tolga Asveren wrote:                                
>                                 (Wed, 04 Jun 2003
> 03:51:49)
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > Tolga,
> > > 
> > > In SS7 flushed messages are never retransmitted.
> 
> > > This
> > > is because they are old and stagnant by the time
> the
> > > Flush_buffers is issued and must be dicareded.
> > [TOLGA] Yes, but should we qualify also messages
> sent
> > after local processor outage ended but received on
> the
> > other side before LSPR (because they are sent on
> > different streams) as "old"?
> > > 
> > > --brian
> > > 
> > > Tolga Asveren wrote:                            
>    
> > >                                 (Tue, 03 Jun
> 2003
> > > 13:18:29)
> > > > Tom,
> > > > 
> > > > [..snip..]
> > > > > If M2PA receives a Flush command from MTP3,
> M2PA
> > > > > SHALL discard the
> > > > > incoming messages that were queued and
> > > > > unacknowledged during the
> > > > > processor outage condition. Furthermore,
> M2PA
> > > SHALL
> > > > > discard messages
> > > > > in the transmit and retransmit queues as
> > > required by
> > > > > MTP2. 
> > > > [TOLGA]So also messages sent after local
> processor
> > > > outage ended but received before LSPR will be
> > > > discarded(?). How are they going to be
> > > retransmitted?
> > > > 
> > > > 
> > > > __________________________________
> > > > Do you Yahoo!?
> > > > Yahoo! Calendar - Free online calendar with
> sync
> > > to Outlook(TM).
> > > > http://calendar.yahoo.com
> > > >
> _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > 
> > > -- 
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> > 
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Calendar - Free online calendar with sync
> to Outlook(TM).
> > http://calendar.yahoo.com
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Wed Jun  4 14:27:04 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04948
	for <sigtran-archive@odin.ietf.org>; Wed, 4 Jun 2003 14:27:04 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h54IQeU07865
	for sigtran-archive@odin.ietf.org; Wed, 4 Jun 2003 14:26:40 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54IQLB07852;
	Wed, 4 Jun 2003 14:26:21 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54IN5B07744
	for <sigtran@optimus.ietf.org>; Wed, 4 Jun 2003 14:23:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04789
	for <sigtran@ietf.org>; Wed, 4 Jun 2003 14:22:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ncso-0006V6-00
	for sigtran@ietf.org; Wed, 04 Jun 2003 14:21:10 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[/DiwmsiEuXCeUz/IUSSWi0VeHnM79KXN])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ncsn-0006V2-00
	for sigtran@ietf.org; Wed, 04 Jun 2003 14:21:09 -0400
Received: from ns.pigworks.openss7.net (IDENT:9+HxLBWGAguA9JURCwxgD6vcDTXiJ6Zv@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h54IMxF27943;
	Wed, 4 Jun 2003 12:22:59 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h54IMxp26528;
	Wed, 4 Jun 2003 12:22:59 -0600
Date: Wed, 4 Jun 2003 12:22:59 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
Message-ID: <20030604122259.C25664@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030604114350.B25664@openss7.org> <20030604175601.74616.qmail@web12804.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030604175601.74616.qmail@web12804.mail.yahoo.com>; from tolga_asveren@yahoo.com on Wed, Jun 04, 2003 at 10:56:01AM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

If you want to avoid that, send your LPR in the
data stream.

--brian

Tolga Asveren wrote:                                                                 (Wed, 04 Jun 2003 10:56:01)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Yes.
> [TOLGA]But why? They are sent after local processor
> outage has ended. The sending side will keep timeout
> information for such a message (T7) and because it
> won't be acknowledged, link will be dropped.
> > 
> > --brian
> > 
> > Tolga Asveren wrote:                                
> >                                 (Wed, 04 Jun 2003
> > 03:51:49)
> > > Brian,
> > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > wrote:
> > > > Tolga,
> > > > 
> > > > In SS7 flushed messages are never retransmitted.
> > 
> > > > This
> > > > is because they are old and stagnant by the time
> > the
> > > > Flush_buffers is issued and must be dicareded.
> > > [TOLGA] Yes, but should we qualify also messages
> > sent
> > > after local processor outage ended but received on
> > the
> > > other side before LSPR (because they are sent on
> > > different streams) as "old"?
> > > > 
> > > > --brian
> > > > 
> > > > Tolga Asveren wrote:                            
> >    
> > > >                                 (Tue, 03 Jun
> > 2003
> > > > 13:18:29)
> > > > > Tom,
> > > > > 
> > > > > [..snip..]
> > > > > > If M2PA receives a Flush command from MTP3,
> > M2PA
> > > > > > SHALL discard the
> > > > > > incoming messages that were queued and
> > > > > > unacknowledged during the
> > > > > > processor outage condition. Furthermore,
> > M2PA
> > > > SHALL
> > > > > > discard messages
> > > > > > in the transmit and retransmit queues as
> > > > required by
> > > > > > MTP2. 
> > > > > [TOLGA]So also messages sent after local
> > processor
> > > > > outage ended but received before LSPR will be
> > > > > discarded(?). How are they going to be
> > > > retransmitted?
> > > > > 
> > > > > 
> > > > > __________________________________
> > > > > Do you Yahoo!?
> > > > > Yahoo! Calendar - Free online calendar with
> > sync
> > > > to Outlook(TM).
> > > > > http://calendar.yahoo.com
> > > > >
> > _______________________________________________
> > > > > Sigtran mailing list
> > > > > Sigtran@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > 
> > > > -- 
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > 
> > > 
> > > __________________________________
> > > Do you Yahoo!?
> > > Yahoo! Calendar - Free online calendar with sync
> > to Outlook(TM).
> > > http://calendar.yahoo.com
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
> http://calendar.yahoo.com
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Wed Jun  4 14:51:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06259
	for <sigtran-archive@odin.ietf.org>; Wed, 4 Jun 2003 14:51:31 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h54Ip7e10092
	for sigtran-archive@odin.ietf.org; Wed, 4 Jun 2003 14:51:07 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54IosB09922;
	Wed, 4 Jun 2003 14:50:55 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54IdCB09286
	for <sigtran@optimus.ietf.org>; Wed, 4 Jun 2003 14:39:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05450
	for <sigtran@ietf.org>; Wed, 4 Jun 2003 14:39:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nd8P-0006cr-00
	for sigtran@ietf.org; Wed, 04 Jun 2003 14:37:17 -0400
Received: from web12805.mail.yahoo.com ([216.136.174.40])
	by ietf-mx with smtp (Exim 4.12)
	id 19Nd8O-0006co-00
	for sigtran@ietf.org; Wed, 04 Jun 2003 14:37:16 -0400
Message-ID: <20030604183906.12293.qmail@web12805.mail.yahoo.com>
Received: from [208.255.120.2] by web12805.mail.yahoo.com via HTTP; Wed, 04 Jun 2003 11:39:06 PDT
Date: Wed, 4 Jun 2003 11:39:06 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
To: sigtran@ietf.org
In-Reply-To: <20030604122259.C25664@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

I would think, this needs to be documented both to
warn people and to prevent interoperability problems.

  Tolga
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Tolga,
> 
> If you want to avoid that, send your LPR in the
> data stream.
> 
> --brian
> 
> Tolga Asveren wrote:                                
>                                 (Wed, 04 Jun 2003
> 10:56:01)
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > Tolga,
> > > 
> > > Yes.
> > [TOLGA]But why? They are sent after local
> processor
> > outage has ended. The sending side will keep
> timeout
> > information for such a message (T7) and because it
> > won't be acknowledged, link will be dropped.
> > > 
> > > --brian
> > > 
> > > Tolga Asveren wrote:                            
>    
> > >                                 (Wed, 04 Jun
> 2003
> > > 03:51:49)
> > > > Brian,
> > > > --- "Brian F. G. Bidulock"
> <bidulock@openss7.org>
> > > > wrote:
> > > > > Tolga,
> > > > > 
> > > > > In SS7 flushed messages are never
> retransmitted.
> > > 
> > > > > This
> > > > > is because they are old and stagnant by the
> time
> > > the
> > > > > Flush_buffers is issued and must be
> dicareded.
> > > > [TOLGA] Yes, but should we qualify also
> messages
> > > sent
> > > > after local processor outage ended but
> received on
> > > the
> > > > other side before LSPR (because they are sent
> on
> > > > different streams) as "old"?
> > > > > 
> > > > > --brian
> > > > > 
> > > > > Tolga Asveren wrote:                        
>    
> > >    
> > > > >                                 (Tue, 03 Jun
> > > 2003
> > > > > 13:18:29)
> > > > > > Tom,
> > > > > > 
> > > > > > [..snip..]
> > > > > > > If M2PA receives a Flush command from
> MTP3,
> > > M2PA
> > > > > > > SHALL discard the
> > > > > > > incoming messages that were queued and
> > > > > > > unacknowledged during the
> > > > > > > processor outage condition. Furthermore,
> > > M2PA
> > > > > SHALL
> > > > > > > discard messages
> > > > > > > in the transmit and retransmit queues as
> > > > > required by
> > > > > > > MTP2. 
> > > > > > [TOLGA]So also messages sent after local
> > > processor
> > > > > > outage ended but received before LSPR will
> be
> > > > > > discarded(?). How are they going to be
> > > > > retransmitted?
> > > > > > 
> > > > > > 
> > > > > > __________________________________
> > > > > > Do you Yahoo!?
> > > > > > Yahoo! Calendar - Free online calendar
> with
> > > sync
> > > > > to Outlook(TM).
> > > > > > http://calendar.yahoo.com
> > > > > >
> > > _______________________________________________
> > > > > > Sigtran mailing list
> > > > > > Sigtran@ietf.org
> > > > > >
> https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > 
> > > > > -- 
> > > > > Brian F. G. Bidulock
> > > > > bidulock@openss7.org
> > > > > http://www.openss7.org/
> > > > >
> _______________________________________________
> > > > > Sigtran mailing list
> > > > > Sigtran@ietf.org
> > > > >
> https://www1.ietf.org/mailman/listinfo/sigtran
> > > > 
> > > > 
> > > > __________________________________
> > > > Do you Yahoo!?
> > > > Yahoo! Calendar - Free online calendar with
> sync
> > > to Outlook(TM).
> > > > http://calendar.yahoo.com
> > > >
> _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > 
> > > -- 
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> > 
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Calendar - Free online calendar with sync
> to Outlook(TM).
> > http://calendar.yahoo.com
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Wed Jun  4 15:16:36 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08512
	for <sigtran-archive@odin.ietf.org>; Wed, 4 Jun 2003 15:16:35 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h54JG7712564
	for sigtran-archive@odin.ietf.org; Wed, 4 Jun 2003 15:16:07 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54JFFB12522;
	Wed, 4 Jun 2003 15:15:15 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54JCjB12343
	for <sigtran@optimus.ietf.org>; Wed, 4 Jun 2003 15:12:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08073
	for <sigtran@ietf.org>; Wed, 4 Jun 2003 15:12:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ndev-000775-00
	for sigtran@ietf.org; Wed, 04 Jun 2003 15:10:53 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[3NhKpDnWmupbBoCI1i5bf+0oNQB40cCI])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ndeu-000771-00
	for sigtran@ietf.org; Wed, 04 Jun 2003 15:10:52 -0400
Received: from ns.pigworks.openss7.net (IDENT:Y06PJUpBLdz47fKIqkW/Bdi7RqDP9M1A@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h54JCgF28715;
	Wed, 4 Jun 2003 13:12:42 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h54JCgC27407;
	Wed, 4 Jun 2003 13:12:42 -0600
Date: Wed, 4 Jun 2003 13:12:42 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
Message-ID: <20030604131242.E25664@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030604122259.C25664@openss7.org> <20030604183906.12293.qmail@web12805.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030604183906.12293.qmail@web12805.mail.yahoo.com>; from tolga_asveren@yahoo.com on Wed, Jun 04, 2003 at 11:39:06AM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

Ok.  Add a paragraph somewhere that says:

LSPR, LSBE, LSA SHOULD be sent on stream 1.  All other
LS messages SHOULD be sent on stream 0.

Done.

--brian

Tolga Asveren wrote:                                                                 (Wed, 04 Jun 2003 11:39:06)
> I would think, this needs to be documented both to
> warn people and to prevent interoperability problems.
> 
>   Tolga
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > If you want to avoid that, send your LPR in the
> > data stream.
> > 
> > --brian
> > 
> > Tolga Asveren wrote:                                
> >                                 (Wed, 04 Jun 2003
> > 10:56:01)
> > > Brian,
> > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > wrote:
> > > > Tolga,
> > > > 
> > > > Yes.
> > > [TOLGA]But why? They are sent after local
> > processor
> > > outage has ended. The sending side will keep
> > timeout
> > > information for such a message (T7) and because it
> > > won't be acknowledged, link will be dropped.
> > > > 
> > > > --brian
> > > > 
> > > > Tolga Asveren wrote:                            
> >    
> > > >                                 (Wed, 04 Jun
> > 2003
> > > > 03:51:49)
> > > > > Brian,
> > > > > --- "Brian F. G. Bidulock"
> > <bidulock@openss7.org>
> > > > > wrote:
> > > > > > Tolga,
> > > > > > 
> > > > > > In SS7 flushed messages are never
> > retransmitted.
> > > > 
> > > > > > This
> > > > > > is because they are old and stagnant by the
> > time
> > > > the
> > > > > > Flush_buffers is issued and must be
> > dicareded.
> > > > > [TOLGA] Yes, but should we qualify also
> > messages
> > > > sent
> > > > > after local processor outage ended but
> > received on
> > > > the
> > > > > other side before LSPR (because they are sent
> > on
> > > > > different streams) as "old"?
> > > > > > 
> > > > > > --brian
> > > > > > 
> > > > > > Tolga Asveren wrote:                        
> >    
> > > >    
> > > > > >                                 (Tue, 03 Jun
> > > > 2003
> > > > > > 13:18:29)
> > > > > > > Tom,
> > > > > > > 
> > > > > > > [..snip..]
> > > > > > > > If M2PA receives a Flush command from
> > MTP3,
> > > > M2PA
> > > > > > > > SHALL discard the
> > > > > > > > incoming messages that were queued and
> > > > > > > > unacknowledged during the
> > > > > > > > processor outage condition. Furthermore,
> > > > M2PA
> > > > > > SHALL
> > > > > > > > discard messages
> > > > > > > > in the transmit and retransmit queues as
> > > > > > required by
> > > > > > > > MTP2. 
> > > > > > > [TOLGA]So also messages sent after local
> > > > processor
> > > > > > > outage ended but received before LSPR will
> > be
> > > > > > > discarded(?). How are they going to be
> > > > > > retransmitted?
> > > > > > > 
> > > > > > > 
> > > > > > > __________________________________
> > > > > > > Do you Yahoo!?
> > > > > > > Yahoo! Calendar - Free online calendar
> > with
> > > > sync
> > > > > > to Outlook(TM).
> > > > > > > http://calendar.yahoo.com
> > > > > > >
> > > > _______________________________________________
> > > > > > > Sigtran mailing list
> > > > > > > Sigtran@ietf.org
> > > > > > >
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > 
> > > > > > -- 
> > > > > > Brian F. G. Bidulock
> > > > > > bidulock@openss7.org
> > > > > > http://www.openss7.org/
> > > > > >
> > _______________________________________________
> > > > > > Sigtran mailing list
> > > > > > Sigtran@ietf.org
> > > > > >
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > 
> > > > > 
> > > > > __________________________________
> > > > > Do you Yahoo!?
> > > > > Yahoo! Calendar - Free online calendar with
> > sync
> > > > to Outlook(TM).
> > > > > http://calendar.yahoo.com
> > > > >
> > _______________________________________________
> > > > > Sigtran mailing list
> > > > > Sigtran@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > 
> > > > -- 
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > 
> > > 
> > > __________________________________
> > > Do you Yahoo!?
> > > Yahoo! Calendar - Free online calendar with sync
> > to Outlook(TM).
> > > http://calendar.yahoo.com
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
> http://calendar.yahoo.com
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jun  5 00:34:54 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25172
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Jun 2003 00:34:54 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h554YSo17566
	for sigtran-archive@odin.ietf.org; Thu, 5 Jun 2003 00:34:28 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h554Y8B17550;
	Thu, 5 Jun 2003 00:34:09 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h554UJB17420
	for <sigtran@optimus.ietf.org>; Thu, 5 Jun 2003 00:30:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25130
	for <sigtran@ietf.org>; Thu, 5 Jun 2003 00:30:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NmMT-0002q5-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 00:28:25 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NmMT-0002pq-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 00:28:25 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h554TLBN013909;
	Wed, 4 Jun 2003 23:29:40 -0500 (CDT)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h554Sw1C010373;
	Wed, 4 Jun 2003 23:28:59 -0500 (CDT)
Date: Wed, 4 Jun 2003 23:28:58 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: Umesh Vats <umesh@ccpu.com>
cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
In-Reply-To: <ACEMIJONPBBPDLOKCABHAEICCAAA.umesh@ccpu.com>
Message-ID: <Pine.SOL.4.10.10306042321060.783-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


Umesh,


  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******

On Wed, 4 Jun 2003, Umesh Vats wrote:

> I have some queries for the case, where an SG comprises of three SGPs
> and connected with 4 ASPs.
> 
> Each ASP is connected with each SGP.
> So the list of associtions is :
> 
>  SGP1 : ASP1 (Assoc1), ASP2 (Assoc2), ASP3 (Assoc3), ASP4 (Assoc4)
>  SGP2 : ASP1 (Assoc5), ASP2 (Assoc6), ASP3 (Assoc7), ASP4 (Assoc8)
>  SGP3 : ASP1 (Assoc9), ASP2 (Assoc10), ASP3 (Assoc11), ASP4 (Assoc12)
> 
> 1. AS in n+k redundancy mode : Suppose we configure n as 3.
>                    Now suppose ASP1 goes ACTIVE for all three SGPs.
>                    Does this mean that :
> 
>                    n=3 limit is reached and AS should be made active.(e.g.
>                    this may mean that ASP is capable handling traffic
>                    otherwise it would have gone ACTIVE only via one SGP)
>                                      OR
>                    n=1 limit is reached. At least two more ASPs need to
>                    go ACTIVE via any of the SGPs in SG before AS can go
>                    ACTIVE on SG.

Basically AS traffic moded is determined with respect to a particular
SGP.So SGP1 needs 3 ASPes to declare the complete AS as ACTIVE(this is
true only at starting case)So your first case is correct..

> 
> 
> 2. AS in override mode : Suppose an application server is being served by
> all
>                    4 ASPs in override mode. Does this mean that,
> 
>                    at any given time, each SGP will have at the most one ASP
>                    ACTIVE for an AS
>                                       OR
>                    at any given time, an SG (combining all SGPs) will have
> at
>                    the most one ASP ACTIVE for an AS
> 
Here also, When ASP1 sends ACP ACTIV to SGP1 then SGP1 delcares AS as
ACTIVE.But with respect to other SGPs state of AS is DOWN.

--Samuel
> 
> Umesh Vats
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 

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



From mailnull@www1.ietf.org  Thu Jun  5 01:03:38 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25594
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Jun 2003 01:03:38 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5553Ai19514
	for sigtran-archive@odin.ietf.org; Thu, 5 Jun 2003 01:03:10 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5552uB19484;
	Thu, 5 Jun 2003 01:02:56 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55506B19376
	for <sigtran@optimus.ietf.org>; Thu, 5 Jun 2003 01:00:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25535
	for <sigtran@ietf.org>; Thu, 5 Jun 2003 01:00:00 -0400 (EDT)
From: kakaul@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NmpH-0002vy-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 00:58:11 -0400
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NmpD-0002ve-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 00:58:10 -0400
Received: from hindon.hss.co.in (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h554urs08295
	for <sigtran@ietf.org>; Thu, 5 Jun 2003 10:26:58 +0530 (IST)
Received: from ultra.hss.co.in (ultra [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h554uh908276;
	Thu, 5 Jun 2003 10:26:45 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h554xvU21033;
	Thu, 5 Jun 2003 10:30:04 +0530 (IST)
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
To: <umesh@ccpu.com>
Cc: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF0190C35A.E6954715-ON65256D3C.001B26B9@hss.hns.com>
Date: Thu, 5 Jun 2003 10:30:27 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 05/06/2003
 10:24:17 AM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>





Umesh some comments

It all depends on how SG is implemented.If SS7 node adjacent to SG is
routing traffic to SGP without making any assumptions of inter SGP routing
then routing of traffic to AS ultimately depends on the number of active
associations capable of handling traffic for AS corresponding to SGP.In
this case scope of n+k redundancy is valid corresponding to SGP i.e number
of active associations of ASP's (of AS) with single SGP(of SG), which
should be n to handle traffic for AS. For this scenario your ORD options
are valid for both the points.Now if SS7 node adjacent to SG is routing
traffic to SGP without caring whether the traffic for AS is ultimately
routed through active associations of ASP's (of AS) with SGP1 or SGP2 or
SGP3 which may involve inter SGP routing then scope of n+k redundancy is
valid corresponding to SG i.e number of active associations of ASP's (of
AS) with any SGP in the SG.For this scenario first options of your two
points are appropriate. Ultimately it all depends on how you view and
implement SG.

Regards
Kamesh
Hughes Software Systems




"Umesh Vats" <umesh@ccpu.com>@ietf.org on 06/04/2003 09:48:07 PM

Please respond to <umesh@ccpu.com>

Sent by:    sigtran-admin@ietf.org


To:    <sigtran@ietf.org>
cc:

Subject:    [Sigtran] M3UA : Multiple SGPs in SG


I have some queries for the case, where an SG comprises of three SGPs
and connected with 4 ASPs.

Each ASP is connected with each SGP.
So the list of associtions is :

 SGP1 : ASP1 (Assoc1), ASP2 (Assoc2), ASP3 (Assoc3), ASP4 (Assoc4)
 SGP2 : ASP1 (Assoc5), ASP2 (Assoc6), ASP3 (Assoc7), ASP4 (Assoc8)
 SGP3 : ASP1 (Assoc9), ASP2 (Assoc10), ASP3 (Assoc11), ASP4 (Assoc12)

1. AS in n+k redundancy mode : Suppose we configure n as 3.
                   Now suppose ASP1 goes ACTIVE for all three SGPs.
                   Does this mean that :

                   n=3 limit is reached and AS should be made active.(e.g.
                   this may mean that ASP is capable handling traffic
                   otherwise it would have gone ACTIVE only via one SGP)
                                     OR
                   n=1 limit is reached. At least two more ASPs need to
                   go ACTIVE via any of the SGPs in SG before AS can go
                   ACTIVE on SG.


2. AS in override mode : Suppose an application server is being served by
all
                   4 ASPs in override mode. Does this mean that,

                   at any given time, each SGP will have at the most one
                   ASP
                   ACTIVE for an AS
                                      OR
                   at any given time, an SG (combining all SGPs) will have
at
                   the most one ASP ACTIVE for an AS


Umesh Vats

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


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



From mailnull@www1.ietf.org  Thu Jun  5 07:08:34 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14980
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Jun 2003 07:08:34 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h55B8Bk24589
	for sigtran-archive@odin.ietf.org; Thu, 5 Jun 2003 07:08:11 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55B7rB24573;
	Thu, 5 Jun 2003 07:07:54 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55B4DB23554
	for <sigtran@optimus.ietf.org>; Thu, 5 Jun 2003 07:04:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14704
	for <sigtran@ietf.org>; Thu, 5 Jun 2003 07:04:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NsVb-0004uE-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 07:02:15 -0400
Received: from web12808.mail.yahoo.com ([216.136.174.43])
	by ietf-mx with smtp (Exim 4.12)
	id 19NsVb-0004u9-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 07:02:15 -0400
Message-ID: <20030605110406.91245.qmail@web12808.mail.yahoo.com>
Received: from [208.255.120.2] by web12808.mail.yahoo.com via HTTP; Thu, 05 Jun 2003 04:04:06 PDT
Date: Thu, 5 Jun 2003 04:04:06 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
To: sigtran@ietf.org
In-Reply-To: <OF0190C35A.E6954715-ON65256D3C.001B26B9@hss.hns.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Kamesh,

Some comments below, just my 2 cents.

  Tolga
--- kakaul@hss.hns.com wrote:
> 
> 
> 
> 
> Umesh some comments
> 
> It all depends on how SG is implemented.If SS7 node
> adjacent to SG is
> routing traffic to SGP without making any
> assumptions of inter SGP routing
> then routing of traffic to AS ultimately depends on
> the number of active
> associations capable of handling traffic for AS
> corresponding to SGP.In
> this case scope of n+k redundancy is valid
> corresponding to SGP i.e number
> of active associations of ASP's (of AS) with single
> SGP(of SG), which
> should be n to handle traffic for AS. For this
> scenario your ORD options
[TOLGA]A SG is seen from SS7 point of view as a single
entity. A node in SS7 domain is not aware of the
concept of SGs and SGPs. BTW, important is the number
of ACTIVE ASPs to handle the traffic, not the number
of associations to an ACTIVE ASP. So, I wouldn't think
that it will increase the performance of an ASP, if
you have 3 -instead of 1- association to the same ASP.
> are valid for both the points.Now if SS7 node
> adjacent to SG is routing
> traffic to SGP without caring whether the traffic
> for AS is ultimately
> routed through active associations of ASP's (of AS)
> with SGP1 or SGP2 or
> SGP3 which may involve inter SGP routing then scope
> of n+k redundancy is
> valid corresponding to SG i.e number of active
> associations of ASP's (of
> AS) with any SGP in the SG.For this scenario first
> options of your two
> points are appropriate. Ultimately it all depends on
> how you view and
> implement SG.
[TOLGA]IMO it is clear that for n+k situation, both
ASP and SGP should behave the same, otherwise it might
bring interoperability problems that SG tries to
activate traffic based on the SGwide number of ACTIVE
ASPs, and ASP kepps the counter per SGP. ASPTM is sent
from ASP/SGP to ASP/SGP. Those messages are never
intended to be sent per SG. So, IMO it is clear that
decisions should be made always from SGP point of
view, not SG. 
> 
> Regards
> Kamesh
> Hughes Software Systems
> 
> 
> 
> 
> "Umesh Vats" <umesh@ccpu.com>@ietf.org on 06/04/2003
> 09:48:07 PM
> 
> Please respond to <umesh@ccpu.com>
> 
> Sent by:    sigtran-admin@ietf.org
> 
> 
> To:    <sigtran@ietf.org>
> cc:
> 
> Subject:    [Sigtran] M3UA : Multiple SGPs in SG
> 
> 
> I have some queries for the case, where an SG
> comprises of three SGPs
> and connected with 4 ASPs.
> 
> Each ASP is connected with each SGP.
> So the list of associtions is :
> 
>  SGP1 : ASP1 (Assoc1), ASP2 (Assoc2), ASP3 (Assoc3),
> ASP4 (Assoc4)
>  SGP2 : ASP1 (Assoc5), ASP2 (Assoc6), ASP3 (Assoc7),
> ASP4 (Assoc8)
>  SGP3 : ASP1 (Assoc9), ASP2 (Assoc10), ASP3
> (Assoc11), ASP4 (Assoc12)
> 
> 1. AS in n+k redundancy mode : Suppose we configure
> n as 3.
>                    Now suppose ASP1 goes ACTIVE for
> all three SGPs.
>                    Does this mean that :
> 
>                    n=3 limit is reached and AS
> should be made active.(e.g.
>                    this may mean that ASP is capable
> handling traffic
>                    otherwise it would have gone
> ACTIVE only via one SGP)
>                                      OR
>                    n=1 limit is reached. At least
> two more ASPs need to
>                    go ACTIVE via any of the SGPs in
> SG before AS can go
>                    ACTIVE on SG.
> 
> 
> 2. AS in override mode : Suppose an application
> server is being served by
> all
>                    4 ASPs in override mode. Does
> this mean that,
> 
>                    at any given time, each SGP will
> have at the most one
>                    ASP
>                    ACTIVE for an AS
>                                       OR
>                    at any given time, an SG
> (combining all SGPs) will have
> at
>                    the most one ASP ACTIVE for an AS
> 
> 
> Umesh Vats
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
>  https://www1.ietf.org/mailman/listinfo/sigtran
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jun  5 07:50:59 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16565
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Jun 2003 07:50:59 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h55BoTR27237
	for sigtran-archive@odin.ietf.org; Thu, 5 Jun 2003 07:50:29 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55BoAB27159;
	Thu, 5 Jun 2003 07:50:10 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55BhbB26812
	for <sigtran@optimus.ietf.org>; Thu, 5 Jun 2003 07:43:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16296
	for <sigtran@ietf.org>; Thu, 5 Jun 2003 07:43:36 -0400 (EDT)
From: kakaul@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nt7o-0005B0-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 07:41:44 -0400
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nt7m-0005Ap-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 07:41:43 -0400
Received: from hindon.hss.co.in (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h55BeYu29263
	for <sigtran@ietf.org>; Thu, 5 Jun 2003 17:10:34 +0530 (IST)
Received: from ultra.hss.co.in (ultra [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h55BeW929257;
	Thu, 5 Jun 2003 17:10:32 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h55Bhvb25822;
	Thu, 5 Jun 2003 17:13:58 +0530 (IST)
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF9B119ABC.F64FBD76-ON65256D3C.0040299F@hss.hns.com>
Date: Thu, 5 Jun 2003 17:14:28 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 05/06/2003
 05:08:07 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>





Tolga,
   Can you clearly show with figure how an SS7 node adjacent to SG would
route traffic for AS in this scenario, clearly showing signalling links
used by adjacent SS7 node and mapping of these links to SGP's of SG.

Regards
Kamesh





Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org on 06/05/2003 04:34:06 PM

Sent by:    sigtran-admin@ietf.org


To:    sigtran@ietf.org
cc:

Subject:    Re: [Sigtran] M3UA : Multiple SGPs in SG


Kamesh,

Some comments below, just my 2 cents.

  Tolga
--- kakaul@hss.hns.com wrote:
>
>
>
>
> Umesh some comments
>
> It all depends on how SG is implemented.If SS7 node
> adjacent to SG is
> routing traffic to SGP without making any
> assumptions of inter SGP routing
> then routing of traffic to AS ultimately depends on
> the number of active
> associations capable of handling traffic for AS
> corresponding to SGP.In
> this case scope of n+k redundancy is valid
> corresponding to SGP i.e number
> of active associations of ASP's (of AS) with single
> SGP(of SG), which
> should be n to handle traffic for AS. For this
> scenario your ORD options
[TOLGA]A SG is seen from SS7 point of view as a single
entity. A node in SS7 domain is not aware of the
concept of SGs and SGPs. BTW, important is the number
of ACTIVE ASPs to handle the traffic, not the number
of associations to an ACTIVE ASP. So, I wouldn't think
that it will increase the performance of an ASP, if
you have 3 -instead of 1- association to the same ASP.
> are valid for both the points.Now if SS7 node
> adjacent to SG is routing
> traffic to SGP without caring whether the traffic
> for AS is ultimately
> routed through active associations of ASP's (of AS)
> with SGP1 or SGP2 or
> SGP3 which may involve inter SGP routing then scope
> of n+k redundancy is
> valid corresponding to SG i.e number of active
> associations of ASP's (of
> AS) with any SGP in the SG.For this scenario first
> options of your two
> points are appropriate. Ultimately it all depends on
> how you view and
> implement SG.
[TOLGA]IMO it is clear that for n+k situation, both
ASP and SGP should behave the same, otherwise it might
bring interoperability problems that SG tries to
activate traffic based on the SGwide number of ACTIVE
ASPs, and ASP kepps the counter per SGP. ASPTM is sent
from ASP/SGP to ASP/SGP. Those messages are never
intended to be sent per SG. So, IMO it is clear that
decisions should be made always from SGP point of
view, not SG.
>
> Regards
> Kamesh
> Hughes Software Systems
>
>
>
>
> "Umesh Vats" <umesh@ccpu.com>@ietf.org on 06/04/2003
> 09:48:07 PM
>
> Please respond to <umesh@ccpu.com>
>
> Sent by:    sigtran-admin@ietf.org
>
>
> To:    <sigtran@ietf.org>
> cc:
>
> Subject:    [Sigtran] M3UA : Multiple SGPs in SG
>
>
> I have some queries for the case, where an SG
> comprises of three SGPs
> and connected with 4 ASPs.
>
> Each ASP is connected with each SGP.
> So the list of associtions is :
>
>  SGP1 : ASP1 (Assoc1), ASP2 (Assoc2), ASP3 (Assoc3),
> ASP4 (Assoc4)
>  SGP2 : ASP1 (Assoc5), ASP2 (Assoc6), ASP3 (Assoc7),
> ASP4 (Assoc8)
>  SGP3 : ASP1 (Assoc9), ASP2 (Assoc10), ASP3
> (Assoc11), ASP4 (Assoc12)
>
> 1. AS in n+k redundancy mode : Suppose we configure
> n as 3.
>                    Now suppose ASP1 goes ACTIVE for
> all three SGPs.
>                    Does this mean that :
>
>                    n=3 limit is reached and AS
> should be made active.(e.g.
>                    this may mean that ASP is capable
> handling traffic
>                    otherwise it would have gone
> ACTIVE only via one SGP)
>                                      OR
>                    n=1 limit is reached. At least
> two more ASPs need to
>                    go ACTIVE via any of the SGPs in
> SG before AS can go
>                    ACTIVE on SG.
>
>
> 2. AS in override mode : Suppose an application
> server is being served by
> all
>                    4 ASPs in override mode. Does
> this mean that,
>
>                    at any given time, each SGP will
> have at the most one
>                    ASP
>                    ACTIVE for an AS
>                                       OR
>                    at any given time, an SG
> (combining all SGPs) will have
> at
>                    the most one ASP ACTIVE for an AS
>
>
> Umesh Vats
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
>  https://www1.ietf.org/mailman/listinfo/sigtran
>
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
 https://www1.ietf.org/mailman/listinfo/sigtran


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



From mailnull@www1.ietf.org  Thu Jun  5 08:29:10 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19805
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Jun 2003 08:29:10 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h55CSgc30541
	for sigtran-archive@odin.ietf.org; Thu, 5 Jun 2003 08:28:42 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55CRSB30325;
	Thu, 5 Jun 2003 08:27:29 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55CNvB30135
	for <sigtran@optimus.ietf.org>; Thu, 5 Jun 2003 08:23:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18865
	for <sigtran@ietf.org>; Thu, 5 Jun 2003 08:23:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ntkp-0005iu-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 08:22:03 -0400
Received: from web12807.mail.yahoo.com ([216.136.174.42])
	by ietf-mx with smtp (Exim 4.12)
	id 19Ntko-0005ig-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 08:22:02 -0400
Message-ID: <20030605122351.17422.qmail@web12807.mail.yahoo.com>
Received: from [208.255.120.2] by web12807.mail.yahoo.com via HTTP; Thu, 05 Jun 2003 05:23:51 PDT
Date: Thu, 5 Jun 2003 05:23:51 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
To: sigtran@ietf.org
In-Reply-To: <OF9B119ABC.F64FBD76-ON65256D3C.0040299F@hss.hns.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Hi Kamesh,

            
             associations
    | | | |    | | | |      | | | |
   +---------+------------+-----------+
   |   SGP1  |   SGP2     |   SGP3    |
   ************************************
   *              MTP3                *
   *         |            |           *
   * host1   |   host2    |  host3    *
   ************************************
     |   |       |     |       |    |
     |   |       |     |       |    |
                Links


Basically adjacent SS7 node is just aware that there
is a MTP3 peer and some links to communicate with it,
and will probably loadshare traffic based on SLS
betwen those links. Once the messages are inside the
SG-box, it is up to you, what to do with them (and I
would think although a lot of things inside SG are
implementation dependent, there is no direct mapping
between links and SGPs)

BTW, like you have said, it really migt be possible to
loadshare traffic between two ASPs, which are ACTIVE
for separate SGPs -and this also IMO would qualify as
2 ACTIVE ASPs because this is not two associations to
the same ASP-, but I still think this might bring
interoperability problems. To decide, when to start
traffic, IMO ASP and SGP should work in harmony. So,
IMO it is a good choice to leave the peers as SGP and
ASP for ASPTM procedures.

I also checked a sentence related with this topic -in
ASP Active Procedures- in RFC, there it stands that
"ASPs should coordinate the number of ACTIVE ASPs for
the AS", I think this may be clarified as "the number
of ACTIVE ASPs for the AS for a specific SGP".

   Tolga


--- kakaul@hss.hns.com wrote:
> 
> 
> 
> 
> Tolga,
>    Can you clearly show with figure how an SS7 node
> adjacent to SG would
> route traffic for AS in this scenario, clearly
> showing signalling links
> used by adjacent SS7 node and mapping of these links
> to SGP's of SG.
> 
> Regards
> Kamesh
> 
> 
> 
> 
> 
> Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org on
> 06/05/2003 04:34:06 PM
> 
> Sent by:    sigtran-admin@ietf.org
> 
> 
> To:    sigtran@ietf.org
> cc:
> 
> Subject:    Re: [Sigtran] M3UA : Multiple SGPs in SG
> 
> 
> Kamesh,
> 
> Some comments below, just my 2 cents.
> 
>   Tolga
> --- kakaul@hss.hns.com wrote:
> >
> >
> >
> >
> > Umesh some comments
> >
> > It all depends on how SG is implemented.If SS7
> node
> > adjacent to SG is
> > routing traffic to SGP without making any
> > assumptions of inter SGP routing
> > then routing of traffic to AS ultimately depends
> on
> > the number of active
> > associations capable of handling traffic for AS
> > corresponding to SGP.In
> > this case scope of n+k redundancy is valid
> > corresponding to SGP i.e number
> > of active associations of ASP's (of AS) with
> single
> > SGP(of SG), which
> > should be n to handle traffic for AS. For this
> > scenario your ORD options
> [TOLGA]A SG is seen from SS7 point of view as a
> single
> entity. A node in SS7 domain is not aware of the
> concept of SGs and SGPs. BTW, important is the
> number
> of ACTIVE ASPs to handle the traffic, not the number
> of associations to an ACTIVE ASP. So, I wouldn't
> think
> that it will increase the performance of an ASP, if
> you have 3 -instead of 1- association to the same
> ASP.
> > are valid for both the points.Now if SS7 node
> > adjacent to SG is routing
> > traffic to SGP without caring whether the traffic
> > for AS is ultimately
> > routed through active associations of ASP's (of
> AS)
> > with SGP1 or SGP2 or
> > SGP3 which may involve inter SGP routing then
> scope
> > of n+k redundancy is
> > valid corresponding to SG i.e number of active
> > associations of ASP's (of
> > AS) with any SGP in the SG.For this scenario first
> > options of your two
> > points are appropriate. Ultimately it all depends
> on
> > how you view and
> > implement SG.
> [TOLGA]IMO it is clear that for n+k situation, both
> ASP and SGP should behave the same, otherwise it
> might
> bring interoperability problems that SG tries to
> activate traffic based on the SGwide number of
> ACTIVE
> ASPs, and ASP kepps the counter per SGP. ASPTM is
> sent
> from ASP/SGP to ASP/SGP. Those messages are never
> intended to be sent per SG. So, IMO it is clear that
> decisions should be made always from SGP point of
> view, not SG.
> >
> > Regards
> > Kamesh
> > Hughes Software Systems
> >
> >
> >
> >
> > "Umesh Vats" <umesh@ccpu.com>@ietf.org on
> 06/04/2003
> > 09:48:07 PM
> >
> > Please respond to <umesh@ccpu.com>
> >
> > Sent by:    sigtran-admin@ietf.org
> >
> >
> > To:    <sigtran@ietf.org>
> > cc:
> >
> > Subject:    [Sigtran] M3UA : Multiple SGPs in SG
> >
> >
> > I have some queries for the case, where an SG
> > comprises of three SGPs
> > and connected with 4 ASPs.
> >
> > Each ASP is connected with each SGP.
> > So the list of associtions is :
> >
> >  SGP1 : ASP1 (Assoc1), ASP2 (Assoc2), ASP3
> (Assoc3),
> > ASP4 (Assoc4)
> >  SGP2 : ASP1 (Assoc5), ASP2 (Assoc6), ASP3
> (Assoc7),
> > ASP4 (Assoc8)
> >  SGP3 : ASP1 (Assoc9), ASP2 (Assoc10), ASP3
> > (Assoc11), ASP4 (Assoc12)
> >
> > 1. AS in n+k redundancy mode : Suppose we
> configure
> > n as 3.
> >                    Now suppose ASP1 goes ACTIVE
> for
> > all three SGPs.
> >                    Does this mean that :
> >
> >                    n=3 limit is reached and AS
> > should be made active.(e.g.
> >                    this may mean that ASP is
> capable
> > handling traffic
> >                    otherwise it would have gone
> > ACTIVE only via one SGP)
> >                                      OR
> >                    n=1 limit is reached. At least
> > two more ASPs need to
> >                    go ACTIVE via any of the SGPs
> in
> > SG before AS can go
> >                    ACTIVE on SG.
> >
> >
> > 2. AS in override mode : Suppose an application
> > server is being served by
> > all
> >                    4 ASPs in override mode. Does
> > this mean that,
> >
> >                    at any given time, each SGP
> will
> > have at the most one
> >                    ASP
> >                    ACTIVE for an AS
> >                                       OR
> >                    at any given time, an SG
> > (combining all SGPs) will have
> > at
> >                    the most one ASP ACTIVE for an
> AS
> >
> >
> > Umesh Vats
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> >  https://www1.ietf.org/mailman/listinfo/sigtran
> >
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Calendar - Free online calendar with sync to
> Outlook(TM).
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jun  5 09:21:07 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23940
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Jun 2003 09:21:07 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h55DKef03336
	for sigtran-archive@odin.ietf.org; Thu, 5 Jun 2003 09:20:40 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55DKIB03308;
	Thu, 5 Jun 2003 09:20:18 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55DHPB03169
	for <sigtran@optimus.ietf.org>; Thu, 5 Jun 2003 09:17:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23866
	for <sigtran@ietf.org>; Thu, 5 Jun 2003 09:17:22 -0400 (EDT)
From: kakaul@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NuaY-0006k2-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 09:15:30 -0400
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NuaR-0006jm-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 09:15:23 -0400
Received: from hindon.hss.co.in (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h55DEAd15687
	for <sigtran@ietf.org>; Thu, 5 Jun 2003 18:44:10 +0530 (IST)
Received: from ultra.hss.co.in (ultra [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h55DE8915679;
	Thu, 5 Jun 2003 18:44:08 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h55DHSF03438;
	Thu, 5 Jun 2003 18:47:33 +0530 (IST)
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF57D5A76E.AF87B607-ON65256D3C.00475459@hss.hns.com>
Date: Thu, 5 Jun 2003 18:47:59 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 05/06/2003
 06:41:41 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>





Hi Tolga,
                     I want to clarify one more point that in n+k
redundancy mode we are saying that n ASP's should be active in SGP for the
AS to handle AS traffic, but can you tell me are we assuming that SGP
handling entire traffic of AS is an high processing machine with
processing power of 3 ASP's.I think it is slightly unfair on SGP. We can
also distribute traffic for AS among SGP's of SG which has active
associations with three ASP's and allow implementations to load share
traffic of AS not only among ASP's (of AS) but within SGP's of SG too.

Regards
Kamesh




Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org on 06/05/2003 05:53:51 PM

Sent by:    sigtran-admin@ietf.org


To:    sigtran@ietf.org
cc:

Subject:    Re: [Sigtran] M3UA : Multiple SGPs in SG


Hi Kamesh,


             associations
    | | | |    | | | |      | | | |
   +---------+------------+-----------+
   |   SGP1  |   SGP2     |   SGP3    |
   ************************************
   *              MTP3                *
   *         |            |           *
   * host1   |   host2    |  host3    *
   ************************************
     |   |       |     |       |    |
     |   |       |     |       |    |
                Links


Basically adjacent SS7 node is just aware that there
is a MTP3 peer and some links to communicate with it,
and will probably loadshare traffic based on SLS
betwen those links. Once the messages are inside the
SG-box, it is up to you, what to do with them (and I
would think although a lot of things inside SG are
implementation dependent, there is no direct mapping
between links and SGPs)

BTW, like you have said, it really migt be possible to
loadshare traffic between two ASPs, which are ACTIVE
for separate SGPs -and this also IMO would qualify as
2 ACTIVE ASPs because this is not two associations to
the same ASP-, but I still think this might bring
interoperability problems. To decide, when to start
traffic, IMO ASP and SGP should work in harmony. So,
IMO it is a good choice to leave the peers as SGP and
ASP for ASPTM procedures.

I also checked a sentence related with this topic -in
ASP Active Procedures- in RFC, there it stands that
"ASPs should coordinate the number of ACTIVE ASPs for
the AS", I think this may be clarified as "the number
of ACTIVE ASPs for the AS for a specific SGP".

   Tolga


--- kakaul@hss.hns.com wrote:
>
>
>
>
> Tolga,
>    Can you clearly show with figure how an SS7 node
> adjacent to SG would
> route traffic for AS in this scenario, clearly
> showing signalling links
> used by adjacent SS7 node and mapping of these links
> to SGP's of SG.
>
> Regards
> Kamesh
>
>
>
>
>
> Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org on
> 06/05/2003 04:34:06 PM
>
> Sent by:    sigtran-admin@ietf.org
>
>
> To:    sigtran@ietf.org
> cc:
>
> Subject:    Re: [Sigtran] M3UA : Multiple SGPs in SG
>
>
> Kamesh,
>
> Some comments below, just my 2 cents.
>
>   Tolga
> --- kakaul@hss.hns.com wrote:
> >
> >
> >
> >
> > Umesh some comments
> >
> > It all depends on how SG is implemented.If SS7
> node
> > adjacent to SG is
> > routing traffic to SGP without making any
> > assumptions of inter SGP routing
> > then routing of traffic to AS ultimately depends
> on
> > the number of active
> > associations capable of handling traffic for AS
> > corresponding to SGP.In
> > this case scope of n+k redundancy is valid
> > corresponding to SGP i.e number
> > of active associations of ASP's (of AS) with
> single
> > SGP(of SG), which
> > should be n to handle traffic for AS. For this
> > scenario your ORD options
> [TOLGA]A SG is seen from SS7 point of view as a
> single
> entity. A node in SS7 domain is not aware of the
> concept of SGs and SGPs. BTW, important is the
> number
> of ACTIVE ASPs to handle the traffic, not the number
> of associations to an ACTIVE ASP. So, I wouldn't
> think
> that it will increase the performance of an ASP, if
> you have 3 -instead of 1- association to the same
> ASP.
> > are valid for both the points.Now if SS7 node
> > adjacent to SG is routing
> > traffic to SGP without caring whether the traffic
> > for AS is ultimately
> > routed through active associations of ASP's (of
> AS)
> > with SGP1 or SGP2 or
> > SGP3 which may involve inter SGP routing then
> scope
> > of n+k redundancy is
> > valid corresponding to SG i.e number of active
> > associations of ASP's (of
> > AS) with any SGP in the SG.For this scenario first
> > options of your two
> > points are appropriate. Ultimately it all depends
> on
> > how you view and
> > implement SG.
> [TOLGA]IMO it is clear that for n+k situation, both
> ASP and SGP should behave the same, otherwise it
> might
> bring interoperability problems that SG tries to
> activate traffic based on the SGwide number of
> ACTIVE
> ASPs, and ASP kepps the counter per SGP. ASPTM is
> sent
> from ASP/SGP to ASP/SGP. Those messages are never
> intended to be sent per SG. So, IMO it is clear that
> decisions should be made always from SGP point of
> view, not SG.
> >
> > Regards
> > Kamesh
> > Hughes Software Systems
> >
> >
> >
> >
> > "Umesh Vats" <umesh@ccpu.com>@ietf.org on
> 06/04/2003
> > 09:48:07 PM
> >
> > Please respond to <umesh@ccpu.com>
> >
> > Sent by:    sigtran-admin@ietf.org
> >
> >
> > To:    <sigtran@ietf.org>
> > cc:
> >
> > Subject:    [Sigtran] M3UA : Multiple SGPs in SG
> >
> >
> > I have some queries for the case, where an SG
> > comprises of three SGPs
> > and connected with 4 ASPs.
> >
> > Each ASP is connected with each SGP.
> > So the list of associtions is :
> >
> >  SGP1 : ASP1 (Assoc1), ASP2 (Assoc2), ASP3
> (Assoc3),
> > ASP4 (Assoc4)
> >  SGP2 : ASP1 (Assoc5), ASP2 (Assoc6), ASP3
> (Assoc7),
> > ASP4 (Assoc8)
> >  SGP3 : ASP1 (Assoc9), ASP2 (Assoc10), ASP3
> > (Assoc11), ASP4 (Assoc12)
> >
> > 1. AS in n+k redundancy mode : Suppose we
> configure
> > n as 3.
> >                    Now suppose ASP1 goes ACTIVE
> for
> > all three SGPs.
> >                    Does this mean that :
> >
> >                    n=3 limit is reached and AS
> > should be made active.(e.g.
> >                    this may mean that ASP is
> capable
> > handling traffic
> >                    otherwise it would have gone
> > ACTIVE only via one SGP)
> >                                      OR
> >                    n=1 limit is reached. At least
> > two more ASPs need to
> >                    go ACTIVE via any of the SGPs
> in
> > SG before AS can go
> >                    ACTIVE on SG.
> >
> >
> > 2. AS in override mode : Suppose an application
> > server is being served by
> > all
> >                    4 ASPs in override mode. Does
> > this mean that,
> >
> >                    at any given time, each SGP
> will
> > have at the most one
> >                    ASP
> >                    ACTIVE for an AS
> >                                       OR
> >                    at any given time, an SG
> > (combining all SGPs) will have
> > at
> >                    the most one ASP ACTIVE for an
> AS
> >
> >
> > Umesh Vats
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> >  https://www1.ietf.org/mailman/listinfo/sigtran
> >
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Calendar - Free online calendar with sync to
> Outlook(TM).
>
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
 https://www1.ietf.org/mailman/listinfo/sigtran


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



From mailnull@www1.ietf.org  Thu Jun  5 10:20:13 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27828
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Jun 2003 10:20:13 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h55EJmD07986
	for sigtran-archive@odin.ietf.org; Thu, 5 Jun 2003 10:19:48 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55EJVB07972;
	Thu, 5 Jun 2003 10:19:32 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55EAYB07550
	for <sigtran@optimus.ietf.org>; Thu, 5 Jun 2003 10:10:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26970
	for <sigtran@ietf.org>; Thu, 5 Jun 2003 10:10:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NvPy-0007FQ-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 10:08:38 -0400
Received: from web12805.mail.yahoo.com ([216.136.174.40])
	by ietf-mx with smtp (Exim 4.12)
	id 19NvPx-0007FN-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 10:08:37 -0400
Message-ID: <20030605141028.91777.qmail@web12805.mail.yahoo.com>
Received: from [208.255.120.2] by web12805.mail.yahoo.com via HTTP; Thu, 05 Jun 2003 07:10:28 PDT
Date: Thu, 5 Jun 2003 07:10:28 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
To: sigtran@ietf.org
In-Reply-To: <OF57D5A76E.AF87B607-ON65256D3C.00475459@hss.hns.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Hi Kamesh,

IMO, it is a fair assumption for most of the cases
that processing power for SG-side hosts is higher than
of a single ASP (of course, still a configuration
issue)

For loadsharing on SG-side, for incoming traffic from
SS7 there is already loadsharing among links, and
links are residing on different hosts. So, I would
think incoming traffic will be more or less evenly
distributed among different hosts (and probably you
will first try the local SGP on that host to route the
traffic to ASPs, but still implementation dependent).

   Tolga
--- kakaul@hss.hns.com wrote:
> 
> 
> 
> 
> Hi Tolga,
>                      I want to clarify one more
> point that in n+k
> redundancy mode we are saying that n ASP's should be
> active in SGP for the
> AS to handle AS traffic, but can you tell me are we
> assuming that SGP
> handling entire traffic of AS is an high processing
> machine with
> processing power of 3 ASP's.I think it is slightly
> unfair on SGP. We can
> also distribute traffic for AS among SGP's of SG
> which has active
> associations with three ASP's and allow
> implementations to load share
> traffic of AS not only among ASP's (of AS) but
> within SGP's of SG too.
> 
> Regards
> Kamesh
> 
> 
> 
> 
> Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org on
> 06/05/2003 05:53:51 PM
> 
> Sent by:    sigtran-admin@ietf.org
> 
> 
> To:    sigtran@ietf.org
> cc:
> 
> Subject:    Re: [Sigtran] M3UA : Multiple SGPs in SG
> 
> 
> Hi Kamesh,
> 
> 
>              associations
>     | | | |    | | | |      | | | |
>    +---------+------------+-----------+
>    |   SGP1  |   SGP2     |   SGP3    |
>    ************************************
>    *              MTP3                *
>    *         |            |           *
>    * host1   |   host2    |  host3    *
>    ************************************
>      |   |       |     |       |    |
>      |   |       |     |       |    |
>                 Links
> 
> 
> Basically adjacent SS7 node is just aware that there
> is a MTP3 peer and some links to communicate with
> it,
> and will probably loadshare traffic based on SLS
> betwen those links. Once the messages are inside the
> SG-box, it is up to you, what to do with them (and I
> would think although a lot of things inside SG are
> implementation dependent, there is no direct mapping
> between links and SGPs)
> 
> BTW, like you have said, it really migt be possible
> to
> loadshare traffic between two ASPs, which are ACTIVE
> for separate SGPs -and this also IMO would qualify
> as
> 2 ACTIVE ASPs because this is not two associations
> to
> the same ASP-, but I still think this might bring
> interoperability problems. To decide, when to start
> traffic, IMO ASP and SGP should work in harmony. So,
> IMO it is a good choice to leave the peers as SGP
> and
> ASP for ASPTM procedures.
> 
> I also checked a sentence related with this topic
> -in
> ASP Active Procedures- in RFC, there it stands that
> "ASPs should coordinate the number of ACTIVE ASPs
> for
> the AS", I think this may be clarified as "the
> number
> of ACTIVE ASPs for the AS for a specific SGP".
> 
>    Tolga
> 
> 
> --- kakaul@hss.hns.com wrote:
> >
> >
> >
> >
> > Tolga,
> >    Can you clearly show with figure how an SS7
> node
> > adjacent to SG would
> > route traffic for AS in this scenario, clearly
> > showing signalling links
> > used by adjacent SS7 node and mapping of these
> links
> > to SGP's of SG.
> >
> > Regards
> > Kamesh
> >
> >
> >
> >
> >
> > Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org
> on
> > 06/05/2003 04:34:06 PM
> >
> > Sent by:    sigtran-admin@ietf.org
> >
> >
> > To:    sigtran@ietf.org
> > cc:
> >
> > Subject:    Re: [Sigtran] M3UA : Multiple SGPs in
> SG
> >
> >
> > Kamesh,
> >
> > Some comments below, just my 2 cents.
> >
> >   Tolga
> > --- kakaul@hss.hns.com wrote:
> > >
> > >
> > >
> > >
> > > Umesh some comments
> > >
> > > It all depends on how SG is implemented.If SS7
> > node
> > > adjacent to SG is
> > > routing traffic to SGP without making any
> > > assumptions of inter SGP routing
> > > then routing of traffic to AS ultimately depends
> > on
> > > the number of active
> > > associations capable of handling traffic for AS
> > > corresponding to SGP.In
> > > this case scope of n+k redundancy is valid
> > > corresponding to SGP i.e number
> > > of active associations of ASP's (of AS) with
> > single
> > > SGP(of SG), which
> > > should be n to handle traffic for AS. For this
> > > scenario your ORD options
> > [TOLGA]A SG is seen from SS7 point of view as a
> > single
> > entity. A node in SS7 domain is not aware of the
> > concept of SGs and SGPs. BTW, important is the
> > number
> > of ACTIVE ASPs to handle the traffic, not the
> number
> > of associations to an ACTIVE ASP. So, I wouldn't
> > think
> > that it will increase the performance of an ASP,
> if
> > you have 3 -instead of 1- association to the same
> > ASP.
> > > are valid for both the points.Now if SS7 node
> > > adjacent to SG is routing
> > > traffic to SGP without caring whether the
> traffic
> > > for AS is ultimately
> > > routed through active associations of ASP's (of
> > AS)
> > > with SGP1 or SGP2 or
> > > SGP3 which may involve inter SGP routing then
> > scope
> > > of n+k redundancy is
> > > valid corresponding to SG i.e number of active
> > > associations of ASP's (of
> > > AS) with any SGP in the SG.For this scenario
> first
> > > options of your two
> > > points are appropriate. Ultimately it all
> depends
> > on
> > > how you view and
> > > implement SG.
> > [TOLGA]IMO it is clear that for n+k situation,
> both
> > ASP and SGP should behave the same, otherwise it
> > might
> > bring interoperability problems that SG tries to
> > activate traffic based on the SGwide number of
> > ACTIVE
> > ASPs, and ASP kepps the counter per SGP. ASPTM is
> > sent
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jun  5 10:56:16 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29199
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Jun 2003 10:56:15 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h55EtpI10875
	for sigtran-archive@odin.ietf.org; Thu, 5 Jun 2003 10:55:51 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55EtYB10847;
	Thu, 5 Jun 2003 10:55:34 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55EoDB10488
	for <sigtran@optimus.ietf.org>; Thu, 5 Jun 2003 10:50:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29019
	for <sigtran@ietf.org>; Thu, 5 Jun 2003 10:50:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nw2K-0007YU-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 10:48:16 -0400
Received: from web41802.mail.yahoo.com ([66.218.93.136])
	by ietf-mx with smtp (Exim 4.12)
	id 19Nw2I-0007Y6-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 10:48:15 -0400
Message-ID: <20030605144935.15728.qmail@web41802.mail.yahoo.com>
Received: from [65.198.40.51] by web41802.mail.yahoo.com via HTTP; Thu, 05 Jun 2003 09:49:35 CDT
Date: Thu, 5 Jun 2003 09:49:35 -0500 (CDT)
From: =?iso-8859-1?q?Pablo=20Salinas?= <pablopesb@yahoo.com>
To: sigtran@ietf.org
Cc: miguel.willigs@conexion.com.py
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Sigtran] M2UA over SCTP && Error Message
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Hi there,

Question 1:
         I am having a little problem to understand
how the SCTP associations work for M2UA. In RFC 3331,
page 6, says: "The SCTP and TCP Registered User Port
Number Assignment for M2UA is 2094".
Does it mean that all incoming sctp associations
request should be sent to that port number?
And, supossing I am using the UDP-like SCTP library,
the RSG can use a different port number to manage
further messages from this ASP using the accept()
call?
Could anyone send me a message secuence scheme to
stablish the conexion betwen the M2UA layers
across the port SCTP 2905?

Question 2:
          I want to understand the ERROR Message
structure. In RFC 3331, the ERR message structure is
displayed, and in the Interface Identifiers Field, it
says that it could have Tags: 0x1, 0x3 "OR" 0x8.
Does it mean that only one of the Tags is supported?
Or could it have a structure like ASP ACTIVE messages
have?

              greetings people,
                             Pablo Salinas


_________________________________________________________
Do You Yahoo!?
Información de Estados Unidos y América Latina, en Yahoo! Noticias.
Visítanos en http://noticias.espanol.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jun  5 11:07:54 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00509
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Jun 2003 11:07:54 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h55F7Ul12247
	for sigtran-archive@odin.ietf.org; Thu, 5 Jun 2003 11:07:30 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55F7CB11866;
	Thu, 5 Jun 2003 11:07:12 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55F4bB11559
	for <sigtran@optimus.ietf.org>; Thu, 5 Jun 2003 11:04:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29655
	for <sigtran@ietf.org>; Thu, 5 Jun 2003 11:04:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NwGF-0007go-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 11:02:39 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NwGE-0007gc-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 11:02:38 -0400
Received: from alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h55F3xB3028641;
	Thu, 5 Jun 2003 10:03:59 -0500 (CDT)
Message-ID: <3EDF5BDF.49C100E2@alcatel.com>
Date: Thu, 05 Jun 2003 10:03:59 -0500
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
CC: sigtran@ietf.org
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
References: <20030604122259.C25664@openss7.org> <20030604183906.12293.qmail@web12805.mail.yahoo.com> <20030604131242.E25664@openss7.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

There may be a problem with sending LS PR on the Data stream. The
receiver has been queueing messages from stream 1 because of the RPO
condition. If the LS PR is sent on stream 1, it will be in the queue
behind those User Data messages. How will the receiver know that he has
received the LS PR message?

tomG.

"Brian F. G. Bidulock" wrote:
> 
> Tolga,
> 
> Ok.  Add a paragraph somewhere that says:
> 
> LSPR, LSBE, LSA SHOULD be sent on stream 1.  All other
> LS messages SHOULD be sent on stream 0.
> 
> Done.
> 
> --brian
  [...]

-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
* I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
* to advertise or represent its position,  operations, or activities. *
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jun  5 11:52:20 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04329
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Jun 2003 11:52:19 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h55FpqY16237
	for sigtran-archive@odin.ietf.org; Thu, 5 Jun 2003 11:51:52 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55FpYB16223;
	Thu, 5 Jun 2003 11:51:34 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55FmBB16055
	for <sigtran@optimus.ietf.org>; Thu, 5 Jun 2003 11:48:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04208
	for <sigtran@ietf.org>; Thu, 5 Jun 2003 11:48:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NwwT-0000ZH-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 11:46:17 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[ea35/Trka5/kPRxuxtXuno9YBtCLIZAZ])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NwwS-0000ZE-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 11:46:17 -0400
Received: from ns.pigworks.openss7.net (IDENT:p4VGygingkBBt5tQNHpp6dFEtUeog/7z@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h55Fm7F14879;
	Thu, 5 Jun 2003 09:48:07 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h55Fm7811863;
	Thu, 5 Jun 2003 09:48:07 -0600
Date: Thu, 5 Jun 2003 09:48:07 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tom George <Tom.George@alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
Message-ID: <20030605094807.A11650@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tom George <Tom.George@alcatel.com>, sigtran@ietf.org
References: <20030604122259.C25664@openss7.org> <20030604183906.12293.qmail@web12805.mail.yahoo.com> <20030604131242.E25664@openss7.org> <3EDF5BDF.49C100E2@alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <3EDF5BDF.49C100E2@alcatel.com>; from Tom.George@alcatel.com on Thu, Jun 05, 2003 at 10:03:59AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tom,

What do you mean queueing?  Where? In the network? In SCTP?  In M2PA?
If in the network, the network is broken and the SCTP association will fail
anyway.  If in SCTP, M2PA is broken and should service it's receive buffer
better.  If in M2PA, M2PA is broken and should process LS as they arrive
and not wait on data.

Are you trying to say that M2PA stops servicing its receive buffer when
LSPO is received?  I don't think so.  That was one of the reasons we put
sequence numbers and acknowledgments in: so that SCTP could ack the message
without M2PA acking the message. M2PA should continue to service its receive
buffer but queue messages without acknowledging them.  The moment the LSPR
arrives, it can ack bufferred messages (unless it has latching of RPO to
LPO, in which case it waits for Continue or Flush from MTP3).

Could you explain the problem more?

--brian

Tom George wrote:                                                                      (Thu, 05 Jun 2003 10:03:59)
> There may be a problem with sending LS PR on the Data stream. The
> receiver has been queueing messages from stream 1 because of the RPO
> condition. If the LS PR is sent on stream 1, it will be in the queue
> behind those User Data messages. How will the receiver know that he has
> received the LS PR message?
> 
> tomG.
> 
> "Brian F. G. Bidulock" wrote:
> > 
> > Tolga,
> > 
> > Ok.  Add a paragraph somewhere that says:
> > 
> > LSPR, LSBE, LSA SHOULD be sent on stream 1.  All other
> > LS messages SHOULD be sent on stream 0.
> > 
> > Done.
> > 
> > --brian
>   [...]
> 
> -- 
> * Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
> * 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
> * Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
> * I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
> * to advertise or represent its position,  operations, or activities. *
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jun  5 18:46:21 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21235
	for <sigtran-archive@odin.ietf.org>; Thu, 5 Jun 2003 18:46:21 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h55Mjv918088
	for sigtran-archive@odin.ietf.org; Thu, 5 Jun 2003 18:45:57 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55MjeB18073;
	Thu, 5 Jun 2003 18:45:42 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55MgXB17978
	for <sigtran@optimus.ietf.org>; Thu, 5 Jun 2003 18:42:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21175
	for <sigtran@ietf.org>; Thu, 5 Jun 2003 18:42:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19O3PP-0004Je-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 18:40:35 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19O3PO-0004Ja-00
	for sigtran@ietf.org; Thu, 05 Jun 2003 18:40:35 -0400
Received: from alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h55MfuB3022711;
	Thu, 5 Jun 2003 17:41:56 -0500 (CDT)
Message-ID: <3EDFC733.D6C2510F@alcatel.com>
Date: Thu, 05 Jun 2003 17:41:55 -0500
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
CC: sigtran@ietf.org
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
References: <20030604122259.C25664@openss7.org> <20030604183906.12293.qmail@web12805.mail.yahoo.com> <20030604131242.E25664@openss7.org> <3EDF5BDF.49C100E2@alcatel.com> <20030605094807.A11650@openss7.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Good point. I confess I was thinking that M2PA could stop servicing the
receive buffer when there is an RPO. Not a good idea. Besides what you
said, M2PA needs to keep looking at incoming messages because some of
them might be empty User Data messages to ack previously sent messages. 

OK, I will keep thinking....

tomG.

"Brian F. G. Bidulock" wrote:
> 
> Tom,
> 
> What do you mean queueing?  Where? In the network? In SCTP?  In M2PA?
> If in the network, the network is broken and the SCTP association will fail
> anyway.  If in SCTP, M2PA is broken and should service it's receive buffer
> better.  If in M2PA, M2PA is broken and should process LS as they arrive
> and not wait on data.
> 
> Are you trying to say that M2PA stops servicing its receive buffer when
> LSPO is received?  I don't think so.  That was one of the reasons we put
> sequence numbers and acknowledgments in: so that SCTP could ack the message
> without M2PA acking the message. M2PA should continue to service its receive
> buffer but queue messages without acknowledging them.  The moment the LSPR
> arrives, it can ack bufferred messages (unless it has latching of RPO to
> LPO, in which case it waits for Continue or Flush from MTP3).
> 
> Could you explain the problem more?
> 
> --brian
> 
> Tom George wrote:                                                                      (Thu, 05 Jun 2003 10:03:59)
> > There may be a problem with sending LS PR on the Data stream. The
> > receiver has been queueing messages from stream 1 because of the RPO
> > condition. If the LS PR is sent on stream 1, it will be in the queue
> > behind those User Data messages. How will the receiver know that he has
> > received the LS PR message?
> >
> > tomG.
> >
> > "Brian F. G. Bidulock" wrote:
> > >
> > > Tolga,
> > >
> > > Ok.  Add a paragraph somewhere that says:
> > >
> > > LSPR, LSBE, LSA SHOULD be sent on stream 1.  All other
> > > LS messages SHOULD be sent on stream 0.
> > >
> > > Done.
> > >
> > > --brian
> >   [...]
> >
> > --
> > * Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
> > * 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
> > * Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
> > * I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
> > * to advertise or represent its position,  operations, or activities. *
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
* I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
* to advertise or represent its position,  operations, or activities. *
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 00:29:18 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28166
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 00:29:17 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h564SpA08069
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 00:28:51 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h564SVB08057;
	Fri, 6 Jun 2003 00:28:33 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h564PVB07953
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 00:25:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28092
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 00:25:27 -0400 (EDT)
From: kakaul@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19O8lM-00064R-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 00:23:36 -0400
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf-mx with esmtp (Exim 4.12)
	id 19O8lK-00064F-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 00:23:34 -0400
Received: from hindon.hss.co.in (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h564MPE28382
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 09:52:26 +0530 (IST)
Received: from ultra.hss.co.in (ultra [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h564MJ928358;
	Fri, 6 Jun 2003 09:52:20 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h564PjU26019;
	Fri, 6 Jun 2003 09:55:45 +0530 (IST)
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF249E38BE.F3DB01DC-ON65256D3D.00145E63@hss.hns.com>
Date: Fri, 6 Jun 2003 09:56:14 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 06/06/2003
 09:49:53 AM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>





Hi Tolga,
                    I am of the openion that scope of n+k redundancy should
depend on how one views and implements an SG. In figure given below if an
implementation wants to reroute some AS traffic to its adjacent SGP on its
way to AS it should be allowed.BTW as you have also agreed that ASP1 and
ASP2 also qualifies as two ASP's of AS if SGP1 and SGP2 has active
associations with ASP1 and ASP2 respectively.SGP may not want to block the
traffic for AS if association between SGP1 and ASP2 is not active for AS
assuming n = 2, k = 0(for n+k redundancy). I am not able to understand what
interopability issue will be involved in it.No doubt limiting scope of n+k
redundancy to SGP is clear and simple but some implementations may want to
use inter SGP routing to route there traffic to AS. So it ultimately
depends on how you want your SG implementation to behave.


                      SG
                  +--------------+            AS
                  |              |        +---------+--+
                  |              |        |            |
                  | +--------+   |        |+--------+  |
                  | |        |   |        ||        |  |
                  | |  SGP1  *---+--------++ ASP1   |  |
                  | +--------+\  |        |+--------+  |
                  |    |         \        |            |
  inter SGP  -----+----+         |        |            |
  routing         |    |         |   \    |            |
                  | +--------+   |     \  |+--------+  |
                  | |        |   |       \||        |  |
                  | | SGP2   +---+------ -*+  ASP2  |  |
                  | +--------+   |        |+--------+  |
                  |              |        |            |
                  +--------------+        +------------+

Regards
Kamesh
Hughes Software Systems




Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org on 06/05/2003 07:40:28 PM

Sent by:    sigtran-admin@ietf.org


To:    sigtran@ietf.org
cc:

Subject:    Re: [Sigtran] M3UA : Multiple SGPs in SG


Hi Kamesh,

IMO, it is a fair assumption for most of the cases
that processing power for SG-side hosts is higher than
of a single ASP (of course, still a configuration
issue)

For loadsharing on SG-side, for incoming traffic from
SS7 there is already loadsharing among links, and
links are residing on different hosts. So, I would
think incoming traffic will be more or less evenly
distributed among different hosts (and probably you
will first try the local SGP on that host to route the
traffic to ASPs, but still implementation dependent).

   Tolga
--- kakaul@hss.hns.com wrote:
>
>
>
>
> Hi Tolga,
>                      I want to clarify one more
> point that in n+k
> redundancy mode we are saying that n ASP's should be
> active in SGP for the
> AS to handle AS traffic, but can you tell me are we
> assuming that SGP
> handling entire traffic of AS is an high processing
> machine with
> processing power of 3 ASP's.I think it is slightly
> unfair on SGP. We can
> also distribute traffic for AS among SGP's of SG
> which has active
> associations with three ASP's and allow
> implementations to load share
> traffic of AS not only among ASP's (of AS) but
> within SGP's of SG too.
>
> Regards
> Kamesh
>
>
>
>
> Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org on
> 06/05/2003 05:53:51 PM
>
> Sent by:    sigtran-admin@ietf.org
>
>
> To:    sigtran@ietf.org
> cc:
>
> Subject:    Re: [Sigtran] M3UA : Multiple SGPs in SG
>
>
> Hi Kamesh,
>
>
>              associations
>     | | | |    | | | |      | | | |
>    +---------+------------+-----------+
>    |   SGP1  |   SGP2     |   SGP3    |
>    ************************************
>    *              MTP3                *
>    *         |            |           *
>    * host1   |   host2    |  host3    *
>    ************************************
>      |   |       |     |       |    |
>      |   |       |     |       |    |
>                 Links
>
>
> Basically adjacent SS7 node is just aware that there
> is a MTP3 peer and some links to communicate with
> it,
> and will probably loadshare traffic based on SLS
> betwen those links. Once the messages are inside the
> SG-box, it is up to you, what to do with them (and I
> would think although a lot of things inside SG are
> implementation dependent, there is no direct mapping
> between links and SGPs)
>
> BTW, like you have said, it really migt be possible
> to
> loadshare traffic between two ASPs, which are ACTIVE
> for separate SGPs -and this also IMO would qualify
> as
> 2 ACTIVE ASPs because this is not two associations
> to
> the same ASP-, but I still think this might bring
> interoperability problems. To decide, when to start
> traffic, IMO ASP and SGP should work in harmony. So,
> IMO it is a good choice to leave the peers as SGP
> and
> ASP for ASPTM procedures.
>
> I also checked a sentence related with this topic
> -in
> ASP Active Procedures- in RFC, there it stands that
> "ASPs should coordinate the number of ACTIVE ASPs
> for
> the AS", I think this may be clarified as "the
> number
> of ACTIVE ASPs for the AS for a specific SGP".
>
>    Tolga
>
>
> --- kakaul@hss.hns.com wrote:
> >
> >
> >
> >
> > Tolga,
> >    Can you clearly show with figure how an SS7
> node
> > adjacent to SG would
> > route traffic for AS in this scenario, clearly
> > showing signalling links
> > used by adjacent SS7 node and mapping of these
> links
> > to SGP's of SG.
> >
> > Regards
> > Kamesh
> >
> >
> >
> >
> >
> > Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org
> on
> > 06/05/2003 04:34:06 PM
> >
> > Sent by:    sigtran-admin@ietf.org
> >
> >
> > To:    sigtran@ietf.org
> > cc:
> >
> > Subject:    Re: [Sigtran] M3UA : Multiple SGPs in
> SG
> >
> >
> > Kamesh,
> >
> > Some comments below, just my 2 cents.
> >
> >   Tolga
> > --- kakaul@hss.hns.com wrote:
> > >
> > >
> > >
> > >
> > > Umesh some comments
> > >
> > > It all depends on how SG is implemented.If SS7
> > node
> > > adjacent to SG is
> > > routing traffic to SGP without making any
> > > assumptions of inter SGP routing
> > > then routing of traffic to AS ultimately depends
> > on
> > > the number of active
> > > associations capable of handling traffic for AS
> > > corresponding to SGP.In
> > > this case scope of n+k redundancy is valid
> > > corresponding to SGP i.e number
> > > of active associations of ASP's (of AS) with
> > single
> > > SGP(of SG), which
> > > should be n to handle traffic for AS. For this
> > > scenario your ORD options
> > [TOLGA]A SG is seen from SS7 point of view as a
> > single
> > entity. A node in SS7 domain is not aware of the
> > concept of SGs and SGPs. BTW, important is the
> > number
> > of ACTIVE ASPs to handle the traffic, not the
> number
> > of associations to an ACTIVE ASP. So, I wouldn't
> > think
> > that it will increase the performance of an ASP,
> if
> > you have 3 -instead of 1- association to the same
> > ASP.
> > > are valid for both the points.Now if SS7 node
> > > adjacent to SG is routing
> > > traffic to SGP without caring whether the
> traffic
> > > for AS is ultimately
> > > routed through active associations of ASP's (of
> > AS)
> > > with SGP1 or SGP2 or
> > > SGP3 which may involve inter SGP routing then
> > scope
> > > of n+k redundancy is
> > > valid corresponding to SG i.e number of active
> > > associations of ASP's (of
> > > AS) with any SGP in the SG.For this scenario
> first
> > > options of your two
> > > points are appropriate. Ultimately it all
> depends
> > on
> > > how you view and
> > > implement SG.
> > [TOLGA]IMO it is clear that for n+k situation,
> both
> > ASP and SGP should behave the same, otherwise it
> > might
> > bring interoperability problems that SG tries to
> > activate traffic based on the SGwide number of
> > ACTIVE
> > ASPs, and ASP kepps the counter per SGP. ASPTM is
> > sent
>
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
 https://www1.ietf.org/mailman/listinfo/sigtran


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



From mailnull@www1.ietf.org  Fri Jun  6 07:10:03 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17819
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 07:10:03 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56B9eL13647
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 07:09:40 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56B9MB13598;
	Fri, 6 Jun 2003 07:09:23 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56B5BB12534
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 07:05:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17557
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 07:05:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OF04-0000ay-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 07:03:12 -0400
Received: from web12809.mail.yahoo.com ([216.136.174.136])
	by ietf-mx with smtp (Exim 4.12)
	id 19OF03-0000at-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 07:03:11 -0400
Message-ID: <20030606110503.74344.qmail@web12809.mail.yahoo.com>
Received: from [208.255.120.2] by web12809.mail.yahoo.com via HTTP; Fri, 06 Jun 2003 04:05:03 PDT
Date: Fri, 6 Jun 2003 04:05:03 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
To: sigtran@ietf.org
In-Reply-To: <OF249E38BE.F3DB01DC-ON65256D3D.00145E63@hss.hns.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Hi Kamesh,

If we have to types of SGs (one, which activates
traffic based on number of ACTIVE ASPs per SGP and the
other per SG), ASPs can't decide -at least based on
the current RFC- when to start/accept traffic. What
ASPs are supposed to do is coordinating number of
ACTIVE ASPs among the cluster, but if they don't know,
whether the SG is deciding based on per SGP counter or
not, there will be interoperability problems (for
example SG uses a global ACTIVE ASP counter and starts
traffic but ASPs are counting per SGP, they probably
will drop arriving DATA). 

    Tolga
--- kakaul@hss.hns.com wrote:
> 
> 
> 
> 
> Hi Tolga,
>                     I am of the openion that scope
> of n+k redundancy should
> depend on how one views and implements an SG. In
> figure given below if an
> implementation wants to reroute some AS traffic to
> its adjacent SGP on its
> way to AS it should be allowed.BTW as you have also
> agreed that ASP1 and
> ASP2 also qualifies as two ASP's of AS if SGP1 and
> SGP2 has active
> associations with ASP1 and ASP2 respectively.SGP may
> not want to block the
> traffic for AS if association between SGP1 and ASP2
> is not active for AS
> assuming n = 2, k = 0(for n+k redundancy). I am not
> able to understand what
> interopability issue will be involved in it.No doubt
> limiting scope of n+k
> redundancy to SGP is clear and simple but some
> implementations may want to
> use inter SGP routing to route there traffic to AS.
> So it ultimately
> depends on how you want your SG implementation to
> behave.
> 
> 
>                       SG
>                   +--------------+            AS
>                   |              |       
> +---------+--+
>                   |              |        |         
>   |
>                   | +--------+   |       
> |+--------+  |
>                   | |        |   |        ||       
> |  |
>                   | |  SGP1  *---+--------++ ASP1  
> |  |
>                   | +--------+\  |       
> |+--------+  |
>                   |    |         \        |         
>   |
>   inter SGP  -----+----+         |        |         
>   |
>   routing         |    |         |   \    |         
>   |
>                   | +--------+   |     \ 
> |+--------+  |
>                   | |        |   |       \||       
> |  |
>                   | | SGP2   +---+------ -*+  ASP2 
> |  |
>                   | +--------+   |       
> |+--------+  |
>                   |              |        |         
>   |
>                   +--------------+       
> +------------+
> 
> Regards
> Kamesh
> Hughes Software Systems
> 
> 
> 
> 
> Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org on
> 06/05/2003 07:40:28 PM
> 
> Sent by:    sigtran-admin@ietf.org
> 
> 
> To:    sigtran@ietf.org
> cc:
> 
> Subject:    Re: [Sigtran] M3UA : Multiple SGPs in SG
> 
> 
> Hi Kamesh,
> 
> IMO, it is a fair assumption for most of the cases
> that processing power for SG-side hosts is higher
> than
> of a single ASP (of course, still a configuration
> issue)
> 
> For loadsharing on SG-side, for incoming traffic
> from
> SS7 there is already loadsharing among links, and
> links are residing on different hosts. So, I would
> think incoming traffic will be more or less evenly
> distributed among different hosts (and probably you
> will first try the local SGP on that host to route
> the
> traffic to ASPs, but still implementation
> dependent).
> 
>    Tolga
> --- kakaul@hss.hns.com wrote:
> >
> >
> >
> >
> > Hi Tolga,
> >                      I want to clarify one more
> > point that in n+k
> > redundancy mode we are saying that n ASP's should
> be
> > active in SGP for the
> > AS to handle AS traffic, but can you tell me are
> we
> > assuming that SGP
> > handling entire traffic of AS is an high
> processing
> > machine with
> > processing power of 3 ASP's.I think it is slightly
> > unfair on SGP. We can
> > also distribute traffic for AS among SGP's of SG
> > which has active
> > associations with three ASP's and allow
> > implementations to load share
> > traffic of AS not only among ASP's (of AS) but
> > within SGP's of SG too.
> >
> > Regards
> > Kamesh
> >
> >
> >
> >
> > Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org
> on
> > 06/05/2003 05:53:51 PM
> >
> > Sent by:    sigtran-admin@ietf.org
> >
> >
> > To:    sigtran@ietf.org
> > cc:
> >
> > Subject:    Re: [Sigtran] M3UA : Multiple SGPs in
> SG
> >
> >
> > Hi Kamesh,
> >
> >
> >              associations
> >     | | | |    | | | |      | | | |
> >    +---------+------------+-----------+
> >    |   SGP1  |   SGP2     |   SGP3    |
> >    ************************************
> >    *              MTP3                *
> >    *         |            |           *
> >    * host1   |   host2    |  host3    *
> >    ************************************
> >      |   |       |     |       |    |
> >      |   |       |     |       |    |
> >                 Links
> >
> >
> > Basically adjacent SS7 node is just aware that
> there
> > is a MTP3 peer and some links to communicate with
> > it,
> > and will probably loadshare traffic based on SLS
> > betwen those links. Once the messages are inside
> the
> > SG-box, it is up to you, what to do with them (and
> I
> > would think although a lot of things inside SG are
> > implementation dependent, there is no direct
> mapping
> > between links and SGPs)
> >
> > BTW, like you have said, it really migt be
> possible
> > to
> > loadshare traffic between two ASPs, which are
> ACTIVE
> > for separate SGPs -and this also IMO would qualify
> > as
> > 2 ACTIVE ASPs because this is not two associations
> > to
> > the same ASP-, but I still think this might bring
> > interoperability problems. To decide, when to
> start
> > traffic, IMO ASP and SGP should work in harmony.
> So,
> > IMO it is a good choice to leave the peers as SGP
> > and
> > ASP for ASPTM procedures.
> >
> > I also checked a sentence related with this topic
> > -in
> > ASP Active Procedures- in RFC, there it stands
> that
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 09:50:36 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23478
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 09:50:36 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56DoBB24961
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 09:50:11 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56DnmB24920;
	Fri, 6 Jun 2003 09:49:48 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56DitB24707
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 09:44:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23303
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 09:44:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OHUf-0002Ag-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 09:42:57 -0400
Received: from email10.etsi.org ([212.234.161.112] helo=email10.etsihq.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OHUf-0002AX-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 09:42:57 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Fri, 6 Jun 2003 15:44:20 +0200
Message-ID: <4091553999CBE4409CC2B562152B5A33019C861C@email10.etsihq.org>
Thread-Topic: pre-information on SIGTRAN interoperability event (bake-off) organised by ETSI 1-5 September 2003, Sophia antipolis
Thread-Index: AcMsMbsFl+9yQ6EDSX+u7GiGVb2+QQ==
From: =?iso-8859-1?Q?S=E9bastien_Flaux?= <Sebastien.Flaux@etsi.org>
To: <sigtran@ietf.org>
Cc: "Philippe Cousin" <Philippe.Cousin@etsi.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h56DitB24708
Subject: [Sigtran] pre-information on SIGTRAN interoperability event (bake-off) organised by ETSI 1-5 September 2003, Sophia antipolis
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

On behalf of Philippe COUSIN :

Dear all,

I herewith confirmed that ETSI will organised a SIGTRAN bake-off on 1-5 September at Sophia Antipolis.
The technical programme will focus on M3UA, SUA, IUA, M2PA and M2UA.

We welcome you to attend it and please book already your agenda and your flight ticket to Nice.

We are working on the technical side as well as on the online registration which will be hopefully open end of next week.
I will inform you as soon as registration ready.

Look forward meeting you on September

kind regards
Philippe

Philippe COUSIN
Interoperability Service Manager
Tel: + 33 (0)4 92 94 4306
Fax: +33 (0)4 92 38 5248
http://www.etsi.org/plugtests/

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



From mailnull@www1.ietf.org  Fri Jun  6 11:01:22 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27364
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 11:01:21 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56F0wr30571
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 11:00:58 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56F0cB30542;
	Fri, 6 Jun 2003 11:00:39 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56CntB20430
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 08:49:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21375
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 08:49:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OGdT-0001cU-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 08:47:59 -0400
Received: from email10.etsi.org ([212.234.161.112] helo=email10.etsihq.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OGdS-0001aQ-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 08:47:58 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Fri, 6 Jun 2003 14:49:18 +0200
Message-ID: <4091553999CBE4409CC2B562152B5A3301CFE6C7@email10.etsihq.org>
Thread-Topic: pre-information on SIGTRAN interoperability event (bake-off) organised by ETSI 1-5 September 2003, Sophia antipolis
Thread-Index: AcMsKgtk4GH3hBdsSD6NdSXACKy6IQ==
From: "Philippe Cousin" <Philippe.Cousin@etsi.org>
To: <sigtran@ietf.org>
Cc: "Ken Morneault" <kmorneau@cisco.com>,
        "Garnero, Pierre" <Pierre.Garnero@hp.com>,
        "Michael Tuexen" <Michael.Tuexen@micmac.franken.de>, <LyOng@ciena.com>,
        "Anthony Wiles" <Anthony.Wiles@etsi.org>,
        =?iso-8859-1?Q?Patrick_Ren=E9_Guillemin?= <Patrick.Guillemin@etsi.org>,
        "Sabine Beauvois" <Sabine.Beauvois@etsi.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h56CnuB20431
Subject: [Sigtran] pre-information on SIGTRAN interoperability event (bake-off) organised by ETSI 1-5 September 2003, Sophia antipolis
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Dear all,

I herewith confirmed that ETSI will organised a SIGTRAN bake-off on 1-5 September at Sophia Antipolis.
The technical programme will focus on M3UA, SUA, IUA, M2PA and M2UA.

We welcome you to attend it and please book already your agenda and your flight ticket to Nice.

We are working on the technical side as well as on the online registration which will be hopefully open end of next week.
I will inform you as soon as registration ready.

Look forward meeting you on September

kind regards
Philippe

Philippe COUSIN
Interoperability Service Manager
Tel: + 33 (0)4 92 94 4306
Fax: +33 (0)4 92 38 5248
http://www.etsi.org/plugtests/

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



From mailnull@www1.ietf.org  Fri Jun  6 11:31:42 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28700
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 11:31:42 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56FVEv01189
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 11:31:14 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56FUuB01106;
	Fri, 6 Jun 2003 11:30:56 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56FSUB00990
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 11:28:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28574
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 11:28:27 -0400 (EDT)
From: kakaul@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OJ6w-00037e-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 11:26:34 -0400
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OJ6v-00037C-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 11:26:33 -0400
Received: from hindon.hss.co.in (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h56FPOF23889
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 20:55:24 +0530 (IST)
Received: from ultra.hss.co.in (ultra [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h56FPJ923881;
	Fri, 6 Jun 2003 20:55:20 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h56FSka19141;
	Fri, 6 Jun 2003 20:58:46 +0530 (IST)
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OFC3E1ED80.CB07A9F9-ON65256D3D.005418AA@hss.hns.com>
Date: Fri, 6 Jun 2003 20:59:14 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 06/06/2003
 08:52:53 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>





Hi Tolga,

 RFC does not say any thing about n+k redundancy as you have pointed out in
your first response. I am
 attaching the lines from RFC from section 4.3.4.3 ASP Active Procedures:
"For the n+k redundancy case, ASPs which are in that AS should
 coordinate among themselves the number of active ASPs in the AS, and
 should start sending traffic only after n ASPs are active.

 All ASPs within a loadsharing mode AS must be able to process any
 Data message received for the AS, to accommodate any potential
 failover or rebalancing of the offered load."

So if there is any interopability problem as you have indicated by keeping
the RFC open ended then it should         be addressed in the
implementation guide.I still believe that it is an implementation issue and
can be resolved by configuring each AS and SG nodes in one of the two ways
of n+k redundancy scope i.e specific to SG or SGP.

Regards
Kamesh




Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org on 06/06/2003 04:35:03 PM

Sent by:    sigtran-admin@ietf.org


To:    sigtran@ietf.org
cc:

Subject:    Re: [Sigtran] M3UA : Multiple SGPs in SG


Hi Kamesh,

If we have to types of SGs (one, which activates
traffic based on number of ACTIVE ASPs per SGP and the
other per SG), ASPs can't decide -at least based on
the current RFC- when to start/accept traffic. What
ASPs are supposed to do is coordinating number of
ACTIVE ASPs among the cluster, but if they don't know,
whether the SG is deciding based on per SGP counter or
not, there will be interoperability problems (for
example SG uses a global ACTIVE ASP counter and starts
traffic but ASPs are counting per SGP, they probably
will drop arriving DATA).

    Tolga
--- kakaul@hss.hns.com wrote:
>
>
>
>
> Hi Tolga,
>                     I am of the openion that scope
> of n+k redundancy should
> depend on how one views and implements an SG. In
> figure given below if an
> implementation wants to reroute some AS traffic to
> its adjacent SGP on its
> way to AS it should be allowed.BTW as you have also
> agreed that ASP1 and
> ASP2 also qualifies as two ASP's of AS if SGP1 and
> SGP2 has active
> associations with ASP1 and ASP2 respectively.SGP may
> not want to block the
> traffic for AS if association between SGP1 and ASP2
> is not active for AS
> assuming n = 2, k = 0(for n+k redundancy). I am not
> able to understand what
> interopability issue will be involved in it.No doubt
> limiting scope of n+k
> redundancy to SGP is clear and simple but some
> implementations may want to
> use inter SGP routing to route there traffic to AS.
> So it ultimately
> depends on how you want your SG implementation to
> behave.
>
>
>                       SG
>                   +--------------+            AS
>                   |              |
> +---------+--+
>                   |              |        |
>   |
>                   | +--------+   |
> |+--------+  |
>                   | |        |   |        ||
> |  |
>                   | |  SGP1  *---+--------++ ASP1
> |  |
>                   | +--------+\  |
> |+--------+  |
>                   |    |         \        |
>   |
>   inter SGP  -----+----+         |        |
>   |
>   routing         |    |         |   \    |
>   |
>                   | +--------+   |     \
> |+--------+  |
>                   | |        |   |       \||
> |  |
>                   | | SGP2   +---+------ -*+  ASP2
> |  |
>                   | +--------+   |
> |+--------+  |
>                   |              |        |
>   |
>                   +--------------+
> +------------+
>
> Regards
> Kamesh
> Hughes Software Systems
>
>
>
>
> Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org on
> 06/05/2003 07:40:28 PM
>
> Sent by:    sigtran-admin@ietf.org
>
>
> To:    sigtran@ietf.org
> cc:
>
> Subject:    Re: [Sigtran] M3UA : Multiple SGPs in SG
>
>
> Hi Kamesh,
>
> IMO, it is a fair assumption for most of the cases
> that processing power for SG-side hosts is higher
> than
> of a single ASP (of course, still a configuration
> issue)
>
> For loadsharing on SG-side, for incoming traffic
> from
> SS7 there is already loadsharing among links, and
> links are residing on different hosts. So, I would
> think incoming traffic will be more or less evenly
> distributed among different hosts (and probably you
> will first try the local SGP on that host to route
> the
> traffic to ASPs, but still implementation
> dependent).
>
>    Tolga
> --- kakaul@hss.hns.com wrote:
> >
> >
> >
> >
> > Hi Tolga,
> >                      I want to clarify one more
> > point that in n+k
> > redundancy mode we are saying that n ASP's should
> be
> > active in SGP for the
> > AS to handle AS traffic, but can you tell me are
> we
> > assuming that SGP
> > handling entire traffic of AS is an high
> processing
> > machine with
> > processing power of 3 ASP's.I think it is slightly
> > unfair on SGP. We can
> > also distribute traffic for AS among SGP's of SG
> > which has active
> > associations with three ASP's and allow
> > implementations to load share
> > traffic of AS not only among ASP's (of AS) but
> > within SGP's of SG too.
> >
> > Regards
> > Kamesh
> >
> >
> >
> >
> > Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org
> on
> > 06/05/2003 05:53:51 PM
> >
> > Sent by:    sigtran-admin@ietf.org
> >
> >
> > To:    sigtran@ietf.org
> > cc:
> >
> > Subject:    Re: [Sigtran] M3UA : Multiple SGPs in
> SG
> >
> >
> > Hi Kamesh,
> >
> >
> >              associations
> >     | | | |    | | | |      | | | |
> >    +---------+------------+-----------+
> >    |   SGP1  |   SGP2     |   SGP3    |
> >    ************************************
> >    *              MTP3                *
> >    *         |            |           *
> >    * host1   |   host2    |  host3    *
> >    ************************************
> >      |   |       |     |       |    |
> >      |   |       |     |       |    |
> >                 Links
> >
> >
> > Basically adjacent SS7 node is just aware that
> there
> > is a MTP3 peer and some links to communicate with
> > it,
> > and will probably loadshare traffic based on SLS
> > betwen those links. Once the messages are inside
> the
> > SG-box, it is up to you, what to do with them (and
> I
> > would think although a lot of things inside SG are
> > implementation dependent, there is no direct
> mapping
> > between links and SGPs)
> >
> > BTW, like you have said, it really migt be
> possible
> > to
> > loadshare traffic between two ASPs, which are
> ACTIVE
> > for separate SGPs -and this also IMO would qualify
> > as
> > 2 ACTIVE ASPs because this is not two associations
> > to
> > the same ASP-, but I still think this might bring
> > interoperability problems. To decide, when to
> start
> > traffic, IMO ASP and SGP should work in harmony.
> So,
> > IMO it is a good choice to leave the peers as SGP
> > and
> > ASP for ASPTM procedures.
> >
> > I also checked a sentence related with this topic
> > -in
> > ASP Active Procedures- in RFC, there it stands
> that
>
=== message truncated ===


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
 https://www1.ietf.org/mailman/listinfo/sigtran


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



From mailnull@www1.ietf.org  Fri Jun  6 12:04:09 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00046
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 12:04:09 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56G3g004116
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 12:03:42 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56G3OB04065;
	Fri, 6 Jun 2003 12:03:25 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56FxIB03738
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 11:59:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29762
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 11:59:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OJak-0003RI-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 11:57:22 -0400
Received: from web12806.mail.yahoo.com ([216.136.174.41])
	by ietf-mx with smtp (Exim 4.12)
	id 19OJaj-0003RF-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 11:57:21 -0400
Message-ID: <20030606155913.37728.qmail@web12806.mail.yahoo.com>
Received: from [208.255.120.2] by web12806.mail.yahoo.com via HTTP; Fri, 06 Jun 2003 08:59:13 PDT
Date: Fri, 6 Jun 2003 08:59:13 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
To: sigtran@ietf.org
In-Reply-To: <OFC3E1ED80.CB07A9F9-ON65256D3D.005418AA@hss.hns.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Hi Kamesh,

In IG 3.15 there are some changes/clarifications
related with n+k redundancy (those most probably will
be reworked but I think we still can rely on
INACTIVE->ACTIVE transition for AS state machine
there-)
In RFC3332 4.3.1 
"The state of each remote ASP, in each AS that it is
configured to operate, is maintained in the M3UA layer
in the SGP."
So, the AS state machine is kept in SGP -not SG wide-
and IG does not change this.

Now, IMO, what you tell -just while counting number of
ACTIVE ASPs for an AS acting SGwide but for the other
ASPTM procedures still keeping per SGP approach- is
not undoable, but not inline with current RFC/IG. 

IMO, cases, where this might be usefull will be
probably very rare (I think, it is not a very high
possibility that an association to an ASP1 can be
formed from SGP1 and can't be formed from SGP2 and for
ASP2 can be formed from SGP2 but can't be formed from
SGP1, if they are part of the same SG) and I would
think introducing a new configuration item for that is
probably not worth. 
Other opinions?

   Tolga 

--- kakaul@hss.hns.com wrote:
> 
> 
> 
> 
> Hi Tolga,
> 
>  RFC does not say any thing about n+k redundancy as
> you have pointed out in
> your first response. I am
>  attaching the lines from RFC from section 4.3.4.3
> ASP Active Procedures:
> "For the n+k redundancy case, ASPs which are in that
> AS should
>  coordinate among themselves the number of active
> ASPs in the AS, and
>  should start sending traffic only after n ASPs are
> active.
> 
>  All ASPs within a loadsharing mode AS must be able
> to process any
>  Data message received for the AS, to accommodate
> any potential
>  failover or rebalancing of the offered load."
> 
> So if there is any interopability problem as you
> have indicated by keeping
> the RFC open ended then it should         be
> addressed in the
> implementation guide.I still believe that it is an
> implementation issue and
> can be resolved by configuring each AS and SG nodes
> in one of the two ways
> of n+k redundancy scope i.e specific to SG or SGP.
> 
> Regards
> Kamesh
> 
> 
> 
> 
> Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org on
> 06/06/2003 04:35:03 PM
> 
> Sent by:    sigtran-admin@ietf.org
> 
> 
> To:    sigtran@ietf.org
> cc:
> 
> Subject:    Re: [Sigtran] M3UA : Multiple SGPs in SG
> 
> 
> Hi Kamesh,
> 
> If we have to types of SGs (one, which activates
> traffic based on number of ACTIVE ASPs per SGP and
> the
> other per SG), ASPs can't decide -at least based on
> the current RFC- when to start/accept traffic. What
> ASPs are supposed to do is coordinating number of
> ACTIVE ASPs among the cluster, but if they don't
> know,
> whether the SG is deciding based on per SGP counter
> or
> not, there will be interoperability problems (for
> example SG uses a global ACTIVE ASP counter and
> starts
> traffic but ASPs are counting per SGP, they probably
> will drop arriving DATA).
> 
>     Tolga
> --- kakaul@hss.hns.com wrote:
> >
> >
> >
> >
> > Hi Tolga,
> >                     I am of the openion that scope
> > of n+k redundancy should
> > depend on how one views and implements an SG. In
> > figure given below if an
> > implementation wants to reroute some AS traffic to
> > its adjacent SGP on its
> > way to AS it should be allowed.BTW as you have
> also
> > agreed that ASP1 and
> > ASP2 also qualifies as two ASP's of AS if SGP1 and
> > SGP2 has active
> > associations with ASP1 and ASP2 respectively.SGP
> may
> > not want to block the
> > traffic for AS if association between SGP1 and
> ASP2
> > is not active for AS
> > assuming n = 2, k = 0(for n+k redundancy). I am
> not
> > able to understand what
> > interopability issue will be involved in it.No
> doubt
> > limiting scope of n+k
> > redundancy to SGP is clear and simple but some
> > implementations may want to
> > use inter SGP routing to route there traffic to
> AS.
> > So it ultimately
> > depends on how you want your SG implementation to
> > behave.
> >
> >
> >                       SG
> >                   +--------------+            AS
> >                   |              |
> > +---------+--+
> >                   |              |        |
> >   |
> >                   | +--------+   |
> > |+--------+  |
> >                   | |        |   |        ||
> > |  |
> >                   | |  SGP1  *---+--------++ ASP1
> > |  |
> >                   | +--------+\  |
> > |+--------+  |
> >                   |    |         \        |
> >   |
> >   inter SGP  -----+----+         |        |
> >   |
> >   routing         |    |         |   \    |
> >   |
> >                   | +--------+   |     \
> > |+--------+  |
> >                   | |        |   |       \||
> > |  |
> >                   | | SGP2   +---+------ -*+  ASP2
> > |  |
> >                   | +--------+   |
> > |+--------+  |
> >                   |              |        |
> >   |
> >                   +--------------+
> > +------------+
> >
> > Regards
> > Kamesh
> > Hughes Software Systems
> >
> >
> >
> >
> > Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org
> on
> > 06/05/2003 07:40:28 PM
> >
> > Sent by:    sigtran-admin@ietf.org
> >
> >
> > To:    sigtran@ietf.org
> > cc:
> >
> > Subject:    Re: [Sigtran] M3UA : Multiple SGPs in
> SG
> >
> >
> > Hi Kamesh,
> >
> > IMO, it is a fair assumption for most of the cases
> > that processing power for SG-side hosts is higher
> > than
> > of a single ASP (of course, still a configuration
> > issue)
> >
> > For loadsharing on SG-side, for incoming traffic
> > from
> > SS7 there is already loadsharing among links, and
> > links are residing on different hosts. So, I would
> > think incoming traffic will be more or less evenly
> > distributed among different hosts (and probably
> you
> > will first try the local SGP on that host to route
> > the
> > traffic to ASPs, but still implementation
> > dependent).
> >
> >    Tolga
> > --- kakaul@hss.hns.com wrote:
> > >
> > >
> > >
> > >
> > > Hi Tolga,
> > >                      I want to clarify one more
> > > point that in n+k
> > > redundancy mode we are saying that n ASP's
> should
> > be
> > > active in SGP for the
> > > AS to handle AS traffic, but can you tell me are
> > we
> > > assuming that SGP
> > > handling entire traffic of AS is an high
> > processing
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 12:32:59 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01624
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 12:32:59 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56GWX307568
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 12:32:33 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56GVgB07396;
	Fri, 6 Jun 2003 12:31:42 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56GSpB07166
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 12:28:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01254
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 12:28:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OK3K-0003q0-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 12:26:54 -0400
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OK3I-0003pn-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 12:26:52 -0400
Received: from [172.16.1.40] (helo=ccpu00251)
	by smtp.ccpu.com with smtp (Exim 4.20 #1 (Debian))
	id 19OK4s-00027f-7l; Fri, 06 Jun 2003 09:28:30 -0700
Reply-To: <umesh@ccpu.com>
From: "Umesh Vats" <umesh@ccpu.com>
To: "Tolga Asveren" <tolga_asveren@yahoo.com>, <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA : Multiple SGPs in SG
Date: Fri, 6 Jun 2003 09:31:45 -0700
Message-ID: <ACEMIJONPBBPDLOKCABHMEIKCAAA.umesh@ccpu.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <20030606155913.37728.qmail@web12806.mail.yahoo.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Tolga

The following text exists in implementor's guide.

                   "An SGP or IPSP, upon reception of an ASP Active message
for the first
                    ASP in a Loadshare AS, SHOULD NOT direct traffic to a
newly active
                    ASP until it determines that there are sufficient
resources to handle
                    the expected load (e.g., until there are "n" ASPs in
state ASP-ACTIVE
                    in the AS).  In this case, the SGP or IPSP SHOULD
withhold the Notify
                    (AS-ACTIVE) until there are sufficient resources."

On SG, n ASPs must be active for an AS to before an AS is made active. It
doesn't
matter whether they went ACTIVE from the same SGP or different SGPs.

Although the state of each remote ASP is maintained in the AS, the overall
AS is
visible to whole SG. The following statement in RFC 3332 helps :
 " Where an SG contains more than one SGP, the MTP3 routeset, SPMC and
   remote AS/ASP states of each SGP SHOULD be coordinated across all the
   SGPs.  Rerouting of traffic between the SGPs MAY also be supported."

Similarly for ASP to SG traffic, the SGP to which that ASP is connected
doesn't matter when
it has to decide about starting the traffic flow. All ASPs should coordinate
among themselves if n ASP are ACTIVE for an AS or not.

"For the n+k redundancy case, ASPs which are in that AS should
   coordinate among themselves the number of active ASPs in the AS, and
   should start sending traffic only after n ASPs are active."

rgds
Umesh







-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
Tolga Asveren
Sent: Friday, June 06, 2003 8:59 AM
To: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG


Hi Kamesh,

In IG 3.15 there are some changes/clarifications
related with n+k redundancy (those most probably will
be reworked but I think we still can rely on
INACTIVE->ACTIVE transition for AS state machine
there-)
In RFC3332 4.3.1
"The state of each remote ASP, in each AS that it is
configured to operate, is maintained in the M3UA layer
in the SGP."
So, the AS state machine is kept in SGP -not SG wide-
and IG does not change this.

Now, IMO, what you tell -just while counting number of
ACTIVE ASPs for an AS acting SGwide but for the other
ASPTM procedures still keeping per SGP approach- is
not undoable, but not inline with current RFC/IG.

IMO, cases, where this might be usefull will be
probably very rare (I think, it is not a very high
possibility that an association to an ASP1 can be
formed from SGP1 and can't be formed from SGP2 and for
ASP2 can be formed from SGP2 but can't be formed from
SGP1, if they are part of the same SG) and I would
think introducing a new configuration item for that is
probably not worth.
Other opinions?

   Tolga

--- kakaul@hss.hns.com wrote:
>
>
>
>
> Hi Tolga,
>
>  RFC does not say any thing about n+k redundancy as
> you have pointed out in
> your first response. I am
>  attaching the lines from RFC from section 4.3.4.3
> ASP Active Procedures:
> "For the n+k redundancy case, ASPs which are in that
> AS should
>  coordinate among themselves the number of active
> ASPs in the AS, and
>  should start sending traffic only after n ASPs are
> active.
>
>  All ASPs within a loadsharing mode AS must be able
> to process any
>  Data message received for the AS, to accommodate
> any potential
>  failover or rebalancing of the offered load."
>
> So if there is any interopability problem as you
> have indicated by keeping
> the RFC open ended then it should         be
> addressed in the
> implementation guide.I still believe that it is an
> implementation issue and
> can be resolved by configuring each AS and SG nodes
> in one of the two ways
> of n+k redundancy scope i.e specific to SG or SGP.
>
> Regards
> Kamesh
>
>
>
>
> Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org on
> 06/06/2003 04:35:03 PM
>
> Sent by:    sigtran-admin@ietf.org
>
>
> To:    sigtran@ietf.org
> cc:
>
> Subject:    Re: [Sigtran] M3UA : Multiple SGPs in SG
>
>
> Hi Kamesh,
>
> If we have to types of SGs (one, which activates
> traffic based on number of ACTIVE ASPs per SGP and
> the
> other per SG), ASPs can't decide -at least based on
> the current RFC- when to start/accept traffic. What
> ASPs are supposed to do is coordinating number of
> ACTIVE ASPs among the cluster, but if they don't
> know,
> whether the SG is deciding based on per SGP counter
> or
> not, there will be interoperability problems (for
> example SG uses a global ACTIVE ASP counter and
> starts
> traffic but ASPs are counting per SGP, they probably
> will drop arriving DATA).
>
>     Tolga
> --- kakaul@hss.hns.com wrote:
> >
> >
> >
> >
> > Hi Tolga,
> >                     I am of the openion that scope
> > of n+k redundancy should
> > depend on how one views and implements an SG. In
> > figure given below if an
> > implementation wants to reroute some AS traffic to
> > its adjacent SGP on its
> > way to AS it should be allowed.BTW as you have
> also
> > agreed that ASP1 and
> > ASP2 also qualifies as two ASP's of AS if SGP1 and
> > SGP2 has active
> > associations with ASP1 and ASP2 respectively.SGP
> may
> > not want to block the
> > traffic for AS if association between SGP1 and
> ASP2
> > is not active for AS
> > assuming n = 2, k = 0(for n+k redundancy). I am
> not
> > able to understand what
> > interopability issue will be involved in it.No
> doubt
> > limiting scope of n+k
> > redundancy to SGP is clear and simple but some
> > implementations may want to
> > use inter SGP routing to route there traffic to
> AS.
> > So it ultimately
> > depends on how you want your SG implementation to
> > behave.
> >
> >
> >                       SG
> >                   +--------------+            AS
> >                   |              |
> > +---------+--+
> >                   |              |        |
> >   |
> >                   | +--------+   |
> > |+--------+  |
> >                   | |        |   |        ||
> > |  |
> >                   | |  SGP1  *---+--------++ ASP1
> > |  |
> >                   | +--------+\  |
> > |+--------+  |
> >                   |    |         \        |
> >   |
> >   inter SGP  -----+----+         |        |
> >   |
> >   routing         |    |         |   \    |
> >   |
> >                   | +--------+   |     \
> > |+--------+  |
> >                   | |        |   |       \||
> > |  |
> >                   | | SGP2   +---+------ -*+  ASP2
> > |  |
> >                   | +--------+   |
> > |+--------+  |
> >                   |              |        |
> >   |
> >                   +--------------+
> > +------------+
> >
> > Regards
> > Kamesh
> > Hughes Software Systems
> >
> >
> >
> >
> > Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org
> on
> > 06/05/2003 07:40:28 PM
> >
> > Sent by:    sigtran-admin@ietf.org
> >
> >
> > To:    sigtran@ietf.org
> > cc:
> >
> > Subject:    Re: [Sigtran] M3UA : Multiple SGPs in
> SG
> >
> >
> > Hi Kamesh,
> >
> > IMO, it is a fair assumption for most of the cases
> > that processing power for SG-side hosts is higher
> > than
> > of a single ASP (of course, still a configuration
> > issue)
> >
> > For loadsharing on SG-side, for incoming traffic
> > from
> > SS7 there is already loadsharing among links, and
> > links are residing on different hosts. So, I would
> > think incoming traffic will be more or less evenly
> > distributed among different hosts (and probably
> you
> > will first try the local SGP on that host to route
> > the
> > traffic to ASPs, but still implementation
> > dependent).
> >
> >    Tolga
> > --- kakaul@hss.hns.com wrote:
> > >
> > >
> > >
> > >
> > > Hi Tolga,
> > >                      I want to clarify one more
> > > point that in n+k
> > > redundancy mode we are saying that n ASP's
> should
> > be
> > > active in SGP for the
> > > AS to handle AS traffic, but can you tell me are
> > we
> > > assuming that SGP
> > > handling entire traffic of AS is an high
> > processing
>
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran

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



From mailnull@www1.ietf.org  Fri Jun  6 12:50:53 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02045
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 12:50:53 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56GoRF09227
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 12:50:27 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56GnYB09168;
	Fri, 6 Jun 2003 12:49:34 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56GkJB09031
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 12:46:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01915
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 12:46:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OKKE-000410-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 12:44:22 -0400
Received: from web12803.mail.yahoo.com ([216.136.174.38])
	by ietf-mx with smtp (Exim 4.12)
	id 19OKKC-00040x-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 12:44:21 -0400
Message-ID: <20030606164609.55947.qmail@web12803.mail.yahoo.com>
Received: from [208.255.120.2] by web12803.mail.yahoo.com via HTTP; Fri, 06 Jun 2003 09:46:09 PDT
Date: Fri, 6 Jun 2003 09:46:09 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: RE: [Sigtran] M3UA : Multiple SGPs in SG
To: sigtran@ietf.org
In-Reply-To: <ACEMIJONPBBPDLOKCABHMEIKCAAA.umesh@ccpu.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Hi Umesh,
--- Umesh Vats <umesh@ccpu.com> wrote:
> Hi Tolga
> 
> The following text exists in implementor's guide.
> 
>                    "An SGP or IPSP, upon reception
> of an ASP Active message
> for the first
>                     ASP in a Loadshare AS, SHOULD
> NOT direct traffic to a
> newly active
>                     ASP until it determines that
> there are sufficient
> resources to handle
>                     the expected load (e.g., until
> there are "n" ASPs in
> state ASP-ACTIVE
>                     in the AS).  In this case, the
> SGP or IPSP SHOULD
> withhold the Notify
>                     (AS-ACTIVE) until there are
> sufficient resources."
> 
> On SG, n ASPs must be active for an AS to before an
> AS is made active. It
> doesn't
> matter whether they went ACTIVE from the same SGP or
> different SGPs.
> 
> Although the state of each remote ASP is maintained
> in the AS, the overall
> AS is
> visible to whole SG. The following statement in RFC
> 3332 helps :
>  " Where an SG contains more than one SGP, the MTP3
> routeset, SPMC and
>    remote AS/ASP states of each SGP SHOULD be
> coordinated across all the
>    SGPs.  Rerouting of traffic between the SGPs MAY
> also be supported."
[TOLGA]This is the place I think a bit different.
Please note the "MAY" in the last sentence. I think it
was agreed not to use  a "SHOULD" here to not force
internal routing. (BTW, I think even the "SHOULD" in
the first sentence should be changed to "MAY")As I
said, basically counting number of ACTIVE ASPs per SG
will just introduce interoperability problems unless
some modifications are introduced to the IG and
considering that SGPs in a SG will most probably have
the same IP connectivity, this IMO is not very usefull
in real life. I personally would prefer the simple and
clear way of having all ASPTM procedures per SGP.(for
example do you like the idea of having ASPTM per SG
instead of SGP?)
> 
> Similarly for ASP to SG traffic, the SGP to which
> that ASP is connected
> doesn't matter when
> it has to decide about starting the traffic flow.
> All ASPs should coordinate
> among themselves if n ASP are ACTIVE for an AS or
> not.
[TOLGA]If what you mean is, that it really does not
matter for which SGP ASPs went ACTIVE, I disagree, at
least SG, SGP is part of should matter. Apart from
this, although the sentence might be not very clear in
the context of this discussion, the intention was to
coordinate number of ACTIVE ASPs for each SGP
separetly. Maybe a clarification might be added to IG.
> 
> "For the n+k redundancy case, ASPs which are in that
> AS should
>    coordinate among themselves the number of active
> ASPs in the AS, and
>    should start sending traffic only after n ASPs
> are active."
> 
> rgds
> Umesh
> 
> 
> 
> 
> 
> 
> 
> -----Original Message-----
> From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> Tolga Asveren
> Sent: Friday, June 06, 2003 8:59 AM
> To: sigtran@ietf.org
> Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
> 
> 
> Hi Kamesh,
> 
> In IG 3.15 there are some changes/clarifications
> related with n+k redundancy (those most probably
> will
> be reworked but I think we still can rely on
> INACTIVE->ACTIVE transition for AS state machine
> there-)
> In RFC3332 4.3.1
> "The state of each remote ASP, in each AS that it is
> configured to operate, is maintained in the M3UA
> layer
> in the SGP."
> So, the AS state machine is kept in SGP -not SG
> wide-
> and IG does not change this.
> 
> Now, IMO, what you tell -just while counting number
> of
> ACTIVE ASPs for an AS acting SGwide but for the
> other
> ASPTM procedures still keeping per SGP approach- is
> not undoable, but not inline with current RFC/IG.
> 
> IMO, cases, where this might be usefull will be
> probably very rare (I think, it is not a very high
> possibility that an association to an ASP1 can be
> formed from SGP1 and can't be formed from SGP2 and
> for
> ASP2 can be formed from SGP2 but can't be formed
> from
> SGP1, if they are part of the same SG) and I would
> think introducing a new configuration item for that
> is
> probably not worth.
> Other opinions?
> 
>    Tolga
> 
> --- kakaul@hss.hns.com wrote:
> >
> >
> >
> >
> > Hi Tolga,
> >
> >  RFC does not say any thing about n+k redundancy
> as
> > you have pointed out in
> > your first response. I am
> >  attaching the lines from RFC from section 4.3.4.3
> > ASP Active Procedures:
> > "For the n+k redundancy case, ASPs which are in
> that
> > AS should
> >  coordinate among themselves the number of active
> > ASPs in the AS, and
> >  should start sending traffic only after n ASPs
> are
> > active.
> >
> >  All ASPs within a loadsharing mode AS must be
> able
> > to process any
> >  Data message received for the AS, to accommodate
> > any potential
> >  failover or rebalancing of the offered load."
> >
> > So if there is any interopability problem as you
> > have indicated by keeping
> > the RFC open ended then it should         be
> > addressed in the
> > implementation guide.I still believe that it is an
> > implementation issue and
> > can be resolved by configuring each AS and SG
> nodes
> > in one of the two ways
> > of n+k redundancy scope i.e specific to SG or SGP.
> >
> > Regards
> > Kamesh
> >
> >
> >
> >
> > Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org
> on
> > 06/06/2003 04:35:03 PM
> >
> > Sent by:    sigtran-admin@ietf.org
> >
> >
> > To:    sigtran@ietf.org
> > cc:
> >
> > Subject:    Re: [Sigtran] M3UA : Multiple SGPs in
> SG
> >
> >
> > Hi Kamesh,
> >
> > If we have to types of SGs (one, which activates
> > traffic based on number of ACTIVE ASPs per SGP and
> > the
> > other per SG), ASPs can't decide -at least based
> on
> > the current RFC- when to start/accept traffic.
> What
> > ASPs are supposed to do is coordinating number of
> > ACTIVE ASPs among the cluster, but if they don't
> > know,
> > whether the SG is deciding based on per SGP
> counter
> > or
> > not, there will be interoperability problems (for
> > example SG uses a global ACTIVE ASP counter and
> > starts
> > traffic but ASPs are counting per SGP, they
> probably
> > will drop arriving DATA).
> >
> >     Tolga
> > --- kakaul@hss.hns.com wrote:
> > >
> > >
> > >
> > >
> > > Hi Tolga,
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 13:26:48 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03315
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 13:26:48 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56HQOw11934
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 13:26:24 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56HPNB11835;
	Fri, 6 Jun 2003 13:25:24 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56HLJB11642
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 13:21:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03192
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 13:21:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OKs5-0004Mn-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 13:19:21 -0400
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OKs1-0004Mk-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 13:19:18 -0400
Received: from [172.16.1.40] (helo=ccpu00251)
	by smtp.ccpu.com with smtp (Exim 4.20 #1 (Debian))
	id 19OKtf-00055M-Pi; Fri, 06 Jun 2003 10:20:59 -0700
Reply-To: <umesh@ccpu.com>
From: "Umesh Vats" <umesh@ccpu.com>
To: "Tolga Asveren" <tolga_asveren@yahoo.com>, <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA : Multiple SGPs in SG
Date: Fri, 6 Jun 2003 10:24:15 -0700
Message-ID: <ACEMIJONPBBPDLOKCABHIEILCAAA.umesh@ccpu.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <20030606164609.55947.qmail@web12803.mail.yahoo.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Tolga

But internal routing between SGPs must be supported
if want to take care of message loss/message missequencing
when the associations between ASPs/SGPs go down or come
up.

Many other procedures in the RFC require internal communication
between ASPs and SGPs.

So in my opinion, the MAY in last sentence should be modified to SHOULD.

" Where an SG contains more than one SGP, the MTP3
> routeset, SPMC and
>    remote AS/ASP states of each SGP SHOULD be
> coordinated across all the
>    SGPs.  Rerouting of traffic between the SGPs MAY
> also be supported."

In reference to your statement :
"I personally would prefer the simple and
clear way of having all ASPTM procedures per SGP.(for
example do you like the idea of having ASPTM per SG
instead of SGP?)"

Having ASPTM on SG basis is someting we can explore. But it would be really
helpful if instead of SGPs, we have concept of just one physical SG with
capabilityof representing multile endpoints through configuration, each
representing
logical SGP. This will take care of all internal communication problems.
For higher fault tolerance and thorughput, one can duplicate the SG onto
several hosts using current fault tolerance and high availability
technologies
already being used in SS7 switches.

Umesh

-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
Tolga Asveren
Sent: Friday, June 06, 2003 9:46 AM
To: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA : Multiple SGPs in SG


Hi Umesh,
--- Umesh Vats <umesh@ccpu.com> wrote:
> Hi Tolga
>
> The following text exists in implementor's guide.
>
>                    "An SGP or IPSP, upon reception
> of an ASP Active message
> for the first
>                     ASP in a Loadshare AS, SHOULD
> NOT direct traffic to a
> newly active
>                     ASP until it determines that
> there are sufficient
> resources to handle
>                     the expected load (e.g., until
> there are "n" ASPs in
> state ASP-ACTIVE
>                     in the AS).  In this case, the
> SGP or IPSP SHOULD
> withhold the Notify
>                     (AS-ACTIVE) until there are
> sufficient resources."
>
> On SG, n ASPs must be active for an AS to before an
> AS is made active. It
> doesn't
> matter whether they went ACTIVE from the same SGP or
> different SGPs.
>
> Although the state of each remote ASP is maintained
> in the AS, the overall
> AS is
> visible to whole SG. The following statement in RFC
> 3332 helps :
>  " Where an SG contains more than one SGP, the MTP3
> routeset, SPMC and
>    remote AS/ASP states of each SGP SHOULD be
> coordinated across all the
>    SGPs.  Rerouting of traffic between the SGPs MAY
> also be supported."
[TOLGA]This is the place I think a bit different.
Please note the "MAY" in the last sentence. I think it
was agreed not to use  a "SHOULD" here to not force
internal routing. (BTW, I think even the "SHOULD" in
the first sentence should be changed to "MAY")As I
said, basically counting number of ACTIVE ASPs per SG
will just introduce interoperability problems unless
some modifications are introduced to the IG and
considering that SGPs in a SG will most probably have
the same IP connectivity, this IMO is not very usefull
in real life. I personally would prefer the simple and
clear way of having all ASPTM procedures per SGP.(for
example do you like the idea of having ASPTM per SG
instead of SGP?)
>
> Similarly for ASP to SG traffic, the SGP to which
> that ASP is connected
> doesn't matter when
> it has to decide about starting the traffic flow.
> All ASPs should coordinate
> among themselves if n ASP are ACTIVE for an AS or
> not.
[TOLGA]If what you mean is, that it really does not
matter for which SGP ASPs went ACTIVE, I disagree, at
least SG, SGP is part of should matter. Apart from
this, although the sentence might be not very clear in
the context of this discussion, the intention was to
coordinate number of ACTIVE ASPs for each SGP
separetly. Maybe a clarification might be added to IG.
>
> "For the n+k redundancy case, ASPs which are in that
> AS should
>    coordinate among themselves the number of active
> ASPs in the AS, and
>    should start sending traffic only after n ASPs
> are active."
>
> rgds
> Umesh
>
>
>
>
>
>
>
> -----Original Message-----
> From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> Tolga Asveren
> Sent: Friday, June 06, 2003 8:59 AM
> To: sigtran@ietf.org
> Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
>
>
> Hi Kamesh,
>
> In IG 3.15 there are some changes/clarifications
> related with n+k redundancy (those most probably
> will
> be reworked but I think we still can rely on
> INACTIVE->ACTIVE transition for AS state machine
> there-)
> In RFC3332 4.3.1
> "The state of each remote ASP, in each AS that it is
> configured to operate, is maintained in the M3UA
> layer
> in the SGP."
> So, the AS state machine is kept in SGP -not SG
> wide-
> and IG does not change this.
>
> Now, IMO, what you tell -just while counting number
> of
> ACTIVE ASPs for an AS acting SGwide but for the
> other
> ASPTM procedures still keeping per SGP approach- is
> not undoable, but not inline with current RFC/IG.
>
> IMO, cases, where this might be usefull will be
> probably very rare (I think, it is not a very high
> possibility that an association to an ASP1 can be
> formed from SGP1 and can't be formed from SGP2 and
> for
> ASP2 can be formed from SGP2 but can't be formed
> from
> SGP1, if they are part of the same SG) and I would
> think introducing a new configuration item for that
> is
> probably not worth.
> Other opinions?
>
>    Tolga
>
> --- kakaul@hss.hns.com wrote:
> >
> >
> >
> >
> > Hi Tolga,
> >
> >  RFC does not say any thing about n+k redundancy
> as
> > you have pointed out in
> > your first response. I am
> >  attaching the lines from RFC from section 4.3.4.3
> > ASP Active Procedures:
> > "For the n+k redundancy case, ASPs which are in
> that
> > AS should
> >  coordinate among themselves the number of active
> > ASPs in the AS, and
> >  should start sending traffic only after n ASPs
> are
> > active.
> >
> >  All ASPs within a loadsharing mode AS must be
> able
> > to process any
> >  Data message received for the AS, to accommodate
> > any potential
> >  failover or rebalancing of the offered load."
> >
> > So if there is any interopability problem as you
> > have indicated by keeping
> > the RFC open ended then it should         be
> > addressed in the
> > implementation guide.I still believe that it is an
> > implementation issue and
> > can be resolved by configuring each AS and SG
> nodes
> > in one of the two ways
> > of n+k redundancy scope i.e specific to SG or SGP.
> >
> > Regards
> > Kamesh
> >
> >
> >
> >
> > Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org
> on
> > 06/06/2003 04:35:03 PM
> >
> > Sent by:    sigtran-admin@ietf.org
> >
> >
> > To:    sigtran@ietf.org
> > cc:
> >
> > Subject:    Re: [Sigtran] M3UA : Multiple SGPs in
> SG
> >
> >
> > Hi Kamesh,
> >
> > If we have to types of SGs (one, which activates
> > traffic based on number of ACTIVE ASPs per SGP and
> > the
> > other per SG), ASPs can't decide -at least based
> on
> > the current RFC- when to start/accept traffic.
> What
> > ASPs are supposed to do is coordinating number of
> > ACTIVE ASPs among the cluster, but if they don't
> > know,
> > whether the SG is deciding based on per SGP
> counter
> > or
> > not, there will be interoperability problems (for
> > example SG uses a global ACTIVE ASP counter and
> > starts
> > traffic but ASPs are counting per SGP, they
> probably
> > will drop arriving DATA).
> >
> >     Tolga
> > --- kakaul@hss.hns.com wrote:
> > >
> > >
> > >
> > >
> > > Hi Tolga,
>
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran

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



From mailnull@www1.ietf.org  Fri Jun  6 14:00:00 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04987
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 13:59:59 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56HxYu15252
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 13:59:34 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56HwhB15191;
	Fri, 6 Jun 2003 13:58:43 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56HtXB14960
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 13:55:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04664
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 13:55:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OLPA-0004nX-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 13:53:32 -0400
Received: from web12804.mail.yahoo.com ([216.136.174.39])
	by ietf-mx with smtp (Exim 4.12)
	id 19OLP8-0004nJ-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 13:53:31 -0400
Message-ID: <20030606175521.1841.qmail@web12804.mail.yahoo.com>
Received: from [208.255.120.2] by web12804.mail.yahoo.com via HTTP; Fri, 06 Jun 2003 10:55:21 PDT
Date: Fri, 6 Jun 2003 10:55:21 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: RE: [Sigtran] M3UA : Multiple SGPs in SG
To: sigtran@ietf.org
In-Reply-To: <ACEMIJONPBBPDLOKCABHIEILCAAA.umesh@ccpu.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Hi Umesh,
--- Umesh Vats <umesh@ccpu.com> wrote:
> Hi Tolga
> 
> But internal routing between SGPs must be supported
> if want to take care of message loss/message
> missequencing
> when the associations between ASPs/SGPs go down or
> come
> up.
[TOLGA]As far as I remember, some methods were
presented, which will work withoud a need of internal
routing -unfortunately I don't remember the details-,
because this discussion about "SHOULD" v.s. "MAY" has
happened some time ago.
> 
> Many other procedures in the RFC require internal
> communication
> between ASPs and SGPs.
> 
> So in my opinion, the MAY in last sentence should be
> modified to SHOULD.
> 
> " Where an SG contains more than one SGP, the MTP3
> > routeset, SPMC and
> >    remote AS/ASP states of each SGP SHOULD be
> > coordinated across all the
> >    SGPs.  Rerouting of traffic between the SGPs
> MAY
> > also be supported."
> 
> In reference to your statement :
> "I personally would prefer the simple and
> clear way of having all ASPTM procedures per
> SGP.(for
> example do you like the idea of having ASPTM per SG
> instead of SGP?)"
> 
> Having ASPTM on SG basis is someting we can explore.
> But it would be really
> helpful if instead of SGPs, we have concept of just
> one physical SG with
> capabilityof representing multile endpoints through
> configuration, each
> representing
> logical SGP. This will take care of all internal
> communication problems.
> For higher fault tolerance and thorughput, one can
> duplicate the SG onto
> several hosts using current fault tolerance and high
> availability
> technologies
> already being used in SS7 switches.
[TOLGA]Apart from any technical
advantages/disadvantages, I think this would be a big
change considering the status of M3UA specifications.
BTW, to make use of the existing mechanims including
network management procedures, you might have a look
to the SGSG draft.
> 
> Umesh
> 
> -----Original Message-----
> From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> Tolga Asveren
> Sent: Friday, June 06, 2003 9:46 AM
> To: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA : Multiple SGPs in SG
> 
> 
> Hi Umesh,
> --- Umesh Vats <umesh@ccpu.com> wrote:
> > Hi Tolga
> >
> > The following text exists in implementor's guide.
> >
> >                    "An SGP or IPSP, upon reception
> > of an ASP Active message
> > for the first
> >                     ASP in a Loadshare AS, SHOULD
> > NOT direct traffic to a
> > newly active
> >                     ASP until it determines that
> > there are sufficient
> > resources to handle
> >                     the expected load (e.g., until
> > there are "n" ASPs in
> > state ASP-ACTIVE
> >                     in the AS).  In this case, the
> > SGP or IPSP SHOULD
> > withhold the Notify
> >                     (AS-ACTIVE) until there are
> > sufficient resources."
> >
> > On SG, n ASPs must be active for an AS to before
> an
> > AS is made active. It
> > doesn't
> > matter whether they went ACTIVE from the same SGP
> or
> > different SGPs.
> >
> > Although the state of each remote ASP is
> maintained
> > in the AS, the overall
> > AS is
> > visible to whole SG. The following statement in
> RFC
> > 3332 helps :
> >  " Where an SG contains more than one SGP, the
> MTP3
> > routeset, SPMC and
> >    remote AS/ASP states of each SGP SHOULD be
> > coordinated across all the
> >    SGPs.  Rerouting of traffic between the SGPs
> MAY
> > also be supported."
> [TOLGA]This is the place I think a bit different.
> Please note the "MAY" in the last sentence. I think
> it
> was agreed not to use  a "SHOULD" here to not force
> internal routing. (BTW, I think even the "SHOULD" in
> the first sentence should be changed to "MAY")As I
> said, basically counting number of ACTIVE ASPs per
> SG
> will just introduce interoperability problems unless
> some modifications are introduced to the IG and
> considering that SGPs in a SG will most probably
> have
> the same IP connectivity, this IMO is not very
> usefull
> in real life. I personally would prefer the simple
> and
> clear way of having all ASPTM procedures per
> SGP.(for
> example do you like the idea of having ASPTM per SG
> instead of SGP?)
> >
> > Similarly for ASP to SG traffic, the SGP to which
> > that ASP is connected
> > doesn't matter when
> > it has to decide about starting the traffic flow.
> > All ASPs should coordinate
> > among themselves if n ASP are ACTIVE for an AS or
> > not.
> [TOLGA]If what you mean is, that it really does not
> matter for which SGP ASPs went ACTIVE, I disagree,
> at
> least SG, SGP is part of should matter. Apart from
> this, although the sentence might be not very clear
> in
> the context of this discussion, the intention was to
> coordinate number of ACTIVE ASPs for each SGP
> separetly. Maybe a clarification might be added to
> IG.
> >
> > "For the n+k redundancy case, ASPs which are in
> that
> > AS should
> >    coordinate among themselves the number of
> active
> > ASPs in the AS, and
> >    should start sending traffic only after n ASPs
> > are active."
> >
> > rgds
> > Umesh
> >
> >
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Tolga Asveren
> > Sent: Friday, June 06, 2003 8:59 AM
> > To: sigtran@ietf.org
> > Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
> >
> >
> > Hi Kamesh,
> >
> > In IG 3.15 there are some changes/clarifications
> > related with n+k redundancy (those most probably
> > will
> > be reworked but I think we still can rely on
> > INACTIVE->ACTIVE transition for AS state machine
> > there-)
> > In RFC3332 4.3.1
> > "The state of each remote ASP, in each AS that it
> is
> > configured to operate, is maintained in the M3UA
> > layer
> > in the SGP."
> > So, the AS state machine is kept in SGP -not SG
> > wide-
> > and IG does not change this.
> >
> > Now, IMO, what you tell -just while counting
> number
> > of
> > ACTIVE ASPs for an AS acting SGwide but for the
> > other
> > ASPTM procedures still keeping per SGP approach-
> is
> > not undoable, but not inline with current RFC/IG.
> >
> > IMO, cases, where this might be usefull will be
> > probably very rare (I think, it is not a very high
> > possibility that an association to an ASP1 can be
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 15:45:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09923
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 15:45:31 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56Jj3Q23825
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 15:45:03 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56JiVB23797;
	Fri, 6 Jun 2003 15:44:33 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56JeuB23646
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 15:40:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09750
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 15:40:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ON3D-0005kF-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 15:38:59 -0400
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ON3A-0005jy-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 15:38:57 -0400
Received: from [172.16.1.40] (helo=ccpu00251)
	by smtp.ccpu.com with smtp (Exim 4.20 #1 (Debian))
	id 19ON4r-00053D-Fk; Fri, 06 Jun 2003 12:40:41 -0700
Reply-To: <umesh@ccpu.com>
From: "Umesh Vats" <umesh@ccpu.com>
To: "Tolga Asveren" <tolga_asveren@yahoo.com>, <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA : Multiple SGPs in SG
Date: Fri, 6 Jun 2003 12:43:58 -0700
Message-ID: <ACEMIJONPBBPDLOKCABHGEINCAAA.umesh@ccpu.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <20030606175521.1841.qmail@web12804.mail.yahoo.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Overall it looks, its dependent on the specific architecture how
they interpret the concepts of AS/SG/SGP and traffic modes.
Different people have different understanding.

In many architectures, its really helpful to have ASP-ASP and SGP-SGP
communication to take care of lot of issues :
1. Message missequencing
2. Message loss
3. Visibility of same AS and AS-status/ASP-status/SGP-status on all 
   SGPs and ASPs.
4. Avoiding the need for establishment of redundant associations
   between SG and ASPs. This is by assuming n+k redundancy mode
   on SG basis instead of SGP basis.

Umesh 

-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
Tolga Asveren
Sent: Friday, June 06, 2003 10:55 AM
To: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA : Multiple SGPs in SG


Hi Umesh,
--- Umesh Vats <umesh@ccpu.com> wrote:
> Hi Tolga
> 
> But internal routing between SGPs must be supported
> if want to take care of message loss/message
> missequencing
> when the associations between ASPs/SGPs go down or
> come
> up.
[TOLGA]As far as I remember, some methods were
presented, which will work withoud a need of internal
routing -unfortunately I don't remember the details-,
because this discussion about "SHOULD" v.s. "MAY" has
happened some time ago.
> 
> Many other procedures in the RFC require internal
> communication
> between ASPs and SGPs.
> 
> So in my opinion, the MAY in last sentence should be
> modified to SHOULD.
> 
> " Where an SG contains more than one SGP, the MTP3
> > routeset, SPMC and
> >    remote AS/ASP states of each SGP SHOULD be
> > coordinated across all the
> >    SGPs.  Rerouting of traffic between the SGPs
> MAY
> > also be supported."
> 
> In reference to your statement :
> "I personally would prefer the simple and
> clear way of having all ASPTM procedures per
> SGP.(for
> example do you like the idea of having ASPTM per SG
> instead of SGP?)"
> 
> Having ASPTM on SG basis is someting we can explore.
> But it would be really
> helpful if instead of SGPs, we have concept of just
> one physical SG with
> capabilityof representing multile endpoints through
> configuration, each
> representing
> logical SGP. This will take care of all internal
> communication problems.
> For higher fault tolerance and thorughput, one can
> duplicate the SG onto
> several hosts using current fault tolerance and high
> availability
> technologies
> already being used in SS7 switches.
[TOLGA]Apart from any technical
advantages/disadvantages, I think this would be a big
change considering the status of M3UA specifications.
BTW, to make use of the existing mechanims including
network management procedures, you might have a look
to the SGSG draft.
> 
> Umesh
> 
> -----Original Message-----
> From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> Tolga Asveren
> Sent: Friday, June 06, 2003 9:46 AM
> To: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA : Multiple SGPs in SG
> 
> 
> Hi Umesh,
> --- Umesh Vats <umesh@ccpu.com> wrote:
> > Hi Tolga
> >
> > The following text exists in implementor's guide.
> >
> >                    "An SGP or IPSP, upon reception
> > of an ASP Active message
> > for the first
> >                     ASP in a Loadshare AS, SHOULD
> > NOT direct traffic to a
> > newly active
> >                     ASP until it determines that
> > there are sufficient
> > resources to handle
> >                     the expected load (e.g., until
> > there are "n" ASPs in
> > state ASP-ACTIVE
> >                     in the AS).  In this case, the
> > SGP or IPSP SHOULD
> > withhold the Notify
> >                     (AS-ACTIVE) until there are
> > sufficient resources."
> >
> > On SG, n ASPs must be active for an AS to before
> an
> > AS is made active. It
> > doesn't
> > matter whether they went ACTIVE from the same SGP
> or
> > different SGPs.
> >
> > Although the state of each remote ASP is
> maintained
> > in the AS, the overall
> > AS is
> > visible to whole SG. The following statement in
> RFC
> > 3332 helps :
> >  " Where an SG contains more than one SGP, the
> MTP3
> > routeset, SPMC and
> >    remote AS/ASP states of each SGP SHOULD be
> > coordinated across all the
> >    SGPs.  Rerouting of traffic between the SGPs
> MAY
> > also be supported."
> [TOLGA]This is the place I think a bit different.
> Please note the "MAY" in the last sentence. I think
> it
> was agreed not to use  a "SHOULD" here to not force
> internal routing. (BTW, I think even the "SHOULD" in
> the first sentence should be changed to "MAY")As I
> said, basically counting number of ACTIVE ASPs per
> SG
> will just introduce interoperability problems unless
> some modifications are introduced to the IG and
> considering that SGPs in a SG will most probably
> have
> the same IP connectivity, this IMO is not very
> usefull
> in real life. I personally would prefer the simple
> and
> clear way of having all ASPTM procedures per
> SGP.(for
> example do you like the idea of having ASPTM per SG
> instead of SGP?)
> >
> > Similarly for ASP to SG traffic, the SGP to which
> > that ASP is connected
> > doesn't matter when
> > it has to decide about starting the traffic flow.
> > All ASPs should coordinate
> > among themselves if n ASP are ACTIVE for an AS or
> > not.
> [TOLGA]If what you mean is, that it really does not
> matter for which SGP ASPs went ACTIVE, I disagree,
> at
> least SG, SGP is part of should matter. Apart from
> this, although the sentence might be not very clear
> in
> the context of this discussion, the intention was to
> coordinate number of ACTIVE ASPs for each SGP
> separetly. Maybe a clarification might be added to
> IG.
> >
> > "For the n+k redundancy case, ASPs which are in
> that
> > AS should
> >    coordinate among themselves the number of
> active
> > ASPs in the AS, and
> >    should start sending traffic only after n ASPs
> > are active."
> >
> > rgds
> > Umesh
> >
> >
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Tolga Asveren
> > Sent: Friday, June 06, 2003 8:59 AM
> > To: sigtran@ietf.org
> > Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
> >
> >
> > Hi Kamesh,
> >
> > In IG 3.15 there are some changes/clarifications
> > related with n+k redundancy (those most probably
> > will
> > be reworked but I think we still can rely on
> > INACTIVE->ACTIVE transition for AS state machine
> > there-)
> > In RFC3332 4.3.1
> > "The state of each remote ASP, in each AS that it
> is
> > configured to operate, is maintained in the M3UA
> > layer
> > in the SGP."
> > So, the AS state machine is kept in SGP -not SG
> > wide-
> > and IG does not change this.
> >
> > Now, IMO, what you tell -just while counting
> number
> > of
> > ACTIVE ASPs for an AS acting SGwide but for the
> > other
> > ASPTM procedures still keeping per SGP approach-
> is
> > not undoable, but not inline with current RFC/IG.
> >
> > IMO, cases, where this might be usefull will be
> > probably very rare (I think, it is not a very high
> > possibility that an association to an ASP1 can be
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran

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



From mailnull@www1.ietf.org  Fri Jun  6 15:52:41 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10080
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 15:52:41 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56JqDu24172
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 15:52:13 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56JpqB24149;
	Fri, 6 Jun 2003 15:51:52 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56JnIB24050
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 15:49:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10022
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 15:49:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ONBI-0005p7-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 15:47:20 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[yWIzUQE8iC/YDCX/I6i2E6rO3DfgL/Np])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ONBH-0005oz-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 15:47:19 -0400
Received: from ns.pigworks.openss7.net (IDENT:JB1M/1qqpGTSNNeLN1YaU8UXXTV7hqLx@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h56JnDF07924;
	Fri, 6 Jun 2003 13:49:13 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h56JnCt03556;
	Fri, 6 Jun 2003 13:49:12 -0600
Date: Fri, 6 Jun 2003 13:49:12 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
Message-ID: <20030606134912.A31671@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <OF249E38BE.F3DB01DC-ON65256D3D.00145E63@hss.hns.com> <20030606110503.74344.qmail@web12809.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030606110503.74344.qmail@web12809.mail.yahoo.com>; from tolga_asveren@yahoo.com on Fri, Jun 06, 2003 at 04:05:03AM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

SGs cannot "start" traffic.  They are not the stimulus.
The remote signalling points must start traffic in
response to a user part test and it will take a significant
amount of time before any traffic flows.

But we've discussed this before....

What I can't understand is why the IG hasn't been
corrected yet.

--brian

Tolga Asveren wrote:                                                                 (Fri, 06 Jun 2003 04:05:03)
> Hi Kamesh,
> 
> If we have to types of SGs (one, which activates
> traffic based on number of ACTIVE ASPs per SGP and the
> other per SG), ASPs can't decide -at least based on
> the current RFC- when to start/accept traffic. What
> ASPs are supposed to do is coordinating number of
> ACTIVE ASPs among the cluster, but if they don't know,
> whether the SG is deciding based on per SGP counter or
> not, there will be interoperability problems (for
> example SG uses a global ACTIVE ASP counter and starts
> traffic but ASPs are counting per SGP, they probably
> will drop arriving DATA). 
> 
>     Tolga
> --- kakaul@hss.hns.com wrote:
> > 
> > 
> > 
> > 
> > Hi Tolga,
> >                     I am of the openion that scope
> > of n+k redundancy should
> > depend on how one views and implements an SG. In
> > figure given below if an
> > implementation wants to reroute some AS traffic to
> > its adjacent SGP on its
> > way to AS it should be allowed.BTW as you have also
> > agreed that ASP1 and
> > ASP2 also qualifies as two ASP's of AS if SGP1 and
> > SGP2 has active
> > associations with ASP1 and ASP2 respectively.SGP may
> > not want to block the
> > traffic for AS if association between SGP1 and ASP2
> > is not active for AS
> > assuming n = 2, k = 0(for n+k redundancy). I am not
> > able to understand what
> > interopability issue will be involved in it.No doubt
> > limiting scope of n+k
> > redundancy to SGP is clear and simple but some
> > implementations may want to
> > use inter SGP routing to route there traffic to AS.
> > So it ultimately
> > depends on how you want your SG implementation to
> > behave.
> > 
> > 
> >                       SG
> >                   +--------------+            AS
> >                   |              |       
> > +---------+--+
> >                   |              |        |         
> >   |
> >                   | +--------+   |       
> > |+--------+  |
> >                   | |        |   |        ||       
> > |  |
> >                   | |  SGP1  *---+--------++ ASP1  
> > |  |
> >                   | +--------+\  |       
> > |+--------+  |
> >                   |    |         \        |         
> >   |
> >   inter SGP  -----+----+         |        |         
> >   |
> >   routing         |    |         |   \    |         
> >   |
> >                   | +--------+   |     \ 
> > |+--------+  |
> >                   | |        |   |       \||       
> > |  |
> >                   | | SGP2   +---+------ -*+  ASP2 
> > |  |
> >                   | +--------+   |       
> > |+--------+  |
> >                   |              |        |         
> >   |
> >                   +--------------+       
> > +------------+
> > 
> > Regards
> > Kamesh
> > Hughes Software Systems
> > 
> > 
> > 
> > 
> > Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org on
> > 06/05/2003 07:40:28 PM
> > 
> > Sent by:    sigtran-admin@ietf.org
> > 
> > 
> > To:    sigtran@ietf.org
> > cc:
> > 
> > Subject:    Re: [Sigtran] M3UA : Multiple SGPs in SG
> > 
> > 
> > Hi Kamesh,
> > 
> > IMO, it is a fair assumption for most of the cases
> > that processing power for SG-side hosts is higher
> > than
> > of a single ASP (of course, still a configuration
> > issue)
> > 
> > For loadsharing on SG-side, for incoming traffic
> > from
> > SS7 there is already loadsharing among links, and
> > links are residing on different hosts. So, I would
> > think incoming traffic will be more or less evenly
> > distributed among different hosts (and probably you
> > will first try the local SGP on that host to route
> > the
> > traffic to ASPs, but still implementation
> > dependent).
> > 
> >    Tolga
> > --- kakaul@hss.hns.com wrote:
> > >
> > >
> > >
> > >
> > > Hi Tolga,
> > >                      I want to clarify one more
> > > point that in n+k
> > > redundancy mode we are saying that n ASP's should
> > be
> > > active in SGP for the
> > > AS to handle AS traffic, but can you tell me are
> > we
> > > assuming that SGP
> > > handling entire traffic of AS is an high
> > processing
> > > machine with
> > > processing power of 3 ASP's.I think it is slightly
> > > unfair on SGP. We can
> > > also distribute traffic for AS among SGP's of SG
> > > which has active
> > > associations with three ASP's and allow
> > > implementations to load share
> > > traffic of AS not only among ASP's (of AS) but
> > > within SGP's of SG too.
> > >
> > > Regards
> > > Kamesh
> > >
> > >
> > >
> > >
> > > Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org
> > on
> > > 06/05/2003 05:53:51 PM
> > >
> > > Sent by:    sigtran-admin@ietf.org
> > >
> > >
> > > To:    sigtran@ietf.org
> > > cc:
> > >
> > > Subject:    Re: [Sigtran] M3UA : Multiple SGPs in
> > SG
> > >
> > >
> > > Hi Kamesh,
> > >
> > >
> > >              associations
> > >     | | | |    | | | |      | | | |
> > >    +---------+------------+-----------+
> > >    |   SGP1  |   SGP2     |   SGP3    |
> > >    ************************************
> > >    *              MTP3                *
> > >    *         |            |           *
> > >    * host1   |   host2    |  host3    *
> > >    ************************************
> > >      |   |       |     |       |    |
> > >      |   |       |     |       |    |
> > >                 Links
> > >
> > >
> > > Basically adjacent SS7 node is just aware that
> > there
> > > is a MTP3 peer and some links to communicate with
> > > it,
> > > and will probably loadshare traffic based on SLS
> > > betwen those links. Once the messages are inside
> > the
> > > SG-box, it is up to you, what to do with them (and
> > I
> > > would think although a lot of things inside SG are
> > > implementation dependent, there is no direct
> > mapping
> > > between links and SGPs)
> > >
> > > BTW, like you have said, it really migt be
> > possible
> > > to
> > > loadshare traffic between two ASPs, which are
> > ACTIVE
> > > for separate SGPs -and this also IMO would qualify
> > > as
> > > 2 ACTIVE ASPs because this is not two associations
> > > to
> > > the same ASP-, but I still think this might bring
> > > interoperability problems. To decide, when to
> > start
> > > traffic, IMO ASP and SGP should work in harmony.
> > So,
> > > IMO it is a good choice to leave the peers as SGP
> > > and
> > > ASP for ASPTM procedures.
> > >
> > > I also checked a sentence related with this topic
> > > -in
> > > ASP Active Procedures- in RFC, there it stands
> > that
> > 
> === message truncated ===
> 
> 
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 15:57:45 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10194
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 15:57:45 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56JvIJ24312
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 15:57:18 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56JuvB24287;
	Fri, 6 Jun 2003 15:56:57 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56JogB24097
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 15:50:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10058
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 15:50:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ONCe-0005pz-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 15:48:44 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[SZUJWzOazXOG+KzY+PrSW9qzjtIMMiWD])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ONCd-0005pV-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 15:48:43 -0400
Received: from ns.pigworks.openss7.net (IDENT:lve24JRQfm20Rs3aaxF9lN7s43v2VaNQ@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h56JocF07944;
	Fri, 6 Jun 2003 13:50:38 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h56JocI03575;
	Fri, 6 Jun 2003 13:50:38 -0600
Date: Fri, 6 Jun 2003 13:50:37 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
Message-ID: <20030606135037.B31671@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <OFC3E1ED80.CB07A9F9-ON65256D3D.005418AA@hss.hns.com> <20030606155913.37728.qmail@web12806.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030606155913.37728.qmail@web12806.mail.yahoo.com>; from tolga_asveren@yahoo.com on Fri, Jun 06, 2003 at 08:59:13AM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

This IG is wrong on this point from our last long
discussion.

Please correcct it.

--brian

Tolga Asveren wrote:                                                                 (Fri, 06 Jun 2003 08:59:13)
> Hi Kamesh,
> 
> In IG 3.15 there are some changes/clarifications
> related with n+k redundancy (those most probably will
> be reworked but I think we still can rely on
> INACTIVE->ACTIVE transition for AS state machine
> there-)
> In RFC3332 4.3.1 
> "The state of each remote ASP, in each AS that it is
> configured to operate, is maintained in the M3UA layer
> in the SGP."
> So, the AS state machine is kept in SGP -not SG wide-
> and IG does not change this.
> 
> Now, IMO, what you tell -just while counting number of
> ACTIVE ASPs for an AS acting SGwide but for the other
> ASPTM procedures still keeping per SGP approach- is
> not undoable, but not inline with current RFC/IG. 
> 
> IMO, cases, where this might be usefull will be
> probably very rare (I think, it is not a very high
> possibility that an association to an ASP1 can be
> formed from SGP1 and can't be formed from SGP2 and for
> ASP2 can be formed from SGP2 but can't be formed from
> SGP1, if they are part of the same SG) and I would
> think introducing a new configuration item for that is
> probably not worth. 
> Other opinions?
> 
>    Tolga 
> 
> --- kakaul@hss.hns.com wrote:
> > 
> > 
> > 
> > 
> > Hi Tolga,
> > 
> >  RFC does not say any thing about n+k redundancy as
> > you have pointed out in
> > your first response. I am
> >  attaching the lines from RFC from section 4.3.4.3
> > ASP Active Procedures:
> > "For the n+k redundancy case, ASPs which are in that
> > AS should
> >  coordinate among themselves the number of active
> > ASPs in the AS, and
> >  should start sending traffic only after n ASPs are
> > active.
> > 
> >  All ASPs within a loadsharing mode AS must be able
> > to process any
> >  Data message received for the AS, to accommodate
> > any potential
> >  failover or rebalancing of the offered load."
> > 
> > So if there is any interopability problem as you
> > have indicated by keeping
> > the RFC open ended then it should         be
> > addressed in the
> > implementation guide.I still believe that it is an
> > implementation issue and
> > can be resolved by configuring each AS and SG nodes
> > in one of the two ways
> > of n+k redundancy scope i.e specific to SG or SGP.
> > 
> > Regards
> > Kamesh
> > 
> > 
> > 
> > 
> > Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org on
> > 06/06/2003 04:35:03 PM
> > 
> > Sent by:    sigtran-admin@ietf.org
> > 
> > 
> > To:    sigtran@ietf.org
> > cc:
> > 
> > Subject:    Re: [Sigtran] M3UA : Multiple SGPs in SG
> > 
> > 
> > Hi Kamesh,
> > 
> > If we have to types of SGs (one, which activates
> > traffic based on number of ACTIVE ASPs per SGP and
> > the
> > other per SG), ASPs can't decide -at least based on
> > the current RFC- when to start/accept traffic. What
> > ASPs are supposed to do is coordinating number of
> > ACTIVE ASPs among the cluster, but if they don't
> > know,
> > whether the SG is deciding based on per SGP counter
> > or
> > not, there will be interoperability problems (for
> > example SG uses a global ACTIVE ASP counter and
> > starts
> > traffic but ASPs are counting per SGP, they probably
> > will drop arriving DATA).
> > 
> >     Tolga
> > --- kakaul@hss.hns.com wrote:
> > >
> > >
> > >
> > >
> > > Hi Tolga,
> > >                     I am of the openion that scope
> > > of n+k redundancy should
> > > depend on how one views and implements an SG. In
> > > figure given below if an
> > > implementation wants to reroute some AS traffic to
> > > its adjacent SGP on its
> > > way to AS it should be allowed.BTW as you have
> > also
> > > agreed that ASP1 and
> > > ASP2 also qualifies as two ASP's of AS if SGP1 and
> > > SGP2 has active
> > > associations with ASP1 and ASP2 respectively.SGP
> > may
> > > not want to block the
> > > traffic for AS if association between SGP1 and
> > ASP2
> > > is not active for AS
> > > assuming n = 2, k = 0(for n+k redundancy). I am
> > not
> > > able to understand what
> > > interopability issue will be involved in it.No
> > doubt
> > > limiting scope of n+k
> > > redundancy to SGP is clear and simple but some
> > > implementations may want to
> > > use inter SGP routing to route there traffic to
> > AS.
> > > So it ultimately
> > > depends on how you want your SG implementation to
> > > behave.
> > >
> > >
> > >                       SG
> > >                   +--------------+            AS
> > >                   |              |
> > > +---------+--+
> > >                   |              |        |
> > >   |
> > >                   | +--------+   |
> > > |+--------+  |
> > >                   | |        |   |        ||
> > > |  |
> > >                   | |  SGP1  *---+--------++ ASP1
> > > |  |
> > >                   | +--------+\  |
> > > |+--------+  |
> > >                   |    |         \        |
> > >   |
> > >   inter SGP  -----+----+         |        |
> > >   |
> > >   routing         |    |         |   \    |
> > >   |
> > >                   | +--------+   |     \
> > > |+--------+  |
> > >                   | |        |   |       \||
> > > |  |
> > >                   | | SGP2   +---+------ -*+  ASP2
> > > |  |
> > >                   | +--------+   |
> > > |+--------+  |
> > >                   |              |        |
> > >   |
> > >                   +--------------+
> > > +------------+
> > >
> > > Regards
> > > Kamesh
> > > Hughes Software Systems
> > >
> > >
> > >
> > >
> > > Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org
> > on
> > > 06/05/2003 07:40:28 PM
> > >
> > > Sent by:    sigtran-admin@ietf.org
> > >
> > >
> > > To:    sigtran@ietf.org
> > > cc:
> > >
> > > Subject:    Re: [Sigtran] M3UA : Multiple SGPs in
> > SG
> > >
> > >
> > > Hi Kamesh,
> > >
> > > IMO, it is a fair assumption for most of the cases
> > > that processing power for SG-side hosts is higher
> > > than
> > > of a single ASP (of course, still a configuration
> > > issue)
> > >
> > > For loadsharing on SG-side, for incoming traffic
> > > from
> > > SS7 there is already loadsharing among links, and
> > > links are residing on different hosts. So, I would
> > > think incoming traffic will be more or less evenly
> > > distributed among different hosts (and probably
> > you
> > > will first try the local SGP on that host to route
> > > the
> > > traffic to ASPs, but still implementation
> > > dependent).
> > >
> > >    Tolga
> > > --- kakaul@hss.hns.com wrote:
> > > >
> > > >
> > > >
> > > >
> > > > Hi Tolga,
> > > >                      I want to clarify one more
> > > > point that in n+k
> > > > redundancy mode we are saying that n ASP's
> > should
> > > be
> > > > active in SGP for the
> > > > AS to handle AS traffic, but can you tell me are
> > > we
> > > > assuming that SGP
> > > > handling entire traffic of AS is an high
> > > processing
> > 
> === message truncated ===
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
> http://calendar.yahoo.com
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 15:59:43 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10287
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 15:59:43 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56JxGd24457
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 15:59:16 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56JwtB24386;
	Fri, 6 Jun 2003 15:58:55 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56JpHB24130
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 15:51:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10070
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 15:51:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ONDD-0005qD-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 15:49:19 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[rvM13Y717xI0DCEYPj+Mib2d6hpA6PyZ])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ONDB-0005q3-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 15:49:18 -0400
Received: from ns.pigworks.openss7.net (IDENT:tvUPA6EOB4uXprPQWRyHVKpPDQMFdJi5@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h56JpDF07955;
	Fri, 6 Jun 2003 13:51:13 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h56JpC103582;
	Fri, 6 Jun 2003 13:51:12 -0600
Date: Fri, 6 Jun 2003 13:51:12 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
Message-ID: <20030606135112.C31671@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <ACEMIJONPBBPDLOKCABHMEIKCAAA.umesh@ccpu.com> <20030606164609.55947.qmail@web12803.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030606164609.55947.qmail@web12803.mail.yahoo.com>; from tolga_asveren@yahoo.com on Fri, Jun 06, 2003 at 09:46:09AM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

There was no such agreement.

--brian

Tolga Asveren wrote:                                                                 (Fri, 06 Jun 2003 09:46:09)
> Hi Umesh,
> --- Umesh Vats <umesh@ccpu.com> wrote:
> > Hi Tolga
> > 
> > The following text exists in implementor's guide.
> > 
> >                    "An SGP or IPSP, upon reception
> > of an ASP Active message
> > for the first
> >                     ASP in a Loadshare AS, SHOULD
> > NOT direct traffic to a
> > newly active
> >                     ASP until it determines that
> > there are sufficient
> > resources to handle
> >                     the expected load (e.g., until
> > there are "n" ASPs in
> > state ASP-ACTIVE
> >                     in the AS).  In this case, the
> > SGP or IPSP SHOULD
> > withhold the Notify
> >                     (AS-ACTIVE) until there are
> > sufficient resources."
> > 
> > On SG, n ASPs must be active for an AS to before an
> > AS is made active. It
> > doesn't
> > matter whether they went ACTIVE from the same SGP or
> > different SGPs.
> > 
> > Although the state of each remote ASP is maintained
> > in the AS, the overall
> > AS is
> > visible to whole SG. The following statement in RFC
> > 3332 helps :
> >  " Where an SG contains more than one SGP, the MTP3
> > routeset, SPMC and
> >    remote AS/ASP states of each SGP SHOULD be
> > coordinated across all the
> >    SGPs.  Rerouting of traffic between the SGPs MAY
> > also be supported."
> [TOLGA]This is the place I think a bit different.
> Please note the "MAY" in the last sentence. I think it
> was agreed not to use  a "SHOULD" here to not force
> internal routing. (BTW, I think even the "SHOULD" in
> the first sentence should be changed to "MAY")As I
> said, basically counting number of ACTIVE ASPs per SG
> will just introduce interoperability problems unless
> some modifications are introduced to the IG and
> considering that SGPs in a SG will most probably have
> the same IP connectivity, this IMO is not very usefull
> in real life. I personally would prefer the simple and
> clear way of having all ASPTM procedures per SGP.(for
> example do you like the idea of having ASPTM per SG
> instead of SGP?)
> > 
> > Similarly for ASP to SG traffic, the SGP to which
> > that ASP is connected
> > doesn't matter when
> > it has to decide about starting the traffic flow.
> > All ASPs should coordinate
> > among themselves if n ASP are ACTIVE for an AS or
> > not.
> [TOLGA]If what you mean is, that it really does not
> matter for which SGP ASPs went ACTIVE, I disagree, at
> least SG, SGP is part of should matter. Apart from
> this, although the sentence might be not very clear in
> the context of this discussion, the intention was to
> coordinate number of ACTIVE ASPs for each SGP
> separetly. Maybe a clarification might be added to IG.
> > 
> > "For the n+k redundancy case, ASPs which are in that
> > AS should
> >    coordinate among themselves the number of active
> > ASPs in the AS, and
> >    should start sending traffic only after n ASPs
> > are active."
> > 
> > rgds
> > Umesh
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > -----Original Message-----
> > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Tolga Asveren
> > Sent: Friday, June 06, 2003 8:59 AM
> > To: sigtran@ietf.org
> > Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
> > 
> > 
> > Hi Kamesh,
> > 
> > In IG 3.15 there are some changes/clarifications
> > related with n+k redundancy (those most probably
> > will
> > be reworked but I think we still can rely on
> > INACTIVE->ACTIVE transition for AS state machine
> > there-)
> > In RFC3332 4.3.1
> > "The state of each remote ASP, in each AS that it is
> > configured to operate, is maintained in the M3UA
> > layer
> > in the SGP."
> > So, the AS state machine is kept in SGP -not SG
> > wide-
> > and IG does not change this.
> > 
> > Now, IMO, what you tell -just while counting number
> > of
> > ACTIVE ASPs for an AS acting SGwide but for the
> > other
> > ASPTM procedures still keeping per SGP approach- is
> > not undoable, but not inline with current RFC/IG.
> > 
> > IMO, cases, where this might be usefull will be
> > probably very rare (I think, it is not a very high
> > possibility that an association to an ASP1 can be
> > formed from SGP1 and can't be formed from SGP2 and
> > for
> > ASP2 can be formed from SGP2 but can't be formed
> > from
> > SGP1, if they are part of the same SG) and I would
> > think introducing a new configuration item for that
> > is
> > probably not worth.
> > Other opinions?
> > 
> >    Tolga
> > 
> > --- kakaul@hss.hns.com wrote:
> > >
> > >
> > >
> > >
> > > Hi Tolga,
> > >
> > >  RFC does not say any thing about n+k redundancy
> > as
> > > you have pointed out in
> > > your first response. I am
> > >  attaching the lines from RFC from section 4.3.4.3
> > > ASP Active Procedures:
> > > "For the n+k redundancy case, ASPs which are in
> > that
> > > AS should
> > >  coordinate among themselves the number of active
> > > ASPs in the AS, and
> > >  should start sending traffic only after n ASPs
> > are
> > > active.
> > >
> > >  All ASPs within a loadsharing mode AS must be
> > able
> > > to process any
> > >  Data message received for the AS, to accommodate
> > > any potential
> > >  failover or rebalancing of the offered load."
> > >
> > > So if there is any interopability problem as you
> > > have indicated by keeping
> > > the RFC open ended then it should         be
> > > addressed in the
> > > implementation guide.I still believe that it is an
> > > implementation issue and
> > > can be resolved by configuring each AS and SG
> > nodes
> > > in one of the two ways
> > > of n+k redundancy scope i.e specific to SG or SGP.
> > >
> > > Regards
> > > Kamesh
> > >
> > >
> > >
> > >
> > > Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org
> > on
> > > 06/06/2003 04:35:03 PM
> > >
> > > Sent by:    sigtran-admin@ietf.org
> > >
> > >
> > > To:    sigtran@ietf.org
> > > cc:
> > >
> > > Subject:    Re: [Sigtran] M3UA : Multiple SGPs in
> > SG
> > >
> > >
> > > Hi Kamesh,
> > >
> > > If we have to types of SGs (one, which activates
> > > traffic based on number of ACTIVE ASPs per SGP and
> > > the
> > > other per SG), ASPs can't decide -at least based
> > on
> > > the current RFC- when to start/accept traffic.
> > What
> > > ASPs are supposed to do is coordinating number of
> > > ACTIVE ASPs among the cluster, but if they don't
> > > know,
> > > whether the SG is deciding based on per SGP
> > counter
> > > or
> > > not, there will be interoperability problems (for
> > > example SG uses a global ACTIVE ASP counter and
> > > starts
> > > traffic but ASPs are counting per SGP, they
> > probably
> > > will drop arriving DATA).
> > >
> > >     Tolga
> > > --- kakaul@hss.hns.com wrote:
> > > >
> > > >
> > > >
> > > >
> > > > Hi Tolga,
> > 
> === message truncated ===
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
> http://calendar.yahoo.com
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 16:11:47 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10860
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 16:11:47 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56KBKh25914
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 16:11:20 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56KAvB25882;
	Fri, 6 Jun 2003 16:10:57 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56K4vB24725
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 16:04:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10450
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 16:04:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ONQR-0005vF-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 16:02:59 -0400
Received: from web12804.mail.yahoo.com ([216.136.174.39])
	by ietf-mx with smtp (Exim 4.12)
	id 19ONQQ-0005vC-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 16:02:58 -0400
Message-ID: <20030606200452.19009.qmail@web12804.mail.yahoo.com>
Received: from [208.255.120.2] by web12804.mail.yahoo.com via HTTP; Fri, 06 Jun 2003 13:04:52 PDT
Date: Fri, 6 Jun 2003 13:04:52 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
To: sigtran@ietf.org
In-Reply-To: <20030606134912.A31671@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,

I think it was clear what I mean with "starting",
allowing traffic for a specific AS to ASP direction
from SGP. 
BTW, related with this topic -I assume you refer to
the following sentence at the bottom of page 33 in IG:
"An SGP or IPSP, upon reception of an ASP Active
message for the first ASP in a Loadshare AS, SHOULD
NOT direct traffic to a newly active ASP until it
determines that there are sufficient resources to
handle the expected load (e.g., until there are "n"
ASPs in state ASP-ACTIVE in the AS)."
To my understanding, there was no consensus to change
"SHOULD NOT" to "MAY".
(And if there is such a consensus in the future, I
would think we should also allow for the n=1 case to
route DATA from SGPs to INACTIVE ASPs)

   Tolga 
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Tolga,
> 
> SGs cannot "start" traffic.  They are not the
> stimulus.
> The remote signalling points must start traffic in
> response to a user part test and it will take a
> significant
> amount of time before any traffic flows.
> 
> But we've discussed this before....
> 
> What I can't understand is why the IG hasn't been
> corrected yet.
> 
> --brian
> 
> Tolga Asveren wrote:                                
>                                 (Fri, 06 Jun 2003
> 04:05:03)
> > Hi Kamesh,
> > 
> > If we have to types of SGs (one, which activates
> > traffic based on number of ACTIVE ASPs per SGP and
> the
> > other per SG), ASPs can't decide -at least based
> on
> > the current RFC- when to start/accept traffic.
> What
> > ASPs are supposed to do is coordinating number of
> > ACTIVE ASPs among the cluster, but if they don't
> know,
> > whether the SG is deciding based on per SGP
> counter or
> > not, there will be interoperability problems (for
> > example SG uses a global ACTIVE ASP counter and
> starts
> > traffic but ASPs are counting per SGP, they
> probably
> > will drop arriving DATA). 
> > 
> >     Tolga
> > --- kakaul@hss.hns.com wrote:
> > > 
> > > 
> > > 
> > > 
> > > Hi Tolga,
> > >                     I am of the openion that
> scope
> > > of n+k redundancy should
> > > depend on how one views and implements an SG. In
> > > figure given below if an
> > > implementation wants to reroute some AS traffic
> to
> > > its adjacent SGP on its
> > > way to AS it should be allowed.BTW as you have
> also
> > > agreed that ASP1 and
> > > ASP2 also qualifies as two ASP's of AS if SGP1
> and
> > > SGP2 has active
> > > associations with ASP1 and ASP2 respectively.SGP
> may
> > > not want to block the
> > > traffic for AS if association between SGP1 and
> ASP2
> > > is not active for AS
> > > assuming n = 2, k = 0(for n+k redundancy). I am
> not
> > > able to understand what
> > > interopability issue will be involved in it.No
> doubt
> > > limiting scope of n+k
> > > redundancy to SGP is clear and simple but some
> > > implementations may want to
> > > use inter SGP routing to route there traffic to
> AS.
> > > So it ultimately
> > > depends on how you want your SG implementation
> to
> > > behave.
> > > 
> > > 
> > >                       SG
> > >                   +--------------+            AS
> > >                   |              |       
> > > +---------+--+
> > >                   |              |        |     
>    
> > >   |
> > >                   | +--------+   |       
> > > |+--------+  |
> > >                   | |        |   |        ||    
>   
> > > |  |
> > >                   | |  SGP1  *---+--------++
> ASP1  
> > > |  |
> > >                   | +--------+\  |       
> > > |+--------+  |
> > >                   |    |         \        |     
>    
> > >   |
> > >   inter SGP  -----+----+         |        |     
>    
> > >   |
> > >   routing         |    |         |   \    |     
>    
> > >   |
> > >                   | +--------+   |     \ 
> > > |+--------+  |
> > >                   | |        |   |       \||    
>   
> > > |  |
> > >                   | | SGP2   +---+------ -*+ 
> ASP2 
> > > |  |
> > >                   | +--------+   |       
> > > |+--------+  |
> > >                   |              |        |     
>    
> > >   |
> > >                   +--------------+       
> > > +------------+
> > > 
> > > Regards
> > > Kamesh
> > > Hughes Software Systems
> > > 
> > > 
> > > 
> > > 
> > > Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org
> on
> > > 06/05/2003 07:40:28 PM
> > > 
> > > Sent by:    sigtran-admin@ietf.org
> > > 
> > > 
> > > To:    sigtran@ietf.org
> > > cc:
> > > 
> > > Subject:    Re: [Sigtran] M3UA : Multiple SGPs
> in SG
> > > 
> > > 
> > > Hi Kamesh,
> > > 
> > > IMO, it is a fair assumption for most of the
> cases
> > > that processing power for SG-side hosts is
> higher
> > > than
> > > of a single ASP (of course, still a
> configuration
> > > issue)
> > > 
> > > For loadsharing on SG-side, for incoming traffic
> > > from
> > > SS7 there is already loadsharing among links,
> and
> > > links are residing on different hosts. So, I
> would
> > > think incoming traffic will be more or less
> evenly
> > > distributed among different hosts (and probably
> you
> > > will first try the local SGP on that host to
> route
> > > the
> > > traffic to ASPs, but still implementation
> > > dependent).
> > > 
> > >    Tolga
> > > --- kakaul@hss.hns.com wrote:
> > > >
> > > >
> > > >
> > > >
> > > > Hi Tolga,
> > > >                      I want to clarify one
> more
> > > > point that in n+k
> > > > redundancy mode we are saying that n ASP's
> should
> > > be
> > > > active in SGP for the
> > > > AS to handle AS traffic, but can you tell me
> are
> > > we
> > > > assuming that SGP
> > > > handling entire traffic of AS is an high
> > > processing
> > > > machine with
> > > > processing power of 3 ASP's.I think it is
> slightly
> > > > unfair on SGP. We can
> > > > also distribute traffic for AS among SGP's of
> SG
> > > > which has active
> > > > associations with three ASP's and allow
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 16:13:42 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10903
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 16:13:42 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56KDFg25997
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 16:13:15 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56KCrB25977;
	Fri, 6 Jun 2003 16:12:53 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56K6KB24839
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 16:06:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10549
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 16:06:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ONRm-0005wL-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 16:04:22 -0400
Received: from web12806.mail.yahoo.com ([216.136.174.41])
	by ietf-mx with smtp (Exim 4.12)
	id 19ONRl-0005w3-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 16:04:21 -0400
Message-ID: <20030606200608.81918.qmail@web12806.mail.yahoo.com>
Received: from [208.255.120.2] by web12806.mail.yahoo.com via HTTP; Fri, 06 Jun 2003 13:06:08 PDT
Date: Fri, 6 Jun 2003 13:06:08 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
To: sigtran@ietf.org
In-Reply-To: <20030606135112.C31671@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Tolga,
> 
> There was no such agreement.
[TOLGA]If so, why is it a "MAY" in RFC?
> 
> --brian
> 
> Tolga Asveren wrote:                                
>                                 (Fri, 06 Jun 2003
> 09:46:09)
> > Hi Umesh,
> > --- Umesh Vats <umesh@ccpu.com> wrote:
> > > Hi Tolga
> > > 
> > > The following text exists in implementor's
> guide.
> > > 
> > >                    "An SGP or IPSP, upon
> reception
> > > of an ASP Active message
> > > for the first
> > >                     ASP in a Loadshare AS,
> SHOULD
> > > NOT direct traffic to a
> > > newly active
> > >                     ASP until it determines that
> > > there are sufficient
> > > resources to handle
> > >                     the expected load (e.g.,
> until
> > > there are "n" ASPs in
> > > state ASP-ACTIVE
> > >                     in the AS).  In this case,
> the
> > > SGP or IPSP SHOULD
> > > withhold the Notify
> > >                     (AS-ACTIVE) until there are
> > > sufficient resources."
> > > 
> > > On SG, n ASPs must be active for an AS to before
> an
> > > AS is made active. It
> > > doesn't
> > > matter whether they went ACTIVE from the same
> SGP or
> > > different SGPs.
> > > 
> > > Although the state of each remote ASP is
> maintained
> > > in the AS, the overall
> > > AS is
> > > visible to whole SG. The following statement in
> RFC
> > > 3332 helps :
> > >  " Where an SG contains more than one SGP, the
> MTP3
> > > routeset, SPMC and
> > >    remote AS/ASP states of each SGP SHOULD be
> > > coordinated across all the
> > >    SGPs.  Rerouting of traffic between the SGPs
> MAY
> > > also be supported."
> > [TOLGA]This is the place I think a bit different.
> > Please note the "MAY" in the last sentence. I
> think it
> > was agreed not to use  a "SHOULD" here to not
> force
> > internal routing. (BTW, I think even the "SHOULD"
> in
> > the first sentence should be changed to "MAY")As I
> > said, basically counting number of ACTIVE ASPs per
> SG
> > will just introduce interoperability problems
> unless
> > some modifications are introduced to the IG and
> > considering that SGPs in a SG will most probably
> have
> > the same IP connectivity, this IMO is not very
> usefull
> > in real life. I personally would prefer the simple
> and
> > clear way of having all ASPTM procedures per
> SGP.(for
> > example do you like the idea of having ASPTM per
> SG
> > instead of SGP?)
> > > 
> > > Similarly for ASP to SG traffic, the SGP to
> which
> > > that ASP is connected
> > > doesn't matter when
> > > it has to decide about starting the traffic
> flow.
> > > All ASPs should coordinate
> > > among themselves if n ASP are ACTIVE for an AS
> or
> > > not.
> > [TOLGA]If what you mean is, that it really does
> not
> > matter for which SGP ASPs went ACTIVE, I disagree,
> at
> > least SG, SGP is part of should matter. Apart from
> > this, although the sentence might be not very
> clear in
> > the context of this discussion, the intention was
> to
> > coordinate number of ACTIVE ASPs for each SGP
> > separetly. Maybe a clarification might be added to
> IG.
> > > 
> > > "For the n+k redundancy case, ASPs which are in
> that
> > > AS should
> > >    coordinate among themselves the number of
> active
> > > ASPs in the AS, and
> > >    should start sending traffic only after n
> ASPs
> > > are active."
> > > 
> > > rgds
> > > Umesh
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org
> > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > Tolga Asveren
> > > Sent: Friday, June 06, 2003 8:59 AM
> > > To: sigtran@ietf.org
> > > Subject: Re: [Sigtran] M3UA : Multiple SGPs in
> SG
> > > 
> > > 
> > > Hi Kamesh,
> > > 
> > > In IG 3.15 there are some changes/clarifications
> > > related with n+k redundancy (those most probably
> > > will
> > > be reworked but I think we still can rely on
> > > INACTIVE->ACTIVE transition for AS state machine
> > > there-)
> > > In RFC3332 4.3.1
> > > "The state of each remote ASP, in each AS that
> it is
> > > configured to operate, is maintained in the M3UA
> > > layer
> > > in the SGP."
> > > So, the AS state machine is kept in SGP -not SG
> > > wide-
> > > and IG does not change this.
> > > 
> > > Now, IMO, what you tell -just while counting
> number
> > > of
> > > ACTIVE ASPs for an AS acting SGwide but for the
> > > other
> > > ASPTM procedures still keeping per SGP approach-
> is
> > > not undoable, but not inline with current
> RFC/IG.
> > > 
> > > IMO, cases, where this might be usefull will be
> > > probably very rare (I think, it is not a very
> high
> > > possibility that an association to an ASP1 can
> be
> > > formed from SGP1 and can't be formed from SGP2
> and
> > > for
> > > ASP2 can be formed from SGP2 but can't be formed
> > > from
> > > SGP1, if they are part of the same SG) and I
> would
> > > think introducing a new configuration item for
> that
> > > is
> > > probably not worth.
> > > Other opinions?
> > > 
> > >    Tolga
> > > 
> > > --- kakaul@hss.hns.com wrote:
> > > >
> > > >
> > > >
> > > >
> > > > Hi Tolga,
> > > >
> > > >  RFC does not say any thing about n+k
> redundancy
> > > as
> > > > you have pointed out in
> > > > your first response. I am
> > > >  attaching the lines from RFC from section
> 4.3.4.3
> > > > ASP Active Procedures:
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 16:16:38 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10990
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 16:16:38 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56KGBO26179
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 16:16:11 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56KFiB26147;
	Fri, 6 Jun 2003 16:15:44 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56K7qB25757
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 16:07:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10794
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 16:07:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ONTG-00060Z-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 16:05:54 -0400
Received: from web12801.mail.yahoo.com ([216.136.174.36])
	by ietf-mx with smtp (Exim 4.12)
	id 19ONTF-00060W-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 16:05:53 -0400
Message-ID: <20030606200747.87018.qmail@web12801.mail.yahoo.com>
Received: from [208.255.120.2] by web12801.mail.yahoo.com via HTTP; Fri, 06 Jun 2003 13:07:47 PDT
Date: Fri, 6 Jun 2003 13:07:47 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
To: sigtran@ietf.org
In-Reply-To: <20030606135037.B31671@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,

To my understanding, there was no consensus to change
the current INACTIVE to ACTIVE transition in IG for
n+k case.

    Tolga
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Tolga,
> 
> This IG is wrong on this point from our last long
> discussion.
> 
> Please correcct it.
> 
> --brian
> 
> Tolga Asveren wrote:                                
>                                 (Fri, 06 Jun 2003
> 08:59:13)
> > Hi Kamesh,
> > 
> > In IG 3.15 there are some changes/clarifications
> > related with n+k redundancy (those most probably
> will
> > be reworked but I think we still can rely on
> > INACTIVE->ACTIVE transition for AS state machine
> > there-)
> > In RFC3332 4.3.1 
> > "The state of each remote ASP, in each AS that it
> is
> > configured to operate, is maintained in the M3UA
> layer
> > in the SGP."
> > So, the AS state machine is kept in SGP -not SG
> wide-
> > and IG does not change this.
> > 
> > Now, IMO, what you tell -just while counting
> number of
> > ACTIVE ASPs for an AS acting SGwide but for the
> other
> > ASPTM procedures still keeping per SGP approach-
> is
> > not undoable, but not inline with current RFC/IG. 
> > 
> > IMO, cases, where this might be usefull will be
> > probably very rare (I think, it is not a very high
> > possibility that an association to an ASP1 can be
> > formed from SGP1 and can't be formed from SGP2 and
> for
> > ASP2 can be formed from SGP2 but can't be formed
> from
> > SGP1, if they are part of the same SG) and I would
> > think introducing a new configuration item for
> that is
> > probably not worth. 
> > Other opinions?
> > 
> >    Tolga 
> > 
> > --- kakaul@hss.hns.com wrote:
> > > 
> > > 
> > > 
> > > 
> > > Hi Tolga,
> > > 
> > >  RFC does not say any thing about n+k redundancy
> as
> > > you have pointed out in
> > > your first response. I am
> > >  attaching the lines from RFC from section
> 4.3.4.3
> > > ASP Active Procedures:
> > > "For the n+k redundancy case, ASPs which are in
> that
> > > AS should
> > >  coordinate among themselves the number of
> active
> > > ASPs in the AS, and
> > >  should start sending traffic only after n ASPs
> are
> > > active.
> > > 
> > >  All ASPs within a loadsharing mode AS must be
> able
> > > to process any
> > >  Data message received for the AS, to
> accommodate
> > > any potential
> > >  failover or rebalancing of the offered load."
> > > 
> > > So if there is any interopability problem as you
> > > have indicated by keeping
> > > the RFC open ended then it should         be
> > > addressed in the
> > > implementation guide.I still believe that it is
> an
> > > implementation issue and
> > > can be resolved by configuring each AS and SG
> nodes
> > > in one of the two ways
> > > of n+k redundancy scope i.e specific to SG or
> SGP.
> > > 
> > > Regards
> > > Kamesh
> > > 
> > > 
> > > 
> > > 
> > > Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org
> on
> > > 06/06/2003 04:35:03 PM
> > > 
> > > Sent by:    sigtran-admin@ietf.org
> > > 
> > > 
> > > To:    sigtran@ietf.org
> > > cc:
> > > 
> > > Subject:    Re: [Sigtran] M3UA : Multiple SGPs
> in SG
> > > 
> > > 
> > > Hi Kamesh,
> > > 
> > > If we have to types of SGs (one, which activates
> > > traffic based on number of ACTIVE ASPs per SGP
> and
> > > the
> > > other per SG), ASPs can't decide -at least based
> on
> > > the current RFC- when to start/accept traffic.
> What
> > > ASPs are supposed to do is coordinating number
> of
> > > ACTIVE ASPs among the cluster, but if they don't
> > > know,
> > > whether the SG is deciding based on per SGP
> counter
> > > or
> > > not, there will be interoperability problems
> (for
> > > example SG uses a global ACTIVE ASP counter and
> > > starts
> > > traffic but ASPs are counting per SGP, they
> probably
> > > will drop arriving DATA).
> > > 
> > >     Tolga
> > > --- kakaul@hss.hns.com wrote:
> > > >
> > > >
> > > >
> > > >
> > > > Hi Tolga,
> > > >                     I am of the openion that
> scope
> > > > of n+k redundancy should
> > > > depend on how one views and implements an SG.
> In
> > > > figure given below if an
> > > > implementation wants to reroute some AS
> traffic to
> > > > its adjacent SGP on its
> > > > way to AS it should be allowed.BTW as you have
> > > also
> > > > agreed that ASP1 and
> > > > ASP2 also qualifies as two ASP's of AS if SGP1
> and
> > > > SGP2 has active
> > > > associations with ASP1 and ASP2
> respectively.SGP
> > > may
> > > > not want to block the
> > > > traffic for AS if association between SGP1 and
> > > ASP2
> > > > is not active for AS
> > > > assuming n = 2, k = 0(for n+k redundancy). I
> am
> > > not
> > > > able to understand what
> > > > interopability issue will be involved in it.No
> > > doubt
> > > > limiting scope of n+k
> > > > redundancy to SGP is clear and simple but some
> > > > implementations may want to
> > > > use inter SGP routing to route there traffic
> to
> > > AS.
> > > > So it ultimately
> > > > depends on how you want your SG implementation
> to
> > > > behave.
> > > >
> > > >
> > > >                       SG
> > > >                   +--------------+           
> AS
> > > >                   |              |
> > > > +---------+--+
> > > >                   |              |        |
> > > >   |
> > > >                   | +--------+   |
> > > > |+--------+  |
> > > >                   | |        |   |        ||
> > > > |  |
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 16:30:45 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11467
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 16:30:45 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56KUIf26991
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 16:30:18 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56KTtB26874;
	Fri, 6 Jun 2003 16:29:55 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56KRGB26759
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 16:27:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11373
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 16:27:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ONm3-0006Ao-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 16:25:19 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[eYSF4pVlxecB7vKcyPxbVgHMW5gnWToR])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ONm2-0006Al-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 16:25:18 -0400
Received: from ns.pigworks.openss7.net (IDENT:6u6am0C4LSpPX7kahlQX9p+xQeXYapap@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h56KRCF08472;
	Fri, 6 Jun 2003 14:27:12 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h56KRBC04162;
	Fri, 6 Jun 2003 14:27:11 -0600
Date: Fri, 6 Jun 2003 14:27:11 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
Message-ID: <20030606142711.E31671@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030606134912.A31671@openss7.org> <20030606200452.19009.qmail@web12804.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030606200452.19009.qmail@web12804.mail.yahoo.com>; from tolga_asveren@yahoo.com on Fri, Jun 06, 2003 at 01:04:52PM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

There was concensus to interpret n as maximum
engineered load and to remove the section from
the IG.

--brian

Tolga Asveren wrote:                                                                 (Fri, 06 Jun 2003 13:04:52)
> Brian,
> 
> I think it was clear what I mean with "starting",
> allowing traffic for a specific AS to ASP direction
> from SGP. 
> BTW, related with this topic -I assume you refer to
> the following sentence at the bottom of page 33 in IG:
> "An SGP or IPSP, upon reception of an ASP Active
> message for the first ASP in a Loadshare AS, SHOULD
> NOT direct traffic to a newly active ASP until it
> determines that there are sufficient resources to
> handle the expected load (e.g., until there are "n"
> ASPs in state ASP-ACTIVE in the AS)."
> To my understanding, there was no consensus to change
> "SHOULD NOT" to "MAY".
> (And if there is such a consensus in the future, I
> would think we should also allow for the n=1 case to
> route DATA from SGPs to INACTIVE ASPs)
> 
>    Tolga 
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > SGs cannot "start" traffic.  They are not the
> > stimulus.
> > The remote signalling points must start traffic in
> > response to a user part test and it will take a
> > significant
> > amount of time before any traffic flows.
> > 
> > But we've discussed this before....
> > 
> > What I can't understand is why the IG hasn't been
> > corrected yet.
> > 
> > --brian
> > 
> > Tolga Asveren wrote:                                
> >                                 (Fri, 06 Jun 2003
> > 04:05:03)
> > > Hi Kamesh,
> > > 
> > > If we have to types of SGs (one, which activates
> > > traffic based on number of ACTIVE ASPs per SGP and
> > the
> > > other per SG), ASPs can't decide -at least based
> > on
> > > the current RFC- when to start/accept traffic.
> > What
> > > ASPs are supposed to do is coordinating number of
> > > ACTIVE ASPs among the cluster, but if they don't
> > know,
> > > whether the SG is deciding based on per SGP
> > counter or
> > > not, there will be interoperability problems (for
> > > example SG uses a global ACTIVE ASP counter and
> > starts
> > > traffic but ASPs are counting per SGP, they
> > probably
> > > will drop arriving DATA). 
> > > 
> > >     Tolga
> > > --- kakaul@hss.hns.com wrote:
> > > > 
> > > > 
> > > > 
> > > > 
> > > > Hi Tolga,
> > > >                     I am of the openion that
> > scope
> > > > of n+k redundancy should
> > > > depend on how one views and implements an SG. In
> > > > figure given below if an
> > > > implementation wants to reroute some AS traffic
> > to
> > > > its adjacent SGP on its
> > > > way to AS it should be allowed.BTW as you have
> > also
> > > > agreed that ASP1 and
> > > > ASP2 also qualifies as two ASP's of AS if SGP1
> > and
> > > > SGP2 has active
> > > > associations with ASP1 and ASP2 respectively.SGP
> > may
> > > > not want to block the
> > > > traffic for AS if association between SGP1 and
> > ASP2
> > > > is not active for AS
> > > > assuming n = 2, k = 0(for n+k redundancy). I am
> > not
> > > > able to understand what
> > > > interopability issue will be involved in it.No
> > doubt
> > > > limiting scope of n+k
> > > > redundancy to SGP is clear and simple but some
> > > > implementations may want to
> > > > use inter SGP routing to route there traffic to
> > AS.
> > > > So it ultimately
> > > > depends on how you want your SG implementation
> > to
> > > > behave.
> > > > 
> > > > 
> > > >                       SG
> > > >                   +--------------+            AS
> > > >                   |              |       
> > > > +---------+--+
> > > >                   |              |        |     
> >    
> > > >   |
> > > >                   | +--------+   |       
> > > > |+--------+  |
> > > >                   | |        |   |        ||    
> >   
> > > > |  |
> > > >                   | |  SGP1  *---+--------++
> > ASP1  
> > > > |  |
> > > >                   | +--------+\  |       
> > > > |+--------+  |
> > > >                   |    |         \        |     
> >    
> > > >   |
> > > >   inter SGP  -----+----+         |        |     
> >    
> > > >   |
> > > >   routing         |    |         |   \    |     
> >    
> > > >   |
> > > >                   | +--------+   |     \ 
> > > > |+--------+  |
> > > >                   | |        |   |       \||    
> >   
> > > > |  |
> > > >                   | | SGP2   +---+------ -*+ 
> > ASP2 
> > > > |  |
> > > >                   | +--------+   |       
> > > > |+--------+  |
> > > >                   |              |        |     
> >    
> > > >   |
> > > >                   +--------------+       
> > > > +------------+
> > > > 
> > > > Regards
> > > > Kamesh
> > > > Hughes Software Systems
> > > > 
> > > > 
> > > > 
> > > > 
> > > > Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org
> > on
> > > > 06/05/2003 07:40:28 PM
> > > > 
> > > > Sent by:    sigtran-admin@ietf.org
> > > > 
> > > > 
> > > > To:    sigtran@ietf.org
> > > > cc:
> > > > 
> > > > Subject:    Re: [Sigtran] M3UA : Multiple SGPs
> > in SG
> > > > 
> > > > 
> > > > Hi Kamesh,
> > > > 
> > > > IMO, it is a fair assumption for most of the
> > cases
> > > > that processing power for SG-side hosts is
> > higher
> > > > than
> > > > of a single ASP (of course, still a
> > configuration
> > > > issue)
> > > > 
> > > > For loadsharing on SG-side, for incoming traffic
> > > > from
> > > > SS7 there is already loadsharing among links,
> > and
> > > > links are residing on different hosts. So, I
> > would
> > > > think incoming traffic will be more or less
> > evenly
> > > > distributed among different hosts (and probably
> > you
> > > > will first try the local SGP on that host to
> > route
> > > > the
> > > > traffic to ASPs, but still implementation
> > > > dependent).
> > > > 
> > > >    Tolga
> > > > --- kakaul@hss.hns.com wrote:
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Hi Tolga,
> > > > >                      I want to clarify one
> > more
> > > > > point that in n+k
> > > > > redundancy mode we are saying that n ASP's
> > should
> > > > be
> > > > > active in SGP for the
> > > > > AS to handle AS traffic, but can you tell me
> > are
> > > > we
> > > > > assuming that SGP
> > > > > handling entire traffic of AS is an high
> > > > processing
> > > > > machine with
> > > > > processing power of 3 ASP's.I think it is
> > slightly
> > > > > unfair on SGP. We can
> > > > > also distribute traffic for AS among SGP's of
> > SG
> > > > > which has active
> > > > > associations with three ASP's and allow
> > 
> === message truncated ===
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
> http://calendar.yahoo.com
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 16:32:49 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11528
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 16:32:49 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56KWMv27098
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 16:32:22 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56KVpB27078;
	Fri, 6 Jun 2003 16:31:51 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56KSXB26803
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 16:28:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11393
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 16:28:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ONnH-0006BX-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 16:26:35 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[j1lpz0NomtEVACGHXdAnEDzCwg55Ba1D])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ONnG-0006BU-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 16:26:34 -0400
Received: from ns.pigworks.openss7.net (IDENT:rcfan8/Yg/x2wjoSvG7gxTbspgbajbRu@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h56KSSF08486;
	Fri, 6 Jun 2003 14:28:28 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h56KSSl04183;
	Fri, 6 Jun 2003 14:28:28 -0600
Date: Fri, 6 Jun 2003 14:28:27 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
Message-ID: <20030606142827.F31671@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030606135112.C31671@openss7.org> <20030606200608.81918.qmail@web12806.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030606200608.81918.qmail@web12806.mail.yahoo.com>; from tolga_asveren@yahoo.com on Fri, Jun 06, 2003 at 01:06:08PM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

Because the RFC represents the concensus and the
IG currently goes against concensus.  That section
of the IG thay you and Javier dreamed up needs to
be deleted.

--brian


Tolga Asveren wrote:                                                                 (Fri, 06 Jun 2003 13:06:08)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > There was no such agreement.
> [TOLGA]If so, why is it a "MAY" in RFC?
> > 
> > --brian
> > 
> > Tolga Asveren wrote:                                
> >                                 (Fri, 06 Jun 2003
> > 09:46:09)
> > > Hi Umesh,
> > > --- Umesh Vats <umesh@ccpu.com> wrote:
> > > > Hi Tolga
> > > > 
> > > > The following text exists in implementor's
> > guide.
> > > > 
> > > >                    "An SGP or IPSP, upon
> > reception
> > > > of an ASP Active message
> > > > for the first
> > > >                     ASP in a Loadshare AS,
> > SHOULD
> > > > NOT direct traffic to a
> > > > newly active
> > > >                     ASP until it determines that
> > > > there are sufficient
> > > > resources to handle
> > > >                     the expected load (e.g.,
> > until
> > > > there are "n" ASPs in
> > > > state ASP-ACTIVE
> > > >                     in the AS).  In this case,
> > the
> > > > SGP or IPSP SHOULD
> > > > withhold the Notify
> > > >                     (AS-ACTIVE) until there are
> > > > sufficient resources."
> > > > 
> > > > On SG, n ASPs must be active for an AS to before
> > an
> > > > AS is made active. It
> > > > doesn't
> > > > matter whether they went ACTIVE from the same
> > SGP or
> > > > different SGPs.
> > > > 
> > > > Although the state of each remote ASP is
> > maintained
> > > > in the AS, the overall
> > > > AS is
> > > > visible to whole SG. The following statement in
> > RFC
> > > > 3332 helps :
> > > >  " Where an SG contains more than one SGP, the
> > MTP3
> > > > routeset, SPMC and
> > > >    remote AS/ASP states of each SGP SHOULD be
> > > > coordinated across all the
> > > >    SGPs.  Rerouting of traffic between the SGPs
> > MAY
> > > > also be supported."
> > > [TOLGA]This is the place I think a bit different.
> > > Please note the "MAY" in the last sentence. I
> > think it
> > > was agreed not to use  a "SHOULD" here to not
> > force
> > > internal routing. (BTW, I think even the "SHOULD"
> > in
> > > the first sentence should be changed to "MAY")As I
> > > said, basically counting number of ACTIVE ASPs per
> > SG
> > > will just introduce interoperability problems
> > unless
> > > some modifications are introduced to the IG and
> > > considering that SGPs in a SG will most probably
> > have
> > > the same IP connectivity, this IMO is not very
> > usefull
> > > in real life. I personally would prefer the simple
> > and
> > > clear way of having all ASPTM procedures per
> > SGP.(for
> > > example do you like the idea of having ASPTM per
> > SG
> > > instead of SGP?)
> > > > 
> > > > Similarly for ASP to SG traffic, the SGP to
> > which
> > > > that ASP is connected
> > > > doesn't matter when
> > > > it has to decide about starting the traffic
> > flow.
> > > > All ASPs should coordinate
> > > > among themselves if n ASP are ACTIVE for an AS
> > or
> > > > not.
> > > [TOLGA]If what you mean is, that it really does
> > not
> > > matter for which SGP ASPs went ACTIVE, I disagree,
> > at
> > > least SG, SGP is part of should matter. Apart from
> > > this, although the sentence might be not very
> > clear in
> > > the context of this discussion, the intention was
> > to
> > > coordinate number of ACTIVE ASPs for each SGP
> > > separetly. Maybe a clarification might be added to
> > IG.
> > > > 
> > > > "For the n+k redundancy case, ASPs which are in
> > that
> > > > AS should
> > > >    coordinate among themselves the number of
> > active
> > > > ASPs in the AS, and
> > > >    should start sending traffic only after n
> > ASPs
> > > > are active."
> > > > 
> > > > rgds
> > > > Umesh
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > -----Original Message-----
> > > > From: sigtran-admin@ietf.org
> > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > Tolga Asveren
> > > > Sent: Friday, June 06, 2003 8:59 AM
> > > > To: sigtran@ietf.org
> > > > Subject: Re: [Sigtran] M3UA : Multiple SGPs in
> > SG
> > > > 
> > > > 
> > > > Hi Kamesh,
> > > > 
> > > > In IG 3.15 there are some changes/clarifications
> > > > related with n+k redundancy (those most probably
> > > > will
> > > > be reworked but I think we still can rely on
> > > > INACTIVE->ACTIVE transition for AS state machine
> > > > there-)
> > > > In RFC3332 4.3.1
> > > > "The state of each remote ASP, in each AS that
> > it is
> > > > configured to operate, is maintained in the M3UA
> > > > layer
> > > > in the SGP."
> > > > So, the AS state machine is kept in SGP -not SG
> > > > wide-
> > > > and IG does not change this.
> > > > 
> > > > Now, IMO, what you tell -just while counting
> > number
> > > > of
> > > > ACTIVE ASPs for an AS acting SGwide but for the
> > > > other
> > > > ASPTM procedures still keeping per SGP approach-
> > is
> > > > not undoable, but not inline with current
> > RFC/IG.
> > > > 
> > > > IMO, cases, where this might be usefull will be
> > > > probably very rare (I think, it is not a very
> > high
> > > > possibility that an association to an ASP1 can
> > be
> > > > formed from SGP1 and can't be formed from SGP2
> > and
> > > > for
> > > > ASP2 can be formed from SGP2 but can't be formed
> > > > from
> > > > SGP1, if they are part of the same SG) and I
> > would
> > > > think introducing a new configuration item for
> > that
> > > > is
> > > > probably not worth.
> > > > Other opinions?
> > > > 
> > > >    Tolga
> > > > 
> > > > --- kakaul@hss.hns.com wrote:
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Hi Tolga,
> > > > >
> > > > >  RFC does not say any thing about n+k
> > redundancy
> > > > as
> > > > > you have pointed out in
> > > > > your first response. I am
> > > > >  attaching the lines from RFC from section
> > 4.3.4.3
> > > > > ASP Active Procedures:
> > 
> === message truncated ===
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
> http://calendar.yahoo.com
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 16:35:28 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11612
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 16:35:28 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56KZ1i27249
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 16:35:01 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56KYZB27210;
	Fri, 6 Jun 2003 16:34:35 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56KTKB26845
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 16:29:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11416
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 16:29:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ONo2-0006C5-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 16:27:22 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[H+MPtJypH4eSxgHs5IaybOVKxVXNHBEe])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ONo1-0006C2-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 16:27:21 -0400
Received: from ns.pigworks.openss7.net (IDENT://WbPCiX9zzoMF157V3ZpXuH+xFAsta6@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h56KTFF08497;
	Fri, 6 Jun 2003 14:29:15 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h56KTEP04190;
	Fri, 6 Jun 2003 14:29:14 -0600
Date: Fri, 6 Jun 2003 14:29:14 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
Message-ID: <20030606142914.G31671@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030606135037.B31671@openss7.org> <20030606200747.87018.qmail@web12801.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030606200747.87018.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Fri, Jun 06, 2003 at 01:07:47PM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

There was concensus to let the RFC stand and remove
the section from the IG.

--brian

Tolga Asveren wrote:                                                                 (Fri, 06 Jun 2003 13:07:47)
> Brian,
> 
> To my understanding, there was no consensus to change
> the current INACTIVE to ACTIVE transition in IG for
> n+k case.
> 
>     Tolga
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > This IG is wrong on this point from our last long
> > discussion.
> > 
> > Please correcct it.
> > 
> > --brian
> > 
> > Tolga Asveren wrote:                                
> >                                 (Fri, 06 Jun 2003
> > 08:59:13)
> > > Hi Kamesh,
> > > 
> > > In IG 3.15 there are some changes/clarifications
> > > related with n+k redundancy (those most probably
> > will
> > > be reworked but I think we still can rely on
> > > INACTIVE->ACTIVE transition for AS state machine
> > > there-)
> > > In RFC3332 4.3.1 
> > > "The state of each remote ASP, in each AS that it
> > is
> > > configured to operate, is maintained in the M3UA
> > layer
> > > in the SGP."
> > > So, the AS state machine is kept in SGP -not SG
> > wide-
> > > and IG does not change this.
> > > 
> > > Now, IMO, what you tell -just while counting
> > number of
> > > ACTIVE ASPs for an AS acting SGwide but for the
> > other
> > > ASPTM procedures still keeping per SGP approach-
> > is
> > > not undoable, but not inline with current RFC/IG. 
> > > 
> > > IMO, cases, where this might be usefull will be
> > > probably very rare (I think, it is not a very high
> > > possibility that an association to an ASP1 can be
> > > formed from SGP1 and can't be formed from SGP2 and
> > for
> > > ASP2 can be formed from SGP2 but can't be formed
> > from
> > > SGP1, if they are part of the same SG) and I would
> > > think introducing a new configuration item for
> > that is
> > > probably not worth. 
> > > Other opinions?
> > > 
> > >    Tolga 
> > > 
> > > --- kakaul@hss.hns.com wrote:
> > > > 
> > > > 
> > > > 
> > > > 
> > > > Hi Tolga,
> > > > 
> > > >  RFC does not say any thing about n+k redundancy
> > as
> > > > you have pointed out in
> > > > your first response. I am
> > > >  attaching the lines from RFC from section
> > 4.3.4.3
> > > > ASP Active Procedures:
> > > > "For the n+k redundancy case, ASPs which are in
> > that
> > > > AS should
> > > >  coordinate among themselves the number of
> > active
> > > > ASPs in the AS, and
> > > >  should start sending traffic only after n ASPs
> > are
> > > > active.
> > > > 
> > > >  All ASPs within a loadsharing mode AS must be
> > able
> > > > to process any
> > > >  Data message received for the AS, to
> > accommodate
> > > > any potential
> > > >  failover or rebalancing of the offered load."
> > > > 
> > > > So if there is any interopability problem as you
> > > > have indicated by keeping
> > > > the RFC open ended then it should         be
> > > > addressed in the
> > > > implementation guide.I still believe that it is
> > an
> > > > implementation issue and
> > > > can be resolved by configuring each AS and SG
> > nodes
> > > > in one of the two ways
> > > > of n+k redundancy scope i.e specific to SG or
> > SGP.
> > > > 
> > > > Regards
> > > > Kamesh
> > > > 
> > > > 
> > > > 
> > > > 
> > > > Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org
> > on
> > > > 06/06/2003 04:35:03 PM
> > > > 
> > > > Sent by:    sigtran-admin@ietf.org
> > > > 
> > > > 
> > > > To:    sigtran@ietf.org
> > > > cc:
> > > > 
> > > > Subject:    Re: [Sigtran] M3UA : Multiple SGPs
> > in SG
> > > > 
> > > > 
> > > > Hi Kamesh,
> > > > 
> > > > If we have to types of SGs (one, which activates
> > > > traffic based on number of ACTIVE ASPs per SGP
> > and
> > > > the
> > > > other per SG), ASPs can't decide -at least based
> > on
> > > > the current RFC- when to start/accept traffic.
> > What
> > > > ASPs are supposed to do is coordinating number
> > of
> > > > ACTIVE ASPs among the cluster, but if they don't
> > > > know,
> > > > whether the SG is deciding based on per SGP
> > counter
> > > > or
> > > > not, there will be interoperability problems
> > (for
> > > > example SG uses a global ACTIVE ASP counter and
> > > > starts
> > > > traffic but ASPs are counting per SGP, they
> > probably
> > > > will drop arriving DATA).
> > > > 
> > > >     Tolga
> > > > --- kakaul@hss.hns.com wrote:
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Hi Tolga,
> > > > >                     I am of the openion that
> > scope
> > > > > of n+k redundancy should
> > > > > depend on how one views and implements an SG.
> > In
> > > > > figure given below if an
> > > > > implementation wants to reroute some AS
> > traffic to
> > > > > its adjacent SGP on its
> > > > > way to AS it should be allowed.BTW as you have
> > > > also
> > > > > agreed that ASP1 and
> > > > > ASP2 also qualifies as two ASP's of AS if SGP1
> > and
> > > > > SGP2 has active
> > > > > associations with ASP1 and ASP2
> > respectively.SGP
> > > > may
> > > > > not want to block the
> > > > > traffic for AS if association between SGP1 and
> > > > ASP2
> > > > > is not active for AS
> > > > > assuming n = 2, k = 0(for n+k redundancy). I
> > am
> > > > not
> > > > > able to understand what
> > > > > interopability issue will be involved in it.No
> > > > doubt
> > > > > limiting scope of n+k
> > > > > redundancy to SGP is clear and simple but some
> > > > > implementations may want to
> > > > > use inter SGP routing to route there traffic
> > to
> > > > AS.
> > > > > So it ultimately
> > > > > depends on how you want your SG implementation
> > to
> > > > > behave.
> > > > >
> > > > >
> > > > >                       SG
> > > > >                   +--------------+           
> > AS
> > > > >                   |              |
> > > > > +---------+--+
> > > > >                   |              |        |
> > > > >   |
> > > > >                   | +--------+   |
> > > > > |+--------+  |
> > > > >                   | |        |   |        ||
> > > > > |  |
> > 
> === message truncated ===
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
> http://calendar.yahoo.com
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 16:43:32 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11804
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 16:43:32 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56Kh5s28491
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 16:43:05 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56KgpB28464;
	Fri, 6 Jun 2003 16:42:51 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56KeLB28391
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 16:40:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11750
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 16:40:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ONyh-0006Gj-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 16:38:23 -0400
Received: from web12802.mail.yahoo.com ([216.136.174.37])
	by ietf-mx with smtp (Exim 4.12)
	id 19ONyh-0006Gg-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 16:38:23 -0400
Message-ID: <20030606204016.61443.qmail@web12802.mail.yahoo.com>
Received: from [208.255.120.2] by web12802.mail.yahoo.com via HTTP; Fri, 06 Jun 2003 13:40:16 PDT
Date: Fri, 6 Jun 2003 13:40:16 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
To: sigtran@ietf.org
In-Reply-To: <20030606142827.F31671@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,

The "MAY" in the original message is the one about
internal forwarding of messages in SG.
"Rerouting of traffic between the SGPs MAY also be
supported."

And for INACTIVE to ACTIVE transition for n+k case, I
think different than you. The consensus was to change
ACTIVE to PENDING transition, at least to my
understanding.

   Tolga
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Tolga,
> 
> Because the RFC represents the concensus and the
> IG currently goes against concensus.  That section
> of the IG thay you and Javier dreamed up needs to
> be deleted.
> 
> --brian
> 
> 
> Tolga Asveren wrote:                                
>                                 (Fri, 06 Jun 2003
> 13:06:08)
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > Tolga,
> > > 
> > > There was no such agreement.
> > [TOLGA]If so, why is it a "MAY" in RFC?
> > > 
> > > --brian
> > > 
> > > Tolga Asveren wrote:                            
>    
> > >                                 (Fri, 06 Jun
> 2003
> > > 09:46:09)
> > > > Hi Umesh,
> > > > --- Umesh Vats <umesh@ccpu.com> wrote:
> > > > > Hi Tolga
> > > > > 
> > > > > The following text exists in implementor's
> > > guide.
> > > > > 
> > > > >                    "An SGP or IPSP, upon
> > > reception
> > > > > of an ASP Active message
> > > > > for the first
> > > > >                     ASP in a Loadshare AS,
> > > SHOULD
> > > > > NOT direct traffic to a
> > > > > newly active
> > > > >                     ASP until it determines
> that
> > > > > there are sufficient
> > > > > resources to handle
> > > > >                     the expected load (e.g.,
> > > until
> > > > > there are "n" ASPs in
> > > > > state ASP-ACTIVE
> > > > >                     in the AS).  In this
> case,
> > > the
> > > > > SGP or IPSP SHOULD
> > > > > withhold the Notify
> > > > >                     (AS-ACTIVE) until there
> are
> > > > > sufficient resources."
> > > > > 
> > > > > On SG, n ASPs must be active for an AS to
> before
> > > an
> > > > > AS is made active. It
> > > > > doesn't
> > > > > matter whether they went ACTIVE from the
> same
> > > SGP or
> > > > > different SGPs.
> > > > > 
> > > > > Although the state of each remote ASP is
> > > maintained
> > > > > in the AS, the overall
> > > > > AS is
> > > > > visible to whole SG. The following statement
> in
> > > RFC
> > > > > 3332 helps :
> > > > >  " Where an SG contains more than one SGP,
> the
> > > MTP3
> > > > > routeset, SPMC and
> > > > >    remote AS/ASP states of each SGP SHOULD
> be
> > > > > coordinated across all the
> > > > >    SGPs.  Rerouting of traffic between the
> SGPs
> > > MAY
> > > > > also be supported."
> > > > [TOLGA]This is the place I think a bit
> different.
> > > > Please note the "MAY" in the last sentence. I
> > > think it
> > > > was agreed not to use  a "SHOULD" here to not
> > > force
> > > > internal routing. (BTW, I think even the
> "SHOULD"
> > > in
> > > > the first sentence should be changed to
> "MAY")As I
> > > > said, basically counting number of ACTIVE ASPs
> per
> > > SG
> > > > will just introduce interoperability problems
> > > unless
> > > > some modifications are introduced to the IG
> and
> > > > considering that SGPs in a SG will most
> probably
> > > have
> > > > the same IP connectivity, this IMO is not very
> > > usefull
> > > > in real life. I personally would prefer the
> simple
> > > and
> > > > clear way of having all ASPTM procedures per
> > > SGP.(for
> > > > example do you like the idea of having ASPTM
> per
> > > SG
> > > > instead of SGP?)
> > > > > 
> > > > > Similarly for ASP to SG traffic, the SGP to
> > > which
> > > > > that ASP is connected
> > > > > doesn't matter when
> > > > > it has to decide about starting the traffic
> > > flow.
> > > > > All ASPs should coordinate
> > > > > among themselves if n ASP are ACTIVE for an
> AS
> > > or
> > > > > not.
> > > > [TOLGA]If what you mean is, that it really
> does
> > > not
> > > > matter for which SGP ASPs went ACTIVE, I
> disagree,
> > > at
> > > > least SG, SGP is part of should matter. Apart
> from
> > > > this, although the sentence might be not very
> > > clear in
> > > > the context of this discussion, the intention
> was
> > > to
> > > > coordinate number of ACTIVE ASPs for each SGP
> > > > separetly. Maybe a clarification might be
> added to
> > > IG.
> > > > > 
> > > > > "For the n+k redundancy case, ASPs which are
> in
> > > that
> > > > > AS should
> > > > >    coordinate among themselves the number of
> > > active
> > > > > ASPs in the AS, and
> > > > >    should start sending traffic only after n
> > > ASPs
> > > > > are active."
> > > > > 
> > > > > rgds
> > > > > Umesh
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > -----Original Message-----
> > > > > From: sigtran-admin@ietf.org
> > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > Tolga Asveren
> > > > > Sent: Friday, June 06, 2003 8:59 AM
> > > > > To: sigtran@ietf.org
> > > > > Subject: Re: [Sigtran] M3UA : Multiple SGPs
> in
> > > SG
> > > > > 
> > > > > 
> > > > > Hi Kamesh,
> > > > > 
> > > > > In IG 3.15 there are some
> changes/clarifications
> > > > > related with n+k redundancy (those most
> probably
> > > > > will
> > > > > be reworked but I think we still can rely on
> > > > > INACTIVE->ACTIVE transition for AS state
> machine
> > > > > there-)
> > > > > In RFC3332 4.3.1
> > > > > "The state of each remote ASP, in each AS
> that
> > > it is
> > > > > configured to operate, is maintained in the
> M3UA
> > > > > layer
> > > > > in the SGP."
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 17:11:40 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13209
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 17:11:40 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56LBEW31264
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 17:11:14 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56LAuB31242;
	Fri, 6 Jun 2003 17:10:57 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56L7sB31128
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 17:07:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12978
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 17:07:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OOPL-0006Xg-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 17:05:55 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[9Je3R5ml42SmvvP+KoDkXO4Z2y2Fgawk])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OOPK-0006XV-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 17:05:54 -0400
Received: from ns.pigworks.openss7.net (IDENT:Ns3+Ey/PN0kgCz9qRzJ2CZSkJ30qBLv6@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h56L7jF09201;
	Fri, 6 Jun 2003 15:07:45 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h56L7j804640;
	Fri, 6 Jun 2003 15:07:45 -0600
Date: Fri, 6 Jun 2003 15:07:44 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
Message-ID: <20030606150744.H31671@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030606142827.F31671@openss7.org> <20030606204016.61443.qmail@web12802.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030606204016.61443.qmail@web12802.mail.yahoo.com>; from tolga_asveren@yahoo.com on Fri, Jun 06, 2003 at 01:40:16PM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

Go back and read the threads.

IIRC you claimed that there would be some
"interoperability" problem from following
the RFC, but did not point out what that
problem might be.

Could you explain now?

--brian

Tolga Asveren wrote:                                                                 (Fri, 06 Jun 2003 13:40:16)
> Brian,
> 
> The "MAY" in the original message is the one about
> internal forwarding of messages in SG.
> "Rerouting of traffic between the SGPs MAY also be
> supported."
> 
> And for INACTIVE to ACTIVE transition for n+k case, I
> think different than you. The consensus was to change
> ACTIVE to PENDING transition, at least to my
> understanding.
> 
>    Tolga
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Because the RFC represents the concensus and the
> > IG currently goes against concensus.  That section
> > of the IG thay you and Javier dreamed up needs to
> > be deleted.
> > 
> > --brian
> > 
> > 
> > Tolga Asveren wrote:                                
> >                                 (Fri, 06 Jun 2003
> > 13:06:08)
> > > Brian,
> > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > wrote:
> > > > Tolga,
> > > > 
> > > > There was no such agreement.
> > > [TOLGA]If so, why is it a "MAY" in RFC?
> > > > 
> > > > --brian
> > > > 
> > > > Tolga Asveren wrote:                            
> >    
> > > >                                 (Fri, 06 Jun
> > 2003
> > > > 09:46:09)
> > > > > Hi Umesh,
> > > > > --- Umesh Vats <umesh@ccpu.com> wrote:
> > > > > > Hi Tolga
> > > > > > 
> > > > > > The following text exists in implementor's
> > > > guide.
> > > > > > 
> > > > > >                    "An SGP or IPSP, upon
> > > > reception
> > > > > > of an ASP Active message
> > > > > > for the first
> > > > > >                     ASP in a Loadshare AS,
> > > > SHOULD
> > > > > > NOT direct traffic to a
> > > > > > newly active
> > > > > >                     ASP until it determines
> > that
> > > > > > there are sufficient
> > > > > > resources to handle
> > > > > >                     the expected load (e.g.,
> > > > until
> > > > > > there are "n" ASPs in
> > > > > > state ASP-ACTIVE
> > > > > >                     in the AS).  In this
> > case,
> > > > the
> > > > > > SGP or IPSP SHOULD
> > > > > > withhold the Notify
> > > > > >                     (AS-ACTIVE) until there
> > are
> > > > > > sufficient resources."
> > > > > > 
> > > > > > On SG, n ASPs must be active for an AS to
> > before
> > > > an
> > > > > > AS is made active. It
> > > > > > doesn't
> > > > > > matter whether they went ACTIVE from the
> > same
> > > > SGP or
> > > > > > different SGPs.
> > > > > > 
> > > > > > Although the state of each remote ASP is
> > > > maintained
> > > > > > in the AS, the overall
> > > > > > AS is
> > > > > > visible to whole SG. The following statement
> > in
> > > > RFC
> > > > > > 3332 helps :
> > > > > >  " Where an SG contains more than one SGP,
> > the
> > > > MTP3
> > > > > > routeset, SPMC and
> > > > > >    remote AS/ASP states of each SGP SHOULD
> > be
> > > > > > coordinated across all the
> > > > > >    SGPs.  Rerouting of traffic between the
> > SGPs
> > > > MAY
> > > > > > also be supported."
> > > > > [TOLGA]This is the place I think a bit
> > different.
> > > > > Please note the "MAY" in the last sentence. I
> > > > think it
> > > > > was agreed not to use  a "SHOULD" here to not
> > > > force
> > > > > internal routing. (BTW, I think even the
> > "SHOULD"
> > > > in
> > > > > the first sentence should be changed to
> > "MAY")As I
> > > > > said, basically counting number of ACTIVE ASPs
> > per
> > > > SG
> > > > > will just introduce interoperability problems
> > > > unless
> > > > > some modifications are introduced to the IG
> > and
> > > > > considering that SGPs in a SG will most
> > probably
> > > > have
> > > > > the same IP connectivity, this IMO is not very
> > > > usefull
> > > > > in real life. I personally would prefer the
> > simple
> > > > and
> > > > > clear way of having all ASPTM procedures per
> > > > SGP.(for
> > > > > example do you like the idea of having ASPTM
> > per
> > > > SG
> > > > > instead of SGP?)
> > > > > > 
> > > > > > Similarly for ASP to SG traffic, the SGP to
> > > > which
> > > > > > that ASP is connected
> > > > > > doesn't matter when
> > > > > > it has to decide about starting the traffic
> > > > flow.
> > > > > > All ASPs should coordinate
> > > > > > among themselves if n ASP are ACTIVE for an
> > AS
> > > > or
> > > > > > not.
> > > > > [TOLGA]If what you mean is, that it really
> > does
> > > > not
> > > > > matter for which SGP ASPs went ACTIVE, I
> > disagree,
> > > > at
> > > > > least SG, SGP is part of should matter. Apart
> > from
> > > > > this, although the sentence might be not very
> > > > clear in
> > > > > the context of this discussion, the intention
> > was
> > > > to
> > > > > coordinate number of ACTIVE ASPs for each SGP
> > > > > separetly. Maybe a clarification might be
> > added to
> > > > IG.
> > > > > > 
> > > > > > "For the n+k redundancy case, ASPs which are
> > in
> > > > that
> > > > > > AS should
> > > > > >    coordinate among themselves the number of
> > > > active
> > > > > > ASPs in the AS, and
> > > > > >    should start sending traffic only after n
> > > > ASPs
> > > > > > are active."
> > > > > > 
> > > > > > rgds
> > > > > > Umesh
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > -----Original Message-----
> > > > > > From: sigtran-admin@ietf.org
> > > > > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > > > > Tolga Asveren
> > > > > > Sent: Friday, June 06, 2003 8:59 AM
> > > > > > To: sigtran@ietf.org
> > > > > > Subject: Re: [Sigtran] M3UA : Multiple SGPs
> > in
> > > > SG
> > > > > > 
> > > > > > 
> > > > > > Hi Kamesh,
> > > > > > 
> > > > > > In IG 3.15 there are some
> > changes/clarifications
> > > > > > related with n+k redundancy (those most
> > probably
> > > > > > will
> > > > > > be reworked but I think we still can rely on
> > > > > > INACTIVE->ACTIVE transition for AS state
> > machine
> > > > > > there-)
> > > > > > In RFC3332 4.3.1
> > > > > > "The state of each remote ASP, in each AS
> > that
> > > > it is
> > > > > > configured to operate, is maintained in the
> > M3UA
> > > > > > layer
> > > > > > in the SGP."
> > 
> === message truncated ===
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
> http://calendar.yahoo.com
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 17:21:32 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13775
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 17:21:32 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56LL6b31920
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 17:21:06 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56LKpB31802;
	Fri, 6 Jun 2003 17:20:51 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56LI3B31550
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 17:18:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13515
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 17:17:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OOZA-0006fB-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 17:16:04 -0400
Received: from web12803.mail.yahoo.com ([216.136.174.38])
	by ietf-mx with smtp (Exim 4.12)
	id 19OOZ9-0006f4-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 17:16:03 -0400
Message-ID: <20030606211757.98717.qmail@web12803.mail.yahoo.com>
Received: from [208.255.120.2] by web12803.mail.yahoo.com via HTTP; Fri, 06 Jun 2003 14:17:57 PDT
Date: Fri, 6 Jun 2003 14:17:57 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
To: sigtran@ietf.org
In-Reply-To: <20030606150744.H31671@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Tolga,
> 
> Go back and read the threads.
> 
> IIRC you claimed that there would be some
> "interoperability" problem from following
> the RFC, but did not point out what that
> problem might be.
> 
> Could you explain now?
[TOLGA]What I did say was, for n+k case -if it is
allowed to use n per SG or per SGP-, if SG uses SGwide
number of ACTIVE ASPs and ASPs use the per SGP
counter, there will be an inconsistency between SGPs
and ASPs, when to start routing DATA to/from ASP.
> 
> --brian
> 
> Tolga Asveren wrote:                                
>                                 (Fri, 06 Jun 2003
> 13:40:16)
> > Brian,
> > 
> > The "MAY" in the original message is the one about
> > internal forwarding of messages in SG.
> > "Rerouting of traffic between the SGPs MAY also be
> > supported."
> > 
> > And for INACTIVE to ACTIVE transition for n+k
> case, I
> > think different than you. The consensus was to
> change
> > ACTIVE to PENDING transition, at least to my
> > understanding.
> > 
> >    Tolga
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > Tolga,
> > > 
> > > Because the RFC represents the concensus and the
> > > IG currently goes against concensus.  That
> section
> > > of the IG thay you and Javier dreamed up needs
> to
> > > be deleted.
> > > 
> > > --brian
> > > 
> > > 
> > > Tolga Asveren wrote:                            
>    
> > >                                 (Fri, 06 Jun
> 2003
> > > 13:06:08)
> > > > Brian,
> > > > --- "Brian F. G. Bidulock"
> <bidulock@openss7.org>
> > > > wrote:
> > > > > Tolga,
> > > > > 
> > > > > There was no such agreement.
> > > > [TOLGA]If so, why is it a "MAY" in RFC?
> > > > > 
> > > > > --brian
> > > > > 
> > > > > Tolga Asveren wrote:                        
>    
> > >    
> > > > >                                 (Fri, 06 Jun
> > > 2003
> > > > > 09:46:09)
> > > > > > Hi Umesh,
> > > > > > --- Umesh Vats <umesh@ccpu.com> wrote:
> > > > > > > Hi Tolga
> > > > > > > 
> > > > > > > The following text exists in
> implementor's
> > > > > guide.
> > > > > > > 
> > > > > > >                    "An SGP or IPSP, upon
> > > > > reception
> > > > > > > of an ASP Active message
> > > > > > > for the first
> > > > > > >                     ASP in a Loadshare
> AS,
> > > > > SHOULD
> > > > > > > NOT direct traffic to a
> > > > > > > newly active
> > > > > > >                     ASP until it
> determines
> > > that
> > > > > > > there are sufficient
> > > > > > > resources to handle
> > > > > > >                     the expected load
> (e.g.,
> > > > > until
> > > > > > > there are "n" ASPs in
> > > > > > > state ASP-ACTIVE
> > > > > > >                     in the AS).  In this
> > > case,
> > > > > the
> > > > > > > SGP or IPSP SHOULD
> > > > > > > withhold the Notify
> > > > > > >                     (AS-ACTIVE) until
> there
> > > are
> > > > > > > sufficient resources."
> > > > > > > 
> > > > > > > On SG, n ASPs must be active for an AS
> to
> > > before
> > > > > an
> > > > > > > AS is made active. It
> > > > > > > doesn't
> > > > > > > matter whether they went ACTIVE from the
> > > same
> > > > > SGP or
> > > > > > > different SGPs.
> > > > > > > 
> > > > > > > Although the state of each remote ASP is
> > > > > maintained
> > > > > > > in the AS, the overall
> > > > > > > AS is
> > > > > > > visible to whole SG. The following
> statement
> > > in
> > > > > RFC
> > > > > > > 3332 helps :
> > > > > > >  " Where an SG contains more than one
> SGP,
> > > the
> > > > > MTP3
> > > > > > > routeset, SPMC and
> > > > > > >    remote AS/ASP states of each SGP
> SHOULD
> > > be
> > > > > > > coordinated across all the
> > > > > > >    SGPs.  Rerouting of traffic between
> the
> > > SGPs
> > > > > MAY
> > > > > > > also be supported."
> > > > > > [TOLGA]This is the place I think a bit
> > > different.
> > > > > > Please note the "MAY" in the last
> sentence. I
> > > > > think it
> > > > > > was agreed not to use  a "SHOULD" here to
> not
> > > > > force
> > > > > > internal routing. (BTW, I think even the
> > > "SHOULD"
> > > > > in
> > > > > > the first sentence should be changed to
> > > "MAY")As I
> > > > > > said, basically counting number of ACTIVE
> ASPs
> > > per
> > > > > SG
> > > > > > will just introduce interoperability
> problems
> > > > > unless
> > > > > > some modifications are introduced to the
> IG
> > > and
> > > > > > considering that SGPs in a SG will most
> > > probably
> > > > > have
> > > > > > the same IP connectivity, this IMO is not
> very
> > > > > usefull
> > > > > > in real life. I personally would prefer
> the
> > > simple
> > > > > and
> > > > > > clear way of having all ASPTM procedures
> per
> > > > > SGP.(for
> > > > > > example do you like the idea of having
> ASPTM
> > > per
> > > > > SG
> > > > > > instead of SGP?)
> > > > > > > 
> > > > > > > Similarly for ASP to SG traffic, the SGP
> to
> > > > > which
> > > > > > > that ASP is connected
> > > > > > > doesn't matter when
> > > > > > > it has to decide about starting the
> traffic
> > > > > flow.
> > > > > > > All ASPs should coordinate
> > > > > > > among themselves if n ASP are ACTIVE for
> an
> > > AS
> > > > > or
> > > > > > > not.
> > > > > > [TOLGA]If what you mean is, that it really
> > > does
> > > > > not
> > > > > > matter for which SGP ASPs went ACTIVE, I
> > > disagree,
> > > > > at
> > > > > > least SG, SGP is part of should matter.
> Apart
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 17:50:49 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14986
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 17:50:48 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56LoNL01645
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 17:50:23 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56Lo5B01635;
	Fri, 6 Jun 2003 17:50:05 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56LivB01430
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 17:44:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14783
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 17:44:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OOzC-0006vU-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 17:42:58 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[1KHbmEKRPGeFTBzaimgOUdKad8k05O98])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OOzB-0006vR-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 17:42:57 -0400
Received: from ns.pigworks.openss7.net (IDENT:sFrJQq1EYUfKbwMx3dkuBCkbNDGNJu8T@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h56LiqF09708;
	Fri, 6 Jun 2003 15:44:52 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h56Lipv05261;
	Fri, 6 Jun 2003 15:44:51 -0600
Date: Fri, 6 Jun 2003 15:44:51 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
Message-ID: <20030606154451.B4949@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030606150744.H31671@openss7.org> <20030606211757.98717.qmail@web12803.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030606211757.98717.qmail@web12803.mail.yahoo.com>; from tolga_asveren@yahoo.com on Fri, Jun 06, 2003 at 02:17:57PM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

What inconsistency?  What bad thing will happen?

--brian

Tolga Asveren wrote:                                                                 (Fri, 06 Jun 2003 14:17:57)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Go back and read the threads.
> > 
> > IIRC you claimed that there would be some
> > "interoperability" problem from following
> > the RFC, but did not point out what that
> > problem might be.
> > 
> > Could you explain now?
> [TOLGA]What I did say was, for n+k case -if it is
> allowed to use n per SG or per SGP-, if SG uses SGwide
> number of ACTIVE ASPs and ASPs use the per SGP
> counter, there will be an inconsistency between SGPs
> and ASPs, when to start routing DATA to/from ASP.
> > 
> > --brian
> > 
> > Tolga Asveren wrote:                                
> >                                 (Fri, 06 Jun 2003
> > 13:40:16)
> > > Brian,
> > > 
> > > The "MAY" in the original message is the one about
> > > internal forwarding of messages in SG.
> > > "Rerouting of traffic between the SGPs MAY also be
> > > supported."
> > > 
> > > And for INACTIVE to ACTIVE transition for n+k
> > case, I
> > > think different than you. The consensus was to
> > change
> > > ACTIVE to PENDING transition, at least to my
> > > understanding.
> > > 
> > >    Tolga
> > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > wrote:
> > > > Tolga,
> > > > 
> > > > Because the RFC represents the concensus and the
> > > > IG currently goes against concensus.  That
> > section
> > > > of the IG thay you and Javier dreamed up needs
> > to
> > > > be deleted.
> > > > 
> > > > --brian
> > > > 
> > > > 
> > > > Tolga Asveren wrote:                            
> >    
> > > >                                 (Fri, 06 Jun
> > 2003
> > > > 13:06:08)
> > > > > Brian,
> > > > > --- "Brian F. G. Bidulock"
> > <bidulock@openss7.org>
> > > > > wrote:
> > > > > > Tolga,
> > > > > > 
> > > > > > There was no such agreement.
> > > > > [TOLGA]If so, why is it a "MAY" in RFC?
> > > > > > 
> > > > > > --brian
> > > > > > 
> > > > > > Tolga Asveren wrote:                        
> >    
> > > >    
> > > > > >                                 (Fri, 06 Jun
> > > > 2003
> > > > > > 09:46:09)
> > > > > > > Hi Umesh,
> > > > > > > --- Umesh Vats <umesh@ccpu.com> wrote:
> > > > > > > > Hi Tolga
> > > > > > > > 
> > > > > > > > The following text exists in
> > implementor's
> > > > > > guide.
> > > > > > > > 
> > > > > > > >                    "An SGP or IPSP, upon
> > > > > > reception
> > > > > > > > of an ASP Active message
> > > > > > > > for the first
> > > > > > > >                     ASP in a Loadshare
> > AS,
> > > > > > SHOULD
> > > > > > > > NOT direct traffic to a
> > > > > > > > newly active
> > > > > > > >                     ASP until it
> > determines
> > > > that
> > > > > > > > there are sufficient
> > > > > > > > resources to handle
> > > > > > > >                     the expected load
> > (e.g.,
> > > > > > until
> > > > > > > > there are "n" ASPs in
> > > > > > > > state ASP-ACTIVE
> > > > > > > >                     in the AS).  In this
> > > > case,
> > > > > > the
> > > > > > > > SGP or IPSP SHOULD
> > > > > > > > withhold the Notify
> > > > > > > >                     (AS-ACTIVE) until
> > there
> > > > are
> > > > > > > > sufficient resources."
> > > > > > > > 
> > > > > > > > On SG, n ASPs must be active for an AS
> > to
> > > > before
> > > > > > an
> > > > > > > > AS is made active. It
> > > > > > > > doesn't
> > > > > > > > matter whether they went ACTIVE from the
> > > > same
> > > > > > SGP or
> > > > > > > > different SGPs.
> > > > > > > > 
> > > > > > > > Although the state of each remote ASP is
> > > > > > maintained
> > > > > > > > in the AS, the overall
> > > > > > > > AS is
> > > > > > > > visible to whole SG. The following
> > statement
> > > > in
> > > > > > RFC
> > > > > > > > 3332 helps :
> > > > > > > >  " Where an SG contains more than one
> > SGP,
> > > > the
> > > > > > MTP3
> > > > > > > > routeset, SPMC and
> > > > > > > >    remote AS/ASP states of each SGP
> > SHOULD
> > > > be
> > > > > > > > coordinated across all the
> > > > > > > >    SGPs.  Rerouting of traffic between
> > the
> > > > SGPs
> > > > > > MAY
> > > > > > > > also be supported."
> > > > > > > [TOLGA]This is the place I think a bit
> > > > different.
> > > > > > > Please note the "MAY" in the last
> > sentence. I
> > > > > > think it
> > > > > > > was agreed not to use  a "SHOULD" here to
> > not
> > > > > > force
> > > > > > > internal routing. (BTW, I think even the
> > > > "SHOULD"
> > > > > > in
> > > > > > > the first sentence should be changed to
> > > > "MAY")As I
> > > > > > > said, basically counting number of ACTIVE
> > ASPs
> > > > per
> > > > > > SG
> > > > > > > will just introduce interoperability
> > problems
> > > > > > unless
> > > > > > > some modifications are introduced to the
> > IG
> > > > and
> > > > > > > considering that SGPs in a SG will most
> > > > probably
> > > > > > have
> > > > > > > the same IP connectivity, this IMO is not
> > very
> > > > > > usefull
> > > > > > > in real life. I personally would prefer
> > the
> > > > simple
> > > > > > and
> > > > > > > clear way of having all ASPTM procedures
> > per
> > > > > > SGP.(for
> > > > > > > example do you like the idea of having
> > ASPTM
> > > > per
> > > > > > SG
> > > > > > > instead of SGP?)
> > > > > > > > 
> > > > > > > > Similarly for ASP to SG traffic, the SGP
> > to
> > > > > > which
> > > > > > > > that ASP is connected
> > > > > > > > doesn't matter when
> > > > > > > > it has to decide about starting the
> > traffic
> > > > > > flow.
> > > > > > > > All ASPs should coordinate
> > > > > > > > among themselves if n ASP are ACTIVE for
> > an
> > > > AS
> > > > > > or
> > > > > > > > not.
> > > > > > > [TOLGA]If what you mean is, that it really
> > > > does
> > > > > > not
> > > > > > > matter for which SGP ASPs went ACTIVE, I
> > > > disagree,
> > > > > > at
> > > > > > > least SG, SGP is part of should matter.
> > Apart
> > 
> === message truncated ===
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
> http://calendar.yahoo.com
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 18:02:36 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15237
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 18:02:36 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56M2Br02108
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 18:02:11 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56M1vB02090;
	Fri, 6 Jun 2003 18:01:57 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56LxgB01974
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 17:59:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15165
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 17:59:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OPDT-000707-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 17:57:43 -0400
Received: from web12804.mail.yahoo.com ([216.136.174.39])
	by ietf-mx with smtp (Exim 4.12)
	id 19OPDS-000704-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 17:57:42 -0400
Message-ID: <20030606215937.32152.qmail@web12804.mail.yahoo.com>
Received: from [208.255.120.2] by web12804.mail.yahoo.com via HTTP; Fri, 06 Jun 2003 14:59:37 PDT
Date: Fri, 6 Jun 2003 14:59:37 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
To: sigtran@ietf.org
In-Reply-To: <20030606154451.B4949@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Tolga,
> 
> What inconsistency?  What bad thing will happen?
[TOLGA](We had this discussion before I think, so I
will just briefly summarize my opinion)
When AS is seen as ACTIVE, SG will expose this to SS7
network (directly with a TFA or indirectly by not
sending UPU). This might cause  some nodes in SS7
network to initiate traffic to the AS. But ASPs most
probably will drop arriving DATA, because they don't
see AS as ACTIVE.
If this is not seen as a problem, then routing DATA to
an INACTIVE ASP (n=1 case) should be also allowed.
> 
> --brian
> 
> Tolga Asveren wrote:                                
>                                 (Fri, 06 Jun 2003
> 14:17:57)
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > Tolga,
> > > 
> > > Go back and read the threads.
> > > 
> > > IIRC you claimed that there would be some
> > > "interoperability" problem from following
> > > the RFC, but did not point out what that
> > > problem might be.
> > > 
> > > Could you explain now?
> > [TOLGA]What I did say was, for n+k case -if it is
> > allowed to use n per SG or per SGP-, if SG uses
> SGwide
> > number of ACTIVE ASPs and ASPs use the per SGP
> > counter, there will be an inconsistency between
> SGPs
> > and ASPs, when to start routing DATA to/from ASP.
> > > 
> > > --brian
> > > 
> > > Tolga Asveren wrote:                            
>    
> > >                                 (Fri, 06 Jun
> 2003
> > > 13:40:16)
> > > > Brian,
> > > > 
> > > > The "MAY" in the original message is the one
> about
> > > > internal forwarding of messages in SG.
> > > > "Rerouting of traffic between the SGPs MAY
> also be
> > > > supported."
> > > > 
> > > > And for INACTIVE to ACTIVE transition for n+k
> > > case, I
> > > > think different than you. The consensus was to
> > > change
> > > > ACTIVE to PENDING transition, at least to my
> > > > understanding.
> > > > 
> > > >    Tolga
> > > > --- "Brian F. G. Bidulock"
> <bidulock@openss7.org>
> > > > wrote:
> > > > > Tolga,
> > > > > 
> > > > > Because the RFC represents the concensus and
> the
> > > > > IG currently goes against concensus.  That
> > > section
> > > > > of the IG thay you and Javier dreamed up
> needs
> > > to
> > > > > be deleted.
> > > > > 
> > > > > --brian
> > > > > 
> > > > > 
> > > > > Tolga Asveren wrote:                        
>    
> > >    
> > > > >                                 (Fri, 06 Jun
> > > 2003
> > > > > 13:06:08)
> > > > > > Brian,
> > > > > > --- "Brian F. G. Bidulock"
> > > <bidulock@openss7.org>
> > > > > > wrote:
> > > > > > > Tolga,
> > > > > > > 
> > > > > > > There was no such agreement.
> > > > > > [TOLGA]If so, why is it a "MAY" in RFC?
> > > > > > > 
> > > > > > > --brian
> > > > > > > 
> > > > > > > Tolga Asveren wrote:                    
>    
> > >    
> > > > >    
> > > > > > >                                 (Fri, 06
> Jun
> > > > > 2003
> > > > > > > 09:46:09)
> > > > > > > > Hi Umesh,
> > > > > > > > --- Umesh Vats <umesh@ccpu.com> wrote:
> > > > > > > > > Hi Tolga
> > > > > > > > > 
> > > > > > > > > The following text exists in
> > > implementor's
> > > > > > > guide.
> > > > > > > > > 
> > > > > > > > >                    "An SGP or IPSP,
> upon
> > > > > > > reception
> > > > > > > > > of an ASP Active message
> > > > > > > > > for the first
> > > > > > > > >                     ASP in a
> Loadshare
> > > AS,
> > > > > > > SHOULD
> > > > > > > > > NOT direct traffic to a
> > > > > > > > > newly active
> > > > > > > > >                     ASP until it
> > > determines
> > > > > that
> > > > > > > > > there are sufficient
> > > > > > > > > resources to handle
> > > > > > > > >                     the expected
> load
> > > (e.g.,
> > > > > > > until
> > > > > > > > > there are "n" ASPs in
> > > > > > > > > state ASP-ACTIVE
> > > > > > > > >                     in the AS).  In
> this
> > > > > case,
> > > > > > > the
> > > > > > > > > SGP or IPSP SHOULD
> > > > > > > > > withhold the Notify
> > > > > > > > >                     (AS-ACTIVE)
> until
> > > there
> > > > > are
> > > > > > > > > sufficient resources."
> > > > > > > > > 
> > > > > > > > > On SG, n ASPs must be active for an
> AS
> > > to
> > > > > before
> > > > > > > an
> > > > > > > > > AS is made active. It
> > > > > > > > > doesn't
> > > > > > > > > matter whether they went ACTIVE from
> the
> > > > > same
> > > > > > > SGP or
> > > > > > > > > different SGPs.
> > > > > > > > > 
> > > > > > > > > Although the state of each remote
> ASP is
> > > > > > > maintained
> > > > > > > > > in the AS, the overall
> > > > > > > > > AS is
> > > > > > > > > visible to whole SG. The following
> > > statement
> > > > > in
> > > > > > > RFC
> > > > > > > > > 3332 helps :
> > > > > > > > >  " Where an SG contains more than
> one
> > > SGP,
> > > > > the
> > > > > > > MTP3
> > > > > > > > > routeset, SPMC and
> > > > > > > > >    remote AS/ASP states of each SGP
> > > SHOULD
> > > > > be
> > > > > > > > > coordinated across all the
> > > > > > > > >    SGPs.  Rerouting of traffic
> between
> > > the
> > > > > SGPs
> > > > > > > MAY
> > > > > > > > > also be supported."
> > > > > > > > [TOLGA]This is the place I think a bit
> > > > > different.
> > > > > > > > Please note the "MAY" in the last
> > > sentence. I
> > > > > > > think it
> > > > > > > > was agreed not to use  a "SHOULD" here
> to
> > > not
> > > > > > > force
> > > > > > > > internal routing. (BTW, I think even
> the
> > > > > "SHOULD"
> > > > > > > in
> > > > > > > > the first sentence should be changed
> to
> > > > > "MAY")As I
> > > > > > > > said, basically counting number of
> ACTIVE
> > > ASPs
> > > > > per
> > > > > > > SG
> > > > > > > > will just introduce interoperability
> > > problems
> > > > > > > unless
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 18:04:28 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15432
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 18:04:28 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56M44i02198
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 18:04:04 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56M3oB02167;
	Fri, 6 Jun 2003 18:03:50 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56M0GB02023
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 18:00:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15195
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 18:00:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OPE1-00070N-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 17:58:17 -0400
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OPDy-00070K-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 17:58:15 -0400
Received: from [172.16.1.40] (helo=ccpu00251)
	by smtp.ccpu.com with smtp (Exim 4.20 #1 (Debian))
	id 19OPFf-0004pq-FK
	for <sigtran@ietf.org>; Fri, 06 Jun 2003 14:59:59 -0700
Reply-To: <umesh@ccpu.com>
From: "Umesh Vats" <umesh@ccpu.com>
To: <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA : Multiple SGPs in SG
Date: Fri, 6 Jun 2003 15:03:17 -0700
Message-ID: <ACEMIJONPBBPDLOKCABHMEJACAAA.umesh@ccpu.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <20030606211757.98717.qmail@web12803.mail.yahoo.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

[TOLGA]What I did say was, for n+k case -if it is
allowed to use n per SG or per SGP-, if SG uses SGwide
number of ACTIVE ASPs and ASPs use the per SGP
counter, there will be an inconsistency between SGPs
and ASPs, when to start routing DATA to/from ASP.

[UMESH] This shouldn't happen.
All ASPs serving an AS can also use n as SG wide
value through inter communication between them. Following statement
in RFC says this. 

"For the n+k redundancy case, ASPs which are in that AS should
   coordinate among themselves the number of active ASPs in the AS, and
   should start sending traffic only after n ASPs are active."


Umesh

-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
Tolga Asveren
Sent: Friday, June 06, 2003 2:18 PM
To: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG


Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Tolga,
> 
> Go back and read the threads.
> 
> IIRC you claimed that there would be some
> "interoperability" problem from following
> the RFC, but did not point out what that
> problem might be.
> 
> Could you explain now?
[TOLGA]What I did say was, for n+k case -if it is
allowed to use n per SG or per SGP-, if SG uses SGwide
number of ACTIVE ASPs and ASPs use the per SGP
counter, there will be an inconsistency between SGPs
and ASPs, when to start routing DATA to/from ASP.
> 
> --brian
> 
> Tolga Asveren wrote:                                
>                                 (Fri, 06 Jun 2003
> 13:40:16)
> > Brian,
> > 
> > The "MAY" in the original message is the one about
> > internal forwarding of messages in SG.
> > "Rerouting of traffic between the SGPs MAY also be
> > supported."
> > 
> > And for INACTIVE to ACTIVE transition for n+k
> case, I
> > think different than you. The consensus was to
> change
> > ACTIVE to PENDING transition, at least to my
> > understanding.
> > 
> >    Tolga
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > Tolga,
> > > 
> > > Because the RFC represents the concensus and the
> > > IG currently goes against concensus.  That
> section
> > > of the IG thay you and Javier dreamed up needs
> to
> > > be deleted.
> > > 
> > > --brian
> > > 
> > > 
> > > Tolga Asveren wrote:                            
>    
> > >                                 (Fri, 06 Jun
> 2003
> > > 13:06:08)
> > > > Brian,
> > > > --- "Brian F. G. Bidulock"
> <bidulock@openss7.org>
> > > > wrote:
> > > > > Tolga,
> > > > > 
> > > > > There was no such agreement.
> > > > [TOLGA]If so, why is it a "MAY" in RFC?
> > > > > 
> > > > > --brian
> > > > > 
> > > > > Tolga Asveren wrote:                        
>    
> > >    
> > > > >                                 (Fri, 06 Jun
> > > 2003
> > > > > 09:46:09)
> > > > > > Hi Umesh,
> > > > > > --- Umesh Vats <umesh@ccpu.com> wrote:
> > > > > > > Hi Tolga
> > > > > > > 
> > > > > > > The following text exists in
> implementor's
> > > > > guide.
> > > > > > > 
> > > > > > >                    "An SGP or IPSP, upon
> > > > > reception
> > > > > > > of an ASP Active message
> > > > > > > for the first
> > > > > > >                     ASP in a Loadshare
> AS,
> > > > > SHOULD
> > > > > > > NOT direct traffic to a
> > > > > > > newly active
> > > > > > >                     ASP until it
> determines
> > > that
> > > > > > > there are sufficient
> > > > > > > resources to handle
> > > > > > >                     the expected load
> (e.g.,
> > > > > until
> > > > > > > there are "n" ASPs in
> > > > > > > state ASP-ACTIVE
> > > > > > >                     in the AS).  In this
> > > case,
> > > > > the
> > > > > > > SGP or IPSP SHOULD
> > > > > > > withhold the Notify
> > > > > > >                     (AS-ACTIVE) until
> there
> > > are
> > > > > > > sufficient resources."
> > > > > > > 
> > > > > > > On SG, n ASPs must be active for an AS
> to
> > > before
> > > > > an
> > > > > > > AS is made active. It
> > > > > > > doesn't
> > > > > > > matter whether they went ACTIVE from the
> > > same
> > > > > SGP or
> > > > > > > different SGPs.
> > > > > > > 
> > > > > > > Although the state of each remote ASP is
> > > > > maintained
> > > > > > > in the AS, the overall
> > > > > > > AS is
> > > > > > > visible to whole SG. The following
> statement
> > > in
> > > > > RFC
> > > > > > > 3332 helps :
> > > > > > >  " Where an SG contains more than one
> SGP,
> > > the
> > > > > MTP3
> > > > > > > routeset, SPMC and
> > > > > > >    remote AS/ASP states of each SGP
> SHOULD
> > > be
> > > > > > > coordinated across all the
> > > > > > >    SGPs.  Rerouting of traffic between
> the
> > > SGPs
> > > > > MAY
> > > > > > > also be supported."
> > > > > > [TOLGA]This is the place I think a bit
> > > different.
> > > > > > Please note the "MAY" in the last
> sentence. I
> > > > > think it
> > > > > > was agreed not to use  a "SHOULD" here to
> not
> > > > > force
> > > > > > internal routing. (BTW, I think even the
> > > "SHOULD"
> > > > > in
> > > > > > the first sentence should be changed to
> > > "MAY")As I
> > > > > > said, basically counting number of ACTIVE
> ASPs
> > > per
> > > > > SG
> > > > > > will just introduce interoperability
> problems
> > > > > unless
> > > > > > some modifications are introduced to the
> IG
> > > and
> > > > > > considering that SGPs in a SG will most
> > > probably
> > > > > have
> > > > > > the same IP connectivity, this IMO is not
> very
> > > > > usefull
> > > > > > in real life. I personally would prefer
> the
> > > simple
> > > > > and
> > > > > > clear way of having all ASPTM procedures
> per
> > > > > SGP.(for
> > > > > > example do you like the idea of having
> ASPTM
> > > per
> > > > > SG
> > > > > > instead of SGP?)
> > > > > > > 
> > > > > > > Similarly for ASP to SG traffic, the SGP
> to
> > > > > which
> > > > > > > that ASP is connected
> > > > > > > doesn't matter when
> > > > > > > it has to decide about starting the
> traffic
> > > > > flow.
> > > > > > > All ASPs should coordinate
> > > > > > > among themselves if n ASP are ACTIVE for
> an
> > > AS
> > > > > or
> > > > > > > not.
> > > > > > [TOLGA]If what you mean is, that it really
> > > does
> > > > > not
> > > > > > matter for which SGP ASPs went ACTIVE, I
> > > disagree,
> > > > > at
> > > > > > least SG, SGP is part of should matter.
> Apart
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran

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



From mailnull@www1.ietf.org  Fri Jun  6 18:14:03 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16466
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 18:14:03 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56MDc203372
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 18:13:38 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56MDNB03357;
	Fri, 6 Jun 2003 18:13:24 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56MAVB03303
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 18:10:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16125
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 18:10:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OPNw-00073b-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 18:08:32 -0400
Received: from web12809.mail.yahoo.com ([216.136.174.136])
	by ietf-mx with smtp (Exim 4.12)
	id 19OPNv-00073Y-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 18:08:31 -0400
Message-ID: <20030606221026.51447.qmail@web12809.mail.yahoo.com>
Received: from [208.255.120.2] by web12809.mail.yahoo.com via HTTP; Fri, 06 Jun 2003 15:10:26 PDT
Date: Fri, 6 Jun 2003 15:10:26 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: RE: [Sigtran] M3UA : Multiple SGPs in SG
To: sigtran@ietf.org
In-Reply-To: <ACEMIJONPBBPDLOKCABHMEJACAAA.umesh@ccpu.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Umesh,

1)Then think just the opposite, ASPs use SG wide
number and SG uses counter per SGP. This time ASP
sends DATA and SGPs will drop it.

2)The sentence you are referring was intended for
counting number of ACTIVE ASPs per SGP. But I agree,
it is not clear(it also does not speak about counter
per SG, so if you take the sentence literally, should
ASPs consider AS ACTIVE, if activations are done on
SGPs belonging to different SGs? SGs won't see AS as
ACTIVE in such a case)

     Tolga
--- Umesh Vats <umesh@ccpu.com> wrote:
> [TOLGA]What I did say was, for n+k case -if it is
> allowed to use n per SG or per SGP-, if SG uses
> SGwide
> number of ACTIVE ASPs and ASPs use the per SGP
> counter, there will be an inconsistency between SGPs
> and ASPs, when to start routing DATA to/from ASP.
> 
> [UMESH] This shouldn't happen.
> All ASPs serving an AS can also use n as SG wide
> value through inter communication between them.
> Following statement
> in RFC says this. 
> 
> "For the n+k redundancy case, ASPs which are in that
> AS should
>    coordinate among themselves the number of active
> ASPs in the AS, and
>    should start sending traffic only after n ASPs
> are active."
> 
> 
> Umesh
> 
> -----Original Message-----
> From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> Tolga Asveren
> Sent: Friday, June 06, 2003 2:18 PM
> To: sigtran@ietf.org
> Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
> 
> 
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Go back and read the threads.
> > 
> > IIRC you claimed that there would be some
> > "interoperability" problem from following
> > the RFC, but did not point out what that
> > problem might be.
> > 
> > Could you explain now?
> [TOLGA]What I did say was, for n+k case -if it is
> allowed to use n per SG or per SGP-, if SG uses
> SGwide
> number of ACTIVE ASPs and ASPs use the per SGP
> counter, there will be an inconsistency between SGPs
> and ASPs, when to start routing DATA to/from ASP.
> > 
> > --brian
> > 
> > Tolga Asveren wrote:                              
>  
> >                                 (Fri, 06 Jun 2003
> > 13:40:16)
> > > Brian,
> > > 
> > > The "MAY" in the original message is the one
> about
> > > internal forwarding of messages in SG.
> > > "Rerouting of traffic between the SGPs MAY also
> be
> > > supported."
> > > 
> > > And for INACTIVE to ACTIVE transition for n+k
> > case, I
> > > think different than you. The consensus was to
> > change
> > > ACTIVE to PENDING transition, at least to my
> > > understanding.
> > > 
> > >    Tolga
> > > --- "Brian F. G. Bidulock"
> <bidulock@openss7.org>
> > > wrote:
> > > > Tolga,
> > > > 
> > > > Because the RFC represents the concensus and
> the
> > > > IG currently goes against concensus.  That
> > section
> > > > of the IG thay you and Javier dreamed up needs
> > to
> > > > be deleted.
> > > > 
> > > > --brian
> > > > 
> > > > 
> > > > Tolga Asveren wrote:                          
>  
> >    
> > > >                                 (Fri, 06 Jun
> > 2003
> > > > 13:06:08)
> > > > > Brian,
> > > > > --- "Brian F. G. Bidulock"
> > <bidulock@openss7.org>
> > > > > wrote:
> > > > > > Tolga,
> > > > > > 
> > > > > > There was no such agreement.
> > > > > [TOLGA]If so, why is it a "MAY" in RFC?
> > > > > > 
> > > > > > --brian
> > > > > > 
> > > > > > Tolga Asveren wrote:                      
>  
> >    
> > > >    
> > > > > >                                 (Fri, 06
> Jun
> > > > 2003
> > > > > > 09:46:09)
> > > > > > > Hi Umesh,
> > > > > > > --- Umesh Vats <umesh@ccpu.com> wrote:
> > > > > > > > Hi Tolga
> > > > > > > > 
> > > > > > > > The following text exists in
> > implementor's
> > > > > > guide.
> > > > > > > > 
> > > > > > > >                    "An SGP or IPSP,
> upon
> > > > > > reception
> > > > > > > > of an ASP Active message
> > > > > > > > for the first
> > > > > > > >                     ASP in a Loadshare
> > AS,
> > > > > > SHOULD
> > > > > > > > NOT direct traffic to a
> > > > > > > > newly active
> > > > > > > >                     ASP until it
> > determines
> > > > that
> > > > > > > > there are sufficient
> > > > > > > > resources to handle
> > > > > > > >                     the expected load
> > (e.g.,
> > > > > > until
> > > > > > > > there are "n" ASPs in
> > > > > > > > state ASP-ACTIVE
> > > > > > > >                     in the AS).  In
> this
> > > > case,
> > > > > > the
> > > > > > > > SGP or IPSP SHOULD
> > > > > > > > withhold the Notify
> > > > > > > >                     (AS-ACTIVE) until
> > there
> > > > are
> > > > > > > > sufficient resources."
> > > > > > > > 
> > > > > > > > On SG, n ASPs must be active for an AS
> > to
> > > > before
> > > > > > an
> > > > > > > > AS is made active. It
> > > > > > > > doesn't
> > > > > > > > matter whether they went ACTIVE from
> the
> > > > same
> > > > > > SGP or
> > > > > > > > different SGPs.
> > > > > > > > 
> > > > > > > > Although the state of each remote ASP
> is
> > > > > > maintained
> > > > > > > > in the AS, the overall
> > > > > > > > AS is
> > > > > > > > visible to whole SG. The following
> > statement
> > > > in
> > > > > > RFC
> > > > > > > > 3332 helps :
> > > > > > > >  " Where an SG contains more than one
> > SGP,
> > > > the
> > > > > > MTP3
> > > > > > > > routeset, SPMC and
> > > > > > > >    remote AS/ASP states of each SGP
> > SHOULD
> > > > be
> > > > > > > > coordinated across all the
> > > > > > > >    SGPs.  Rerouting of traffic between
> > the
> > > > SGPs
> > > > > > MAY
> > > > > > > > also be supported."
> > > > > > > [TOLGA]This is the place I think a bit
> > > > different.
> > > > > > > Please note the "MAY" in the last
> > sentence. I
> > > > > > think it
> > > > > > > was agreed not to use  a "SHOULD" here
> to
> > not
> > > > > > force
> > > > > > > internal routing. (BTW, I think even the
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 18:20:30 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16820
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 18:20:30 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56MK6G03607
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 18:20:06 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56MJrB03551;
	Fri, 6 Jun 2003 18:19:53 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56MHNB03472
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 18:17:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16714
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 18:17:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OPUZ-00075m-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 18:15:23 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[V5TD8wHqLkLrhaqSID5teze9hpul0uxd])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OPUZ-00075j-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 18:15:23 -0400
Received: from ns.pigworks.openss7.net (IDENT:/+/S/ZqAuN98Fy46pk/Rerabv+8KwOlg@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h56MHHF10210;
	Fri, 6 Jun 2003 16:17:17 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h56MHHF05852;
	Fri, 6 Jun 2003 16:17:17 -0600
Date: Fri, 6 Jun 2003 16:17:17 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
Message-ID: <20030606161717.A5827@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <ACEMIJONPBBPDLOKCABHMEJACAAA.umesh@ccpu.com> <20030606221026.51447.qmail@web12809.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030606221026.51447.qmail@web12809.mail.yahoo.com>; from tolga_asveren@yahoo.com on Fri, Jun 06, 2003 at 03:10:26PM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

Tolga Asveren wrote:                                                                 (Fri, 06 Jun 2003 15:10:26)
> Umesh,
> 
> 1)Then think just the opposite, ASPs use SG wide
> number and SG uses counter per SGP. This time ASP
> sends DATA and SGPs will drop it.

Why?  Where does it way that the SGP must drop a message
received from the ASPs?  Why are you dropping it?

--brian

> 
> 2)The sentence you are referring was intended for
> counting number of ACTIVE ASPs per SGP. But I agree,
> it is not clear(it also does not speak about counter
> per SG, so if you take the sentence literally, should
> ASPs consider AS ACTIVE, if activations are done on
> SGPs belonging to different SGs? SGs won't see AS as
> ACTIVE in such a case)
> 
>      Tolga
> --- Umesh Vats <umesh@ccpu.com> wrote:
> > [TOLGA]What I did say was, for n+k case -if it is
> > allowed to use n per SG or per SGP-, if SG uses
> > SGwide
> > number of ACTIVE ASPs and ASPs use the per SGP
> > counter, there will be an inconsistency between SGPs
> > and ASPs, when to start routing DATA to/from ASP.
> > 
> > [UMESH] This shouldn't happen.
> > All ASPs serving an AS can also use n as SG wide
> > value through inter communication between them.
> > Following statement
> > in RFC says this. 
> > 
> > "For the n+k redundancy case, ASPs which are in that
> > AS should
> >    coordinate among themselves the number of active
> > ASPs in the AS, and
> >    should start sending traffic only after n ASPs
> > are active."
> > 
> > 
> > Umesh
> > 
> > -----Original Message-----
> > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Tolga Asveren
> > Sent: Friday, June 06, 2003 2:18 PM
> > To: sigtran@ietf.org
> > Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
> > 
> > 
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > Tolga,
> > > 
> > > Go back and read the threads.
> > > 
> > > IIRC you claimed that there would be some
> > > "interoperability" problem from following
> > > the RFC, but did not point out what that
> > > problem might be.
> > > 
> > > Could you explain now?
> > [TOLGA]What I did say was, for n+k case -if it is
> > allowed to use n per SG or per SGP-, if SG uses
> > SGwide
> > number of ACTIVE ASPs and ASPs use the per SGP
> > counter, there will be an inconsistency between SGPs
> > and ASPs, when to start routing DATA to/from ASP.
> > > 
> > > --brian
> > > 
> > > Tolga Asveren wrote:                              
> >  
> > >                                 (Fri, 06 Jun 2003
> > > 13:40:16)
> > > > Brian,
> > > > 
> > > > The "MAY" in the original message is the one
> > about
> > > > internal forwarding of messages in SG.
> > > > "Rerouting of traffic between the SGPs MAY also
> > be
> > > > supported."
> > > > 
> > > > And for INACTIVE to ACTIVE transition for n+k
> > > case, I
> > > > think different than you. The consensus was to
> > > change
> > > > ACTIVE to PENDING transition, at least to my
> > > > understanding.
> > > > 
> > > >    Tolga
> > > > --- "Brian F. G. Bidulock"
> > <bidulock@openss7.org>
> > > > wrote:
> > > > > Tolga,
> > > > > 
> > > > > Because the RFC represents the concensus and
> > the
> > > > > IG currently goes against concensus.  That
> > > section
> > > > > of the IG thay you and Javier dreamed up needs
> > > to
> > > > > be deleted.
> > > > > 
> > > > > --brian
> > > > > 
> > > > > 
> > > > > Tolga Asveren wrote:                          
> >  
> > >    
> > > > >                                 (Fri, 06 Jun
> > > 2003
> > > > > 13:06:08)
> > > > > > Brian,
> > > > > > --- "Brian F. G. Bidulock"
> > > <bidulock@openss7.org>
> > > > > > wrote:
> > > > > > > Tolga,
> > > > > > > 
> > > > > > > There was no such agreement.
> > > > > > [TOLGA]If so, why is it a "MAY" in RFC?
> > > > > > > 
> > > > > > > --brian
> > > > > > > 
> > > > > > > Tolga Asveren wrote:                      
> >  
> > >    
> > > > >    
> > > > > > >                                 (Fri, 06
> > Jun
> > > > > 2003
> > > > > > > 09:46:09)
> > > > > > > > Hi Umesh,
> > > > > > > > --- Umesh Vats <umesh@ccpu.com> wrote:
> > > > > > > > > Hi Tolga
> > > > > > > > > 
> > > > > > > > > The following text exists in
> > > implementor's
> > > > > > > guide.
> > > > > > > > > 
> > > > > > > > >                    "An SGP or IPSP,
> > upon
> > > > > > > reception
> > > > > > > > > of an ASP Active message
> > > > > > > > > for the first
> > > > > > > > >                     ASP in a Loadshare
> > > AS,
> > > > > > > SHOULD
> > > > > > > > > NOT direct traffic to a
> > > > > > > > > newly active
> > > > > > > > >                     ASP until it
> > > determines
> > > > > that
> > > > > > > > > there are sufficient
> > > > > > > > > resources to handle
> > > > > > > > >                     the expected load
> > > (e.g.,
> > > > > > > until
> > > > > > > > > there are "n" ASPs in
> > > > > > > > > state ASP-ACTIVE
> > > > > > > > >                     in the AS).  In
> > this
> > > > > case,
> > > > > > > the
> > > > > > > > > SGP or IPSP SHOULD
> > > > > > > > > withhold the Notify
> > > > > > > > >                     (AS-ACTIVE) until
> > > there
> > > > > are
> > > > > > > > > sufficient resources."
> > > > > > > > > 
> > > > > > > > > On SG, n ASPs must be active for an AS
> > > to
> > > > > before
> > > > > > > an
> > > > > > > > > AS is made active. It
> > > > > > > > > doesn't
> > > > > > > > > matter whether they went ACTIVE from
> > the
> > > > > same
> > > > > > > SGP or
> > > > > > > > > different SGPs.
> > > > > > > > > 
> > > > > > > > > Although the state of each remote ASP
> > is
> > > > > > > maintained
> > > > > > > > > in the AS, the overall
> > > > > > > > > AS is
> > > > > > > > > visible to whole SG. The following
> > > statement
> > > > > in
> > > > > > > RFC
> > > > > > > > > 3332 helps :
> > > > > > > > >  " Where an SG contains more than one
> > > SGP,
> > > > > the
> > > > > > > MTP3
> > > > > > > > > routeset, SPMC and
> > > > > > > > >    remote AS/ASP states of each SGP
> > > SHOULD
> > > > > be
> > > > > > > > > coordinated across all the
> > > > > > > > >    SGPs.  Rerouting of traffic between
> > > the
> > > > > SGPs
> > > > > > > MAY
> > > > > > > > > also be supported."
> > > > > > > > [TOLGA]This is the place I think a bit
> > > > > different.
> > > > > > > > Please note the "MAY" in the last
> > > sentence. I
> > > > > > > think it
> > > > > > > > was agreed not to use  a "SHOULD" here
> > to
> > > not
> > > > > > > force
> > > > > > > > internal routing. (BTW, I think even the
> > 
> === message truncated ===
> 
> 
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 18:25:30 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16954
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 18:25:30 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56MP6r03758
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 18:25:06 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56MOoB03739;
	Fri, 6 Jun 2003 18:24:50 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56MM4B03658
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 18:22:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16856
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 18:21:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OPZ6-00077Q-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 18:20:04 -0400
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OPZ3-00077N-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 18:20:02 -0400
Received: from [172.16.1.40] (helo=ccpu00251)
	by smtp.ccpu.com with smtp (Exim 4.20 #1 (Debian))
	id 19OPae-000687-Qu; Fri, 06 Jun 2003 15:21:40 -0700
Reply-To: <umesh@ccpu.com>
From: "Umesh Vats" <umesh@ccpu.com>
To: "Tolga Asveren" <tolga_asveren@yahoo.com>, <sigtran@ietf.org>
Subject: RE: [Sigtran] M3UA : Multiple SGPs in SG
Date: Fri, 6 Jun 2003 15:24:59 -0700
Message-ID: <ACEMIJONPBBPDLOKCABHMEJBCAAA.umesh@ccpu.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <20030606221026.51447.qmail@web12809.mail.yahoo.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Tolga

What I mean is that both, the SG and the ASPs serving an AS for that SG
should use same value of n.  

Like in SS7 network, two adjacent pointcodes configure that link set
should be active only if n links in it are active. The same n value is
valid for both the adjacent point code.

Umesh
 

-----Original Message-----
From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
Tolga Asveren
Sent: Friday, June 06, 2003 3:10 PM
To: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA : Multiple SGPs in SG


Umesh,

1)Then think just the opposite, ASPs use SG wide
number and SG uses counter per SGP. This time ASP
sends DATA and SGPs will drop it.

2)The sentence you are referring was intended for
counting number of ACTIVE ASPs per SGP. But I agree,
it is not clear(it also does not speak about counter
per SG, so if you take the sentence literally, should
ASPs consider AS ACTIVE, if activations are done on
SGPs belonging to different SGs? SGs won't see AS as
ACTIVE in such a case)

     Tolga
--- Umesh Vats <umesh@ccpu.com> wrote:
> [TOLGA]What I did say was, for n+k case -if it is
> allowed to use n per SG or per SGP-, if SG uses
> SGwide
> number of ACTIVE ASPs and ASPs use the per SGP
> counter, there will be an inconsistency between SGPs
> and ASPs, when to start routing DATA to/from ASP.
> 
> [UMESH] This shouldn't happen.
> All ASPs serving an AS can also use n as SG wide
> value through inter communication between them.
> Following statement
> in RFC says this. 
> 
> "For the n+k redundancy case, ASPs which are in that
> AS should
>    coordinate among themselves the number of active
> ASPs in the AS, and
>    should start sending traffic only after n ASPs
> are active."
> 
> 
> Umesh
> 
> -----Original Message-----
> From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> Tolga Asveren
> Sent: Friday, June 06, 2003 2:18 PM
> To: sigtran@ietf.org
> Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
> 
> 
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Go back and read the threads.
> > 
> > IIRC you claimed that there would be some
> > "interoperability" problem from following
> > the RFC, but did not point out what that
> > problem might be.
> > 
> > Could you explain now?
> [TOLGA]What I did say was, for n+k case -if it is
> allowed to use n per SG or per SGP-, if SG uses
> SGwide
> number of ACTIVE ASPs and ASPs use the per SGP
> counter, there will be an inconsistency between SGPs
> and ASPs, when to start routing DATA to/from ASP.
> > 
> > --brian
> > 
> > Tolga Asveren wrote:                              
>  
> >                                 (Fri, 06 Jun 2003
> > 13:40:16)
> > > Brian,
> > > 
> > > The "MAY" in the original message is the one
> about
> > > internal forwarding of messages in SG.
> > > "Rerouting of traffic between the SGPs MAY also
> be
> > > supported."
> > > 
> > > And for INACTIVE to ACTIVE transition for n+k
> > case, I
> > > think different than you. The consensus was to
> > change
> > > ACTIVE to PENDING transition, at least to my
> > > understanding.
> > > 
> > >    Tolga
> > > --- "Brian F. G. Bidulock"
> <bidulock@openss7.org>
> > > wrote:
> > > > Tolga,
> > > > 
> > > > Because the RFC represents the concensus and
> the
> > > > IG currently goes against concensus.  That
> > section
> > > > of the IG thay you and Javier dreamed up needs
> > to
> > > > be deleted.
> > > > 
> > > > --brian
> > > > 
> > > > 
> > > > Tolga Asveren wrote:                          
>  
> >    
> > > >                                 (Fri, 06 Jun
> > 2003
> > > > 13:06:08)
> > > > > Brian,
> > > > > --- "Brian F. G. Bidulock"
> > <bidulock@openss7.org>
> > > > > wrote:
> > > > > > Tolga,
> > > > > > 
> > > > > > There was no such agreement.
> > > > > [TOLGA]If so, why is it a "MAY" in RFC?
> > > > > > 
> > > > > > --brian
> > > > > > 
> > > > > > Tolga Asveren wrote:                      
>  
> >    
> > > >    
> > > > > >                                 (Fri, 06
> Jun
> > > > 2003
> > > > > > 09:46:09)
> > > > > > > Hi Umesh,
> > > > > > > --- Umesh Vats <umesh@ccpu.com> wrote:
> > > > > > > > Hi Tolga
> > > > > > > > 
> > > > > > > > The following text exists in
> > implementor's
> > > > > > guide.
> > > > > > > > 
> > > > > > > >                    "An SGP or IPSP,
> upon
> > > > > > reception
> > > > > > > > of an ASP Active message
> > > > > > > > for the first
> > > > > > > >                     ASP in a Loadshare
> > AS,
> > > > > > SHOULD
> > > > > > > > NOT direct traffic to a
> > > > > > > > newly active
> > > > > > > >                     ASP until it
> > determines
> > > > that
> > > > > > > > there are sufficient
> > > > > > > > resources to handle
> > > > > > > >                     the expected load
> > (e.g.,
> > > > > > until
> > > > > > > > there are "n" ASPs in
> > > > > > > > state ASP-ACTIVE
> > > > > > > >                     in the AS).  In
> this
> > > > case,
> > > > > > the
> > > > > > > > SGP or IPSP SHOULD
> > > > > > > > withhold the Notify
> > > > > > > >                     (AS-ACTIVE) until
> > there
> > > > are
> > > > > > > > sufficient resources."
> > > > > > > > 
> > > > > > > > On SG, n ASPs must be active for an AS
> > to
> > > > before
> > > > > > an
> > > > > > > > AS is made active. It
> > > > > > > > doesn't
> > > > > > > > matter whether they went ACTIVE from
> the
> > > > same
> > > > > > SGP or
> > > > > > > > different SGPs.
> > > > > > > > 
> > > > > > > > Although the state of each remote ASP
> is
> > > > > > maintained
> > > > > > > > in the AS, the overall
> > > > > > > > AS is
> > > > > > > > visible to whole SG. The following
> > statement
> > > > in
> > > > > > RFC
> > > > > > > > 3332 helps :
> > > > > > > >  " Where an SG contains more than one
> > SGP,
> > > > the
> > > > > > MTP3
> > > > > > > > routeset, SPMC and
> > > > > > > >    remote AS/ASP states of each SGP
> > SHOULD
> > > > be
> > > > > > > > coordinated across all the
> > > > > > > >    SGPs.  Rerouting of traffic between
> > the
> > > > SGPs
> > > > > > MAY
> > > > > > > > also be supported."
> > > > > > > [TOLGA]This is the place I think a bit
> > > > different.
> > > > > > > Please note the "MAY" in the last
> > sentence. I
> > > > > > think it
> > > > > > > was agreed not to use  a "SHOULD" here
> to
> > not
> > > > > > force
> > > > > > > internal routing. (BTW, I think even the
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran

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



From mailnull@www1.ietf.org  Fri Jun  6 18:31:34 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17107
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 18:31:33 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56MVA903981
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 18:31:10 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56MUrB03932;
	Fri, 6 Jun 2003 18:30:53 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56MSSB03848
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 18:28:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17059
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 18:28:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OPfI-0007AA-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 18:26:28 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[lEaBsZ+jzSLWRHk01ALzA8pz33y9Pqmk])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OPfH-0007A7-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 18:26:27 -0400
Received: from ns.pigworks.openss7.net (IDENT:rRV87uwUCHwPSwC56M5i0kHJN0MmUfh6@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h56MSMF10330;
	Fri, 6 Jun 2003 16:28:22 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h56MSMX05985;
	Fri, 6 Jun 2003 16:28:22 -0600
Date: Fri, 6 Jun 2003 16:28:21 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Umesh Vats <umesh@ccpu.com>
Cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
Message-ID: <20030606162821.B5827@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Umesh Vats <umesh@ccpu.com>,
	Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030606221026.51447.qmail@web12809.mail.yahoo.com> <ACEMIJONPBBPDLOKCABHMEJBCAAA.umesh@ccpu.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <ACEMIJONPBBPDLOKCABHMEJBCAAA.umesh@ccpu.com>; from umesh@ccpu.com on Fri, Jun 06, 2003 at 03:24:59PM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Umesh,

The SS7 network does not behave as you describe.  There is no
value 'n' for links.

--brian


Umesh Vats wrote:                                                                    (Fri, 06 Jun 2003 15:24:59)
> Hi Tolga
> 
> What I mean is that both, the SG and the ASPs serving an AS for that SG
> should use same value of n.  
> 
> Like in SS7 network, two adjacent pointcodes configure that link set
> should be active only if n links in it are active. The same n value is
> valid for both the adjacent point code.
> 
> Umesh
>  
> 
> -----Original Message-----
> From: sigtran-admin@ietf.org [mailto:sigtran-admin@ietf.org]On Behalf Of
> Tolga Asveren
> Sent: Friday, June 06, 2003 3:10 PM
> To: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA : Multiple SGPs in SG
> 
> 
> Umesh,
> 
> 1)Then think just the opposite, ASPs use SG wide
> number and SG uses counter per SGP. This time ASP
> sends DATA and SGPs will drop it.
> 
> 2)The sentence you are referring was intended for
> counting number of ACTIVE ASPs per SGP. But I agree,
> it is not clear(it also does not speak about counter
> per SG, so if you take the sentence literally, should
> ASPs consider AS ACTIVE, if activations are done on
> SGPs belonging to different SGs? SGs won't see AS as
> ACTIVE in such a case)
> 
>      Tolga
> --- Umesh Vats <umesh@ccpu.com> wrote:
> > [TOLGA]What I did say was, for n+k case -if it is
> > allowed to use n per SG or per SGP-, if SG uses
> > SGwide
> > number of ACTIVE ASPs and ASPs use the per SGP
> > counter, there will be an inconsistency between SGPs
> > and ASPs, when to start routing DATA to/from ASP.
> > 
> > [UMESH] This shouldn't happen.
> > All ASPs serving an AS can also use n as SG wide
> > value through inter communication between them.
> > Following statement
> > in RFC says this. 
> > 
> > "For the n+k redundancy case, ASPs which are in that
> > AS should
> >    coordinate among themselves the number of active
> > ASPs in the AS, and
> >    should start sending traffic only after n ASPs
> > are active."
> > 
> > 
> > Umesh
> > 
> > -----Original Message-----
> > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Tolga Asveren
> > Sent: Friday, June 06, 2003 2:18 PM
> > To: sigtran@ietf.org
> > Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
> > 
> > 
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > Tolga,
> > > 
> > > Go back and read the threads.
> > > 
> > > IIRC you claimed that there would be some
> > > "interoperability" problem from following
> > > the RFC, but did not point out what that
> > > problem might be.
> > > 
> > > Could you explain now?
> > [TOLGA]What I did say was, for n+k case -if it is
> > allowed to use n per SG or per SGP-, if SG uses
> > SGwide
> > number of ACTIVE ASPs and ASPs use the per SGP
> > counter, there will be an inconsistency between SGPs
> > and ASPs, when to start routing DATA to/from ASP.
> > > 
> > > --brian
> > > 
> > > Tolga Asveren wrote:                              
> >  
> > >                                 (Fri, 06 Jun 2003
> > > 13:40:16)
> > > > Brian,
> > > > 
> > > > The "MAY" in the original message is the one
> > about
> > > > internal forwarding of messages in SG.
> > > > "Rerouting of traffic between the SGPs MAY also
> > be
> > > > supported."
> > > > 
> > > > And for INACTIVE to ACTIVE transition for n+k
> > > case, I
> > > > think different than you. The consensus was to
> > > change
> > > > ACTIVE to PENDING transition, at least to my
> > > > understanding.
> > > > 
> > > >    Tolga
> > > > --- "Brian F. G. Bidulock"
> > <bidulock@openss7.org>
> > > > wrote:
> > > > > Tolga,
> > > > > 
> > > > > Because the RFC represents the concensus and
> > the
> > > > > IG currently goes against concensus.  That
> > > section
> > > > > of the IG thay you and Javier dreamed up needs
> > > to
> > > > > be deleted.
> > > > > 
> > > > > --brian
> > > > > 
> > > > > 
> > > > > Tolga Asveren wrote:                          
> >  
> > >    
> > > > >                                 (Fri, 06 Jun
> > > 2003
> > > > > 13:06:08)
> > > > > > Brian,
> > > > > > --- "Brian F. G. Bidulock"
> > > <bidulock@openss7.org>
> > > > > > wrote:
> > > > > > > Tolga,
> > > > > > > 
> > > > > > > There was no such agreement.
> > > > > > [TOLGA]If so, why is it a "MAY" in RFC?
> > > > > > > 
> > > > > > > --brian
> > > > > > > 
> > > > > > > Tolga Asveren wrote:                      
> >  
> > >    
> > > > >    
> > > > > > >                                 (Fri, 06
> > Jun
> > > > > 2003
> > > > > > > 09:46:09)
> > > > > > > > Hi Umesh,
> > > > > > > > --- Umesh Vats <umesh@ccpu.com> wrote:
> > > > > > > > > Hi Tolga
> > > > > > > > > 
> > > > > > > > > The following text exists in
> > > implementor's
> > > > > > > guide.
> > > > > > > > > 
> > > > > > > > >                    "An SGP or IPSP,
> > upon
> > > > > > > reception
> > > > > > > > > of an ASP Active message
> > > > > > > > > for the first
> > > > > > > > >                     ASP in a Loadshare
> > > AS,
> > > > > > > SHOULD
> > > > > > > > > NOT direct traffic to a
> > > > > > > > > newly active
> > > > > > > > >                     ASP until it
> > > determines
> > > > > that
> > > > > > > > > there are sufficient
> > > > > > > > > resources to handle
> > > > > > > > >                     the expected load
> > > (e.g.,
> > > > > > > until
> > > > > > > > > there are "n" ASPs in
> > > > > > > > > state ASP-ACTIVE
> > > > > > > > >                     in the AS).  In
> > this
> > > > > case,
> > > > > > > the
> > > > > > > > > SGP or IPSP SHOULD
> > > > > > > > > withhold the Notify
> > > > > > > > >                     (AS-ACTIVE) until
> > > there
> > > > > are
> > > > > > > > > sufficient resources."
> > > > > > > > > 
> > > > > > > > > On SG, n ASPs must be active for an AS
> > > to
> > > > > before
> > > > > > > an
> > > > > > > > > AS is made active. It
> > > > > > > > > doesn't
> > > > > > > > > matter whether they went ACTIVE from
> > the
> > > > > same
> > > > > > > SGP or
> > > > > > > > > different SGPs.
> > > > > > > > > 
> > > > > > > > > Although the state of each remote ASP
> > is
> > > > > > > maintained
> > > > > > > > > in the AS, the overall
> > > > > > > > > AS is
> > > > > > > > > visible to whole SG. The following
> > > statement
> > > > > in
> > > > > > > RFC
> > > > > > > > > 3332 helps :
> > > > > > > > >  " Where an SG contains more than one
> > > SGP,
> > > > > the
> > > > > > > MTP3
> > > > > > > > > routeset, SPMC and
> > > > > > > > >    remote AS/ASP states of each SGP
> > > SHOULD
> > > > > be
> > > > > > > > > coordinated across all the
> > > > > > > > >    SGPs.  Rerouting of traffic between
> > > the
> > > > > SGPs
> > > > > > > MAY
> > > > > > > > > also be supported."
> > > > > > > > [TOLGA]This is the place I think a bit
> > > > > different.
> > > > > > > > Please note the "MAY" in the last
> > > sentence. I
> > > > > > > think it
> > > > > > > > was agreed not to use  a "SHOULD" here
> > to
> > > not
> > > > > > > force
> > > > > > > > internal routing. (BTW, I think even the
> > 
> === message truncated ===
> 
> 
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 18:35:27 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17188
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 18:35:27 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56MZ3Z04111
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 18:35:03 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56MYmB04075;
	Fri, 6 Jun 2003 18:34:48 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56MW9B04009
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 18:32:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17128
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 18:32:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OPir-0007BR-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 18:30:09 -0400
Received: from web12809.mail.yahoo.com ([216.136.174.136])
	by ietf-mx with smtp (Exim 4.12)
	id 19OPiq-0007BO-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 18:30:08 -0400
Message-ID: <20030606223203.52859.qmail@web12809.mail.yahoo.com>
Received: from [208.255.120.2] by web12809.mail.yahoo.com via HTTP; Fri, 06 Jun 2003 15:32:03 PDT
Date: Fri, 6 Jun 2003 15:32:03 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
To: sigtran@ietf.org
In-Reply-To: <20030606161717.A5827@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Tolga,
> 
> Tolga Asveren wrote:                                
>                                 (Fri, 06 Jun 2003
> 15:10:26)
> > Umesh,
> > 
> > 1)Then think just the opposite, ASPs use SG wide
> > number and SG uses counter per SGP. This time ASP
> > sends DATA and SGPs will drop it.
> 
> Why?  Where does it way that the SGP must drop a
> message
> received from the ASPs?  Why are you dropping it?
[TOLGA]"1.4.2.5 Message Distribution at ASP" and
"4.3.4.3 ASP Active Procedures" are written
unfortunately just by thinking n=1 case(so they speak
of ASP being ACTIVE instead of AS). After looking now,
I think some rewording at those places is also
necessary. To me, it is clear that if SGP sees AS as
INACTIVE that it should drop incoming DATA from this
AS. 
> 
> --brian
> 
> > 
> > 2)The sentence you are referring was intended for
> > counting number of ACTIVE ASPs per SGP. But I
> agree,
> > it is not clear(it also does not speak about
> counter
> > per SG, so if you take the sentence literally,
> should
> > ASPs consider AS ACTIVE, if activations are done
> on
> > SGPs belonging to different SGs? SGs won't see AS
> as
> > ACTIVE in such a case)
> > 
> >      Tolga
> > --- Umesh Vats <umesh@ccpu.com> wrote:
> > > [TOLGA]What I did say was, for n+k case -if it
> is
> > > allowed to use n per SG or per SGP-, if SG uses
> > > SGwide
> > > number of ACTIVE ASPs and ASPs use the per SGP
> > > counter, there will be an inconsistency between
> SGPs
> > > and ASPs, when to start routing DATA to/from
> ASP.
> > > 
> > > [UMESH] This shouldn't happen.
> > > All ASPs serving an AS can also use n as SG wide
> > > value through inter communication between them.
> > > Following statement
> > > in RFC says this. 
> > > 
> > > "For the n+k redundancy case, ASPs which are in
> that
> > > AS should
> > >    coordinate among themselves the number of
> active
> > > ASPs in the AS, and
> > >    should start sending traffic only after n
> ASPs
> > > are active."
> > > 
> > > 
> > > Umesh
> > > 
> > > -----Original Message-----
> > > From: sigtran-admin@ietf.org
> > > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > > Tolga Asveren
> > > Sent: Friday, June 06, 2003 2:18 PM
> > > To: sigtran@ietf.org
> > > Subject: Re: [Sigtran] M3UA : Multiple SGPs in
> SG
> > > 
> > > 
> > > Brian,
> > > --- "Brian F. G. Bidulock"
> <bidulock@openss7.org>
> > > wrote:
> > > > Tolga,
> > > > 
> > > > Go back and read the threads.
> > > > 
> > > > IIRC you claimed that there would be some
> > > > "interoperability" problem from following
> > > > the RFC, but did not point out what that
> > > > problem might be.
> > > > 
> > > > Could you explain now?
> > > [TOLGA]What I did say was, for n+k case -if it
> is
> > > allowed to use n per SG or per SGP-, if SG uses
> > > SGwide
> > > number of ACTIVE ASPs and ASPs use the per SGP
> > > counter, there will be an inconsistency between
> SGPs
> > > and ASPs, when to start routing DATA to/from
> ASP.
> > > > 
> > > > --brian
> > > > 
> > > > Tolga Asveren wrote:                          
>    
> > >  
> > > >                                 (Fri, 06 Jun
> 2003
> > > > 13:40:16)
> > > > > Brian,
> > > > > 
> > > > > The "MAY" in the original message is the one
> > > about
> > > > > internal forwarding of messages in SG.
> > > > > "Rerouting of traffic between the SGPs MAY
> also
> > > be
> > > > > supported."
> > > > > 
> > > > > And for INACTIVE to ACTIVE transition for
> n+k
> > > > case, I
> > > > > think different than you. The consensus was
> to
> > > > change
> > > > > ACTIVE to PENDING transition, at least to my
> > > > > understanding.
> > > > > 
> > > > >    Tolga
> > > > > --- "Brian F. G. Bidulock"
> > > <bidulock@openss7.org>
> > > > > wrote:
> > > > > > Tolga,
> > > > > > 
> > > > > > Because the RFC represents the concensus
> and
> > > the
> > > > > > IG currently goes against concensus.  That
> > > > section
> > > > > > of the IG thay you and Javier dreamed up
> needs
> > > > to
> > > > > > be deleted.
> > > > > > 
> > > > > > --brian
> > > > > > 
> > > > > > 
> > > > > > Tolga Asveren wrote:                      
>    
> > >  
> > > >    
> > > > > >                                 (Fri, 06
> Jun
> > > > 2003
> > > > > > 13:06:08)
> > > > > > > Brian,
> > > > > > > --- "Brian F. G. Bidulock"
> > > > <bidulock@openss7.org>
> > > > > > > wrote:
> > > > > > > > Tolga,
> > > > > > > > 
> > > > > > > > There was no such agreement.
> > > > > > > [TOLGA]If so, why is it a "MAY" in RFC?
> > > > > > > > 
> > > > > > > > --brian
> > > > > > > > 
> > > > > > > > Tolga Asveren wrote:                  
>    
> > >  
> > > >    
> > > > > >    
> > > > > > > >                                 (Fri,
> 06
> > > Jun
> > > > > > 2003
> > > > > > > > 09:46:09)
> > > > > > > > > Hi Umesh,
> > > > > > > > > --- Umesh Vats <umesh@ccpu.com>
> wrote:
> > > > > > > > > > Hi Tolga
> > > > > > > > > > 
> > > > > > > > > > The following text exists in
> > > > implementor's
> > > > > > > > guide.
> > > > > > > > > > 
> > > > > > > > > >                    "An SGP or
> IPSP,
> > > upon
> > > > > > > > reception
> > > > > > > > > > of an ASP Active message
> > > > > > > > > > for the first
> > > > > > > > > >                     ASP in a
> Loadshare
> > > > AS,
> > > > > > > > SHOULD
> > > > > > > > > > NOT direct traffic to a
> > > > > > > > > > newly active
> > > > > > > > > >                     ASP until it
> > > > determines
> > > > > > that
> > > > > > > > > > there are sufficient
> > > > > > > > > > resources to handle
> > > > > > > > > >                     the expected
> load
> > > > (e.g.,
> > > > > > > > until
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 18:50:41 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17519
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 18:50:41 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56MoIA05440
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 18:50:18 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56Mo5B05429;
	Fri, 6 Jun 2003 18:50:05 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56MlZB05337
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 18:47:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17468
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 18:47:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OPxm-0007Gj-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 18:45:34 -0400
Received: from web12808.mail.yahoo.com ([216.136.174.43])
	by ietf-mx with smtp (Exim 4.12)
	id 19OPxm-0007Gg-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 18:45:34 -0400
Message-ID: <20030606224729.21500.qmail@web12808.mail.yahoo.com>
Received: from [208.255.120.2] by web12808.mail.yahoo.com via HTTP; Fri, 06 Jun 2003 15:47:29 PDT
Date: Fri, 6 Jun 2003 15:47:29 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: RE: [Sigtran] M3UA : Multiple SGPs in SG
To: sigtran@ietf.org
In-Reply-To: <ACEMIJONPBBPDLOKCABHMEJBCAAA.umesh@ccpu.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Hi Umesh,
--- Umesh Vats <umesh@ccpu.com> wrote:
> Hi Tolga
> 
> What I mean is that both, the SG and the ASPs
> serving an AS for that SG
> should use same value of n.  
[TOLGA]If both sides are using the same scheme, of
course there wouldn't be an inconsistancy. But IMO,
till now the assumption was always to use number of
ACTIVE ASPs per SGP. Using the number per SG, would
put a requirement on the internal design of SG
(internal routing -yes, I agree it is a good to have
feature-) and probably it is better to avoid this.
Afterall, IMO the benefits using n as a counter per SG
are not too much for a real life scenario(maybe just
decreasing number of necessary associations for some
configurations as you pointed out)
> 
> Like in SS7 network, two adjacent pointcodes
> configure that link set
> should be active only if n links in it are active.
> The same n value is
> valid for both the adjacent point code.
> 
> Umesh
>  
> 
> -----Original Message-----
> From: sigtran-admin@ietf.org
> [mailto:sigtran-admin@ietf.org]On Behalf Of
> Tolga Asveren
> Sent: Friday, June 06, 2003 3:10 PM
> To: sigtran@ietf.org
> Subject: RE: [Sigtran] M3UA : Multiple SGPs in SG
> 
> 
> Umesh,
> 
> 1)Then think just the opposite, ASPs use SG wide
> number and SG uses counter per SGP. This time ASP
> sends DATA and SGPs will drop it.
> 
> 2)The sentence you are referring was intended for
> counting number of ACTIVE ASPs per SGP. But I agree,
> it is not clear(it also does not speak about counter
> per SG, so if you take the sentence literally,
> should
> ASPs consider AS ACTIVE, if activations are done on
> SGPs belonging to different SGs? SGs won't see AS as
> ACTIVE in such a case)
> 
>      Tolga
> --- Umesh Vats <umesh@ccpu.com> wrote:
> > [TOLGA]What I did say was, for n+k case -if it is
> > allowed to use n per SG or per SGP-, if SG uses
> > SGwide
> > number of ACTIVE ASPs and ASPs use the per SGP
> > counter, there will be an inconsistency between
> SGPs
> > and ASPs, when to start routing DATA to/from ASP.
> > 
> > [UMESH] This shouldn't happen.
> > All ASPs serving an AS can also use n as SG wide
> > value through inter communication between them.
> > Following statement
> > in RFC says this. 
> > 
> > "For the n+k redundancy case, ASPs which are in
> that
> > AS should
> >    coordinate among themselves the number of
> active
> > ASPs in the AS, and
> >    should start sending traffic only after n ASPs
> > are active."
> > 
> > 
> > Umesh
> > 
> > -----Original Message-----
> > From: sigtran-admin@ietf.org
> > [mailto:sigtran-admin@ietf.org]On Behalf Of
> > Tolga Asveren
> > Sent: Friday, June 06, 2003 2:18 PM
> > To: sigtran@ietf.org
> > Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
> > 
> > 
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > Tolga,
> > > 
> > > Go back and read the threads.
> > > 
> > > IIRC you claimed that there would be some
> > > "interoperability" problem from following
> > > the RFC, but did not point out what that
> > > problem might be.
> > > 
> > > Could you explain now?
> > [TOLGA]What I did say was, for n+k case -if it is
> > allowed to use n per SG or per SGP-, if SG uses
> > SGwide
> > number of ACTIVE ASPs and ASPs use the per SGP
> > counter, there will be an inconsistency between
> SGPs
> > and ASPs, when to start routing DATA to/from ASP.
> > > 
> > > --brian
> > > 
> > > Tolga Asveren wrote:                            
>  
> >  
> > >                                 (Fri, 06 Jun
> 2003
> > > 13:40:16)
> > > > Brian,
> > > > 
> > > > The "MAY" in the original message is the one
> > about
> > > > internal forwarding of messages in SG.
> > > > "Rerouting of traffic between the SGPs MAY
> also
> > be
> > > > supported."
> > > > 
> > > > And for INACTIVE to ACTIVE transition for n+k
> > > case, I
> > > > think different than you. The consensus was to
> > > change
> > > > ACTIVE to PENDING transition, at least to my
> > > > understanding.
> > > > 
> > > >    Tolga
> > > > --- "Brian F. G. Bidulock"
> > <bidulock@openss7.org>
> > > > wrote:
> > > > > Tolga,
> > > > > 
> > > > > Because the RFC represents the concensus and
> > the
> > > > > IG currently goes against concensus.  That
> > > section
> > > > > of the IG thay you and Javier dreamed up
> needs
> > > to
> > > > > be deleted.
> > > > > 
> > > > > --brian
> > > > > 
> > > > > 
> > > > > Tolga Asveren wrote:                        
>  
> >  
> > >    
> > > > >                                 (Fri, 06 Jun
> > > 2003
> > > > > 13:06:08)
> > > > > > Brian,
> > > > > > --- "Brian F. G. Bidulock"
> > > <bidulock@openss7.org>
> > > > > > wrote:
> > > > > > > Tolga,
> > > > > > > 
> > > > > > > There was no such agreement.
> > > > > > [TOLGA]If so, why is it a "MAY" in RFC?
> > > > > > > 
> > > > > > > --brian
> > > > > > > 
> > > > > > > Tolga Asveren wrote:                    
>  
> >  
> > >    
> > > > >    
> > > > > > >                                 (Fri, 06
> > Jun
> > > > > 2003
> > > > > > > 09:46:09)
> > > > > > > > Hi Umesh,
> > > > > > > > --- Umesh Vats <umesh@ccpu.com> wrote:
> > > > > > > > > Hi Tolga
> > > > > > > > > 
> > > > > > > > > The following text exists in
> > > implementor's
> > > > > > > guide.
> > > > > > > > > 
> > > > > > > > >                    "An SGP or IPSP,
> > upon
> > > > > > > reception
> > > > > > > > > of an ASP Active message
> > > > > > > > > for the first
> > > > > > > > >                     ASP in a
> Loadshare
> > > AS,
> > > > > > > SHOULD
> > > > > > > > > NOT direct traffic to a
> > > > > > > > > newly active
> > > > > > > > >                     ASP until it
> > > determines
> > > > > that
> > > > > > > > > there are sufficient
> > > > > > > > > resources to handle
> > > > > > > > >                     the expected
> load
> > > (e.g.,
> > > > > > > until
> > > > > > > > > there are "n" ASPs in
> > > > > > > > > state ASP-ACTIVE
> > > > > > > > >                     in the AS).  In
> > this
> > > > > case,
> > > > > > > the
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 19:16:11 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18012
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 19:16:11 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56NFiB07142
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 19:15:44 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56NFQB07134;
	Fri, 6 Jun 2003 19:15:27 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56NC8B07049
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 19:12:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17976
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 19:12:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OQLc-0007Py-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 19:10:12 -0400
Received: from sjmail.ciena.com ([12.7.169.25] helo=w2ksjexg01.ciena.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OQLb-0007Pv-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 19:10:11 -0400
Received: by w2ksjexg01.ciena.com with Internet Mail Service (5.5.2653.19)
	id <K0T07XGT>; Fri, 6 Jun 2003 16:11:40 -0700
Message-ID: <829F074A10F98943A218DC363D09C92A25018A@w2ksjexg06.oni.com>
From: "Ong, Lyndon" <LyOng@Ciena.com>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>
Date: Fri, 6 Jun 2003 16:15:40 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sigtran] 3057bis
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Hi Folks,

The updated IUA is now out as draft-ietf-sigtran-rfc3057bis-00.txt.  Unless there is
any objection, which there shouldn't since we agreed on the changes when we
LC'd the IUA implementation guide, I will ask our A-Ds to put this on the IESG
agenda for IETF Last Call.  

Thanks,

L. Ong
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun  6 19:21:36 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18270
	for <sigtran-archive@odin.ietf.org>; Fri, 6 Jun 2003 19:21:36 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h56NL9e07403
	for sigtran-archive@odin.ietf.org; Fri, 6 Jun 2003 19:21:09 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56NKwB07394;
	Fri, 6 Jun 2003 19:20:58 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56NIkB07292
	for <sigtran@optimus.ietf.org>; Fri, 6 Jun 2003 19:18:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18096
	for <sigtran@ietf.org>; Fri, 6 Jun 2003 19:18:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OQS1-0007Rt-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 19:16:49 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[yXAsKStakSKc2QGKL2hcHMO/fbJ1FADI])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OQS0-0007Rl-00
	for sigtran@ietf.org; Fri, 06 Jun 2003 19:16:48 -0400
Received: from ns.pigworks.openss7.net (IDENT:Zb609DTiYH4TvQyhqin9fzHWQD4qdDRB@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h56NIhF11135;
	Fri, 6 Jun 2003 17:18:43 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h56NIhk06632;
	Fri, 6 Jun 2003 17:18:43 -0600
Date: Fri, 6 Jun 2003 17:18:42 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
Message-ID: <20030606171842.A6559@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030606161717.A5827@openss7.org> <20030606223203.52859.qmail@web12809.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030606223203.52859.qmail@web12809.mail.yahoo.com>; from tolga_asveren@yahoo.com on Fri, Jun 06, 2003 at 03:32:03PM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

Tolga Asveren wrote:                                                                 (Fri, 06 Jun 2003 15:32:03)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                                
> >                                 (Fri, 06 Jun 2003
> > 15:10:26)
> > > Umesh,
> > > 
> > > 1)Then think just the opposite, ASPs use SG wide
> > > number and SG uses counter per SGP. This time ASP
> > > sends DATA and SGPs will drop it.
> > 
> > Why?  Where does it way that the SGP must drop a
> > message
> > received from the ASPs?  Why are you dropping it?
> [TOLGA]"1.4.2.5 Message Distribution at ASP" and
> "4.3.4.3 ASP Active Procedures" are written
> unfortunately just by thinking n=1 case(so they speak
> of ASP being ACTIVE instead of AS). After looking now,
> I think some rewording at those places is also
> necessary. To me, it is clear that if SGP sees AS as
> INACTIVE that it should drop incoming DATA from this
> AS. 

These sections do not say that an SGP should drop a
message from an ACTIVE ASP.

Why do you drop it?

--brian

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Mon Jun  9 07:54:49 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29114
	for <sigtran-archive@odin.ietf.org>; Mon, 9 Jun 2003 07:54:49 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h59BsLr26711
	for sigtran-archive@odin.ietf.org; Mon, 9 Jun 2003 07:54:21 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h59Bs1B26657;
	Mon, 9 Jun 2003 07:54:02 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h59BjvB26293
	for <sigtran@optimus.ietf.org>; Mon, 9 Jun 2003 07:45:57 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28725;
	Mon, 9 Jun 2003 07:45:55 -0400 (EDT)
Message-Id: <200306091145.HAA28725@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sigtran@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Mon, 09 Jun 2003 07:45:55 -0400
Subject: [Sigtran] I-D ACTION:draft-ietf-sigtran-sctp-mib-10.txt
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Signaling Transport Working Group of the IETF.

	Title		: Stream Control Transmission Protocol Management 
                          Information Base
	Author(s)	: J. Pastor, M. Belinchon
	Filename	: draft-ietf-sigtran-sctp-mib-10.txt
	Pages		: 45
	Date		: 2003-6-6
	
The Stream Control Transmission Protocol (SCTP) is a reliable
transport protocol operating on top of a connectionless packet
network such as IP. It is designed to transport PSTN signaling
messages over the connectionless packet network, but is capable of
broader applications.
This memo defines the Management Information Base (MIB) module which
describes the minimum set of objects needed to manage the
implementation of the SCTP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sigtran-sctp-mib-10.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-sigtran-sctp-mib-10.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sigtran-sctp-mib-10.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-6-6133256.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sigtran-sctp-mib-10.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sigtran-sctp-mib-10.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-6-6133256.I-D@ietf.org>

--OtherAccess--

--NextPart--


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



From mailnull@www1.ietf.org  Tue Jun 10 10:33:39 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03164
	for <sigtran-archive@odin.ietf.org>; Tue, 10 Jun 2003 10:33:39 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5AEXEC26781
	for sigtran-archive@odin.ietf.org; Tue, 10 Jun 2003 10:33:14 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5AEWxB26765;
	Tue, 10 Jun 2003 10:32:59 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5AETeB26523
	for <sigtran@optimus.ietf.org>; Tue, 10 Jun 2003 10:29:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02888
	for <sigtran@ietf.org>; Tue, 10 Jun 2003 10:29:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Pk60-0006rc-00
	for sigtran@ietf.org; Tue, 10 Jun 2003 10:27:32 -0400
Received: from web41802.mail.yahoo.com ([66.218.93.136])
	by ietf-mx with smtp (Exim 4.12)
	id 19Pk5z-0006rG-00
	for sigtran@ietf.org; Tue, 10 Jun 2003 10:27:31 -0400
Message-ID: <20030610142903.25419.qmail@web41802.mail.yahoo.com>
Received: from [65.198.40.51] by web41802.mail.yahoo.com via HTTP; Tue, 10 Jun 2003 09:29:03 CDT
Date: Tue, 10 Jun 2003 09:29:03 -0500 (CDT)
From: =?iso-8859-1?q?Pablo=20Salinas?= <pablopesb@yahoo.com>
To: sigtran@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-2029033701-1055255343=:24762"
Content-Transfer-Encoding: 8bit
Subject: [Sigtran] Network Byte Order
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

--0-2029033701-1055255343=:24762
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi there,
              I have a silly question. The RFC 3331 indicates that M2UA packets should be sent in Network Byte Order (Big Endian Order). So, this means that for the common message header
 
 0                          1                         2                             3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|           Tag (0x1)                  |           Length=8                   |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                 Interface Identifier (integer)                                |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 
M2UA should send first the Tag from left to rigth, then the length parameter and finally the Interface Identifier (from left to right), rigth?
 
Please, can someone help me out?
 
                               greetings,
                                             Pablo Salinas



---------------------------------
Do You Yahoo!?
Todo lo que quieres saber de Estados Unidos, América Latina y el resto del Mundo.
Visíta Yahoo! Noticias.

--0-2029033701-1055255343=:24762
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<DIV>Hi there,</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I have a silly question. The RFC 3331 indicates that M2UA packets should be sent in Network Byte Order (Big Endian Order). So, this means that for the common message header</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;3<BR>&nbsp;0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Tag (0x1)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Length=8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-!
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Interface Identifier (integer)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</DIV>
<DIV>&nbsp;</DIV>
<DIV>M2UA should send first the Tag from left to rigth, then the length parameter and finally the Interface Identifier (from left to right), rigth?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Please,&nbsp;can someone&nbsp;help me out?</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; greetings,</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pablo Salinas</DIV><p><br><hr size=1 noshade><b>Do You Yahoo!?</b><br>
<a href=http://espanol.yahoo.com/mail_tagline/*http://espanol.news.yahoo.com><img src="http://us.i1.yimg.com/us.yimg.com/i/not/dailynews.gif" width=30 height=26 border=0 align=left></a>
Todo lo que quieres saber de Estados Unidos, América Latina y el resto del Mundo.<br>
Visíta <a href=http://espanol.yahoo.com/mail_tagline/*http://espanol.news.yahoo.com>Yahoo! Noticias</a>.<br>
--0-2029033701-1055255343=:24762--
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Tue Jun 10 10:41:39 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03512
	for <sigtran-archive@odin.ietf.org>; Tue, 10 Jun 2003 10:41:39 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5AEfFT28294
	for sigtran-archive@odin.ietf.org; Tue, 10 Jun 2003 10:41:15 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5AEf0B28279;
	Tue, 10 Jun 2003 10:41:00 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5AEcKB28072
	for <sigtran@optimus.ietf.org>; Tue, 10 Jun 2003 10:38:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03455
	for <sigtran@ietf.org>; Tue, 10 Jun 2003 10:38:14 -0400 (EDT)
From: svakumar@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PkEO-0006yv-00
	for sigtran@ietf.org; Tue, 10 Jun 2003 10:36:12 -0400
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PkEM-0006yc-00
	for sigtran@ietf.org; Tue, 10 Jun 2003 10:36:11 -0400
Received: from hindon.hss.co.in (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h5AEZAb06745
	for <sigtran@ietf.org>; Tue, 10 Jun 2003 20:05:10 +0530 (IST)
Received: from ultra.hss.co.in (ultra [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h5AEZ8906740;
	Tue, 10 Jun 2003 20:05:08 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h5AEcac23051;
	Tue, 10 Jun 2003 20:08:36 +0530 (IST)
Subject: Re: [Sigtran] Network Byte Order
To: Pablo Salinas <pablopesb@yahoo.com>
Cc: sigtran@ietf.org
Date: Tue, 10 Jun 2003 20:03:33 +0530
Message-ID: <OF06D06ECC.2BAC9684-ON65256D41.004FD509@hss.hns.com>
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 10/06/2003
 08:02:40 PM
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-2
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h5AEcKB28073
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit






Hi,
you are right.
M2UA will send first TAG than length and so on..........

regds
Satyendra




Pablo Salinas <pablopesb@yahoo.com>@ietf.org on 06/10/2003 07:59:03 PM

Sent by:    sigtran-admin@ietf.org


To:    sigtran@ietf.org
cc:

Subject:    [Sigtran] Network Byte Order



Hi there,
              I have a silly question. The RFC 3331 indicates that M2UA
packets should be sent in Network Byte Order (Big Endian Order). So, this
means that for the common message header

 0                          1
2                             3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|           Tag (0x1)                  |
Length=8                   |
+-+-+-+-+-+-+-+-+-+-+-+-+-! +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                 Interface Identifier
(integer)                                |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

M2UA should send first the Tag from left to rigth, then the length
parameter and finally the Interface Identifier (from left to right), rigth?

Please, can someone help me out?

                               greetings,
                                             Pablo Salinas



Do You Yahoo!?
[IMAGE]Todo lo que quieres saber de Estados Unidos, América Latina y el
resto del Mundo.
Visíta Yahoo! Noticias.



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



From mailnull@www1.ietf.org  Tue Jun 10 11:59:18 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06620
	for <sigtran-archive@odin.ietf.org>; Tue, 10 Jun 2003 11:59:18 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5AFwpV01891
	for sigtran-archive@odin.ietf.org; Tue, 10 Jun 2003 11:58:51 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5AFwZB01840;
	Tue, 10 Jun 2003 11:58:35 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5AFsUB01524
	for <sigtran@optimus.ietf.org>; Tue, 10 Jun 2003 11:54:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06477
	for <sigtran@ietf.org>; Tue, 10 Jun 2003 11:54:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PlQ9-0007eE-00
	for sigtran@ietf.org; Tue, 10 Jun 2003 11:52:25 -0400
Received: from web12806.mail.yahoo.com ([216.136.174.41])
	by ietf-mx with smtp (Exim 4.12)
	id 19PlQ8-0007eB-00
	for sigtran@ietf.org; Tue, 10 Jun 2003 11:52:24 -0400
Message-ID: <20030610155426.14619.qmail@web12806.mail.yahoo.com>
Received: from [208.255.120.2] by web12806.mail.yahoo.com via HTTP; Tue, 10 Jun 2003 08:54:26 PDT
Date: Tue, 10 Jun 2003 08:54:26 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
To: sigtran@ietf.org
In-Reply-To: <20030606171842.A6559@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Tolga,
> 
> Tolga Asveren wrote:                                
>                                 (Fri, 06 Jun 2003
> 15:32:03)
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > Tolga,
> > > 
> > > Tolga Asveren wrote:                            
>    
> > >                                 (Fri, 06 Jun
> 2003
> > > 15:10:26)
> > > > Umesh,
> > > > 
> > > > 1)Then think just the opposite, ASPs use SG
> wide
> > > > number and SG uses counter per SGP. This time
> ASP
> > > > sends DATA and SGPs will drop it.
> > > 
> > > Why?  Where does it way that the SGP must drop a
> > > message
> > > received from the ASPs?  Why are you dropping
> it?
> > [TOLGA]"1.4.2.5 Message Distribution at ASP" and
> > "4.3.4.3 ASP Active Procedures" are written
> > unfortunately just by thinking n=1 case(so they
> speak
> > of ASP being ACTIVE instead of AS). After looking
> now,
> > I think some rewording at those places is also
> > necessary. To me, it is clear that if SGP sees AS
> as
> > INACTIVE that it should drop incoming DATA from
> this
> > AS. 
> 
> These sections do not say that an SGP should drop a
> message from an ACTIVE ASP.
[TOLGA]Yes. But as indicated in the original message,
IMO, messages from INACTIVE AS (rather than INACTIVE
ASP) should be dropped.
> 
> Why do you drop it?
> 
> --brian
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Tue Jun 10 15:29:42 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14584
	for <sigtran-archive@odin.ietf.org>; Tue, 10 Jun 2003 15:29:42 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5AJTDx19324
	for sigtran-archive@odin.ietf.org; Tue, 10 Jun 2003 15:29:13 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5AJSqB19281;
	Tue, 10 Jun 2003 15:28:54 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5AJP9B19048
	for <sigtran@optimus.ietf.org>; Tue, 10 Jun 2003 15:25:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14422
	for <sigtran@ietf.org>; Tue, 10 Jun 2003 15:25:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Poi1-0001Uh-00
	for sigtran@ietf.org; Tue, 10 Jun 2003 15:23:05 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[7S4qqyhPuF+vVCAJEM9/3uh0TlbPx3Yy])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Poi0-0001Ue-00
	for sigtran@ietf.org; Tue, 10 Jun 2003 15:23:04 -0400
Received: from ns.pigworks.openss7.net (IDENT:VEx6davMagT4TdMmPvl8KLopa1knGw2g@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5AJP1F02142;
	Tue, 10 Jun 2003 13:25:01 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5AJP0610419;
	Tue, 10 Jun 2003 13:25:00 -0600
Date: Tue, 10 Jun 2003 13:25:00 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
Message-ID: <20030610132500.A10230@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030606171842.A6559@openss7.org> <20030610155426.14619.qmail@web12806.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030610155426.14619.qmail@web12806.mail.yahoo.com>; from tolga_asveren@yahoo.com on Tue, Jun 10, 2003 at 08:54:26AM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

Tolga Asveren wrote:                                                                 (Tue, 10 Jun 2003 08:54:26)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                                
> >                                 (Fri, 06 Jun 2003
> > 15:32:03)
> > > Brian,
> > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > wrote:
> > > > Tolga,
> > > > 
> > > > Tolga Asveren wrote:                            
> >    
> > > >                                 (Fri, 06 Jun
> > 2003
> > > > 15:10:26)
> > > > > Umesh,
> > > > > 
> > > > > 1)Then think just the opposite, ASPs use SG
> > wide
> > > > > number and SG uses counter per SGP. This time
> > ASP
> > > > > sends DATA and SGPs will drop it.
> > > > 
> > > > Why?  Where does it way that the SGP must drop a
> > > > message
> > > > received from the ASPs?  Why are you dropping
> > it?
> > > [TOLGA]"1.4.2.5 Message Distribution at ASP" and
> > > "4.3.4.3 ASP Active Procedures" are written
> > > unfortunately just by thinking n=1 case(so they
> > speak
> > > of ASP being ACTIVE instead of AS). After looking
> > now,
> > > I think some rewording at those places is also
> > > necessary. To me, it is clear that if SGP sees AS
> > as
> > > INACTIVE that it should drop incoming DATA from
> > this
> > > AS. 
> > 
> > These sections do not say that an SGP should drop a
> > message from an ACTIVE ASP.
> [TOLGA]Yes. But as indicated in the original message,
> IMO, messages from INACTIVE AS (rather than INACTIVE
> ASP) should be dropped.

Why?

--brian

> > 
> > Why do you drop it?
> > 
> > --brian
> > 
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
> http://calendar.yahoo.com
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Tue Jun 10 15:46:46 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15180
	for <sigtran-archive@odin.ietf.org>; Tue, 10 Jun 2003 15:46:46 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5AJkIq21131
	for sigtran-archive@odin.ietf.org; Tue, 10 Jun 2003 15:46:18 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5AJjxB21119;
	Tue, 10 Jun 2003 15:45:59 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5AJi0B21034
	for <sigtran@optimus.ietf.org>; Tue, 10 Jun 2003 15:44:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15160
	for <sigtran@ietf.org>; Tue, 10 Jun 2003 15:43:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Pp0F-0001eR-00
	for sigtran@ietf.org; Tue, 10 Jun 2003 15:41:55 -0400
Received: from web12805.mail.yahoo.com ([216.136.174.40])
	by ietf-mx with smtp (Exim 4.12)
	id 19Pp0E-0001eO-00
	for sigtran@ietf.org; Tue, 10 Jun 2003 15:41:54 -0400
Message-ID: <20030610194356.57791.qmail@web12805.mail.yahoo.com>
Received: from [208.255.120.2] by web12805.mail.yahoo.com via HTTP; Tue, 10 Jun 2003 12:43:56 PDT
Date: Tue, 10 Jun 2003 12:43:56 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA : Multiple SGPs in SG
To: sigtran@ietf.org
In-Reply-To: <20030610132500.A10230@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,

[..snip..]
> > > These sections do not say that an SGP should
> drop a
> > > message from an ACTIVE ASP.
> > [TOLGA]Yes. But as indicated in the original
> message,
> > IMO, messages from INACTIVE AS (rather than
> INACTIVE
> > ASP) should be dropped.
> 
> Why?
[TOLGA]Because IMO, the intention in those passages
should be not to route to/from INACTIVE AS, simply
just because it is INACTIVE.
From IG 3.15.2:
"AS-INACTIVE: The Application Server is available but
no application traffic is active. This implies that
there are at least n ASPs in either ASP-INACTIVE or
ASP-ACTIVE but the total number of ASPs in ASP-ACTIVE
state has not reach n.  The recovery timer T(r) is not

running or has expired.

AS-ACTIVE: The Application Server is available and
application traffic is active.  This state implies
that at least n ASPs are in the ASP-ACTIVE state." 

(The same explanation that during AS-ACTIVE
application traffic is active, whereas for AS-INACTIVE
not active is also present in RFC (but there number of
ASPs is mentioned just for n=1 case)

So, I would think, also based on the above statements,
when AS is INACTIVE, there shouldn't be application
traffic flow.
> 
> --brian
> 
> > > 
> > > Why do you drop it?
> > > 
> > > --brian
> > > 
> > > -- 
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Wed Jun 11 12:32:39 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16355
	for <sigtran-archive@odin.ietf.org>; Wed, 11 Jun 2003 12:32:39 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5BGWCF14062
	for sigtran-archive@odin.ietf.org; Wed, 11 Jun 2003 12:32:12 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5BGTHm13793;
	Wed, 11 Jun 2003 12:29:19 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5B8AwB17457
	for <sigtran@optimus.ietf.org>; Wed, 11 Jun 2003 04:10:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29098
	for <sigtran@ietf.org>; Wed, 11 Jun 2003 04:10:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Q0f5-0005od-00
	for sigtran@ietf.org; Wed, 11 Jun 2003 04:08:51 -0400
Received: from email10.etsi.org ([212.234.161.112] helo=email10.etsihq.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Q0ez-0005oI-00
	for sigtran@ietf.org; Wed, 11 Jun 2003 04:08:45 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_001_01C32FF0.E5BEB845"
Subject: RE: [Sigtran] pre-information on SIGTRAN interoperability event (bake-off) organised by ETSI 1-5 September 2003, Sophia antipolis
Date: Wed, 11 Jun 2003 10:10:18 +0200
Message-ID: <4091553999CBE4409CC2B562152B5A3301EBC8F5@email10.etsihq.org>
X-MS-Has-Attach: yes
Thread-Topic: [Sigtran] pre-information on SIGTRAN interoperability event (bake-off) organised by ETSI 1-5 September 2003, Sophia antipolis
Thread-Index: AcMvTBHe+0/jSP2USI+zHGkhFnBEnwAnnNMwAAGSWAA=
From: =?iso-8859-1?Q?S=E9bastien_Flaux?= <Sebastien.Flaux@etsi.org>
To: <sigtran@ietf.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C32FF0.E5BEB845
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear all,

I remind you that SIGTAN organised by ETSI will take place at ETSI on =
1-5 September.

I attached you a list of hotel near ETSI at negotiated prices. You will =
find on this document other practical information.

Please note that in one week, our website dedicated to SIGTRAN event =
will be open. You will find all information concerning the event.

I will inform you as it is ready.

Kind Regards,

Sebastien Flaux




-----Original Message-----
From: Wodarz Juergen [mailto:juergen.wodarz@siemens.com]
Sent: 10 June 2003 14:30
To: S=E9bastien Flaux
Subject: AW: [Sigtran] pre-information on SIGTRAN interoperability event
(bake-off) organised by ETSI 1-5 September 2003, Sophia antipolis


Hi S=E9bastien,

could you please send to sigtran a list of hotels
near ETSI which you usualy propose to book.

Kind regards

	Juergen

-----Urspr=FCngliche Nachricht-----
Von: S=E9bastien Flaux [mailto:Sebastien.Flaux@etsi.org]
Gesendet: Freitag, 6. Juni 2003 15:44
An: sigtran@ietf.org
Cc: Philippe Cousin
Betreff: [Sigtran] pre-information on SIGTRAN interoperability event
(bake-off) organised by ETSI 1-5 September 2003, Sophia antipolis


On behalf of Philippe COUSIN :

Dear all,

I herewith confirmed that ETSI will organised a SIGTRAN bake-off on 1-5 =
September at Sophia Antipolis.
The technical programme will focus on M3UA, SUA, IUA, M2PA and M2UA.

We welcome you to attend it and please book already your agenda and your =
flight ticket to Nice.

We are working on the technical side as well as on the online =
registration which will be hopefully open end of next week.
I will inform you as soon as registration ready.

Look forward meeting you on September

kind regards
Philippe

Philippe COUSIN
Interoperability Service Manager
Tel: + 33 (0)4 92 94 4306
Fax: +33 (0)4 92 38 5248
http://www.etsi.org/plugtests/

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

------_=_NextPart_001_01C32FF0.E5BEB845
Content-Type: application/x-zip-compressed;
	name="Travel Info.zip"
Content-Description: Travel Info.zip
Content-Disposition: attachment;
	filename="Travel Info.zip"
Content-Transfer-Encoding: base64

UEsDBBQAAAAIAE5+pS6Ei1N76kgDAAymBwAPAAAAVHJhdmVsIEluZm8ucGRmlFl5OJXp+9c6Ys6U
aGPiJDXK4Lz7+xokZMsypCjEiWPPESdFWVPSZJoWikpRSCWFkBRtKqWSpVBNVKSU0mRJy+85Tdfv
+n7P3XX9rp9/jvM59/M89/q57+d9Z/1ubqGL6eG8WR1PbjfwFDABx/IFfPGKQJ6hIZ+nbxsQIhKG
BUSJfPgY+urAxzCBAP1jxXfj0wxOo+80RvI9pKJ8SoDhtPTXBXwOYxkW/WfPxxn04cwnGQSh34yN
+TxRiI/0AP7/929tmMiX91VDAsP5PMG3P4zmf/3kh/AU/kVoipPFMJYgBQCjcBJgDMbJYDhOCiiI
0bL74TiFQTmKgXI0DuVoFsoxBJRjOCjHklCOE0A5jgJyhAADcgTyIMAwHMphDJRDqyHGQjkYD4Rx
UI6koBwF40FQMB4EDeNB0DAeBAPjQTAwHgQL40GwMB4EB+NBCmA8UFpBOQzGg8RgPEgcxoPEYTxI
AsaDJGA8SBLGgyRhPEgKxgOVApSjYTxIBsaDZGA8SBbGg2RhPEgOxoPkYDwoAYwHhcF4oPKFcjiM
B0UIGIhBP1MszkKMwmQxGmfAfjQB9aNpwGs4Q7KELMairAQYSeIAoykgx+EYkONI6AOO4qAcrDdk
BSMrhzCQV4hyWFneJRDVy55LYBiUwwgaYiwNzsUFwPeofKF+LAf141iQGyTqd7L9g5RKAowGZ5AC
lpPVhZQ2U4AR35GDtUVKG5cshguAX0hEsrI5REqTF2AMqBkS9QpgB4HjYC1BcrL5TKIQAV8RsEeR
3+E/kiQYYAdJMcAOkiWBDygB4BcSmQv0oyCvkRQL8hlRHQl0oRHbAYwEtYUoEeqC3AJ0YXAc2MFA
LpZSJzhXOmfJYixGgP3QPAT2QykO18KeR3IIBhgOc5cjaZAbHM2APOBg7qJZEuhHCQjgZzQJfAdj
KNk8RXSPAzkM8iSFkfBcDM6EFMYBn6JWQcjaRn1ndqRw2C8pnGWBzojYgBxBghqkCJqU9TNFQL6i
EOnI5hqFChPojBIa2EaygEsoCoN+QbUF1qK0Ar6nGNC30AQH+iWFaku2ZihUW3AtDbidolloGwN7
D8UQgHMolEJgP4ZhwLkMB2Yp1PYBD1FoRAdxY2lQHxTLghmO4jACrOUIGHOOFoB4cCyYE2nUf2X9
QqNuCzEK+I8WsKBmaETZQA4jQJ3TGE3I6kejSxjQD/UtWXtpdImQzSF0iwI8TuOsAOyHhgtZX9EE
AeJLExTo3TTBgtygSQHIA1SBONAFpSmwl2QF4AxEdkCOQrc1gJFg5qJRQgP9KA7wOC11IMAowNk0
zUJdGAGoVZpBjR9gFNSZYcDMSjMcmA9oVDNAZxbe82gW3tXQ5Ah14eDdlOZQMAGGiAhgsO8jL4N8
ZtD0Lbsfgzq67H6oS4MzEA0BbmcwjJL1C4OR4PkGg66DcC28hzK4AHATI71kA4wCMyGDM6AWGEIA
eBelAZhFGdSmZePBoPkPnCsdvmUxUvAdDNYWmk5BDTJoIALxQAMHsANRO7CXIjEQX9R84Fo4YzL0
d/xC46BWGZoEszxDM1A/Bj7TYhgcA2uRs6AcDeqXYVhw/2AQrYH9WEIA5SiYayycrxiWAzyORlEw
2zIcnDcQQ2DAfxwLnnkgjJX1FWJTcK9Fpglk92PRqALWYgSY11Dlg1pgMQbMIIglgW0sjlFgLU6A
+wKLU99Zy3xHDtYHChGoI5bAoW0EJQA6oxoEvkI1CHyAahDYQeLfwWA+s4j+wBnfeXaDqB3kJEvh
4H7EIldBORrwOEux4BkKi/ogwNAQAuygCTAfoOwD+ceiWgW+ojnAOeg2A/iPRQQIdGFg/0VWwHiw
AtDfWJSAwFcsAWqfZSnAGywLnyOhygI8jjoK6Fuo1cI85UjAzywH7zgom8H9g+U44ANOgIH7Aied
5gHGgFrlpJIQAzwu+Pr24r8xDPnvP9ZKwoQBwaIwnqEhT39RQJSIj1qxgKdvHeIr5mMCaSXxnfg8
fSexWCL9zn37/nuYKOLr6w5a+gLE2tzNkGQ5X4LzwVH5+XBCESok6cPvFQTnzXArRELW+P+W8OAZ
G/PCJcIwydeXIALerFkLHCy+vkLhfTv7f9/ZOEeGivj6ZkKJMFjsJ1VI6CcKl2pIfdPQTiQR+qCf
pRjxDXMIFYXM95YEiEP4bv++5JHi+hYBkq8vd6R72Il90L6Lw0X24hDRf73JwUjBf7w10l/Ex1A3
5aSrgyWiMPQZLJSIzEXeXzewFYX4SfyRMwX/eky6T7gkTCRcyVOwSu7Z1e1yV1H1aqyeViihdErl
lUJ29v3sEfnlinOzi47mdBfYhlnfUNEpmD0wpsy88rXiFoXDuaK9TXZ1tRUZRfvTToWccEkPbAzM
vRlyjwi/dbNKoN853Ml1DVdGpfX+ICc3QY7/SU5ejj93hNnjKvzBmxg5yYjQ1S7NXguLUl9v6tqY
8Clv/Oc185/FvDr9JrJjpeGR5f2tWfomKgE6q/eV9J2rWLfh54jliY9LrlSYpW+dYfqHfm3HbDn/
2/5nAnT94uV231QIP7EimeF3SMJIc58MT6q0b9XNSdc614udz1RNHaz6nNcY8rPHpVzuQ1u8/N25
Gkvlv2iN8nvVtGzO43qN8UorLXIzJqQN/ap9efqwnP/k5dPk8657vzpD7S67aNn/Jc64fMPeB4tT
H45SW9bfqBzvWPGmvPcHl6Nrbo3/XMEznsLRu+IGVnYXXouJPDj4Bqt8/26GsmGflXVU7gZe8OXD
E5WMfF06TnqFFRo0debVOT068VPn/sBZL7zelniVaTwL8dua65hv5Wfy1H56uL7a1hdOzyN6r5Vm
edWr+SspHu1NXmwkXnKheM9fqR7TN18IvHIzpnXiGr+zg/b7lbpdQ03Oev8gOlx6t3l6z+k/725s
qk6yM9ynOKGhc7BIpWLArMvuRuGLNnxHd5+n+3tTsu2tR97z435asRcThprGqhsFjTwQ67j8qrBm
22+lHb911gT5RXfQsdtf12msE9ZY26v2vpzZuSZ/e63Z1RqHR4eskkMXHttkOpRp4hnIZKe6XEry
29OgcIbdXq7j6ZiUHf8ueEF4x8gxe3sc9jPKi3bceHos01lePmXade2Cawc/xItXnnYeZ+NaYH60
UaXBd3VJ3IwPT9/694TvvPVgKE/H0+i3KV8e7SuOulUtqp/uVvxhZpfQYuh6wMDfw/MoYaZnXM7U
wbhkvnOVtd67WjQeqiTMvu9LZLWe2Fg93NkyD/9lIM79yY+rHQPOtm4swicfeO62PcnfUn5uC7vm
6LlTZi6LPcTaX1qNW9a7OzTt6jf+vP7yrJCwMoPs5EPXsxcek9+/eXf2hBRtFZdJWvmmpUkq58Kf
a/lnzG1P3potPntql2fgVqcdU+8ir3ssnp4UazDV6WXCJOPjVMVFkUmF0Uozoe7IBfb8xtCkxHsN
tZnJtZcDXu2aKn40uN/EqtNg7pRr1MEbnuU1Fnr0C6u1otOBLkZJGzeN98h/ptf7her8xHRNi9Yw
OnnIM6N10+1dQefCoiUhOXMsV7XKGfX2v0lRjUydPu/1w9NrGq4VG4h81l+3Ic7PfDvHKUlVI3iu
5mCKPfNX+M4yE/Vyr5VdN7ft2j+19+ypMu+enKGmrco5DWX7Pj464W06cSFP923MH70xlzfvZEp9
Xga1yYtTxs1J8+vtS3nZ1pobeMRZa/RYlcgnrd5apqVxyhPkTN26M3Vc+PkjItp0C0xtbGpdeJWW
4/5eoLJXURCflXfZUXHSqLp9JY3v/mwYmTXhZLBvKXcm3FrjYe8S13jznbGxY4qPfLR8tKCl5mF5
+6TI2SsDr6QIZicGem58jqWlFk101+w54xfVeEf9pwLMtWb1X5sMt68iNXMfVob7ab+a+Fu7Xp26
iu6JBJfEPp2ROe77zPeH0tdC9jXOUc9nMs5MGHQ9f9ZszdHMQ5xSSYlSULvtobtd2kZeMTM1xUHc
patTHbbOKV3ySXdL+wOTBxHrkt/4vp/h7+s1cvPxl6E/Ga+/prx17B2D2s+L/ply28pVvy7C1lI1
2v9mTsMrcWexw+20vKrwba8+BV+IXPfooH/TzCVFDxKnGdp5DtXplj7zfvKpXrLpiV225+6jeqmR
tvOObSu/8+XHyMu6EcH56gcO5JuEfexI4BWyVy/m1q0ucrg7KrP8efrN5lgrW9Xdyx+6nXyy+lNP
+pMLfW2ZXqenbTLV3T6+/MMUvXTvxPr1ZqppmvlU6ce1R8o1VyQVPlVufuG930Sp7rD1pVXN8qd+
v9CfO9Z/qZdxp+JjMjZwOzZ2w9Lb6bb1A+4+8zMsj4dNy6hb7rzo1eSRbBA+8k1ugsTR1HlEcECK
rR1+sqRPxydm6JcF4td7tcfuZrhg1cnh92/3Kxe66Tb6mnVFv3o3sdVUs/bioH5MUVVnuPWR50+1
Gse2mw5cSwzaMcHf4KF9XVr+C73iIbPhnGaVVf4lewrG5V3frGRn4z/Xo+KpP9F3ZumpWkX32rAi
x4ImHevrak/DXj+1a16icHdDh477StO0l7uOKd2M0yrSGv+RGDntVs+Y7QUacro98dqTXxAGfpxy
Gi8i6eeItW33I4xeBdRr5cdVNF7rtns4cd78qKcfswL63y+1GHQbb9Tkoth380zfshS10tDIs323
usc18NK0xCd9esqNX06sz52/sTJWG2PP7R086Xvxn1Hdz+9LFGd4ahcS2Vpp6X+yw6PEqmzCriJe
lN7xL02/UjNWuf9zbNHVrnu+qZVPlC+ZVzlyP5uxy2cfmDG0octuWXjLgrB9KfrvTyQ/c3c9JUxY
V+29Rm1VbMoEPcVDk4ZalyonTmkJ1f9SL/ZfdeKgqbB74fTpn/784J95ydVs8PIJkzsWQZxgcLZ+
8nl6SxmlXNPcN9ZtQ/3Mw1Xuznu2W/7xo5uSetezZZ6GTy5maWaaxfgXjPujV110oGZMYkuZa0m3
fHJUkNvil++jP66xbTGcfzSq5UL8kjHXW418alrtfo5Ztrkno27W4iDxVL04kV+l55apg+m6Ojy1
0OxfLYRalQOLbXaoC2f0Rdi9ePtOWW+bVcaRtnsOqfl5lfvsz21zWm73snvRzhDzW8xkT+PTz96e
LFaWRG3ZF5297lnmO/px2Zz1C2onD/xS9nFlpyp75Zc1ShrceN/qorRzF6oNKu7G1lkNV2tsj8+5
bnTwlFtbaOFPo8N2fvYpsW/bYTKBjbMMCTzkm1dWKmqZrB2YNScjZy8VWTJcov54ROaeLX6BW+49
XbqF5uItbey6bRU0NX/XDHR95GWjmbjMJvOx7g4X3XMt0cX6/cTHzC/zMwJF/n+79u+sXDjC7Lzg
bWlxjF6JObFsxpV3h+XGGiqZJx7eYVR6/5GJifz9J2PsjqWPLzyrqpCdygTkhLb7/5GRG/Dgr8wb
KW2K6qv/ujxv3vNJDxTWEMcPR+SG3jjSrH1ndHtl14YLYdFJgpRPDgFnDlhG22TX+y+Y1Jd3NXrt
Hv+UC74W2f94D6lqOs2MtzoWeWVKftYd1SZnnZ32Wdve/r3B4xTH2x/1sCIwz7TxWLFuUMjJGwdn
z3eqWm+j97zg8VC7yQorx0slHrvt05bHqex/6JUQPL09fruSTrpXi33V7ssTx3V4qQ4Jo1ud+U5H
9yrU5J+PvzLwi6VZ7kGPdJ3PNT1n64eNTz/WMFCb79YbJtpx497oNvn6Fcsk7z+IxO91R3YGRb19
E6EW+EFtRtCsUQ+Km/FFOmq9yodVPNOFAfeOu7y9nM/Eepx9eiVNLbnGiWpI0+v4gvW+dJ6slnPH
1sAAC7TdkhxVV5a618FwRPOVyQ+7zp+PWFW726Y8nO9XXdPqFbhrQLNUvc37EjtHve6o3a8jS0yn
tR+Yq4PveLDOIt2gVjH15rrkH/pP4+9KyXE37Genz/vJonS26UcjZTl8xDrbIgvV3UpjNuT7XItS
zDw3fTReRxVyA/ZXn1nxn9uoXzEvPNQ4Lk4yxicuqWr1i30u43rm9SvOcky9Nb7rosKtTRNEFFlg
2dte3WB155Sk6OrcNrcwTfnR1/PWNtsP26hfbfaMvv3Plp0fRnjObjwQcvjJ/fXliZO8I46nZlHz
1BPPtf7oGHNx2LVj2vnqSOvwE88uxN8S3v90O2PiKsNzbvcOsZfMdWIKf/ecN3eHWfbS9nLN6Lxq
eUmPzibrmVXuCVtJu5luOtvGX0iwNdM8puFmnxQmWVid9eJS1dLg/2HuLeCq6pb/YVJCEGkQJFQE
Jc+hGwREUURCULoR6e4UQRBEFOkQpaRLke7ulu7ubnjPPir46Ln/C9ff9b2fI8LaZ++1Z2bNmvmu
WbNnKy5cx59GxjYTo8M1Mg+cjkRHbngAesL25X1hNJM0XAkXu4NAdtl1Ga5P486H+XdVP2s/Zls0
2E8o3PPMDllbUo16+skcTbIrIivLKFs8T0Fbht3Pts3gWcyK+sUoFtccYgot0POV5U+SGN3K2oFr
xnWHe71Z6q2aZwutGvgdKXO25nZiog86JCP5cc6FjXc3TnliumxqzFzT78WWeGaijLGpFdjwvL/9
zTz1sjY8KYl7d5JgSdlXEX3feeKqa4NegwuqVr3EzPG8GlTBnutmH+7bt7+/FRZQfdG+jQ5rTzF4
em20WnvxdteVpPkQvLsxD9uDPuliGewiPnumWW2feM6uQ+VS3ef7fEudu/nacC1Xu0it/OnhyERu
sZHfv7GZddYb67KgYVHQgy6WITJMW9E9Zpys1IiJbVzylFhnh71XpdmkSwxpaMiY/O/suht3NvYv
xHEo1vstaRWhitFNKzEH819ZmX5bEXLxjpY3zbSHH8IMReMn+60Ll1zNQ4Vnk4ivb25zemtsjdyY
XCSvzewzNJsjSUrWFqVlAknGltHp7cw8RF5lCFkNejJeTyAz9aH54QWfCO619DBdEnT1Ybrtwn2t
+hc0r9K8Z0gHaGW4sOdCZDVLsmcJuMIxTZLtNaene1KtkC6ckbexLbnuJECT43/vTD1oPJPbDYFN
e3pSC0VvBOzKFYbNW5Td34IgMCVNd7vRcjZ4nOpw8uLHiqbYucP7X3K8r2I9vJttu270cve5VMBc
TOBNedmXOpixmGlXH21d4hwJuJJMRPtZDhQJXqu5bcy+t4SuBdYgUglOm1qeGGFd7K597sUtsiGU
mluvLTqavrwgN8A2eXFvJfrdVbYZukVWZRtBlbu3hBdfCr5RJ9ifacXhDF2M6rHT2c94O/IFjtJf
bbN/uRn5QUNqVSZfHKl5+2BNe584vJ29IfH2lxkszZjXZgSPrCOevNvp4BGJtPAPeIzysWxBOqwp
HfmJnd+TDIwld9PQl3USt6aj7DApzRN0FPnrK/BEXPe63fLYURERXllk4IEXjAnvirM7Wz9YDqfX
sZ9NM9HmRIgltG9sGne88jHXxV1Pee1BnadsMVhMRBn7gocj0kpRCKP7UHaKh595JHtLpKOzhqLR
G/0DCfGZj/crdLMxfMYCLqajvSRNjJYvsVMTnLxxSSVQSrxv1+3eBM16/6UXmHkuplRVadW9z8Tl
P/czLatIrmcks7lfCg16GT0Ctx1l36F0OeaT+Wb/RY9ouztIA9pcD2ky37DXJWaU12iuve/HMHHI
NwTHcOgEUBmpUBMxqhZ3jBDIHGyYRFrVhGhJ0ysVJD5gyAwKfftau334ttDUUyQGzerOO3oDxUFB
91NBfd787x739HBLMi3o5fR7C6ro9l0K0Ug0XXkhaG8SZnfPaJX4zbWn7yofMwg0G16kuojbgod7
3ZXLSWGt7lJVUIOPMs/qOsXQLFUH7oXB3geWjsUJPMz84u7e2da8PTfgqpiGwroJ5nuM4FtpbSbM
w88tIiQLfKxyOJtYlH7nLRxqjRhX8EEgO0LcfrWjj90E2b64PFaPmsMG6mvRhPe6NmlcZeRueGGj
JA9LDlTVWV+6++6qhJStvj98vGLormeMZ7a7yxS2k2qcHREoHr791HjfjYm9f+asuYiDUKposNSF
5CQ8w2LjrGnmBPxw2uYmr5fGq5dvGJtj23NfRwgV+Gx5bq6zgYsYY+ZanL7b+gvhoaFSHSqfiJSC
NNTMVzfmNO7s2MYZN5A9C1dlu3aHu4Cb1BX9DW3T5E1TNwf3lnfP0FDe9s1f/0Sl0TC8zFa5sxD3
smHNpUSC/vob7rcjn+rfN+h2fsoGu11gtJmuDSuw3L2JL+0M/yFwblw4x0/Y3urdzgulVg+DD06Z
KlcH7jPaE5FnEldqkmvUcJVzB2BftnOnE6Fa+MTIHPCqAGzqE5Ku84LAh4BSzvAzJUsQ0R0pmjuf
g+bqQmMksRN69zs4w80O3Tfzncomd/d5mj6ssFBmWNf0bTQSqvSZhr2sVNd7VRYW2PF0Cle8v+Fz
1cQX2RoQJ+Z8g2+4dtyas2/DAusFZpVCZhVjw0grpzbEF8ip0WFTPh8QxVNECWIXdCRfLpredU5D
Ohck9anjCQ4eT8PF2Cp9upckZM+5UoqZRyORr33GvC+Co1WkPOLS/g5zUd5IuX+tZs432XM4PUZZ
f3cjOGY0sDk86L5kEd+itzzrpzginfNom/PvG6vZPNRcKfTE2oLZXMWLhXIpfVyvfybrHAvEsHHD
cQ5BchsvIWMPY3i0Wrme25Lro5JzzUIbv7rhcTLJus/UBHVE1Fp8An2nRqAvmHK2PHanhTuV97pi
oya5wSUipjNaxrLYDxA21+tWPHhefaaMj/M5w9Y/GjHiMlx1mMTOwcsFQvNEV8H6+PhWMkk4xjrm
om+K4UP5aTOPIURSKfQ1xfrdGKMqlJRxJZTSFRuXAllVFQNlpeA6hcpom/vjV3fPP6vUWlN37Xyf
OvVWZJ0wi2hbjn5AizxoWDxST+IhxeInb4NDh1StydeN5RE1Oj1yg3pzLyTft8VqjHM/w890Eg6B
Xy/QFHW0plPmMN6vMZ2VHeYJvHBt3zM8INOqqWj2hngHdZsOL/niMwapwUSGEL6F0Dw9KbJkJSZN
a1TmqoqYqrHnL4l90RpN58krhW8dVjeMfxQ9bGxYxdZu8lGkl1voKyRT6h/Udj04F+LaLjKxV99g
sVhTWT1TAgrA03UvvCF8/hkeJTNh0a7hzNlXFoxTY6N5StQthRuZy1wJi18NGyLh0wiX8bYtb+J4
00WH1ur7zxqbue88W1BOspA0Imlyg3s2BVY2fT6NMBbLC4q+nhbiyUBsovJgPfFuTcJFixnzRSok
WXnmJ5WOwRvideJFmwMbD1rkMWXeIYtbax+8697bqkyYC7YwRSt5Z1/+oYvanDfWq7na1uHs4wqa
mt0df/t3+JEYNVd5mJwZTbRSRW6+c3Zi6HWc3aZhw+mQ6bLORVGdI/+s3Pv1K8dSZVs31TvTEdmL
FVFO6g+pbjEvLlwmSSVEjvpSnESNbHvGkbHvTbtT0Odz9xw2JuJ0zdZaYlOj/bThqak3eraybabD
R9EY2fnN9KUHB/dXhl2N+VV7cozQy/LSWZmKs/qddXNMWG34xbnp+Vbqsp69wUVjPQQnEzTrEucZ
zQ9eQdXbG8w61IgVOQzUe2tyECPJPtudzml06B8f5n6vjCXOyoq3TV25Mh+MDj4UXO3zXBrQdhx/
+3GrL5OaATH2gUKf77P799YkPvvPJ9s0Isb2G2gseyTXUboIeiE8jsCnXKHDtr+BfhsRIz2dfdCe
ObJyujyJ14Qe/vGG9PJj/S7rCT5nbXfDQkf2WIR3t+HC0A1IUA7FE9rhPkc85FaVN9od1cmSaQv+
gFXFa8KUIatqUfDCJDWv4InzRFup7Vq3Y7by7deW9QJt4uMiRorS+uvVd1eDBvNnn9x164z08TXy
4l0updp6UuaDwssFX3Cg3J3WzjUBmiMOcdhDKS1RuGpJ2d3phD2U7W5U8eZSKUooxmcXA/llUc0t
9TpKdKMVtgXzh5ZiyS7wTLI3hFwEewTehS2a+XZhJOlfb/4gXGDuFG3FpTd282JfhseySCM/HUMq
Q8e0iAsa27sM56hscRuqgifYYT7XE+Q+GIoPTpYbzq30KNZZjlFzM0TMqbC+ld+1u5BNWIVXAzab
360Md7popWXSpum92dEVTEJ9tw/h+myV3XVGHDchvnT+TL4tawbq/OwBEHdzrV1ixplbVg32wQXT
JPbnb7ThwTUgfaDDWH9HeiHEqFjKWULpzDlTYWe6MUoKUSIVbJIQDgrXaDVzwbDL8cIT2EEiTU6q
Xsqm9iys8OekL4q9RxfSlhKZovXAFrMfxMJCfvG0X7mG2gZZe5yK3A1r6VUmi8MXEQ8XLYnI85z9
jAq6nqq4rNfaPNHwWulbFyeMYxZfbOlkU+MM5QteIbLl8Dkn5YpRjmaFij2c77N/W2RyA1uF3JW5
ajzJdRS510naw9P/jhXXDio+M0vrRY8xClqZK8v5Z7wf0Vc4RSn2JVRzCnWh6Fx8cP3cwnvNmZuP
Y5Py36woLIm8Zn2QVDdL5V+W1LbqnS6K8eix8fQicYVhQieiwYhZV7jfPKlQaLgIJ23ldl0Lo0+e
LcHYg86RZ28HguPU2PBkYuN3e6j8o7xvoDFVyt6/rYwslnc9AonrqpRrtsgelXjVEyGRMDwK1Jj9
JWTh2IpHiKHvpe294PnSEgPObYjGsKbFjHet8HH0XMTvkH3aaqiMa5YpjFf2FjHtY44OfvJ5G44Y
hmYqSVBbWRgx2mNJhqCUeIzJJFSh2yxIQVcQ45iXmF6iIrltOjfPnXPV/pp25Sw2pXrOVTdpz7EP
nKXPLVuHgrkRWO7huU7Fw326Lyd24RYB/OVzq9l6CZ69Cw4SfTYvR+5Unr22oRrR0jc+HZO7pB5g
eD32jmyFvz9raKqOxldq5kXjq6HV7dk147Xyt5E+VPuYvrp44Yll5SWDiTfqGeo4Xjxa9b4qXyOF
vQTwi9ju1tH7wU1ynSVgNh96+fb10FsKtZ0Qm9zLZ/tLTIXkr+VqCc/qKfgyX8F5tOFqTqJBlHiu
X836ySDFA5TPplpF40ZkCE8luZRGMd/XhshOP63tuRaNfvvO57rxBo0L11Bjo03JRR6a924Fq7l8
tdc1P5dTF6ZiIunIxyn75UvHq8jg6+iWaTezNLBiuCa8qNM/yvm3L+9539jGkb+5IGiTaA6fpp6B
Uj/iymHtThfjivmmweKSM3Ym0VupPD25/VsbohJq6TExNnK49PMMorSqUfo3DT250j3oDrBitA7b
Kh2qlvNWt7f3nmNWEnH0CmBQGjvfvjvyehXxZVQ8M3FUtFaweNhzzWkEyQBBss7V7WkKAf2eaHOf
66HvzunqI1delxL5aEBKoZdFzKYVXce2+g5dJHhMWKH8SsB88wbW3OYio0oB/2LXbDIZ4+YzSpM2
nIfKX3TXvTp99CmkMKLADG6LOqMF8kTFmc7+ZJ64+HBRcDX+6OBnX+vNpdDOdyO8yYTzmj7/nGZ0
+I4d5aQBwVMmZo1eLabCApIXNCXWDdfkHedf9JfmT90WdvjEDBc9oIqLhd1mvd1sCpepViRt/SDu
DG+23kMlCX+rxwO3rq4ltZOvEs0vYlbYPLs9lP/c8Cw3eqJaBZab3sdcih0eXzLr0setU1beNTjC
JPyOee6ehzcnqBoXKkeoC6tBcYPDBmufN+0YZHiY+vz9nprT7Tgc5IBq9spNDuSNYj5Z3Ym41Zau
mGTPhE2QGtgbv3QALlolXFlPrDojH1J3gUO6m/rjahm9xOzXYrOOSs1NY+sSorl90ZTxFny/yXGS
F2twad5cX65+qAx8eZu7hX235L2Q7JyGp6+ZEt3bR/F5lyT8zB6CzZrdQoJ6LmlSsFHi0dHfecEm
KhpDuxFbKWUAmjt7p2t2vq8wQT3xOsVViwkqiYDcarFbuLWxMQmupT4GlM/ZW6wYnnma3bikMQon
jEY0XbuOcJHCGRSEjTgn8myPIwYFsjIhZgajebiiZdXyRLFxGAp8dfZdrMky5SGGSOrdgLdEiPH0
4KF9r8iomN9XR2fndi1sjveaX30n+wXDnqZIJD50TzUjdm+rXrmbTL9mF9PZQvX8wJRfb0bCJnqO
CXkvBm5iT1hzIojz6+jetpJp8oJOTFFN9n2H/PhP7Vh3J6wx42wisO50F5OjEyd2bQ3loDvpyxa+
Cm50ZStib5aWrZXpey2ktLhil9TzTuMqtR+nYMGt+RhyLR8Dh0PbFzfD9clfP268OFox2B3ad5Cj
r59lITBCp4J3+MBCZ8H1vGKygr5KXde5DTQVnsRzLwuva+or51DaPCAvvySVke1CQu31ektUqtrR
0/SBHudr/axbhP6KNG5zJm87HfzKb0c0RNBucsjYDKe/r/R48HDZeqrM78Pnqwxy0mH5F14Xzum/
nznPOrfkEYWTyymQLuHE3K7Lkx/08Uy45RlBc7S7H6i8q/3hEOYU7R+gCpNykglUwuUKn+c6aweP
hPQRvbi74bKQgb7vZcJ7i+gV8FWxLExcNCuxiO+RUHREOamW1gi72UR0IkSciE1i9PKdFd69lDmT
hqR9xyl8dp73Rf7WXfIg69d1abmvlowNVBli3g2zTAXt8NOODCbfolgp8uKZ+ULWJbdD7XhV/Ero
dlugReECidTqjMmT7gIj7Mhq0GLWcmx4DOZXalOfRaKm9gLfj1+ukeftbBT3CDZg98fOjCn6Nq8H
EYjl3rdLxfLks7vMka30+LbyB1tvuyABusE+/VHX55UeEBBysejK3Eca915+WYVh1cc3OwT63+qB
uODE7N3eJAonT96qQU/1s4uNrnbYjV2batFO8Vwo7fPBnhLO3Pe+i6kx0Iz6RCmhJzH9HjZOTeNw
DEbos963wvFnEQ5DkYl6GxAQTbxFNDOm/a+cd3kOr4PyeObZo6kkpHr/MpN8f5fPtSVrCvVfbjSc
uYpNRFGRh++5N7uOImq59vnhDWzxiIsJIfGfjR2F6wrYnJNbx2bwyvt1XpG9Jqj9oHhz8WPJeO+D
pI4qMeMND9eluE9nFQYpruhrP83Xp9lnG1zLYiDqeS83gI/t2Y7SYTzMY+k1mSNXc0n2cU62p+Au
n9OMDTxLS6nZsAOi3gb4y66ZjU6ST3af/A7FWuKcxYzSwUrMinvMLufYltWOQr1dUmL2Cn0mYQ5Z
QayaHUPVXZL+K+1XPqrcqTyTlxO7ayFaPijW1U/oETft9S4VPWvznqc82yyh1Xihxbg7dXoVIfrt
WyKX8VkfBxVjPnvIev6yGreHmYABK1JZ9EH1a/mY27keogmPPntEkJor8l961Kv7eTMQ3/Ce45UW
OCM+lrcfbvexv7dJ9OMqlBi9iSil+2Za7QPGLUYT4nMf4YqnoyxAJN5EU1FvqxDM6ShE8t4rYESd
e4V0ni8qEem5JptnJ7On5EVci9Xq534koW2lj+UXKFHTHyk2mRwULCW+TXFCiX/wTESb6Ml2UoCW
FdoHOVBn+w0y7teCd83GhWbUei6t5iiv8YD320LgxIwY7A/v28dqqy002cSevzes+4mzs0Rhlguv
XHmCGRwokuJ9LahHuKA3zi9+1Jk/XEoeQ8cGzVlZTmXCTqPKekY7PD7hg78nVl0Xda8u0tttTObu
cAmFrZQ6fKz4PJYU+V0V/+kkhchbk9QMmHZpOJH7iaSPZ6ecE19cleOwuzsIxpg5RzfT+cDz5cTw
0qiQfpl2if1K1dMWncqhmZsHexOskhKVqg3etyjrS5Nfz7ssP9dEVHfrrbDmR81gsxBcvlN/cx+3
c6cHpYyWzX4aLbbbH/lmfWXZ/v5r9brGBr/1S2G9cbQb12iWn791Jyqyzu+mvhdEMm8Rc0Hdc1rw
2Xmij1qcos807zbBt6i7t8HZLOEyDQkUP/cTio1GdW4pCELkTQdHfCxw9szL5Onvpzvf5KruH1Q+
IxLdVqr8ocNv5TahrC+tYrtd9Yrsg1db9Ajua/AjheoRuE2rAZEESeLtdN4pNItf+hE8U3u0rZP6
irmRIxgT69M3K4Z4L4vmSw/h7pan1AgJ7im8tZoJo+Cze3UQ13fXIRDls1xGLnkN8aFa0dzTkOom
jkLG7itplIxBbudxvi69r9azlo6XZKcUuG93Bit/ipLwEmJOoOzSmvDLAQM2eNdLhM3BH5jNL7yy
DCJZNw1YnsKzeBrv/Sncel2+J2eaLuhe28d1VwtDsFxsF/mAeNwmSk+6Zi0536GmJThvd5t30CFi
cldzAftSqwHPYKCY7QLcQppOkZwxRyTul0vkFwc872TZdAl9eK2rxDrwNUx2ePuhjzXW0IuApNl2
ieg2I2dKyTxsjavRn+WHUi5kKEUpdzySUDjcu/vIV4tvmqyju4iIbo748NI22S7iUA4L87Bac5pv
JR5NK2cPLo55aTs/kxwbs81Ndb0ZnCpqEu3esY8lPXyx67tv3ZRFWLovvn6xd72tcs07PcqlpOxT
R0dHzyHRaAiI+bzAYybOTmzmSdvROEqNB1uJLNodWfedkZHELLGFmj5Zy9LLiKGoia7hRd6JwG7t
VCfj8X8pT23tL1fiQnfDjcZdNwDvVbCUN/4H1HR22dSHHjij179i2MpcgVezV0fRItgW6t3yUZ0p
1Zdk367TjEv4uNj4qu98emUJmUG2tphJ2ZxcQK8Kd8dEP4a7cGv3VQWVD3fsnuYk8jzOQislj/5S
buRJItRrG8TY3qXtW+lz9605cyS81ThOQ9MrnpWwVoGOci73O0wbspd4NUvWM2PsV58hPZ3U6jPJ
GxUmOV/MyxAa0YPb9jAYBemVa3cBT4td9cFWy+Xd5YpOxQ/T0dZRX9t3WwYwu1wKWJkYRy67J3nV
181kDX/YP0DJTchhHF1Mr3IL6c64XpE/c6HD5kk609tJ4gAivKr+F9OqiDzJDB6WqIt9TWNu/F31
7ZY2N9/Q6jzlUb9rb1os67ZEJWbY3LN4TdiyEm8slt0HE+Ksl+a7GyQsrtmWzJ1RELW/+cYDhz5a
dl3YWjH1NppNEupcjUCBkKole5WAWQ5TaM0zSqa8fpNXFlLeXhqgL+GIIEPi+Y9jTJmPeOJl3bIM
y4hUznmkiQXacSU3r67fz1MdkLZus2MGJX8hXlWUfKf5RmCUr5ye40Py2p6gzecBsskimdaLOwUj
Se8l7w/RDp/rl+SweMS7SvrpTgvlBTSjeV2HeIZsci+9NYMJzvOYF3Rxy1z0U6poWa0VRtbmn/V3
Rtb6FavdJ+xWcgFts+xqr0wxMUl8pktaF7pm8JGTs9nfTsn+tuFZJ8JIrOicSqcrcYEzyyFb7cGt
0svFbRsM8hm09XzT5tX26qqijm+nm2aeFlYtdLASS6qYkRN09tEktyLc6cipm0c1HArKe2OQ+6Qw
8laRrvZIOK5RVWkufaYBWFxau6m4AmxteZma9fE0okZ+67JZ2gZafMm0EnciLnusr08kn0+QeMfr
/CyK9YNp6xgX/lJxAzGrF1i03gW7rWgsI2RBh3HOGeVCdFHCDQ0gGRoUqo/W5floMQG0zkhs9zzB
C4pBqvefZw3733hmXaV57nNAIqP4kKDstaSGYe4tXRqSR00thZdvbils74QtWmCa0+YiFolZXu9B
pnvzPGRuyz7yswT4kXXZjmiM9ObMtQaU0Os13F4ra0/jLjDimXnmRGe2kg5c8jf3MXGeQfAyfdt1
1ReVRCfbOLjpdW1Vr3BITz1DstxNDwUkRzM1wpIntd3ZIpdHi0XFa6driqijGXT2P/kw86U96TPi
iJKMabB2JqjYXfosQEDw5fqHEuHU7k8HubrC2kvtozu13ui7vlpn3zB+QTF8u4yHJTMuJLpLJSdm
kxlJHahjmd+1pUrCmBakLj3/cvmNfMR2ltvVuu3LI/Q3N1XaG4fDC2y3baUxk9Am1m7p2+DH9vIY
Nlf63TWj7X99pdTCjYxlLnVBvO+VGo/ZRK+8zNI6wqWghQA8dMv6c2PnSUfz3ntwPa5guuDztqGB
vuo99vwCvoYI2cNLftHaKdbkn0Z8bl1/Hk86Opi+YhKhkUwm29JTtnNVIFmmvUOEcPHhbq3zIX3c
mElSL6lWa5xriuL4IJK8jEx7X8YEiJzwTlbd+HQp/4PNVFAbmyixucVKsCze+A2VZ26uTZlfHyuu
BqnMFhZS1b47zFyoGy90z0RbciZ+ss2vyivZkyXeIClomxFBG+epwdLZMW/gid6K25a1kZFl+jpA
QdE/rDTTSzvJ7tp1HolWfa0aMruP8Us8dq7v20MjlNJYyzP78iJHk9JTq9axVLyGA5Qr7S9cNRs5
E1NQbdTcYMxuM5B9J3TWs+ZGJYfjk+yirwqC0XddY7PgZofSEJ/WFt8e6qJs3M8byiYaquLle0bq
VVbeva4sTBerSHoDcXU7Ws2CQT0p7dWzWmbKZcYlUUY7RpMKyF0JXHONhD5yFfI2pUpnF2519d6X
pzIy5SbFDuKWBAcXeEsqrGNy9Aryi0XxlQfZbwnqb32RDpwrqCW57lLCn/ruzrV2HIJaq/zLzsom
DFRpciCjwkLB8rkPOrjvqOjC4nyH5hx17t9zrKDtXyCv6JZrofpk4SI6xs3niUn+/jJaEtYLvFld
nqWrOJJvAgMjNxR4ml2cA+8ty2eXUWJbhDn6F/OU3+Dad31lE/jyCi4lXX7HoAvzvPktcfoKDAOX
pyYRtpNKOesSPHdcPgh+lfe9e627SG2++8AyKhUt/NYlvoq5QRcS4WZsLpo4Rw9JznOp5zMopK+3
Vj1b2Q83IXthdlskompu+0DlbOluWBm4uDNlffC8fJSjb7kt2fpYqdFQBOIaJyeLi7uZGsm9Tkp4
TgvsTJ3p5HTlszi30pSdEW0OzoRlNQsSL4O06Tewqs5TrX1p72miAq/FgLyJ06+y9XBGmJ+p+WAp
HU4TiiBiXc/GQScffpbO/4NRRcPuVK/pbFMapU9RMKNjDejaU+WqW6z5Txd77/hSv45UjULQdF+k
jZsd7SY3/YpRxNmZ7xHxGv6Th+kem6IePNbSPTjiYdswA7jr1oyrpdtLChyrDDj31BjU5yxRrCUQ
L/gxk6uZ9V6UDeMYymfUYFA1Uxh2WpblixIXMiGVUN55zfrRIG6jybzDmabC3GKq2bNXX8DD4yK6
ZYqGEiZHZdB7ta24Rk9GzxuCROAzC2lCxReFs17QSM29QrK93x3ldettlCC21VdKD1fXS4Xv2Jev
FvYSOvIMLO5uOzgZeTGn3C9M/nhGaUpW1mHDX/ZFEFXP9NVB0xW4Yi3MmwTV2JH2fvLot6lyV+G2
w5jP0HDGOrlbCF7bHUdLw7nXEbzGt0ynFxk9wR6KRTlzXu9gw/ETaQt/C6tL/bb1I278G1QXqJJF
k950pNxsFg0ioHtr4R7fTZPQYpZX0cun8zD5czRfSTrvCFjP90nFq+3XaOgjrirk73bkG8CXqdKY
TGV467uC1aXsq2KqWOdKSLRTxO1Jixs6Lk+RZNkl3Siu1lO5vIP1xfZ+MMZXmzQCQfzHizjUnJNf
Zhv5tb2eWQS8MR3SJfKNCUtbSWpLZGCNI7h25XzqV5KCJya8JmctDaW3YjcuB4XxzrdkvzFJDZMk
ZAuxGg5T9TGd3y9GjUJp1jdbNcMY0swJxi06VL9OD1pnw2FnR4rIDb+AtmJfXK1OyfqOjuYZXG3i
lyT0Wd5OUh3FTq5LrYQh5/1xdBTvk1BmYoxHr7uwonzspMlFeaEkG/BJIp4WNHfPJPWhJkgVMc5N
2SBT2ayS4q3Pe+77AxLqxaMXyCf4hXgpZ2a3HJ+QMT+7lxekZkHsL6T99qrldWJ+l5bsr01T8e/G
9kqw6YlaCaevloQMz5E+Fo6hNrcPZB0ObIzHYo8ZKFP3UN/xaeuZlx1jClcaAXs0SnYQ2dZ7U73V
2uy4V5/C9Mywbtj7jqrB2YQ9shW1vo/T9/IfDj2x6UqgXogtznqKtHKe5zYL9jWBPe7lqpXGp6Zu
Tm5qOYlXz+KoHXAJg9J92V66bt3UPaM+Kq3Phdl8Rr3njY+Cg3I78kuWWXbexyjTq2d2nbPgG+zm
vrxVkySQKSt3eHj3IUfc0xkpouHEN7VIieSdX/S0tdZGzo5xTr6KFrTW9hyiRMpfUXHqP7R2RGeC
q3p1iQ9Inf6e9XycRP0jjRsEYuHkOM6u/paN/Ut+N5CRDU3MNtUyhOafs/zIR9cyM7Iw1QBSvkFM
P5LUhYwMzSHnAcdYf5woaGhoBDkCTfcGQY8pQZPDNXXVbhhZQ44Dd2XlZKUAnrABvhIyNTKG/Y2U
kbmauRbFP+v7fO/2iG5BCiA5/IHUbQqax+bmxlyMjJpGGupG1gxa5ma6DEamOowGWlrmuoY6ZsAX
ZoyPjcy19M0YjDW1rzFKf7sQ6P07/1DqIS1pC3Vz6IG7uoZ6UPY1zCEUgtmZKYCn0Fg4QBQs7N8q
FAl9p5wJ2rphZKqpZfqPQ7coGCV+ZQH8Mwv3TY00pLWA/hnvC9+kYJTRsjanYLxtABkLoe+/b0N7
ugmRN5RdGRkwUCPpW+o9pMVC8a3Iw7cWtH4S+EeLA9JiPzqTE2ixHKXIMz6UUH8C8Ab0etsARAEC
g76fe9sADLRYfrSYgRbbjxYL0OL80WIFWhzfNeC2ARvQZP/xJTvQYv7RgpADZjq6kBNocfxogZiA
U5mO+gEB9DAddQSCEgQ6agIUgZmOmgBJ4OO+AJrA7Md9AUSBj24MAqhiBh81AbKYj7sG6GI+6hoM
0AVmO+oLDNAFProYDNAFProYDKXriGEwlK5joULpYjnuCyqs476gdB1fDIwexxFTYGD4OI/oglAI
+faYRwgDkK+P+mIGlITziC5Ir5DmUdfMgNJwHJ/MCjSZj/sCtIjj+FbsQPO4LyhdR0wxA3RxHCsH
lK5jHlmg43h0MQsgL6ajO7NA6TrSMxZAXkxHZLIA8mI6lj0LIC+mozuzAPJiOr4Yql5HVLNA5XVE
FytA19EDK5A2VF5H+sUKldexUkPpOpI9K1Rex99C6IIWm/rRFxvQPiKEFUIX8zHLrABdxzyyAvp1
fGM2CF3MoGMeIVMZcvHRrSBzGcR8rCJszEDzqGs2FqB5JC82gK6f5hAbQNfxFGMD6Dqe1GwcQPP4
ThC6mI+nFDtA13fFBvpiB+gCHfXFDqXraCjYoXQdT3uAruPJyw6MI+cxj+zAOB5Llx0YR87jvqDy
OmKKHSqvIzI5ALqYjvWLAyqvo4s5ALqYjkadA6DrWKE4oHQd8cgByAsMPu4LKq8jYXMA8mI5vhiQ
F8vxnQB5sRydzAnQxcx51BcnQBfLESGcAF0sRwPHCdDFetwE6GI9oosTql/Hc5sTql9H8uKE0nVs
RwG6wEfC5gToYv7JrkIH8thAAz4UcuDYGjIBpIHZjtsAbcc2DKjEAGmz/NQBVGysxycA5B1bTBAT
QB/zT98DBDKz/dQBlMRjiwuCyu74jlDbz/rT94DRYD22TyCo+T8WCAhq/4+NHwjqANiOKYI6ANaf
ZAB1AazHPEN9AMuxt/nmBI5vAPUCP7MAdQPMLMcnACSyHN8R6ghYfvoeoJDl5w4AEo+VCwT1Bcfq
BII6A7af2gCFHOCfOgBI5DjuAHAIYPZjkgGHAGY/HmbAI4A5jhUUBPgE8LFDASrNQE74qQOAwmM7
DwK8AvgnjwMC/AK0ztiPEwAS2X5qAxSyHXcIuAYw20/DCPUNbMdCgjoH9p/aAIXsxxRA3QP7zx0A
JLL/BAMAEtmPhQb1EOzHigR1Eew/jQILlMRjIbFCSTy+IyuUwmM9YYUK8acOWKFCPL4DK1SIxyyw
QoV4TCErVIignzoASGT5qQOoJv5EAVQTj9tsUE38aRjZoJp4LHU26GT5qQ1QyPpTBwCFbD9RAHgN
MOuxDNigmvhTGzpXjlkA/AaY9SdNBDwHmPWYZ6jr+AlfQV3HT3MF6ju+UwwFoiLW5qLSULwPQFFR
aeD87zKDfi9kpG9kKm2spvHtBCEzAK/8UDQhM8DR/5h6QmaAMQH9ECikCfj5H/MM0gT8PMvRIsYM
sCSg7+IEmoCj/yFtSBO40Y9ZDGkCuOiHVYA0AVzEzH7cFwCMvhsJoAnQxXpECGBCQKxHZAIGBMR6
RBdgP0Csx3QB9gPEcnQrwHyAWI7oAkPpOroTtGoqyxETgOkAsRzTBQWS4OM7A3SBju4MBZI/EAak
CdAFOqIaiiNBLEd9QYEk6Ej0UCAJOiIECiRBR2RCcSTo6MZQHMnEetwXQBfTkXShQJLpiC4okGQ6
6hqwFSCmIx4BUwFi4jjqCwokmY7oYoHSdSQ+wE6AwMdNgC7w8ckAXUcQH9KGyuv4VgBdzEcCggJJ
5iMyoTiS+UheUBzJzHTUFxRIgo8kAgWS4OOzAbqYjyTACpXX0Y1ZoXQd6wQrlK7jswG6vvtpYJr8
c5UJHAf+VADmqKGmljVQcPfHpAFDEex3EIqp9NNlLP/2MpbvyPYfl7Ge4DKW3y9jOwGRHL9fxv7v
L/tho3++jOMEd+P8/TLOf3sZy3dI+fNlIKYTXMb6+2Wgf3sZMyeMu4H//WUcv0sSdAIt+eHxf77s
32sJM8fvkgSdREuYf7/s32sJy4+w1M+XnUBLOH/XEtAJtIQdBpH/XkuYOX6fAeB/ryXMnL/PN/AJ
tITjdyLBJ9ESGHc7gZaw/z7c4BNoCfvvOgn+91rCzPH7cINPYEvYf59v4BNoCfvvWgI+gZawweDt
BFrC/jtvzCfQEvbfpynzCbSE/ffhZj6BlrD9PtzMJ9GS3y0X80lsye/jxnwCLWH7fdyYT6AlbL9P
U+YTaAnb7/ON+SRaAoO3E2gJ6+/DzXICLWH7fQBYTqAlbL9rCcsJtIT19xnAcgItYf1duVhOoCVs
MERyAi3h/H2+sZwEl/w+3Cwn0BLO35WL5SQeB8ZlJ9ASzt+Vi/UEWsL6+91YT6Ilv0uS9SRa8vs0
ZT2JlsDg7SctAYG+9wsCfVdDEOi79oNA380XCPTd/EH++H6E+fuSDDKbvqvTP27wQ5+AEoo/Hf6h
L8Dq9P9Zogj0nep/lihy8y8RQwZhiGyu4iudrbwq3lavfD5wpBTrPDahhOQh+d3BN5/bcMgygyrC
+gZqxFcL1LZQFQRvkbKIUeCdR8t+7UKzl2/AyD5slmdnXbl0kOdg9NHZ/THWjXZn2YfV6MQ0lXjK
Er39o2hl+10bMmofVUjE453BbWPNNOhJN6kFnpivZKG56AQp6e7mieEKG5obmiegYLUicJW1DmGU
fjA3EHVTuiDP048nbhLbgdvITeOR0XuHpIA9xFl0Gima2bulg4ECX66Z8uZaOTMTo3ldukCAYO+N
1NYKnClj03DN6qyhOU7Q4Nk+03qk3Ve2NTpfJ/KqntNX7XNQWjbn9IrmfvmMG/1AkbfX8qtYNh0z
Y2wyrYMwjTLIIdrO2/5u5Y4Z2evL917qVvY0BBsKyhtLEg7q4w4OE1yuLCO4bT1d5deYsvg40L5k
1ydLi83wzERmFJqRpPbHOx9JJuvgepQuWvrbXjy0coy2auJcXK+UsPZKWVVMbrCuky4nqJoJuxvd
NmZ77ZNt5ZvAwnYfzjb7CnR5ybgC5BdXU7hGnBAw4Mpn5QiBcf5lYxVaVRM64kDY/6fDHCdXBHZY
itDOa1jGhIE81B+3hPbQa+fyJgOxnXujYMsu49sReQz6tpuxcCqafLzMsyvL1pUZjgd0KnWLOGit
XvO4cDYxMpSt8lRwVN6zm6sxsyl34K/V6rn2sd6gSbAJu0iZPvMKvBRdEerW24V4bwqzNaKd5c7u
e64vT6/Es5isXPU7mP3wMu8cxrIm3hnhDt2u1kieNKbzEhyLQdExTqHca/JXlfuCsGvrE3GZL4+B
dQs9u20pOkwvtg15N7Zcjh0f3ps7j11rz9Gv5DXekudvHNvWEJO1qZhN7cuFWNp7RcrlKnfulYWJ
+XtTn4JQlPv9s97q5mQHQy40xc008FvQFozbpY/99OFOAjVx8nooRq+y/ALb7d5GhWRxsaZo7I/U
KX3KBP3brxkvyycqeO4bdKZLKmNxGBfVHPoHZAaCS73Hr14RbPFJ7eKVJ1m4Ib8g57nfpLweCYcI
F3EorwBzAH9YT2BD5PgwG9PJB5AT5gByG7oJYJwZipCuR8v/PDnN1xDAKTTTcX3TSJ2NqV7o6TOk
Bo/lVJWnvWRNchsLswUORkWhOqjn1i8Vj3DY0jAQurtN9TfNPi3zvE3BwsW8FR1CsRKj0RGfeT0A
qRz3ngUWkuFN3NrJs4hNb+1QG4zR40E3lWQpEf1tPhNdWz8bNeMaR1DNEzcHenTNrvFmrTJjIo/U
Rq5lTfx0qD9S0ibdhY3WZbZxZ71AOgHde5xLWoHK/TwFdFvBZkPqY3Q78fILvaRMjzjtCvVX67tX
tcKxr4j3JDAjqqA88uays+94ZGk+nzwZ0lrewGVXyBMqWq+sYLAAn3BVsYMYviypBp1rS54GuRul
UdKDMD99v1C2rGx/42lKuKmhXNy+KPOwZgpf/is5/goNi1QD1vy+VL6pQ9lDJCK4thJZFFhDxAY6
Hosfe/TQXfCftuhlTC20oN9gQkbL1Mxc6LGaKQUEwGIy3lX73gKCpZiMcrqa5o/NoNv4wBwFvAcr
1GxzQBaqbBDHAmyWAnsQ0B/IMVbIag04F2gDv4Ef4ArgB/PHH//q58cFTNBuAJ0CMUFWv8B9gB92
yEIME/gPegCy5GeHnAu0oTdhYoIeB/rhgNwcOA58zwb1fj9fddQFJ8QI/eib6ejzjb8jspiY/kHe
ER/AZjbwA5wA/Abu+Ss/gBCg3/8QAtM3SjChvX7/+fXOTN8Z/8dXv34wf8j8n1f9u8/xuZhMFN/C
L986+Ven/esP5r874V99ftOGb4cBGQEJGyKGEIOha6hDAdE9Q0FDM92jA5iMN9TMtKCqzChoqqum
T/EtvUNYy0zDVNfY3MgUgCjfUdE/onpsP+DUn04J5t+nBJDTcjwlIHwwc/zfTYifRvn7hOCELMah
qv3951/PByhNwNFTzAamo8O/jhhw7OffAFXA39AufuYL+A01Dt+//PEDlcVPFwJ/s/88oVj/nwoP
6/Nj2gM/mKebCL9//mN9PmUH36gE/j+lttPdMNLXhKny35dU/1T5H0uBX1T+pysxGQXNNICcNaBQ
KyajkJrxLS1dncfmFOwgoGAqcCbwLT2QP4QJeHMds28TAujnxrf8M3qgMDc9EOoBMwGbGsA7zH6k
Xd1TM9D6hfbb5mr6uhqChjr60Bw1RmlzLQNZCmCZisn48PvdgVe3/cILy3+FF062X3gBXlwG5QUK
M6EW+F/x8o2RXziiByg/4omZgYOF8//NFytsvk5ploB19//DLH2b7ky/GSUmmCbpF8v8s43+3Rgx
/cMU/dOq/GSKvhucf2uKmH6yQ5j/yin/vwzRd+zw3Qph/mqGmP6fRuh383GCGf0feK1/6s/vs/l7
EOGfmvLTSvm/OpshKkkP5KiAgRfAQGYAG6wZ8C8nMue/mcc/B3qE1PSlRG9AN6blHuuaa9030jUE
8jmZGDiBl02AKEAMTJDRUqJgFFUzMFADFJsBgrPAoN9+Q5Nl1cxNdaEJsQws0Ag6Axga2mZggqbv
MTBDX1LFwA5iBXYcGL6l/DGAOICtJAYm6AT5dl8l6Mrk5+AF24/FKRAH/+kw5/GQ/Jslz/eI9q/B
C05DRBCGiF2k+r3i5y9ufZR4A9a5dREpxwm3Mbb5Ai4ionuV9Y51K6GOzR7f+ahPMVsoUVnIfoIE
zO4pzwJTF6t6q9jVHw04kUW+tGJCZyGuPksqQRoj5JfmzM2kRNic49wsa0jHhLRidDkbgwer0Dw+
Dxt+ZuiF3Rlld35eg83iT0/Fimc9MyNvFt/Wb4u0EbfWRDK7ZnB/1HJ+rOHQCZt/2GBO9t2ztmj5
faJU+6K25c5SXamclmDj/LZg69w2yVc41oXc+57k4+CSNqUPD5qydhKcu7q2bkUu5fdeVnYuVaK4
M99RQjsItiP3e+CxL4/CM2tZzr+qKLV/OXLv2tIHxYBpcLtBoXYEeH8m6RBDxER5zo93+XWunfX8
AvlQiFcd2zRzavCXBetVS0RDXR6V4Szp3o1HDYsOxXYhPgqiuIw2caKFru4vx4raZhaTg1Q+0/Ks
6sbt1vVWKQqJlwYXrs7aN9mzpRpm1lpXD7QBS1qKF3LvYa2XoMF14E9W4F2mx4dBJx7f7+H5f46v
uX+TYS8ThseiLTpZmxCR5KGFErd+mWWNtiqWqrWQR2xFiKrdvmRGqLHJc7iX8E57dCvUxPULbS43
3DwIM9mLfDaJ0B8eYPcgNMrVo5liEIWvM5Fp84XbeAy7Sr+Tjbis4Fq8Sqwj8XrHW9eHsGFB3uLl
OQcc6wfznnIFIx861sikVcOa8V3eJPjmz7EusjiUs1140YjeEzn9dYBhLuKTHh/NbZOrD4Ow8G9f
wf8wQ32my15qH5/eigT9EI0v0dHuDWNIkY/fstsD7QesBXVmeYerNQm2TaHONucE3d7eWvcoJE6x
idM/Q2Y+qEepim1Cxao8uXM7Z+LpDOM+xQpZw6WU6MpZOtvsCcblq44UezXqBvkaPkOZpdxieluv
DXSHUW2KG3E3r2zd+UIaa44bm1Ga+cB2/IH6i9oVYeR7Pezz4k4VjC0LDXklc+4l8CVLZc2tWYhy
E+/7vM4w5PLfJPLdT382+tiSvBB7j+fC2bKvDE4NZxbcVdxxeipaF+2DfZ+Mj0d3fxovUzcwfBa6
GxgXp8vDexA8VGfOJZ5qkMnStOsSSmmNtKpNk4P53iewqNo//Yx1eL2VtSGvYhGbqaJ3TdfGW8O9
S4ODSSNm02U+CQMXmq7RmWVM5joS2tQydKJzEhJUs2mkHu4tzy4YXwjVqptNRVI4uITcJGS9RV0M
1wr/qAmmooFPqFFAPvk/lUnmPggIcPWto7/EBFcT5CIx5Ue/8GATmTeXu9KDf18agR7rwIGqQrzF
BWWpuuzitab+O6IMrvY6RrbeTFwZ3i9Uuin6jE2RPiHM3u3Lc9XuhNfE2ezFMVl4vNbMcsMxehjH
5mmcGsfFRMTqswqaotLqER3rzKD9C6Xsjbewrz9WSONAt3HsGBZvQs1APaxWO4uasLa+ME/PIEii
KY5748PMxrlbG4dzciYkDYHa6UayYp8uzS/oy47rkaHV14aVvn1zx01/AZVcBY1PM1VxRNQZHq7c
TlcGHZaIToFaId7pn46O6Z9ujvPIzbH808tBQB4YmlUEJDExQW3+zy5OTOjWPSFhWmkbA3UjfXGZ
f+nsmL5fBRlJLSB75cdO4j9cHvu/gK7/HuIx/wzx/rnwBF54rPQPYPE7zb/hiqP8PxmjB4a6UH37
rpK/0fx/BUs5KH6DpT9/jvHkjxbT0Vn/RKD/Ao79HBf6doT9x+VMPzph+gfexPxx2c+/f/18v+8v
gR/gGyDOg/njj18DPky/hXuYfqLl+HPCdeIP6ZwWXf5rZPljP/6fg/0HyPKXCff/WlmB2L/hShAT
B5iCk5MD5sLq3y6qfn2siZ2d4mQWlY0DzPmjAU2IA7H9YmH75NBkcHXIDk0RbudcWJJPIL8vQ4GG
y0QTyOrmPGoajCSsl3yb6BZLjVs9nJQMxXVXuY+XImTaZWU0eb2qNgyU7HPJZGiU8ZVS31okrsd3
KghskjxENuh3MBrsddi1nHAwmnByLFp0GuOHp4NzJqE5Q8rEeu8ptSLd44jnHNlwSytiLW5ujQVO
/eec2dVdzJ+K6OQljt+CI+JDh5PNovR1F/TgmqC0OQPHYxhA37tyntsfsfhdzXPLJjZCTYNwOSc4
5yjvfYbLUXV70vuaCM7vZIU9SLDLlEqvwas+J25ZJKFf896TsWd5TwunahVy+6mhwJrzY81B5w2z
h+bM+vrnUgm6FwV2mhMyzxuSY0XDoyYJr7iwvX7fwtmMf4vZNDQ8rcGS33ljVQEJDmUYIWkh1AZB
ktDW1mXhztp5s+cLy0quYlUBfJZanOl6pO8Tn1t4NqjX9KVZbTXy4rD5oqR9tBdkiqzQ4ryZ8ajv
AmuAl+eusT0bBsMGfEu/FXozIvqrYgxUgQ+sITmgrVz+lKrW3O2uEOTwuvdNVO28vrKkCSZfnJw5
v/o8Rs4oEB7HpCZQTOVd89mrDqnQEhcKYZmOVEtJTcv4gipVM5lB+dXO/t4FOYqZwHtfxS9If8Z/
Mp+Dh/kGjSsySyJwvSqfGDmqej7GlWhE9qnM1UpXW6SDgoCrZ+FZsxrVmR9lRrmnTQZjIMm8uUJP
4vJs4zEKdVyxsCL2C+qRHs/7UTIJUp8SOECkhqjeRGgqg4gkfYOs6leuBj5TvwwyF7+h6UbHcncD
a8XpEI5qdqcyrAIx7HUFzcL43GscYzH0xQs6XlStOJHhe0qfSgsiUnAb9XpMe32fIc9z7VePl2Fv
GsnwWNnErTcVBa/tTpCTvZ1PMgwjNzaTdUdhNajM5hxQ8mAmQ+7UuvtxxPL2WgQxFZ8451udPfCN
RtLNkQbMw1xTPaHWLyRW7/dm2uQaNpT0GAxIA9PU5ctil5jDGV5LY2LrfSWVaTfyR0IZ9lpT5PZl
3xnzGXlZyqxApk87NWbB4FuzPIjDs7dyCVvyQJEncn06umPnalPPCIrdpt08r1/hk9xMZQvrssDJ
cRGeojuWaNn+ctxtMYNgxvH+qv3XhVbyGZVlYcuKFCotMoUL4K7PbI8DDGtcZkvDOkJ9Nac1NALk
dp6lrNGqLNG1be97UEdG7RjcpA2bxyxcVnRQtunNvsynYWgjbf9IpPhi6sdDJ5F8cTaMs1MmPFuR
ZdY2UsMKEjtGgvbE5CWMI6OeOcwI1H7MhjFoeW/fpb+eUfFfu+H/bPvu7a5pQ/Z2xpRb8V+ahzgr
zAXvR6cO1YUoKPs7EDgR+Cblm4QcClrsuxO/MeSdZ4mX2kBL/ipBUjp7hSFw0a9sRrFKYrxG2ks+
61qyXUW6QWlnxW5s/lfpvh7ljvtjHlW2QRLJfSVig9ZL3NO51Sgiocxs4euXU+gTQtM3sCZx1H3I
xbQt5rUzOYqkmgM+XkzkOyhd6/h4QyFtwMmYlLSof3AXtcHR65BHv3nMIIbTdHJINFI5NyNvZqe0
Z/CztGhVrswiR9FS/mbr1UbWQGfzA6walSv2Nuo39qYlp7EcQrHO+bxGcvuclLNTBULj//wIZyWF
VZ2k/4WCV8977S4eJbIrZzccLdtnNyousrfifbb2tGabMO52C7DD9GhQz+RFz0hIMrPMWlAr0Es2
1Kcw3bmk/cG1c1+sfTAiiulu55uld3L4UVfoCUoNmabr7wtpt2xzccNLm61r42pdmcOTuZ57xxSP
7QbBS7VUsdeUQmVj2CvPbwc9XW9xInWjI3sxC/KqaWoKnKAUQicWw4ymQhJXfQ1uiS6gEA5OUNug
mGe71k4owOpHhc9sQS/eXgn6RMpA4iOyueVXFZwhztJz3vepWObL96pE/sVX3pTck0K9wfjSPLzb
/+MH8Wj8iWe1bkFnNZoI09tYwNgTNecbL5UgXdQSThZ9IxuMMtGJi07N6qdLmRycURKEVTZsbbOZ
K3fJO7qgd/5OzhK9KZ7qljYh58MUuOXw7nMEZ1lkwkhzOVeN2AuwCtPwrkshSdS8CyOYhmuIbV6i
jfNx8rMaXvz8wAJnUDd/yHEhXYKMLPPRdaOLh0/szn/mYtGYiKBvQ8yQY1VuOPSzmo/bSKhaL3UJ
dSTk7bJcR+Pk1CKYTpGlX+K7o/jcNX8jaH0C38+wFK7FYNBo+PVziTUz66o9FIuExOwH1LLhPvca
n5vgDZj4xS2ysVUmsAnXsFlm0S/e4r40kL+sqipW91TLilMIfdFG1NAmg9XiXNP7orz7Mmwzinm+
JBbO/BOzwyhGbIwNnBn8el22yYObpXPBEhOE/kZ1OPoXD5PqFnof7bQMo4z2GWpN7b2Rt7qprYzt
wDc+xXNHvWgedC/ej53LmhCEsqhoZTmAa9JNVOxWn8gdWKe2+iTtNdhd3eSOV3p3BdmzB068UXPg
lHz+mS+sMzpRGgXDRc23zpGFbpeX2xNfUSSYRc7mn3gGUnEsULHc59CPU3fO8JFBUuRzL16tUj1n
aE1+EV5jZmjn8sarkOIRtZshnyX9KCkP34M6uTl2xUjDziS3CAsiqsWJP7r69OXVdx/z1ILUL9PE
6s0JE6hRJ525gWHReffx+2tBdyhZ0aWy+jXfNSAjXJfj92FqfnW14hUbTho7auoeeP/1ky7ix9oU
71uEcQlKxcqGUW+/gyuJJkIOxhMKHZu+qx0+UE9h06+wCP/u5Uu8/Pl3khhP3pa79lHwPrd89dUz
TNH1/UdQ6qyfJbyUw8ct23sVTDJk2O6t8UK4Un6iFDdxgvViLFAf5HpWE37AK32O/fU5k2DITZc1
fWRL6c9+2u7RdJcu7WFanb9erx2vzUKzJiQcFXxXUyxKKqbz+pJmCdIz+eRbnSPXMb3LWGuFkSOi
vZ56jX3hM+PAlihtIQpAJ5rX5OGkxHlSlaAachNZeqSFNmXa0qNqVOyZLDL2x5YEkxg2k0vt0RUv
pa99uh9aGoTa+uAJ6f6y2MIH37grh+Hb17H0ZmpHJgd2lV0FRUQUm2fMkNvBnmcZ4lkFnKtf3xIQ
aaekoEAXRrt/Pp3yPeIXF70XZ0e48BJbCUQUROZouEamnmvRPVCQI725/3jWsGYWDZ2jvn6zQWW1
gdvm9oLDZp+dY1Fm3y6SwatW5ofzH2/whlEI4BN5aysE3p81p/wS8Q4DbaMDKYo+g+CyBT0qkoVz
p8p+p3bHXYNXYnG4Pfcp0VwiDiiVOx/12Go9tnK+Xt1GGEpPwyroms3F0Zyw4HP41lXWk83WfYv2
KZLBrVeyH6R9HitruvcMqqC2I9XxyDRc2U4MwedhdeHqyDrPopy8Ru5y3WVGdX0tm4u+8sn5B6+G
YjDu78Sbp7jei3n9yER+8+wsqfJ10vFUoVhezKBdtCmwkPnuQ29PVvVHz0OorxDhJKnhXyRhldi8
iu1/O4gYuyZIICMe4hjPLeA5KJr6q4alVnHcYrqChi15IxqevEEvQtgIb83Pr8bTCMzU84poMIw5
w5+9F/Nl8a1P8u9kc2st84JvHrLrDrSS6zwHfaksv1nHjPWI1rNYayEwdOyqp8GWmErGyjOvW2gl
53Q8MWXxI6rQez4sOoWR334tmvUyemXa1INsfiaKFIu23ETqTtyb9ODur5/Dv3yKRTVJ30GVo2RA
MxuOlAhstq+xy5ee3jFmM0WT5d7L4t58KPEkdM8q5lk7VYMy69gaXxQoZe+F+eLaxWd3XjIGbHGZ
v0iIGF1RD7FrHGml7q+K6UzmfqxnWhc6mjeO4f1m+nqsN77ZfPhIic6amYpTV3lkUyed3goYQ3Gz
a/2ZFRtfAuHw3nSVp0NRbyXOS5mbsb53100H0y9tWnTWpjemrO9W+oTb73Wp1D/F0zak6BxyRFWK
2OP/yn/QoJb2oXwC85r/pJrOBLzNomwAF1NFHslZDx3vzwHJ7/s/X14cjK2+lmuitMVPJCqLQspQ
1Lw0J3DjQdxl03nuMu7rPGPSlhvgdbiL0YI8ws7wIwLOj/fEnaPfl8S6dD62Jbm7TO8RMvFYTOzu
SzExBbz1PEvRC413VWXfOnS47sxz7pD7btr5Wz2U/ZzcNOYhUhsx0CKp0xWh4NjOU6WhtFCW/+KN
Y1juyCpVAdZ+1jycHb6tqcJeeHRd9iyPU8ikot+OVKaqUNMH+HCGgQafh5lLmQy9KI2BB80FVvKN
Q82i9x5hP7WNuyptqBg1iFflVfQxVsLy3ByVA2PrNbXONHGnyP3rDruBnvtgr03+Nov+nbWDJ2bi
99TGnakss0kMKxsxyB8MiUrsOO4sR8y9xeozkmdRSG3vetD/ksRyXXhLTmdShd64lTuyLr5lsCHS
sYYyJZRrj8FTjmSev5vM0Elv8V0IlU7bM9Ndql1bz1evpR34DzufNX/KbsBtSu2NNMgx5tkfiNcr
C39RPwaOmEnotaeUDKpBm+PSxsyoXznc3ZSbgaPOJWi34buw1GOnLdsYWZC56s6zQDbAcF9ovGDA
R7q3091fNegz3zC+Zacc1jPSQdYxL9CHm007gUwG1U2z5haBSebdZ5Zz9q9yF20IvtWVimF8gfWC
fNQvYqW/QO+FMpf5eh1WcnJjPJ4GyxsfiUBlX7LLSkQxMwM5WPZXCrkk789l0I87PgqxNlav3Mxk
57XRBxNY0i8MBaXP7Dkn+QX30zL242bMXLip7RHTn3t149pAEH93GAmb5r5Pv8R4P49XAGa7psXS
/vqXXtnNVP5ktPyi3PLH9E/c8m6tOKMMnd2S/Eq6MhE47/a4J/nyqM0NT5kbNtey8hAw0M4EtdKw
eO09ecFOrKVx516ofOSKmUDJrpBT/m6GTzOKQP76RqEeGj758lm1V1ou1v0151CctjcczabVUOuR
CYPQ46Kw771We/dMekTruVvwmpA1+W5XiSQHMnvJ2Ql4ZNEMPCQTkiT3qDRSy1LrRkk6RCdrVQ0U
XlWmuxRnXjkjlhefM73YPuRh9uUp1pjAJUeJsoNJTVI+SoqnnF92bn5Fpx5mXEJcqyRWiiJQOlTc
Q+dJfy98g4v0aWg+ShH6HCX5hhBIppR3RGzj1ZmNh3S4iRVO7wLO0hRjlqbtCBfb0pSa7A4jXCy3
fPFSPXdLdJl0TWT2znkLqrCSTxHYLnep/czJ72Tm4+CW44xFXe7x7vxAgy1OcaVEmfTR2dTbKHjM
+FMoLK2tD+bQpKZ88Q05eghd8Y2INcsuCEvCPTNGJXuFVW1v6scTGx7vKbskr/uOJU1IpC37ve8W
RtcUKmJzD3HaeSlJM15954b4R256+2gx2CHPSUyo33iGIPlZaFJ131FuHl6z2wmx0LbURzqrNax/
La9BuWdJ/EIdQZ2WJG3spUAkzsAoal5sHaZ6dxFVNyy1a0HNuZ9obKqV0WrVxjIRxkm+wFvdXyhD
tH4Oqrp8k5jY/ZKoCbV0tQzODUcJ9ed++pSitzg5bze+OrPi9jLW0Jyno5nighBhy5UQUaw2KXnB
xVaV5lq0uxXec5dlS+9lms2hJ446h9ZO5zxkCO6tvjhROH4hhzrsGYrjeS/a1EkrtvmMrUel5VHv
84goU7BX75NRVO2fb7hvfINHfu3JlQUa0PMn2HQ3bwstyFK8b0hDzMnMsEKqHdbzbm2bGsw0Jp45
P4j5BbNpmOq1RsWkwJlXm54I2+HC9ve1oyKlqqXUL+ndhl9RFKu9f89v9nmrK2pc232uwNjmGHPM
/hvZrRpreMkiEs/vukZMVdgHkYeWlH5VDChny/TtptZHodUcn8PjrpM0RIgbx8kZVyTLfsFd/sCE
tc9CuTFvNYfGYxt8gOSk0ireKgqWf//G/w4Vmy7bOhvBFkLCO7zankm+mqtKt67Z35whrrqbFdIY
/TkrICjnTjkaL5MfXBGBVW9kS+lmNT5XQL2qnybBis7VlisYnzML9QlD0TvsEVpA9MEoXIZn92qd
EG35Ah0baSLrQqrvyCOsqtErfZWhc3/d+O6y3RSfdxBGECpD2OX21uU+ENgttxl9WlDqXJGfSla6
uFKX2aCd4+J4L4jSRN010oaD0gZEOXxZRVm9yvKWhvEbjvv870Lnr9AJzrq2BzBoyOg/bwnGyUk4
08Gm24FnocRl0AV/NW7m4cG8nBOlVttXLBry0FjQfZHgTux8MxXlG61Rn/jZ53smIxbtGrk3B6wW
Z/2FC32MAu+8Cp0wUg+RzHHbQ8bZE/3iZDg0cGFsoMSq9OKK6PSjekO/Q6qeMOd74P0veI7aLTkc
3cXib3hfxBE4NR0ybWpI1TggpT3MnZpE+DKyMa79hdYYi4HnwMP4Yopxlyp5Iau7T/gqaKFAbkk8
k5zMRORL5PstMs6Z2ZmZvdfZHwqSP2lNvpxvEO+9kG17IWsnl/4T60LDzNXAkb6HBSWSD3RTaVRU
PjfKPqG/xnCdrrrpDVXLpaFk/As3nkgoRrGaXG+PLyggq0xEw7siizYiIyjZJE+SUI7JrJUcg0WP
5VTZmq05rZB+RbbirLLEUxwp/B21+w8yxooFMKbNBB/ITSk9HdBrvuFTgkc5ahrlgZPhi4wvNiL2
fIOU5M6zEUFSRulX5PcRP2xHnKkeI6R45IyXfN9X+5YINQg15VJ7xLAAQ2nS47cXMFrEWKul3uVz
+xNF7SOm328eNp2OOCOGUPbktWuP+B2WMiSEm0TXz8RruklWdo8WP6JqY4q05dV7pqlISyopiuOh
7i8xRXfzo7vJ06yR0Ow5iYekfQTPwx8lWyx9fOWgqKZ/3eJmlBFWuayeUlKXBSmiA6eVBE/H0yiV
quvuH9Bvjt6bBYnd07j1jBfNLiFmkuSB0F0c/vfNPJ8ULt656DnaJxNDg3EvVzsxwd4sZ/Y+vpSU
EKhDJI80IQLVsNpf8InxinqMxEfFxGUWzaSYO88a8AKDhNVanqibi+jcd+f8UPqU9i0V3eV1YkVs
GWJZpjdBXk3ttbktsrcws98Ts4W/I7xYQkwcZ+NiXdvTOFYfKd8n++C2A8IXhPY8JyXa20E4LQb7
SEQ1nTW18kL7YHFWn86uTKpLyMb3QFX3ng5O63IEjO/NSCa6otah7D/sdRsYeD5ulfMVKbJhh8IT
g5fzvMII/i0u7ZKu+Gn/F8wNexna+3yxnDlJj0x8E7+8ZhzeRk6LqGWlPcTR285tfshNNX4oyJsb
jSXasVTsEoQjVtHQ4+7RaXxnpxM//HaLhQvR4tBdL7MldwLC8Sh8jcpy9I9DlUWP6Wb8kq6MJrBc
EZ6O6rRelEqdzFNUab4WmteUj7FW3nD3zWc9ve2XrHsha+jSPFfp2o2HoxA/yhw8uZj2vgbZlzt9
8HCrQFRhPNAbnGIo54a1LKM1L12ceLEUoy9D0dUNbojgpqpAmEu/OsnaSty7ixZCqGTtBS5c7D1O
/eVGxgY5pLW75xcus1AIY+O5XXF9mYYyrICKqEiyRzpMt2MbzF+2x/kc1LOiQJM55yH+3KDUIB7H
8EbylLPy8PV4msSSrV76Z+cFeww44bWkWFdr9om3ed+TGBy4c+ajspaiNHsVXgxou/8yZ/GmUmLM
udwKIaLFq/6jHPz4h8IvKRYykSTP5NghLDkVp3sw+d52IzuAd2veJBZ82m9Pzjf4YMmY3wVu5PxM
12UWNP5SnVbVs610hwTRFuWjj3EFVTDX89IjHOs/RR4SnbtkWG6CtVL0NHEMhcnHGn7eChVL7eJ2
+/NZKg6FqcyzesjvUc3e3/pMecBdKmTD3347m9J7lL/Ie3veOKjjnMSWSWbsmyknotGtbZVi7MxK
DLbMh+Dii8PXu64KLZDy5V2KqOLkhydLagiM6R3jfpj4HH6S0sWaEZE0FT8KOarMzbKO6rXvfecd
mhWHEQoM5ldhzd6FCqDO8wok8b3uNhdUJ4qq6geLg3Qud3YUzTFuCPLuPM7HfJ8IJzsEP8BONmT1
0qWGZSff+yBcEdcRJXxo4BEC6tLnvtB8HztHtKdea9mY3oWaF9i2up76JFaoYMoh4kaTWlXJeR88
+rAI3rnZaeaT6XNPJ6CXa5dNCDOzw+I52y66oQxn6BODe0b0o7T2F1USzZQjP5oPCFinfu7eDsnu
tkGPwh4mWqlPsYxt5JTkXi4tt6JuRKW/r/wyU5/2rcMj01W53dqV2hX51kcrJCqh/gef/AtpYoqu
x4hGr5lJ5YqKLb5uVYjJuhrTL2WbKXO1VzNRkY6wdjuD7kUGhRm4Wqu7zyKyks0p+LHWLbyHjERZ
bzV4e6e2rg49rx/uuqhU5ZFjnBX6+clwkj9JNL18kNg+igbxjVhzf6mFT3QuUQ8DxoKmsp6G95gJ
3FpY4/TwtAh3m95jcnuD7kD0IPMKuYoMwafQ+wpEpUL9ljT8nVqLGRYBn9eRIlsrGpTtWud6ZggW
Ivfgwsa0NpZFlHNpOAf9g1i8WrMoxZl1e171JE5vG7Pc1Emw6Kl/rvjpHsMO4+7LTDsBRUyfS+XT
3RoalrbgjzTEg1qrrvdxJc75gsKIYgI7WijWPwpSjfIf4K2bxG4klmCQYmFWgKscPpQ8Kmoil8IV
dDh36Urwx0h53AW7uuGJdxFXDh3K6W5nUM4+Kq9ul750D2ThJhKmjh33sPw5o7owho9o3u0v/AF+
UQpVZVXFhDmu9mEJX8pirAIVfC0vrHYOZxTNWKvArTDgDT1SfL6ZewkpdmWL1zG2FLlMpmKuVidh
LtXyC+niGyvxt/gVMU/YHzPqReoyZpzZaLZ+Ba8NDgydvNfYE9YQ0thI/PKi4Na6Ry8RdXJZtqS/
u6Q2trtNNSF9GU/Tg/HbpUwuYjkpHSkiSVj5doQF2LNCi8qz7wlz818onxHvVYxJkWK3/PJ52K+0
iX/l0VCk9Ug9SVzfg4ULhbvoxawoPDljtI1v3iXcSqKjy51UL3vip9DJ3fxp07CNTepqQugTy4Wv
nwpywvI+Gw8nP3uWzUBnfECVrxr2suFQh3+/aE4niXR1Q8qd1qOgOOG88Nbehg+j6mpRH9JX9TWE
xCYHOYbsdoVIhZz55UhudwwPcT0yMbi78gK55dEi0WwZfm48/vpIvrfN7mOovZmQTAnNcl6jvUp/
aX+/UMDoyvn2928Yr1AffCIdPL+nqPpprH6oZAjlihJRFrEr8XViU+LXRCvEpkT2xDeIXImkXBo6
pSgY/aKeO8uLaUZRmsA9JqblwAsiQiJaIyZ1TspO2sNgsok9c+ag4UVq1Wqv/fircbizjBtfNTDf
s28r2mwdHvJzv5wk7RNgYKe7BwdHP4QDc9/8R44SsNH50+GT5yixw8pRsn8gbtZLcb5gV24Om4tA
hGKtRaF1q/le4VVZu5oxZypSWo07ZNFXGooWETKStVu9seQJNuY1NundiXXCVhFqnxBwSovRqOhs
XgkwVntci/Sx/qU2HRVtrQm+fcDVKfiSnHdY403Bqs/uqj9XJ6AWOTMu4owv+tCP62FGl+8Z9alO
CrA8XwNYdqx4edLHO/OGwFVwQAypzZx2H7wxOfqCfT0WfMmFy+qabzyeG79EuR5sKhPLQCURsVLn
5JOqFXypydQBtY76VjoqRnkQH74XGnbrbt1KX8tVrU2DcjEE2Xp/KaLp2lGJ/Lq3TDZfsTg8iw7S
7Tc1JRmcijtGZuxNssPKGrZNTTZJxDnyCp0X2YtSAl/cuZDTqTjwriv7qlQSarhkVfkbr5G3QgzT
xPSRchKxFwawA5Nu8V0my7zEO8f9uXR0UD6TrTNL6EP2ULCckgK7UNsn3iTus7kJuf0piZ/MXAz1
ptx90tssw59gk+uBrmexb8R8vIslfpboTJ1hkS5LmFqhQ7aBbXPnFCdHSWX0zWXt8knLhHU+YvS1
9Fj/Q/ukUoloFl02U3yUh47NXq8f1pm/x7fJJ2wqLWCg+Xx3+J3I63Fhhey7qIrTQ/FVi4ZkU75S
gd0fZVZYLJef67I84PjkZ6yRpz9XVDJafSBxoQbNyD8qhW3JPQiNFuHJzYmoimSbubThp8t2vHPh
qLGTpe9jGEDLrWnWPWiX8q+ACGiDzwna1pNNUhY8y17oLq3N0u7HMLPu52imcxZDYBT3DTckL6Dj
odVM19sxTrBav4NGUqVxl+PaSNU8X4GeVELxqKWeuZFqf5aM2kDIzXuaQR2MPoQhmVd4FvWMhsX7
Ryeto26gZOkuhORNn8mcn1QVH3QD37oqwxb8cSlgZ+7DwcVLtdEV2MWGI/5vxHpVH45u9ghyNwse
mrSdV2Sd+Pp+z6yVMxf96d79LQ5+KcdM04ba28XTZeqO8V+rDaTePt65hUnC++WcYAw2O9Wt9yRt
cjI7Tv5wvWVn6Y37h4zft0rM27LSCmDsLMk5w8MZg/zewsrmgRba+TG3vu2b/ygMeZwmAS1ESfEt
CYKCGUTB+H3nHPLXDV1zs/tapkJGBsZGhsAOOpAt8VPFnqPHNo/mKBMT7En8zzmbu3UgV/kx23Q2
gonRqTgNw22skzchb0ttsI6canIgUd/Zqy7JQcZmeL9BomjBYVvaYfnpTmVckqpJDKaEHqND/vb2
5npotpiY2Nj4ODER0dzcnGzSw+WDfTtnOES43fucsbDsDwfo1MJg+kNhsJ5EGHDycDGH+weHXcs7
RvULhEkjZz8O8+VOhvSudq3shvatsmVPwsUOIcYOXU4bM2lYKJ7Ziuxf5c6ZRIgbghxHiB26lDpm
0rhYMrP5YWCdP28KMW4YJ3HkTvFM0sjGxt4BAgbcZWO+ezAlAv4flsju/kH78o5F0yKEPfykEYni
meSRjd7V3cDeVdbsSQjbyPFD9FkTrm1L5bPbb7tXWKFi+iapK+ljNk2LpbNb/t0rEPEhxQEyUq+e
L5rZ2tk/hEhE5CY/CkyJMJ9WImzg00nkR62m7xJhBZ1EIOqqmgjw2gQ0qloak3BSYYoUkoZpTEE1
ZXVVjBSo6mhoL557uRCpj+DAwZ+Bo6KET4PJGstfH+wT8bazu3iY3sVfeq5oQnn7lUMF4qhB09W+
LfvlstRH2fyI3XfryJjo7CjyFm7v1GTbKR88ND180Z9CmFRHDi4uz7xXwLu0stsjOsizWTDycPn8
4+erEYG0ZI77a7vkAhDLuBnAmwRTGqz/7YH+UYXrR3YP+KQDjaBNIMvGpDo5NDaiPTk8PoqCdpYp
Lf0sOtrToEvvIYP8Wqq1tRWcYbqCTkEpQmUCmDz+TIRlmFyynXrM/4793562mvHMfq1HBqKzgxMU
I4lgUdqx3plvmjlL7t/Jr4ZwVizVQcZ0Yd9HomjR8UDJavpDbWVcvarJW0wJEkan/N1xiP1nvyMm
5u/vHxQUpK+vL5uiuD1chgIIA1GXsw2mMNhPLYxTDvmPqm3fhcHCfMIhV9dWU4PM7KEx9eEJyIAT
nsfDIcDGxw185f86wA8ZlQkOJwk+HyZLHKdlifW0LLH+gyXmEw0vwNJNeLok/XiE+jnSsGpFBkNg
YM6vweXB5ILz1APzZ5aJk/MkXNgu7xu1jWNlzAJKWpw/51LSqWO2YN+9ueKx6BJ4t44cDtnllvb8
h9dmi00Fhx1m8x9a3ePOC1K8VtmM3xnxCI10bCraFXGaZX6HuuuFot0byZi/Od4b6QQYaaMK7hhY
ouA8NWDj/CNJnGw8c+02U96+xT979iwiDg0dnf3GGjFgW1WRUGRhMnFqoHVa2/qjHuKPicZyYq08
A9HKufp456e40W4vQj0CscrHgel2BiQsXAEHAQZkffCmMHk6NVQC/9nInExHdw4mBz+y85vdK3qj
simstv+m/c3iucIdx93VxYHZSIzPfDoPN5z1xoVWLzZRD2yZzzU0faYlt/jMg4x+o9wnm1cvf09t
t21xPZDvsaFj7VmZnH0biMaz8+2fgRidt9k8gTBFcWqMdGo7+k9R/Cd2VHsMMKSq2MeWFGDpvBH8
c5gs/X1sdHIgvL578GVy427xDEr8MHLc0PWMcafWper57YCeVfCniW+Y90LyiFLl/KfxzYThdeH8
6W9LA8g/0uQRtaq5/Kmt7PFNydIZ1PhhzI/DPDmTb3tW5raBpUHTO559mBI5NT76G4YoITl5fHJS
RwAhISFBLlV5f3eTETBEAhdRvGAycWr4A2L/My44TsIFl91GUnw8DeJ1VQ0NXBycEVHkvr4+YmLi
SD4HBIiSxlGhHMLk5tT45Q+5YTkRZN1Zm5Y2NmYiJCREPFdcWXmVmlpHT09BUtJkdaJhsMgJEYkI
bi7j7DpMjk4NX/4OPJW3P3xxEKBDV0fORIdIGauF9f5lfs7awWQl9WCSJZ+OCjw++8CB/uobIwg2
DTddzeycgGDTdQgicLto4zDR30Re5Mj4MK24uNjZ09PTxYWSh2evNebO4cE+ImR480Q4UmEK49Qo
6G/MuBA+h1xXVwREnFd+ft05ZpOpKkWAmxQ7j/IGBhNgptMHnP4QyrGfSEdXdhczUFTEs/kh/hDu
uQw7j27eznLfbiQr4eCLJEckbDylfZrhr6FCqY50hZsV5rvMzynOe6ba+NuuzAdb8Wfz7S9kTCK3
ZaDM0ZIRGdixjU9MWvEfIkBUO9KUBwRTEP91DPSjrPOP9eVJAwnqZxAg60tLpiGIm9TQGB2bGEZG
W102yzBBQ3UNulEKXWKOvIYsMsEZquKmKwBa5XFEiIPJ5OnjR382f08GinI3x60Ggq1a9cihq8ta
kghLlV3rjf4m9zvk7ex8WsrncPDk9+On5nb1Ih1VDtfyxvrs3vpIPAoQws9W2rc+nF0kyTaE+Bla
GhomEKj761c6hc9zEF8DiAJziLMdpihODYr+1DifCEDsbC1/iIqixMXFRcRpbm29TktLy8jIKIQg
IiKSqdN0sDFPAvhPPSwcIZhMnR4W/eH4nmg22x7OGpXFYHnNRjLR2xXD3byUSN6huGe8Wbfoyc6n
a2hbm096pTprT3DMr2tyYN9+Z96o49mm8bpAxfjk4ODuyu56KPv6+jo6OjoGBsbKyor0VQmbzYWL
gCCI4DndYAri1GgI/Gejy8Z2IkU3n34dG3v18uXLiDiq6uo4BASdHR0WJiaevr5GRkaDn/S6qnzJ
D0uKD/Z3P2VlNWfdDeYZL/PAAvR4novUHCanp4ZMf8MLyeeYxnz5wgHhUkdnMEOrrimSHx7wQp0o
SjCZOH2kh/l0XPx4UcCpF6Da3xYoI7/Hed6+kYODwANCFwRsmDydHiudkqcf70L4izydPvDzp/jv
RAAdTgnuPbAjs7i937W8kze1CVkuWTQtWDQuRA6sty/tDKzt5UxuPmtfli2bvV8yY9u8mDa6UTq7
FT24plk9D1mUsWZPQo5bNC4G9qyG9q05tCypVs0ZNyxAVmdjG3sHh8AWRH+nGD8soYD+NoQ6zVp0
e/9gbGO3fG47uHf1Se2CUuWcZ8dyw8L20Ppe7tSmY+sSZPHJmzulXTsfNbBWMgvsVD0qn72cOnY5
bUwgd0qzes6nazmkb9W6aVG8aOZB2axP10rL4g6kW4hE/MNEnsKUyP/yxh1kMOe29qrmgK0miDgg
LHl3rrQu7Yxs7H0e34SMOfPnCaZPE1o18x+H1ytmt8L716RLZy8kjeAnjbBkT0IugYggsHfVsH5B
KH9KtGDavmWxfHZrHbpxZ3NHOBimRE4PvE6JLll+MXCnCMH8a2OAArEF+MbwsLYqwKDTR5VOa7P/
Gcr+j+3bCP6vPBG0wh/A5On0+InllMME+g9A4RFPqpPH46RNCGVq7M3rgOEAYM+BYAS+FyZTp8ZC
EMGfjql/bpGynAgL/VtHdF8GCK6QoiDAKuoBBp1+p+y0Q8X8J0P1L7lCgjBFnIkAhsnU6XHQ3/Ov
ewcHKzv7Q+u7jYs76WMbr7tX3NqW/btXi2e2Btd2v67sFExtQpqGdQsmDYsB3auQZvH0ZlDvqkrV
HH8eYCkhDuhN90rM4Fpo36pz65JZ06J310rJzNbSzj7Edkp03SWAKZTTA6lTjjQz5//JSI/BQFJE
iQgXYDJ1eiR1WvUF/5+rr/93pojfIlyHxRT41EjoD6O3J+IJqSQdEw4ODj7tsEhLjSJKXJ0E7vZt
g2wlYFU1oIQnDpOT0yOYU/pr1l+sy6m3TGCZFyBcibsB3wmTpVNDkL8SrgTbeOXl5WHiPPfyyjUZ
rSxyOgTCle5DZ2GCDvDpQcdfTIA6OOxb3Q3oWRHIm7qSNi5ZMvNuYL1zeefz5KZi5Rxx0ghmwjBL
9oRV02L+1FbG6DpkMQI5Ahc7dC5hmDV7wqxxIXlkI7J/7V7xzKW0MaH86ecdy53Lu99WH3F4gpIw
JXJqyAL6M4kwn0hTd5ZHRYWFkbCwsBBxllZWcm1WJ74PrTcmujVMRk4NU1hP6ftY/2kRgRl7oil3
A76eLike4a7+HGmYojEZOxZ0DwsjEw5W1iIYfGpgwnrKAWH9J9w62R7WDz704y8BbPTx5Nvv7SG4
AvFjwBCeR4Gnh8nN6RHJX13KzW/vl85subcvy5TOQiYcZOEOgR3tyzuJw+t6tfOQ2caWPaldPQdZ
r0EgS1DPqlzZLGnKGBYwESdVq+ZdWpe8O5fNGxdvF07fyJ8yqF9MHNmY3ATgiHCFEKzEAjD4vx7X
Yf6nRP5CXAd8ajTCckrnwPzPTCvmE+0LQBNAEO7SYSTV0zh7+oQ/ffMMSAEJ9FVxFjlPUQx3/ioc
zGUc8/9yRAYCo6c2gXCUcf0Ce/YkxFc4tS7Vzu/0rO6G9K1CgDJ+4gh91oRS5ey7/jWIbvt9XeHN
mUSNH8ZKGGHImoAoMORI/NA65HLw50nmzxMGdUCK8cYe4CX2OW88himR0+OZUyotK+iPlFZz5F8H
IOrhV2Hy9LcBzYmWtbZbS8MuiCgbC/15WBjO3kIe5xz2tpYPDw8BK0tjjN8Hk5VTw5o/TFYC3jN+
EoWVg4s/XNjeyxrbeFg2ezFlDKKAdi1LzUs7TYvb1k2LV9PHEWKHSJLHoFhnLXdqU79ugTxl7Fua
O0nyyP2S2bC+tc/jm7q18xeTxyCwRr58NmlkY3EbMLGvs3hFYYrj1JjmD9cRJ4M0a9PSGtK47Ozs
iIiIly9rqKoOPTtLCEAa5asoozD5OH3k5e8t59d2DwqntyyaFiFAky5zXKVyDgI9U0bWIb5UqmT2
euY4+sdhqrRxy0YIWt2ELNK9Opclimeo08d4cqaeti1Vzm4v7BzULWxDrNed4hmIWfLtWimb3ZrZ
2ts7AExRqPXNbJhC+dspzhwnss1cWzMejRM6QPK6M3bbCkp/F1/h/nb29opo9ydfItWROVqye0Xr
2/upRTlxg55JN5/fSXXImN3eJM7mTzSyRyf0V9rULBs14j88ABZhRXjcQTCZ/18O8GzuHVTPbds2
L4oUTLN8nlSrmg/tW0sc3njRtSxfMQvxNIRJI5w5k27tywXTmxDP5Nu1/KBsFoKxJEtmIWe2L+0s
7Rw0Le5AEBVEm7Rr5t/2rJbPbk9v7u1Ctwu69G4RwhTKqREV+JTO6dfN2hPNd679DZ3mqC6MOjKB
V9UzohaBfDzbG3FjfXYT41jDI3y7Ksp7S7NTs+Rku8qlyMECI6kpjnvI51XhEK/QwdzkZD59yOe0
wPGXkM9/HziynBpp/enQnYinnoO1vI7GSejQVcbGMS/aF24sy/WlsxsLdo5j4bwsslkebeqkHsTI
voRnlmQNJ7MxU6UCZLxvs9PBBP0sp8dPf2/ezm7t50xuQRYxfLlTl9PGRAumvTqWPw6ve3Ys3y+Z
uZI+jhI/TJo8BjHRkQNrEODp07kiUTJzKXUMAjP16+Yhzn1ic795cQcysW8XztwqnIauorYg3UKw
KhCY/SDCDlMof/tpNI4TrRp6so0iMzOZEYmIiInpVQr3BoucsIoOGvl3X2pUCLlrYTk/txsvWwNy
AbczhxZ0OnwkKF0FNPPnt2c8BhcctsPNdi7WrXgYm+zTNwX0HSJAZvSXNyywEjzBLH87GsVxspia
6Wpm6Q41VPuXP09SDx7Yr8z7DpbIhdGSlVasZ/P0Hq7sVmwWhVkWqSodwDFEOE30f/Itkr5XiK/o
c5/Uaq6hQaIISNc4d44TJj5j+dtpRhwnQqu2u6uphyVyirTkYCCNrIZ6gG9vR2f1zaJ8aGQpsgvN
eHnvropjU+HqI4vLN8Istss4rQpJrbfLnkyaXQ2i2PXycOjiL9jdJoSsLCcxuKtgcn56RHdKewf+
T5+U+NWGT2B/N+IEr78FhgnC4Zdg8vTXAdmJksZy7TaVn8hfADLhEBH5+Z10dac9sMgd9/f5Vzd0
KtYliAJ4nSny+hkti7YclzqwAgsYh11f65F1qOwsbW/yv1OvYUWtkIK0lZEurGBBhlTjAXsuTPZP
Dcn+cLFxojm8szrZ5E3MDDwuXVxcWqo+WukDLCC1llE6YDJxegjFdMpBBP0zgsN+wk3eKwRMcPCu
VeUYSMCDPKQCxTUVDYjvbba3kJ39371Kex5PZOHyxS3aPwuj2fgRpw0yRUx8dBJChtQDcSXEMfAZ
wCn316OXw2T6vw6owH8W1PgPABXr6UNXLKcEib9kjf2FbW3WU6OnP4zUgE40xfZ3N+d7sxkvu9wJ
ZOjPs1qcbIoE5pioC6E6TC5OD3dOOTSg/5t96KOhwQmEjM1oABBEI36EgAuTqdOnQQP7Dafi6hcE
fyJffvRc9fmGxhK091++2Fhvb33EQEJ65ibi7P7Cy/MO3LXb13SJXykBz1V7idVeTwDGLo0X5QVM
Nk+PWNhOaSp+WXudyMf9q7HD/iUJhgwNAWZYl/X0cAR8SmvxiwX8r6eVsf51NHIiox5ivZq5lwvF
1OervDwSoQULjOrT2fNpyUsrtDr5uldHqhLJnfI3i9RVluEYDAtHt6ez+V80FuKqrKIyPM7Y305n
5z/Y30WBrCeiLLiNYfJ++ujQaSMEv2Qd/AWH9rcfGeM40cJ55/DwMEOrLisri6hYQEREa6b94+HB
ft76ttWKZ/a3IOCuF0pw3ADf9kbe/ozoBj4WserIRp7KnNP2aOmuyrCHShmyS7XJ5osPqU5wSERw
ujhsAzD5Pz1IOeUUBbP+30xRdcJfMknw3OG7YbHEdmqMwnFKYwpi+o9YuoLCBMpMy0hPTzczNjVB
1CVT5nOEp6CnuUKHEP3taXHSNXiYT1Gw/df3x5iZ/vbMYzs9XvnDmXeyh712t7MnCwPDaMmAVbpw
Hy35vcLt6f2mIlwjeynFQ6RLqMKktGRsKgdbc7uRCWcXY7r4XF8ozFk7zq37jmMVzejboBO29++Z
d60uFh0eAK5k4zlPFEwB/Nefe2f6z+uHfB/U75mDEwTAuI5OTBAEvgKQNI43zOfewWx/O/LCeTJr
ur84GEs96LBRNKaw/kqtG7FzHAsRq3BgdWS3MJAf4VyhK+qNV/0LhBC32b+9Z1cd1bWXSCaItJ7N
E2qyu+ojURTbt6eZu08M8axztGQI+KS266O73wpv6BzwwXreHcz2X4c+oP/bjHo8goDvxWHw0eF7
YLJ0eujzVx8kyZncVKqcJUsZQ4wbYv486fd1pWpu6033ikjBNDY0jw3yj+Xz5NvulbqF7bc9qzcL
pnESRyAHeXKmwvvWJjb2WpZ27FsWWbMn8RNHxItnUkbWv20E05fwD8GUyOkB0Wln8C+ACHyaQYaW
fIIO8+TICA4w0vCt79VHoPlU1+EVYHJ0ejj0h89bn4ijnr2x0NWIwL5voVPhBTuVBZvl/VYPlXTR
QdQURyRspEujBk0B/Fumcw2+XzWM3FRHVmYj7n45mC7p4n9j6Ng6uOPtgHyrGYKHLkoUOe2uAhG3
B1jclTBl8LfLB51Gz6c39972rAjmTWElDCPHDd8pmkkY3iif3bJoXLyeOYESD+g5RP9FCqbihoDH
gyybFmkzx78d58yZjB1cn93ay57cVKiYg8wUvMQR1aq5ounNtV1gJ2XxE99XWBJh/9sJSycz61zL
E6J7y+zAc9mMdsVZe4LNJXKiyodfV9YUmqPkXBO/FQM7l6eib7tiUDZq5IKigpbi7gVx1oVjB4F2
Ko4SX5a7rXuZX+JjuciD7xVyHx5MphZBs0Ct+nlgZgewnx6I/ZWid7k7y3LT25vyoZEZqdbF6SNq
ay1ddioHX9dH7PrSIRKKZGIEnmyO2FU2tFkx2G0zEjAJ/uQbVOwawB3BmHM4XtI1aLZgbzmw6mrU
IRTV4Qu+V8C7v1Hl+00a6Rd5k2FK468/r3+y57k31h4pKIR6eaFfvnz5VVJCQq7D7kbc4CEb38FE
ziLV7IoHZJ18K9UBz2quwa+LX3lvi3t1QwdiQJxdBaLTDm4PBFvZKdtHWky+mLaMpxB2gCy5qAcP
ANyD0s5ZB1MQ/30o98fe/pRQjv30UO6USw6mP95KgsGSPxCPwmOAfw+Tp9ODsj+0YyfaheBaWhGd
GoYYLKC+BMSOuSy6QKyT/SDE6TW5BNonkiEgU1ZrT77owCoydFzp3yym/fKlpFNnddHRZme+qb43
EjObT0fpwFmjogzi++4V7K+vLvIDOxPyuzyMMOVweiR3WnVl/1N1/WU5OeL3HZySwwan7KeHYn84
tCfy2bnb09mHJXI/gEtuaGSy49Z6TTY/K+FgXYoDAgS4dFv4QpYX5vujqa7Mi9GdPK6oGQxOQTYz
/f2MRXJ8W08K9zl30V+9a92hzjR0OlhahWb36zhwe8MUw98OZ51QDI77tjduINDS0iIiPg0I6Jzr
znTa31nfmIzspCUv7+JRB6rofJXjQeVf2Wn1GIQof/bgPgJkqQ3WI/+keLA012v0Tr3kAdbwCGQ2
aIfbbm5MQvNh/B9wnIMphr9dCIDzRLumtlvrVlPDXfmJ32ILr/XIGop2x0dTnfq7+GpS7QBtSHmL
pZBqb7+1LlGxvQlBNiUVSpuFPKsLkwkeKpif+TRc0XZIrSHYN/Xw8BAohXVek1celgT+f6jUffKM
oOWd/dTRDa3qea6cSZLkEb68qVdfV1JH151blyDLLipoRhBq/PCtwunQvrW8yU3frmXJ0tkraeOk
yWOKFXMfh9f713Zbl3a8OpYh5wvkTdk0L0Iw7fjG3i60GjONmbABTKH818No4F8iLv95GG14HPeb
5Zt4AzV8BAzw/TB5+usY7GSFgjbme8duv8HHxycmIuLg5MTFxV3sy1ldPDwMZyzsnbctSZuDR9I1
cOSaXAjcVXEkjHCoSh+hFH5lsf20+nKqkcNOwf62Vd3FpmGv4ABe48HdlbVe6O5nThIHKUwx/PVc
pxO59hDL3czW77lOmy6BXXwHhRvLgXURgXO0ZMUVyVaFHAcTkyVy/ElWfDqPzuGPKW0bl/pIdPHt
e/HthECg+HOKSS8PAzm+/J0DIO/noirnJEzu/+tgDcz+f6XY3x36hN/3nTZCaniYEbTTV9T+O8X8
dnYmVcoqsMDfqoEJQxwSm8rB0sxu5DhW4QV9h8qMPXjhMJvtsnZcowX7A97dRp1kcYngAMEKekue
wf2R3ZYufnus/BHl7fM0pZA1a6snOzv//sHmIrS8ODcNHydMYfzXERv4b4cT//vls5l+SSUBn5al
H8Gzb7EzU5GKcipgOYxtDW8Gk6P/UfBlMnrzyZPr0AdDnhYWHpQ+OwuAr52qwYk68pjOb+Driyyf
N+fORE/VoKjy4VLfJg4EfF1KJB+PtHGa3k+FoLQKNS+X50YdZdGjRotO24jnVeESb3BchimG//qW
ItMvW4onLiL+z4FFaQUeMBXwuiMsgwE8rtcK/xAWP6evof2nS4sT8dOztRVaszGZ9K2oaOo+Y1PB
rs38qFHR09QcOT43VAS/5Y1J7kgn7uWJuF1gQ+vdCGSFua58aD27ughZalzpgiw1rqc4ZYyUdBkV
HcJDwCTfR64umBL4Xy6Y1L2ya9+yxPFl6lzC8MXkMd3a+ZzJzbTRdZ2aeeqMcWRo5WKK1DHjeuAx
xKyxTd3aheuZ4xB4CfnfpXW5eXFnams/YXj9UfnspbQxvtwpCOYcW9/9lltObC5QClMip0ZdQE3o
HyIBn2h/559KDmI96TOpN5DrKZxLXdDS0gSeOV+hJeFGQaEmZMdiJD+/dBYV3eWxGrYkiIKKgfIa
Fb0QLwUtNWPqu/jopPfoLIriSkK4t3R1Z6dck9rb2JlYbiBXQnoSJIA7S0wMCgkKCQ5VeCj/qNfZ
O/1TWzZKy7mX9xoFais6Gvqf2ha31SkoD1R1NfFTvPKVoLt1iWjs6av7XUyv3g5jA7hN+CoXzIdr
/oPi339jpZZ7MJ09GkEIQWlMdE8vJYY3+RZtm8yukqc6MHLK8ri9IAx32BzrjdTN5ks0tEcnlOlZ
0qx4mqpyuMdtPvUqOZkeKG2PiEhOrqKiMtibbQRkq6dzscF8IP8/qBX+hxI4WS3IveHAroPAH9nq
NxUiDWxW5lc8VNQ8VFaTXb3Opji2m6yPJpI7WfIdGmbvIu+ix6uXJTd18h3szDcVZeo07WxtGZuY
QFBVfEICg3zW1OpkE6AJXdUcd2HK4fQ1MU+Z6feLHNhBJ5HDE319PAICbVf4M2fOUFHFjFb5Hh7s
7y4OFqWqFC1MT/v5+akJIAhoZWo3JCQl+QcE3CSQk5PjNxkpj+R3AsDC3jaRPUx2T19L/M/YPdkz
7T1paohA6e3rj/X19yCM+pLzF2o4Q3g5ODwkhzhJrcsUFTDZOT2a+0MtPtn7DDYXD2uy+RHPFaor
HwA7/xv4WPbn8nu2R3bnuCM/sfEjewm82pjQYTZ04lxd0KlvYb9bF+V6t46MyNDh89ZBIIqKU5fy
DsWXC5oIk7UeKXYqC9YH+9+flhZX4SOHKYpTw8C/U/JkdVJCUZEUGFyctE+fHFa2ar6XPHlJgu4J
k5G/vRHKcSJGejZH8toiCKFr6v4UQoVIR5X9pcSSTh1jwW0LiZ5Ux/yNZbmNj9mkwONE+J38unkr
ywuBg/iTg2bJbl5nkx39TWb636RCZyeRBWc4DNaZ/3rd8ZMlJ9murVuVBFslfU9OGtEje6CyZ7zR
3xSNaxQUwO+MmpFqfd5mbL3Dtyhg4DAhffqa8PnnDwP5Ubn3diYmB2fJHDoG9jAYDNPGu1dQVACv
xBHHCSvXk/n09cbBp0yi+0UArCdanfV8MfkQHExMQkKCqEzBwKCspLQ/05HodHgwPjkJ8bmX6+QV
FFRyzdFogCdd9zWxYYXMmE9fZvxvlJrist9Kg1bGV1VXD2HV6+xKhQ6QNDHMmsTMpy8Q/leeUw9x
WnxRWxkHTURuW0EZnxzkPzzQaSlInbk1EkZLxvBld/wgcHDYQ8Us2R6VEItzb2emSsXpYE/3yZPX
gYE6cIhKSv3h3FYHB/skEG9jd4NNCibzp68q9YfO80TBbQgC0NTS0hJAHhgYGB8fpyKiYGQ06s7Q
4nfcAzIhhT7iYMLk5n/y3Si26zNvc3I4oS9pqq6p+VHSXAMHxREmE6fGM38I39hOZDFDQBru/v54
kFmloVHX1MRvOfcVeKhG8ct9RUU6BoaXSQK3b+vOdiYLCgr29fVVj2xsbHSlKO0eHvIDzD4xJIBV
U5n5PygI/ochgRNh1Z29XaPFdQmp76HJ93pkb8OdnA72U0szFzkgyxZUML3dUNpuxcYkvyzPVkLm
OPE397DUt7myNEvOHemU3bNNeqk6Y89lnuHdyCKAcu5NcpbBFMGpUc7fUNqePKtUb28MqBGV/2I8
nG00CLj5++9Q5GAy8T/5jhTbnbGPLi7w316PRk/vcHjAC309GimKFSwmTl/g+w+N4Qnf47O9Gvfh
w2XoqyLuS0vfuXOnrhzu0aNHcimK26uTWABHgYO4ujA5+tvlDE6GvnaWN53mKza/R/4F82nJPytv
b43sRkbMRuJ18bu8sJuzs9npb7JTOSi/aHf5ywyl8Cu9caF3G5ODB/Z7W+kZGVKysgHwGFJSUob9
uQBCObjHPgFTAKd/O9wpayL/ir5OtJ+zszJel/Ag8dLly/h4eEFBQUTGiJiYPk9RsAqdDgfq6l6E
h198dJ2NbaPkKQpgOuzGz8N0Ff9Bae6/ZD0H20Mj/dl5tICIeHQXX0LR2nBfXmSOzoAJBK1gjz1c
brY7TFRiLGT8siniMIr7nOI8PL4bqa3Fxn4TL2Nh74I9PDae4j7NwtfQRHInIKKq2c31GqYITg1g
/kqwY2dve3V1simS1+GMsC8ZL8SaGomKit686f7ixYuMDDA3NzfwbpDrAELlc9gJZtbx9vZu1gwN
DR3MtwG2BDj7L8LBZPdvx3bYTpQoKF9gayEvL49AFO0saGOzXfOGGouUI+1xy/uZmSe0tLT37t07
I9Pc1obo/0BaWohgbGJC+dOTju8uhUzhwjRMVv/2O+LAJ2K1tqlJBwJNKc7RPcoY+/4ksbTxGRaY
LPztWM7J9tJ39hdV5mN+bLwKKtKSbygfrkGMa0oi+ThgfnvnbU1W5pt6I512ye2RZRAJJfi3NyAr
/0h+J4br11/7+2vCPW1ubq4LZAQyZ5b22Glgcv8/CWxmFhcJcXDUBRAgziPuXvjOdw8q/AkF1guG
mP+D+t1/GI47kQPhOpiIW28khO5ZPb1U1c94r3Df5mBfIrCAsVsOgk/RUxxZxicmN/kPG7/sP3IY
lf4ChJQt+Q83dhcPee02Hj56lJ6WxsTERHPtWrJizkpvthGgyPmY7KGwpHD6gt9/GsU50Vzk2lzQ
qY7qugtIAfoi4LYIQu4IJ5VD6IaeADbqa/nV+L29XVwjx9hI+7rCEUpFRZP9N5205IZOB0pWy4iD
CR7GJbG05Hx7O2chVvdaIddZmOyfGkb9lRCz7dKQCxDouI569mye4/4OL4bx4cH+4mDR4e4m8FyG
5DuydzDZ+Q/23P6MnZOBotVJ37g4agDnXletgneWwsfHVym0h4cs+Be2UGHtHjKfvkz46asa/PPB
eLaTFmE+rmpQgxwNrWqAjAStahB/RriinMpZ+47Y7Tq4a0ApFBGK5Oik9wlnojtYAYdIlYTGCpPZ
08dq/kpld5DGzSstFDw8PPz8h/15Vt/fpmlZRmQDk4u/HaM5USjc9vDAQVBQUEZG5gqGm4cHo3L+
1mxXKmASiyzPwXqxA/Ppy3//YVz3ZPU0gHpCLy9yq6ur4+HjP3r4kCgNXk1NTVS0qrGxMc9q0RGy
BKakdPH1xXoEf38RsrxwOjzAhFg+6mx8f5hc/m0Ew36i+ZV7MB3YvTEJPL9f/KriJSHh4GHu2nBc
xTm85a8aRhDjHm43Ed4842EsODrP+LLwAKjL252po/f4MVOxgKRkywdRX2CmOXWywHqTDvPpS3//
lZk2MzWlCkDPC8+9vJRzzachlh7QUONqFFhvzmE+fbHvv8HEzsZ86IcPl4EMduBdELarE5gA/nr8
EsUDFhOnL/H9hwv4k5Xe29ndXKx4QRgnHhoQEjIzPq5lYGDw+PFjTU0kTWtb28qqKitz87mBgt0y
Dyxgl/tg387MzOzu3btXMISFhf3fvuW13zpPA0COdD/qHZh8/2+WUtpenfQhYWe47PKCkLHQdn3m
uwrerCV0hsnF6XOqTzl64F9SE//CK6mYT1/FG/RnRvGEr5Rdn+0qsNs8R86Xr1UX8CBRNvlR5plq
OFOj/tz1+d5siKUHAimF4xeKYDL13898/uOaNGqTsGsMEdyB34LJ06mxxunh4T/1j/2kGZRQeMjU
UNlYghb9rejV9jYyBB5+PCMMwMOgIA6qmGgtZ8vq2hpauGsiVFr4D1gtMMXpgYd10JHRYG6mnL7i
9p8uU05kNHIhmhdzJ5ABF4VBOd96c6G/yAn6hu7mj/RcMNn425jjNE/c7O7uzs/Pd3d3V1VVJSUl
vXr1KjIquqqxbWJuaWNnb313f2xjr35hu3Juu3tld2kHqKy7vX8ws7XXubyTP7WZNb5RPb/du7o7
sbk/sLaXN7UZ2b+WMLzeurTz7cWSZZlSZDCF8rfrCZzMD3Lt7HhsHshBU0j2cqkduvjDrVfLNuFu
vNIbL6uXNlLZ3+JeXNCZ/iQxNPJej+xBmNPhxmTkwGwksIv2YlbfMcRhhx7w/xeHOWDVEGA+fTHt
P4RiJ4sC2m6sBWdkgBGvqdb6XxsscgKsUN4VlHxYLJy+dvZfCWSGcFsxcHNzI5q8i4kZ/77YMXA/
Aytzm/n0ZbH/8DXbJ/R4e9tmYmLo5OTkiCYCUlKm6zMdEEbk5ORE3yTEx1tvr1ABqtWjikkJk6m/
XjfpZExtbx62h0ZqdvGqAbsnQQG8qBxbM+WhkbhG9jjy+6iXUIW1eyONrPfm13oj4VGg5cm0J1f7
GQsj/z/m/gQeyv77H8cVUZYU2VIoCSHGNvapkKQiKooMSsiWfTeJUrJUQiHahGRL9n3fyZ517DuD
wRhjZn7X5b7vpvvznv//y6fvt8e7x/141DVcc59zndd5nuc51+t1zo4nxQ/ollLdX7lNz5X/tS+L
ZlRBjKzy259E8puD07cUK+Tshv3Cw1k333U+Cw1Fr64GBwTQ7t6tde3aHWPj0+FBwcFKrgtvExMF
I1NqamoAFg5WoNmf7xUmq+R/6cw0PM7l3Lnd/Pz8mzPT3AkbWCA/BfcoPR2hJTdWWOJ/0Y76jyxV
PAo+8NrlaNJfLxI8k7hSvJdX6lHFu8wGAo4+EbJ1/UocwyiKFnHaelCz3b5OSFuZju+CEZQQBAUZ
mVehoaE76AsKCpreyIPdEqsypFrJKr9tWvNHyl7S1pHPnu2jZNrHyqrkubYAZEKgBVVLaKzIKrFt
UvNHSgo9hR5QcCNry/2HD03R443F3ngw83k+SHOLrBb/la906mprh8bH75zaefbsWQwKSfznCGAq
TShZJbZNKX6zcie5pWq+nPPsq/x8eRAVjvAICekbGGxsYNEpKSd5OK8HBAVZDxS4xcIQ1IB1ivB7
yTUulvhf9JT+TY64JUzvWd58HbPJEWuzzJK4vXrX1qKG/t5mnJfi5b46p9nxkPFLPXdZpRRU8Y3b
RH15ajFdc9EtQwLFyfk0XOWwBxwMZnszZbBkFf/j21y2lLu6Y2ZSuwgRf599yQzSDCnGLq5OwGMp
RWWfVRx2Kc5ZIHQBgf2ltIIP3flkr6+rLdncCOJhBdfvfX3Rz58/30HPxMRkM1CwB0DHj3elyBYj
fnarloGK8/zy8a/xnZyoP5Mfib/HZf5bdscr9cEj0vsKcELr53axqr2/rd5kvUTFWnO0hLbWOJ3m
uk3Q65r3vNoSM6ga73uR/UsVvlZ7w7HmzrosSXvm8i9Sc4wO4oJqHQ1HpS72cktbfMoQlvi+euB7
kZXSZ53dEbbcXMEpsJzmg77ZPXzyb5Jk1YMGEuP9P7acfbPf902MazW/xWkNx0fxXiaOHzbKa3cd
Cj0fUTdTb3dOaX8Ad29QYlDKeYGkM1CGV19aqyiGEhgacjikkZlR0VocRhUKJ2bOQlkOC64U1dGa
N1/gf+r4ykeQlzLuiAXxx0c+vvqLuyxS0F8TeJsDMW7yoSuFX9TWZdvipR6UHPzGTwWll+Hdf6Jj
/4vzbtGxIumJT7j3pOt+nTDd2R8IuevoxWYTP0vFfShElL+3dOTAbGXQiwr+XephhM4gmj2vj/eV
8VpolPudu3riB+W6SIF+3hOdD/7wOUe4Ex0s/3kbg3oB5+igSFr7HDRJWv7IysDqlSHcJfEvUjbH
jrJPfuLdOMNtWM4icHLqx+L59aL83Z2qAe/Dz3cjXt4Rxcf2PayxDvh8fcz52cePaYr8mXkqRnEH
5+6NdSTp31lgP3JltFR7JV4kLfMcZ9Fb16UaoszK5XRvBlbHqsk8m/OLODWpkQN5rtLHGfvNZl5j
Aj+M6Dgirp0N5dlvpf1Y+Hsq3whDO+0lhZljyxyya/eZJPbcX340eOnxctBi5Pt9fAqGkx+fewZF
Vmo8KjxQw/nQ/iul4c70bOWC+JuOfPD3EcyK6a9cR02Vy2/dP1V11kSD02Ps0dW3BtBPJ1TezrK0
9tANqdC2WKZFq+eIGDDL5ZQ8PaxWa3/qsT3bdAkSYqx/+t698BVY4ij+GvedaofO7GtZxbXfhnOg
bUnnbb8o3JqtWnlfU6+0Wj1E+zSe/4l6a4ELeuOTmqiCXZud9Xt+ix3sfZ6rPPkbNRxjnddgw4sD
I6rX2eBomcyefvnPGXhvFpTL2aXh8OfIZ8oVGToLB0Sd9c6mURocThX5nkpJO9f/ug4Vx+bcjt3x
ugPJbRNsM/01R/bGC/Elg2TqfkHGtb4guhB5ArU77wnVrPuxjyFsazsNP2uvnyyh00Yt3HKYr7m3
jOsqNVic2RueL2jjfVqmOz70x3cadtPlQN7CxIWu1iBpgw+Tz19URxmPOXmtQIoWbZamuIFcayr0
60UGcg79K2n9B2+2VNbsyXWIj4qK8vVVvn17dKjc3/fBg0OHD+PxeNu+HLv15anPn08AudHFixfV
1dVtbGykpaUvXbp0+fJlBgYGfv74XXSsnhtrz40PBD44QgeibZg6+1GyiCP1nwKCLe23UgpanHJp
G2PMyjdcSHWv+Tbr0xE8oWPrPYDd8KgPCwnOh+9O9q7InjaueddlyeXttYJvbrNF3EFiZxGDYX15
/NFCXHnzbrLEga5eVLFNd5EiBHL56tWr2triCgqebZ8ugq++geBfLsC+y5cTbNZ8/5kS2Zd3/2o+
vq0E5a6V1W0zMzMjo4XFxdcwRNHHjx/DwjoaXktQ7tz5MS7u9atX9PT00tY9ywDHf3RZjPbRYXDD
uo8MA7mRLBL/agT+z6MU39omnoUZVAsUxt+/ccBlNgg/zxbsYXjnjbs8rmkiM6ToUtGiIK6914/Z
VuhkAdyRWJ8OhaG8sPj5CaQEyns81gvuTCjf0OdmLNxwHp/Kl9J3udLVXlFVdZyf38XJybr76xjA
PZpji9cW0RPFCCL72VIB9i8UPCUUQ0oaZIsc/2r//VOTrTWVxRCJqGJiEYGAGa+OxcG94YQ1S2I9
qp7b840dDl2QD18t3LDD1MfyIwkG+DWPrqcoCVuETfGSXWuQpn6Mt/zi+ERnPDI/1euC3OLx0e8z
gTq2uFTEDfTkzHo1fGIAq4BfnSgURRRsLGJQRCL9B6MD9NcogJCKTL9CrgmIxL9aef8Mk1t7QbKB
Q3a7wCb6sNr3Vm8ut0Bz45GNOXiLmTbbGW5ElPuMw1wcpjEC1pCPw5YkcUOV8O4rI81J3AiAGuQO
DnSpZxc1FOPGStCpXUgveS/0wAZf/efPn+no6DgPHpwQ1ctBEAlCuikKHuuzM12pwIUp+64PRlo7
wbLwk9DL5GaaSfyrjfdPdbaUqc6WQugenDpAMUhAPBNhiMvMzJzSCpBUobLL0OJwPZrQxzE5s3xT
M59w1hepBg/NwiuhWF1enW087k2j6pK8fP1tVGavypy2E9Pa/ZDvit8XWpXbtfTewwdVBzOqCq5l
H5P3q46ba/iCrbueH1PNPhKtIbjj/uNASGjLJHED8F6D2zeOk1UIQg6AtlT0AtcaBkYcIG7gpquR
+XCCgStxZjCJm5MLoY9fmHneBePyxINewoYkGgLLsPkpypLb6yZmstdHF3bSa81tHp9aNMPNedJr
spBgUembSmNIkCGMV6+rwaGKWGfqhAkiAnR7akXQ7b06tWjJKiBOzlnEt6TA6gQxKx7JHFLc0b0U
aNuh/MmU8XanojrwP5/7YPt03quldz3QZUw51LpZLsUbWPnV/nBiUwH+OmLKt3yerdWS28LazdCd
gC/ShTX157QhYaX19RqnT5e2tNj1fLOIEIUTAM//x+UrQJc/bH46lawWEv9r8MrDjGEAv269VJTZ
gzWwb+QNH2MMzFYUVcJ4ryc3v9GFVXEjbuXhc5ce8Z/2N7yYi8Uu93Knem/0Y5Y8xh4y2njAP9u6
j3/FXMWFMeIMPXudZq94qPlHREQ8f37Z0XEZgOPmN/IYLHoC8BBI4IPLYno7wIxQVUOFbForTSbk
QrfoIOkMFEd2U5Rwtzf57ad/yi69850Rq3maxPzi4kmJq2GvVSsa+rySWfZPRH8+elSF6n7nDZRX
IGSizwPRjKbTBWSSETquQlYmclF2a0/XnTiDWp1APm0udOlBa9vhmVdZGFeyFZKKFow7PqRmoDwv
yWM77044dARp+u4tjPGaqA9jLEYS113W+5uzhLi9GAtaB9b73JBJKTOxwUXYXEzF1PT0XSDqKSoW
pqWlvZYwi4EhCG3xmkQC/haIP2mb+DPVqXqOrCZkgi34MnArqx1HJBaKFkcorUU6LwX1p7AdjIq5
gfK87DyPb8XBdZU2ejyxypNDXQM0hqxvPLKXSrvQKEQhHovBYmBRMZ50chvHR9p73Vxg3B5o9PeH
SaHxF4KePnVwdg5+/PiVpEVrqS8Nt6L7MnpCc9NpIaDTvrA/S/YFqfRvxOolHBir5VO8aRXWztvW
S7R0hHxxUbItWLYDnJZu3rsWhm5yQmm0zTUzBRdfXx2sb9QsViISXFZGUi2yldS43awzZ1RL3nXp
2HopEaZn5j9Uc0ZFenp5iQgLH+Xljb8Y5byxtphtiyRg0f4ggSulBQkcTO8suSarEtLkYjVka5oA
4PBO2V9cQoLlwAEqKqqCgoJrX/QWx/H+vbEIjAHx9rc52bYlmgdJAFHzAgJaRDwQs9cXksbLaIIu
anKEK+67gf9ujaqfyobZeq2LoNv1u50013QVv3WvvJ/oAbFKDHTXyU13PUaQI7s3QppcfN6qJcbq
w4R07zRFT01NJX75YmVpqX/jhvvk9yE1FIzbG/9hsU6t96YoQ5bSU7l199U3zdkwojdhrnmeDVnf
XAwdWL1g2da2UJ4K8gviWm+7fqznavGB6/jHLh3Kb0SaTYILr3sSZz7YIgh4YrMY7dlSo13ge5Ug
SlVyHX4koORC8xY1IRKJ1SHcooYFMgjCxuSkuZeXl75+b2trqxcOg0TgFiejYhW7YOuHPK1z0arL
z7vQ8965AOxmoBCrBWsDrljf+gG2T72xD7m8++1WRnrU4PED64ccJwGerfZ1JkZv1jXGcXiuzAPO
5Y0rJ2ny6fLZw2Q1IReTxbe273MRQ3ztAvNIQdArbvQYY55WjNgCshRMD3UlZivxvXG9lT3zsKcq
Hsga2uEbaStT2eWpiIZcHN/iGmeIl2jGpcKbwDPvdikeIGx4ADTxIaYoPMYD7k0oj5aH7y1at5tA
ozSLCQQ8Jhb0jdP0oG/Iylw4S1YPcqF5a8kNkGG1PedVu3v3bkNjIwsLy+HDhwHSdilGzgmFjwjS
LOLjQnzImnrdOR7fogZvzkVje+LhLsUbhuhJy9l06AnOGJXDbopDVfGmjEXfDLCTBRNx36f9C5K4
pm3cpInzEfqxCOL6XyqUMoAqtM/D4smqQC4uQ7a8hQT4DxBbUkoqNyenoaHh+IVXC8u1bQAfaijG
VNpg6DrHGGV1lSQH1r9gl6o5Y71ha0v5qHV+3+Rm9nDFQb3F7444dMwMN6Z4Y8AR6zv+KV64ntvc
yl3ba6h8rrmYA6QVyyCtaHCUaycrPplgvFVyBKykqmrk0ZCCa3pEP1Ms5SNTxrVrioFyS3faRmyT
uL0uyhDOWpQzAypUdCnUKeLnK3pjgcequDquNvA6O08/xj7FtSZ36fLguy4gschHj1Z+s2iLjo5e
w2I72ttPnDhxKVYJP9cLJUULQ0klV7JakE2St+bZOAwqtFrTeb7vuqFhSnx8/Nu3g+PjnT097uNl
cUnc3k05+EoPotBrJ81vUBiD3LJ7XaNmlxIhb2mxa5Qz9pBz8b6b+ISpJX8WxqIsQ6zRtxWO8q80
BULc01be0lNV8flwbwkSxroHKrCTlZ9s0N6aFdATzeX+jGwiN0bHxvh4eN4mJLBzcubbIotckN5c
3ngJ4qxHHINmt65C+49lyamK3jfNxTDcqlk12vZJNbLmi1dZ+vA7YN1Y8COFEQtOA29EY3CG9sme
NWmzPutV8XuqkTZu63gg0G9mciZgJifOCSN7QA76GzEb0KI+QjSEG6Zk3fMtIUEAyMHMzCYAfC2k
Yex3x2G/z3CH2noFyBI6HYhJDTq2ugpr7ph6FAA8KFdC4UpddYlvajSm6JzcovNSoyaQRUTZjziU
lOoCFOaglde4y8LV/jhG+VgEAo0W3axYsIAViwfP1Mh1mpaAkovZW03i0mnLxPZRaBH1VQyeClRe
h87dzc8VNFTjP71PmOrCvtZP5pqi6jqXEOXvUJAMDNf+IMiZ3RR6ti/M5TiDq9AyA9ynr2ZmDT0S
MY8433O+Tig1wSPzi0D03Vj1G6w5Jwa6+8fj5M0jHms6WhyfmBjumeW6ps22Jj+5QmjWBBZYWr1e
DFmFyAbxLb3vma1Lp/XdVAixSOPX1BlnyZLndOJkgCNTIOu379S8uX4GJyNWJQ55onmDd244ZcUb
wo+3paztPOgzzx2xIudlg6XIrOjWik8zsMr8MY6gF6SPka0QuOnqefPIoPDgalam45sl308MlBB+
//JgPGCUN9rXlsnp8GtvYIa/Xzyoujqq6TgCogOf6JzmuWNs5bD5z4s8YifFxMFf0+YRVb9tauNo
4ejGwwBqRvo+ckF0y5k6YymQqRsheqZh7OyVd7SYosL2lhnte/FC0iIlcci8xxAX44Hpk0eUf0c5
MDGVWz4MzX+t1HNu6FKvjnrvsMSlhgWDoJMrwnMm1rZB8uEHBF/F92uXDl3k8LRcEqk37L0a/JRe
WrZK1MO6jzn3qG00Devq0SP07oVENLMRRfyIAdmTJjJkE90tVVKAFLUZwPK6ZsRjmSW5qYooIO3u
UljPWxiImKbjPrO3MKtnsc+u+emwAwr0vElwaFRReCwi9t6GdW0uptqQ6Lm2gkniRmAAtoMYcUCH
MbbZeA2sL/fmAukAkORPdSGLiYRNKMzZhMLEFQ1y488lZP73ee46AY97I+8CQHl3f//h/fuHpqcP
srB0wIzLFjMmUgvx9oMdIYlQ2ESsV6zT+k1ikCb/AMFzfa45SLPYuWhtwGvl1vBidroast3Qs3ht
IKKDsdj5Jo7dfS1zJZhtAAcPi/YoBliS/C/MYJP4+wyr55PVhGxo3WImhkFFiMK5FN0dCRvYxiho
dmYmHx9fNf8xSUlp697CifGn2QBXVlpfrwY4Y14qIsZ9Bk2IQAKcGj05g9Lg9rb2IHgNBzWzTCCh
Butpg/MRyZrFqa5rUuuTUc/KU+maCvSBvLW5+JfCwxC3BtmOLTLkYusW63NoFJhQApnjDY9F5alc
DB6qlOyxbI1Do56iEIkFC0qzCzP3KVOXmgv01wdnFqEwgMdAJpoi1jW4I0URBq6o+uddsHlPAn58
AgmkPLZuS15Vc83AyjIEsraiCNhJxNrKwgwKA/DNNTTqn3LjeTBIjWlcI1uMliEXarfI1zAo5Ae1
EHd3d0cnp9evXgGsjZOTEzVQiCN0IYHV4j7rVZs7fAT9laaOM2Y02t1ltT8VYHIXile6b+McPpky
6oXDvvctf1sqw3mlel/Iw9a69joApOllJ6xWHj2/gYNviu8Oiv8FJmdJVnyyMXZrPUUULMCj0JSU
vgkJ5mpq1V+uZ3zSjFVymm5Xfcqq6LpgtDhc2fbpYhTk1lk4PPbFCyZm5lBf3/LZ7oz6+vrKykoG
evq9XAprI9UhCCJB0WNdWFj4gpqamo6OjqamLXAjshihqanJtm9fWnZ2sf0Y7WaYZQTDLK+oGNnU
WIZsarylMvZsaf5+qv0UFFo7GSZLEs4IdD6gvvKW4mFCSfxOn73fBlevCUNeHXawNkhDvXH4+HL3
EQqKW18yszoP3mqQxQw0o19qC8TtO3PrAkoxTmV3KTvdkW+dnT3RGZgBWbYzjyGdN1CoRlnd8zdj
6QoMEbP8JRROBBlyY84lZMjFVaktFUd7lkajOj+BLYeoDnk6odtQYYzF0oYEV2y5aHah6KsIxceK
hFVg3Rd7489raIxMTJgZGYlJStIzMAQFBwcHBExPT7uvLQz5phZnXCq+dYPAs7gWJcTtffWmZ/PX
jXdtMWxAei+zvu6PK4q4UM+1Notww7ehLmoWWdi6Hc9Zf14zrXYmiVswBWHyFS8LmoqSBgQzgvnl
JnKKypLLnbfW/Epuedp/PtwMUDRnzsttbiT1ZnPxjLXbNcd5PMBFlfcWmsAXS3CDMwBqEfG47Hfv
Tl+7Fu7jc0ReHre2OJJt05/nhh4HKLr3xprd2Ejqqw+2ObpKwooYQp1/bCI/UlzEY5/rQseKZnGW
Iv5OwZwsbonGrtqweGPRpaVQ9L0lV22yx3DBxK5NHTdTOb7hq2RPv8iSIQSyWy5Mntq/j+K7fC3L
uVHWfS3dpYG0vK98Vs/vYn4y3bzIDCyn1xwU3zqrXrGPsPNOzEbzHlW5cj7u5Q1LD1TmNcFKD9vk
ucJYh7vJR6j252LK0BuNwKIrGOQke0xMlkyc32InDBzG1siIZ7PNp7KpqemtWx/u378fFhaWnCwC
hbp4em4Az3kzJHwCQ8KVk/RkK7iyZHPerVVLF/Eov5lYK2elCUMs2NkQ66R54mQBbG26ul0/9uZq
waj+ipZ9Y+gDCRQI7qtdSD5M8TqXq2DR+P62rzRHLWM+Rnu6THaEOOim6l69amFpmZGezsHJqRkj
iQUP2BE2jMEa6XdKsEYa+1bOhqz85CKz2Fbfqep2YzGRUTFfU1xLgBxpuUfNiQ0MvB+wSzT45GaZ
awov9TGTdf5wFxhxvmC1xRHnkBLGONYJE1HCEMpwsbopyIbGxrCICDMTk6+ZmTfTjEpnusC5GJsV
rH07wLrPe31parKCk4nFW2sCM1t6es+pI/QU3/cEWO0SHixlsDrqCpcUMaH54CpeMjixNugxcWi/
XdOO+xjvpsTPKi+1z1TcsEQVZoY77D3yUnt14E5Wp8k4sHZHBuia0ZqxwMM1v8SaQFZGcgF2a713
ehbWosY3IdGPy9sLYAm7MEUJtp49TisjidmwWWdFTXns6vwEMlbJi3bv3ju3bt0yMtpNS5tnP1YH
8InzTYVmhgSx2YWkem7EigGxInfp3VjwBFhaWCDorg11XcqHH/JAozvj4Tq2iPmC9XRcT3yKZax7
KiLSHi2xGa6owXD1o1EziaxmZGLv1rrSruNxGB9KmoKCArD9DAdHY0PDteQbgFqp7cy2brpKt/VW
TzmufPjSZpvquZY536Jb/6ZZSlrpjSMaHYeBoZsKRgwWtezwoY80uAc2Nuo3FwrV5kDEQWGyZ3Fk
yUVWsa0VFACWk2nZZW9v7/fwIQcHR0d7u5ycnCEQhmZxseFC3GHSYKOZU+YrH9LKU/cWE+zm+0Mm
P6TKAuv+Ji5hcja/zRZxKRerbonWWZQK0b5UkLu0yAY+XGVa8OEmt0LI9g6SJRdJtygx4DyFHpgT
QkJ/ze14+fLl3bt354GEY6qrWBVTdNDWownw1MlItctqA4fc8ehKDIw5BdHes3HFuf/DbBtqb9E6
5K9Rase6FAJghPH2/NhNKiYIUrGPWuLzZCSWFCMXEsW2th6AZxzECa2rrw97+ZKdnb29vX16ZgbV
n49ZqkaqQ2EzNl5VoMTTasb+cJTXIn4+AtnBNlD/xetY9rx605QLznDjldNERvfqxAtL7srDHg7D
jc3AU9jMrxwpwPxKcq/UHbJSkwtyW6u4bmDR3yzaANYLPOOc3NzQ0FBbZBEejSpuDCnu3pyN4rM6
buaA8vYizGnWh4VoW3Kln0QMfsUAXoiEKmLv5I7IopdoWOVjUj028Mi/2brUJltPFDtBVlpyKe3W
dniuYzHIECDn3MARMUgiQFkpS8f5kZnSMGD18kx+n9GPRYjmYK56tbUFJ3GHFGKN82dkgQgzxY8c
wG/gVma6vL29v3z5Qk9PHxgYePnyZRfUgBd+BJxvJFzPTc3tDnpvYraSQ7InOIa+Rw1p47n+xnUj
uTGFzcOQQmQDM4OCbVYuD4LLXuOWngxZBcmEUomtLaKe1Q1cFT9SWhFbNFWb3ah5fxZFN+/12mui
/os8/E4foWCW0AUFYpAHVtkMrQPkGQWY4jzCVBcQmqSgism5a0MVUdyr+XAxEY9n9ktzABdDFnp0
/fgBrMdJFMrW1JSPh6cE+FNXF/n8+eL6yowujPAyFgGwS+Oad7pdMEKk84wE8G3He2OS3ZZXVieQ
FvzIG3Oe6WgsRgTINj02nMpHbDm5EDdxk1FEH7AUd8LW9fM3whPs6gQbbCNveShiMcvMOd/QgLCg
YVufEd2GOlmAm0pH8QGrpKV6YGBtGdeVCgcYoJzX+vJrCbO8/HwpSck1LDYpKakYsOhyb+yDDNSr
CFig0rr7UmMzsLJsvZdEFtf0o96IrhasNQFAyQXWjYdf5JJr/ywpRoYIbI3xrS+OVL/g0wBWB/um
M4yMjKTCiwlACqqc6u0KJIJ/lU91bL28F/GaXZkhw5Zc1+dci1amMOWp3gARTswe637vASf8Hfe/
b8K59yURI7Jykon7W2tdA55vAdJ8bzyOiG8uXtZBUekqgtHm9soH31TvgjVCtQWGLnyM0TFbQR43
P/EQA2vMhpndWOVZXpip5/Z+yO3dmD7sgyHoAgYzAZmV+ebbZ67rEtJkBf0n+EvLSPL88vGvkZOc
0CTf/nv497+1+PZS0aFXjP6RC5HWkdeDRSNg3STjeFdqXJf51Jjcd/Gbgs8rY451TSDgD569kbke
+Y5OdZhnsJTumRbiemHqDO2B9t4w8fd1dAxM0zNX9Q4a7BWiLihSyw7sexEKf+8n7RYwMMr7QVBI
KpJJ8OPLg+UV1p/FfhzGdcrLy7K7NiloHojqpxmE7akQ5nkvqfqoVDuMrdl8wKD13HOW8/sl4q6E
CErF+T1TGz/LLp1XG4SY7XOLefqSgXnhwdxqG70ljTxnUFSOHNeZK/R5O4K9YQ9g9C17fftlfzju
l72oalgb8BX5cLKxD31mdLam7RnD3v6+sj65e21WXV7QTHlow2B2AVPk5cFPKzc34u10b3t/Ovvi
7hEJU4I/V03nbHXL80NX0PS8gpB8wcf2Ktaf8Osx0QdjzPf3UGcwzo7KbNjriqaxvdDVUZsUzqNN
vFfU1PD6xivb6d7mezORLY3Os661wu9nTnXozeqoZ5qPjxjvndtd2NdNQ5Pe+eLiMgfxHq846/EH
B0+onlxh3us0XvOk3P916VsOUwETthG3UfUAyq/OyXPZRrUWviq+IZSd1KGfak/oFT+JL5HAryo7
xuQ5oYaDKyqiPgV8VWG4+qk+41F7Y+DjLG8q+UMRdU5W+xzsejEy03Tpx8ue2S/IrOpodFLekDge
Hn1j9HiyQJxsnELhzpXeeF18haPxewTt5SPmk/rm0ZevBp+vpDpC1Wj6ZG+p6PzeiBRYWWNJ/nV1
ld6eeyFZuCJY0Qf2pYdHNdlFZQyf4DcaTzSXZ78dZB//9PmH7o5YKk+MXTCt9JcRs2WGrtNtNO3f
PL/IVIkkDLa+mlUt7boZrVEe2V1tOxkWsD+8gvuwc/b7qctW3/Cwc/tP6qUrJGqze8Yf+55Cb0l7
gv6VYNpg/8ODud7tE58M8SxGFBVJ1vUM/+kU/1m11gL3xjMAf9mD29+BzOOvY80MotqmDrZO9rdM
HXik/v5E2dbGEfglBx7pvz84bWNjC1zq8/y1j/yvU95/3X8T+PFF09sWxmdsXYFfAOmJFJAxyADk
G/yRsr3tPfI/0bbdLKGL/atA/kvkBf6vPKDnXtVW5xGwNgb811bO2tjewtHc9OQtY3srC1P7U6aO
DhYnbe3NBEV1/vpF8Kv+1ndTZrAs/8/pgAsWNpab6t5yBMQB4UEKKs0jCUCvlIzMX8L+LabY5tUZ
W/vbAGT8+tE5HlHNf8kr8f9fXjNTG1NnC1Nn05NmpoCYpg6/I7EUBLIpsZTE70gs+QclhgICS0vy
QKTFNwX/3wks9avAWva2t3RMwe8W1VI5yyN6xdTV8e9zH8p//62++TVngSW8qdyVK+JgmeDvATFX
rkiCV5B/rqTBK/F/riBiPH9tefsrFPw8YQJ+j7o1BCrB8/cZEfBCkkeGdCHFI0u6kObZbDP79xWU
5+/+UgyblzI8EHHSD2V5IBI/r2TEeP7pNQBeQXj+GWsDXgFaSJO+RkaCB0KSBQh7EJIwMlI8EJI0
MtI84iRpZKA84r9IA6wicZI0QFIvTpJGVoxHnCSNLIRHnCSNrDiP+C/SAC4kTpIGABZxkjSAx4uT
pAEyVwmSNEBuK/GLNED+KEGSBsgPJH5KIw7kPRKSpCsIj4QU6UqcR4IkjTjAbiWgpB9K8kjIkK6k
eCRkSVfSPJJipCsojyTkl6+R4ZEUJ/1QlkeSJA1gX0mSNIB9JUnSAOaV/EUawL6SJGkA+0qSpAHs
K0mSBrCvFEkawLxSv0gD2FeKJA1gXymSNIB9pUjSAPaVIkkDmFfqF2kA+0qRpAHsK0WSBrCvFEka
wL7SJGkA80r/Ig1gX2mSNIB9pUnSAPaVJkkD2FeaJA1gXulfpAHsK02SBrCvNEkawL7SJGkA+0JJ
0gDmhf4iDWBfKEkawL5QkjSAfaEkaQD7QknSAOaF/iINYF8oSRrAvlCSNIB9oSRpAPvKkKQBzCvz
izSAfWVI0gD2lSFJA9hXhiQNYF8ZkjSAeWV+kQawrwxJGsC+MiRpAPvKkKQB7CtLkgYwr+wv0gD2
lSVJA9hXliQNYF9ZkjSAfWVJ0gDmlf1FGsC+siRpAPvKkqQB7CtLkkZaenM45M9LAP7EfpEHsDBE
jCQQYGKIGEkiwMY/JxGClxCen/PrwEvxzVLHz+8CzPxzeDZ4Kcnzc/Q7eCnF83NsOngJQj1Jrk1Y
/kUuEJdJwAwORYaQkBmcEAwhQTM4GxdCwmZwrCzkF3AG56tCSOgMDhyFkOAZnNUJIeEzOK0SQgJo
cNIj5BeEBuckQkgQDc4LhJAwGhy3ByGBNDh7DkJCaXDwGuQXmAbnh0FIOA0O04KQgBqcKQUhITU4
cwlCgmpwZhHkF6wGB/dASGANjr+BkNAaHAkDIcE1OCAFQsJrcKYI5BfABsdzQEiIDQ6sgJAgG5z4
ACFhNlimgJBAG5wuAPkFtcFW+xASbINN6yEk3Abbv0NIwA32ToeQkBvsJA75BbrB3tsQEnaDfagh
JPAG+zRDSOgN9jKGkOAb7AsM+QW/wU65EBKAgz1nISQEB5uvQkgQDjYjhZAwHGzmCfkFxMGWmBAS
ioNNIyEkGAe7L0JIOA42MYSQgBzs9gf5BcnBPngQEpSDDeUgJCwHW7NBSGAOdiyDkNAcbP0F+QXO
waZZEBKeg+2mICRABzs1QUiIDnYygpAgHewIBPkF08FmOBASqIM9YiAkVAf7rUBIsA72LoGQcB3s
+gH5BdjBRhgQErKDLSMgJGgHGy9ASNgOtiKAkMAdPNQP+QXdwePxEBK8gwfNITK/MEbS1iCQM6rp
gAv/72/b/PkvJ47BX1B2kPrl5LGygzRIQCV/XgEs55/HDVyBLEf65xVAcv6+jwG8BFjOP88auAJY
zj+PGrgCONc/Txq4AjjX3w8avAIo19+PefNrAM71z2NWdgBukoD+lAa4SQL6UxrgJgnoT2mgIOUi
SQPcJAH9KQ1wkwT0pzTATf88EfAKkEbmpzTAPRIyJGmAmyRkfkoD3CQh81Ma4CYJmZ/SADdJyPyU
BrhHQoYkjQzIAH9KA9wkIfNTGuAmCdmf0gA3Scj+lAa4R0KWJA1wk4TsT2mAmyRkf0oD3CQh+1Ma
4CYJ2Z/SAPdIyJKkAW6SkP0pjSzIR39KIwvy0Z/SADdJiv2UBrhHUowkDXCTpNhPacCIKykmSboE
GKmYFOkSoKRi0qRLCR5JMZJEYMSVFJMh/RhgpWKypEtAKIgY6RJkyRDSJSAWRPyX7wLkgpDkAony
34ETXP+/pHVkXtjJQrf2OvRjhIYtpxrTfdQGS2G2cdpBDC5d1jq6JGqXp5gKD80tRt67wpB35x5+
DFuBNRGeJk/bNEl6fKpRNlI+qA3vas//jIDvzjKmE+k1ej0Rrj50Y777jVTyy9nvot7Y4DlWlFIf
3aqjwUaRVspKYDnM59X3z5kH905fs0/5sW66OD/BNnQAZ1e85pdj/UZ4rWSxy6/rQKrb0+GrQrd9
OLUL7oZFL4UPlx70ca4Pn3ngQpl642Ykp0JM7IL3IEPeh2epPfcVaDCsnjyjGie1D510a1bHvt81
YrA7GbNLlNowK+8A4+k3rS9enFR+WuY181TPTXWPS3Jkqf/3vM4f+zE7kGMPKP1Zvx1xskuOGRKJ
u2AeFD2sbBRUUUJfkKWe9zCCdW1f173X0s+KWuZYuM6NlaK8y2guCYiqWJotHPl8VlMKOtj/IAwq
mboA+bR+9PyZ6VcQlhTByqszZi85HtylN2Hulzpw2ocRwrLxvuvUVbXsKzm8TtUn3izdSqe1Yn24
6kzLeEQqJSyu9+J55wQkpPtd3GWb5s+6OTxXq6nFxvgS3a16mA37vxs+eLmzC/ot9Z6yhWha6QW3
z9ce2lYGSisbJFfLXHrJZqTt4/HZzNcVVkkZd+GUZkfOIPTlkNEZHzptDqtzOoZMPae4EjgMLvdM
/jB7m20PH4xsr6o6boB+1Hr2m8SyXgqXF+Qy9RVhe+0c7LGMHWdXX3K9p7VreXjSsMovdfGUaVqF
+rWWF6HepdTSY4nptEFnNcOeLz26JRz4dqdu12Gdlsh93s4XHkbNBCeae9RDWFAC1QnX+5D3An0E
tQeVtUQnTtfhI68pa71rv+3jwZJ/Ieip29BOaYgBz12DFzEtgjQnDPdvDEYGxJe5OzMEo3byA39f
VGU0DiOY7I29qTM0ykp/y/tsXvyLU/HHdYZ8EqxyLr9F2o0GfjtOPdP9PYCLbsX+Ut59fSRVvG8k
ffK9uzseiTQ3nuvqYni4UzjyUdH+loAsKPC53HvxpteR/MqRIskLnEcqAw5alD/5mmW3kmgBQUVk
vGNRVDlAnSB4j/2jDXX8Z8cFjUodXOq3nLvt33LnWXOGWA+X6B3d8VX/RE//ufu08REfrcwrdfS1
pZdfZG18fvf2xYmD9/mORjIkT6WfxVaeiGJItpN7f3TeRUoz+Vx368FiLu2Jd9fZlleedX7LN7Z4
2HakMfyaAoc2W8QqrQvUhFYia5Ji/uwFIfcvrfcpzaPVTOoG6M0rQ/kiG78scO7ITPNlkWTRCr2t
+y3/zp3K4KTne9mS8EZmToPuzU7UfoHf4qvMrxW8r+6vydr1RrchMhyNV/BzVf5s4dT2fZoil4NP
meW23mmdW5KcN1pGWM4OItU0nLTjyp4INXS3BhQdbp0u2aedI3xz1qL7yh65YFd2E9qIHnRa6Ctz
jurnuoO3ntTR6TMzZDPouypqJe03yHw/L6UZLlidvNuV0dK2lPGyU85ezUrdtX3X9E7gL1zvUnB7
Lps0Mgi4KbQ98R5C400AY3Z7ejJX/ovh9l1O3+OHn9B9HszxoLQxqmHLOeY+et39YVt643D6DdqY
6EStUpNH0Jerrmo7D9kK7rpU6bwPvji65BEeYp08WF36Oen246uyQ09KT+QEOfSWxR+99iDYmhW+
+OAKrBaaw3Wg4FhHts6rnNbdVyrWlgI++x3fNfPxXGWoMUPLpZE6j3dM4QdSTV7djdlrGW5bP/OK
6ZYew4AGHVb8jl2jjnFjY++rpb1UK2c+i5o86VK4+tXtCDSvQENAHTMiXDScWPIpKvny2M7UYxw9
ktePK7DcqKEKqquxt7z2gl4Ek5N/wVXtCdS1j+NyyufzL3bV3zzUIKV5trNS4/3QWEDCgXgmmvVq
+kudQt/4Fxhmd1Zyxb88FidkcPC4QnfgUNXT/KzVsfWPL4+PPb0+8GzpXfKD3J5wjafa4c9EjYSW
dKK/3NjTpDLwUiNY+0pHgNGtk+2ePPanS25XXWkTS3tqbnEi5+ikMzXbS9ecDGOOMvGrwjfP67Sw
pPkZsyViIXmrJpUHnn3+QZUp3HUyTqrSg83DvjGkZYVN4+199A/JTAGMQFz1ZJ59NhvXarjgnIDl
1ccXL6LtRbQjC8ruLLLE3MJZLJbfXbTJfHEhrSPiYc0djeMimnyUUaIx+qW5GLXyzupz95wNRAe8
cthmp3IGrTKruBHCB7MM8AFLVuE0MTVHR0J98qQGIyk+dx9jOcGFcsDGq+a6HIrPUk1sLF6N9/ZQ
eNpxXZi7YukYKxNXl2NOx+Qx6drvArxKdQkD1c4dXzH9xvlTl4c1hQoupzHo0zMt3Kl5638mtnLo
WPc7+EaZ8+SnWn1jDFOErYiCXY3omqTLFY/Z8Bx3d4QzZQIntdM7KZ9nzQwnWfBMNsGNeYjreZ3S
jBoLV32Re1z9H9m+xd/L3WieRtJ1UwsnybeUSdWmd4SofzlUaPTBJrVfp/lYL8K49V3kM6TgrWFK
A2exftOB/e+vyw47faz2VPd/y2Syp+w1/ZVHZt1lH7UP5hw1Xbv+evml5kLB4738b6tNTyryNeUV
NDabsWrODJ6APTFXv5TeGFzZLWEWIWUsZnW898m3BrNMjfy+t+vT+RqqVs8Ee5ImGp8rzkcMvrmD
X4kLYcxn1h/oHl9JQ/QqVNmu39q4Qym7L/LmxnQ9YaH1jTTusC+x2jsqOEUTz+tBjR6Ot67bz3Dz
9LuJk62UMUYS6ndV4NExQ88s3J2LEUGazRrnjrRZya0291ug85DDOC8Hg4HT8rvKrdoOr6dU+nc4
hBQbMu65zv8xxKRpwwGTRQ8JXdRndcqXF9K9vXDzTVm3LqNX8S3zAvP1eLxF25twrkpF8YVd5siM
2GsLXd/7iPR83+Zi8yapfWgFKK5ne9yG4TGZsI++2Blpi7JQ2hMsl1nsDKehnNoclrIPv5n1T7Un
x+pMalN130JMSz9z1HqQ6k/QQEyWxvezFmZdWkQq2ojFLGJr8pRpY6wY5g08lxsWzubwVkDPdhU7
9TbyFsjI7Qwd299Qnf1GO8DY+bSJoufNyPEKwzzb2Xewap7iD46nToavHRWyD/f0WmMpm4n0Zkjt
zlhxyPbY6eTUlj1LcCNKKdlyd2fjdbNmPozJ0cjZ+Pccl1eCiuKUGWWhxxaR3TNZqKOI2euOjx/J
TQ6qysppmeg1f1cr+O4e2SBWZE+hxNUbcrMhnfJOjLl0/AQxjmNfaIamxZsNOrxcMGUQ5nRzYDlX
jcIX0Rc7xodl1sR7W4w/WsgM+t+Ip46SVWso0ws58VUx4VFhYdbeTkXzCV+7M8FP1iCNKlo/HstM
ZKTc4y9dz/1sOa1RVXZWtN5CsOpo/ZtB5eIZpDSiaGWWMkdLCk+4fyS81lJvo9vS7DkrFMJ9zykn
xfd+MK2QQ2KFQXHKCdReqIhQ/IrL5dTGbqm37yW+bOwRty4xP/hj3Kjy+z0dqbdJj4V6r3ebHEw0
PphoV8c+NVQehOdzRzugy72JvXcwy4wCZ84VHRjKfSik8Ug/VpSmUewWVbH0bfqI8j5LgrNsOM9e
n4mDry/0srIlv38TKDvosLdPGe1XxinZrL0YcMTRTnLsgi8DjVpTljvz7Pm+N9VNr8xzqfJ45avo
e8s3HjCm4pYXc9x+rCJ1U/dOHlV8vH5r+qP8a/ryj7u1WMyx8MWAkHeuSOvsjppY19M/6ui+c+D6
F4Ukc+YZbnhj0rptLiGLYs1njSjk4XcNjhHhLV56LmW5vM7Fpcf8HMRsfC2/JygjZhltNfpyIm3c
+A/OltkxlHQvWmMRnUnW2c9HHhehdOlXn9A6P5mPKZLTPD2scJy64L5xiSiv/TGIhv3jI5nB3rzw
6M9yHRK8N164vClZuBvglSrnNP3SNA6iEGyyF3oBmQR3K6Td93miev47wvzVKLMg8/Ge50YZXZmN
QU5ttPRwrshajZmk3Tr+rA8E6b7VUL5fGkNSp9hVD7UqaHsZcfE/5RBMPol3nczOv6R3nr34pqKF
aVL+Sc+Ng4v4M6qz3v0GVfN0lWk6rfI2MY+TooI1P75IRx5elA9LKFdXyh9pE4UiYuxNA1LiHqsS
iSEpUak2y9MI5OVTU3e40dPJ0VdTsypNv4wYFbCJXGiWHZjTespH15H95cteVBTchUnuANX5TnTa
6d3nTKzGdF/XTGIt2LMbI7wVMsTjnl0WvyCnLIq2F6NPxL/tK2nqf1qdOZ32uf8uPdUtYfdYlXvm
DepmGwu6l11d+oujDs8wj8OXauhzx81a+aIuzXfMNSv7rrynVNdZuoB9NwXjErCLssmv3IHH9onG
Dyt+pGDDSu/y56aYapLNHut7/+bqKy/ikwrBCS6GIPhb5JCcu8FTfG3UVdgLdwMi9Y3WqOQnxLil
jcvRQ9OnJYJ2fnh9Nq9C66o+XqXpbV3FubTZUP10aj1f9lhsVjv3oco8sz388MPH36hG2DjGMhxH
xHgeKZbmzTq4t/GckRzzPjX75ifeF5KGciqP7WwZ28Hc/ONs1vy8Gutr8bFFP6/gxjnmAk//XSOe
rH6TTq9dg/ZJhzgyP1m/fPqHwkq/AHubTxuFp5jClFKr8tXFEA59YevVfHSc9EHRGn+o7xpLzyN7
d2s0d7u09YkriXDd27MxH8cWcqYwHj5zLrpOi6ZhrS+UrJBXoC9ViTrpaJ13RXnNctkH6iy/6Kwf
T9rwv1bLp41rnxVX9Xz14mJI/Yz5RcN5pjBVB+2v9g+uNr+Kb4g7ae4XbPHxmlbHXJa2Ge/Sgxyn
Ng2MpNFG8NTT88eeUyDN2mq9Mz6kCvZfftrbeXzH42TdunWxR5MTRTCIanDmAW0ebXv4w429V20+
VOTQsLlEUnvGpxfzq4TkDO5XcM+ZU6uU+T6tk7HhcjaJ/2ts6d2u0kKqzogdHa13mFaQO4TsJ7iJ
G8uFn0JSXB5GHVBzP/ux66hmCqOw25uUJv1vUdcyO1waGdtzmbqey0ylPiZUe/Ne2H+NzfF9f46y
mbuFs5lhi+NH59xrEByUptVC6w60T26fVUKlH9KXVvIE69V3iz/uKdvBFQc8b++vavcLKjq+u73F
b+P8AcPFQpErpcWf9uQ9arMzEiw5P+ij9C0B9Vqtmf+87+4O0RDe2SG3J3Rz1KoG76D8u0SNjVcJ
MpITNC3xDzs+OY36Y8IsZEtUlESZPrt1nqjRvKAKx58eyGQgQt3aM+cyqNGYvimDfOd5hoHMzhPV
GzLRXM430REfBoe/yjNc0Yq0mZW3E8jUzPZKLWtMQ2bh2RKkJnPw94aZTDNO2H++Cn09qPw1OALK
mI+jabLoLio/+Cn9zK4Lq8w/VC8H4ox59We+KUrJ77zCfwKZWjXkOhlyZU5JcXDfshPz8dTCqqDe
bNegEPd6y4y3ktJUa6jvLi/lPxrxCjnXatk0TyI6hX1O1no7RH96Tdi9PllXfniFUjGRqSXM48H1
42YlD79cdBsS0PqIsOEWfdnSmMhsmzAzEuBVylnTot+ZfKv6xhv9BP4Gq6zD5QrXcPQzymjR96hb
sCC+wMWUVPe2l7ZLn0TGRGyPxqFftl7Dpefbnco8KuboUTMjwSa15CuGxMIa50ZsisfydVxcC2BJ
6ydmnnlao48r7YJXPBH9aPZY6LMo42DzfjFPBZtTYf6cKRf86ujWlq+5agmoVFX3ePcoSEzGDLLr
xibKXi8ehx31s0XDL9m+X9zFwu/xnT35I6+B1ZOIqPL8CyVPTcLvEE/qsEPOOVR87Jl/PwLDuTxs
Yn1afW699gpW+fhz2qiPiKNRXL03ipJf8ZW/DEqwUrluaWpv4HGIWbEhUMP1ukZgw6eJ94J3Gkwe
7Q7NCL0gaimoU9EaxsUpy5jhZH+hNYwjYjeH0MhS+9cNQ33+T0+cauz6X1wtHerOi2NPLpen9TRS
5HoD6Uj0F+uSyRGtejg1naV34oHxALud1lNfv9zhfbQJajxH4U/K+qtkL9y+Ac2X43e7lsR7XXhg
bF4TdUdlj1byETmjXcx6ZYdqPkUfbSuLChf0C2eOjn5l0zhBpfKqkac678txuPhLp8W8VyfVJ7uM
TVzFFYerjnv4zrJ3OF/6VJ9WezT5zCPKL+qeArZcEC4qzdsjn6qeltd0GrvWT7EbDI8d/bTr9s4C
Mwb6km88BRVVPzopltQl3lK079IX7GGaMb3vE+tnxdqGThgR2cU5fJfRjOlgzUWrowwcVgdoPOsq
Enp3U/8IjEx9L8vcuV/rxsDx8iDJOq1zh87K+g7FMpx5S3GMmePgbcHXybHc5R/WlwKD3ss1jkRr
4Zv3Xdjjsecbu56hukaJ6bPRMioaY6psHrY4xg97Jn1iFJ7TySt9rHXba3QiT7rkWx5zdcyp2Qmx
ZxzP0qJ33s6VmRB9nXw2zUjy7niGRo1KTkcgs6iYPLU69DrnsEQbRcnbGIE+9Tv6omFsH3yUxYv5
KfotDrNdizHq+GzGqqD/XHNiNxv794Pyig0U4zntRy87mF9aFZZ9eSO6XHByVxHEknC+4Ov4TjNE
tM7DOZlQuqi3GedZrMM1es9TR8u+nM85/oYPOy2pluyjfMikRuWYj4VQl4Ci8GR5rmywOEKdW/Ut
m/ZDS2racMejShXzElH3k0rYJeWvtY1xRFl5+PGI7jmbmx+ZYv8YLkrLavbipYCIl5WloN/U4Mpb
C3O+tdt5Bwfk9PcIXrKs3e19o055t662SeiVCzZZL44HNjVYFgsEqhq/2SWZLlDKg9h97Gyp3v3X
nY1aF8+GMpy6RP06Ibxy5dmOiuCz8QeNWnJ2Xc867y7y7EZuRpitne1+bOmdGTOulTpX1i9SjJ9f
v9Tj4+ypfEZx+gJN60P/QNfHP06aO10qe3hNROja0/MiXbX3HE+6OrSYcWCD3eSUotaPPTn8Ooz7
q/4rIy7x+K/HskXeUlEHNTLPSXwcHmait71U5O6Vsv5VYdoxkU+hv+KGh5Nbo4jd2Ue2P2xirRlb
KGhqrGSFpgz3qpkqXg+nLhK1+VTufX6vcHC9y0WoXcZpmcaF0he1tQ0B8dFmjM892lr9mt6cKc3U
cNbmG0e3vpR4Gt61U1OPwbjCqfehe0qIYEprctdu/XMiSbsZd1a+fTJyH7OrUrPudGjD3fTHh/hr
ecMKvvBa3jC1uv3tLctLiw9rOm46kleozwtQmmrLs971t24qY7cLsVAY3nPh0lGs5ZevsWtneTnK
GxKMj0zJLhxvuvhkcs9QQ1Zkj1vO+e9nzp89Paq1dEBlzyGLOxtyxe0BHFKI96iy6yI9ZzSeXMNq
a2g8UBHQSXxwVuySxvUSex1V+9NSYpkn665K6be3B/tdHPlk88mGdcSAjTlHptNA50mit8Z73t3Q
KtGB8y2xA9OlAydoxLhCDQ0dCjtDal2sVw4ffNBjcaVR7OnEsczkFFOD1ps6mTrRK7b9UUbRd5eq
FW7FWOOs+njNGhtMTpkZvjikqGqKvz1jJ2J0+YQcXkL2pPDkaE6OQr9u846rtV3vY56p79jNx1ep
43fr9pjx3rOv3mQniHoalaWloizxV+zWCE2ijCoW/HsFMhfqrDM+o4dZV9Lf0i1cZdUrcMpT13fL
ukaRm5X4MQrf6vyF+sTTRUPWyjMams50wU95qmWeXH565v2Jm3idhzlBT3PVc72Ocs7dCm+5oJ6h
Zdp6RU3SNf1agV7UsaQW7EXi6QlI/i4LScaV8dKjMVef5Wd+hQROHd47rFP9Xi8ZcWddJtUqE7G8
c5Fof1NElnVOwGogyVUopw52W1ExpaW3uP3+xTKLjo9fRmMWpM4OGUaMshhXjzCh31q275UST1Ny
fIQ/U9BaCsF/3uU/d1JjzFLp4wr7VEeVXVVHIs+8GCI6xJsTghRzrSKoTq/k8662jkWai1EeeMS7
2j2XGrzPRO+k2qTsxzsv6Z6YPH9BFXF1QiC90To66LmVgEuuhPhc9RP8u8Orcjc4lp2QmgnZLg4e
mshUGRx7YFbflOriySuil4mXhqlvRfXNUDavGQw0X4ytab5ovrBf59BdsW6jmxHCx2ZnWs9VV8TL
aV3p7qU03p1YXEUzv5IrjERxGXBp3ardabWvS4lYkkGQmQsqy8tNQzseOcd/rqXgyVsOWSm/Vwr3
FhV1XdQYXiRynajkLeo8NGBd1+N05aT+d+iHimoRTurUQwdHWO6UhWrFwLuWnhpf36OqXK4hHNTh
YCwjDMeOhI2l33ggtarrN9hU+WBfk8oXWo9DLodoDq057ZndY14sNPP4lnn34GU9WNcMZ2uFPE8Z
N3fUObXQwPreW+vuTgjr4tPvLAXPmXn65tXSCD66/HgPo9vlwABpgUR5hc+0dTdV6TUa+C+gvLX3
4dwuH1kZfVvocnNRprwiW1O6zak49Dw9einx41OOh/O+oyzVlfxNveevXvoB11KM0w0/XRNip8Ne
wQXH2EdhEzmC0b1H7ORcvR8dfCjMoRvu6Pjdj4nxnKyxq1zfQq//kyDePYqZYskp3tHsdzRavQ47
CXnb3n5mtzITHzdyRHSWM2dCZgNpczdDPECk+dIMIkSnoRWda9MetVd94cGDxxZuJ/G2UA/YwWsc
Eq09nOLUyBZliW6VFthqvElNpTndBFGcK93Ymiop06/jUb6PW1g0/1Fon7wfHZffoIpZva2XMRw5
owhzvgX1GjfLWUplO3jKxM3vJSJEuQ7eu1tzmSY1dtBp8PoZClHzVCaGoU72hhg1DqxJWvILQyvK
qrpr73LuflFneB4mGr2jV+f2nuzl9JnI4uVDjDI7v77vXSOsDWtqS4/WM8xUMrkesXGJOFaEG1Ax
mmbLut3HbxXkM7dbv9iuuGDl5eeMHQH5Vekr8cPhUGohwiSy/NITQsreLpqb8wJrP6y929w4GGP4
TTJis2/f9YwKNtA4dbhZW+yL23G4JwcmjJfStPxsfoFkSHulCNdk+9pi6XPWB6/qAlzY08bmGBdN
PCg/GD0V5HXr4n2uuPpq8aFEyAe9JzaS6yuXgBUbjpgLOFIeYHq2kw0uhT46UvpizCpRKPrs+WMD
zm1jKuHQoZecLqpHQ5wov3K6utyDX9VDfmw1k+mK7jOV97rcLWRvbynA91DJkHO3AYJW8erakcnL
sRDjnRXtiewCBzRpMa7TV4YsNA8IGFx3ZJuXZz/IR7U+LHHl4qU5+hdnXjFSCt09nTxRxef4aGcj
IndY2f9eHQvS52Akz7zz44N4LZ+6x2bUDx98fGX96TKP0Oije4Eaz+1cbZZx7oWfmju7OsVbqhhC
Tx+Z8V5op/MQS2qz/3DOvHhxKTp1oQclXhV7pM+Zdt8My4G4Bz6Rh7+U+dyZ/fJlf6HsYvmF97Q4
17bTcuHUTEWO+5bOlqjRDt6vC1kI5pbE038zNF58dvdFVVUMk6bW09YCfTmumiSDOPceE9EDZjbn
7gg+Gz7jS8uqUzbHW/nWI/leCn97NuOS/jTuHupBIZ/7p7K3A4Z7nANv2Pi35qqovz104JD2MV7E
kedxxplRjhnvCKuKcQevK4hEo/ZUXclXlahdGTb9fk2iiyi8cZ4vKcPiE+zLPkZRjBPDwdybtwUP
teQIvQmQeFA2mDoGZ/rae675UPPnnn1mzpmEmr2syqpW0lG5SWLmg6cfmip+feWP/5iccI7LSdL/
YfTUxXRIfxDFrCOe6bB5RtDzvTTwXXv6qW8Y3qAVyl/7BsV9GdPxcEuu7mv/EftcPzXuiCDD0oNQ
9dkXr/epO39+5Ul1/eYX4bf3vp2uOuTs+HQ39WU9XnPXD/3H389BMtb3pZ682GHOfg9XFvGmKuJ1
XpXWoZDAokym6ImY81/bHvm5nik4fsCdlrVP19XG3fGHY+0kBXYDxhDbn/CkLa24wkz+/DGuw495
LVXeTczzZJgRqoSkVTmfOzjL1s9dlXHVXdDRgxi9dN0/M0R1o2DGLQJOGFvtrxgwqI3a0cKRptwt
Qj/bhic2iZ07sYfhx9k9LneqYqN1regNwruiF/mku/uya9/f/9EVV/hIJd68CmN5KnnvvO/dovRm
+3gCvfuiyPwb5o6MQsIUlmldwmtZINBAxufQuB37HlFxxbYcWVbh2mBqOhPKo2uNY4/KniQsRqRY
hWQ/9IKa19U+9+X5fPPHi2Mf8HRFlvO9776Kv7imJx5dvDhUpXxN/r4DnxyVw2d1a4W9WWf19nRy
e++pFmGIeKZZLVodcppj6mLSMWJgsyWDkW1qCEd/1UDU4GNniaE0XoEvjhI+iXpi3pfjXx1oN7ni
MAMjEjCwTOdQlbe3+kVO7Fa/vpzjmfpq6oy4hBXVbfsmFtfMsJpBnrKQ9Jlr8KJDzDdCIl+UpWue
Lv+hceKKT5o6vf6eyH2835gO1Aj4hnu/C7bvO8SIHZZeapaP7Egbu2rSlZBFI3nuYInvzNB1a+4f
6LHp7pd67sJ7hYrHhNRCd1sAQfKT/71X7PMyxZh4tXcVKw8FsnL2ygyvPj90ZdTFvosOVtVVLaG9
O8FV8YzYR8RQQXYXdMdRQViHlGKGmYeVavk8R+ajs728MWrcJ+4kP5FNuccsC1XQu/f6SPWLt67C
ww9n7KziXhlVpnLG9OzVy9K7JD321djBE5Ogn+Tsm7T/xjvBeZ+k8gC4cuYc69TyErTBEW7Ah0zd
z4I6Xt7aOiO1sXrp4quYq4+eeCNTIcIieTtnpmwuB/buubgYfOiKjP5BOzXh40NVi8EH8iQU6xh6
R+n4mmk4hu4UeDN5i2LCIVnAAqRKUz15NKPYJ4O6a4TJQmKnq0+Ra/+3lOiEseWPRd8OTXLNVpyj
pz/HbDbga52/TMy4SYXx4goTeLGSxeo1TTF7+5xB3OE+0fcay4e93hpJ4l68xY9+uG0Hi5R5Y061
0cQTLhhjLyBYsbYUgSnTmxXTEOs1YdDXwkTr0UL0FBYDTjzqrdBtrjOvn6htUUq7dapWmfkNuy7/
mUPBl8SyzviYnfE12HNZkFsffu4p4tGJmhqPl9MXjOP0eONYY4IXd+sZHw6JlV0KYtnTFSUebzT8
/Eziez7nUGZPecFl6U8qIYV0EZyiDkosMetrd/tieZji7FCqse+u8RhHlh/dY98cWL8yJRAdHtYg
kABlvnn/zBgKPXI6yndl13vxfSzKTVSlHU4Bb23TIK/cAjF+orFW3yNqrio/vFe8j9tBF0bbVUiT
KDXjfuu6saUoJzXfGO0uX2OX0kPdmSKC1Stc0ioOo98Uf7hFflMsX/qu7vb44xtu8R5ZWMiMYejd
AyiRh9/DRgovvuPOdKAqu1t+PKoyjvdzzCysmpl9JGNN0rJMqjwNWlrJcPNeSV/caYo9X01++JZd
bEp7umMoWqAjjBoq5ssAY9Sz41SOPzDqqWMhwKqyU7leTNLqkUHrvPW8DiHz4/mRdKzVlFFw7ovE
Pec7dYc4nKG+LCERMvOuG1XWwVYXfLXpFW9Gr8QOdOZEhNj2t3krot5+brQ7bFHwHF1qxW5yrPXk
IZM4XlbB/bhaN1Xm5weF/MfPhlvkVzHZ7ntqzA6VzW1anfhyw9pe0OD+QH7v9VLpD9TmLC5phTGm
Ho92Ln9O/UL95uuBG2oxPyLCHV6mwot4OKZO3DC4TVRzCuPs3V+e1nd1g3bgXPvNR7y6gwseVfOw
tHMUN6wfKwoyUZXunxTWkeAZ/ZDr5OB3fMng9L208433VUROpd2n4/QTNvKLSW/n+niREX4ReuEA
s1JUk3SXocDRcwJFw21JIh9ty9XNnfH8jz6doYXGdLzYZaOQzpfR58UX+o0rzB1ieWs2iC7OkKf1
rVtPTvEN58Pvadk+vNrxYvyHSGtg5tJ3TxOEXEXks6g2FmZ7CfMVpkOt9HTR1HKraY6nGHBq2eom
LzwrStt33jQpJczJRFR8cIDq5+nPMlHmvFcTGvQz0Nidy+NUFhDxfDEoWSmlwm46RKQ28S7S5LxQ
NnT8y3s3oZ7a9Ju9Bp+fKdaWDd/2rH282kvDrwiblvBrrj5phX5dxx/+Xlh8eZh6t1p9TvG01/Ln
denuz/Z889HffBX4IYdtRo7tzVqt+uZxwTOCs2LnRGCa/lL1xNXKHb3OAUqD03l75aV2BuQ07Nea
upjBcnN6/hK0aLf5WYaqGU5tP8bj8EX5+oQ3ZemBPZLBhh/yj/JDj6m+WwuHYa4HzWfZnbK6UHcU
Gi5W/FJeQ+bJOcupizc0Lr9aeWh6r0f1x4X465n3W/ZenXNBO2AzfuzFqTKdNPJXMbg6tvqtjovJ
oSOs37lvoWDKO1c9hmZaQHti0ckgIVwZi9KTFm07WH/7VJuNRcSI0+zR0MSY3NLB26afvChOL/Rp
tX6p2M3sKGdfyGlx/tW9iaGPkmIHDrbLOKt0XqHKOvnVc+3IhLnImoyBdRHlevSPfSG4nKznK9IF
9vDPQ49Lk29Ktdb0h4mFd6QU+CGWWb4JsMPqzw3Ljc8LYK6g33d897yQuadPsor67Sc9BvO8qMdS
cRvEzKQOSMfdiOTKKw4bj4K+73ztaDx06+zkpVTpWozj5d6FCyWPeo/P8qZmmVW43bE07X749MwY
TvWzlC8+81w7+8UjxhxWzyEGLQaYuYDmFd3jTROvE5du13HcTFJZHAx1Ra3cgPhBv8m8CXhw5fbV
Sg7dKPanB6Vrz1p9jtGVizhE4R72weyQy1ArnIXzKlFRUG+16fssij6GnvFQIjwm7lqjVtHAOS/v
wtoysdI5tIm273PGE6kLgooek8jJC3QGx2L3YOY6hNlWmawv0EBH2BQVG8dutULeabZQ+sd+4j/J
erfP715imKL6ux85T2YbbFK+iIwfrXYfydE43H8hKy5FIWeyaAjrWY5NsFBQ4pZyKpN8rRGArmqv
3z947pmQSqhuX04PJ8YbhtJILHf7tNekdqXubtvZMZ0TRrG6+3uOPRFrayq90zDPz/jqvrV6/fUl
lfsHJrB5/IFLKJdmVytMPAdGHRK8QvVidq/EZ2L0zg9o2WMOkrDVS0P7Vj9ZjjzjW6E7g0bdZegz
hLoszy2c60pl5FpZWXYP81ZUVmyWZ+CZL1d5dZ9/RGHK+OQFlStG0DGkV1zFR9G2D00tTbKdoYhi
xMb6eoZ/a6CheXqBp7/x08fMcSfH58L3dJbmKyWqYuf4hh9lLyIgeWIVwV1HnKXGG98vJl9aHY1p
WIRHzh/GN3ul415OFU14l8+9E4vELz5qQPrWOrFnOXNk7U+z+BFxP0HI00o/Oln+0IQz9ML9w03E
HRStPs2N/3na89cznVsbA7OtabM/d1/+vSXtDwyb3f7UR8ntaST1b4221HXqp0ZGE/+h0nDoP0NZ
2dZ2kukYsu3ZS9tVSPp3FPr/aSIqQCGOjJ3iZE4Yi/2/1gj6f1OjfWF/qwQeQuew3Emuwf72pylt
UyOZ/xsaDTL/DyOBGrGv7eQmo5H4tjX6cxNlNwiEpXX84AquGbWePrr6onvJr30xtHupeAozuLLx
Y2m9aGotrAdt2zB/r2Ee+EfBJKZkChPZu2xcMwfLn1QtnLKom3v+YykOufymb9mnbcGhCfWkc7Fw
am1hHZwoq7Vw4QC59ibbfiTbGvf8c4v5P0beUm+A/6MjgjZm89m5n9xJ//9iGxOIRBQW3wWOAAZt
6dSEcmpGvelfbltYR65s5E9g/NsXdStmtEqnXZtRqSOrZTPYuMFls9o5iawJieyJS6XTDk3z4T3o
6L7l+60LxtVzNg2ouMEVYH3giUTAxoNe50+ReSRS/49t/M/BgT9mY+ltK/R7A+7A7e5bsfENijgi
Fk8YXd2onFl73Ye2rJ+7WTX7uHOxYR47tLIBWN2ndUG1cFIhd9K0di52YLl0eu0DctmgcvZY2ujR
1FGlvEmT6tnAzqWovmWPlgXNkmntsmnAiRvn19c2x0KHY1X9yDyP7ROebRoY8ocN/KenXG/HwIAT
z67ha+ewYT1LgHWvlM8EdC59n8cCVs+ZwDg2zQOeKpo5blw9+2lwpWoG+7YfrVcxy5k8eiBpGPBj
/cqZp52Lr3vRdo3zqgVTAG47N6GKp9eWcKCBPXRUnpN5HtumS783pFdiS4yWgoVimgj8weFwq6ur
KBRqaWlpbW1tY2MDhCK+A1r/qYj49lnSNleq+J9dqeLbJ0l/dKXOY/FlM2uPOxavls9olk57fEfl
T2E6FteTh1dtGualsycksydu18wBS/nr6GpUHxpYndwpo3s/D0lkjRtWzQJRJrBryaUZpVE8DZAM
87o5YE0Pr+IAA5+TUCYz4VZ82xRLclujYX+ePPtnpW4p+G4a+Ay18BerhJ0Ns4eiDfoUCjw3dno+
OFMGNjfaa7KDhowq26ZGvznkdktrNc9ppnO+Px9TWhKj6BF8SHYJPQH2VwPHX/PlsHSSUWP7hGib
Lif5h11u+3Tmz7ncBoE4hdnIn1y1b0LJ5Ewo5U94taCqZ7F9yxsx/cvKBVNAEBDKGAPc7E0/GvBM
gAWeyp/ckzAEuJxQxviVspngzsXPQyuAywGxQixz3KxuPn9ybWUzOFAcOHObzPPYNhuS2tbz+Hmg
c7sud2ZHg/CXhoSjVrP0f7ucZ8HGzgdnNl3u/A4KMqpsm8j8psuJb0WVz0lJGZmZmT47LC1n/Pz8
QrhhALBy85RQIO7TocgosX3yIr49e/yP2saW2sL9nxwOLNWw3NuxSEaf7ddq/py/4fCEgWUcwKaU
CyZ500YvlUwD1BmIb7kTGKNqkHTRJQ6JZ40D3gh8kj22ClBtwNMoPg3+9blN/XzS0EoccuVa+czR
tFEgxPm0Lrag1gmb6VS8wWnl/3weEtvmMFLbyjD/OST9c5FuqaP9P/5mlXAUDHANu09CGcFum/Rr
FNFkdNg2bYH8nk23Nr1inYDPf/hwFzMzMyXT48eP1zawaCC27QBM8YCHlsxQS4ntF3S26Woy/1dc
7TYb6GsH/na2XYCrHTixo4GMPtumHOK/B4Bb7GNLoUuRAFYuAAcCIhdXyqhwxphzM6ppHtu6gPVq
XRD8Orbz0yDHl+GLoP+BpSn7RtSR1FHAz4DP2b4MA/QxohcNuCCQ9AD8EvhPp2zmI3J5DosHjBt6
WpFMRVVi28RFapvE5d+lKYktDZ0BjXt2x08mKeB50gZsO7n/A0URGRW2TVV+z5ziW+rvn+c8FxkY
SE95YnJycm1xhAaEiWsfaHTJyL/9Qsv2/EtG7H/tX385mMnQfwYz0L+YvuwgM59YYtv84jf9a4v9
iwkTyNfZMLqmIh09oopNf6jfiO1q0YY3aiZWHarEsdkkesdEgP+ps12ZmtXIjdnC1ZZ7MxJvefbZ
fXFNKF653vEQIx+LQBWsX3ap10kJ4wm7yqZk4E6kAzhKeI/CYzIPYtscZZu+JfPvipHElmv7Z8Es
bbYh4f5DX2YVezv0qZdLSzuA5IZplaKfjB7b5ia/SRi3hBE3cu352NjYKJkGR0f70m9Vo5DFYAxT
a6S59J8qSG6/JLJNHxP/v+Rjt/eTnGwH4GP7y3Z8IKPPf3NFBEcgdi6tu39H8aaNAZmYRsl0wuBK
Hxr3pn9ZNncCiFVU8YMnvo55tCxUzKxF96HlcyeAGPZXGAPi2b2G+bLpNeCXFfMmgd8EAuGNipns
CQyWANLFczpKRDLPY9scRXqbrvbvisjWRp+A9qXeyXpNwAiwMJW2gTDP5TvHn+1j09sBZRTlhuk9
u3hKa/cXdT2VAwCGHF/Y8YSMYtt/dfS7b1q2pJocdlxt7Tn0TBI3RMSjhOLsec6Y5ZtEx9GVkG+h
tqadSibUdHWpiFa7lZFQ22KUJ/aNx/qb4XX+hvrTw3c5Y50NccsLMygh3VTTO3cCnj6VEBPLyc21
HijA1keIgpnrXLosmRlnktuvsvzJogShe2ndsQkFMDQg75HLmQjvRXctrr8fWJbPnfxrdfOkjlrW
zRdNYeIHl0/lT+6M/3vVA2vcvG6ueGoNyJPOFk5RxoOVCpWCyXfIlZUNkLwdP6KkQOZ5bJv5bHfV
/7vqJL1V8rZz5x3Wa9LOuwc3yfnQGOUeNN3upYXde3xfHX1vMsxk8kL7FI8IrxD/TqZQ3WdgFUq1
mpKBjILbp0a/t/q3RiXylod0v5fq9glxiwt7UJye5oy9VISdavWHd8cPPElxq6BifQnHJGCX/PmR
hL6N5fzBWfluJ02e4YNRMas3icuzuNh63ZQ7d+7U1dSIiYvLycvbklY+uku2hMyD2P7Lp99d+VuC
gXUcipiYDXsfUjR+c+WZUyWlb3JzXopX3hqhq8wDLuysYHZj9b5xN2ViZghTcGH34gYuUg1+c7Xo
9k3Csx3CJ3OpjxVhxjDJmkVYbtfK3OEj+67PeSoRByIYiwk7AT6CbVYkMwJJctu8arvL/t+1OOkt
B3MQ7KWd94oZTYyamJlNjA/t2oNepEvLoKP1eVW2ufLPvNDWftEq/tWe58gdt11gUnNm/84fZHTc
fj3od3F/S86dR5jSXW7pKvh76QMruikXDax0+C4zZG2KF7D0D8A3B+L6wxGUlW2XCsJuYh67yZ4z
8GprE8xWKlwjYJbCktTV1bW1tQMDAy9duhQlbb2+gZUA86ON87KZ//kopLbP3X5v7ctuqfa6vjqB
HIhAUjKCA8yemWIpgy5qCol6yhDGq/vkYy9mw27prVI8VulSoIVtuI+M2EbFeKIHiAFuWMoc19GW
rt4Yb/mFJbXlFmi0ENfO57WrE/1dSkUbi2wAFWg1V5gh8xy2X076vReUW9srBA43IuBx4OydZxRs
bBFBQRevXr3q5ubGwZTw5YtBts1h0LRpl5gkyai0bdr2JzILYDk62NqKUjIZ3b595cqVAscpJlAF
Fw4aMhMypbZN0MAJh7+hg9SWKpWgVYq8cDKyshxaO5iZQz9+/Pj8+XN/f3BiOhyObPmghiAS8Iyb
49kT1FiYySi2bbL1J2zT882CmZ+fH7CNsXF3mnF5KrwYVEFdi4YMP5La/kus36QPW4oU7ji07eqU
y4Mkrk0MHbbkWoETl5dwsY80uG93KRrvpBMXQTxzHp7rby7m8sYyXGG8Qqnb575S/hSFMCzwvK6l
xXPyZFNJyduEhBzXxWHNWCUwd981KWtA5hH86V08W5yfsz6BnPaHi7gomIEo+bITlpi/NlSGgyfr
Kj1OdaPaf+AGXmC4ZgYvivjitdzozn+FT0VhumaG2dabyxVbjikR+nueas/Gt5Hp6i7YJl34cE3h
GJlHsG3u9Lu4KblFlEH35Tp0d3cDuMnLy8vPH//s2T4Y0+DIiI6WlrmtLfiyaMckzRwZjbZNgP6E
a7qjxy+amBzddM30rCzC8hQzCJuWiTQeZFTYNr/5TaNIbK1IiEEhQ6s1GxobOe5RSktLq6qqAiEt
PDy8KxUOvv1X+0rX/Z/KSG+bofwJe9y1srptamp6amdAQADUdmADhxEF7aGEoHElo8L2C0q/CZVb
IheRjujQjTz+C/VcYvf3P3tuN93/wRYRrrT2OXNKEG2fkLPSNKEGJ66tzdjOhIXQzrybfh0OOye3
uDoeD4chiDHibgGRkQfBN12UyiYmw/35LkQ8jgacr7wk847MQ9j+m67fBMstLUr3lRHbrswQ+5kY
MWGPkm+zPk3h4GQxuY11tZoh3YZ6bopdPuc8Gz806Ng2F+KkRjrNMoM0jzw4dSxz9TLhtQtUCW+I
XkiqzZo4tf+vUV9v7NFtXTAiGDjtx+RDyDyI7ZOa3/POrb1TcV9dvn79Ogel3SlDQ++W96pgvtxo
RE3mnYr0tsnLn3n1CsBLuT9jcnLyJlfWtbdfKkZs2iE7nPYZGTW2TWDAMbz/7wkyFj0RLevw8uVL
9t07rl/vfsLMD4ZflCSNGBkdts1A/pQp4EZGPJtvwe85OeEXhsr/fgsecIKsKbZfgfkTXFJuZTV+
MWtCuJ5bTNj3aP3hZs1CvNsQXtO/X/SH7qldqrqwSCccegKJ6FJav5u2wmFQiA2ewMHxa1gMMv1W
tZW1dffmyEdJKSkwRsz1QsGaRNUhGQkyj2D7e25+8xFsCRXWMUQiFlNcFlJwx5AAzpReZWE0wBT9
WF/GtdLAl7MUKANOPeupisd3weDrC0L4Uf3xMa3TAH+UhCpGuc+0oVGIvFQvppv43SYPOpomLLkR
OCIRBoZKHRkldjKP4U9Tly2+cHZD3wEWNACOqqqmQG4HguPXQGqB/1QA+l9JV8CMFViRx/j4OJ7d
v3+/pOIJM+iNgXw0ZPakQLdNV8R/Dxi3OGAdwPfebFuzpuipsTE+YeGG+2yTU1OKnmsLbfGakZGR
gYGBNdpYLBZZjADZvdwaM5nYBf3TB6hktlrvgq/XZkf/XfnbSOJqzMNjAedhmUDSpXhTsTEqLa/P
TyCzlfBLSgu0KTEeY+WEmdgB4jpuqNy/oeGCsbExtZiAgIDr+qgg6F0zotAyMtpv/4XXb3Kwra3O
JRwyWj62Q1rJFExYj3UpnFDEEFpxsaYTSIdUz937b8MXS+wwT5Obi1Pd1q5aSlzhA/cNTBahxhaz
YZpF+KmvGD6VfQn1xJIkBxQCTNjNsuTIJEbQ7TOX36snbW02+zoOg0rUiV9eWQGYC5CqPnmifu3a
tePUCcnJXktre0B7DrMxkylAQP/w7pwtRv/1lZkCNzQ4jt3o/vPnl8+evYMs8gIh04NIc5mMFtsm
Mb+5pwW6NasAeOPPyB2j5LZOvztWwWthsHS8MWpmZib0xQsgtI+Njurp6bGLUTAztwUflj9pkFNS
Xe1/XMplvg9e7A2uQfZB7gEy2v5xrrOlmmYPeji/rmozGSx51kzQZSwiyC6OxxPCzYTr3z04msSd
7Lk21xuLOKwLO5/sRqVrVTSCxWJgRAKu2KLt+OHDh48fP05NTS0llXkz3xm/gWXmKaH44ggNIvMA
/vTRKJmthfgNgu5yC/QCSPY8SgpmfRqb2DhjPXuxw/ljwUB2t5vpOl4At5wvYYtgfeNRXTR8xMDA
fS60FY2aR2DbPPDMxGm1e6VlGagBwgaYBYsgZLFklN8+v/kjCETA43oyLR/6+bE/u//y5RUg7wAY
A8r4Pn9I7AYBzwkY03eDK+E/9ZH5r6Q77pj5m8bGRyiZjExMWru6EIQNWRBEbW1p7pBRYft05zfh
Z6s7iXGBHBImt24xl/Dw8fEBnlVURACgNd95LlLC7NLly89TUk5SUuvl2o+VPaQDcvfnu7Bra5fe
yK0A2ReYaKwKHU4mo+4fZ0BbfNOFQvTUZhsIcYG51kAYY0QfcQnfXPzCAYXVVfR7mo/yckPVxwIJ
RPesZ2neoXdFs2X+ujCC98YaBAJ5Hhsbu4N+eGSEW8GVAnC+fnvoDjKq/2n6I7O1uihAf77px97u
UjQB6Y/fNVidLH5+2B8uxYZ0SHHdvZ/qaMZccxeMkDU3Bf2Q3Dz4AMhI9VCeRbhKzIitt9y89479
tw0JJUYzGR2MxWCx4HKu7Ccy6v93sh93/LqTpaXQZrFAS1v7RppRKUDhi2/d54Z5b6yvgFtAQw/x
1JDRZ/sFnD9S/CASiR/UQgwMDNifUcjLe5ibT/69fTLXk9aJjBrbpj9/JGNcGtO4e/cEJSUlM9N3
AEIXh3dtQugeGgsyKmyb00B+T4etNaxZR080Z8Q319XXc2jtoKOrn+/Pz8jI8KG/bXfzZn+EKPzv
Q1DLUfvayej0pwsyMlvSKW+BEDH+Kb5hk6ehYyIwxRtFq4vZLZ0AT9s/bK2r5L2xwnjufIobFduV
3mVHVD03wNGQuQ7xQLDYrNVTwmDEDSwa5rVOBQDlu3XpCDK6/+kDUzJb4qhy6+v+E0UR9PVcp55N
rYLFpN7V5ajFLLN7pxMzQ06IFhSjsS7dWEy0ENfRii6FnQEKG+vx6Gm1+TAtu4GrjOV7i4swY5tn
ijivy/r8p9qy2yYzvwuQW9sW5DBx6cqVA5Qn9rGwBD1+nJCQIHB6V2Vl5anSw/LOFADcP09kInP6
V3bbvOaP4Argk68lzA5s7miBwRAeHvKgQUI+0XiTUWHbXOU3qZn01nBldU7/5s3DlCcGJyZsra0L
7cfq+vNdNN/IsXBzh3w6paw8Mt2RdOfOHbAiNWxoaAgv8sT+XfWUP8G+TkbPP70RWWZLFbfpXMIT
lw7lR6aMPI8tsL4DM7FFG1joVBV/S8duu5QwRpfCNcJkL7d/v2h3BOz+U/5oV9wsjptHQEBgHyvr
HQpKXt4PbfGaRDwO3HdlQSstR0bzP73reGuUzH11TnPsIWZWaHMXicqZJG7WaDeXRXxqdJvta0DX
3V9PIgYLiWNxGFi2Av5TBlZQZd9jvXDYvV7c0nQ1nMYQL9a3Tn8yJW+xNrAXDr6DUtCThZNRf/sU
5vcQZ2vHWOS81r8lJgpSnjC6fft2NfWPHz9um5rGX4yiBiJGysYuMpVF2T9NYrZGxVbnel/waQDy
/1WJunHDvTfLGqxEeUeTOy0mu20eI/575pDeEkMGkr6uTxejXF1d2cHdLB8CAs6fO3fuypWXqamp
L18CgaGmvj7fE/v12bN9ka7XrnViUEiQbiKn96HJ6PjHec2W87/vpbqzf+V/pR0hlwqw2BFU8ePy
VFndoxVSUMXClSnMJ37ky06YDx3gfjLopgjNYqKi20bFwEBMWFjYDvoHvr6ogUI6YJFmGUiVklH9
T+/73aLqKyjig3z4gU5FYzD/exWuCMLIZFSsw7wn60307qO7Vdz1Y07mE1cAaGlRQ5bs8qkBcr0g
zaL+jWUhavVoj7Hy78qpXN54SkD1veYKwv+pOkTsT3Obrb1Y6/lmEZqTI0PZcuryZbvyRwygbz64
SNVMToP/Sj7jTiR4mZry/VVq6uwsQhCVwDhv50ZuPytEbPuE5jcZ5tZW4F87swoKCtgfU3/9+jVe
M9Yw3WSXkJBQZHvFE2YEfn0XsLLeuzCOktPpj5OXLSUL7viRkKZxs78SpdVxs+YiohcWH9KSBXy0
f3gAB1ciEuLnh2laOhiHHthbxh5yw6MxSGJvtm3X9+9G9336+vrMNGPBOn7oOamz5PT+49Rla5t4
8cP5HcETm0nSQLjZ03lEP244f8rZ7+1yj5oUG6xgfTF+poe/k4VxaPj8TOyyAXF5qTr2Uz33K5DD
cdp4Za0NsIHlQ1Z22V3k1P7TlEV8S4xtembmlomJCc9eMXHxu3fvxih6sAKk02iIKpycDv+VJRf3
xWHVU6coACgxM8MsLa1j0fwglJiJ0viT02H7XOU3d95urZgJcJVwEX16BgaOxxQBAQHW1tYIwoag
sPBtE5Mz4SZmZsh8F1EtWsA2PqX7ecjp9af5CXRLb+jlALRoj1QD3KrkeVtMhK03QRG7Gl+2zl8z
nBuPLMRjoaMLlkBONPTgmjy8j7CBQxYTCwsLATClF/ve17cx3sgJOpWtmSSZDlcQsT9ecNnSipRD
z5sNlnZtYklDj1pQBMzQlSixLHbm2a1K3wTeVDhhLYOwqJvrpDk4vJHE9SnWE7eIQT7EFN1L8dzN
pnuDeAy3rA+qffSrDLmQvv2Ww7+LJVvK789raprxHExLS9PT0ytwXdwJLFZ1Nar35BT476yx4DCo
IE6opJQUxzMKbm64nR0EBJKXT8jVWCDb7yn8m0AivaXiA1hGB2hJhCh8fmSE9+TJpvuU586fd3dz
uxglPdcYBS32xtvfuwckqCrX3n7+vD66GIogEsBwjb7ATqbKDtl+n2CIxLYWm4TMv7taSW+1y9hf
B3r3NTaV1u76mOPmil3bRUVF9dBPNYFapbKC7/4djfPq9RSC12XddqnyNMZ9/PKe9mNHO5jhHYva
w0ZO1T/9omeLIXpy8jHw59heFTW17MzMvzcJ8FezkOk7A9l+y98/5VnA2mNmZuZ9furMmbIs616w
uNPnuJdcZ+rtd/mFbKuN/38oIbWlnIuq9N1+CgoqipKwPsEAgdenJYNMBM2O0xJdsvP7D++/c/yo
ChXF45qGz9Pzr69flUAD+kkLsJ0np9/2X/v8kRdw6yuWly5dOsa0m5ExNTkZT8Dj/t59PNu9L4Wc
HtumHNuGhv9BOba02P7P0HDs9auPH01vj913rhESOOHz5cq1y1d1gPSlHZzDIJi/5zM5Zf/4Dtst
wX2ew0RTnEbESWaGGCU3WiDbPO95gkyFDrL9/ru/2ZBqy0ebJppjUw1y7Tn2UORyK3mCfRcuWbLd
J6fC9s8a/x7Dldxaf/cjFANgM2QMBvPjx4/i4mKAuyYmJiYnJ2dlZVVVVSGRyPX1dcCLGisOFpNT
60+fN95SGQDMRzqSdEV5fZ6yiSq5LgwiixFgkUk1l41MPR6y/Za524aCfzfk21oF+F9QsOd9ziYU
JNJTUeU+9PN59PRxwBNKwT3qghbPbop/tV+iDTgfUAcqmWJOY0NOyW3zA3Gxba1ACZl/N6aDbgkC
TIyOsYpR7HhQTbUTbAM5e6qktLaS4T2g6qkDxfffPkvb7eST8CrH7+OB7/csOK7L8vClvk2g+qpx
XfUqw6g4NZhnRLDvqSen8PZrFrKSPxUW34LCsv9uAweR2nKL2V0NPPfLfPakpZ16eP+YEKe8vDwN
PxuUUXTfwiLd7gfmR4z37+M7cfzkEUFVRbCrixA/oPRHekkD1asXD5+zML9r4Tvb2tLRBj216xHw
RadZKeg42MUOckS9iox8ra93wycw/dq39F0tzqt7g0/V1XZXdgS5l/SX61zrrO+t7mqOjegC0Gj3
qO/gs+9iz8KG+sBlU7IfiiT3FLdNZ2S2dS5AQvZ/NOnfYmuQYzRikIy0r+np6Q737O0oLbgMlbx5
Ko+XHBGg+uinCvIzTuwOsrFk2/zlzxwGAIJJT6alk6Mje8mpy5fTs7OBD4oxxRtNivhgi25KajGT
mwSe8ckoNTjxQuHKk1uVytSvcqZWzXpjEcUrUy6tT6D3TvOId69aNT9Fgfa8SyNdRU79P/4maEu0
53Pego8TlvKRqVZF7tLQlAusmIg3y8bx0b3IKVvnz1bCey/iUwnhZg31+4ZX8+EK2HX+9UnOAbD0
Iv2z9AKqHaQlf42c2n96FMGW90U82EV34MAB9pKSHz9cV6Y7QB3MVGjIFU6238FXfFtdev6XOXve
2pDu6HMoWC/aR/zs/9AMCcOtxi8u0YyPMQ6Bxor2xqDLcPAdNPDSXT41zl1PHVDe4IbFXenCGuTU
/NMHp2W2BDk9S6OcqDr/TTXblmg0uD3xKyj4aqJLtNC+4UNCXDaeG3M4JPE0DdwuxZWCLQKOGe2p
hr/Rhf21LcuAOFoRFYsg4MFjSol58u7kNN82mfrNRbq1zGoD62Cmy8bIyEhJCe7uiIjoei1hBiIs
/APNIDk1tt8O+DfX6db2NyxM+/fPs23WNVsf8eOhSv3YDXl0u34Oz8wSjQ8NXBG/OrEww31HPoa3
QldhQXFhGouBgf6I9xO2JKfnn57ZBN3ame6VkZDSTrPNQx1aU7kYJGFD356YNPjZn/7csOnEAGId
nzoyrfauY7fdKgtjtiK+aKLSJTNI8/UzKjYkcWkMAwNJVftReXJZ8/ZbA//uQZat7ZYjDp6+ZPP3
XkdubriNzXy+C8qbiCteJrCNMWiyhyve50EfbpaGYZ2n5zRReNEh8HgLS7QbBtuFvMpYfD5VVYD1
Bl5goiEfjtgcS3GHHxpH7gH86fYvWzP658K1GK9KMH7ezkBj22wRXJ7YWwVzsmh7v5zu1QkojKi0
shq/Oh4PBtCLETCF9dVqVIlQEwsQQHPjkUUbBBqeEgpsn6wIOZ23T5l+80XF1t7OeK6l+fvTULJP
Tk2J6KWBSZ5mMT4xZyHGoRLcv3b/seVY+eSHVFvE/8fclcdFVbX/ADUzSSWXen1LzPyVWTB35p5z
Z1LBfTdzScolAkRFAwwwXHF5LcsWl1LfXlJcMhcUNBdUBBRcciVXRJNlBAaQRdZhmIX3OcPgc/V3
/TUzGJ/fX37OzDh8v89zzvf73DP3PseUkHfF67tRrIXDLwm6gmXx3ktWRrsdn/6Rqa1bzOGygoOT
othO0fG1vMTBCJztXYebxJCOVRfElayfXt/Jo3T3illdFumrtIsvfdGGtVE8cUrl1fvneZoLZ73r
xn6f1K9j+J9GdYkmUxG8eP0UbTO3GceL04+Ge9YZzN07cj/rvVKKeVPfO2NdDxN2h9fFnxSsQdpL
L91KT9+2dWvQn0fKoF52io1QFs87t6/IodmuwIXv6vI0OzIj0iYbTuxXdx24GgpMWPmxiwxzcqra
6O+6Z638aX2ffbfKDKD6TOfjzgkGiSjY0eq4kdPfqvzPPG5YGmpe8u3n5FzSRy1OTarbnqB7mS35
CxnsHvEMnWHF7V93XJT1M32wan1G3fyKa+7aBHfVhN7LW4bsXaisqNaMrm8L2TpLJdEykbOjKXIj
82/d7fDzKqbNnPlWz549nZz+dexY7Y89xkWYDLrstMzE+1Gvp3mYn6i5VW/hf+q9z2YYZt/Vu7zW
cuDaWa+u27S4rlwf1UPw/HpPRLNOmo91svLfI73q212tv6V0kApDkz89Zd3Di0Zd3I3Lmovs4UWn
rj8dGv15Qo2porRubWjpUS+P5S0d20G9eqBkYYTxXvD5c3HHh6pNz358t658weWNqcPvR8lONuv2
QlJETa7WslFumtTHQ4q97bf6yG3bAXis07e1++QPT6tQm8+rePaq47L+rm4bZF3MN5e39XUQpNg0
+Q08Vl1ETZxb+k2ypS3TmJo1aamJxqOV2RvAut++sGVZ36kJ909/ofVsk1Dr8+3rbr/VXkle4F2y
SNchtMg5c/eKtv3WOY+uTjSUVZSaazd3+bspUtSbvHazSs2PLdJ/PmFCR0EQYDUfPly956MDEcba
quqzmZtmRU29Wb+alV69W3tUFl5d4T09w9RaWdMKVrMh+tX/eWVxqC4l9pzgMWzvPLaanxtfV3tT
k8nUfE8HpcQDElzTd0C2ztMq7wff3BVuvhXWqevJG6umZZgMxtSkgDiPC3sXJx9s/dbl4wYfKOdL
I0zFx6rHTCvuduRISkknTUZdb7iwKY7pBNegjoP+vd7zTaW+JD0uExY1u9TsmeLhLhUF20s6Gxf1
o+3drXsq8H8vao3ahR2S4RAy6PSp7uyas91ch1ApPk39fLmV1yUPTPVr2CzR9wJTX0ioLVProyrH
BddL9Jrk2jd6vhqRUKELL9qfdjx6sxpmwITJc+tqz2YeDU+cETi/BTdwzr1rZFVihNHYBmr0Cat6
SXSb4+xob2xjQvlGJjSv/tzrvLyO7NST5ld91S5smbo0d5DaC2n6HsVWJXTiwrrossMWz92SNSA2
NUE/z2R0T11UX1Y5rgFHjvc2KMtrd2hNG36WfbbdeXSnDH25Qc9ut7xOPfwdOqsT6m7sT/OMMBlZ
7T0ot9cBqQDYXnvZmNBHe3LbcUhU/fkaOXkd2QEb9yCxG1azk+ZdvnWQOLuFs701cWOF17qN9ypt
3Vq9d2B4widTTKyz+s0ObfxWJai0JZrLmszi8KSp3g4uy10hwUuX3YmKCE3Xr4XLy682F1RrzAs3
N/zsulW3I6McnLM/LJOZbt0JLV1sMujZUp1Y4FEpFYi/+/By1WMn7VlVgdRndppFfOvXqtqFLdVc
tdrlRUtqFzp8IcWoqYsqlVWUbpfnRFZs6mT21AUnDhr6Va5J02QYJ1fkRxa77XRtdrRk3lHNae2h
VYnpxREn2SXiH5/qK5xXJYFIx+lvD6n6bvRPGzyzJpfJ7l+Pn9VlcZ3JnNaRvXpL3cNqR29kGxes
YPeCfXJa2S0LbbUOEmfick3f6di6p0f05SvqTnoZzM2eWVaTy4Q01pEzP/LaJqiC+i5rm3Oo7ka2
V6aXh6HwN013zfCdR4wlnSKjFi6oLB59LXfVxMio/TFzXX+rHXMuXZvmaaqFupldMswM7y3R7YSz
vd1xo08O4KwJxHyTYd706Tv+859/dOu2be3asQEBBd91FjzqauOrCoQop9gPN3hO/bC6b8ilbTu3
xWqTDCaoKXThnpGlc19o3+y1nw6tuvpe4h2jWg/XEnvC+zdfOjSsatvObrFtkkzPgS218FFFSwWj
6c84t+6uZa3J6/bXwsrOm2Tui08cVfvk7YrbkWn6s7ZywYmTaTBZ6k/V6brC+5X5Rr9r94L7Pev9
3N4vV/YqidivOxf3hnfdyGO6czM1oZfXtRmU1vstD63p/FnvJJPJCRbIL659pG4Etr3lsq0r/umc
44inzLmsrz9nrkMvh2wJQra3XW50cq0/Dii32rD8eplwRNNyZ1bzndkTUu4f0WhPF+mmnyt+bV9O
M/PJP047skafLDyYW33qfs2sCyWvN7zeLz7/UK62VGeMUVeNOVn48h51h2j1zAslvxfVaA3sjOJ7
aR4SzUY4O5o425hh1VPKcF47luK2HddbTjlrH+pwTopQUzdktlLLass0mbeHeDu9kOgy0fhVQLpT
5Eb3vEzjwry7qd9Hd1n6acy6Ni+v7/PMa/c3pkI1HWJKiS2Z1QVqtqwW3/QqnXe0PDtN8DQ9c6NT
1IIdSbkv/7F6X0psnGedKVdrborUJdNT4thSzvamzLZll5fZf06kfdn9/3yc15VSXdDFUtmhvJY7
s11jcuZcLk2+X7NHzc427hprWafd9uUsvFIKqzJGXf3J2WJYv813ZLkfyvs2rSytrDa/xrglg63f
V2NyBh4v2J5Zma81GExs/bau7LtHKiC212Q2ldq87LG7l2wotaUyLDrVuuMFB6MUo6bevmLPZlmT
4inPbK0r0Rm3ZVVNOl1E4zTto7OHJBRE/lmx71713D9KhyUW1GcZsg8Z/CWjMqFAu+LGgxFJhfD6
K3vV084Vx6qrsqv0l0t1S68+GJpY0C++YMnVB/EF2gKWZXZU4T9bDfxAKia2F2g2Zln+lLLcMbtD
fZbz1q1ZxyqLjhsdiqQYNfVPjrZkOV9r3J9TPfN8seqIpmts7nsnCn5ML9+TXbXs2oPhiQWu5izD
Av/4TNHO7KpjGu2X18uGJxV0icmBhRx6uTQ+X1tQY7xQrFtw5cHAhAKYGMuvP0gurAF3NprX8uBm
g3pKxcT2asvGLCuaeC3b3ja6CbNcrjceztUGXizxOJb/1oHcgPPFv2ZVQfkESxLWbPf9Oc/uzHrr
t7xlVx+cKNCeKKypzz4IeN/4/G9ull8s0ZXVmqA8m2de+5NOFa1LrzhTVFNcA1lma/kHYfA+qZjY
XnHZmGX+aa1lUZK92GV0p6WO7aQYNfW+ly1ZrjKYIHezL5V4HtMoDucFnC/ZmlEFpvzljQfjkwvd
D+a12632jM//Lq08pbAGPgmKPSa5UH5YA+X31oxKMOUKvel8sW7FjbLJZ4pgkvz7TsXZopqihixf
Khn6vFRM/uYtMF5GmjrLtpdeNtaSj23qNfpasEGcOsx2KJMi9LeXTkJTp+hvPhaelz3ty/W/StHf
XveomjpFttc9vE2MuMeuyKw+4F2CkV/7Ryi9tNLRRYqS7WWLjZS4p0NJIksv93R8TYKS7f2fFTY9
E8Jzj9XbVu0L/+W8e3/82BZA6tUIx3ApUrYXHjY9t8tzj5WXVt3qJEnK5RFW7HeZzkscB0pxsr30
sE0guKdUTPm+iJnqsN58YfSRg8SJrZwd3ZybrpjS6/VFRUW3bt06c+ZMdHT06tWro7Zu/z31uqbo
QXWtoVJvVFcboC4+U6RLL9c/qDUaTCad0VRYY7hZVns8X3sgpxpKpzsV+rxqQ0alAV6Julu5K7vq
SmltpXmTMkk/VqqYErd4drYE5X0WAWf4J4SR5GSWX++d3cf6hwbPCfHzD3XlLHuPjH9QGHws1FVu
2bBydu8XFBQML0xy5SxHN3OWRgec5almzvJII2d56o+zPAzHWZ7n4ix3dXGWG0GcOQsEzvK7M2f5
lZKz/KzFWTa7p8BfH+U/NcCnf/Bc+PvsWwn8FyUvN781ICR4tvQ7Y4PDIDvwojNLzcPgiMoYoOXK
5s0HY4e5vhnoA0kNfncGZNM3IDisb7hPkM/U4GC3aSE93MfVf4Z9jyWe5njA6OEcGxkQNMscTph5
kyBwgiuBolYBVRqBP2lGasEoM4/6B4dMhSkkfmmoq/vox8DS/xtsiL+f/+ywgOCgvoEsQmEz/D91
8wsOtAMwizrhlLA6iCtRyOwGLDwB8IywsNnvuruHh4e7PQLV3Z7ggsMRCKxCxpkx24tV+ddYA3wD
QmcEhzUGKw8OzLnKYTbzVGE3VtUTsFomwlAzxuBA/+k+fX3CQn3C7JwGbMErQD8UYE7stgE74Yp7
KD8ptOawmhHbHVs2B+Bqmi0yBtpesNwTwDbEVqZQKfv6+PkFh7xjBh3aiDWmgLXF1piiQb7swCt/
Al5RcIOCP2/crIWIwsqSwxRQ2K8G4o7GkpHlOLn8aUVWLtRHVq60P7L8E/A+ol4hfnNC/BujB3Ki
NOsBQ2wv0r9wsaGcXFC9M2TUUwkuCKVcBnogh+BydnuZ6kleJgquGS2CtU8UBHPNwUSBobYX7ZOM
zBJg33A/n1DA2dgygbqyJ8gYWHbLqr1grXCyaSE+QX7+5tiG+If6h3zuw+oGe6PMNuwEUDG5jD2b
YC/sR0zt/ZBgv3H+7Mvd3x84GIp5/7lhltJ9gOXfYeYvGgzVqZni+PFyVp9bdvbGj+fZiGsYUTaS
N4yUMBLqP2lm2XCRwL5nWKCCyMCdLRtqbMjBUMChHIZKHCpgqMIhOLx5557VyWxMYMzh2xSGchwK
MFTgEMoCgcehCoYEv4sCLgFxATteQFxAjxcQF5QXvIC4KOBSinBBoHgl4gK6vBJxAV1eibiALq9E
XECXV4pwAV9eibiALq9EXECXVyIuoMsrERfQ5VUiXMCXVyEuoMurEBfQ5VWIC+jyKsQFdHmVCBfw
5VWIC+jyKsQFdHkV4gK6vApxAV0iE+ECvkSGuIAukSEuoEtkiAvoEhniArpEJsIFfIkMcalYAYu4
gC6RIS6gS2SIC+gSToQL+BIOcQFdwiEucx2PuIAu4RAX0CUc4mI3JBDuIS7eXFALOJSb6+uHQ8DF
qXAIuOQy0XcBLjmHbwMuuRyHgEuuwCHgkvM4BFxyES7gS+SIixX8csQFdIkccQFdIkdcQJcoRLjM
VzSIC+gSBeICukSBuIAuUSAuoEsUIlzAlygQF9AlCsQFdIkCcQFdokBcQJfwIlzAl/CIC+gSHnEB
XcIjLqBLeMQFdAkvwgV8CY+4gC7hERfQJTziArqER1xAlxARLuBLCOICuoQgLqBLCOICuoQgLqBL
iAgX8CUEcQFdQhAX0CUEcQFdQhAX0CVUhAv4Eoq4gC6hiAvoEoq4gC6hiAvoEirCBXwJ6j27QCOo
9zzQJaj3PNAlqPc80CUiveeBL0G954EuQb3nSf1GwMMh4EK954EuEek9D3wJ6j0PdAnqPQ90Ceo9
u5wkqPc80CUiveeBL0G9Z/ZGUO+ZvRHUe2ZvBPWe2RsR6T3zN4J6z+yNoN4zeyOo98zeCOo9szci
0nvmbwT1ntkbQb1n9kZQ75m9EdR7Zm9EpPfM3wjqPbM3gnrP7I2g3jN7I6j3zN6oSO+Zv1HUe2Zv
FPWe2RtFvWf2RlHvmb1Rkd4zf6Oo98zeKOo9szeKes/sjaLeM3ujIr1n/kZR75m9UdR7Zm8U9Z7Z
G0W9Z/ZGRXrP/I2i3jN7o6j3zN4o6j2zN4p6z+yNivSe+RtFvWf2RlHvmb1R1HtmbxT1ntkbFek9
8zeKes/sjaLeM3ujqPfM3ijqPbM3KtJ75m8U9Z7ZG0W9Z/ZGUe+ZvVHUe2ZvVKT3zN8o6j2zN4p6
z+yNot4ze6Oo98zeqEjvmb9R1HtmbxT1ntkbRb1n9kZR75m9UZHeM3+jqPfM3ijqPbM3inrP7I2i
3jN7oyK9Z/5GUe+ZvVHUe2Zv1KL35sJ50NywIePMG6usdB4yjmO972T4vmjvnH1gQCgR7aEPCGXN
kmmDYbAhQLUYhnkIUBv8gg0ZVMEClY0ZVCW+zaCqcAhQLYZhHkIIG/yCDSGEFr8wfxdLbYNhsCHg
ooiLpZYiLpZairhYaqkIF0stRVwstRRxsdQKiIulVkBcLLWCCBdLrYC4WGoFxMVSKyAulloBcbHU
CiJcLLUC4mKpFRAXS60SccFMpkrEBTOZKkW4YCpTJeKCmUyViAtmMlUiLpjJVIm4YCZTpQgXTGWq
RFwwk6kSccFMpirEBTOZqhAXzGSqEuGCqUxViAtmMlUhLpjJVIW4YCZTFeKCiUhVIlwwE6kKccFM
pCrEBTNRkCEumIiCDHHBRBRkIlwwEwUZ4oKZKFgMg60T0XWw/OGpLJNcWef7+r8gb/iuKfi5ho1K
qBXlov8u/lFP6pephp+u5Ba07G/jL1UXve6EdBZcFmm8sgKev+f8xpE2+0av8fXf+6PvvHfWV2wu
cur+3TtBb37fbeyE6g1a/8U+neOOOr6ee33C9qk/OFXzx67M+DlUlhK1IWrmqTEV7fbv/tAwa8K6
wd0cF5f0K/vt6k7fDz7qkXxF7TP4588WPN/meW1Z75Tf3x2b9/aD3I1H3HrmLTI8n+nWsdWYgzXK
bR6OC7lBU57ZOmLrgCVrx3yh3hGyZXj/lgfK8qrXtOpUNepAdNqkUy1rjjabO/Kup47/cUv37hEz
NaOmRtaQxGNv5x2/XnM3ssLXbcS/Rrf66mvNG8GdNKXLih0j5DWGVh3qJhuUvSZdjIgcc7C/4tcR
zSvu785p3edU19A5k1J3ynPD8r0PD5jb9tp+2faDfi8MG72irDjKe4tz+9N9Rw3dVbz1rmL8zNUv
dsg688fkf/TS+vXRK/VDbgfKPHN3N3P/uF/y5YIwH+33XyTMivvoxNUTwwrXnsl4s3l53d3Duksh
+mlRRzIPx11YMf8b07L3SkpevV98M3CK1/iJ7eJz3hda/HAoPfT3oV9tGjbn8MJB6uU+gfucJ3cZ
5zJx/9VKw/KN/u+Nin1zSo+XXtz+5YauE7y+GdY5Nd6jWpN3d9GBXUlGH92Ct5MzRm4elJM9crM2
e3KPYcNjvroV+dyqXim/jNixyfNtr1kH/xl0MePnzc/uTlF95iuMOLnhotfZ7a/7Dt/XIvJqapXz
7ZjP55xo88r8thktD8S/MaHfJ1xrWf8dMSlHlizZ0yvuv+ydZVSU6/rGYZDu7gYlpGZgYAgdpEtA
kK4BB6UZUhqGkJBSQloJAUFCaUFKWnBQaemWRlJADrjZ57jX2fsE5//pv/gw61lzf7re972e513r
un/vuhEM6jwDrXAJprbmtskAjtYvQaUT4NyOvfVJRsvLZcafhNK+6vZFs8ni5qR+mkFnoozGaNcr
K7zHPRgw1lfxYs+6fL+saHdHQVUhyVe80CYKQfYonqymn+F9wMco7KqR8bbnHlAFODuoJclS5guC
SiEu2z31QzpTClM6QuaLpi0930MLC9wFkkc0bfKk/s08Qvb0XSW3whb3QuXp72BFWkaxhTUeKmj3
ahel7Yrq6Moe1njUQD7rsj6wOFAmseReP+7XY02zoFchmeJajhZJsIszMQ2Gjciz3P++R9lmR4+e
HvtOrCKWpPBO2MZkBd0Mp1X+ZyE7kVRTrifmPbJvg9bFL2lummlB0twj1ZmX4KzSbUffEdWj5Wz2
DvwsjNGdmFT7mSupyxxb6sxsU2KraUGbSiKMbXUxqPvCQljZMfZLwQqhk+uhaQwz8PJFzWQrGqiQ
AF6ZXZAJbpaiu/ojrive6BztvnYoRvUDnFzzUs+83qIhL6iFfCcnKcipHg4CYMLHMY3xg7yDDDYU
XBCuvtqXb4nx4CWJKSXaCCjVXZ0H7x8lubTgGqzOjS+47YvFqbEMBWUKHk25KjOXi0qM2FXkQwdl
SFDugghK6EuH17v4vJpfJHo8F25mjkjglj6Z9jEfvC+nHGx3uzaCXvYwoMpnttjr5uMGBseuO4DK
5Pd0gRwSJJUC0y7zIEL6YDjQPnuBZICBaITddbRGNbOCh51ShK2qHBPtOkn5g/0a5yT5SI64h3S9
rXQYgwx4Ixhco/uqUxX+SeEp4FewLAmub61MaK0maoYWMvDCQPyWd5JxAVrf/HuuzLHKqL7/cfkp
UBSdWNRfPOSdIcVh/MeBLxYOffnZnY1tLbSefm4IJ99gk7ob6I5BxFC0yU5lPUXPUXLPHkPeJZ9I
j5YZ0bwnvIdvPYb7ForGMge6PcvRexJosKJKRlWhpZ09wsxqLU8yvr7Y9643yHzcbb9NW8ttj1dC
X2uyfffZ81t8AE+/ySNcEsgeQhW1uD/bdICmrwHjeadyQDvQKDHfKSHwdXscZQpRqDfbVGHVeFYy
2a54Kde0uRAPlBLZUKfNg/GQJDduNK5Vfb95c9dNOdfMzGQ3cjiJdzIXo46NZ8x0TE/WZPrge0W1
vsibG4kEfru1LpzDV9foTAs2py0+yxMo0nqq6jSBidrvC0Hr4vqvMIib6EjdntuKssEZVFzwEDYo
Xugv8EGSkNEFgBaMA4JLP5CFjphtR8rCRCfwZAPU9DoIzbyQ7bYZem6puyZKKzQJC7ByBH+vxWf6
g6FelVe4Up5F31qjlsxnAbbZPuymmPO4HZjaShIKHzf6cTXl3neIEds/t6igHdMCxU1GkvfQmMg7
Nay9JJ9hfjH+kCygONQZL2ogG4VrodseV1qg3TRcINc5/BIMW+G7ApMCJOVcKqYA3n26nft6YP5K
xI1GhJ+zG/r6YSdzpg/aaKNErm8CWpf/XVfp9X7AyG708RBhTBKW7WFg+9WqlBa2Uu1VKeS1VKNU
k7c+XlQgYgMdDIa72baVklDjfD4X+pemOKMEtF6x0u+kRTtuVCos4q7yhl1SaIJ8egvixSx9EtOU
bHOoN96f4V5gOX1v4Q0AqjqNPdiIN+BeMLv61iQRbRwwDgBPzbECwCKdzNctDoIAykyXbKtm9Vpa
J/hJSUZ2o9arGEsoCuMptEwQu5E2h4eHRtegljHP3sUwZXc/VZtgjByYtUtkySr6xJlvi3R8xyER
wwJyVHw2H2ZPvqyp7K59I6SIHHhw3RzQV15VXMOWbj3hG8SrIkGwg0P1avhLUYaZEtZ4n3tCMo1Q
gi/3xmfSfrA5Vn5cS54w6JJFFC3wbQBtpnMILbAngBYp0kYAufuBIM05/KSeTosUOvlv+oGgMdki
xCh/+loZl8SLjYXdCu/p8ZGPDwlGa9pC3DTZZRLX2x0vLePb7R7cl/b1xTM47J6dWmZLxepPx2Jz
aXi/Q3KgJXCkBNUKf4It+sBDdllmf1ddRFx//DNRNbP7wsGsg3o3P2vdvAXLc+7kEg5pRrk9bqpi
pEVuXH5YJ+PejYbe5T3zwrEcmMAsGvZ0Ksu2K4MZpbi3+N1P7lSc+SzfNjD9d0IbAEtfLWdj/Gys
GiYOLHWLR4llzGYrMoI0OI2ihNeDxXEK0fodE4Ljt8nNMEufsmyQ3qlhCqRTJs8W3xI65J1rAhLp
+AER/GGdkwJ6ryZS1sPbbUadSlIcI57gP7868fwLYNizkuPz5VpAD5IT/xV3sX+JWWeTzYuHzxqg
Wy9D4xPysINVDS3qgP16iWXVfNBWBt1kcCWvckq0NKz1aZU+hduTIAE/8YODDhLXyfs64guP9/em
RjL5/YPeaS0T9kgtdzckBo/hPxBWZ7Ja/TIxdAO7pUCd6tG1q6ILZUXuu92JAAPagZSrwn7BSGyX
sYKRvoGFnWI0O5JVVPltktW+Lig92JCd/HY9E95uOJcIX/zCsx16/F74Nw0MatrD/BKB6Rx6/4R5
Fu7ENytOog0OgNc4OPjoL52wIQXEyu63nFK4HRu1ad/sGpkadKhBRnjH2PMVvZLQ9lq3c2cFpawE
qGqnwFJZxOO8oSVmTby9KvbeBnrHj1iNFdCak4oa4RMpjrHBKErsigB8NhSzq9PoYEGIrBxq5SVL
NMcWW1PJRJNTshSNc1nsBuF70jTQTCyC6JC0EILXAfGiWkzVkn20sW1E9hAi3rHvKY/bz5A/o8y4
I50IbHpNp+NhHcapqmce8Py52xGultHY58+Xr4swNjKisnLa00PSie5Oyn/f2QzsW0un2YqjaZeV
dJvI84pbr0FAK0ZFjo9eHbluX2nz8idonInYYBom2AlUZz3QiyVKmU0dIlnDzHW5xTP04MCciG7Y
hICjgUz0h6HfXb/++x6G70Xe2jGtxExXH9cIoNXaCa0USKh88K/2LcOCEH6ye2mo73jfBRTkbqgY
4rKMPpWq91KdW7hdummiYhYinJXE86OaO54U19KCUc02WSBqGI/wqddSfqEfNkI5XMsO9MKsa6hR
IrRkgJKo8oGsfOe2KnE9eRyaNyr3Uk002fP7H3j706eFvngZEq18SkdfPm7z2t8Rtr8EOyzYy4FI
zxgf+7lTyOlyVMlMDr/t4ZRmyQlLhu5/97G82+/WTqC0UE5Gsrwxvdyz+iOdNpaucCAH6UlkkC2a
TfD95guEiS5wDmKpOaYBnIHcExpTLM4e6/UhSoC5SSz2ZQkFygtbKhG75ws2Id56VqU8ZroGOH6b
MxXFI0d5rNYGoQa7e0qkGx2BaQN/ZIz5A+krAFQ1uIeJXcwRaHPdzk4iR0vwI9tXfv76uaUZaDOA
XYl1YgMmJveuJjNszMGBkQAKOOYmCqupfrxtkNKHVc4DYS2nPnXr3WwbzhpNY8+33GM/nLUlaAg5
zppVtCXdpKHuijAA1ife8EDEi/GZw7ObZqDmcnVTsLcSxsuPMHV/gWY97yHUOp066nqQVy1Oc3Op
ZohupDcm/Q472peU2mLyQ4a2gyLMhZTwQEboqmQITB+AraaOKu+lkLWtRvJHVTRofqImKKWRuaKT
Jj0QLuKI2sKS4Z07qTI+1O4Sn8A399KAv7HSuSEUZsA1pxjmCkGZI6KUC1OQZBKtuE6pZcoIQFbI
8aukormO4gVMDY/bi4RuPpQrrF/2KSRv2BFhpcYHpifC3ZhMhPTrJQUe7ZtHEMH2ywD0XS6lRx0r
jfWOuAM1X9n5A14b+GUTh06BQwuePdlpKlKRdfBnJKlY2pnqWtGPZPBO7zHDoo6eBPd1GfI8SWGV
MNb69ENaQBF7eJZFDxG6whQUnElT7su8Mhg6qN49lkxJuqpnr7oY/1y7pYBUjOfHbS3p+sum1p8I
5bq2SGXm6VVebPFu8nqqarMZZEzSe33Y1JcraW7qfdfeQJR0I4phYllCUCaJhkwrUUyQsRE73Z+P
NT68me97i2Ov8h7Fm7llAD8yNlbgjn75NJ5axJFXOO+ek2PPeA3yEp+uYNkUnqZtFZKVSjcmbxYv
4YnxM2qbIrN7Q5Qc96qROfCfVZ0XcEbHK1Ng4RSJMJ1AoVhPQUvlSLdqVBaiwrosJYpOqoldo3qC
nSm0chS5hDBYp92Dex9L7WP4tT4uptZN3JPMAm6FBBQKprkfjs6MrE0X604Tg2khqTNfERvz5Nbv
2Iw7ErsDqa/OWEPUVtN1XreZCfKnhdR/C7YCHcffJlmW9pj0SbkS9cI6oO56Nzeyqjs7w1EGEZVZ
x/8QS0V1um2JwEqxUvDBh+JPfS43j/o8t0oWIQa3pFY2k59+BGuLMk9xeeJtPrKc2Y2wWaz6rr8t
05RfGJx123e1KxsxnweHeihQ+g5/rHeVYYxotluzrhn5RvHmPYw8vUnrQWWfTjyfdERuiM59uhYs
dcLSde1MKnU+oW9l1DaSImXvtXANJMtPlrCT5RbfUky0QV2njsyf2C/kKa1T5u0hagdW1pFjS+8M
o5v29cZZRs6LM57eftr6oy4CncHh7l2LD79aQ3tzRmacQM24xQCy147zVzIdKoXF0739qR8LHNDs
D/tsrqhzCWChZPpw8ybZZcIuUwfV4r94nKttLS4WGgh/nwfg+9gynbzmxPr1Y45k7WAnhtNRZV5G
Rj/vDweO4hjqrWB3NbjlLV12gm5KzpUuDKMW2oIlTdZy7vkKs1dYtQG7cvpEqE6Vjmija5KqGeCI
dTOwNZ2G5b3GLTNGJlvlSWEqBoXl7rdiG3A9JiZ9Y0147YFiI+pDROaMa7VJd4LAN9TLq3NKZt4m
GisoIRPWKubUDimkM4qjqijyEnWpnKMxA26P5uOJED2csbDbyCUDVjFsNST9yaJwsuSv9jeqFF5d
GMGWzka9jl21zDLFkuPpYhl215Hu7eQp2amTQ5XV4qT1G2DIddo0dO4mQB9vkp2UKTXKyOB2lZJs
Rwr+6GieaR/GCP8JcgX+OnD0v4BcgUK/1/4Buf49IP875Ao8S2qAZ5k+8CzLB56F+MCz9B54FtsD
z/J64FlODzwL6AmBZ9H8KbfwfwexAn+dOvrnEKuLg5UtHGph62rOZ3VynU72cJfzIirCP9uUoNMW
rch5eRrgrwND/0yxlb2lA/QnncLnCHexcvmNrvkfcLDT1hBI6DeW4Lya/wNi6U8ln4uoOdUMFvtN
s9h5wTDgrwNB/xoUhTk63LWC2btYmcOd/zeC6ZSnPu24g4BiLKct7PPK/g8Ipt9E8584+VxcGFDw
J9EKPPHDKX1wXqH/BsT96QdrB2dnOBTmcF7/nh4joJ97DsgCOv+e+3Ww5r/270/B5yfuICeP/+R3
clKcqj6v2r/CcP9JLczOHObsDLsDd3U6/24TZAGCwSe6QSxA0XO74depmX/mBouTdwzMwgVqC7eD
O1ndsYLb81m7wuxt4c6OVvbn5jFFQb85BAQ5cfX53fFXcO4v9/uvdZ/rposBf35kckoUn17AeYX/
4eV3gQ0qXWCDShfY4AU2qHSBDV5ggxfYoNIFNniBDSpdYIMX2OAFNngqVeYCG7zABv8/YoNCv0eq
f8AGz87lX7BBod9jTNDpQ/1H+Zek8F9jg2cn/x+xwbLEESf6atKQtW2KKuWQcNxpSWiR6tBwuVHU
cpCLN+s88pG8jT3XR96PG6vOHAJJle3RzQzttDEunNy3wwIXrZ72LvyoQeh4Jx1rk8r1E8vGZQ19
uMvpmiB4GIzNbmWlxK1sQHe5Y3njIebkHBHx6/W1EX3pWjZqaWRGHgcfn9znMGbJjG6CyTs7jq3T
eHukTRrsf2PvPKPh2ts2jiBNiSCIGiUiJ9qMwagJ0Y4aJEaLzswwGL0TNXov0UNCECW6MATRRaK3
6L0MIUYJ4Qlx1knedc6bszxnvR/e5eue/eFa97r3/Z993b91bemWW0alRVi9ct4SNwwc6n43OGi+
D1nFOGmy893lgi5zsLNkNq60U5BRWeR+Vf2YqzbcsGhqewCLIija9ZVRUy61oMyYR0j07QcoIlcb
ka3qyume1MoHfG5qyMuSjdutFjabN1HxSU20Obq57je9WiKXBnsbZjZ2EogjTQtf8k5/7cXwQLU6
OtzAU4Z3OrwxgnwaKgp03dKCwV5MbUBzGjThVJmbqnKWk3gIPcHEvVHq54qiyZHkyzYDZ9L7BBmF
DAK1Tcs9IxgM0HtVir2D9YMpfiWvi6xhN6IMz8t6dTS072oz1/BJ5V168YHkqqh6aNM8SYmmUVD6
0g6Ty44goKLGPZs3Qdhv/bLeDXjm+WzpIuzzOVGLj+V+a9tllo8r9WMK2yTL/KSs1J/NJtoUVxmi
qWFy7ukLDBWEDiMplxN3eVU0X633M/1sTR8HP/RxzzkfA18G2jBJX83EeRJxQ9dbYmdNs9emXF4x
fx5RAUMv96vay9/sDZOPaIgstHTsyxjBfUtXJUOfo1mobpYjrMX1/jGXs8NllsSndhQD6YbUD7fr
0vMVBnjMlFU1KIJHaPufsLJv99AXAoiiNzaXiUON0SHyrV/eJV5ORQomgaLSLCfiiI1XkrufWZEk
hgQIAQyeDXiML+hjugsFKClKQIXLEKahuIGyOxffht55ImiMM4fgjpiApPQtSVlFcOsPgFwNIM16
dp7iAmCXHQxs5E6czS1mXdqHyAHvSM9KdXctv8c4LvLukKZI0p4Xo58cHGwRYg4VkXAx+03SKr86
tPi2JX9Jx28Pc2tG6QIzDOv8O5/FfcKsHFxRaIknrZfhnjXtdadSEBEZggak8zrsibt/vBsaWd2D
JlbZuMHyggs10am7qOHtvvJM4zWwMgThr+Q4VosiSpF15Ikrth+RR66pvpOKH5pcJf78LiZon9c5
Urh5iHIMk6gfFNPj0gTeDPlARVzx5Vz9CzCAcAzWTd3flApSyBQ1bBX8SJ9F6DZETy/6NkQemnSv
TgH8dmV56AsHCcJ3QSBvpaU+UpI0P9EaUhtb7DU3MJvufpeu/Uoo+WAesbEhIoyAIxifTWOWUKxS
v4LvXD+9uSJMQl+hI0ONlYqxXPE9VHph2FdLDlYMYyz3pVKaLGDJtVBOt9ulrkgQRW/enW+KmoBg
xcY/ms2sEMEJWSDIHbt9XuWJn2SBjdR8PnE1yXl6vLVX1H6wPJp2P9WeLArzVZEzF+01bGqsFjtD
X35EL8lLZZUV4xZqmS8orOLB4NUh3y72y+V065Qj6PwemLdZaQ3S6pSrtMind2mWdd8neDl8mabO
+xPTkl2qhUb0/msE9lWNskchJSDbkNxhq9bimyhbwR4aCB8T+S73+8iX4nW80LPeCAjh+cot32Sb
TPSSbKVtFesIG4kwbHlHPmNOym4y2XtJ2Rq8oZydXtbEvs1oLiRmHtC/ahxr0dJMls/RMjym0zGq
jUIxz83NvWrVB5GrGaTSsSeljN+Ply1DxARG+psYrofCMSWMoh1SF/B210qHzOeQeVxn7F94YwiS
ROTxUrkNKJm+TweeDwi70TN02VhqecwRcFaz2/rWE8GCv6WDiuA7TaLSC3xbWbopkgH8/gkkd5wZ
OhXiPIM/oW4KzEZ3eBOOkom2uxO2ypBa3zXy2eS6MZwH8FSD948xWJjVsImoDWP01VGUwSy2DSPQ
IFeytvyyqQa4pnBuNrurQ7Ymde0zUZtcse42boAgUrgnPX2Aoa8EPpw9H2w5LWHmDiJXhjO+sPEw
Rb8GuDzy2Exh0C2ufaBknQi/oGCDCnDKnXcueR7jPFQr7uOWod7ld7BdUP2UoMOjn4aYI8RiwjoY
baclSknkozuNfBVA0tPNr6GiQtyfk/VU5LqeJv2SQYB3y3zGBbXftlr1mZUkweRZzGjyUtwXiesd
KNsaXvSovt+S7OXNxbaV50blksx6+ZLLdm31I4F2N21cQZRJQ7YbBcWbhpIau3DIx3Impjx7oVvm
vKBbInjz0ProZhwU6VyV7MZWbFFOOJ6ecbJKGgMnq8rB/p7QhyWusbOCKuO0Lu47FU5aQQTsgdEp
A2TTdKTZaQHphE86LGLvO5RQ7fBwWG00LfBtlyGxjcth2wd77/xaQI7O4JuvBng6PK0ukd9NeLWa
n5d54FWHtegx/oorakyTUs7fmjFNh/K2BnbY1iaHgI/eKydIzTaB9sOXZb1WeyxCD4YbNon6R+Ay
yJA6CoIwFES0D+TJlOAh3sYWEua3wa98rcrLpfpitlmeWBD4bNfLhYm1jO1NNPXXZfa3awn6ew0p
hbdKmeTUeEpHbQlvsU3KXOND+RRsQgk/87FCzgFWINDKKzfhcXXCaeBI3jjL9aHnD99S6uNRTUzi
mnA8sG/L5+on3+oVpkJGXTK7kzYrjXAJ8+0KWx6Vqulxo6bakNK78rX+NehLpBXR1/pW0Jd0nsD9
ICsx93Shx/t6I977N9rTRNOpO+l91DdMhJJC7uwMPK5z5SR+DKcn8odTEDZfpSBoWWQnao5nJ2hW
SK1Svt1kX4yO3Fp1wx0LlOlmT+krCrRL44lkTwnfsdpZDdBSlU0Z0gXv/KaxTVAqMb8FL/xCtQ++
ujSZ20Sqiu3Kn8UAhaXs7UpgVGtwbqotfVrf19k/oOsK1cGHvyljH9/Cqt648bsH39hFhxvptkZ3
1G2jwUYKwyLj989+yhfmWdi7mHc3D3JQHOd3tkfxBvlwA6LEcQ1RfYEzfd4NtaKFX97gg01BPNOd
PPV7aqie6jjZU6z8IoFn8RxOQRZBpUb23bnUTDNzOnWSqKzq7dQ+teFZeB2tD3X4+4KM6eo0mlJJ
LPDz/hvU1l+MmpSWnNdRgTLbYkqmNou39yLWqbBKmzAAK9rae5a3tSEG9+KJbms/+sLY/55Vj2iR
agQXowE+gwmy8nSKmE1NVglRsoj2S03uDFZSrKPpsX6NvSgT5+XU0b1A+QHV48rtCStLeS9jqmj8
rCTftyFYEDDp1FQ/aaxSP0kqzSm7Qb3jNlpKyYPtZTEqnxnLzIt5tNYc4/V4rIaEbJOqopzVYja0
19dlD1GhpaoX8diOpU3SFqs2ya3qofrbaFmbwSsc0KtvB4JXB/2wOtuv5Setd2dWrahei2Qp/fRB
8oKj/tLAfVPFQLpCoISux9QIG/eylRaOQuMGmEOQhvjd6vulcA7ehMUGmhpTrqoBmJOPqOkHomVL
XEe2Hm4IUFKPrGDFjL6PSB7Ih4oMkCoZjljSX0bU0+pNmXJz8pITXOTUWKLsCpH2d62vX3Rg0YOu
rAmfHXQJQlNmTklg+1aecXVg85/y27X8yKk4X+/6cEmLPtkbbGhiQ1poOkNQCGw9PygTL26nAGas
vE8nZifJxyh43rq5YwHf8FuhB8GKmQYF1YmsGzKre7RSxLJ/WcIw9kQfR9u9rbCRMyvTihSRCzbr
i+v1OkKFirp2sg/D4+HvGgWm8z5FFTYA19etoyOokGq3xBrz08I+nkF37yDeYiXvonblPRzjPGp2
uCr2ied6S4d5CcTdJUJbPuDG3NpZL7VjL8XRvle8i52/Ju7bRzuEP8C6CrRjVg7RD5QtpWi64gr1
vUxMLEw/6tGzmmdB32NQs+DeMHEtI43ZyNl7/Km79qCC9DizhDkkaul2o8+L5ucEM9uuI55NTyPr
D16CwS+7c7r6YJKewwJPt4Sf9F0KzSGiS6mxt7DYN+5etXTV5tQsgIhtXWWlKCzJFn4Kp4l1uul3
YFUetIkxSb2f9OTegUjDzGvu+1nXw4Gd8Y0aF+hLsl699vZIBrLPstyK+dD4HHZpORmqB/19mudd
u2EZUCtoMA3KzHE9vbnB0WxaH19WK/GsFMf1nOYGnLgKB1yTCv5Qo6NfcWLK44IYKS4+mUUU8Lsa
Wm9ytVjLtus2Xv4M5At2FzUIODA3v+qVkqAwobmUA4loFgjPenThjcHiUu9XzAymF63qKsYDyygI
l5g3zHzb3vly2zUKZxF5C1R0kDoD3vjsSCmwypkfM9Tdl/t6vPKzYu26hITAV4qu/hW5kVUn2040
jheiDuPjYCaYmJWgMILwGyseNYGKjIUz7nBeiJ5zy8AJXC4rqVPMyTnQtVbLWTyX0PaaRpfiTS+2
gzZkpMNBk7Xq6zagSjzozHq5liPJzn4nX51Tp7MUA1KIZ23CtnJwc2Lm0ZUHonYTr6iToV+DE/c+
Ei0YZK+BpsX9DbLfXWXyklx4MPs4rC947RJa9nryMvJyWt/nHtEtvZ61a8rNZ/Dm9C1D0mCXtBz0
pPullysluhK2E3i9YSNrXLKT0TxyQw6ywWxkBBqw4EZw6Z6hpbZQlX19hvPIB+cJSiPNFTEKDn7x
52rlScm69uPySct5aWBYV5tDHE5oOdwtZsDL6Gwe/E1EnLk8EGmpBCveQIvbhJBk3TCpziyZ0rSE
ogZL4dn6020wNZaEHtXP0itZBOQacLpW2uggZXHy1B5FKWhe0mx4j3zLdZAKNpUT2+CzBzcNYwGr
OtxIgXO2SRAQcySThHXcWYVqrNkNqeIod+x3gm+gyIvMPIg6uqQRPGy53TcQJBOz5cAF/EDnax6D
7fPIfKLpYj30m7dGe1KXQvPuWDKVXUWbCL9+UF0HYGp364JRr5OvDNAywtRjMmdWnzdX7Q3OYmpn
zucrOsaK+LOJUSxQ1F5yx6XE8rMrzP4L3Iv7J0Dkn+Nex57dj7gX8I/b/sS9ju1KwLFPCTj2JwHH
xiTg2JEEHFuRgGMPEnDsPQKOTUdCwLHdCDj2GQHHBiPg2FgEHDuKh/vofxEH4/4FlCLNBeb913K2
DncHRymB4BNv8I/K/Cva59+JgjrczxyFMH5TfVK1fwem/JlixgX816p7GLx3WF3ASYO2vjft/1F1
ub4HbR2qPqnav8NQjqvrZGRoaHTbzIjdxAqG0DMzhJ042ZCf4XAHB+QCMRzuuE4q9+/Iy5+omZ/E
npSp4jkiwIAMPCcnwAC/oC5VLIxhhzygOczA6L9NMuM++nA3kJv76JMKJxX8D5DLf6l3D9cPR8mR
JwdEAb+ALb8Hrf1Ifx0W+sTT4bC6h6jdIfp18tn7D0jLvxB8MsjuEAr8VulDPpT75PP3nyCX7EZm
jtZGRuyWemZ6/20vH3JqABDgO6fGe+JePjr7f1Hpn1SfvJu/6eXhOnr2DnWfVO8vzrkfYgO/k9qH
/7v0/ptUSTD/t24+xO+4Tqz5H5x1/0PrSZNm+XmPmhl8YlgU+NNJd8otypxyizKn3OIptyhzyi2e
coun3KLMKbd4yi3KnHKLp9ziKbd4KFX8lFs85Rb/P3KLwD8s1J+4xeOx8wO3CPzDvAQdvq39efkH
i/B/5xaBf74A/xh3qBlLWkHilqLzNPOZfMGDrRgHT7wiQWddBi++XSxHrik6S/1QdefrYXtTe4Gq
C10UZTy8yy3JwpYZmnkcWdmqGNf7Jr2ZDX6+0ELU9bTk9gPkAxWT817u+w3SGprKgfF9vjKAsURu
zo86tW0fD3ZcHpCoTtfJjpNEPXteck5gwmt11lqc/4lOypoljpA3V885ZaDsEzTtbRDp/qVWyimH
LjKdio25r+UoRJ8zI2Uk0oCEt0+VWilFlFq9X7CqROV3hWBaGhE00cvR+2rDCcO977SLXPjW6FrJ
Ej5d15YffLSmalnAsA9CJHqSqFzLim4MZ/PjjLojXu/f6G6D3LfhtXkBvNIxGUDZxGbCpoRuLNoZ
zDdJfNn8pGA+4hUo2tOsS3m7TSsFOTXvQCXSyFL1Yk0DnI0knJicMvryJfbsNP6e/SUSSXb81hpx
XHxeJB7cU66kHmX/bhAzqPMZ7vW1goes2JAQ/z/s/XVUXN2CNvribiG4Q3APVoUTnGAJ7sHd3SW4
uwV3d3d3SJDgDiFAcBLcDvX2u3elz9f9nR7769vnjnvzRwY1F1A1a7LqqdT6PbXKo+Bkt2OD1hZB
YDbJXrE9JOZNLw1ce89+CjFuuGwdjQ+FfNKYdt06aUD8PEpG5IuXSrFz1oiNtLMvU+VUosSWWN1h
ccmO6Ho2GrIri4psk+lcFm0RcooDozfLDc50cxkS5kmbABMuX3A/KGAcN8DEiZA2wdDDjq6Yihfo
/dCRNmzFz+ngnnCsU6sY0Xd9fbUE4/aOtEmKrZ0RGl07KgogRRXfDc+xn/ydf7HKOk0tnwuHTgTv
tO0O8L6vx9y1G5LICZ8aWwTGkoGrQjHy7UF7Q/CBkjOmjpoxk7YWQyhX5NzQmLNpau3eDF0qQfuP
rFyswHdybi6E/AG8CJkwrm+2SriVtySPNaJ9bVQApHMTHTex468rbaL24rYnEZiKg8qdJKw2Xtkv
WTUR2sdxtmKk13COJ9fxkFN22GeuHjXy88VH3ShYvmSqVNSnG8ZIUi8Sfe/bTV1n/XIM0fyrq5dw
Liqjv6gDzVSf7tPLXASUsH1PH32nN+WZVidrpGNlpn0lbgUpQud3XVQqHLtf+xUi3JDurEIDQ6fH
ypotZ4bNDuEkDrgi00WRiCoUCeioilm3L87qCRYKOEl8hDVQr+Zz1F+UEokg1PmfRAp8UiEQuW68
9Z5npP609CNrPvyBKfXe61HxTDyec1IhyzgyyXZjH5enVdoE43qpDWXM0YWgt2jCNeNYWGTrbFxj
i9m1YS74h65br+xlxcd3EF0Z9vH+DzmA/iQIjfcz0Trmew9pQXI63Lt8ktV3Hv6VfGfYpfqdSxzf
nD1s/KjjIwCvPuVXG4dT2w1jRVH3zHcP09Qz5Ijv2nyWZxNjGE8zDbPZf9tSkJP8UoAHc6JrPYGZ
rybN48nGvmEBlZDGdClh88YP9Uguj/o7oQ5l/ZUtgqNrtR2xXgVL3yJUGtZTZDJJmoQlbzTreGl2
fJTs9vvjhcboq91Brsfhloe19csEcXhpIWZVYPPR6Du8tNpXu5eE3Mv7EdGyFUaXK6LTZ1ou9wsk
FcsqRo7myybf5GTxomoRNiXkjnI6j5QGi6gJRjMJzuCMXlhHZSyRJxwpiRc1+qbycrJg9XFcqeEE
8MPIpH5KLnSkl4SHHpDks4Qe2oLMiO4XCcIL7aPURYqHwKLmoEkXiZnBgn0qRiM/iYTIkWZDILEp
G1sMp9m1GR5bhJksb/W8/bkToZUumMHvekpmywSd7Z+hvdor102H/esDs7Mq6ZN0TK6RE8CPqLIz
JrQksyqtbVXAElK8TLd+vdzZd6NZnXcwiPigOm8bfaTKJRxbnau6pOSyefXQ2a6NRnC9nDqo1Vww
FUlD1Qta22qJn5eFPMz7y3zbUWELpLYOUxKq+m3ToGYbjbwumUZ5t4+ymP8uujvKi4g6vVdwBvRq
yqrjEnSeaOnfoPMhTwtcjqw4beaiHymolh4r9U+ow4BS5dScor1tO9TVNT/uYrbOG907r7cS86gP
IUcn53nE01VVvIzeJAY8NuHC2tRa021ZXWwbhh3XjGBZuVDzDRjcL6qEl418VVFdJmY24kSNjsYg
UbfqK2rCs4Mm/1l2YVjKqlEsToOp84B2tiz7Y6qbCMlvJkkPyeHbd+/Y74VoZLJBBB1R4wCdzG+F
p7GxpSQtpaJ72ILyhaxGm/6B8JV7MALoch+5N6gJTkqJ3zpd2HksB5B204Xu4wiEa7w34/V7yTsE
wy4pu6Qb/2ZS2mH8NXXNacO+eGpjxCT/SVahBrsEGn3/ep6o1qmqGVkwB6TmCzz6DX1WrFxjBtiu
t1bZ0sVcZWkpqUEadN+yhaNc0HL0iBvQctAReivRJeUk3k0cUDNHj+bBkelb63C/sI+JkuQjt3/D
PW1exqe7BTPvttpjybU1s1msQjZARlSzZctBy2F2Kkn57u74kuwzvh7uUHo1spL4ErKY3BJ3Wuzl
yoikfDYTquq4cmxj6+XC6DtY3KrHS3MBjxdvXM1Li+rCb3YsoSLdZhVU/VwKg/v7+jJxTnfIU48E
K3ABL4lDtqLa4czLnJ80jvyi7QO2GcweTNJRBDk7cztj+bEqsJ2fxC4hoGJCIb4BquGFkO+YDnug
238OU5y76KOHRDd+GCA5NeO1ffBb9Ed0PLRYgCbBH6KwQqAntkwzzbsk/TrtA3UB81VkAyddkQkZ
xgn7F8/7MqaS7c+48Mf+StBZIv5mTAtfDUqgxSHne6bzMkgwk2hKGRH9OpRCoBDF9EIDkFpjA+Ls
/QKQRmMDcutFhal2hIQz7KOet/sF5FY/j7Xlhd+rUeQo5G9zmpYqYRFwRdiLJ+invCzAMDK0QrCv
/aYvPtcaE5shxFsaRMRKMxkVUv9TX9y7mc/n5hus7486h/NsSc7pvfv2/guR2jaLYXTffiQ9mNFG
Dave+/pMsnNG1ZaRsn5ay3Fa3QjUwYBLqMeb5L36XuDFu3zV1gzCYMhtTgiY75W95+ijVi4EMvY9
lBvMtyGiUFDLlrCM37Iy+1H0IhDkpakuKaLfLjXKLRXvt3v5epYP2itpvM9zn+D83MwU+lCkzhyr
pzTLp/PKfRtiGDKjiNS5DBUDQ9R700eNRRULf+Qn7uOkyLFrjCiWPdILyJFeQzZmfBrI7+RHd4MX
3U1Etj3ZlKeNooSnOipQml6PMvOyrGuuy061XsvsQGuobNl0IQH+QY70t6+BTt0cj5loKd91hXrI
E52gw9pdhPChBZM8NMeCu0kDqTZY9sQ35EdhN1hoJTaipzFPkxOgT11GuZ+3w21E9z6PHflPJfQQ
r6Vjo+azWav8MTqD13Qx9to5xGrJZGtGw5dtsfpHttubnehZBAJRm48S90JQ3TcOIH9OlO3umsGc
8bHSmnD98BEtspnuzulth4RFYfqOmlRdOb0AyR785BVNBHmaTCzoXvhgHR8ihNLIiPby0ILmxSkJ
QXdELYQsq9O3jMOc67Sjix84CN+NnWa7tS6vHYhmG09dpKtciE9fQ7BSZGQhAOuUyvIm4RcR0SXJ
MrNIAuxuo9n4Jcem6qpSSPKxuYfOZ/rICwmhnl4WIge45ORMwMt0oY8WCLchvSMJEKP9ckBNGz1K
RfuFgYYWfZoiATfhVULTqPrzdnFa9N7nsSN0ArwezqgI65v3N1ap+FBbPY36vucKFMLfl+7KaQMB
NG+nxoaX9r4ZjtxFlF8wj072VJmeUOUXMzVdaR9oDM1d7Bye3y/eHFLo3T5MeCXhZPf5SOqcNKbB
bRBJe+w/calNE73xlM9c8RTqx53Vb2BxujWo9ZX74ObN+qJG1mmW8YEFVT+qstM3Ev7BZ0HtoJVY
/HzCG8YbdXJwAgNG7vgIcobqPcrIJqH7XTYqpeWjhEcD01Ak4dSVJ2yWQn5cKgaZUIxbreWXudLR
AmVK5SPrCh1aVEDmqFYte1zH47d7sVZC1FM4FBqpnQGS4sU98fXP+xCjsYBBD0WEgwkv5CC5ozPp
n63c3V+8an2W+bdJoyeNTrMMtTRVCKyzZKynoHEIRugL3FBSxp5+fuh6h7a+6WfS4PzhmA3Rv20H
HWBxN48qfYV8d8X/hC8w51yJ7NITF01sFkykS4PN9qG3EyZSY7zW+U1deYzQWlG5FzklI2RupqjS
FSBUWzoVaD2XFrGyzHJ5OS/dNq67krO+570+hSShD7mHFBWm7gsruPdzyUPKrTjhIjEdFu9r9c6b
AItv9HOKI3h3esu+Ejz8GVwbLygoE0enU94GHlBhI6jYsig108mw3YuXPnYEHQe6UCd/QLbIJ9BZ
DuflKGAu0tslpO8USlYmboHAcFZrIiattTIrTtOrocCCS6RDwC0EqA2RjffiIUg44gdk2MMEvBpF
6WWM9LOVWfxoW0QEtRlSCauHMygELJQmGxeG0HsPK7RwoEFEcqxIi2XN8lq/Xn4gX5vSf5pZhdyO
heiN3dVWTPMVLeZ2nvsW8oaqii8NEiQbQlcDi0FOSYRqlre3WkVc24H8PJpXTi78AhDOuqf5V4K3
iysvtUvwxONFwqaabObRt4ckP2lqWRKBpqHvF9U03Z6jH7sFoL1bnYfl4mtzfOw06+JnoDwMTL7T
tZYlZvysDy84OcFUD+/ppOZZXsoTpCh82yDxhF4WXZZF9M2lTFNdeQef4MXCLpLoh24i2ZqpJBmY
U16gJ4U0CVnL55fYCxjJnJUy8dW/avCuco9yV71fLXA34H1IZWbTin1ctCTk6SRDeRW2tUksrJgx
zRXSb+61x+IP5Uy151wCqeyLR1cczl388UwtG66/7vBN4qEI9ha9mMc53gwkQzsUSTVZ0ybbQaPU
8s5YTtN0KNUKox5Snk9Lz6yTt3pgKFMi3zYZhg8sLExsySxMV/1RpZGypG/KcRqad3Y+TBBTvs5X
3GLCisG5xFUGaUVbxTfw0CbjYdMJGEnsY4Z+b8KY4hkjttTU5jfxGIZsGcsPbcff5gFx3hsT/Rx9
Q4R8wBalroc1RNGKM1TO2izzwzWfG3VyzFseWtMrh5FDgGCGNSJIWuRd8sxGQp4ZAr0DgRp3ZlB1
raxIEZGcyLv5Qj/lbTOEAwUCNUBmUDaztPoijZQOxJguomccJge2DaK01Ib1E1PN8qBmLu2pmSPi
w5b0hnjwUXhl3VlypaXJSzntdUNkmKG7NtJjUi+Lp0Erhp/26gkjUdHA1JywRi3mvFc+ERJqoV+/
MY4iQdc9+BuR5uU93Q6VGcrTBmDrbM7sAT6ndspbJwjVp57dM5VzNutg7WAmIKVsPHhKfoangeZZ
w3DgMqb7aUrNKBXDXHkqKjNqVWchP0Iaf3Bxu5ApF3Xx9H0pJI+6x2rXA/KRdjY+QQcrOujgrTee
y44lMMDPb11R0XVE+GuHr6NeDGYxQTOKLA8uvLSRpfaal8DhchfEySnDF3x50UCGuXKaj5L8AooT
bgrNEWr2SY3h2nWL1BOs5CZe9JCH373o7Xll/UKGvAi4SB1GSZd3v9W7WU3hFnfR86Hnl9hpoaFE
tGbRj02ozVd4Xj6MiDh7XjKpKsFJrFwzOg6YKGfzbv+EZeL9FVH05DmGdqxqjnimGaI7FGWGG4Bk
jclpbFwoQ58rjE6ohrRUJ7aZ+UHZy+WzrSATJH9AibEXxioFOdLbH2e2C1S4bgYUPanu8YroybgB
+fN9ZU3bOYB2Isw7zDqTDwoRA9t1LC9g/ZvSM9viSv1oy0Zu4jAJXY25ez0DUSu7yEIacqJ4Pqhq
o8xEBzftttRu0XzQUKFPDnF9amrVd2GuYDDa//Kkpjo+raW+aKAqllQQ+UUbexa2wi+vrooC9iCZ
kWYXudR8A7duaLGUQKeK6U0sPYlwCFu7tJJ5Y2n9qto66TK1SOdl9Ie0GYumsIwzcaVzYRuOQ6+n
NwI0JfX5i0VxUQJOMuFDJllIFRMKMl+g9KuwCxpz1SI/J+fXnuDG39wooVUG374hgLivOwz+cmZ9
W+CwN9ZaaSYZ8tMz20L+HlH7rHmxYeRg09K/FQECSLgb25sU6U6ZrQDjDsPXWMysR9soRkpqzXze
/451EdtfiU5Fk2AvLX9DSGMCRf1Hbh/M8Y3m+TRRsBai6yd6WDzXezwKMW78oYIe5s6WHqZuGwO+
OTjhFdqgsf1xnNz8dWF7lIBZu6BVBSyOw5G2hvFvXoP20Wd5ZlUcr7W7T0sNCvmpXtEp1uKP8RPA
J3V8/lr9KklvDK0kY8d9zRb+eM6WuP5gUXyyMm2H8pu6gEET4ZPuXJnMEQ8f0vJOj4gwCZ+D80M5
VJuOkf48+pfs1RAlNItMuDRs55lJbKt3e6P0jESHWAb7MWhy+dBqpNLBkq+TlpyyI8qhPy4hX9aP
RgomMDdEcsmmTcunEdAMs+xfCfJVClDNX5WhjDJ1dHg3t46SMezPJg4sEwURa2kSEvB7b9ZDjy3w
Zk6foC9PtN4kIUKWjkwcHSmKLw1OmN5CesLC0zGmiIW+cgWQyRySRDUMXTYvH6ZZUdh2R67T+cq+
ujteZc8MxaA08q+HIDZC8vvCyun9EFtxuUZ+yBtQ8pTeLthutczSzTtt0AgRl1IZf4cjd+dDRfpp
xqzuZKiAqyA6/Mdx2aGXG53DBgv1RPxyGjpDGQKt+CYMaxn99COVl2WTz4Pie0p1xJrxLDbYHKg9
f1iWHuRRji8b+omXMmmtSio3bd9dFIxlm6ETIiFGPyXka/1KJH/zrv2B0H1quGJ96PIrSRdHVRp0
593qbp9Fm1XUEYm/vUYnkXNU6Is0eBPyFylJUEPGVTfCZYFYStCSRcSsmB259UzV3vTDR8BGGYQu
74dWShs200ssLQrnZhs56dI1XJkUOd4nQ7Q+Gepu8u4uAkAo95V9ICv0F/u1xQD6g1fcJX7XITAY
LSprgiLnb2fgJ+1aAzBcshxZAg4sRBue5DwW5JAWqRJaAt7s3EQx9P8yfqr10mw6+DbfF8vymYrV
EKHi82akZbvEZ8ufbwKfiJ25NXJoaXylAplv3R/C9J5KvByFKbk1hUKL5pipoQTnFce8MBsbkfMB
PEZKeGiGSvrpBGyZODyLehZwNxgzp4ikFNZ9vVHLzefVexhTRs5bCTQJg7kSoqmIcNI0+QE9VIWW
UsJFfBvYKPwvVnt6uTfh+h7YI04Y0zfubDcR2eWxwsICjfbnkRkqfAmCTc2Sg2KYd/0Sv+ST54+7
VY/uTmMoNbqdjtZwBDhakZT/aOGAcaJDV7nSIhBuZWwcNSjl+Iaz4tU/1p2GCfeQKmbcGnev6QsJ
oe76Ufw/KNSz/7vu4n+9UM/xz+PH/yzU/20vvxfq/2Yitr99iO1vGGL7G4TY/pYgtr8JiO1v+2H7
G33YOP5xNJjsv7Uoz/6flR//rrjpWenZ6z3frX/rjP0ftghBNRdQVx5UovjXu/Ls/1n78fdG7N/T
Zvo/+qh6UF3zr7r8a/b/k7r8X3/q/80am9jruRnqWeqDaoSWTgZmRtb6evb2Zkb2/3IxFgTwf9Xm
uf9PavMc/1n98fdi7P8y33+tTcj+b815UO3nX2/Oc/xn3cd/nHzS3sbMwcjR0UjfSE9Iz8XhXyx2
P08S1Gv5tyb6v1wu5fjPav6/re7vEzYw/ddX93nCbMC/dmPQxP/VCf9nRX/wuz64gP897/oAnRGT
468T/7Jz/Mtn0OX4z6r+/5vmvMO/1f8/WOlZGxpZmhk5fbC3cdOz/GCg52BmbcNs6mhFh/qvPB5B
tV5QfRrw1x37V+/Qv/BWgP/P3CFQ+xf0WP3rH9u//hD4d8+4f/q/Un/6v1J/+r9/+r9Sf/q/f/q/
f/q/Un/6v3/6v1J/+r9/+r9/+r+gqYr86f/+6f/+/2L/l+MfB2H/Xf/3Hw9RcP+X4x9HPtlBz5L/
3PzXD/6X+r9/h8C/7//Wqy46LwMxva5UN8yCxkVNDylv6cLyGB2I2pZV5OSyDElMw6X4Xkmv1q4c
P96V9PaKwcgaJemI9g5AMZciXeHI1X4oq+J8bXgXGELx4fFnfnYjJcqjE4v4dC5lIK2pXgrlWNvL
7xFXgNNaR8FoGvw3EszpsCRrUkn1GGtDPqd99mYINGMsNCtVEOjkKJwfscrzyw8ZhThfWr8Yxdtu
nkb50OJ40LF6fHDB/yJihNVun2ZOidD2QydB9gHj2kZCnKLiJU5WA7JxVl3akbFPm1uxapZDUx9c
Yz2sUXD11JCE8CDeLYAU3YB7h9FTBhY+e3Oeg3fWOm7m5uZmC8nkx4Dwe3Kk1cXMD1Y1fDdHAfGa
9hRvV6LokOlhW8JFNjFbBDYHpzcnfSJEXN/31dQqbeMJDwT3XV8MmRhC81ZDJExhAk7WIB3RX6pu
UA/LaKZ7qGZ5ct9wH82lZUmL9EjjQCxwd2jpCwzoCWBboqY7SrXgR9ZVvdochV6DgJ8bdnNSXY/v
irkxbyg7OUGHGkMOWkareakUawyP+Y5u9nXqHBdJIlBvgTRfOGkoIBD341JUVq+68Yoz1EyQCIKY
9DXe3Kcw+JdHdjf7y86KT6ett6/gNqUo31G7EyCmQwM5xdnpURXlKWJfswvzAi8OK1u140uzUmhe
vyHGmkmh7DPEd9072wNK0gt/5CfLj77gbOlanfc63kSh65k4XhOFRC57hILP/6qSooTiVs3dZkck
X8ZYIeIBjIJ/14ssHVGAakD1YkaXz8v3blgp1IOnUOGhsrWMVow8gT2Trx++J16IYzgdtuitzFfr
/ebTH84/nbQF1UlfRNVoA3OZokQwNN6hKlvQvD71Ez1qXOa1xyLgx0wnJ/geVcdDQZmx3e66YMXr
Sc3kIFFDV88aFViQLaymT4QsBomb1t9Mx8hQ/L7v7EXgnAhcoHE0ZtjavYToiwTCsZv9XnP/lI4l
AS35WeVuW0ttOup3cE82gdgbRJpqYa9p9J609fRyHH/Qo6Sx1S5dCAVvF0aUiyISRRjgg2q/fWeO
6he2ZpFjpO9VHm4abDQDCKLJAxZ7r8TlkxIPzgSMWFycEi00jJ9uFVZPpB6jd9Yl2AmmhF65EREw
6fVsv+QZLuCU9JRlfmD9LidyXY8fZcDMgUUiH0H1+WMJk3YxWpCEYW04kjDkrbMMtcdPEZsQJkiO
gkLCjoXKNgCqdkftHE+crvwV3NFZvyoQe2y57dNhkzzJJMIIEA8yrpedFylUpMA2AOaDPwXpVOU1
e2u7uwsWVkW1NRTW/HTkbFKQjlzznmTAE0cCF19OWttj/IpSm/c2jGwaG5+XlcjKWW/oRVBowCUJ
jh8aOjUzVIWTletYN/WA13a5IiC+tiWVtZz+5GVyJG7B11pZ0pM5VKv7/tbVta5DICpOUreWs+Fm
IYOIgeko9dwRl73RAbsWV2PSiFOeZLDT0a9aYnUWwuSeUtmsWA1Oe+ASVKB8+ZLeQ60TfiWBEW2L
+QZhPWxrqkaDUfHzpvIlDGPz2fr3v8ZW7FIBznisKuZLBGNm/Utt71DGH7hsTY9HbrpXVEP8Ftdh
xodlIdBArd8mVYl6hSORtfevr5CI2WKGig6PBuztxL+f7Cb//Lnz8Rt7PL+/D0HGA1O6jxW3LQmE
/wy6BQLuXjTZG5IEgpZlfMsBTg66yO7GfmW4rdubfe787FJA4PrbKS7PwLRjbrcWL7X5LtU2bO4K
57SjtdevPHsDmX0r6ZoC35ynNzwEZnXfqrHmqVVmz+p+c/T27my2f0Ob29+M+1mrr0A6cylO88wW
uh3iOw4zp1UaJISh9G0gfHX5vGBcl5SUgMmhQ6WkNRtDDjYNhjWkbMyIIRoa/c99veaS3o8kvYUC
RlVlgt4y3Aw46WLzqX16Svp4OIuH3xVVVpXbzOuq9puOBIIdkmYPcKNnqefVG5Z6T5K8FweEN3Gc
YvVq7CXbDmuEfnyEnAjk6BO6xftMptYIoX24cZfALyCg0A2TFrvInIXoet0D56JieOcOJ3nACVtN
3zZiwra81gCxGe07lYD2arju0yACEuII1xFsf59FdI5Tlub1V07qEfkhJMITzoc+P0RWPFgpP2Rh
9STWLkruEEHDDWeHOm9f/mVL5SrJz9zp0sPl1C1f4X4wtrWt1suev5He4J16I78Bu0ao6Rdth2iZ
ehlJQZwOP0oyzHFElDinCf+DqMS5n3vPaHslfmG4z2x9rcCCLOGBdyFkyW1b6PiW/0nyCjZ6+Lim
w9rf09TsFbC6/oybw6lRkLWhjZfDqZv0U1QMCarF+XdKl/xdXysx2gNAcncDX9qTsM7DbM3xPSPg
3RjLunb6yxgyvGJGhPceIe7p85m4gLpfL8fOuVs8i0dGieMJSvxMroaDVS+OW519OiQu985Ms2DH
VIhk5IkcX6H5ieuhj+LAoJUrNEI6ETUhQ5m0+z4R8S+f7DjbBi0zu3y23CACYDXfH1TeOihXkJdy
tXWuWqfPIw9RwZUoQPiszT1+mZ+1djnoLHfh7Ni3LU5ma18WyrEtOEWQszP1Wy3OG6KcsDD2sE07
9eiEDxj2APgeLXVwW8IeYtfsJIWVQ79jjZqt2PSDwP9Fqni9gVM2JcIB4bWWELxvS58VprQz0ngK
9JeCHaJ++1ECLhhKB1mJesQ3u2ebzn0uCLB7HJPRYRWRPpPpl+Z/gMBZpA3N7rGN9zq62V3HWkux
Pv3yV/mhlUE+39Y+cHF5kNaNspX8HEXTX8ituv6HBMAqEpKoZpCsYEKWUnzcrs3Moa6o/gahUUXs
jXS87kHhq06zO0OJ+UnEyuG7gR0zAcVJe6/mX1/Eou1dx3LSm7zO9ncG2soGMFnwOpIQ6iImnPje
f6byaEnJ6ry43xBMyfdkzoonVniEVtg22wF6K1aUPtH1aL6Xw+BT4IBAYESVQaSBBACFp17eo+3q
mFNkOCw6JQkpG7sWxDbOtEEXvPI7OSWvZaIeM2zinr7vAMw+2tx5ubagffkBuxRe7t5fFJHl4u7V
o2XFoIuoC7cntMMx1iqPjZEi63TXjV9OC89DpkncvGjVQbk673vdWtlu69Wn0xUCNXd0uYr4vjcW
d4ih7JMSfTcCCRfs69kzEalfAlnW16hrL7Ayv4oOrc+/uO6aevFTmye3PNe8fAJ98DUV/hmqAmaG
RL1hP3eIVHVUyUhKXXL8HHcBzatOnXcf7WTeD3pm5MNspxRGiPHkv5mmWMi2CstwZEUCPgwW5JBG
pgTl28iI2JLIikxzF/bwRheRHxFNTwKLZmJ+oZqdVm6bSd7dcriun3FQeuXN8gKkMOkiE45bg2iU
gzyI9fVjGHDQSzeAoU+cxzozP9J4r3WM6qcfuLgw8T0vvb0fze0urc/8yhnsBZ72t/pSVfvrxaVX
ZLgLp06XJGNO++2czm5XnzOUmcWXSOxy7L68zKdYPxLYdF6Els3f15a8+3ozT1HoPgKNzat6P+nI
eJO9yEKmQWG5kgqqB78wK/7m5AKOkjAfTelu4lO5+XmhfTPpyom7tk+yu8OLr22ro4srX6o9uSyl
3DeDxQsTJp0U3uP88OAk6dWoflLa3vxcvOnO4YijZD8sawIXLOpC+Wgl0OeB8SVHVjjx9Ms57GPL
OP1kP+axOC/RqOV30nV7uC7Np30S5RndV755nKNdwi0s7J+kXZ3YA2x4RzX0Z+gKxGE3teQ/1JB1
QvFnv9RDPBuaK2UMPopA+xENwcjn+3HL9/t1w/IrDJhDzBrkQ2eIz134VZ9IivTIblU9ZWA0MWms
OrReYJpsdLJVNIUmDNLK4V6us39wTqNSucJqq2J//JR6VbjHZ0EQaTJdjH9to08l3hmwpZkuGAik
Ct8VWBQ4u7K84SWZwT4sCQG05jAIaayvtkBrW9EVWGQcb2yqbDXnuCQX2WvKPM6iAYELk9FUR2XM
XKueM9thDLmnBATz3ytvPwLV1e9lo+8QOpXSagF5smSrZZelsjLT1O4eH9I4BhnDzj6+hi1fxmn5
noSVg7EVOh/5glP1YNVbseGpTn9QTe39JBHD94hU7KpBi/KUGiMVLNahMG5NfTFIh+fhRLb7DYbH
lgiUbPzt6C+0A9v2PRSCKntiuaZEv+3A8r59pYPTj4d5vlU54X65VW/4hRYaU7CdIlQKw72+2RyW
s952Scf6YimvG/K1vfHK0Sooub/FR5LPEbCVUhYK/8ASL/SGf8i+oNeGpEXEpsbZqka/pxN5x/VW
YW7YXK5dZIDra48e8V0xz2ODSVq8jJ/GqaAcH5y6rBYtg3/euEio4yYjJVvCFjUznRxxzjtnzs9c
i/2VGjJtMnyvQy5M1GkNLl9nTggEvX8g6MDZP7D4mXdwoROBnck12XZ8fbRecRqQF/f4uv2j7wXm
VwDZL8/5Oa6BpKSF20XuC4PG+E+Mkv4tLKSboUOK75wpEjlcBLqH6HhRHnX9CoS4IWk+CT98hAcM
WKhjm8OxZBRB+HajWA5/zF09/JHxAj+5OLhXM6yNFx7QHoNjp+ff2Fyy+KH7A/I3Db3yQPWJy6of
/gQP5bdnrAl4ccl5vL0RXBBBkj3Q8GMiWjdMPRLKnJt6tu+BBwhyxo62e4euuU7ElOPfzFzh1KFe
HEiszGbFyu32IEwFfZOZatknyH+CwYPIZdKP+g/aSZz/rozxX28ncf5jG7id9M/j8+B20t/He9j+
PtDz31wy4vx/6GVY6dmbOZoaMRvo2VuaGdkLGTk6mDHb2Jv8C90B0IHp51e5oBf2ICv4F2Ga8z/r
ZvyjsWNkbeRsZuRsxGxi9DxPI4f/kymDDo6B5swG+D+b87+rZ/yPYfrzCFQC4PrtCOG/p3UQiAE4
fztUyf08BB+q5GB9HoIPVXK8fh6CD1U+71aA3wgIBGIAMAGBQAwAJiAQiAHABATyMACYgEAeBviN
gEAgBgATEOgvAAATEAjEAGACAnkYAExAIA8D/EZAIBADgAkIBGIAMAGBQAwAJiCQhwHABATyMMBv
BAQCMQCYgEAgBgATEAjEAGACAu0vADABgTwM8BsBgUAMACYgEIgBwAQEAjEAmIBAHgYAExDIwwC/
ERAIxABgAgKBGABMQCAQA4AJCORhADABgTwM8BsBgUAMACYgEIgBwAQEAjEAmIBAHgYAExDIwwC/
ERAIxABgAgKBGABMQCAQA4AJCORhADABgTwM+BsBgUAMCCYgEIgBwQQEAjEgmIBAHgYEExDIw4C/
ERAIxIBgAgKBGBBMQCAQA4IJCORhQDABgTwM+BsBgUAMCCYgEIgBwQT0VwCDCQjkYUAwAYE8DPg7
AT2vBvA3AnpeDSCYgEAgBgQTEMjDgGACAnkY8DcCAoEYEExAIBADggkIBGJAMAGBPAwIJiCQhwF/
IyAQiAHBBAQCMSCYgEAgBgQTEMjDgGACAnkY8DcCAoEYEExAIBADggkIBGJAMAGBPAwIJiCQhwF/
IyAQiAHBBAQCMSCYgEAgBgQTEMjDgGACAnkY8DcCAoEYEExAIBADggkIBGJAMAGBPAwIJiCQhwF/
IyAQiAHBBAQCMSCYgEAgBgQTEMjDgGACAnkY8DcCAoEYEExAIBADggkIBGJAMPmDPAwIJn+QhwF/
I38QiAHBeQ8CMSA470EgBgTnPcjDgOC8B3kY8Le8B4EYEJz3IBADgvMeBGJAcN6DPAwIznuQhwF/
y3sQiAHBeQ8CMSA470EgBgTnPcjDgOC8B3kY8Le8B4EYEJz3IM8CgvMe5FlAcN6DPAsIznuQZwF/
y3uQZwHBeQ/yLCA470GeBQTnPcizgOC8B3kW8Le8B3kWEJz3IM8CgvMe5FlAcN6DPAsIznuQZwF/
y3uQZwHBeQ/yLCA470GeBQTnPcizgOC8B3kW8Le8B3kWEJz3IM8CgvMe5FlAcN6DPAsIznuQZwF/
y3uQZwHBeQ/yLCA470GeBQTnPcizgOC8B3kW9295D/IsbnDegzyLG5z3IM/iBuc9yLO4wXkP8izu
3/Ie5Fnc4LwHeRY3OO9BnsUNznuQZ3GD8x7kWdy/5T3Is7jBeQ/yLG5w3oM8ixuc9yDP4gbnPciz
uH/Le5BncYPzHuRZ3OC8B3kWNzjvQZ7FDc57kGdx/5b3IM/iBuc9yLO4wXkPeF4NbnDeA54Xgxuc
9wDQqWJ/y3vA82pwg/Me8Lwa3OC8BzyvBjc47wHPi8ENznvA82Jw/5b3gOfV4AbnPeB5NbjBeQ94
Xg1ucN4DnheDG5z3gOfF4P4t7wHPq8ENznvA82pwg/Me8Lwa3OC8BzwvBjc47wHPi8H9W94DnleD
G5z3gOfV4AbnPeB5NbjBeQ94XgxucN4DnheD+7e8BzyvBvffef/fAvFcoLn+NgRNFUyfXKCpgunz
OTq4//mEARo/z/UfTxig4fNc//GEARo+T/UfTxig4fMS/kb+z9HB/c8nDND4eQ1/M//n7ODmBM/r
OTq4fyP/5+jg/o38n6ODm+u3eT1nB/dv5v+cHdxc4Hk9Rwf3b+T/HB3cv5H/8+Jxc/02r+fs4P7N
/EHZ8dvygaLjN/IHRcdv5A+KDsBv8wJlx2/mD8oOAHheoOj4jfxB0fEb+YOiA/DbvEDZ8Zv5g7ID
AJ4XKDp+I39QdPxG/qDoAP42L1B2/Gb+oOwAgucFio7fyB8UHWDyB72tgBsInhfohPfcYPMHnYOb
GwgAD5/nBSZ/NlB0gMmfDRQd3Ky/XdfzvMDmDzo7PTc3G3j4PC8w+YM+GoAbTP6g92dwc/82L1B2
gM2fDZQd3OB5gaIDTP5soOgAkz/oI0Vfs7L+NrHn8HjeAJ7Zc3o8j8FTe06P5zF4bs/x8TzmAF/B
c4A8b/hnIwH0YRrPY/D0niPkeQye33OEPI+Bv10BB2gDeIpsoCm+Bj/w/91BAdDtgJsF/zbN5wv/
Nh+2f1RrwBWDvx6Hf10C7XbgzQCy/2LFgBOcUOCKQb7qsvWyJKhi8Ot7qEaE++KEdPyIIvUIijHk
CdogFE64IemSguaWKAVsXOOQT/sdrkdpWAItnfNHRJTJ/OHjyrESxaLK3I4P8DtKDkXlaUzeXfat
jEoRgp12NcwV9nP7HFEvGxa0B+5rNbeMe5KHyiSnhA1uUB9HcvMnP48S3GzYhItVRmisaKuXGdxo
HFvuO2YaaJduu7ZSzs19M2//7njIN/+ZKvATodV0rVL4lerPlKQCS/RVI8uvNjllKjnHDF3KpzU6
KjmKyhWMcroe21MILdIzWriBo9o5P/V/XRjh/mScqwS+TjkaHaa/0Tubz7sqcfXxPq1Ofs2DbyCj
k9KTxSE98jF6Sl/RyZxzzJGAk/06XWLsTntjt1X1rtHNt+t+YeK7SvKL9p2htsLVm07z55961XKZ
lt1anUGe8h6P66Dv7cRj3fVdoqwjkoMu2co1XgOW5NoexsSmmbosYGPvktBNIniF4052Z1azfEl+
Yq0X/YtgvWFx5Mf5OmGTWCJB0i+7WDTHMfppkX4ItqqfdcLKirxtDK+Cs61FipWZbOZRn/yRv9F9
zKVFIsUBdBVf6RHOdZq8+nh+8VbnoQbdaj1UebflSxiRioB/PIsx0KHkc1BYiryipUE8EX+bRaNm
7VfxaOWO74QNSB1VjcTK+5k+ZiaIUPjHwgzcbxgxOgvKy1SxjdJOqKbrfdktnJKWFdg8FLiqyXEJ
gU7o3poVCSfcaK465MaO7l051ZphHHFYZ2VBuggwW4+X3kkUkB1LNzT93uO7tqUJjLs/9x6ljNvu
ltdhFaSJVosLskfmD7JnJwpbcPuRCGYVHaJXKJJ5RywJfYWgeAXoKQT7ySK9U9TDPnsTeuLqajQk
ygCqEtWGUzHleIe0DtHECYbwO49/NdiUef8UvPjctExfn3COHl5GPrYRwKEaCHlHV97XgKrqoirI
zKyrx1b2E4sh4vN0zTkLQnRF9dC7nY/s3aoIJqyrexyy4xx18adop63iuvYjGaFfvyDIfaRHQ5/1
eU8vCA/3dqZyp3B7spslntdKvEsmfR/4FGYwp44K3/l9QXWBUwT+9U34IdKBvnazjGzVAg+LUxhq
eU5jnDFtFJa0AzEufFr06jClwVh82+YvPAy6TE5vzK3oqWjZn/gNt+5B3w3hcPoeB6Q9s5JSnfcD
BNGsevtr5dqZtD8/Pu7Uh5I9UpkDBAb1tzBkxookU7KHkDCthVxpX58apZso1dD+jN1FJv+FqV0g
nLEwPLY9KT4ywub+CR+3A5+fmJeQQss4kMgrcy3UxGHb8X0vjvOkZ5c/LPxpxrr1F3cmX62UXzul
eF4maNgD3bBkj+dH56ELtF9XH4QK99i/fruHHhbt7NyxaKi4LQLsQtA2MI39OtCraZFLr1PEvI3X
41bwcDwSDJ7h1+VVAwrs6GUT/uqBJFdTSyYnwHoXQF2P3l9Iwdk84e/eIxhAdHMRSxEnutegswC4
t6WF9ggRJikaMDrZVCsvxfFdEUBNQouVdkza2aG0hU8+wotiZGbJ/tyJsuiFhXJFaG2Uc/DA9Gso
yGo95zVQgXMXyLVkX5EVFNcYmWFZNnsn/gJIJNEtxn9JT+G0HqnNYscDOVykLS8jE4VABKUz62Uq
NZpTNyGrdHMp5RX2UcditumRHCXxSjT/BLFIKmDQfwayx6jOn1Io3POWw8Mh5KZm2jeZL4NtBMZ3
/b39pZrEGcZ+Fn02rMpE+CtY7xyUIjO2z6kGLzpvI3nkqdkqQ0QnjN9PqIbZkMTea3FdaA/IdmKZ
90pjNn29+VAyFPbJg8TqG6rJqot2X1q1LpUZGZStxLsgy5vkdivVH+T1GcNwGktCfcMV+Y62Bpjj
N0Bb2yxmGbq1dwqSpXi5CiKnr6xkYwjtKm0l3/puvr29IDYk4Bd2W7sRVBqwuEsl50Rmh8lOWpLg
ZoIXcMBDlyyeQiTqp8RklhefeHRmEpzHwhn+XqSOiPJEiGS+b6G+16Sdd2z0mhKqekA/09rwiCh3
Riw/S00i4od1tTlSDUsZb5eGn0zrm7KyB1YoytM0E1yF1bxvRKfsuehQlfU0K3bqYuXfAiuMqXFs
U15xYMkSe50kE9LV18VJrI+FG4adIvKaVQa5QcENZ7N+Ltu3/OqhnkiJRyQnioh5XZFLaTeiF+Aq
R9+agzs3Vr1ai+D9IAttGjdU5H8i5kMB31UkXRTM7GUczYyZpsVFaTrxbTI2ruTdCxjZIoVOg8wE
ZthaviGM7jScReAsRUexZwQWEycHiXnCB7tVSAE42yu2CooovjCO+6iSYCR/HF8vI4FYdpPXUoGv
f+wShZRwsRxykKmz3aaiaQ/k8TmYQxVXfiFToBdwR7irKRF6+03K+b3l7s+eoRA3o/3AN4u0Oe9r
y1EtyHvRjgqSNe+11k+sb/LIVhbNOT9DBOjlFc6/yoxPgPOHzj7CmmB5u9FfiIeCiLPOQUrU1skP
H6H7SPqk5Yn3o4rR6ePDS7YRniOksAXRhw8R+tcIVfKMBAhcdPC37hU4EKR147JqjTlDWAitGm/g
Ofj9zHYtNuQ3pIg+Sd2G2JBnX9fgZgRQ+kaYi38Nw2vGcbwwBZq/bGTYqvF6Reo4e6TSeF/oqHYn
w/PZKwnvRYNAlv9uM07AW+Of9bZCfC31ClXmL0RLlzmiq37dcHCQxgFiH3dDBYg9O/0UmGg5H+r8
M2GLqL+guyve0Ej6p3Z9/fr+fkEz4UPu9smnxMkj/DY/Qv3dQm0Ptp/eNayM7+34PjlS9tfjae5P
bNFcNG6nDuSESUDp9/7gDRly6dKRVvUhvew8ckmHTWFL/UIdpbetxwqT6v2phvq0LLiUkAOWuAmZ
V0UkapAUkzqD4qTMXXlCi1LBVRaHkqLVWVbiLQpmUVuVpFN0r2v9lrB4qohtdwDR+zl8IhWSz59u
hyWfcHUhtGzVfP8jWwOS/Wu2xv2P/5X909b++Vrkv5PP/lH7/H9TdlBBQ9B/Vf/zN1H+kZ4/0vNH
ev5Izx/pkfojPX+k54/0SP2Rnj/S80d6/kjPP67rj/T8kZ4/0vPP8X+n9Pz10PjPpecfb3wGS89f
jx3QJS7QO07Bm9nI/ovS8/eD7//+ZlLNeOwhVG/Brtz49nQRYJ1XVmq7nlpb9qFQO80Z9CX0oIki
ENmCRZf+SeCHdcluYSayXviSUb15w9dWzzjnu3WdhztGAjsPJkcv4ENrWVnjC8zHgWgNlQqchkoG
hoIXRU28+KknH/qG6B5v65fDyYodv3X7SA1zKFfEy/DY2vG45fTvuxeh0El90GhKhOcuoJcwp69o
z14XoC/PT6A3r9gaKlode7hKVpXP0hK4VeG7vdvf39yjr3v6cf42pE++yORNnljkq21PTdXB6fAg
9P1DmLKElxLKdLv9+yPHeLLFIzCr1IT1iVtTpLsupOgSmg13P9+oWLNkerVzd+Gur2R8CM+LWZMG
/jruS8vajDZMjzMlXgmCG2TZORjV3OTHm0xYfdyNVf1JqLyqZE0r4GTiHjEWXRIP/2gecW3H4sOn
BultTo4uJNz78l2qQvuE+NLonljaU8C8rpbhbD2PFvRahqGUd/R7gWK1i2wuQVrj4c4nklftL1EN
M6NKyao/55/CPWzzAYO+ffU72c196ru5z0rrezFq9LTuH5bT5XEBmevp5XKnQsuQmf4ha/3Rs5OX
yEvXHAOb1Jr8Aj9KquX1NF/j4S8IQWb5tnWXt+0veOGxSwMtOPMbXKXz2f3aF+mqcvCKHHnQONKv
UI60czebCRQdL4Pht7RDDI5EnwAwhrrxcWRMUYXYLrurF8ek7ZJPP+aU0dIhQvGpOnlk7StfY1NG
l8n6orYhEL72XSqozoBS4yA39IW5W/8MCVllo+MlCblHVNZeUk4134L0Kx+Ah/hmG88oeFJ778Wy
UgyJNPP7zhLL+EAIlQL4quJc1fqPP+D9llhaxVysz153VMo9eZ7/asn+9omzWMXLX4ndIAZRIj0r
8Mo06AcU7MULxumtgZ2fuOs6UeertLbw254H+nHGQRooSGv1dNTUlJFHA4ZcZHAbfAFeVkKGglgO
sWTs9pTGfbrdTxWP46xqAig4zNCLEbyiLyeBVqVLcmZQ6EVLb/fpjjxzK65mE7SCMnO0fenfYUi/
IdY6dhTW1XYssnI0nUZ7TAs3V9Xj4jmfCp/xdMvBj9Qyg8v+4Eo3zsluLIS/urrW6dUlzp5wxTNh
izE90fKd/Xwk+pzuC9K7LnIpTUXOmGlloi6tWr3uWlYUvNVdBfMJyUJ7VMbRQD2ahE3enzIpEoSZ
Jh2Hb25iADLnfq16TXCkvOtOFrYMHKuVvNH7ju0Hnw00XmV82ovJrQtf5SHut7aCfH0YFpQRUK1H
qC6TqhJot46fquq/RbTLS3l/+/3yMmpQnigVkvbEGTd6nffs+m0ES4s7StwXoYMqIWE4H6iLLd6z
cxo678X90UanT0ADu+MnNiJeo2Z15VoVKx9mI2qoCJIpLOYKzI8RZkh+SU4F+ARBK1hyh1UG7twB
ImPZiQ0WwsB2wXIr78ZjZau8DpUvYjWEbZfrKx13O83GudX2FbAxGQw/aZmBdIEqspyt6hYihLWr
JcZTcNiAwA532nq8HcxI8QRp0d0VRP60HIdjIRPLi4Qgrk+mrPKywzsyBEsNXPFw8/7Iab5whXy4
5qR9xQc7rJ/Q0MZF7iYjHxCA39IySWOpu14kRJudi+J9ZxJRRDX/QCNJMsXAx11t2UADf6XI9Tli
wemlKvl2svbicqACSydP1ydSqWECg3mN7S3T+lyuXqUAP6+Wp/m0n5C1xk/7EJrr3u2hU8PR5OJs
Ehwyns5vd0OEjYoRpc7ypdxlWIZcdLEDcI2jsc+I17oiuODEkS6oyJNR1JBbxGkmn+JipLnKA7Wg
4aF1LANWprYQ3KZ+YSSbjhIik3KKKFKrpUTwibzsJ8DLXUZsoYiGc64YCO252OvB7+d8l/JjjKwS
FqYB/702bJkE13xv+6qsUHatwUS5paveLkTXIDRXQjkJJ7HVmCZyu/YaoUIcJ3eBPye7pFlO+Uoy
3FvC7KrkLVHFtzPebIV0UiLn9PwFOdoiX9pz+O1EmYuuJ5n3wsk6qXsf7uyYZpkZMcWquAT8EgNd
3uh/hgyM0r3Y+15YH8oT3wQUglJ6O6awVWBEx+wX21b9wW+mDgFFXSqg/rvRF8dwoyKA/HVs2jv9
NzY2dKc84TK/vjMFzqbt9ly4e7z6Vq7zydStg4PfanIZVcvB/SfM8F2LoG3M8eQSboLLjNB0hmjh
qBlQL3FXpfpxquP49dXeyrhaB75fnU5XcXPwUvHCz08dh1THouzkIt8o2BjNjidhOExSQ79HWFsS
t63dYrnx840W4LWMfCfhVZXx41ebpT7chGMzQh+cR/QAJsosfrPK5Ie5P6vzkSiutSI+nw8yf6uY
ChX0JWJyfmZ9LCY6m2aZzDdb4qUO5HHPfhilBm7r/orMwt7bj7hUkYwDPUBIr37PkLeHuR98nu55
7bCC89azMp8q1sVeGn53EUaWojZVDx6s7YEM6NznL2HFJcr2fClNHyoztBU+g0gQAtSWT88xD2FQ
mxdmxBUnXJd1SSY9sV4P/g6Pe+dYU0mwANxYm4m3RSAwBDyQV7J/9kssnUXJOyT+8YKwPU9PRYF/
l8O9wIGDsmOKsL1u8XXJmcy6TT465GoM59e+xuuB+RfljSaRlU7FD3cOMuZhER/I9L4WevZcflrF
XDr4+MF0ZOUYN2+G2t7HW0rW4wfECh2AEuXiCRXRv2zb5Br2XGzVhHxTpuea6iiR8F54W2oXt2sP
b2mzUSRilv7XrMcvmU9uhZk92BUWi+6LnEDBApOt+/pvn+rDqF5oDcy5FVorSHSQfolwaaxfPOcl
PG88tDxdcx4YTbJmrrAMbTMzCnfHBXDpMDXMoZp7rLrKMX1ugG1YaGksPvq0GqHxKdmtYQGvdu6i
jMBMe+ErkvkLZ0B7Y/BX9qqCm0xV6eK5Eu2uYqOOnx4ab17ri29ZL8/kbu1wRrKsKs01i8OQ5KDN
6uhTeYRKwPaes4ZzkxQQjPV5brhicSQFe++4/nL87vagjaJ1mTQ8CNvclbMrv+d4X9hVg2oKJB1u
tkBF5Gmpn9l8s7TfemFnXSFCrnFA9srLrk5kWbf0YoEVqs6+uzeR+R4/Lahy5m3RYeA0ru032l+Q
mQ2qZ1cDkCu10enwZl/8K/VrlN98UZEthdNsqmkJGDuwbUF0aXIF9Ks0yJkabH3pOeHkEwEwlcdw
jl9725DpmUUSXVBaTljKU6wFZWKJJuhYv3V1yqGbameFYmZM/3hoC5k+XNhLP4LmnF/DiKPzxrla
XIaVBLmOkhevYci9xha5ts/O8WOj2iLVZk8/1xsZxgdh+2/9iIE4ejkMdXoFr7IdD3UQ1J1xqaJW
kWHGjj0najyODRcz+oDOX6jG60Dnt2lngdYnzlqG3EiRG/KAAOZueuaxI6DR8bQhhO6Tvdm6p13t
au0TAeAV8gvK5EXq3X+IjtAwMkx48dIKHb+gNea7Q6xdFQRkgyUE1vKpv4iHf3KA0WhTR4m2OLnf
0LvkEscjxkz9TVURYYJJYTULI83+pa9obuViazjlgbSL2O/SrJnfWG0lZSclUxUzDeu/wDV8Ye6m
Xmqrg5PDFX7+TjNGrHjnApPrtBamIYMRuQFWL2Cpn0mYKYswBVDimwr5Uv3Qd+QnLRCFhTdrO9YB
X8eZZOjVOmv7/a/9n2yZrVxbupKpKE0wUaHw3gdq4Wpq/p8mtvUwKYBa0YEbdRpVQ8JmLBRbRoyW
t2rFu9WsWtsmxqIHovclPUII2OMhiMTKg0yoKgm2DE5MJE0xTbBN3RneExEplcyQqpFSn6FxWaS7
lWMGlmiHKWzPapV42xmhVHF2/MrIwrsHDgqWto0Qm3nUcZqRehG0QjVhmAW4We0UGrCN+/uZPodQ
cYmFmuwKYS18s8jMWFXXje9zdXZGvDuMMJsbCuXX/3QMraEvKjRTNjnO2QFrNWuYTNkokmr1ok5F
WN3hBSQDS7sV6ej4E7TRGoKGG3RQoBOurozF4hv8fAnEUYUvGzkobprZ44H2WuK1jg6II9VD2DER
yVSUDMP6kViGL0Zc1enJdHBiGcPPJVVixCi3LxT2z2oDDDMYww1h9URr+5ko8P9a4OnmF4w11y8i
dt7b4uk4Cwy92mVrP+SLkujUc73Zn9k1ambjkus4REhyXRZnFeJucYORFl62G7t+a4PX4+jxYgrR
dky0X8Frxd7vp1t1QcWLpafoi1rNqG2u3NOyDfs5Zd5B3UenXfoRurZDILYUbqVWRXGiWPA3+jHl
0l9EUjtuMynHcEFtRQP4YbgJQD4gXvbUdWuRHXmjdkRFq7n2qqElp6yRfjgD9GCSqUW1WJK5FPyg
ouZKHI+xLbJHomaQamXQJra1XpUO8SG2NRXD96Tn0ebVj9k+nR2VS2FrfONNnDLqJlv7/P4zZ/jB
0kU/dXsBKsovaFCj3HOSmYEvR7l1n7/AWPKSMynNPDLzsuKoOOo68d/dq3/1qzHgHzE1OQpDKy9k
GXFe8+O/Tjns9DMUrWotyJpq+1Rr1ffNfFAgtpywXYqtEi/FMLeCHF+sTh2CLXMRKlUJCG24UEbG
3m4vhlLli+Jx8ahb5cuo/noYNOpStSG5pB+uxf04zoo8rMb5JshB5LxQLit1FxVPuhnS/xMJ2qTC
aWxhD6wGEsk0B5eQtGbXik5uIik1Vw9cRIMTqtrpzO5+K1yE7EEN9nZtIWQe+lBUzQ6NboOD5YX8
kMrMXOVFv/PbraRcoYUfngetjbILBO0Pq8OBkAbS9ZwLuabO0gSsmUtbSQmv/TUXylbY2u05Uaqe
V/Tih26VLYP66ybQqEu16nmWTbW49mOsyE1qnC2B8SKYwSxpU7415ly6SeVFATuOGEHlNYP2SEXk
Ft3V6cJQTRWSZaGvoM27RdWmfG+8Ly/qiiENhszjZrfJhjXEaxe8LhziArlHgoriI4QPlzqdtY+0
VS9ejgwuXfwKLKEk9F/1tRvopnxphTpC+2kbKuZsHGc4vxefrE8HNnUzkUHfFfZ5Ta/gPWANR8Le
GD+Prjvcf1arvknqwDAMUhcaLEVkSyeMA3jdjvLZdKv1ouJ9/WXrm/QxmgOV+Xk9YwprIDWWbncu
MSuC3H+4vYemXiqFYxT+XGXV3V9PoimiGYSNmoK+zp7+q63mEc7yBmgypTz7fSJr6nVI3qE7wUZR
j53WpqGvjHqyXrb/JboJg/u6wIxohU9laOvFy4ujHVERToEvYUE0lhVVwi6v3++k1XXAvs1PSTZh
157DK9mqHixuzB0UlW7I1kwqiaTI44dnZgtSDYvYMYpS1wFdBJq4tgwbMjCyJSWHR5zpbOZvJlKw
/8ylMEhtGQ4xx8Z/xa2w5VqniTP7I0mWOwszzgQecofIgvJLL+IOESvlF2GoxoyDL/Vdml6HXp7t
UnrcPt83AS2iGfwz1+ST7PPBwfI8l1MEg9Cqv1a3JqFUBp6S5qozrfXq2oMCeWZZK3W8zVDDZzge
QkrVVue+iOwVehfSz/3aTKX+kfkO7T22RZaZhSPD/YKcng0iMu5ADcuBUBafm4YARRmRXXTQWKyp
xegLKvu6bIKzcRXOuMzpYvGFstnhU6RdlCqlV4fKCPpVSnmGA89b3nL2nih76lep5B0Gzg6zSnPq
z5aLAwGUNil2G/ESlNcj/pz8RNkFG69k/ZHrsfjyzSx9kxq9WzqU7FtrLNu07Jvtv2E6PI73OYRy
+1jD9zbPpcCjP78E+9gHrerNUUM3n16oqeVA65ujqeNgnmWOpppmreMw2MBZFKUYrfA56DVz8FKA
GhJ8035YYYkW+6V13ZEX7gcu10ySyehlaBnBqbnJaOElJrNBN3Nkn3KN6z6dgazNRMLnfc1noQyA
4QHrMxJ2ZvI8et7z/GtUz5I7MHyC1E+HSkMF04nSgfbbEcbpynX4TYbcVCJz/tWGoQ3kFkAmdSjj
YQLM9iPRwcZwxJjhBY6z1/Gn96nBXyRdL1cm+UePrvpoiO9oCd02PhmnE8ubD6Z1WqpybHfeZZ41
OW3W4j9xsSowB7Q651QVkkIZhIyIJaiycmmbfIyVh/B/X8+pmx8Thdw8zK6pZTi7RXFJj4tatQLs
Y9Dq1+mIWmDQklEZFwONTmbDIzpGBw4DtTjGe8VUZJm3VmLaN5eDloSTbDUR/uNV95kw3TWx0iPW
/5mu5/K86ibVvB6FZ9q5q/7wxDe0t64bo40xsvLmyAdBH9vSvXuypqp8uG6Vv+LACTZPXu/TTFcV
Yt++nmF5tJ6MRsYuzDK12JN4znDNYUXNa4PZXtJL+keUqhXWPobnhe7wW2C4llaJEASNTmYJIzrC
ug4Dr9nHPwqqyN5vfpMM3T5qjFGuY6r/5vlWMpMYJsGhPJYPmSbBoTuGDxlxwZnCQHvggYpNxcBz
nJLveednx8wE7fuAj+hZjod5lt/8LJaEnflKmFD8XBugIrygDDjJaz751Zyvw4jzHJpbtnDmZyGI
L0niPX9HltvKLzYcDy7P1KJbktwKxzbWpLF5uHRA7FCZmUCnxS5ItTmkw524RrU5pTwlHDRaL8PF
90gMX0RuMU0JDC//pNXfQu7W14TaEMi42Yhh7g4Uku6R+ASHa0rnKjmzAMFk9WDvgeg9+66xrpFV
p8aN0PXvxb3khxQzu9p4IyEQJkDSXMtkOBO/JCyY1GOJXCbTpYKh7PUl4m5dtKuwuMjn1cNSLlK+
55XjPWdFmre7BkUGcDNacyDmFDekF+exWUHvPrQRzgdrxlrqw/N63xvMbj2v9xNKldbrPob75/X+
uMBwL60yLggancwyPO8bz+t9zz7e+7zej5vfYvo3GUx+BZZ/8sqhOqDT4yYOILcor0nvNRsmYGUs
ium2YiAQ+TAkal5oifS6nxJ5V9Si6FgqX6JHHJfO5xPV8itdg3hfK8YySNsKliG91oQZlniWCOjX
k4CXs6PvBmhPu7TTPSg0lGAdoH/uzvetmtVZlUTeudYtqvz6sTVWaI5gc9z80sjnpNeYNyEne+1U
zDi2JZAVs4lnJVWYIjiH5WBoTkDGInqM2XttNXGZ9OokaudyfrXGMQ3gI1CbmxM50qAv5sUHW/Ii
meETDtbWx8f3985O9E0+/PceL6sc31t/OC7hqx9QNsOG1dAI8WgwFyZsDxfM2CUtRZyp8rIOvfuc
xumHDKxEzK0oQeRw1nqH6WpcRlltnghzOBun6wrLFaT6FuqSPrRa9a1w7dbzlgLKjSv6vmpVaeHL
3jjdlILnn02CAT0ZoZQVzzq1d7G/31ONzfoeaUDyFbnx/JNxykv1Gp5BFxMHHi9LnEW2gzNC4yRU
Bx4fSxz1Kz7scMuCfBkCYkyjPZnZb6zUxotqyqNoljhuxplZoqNofeO1KfsKc+w2b9HSIcp7TW1l
kZrn0RJ4lO+rwtvv6KXSVhwstJcmk0XtZJku361or3t3OjW0he8UJwo+np05fkFY4TKabfTSUllH
sfr249JTJfMXr8vFma1Xg0sw+vEvu5O1k85mlw978xNK31dmd+9mNp19vrmVpN/SjxddtEDJUtHM
b1tlGx4VFeaV7yW3hyzuik6UuYrYCByfGCQiDNjREyrX8GqTHq8UPZzdnj4G3tkCW7PWH8/bllc7
aG7bSNceA8XnB5bnbVYevvFa7QHDVmM/nm66NjtVuRR9kVhC//Jd42o/KUxM9fBkbZ33k7rj7UvV
azxtHpo1usSHOXn895zblkdOOh4DFuurSccSGisTx/Uubdtnn5JOxmqyQ8u2Br1aF0+Or45vo7hs
Dx5/XqlW+bjf/Aj+wFVTcX1ixJ9giVh59YJNWTCpYm6l7t2dmdMM3fjT5PhjL6rQYfje+uDZSQ1k
iNcLL0PUMwXA0a/6ApwijdMOtUABHRcehVZ0YzR58lF4WVW+yrudsq6Hy9siAMuewWfpxmFZcoQm
EXmW1LnHHz/PbJ9YM37Unj90Q3sKBASh92SgHRMXDHi/JJeLXMr8nKTPh+NCKL/b6nPirNjaT0nO
X8iz48dryaMgaNmYUHY/f/fSRIZ25bjP7Ev8JNXih4eft8foLov6jl6GkEaIkJSJZCWvHSrMhoIL
qlBXHfs/OMzJlvt8wJ5w6/qxk5cc/dHx1Ezq3UMXBDSEqHv36H/QjfwL0f6FbiTXPyEE3I38h9T8
N3Yj/7qZ/6Fu5J/zXPxpP/5pP/5pP/5pP/5pP0r9aT/+aT/+aT9K/Wk//mk//mk//mP4p/34p/34
p/1I9v9C+xF0O/+b9uO/3czv7Ueuv3+Bje15FcCbAWT/1fYjOKHA7cd01VX7vNEXnVeKjnLKpWRG
E356KZAns5l1nbb0i+kaZfbxE7Dir9IYoWAn3b2aviTQyLigS0pCLbbt0Pvt3+w/3p4cMNik8WtI
5uj4czyeC6qK5yPCXA+xUGOUwLyKfPcGo8feAbu6euLMaETwiyrJ5OC7WhhSa8UEhFerJE1kGGxf
We/NXcTLA/s5SYM4qxHE8EgFAqayoz0cTA5gnhAHg59atcwR9FpIot55SpJ9JIspp+soyD/uapdv
unIhtV5/Ql3z0Vq7CVeTPGla9rg+3HGaxZ79XClw99iV7NOBZKdqg9M10h+CUc/VuwcZZYD1Dn3n
F3BARKJE0jEbjWedGd10OhbJkfHMUHRIUu3UxqBqbkgYu4iCWNqg5OZ+/nJrVg6PPjb9JAPzqZEI
0sMY4xgVDu+zVxtQ92RV2a1Fc3F24rXoW1pHRaGorVm2zVnWYDnDgAT/pFjJKKuUpFzEIp3DWQne
vm/YFyIKw/s4LQvqHHNFviWt5e1Bu+V1Ew1ZIcPQmkvtFkgfwhfGHsQohav2dCo3SeYTjKbU1R5f
1prDMtdj5vQq8Rz493GOas/wqw+fpx+HtTfCfvDQRv3V4MXMRdgq5jH7yvKg9dtVkoIrguXmcYrv
O3HhozdIYp6Y8Oz6UGdf796QxenidL5/K2PqJ1FU552OpRPRD+zJ+MFUyec6fafm8k5mqADnPY/9
uJjmFkdPHKvBWL0tF6XBy65P73OWht4uSFA6XlTSafj43XxzmjRaX5u4EZRLCEF7VL5VWzXbb+/k
wXQXgBPH7h5oJMLSwVVWEdZZQtnm/VWau7WbF32ggB7GqbSXoayt7uq6WXximajMbFcNU/YV+KSb
uyK0fKQi5gVtB7FeBSnSWAlID2Qy1BQAWrRGVtiWRG3e8QHFw0QnqIfSXUlISkt/YgdNcbvGh2WJ
FHnl1gMyqYAUVSLs9I/VwvKCy9MAEh5N/en1ALjOp1biKuul1o8VvNl+93QONgJcA189HNcF737i
7b0T/QmrL8cX7Yckeq8Rn1Jce5rCOSxjLYRf6rU+lQ+XWVHW8UHLKQMgrFeWEX3+fPcQ2bA3v4i6
qWCnlbf7IWzH9cVEmrYdFnSPRjr6b3n4J2wjarUbMz92Yaetfq8T1Ow3yFeZCgRmvJDHOgNGsFCd
EpZ+AML00W2TjRApt1Qj41LeXfNs0znozxMbrhMXduDpfvtMs80RrIw4d/IKUxojpJ/MAv8Bk4iO
Uy6xX5jKFOBsqIRxM1X8TZ5NPVBMTPu0G8bnQmCByybMSlW3cD299rPU9sgLDTl2laFkxfwoaFTk
LZHwffw6FF3//uY6JuxvToo2zfTrzCcnG3qqCQxhe8nu8F/E1HsVL2dr+XxKQ0sCdKxjM1eafXUe
jcI4rz6LbErCn2RK39WEptz6SYk/3PxCEZ3sN+9n6BNxDvJyfnvdNycgHtNUMI3nXnA0yzvIJgdP
LfQ21X9NwRqoH+Nqan7GJjv7Ju+pxY8mbCvkoyfG59kwC9rwKhjyBuZ+DIaPAUnZipLnbw8/JiEP
l3o1qdYCnP3oLPOnd3WIGnBcwqFfYqVFhcoXKo4JzcgzAlLUe/B6QjEjGb1ewActhXEQCnTrlshP
K7IS6bCHpJOQdMGF4EPmYmAMXxfYP8W9WfI/bhmsdlzv7IYWPEL3wyVW+mE2d2dF424/dVsD/0l3
JckZqHDiD1fWje/Bp5fCj1EFxUjcHesMUZYFqUaRJyCeGIxkXhbBLICv6/nWugqBQ39cUQzdsV9o
e296sziv3USfdLQMf3F4+cxGbCGN5Hh46kU+oyfFdCKCjc2quqblERC1RkyRBCiLeVTvU11W0+mK
5U4uktTske278XQzl2Ijprdq+xVogGnTZTobtqggmiW+/THC/VBAA9cUdTEK7zVdxc2MA2wL8lCp
xWQlHn+Q7hkupYP11FygsQeq+m4S5T1/9+gobCJ2XBxcqq2Sfe6b6OzdYGsEQ6v6bb9BBpW+hvtE
osDwxnt5Wdy8tdUGTWHMTD07wLEDYbWA4AXNR4/LY3wsgrai+eF8fo5IMbkZCSjejhH6dib/4PKW
oHbnzZrGyAKPyeB7ve0ZBVtCKYNx9U9WxGhAtf5Q/E2yYM34TiqrYj7Lg6WbRjGei3cGWPPjXgZV
H8t1pURkfqCZdODAR30yqiDNQR7xiVC0MfPZaSnQi7vEri/mWVbCd9Yp4kR7jRfZ9e3CeHl3DICM
PVarrXrvYuLT0zk/hBQk1UHSztgyclKh2Cc7srFzlWI2SIUdBTEA7ayTxTd3xOqywrFhqEWMzIH7
duiiTDmtralC248QLarQl+UuIRpNxzhQbmyDNb76g+3xjze7fT8e5xtipiIwByct1JRhLTLm284e
Vnd+8bq1jDcbfox+sYk0i/UqPV9n2jTdiFmRxfp67QQfzlo9br2s6QVzyStL6Fe9Dbu0epMnL6ln
zSOar4pmSPSmt6k91xKqxVJCfoyewHQlz+gGNDTlm0aYZiLwF4ZGTlidYXcIv/f3Hy4sxBRqoCwz
FVA3Yhk+PCQQ3ObFNmEkshj+VHj99hVKb6/iwtKSFzoxo/qvsEwqNI8Lzrx8nhrRQR8S+0K7h9wf
rF8aZWMVAT94Yxq2C0WoDZlPgI/p3NsC/UkX39s98hAF87yI2qU8VHw/vlYwGVgjtlzp8fJy5iRi
bV2UiTSmhi86wzWXeThHDtqadJyzXj8ul35hGvXA1dhGI5WD5ce2H0JIrLfQyEwUyY6yXYEuOU/h
Ho/XjdiWL5lLeWuHLofC6xHfq3s40UMGmHxXSJ4I8RWjtFXD0Dql+1hE3hB4X168JUXgU30w8zor
PZ2XhYVx4J2/WPqe4eBrQQ3CF5Tf8ghuKLCHRPsxhy96DJ34SnT1AvhJ6xCOZupm7aLq1x4y7jZI
n67rPZ/sQgXa/ZbL6T7oGsVe5rx6WeVwaCdRUGj89mNHRamdFXy0Wn42HUkWj/lnfHNNSxJn2THG
OEXuM669UBKO2ixOmrRI1j3DSAYp6VehsNsshJ6USnb0Cvw4QwqKH5rbucWN3d5z+RwXVHyWkgPa
T+kUmJ09weJBAEWVgP8RHAHJ/iU4Ar+a+Ccc/f2C4vcT1v/9EuS/+UT1f13rP+f8v5733d7Iwcje
Wc/RzMbaQeh5YGPv6MBkY2tk/S9+0j0b6FPznl99gj6lGXRM61889ftfS/Y/j2B/zgjy13X9MbE/
JvbHxP6Y2B8T+2Nif0zsj4lJ/TGxPyb2x8T+MfxjYn9M7I+Jkf3Pm9hfu9z/3cTY/t7VfqOwv/ZF
0CV2UBSCN7OT/Rcp7O+d+d9TWLvqctxK4wuv9Sqhc9FBTrVsO/Lior3a9/n2lBK8dPzDbguSr4wy
VjMuxiuVb9DazqNvwjmsKSWhRKZL7NUHiJunut9ccUcOLoorVCqJcKXbL3IZ3m1Z9tEaRMQfSTy9
hFn05r97t/rBa/GFDgMSdtmUPn3tk0x2yVOnl9fc5BxG0FMLKWoeUwwcAT2+yNUy+/eIoehrgwOB
D1/oFWx8gNsbjNdDvIgihKcC3r03zsgwU56fT3qosKkP3/hZYHYtHc8x5TxgavVz3rNYA42EHBlK
PjYjZepwJ1wmO79b19bqdLc7+34De3Nz5IJrMzzWtP64/7H9cXkG0IWCTs5Ewq9l67iFqnuYH978
3qvbaAWzPvpqJsvZJZr3vHaNQ0m1bUnc0+e6ljfu5JLzu6xq09V81mW0oQie8YASgW9s8l3aF97z
27MfUc39G4vcyMEml+VoxXcDDd0LLyo4lWmmf929R2irOxdXiBF5MkMSL9oeZLoN8HwFc9Opvz4f
V//R9E2M/bXNS/ZBN5IG3ekCS7iLk7fFsPBLzNBWrQmnmKZ0iN+nCxoKMLVUtBVW1XmBpKWr3y9/
3H6XYmLISj6rEbIfM6nw5RqpaeZNgoV2rkGf1QtuUZmd8nJRCS7luVdykDNyurDt6OJ9PHtnMVq2
aufjCrS+BPr+IFl8VbpKXIF6/j3PZXmdhxJ3WQvGdVnBX1QlnV6W8p3SRwbMb9W8dysGB7ZtblqI
PClXlmlBnWKTeexyLs6QLkUVIdGMxjKtyk65yYXScgev7r2b7uYjsaU1H9q+X/p+s73wtYdsU8Xy
/+UplJg7TPwuqzJW8jWtYKadvezn9Le+xUnLH3NooWBdgBhhP9I3H0iHiSnYIyn25+Fmqwpa7LHL
7YY+YpR2JXmiJFLf7g0G4byaDgRsXqutVxSi/ognJ/62b8vrpiKf1V+XJdorSjJi+CS+kE1bHkhz
KV+7730+WPRz1+WuTP6b64OZ6rLGFXKoIapbTT90BmJX93QnG4tehQDL8HRLu+9XlVMvnQ1DVojw
Aq6x+M2W60NHcYog5lfseAmNGhlSkj4PBpiZJycCd5j2xeoXrCMfN6zIkSsYECxqMeY0CtAg7VMC
8eWQyvktpt/xC2b4NT8pyCKYliSNcZCLoDGTnjx5NDeymZZJaLaKOe29nNL21vI/YuCY57Idf+u0
3Yk2NonU20AXqr2gD1m3xjy+Fkajaq/rPAKX1qJSuEaGbyUzxavMJnpBNdzMvZPBhkFhwbZL7+rh
cEpCupysmspSNan/IYjQALnEKfXtIwXhGp3GFBx/QT61KfTPnpVCrbaBukY5nvT8DytUjAt4S+bT
t3L5DuFbqa43ODyuqUnnfvFGJ8XazhJilqj6DFcrybjyLOudLekreaPcd6vWbTWCe6jGvdjDIwtf
hl5DKbESl80N7n2P2DaTMSbaTfYHiMIVv2uk9ewj7p7Gaoi2Ujy2Pv5E9m7azUxuQgZ61CDcn9+/
A9W3ffnEJjqve6kyjMYvchtPcpHA00xm6DVrLXaU3XaNUqPoRsrreYjIoZ9+xBTbMoyo5fxztmk4
1D2yJNrdq19nyImDWdqcVmbraA/pw9roUcJrGm4dqXC1q0q1KLrIv1Q92nk1HWT3E0TJwKQRKFWn
K+X5TelQDqIwaIc01g2ZXl0ynywOyGtuzzHjrqXkTyGFJE+IUMmPiwjIjQtSzypQdPSF4NPnJ7ot
ePA519lM239Cg23Wo/Xte5/Co2m52q5m0eBFylTc8HkkeUkP/UOzIYVwBFl6pwF1dHJn52j+yiBw
UVo1bR+YTnIqikQtks4Uv8RD8Fnc2rdkqpNoPMi6uh31cfpK/rRvo+QctiN0ItPLcQMZ4TNVy/qs
2mHpw8NE5Umd3BsHlNE3DPmct5Dp42UVxKUe+APBzNa+TuWD1l08cWV38K0or6qhxGl1RT/l4mBH
fdXy88/0w40O9rIX8wtwJVQnGNTLz7A6VrgZtMuO8xqjOo/s6+btFheVCa7jINLVkOnrOWcwxXuQ
m4m5MEPT8myMC18VYGjBe/BGZnb2qPhGYTrfybKVS2I3pVAjyC+gBIOg5XqnP52meU5FxY7Gax3k
YckX9Q0Fdd8Ubzg0rfB5m0kLT3d9Spn/jqot5+2EbUN8++7HSy3XxwCY1lJYx6NGDan5vSvNyYZl
CyptWJyUgoKfT9kW63tj+SfRvyK8Zl2JaOcbbvrIh6qpZR9NgfLzWIrzZ1/Onaq9C+e/8OdTskGg
FwZkk6Xy4X8rtOgmfkEfyXeBpX2KA5HgBtNAeacQcCi9lFD3QcbNXvhQJZKEmWOj+3p1I8t1+7tX
YahY9OQANbPdZn7GoJtvdJSz99EmsuMt5r4KqYAscjTaUOgp414ox95Pmrk3AN4atE8RJZxMBy8P
hMReWniWS94bsJv0kRGb9I4ZmKd4mVQPugdgSamdj54yb6bGKk+F1Da7Sx9OqTGWzIUMIAcN/BK5
eLw97klyVSQ25/N2avV158OM/eXqjihLwqsLTYfKCynyi7PjjDNjxGHwy1Q1OYrf/mjziVtkWAWe
2hhmhGwdyqs6pJhbpeJC1Vequyt69+iQLoL2Vw14TgMeEVLYG/Wbe59L7Ig3w79dxwmX9e0zVcVI
hwyEwSbkoMa49wUe1dOTo9xe7ZLOIvtwIig14NPauCbKwPK1ayC1XlD+GpRcLl5Kr/CINbZcZSc3
CbdSH5yDnFjgqdiiYpGRK3vZl65S0RqoXjC7UStcJr6cKUpPGTPOOnmGNrO/cHbUOTg88sOio0cT
hd5+RZv856cfzV1lnGy2sRyMieP6N2HfYarl6r+vSDtsw+SUcWFXqNFr5MyR+QsPa6FujvdtooW8
3XDdkbsowZ8OVUzIbLyVUUZEoSN7H+XrxfGi+OWgu/LbwqMn5mI2rRdiynAe7xN7MlWNsjVVEtU1
3xnN4SilNrkpG1shToZWqFJtJDoSikMdVNRkmPjykNwtAjrs4UV4l9H4zYLygE4qS9Y67xrjHFCt
Wq8JrBikCUdeN7RSkg/eHYi5tj7s3MYrc4V9ai+toWaJ54znb+Y+Ujs2IsdmNjL90hGWl61WatPw
bj03EBtDltw8BE4TJjE3lo6gAwuVi3psiqM9YNB6oRBVOmwwOUe/JnRCSMOyl4pFaRsrShntg4h2
zXtJFXVLyF5iVWauNR3QP1quqMe1JEnj7MVQTpz0ds6k9I+cWBntDf7pDYO9r4QUYy1Wi4JaPukx
RKrNt8Inc1L1Eb/R3S6yR93fijtD2m8qt0UYwIyoE44Zp4iXZgjG9n3LC31TRh/MasH6ccSgHnDD
HaxUThHon+GnNY+P4N8BEfdOjb3TiWO2RC0taRC7SB+1Sed9eY8OlkX17gBBSvIRSm0j2ddypmEO
m58UE0uY2S81sWh1MwAt3l7mKdi0c2/rKj+gMzPALHEp5ZHOpyzOQBklUcwWqBp1POhFbV8q1zXf
waJY4QhJBbua/FAK/j6/kjpZyoknSy5ZTMiITD2bI7dZX8braEbUhvW5NlpZJu6jTjAqNJIR8W1a
drmIDcvB5DIyzy+YsQNWk3Ce8cVctLrG7L70CuhPNQU8CdrB1u9D8l9lRawepimV7WOYjFXSkEb2
fuV+feeWkZTstLdmNuEUPgGdWfji+uOYFp7OxGQZIt/qo+fDTtZlp9j0OdJOpI+smA5THAaJPLNK
jALOwrnAqiO9SXwwi0VSqVYoNkbBsIgoR+7LlpROgnHz2OADJWkrwm/iZ37Dmp5W+/omRNbxucP+
HbTnul/CV2aYf5iv4OOWv9mDtYhxH/kxoFNNHcM+J3eaIvaSQLdnOtxFP2W21JHkTfmaiVzJmlGk
0mstmOop/aftDhTnlUY/1nv6cVk4/QrJsPxvucFkaRSEjrHZaEi/ist3ymMbOmJ2oLxjBWyeNkPi
GNXXJnI6DA1QJShNvt+ZcPDjFRG/gH43A7QRaoC4cMrfGqPwmJhMdUWNvT0fCcLUvzHkuHMnezpD
XbxGM+Ujaoz+gU8kR2/OkRkLITF4UifeMVFhq/HyFTERYqeWQ8Qmd6Fnl/+nTSLqTzCBid4EWI3y
/r2XiO+AB5YoTtONKciNECNUmkLfcisgv8VV8O/BavqK6GdOLsICB4NwN2PWtos2dJOzfPsKEpwS
yepmFM2qPkgyfxIcM+dqsiPIMHaVJwkdCsIVrO2MCBlXPslmaUAKtfY4c1VcHecKCUhV7mr0cQxx
/HWhZwbXKzPjHrt5179AwqjQkpIzruMbWGBPgNMo30fhwQn8GFhGhkUrPN90K6ykpOK2ztnNsSlt
bOFfV+dvALtC3Y69FJJ+iSYk5xp/M7oGuUhnE2W67cWZm7xC6LAtgHIdUGpAei/V6/iSQaply6eC
ZeWY94vPppMvQWW3G2DE1qxIy7eJtNNTZ81LG0GqtipP1BOocudffLW1PC5OlZgRbtt8q6b3huTI
GFF8wp4Kqasz06x2PrqA1oWhJviLOxd8xP3hO1wyAg+JXLV5qi5hPr4kdEGuthNoU476vj0iAI3O
Z+Y81wGt3RrO1LwDw0e0CSfMGWEGh85Fm7u3WI4Q9SsorcIvQrhWXLvCHzSANf7DX+FtcJcnrOv4
rXGZRtjM3kVpWysuvTce5JJA7vGeSa9qgdRPFHm8hqpRVJ95GGhdslkGAFKnsiUaw+3gFxGj9QT3
+73e9JpK4Zk1BwAXJGMlyUXUnAX7UAicLCgryO/exTgyzqycWROxLQeWv88LpC01/3nF6I+Bi8VK
zB+aizNwTKkyYIb1iTsqvxiJDthyl+Xvv3a239z3gD2Ktc7maRMW/kuQc5Y5qNzoRitZU4l9lkmw
rPprFf7QyODn/EJSmvmBkSt/jMKtUPlOxm64QHjepiebyjXxt28+JM4+2eV/nhS/amUifRu9f6mp
bucKQfu5ZKBI34WxFIJGWZkHBbYQrjSujGomqDcZ8Z39lFsFjD32d6G0HQP7oT4hicqzFbYGfMU0
OHPZMcZ802OK4i8/1N4ok/F5u9FdxmS/5fvJ4v6+YfGOlIEeGps4KCegnorZApY23+S1TPScODrF
I0QNgQlxJHVDVB1zW/kH6WvDfDsp2QEPnLOXVFhnUUOQ0ajfEXEeV3QUR69In5o1vTuuKDtenX3O
K7i+vrlqW3bxYcKt96vipbLJb5Vq1zJPUmQRPh60iYQp+5pCUrttg3oiv43iA3kvnCbVz/SgnGd6
XzfzppzuqVnd61w+U5oHSqHLm/6H67hFYSJJwXgRlMN0FxQKBMdkQ+J/ULf465jR/1PdguvvIwm/
1y3+se23usXfbdnf6hZ/H4L6b65bAP7R2v2frFtwcv5dt+D+l+sWXGT/Y3WLP5/H8qd98ad98ad9
8ad98ad98ad9IfWnffGnffGnffGnffGnffHPb/9pX/xpX/xpX/x/X/sCdD3/a/vi33759/YF8O+f
Ywdw/vYxLH/94H+tfQH85+2D2xflycv2hC0vgk5usCQrWdVf9t7ElF1nl7qOJWHHp3VU2+fU7kdi
pp6/vWy95OZK3JUFyLFTQton5B8SxB7u90SLXwFWwwuMe/Ekkj4iEhOpd6kxcm+nI9d6Zwm8FZtb
xznZ2z3I4hJFCZKih6t2fXssgLkf1FXR9QGIw7d5yuJtmw4rle4o44B2nIXDR0C61hfs1O6p+Y6t
/KkGg01jQ95eIZM71fMcNZt8/aXgjgnyhKcbV3xvnH1D81t7fs0qJr9ITy0E5V8F8r3uxhw15KyK
Wb3bRVf78dGY65lVOp3ALldvOW8PBzfvF1kEKYr03XlkKmcq6un62XtlP7FbPN1qKL7oZDxV384f
UzfUj9+sBl5R1CZ8VCeV7087E3JUF1tyPZn5wLVcRXiuJ5L5waYpDf788mM3N6Z14M63u6p5TXvk
Lp01S9K3rDBfphaQS6qj6EKCXsrcPbo9eLMUOin2ulG7rKJHUx71ftVurt8+SaBQTfiA+glGrJwi
xu3UR50zvNF4gPORu+DGhX/irSTOdzNnZYc907lPrhloLKxM24upcaS5pW4SgDH5eUCTDxEHEWfS
xGNlPk7K6hxQ0s9OleK49PsSr3uXHw/HL3IdgFpk0NoTG8ICasejvUOT1/XMg25qdlpw2x0L+hjv
NcX+rh+7GECTy9V4/+6b8xUdPfeHJigyMvkOWH6cMTHpQSth2JZ1RoGopdJj1yzWsKOVK0v+SE+I
KQ8PPi3uQd7jpDgs9ej8TwFci7lS7AM0hd9rOvIErbme2omThGhvD8hsT7493iJ/Del/a5klARFb
7QPpw7OD5HfnRj6Mqg6hyHeIjJg3UnQ/m3J94UzupyaU+XBy43zPbKB22UlYLAv0WxbbWlubd7+K
9iHTXCh3CZKpwhgmVhYWUeiegiDf6rkvOKr7aQtpgsw8ze6rzy1HS7f4hsHlfVOwE5NCmUf7fsDe
j/v9HxMD5lXvrl7syKw8/ioxgOr/dnTc5+r/euwOY5saTY43eGWz6eVJ0tlCAet4okMiCpDAv8xQ
q+ExyoQQ9SHvrTy9HvzrawKgnZKCkLYSaUhHX930Az99jLBMjMyvD1mvSg3obrSEyi7QWXQ6yb9k
oU1yTpqwsHweGY6q5NruU1quubZYgA0Y/2mwlUtJXsZzjzDgKraTSp2c1valKa1s01TDULv7sbFS
yv6EAcZU770mWY7A2VLMK9rPXWvr/IcFkXGQYodFkThtgsvx6vEkCexkosmKUnkJvpTDzGs1qwn7
qjkKCJfcI9sHZ7SpcRJxTTZr/fOTB5AqRQwfzfL3d7LJUjM7tUllC/KBRQoKnpSxCS9kJqTzpT6F
p39Xrf/2AuHXL3O8JMy2VW4oRTlihEOThFqoltunYVomqvjOWF44nlHEnGaBVMWb99gM+nIqZiWp
M5wvmebO29unkagDFd0S9TEGt9lm+qdjFKpq8mJT1JMtnO+ba+fS36kfxEZMSzpws+Qd0k7RhK6j
SsOWPN6bGX7HbjCsrs82T/qcoBrMcxdaINttfeTztnzp/bavL6qf3uQP/VyWM0yxwxTKcuPDfo33
u14tNAln1Ou55LyRFei75vOW+W/VnQyPEgpM6elal7XtUugk0j6qiDtZKsv0qSQSMV857F9mQwdX
Yp+n7Lnq6zJpi71+Q6W8XNKIaqGysNSo3PUyQ9NJmjg6/f1HKDjF5qluBrWRET5Yg9IVK8Ts2M5F
7x7I/hmPFNpfiGzGUtli42a9ulu+2YTFTZ1o2gwy35G2byPC2SuFEvOkex/wx4GZ9m4qGncvzw1p
9OHPifrq+HAKajhjuUpefpfJ5jm3odgeHty+sPTFiQ57/4oo+vMQ9FFltS3juIOQ6SeXbL5AWIjF
FYY7xyr9lQAINuei3DM9MvW+vf4x0bBe8r7sTNa4U6VQFgTk2bIaueWBrA+kr49ymM8hj1G4qWQN
FvMhz1zNRfgjBCDKeJTOvxbK0hQqhW+P8lq5mCUNJTrEuqS7fKpaYY/sxIciXl+dt3QDRK3hv8xw
nVXTb8yxUpiJR5UQ3m59+dNQmumnqNMYX+ysWiuETB/pNyCUjNyeso+E+4j63kf3KQM5U+5gzQET
UkyJZqotvr5Nr0FC2NTRyQI2TyeA0G7VHsB0j+OeisE3oCDtIJjXVAZ7NY67eDKFxR2NXpdJtj7Z
ygyCyScJoiFCrZqjn0G/532lca60h4Aieq50m1w+BV5/CLNiD72rcDKE06dPrmKRQeLF2PY7AjBo
60NGyJGYzWgx/YmIC4G2R1ctWOUz+Ol+BkOK3Yb5ed3ajDkEKfxvC5os0xQWL2nfvtkbJ5IsMHEh
S8Q9Fi49SidPjNCWbPBCzj8fff7alygyYjGkXNp0zPWJzeASMFOtXIOqmWjfrFUQZ4vXIlngC0Wt
S08No1iToR8fRLwkpal8L7dR0lrwtm72AJiTnSdmAi19QJJLINJ3kIZOag0whHX9uD841cbkxh0O
H2QgGvZWQHnxDdbKD6toRHND4e/FKCahcmPDMITLqaNM7MmaSDwd9Iobau7ChVvDSThSVPU+xqWS
8tiLLWFk/jS7vDT2FPXoF9panJRS90IKwj/0vuCm8Rcro+HB08q9p/XvMVD+rFuG8764wrPXDT3w
JnFVVK+GHy4w5cFari+JdM1YT71lqDfKQV+P61Jt4WyCkZHhSm0hVDXKqPQeoSgWx6lv6lMN16eD
pKXvpa1WlbWfpHE56He3CDFz8+6P+9Vlq1fNeUPF+zX4v/1wDotYPIjVhUmtfnOMb5PoBJVH2LOn
oVv/IqJuuFi3EeX89UUFlEzFqvV+TITavPHS1P5TUMToHYfchHjeR5J39XAKG3CCL+1HyTkTYVDT
j+0QlGB9usmNyChtt2LCuZoMB02FVJJF9lFXv79r5A8TSfngjBY83cdLNMrgwv3V+TPR20Hm4KXO
QBG3neevZ6M1EU5BhVJmcw+5ryt4auZQOSuU7Wc0qBqSKhA+rov++KyUcl50H3WP6LDh349pwENZ
9HKvRCDaAN2SEQN2rFRlu46oKIejk8zSlx3Yn16sPZaart4KjNbjLsF5yIXixhw07hUqMpjhCwp4
/XWIIakuY32ftljnddNMKBunjPaRuATkT0+F/jwcXmWspUg5DJzgpO6GQ3kfDYKILL+PvrgOopE7
C7YX7+LXXWW/Yi0bvPMXUPgiJOvtSshptENizvMZkXNxQUR2CJBXWL4iIkujw5lEYVCMtWXYlHta
sUCdxl0t20+yQK1wmczgG3saN3NEUvSJZGabFhbxYo+kyJXz7Xe16JcSSChRZzFjVpN7NeOK359u
vhd1DcHtopmPTFl5Gn0hfEqolxnjQl8uQE2oXSXZjRGaVoUqcAfMuLs4IMIElu9eAt9TB9eocAkj
hClRxYRpXCvFCr7Nnt6qRzT86AGlbpzhoe9G8S7mdngycd3NCspoOQ8hQApQtDiCfoJBW7VC9W6Z
+yUtfhuM+R0O1E7i89chhiE2HK22RalBnbqZGpURWYvErxqNtcODx4y1IfJvlLwlMM64seL0iq5k
5WjwlLwUZsdfxfT5x6z1hNct/1iwGz1HhdkPIZM1QdOYDiyRcWuvLUC1MjN4mQRhGMeWnreyALW/
YLundkwNWazUJkPuZ3vXzDh3szAzYG1t+NFAC//Qj2m+MxoGeXeH226yqaeGhnJDoE1yuKqYGjPs
6LVkN5Gtw6e4+1MuzNFRfkrH9JeYtTXBAVE24sLqLcEBcu32jEOLxVgyq0eGe/SNralBFWFWC6UJ
fTv0CEpEIkYoQzqKCjILqQGpsqH1doOjRRqrcpDkHke4Glnw5P0540Kty9YiuYO5L+mOnlpbSJMm
1Sc/wB967fmYViWtNuqRXTMcyvKovZB6n6D1C4ODLi5bLIwnmQRbUy5i0J5sDPb+KoOqpGnnejoc
QsqT0cTEOLn8IniLQvrde5pJdA1McsWw4/MkymPuj+ffdlCFKpzz7HZZ7eLe4WAawqGc6ZEAgeg9
H3asgQs6bvFh0ZpLEVikV1pPbANDdk8/2Equm/t2YrdWP8eHCfIv0q09pivd77c0/NuGyOS+aYx0
byeOzUep4PBCkrY6a2j4iYpEWYNW2+aRGdv09MON6viiTSB3U1DfER+qhMO3z986izMMLa8ydWVz
skmK8PKSjh26iGY7WDHSGZcEDF55yS2lnfkyYAY4QRl9j52rT/V0uPtpZ/fEYUKEfXL57viyMqxV
Iw3uEwLfe3Pt6wUuO39jq1jAajDHdhmxx2e74x/vcG7CjLDLdByScBnqMKos3BxcSkWozo7njE87
R3WV049lF1tHpRs9J5J9uAakhQSSXC0nKVEih5dw5PXz+7eWIPud35asni5XGuIf7UqoXe1Bv9m0
Osw4CiQnmkBKMWoAPC06K1o2Bh+1I/oGM38UKrIzxIzxFfWCEbxIw46hHpgiRtGgPN4antuxXi4/
3EjyTZMgHh/kx7Z83Hx3/Zrii1URTTESGfpK+1t7PqGW4fUyz7sIPyLoiSZMkYmUxpNSWZyFkuJk
09VckxsOE3V160djG+ZzEnmsFRY+0msKaAkVrtnpPN80Fn9d2jIzHqkJHmT2Yva5bzTDIqWyJI+8
t59Wv0kj319yszBde8vwxBySM6Cpq2dhHF6c8hKQoEcV52TiHDgTHmvM41gwosoaDcRCFudgGleT
K+mKIWT/ErO6HLR6M+ZllGLjlqW2JsF5otznnnTDfvRmqEwEkUm4xNj1s/Ok5cjaESGTkrXzdyMx
xpdr3iHmeBvG8RHT3KTGb9/OionhdZ0u0B7ZetVfLhVmNJ3zJt+VtL2Myx9p7SCwgefShV/riSGv
SOOd2TTDoHK6Y9f/4daH9J5PgLW8yqXrGFdeMGKp6iFViLdJ1yV6/cSm0oflO1bBZg1CVXMzUqSF
1IF5PktOlcw9rROFQqnIoTPNpjPbz8RUefnLVLEPlECTtSiPRupbiJQfpp3tu/XcKXXeY6W6h9Sh
WOd5S2ww7InFJzjovFgPS4KQcBCphbSc/0GJ4a/jI/9CieHvl9e/lxiA/2BycInh76Mt/80lBuA/
3mbxP1piYP+7xAD4V0sMQDayPyWGPyWGPyWGPyWGPyWGPyWGPyWGPyWGPyWGPyWGPyWGPyWGPyWG
f377T4nhT4nh/49LDH/98f6XEsM//mjgEsNff9W/SgwczzcN3sxJ9l8sMfy9W/z7EkO9qma8YssL
76uqd+eO6eWcrdLBRRgpX2sHegPskoIX+YC63XqD1JfVXx+j8s89ZiqWW9RqoxUbYI00Z8z3Fcu6
qjTrAnO1LKRx0u1nNWo9BTRZR/G2DW+Y77HiGLsmjj+xlEVb9O5+ChMf79kiqL0TCsh48rrpG5+e
ewH3dI8+ZsoQgp1EP9j9oDfYfnaK5s34MNSkLvJ9zOdz8ynONZLc9HuGj/Iptg1aBFCmAuN42Csx
v8x6zZfekXNsRR2MBFDeb1UzjgMqCrj0en5KRUP7cKN/n7g4Ct+dr8rUjvfp6mzx3pk3L0lEO9sp
DvlGVX51uz8wliw/8rMrNq3IJjP2KUKuPzJHHGObUpn5kDjpvRv+drLb7Zj7nZPsWtVI3axzm0AM
oAphBVEviFDc+7p1Kc7j+mDC2EPy9SYjTGAfm53IUzihdAHFYP3XZvdDH0EUK/Q6JyWU1eg+Erkc
iR4yn4S4+5XqrN2w+jg8KbLwjScKg+9G43F09zzBNy6c43HIS3J9luzfGz+q020lSLSblmBm4gt0
TYabcLhMuJ9VL60IpjJI8uV3XysJ28mY5nE6dSja+ZSmy7hMeKOmT0/0+FTGqrcuPrHtppcaXzQv
WqH7LH1B3Zm4rV4WJMHhxQv5Ppb+frG8yfG42GwNtmnVX8K+gxHWt4nJqRumolhZFHFUJpt/scqE
lMcSvylrqCHf381H5/LVOtTeFD4y44Dr3QwXpehczo9fwoSWa/nFhvyKZ0vHn5oOLnbvbqC+Ft44
fT47NOxyh4lCyG+MhjIMY9hNg3jNioFo7Uu/bxxU+1Uxw9bVjDfS7/rRYnAkaDwijwwjyO5rSjDw
6+jWqTc1iug0UeS2I95B0o+zd32Uk/l36pN9U6zy3nfwtYEhwDKpp5e5/N39mqGApsmzy0eNS3zG
zxl5S7GB+s0OrY4hISGbRNLlhtcFTJ8FU2E2Sf4v9u0rKAplTQAwWQaRMARBcpAhSc5JQLIIQwYJ
AyhRkJwzDMKQkSCIgGSGMCNIkCxJ8iAZJMOQs0gckHvO7j1nb9Xuw9bWbu0LT13d/Xd11V//S/fX
nTW7U1KPhMyTrFaUvlJQm+ZkajS+yxa6yPU+nDuOtyOFeivk6sw/ekV3q3kuEdWtRhOfp6lFTEQE
LKDJc+uQjCSfIIkpkSwAl/E0s0zg+x1fniTK+8/MvS0Rfzrq1pyg+2Roq4CSwS+xd4nTPqfup4zY
iNXx0gPl15NN/Gc7ngYgFhM5WiBn2jE8hFo3iyXPAqvwQPzsDP3J7/E9CjAiDm5k920ipv68yOBp
UWkJRg3cKJM+yYxMODbwEFVzVYv0gNFPaUgC4kQ3+vjyunb4kouOiAS5kqnA3XZTLrm95DYaaGh1
jijRe/iiQCwF4wBoNUyXo9imar9a4tdD8fLrjWOTDwLdvHLf9Ieti+LeFcZ+lvCxnba3HiIzfip5
ImoalX2HoyhP5lfcg36E7CqNdVxx6kDnjz7XSKcUQz2TqrX5hHf04673ZDl7mQvF23/3aMPwJU1C
S2c8EVeOhEjPhivbNmEqiYZuokDWpqXaN2ZTrhvPT/xty9oz+itJGNZnh07JszSndvNeaV47PoKz
AuEEamYMsFBhRQ43Hxx1bWIzMG4xgqbNGug6Q5AjtU8kZTIl4Jb24Isw1gUaDNDCZipX2kYsX8aw
UfrCCUNfPFh/jFzH+XhEQvZJXVnsgmBSUQ7bh7iOV77AEEoEHZbrtcaeVdThGuOIaR5WVZummVe4
yXDv2fCwH9HeoGN32MAdCnq9Y1Lqe20rklQ46zdtVpRQOiulW7Eiy+sAJ/ZaSIamPekJhe4omSY+
oq2tfxMUsE5c7oTCUE8xHkLaVb7h/Y5NuLoYVgsWhF1o+ps/HbyvZ88UlNBneN9VP2DcbboHpvj8
TvWMfN27JsnCCqfWofvGaQ/cd3LjdyawISllM2+5UvXApxiBYR2t9j3KKmzMvIGlf77ZbAF9CoWo
vIkfLbMeIP0dGwqHeT9vs5XANy8GSGbKFp3rfX3Wf3hCE5lfVFZr/CzTPZgjJq9rS7adrOKE6hun
UwBPOHkZ2EQgf4+1PTQ1woECj43XgiLui5eBQP+CukC+zx9tVAJ2ckOIGvtAUgtXfzsNuD29XtrC
nRNIb0qLJH8k5yedGU2gD3spCaLsF2je56XsO4gzZK9PPeZoyk6/ayWYqtHZ1DGOxnFnPsur0rz5
4nfDKLVqmhTTgMO9W4fuZnfkBpD3cUq22qKS9Bx7Yc9xWZoIWB3f2yPDwezfTsvFxvQeKhFt+wM7
LpcrsPABNmtaivJ6BZgMfaaUzBhAvds7q5XqQKRP8KyYpbVqRvi6QRNdt7xe1Hw8JViAXkHKoCnL
WDTWOs3pXTTVeqB0URMs1qiL29mcojzGh7Ic/Ufbn/dCHsehpdpTabi0RdRR1w71qX+92cVtL8xV
PbBWCmk2es9CfAZnNO2ZXdFd3USfbjZMdgpi07vKk7bZtVeZ28Sg0QlkXsdu/u3pFPve22Wzd4fa
UvblGtnKys1JPo2LN6U3qs2FFK15rfI2D2s0q1ktdmNiW8G9chz2YfrPOGmoHr38qsYp0jNreA6u
9BLNe53uxZrB9xYwyC+uzHH1QzSNkM5IOX8zS4T13PBhvu8cPQBN8MM/cBub4NV0rd2+FXdmwCz1
JCM3FK+WFGfkdJzlN1V3XnY+MRD4mWJ7yUOFKv9pv9Xs8DJFPpaLukQD9HxTd4xMKcwnXrIfi1O+
v5PCt6YrraR68Y45t7IXzIAxcnPThfU6T/tw/muI7LXX6hVId0jzgKIQ+Ns8gFyXC/5mSi3sBijS
hw8e7BQMAjs36JCpsCLSuXSCFpUA3+fqP9o8jPYq5cTv84ZRn1cIUdQw81mQR9R4PbvHvaBD8tbn
GSn3HyV1VHP4wfmONRlv8u4eIaqK68CrZkEeS2ngKDqSmsWUz4G8ECoMWWBlr7fWyAXjbq6wJAGf
0vOw+4Bx52sJnZeWz7IScwMjPh3DW09yxxgl3tb7wtdsi1XkfIcbHd+58lJ02GQSxo0HqfyAC7VD
XTRB3gBGeGiAR5qYgm1mEiPJToQ7yKajFsFH0bi2qEBC96pNuIKDopU5zeCP3AMBg3Vc954YNxWT
W62WKVEGpSjiLZbJUybSsZFn6L6mya+dFBgf9Jtd+cHW8tVinSW+Jnwk6EewzC+Pg885xCoccYqI
BBW3dckqwHH1ZAZAkcIcCCqGEVcoQHF/pxLZf6cZc4iThgumKKkYj6hyoUYne4W+IOiIcApwxQId
phGkOq1onmEbBjwOHRNohvyX7EUa9TlRo5xKhuWwcS1r/wtf/c3XS5fLStQ5gOf6m4xPtZMP+rwB
y9eV2ltEKytU30oqX6UifVVRoIMHWzx/5LqPPzp1HTdBWSWL/MMLvYUd+xaWgbBeV/XM9fMVD1nr
xB4r//VTe84VAY4z+wyOXJuAjIwtREktdd9ehiaIkx9vITn01GIcQlu9SkXafOnQkstPnDaE9HCy
ejAK++oNPMj7fPBCdtaE0Kqf8FV2JC0ZRNzdn/yxsmO5TDv9XKqYqC5mBbzuKWCu5NA8ySUqU2H+
wnP6i8ZmvsuKx2HlaMOfJZ2zXRFCfxIfZtpsEGz+QWQp4DC+YnKVgNnPQx2DajlO/ZAiKcWTUIBq
8snH2X0Zj7IfysFNN3FKO3K/IgXcg0dwCqmxUQtnEL1WuxSRS1TtfqMKxCK25VJ9dkBDZg9vvnv1
th8j29bqF4SxvoC62vMj2/Z97vz8wnZjjNvRg8TsXcqayF4WYacnPOT7DJJlTpJBH429r6g/6NuP
uPHzNcMeztN71bvdueqvvRD0vA3TPBPMXrAtyeHCLB1l9NEgCN1Dmta2e/oykm5oGR+7DCeZaogg
ADAWqESf7qRgzUi6oMUoNjvUORUFov164/v3U4V4KWMxJuDDO7J4QywAR8pSj61kuA17KAS8i/Mb
g+KDRxVN159ah/7UMEMNovgmeG2TGoVK1alM5DZXIHxNEuM6OF2E0DGRxuOjqZPg2WBJd0es1mrZ
8W+db9ytl/uoPaqV7ek1tdzhME+ysE/Kb9kwfCo6xNePf7GWnYxGziOGzD2Wdy6vtXVD72uH0jZg
d3YcoKzXhtnsOdTUU1YIP4xe27l+l8zRlv4AGYixExhZyvd1AEI3gLJo14o6JKE+IdpOVFHSNo6C
SOizCRNoahl9bkbO0QbLjNL71iXciFjQCtzSkeFZ/BQJnQVFvFT7aePn5e3kJ2C5uHZf5srjV7Zv
afCdpXqkAcNXbXfYKs3Rrg8IIg6Ke1/buarwXSuTcXJerN9CDWi8OparJvijS4nNRq86xPpHHUPA
qnqB8Js4Z5YMRXLNdrHipNp0ZjCRVkeTYcl7+u3zb8tp0519jm6EPJfg69aN7hj94rUesgkToo1H
Kp6oKE3alBOdEacB3Tj7KfxLs32cvTKeNtM5SHlQEnqThIeumW06lMG35Emk5xC7hDtcb5ZEjy1v
QcTDKD9z4fSnS+Lj3HT+u4gTzMtwuhyzmB6mxVzG/ZBHG6ls5cbl8NExWrpGwJthsa3iDy3fcLNO
MPr1KQnSRxjaNu22Fa1pJEHM6sTFkwp1mdA133VQVIxY1OtJuhDNHotw6eyL5kBB9DWVJRZUXZzr
v9J2Meb/mbaL/3Wa/A9t/+uA+b8J63+9oP//FOpbkf736VuRvhXpW5G+Felbkb4V6VuRvhXpW5G+
Felbkf5n91akb0X6VqT/Cvi/Fek/1/0nkf4r0f8i0pL/jBP+85rj7+F/C/zvibTk3/v/y7d6oxH3
DxLUQWdG9uV1dV1a4rg4LK45H2CgtAoet3jpJtIjOcvn3p/bv+N6yvgNPGaHCEG+qBrlt9fsvdQz
RXQ4Qj2R+7JncwUFNrtRutx1xNcCKErTFonnBMFkeCymVN6crHWN0v7D9RfxtnmgoHY2UmEuuyFR
in7M2fZJ8s/PqfjnBWFEV5oCD1OZ7mCnLzLii8xQ0VRsuvl0ZdZfDutw2hPc7OZznqR9erV75zHS
EBAhPqUaxt8BvTfctc9BASF0uPLGKEeAvCkJqnK7eHUykQSQwQvrn7gF4JnVFtnHQZ2tvgPQtsCA
0x2ugOt99NAUPsbd278dBWlp+PjiDYypGD7DRLDocXq1+2s+8mI7F4lCaU3H+uxeoeshrUKXNDl3
dy6uktQr4kjR8ffqH8yR03bb1o5k2zov7CSkeensTV76EqruinVvvIY8aKgsmH63hf6YoqQRMAoZ
kEIa6zighdb9zCdFvgiqP5NoQl8mdqCc98pzTuiG5FKDqvKmGlt/7ZLj4mgVvyWXcHfhH6xoCVmm
tCBurrlbzGP+y3mLJaH5MD2Z328m5PmneBSmutXPtt78+joaYmlgkNZie458nG4+Mz7MiZeRnc3r
BTJdHqg8qYKLalWLpVO6tBRhOVm9z8QzsnEe9tmagdmNjXWNpNgckvhh7z9Tamz6eUpt8dn5ic2I
/pMFBuvO74kFAjWumWw3LL7RIief0diBvbJy49hyk/fKs4JD+8TBQsbRhUwx8MjOFLmpV7aKBkwv
yh9lC9RHQuo48OZVxp46Q04ZjoGtr72NqML5GmyN/IN2adhc4478osHbcwOBLE8u7KFzXOmdPil4
+HxKEVOIBGn2LomkeySFwimj2mSLLiZ4Q+yZx7Eh3h5bAiCbtw0NDSUwJrtl7Nw3L0zwELyGQ9kI
KVJiXkmM5c07Dk3ag0QT63DJRMMVVQ2YC8FAkNiZQlfEMoOBZYeVrNBE9o3bYHik7q7w7HZ6ZXJ1
7/rzI21e5JTvs4Mf1x8LHGVK359dKd6XxgCIsipFJ1SgNUtgK2Acodr6UqLQNIVmcWYiqfnsdO6B
p6hYMl6Shgmr3pO9MKYSJ/VhQybzxdw4vbWSPs/nGthYgQGCorTCcNabhULNdhtBCqvtgljNyRiR
n2xH09bC0nxaoz3z/pZVWV7lG1qPIbIjr17mB1YdBN5h8CRG5HIvBf0UCUNdTTthO3HwqiDTJATf
Wwo8zxE3szMIvxxVrUyoHYBsIuwHnEn9F32+CPiWdasXkJ82duwevfPbKyOGN0BycecsJd2oXm6P
bmGRl40b3jmGEurQQRZyAsgPQzSGxReE0LsPyzjWXLYA8fLCZEQ5aJDL4bm/jKX0wnGbJgXofvpq
XnzL4Anvm7o4juonian6SZzU3icwKr8BxOz65GGog1hJeayRExkLTG3C06hhcaJqaQJRMWmpmGue
eo0Ss+yeksDvzVBWcH2atcp+DttrKRJi+xHCpbsLhTL98hasrnT19kz4qcK/yBsN6oiM6jarDjHG
HQfd7cSLRGAmwe4hJQ4wxAy/37POB+aD+xGPtLZbm6shxmK7gXX39XGFlt73v/XdXoGShRCTnsbB
d2q43ZwPY/tgfVJO3XOlSmyAZKoCokqcX5RfMDsyFzgTQDu2yVNW7W7cSc1e20BO+QUrkTVf3iQS
3kJhdZlsmjXgsY57zjgB5xqV4sV7Gh/VxTXR8sPt5oomSSl8b9TLy8KIaY8ukCixwnnXeUpkWzs8
8h67MlnMgQ404CVZKeknIhp8dpow3VhfG7rBzS08WJ/TMA8uf9+xded+f3DnpM2rRfnrNWWrHgZ5
mxaCeDs3MrnwQoV/sHNfwXCw4R7A1eglfEu01XvvbUUv0QlRNqIudiNiESxCsHqNYIUQdaNHXb1H
J1rU1bsgQqIH58w338ypF2fOnLvj9n0u3pn/xTvzn988r0cGJb11l8PQe/9fqXGbBGr4n5CqEsij
vOXyoS3eyQ1Cb9Go5G0LCEW4gCVWqp6F4CQ5ulEOj75fSGHnTHnZF+cVFRX6ASUR0b2FL1xds43u
GACpVKhMRgh7tthUAGW7K6GpkdqqUSyG8PeKthMMGogmIa1afPqg0vsy21gKb+qrT+o0uAlKHDD5
5oFQBsu1CCjkjcq4yDDdEzHKuYHAdylQT6Bhu7RQuf2jiBFnwi59bxuwGHFOOZpK+cGrqIarX0MZ
jc+YYaXs3EHMzoYhR5sgKhOufBIdG0YNRhf8mZplfQwDqP98QOalwcjS9wy/BiICh8z8sN85eHh2
9hMNp5nap71RKZB+OhDNGDHcidE9rUdy5w/0oUeCCK/tfpjuD4VZwwkDdvWQObYJ0Yikbak8O/rT
zMt89041OVULk5UXre8XlmchFX1Inf3r6oB9oEQXgQbz8cjvCdx+5IaOXgscMo5BuzxXxc4CdbP3
qoORxmvjZYrX93Tl+jZJA/jbJHm7RAximX2QjhA489EgnFJEuWMydAS3jrlMSVVcGSlWvMFsQZI7
qCqwcW2kaTjSkTRCgyKNrZBvMCVD4nsQGgd97eLuw3WHssdIG3bdAmwDXIjMGNY4l92VvEYfpHNJ
fIKPxfQquGvZMWQU70s7vTGvjTTfcBslXhdrpTMfzCGdzzAuFCrhiC0RvHJetCaQ8hlMxQnESdui
PvqpFEDAYYnblYuiq2XTuKwrdNlV/bMgpovK827043OvbxYXy1Ro5Ol/Nf06TDGmo3t/s5bQZkqD
WkmzgNe8p6K0JZLjOYl6xu6y76ZP7PHxm4245U6nuC6B8Ucqts+c+7GSIiysO1KRzrracto3tlRO
jFHP53VoydQBj3ifzxFNqtGmRzAfkl055j9fPGPshR9Iv/r8GXusVb9B9oGMVnzu21jhnFQy/sim
T+YSMQh67BYUAiLnFWVjVZCU0i6I3sy6YDgK9Cs/FFbJnVWNRqP9XvDOtdR0BzFGk9xyhVkEzCG0
DLpgsow+YxSz3xGFvotP3QRg79b5NUERCHHHB67fxagjq6kwPWySQyV4lb77ICJ37FopPY+Z0xCS
aUS3FRiOq9YSfh6PkH3Goiad3xQJT6M1QvAgGxgqRelV3m00l7vrzcgWvT10ixTn6yPcHwJjN+G+
fnNmMxmtS3N0Zpk5TBRA3bLW30C7BsvB6OR57Wg7c6kRoiG+cvOGUcqXzFoi+MOSdLfAB4nCwnH3
bFrN3sLPBQ5ltfRZJCWtK7+uECpVNE4ehJ4YWO0utTJtDZsb/sxdHxdOsGRATcs1+goOazVPTODu
OrokhziWXTqlkH28fvFn8Wr03rc4XBXZ+K6+lGNaEz8C3Cu2300vXjCSjW23Im03n2i+uVVWSqJ1
2ewDZfBRIFZMCuuZ1nXjhvhh/i9UilfSGklhC1wl1dOopdvxwk2zsGI+YJLD0wtLH8hjyVEF34Hm
Fu06FQJz87lEdzYnjR/LucVLGUtTuaMY1iE13z43C/B4ATYzYC06yC55ceP0dZDklC1Zjmu8T9vS
JkB668+8rpj3BfPQvFEihrulOmwSYPhBDaj/0Qae4hQkdKPnX7ePocDvDGgLReGRrhDnlaPegWPo
dupOhHmn0Tj4dJAxH9Lb1y6sMScqYPxWPlL+QxGUYk3NPU8pwsfbhAmGUE29QYPfVCPde85y4fbo
vCPCmY6XAEtK5YqxNx0XzpPJ1Zrqux+5EQ1Vtsdz4cITu191ftcw2NLOZlzQYC4MXtCzlSWnaCq2
gB7V0PCXcTA9KRBcph/kQ7FDspJEmSF7Z4fZytiBJmgzHxlOGZlz6vus5uwcCSa3FRspk5kczb7r
ZkUQE1iogaPD1VakzFJIDqHoZbS9XphTwXg4eQSIT4dbBUr8VG+5H87WzSD7Oq6I8Ys6JJ23vcX9
rcEO4MtQQq4JdXqviL9B24qj674o69KtWammTIK9fKJ9obid3u/XDxlQRQT+Na1pKizw9LEDdBMk
3aLoD+39k3cqH/2xj5GJx08WUbIkdKH+Vlh+ydaq26fVMWIC6lkzx/NFQPRRcSMDGbmpHbduJsVj
rPa5Tnm23j165xU8RlnvVRKCJJV7a49emiB5IdS1WTeiw8J2bYORYqPfm+3dcX9BLnzTZ8h/HWbz
JZoENVFt0YmN7i3JkAPqpSq44zNv0sQTB1lf2VuO2F3qNWXJZ2Xtw28j2npvqHzbogx7QkolBJ1b
7TR4FSMq1rcBl9WG+vYJ0ExP6Hnl44VSyI1onpkH2/qOZDn1iTQAuhmprrlksXAdMttbhVOoEDYv
Gt7uFgqT95tTQJhje5oqbnNfn+JKT8HGi4t25fi51Lg0pKX28qBPKmqtgsm25m3y9CPxqpxZwY8C
OQWrbMbaIqI7DdF9+UnjPstilJ+Z9TyEz/xE2e2SawVL/b8L3w8Y4ZTWvGFO1dDBRZx3DNeckM0n
QX8HKp0yG3T/tZjo3h9H5ksPP3vsJ7h0z9JHUf3QLhTi0Xk87itnNZ+/V4+Dj1P851rsv4Hhv3vq
/wKG/ym0/x6G/ym1/6cw/Pc1d6vLd1B8B8V3UHwHxXdQfAfFd1B8B8V3UHwHxXdQfAfF/4zvoPgO
iv8fQ/HfIf1XKP4nnH+D4r/T+xuKZf/1Dfi3Y2m2/yEU/xP/f/5/HYzCYu6/WT4RHHtoMhLTlWW3
NF3xbr7P0Abs4uW//7CoeaGOsbx2nBu8zbpt641DrmKKx1UyEM35VpFxmPDXCE5+tNB7U8D7yuSB
Jo6a9gSe2oIUCYnmk8SnSXO/dh4fSQW7EjOVJtN7ktM8TjpRWp06t62RzS8po8j9+TGgyNXKy/So
JCUl9HI9SmH1lA7o/GMdYZZ0tK/M2ZtF0NaSLAbpaU247fSWWSdoaWQVvx93zlvbZVkcmposadD1
CXO6xsFIH6IS/03EjjuVYrZnKMv2Z0GD14/rk0jUxvrJHqvzRs9J38xL25MswHyKGY1NqekOtYNy
NUmp7neK9zKfJWbthz+lemlVBEOfXInvh4tkVA3tn7WXB2GHURsV7MujZ0MQdR4krIIPUb+kLPQE
vDZBCRePCenM28kOcEgBd1t/XEIqsxbwavWzDch0VdzA/V8bKxD0xCfeMrH3b4cGAfXwwAS36RyV
jnsGRhw6hVHFB91cbrQF3AwJY68GNuc8blLItM22+FgaPfTJIyFd4jF8675WKMCvqQ3YbiWx2YDC
WhjjyvxMR6LBr0lPULHdbXvCe8E3I4EzbgNKTnFg30X3sxkFqROYzCXiS39oXI4MBW/GL5oPgV8s
CgvDneXX4lBqwNb10dWsaZaT8wrYC9oGZsQ+5bP1z8F/yKxU3e75YK5IGg8QPQV8IbXRoekDaIbF
xJu309+FR3MUvzl1veJvnYi1yvtRWKNuH63KdAB8j412OB09+9y/3M653NqafZJpZC4x6HYm/x7h
njvOXs+8QI5LWqE7+Vblp2qKEYMIfZ7LmFvERlw3FUQ7PpSVlseIK17PNU+jOzbJxbMX29nx+qTN
Rvld4khgc8ScXQwgcDpc1FJn+BFRsaOEXH9+AMsbKhaIMW7S1PyH4xT/Pr6PpjKbf4EcCAG0q8B0
lmevxAvxNJ7xRPjFApT5snYKx7cz45lqVwQzJ+avBsM+L1zBYvjXdwRFv+R8E+geLHn1BMVzWDZR
eUZ6WQr8th1rcTXiH+ut027QIoX3lUSYJdKO+Bmq7MWjG2kMG39WfeRhVbEO7ogta6ug61ZXG1nn
U+LWGVzh4m1A2MOiEZyWQBUbprgnkEKqmDwvD/kMiHnxb7GFp4i/KD+b90MV6A6pOVLhfOqpSalZ
J2kl9t1Vk5LKgBmjzJ7jmJZMLAn6D8G7nqn0TjnOl39Yz0q3vBfX6Ka7UoWbgqvHY2NSF3xMEiRP
nk4es2DNX4KzTI99WFmPpOnyaGplFY+U0tLW0BZF50BBE11jUCCLcbrS5ziG6dOAUiYTRskGjsID
3OPQmP1F8huM33korYr67YxLk/LlrqD0ugvauPzjlltukMDSPso4wsNUoKL/5Ma+fZECTlJKZaNg
FUhTYnj7dS122wIMxBQRLHBH9eD8FnCbXf22AfGD4YlTDknyCgsrKvw1xDsfz6tc3wCudZQHPmyB
ggI/iC/KV1liTXb7MTimyIE5yngGg6vewF5v7HDWZo6XkzwlqmBTJZuWA+FCXl8Zulrk6SR7mrAh
40hyDneACP+4xm/ybUjt1eApvH7kz3dQX4NfoxwZi09OJGfS8SK5Qz7PUx+pqEqtGqI518j05gUa
lAYxU/TCVxEOxpVDZBc3ZkJI2/y28ywFksKH8l7aTtR/RrldwuvbwWWrdAKrcdykx21WysJwh7pP
zGLg7qqv32G+E1XeFj6tTSmvbK4202mQUylx78t1TIhL5rcmtYHbujQXbM0ECBSXEg7iKSgsUOw1
EjRtrdXsW6QYgQnu1/OK7OL8ceklN0BJFwV4BSuhFdXOZIHyZiNr1z3U5uG7s25ORKZ4gHdOvFEi
DtqwzKnYVdU6AqULq+eiosZkanjyJAmekSEoD3N21uk97XSvJpw8T7HOKuPxSyEDLeqve2k8/NVS
F+4paBII/TiXjT/R2Ab96DgSXSNVWPcWnfMhn788Tgphn4b2bhNDtTlIyCGgaZ/i5C4/0GnXJ6M5
TVPmL6Bv8Z6j9cySOtwJx61y3NKwTcSwbT814Q3o7Fwd+jQK6hI1sMYF/rCAOOJJQPuOfG7/akEW
EK8AJ9E468gXOFjKfRxn/32Dv95vL+2sNJzxw64YResYa3A8gWGNMTinscK6iGJI7QDrxAhLsSGQ
3vF4SABr96OESWWFK5THGxNtMn+DQpDzZDXGn34BvAaozzETikfVY4+s/0NMK1ZPMNZ4o633GTSB
O/acNCXDLM7gPKL4/hyf+xOplUx8BlNLWomrxZwg/Yvj9tXJzB5PeV57Y+uGPlqTaUKOoO8VMTeM
5tW17X1xXsEQc6gs1f2ZJT35cZULZzJeB/Myi5sr15jSX5XNi+v3fYpLhPbbwj7Za89xV2INpsJ4
GmxBRIoZX7uyp7VmwzwpT2slun6EW81OXng2khPGf2PR90jRcqDi8TOMe7j9ZedJrzcXkG51gATI
Ta/vgeXa6aEFudogm3OnCb69hB7XTNQ2cOrIruGcvRTaa2IT3b59Vnavs8KsWJRxx7TksSGQwvta
kUgh3ftsocMvVanQ8bGRBNCJXpxSwa1fpa9HMo5oUr5Xcj77qOiDPSh/n0HbPuFIv81BBOqeky8m
OSY5kdBNAu0rdKy5/7JX6HggBKhBT+H9SO8imNzbrDnK4x4FgDhNRvsiOijKD8751iME+VE5X6+i
vFAvKaK0m+TTjWuB8NfQyaja0ORB9gOsDyM0xQYp5ZbFKIGBHzFPuCrEelszvaUclC+YHIyqpXd+
a7hN5rU7JCOJaZVSxEiu7XhZMy/qZlA+Jes+EH8ojsnfSK6iqLOxfYgx2eMoem4N44BF8SlTl9Lt
kn7CZLRZgqhHT/zyYvtPLxDCMJuS2K06scuUgGC5f2HvysOpat+1KeNO5qESkjFir73tAZmlpEKZ
CuGLMmROxsiQMoRC5kLGzMlMEkUSSYQdEUVo8MmUdPa7vtprX+f8/jjnXL9znX/8+ey11vPe7/M+
633e576vvTeJFHyIb3zAWpSp5suQQ62hNyfpjhZTtxM5d1zIuaNcEuNGzh0SOXdG2O675f8dXrc4
5WT31elloqg2it0lLvPazyOxAWV+hHjD7Qk22gZDhtc7D8rkYKVOlSmlGtwqQYUUKfcl50/WS+lY
Hl8OjPTVm6ILP3RrLU5Mu9e9nMWh1ivsm5kf83q+C5GLjyEi3kMgMPlLqlzdWLEwy9TxZ3mkDfsa
iZAjgsuuSQr0h5VN3zU7ZXl01fKmr3A4ztHhtpL8J7u7+P7KX/e70EAaU7w4dsPH9urXzsorPDLj
PTZ9iYWo1/28eiXsbaxLnxuhZVPC3qqD3+jfVr35clkffxK1w+RqyZyPmCpvmv2DNPmyjlcBxZHd
x6LQ6U6RvCpqFvGr8+fvvx0WehPo0LHk+22l1m33ShCUSVPW/sqvSZb77bMIcccR35dfQpONKm/e
pKe3NSY91VaPaI9zizT1zTeqbEtXNy1QmomUg4Si9Ffsfz320+Ur7RN5VX9ufbBmiEfzcLdf2o2t
BSxWUccVx2es5YSmV12axmSrlSvTfi1Hkr7g77UvRcnxGxfv6ljLDDCPNe6M+lntPsbNz3ninkkj
3bbWlVnZ4vXW0wOHzfJkPnd4VFQ+42LluJTFtlBXUBa8AAqrcqAjbsRDiXE96uypwOxz62VBayrN
HkEv7OMjA/iOV85lej4+OvVCp2CY2b11bN+OlnvYdkfaOq5+v1P8fT8Lq7MWWtunN8rDC05DlT/W
+gN2fdw9odh1ICFhSizEJJBdSjh68dHBC8YsD8XfzcRoHis7eN/Z5WJa+7ztcuJz04uTvs2hBLuX
b5jvTQRFm464DKtz/Ew0vqt3mJejukKoL78qpkgvsCC1ccqhAm/dXvFyO/fUzR/8+zH3n1yhmWq/
1ZSZkkH0HChsDL8c7z0ZVvnhC15Rz+vx6DUvzHbdk8N7UzxvnGzdk3Wq013pe4Zk3cr6pNdBfeHa
lRPLW/p5n7AwjBOPbTOfLTgX6nz3gr2FY7kFHSrggpA18/4rV99BjBsLAm4lyb8kL9Xtm/1S3WlR
Mcpz4YK/lHNsGlM359EIXtzXLapzZ1SMBHnvvmXW6nU/RlfCt76syhrPLYO5vocG33Q9maFghaSm
un4iqlrKk6FHez9PGp+jKFNiUUNJycl7l9aniK9Pn9VjLdp55IBA4ZkkmfkHa3avXd9D360jHXOa
Uw8w6zMyy1yrlZ6N8k2d83GSeKIesJpeasjKmR3D02pb9YOE1Y6gXW5dMH77TJ3Vf3Vy+rrX5Xjf
CjkP6EyVk0Q7xviKDJTb/YFXPFUjvIXf4CtLgXVErqiawi+J+ilJrUOK5+tEZj/Uv7ASMC1wzN/9
2tnR1I0p/6M+nvuCadKc86gzad57+mqv8u5rPz+f17nSMvUknk3jcV1jmq15Vov7zcKVjHviD99K
7dafH16zf59Gq9w7V2H2Qzos1sS6aFq7I+zMVa9ipw1xUQ/5rjN7hxYj5aNNHcW76YzqU01xoy2T
391mbaNqjQ5ve7rDaDXjDTr2dmyc7SslyeevTYgP3fPYNnyEdU6WODdXaXoMTkRdjTYxb3rAroUf
IN4077koWuvqzd2loTbjf7OEWYm4vRqb/HHGc+a2flK4zbCiswGDVrj3aSnmAfHZ6EtR7jVPv/rI
290ROXLNyI+R1Z4fY6CO9V9z7P2YumFf9HxiPTlkSZBZ2++mRFMRc7JjlZInLbNIdv6hmi+Gogu6
k9r2UXLXJx98UDsbz52XnfC87tFX7vzIcw79raqDAn0XKpw1aERfRnsy5y0kpVjn/TXTwH52LuiN
h1i1SE+Ib6+g553T/jfHcxMi+WKUxF82XqF5EKLr/7HwbFb1xhyt1KHQ0PtqzDMKG9r2HKIEFst6
6QJFmcbwIaORsWKhASeJ0n31j5bqfF0DtvvwtowulK5WHi44ztj+KhA1rouKfxq8zzBd6rqhirDU
i4LTA4Oi4T52yVLcMt+l3ONImtotD2hyzwpP1576UTzW17UuYW34t4j0tqlvN0dvPZKWrG4zjF0K
FXv61oM+IF9lh35E6TyHh9Dzu/tOhcu1SBhbxuTGlQ5OnFv9q1X7uen6raF9xU2MdA+1D+3cSodL
//5o/4zZh9s09DRoh8B/9RfyMFPwv5H98X9adET2/9O1/ztlf7zI/4fsvyns/3N5U9jfFPY3hf1N
YX9T2N8U9jeF/U1hf1PY3xT2N4X93+amsL8p7G8K+39u+L8V9sFz/1nYx/yZD5WwT/x9H3mZFCmP
/3Pjf0/YJ1LGp/5N8pHrIziOwGVTji2sBjOpe0cLm8Ud6Paci8Q6OQunqkpVp19wOlxa3D2wusYu
X2+218+SoZ3OyTCnzu1Fyrgbjj9Mr/BlOpcMFMOn1v1B+tCrhOz2PjXoOt+2+2PfVH9ZiKQebC3X
V7dVKBq4OjMZ2z6SIpGiIb1ex5RxI1q0G8vpwPqpwfxTWIS4iizpYYTggc6JHkG7o3RqVtd2ZKcM
sgiro8Z3LPM4H9fQd0pTKDL4cdpc3krxwsizqsqRhTK+nifbBqPCNctHvkcveHNvdPobRXIP+YZE
PM9///PvbfIvu//GP5TtjfqId710KVx1ws4Yl7bQbBaof6OO7gdO8Z06A1NOk0wpC//5kPqElfIp
bo371p4JuyRaqjSNnGz1hRUPKqkkjrVENEqzn7MUj3SzyBFqu1Szv1o0Il1gN8T6RDQJ7RGIivOT
C//FKpy67uOz+/6J3DDMHl4xv7jhTM/CKM6yWceI6SwNfHuztPftyO3ohsQ8TRUd1y9draW+bvYh
96OlOrWx07rWCu+47oiGixqhCvmZJl7bLi1HZ29NldZCTRvpVKk3lPOUP9S/Mx8d6mA95SOkWuOk
t+gjjQpVt54xh056C/9aQiXG4XLEt28wLd1uawtjuJFVl9B2pz655OzDo04ZyTXYPsbuOpHnTk1m
KNr5G7riYjy2/dqp54hKbg9CW0P27qflf8pQv2WUvzq2uKbulGL1A7fogPlF3+oUTF73HjG6SgHv
PV4HBGZ1Cqe1v+3c4m/TcEKDM5ntRluh3JBVzEkxT0fr2+eT1khuHVvPYKfCMnticv07jKReXMza
fpmj96yTadH5Ay+2SED0MeudLZCebEWbee+B3L8TzqprqM6bs8UmhqlyXJj3V7enbyn7PPupd0vv
LjG9BkY6qzt90vHVRrnLF3dzneASZTSysZ791Jj3dCDSTzXdZB8P0w495XvHi3C077WiQw2Y30o+
Yh1Pt/m5pDNWsV/Sqm92cKRxiG8rl5ThSqDhfE37SpwNTSgkWBn5+Z3yfHFwAuaJuBf+YOzsRvHH
AYcQrSN1W+uuvPsb6+xxPshdWjBPpiOwyG/qlaYLW9kge2G0z+dsOqZdKre+VZzWFZ+9KLJLINNA
9bzrTbdvPPUvgoKjLDGLWUXeTGxJ6mMMt4KHaWvvhnZpj3OlM/Nd7uqacPP1RZVaE1kHqz5y8Irp
eQnixWqOvsmyO2Cff0K+JbLy0nodzb2R5qpRXpZo+pXZwUZSS4CNu6f8RtBXAa9osxJf850q8rGX
+WV1H6UtkXQSnzh1H855gCtZx15SCY0hW17SLj1dp7wDG4ZcPPsTd9qtiKZo0dC5Wlca1NbROz+U
8CyPfSjhBr0P/mqRMZ+nZPyJx0a5pWqdpYZWtHvnodqdgijDpxxHY36mHHjTNcHs74satyZGfiWj
TfRmWvby9bMpVpE0lg/md5FUssosihhk8FllHhWWvU6Xc2s1/8i1/hpF0+TeO6riF79L205/k51n
X0b7afDpyHeITT9I+mtaR+VHgb79F//4NVSfWeCBBHkaDnZDvrIedPCKCcO6T0uZ7tykkbe0tZvE
8/iFx4e3b0Fp2sV7sFUSrK120cuaXafDzRO12+e0lSxdNASkaxxes/VW5hdU5I/uORmIz8lKe/ts
lj+tp0Mr6TnvrhbGpv53uy8XpgR2pRQUZKglunMUSYUp6Nwz6yaHUVM+VkNAVlc0fWlnNh33+aFa
/zaDjnFG+5TcuZTh0/vqC9I/50Q6t1ulhcitrQxwuZP0Qj93Zth/WqC9qdjW6RzMP7bByDMr79n/
9jthylvBe3FBuEeQUHlLXTM3NzhIWYgJUymZnyv2ZZvpfF1l7V72LUWeBKtxAXlSD+35Z1NLl4zX
3yzErn6Fsu++fNdm5DrBOsKJuqIUapZnaaBN4LrK9zGr18rkWDvXwY2qygXJfF7NK0a4vgy+H458
8Y5LgqHZA9ndb8QmAz5pprzWGZoc2VtV0/m+dsOJfku+24zJ7bJej1MtPJNjjxZEXSPXWH3llHnl
9i7bDfWvVopy231adiTEn989fS7neKXU3pTsj0veuw4feW+o3/ni4lHh2A5Z5RxjW5Yuv9Yi3bDE
zHIu5oYiA3PFzJrS+ZIbPBtqtgokS+jxPvvy5xMNmTcsWxVKe+aVvJ1lF4I4vrJUvyjdY5GK2tj1
wfly2UXjIZJllu0p2bThypiJXKF3e0axTwn3aoP38RXuk4wy/UA0zmI65GuRzFlxbIdyGo5xf7ol
yej4oAimZI1viP59+IGlW+yD/CX4Z8pJQ1wlWlqLat9vNQ6dEB9u4E1/Vc5p4SpTY7Ga+1oJ25wx
4Kbb2v2oma4krbFuucz0s6Ta7mtLZ3SLVeRN2aUZWzROH2voMOM3n1YqkDK9vPjIxdY68dSyAcfy
dxk1CUEUR5zqstCzTvZz8TZ0YYYCTaWOVeFWk6SB6xBj0OUkBvqIsqLQMpmeDF9mh7geAV38VH3R
xemGZd+mqgHXhSNDd/hXbe7LNbOdsFDxD+Nt3B4iUfs542rzRlMsXlzJZFnxpMnU8JUXIl07ZQI/
ZlXQWpiPuWBaDr1BKc2xLdcu8qd1r11NbVCweBkt4K97yP/2T/V2uh3PAkzvOM5XqfIwzZpOGNso
73/cNfGMJfX9aOCZs/WKewRo80x6vUW47QkCx+YWcUMhjDvF9btoOS0MODp/fj4+vt1C6B2nNMpZ
b6XfTql5K6pi/kcU7WJY0BYBGk+eHeb/VSfBwEel/7lOgvl9pKLSSTC/T1X/Tp3kn2H+v78e+S9U
E/KhEPrdxJMtCFiUzhADLEqDigUWwhwD689hkdztAxNpXoFF6TfJcCCEgiACi9LXksGhISpCAnx5
E0LYDDQMiNLXogGi3zQBMAEkpHcHR2gIwiO+ACiklwcHaAhp1sH5GUJaeXB8hjAU1+DwDEE4ii9w
eIYQBgKcnSGEn4BgXJQJQzAuJKgwLiziCw4W4gvGhTwMVg8hvMj40WgiBRcZIRpNQOZIngAajTBc
GJAkCP9F9opGI4QXBiQNQtNhQJ9O+Udmsg2yiIAMhQcm4gvGRZkUBuBCWDssjAuZIxZeR8rDWBAv
hPDCwrgoeYYF8UL4LyyIlwISeyyIlwJlZCyIF0KPYeH0oqDGwvFCVAeAi1rEgeOFqCNwvJCkhnFR
iYRgUlRinAgaQ0W6KOKATaUXkU1qTYeMi0pNAvlFRR+ScWHQyBxxgFSh4ukgcJmKGAcmFT0NTCre
F5jU5CzwRUWZgstUdCIwqRhBsom8UniA63di/0NSgbupaChgUpYCD+NCXnuAC3l58WAdicgc8WAd
kejiwToSEV9wvBCSCo4XBSYB4FJA8osAx4vyMAHgQjhRAsCFJBQBxkWZIwHEC4IQX3C8KMEmgHgh
bBkBxAuLjATihVBrRIDrNy8HfBEBLkQsIQJcCC9HBLgQ+YMIcClScBHh/ELebSKcX5R4EWFcyD4K
cCE8JhHgwlDtq/BCIhs0uXMHHyC7oQKAhtCiaAWADdnD0AoAHNWuhVaAw6aI3ADgITsmWgHgw1Bd
BwAxOCoHMERkx0XDsUNGhPd+RarrYNNQRPYnNLz9IwFBw/s/svmh4QKAQxDBBUCRKgZwCUAkIzRc
AxAtC/1PEUAGgKsA9RTgMoBQumi4DmCREeFCgKW6DhBiqR0AiEhyoeFagKQTGi4GOCobICRAVA4A
RERbQYOCACG6DRoUBAgRbtCgIvz52TzYAagJEFJQ0KAoQAQqBwAhss+jQVWAqCoOGtQFCBGO0KAw
QDgqGyBEFC40KA0QjmoZ4dqA6GdouDjgqWyAEI8ggMsDntoBgIinOgYAiIgshoYrxH+wb5VhUa1d
m5KOg4dupJsBhgZJ6S6RlDqAtHSKNA4hIRISemgERHLoVECkGWoIR0BFGiSFj5nvMMN7Xe+P94uf
/NtrX/t61r3v/Txr3XOva1BTMwCiRYhd+woiCIgokoAIiKiMQARC1D4BIki8tgAQQSIqAxBBIuoV
gAgSUQiBCBIB1xaAQxS5tgBiJ15DgNiJqFgUsROvfUZRxE5EsS6KOCzXYjhC4LUF4AhFryGAdw0h
1EQUbrRfIrgWI84K6hXgfUMIeG0nwjuHEGo8C0C0jmv6CtE6rp0VRO/4B/H/x1wB3uivjp7iY3gx
AVwRehnC+/zVObsM4X1eBKn0H8MrCeBqnHIZwhv9FduXITzR1Sm+DOG66KoqwN18eCiGWgsujK7m
OHDz+jJETSzgJQQARMKEFxAAamIBrx8AIAoXvH4AUMMRePkAiCBxCSFwoRxcOC7U6AReOgAiKFwI
ISmEygzHBUBmRgjJK4VxGcJxAZCoEToSgDKTEUISgKQeISQBSCAIIQlAwkToSAAyMUJHIueXlzEc
lyCSXYSQRPnYCCGJcqnhtQKA8qDhpQJwzaNGCEmUhy2CwIWkD14nAEKoEI5LCPUwHBdS4l/GCL5Q
qeC4hJEEIYSkMBImQkcKI/lC6EjknPAyhuMSQjKCEJJCqKfhuISRDAARfCETAxG4UHsCiMCFehqO
Swj1e+5ffmTCb1+58IB/Gt0lX8gL8X8u/qn/VwoKZdD/t8aCXwHgY1DUbSDTf2bQX4m0fzXoJ0zm
vGB9pCEQE80zrOlV/03hEdmZdYsMg5Xputd5LZVkL54aq6rKoXNxnSQ27rZKPEYXx1IL4FFnaClj
w87I/C4RcuLt93Dg1ptKpt9EpPVnPsdrBBo8KlTnXR1CD/BsogrjAWovsgkoLN1MqHi7h2HK8gMr
i/yNuO4ecal/vzHukfiOec/0hB00NmtuUDo2a+ih2GcF84szyMgbxgHxiq+oP6g5+7Wtly6TJXvh
3CQSmboyFDUCQ4dxPnjIWqwAMj6CutqPSXDZfjrqpnAPDT2E6VS1h1L6StUbwTqMbSl+kbxPy6vb
VvzMolu1Hk6o1VAO+XsjFq2oX5L8Lcyrlj8xLWWC4YFYREhYTSumkn0poMdDOf00hJKKvaVuxi9T
XrjKGaeBO6xmDTIxpSum79CFwVIZJXaeYRMw59bvY4VRZ+PDyJ/Nbg6mb6I9ifklueA2GJVfhGa9
/KuIUfSgckPq9ppvblcNE48cLZX0HmNVyYh0E5u4YhNet1W82KFiU3UaZUjTiCGlH0/Yenyg6rME
YgfD4xUy+wHj/v5w8q+E9B6wioFvHRy43vNSgIK9NcPeD6GQqYe1jyrD5Zqd69N43bvfRM/vr/tc
TPsy9lv4C6XddvhVLn58Eur4ZYdSQX8DNIgZyXbBLopPexiD6StzLFgJNbdK+WDWnhtXUvZ03n1u
bKSsox7IRLwlHdVtTSvQrbiNk3DKCLj3+EHm+NcE5vJD9Ox3M5q1QtRvsd5IKiuI44934izu/16U
EXEiIoVQkXdqVf7VedBrpXP+jDtaFUZtqv8t7/jMMJ8T74Hka1KjHPu1UH5zsq4ySdxOxyD7IYYc
MQ3xsYCo/lB5EQO9KLaK19vgsWjnqH65oU49SjFKJ4JyeYsucm3HrqDCL6fuLyQ2hW+ppxIVR78y
+o6WprrvUBG/Hyi1T6vPT8e5a/iA0RpjJ/Bu8vk7zB2G5sGPLw2Y2PEMBvSHPnMz/uW04KS7jPvq
pcnZ9xELS6b7+J9ZfuhtHYAwmL3iyx2gFb4xg7gP0LM0iWyCS3HRuJjNVp7a8jBONhDdcYQEK42o
JmG7cEZzVPn47YxSeF4sf6+NZ562EIf9bbMr15tvmRwZhT5t2Z+S2N+UaK8dkeJkas8Tnz/aWy4B
JkD/Xdf39RgodHIr30uqszeFrtUVwsz3haw3h5rGZsBok6wtxgxb3z/4grzuCE3yudo2s4Mi4/66
2wGvauo8oyOH6QFUS8pF7qeks/1Hte1GHd32VpoNnQ9+hiaf7ZUktL5GLXHeSUsEl9hy7S0WSONw
reQ0HNxVa94DM/bHFZZwtiWntAhMn6awTMQRcykf2S7TMupMSuuSexFKPWao4ht7QEoc3vmebXbv
NfurA2dgHE2xoMCfwAtLxVJuAaPzOhk2J45J9OiNvbF3MMogrWdHcZoTlSfNc/XsVn7NvyqtWBLa
BKTTk9khOmwNvadjj17x869Vy+vzwdasNdyTrAdxvWKXNJRcdYg4YKOvO56vKWzdh1kWOdO5GU1e
aEzW1J5Kef26zarCaglJFlBK80hXVH0YyBY3qnSLylCJvecF734OVcnzCVVQRXWcfuZuKcls0dxC
Bn7U4hL1qi7lplt3iOKPGLBFA+N22KGSc6R/s9MfRBeN7l04ZobpVeyL2tZPvI1pQnT5NuOOVW4f
9VJHkZxof95Txs80+X6a7MfOL8zdWhURMbVeciD/Lck7dIohBxLwR95FlXfoohO+2HjAy7cK5E+F
sLD2a8mwRowKgmxKg74sJxY3T6t6kLyTHDhROQh6PdTiYx6aa55CTel66gSdmIv2XrJfgdE8yl9D
T+18sPjk6INFsGbuyamHjtt6TLTLKGBZz/+pwu77x0SMkNUo04tqkYEsjg8GIm2JtbGt38w8lt8L
6MTT3c5MCXDkkR1vJBte0AsxFN+Mo2AMK/usDOsb2BuNmQVlj1CVHjFk3N9ikzrftf0+t7DCyxtC
YmuR2CNb0ZSgSQWz/bSKU5zxh6JGZMSH5A87t+3R937rfRwvJo624+8V744WZc8O/yQ7vJb1xrwT
K7isZkpQylL+r533urFBRCGfvwi4jznIVAjmruZ+zNbhNou815rRYGOesPa25fvEMQMPCMCxES6h
S2cX6jzRclcKml6g2+M27Gfv8GNAAf1+MMR7SLeq//BVRpXcwqDpEsMrSy+yh8XZ1eN16Use4MHg
zkObzwZ1OyEqxrmw8B/zHCXR+2JtbkfVbqJzRwN38UA9P3J2MO+Af6eolcxtFriTzld2DDi+3F6C
ZXx12yBX/uBau4gdCZ0sh654inobCtGzVdWsjqc+vN1gl5R10h6V3hZ9/nBafxqNvq1LmUKrf+f0
yTyZiqKZZPBUum+g2sLBslvzgdXGl5+9vK+TBkvlVt9/F4yVxn+vd7LbnTMA0l5tMgIN+Blh6jOp
tbluOhNGQ/vWhWjiw9YKAUJJvDYh0g5kKk1PwiXa3gtJNXnNVMS5q1c7fNMoslGPwld/8xQ/7iVv
7LB3aRie+7ZnY2IAcdvKaP1WZWgjq0E5JiER6bJBBoXwp7BvPUqEfpJ3GhVPHIpZMAa2GdGx0SZ+
cir+O9tclOl/Z5sjhSbKNr/SZf+ftrkY041tDo9ubPMb2/zGNr+xzW9s8xvbnOnGNr+xzW9sc7Ub
2/zGNme6sc3h4Y1t/n+xzeHv+j+xza9U4zXbXOKfJYThf89C3kY8+J/Z5hJIaCjbvCdD4zFtE+mT
rRPyj8xGwtlsIDHBtv6UnNkeL7rMdboKuj4yNk/F1DpW8q3zU5HcPQxVCT2jAaN9ORno+Ld7YdAS
bxmWaUPHoKSXlRcSF4OZfQnyWOdNOFoe3ckONAQK4llhMizajVYd3fO/g6XKdWUuVkBCHOEXLbfF
7gtXwaz8gXnCSqNn5yDre+Tx7QNmqfjC7KNnNUEWxxCuJNljjlnBCjL9hD5J/1vNTJG4a7el1WBn
YPF2eTGTrbW1rRzlU66nPm/OsMmmovX9o3UkD4rmRieHxcJO0X5Yun5525O1V2RQOFsWyJFGgvc+
NyoktjpJLzJt+X481dRDkWYorWakknB8qffojtVzz3KQZOHcD5tmiZ+zvejU6pxOZO1vRwlbXcMU
w77QQY2/1hepcrJ2Emzn76hF/By0hro6fO2bPPsJEY43/qYpV828mmLDNwJpZE2wqBzmpMLoTq0L
o59S6jIufiR+342PmmLcPviU8W4+kcuUY9xJe3JsuEn8TK+mYK1ZLjTvt0yVUDWfRJFjXyTEX7gB
nZlZa1PN+dMyZkWnVjtaNRY11am5RW3MSrfvYZAW0OEPETNFiwnOwpdx/C6e9LCefHVHB3q/z40+
Hi12gPiJqU/eIZJuiu2cBo0S1I0FPs1C2EPiXH2J3JxZXj/P5EV/9RhB5ppXAr2/uPBqbn3s9QGR
45DIhdQkNq9Vq9wpesStKHjrA/t7WfrWgr8ezFXnxC+MgDHoSyQNQPQGdMLThBnHS03TnpTNDc0b
EAjAV6WdqHjNdBGbMZ0IJJsiXsTHJmtCRl+v+rq5PpeLl9sEp2Z2ru0O+4q1gR0YFG2vbs3yc41j
PU1unPBPmilA+PxUeGalDof3EmRvV0LEzbYsETv98YUNV0FeecMcNKS5rMDVOCYQm7dpcVMfLelk
ZOUgjQTjse+dd23PTuhOycpNVJuxHmm6PmU2Fu0cES7Ci0773iP8sLku6U2yXPiRn9P46kUoK0en
oWq8cn9/joi1LD1VPknPF6r5WzlkvbkGdm1suZW138Ld7TojWKhJsV6XaKdnfU+nqatbLdOcYeX8
xKH2hzr42DEFq1+t6tEhlgqNS3V6DVqkTDo2ehXXqE635wIuH+Bur+SLse0mSSteY79Bmnuxzo8d
IR+esQb+Gc/q3z2wQPUDTCEghUmdPRff6tI+hZHj+OjlWlkMTYolH3Rvz9xmv4nfk9cFOpY6tPSj
oderXecvEeJ1BVNRTiq/fDpO3z/z9hdpYxsdpZVeixjW7Y/nBKkApzLb0MXV7qgD66q0h04LOkMl
cnOXQaouUNYZD2KageiQUFbaWlAB73HmczX+oGrqAS+DgmzmQnSmLAXZl92OPueBwXgdORqbVcSV
4NK8J5UL5u2MxOeEqzy9XWzdrcLgezOeGdO2bLTPYv2B1vTtmB13efMYXpiVUMIkCXLuT8c89cES
nxZZKKqBEEKbZ7btEmISw8w8vRugU/i4tRFvirgbnZSEOw+pP5XeA0co0cppz7rUYM/UqUZRNFiF
WLydg4pr60bdtsa5IK0co3/bLXdLMOLZ80mMCCK7+sN3w5OT427ruO/CbrXsn1Pz0iSAGwJ9FJkL
QTGP7rw3aY1b/0TZCiRcIneahdzvcHW2m2w1B9iSXBw2lhQAx/pWJl7avYWk/B6iSI7LYSlUP4z1
O7j3E7TEkx/mRNDA5jeFc/Cttw1bEro8xDZPJbmyrOxQIU0H7X4yyUXCcfxu11o95wdxdF/cpjXD
jqJSMW1cMoS+fnTkRHIlFpRSoxPRmbDrVA1hAsTXpgZO5or3Cgloj3LH2srtfqldaxHf4BbApvBV
tsy/Q8dbkKg/CtnKTnX8WlBsoT063fFVRP4NnzofjtEqN0SvOFDsdy7PPkP872cmeZWL7WDq0Od5
0YDlMdsniYJLBCYBgQu8Ym95TooP0C0qTOYIw111VLHYtVSsGfB4McNN6yLwerSeEjouYHp6ECjY
1C6JsmIm+jI5eC299Ej8XQcVXyfZTmeeebiZpnmIsZwqgc9XS7FBLMsyRBXv0fV10JP2Sf7BZfF3
UFY4Z5x/AX6Xnrbim5zeSN9zy02l+5YbZRpmQ0Rtz8bTmjVfPYht2d/rTfTpe/P837Dd/MCmbpTp
ITSaNGkS1FEzcS2WaYWcDnZcqhKmhAr3XohmPi+UsbMblhcp9tjis2D1/kBLs2lWTg+edttEwwMH
bpBIUxvUJ/16BnDunqOnLt02CvAMsFD8yU0wz+zYQzrd5a22vDuwNDtd/ZdWm1ZWsMTocFawjqef
VTcRaWxQzwYzDctzWpIjhucaCxcBzW0qefXrYRvt4YMVzowvsr/6utg84Z4SMZ042SJwFr5QaLFX
mp37obFHAZ44bDrSXKDpONJbiK8c4Wg5qLnjrlx1VNRCFK3RMsSjshDo9LwhYKVjLsVNTktebFuU
k9I/G5LQogUOWHiRFkKz5BEpQc2g8tgr+d9/9lDsyKhwrhctuJFOFF0Zw6+q7lpaLp4J7NVdOP4X
e/cZ1MS6MHAcAQ29CIL0IKB0CKEE0FBFEKRjKNIPXZCEJggEAekQQASVXqQTCCC9Sy8JVbqANCGg
NGkK3Huce86578ydee/cez/mQz48md3Z3dlk5tnff3b3+/nKEZDtsCsTar6QtQRwWJoHaf1MMx2y
RM2QHxc44iSWBSxC/TbPDzb8K4Xuhsp2OSwKvC97h7s2DX/HojXQ/WDg2wygN6o4Q1rkbcyAqcB0
q+3O14HaiXnnekv09hR0i969rlBvQf498pHw/H5+GDH6YbS7upWitE3/Bva611kZ8Xdq/vc64dvi
7qMGh52D5f6AnCm64zm6nSjl25bFADgxs/7J6B11CuEN5FiI2seWRkBkPiZp4DALKPQ9Cyh6kOVY
NxxC0Z8NuOxUBLiWFEAruOm3kuwZQBvVf8JpOEx9p3Bs6DAr5+//Dsy3Okl1EEUVg+8dATW9wV79
eETl9dAYYVcJHs1nvb0ZY25W3Tli4P1w77Hni873AydvjQpz4HdFtH4M85bsluIqQFEcHMccgCW8
WlyjijPRR1clRoRKK9vrWsC4bemCan7fazchrtkf5o0mNCc9S4/J0z10VPsNhry8r5RnUXQOZOMc
UweZ1TKv2O8HR+dRYna4aUT3Fytr0f6ZbG8yLbL54ZIHMP5nL3MmPpn1BulFGCYwiPuZ0MdYPCK2
Ff/7x0I2eEQz2mpQCCCe7EnCQNFwKUapnqi7yY3UdnQoBJO3NUbEPC+eBnZCWVr2stu2AdawOezv
2ov8GmNQgB9ZWm+6dc/SvftVLOSjmmu8DXwK0vbiYXGfgxFaqkqyESEL0jfuGE3PvnSu+PJEwE7g
CSQqBEaKvV+Qmjg+uX0VFIoEKqiwY+WoXIMdB40WoTWdEa39I0hJrG+npln7OW18UXenG7EOlZps
XN2ls9+kEiEd40ynOC5R3Pp3rUszaDqeQw2jrEXn5v1KTKD7ZSJqWPb08KOV7vB5Z8xcrnet6oXb
ZIl89Xwpstw6ulq5hNqPcjhsScY99P4O/Q0iB66bevffUBenvzOKMl6/ZMDukbD7/BaXsqbq9hrW
twJ5ujeAgCuGi5jerkkN52t4NlMmTftlp0518RppsWmNfKMD6xfKdbVe0ZrlChySjDY5eMqxDnQQ
yK1zfhuOZg/mDZ3gNPNJGkt+2p/0LNhgPIgiTcK1/0RnXoGmfFGfTLrz+07dTK7KD7vm0AmbM89a
rbKMxJ919FDKooQbcWxOVcjrC8ueKqoXYZDtL4UZTjSfHmZi1wvvAGd+FvZyIVUXOGHR96qnoGUu
z3q/DjOnXkc2dRjlOdTKvHpWFd/O6ow2HQfTwPJfax3JpI6YGi08DO+5qLAQaXYlVjou34InRKza
kXTH+kUkchZbIArHNUXNqrQT2oxv6/9YOEqd7tJlK+De5AZV3LZ3aOnRmnhvA3vf2zPvVI33Ccx9
+EgPgW91Oe2WBsx6jfA6NJZuo6UuzyQ7A4zhLlbEc6wDucfCVhZkkeUfqWNj17lPdIZoXEh9mVPk
ooWiUj6bCRzW5Bfy3+RDceuOeErd1NU4UGFWmR6/uoREUuif0M21Zdkd7xzzUOnf+DB2NrluBUcT
04C/sIws6BX1UwY3DUU7XtN7KTUUnQDRluCN2o1bnaXS0KaKLAfzlpAJgiOvZmfq9bHn/KRU4lW+
WX6ELi8tIo3acaVRLmPCMKngNPiR9jbwYX+Qh2PVMgPQ1Wyig7WFbOYyqSGUu9qipIBTA9fk59x1
8wzjVzwOPj/73oSrbBoq4XgdfnVmrbnLrOPNOvMTXsSu3a6VeNC4hGHvtzKtIuLIrWhvyihfbMHX
bfwL7cnlaaekVTjVB1XvB04Xasq84NRdsWJaePUVLxm3dr5o1EZU4l1F8eeKWkUrCDhbz2aIPsuP
++8ktY4N+b7cMehbCdHtyfvMqCbIhjTdnZaOcKeaZHLzquoDBQhuuUwqx1aoZq0BrG42VXPXdO6l
QBpgnltH710Pm8z9uQFjKsI+/oKB63fbdRLPGOt/0EW2f2xua+UCTalU3NwzPsrovtfg1YqLSGee
Q+oUXub2SqsdC1oPE9Q5e2DkyZcT5FEvNwd4C702fFDbB5ZWn5G8YkIeocDqU7vUaDlX+WyPUsHX
XWcmDMm96ch3KUQ+sF31hV51Z2pchovcmbFvThDL4juBmVIsiTOnJYmI61kfXqh8Jiapl8TaUqfx
II+vZZYanuclp4iyx+hFMAKt73o7XtQlkh29Ko1/wTy92cu+m9Ium3sd8Fldbqb8CMJfGe+thE8t
fh5thTtdKRgm1ifmA0FGRbSpT8Offf5M4QFLVJmlapr34IWKk7R6O96z5Rm8FhObmjfKvlcpdFmX
ItxcHm81mQUNMn0l0HIBk4x3pX9gtn/D2/zkJR3dC2fqvPxerXt7dYmlseop1/WfGxxahzNmUrJn
I0H+7oxQ2lzzfO7HvZplLfGmg+l9FPN7CKIRqjcPmgdPxzFuNbBSg2yXSVjpvo1qSMo5vRVR49PN
4n9RhX+Rxn9QhUF/Xn//WYVBfwjk/7AK/9oMoQoTqjChChOqMKEKixGqMKEKE6owoQprEKrwrzGh
ChOqMKEKE6rwf1WFf53e/78K/zGD+6cY/Otc/7qH6vfHQP/1tRTw34zB//ix/N8YvAIbQMxKM87j
hYY5ptT4PxHNG+07JmKro8NKutNpRAykzSLHdas51mVmNnQOb/nt0pEbJL2Unp7IoL8UXFeH8sA1
K+q7dEhJ7FQkUxg+Zk7Sve9hWMqkKcO4s+e2ywR+ngFj8Y+FTUiDVZejYzqEm/AS5E/oCpIcWhkX
xCD00uuOfWQv65W69oExlUqiKITPqtEL43zFiCGrLptxNL2MRQx3/V3G87M2XWIJahnV0cISy7ly
K93jzMbLaia7s8HwVmJUhYaxzdMpBijRxBu1cEuO3/jF70LslmUskFIt/C1pNC2iFLFthd+DS0LQ
1ozYCX16Vlr786ws9P5lH7llmFigYCA0OwGo3MteE3QlMJp1DpDsa5v5imOzOF9MptAt7eKuoeaV
968hhdfUOiTi04ulvOYdR7+oZqi0WbPVhs6Ox1J5Rlqe6FW/FbBxOjXPGeaVeIvIWQkZ1pqHIiMk
/CC/dTLFeIqSVEfh/VASsWJmQSmdJakiVhPENvOlGyNolyd4TYWSw0WogmntfM0WXnpweGlj6bVq
PAtkrh8kLcz185iptbgBSmJ3OfCbDLZT2r73uhm0kAv8oahFcOnpi4CYs0IchJdVtbEI/TO6pnyg
peHAtqLw8Ca6kg+VLNhEyxAc5aJQPixXBczz2sjfsR/7NKF0bPQ0xHtJtxa19FHn4Rv3vkDfMSP+
tEs2ZQMPnywmGnQgclW6KcEhxhmAqlMm8yCKMvlJAcfdVZaGRjSr57KDhfmL5vtMltlXy4iWF6NF
/ZvLG2aFw8X8k9RjBkmN7oMS8b5BXEtCSk2c8fkMec/hgvYDiGoKBdfZBfzaJjAEwCJZmcFhgjvF
IdPPKB/fhThcorQOh75fNpTQyI7AqCtJg95OnRlf0XDR0EYZ4Lrg7thoYmKnWOUNsUXYumowGUnT
kwTSNcOr0iGTwlZeGItOHio6an6heiGwm3l/xXm1+hnUuqjOhARGzRI4OOn08ThxdfG7+aRbQkh+
99EbOHC9czGV5r0P9ebSujDQHhuZsJYnqTrycqvXcU7mmyFZaFTvB8vbVMx8NwsSwHFZ9x6NM5CR
cbXITOSbfqftck8McbnhFXPCd2+GCCAOoYgoaUUDkX46TDfymtrnm5dbzJ++Lxcd6ToDtZNP0vOS
dnVRtbP8PO9zChszfas6xEMrKhviZ/PbzC3/KNxrlialB6EqzbuvQGbOt6lvH7An942vjx12Nn6j
zVTKdbiaKX7edqstWjH1rHXFH5kxAfIraasdaojz6i35WjyaucB+gFozy0G4MQBwy+NwsJEvp6NO
QFRKgbb+SN+qvOFRvDn9MyBFVBdsWC7D1i9Dg5Qv9odcPzvREtslWdF8X/7I4LdyT1C5NNZajgLW
4tujNF9OyLBXP0IkWCHR9EUGWASeIoLfR2sleYjdduimAr90cvrysdgtpfXbS6Uy218bREdqH1h+
m6H2FF1vOVirm55zGFzcF2bsriqaDQJR2xXMMcFQc8lEoYHon5pZ1rYMDMeUd5L9ehgPFzSildTH
4k5eNlS+TFvdO0eqmxTYsEOicYiP9Hbk9ivhAtGrw0O9OL3rTViEZ2K6LhNE8dSP/DKDrhqJCYi3
jZcBnUfMs+xwA6s8QNkZjwcIaouwoiPHDpPWoxw3xmcCGe3gwwIbGOOtbMVkHm4b8/2Vnopld+JH
nO1sxHKssq5Na7MiNDS9J8vbyZwzIjpnx3YThhxzahYyH5o3tkiYoej2V7dM930frt6nmsTGS/Jc
MelcxF9pf3evI+BdqPGpC7HzZBxIVHrCmyt5LlWRxd0sezC/oia31zgKv1ZTdvaKhFdFhlQMnZE1
n9+f1xhQZ5skbz8hHVC/2dOCUARlpQu+ORyPbEe1+Y7iRGLd7+6Hu+kMD4wyLC6kPniRYZ5i/vor
eEnSRLtymxuMyB39UQy9PvhZVhH1Zhemhav9dmscrEmjm2C02bU8E/Ypic0HbvsUlQGTVxCcJ5cd
xtY4+x0wn2IOTeqKh7nfS44Q+/WMe6josHfeqxQupkbEXpHktC23npu/IgDRDKcKo7K8kbKHubUr
tINB3pTfG25T/bBNTgSWepSaTxQmeX4v6BIR6OEdm38lutLA/0x0/5wD/SW6f0wZ/peiKwMkiO7v
I4LoEkSXILoE0SWILkF0gQTRJYguQXQ1CKJLEF0gQXR/HxJE978R3d+P9d8Q3T9eRPRPoiv7jzXB
MuB/Et1fC/57oiv75x79JbqDKWZP2BrpgxbOhKbCiRu3R8KONE9Xpmj8ok6B1OOcWXAuRg2Ml5Vm
mbDMrYuWD3iEj4YG+WgOGZ2YVNqSe9g+PKIuieOVejtXGUhlv4ByzjqG+q2YmP3hy3ZUphhUMjQb
70VZlbp6WmSU/hhac13tvDZgYIlZFZS/rbCGbMjiGAvLYdkgk6EYKm8GaSWas26de8Bb1fKuWXVW
A0eoZwKUDWXBxWBW6+N1KOPXtvyc4mXI8WYoTvP4deMF1FKyMP0CoVT4so2rvNOzoHByl8FiaJ3x
uUymVWuSOuNFyqe3QQ/0rM+0x95lahsf9CH1HsvF5emlU2ifpCPW6f3Jt+caGvxRnxZ+Srb+rPIZ
Llv1T0kfJe32lipR1Gp9o/CpKfNiHiv2tE+uWwtdoO+OOcjO+vhuUYH2HHWDRwpPilpiV8MsSIWm
1T2moE/Zr3/89W3J/GGFpTDtcgCcrP4Ie6KqHqN+Wx82+S1+MS99Fys5dQFyL1TneXRI+YzJyuA3
NUyEWpHHD/Rd8IH3rtDpHWHE5GJjMs8HOj534vg9DJBjreNJ97Zd9UbqSVerFRubZzt3wVUNJbmu
EQN25Rbr46dKZF9J0+POPK/bXnqeHrd03IDJ4sikWd7KRIbXVIiVWdVOX0iX1sMSZ9pjDKotLf0b
jjVN7KzMKmj0Neonn4IBPXLsNC9+XC22rSCSSu8bKGUAktjG13ZZB7TOIp0ig4vvisICxsm4OVYD
pj5DuiOVRRI7IF/TJPCLT9VtGSPLBjeOPefCAukF5T0k3FXw3nlSb0GPYjkS3B/hMfsODxs76ufL
PqJyGRxss6t4mHtAD6luE33vg3zNoH9WV2B7Q1lcFu9p7f839u0yNq5tTROwmRliZmZmiJmZmZmZ
mdmOGWJ2zBwzxOwyMyRmppiZPTm599xzZtQ909NqtdSSf2yp1tpVu76tovW9T21uL+HJ5HpDLvTO
fFdobgXXNmweak1xQxaZ5OB9I4DO8dqpu3yN8XFcNXzJfmVjj7glaGEcaVy5A3pBHwJ0g1YDy4+L
wflAi5yTkwGKXQPloqeYMEOpvE23h2FOMoUsQ6E+TvKEH9xTsxeHIQjP3Ay5wtvsxZcWClhXqNbQ
L1Mdqycf6djpdCbG87OBpflPbqkCxH0PrrxGINeYvIjrXutzvljvCJPoE+2iVG6wB4EJV9oEbU6k
k2MqFaNMtpxA++C2AsH0r4fKZr29SMgFlSWgRScmcTEN6n1lonDwPCp02NfgXsqhr+/5xEB+JFIc
ZP4aBJuDN4wGqeaoO4k2p1vJtWct95hpnJTsQMVNBUuFDGfu7kHO6bQKoU1F0b2sLLnJKHvJSwU4
7EsJ8HsQUbI4UuZnTRvdNWsMK9ZkXe7buvAgLuDINwniaDiNJT9FMHY1zyPKWo7RYcjJu8AYB2lj
n13p+yrQE9ztl7uPQrbf1s9tV5H+uQPbzk+3Ojd3dhWJAGql05mU9aMCbpHzS+75T3iRGJz4ZEp4
Nnof+/09CePsYfhuyS3F8ohsbrYzbah2J16+vjjkZSvJekN11mR4+5dPNg6BcKbDk0EyjJ/yzSlp
biKqC9Gwz9NzYmfNk8EjhK2dH7ye4QIB0QaaFJNCj9V2/tj8fJT3MdssgHEsvo088MEZemq4BsRD
UwHvCPDSLu2ulRp3BbYlQbgJumOxXk4hPBsre+WltLiRNTU+FE2BLd2+KatmazIHC0RIuSWAOCuq
T67gWXkoj1w/kMeMNqVmMO5yGuTUtedVg6fOMcAxSAsNiP8+OEPGvgYfAr7wVtOwsTsv8Nks2tfC
Tu+WBxC5r14xgHGWe9qiWJqbohp/os8ltjlg6czlmP040xyWe5JF9w0o+a7WItXRSn68OR1vjqsI
HFTctrxRztqkudmNCDiH2Lw0DHjSXz3mexPqN97LO10PjVYhTLQKjCeQQ9fw+M/nLQcp4fY5dZe1
o4idGjW8No+AkeAwp3KeAwaKtuCFgTucTrt+UU13D0CYd516HG8Z1RPrwYRELsST0VahBE+Z+ng/
VaqpY5SaKC6o0ocSvrQBS3VTpoD6mhcY5k0DR08IZl/HLq6srMX1btlxLuGJKN7oLHLHpJzR8bXM
L2n7xVAraN3jC2peyJ9jmPV6RB5xE1iO6T16gZ0eTn15pxnFkLzBz12+ZioWbVqW4LmDT5l0r4aV
xUUzOdEpyxNj4OQDhuarEV9Oh9g+pL5xDKGPfCemJOYYshqC34JxKtyEcaIZAW4V1BK2E/1B0lz+
E1p59mYodsR0R80F1Ml7ldipYoQfnputGy6+91hEj2FECQ22Hq0okRYin1A6i3ZoBh+m3vlgRIJi
0lKCD75aL34zCpyFr7P2At3J9USPq/lMPNlI/AAGiCXITLeMhfKxjQk//GxxOdRaUh8f8eCDngKa
ngJjMPtd9InXmPo81qDknmFTVvue0/ayeKkpUffDjwQ4UjvzZteflVpKYQwds6zFb2z3M1ebsOMs
OD1pX4cacb8d495bsYQxkI2lDtyFMWBgnx6+YfmwDQI2R5/Kc7sXR8vPdzXJ5DZx4BY3tNXizm9m
qH1GR4C/sa12Z0fZBdgrVHc3V+JsZrmMnlf9euUE1pEeddP5j9yDWRnlY55WMzlFK4jjgKmiZ3NG
txoq6u/hiJ011j+vn+nlnrqvHu8BrPMuStddx3gWzkAShhev27lv2p/H/BYXu5qLjbqs62wyYCGh
0mGFEKbwmBZRtDOZmc1HFt9CiPjiHqAA25RL7KnJ7ZpdCb6ptciqKabnkuVSfRSdFB2PDVib8ljD
XUHljl5makLzGUyqkyzaBUcWsTUl1CKqc1paDBVK89HWKvBh1ip0NOLlXpYp5aa7AvOZdgESohwK
bJTqpVoLsSqybablC8m+2LXZ22XU4oZuBd10XFFGgqlBKokDhGgmlkngmkvCgm4IAvkphOJaS99C
7IuPj3EqO7jX9Jb5Z1m33VKFlikOHYOM5FiCuCuo0RFcihE87e2084SvWIzQCn8ysRDhOjSwFN2B
DfIaF1fpL+TRPKVx8Egbzduo83FbxsvpCJovzJXHUalaWHUBF8xWzzGUqezMulvIZoRJY/jfLag4
o0j6z9ks7CGqUwKh20nBIGNVmSdiWYRmYwXhKWmXLkMYAePa5XS2Uum2bpVVAlzg67F1g1uEFi1+
bVFOedYJCwdaircuVUdetXMufLqFThnV6KsCi3rNEovl9fKgwa90UykahLtCp7yQBKU8YkbJECVH
J0osp+7BzPnlSayzcp6U1uJ1i03oAJbd5PB6JzT1ZGNi6hFB3Ocm5GEV0SYKS+4ceyrTMps/ruZp
mc2wk1IqziIz8ggO+RlMDGGOxy2GwPLj06m3iPSxxoYX/xuoCUwLWjXpfQHKsSDL2KaGaAUn45yv
pf6Bv6+7L5e9OYqBezBlk349MLj6z860wcceuMrIzsbfF/K0v5i1+olFv2C/eF+0aOav3l5Iw2qH
hPl8FbX/9QFxwuMSAruHQp6aChbKQLUKhnkqeMle9gb6frQhynQTSEbQmx32YTnlauNhd5vh5y4w
npvFQ+33tZrpI9OuH2uFfX3YgepIpWad35f5AHcgdZ5ffzh7/GTE8M0DcNWSHrOyHj68NVm6mkdR
nVJrCVicTLsCuGyjv9i0MizTB8PsyPRDEJc0LZdIlV0160Oxidyc13qKhQ8AAGwxqfEMFa5HDFD0
7rSGgnaExY49De3rcPbKOMhjX+kJ2yMth3iszKN6sCxf3bjEo0GJ9yAj/Z9AH59rNfnzdk936xrF
bUL5lxruFUDTa4fbozvq7syI/OlUdL7amMNxR6dL3WWNm9NkTWb19Z3uBjS1g/ZvI5aFRvLkCi5u
07sXikny1o9fOCu/hl+XHyriQBT4D4iLSyF/d4Sq8tJwvVO4mRH+otfSwmlDQgZMVhvqv85hDCkE
pWXBAOYfb77mzYK/Uj/8M5tuQMnOKiBKGlx6UpQkfuurwFGQ5Mpyw+jBUpHDXJ+ZJ8OX/aJc+GMl
M+pvqkZZHLUwrUGVIIAdptOpk0/Zge6l/mKwdcCXE6GH4fnqQglRbascHxazh73Q81lTuDi0YLBH
Er48X/C9oigC5T7cUaBHiA1uPS2asmJJyQaQzxl80hW8wt8C3vTAuI3gwFHdUIQpB1c1aaZMz6G0
sFOesoWKRmRWNA24vkYm/wapOMOpzaqtP8S+c4mFPIQfEjRm4UjvFCkmbUaPM5490cd1xgG0y2Z1
uuJE4YGHjNoi6NKCLMlmriqNH18kxSIXW4jyaEcKb7XaTvKwo1NHw84mEbuxe9JpKH3dX4QYXlWS
u8dtM6QDNMua0/M1cmzoruy4NyVALS2eVcKjSWFb53SZkfSyMULfSEAyjeeV+HRqdYV4awHRw/zC
X/6ZmThAwHsQzINbMibjpRAmC6ksRo+qR5UqakmG+SQBFI4MipkkydbCrqUxDJOuFBfJz6WRuoAr
xlXBntebScRhD3xImbfhcuZaG/flgzc9aWbH6qWroxBwHABzzVn5mWokUV3JjAbWH2m4e8ke6TYc
/oFIC8nWqUseh1b36Qyl6SrgDV4lE0npya/d5/pQ4HG+eEW9FkRyGrAJzR1dSOwFUQ0DaE2jrwok
FXj+8fgj1bzr0bDrMlQd/3mkY9deWpIUFI7/AoIEuTiTaoflxYJfeTgA5BaOQXahrTiilNo3umEs
K15Q05PVvUgQGGrZrAMIc7zpjnSpun7u8bP5LHjJfFKkCaGh6KmiuhOp4SlO0AEZxhqIAqmsi8TI
yEY8Z2KQ2zYeghTGLJ2FT6Plp48O5ifOpalC+fokcCgjssod2C7RPFsF4a2wPWICeB7tptJBhreY
kA2FZii3EIOPN+qmiKKNNWAK5edtv5qIsQEMuRL50S9i29ENXhxir2+Bg4e+TBz716nYoVAK+CS3
p8c0owmlnWaqXVDEQKEF5v2wFtU7OaSsSZW5R8yrjvIBSdztcG84mXsaK5X6/mjHHC7aikzEndg5
Oqzbe2OTCBNbVb09oJtyxahV47HUlWfoMjN8NZ8/J4bt1IU+9YAbHeoocR6tFnkbv6AbAHmVXFT/
G278uy3/T7jxXx36v9yY+c+M8r/QjX8/zX+/G79L8bsUv0vxuxS/S/G7FL9L8bsU/x6/S/G7FEu+
S/G7FL9L8f90Kf49/e9K8Z8/3n8D4t+H/ePWr++WvwMxG+F/EIj/Wdf/DsRFaZNOK+wo4WdXaJyJ
kmEgAufrayjijlwpNp50qbpU3ojXEcZMm3AUpGTeuR6j9p8gpgmpUDKBK+ulicHcQF+M/Ve796gn
uQxJ1+0xKdBeexhyikmRWSWUsBOfa1u9pkVNFuFnk13ax+dHccT4XXGkLrOfLzy3kT++OYNOGLl8
gER7gZcnlunBk2T+MKXh+QXYnGn6o/GhuzSoVAZmRy+qbNHPOz09nzIJ9aZXdhjis/yllP43+9cK
HbkNJxcdOw8USWwFDQS/UCE6jvvi4LPNT4jLr3xDoJcFFj/Lk4F19rO6OGJUTFi8IkAVSLeAw4c0
urksR8d5nFaek2vUYj1wTeLVs6nmtkDemDJgkIfREzkRZlR+gj6ND76E5aMEh+7sz8SDnp6MBOeC
1d1NQyLz3TQvYJxj9Jr6BIvxQs3GJNHBpg8JTOYqQrFDB8bJD5QkOhDcbioSmCnFs3r3JvXIEoMm
LePho2AHTIZQBOZxy8nEmkrJaH6JMcF3MA1moE0WWKfNZNWhGJnhmBSASoivJ4zeXyuJ2fmEIMhX
5rqVDomVDc1PFuETQhm20061THRSXpjMrlLBoISLB4MfcQPgsEIODqDKLqFYLEPML5+zHwIUP0Sj
FaU9fW8eD9TZ56gxEOfZILod+WZRUUBR4nYvRwsvgtZDvB2O0CiNT5VG5rM1xnPPTNZRTtNOMFTN
dTtQTWE/out5VLEHRbXQU4B3mLl3YA9uUDJjGQ0rsW2hJXKWxaQDJiMvu6hK8DPR53yEwVcATET+
432R5bDtF3YcoVdMjtFrs2WnxcVX9kD458lwsGHeepqjzGt3MpUQbLNR7ZV1QgXHDjLGdR819rzl
fG618KfgMdMYgaq2iIDYEUROj5jEb0TnEN/X70zFb2vPXhFY2OX22veUJ0yCHcvYQRGimqrwRwzu
n7VNOek7ZOKfeXzSyxVog5JFkOfy0uFCodhzR2D6wXGo4zKjQJgmOp4QolCnshiZ36CnKM0dISKQ
UusJU02Bq24VUmPEqJUb0WO+r0io1YsqiStyk98ok/llJK/ZD/hq43tfKnv760h05zOTi8ELaQyr
gl6HbdaCRX0KheI1EuQuE8if4S8L8rvrgIt3jvsqGJrVXkAXt3PSHgpGhEb1FYw41JA7ibBpCmjV
kJEXntkwH/iUNBsW+DH0IkkqBHonvVY6wiRZCPmar6EdET8Z1oPh0xdQK7nKo9MPRxyxFDHpUIm0
myQyZ3xCPshHUWxDpUoEQrE5GxKyrQ5grvwu+1BVNpwwmw2Okk11+g7zlXrrqq6u3Cn1fmejTwzK
xIZbOKRTmK0SAWuM2OoxU2MwJLDoGpzoMz9PVYa28xFwnFeRmsTM4ZaB8eC6P+DJjpOmgbOx577h
smFFkoAkRF1nzClQa3IoFRbrlH4abVMOVmOfm2KMmEzWpUvvrhiA/0wtYFHjVxq1mUeCOHOJqN6V
OuD4BAB18TM4VGgwlTebIQSCsGWVo1/K44CbRadg/dp72MFLXbHFVKHkKk69rOsJK1RZyxxSU4fd
594NA+o4YJU4DlIB+2BoBm0Hi0ROUrv0VQNFkvLOwgi6BFcDxZI46xuJ9NJIENmnfg81niTa6XRa
UMU1hpPF5Rrbm7vOY0FE2eZjAXJoJCwK6Ckcse2IGPavgoNi4INm668n7Yuii+idXbKbQWzSwCm7
5MBImZJA3hYulHFTYyHtcLGqxJ/PRKlE0pCJcobjnw/kz3+d9X0k848H3QdBGhw/ERiO8Sv1AJcO
Nxj0h9Ea2+m1xLTQXI/co3LNG9wkCGxCDPgpnLBtGKRMTWATor7+yTnbD+ODaM17ZjHLgTgx3SlZ
kjVfV4CGMEg43LU3zHrJo3f8W54sbO7BrQoScGoND4/2SusUlem/d/ewOgMgqmxqN69XfB15ex35
D26Kef3IGCoCM01rmPqrFB0jcToNoapL8zLQqfeF1TvNaBsMw+BLyt6O+J9m3PfQc0EKHifbrjB3
psBinTiRQgJbUViHLQQTQgnNoaRQQJqwgpfnrqBgWNraBIgFOU1HSFtMxvzjwBSZVkDHwapikWAb
6gkpx3qd3QGaAykFdYINm21X3tOnQxVN9OoA9iSgiMRfG8qgkdiwQahHXga8FAarQgZqHLFIWyra
nau8XZSvNu6oKSxzZACQLHElsBYgGMiQ0yxARu1QB7yiMCsFzjzOroxQUmTDBpFSkq36kpcsgenJ
/mP/8EZas9h4YqbTgRgRrizqvl1RFRytYEAdjIOoKq5uG7cSPzWX4M1jdXnFbBmpfXkfoP5E3QLr
esqi9SBwjZEVQP9lvHKKmyGklTIe0IauEnbOpmJ8f6srCbn1PcWsXvdUCgMsnY2wBVPMYHQ32BaU
mRlVrEK60ExMlus6V8Gkb3Wy6s2CJusVtZgZPEQ6qONOb6VRdVG9/vSb5Wl886VIX/AcjY/C8s+2
et3VUJl6CxcdE0F7zHxj9RkztQMNyqsTSN4kXOwvighPr0WgzsfyLFh0j0my5Z8P5VXwraErM4tI
DNYXUizq2/SseueSpdW3bFrIuN3IGuqJYqZHOUbLsKDRHz0GaawT06IYNlP8aEU1C0ynhAt3CyC9
+qZ02lEyNfNNSYbraQ5B113dqd1+XuUIgo7PlgYKW/da6GjPFmWDy++reoAUwGlhY1WTTgZHlLi4
9olEOIzkyzpytplN2Eppawr0K9MzpMnP43PvRXGPxe63NItqq9zoOuvk7MhskrDIbRZyxPTX4Vmy
4JjRUzHqohHkbn74nL4lJlfccvIUF9dddzZ23eYT0o7U2qols89NSC69SS5WsJ/90wN3dBzfAc1R
0gseGgkyqAZwdOJlYsUVdgecolVYi3nUzMDK4DNZ52lJg3NacHCZ7TLd0aG/tHX/VnwE1HXUUhFd
rjtd0tif/4Ehpk/c6KguVRi1Ddf6hpVm9MKUi+BktPHOkoUmbpLGarxODSlci+kTfKcp2wKMxUKa
cVU6hAvXt8qNQt9W9omM8w/gPeRUk2hgno/4p17TeUeqOcJ0pA9+mtgH11hhGIeMZGFc8lmDI2ht
DtjjMiWTlM3dEBSLD+M0TlYVug8MxAUAaYAgXOpcw3EDVEhGubtZuO3Z4zfbNsBankEYi7n8k2eH
fPFtq30WaKulnLuqoB/v7XxZWUXcNfwDh032s0ZjSfGJq9ArSTfQ/FDzxb+FHOyE/2/k+LMh+Dty
/GsB/Rdy/NlaCtrZ2f+a0Cb8M1v6wx3+K+WD4+81C/7u7FSVJAkpbQ1/rTPtuc1tnQQsbY3t6O1M
XagYlP+x83c7+I/z+13fr5Gyq5HL7wkZSzvr36dn/Aeg/JHRs/5qZf9oNFl/NZO/S/xncf8YCdk7
mfxazv59SoKQQf7/qJKT8L/NZ96v5Pvn7nefefeZd59595l3n/k9fveZd5+RfPeZP8bvPvPuM+8+
8+4z/+N95o+D/Ps+8896/+Yzv0v+7TN/vDX+mmYi/A/6DMtfn9e/fKZSfdRtuwV59SdNgugEMAuK
LBCYAHcWJx/q5DAWBYVd9gTxRFAxJZZl1FxCcvYEP0FW19CAMCudpp35zAtSj/qm2nxV+eiPAadh
aJLRmxjHxA0GBN7RCLkkDfNIwtGT4y1hBskf7cvQh7/ucyMuxv5CSzQ688o7ThmZ+pbekw4zqPIZ
zNsupViTFn2aKxp1t4qcyTwK1y+lsV1ii1SyoVHKvqKNLrqnYbzHBVuGotCyWcr1AwVQTLBEp6U9
RaPbSiJPBMcFMzlBVDV7SuN9n9PtVQyysFkhOHqf97AxAoPGGNdh+Q99SZanl0sT9WHVz10rriix
9DbnaYt6ssqW7lNSA5puEeDneyR6RJUpXYrkQ3eqRUZyo1Y4hxrTT1DAha9aGF9ahDifo1+/PW/H
AIhHuTRr079wBd37RoB6xwnXttOwo28iGyh82JQTk2wn1+FhWXo0nW4LlTP6PqcDsHRyYKnd4Hya
BLtkiKRdWOlimSFxOElZoRDppaKnO0VlN3U8fc5c0e1w+7QLee43UD8XplXGKjdPOrci2Iw8jfAW
YuM7z5dZX2+IDhjjcVL44vn5M/l6Z+Pz+A9wj56IF9gaVfwSxuQix5xENOQEKk0HAKKDve3hFS7E
BKLIJU21o0RkSJKQZluXokov+vzN+Il0WjcWQjUpe8hEqDPSlwnjlFikjIiv6khyXhEGEpRROf5f
ln6kw4jLeYnXLLuJ2i1VM42HrWSKK7sO6LogpCWWFpjr+EQdyQACAHVKIlt4qZ9D78ScUUlGV6JI
8LiO803NhkNMjza0iLMzEBGzDyFnVXbaVtXenNQMBcxnrjhTjLH1Tr3D/FFOJVxnLo+jLPUPP6ru
7H2kUYZDVJUtADfW2lJt6/9BVufvsy+gPsEHTU73/YciPhTRej7V6vQOvRR0k9vpkn812suTMZ0c
5r7N+dS4BzOFbjsBdX25l5NysugiO59BGZqy0NRHtDcw6niosgQnGEs4cmnEhIn8ROCUZkcw6Tgf
Y3y1AiThy7LSs2WIMsEElFRpl4Ws27W5lNjZFtihT0m04MFQ9FxFMQCl3GPinKQWOhm+hrQs2zue
r3RZLWVhAqZxLabpkDDZH0DF8zSg9CbFYT5S6EBFcgWLX6XLskyw6DcA4PiMOvaj6VAGKF5GUGkd
N5yrcp4OLGe58Q96jIgHYXIRzirqbZqX3Xa1jnaBcaX1xNNM7XR2KAnYRO8q0q7DCYd7HNYr4iB8
9pwjjy0DH79gZjEvNDDwfHW27dQVz8h2pgQLudvvjGQ9KUePRKPD1YhRF8MzWqkrIJlSYGRfdWaW
+bJ+FWd3YkZVfNlrx/e9ab6NRrchID2vyCbLla1zSx77DSRMVnOu0dYxij9jM1Bn3aDb/HohOF1k
Qg37IEM2/LlI/5kA+EljXhWLWDQEFv9Ho6/9qSJItyp/AzujaUSFbzmlL7AFWtcYOUv/WcIjHpI2
Z+HhhxHRWYHI1vHgWQJ6iO/SCR/S2nLS2Sypm2PzfEPeRO92WRG+s46ifYzqWxTunoNi5IvqVg3R
k9lkiui1/ChCRYctMGkbtMBpvSopfoxXW8qB49+O6YObnuL8rIN7q2sabPagri56htcwhtnWWzW6
2VxzP2z8RVFlQv6C/yOF7wSdpt/OYfwJ/gyTsAcGpb4W8uz9VTaPB/6Y402dVVjTEzOisRGym2e2
TzhwLPVCjIw/wJBOya4LZNBwPG9ETxm5xo2BCMxk2nuuH7YKFqk1ncTl4zFPP5cwNur5XZxfmxbK
Hme6Nzyv+unxIvJXxdrggFlx97JzxDlvnPL6tZryeV2XIdWEBrslRi7Jt3azlo3wEd7SHWNX5Jxg
kR2AFXc/jScRgV4ENce2wkqfwnJTg1Vu5mhawJSFU/Vkr1+7uXNsBAT48/zp1ZiE35gE7NTW8pmE
4KmiG7tibuTJmF2rPYSKqZw87I6slF+VxL0j4v3ViwLmgZx6Ao4BVUXb2qKouNvpjPBPe9UiC7V7
FajS1UbdA5OmXjoHf7br5sAO+Bd/qhPUOQKQ8to0ezqyqKwlodvs68QWiHWsBtpd+0zglE6qR64f
sX7jw8qGwnjFWGY7PMKvcYeo/G3XnN78RqUNCV+0NGR0G5nsjm8OIuxQfL+ayDenRXrF5aoaRPkx
d2IJOYthkpK9CP/80J69HVSEgwO/QjmNzPOWcEKkDpVSNG5wWvEKYi36tgPZQYXYiz0xDB11HCAU
RqmCQQDTMm6x7V+BL2Twoy2pZDBujYAIIU9OKUqG7x7nZQJO0Y5HOTb6bq17fwSPezseM6epLHQh
lh20fohqmVzKlQm9PwthgidKQ8zgUCS6YLC6bhUoY616sRhM2802tlD0B6Jhfe4Eo4nQy0xl5zRr
tRpNWtRYK4zFZr+Z03xqsD1eAlqoNqvcsW1FSuAS8ebm6TTnproWBhlfujPFeqI/ralRCAMLDU71
kCB26ISienD0TifNQNOLTA4cs7118Apk58ZygjQUvidrushr2Hysnym6rW7SpNlzA+rlAEAXEyEA
DaZHHEKRJVZ1mPF4X7e5keqGGd5EH93ugax3kV4X7sRI1YeoUTMYIqlbq+qA4Lgc+iHh2zPfjvAJ
x8sESu1VSK9VHB4W2XJT2VTdI0ocMa/r29k9TpJsvAMYD/Fy1YnckpvSevaGGSiR4IKt+FHBjw0f
/e/6EQ9u64F6I65QyeS6J9baVWOo0goV1/LXyffgXlGSDZ/LPvdC7njvovWiRhPyTgyX9RVN8+bC
2qGrWHxEfSDt8JnR44dmyL2M9EHR4z8keWAtPo1hNLrfGv964eyAkvAGwwiUFUXW/29IxO912H9C
Ilj+7Br/kgiWP1e1/4XowPLn/2Le43zC9zif8D3Of4/zCd/j/Pc4/z3Of4/z3+P89zj/Pc4nfI/z
3+P89zif4f8rzv99zP9LnP/Pk/1bnM/2zwf8/sr/a5qd8D8a57P9q5C/4vx+9XGnHVakb09UmaCq
zCmKlQTSt2tCbvl5UCED4JCpwYuFGZhmxwbe5MMsJyTnIk8fGkjjT8ZMKEhDCpTYUk1ab24WV/Vp
eixTHQ0S6EAGiXo/+pyTAtORlCdJCDQhyE0uY0YtdMbl0QXN1vgb1doEQ9X3vq6AgfUe3wHFlq2l
FyjaT8YWyVhUCpTEiI1ox1Kaw7h1jSxli7JGEdtWJTabqWJ4qi/MTzQcy4oHW3IkcucjgwyGJ6w1
NJNU4XHsIGyBj1N+3h8vZ13YyqK9ZzFQEGLUUEDrjOfaPQAv/CxsHKSfB/NtDEEutrXg8EWZwob1
Bfgj/3VZch2fII1okgkAfEsWskNIg6YLhXyjERp9t4jxp4Ky6Fq4BOaFtSylIzjnI8Zrqi+OA3Vi
cl+MIrky6YXrJCiO58GJ3r40KK8IZkj4PTmRAkOAtbmYdhetFscUsmhWpjV1YXaW74djcX8ZwrdP
EqV7rzhdm4ER4kiFNL1BJ3eczxctCb4Xwz2kq/0IDQSeQFJO2OJPcO2fJiMWZVvpKsgqR3pVQoGd
tXV252c6gvj9JGLNGP8XO/cZEwW3JgAYpBfpXYZeBhiGoYP0DtKFobehDR2pIk16r9KGMoAIIyCC
yNCRXnSoAtIVpIkgqIAgUrz7me9b7yZ3N3dvbjbZZH6ek5NTkvPmfc/z41xqjAlW0aSThWtnJSnl
E1tNDaJG+zXCM0mGaDE5WtN2n3qTF7SSPf24TEKa3PuZXflqRE9E3d8Dzs5AePml1Xfy13984NR1
u+VQ3CBFiKm18N52vQLjM0403pFvnvbrZO/EW2LfkDLg0X8Tt+y8NsfL3Kca6x9hK40UWjeXewIK
bUvLGSx8E65dRDI8eaCLc8skZQuQLgseZoWXKhDDrTj6NgfaSZxA+cwjOubgW6b0iGVJ4K6HsfTe
8/Pv88pzFKt1Ss63DQxx6cJuShgGZvKP+nIeZ5HOHCuPfQ0Yypl8S/uChNI+TwhvBxxoTgguziQz
CSzepsYxvFuSiXNCHd42tixlX3EAyYWsxOoU+64cM4AxGLQIU0Jj3gJwpxtVd2U9rVDuUu3lCGHN
BzbEoKV08e99rH6Gq1V0ItNd8wWkI7m4wM3rflj7hezy/QiAnUCwGapOa13hI09sytoYdi1eXBI4
W9l1ujtV0KonyxZm09h23F1uzh9jjazNnlQpg9THVEqNFZWbLjIL5qFVtDCyix1VK74y9TaUulmD
kUgKfXd7jBcXW4rlz+eMfURhMe3DdI3xfoWM9zc7Xe+ot4dKXBsICaEN4VFjZhdDG6Y1GZVjGAn8
kye/dZR2qhwM9gwUSJkzt3jNmkrLvYR2OWrsFhKItwsNhr05j3gLK47znMlN0naSK1rckk0wpiEP
NR8Iw4N6542P4T42c9stxrQBxj8uTpv6WKzoq140CHmZAvhbFXY/62XAYZ2sKS/Eq4+T5DnzwmZW
he3NLgejuNnIImKH0vcJ96xD/Apxaq9omTyIuXVP+r8PoKznXOitaiyt9mnxhXw9a+t9Dtaqll9n
+2TJniJ/hFF4SNvFhfzkczBbKLVB6Riy8rvcvXtttEshmmLVzr59v1lXRHONsNgdD6i8MNvJdzdV
47T/0nk9Yyngw1M/S+isdaz8elCoT71nWYzL/JWTfpmqS5v12dsaM4MJtpycr/eJBU5wSmEvZd2X
xfRA1RSPgT30JwrnnwlWvgf1hMeTxqq4jXW8SzB7HtD67LBsqQ6W2CEekihsKvaVdcsvr6mz13Zz
y8NcKMS3/VVxuzlbV6NSjUbkIYUIVxdtLbxFu9RRUijs/Y+fVjwdp604eDjJrfF4/4gkpTn+NZL8
z3T3myT/KgT/nSQpw/F/RpJ/ZDTsDzA6WJLEkiSWJLEkiSXJPwdgSRJLkjpYkvyjjSVJLEliSRJL
kv/vSfKPSf57kvwzPP6OJH/Fzy+SlPqPPf7uFuX4J0lS4ne8/ibJXPNl/2Upqoh5cweUyGYs1QrJ
tnDz1jByyYBXCmkwTWRV4R3M85p3i+cqvYV9haA3leeav3xpI7A+uLGgCc6YI205TKWx+DZOTH2N
UhExB6TG5y+6k+vN5zvBkpyfTk87C+L3jbQyClzVI8bkb6/O68Stf2ogYTJ5Khqv4zmpSKLfSAXU
EeDDWPIijOM7fmIWkDR6xMbDHsfdS/R7KHEhq6ZKac8y9QpRXPj7WDL43CLVcEKE89wLoRJYYP78
3nMIA3xx8zOJBm/RMQNdwkveAXKucoSoKWPO6uvgQyepm1Cx+JkBk1Mx41aii10TetUiWpqqZ3O2
bL2r6NOCAKctE3XZmyKO8ZZokJRfDDTwhtpzrtP6DIIuFfL11J9jkaWQsSDMVK6j4DS+ywdvtp2s
xLkDp0h7DobYG9SZKhXcpm858y3Ek5NHQzzZaWL6XPtpQNqMrqlRGxjKNb9bNhtxssgTIq1kN2+T
aEmSdVic4LuzD6VMeKYCldN0us8L9K0jznMtGFdXnZvsp8JbEONK3aNg3/qntjkMOlX6RXT+2ix7
s1X+snKd7d1tJfbRHvJ5WXchd/zEe54L4H0O3AM4FLvdeWdxiB6Oeg8mFnO2FIiuYXEsRwepvmq5
s6i2iAMsrrh6oHYWgm4KAT4R7niye31JXlIu0LoctXCgXNrbTpPqBp0b8m+N1Owk3Werc4xm0wso
7FAyN5S0UjTdet5r8HE60uu6hFtc/j0TxOplZ3MRvQdbbcNPzhuyfoUziYXi9THQ42abhnS5ta9O
zd6Y5SCYfrlcmPIWRbVxdwQh0eGPbrcpPnv6nRPmQlCq2+nUzZS39yKJBUodxjVtF3gj1H2eMih4
9ILfxhk/uY/09Vp7QetrvDwfQak8RIP7QRf0EL1wTYdlqU2OjmRIFB52e4Ad52lO0bUcs0GeOa1Q
xYecxY84XEj3he0cltk+zRJcJaoMzqmX+Zrv1NfhQrc9IZEVojdieLZHI3mU66MhwzRJsAbDjEe4
sVaF7xSpr39+lK3GrM9x5kGg7RU6VgYt1oqyAwrWwGjwYx9Axm9vdRnSgBZVHHBryMBRWtn+1e7P
TBkQwswRIdUtBD9w5ctu95kw226ufjKf4S7VToLkSDORJi36ASwwDhlosSei4DLz13iqDx+0QFbx
VGUwud5Sbze3OoSsqrVdgxO5xW/XXls7IrNNNi1XL9ngYX3Zq1DGhZD4mqvVhNA4ytx+RYF0SMav
A9jcSy6nTwduSiCSWPha2PVGwk8FrHKXzyWngqDeIDST3uxOV2gHwI6wK/EiO+rUQOKwO8ffhJTy
ZKxiMw6fbF+ozPwNr8Z5Tr/k2I3gmwLP4ZmDvAQ73HMW/dMa416fiFxt6zAA8pHQ+A7eqG+6OF5W
zkzJ7vAcuchL1q3rmNeXJnYflm1hiWnRrcNFnxsoUBI+d5u1WmLvE21cBVy0AHy8q9c42959DB7w
tREo5ZMxDrvOfRypkIaIX1gSkSdRA8+YbMCjYIGX6HbhXaPiozgWw1gf/sA7uoCb+9T3gClqcF2a
EpAW+Rbx7rKTpdIjaHdsH9PhjeAIwf5IMov3ahebjKWb/Aa9e4xJLauC557DnWcXNEDS/MkdQFSJ
Zs+C3z3F86kXJf21gPGm1e0m6jncJgEcSt3V4T2dJOMv4hpCh19X/EpAMJkI4U6k2sMfJ+N7HRcP
itN9im7zUsY/WRdtuGsYRM0jT1hg8ZHyEb0oSv8bobuuBxIh1NSbnqdjWMmt6BWPq3j85McDfjoz
fosvWaFr08Y+F/diedhJe7h9v/T1Hw+sRYg5IsDh/OTxn6EKi8JpqLUhoXmatuOHo54B3/YIOxg/
kNfz1JzgDSbbSU/WjPe5Dx4NiOLJaStBbIiWrbmOpYqGSGwGxJY/peoGEuBR1McNUWz31IB0CUZY
PDqty4C8K72mHKr8pGPhmrf1YjWC+42yX9SypanpDhiL5AY7ECtOFESlHZ9ZDZJOF9iWE5q9tmOh
tSDW63YIyXLLtr2YKbHor0nwitNiil/WZNFOySHwX4fKJ4dhYPBIGLAp+tWkT70I2D5KLo8EZQeS
eSXUR3GDjr4PpkeP8pFrQl8yCGPOvd8dZqwqEHomrSoIkXDkXUs8kmqeghBx9a9JOgVzs2R3mciD
LfgDa20c2pVwOvx/THxyNjuCkBdovzesNDDMePUVfWUfhYtD9HGM+B8Y8K96718wYIm/nhq/DVji
r1Lo32jAv5bBGrAO1oCxBow1YBGsAWMNGGvAWAPGGvCvNtaAsQbMgTVgrAFjDVjkf2XAv+7s/2DA
fx727wxYkuMvA4b83S/gvwb+cwb8+2H5XwzYZ1nzDwMGGZWXs6EX5QruBXjLGlGP1oyhiIsUITTe
TVNDvFsSV+mRfnCRSnX3AgOaXpRk0dtCcfgEuZbvoQ1nyuE5tUtS7/3vQ2jNGg6ZN3GPwsVDAxa1
0V51heWusqFHBxkVia7qRt0SSlcAXreSnwoVrPAlpGMZPr2MC3CcaQIhl+qgSe9xXzCApS+OyjtT
zHCltBVY7AH1OYU2ag6ptduauTjVR4XEZzJ276u1GD6gKulTwoc5bamVLXDHy64oioV9vz4h2gHa
DYIWiT8+2ymj1qBn0VE1LvIA0T0gF1dOcBw2ss24Ul5+LXJ2VsU1cHkjE1Jz+b4nXj5+GnFtQnDA
tHlBuc6SUahV+6LQKKMe09gPsswv9kuBHrqQ4/Bti5MWEH/HF33pfWF+tUfcb1ClTJtS8/J2rv09
8h1cvPsHRL30otHBp0npvKyIJbzploQTTgKjhzGgoRg0SShDCbSHOytgnSXlc/gKY0ZbsCqdJi7B
F7w2Xma+lN0kLoAx6m7Tk4/yZbZdWoyfUUejhif1JCMp8Ok1DslWGUSDASO7yOHiPqvtu4kGeOqN
05Fv++uEyMYn6Vmsd4y+pD6Y8aBOhF9ZSCrnoep6GM49WjVOO0NjpSY3kgdvup/s6CazlEtYQYPa
VxrspyITTzKrvsreAQiq0Kp9ZzRBFCCPIutfH/qZC+umeWUbLG4O5JCmOrEFtzXNsJ1S2DgKZFjH
t3y5mc9z5GhSpDyxjubs1ihdBwjQBXZFKeMnCDUOrB5PRkxy0Y2UAJh5TSxqVZQSTOAwnJfJ5r2u
VgcS1g+uvx7F7bXCATbjhC/hnljHqjbaPjyvTVAtUnpUo6ZnWcBhwxHqHgWtsWBT4ebxVx/NyY1a
thiuCpoWrDXUYfPweC5gJlTtvpFE6G53IGU4JGUHNbJ4ut4ebXm2WyUQ98YQ7BW0qLEjoEI5DVPA
SQ92PGlbzt/hJ45QJZCI9LcNb7pf5CNrqCGW4S5B+wqhc1xJRT7MtJ8296ErATaPwxyfb/TpMy/3
iougNNIrxePtnLAZ/1SE3noQTWF/kYYMk1SHIFKYVJHWTYltMo5Vhwf4JaQ/5yOCNzVz+9WuL/oW
V5Xmimromj5cVewlPy5zdrT2+fg69HKrRl3p0WOWwXkJzGVHVLtQzosqlg+sBgneLp1ExvhHGwft
Aux3994423qPestL9o170OmNF07c9nw6VsfDT7De78XxNLuXjviN1M4u1QxsMATVKQlJQHyi0gU4
l4s4XafKc3JbrTQpcLGtr1WwYviGeehvCrRokllZ9hayDOO7K3ghK8BiWp74oQLccj5t1p9l77R/
qT0v6DPSZM6mvzG50RrJ8MOUU5X4xTfvAoRyFZAcGjyrr3q6q8I7oV5XHDOsknFo2tOBt8iJHCuT
tsfc5Lsmz6351BEWgPzmmr47BGgkdE5TO5oxt9otdzQY7FaAfiOzoj/fodqias4YOVCkVGOToiBl
eqzM7fKOZv22XudQte2oCEMqsxsiKmj/WpJBzmkwyk5fCc3eT0E6nfWzG1H6FQCO28pVzgIEJcq8
bEciOJu/oLKoSrdfiT0bPpJf/Nl1ZatS2MEA3u34YVWXfuxi+qrbD6pI/+2qHfyoYgRm6ZItUZIs
6p1091nRQ10L+DYprd+BXiA/6vKetw1StCIZNk8VQmqXTZj7TEQJIl2rzySN0+4bDpBGFQLssyMh
rn4oMcUI37RK9mDAJ4bh8dT3lGDwl4R414Cj0jcGFxyTzF29QGqeJOnLhV74bNrQZ9bvK+KRr69f
n+870aAIvaE/IrCt41N86ZPg4/DyayXo9M1Jn2m+C6RNcja4hw3IOwrJdN7Ry26ftEgJQr+cYBLy
n5Ls9aslYGh4wYHs4jz5ShOlnTgPAN2yfGA/YO07EzgnGl3Vu+YS/HgT3HPVwGwxywxDbTya5dec
niCEkqU2sTl8NGxPOuI4r4l7axU+2dXU1dOFtJ+041TQdzn/EXo7AH4mijH5G3v2HRNVny5w3AII
guAggiK9jcDQhwERhjLSZKjSBOkOIL1LrwMj3aH33nsXaVKH3l6KQxcQkCJdunDzet99373J7s1m
s7nJTea/c05yWvI7OU8+X0NVarK7cQ83jsCc87ajej8quJrOkB33qFFEmyBAi9r1rmOs1MwhnESk
pypq3bHwbUS+uk34UCwxKLLbl8d8d2jSVOz8jTBD4C3yL2OkCudfF1mmVBTwZI6vbpBci2bO0/tH
nCvE8O9x7p+jwl+c+7ch+j/JucIM/zeciwNcHODiABcHuDjAxQEuDnBxgPtrHwe4OMCVxwEuDnBx
gPv/HnB/v8g/B9w/VuXfAe6vhfn7Fv/v/9G/DvMx/IuAK/jX9/oX4KZozdgs9wC8PmtRVPAMThWg
vFg/StCJtoBoDM0gJkyPDFNu6WRZbX9bYi2c+vGWxQcd37S2pjY32JhUheaTyVLf2GhIEdGodU3P
o3mQk4y/fHeJvmVPOEguCBwCu75us3dZpVZRVCKMtKh1vVqmDei2AEg18PN84iHEWy8nVs97hPBn
qxwzS39NM6oNi7FLsssXzEl5Y25QO/roN97XA49Z418SIVrKq62ztSEhe0LhmUfygYyKu/QZlepC
BDzhWSrU0kdo3Xs+Wez4441cDtkHInoXdYYqrVKBJFmP89QClmKyicMcIj7zePv9XIK5uxfCv51g
JFn6ZE4NvIC5So8JqAwSbTp88zCphe3TZ4G81zdFR2LQGi0eFWRuRH5sNHNEl+hLRBu7CVMQazac
DZCjFT5T8lZXWE/cLPKJHf6P664Zj4Fojbu17FVkAAwa1snM0TGZzzY3Bj6Ws0c9g2ezFQKF5URo
sEBMbjObOiEKco3tSjUruT+MrH0em3G9/KddSYiXvoadF4hsuHgAg73JQMJJRXLfCHxmqC3dPmWw
qqHv3b+xVIEazJxte6C/nLDLIjUsAQy77RZlThVKNPLy8Rs8kd/e5Un6R09GVPTanqmrV4hsCUkz
8DEjfB8q9NgYYre1JyDKYS8ytfl3OTbUrCRs4G49me0Wfs6qq8Xu58YOeuIru7ZUBapIQLDOY+hI
/KFSM7mhPIyW9MYAyKHXxxoUBzeqTwjM4Y+AfKoMPAl0ypSNZPa3gfDG8YmARU002utlBIsmMwBQ
EYLAiZvwFyWPQGp0AiHbrohPTR23MT1JTDmVvTFeMsrUgUGrYDsbv6atIesKz+ZumqUZE7aY7Bd5
X4HvJFbHMPsFQGLxgzvaDOqQh0JUPqjIK7+dwHrgoldrKz9FBqsqfzBZtyUW7vue7jLyWi21rlbs
6F4Qof1X11EUIWfqJ0qmthPdG53uFiakx5/X57he0R05J5ZanJAaU1bxjmbdUZI1SrCmy1aU2yLX
eP5V8dyCi5oot1VJkJwZpDir/8Sq2VnKSfMAPf6M7pzDTJ10eF/76eBlR0fKPvdNuo6Lbt3Kp9Da
mWiCINQdJV5EJpRMYw4mWJl4UjNslNrcmn7d5NBJOO6+urPmZNclALJiZPaR/M4obMme6KcUSKM0
jVTOyHBdMkqPFKUocF04K6FOTSv49ihGObnig3Jhz+GPxXetujqrpMr0Ak1CM+VGL2I07nhcnHSw
x71vYdEPW6t4X8A/m5vkRCZNHp1Oggwx8RDx4Y0otHj2KjEmjPQslw39QjbXouGbvIfeEfxAs12r
D2H1ZLugab3gg5a263EOVuLooolLc6oD8onMtCPviYb9o2TJh85qk27vbi73+JSPrEFDAebV1/SV
ZEgElbzq9ONNxyVOmhki0Pouw1OXXU8olubGU+pFJHXPymx1XuQH1o3zL9dUlPaIUC6eCLpMcx4K
c926eZ4yVqKQZi7bkX+Tcvut+DU8BTa0fI/iEerUSmF7/F6hMcdhClDt5faWGni/k+fQzV80s13r
t/ynDzBD0Zsr3Jx1EI82cl2iNpqhRsb6dVlHG0KZHzS3f0o5mfAepg10A+YhygW071veD39+26b2
ftM3ethHQJlq/Xt+5IE3g8ZycqQC9WgMUnSP8vZb8tM4B0YqxEvP5LLX/lXmvPCjwBWRm3WBIj4G
VFyxpEtIN0qYjaqXvN7KMFYsAgF9ODLxhe3ckb+YrlHR8rN5VkqnSsLgMH2HDDjciHMcjH4hetAT
xlc6IjgXrbZL7/wgSuAB+Y3ehbBzsyiwtVn8g6Ru2Klx/UAdtkS01y9xvpVOS4+pXgM5qCa/bufm
d8HAJA1tZX11el7ZKmREEgteDZiQJfviZV9S2UjsQPi+pIdbIl3OVJNeZsMYMcGmiTBWDa4VUzez
HiMNHorca2BL6oRHIqtmWqir6oHDiMq+TNK4vi2m66SmLsE6+P0PPlcCz6XnPc+Syhl5Y/Y9KjrZ
Y9HtCTTRZ73Sxg0Gi8+yYqBTUo/S+H9OvioOXm/Ybsr/HsJCd6QXT+4f7iw6lcDIk/jsJ2j6fjVo
1QyaKVVdAvftNUa9AaYYJznaK1m0pMXLrIFDVdLQdbVfBU89uRgFQ3ZjdaIidkP2T1Umo5MShwYZ
696KaVoqf3rkqGV7yyRM5gWsgWV4UOkG8NS17pS60PzccrZU1zrhQk356Rc5d4C4+OXxs2UJr2ou
unQL9Y+99q8NHnJgFFnQITmByV8Ftmi0YVGG5wnWZqKj6gOn3fcGuMXXm24AyfHkmb9L8m9PC6CG
66zL7NBeiKyNQvzrhjCjtR4Xl1expw0Fd3bKUodhvAlchiMXDQmQxu9ivRw9X/YSYqdahjxyhVNX
Vz6UcJOeB5ESQM2tMNaRKSQFaa6bSLZqX361J0KDp4Fm/RGOYBvvss3EKBNmAMByyW1W7Cu2ruzK
lbsiGv8dPNNqLB2FrgkDr1E+Px3fpZTWhHSA5wPMAJ3koNzTXgte7inQnHfT6eFpvsvSgVlYIm2r
ULFwsNlssjJhKHYz4Oh1XiugFkVvRcq6DbdLnZ9r5x7eNL4yf27wDqvu3Zw6DFBod0lMFl5iuUwM
7eITW3Sns4x+CkzuTT3OQF0kqMcMRy/ABz2kHOLnJQI5Cb0RzORAxradVSHOoJnvINNwlRps6AAB
hGLJhV0wjkoAhqCvgnBvbxEJ1C2t1nxdLRWfIxjyceR0RnW/ARulDgQp2u25HMWJvYOjxrkVZr+n
5/lgFJdfRXwgLSsJert7ABkuojlCidhaBFtah9xSVCPffanr8/Eooy1sZvEkLW+ulq3htp7xiIZV
s1kRcC4vfnnY5i7pB7mFlfl25plppXeKFf4eUasrZbwLledflDXpO9wca8ilU6EfFMWelkecLMAP
sdaWogZitJYlEFdh435s+eLel5IONuau1nq0TB6N+2fpxPKN7wq+Q2x4GwETF8oL5qHX7nYUguFn
vti2ybAa10qfrHDZ8MJI9Hqk7+a8lvbaxGcfyUoUN39KQ70KvI+3JyDvSPw6wTX+Fam+f9Acfk31
/0Zz+BM8/moOgn8bxP+DzeHXbXDN4b9ZiAHXHHDNAdccGHDNAdccGHDNAdcccM0B1xxwzeEXtzLg
mgOuOeCawz9tDr++xv+lOfzxsn/XHAT/OIH/94nnr8MQhn+1OQj++SD/ozk4zPQAvNa0nCZarikJ
Y2Z5fYv2MyZY7YsmXaw0IbXFohIsLIyU8vjIpuILmX0qt14Pb24zUzugxEfjeHbtQZvDFaf07a6Z
ied38yfm/IlDdqnEn0W9VwUIyLO8qdVrahY216FPEc7qcN87Ok5/MkdPCSidPFqOl5ZY3LAlfhBq
aRKVG/xhLU3dWJs8Wh5fIfADNV+biQXUxFLIWLXzoyD1q9essadlfXSWHUWQsJ3xiAYgrTSoi96/
GlRGq68DQ1cFzWbbcV+2aoYZHlf2lA4WTyztECvhczl19iYgCxNqDG8w2rHh6X86QbuE7mh182iw
P2qpjA+uglzmsyvezyfp7QJGJoNbJ3KcNUQMfEjrcxTpMGG3Nj09Nun2o9qF7xICLzY3IonbhOOJ
uJ4scwjWNJR0rOphf5s5S5hbQ1YUiQWrCAAemLWCWR3ICNwoXiONOCyMi/rFuB1RFOUs90w3sugW
Gaztv6S5MiX4JRFQNxHI7ilSf7a12KS8WNwY2wAeQ5buQFmiTwLKmbTXYnzmWKKQ8sm2dTK0LZ7o
fZi+92CR8afsRq+PuYx9QYWAQklfivwUeWd12/QowPxHcsqdymC/Iv3MMUx4QdnBRqbwiPunRk6p
wL4YRo54gpk0s5k12MpGF350Un5zBlx3Q87DwMZRJMPS/EXMaYO7Z6VgOZ3D2jK/0fQzOr7plquq
z3bOoKujh/QxLGj7q9xCHmV9zasEeegFXEM5F8ZSDjg1sCD2rUAYmgx6584dHEF4hnsCH/Ftvr66
l3c/1DiXgDGMY7TWuSRRkggpFR8l0wGIfLgkaxCKFODKQ4i3SI5lE27XBpcWeWD6LQNc+DEsyI7L
qolGWLdy0Snbm/F6RTWDfqVggDtJEOLGDlzIIA+Vy+Xxk6KR4lX6VeD8FWromxBS5iNRVvJ7isx7
eLLJUehsGqIBBDSaBR57xSwf3sX2ytraExaHVyDp8qYdeXcZPDgWGhPUa4RZXe2b2Dh42lB/8Y5x
KFtd6NQcRRsCMpT3u0EBf3wYeu6kRIJ83sD/o9M3R3GCs49bgueZZ+UDOeuqtlZ/gYnP9+W3uJQ5
j/sfT+coC0NK5981n2FtiUdclhyDG1RpuuTORcEzRrrH5yg9peQt1ppO6pEdwik3rHj8LRH1ly/v
N3o0cB7rLhzbQQWnlSPpsp2RlFi/Om+syYiqhpXj9MJE8Y3U+fuezBvqfLTDYXuA6jfMfG4gh6Rc
qZqWx/lH0ICbUzawt9JuBeaoqzRak+d82bvGDDRlfNZr8WX981TsvgzfiWpb03ZDmPpUQ5F1pbzq
KTGkum9oqvivLT0jq705281Ty1O6sm5H1Iov/mO6T6OquPMrSDlxi6/mbrPOQN5dcYli5zT30onn
fPhJdrIfEyhIK/SA15qppKuxR7zmY60/7hJMmd60eKoNb7m26FS5AEU0UtGrILUEiu3husVCtD7h
ARjv3OipDMYVKGiEQBMrORLdHpwRG2U4OSZ5UEeGqNaGbo1iF1IBgQplvHr+lhUnbwX96GX9Nd51
WXCTc9bSCLxsebOozpJgaeoN5npUVdIovId+xfXh5d63IipuSabrFsL0QXgxpqoFOTU1vPcwObuv
YX0siI3OwfEb62tfxibW7NgDilXw0i+t0oe0dqBN6ZHMz0HNSoOxOmA6uXuncXwMP3Va9Brx1hAv
PWnpnaLsx2a4GzHPvRytqjh8LLsvpk5qWh/EeyWN6CnorSp/iV3jp+fz327u9RJLECTjsLrY4A5f
pnlO42cqgqo1T+nQMVfrP2ZmIDShSpD5FnxCCBsrooNZEMDIoU2QMcy4i9/47E4/1dN+mhXTFdU7
W+SySnofAnejaeDlsfv1ot2e72VuLYzh602CxJdMg+nV6qUjjsny6m/tHKz1GRAzkj+ygtk5vp8K
CL6lUeli+sKMn7VQL+JsNcW2UjYr0sR1pbeB1yR22ylsw8j+nmhsl0h+336a31Ptydn1WlJ7k+Av
bT+Zyq+OWRdUzGX7eBbJz9nJbm86+HPlDT1Lf22/TFS6DC3xaHI9+/YbGu4e0kLSpugKmbWicJG2
+8YwBgSU5XYtDtQE1MCMB3lE9x7XfZ+Sqo8jYlxDiCTFJ7ol86tVV+WZsc2KzvEBItI7bb2raZd5
Qg6yPKfjJwoEZKhud2NA/8XemcdDtf9/3JJkKbKUbhTdsoZhhjHEXITKEiHJljQJMczYx3bpIkR1
bSEUyi4pW2OrRHYR2RpLlmxjiWGG8Ruq39c1fo/T4z5+j98fv4f/nDPnfR6f9+PzPO/tdR7H4CPj
p6vXXxS4xstGI8CuqeITvYHHxd9eF7nIfHJ1b6jglP3H4zaX5aW+qb2eWBo93+aQsJRb4nNy+qho
LLY+PydvqrJ6731RvuzxE0r08GR9A5r7sSfE7yV2B2ZHRmiktN+uDoppZP14tvpvbNhsINGLRcWU
42oSQ5GwbP1AaQNUDcE4Eah+GLxbGSK1+6QU8asX5zXGujEyTKzALMpNPd9nZLgzW3TxVSkBI/X2
Sk/gLo3DY6cz906Hd2kdbuJwajfQln+aJmSiQ4Oee6vXlehPZyCwN4+TiC1rVNYyqlDi7s9kj7/f
Ht4xKpDK3jpJvp42Hmx+mNVjgDdY0PB8irCK0MNP06UPaw3H+0gTbEk+NzpKv2bOtnvKv7zX/vh2
jkO5aG9tJ+Fr67if9gt6gb4pzQR155fElfBCD3NKqOghXRAsXMiqWVZxwizpBF0IfRIj5oD/PDQs
etvsKtbxya22TM7f74o1DHdezExZTKqtH/0ow+fo0G8kIX72N4alvhXu6v1oiAItzAcC7k32Jh0z
DfADTfcYLKA6vlSLhLd92FOWybEYPGkQn6pdVnAP1mjJZC+vQbJ4aJA+gSxx8Z891n1RI1nPKcEp
gdF0+SuW1/yAigILcmzIKpEP1T2VhXU4sb+GVcJqiY4+30rVXXyQieuMKap1RlGmS0aCuNvsWN9t
VCu6r7Ev7v3sS7vKfj5B9xL0s9ojfGz+dGzOnNlzKJNPuNn4maKmIzU6MDmMll2zhdZ5pUzrlQIT
heJCf/LAQIlKVusU+JJV0SNSGaEpfiKh4EBbtG2qxtQT4XmXhSWOY1Knkm2R4grO6mO0qakEG8u6
F9Nmlx/HcBKfhj6qmCv9PeNgxOFZn49pXWadsWQRqKkM3YzIAJmkEr8yM2xhMJmunTJzQCjhXdyT
8OB7jXLsJfMNPl30Ttip2+2f+vYm69hCinhJ6zLFXLiF5XYyBZT/38kUP/vC/8gUsj9rUWUHByTl
hAnlqu+F8Lpy8L+pXchtXrPyRqdmeOEsv7C9JaVuRMrbIxDONg7W6D8QzmgbCSTKWkRS//sVGz3e
dyc3Fkk50ne56rxxQsvGwW7DR6t1HWR9xrNe1oOhGyPW7+v8scLvRypI1DVKjbr51Bl+yfNblgrj
/7+RWXa+1LMjuuyILjuiy47osiO68O+ILjuiy47ocnZHdNk4sSO67IguO6LL/yvRZSP3/c+iy4+8
skl02QgI639RItYm0WXjwl8SXX5ElH+KLg1GxhE9suw+hDz+loMZfiWD2sMZPTn6qTfCr3/kUmth
rB6ZznyZY/BBsLECP9Ni+eDyU6QajWTUAKu1kg/a0cWQi2u/QW/OHrVDKwFwA7tU98CoJh7RfVlZ
8ReT7SfeHrItyso6imQqRRodEi1cHJ0XVbaZHWUOe38lbMAUg3GohlQn/B6ln6CPlHkTeaZ97Zwd
9I1xtI11e25sAXbZYPpofW5mRHq5ao6NkqFJW+CQu9y+RUZCX4jYnSr2XX6IPVentFB2veIZYDLH
QZ6+yMZy6Y7BJ5dWy46lq2R9plsZ4GAKETmtDkpLl8rCtTgteDu5ZiZ/eCev6OKvy7lv6cSTupK3
B1weWB3DeHmCEioaYCtKAqxTWqJSZwtHZqrEtQIuPNANFllNWbJRkxLQSpGpujXKzA2/9ekrzys2
srYHkt0wPYs+rjvlff71yD+Ryb+VDPrBehM4evGoiwwFGM7MSaWPuAqTdNZcPpFMULPnFbqYXtrP
i7V/VCTZZNMZrwTyIO7e5UlgEGqSE2YM6wsZ43W+JvFsRF/nGUwi3q0TvuZphnVfZS7zCXeAInFl
xV296maRHHvEn3bsJnoulouy7Y6q4SvNiitU1VjyCqTj3M2aWslLiwChW51euFZUvnjFeSioTRoW
xezHhS1PtetzlWauSrJRT41+PK/7wEvUzfvb1WBzj9J9szGvzKy6O0ZmYrjO5N0n5itDFwTMNBvu
R4icvhtZ49yozOV6SrOTi6XYSHOCaf5UkVpYkrmguhIXLpyln3YoxPOdeK9/P8+FKd6vyszQydYL
zCyezCP+PC0JLajALJp6qybJ/jqM6SNWmCnuVLtGQDmtRA6TdcmZxJi14vMsH40NVM6evLpyKHUy
gZ4rRMY4MvDuwdT95D27X05x+I6xCxEyipUiP5YLNauM7LlnnB7zmF5kSpJBFPKgTrim15Yj2+Z4
3gFnTEZnovXDCvtyx54WNnBZL621cyJBD7mrTv56V6r2l/APnT323nLtCriT1tWOI4xGXV9kiaI3
jI4nXcutv9gfrtkRVAomiRUH21qHmxm+LuuNH+pABuuzBdc/WlAF/yltow9OoV8JCNOsbD22x4Su
vOThgcG4/QPpXfEnyN0Jgm9Cmg2GBv8KTaGJuvVlf2UsS0G9LjlYzPc9/kBhoVjF6Qd2ilG6J5Zg
8s9jHN9n1+93PAAJMLYBXw3WbTZI+XCmCRVLh1jEoRa9UT1R2kF+ge+ihDIR0TeTGW6tGSczNVwK
Ub83w3EumVf7z2RQ/L0TipkoE1ZPs1orBY6HKcWOto63r3ysTxZ/iAqrukavk6+LHjFXM8TkYaef
6+sNm49Hjr6NMDvCJ/QwT1imHD0yhB2rgY21MNYu6mKEplyki7Uxk9XVk+MC+2GIwtZrsQqQ4iOO
R/4qVB/jzP9L1dzgiaxLGXuI4IC+SAoqW9H6+lCc8k3DUQ31XL/9ZIPG4m+2c+o3cvO/uO6aSYtj
ZTs+6MCWKNlfmR/g6SX/+ELVyap0/07NFguCp4DV6l1iR/T8kCLxRlzmZ3Fn48xDxfuTpAIa/EWW
bY42PsKaXphSexp1TrI2cTLP4IZ7pqJZ2vyjc2CLZ4nQhYFDqJTIFuML7ZporqhFJqcjI/y8gY7F
S1+TlR95BJ99Ocad4WshkX45Y9zlkfDdPS+cGvmd4+4tf2GVaUqKU16Dp/mjrs6GWGPYJaJDWOoe
aJYrDRRwitD68UdFZ1bfR7EzTuUJ89zSyy5Q6jzIvBt7hxiUY8JgGGc59sIq7m+f3x7BmCICy0RM
SK85btMeLK0ZCS4NylRzc0H/YXZHnmd47ktVsrYTia4vLgfXm6qrzEFvXyaq8KoZEYSu9GRI42jy
S4Rw+LOFeSTxatVVZeafeLLa5JyhU8lUO5n6WiYY8inILfHcNCmVPsh+9sTxmnO/C9O93jtq66XT
KHCF+YgecVdAmkeapA8o2n1NV5TTuQwXMKvatfKxG9/M7eULSrfT6kpj9pJRMDB+Ecbm05jsoVm1
og8xCh9RFS0OSJ9b7MnN4M3taXrB191Ro7C2V99Z9JlWYZXgjFKiTctcDaN4/3weDT1N5keJ8W3G
yxvtwJbx8sZwc9Pg1QDlgtj4ZS8lBaHQzqo3LFH8lAy8V1LL8ueRLOXIyOaa8431sTJ0vZ8GrTf7
IEqVCKVkvY15rCUasXFryXOqZ3TVVMSMbBysr63PgcUvIKxdblJu832wehqBtkLZODojUZQb/OwW
/pFdN73SIHnW4RrCHXGN/78r0vViG/KjCNqcYWWAjajehZCVBTaCUhlBgY3kqIzkgI1gVEYwQKMf
decmIygI2EiKykgK2IiqqIFKAxuBqYzAwEYQKiNgIqSpiIACEyFNRQQUmIifk+9NRsBESFMRAQUm
QpqKCCgwEWAqIuSAiQBTESEHTASYigg5YCLAVETIARMBpiJCDpgIMBURcsBEgKmIkAMm4meTuskI
mAgwFRFywESAqYiQAyYCQkUEDJgI6v84BQMmAkJFBAyYCAgVETBgIiBURMCAiYBQEQEDJoL6s6sw
YCJ+jgc2GQETAaEiAgZMBISKCBgwETJbiYCAgImg+nwBBARMhMxWIiAgYCJkthIBAQETIbOVCAgI
mAiZrURAQMBEUL1TCQEBEyGzlQgICJgIma1EQEDARMhsJQICAiZClooIKWAiZKmIkAImgmo4ApEC
JkKWiggpYCJkqYiQAiZClooIqZ9ErA9pfsxj1ueQ2w5s/jmgIS4QcKt5FVD4suzyyNNEu6QDn0nP
8dWENqTvEY9Vq6EhpCbe14w0NtHaCZ/2WV4dGU1qrlgrX10eHa/BYcxXPi0M1tyGwqd9icsrQ52H
CUk3cWVu77KNvTkFmxIVkPPROdbNid5LMwPxUKSSL3mFRMCvra2Bw/z1QEs0f/jR0sjXXz7MjNja
FnyvhLe6RCm7fsGlySptZv8/uGj6w6dpH9sV3z1nwsIkfnmXwLFS5uyiWaHDe3ENmKGwNpnLS96h
6LqT/vZZDVbSGS1nVQVq+2/HhIsmwG/aIub1al52V8zQxL6I3Ot1UJ6uRExD8nBhdWfeTG/LgrZG
JWetSbOiyUTv9ZdEq/WXZ/LCDG9u5wZ0u52R+qWdmZnAvy+CW/cSEzBEs2+tnQzWnxvL5j1IbciJ
I94PnYf0G6sJ4kZKEljC8MzEUSh81XN1qLke77uvjChF+Nx5FgqXLCYMt4TmdeK8FTxWmxIYQkXF
xFhYQuPi4g5IXPbq768SM8o9RdmUic483zUygoch5YounR+lV9OX1buynTdy222K3C95Q9l1PAUc
MplArEkiWfhYkJfs1urx9Ue9HjqR5lcwFovlK06E+iQhHNl0dcmOEIoHI30dKuacBu+cj0/yUpgd
GS18isPk+Z6TJwt+aZn49jfSCE4sHZjt9HCDEyzWIFMdT80kyyuWyATc2hpryhUu1os07FdomtIM
+rdzBbadK7/0yHiS5vFkIzgm1zdEnvjOoZNlVFGSpQkb74uv79awIOX6Nsgty86+jR8PPRoNX/Ic
bIxgtPD1XVrIwxOf9oLx9ZJel5xHh1qNcM2nfF6hhqJDQupiY2MjIyMTExPtewrNsO6z1fUxcMq+
rK3B3wjzMARw0+zioVm+rGm3jSPSoH/tCJGEX8tprhj9vMrhNnlnoemg7eGk7ikfPczsm7ogC6NT
S5cxX1X7q4yUGM2jknwrpluLQo/6eC8tEL4S4HZHvBvh80ozM/GTbfgDOBJqcKqZ3lpyQTuWnY9v
amyMh5tbBlEX+SaIDe49960zz+I/OyIgeObzdo5I/XtHvk3gyDHw3yR8v31eu2A3r//IMIKXgB3D
Ep3eDCHReK/3pxY6bAgsf081t50vX49mfc0VFStkzMBq822o0l98Pvb584jagc6CaS/Y8nh9E32Q
ra0tFottaGy0unr1elOCx3h7hhv+8+oqKcaSK8y/ipmGjpVmvFk9bztHpP89WqtD+MAa3PPzZQV9
CyqufZzRw2xaRYrIkhXLvhRkG9I7HE5+d5OEHr5zPiW83Nh5beLO+QqlFaLbZGNzaShekVDW3j3X
a7U2QQnJSe4kNGHAKi0tbXFxsbS0VE9Pb36k8ZX77GCMpAV5lVQDYlavusJAQwleQSQ14e0cAf9r
R0pnv3a2myQNRVRI9ZFNHRd+pziS7aqUVzJjOTLVnGMEVz/qbVW88OBDoFCrhnlz6fzwYJBFnu9K
H3nFZLaEoIMxz7zpNfJyzRD3MiLIwqfHY+yGlf7fWVlZ9+7pqai87i1BS5pjl4brYyhxS2o9mVyi
XU8mnCdPG2znCITaEUpP90u5JJ+JRoCVphIHTkXTKzx19GO1SrtroBL4jCU1f08w+pT7wf12OVLq
eO8mm+sNJ49h8OjwV0Udtjmw0UgOGv6rIn8FGyxgEpNeUXApKhbbLqhKb5e8f5H7uVFcnAbu9b6K
jk9LkXbDqk8QbFwdiiJy8w4TbXgK97dPzV22a9Nv4mbLcVVK8ppvqybA4atkzGRjxHM03t61nN1s
/ozbxHyp5tF9FWSnxfE7i4uuRkZGxsbGbm6EEvSo+SvXKUp2oARv6/Xs8GwjO5xtUM3ezpFtUjYU
+kvYE6b7JrsK+Hh5TU1NUWg05Un7HkJc+iv/nJy8aWJiws3NbWlpqaOjIysrKyIiIi4uzsYWIW5S
CFrf/G8bmz9ty6Ww3bK2S8GUZ/RXKJ4hW3eVEJ70JKFzvGqfTdK2PWekoClRTEJ0zuNlDsIv4b2q
/ouZL4Fq8lq7DqCgoqIoIKIEB8QqCjLPccYZBRUFJCggWhQElTlJsVpUVKyKqAgRJxCQKIPMBBlk
KkRFQGQIc4AAIQlJyPydF9vb23vf//uTy3dZdbG6uqx1nX2eYe/9nHPeQsYycXLEBlvymVCeUEgi
KhFF8WHMjIoiR3tvpF9aUH+GuIGhgKbhxvN8hL8kJa3etm3bDz+8+vr167H8AAxvbED8O12dgJrj
6jLUr3AgYJjXWCLizcOJsZs3y8rJyaFQuLAwQdm1Berq6iDA1lZWqnquZ7y8vI4f9xtpNf/lgP6s
X1YgZugjFC/NcYJbAxxlAukpSaICqvmsgBbOLbjjxLx6miv3i6fSNEfrXdbcAFIkskYzbKalwClg
eEFfr9LzRpvkglFRCR9NFolaOIyIDy8TU2uQ/q9DlDFjtXG2dnwe78yZMzm5ucbGxhoaGlAf6K5Q
glYvbw2t/uE383cwqzeE4UljyRYPAlQeqfb69Wv1RYuev3jh7OTEYDLBDsY9fqy7bl1kZKRYwC2F
uqn+RDfd36akDrcAOH6TbPtCxlh23S+UPrTEZxCCit8MhX/m6Zx1tIkPYmZQvumkxJHMHa3uHeU8
7+vi5wOi5tID++L00kLRDAK2LHMofDxPh+tFxmP5zLEru7lcLuC21NTU+/fvZ3iRsOyxZjwKt2j7
+9WLxhBaxQjHJIsjcKuHITUTieQ4j0Vtqouz9PTwWAR+qatHR0dT6uKonZ3LtLXLP3w4+eOPi5WV
u3p7XyQmcjpLFSbSUA0KpNh3bgHcSuBYaYNk9TwmcuRVZc+i4vX1cNA+tubZLvAJs+CyvQZyOYMa
+De6uCeZop3UaCVOkaCIxQ1sK1fKc45/SwhKyuw83darZGojzDvH3XXixNN79xauWPEsI4M52JCC
ChsfpZFRE0uXhZZ+5qKZPtzS4XhIog7JG+0szTxdf+ToUZCDQC3m5OSMj4+D7GtKPfrs1auqqqrT
Hh6Z5yl14GepZUBqQkIn2HexSJiSnGxvb58XyhkhE3HqUJTToSjHnNNcALdAWC7Sl5Ap50yfj0Ds
/3X1wb79B9D+cvsfbnGX3b0jR3HDpWOztR7hFBchsj/ojRRSOIvcEYgZy+pyz6//EHTM8YcXWfft
Ge0R81KzLs+78dZ+DSWMnN24eHNQvBeg1VyOza2f7asXpWSlgf9sX71BfjxM1LC2GLGFqX8ADgKc
cdwg0SYPvS+cgOC2K7rLIu7o7ITCbWWrnRarXVuq63aJeqjLtNK5W4WDoTxetMJ9NuKnDUU0S4rV
h6SsOvMmpxcLadab+/PWv/jSns/xuRE+T3mzGcV+1+uLM9478a2izq9/MVak9+LgjE9OcsBA82bq
IxakWcF1ekM4ujIyl2T933hjloCKZtdoTlsaIhyhAO1UtCst+EtAbzewhakBRW5HRVqC/hZgsYAP
19PRsd2x42p4eEJy8iAQVNk+bXnBzL5ntlFFgDKAfvhy1zf3sFWlGZfdl0ie7kU2XBfaUUDpLVci
3ioQHX/bnUsKjyEViZvpgtieb7ZPU5DmtOD3UBvUQkBtsP+OQxscPjgPaSxRfJxCxGvJE/jKNEOZ
nU3kh9moyDSskbCR4ozHUs9gqzOHNrGbOXo4gZDL9Nq4EaGjoyMn93NubvDWrVsvXLhw8OBBb29q
W34g6IUO/iPW9QyF32o0L2uGYFjdhFspyKP3UUZkehjwnmrtYgZqvDqgiRlJwy3FCLfgqIbvG6K2
HkbdOcYp8+Cfn+CbuZAv27XwAB4OJxxbSjaTcTrHUfyOcyUQ8QDnTFObma+xmaPtMRm+uOSzYfb+
IiEViQNtx83bu6akpKS4uKO392JnyRXebuSR+yjgghiAQIGb6XPhfnSjZjQoEdsFY5b0Mo27Z0ns
QgG9pwU/kI0KdBF+xQw7NGXZOfhgT0IC77YMJPD6Nu5kw0AygrOaRhLpaB6XQ44iikUivphGxmkd
8f8jkiuX4H5HGJmKNaKNxNwFCH3C7AMmEAJm8jl9uqqsrKy4uLiyctHChReoja8DUeJ3LqLKPEFC
RVFMjI3AidGxllMdYeEcvy6PwxLFkIO92tV9MO8GqgKfaBNFIncI2TkEhExL12E9HDIYboYu8EvW
NHaVbkQgOrT8lJdP2+py6PalU0itkbwHPreOta0cWL2vaOM5+/ebIu5/ta9ftfTC6rnHVh74wWl/
inau4Paib5l7R+qey2PmCYt+uemtmuyc47OsueTOFZLN03pOf47GdYs9n/GPrp3Um/M0iZYp0Npp
l9fpor6k8AZNgb6rbb2VvMhxkG9T4Zfrcsvz6C/HTz1aNePSyqowG1qwK2qfEn57vbZ7yoC10t2n
c722uh96Rwqd/9Pdki1v0swO/eSh4bh39cMdBsfVn9zUCMw9qbeT3RVd7pL/bGUhtYLp+aZ5bA1i
/cHiTaHjqvsaF3olJ9GSwyPrzW5Zxt1KTn70cual21Ueq693BWsu6+mkCQM23r8x3EJq8vP/FJk+
x9boieZeduamw35XcbjP0OG/UUmOIty+w6gKCQmRyxGTiGKskC8eJqFoQsKDGJTbEfZG/+FniWSR
lVBk61nqAOzQnncoHDDVdFNUb5P1Tgv6h4Cm8429SpuViFgGSwmarmxRh6p4vs76L3ALhBEbkjlH
HpdJqY5ee/PGDaB6AF0vX7GC4JLLoInFIMN5S4PKgfxg/KLT1mRTJBB5Db4mAbcAJS3vU/Z5GhYU
eTXUSucpQK1UN1ibD7c4GDlhLhFT8ARc5mPz85mZmd8Xd+LECZ/2Ai6TRIwjES1Hgt+DxfE+JDr4
YrCsbl8xy87AG/lWF+eWweT+UkFmF477EPnTmekKPFByRRzWHwM3Y8jBPO/XV4ZbLIy0kHCxTAqp
szRCKBAA4QMEJNjS+7pHGcCWxuKxvY+xFcTBZaXpCptTkNpLcefppYSlJGILLSQBKLaW6KgmGxHw
E/HAHA9kRV2vKwrlCr+HfQ4UdkGqXj3cYuFEhL5EOojHoZFvapgCh1BeXq4+IXdjHz1ylX0fRTzW
hHp1Jqwa+Ehxsq1IAT2MoQurK8g/6LSfex20OrfvQF9VYGK76HEgJ7K90Qvg2aYZjBkR6k3oyoWQ
royesaEVbrlwmkFfsjQFy33tnJ2cknLo4EGQDMnJySOtuUxeBfl0NkrjTGgdyISPg7YyYLVBIiHo
rbWONtWvQ1cWsg9UX8sGbgMdJo6sTVNbnoK8shSLGW2Iwv0+3n8+Md7fu9GIArdiGBUgYTYANybk
c7y9vVVUVIAYrq6pobXlc7gcYq8S8dFwELTgykHb9xGuNLC9rChivS+usY2x58faZz0LfDmFgrf9
7WqRS0lXDqNmoQS8USryz9StiDG4CLfYSRhfsL13K+x4fD6LxXr44IGRsTFYOQ3sMCA9sLhgGq4q
t2sZKKXrVPxzfEgoY5jkiBLVFTKb/SvOg/4F2Hx/2+jz/lZ+oR6RlMOqCqs4D8xzT6P1Tms6uycW
P7H6EGj1kXMsjsGs3hiOtSXzS5B1A7n86NEj0ClAm9izZ09ISEi8FZYB8mMbh2gBOkWeYFnF9Qh5
Z3wDmncOyCggLvfkcqsgieSpdOOdjXc+o7M4BXnMETXoE/whXQA1vW1eZDR/PBKapCYgoEnq3Q5z
U7ilw1pmyZYOOlzCloj0jAyVhQunTZvW2tYWs/4Yjzecn4/G2hVwm8ECX/YqjTtaX/jG9K+L07Mr
EhYxOh3re5WcYvEGuqEdmfzeHg18gI3Y9VxfXEmeTsFapNNQULs/t7RN77tfngU5qZey5lvhlg47
BJZs6aDfARWuquc6NDy8buXK50+ezFu6tBBYuGwydkmwMKO/NTT6pl1zDOpgy7jRyNfYs3ZElJjt
BWTraR0yKM6nRfTTXXTT3SO4YxdokbRwx9a1SICoOG9i8z/ZogkYwXA9Dffn1InRjnKHAwFrtSVu
2vU6doHD3w4dOJBAIBCePOkYHPz25cuFQcEVbyS2rohZTin2fphll2mCmmM1HtJ10w4kfhGb3pTp
jD/GLlh4VKjf0UHlTRyifLs4/KyZTQF68dzrsH7c6CFSVpQpSnhiQtjJQcLOqNZmCxwCGIqUNAxj
A/W/rrD90dt7na7uQhWVpUuWLF68+NZSFFbcRqm1K1qFD3pWNPCw72XifFtXUoGQW12B5hBFRzn9
3mDzkzXwvyCxbYFC4DHQLYSwC2S+vQdry0i0UpYpKtKKEdIYR2pCCUUszvcjnkUQG8m4bUqAAzGZ
CXFvTfRax5O1j3oHBl6lpp7x9na2t/fv6HifiCRqYoXPuNW2+W16rGwbaE19caRsG3EIXUhqV0Ml
ry8wbRa5uNfXfywlhKZhXMTjLWMteLm5Rcpo4dXQ3i2va0lPbxXEB9JqQGsSC8WkPw8UAtq2LYYD
AnuoKxkQ0EgropB6rgVmOJGgv/8UBoNxdm65c+dOIZ+NCuIP9MciC01tuJphnm+Z27782pRBCyvi
95IyaDggV9r9e5+1tMesasFPR4Y0AD/8zZZ8slW0JGA8S8DTAeLm4VmcJk5Q25qPHsGKav8E4v9u
+yw4ILAzZcnGYSIO+VMTyiktbMxytBrLiRy7SztJ5hYA3XfN1GYbEuNeyLzC4OnMzUdnooU5TG72
Cl/sPqLQnFfpzSnUY5IKjtE7qFc4KJSIF8isp5kHFi3Eh6L9RMJLoWhgzP04NTQQDmC08FB/3TQb
6q+K2/eYwcGAPc+VLB6gvmti9Owem204+y0zKWm1oqKilxcFiofC3PYw5sBHKv6uL+aWuaiRWZxy
w8E3BjUeQmHS+GgsLYT+TDhY8WQL4TGnYIeVKOBzrZ03EhMXwjxfmdC0ODZ+0De473yHZ8MVTks8
DscV6v15CHqMaLsMDgjsaa5E8QgBjJscgVasK1K0FliwymKrTFGvQwVnRW16npR2PjLMs0iYy4xX
U1FrJ2DGWEAvRNIwP1jw13eOxzKYtBjrcehv0EGLC3j0QH49DQj6dy5cfSE7cZhExOM4zE9NZDwO
SBbaPxV6m/7eBzAwTCZxlssebomzDAwY+vqpoUFl/vzOwcHFKioNqOMl9AwKoZDr39EQ9coURcGH
4jF9GDLLrqJdEMQWkm7aEQOsxe3nh90/X8t+a0v+4hJE7G+PaVAisl3EC7HjWbV1avF8tGocJrvr
fZMzQCLgR/15BHpQsDMFDgjsWa5kFwWYNHKtHVGtjW8f3Ilp5nLu+mK/jffwbyWS+8hCe/+RYx8T
HGUUXFXwmOzBziZgpkYwdPcPw6SsGJtMV27OuKip2xfbKhRAZ7wamrg4LL8GMIojoBiwBWuROGse
j19KIKKgGdg/n6+f++AAxyAmsEQumUflc2gxemhN65ALIgG3NtY0OytLW1tHZ+VKEyOTsy2FlL7I
7GyU2IbHqygJRecRcPEhVGZRDEoTI8QMlBIArQOhktsl4PN2IwH2dNYA55AS0eSYaB5mbC8oFa5X
O3BfvX2JZNTvQ47v53P3ft0LN1k0gWNzQwndNo0M5LWjjcCit5Ginm1DwAmGQSkAt9LK7gklZ9mV
U9pNXXlvRttj3Ak4V/E4/2ssPkUTG4fj1IBeu6+Iy+2n4qNQYqxISGuPISu4io4w+1uuK6BNrUUB
Y7VRKSAwYjZFCGoGKxSyKWQaUfzTTxMdTH7irL0R7QuHCY7fJbxfAxiFhEdB9yxA7YBQIc39Pao+
e8ZZFxpnsRas2mdxbry/3pSGxogxFCZhBQF7JoxxtrSeZgsqhzdMisDjSIXi3IGq7NxA4m+FTM/u
bpotWmw2NlgBYOUTsD/mjB1n1Nq14HG4sWESDSeeGL/fg0TjWo1DRXBoYIlewjGU+Vzo0tP+EfRX
hyCZmSqqqqtWBSxcuWreav1VWz68mRZ9VnQGZ+NSeomj+8n7rdfcCsoSv9XbmfKp09ote2OYCQ9K
ZmmiSmW8iy/oxzi5ajycczJ97rXWPOy9yFDMieVuXY3VPSnMTwbhtypbhkUtq4oRjYSDMnAY/pnj
vz/n+OMzM38+6Jj4kI3W9/caWobASe3wPO116oIWgLr59IXz+z39t/iePefrA31dyEzrL+9/Tf54
Z/z7/hhJ1B5PuHmcOHnc053S0dPV19nbrTZvobLqfJUFMbfv3bn/a/Rdx/0HZYG/XqIgC3d/wMRU
akxG0mEy/ismibzl/4ZJNRoCBY0M1ENkV8FBMvtvQzL5P4b0PUzTIEgZsgZwkMz/25BMJw0JNIl/
weQerQAgLdKSEcBAMtX/b0Mym+oomW6QGtIGaSD9467sn4MwiXQH4hjiqVgkFnMEogGOoIHOKx4c
f9zKvPyF/ssXenInq3WM38ni1wxzX3WyAkk0j8qhS/X09B5O1dD42252AIm2pWDAMpdyuJR65cvo
U/JYUsfYzUbGudqRIBLtOZnVxxECFjsRswduDG5qIPWeGEoXZvO/hlkiZfzvYe5R+0ucocRVpcoi
4BAZSo3IQCpEf3zb5Q9EEg07/3+JCwFSOSdDhwNk9F8O0R/fbJtkiP6lEiEGUAuXnQ+HyPhvXIhC
kWiUJ/xE46Z1s0M+0hxLqWdqhtN72DSusHaEG982drB0cENW377igYgGeil1vKCfE/ZpdH1mn3JK
l+G7vv3vB7GfRp+0j91tZjqWUTfn9/v8NpLVw2HwRaDEQSGGr9jhB7cn0osXKaNsMMkon+z8f+St
qoIMCw6R9NJl6qIMfo0LRc0M/usuFuiUO4oGztSM5FA4IPS/DXOjvzG2FPQvI/TYFvbfbGKAuOdR
OMEfaave9k5P7AD/tC0cCPk4+pw8drWBvrd40CyH4lw+9LyDNQj+UhEU5ZMrbK/C7YnU2sd0Ulti
KFGUp73fNAuBQMi8EaNifl5Y1dhoshNx586ZfGDoyIoLHeBwSC94pMxWw0ll6//SZVUPyXBhEJlJ
r3emNFt5IFuZfNBX3CuHtxYOeFaNJLSPkVn8cur4tQb61oKBFW96978fuFxPf9vDBj+gdelm9iFe
diwn9OwrHgS6ASTy9Ua6cxnVOJtysIQa2cj4OMoTTGSrIWu7D9yeSC2YoNtC0kT5XwyVRMecUJS3
y+7RTT0z9Nvq5UNLHru0WhWECWQvbS5Z/hSanCpjZeBu45pJLXWkAvPvtSfZBWQuo/faAh32UHOG
0mz2SFtoR3G4ThReIOSrQW69UqUBDor0GkfK8jOeVPlJTxZm0oucKS0/tkD0icYDvLAxfwBwvcuH
IUI3e3BcUEblelQOz0nu1Ezr2lzQf6l+tHJoPJfCQX8YmvOqUy6xA5CITV7/xTpaejf7QQtzY37/
yje9gG4et45R/yALSuy2o3B7IrVMMtaXLsp/NcqGEu0IiPJmmd9A9SX9U+0J/lF882bIrIPDIrW8
mWTxSaTKv+X4uZ86lZSVlTVn9rRp0840p/eSiTgIxu19in1wMKTXNFKai38x+v9tc2Em/TBmSj0x
ky8EAtu9ckgttcskmwJo7PMo7yuDDzgPyDBAb5ppPfYl1MQOViOdB8TY4tdd4DfBDzKt58D7QSDX
i/o5wSSaFqFHN7P3eMXQux72uBCqaFB3US+3bofbE6nFjbFUe2Ji8tfRB5QiktddkuyeM1DhndM0
VdKD7rnMzkC8hEFhLrWg2SBV9/gPS47Hojo6ONzNzDSSU9Y3NSWne9aAYMiAaDx8MesyHA7ppzZS
lpz5/3nJ3YmWg0rOQ2YIDpD0I5fJBQb67qEkJeeEeAHcr7iJzr/8hb78TQ8ouT3Fg4DMhrnCpE6W
dW4/qCtAafqZfcDxkmjcuLYx4IRlJ+oN/D749+CPox+o47FtzLUZvYAUzXMogBFbmQLhRL35GGzU
htsQqdWMsXQRNv3rxMZQcpkpA/Gc7G+g3ipd1vtAJ1zzxhD5cBik1i+T5DeJMISIBMH+/gaWlpZy
yjNmzbLA8IygjnHGTWE3HAbpxzJSxmHDf1xp30vtROe/19p0UGnKqTJw73XMpZ+pTK7SJLxHyKGJ
qUgcpZ37lMhSr2EomFjiSUVMbjcNx3cVjVqOPjreLKeljGauFn2NZdJww0GiNm/y7r5epY6u4xFo
uelNKF5fHkebyojwp8ZfRgYXDg9w8DixzLRFCJ+dqEC4nZBat5hIGdp/mS5JfDS2XX7CyCX99PPd
6Tv8/ZijjPCc715uo/zdpEVQuiLtZM7DYZJeukiJyfD/KF09OlX/kbDyIF3n28jcgQMk/VBlSj0Q
0GLJXSyjbAro+KC/4z7TKBxh9TDvaBn1Owcovurc/36weGAccIBzGVUusfO7Fpue2LG1YADouOJB
jnM5dUZSJ/ixyOm/18wY4f3ugbS7N7X8+54Y60utYqRN3L+OICAlJ1mQ5WVVD692A2GeZu/idsDn
jb7p1arSmgrSesThNatX6sqeuHr9mhyoyNUWMm/ggE39YZREJj5klGVHjY6ycI5/ux5X/Gb25a2H
Udct2SeZd33v+oYZtIkeY8q3QDcqbefbuiJDhN3cbBRzBPuulf54ge76PN6BsU+mEWhxEIPBuqFu
eGPiDcKXhgZnZ2ekTdiMeW6IBafMb8Pth/SqaHL7Ifmdbw5RfBglSE7v/KE0XSHdG+kZHxJKrSdE
IrHbkBi5hTLL7/cqLQkgfh0dbynnEO/sKzh+jD5veV2BINz6iKCVjz6a2E5Pk73mfSbEya9TyPTF
iYR8JbAT0/Zv0oXbCanlkLQp/9fhjomkfU1W9qTq4cMm89yg1tZ9sruzV24mU/GNv+KsmT8/WD77
6YkuXeU7d+7Yf+6yMtBadtR8A6SXLISyMPfNjPWnft4jmWJiC+1aoqMWx8YbrAstRmy/462pjQ/K
4PRymgNtYn1C6wqWrFydM3i8v7NJwRWDYwtJgnx0aoCN19G5h5YECmrfmqLwRUHG7h9mL1iwQFVV
9dChhvv379tGaULkvARjDnP3xlhfet01JTKFx/dtyop66q25QTe0mDh4fOitqVq7OI9Bd/za2bSn
RlP/p1+5bMpuGq6QR3ccrDItWIs0KC5bF2CFpndQs6KIu+swt10m3tw/zIqqJhGhpxLk716v7Ks1
bBOQWrBJm/p/nXhB/7fk3d4kQN+tu6Ono6MDWL7pM5l0xXMzZswKf1Cy/AbI/e+pbxCWrrXMPBjK
fGuObA4cxqk/FpOowEOg51Y37b7F4r9nvj1odHEhof0NUdxA4hFaWF1R17L9t0N7S5/8TGAXCkSj
NbTT2TaxZ3B1MqpqQKsOlMXW07A2GLp/9b0f5OXldXV1f/zxx7179yohbaBLGTqe5u/htkN6FTcV
yR/CHrYTvuC4fH++UMhI4IgcI1yFZmKR18f3jntqkIjp4ZXnqBnq2TZo4XhK/5BlnYrSsksbPQqG
uY8t8b4YXltI77Oxb7YbWf5UTe24oPMD3QSyWAS1gVhrqy64nZBa/m2Y3OGgZFdueAJuRn6+pYaG
hpzyfgeHmqqqV0lJq7fIlpeXO7zcE8xlaEMa/WKiMswzGuMNUsu3qbDF3966R4SHy8gpu7m7xxqd
/hyhhIQuejo0K8A86zfeILVSM5hcXCT7ck3eecqtmBg1QDMAh4dHD4XS9PHjm+zsqOvXk1NSWt4c
L81IJImA1KCRiUDEoHPOvW9qUkuanTb91ObDhxt/VlCCMMunLIE53zXe8DdVYwwK+VIoes87ay9X
9k8yN3IcbW7YMHhlschYfNj5VuYdzPQdt083y1Hj9BqteexBPp4biNLwDa2b5rAkqL8BkDMKw00P
4/o7ODiAFrVsWcK9e/dCOSNQVa4LMD8EtxPSH7VNsj9JxEkhjOFAoLRn12gi5tenK4yEol35Y/x+
KrJaI14/fHr4Du/6jGglYrtQ9iD30UXuFvkHOSP3vahIXChj2G6AyylYu6mrIEVzOzL0PKubgBKL
IKty9ovVCrgtkFqrTbIxSXYQleffe/3WrbkrVqyYKOTuCkRra+uBAwcCae3QTOidkcIgHBipxdZU
dKRHBsHX09MNQIfdv/9r5ul6ApoIVefOzwrX4DBILZMmyxQS5SSPx/L283v7/PlKubnFJSXLtbU9
fXzi4+Iw/R8TkCgs9NJB7pQiAw6Q1JpoSmiiIDjjxQttOeV5qqojIyMiAdcQorpDCQpBcBim+iRN
spZpMToYwRHFLFmrCYQMYiuQ7V+HQ95yqzjuvtitSExpvvKatHT6aU6WnV6RsFk0FlsTH5Nak3C9
NtAKzepvySbjbmlaD1KpNR8+fCgudjtxIv1k7SPcdyHTWGn2Am4npnqOZS7he3OxeCAQddEE5X6E
jbh6JAZ1FSXqq40i1jravNHDIeZPW353mBRF5Pqx2+xi4/QexKAuR7aMhMl8wVKZtI6fCeaHfyoL
drTeg+KyO5tQOLEYOlfdQ7UJh9kDA+lP3yZXopK9C3LK9X9RUGAl5/fkyZOOgbuJ0FH3T2byjnAI
pJY9U3N+yKTYbdoUDiSonPKbrCzrYEYPESeGmuU90Sw4T2kgtZSBnr1NAoexRHM2iwv9twkEPSUl
JTlXLS2t2/fuXRj4/AIU1t6HBtsOHVI5etjW1qv8ugr4HYjNNGLmw3xazthAenUyyVKT7FLTKMvu
fXPg0xTkBtB0Nq3RiB9z4QcJ62l5u2mejTbhM/wJYYsCh2qzooh6heKHFwTryMkR8/zKWXaP1uOC
+FQyUKdr1qy5fOWK+qJFZeXlirNmuRaGTJ/nhmAmmMEc2RsbTPU4yVyiIPOYNFxTlp1uDXKi+QpS
NPcRWdxPTai0ULT+OqjlPL26goAWCyz5dV7th5Q6L4E/uhIfxGRTyFsI2B99sdWzD+sV9R2o741C
YkVCsRgFMZCqm40M3CZILW0m23MkOuVJJhDUVFQ8teZeCAwkhnLmahUj3CnyMF99NTaY6ktCko0E
WYPRoFInDPCOHTtyLlJVoSCc2qNwEg6D1FLGQKpHaP9hu+EBI5h2LN/AwMDI2Li5uVn9nNz06VfU
DU8WYPjvUlNv4PHIo9Xl5b3F4XIQJzy2mAcLbso1zgaJwHE55Keh6LFsG4jZL5k5Wt2wZPdVV6A1
kLiMVvqS9T6ZrOauUHQ8jl9/cfhZCU9n3ia2itLPcwstxKKmbF/y/XXOLwkEEkLexMQkP2AYeo+n
hjStg9sB6bXN5FjRTLJTm3FWVG+dGrCDG2/T33lFFYmaGWP5449s9+hvEh2KetkuGBtrQTYV6h25
j7q89r4L8xRdSMDjxDXWwluB2gddLnbXH1IiYsRMJVCd+rstYC7iGBtKL2nMpsJ1CPmBR44sUlNT
A+7p4MEbN2/WliGOHj0aoYQUiYSWUKk+q1gA81VZY0OpFc5UtBsLv67LDx+qA0974sSPp0//MWA7
wlfYAYdBenUzuaCYSvjVXRa1JkYPbxPMGxrI0InCL7EOucB4XhUcHNze3v7o0SMrK6sbN27MTkKs
tj9yJEgwTu/vP7Vq1SqPVzk5Od5NaZC7OJyxpAkO8ZRLHonSMI8+EFhCN/0+MEZsCnGOX1cAPZBH
c73a6a8vXZdTeY4PCxXX0Ar1iiyHsTKOqZminSSWHVksAB3Hyd5eGSIYuZ+Tkk75+dH5HBp0TPJl
vWkw3BZMtdoxk/Cj/mJxTyz+4X2U2xH5zak1yAuuwrFeDrHyGeGo26WNHm96m4Hgc7QRrCnqm19v
cDlHOKIWSBSYM3gRjS8Tf9Nn7ctHu/JGqZzvV3Cnx1rR4MBLr3Kmog2F8HpeXbs2U1FRUU55lM22
CRj6aj37nFgk1EMXCfgcqK8ecdV8CAfob6l6nHLOJbx8uWpi+OFaFMbl0MhQRu79VcEfDoP0qmcq
2tC3DC+748ePh4WFbd682d/ff9euXaC42MMtUZrWeSfKr/f1nQwMDAR/Qv7g7V9/fXthwN7U1NRj
U0AAG7QoU992aGRl0bAY5m6ZseFUSyHJa7CLj2b9IYUOW+0xp7MbE9FUJM6wTbRkfVoWt7k1Hx2P
ETuEDvxcOWh7zq/CWo9D5MlMi1Rd9/nLFw+E3IIFd429GyHwsy1NF8GBn3IVJNkR5igrCnSSCRXU
2JeYjRK3M7vy+wchFdTnqWSRhg0TMgnkcEfQm0pUzr8OM2P1UZSIopPxIRWFymvqcruOt5UrbdwE
nd6qfTSHuVVtbDTVIkiyWfi33POJd+4oy62pJJFwXAZwi6gid8STDjIRB1Xt2XVaRDgwf9MRD5/j
u23ble9XxA0MLMLGR38f8TyQmXUdDseUiyCJbMkj8/MvQQtdsWLFgkUI9fT0dEW19dAHX0BQwI+S
h4a6+gYtmSfpXV1d8fGacnJyHn7m5rkPDb1EAu4CwBcaFxbBnUgZTbUAMpPsxJwx7MseCCxImRg0
b3KKxdfl83s/NZFfUNqZK66FIoMuDg6TrIH6GcLKqC1EM5MEJRFQieZdXGttHXfz5s3w8PC4OOs1
awbr4iwhAfDba5MIOPzSq5/JZa2pRJ13jQX/1vFmObMfCwSdVDwuXAH9Vtd2hhMtjM6rgL63uZOA
Kbn8/KtPU6QtWrwkiLXlYrfDyQchN/facQrGRUwaDuo6XZfMYb6fZGw05ZpHogQfHBpaqKbmtXH6
vn37tm3b9uLFC+0kLRQKV/fY3Le9QAa4aPtHynPg8Pw9Bz2ckWM7dsyYcJJXb9wowAotIOfl3aoA
82lW4798+XYqmo6JRGXolB/wOiFhGbCPnp43r179mneR+to5ez26qLW5+dWrV9dSN27ffrLk8kxt
bW17e/vKLnl5eeC3hBwaEsJ6nakK83rP2OjvKXa+CbsiSkdiIL6fV89QeB/hisdwmMU1tLTQ+V2p
azX7HmNDKUxaXQqyvMnqUmQsLahIVJUNuMTnW2ZVZeVVmdk9PT1Ozs44kWDmPDdEtPX/MHelYU1d
3VoEDAoKOCFFCai92EKZWsIowYoXtQparSgo0YJaRcEBZQhJ1EpRacUJqFqNbam0RY0EEARNQIwg
WFO1gIAQpiSQAJnn6Z4T9N7H3vPjHPM1T5/HP+YX7177vPtde6/1LgyEn2rAJ+YWO/DqP0KEPFR7
c65R7Mg5O5k0wxZRry13ynE31u+5oWQSSSPJb6QV3Whx7L/niU7Bq3UNFDqwRAfnO58jikcvo43K
YOKuYKirkQCzyxxYev7UyZN9gGaPsN6zZ8/IywkLFiTu3s1ryLUHkWx8Zg1VZx1g7ksef1jBw8tv
FBTMAmsX7Hz9/Frb2mgZoonAmR//JSoaCgVyhWPa1T68ATs12Spqbi7KmPSCL1hpaeClzrRpba2t
7MHByMJDhw5tuZ91aPPmuZ6entTq8+df9NzHg8EKWTvNBgqm2aUNTDdFgaEinvxFYPj28fvl8BvV
Qv0f+WDh+9qu4w5FcZpf+Z2NeQISYy6hwWpGUoLebaSJzycTSUrhj+Xl6yIAbrWTymROPgl2ANEM
5AU8gUJv9msdWHs1yyChjBXuNLJsixiV7ErAi3SUzm88VrWg6xh5TJpGz8UpKmNeeaIfWB/9VSbO
9aEb5Js1iyrUjpvX7Go4n0ghhWnVKGB3//lDGAoKuLnlDbyHK+rt21u3bdvm9t5fwOeZrZoOAPBH
W0F4ygcE/DuvcMq+zBm/wnFw2Fi9r6/IBwcmUdEGFITjdsBbxsLmoBh4phJq+Wh8YuLPx45NtNwf
ERFxrbLykEY+6urq+tXnjo6OTt6bjfO6vrVTQ0Eyu2yBB0mswTFUCu3rTInKv7rqvkw1QKHLisKF
7if5ezPvSOvbR2PoHSNZFk5Wu71CDWB+EJjyanl09I6kpKQJlsnJ/Hmhh8Ebmjp8QAQUdLOLFlip
/akQMdjcGNQcrBtTsEjuuQnlxiQpQy9SgOMSVlIID48XB0mF/HSsYYwo2nK4e0a125olAllMnoAA
ZhQvMUG/QeDFmFuwwKu3+XzDhh1u7wEn/B/f+w0MNOaDae3CMmsIJ74AzL/yNWr3rl1nz59PjJh4
6dIl4LvTaBRGz4Fla1HnoTCYu9YG3nSymrThz7Oz74E1Q+4T1s9wccHLRzrYLUUuzs7un5VRqYUX
LoTh1XYAv7N6p0GVsWPMrkvgJazi0Zh+UeCTFlffujNt13cCn0imUBbDe1z1BFD98lrcSJYoUd/N
bHa5WmddEBh+5YBEQjcY7F3Dhni85gmWEfKTMzzAI+Ey4ZNGKNhmv2mBxZ+7a7RnQRKhdqr6uSzS
zdhwKiXDBrxSGuoswZFJho875N9uD/60rI1Tkk/TE4WyfPX1klXL+/0ae5LIRFtAgbEVQSugAJtd
iMBikXOFhQCL2NjYgAY1XCYZZJH53dZQpcHIPZDNwSJqvQ4PJAFoNNpyulAsrskQzQdZZH8gCg+F
AbkSMY1F4HVAgp7qZYmNYrG4orISLKG5bREeHn7woOTUqVPrSqIJOnXlzZurExJcNx0tLh688ME6
GskwDdhryybPgnrERW6DbGzXhg8TE/g3roSl9t/0eWIc/nha/9i6uDozQ6W0trKyyjm+7FdUJJi8
YeImDUIBMrvkgMUWcWkGzwYqat/CcvmzLjKpDat+VNbvvvlMpurrqTE0nVrjwxtKTtpPK7CPuacT
yRS48nnMTYUL7Mp6VK8ymbbgrSwvPxCqYQu5RbKplySwPraVy5efWDgtMjIyaedO1r1MiYBFBwlj
VsdsqI8NuSmyOYy51NLhdcnJyWlpaQvtACSrLvqzVRIuCIOxaBqEpWwAch9jE8vu4J3Qr2eczfbe
/D2ZLOBydwKgrCYVFhampKSsXbtWJpO5YPZkqAeHWXQSSa+9u7X+mFKpXD7nxIkTTS0toVnSodcv
Xw0nPaAST+Rmx4hJ5G823YiaxSFJZFIkA0SE2TIJwmEt4B3cjk18WoZFi506cegLMcqu5dqJRMbX
n6GJCRmGPFLrgmo3h9U1ouFGMqnViXWQkm3jlJQg3yproETsZ1lSItvDpm+a+umxUrTzHsIOqi4Y
PPVk0iA/KOBmr96FdeVak31x477h5790VaWSDPp5gEb+77Mf5kH9/eZWHn6wPkAZv727Nt1nwdHP
irwX49UjwAcJ0sjyMKdjUCAQSw8/04T+J/AcWNwn9Bg0Gs3gwGBTU1NVVdWNGzdKS0upVCqdTm9t
bRUKhTod6PL+YO57UD3nyG2HzRIbCZd5vjHG2xibbhpBA/wfjM2Kv5ySoEAg749GynVvO8HBM3CF
5rpf7axyjP21LyBfJd7BbdgcZcQhujEP/qnc8Qc1KgqPyyapBih/dXqs8l3i9jtNqAcE1LoUAic+
Z41d5LoUolqtYTXn4mpvESb+NJZMDqEQf8iWSC5cJoMy0b8rrAQKOvKik0BE2DFBb9u9wbX0cZvu
O9HiWONDOysv0JIqoq7+MWPqT2A0j16YUHTtzG2bgqPjhlRpWhRUGQpyg2ETgwovb6mR9jk1GoNa
90xewqLpVD61Y5NnnNuq70hn6bXx6l5Pw4czGUAaTVTpBAoWCevnYGxweBQBMUU9ALn3MOL4vW0T
h4HpJRZpvcrtyIOjk30/XppzZKGtp0toKMrDKdDex0EosrU59pX7Nse1bu//l7f7B+9/tDTA7SNP
Dw8PCjiC8vOdtlAHMnJLYn9EJsv/L5wBsIDWCP8vnE+5LKJe9yacF6twBm28ZsgFDOfUovBsvQ4s
O+VUen0CBe8d9AbCOL7tCYeBSafjcVwye4Ktn79/+W1qWfnBfUZjOJEIiOMUiw/CgUD6ub0/HsjF
bp4ePj6Ua6C1VFyIbQwUUsTKxMRAwrOVCVFzUHxx7pt3tSicQSnWkJ/UjJPtPSPZtrhms3Eg2X5U
hH0dTnagVzAUSMTKJQjZ8Kugd3PDc7P09fcDokillgFhtNiV4poQTnT7yG3RQrviSON1wrQbFmgo
QIg1i4nJNbzE1GAwVKWyNm/Z4lx35OzZZ93dOiYZC6qWwsQpUPk1cjNhU1kEXiOwQekCnPB2vg+r
eH3dPnQ0QbOAxnG0PJehqMzH6rWXs/gfr7GgKotdyDS9HgV8XCyeVwgEPuQ2w2Z5Y4tTKC8PG8f2
RjgAiqbVKfyeXlTC7/S4WJnf2/9pKfpQgk7J4dI789AZseHH80pTs0O4T4sYCtpXe7KmOK3vUKbx
bjJJBh3Y411pG7oNCjpiJWNiwgbbsS7XHm1nZzen7sjJk79VVMwEWOPwdlQDFATk1yYmUiOsaxNe
regkeMP/OUsqlQjojSxt7xaZjXdTxUj9KRSOpNPFHhQtVjTn7tvPYbuJ0CSjG0FHjBdUazByd2FT
Nyi8vFraV2QAnaRcfY84vhCjHnv09KilyaqvKd/Ek/3qHm4qxD4Jkcnri7Dlguy1HUIrb+8K3jYJ
Oz+UTErvkUx3r1avZecogBMftJp+5hwKdceM3JXYROMW+JdiXVUMBgPg0CtXCDJeK0igqVtQUBdC
yF2JzbJFV4arCsEtKg4V8tpZpM/GSH0bRQ7eTbW8vuF0rEGrcdo/GECt7uVFAbtXqVMYyyv/zPSC
ymzfwafYxC0KLz+X8nGMHMX85PE6BVdNgitRNvBXF5mGSqi3Ptq0V9Bi6UMaIYq69ytsq90ADePs
wXIlSRboBuM5bJv6oZ9TxwgqS+Ds0GwKLYPCjVizmGV7SrjMR6svb9q4cU5dxBdfyPoacsHtuYNq
8wEUBsQyBRwObcr2hNeAKeVTRHKwaKtubVdBPkmv8ww1XD3EWFp9Td+2k0LUEhQSyrM7XK8Wx1Pf
3QnHS0eZLJLRmrGQ40OAwmn2lh9Ye7RTOHhZddp4zp9RXy+RjGUTRQOpADHOL0XXMwowYVeyJS9u
MumSaPpAnMrBe6zSwNbHYq/3qG/c1k/e/GdKe948Jh00v5ofEwxRSINBbkBslkNeNBC1YsVkyzm+
fn6//PKLbnxa0JZdNmlQEJAb2JnIoPCa8zRiFOv38QJmaWdUCUuvVfLJ3becnoB1hQej6Ro5l9VW
wnrYHvZl3DcOMeEiTgPF+JQlK/DaA4XT3KZ1MBtj9LqYnovpx0rHTUDmerruIBPTBS2C1TG0+LGM
aY5W89tm2f+cf/+usq+9H49Lqwr7Oi95T1aIRM5toBCV8zKsndZvNBQP8BoF40pnyqEwCKcbDHLj
YHOd9j9H5YNO0HURcXFZBr0OjOFhjg0DCgPySxcT6RReW6VMgeMMpxvpdKivHavXdynEtU3GzsKe
L+zTwwBUTPrgjNSgDWHHPXck6LfKrzAj9oOPxzdyfCBKijBmN/2FJ0s7tdLa1qfjfArwqguahFfK
YnqG07NLXR8wKjHYK3hFC0OBPX+azt5oMQvlfy763mKFPhbIGv35rkusNsWGfRskVqsbcWCQ/XKD
X0FhR653/JHdVbzrXLk3I136jUNdUM/HBxHErV81F6BXR1eL7VBoEKsYs5iiZMkGYlpz7J8nGz2Y
IrWl6AIyyTDEF1Tm0y7tJYG0c3qWfWI+/a5Q3/6gdpx2+KmEO0M9RYmpRCvXbAZ17odf3RvtAFIu
IKcEHcsX2C5eBrUC5p5qCdPvTcBqKfLR6XTOc+bMcXZms9lVe7smATAInpMh5tBgkBvwmlhDAFPK
6QSkUYY9yD1nWUdj0URdrU5V1cYpWdXi2B/g1GNQaijiB/hbBfZnWz3mkSR97SwgXKCkWZbv1wuB
E7kpr6mWpvCMT/Scnb31sa8dNCJ3hF4FDj9ZDxdsIM2jZFoBG7byuxiPHmWaqIGi/VhgFbuUcTc2
fFWYnvOqFlc+lt3WKZ05f1GN2nGNQIMzdjetmxfSBLUA//RIqaC/jU/8R/nH7F69MK301XqjWe/U
O0YrghPVG8JXBek5zbm4XJxB2GE4lciwPBEkEeem4HFjeBVBkSfwxidQvXJPJe/J9h9+xM1DEwuv
4n1oHMc1x3d1WNZ2M9NpSr3AYGyUjeGHQzxqYJC79ZqFiTQKwWhX1ZUrV8aZaNbMmXIBCyTUjAM2
EH6oGOSOuyYyEbyG9iyDJPXRb+Mq6OHZQNC6RqgvarsOMNGPx155og9v1ijHuKzigdSXsaAMwomu
DY3UxtBB4zo0sIGD+/wgP0ezzz+ApfnA6mrRXcU54/yDCZEr+eQKnC5D0ULJTKfPSSFMAvjox9b8
A9H0xZoxbkU8uQKDzbGhepF6aQIwxYym6RwPKwMUzbkRS54F5B9g3sNLZfbgLRD+XigJahn+6Qng
QW8PP4DX4/3WoDuOcZ7RhOfGaZ8Rcat+sASiOgNtAdEfjUHu6WtqVGE9DISo5DtHygL7X0f1UReZ
eVeiam7EfVeEXXSTNBGIasF3MfG3soFjJarhF/uVLtf655eit/+QhR9uoHwUQ7s7Sqi/L3ZfsyZZ
8mJFIJauUYGp9+7WUAiXGAxyU2ATH7Hg9TMCygj4V+SDu1Vc/LCuru7RIw6bfUjCWQ1SKyXKFsJq
FIPc1dfUzAxWaVSImlPScXrc+a75m5IXKQS1TGD4toucswF7PO/yXhKxl62wFZCyxkiPa+a63ypn
d3RGga/m4JvWxTwfDARU5Oa9pip6WFDVEoFBFIhdF32vIF5xYluHJYdtfzOdtnGfwnbN7d4R/Kbb
blbDezLbCKMDR2OxK5n3z+MMVvN/rdav6FApuD26V1JlqeBorLbUFWCprWUDqp80OKxeDS4ESYe1
gloIxELJLNsXnMkkYMVSEvbu2PEI2L7NzbzRUYJSuA3cvuUzbCG8bjDvYANs4pHqD5OOihT17eOW
RddLZlBIapGCddWJVRmI3X7sZPxIRpm8r/1jAZExF99Q0++++b6+bWe5IFuv52IdwP6/qG7/S1Bw
zT62AJ5nv7Qvtr4j/RSf7OuFr6vQHmWc5koExGAhL6rttyoqP+KYQ3GlapeiNQaPy2aGSqIPdy84
ce35Nx6tTiyWVgu6OfRocPtvZjTVaH/svuWU7ErQiDXGlrS0zDCI92kMcmdgc21hJhkbuLczKSkJ
ZOAHD/p5vKyRl8aZWeVDtg+goCB/CTONgeEZ39Qo2Okv+/53FEXcZXL0fZmKSTcAlJPWrTk32Wta
5PUucmqGdlSrwTlG9dz2JjVNmNHeJd6j72ZiDXrwif0p2heiCASD3BHY1G0Mb/aKaDi9NUdx6fJV
gEnBbSx7ym0ZIwVr1VE9F9OnGHf3hCU1l8mra1SZghZBxP5l31d3PipZXYQFJHLywEDqVU2CmJLV
dLf/R01PbPzVbI1aY3whPN0WVgm1DsjFlD8ybfj2MrzrEOTBPo4jOOpygMOZXdQLBnZ6mcURKEDm
HvsEd/6beJR53IV843A4d4vqzCHV0sbFPoU9hgNKWX6zRBAQuHj7Jv2Rbc42zqmE8FE5dymFuH5L
BsV6RixLWaES57qQiQKiaDGvKbmjMr96Q5j0peLAwHkBmqQDTdwfJS2mQK0F8qc1hML/bz0csIQy
1IRrjqNxiulg39nXg3dnz7F4CYEIuVWwydGFP+JaqNbf6Jevf8Cfd7PfqqQPU8U9+1LcwFOeeSkO
vTtk+xs4tHTi9V7fSs63baKHfOWFDvHiu0NTjb97lLGP/yXqkWr+FKoP/jHmWc6x/73/09rhYpaU
rwQL8C3twh9DLQjyGyeEIQ7+D4V49vig2pmzC9+EuM5iFArRv3mKuVZveDKmTnsKBIhtXdL7fhn7
8NMx2rCipFe28SEffWtwfF7tQuB3pvABT3GzXx7/kO9GAX9fVMYmPRe2itS9Ms33XZKo+8Nzb/Z/
cgfcJH0yLRDiJT9g+6AWBLniQhbiYN//aIh7Z88uvHCuEPRU+B/ezjyqqWtr4IhzHcCBClWJQy1S
i0kIJIBKqlZttRURLQpCtNSHSjXvE2VISFLBQrUoVkVUhLT1KQoCoijIFBCBKgoiyBRIZAgBQkhC
hpvp5r4b7NOW3NUkftb/CGvttc4++7eHc+/d+7y/ZRTC3bv4Nxgz/O5M3ANoz7VK1xT3fZDZPTOj
c1NZ/5UX8oJegFYnhj36pRfb3OjcUt5/o0Ne2qc88kzsnt87Nb1jblZ30O/C4j6AD4Cwd5MfD6Lv
9MCOTK0T14tVKlAHm/jjlk9zkTbE/AdVZhVgePcRF6SbtB2IJn552/T0adMSz/2cqP9CzG6ypRWS
Su/60yNz7pxWaKFygTLsqXhVUd+C7G44Ikc+FcGx+3TzkF+FAP45Jb1jTNoL3J2eo/XifD7wK0e2
6/cB2JyzMztXFfUmtkqfilTtMu1lrty/QkAs6N1VNZDWIW+WqFWg/s7pZbM/Q3qgbv4wY3PN7PwW
zNzzJzvDoTrxjK9+Eo5tkeUcJJXe9SQcc8wsUYNVQlVsg3gDq9/xFs8tvze8VnSVK4P9m1Q1gM7V
m3laRsfqol44IcNmZrbLdlYNOOX2LLzJ21ou+IUja5VquDJtSpv063LByqLePQ+FGR1yOEtrhq8W
J8Wu+RBpT8wvu8w0M+5teXOHzUsz9yTCdtZX1bbXLBFmyODNn078Ds0MgLpakerYc8nG0n7Yd2Fj
wxVXdqc8sUVvZtxd/vSMzg8yO/0eCOCIXTGgTG2XBVQMYO/0LM3tCakevMsDuhUa2KhJbKlvueDL
0j7KU/EdHgD/Rz0ctNPT1/4HaU/ML73MNLPL2zLzn515k/7OXLvbls5IKr37N36mmxkOrU0Szalm
KZyS8Xk9XmX9J5qGMjoUSa3S4EfC5QV8+6xOx9u8/dWDN7sUlQOq3ziyb38XLr/Xu7KwN6ZBUjWg
7FeCcKUFB/O9j4SBlQNHG8R3+Yp2qUY5bGae+PP3kPbkHy+/RrzTffPya2TMnnXEEmGkAf4N5hw7
m6fRiPdBZp35gztHqvRiWCf9kWGG7yiEe87x5k8xNtdEhLdgIv70P9no/Z9fVk/v7x8lRtLon/6Q
yf0Npy+81GhnDyJ1eoVm9I16jqSQ+aWPmSZ6a+dUU73I/MrHrPBPwIw4lr2D8P8PFy4EzFs+hhhX
yfx5wzizRj4RMCNKblNb+/9eJWufLfq7wuz9LPchKWV+5WHWKycCZkSBaWKjtDE7Des0Z7zlFiSd
zC89zAoQBMyIaur/GyCmnz33R808C29piaTRu+4PM6eYAkFQJpNxudwnT57k5+efP3/+ZMKpgtIK
dlevFFDDBdGACmyQaO4LlHBp3Qdo4UoY1EFiNciRaX8fUGV1yYv7gEaJulOu7QXAGpH6Mld2qU3K
6gMEKv3jykfNmxEG8uJfTSL2h3X54sC3uyN2f/taEWdXV9hOL8uhKQGvhVyNC+ENhPDGhQgGQgTj
Qm4GQm7GhdwNhNyNCmExI4VezSL9GyGsgRDWuJCzgZCzcSGcgRDOuJCLgZBxIrAGROCNE4E1IAJv
nAisARF440RgDYjAGycCa0AE3jgRzgZEEIwT4WxABME4Ec4GRBCME+FsQATBOBHOBkQQjBPhbEAE
wTgRzgZEEIwT4WxAxKtJTn8jZEAEwTgRzgZEEIwTgTMgws04ETgDItyME4EzIMLNOBE4AyLcjBOB
MyDCzTgROAMi3IwTgTMgws04ETgDIl5NyPgbIQMi3IwTgTMgws04ES4GRLgbJ8LFgAh340S4GBDh
bpwIFwMi3I0T4WJAhLtxIlwMiHA3ToSLARHuxolwMSDiVf/x3wgZEOFunAgXAyLcjRPhOpIIAsY4
Ea4jiSBgjBPhOpIIAsY4Ea4jiSBgjBPhOpIIAsY4Ea4jiSD8pVfuf1W0aZ/eD5StnBSNmWnxQsew
/uF5zurF8w9LrSN+8rZbmTaEmRBm3fOg7utH1KVAL/mQWENZ0K7yOZERjKsRnmactrz1Abpgw6IH
v7X8iHfqOBBwjONBZn3YqrvWHnj/1+iqSbzZn12pbWJ7xH9Uvx1DesCeGxQfmnXWuXLegmknxsVA
0hk7LTb5+SG8jSH8pf/tf/qY2PgLiKBsFuQJqjU9fK4DVxeoEmuUyUx2Kt0f7BVcXEcK94Towq7s
cJauBFQBnCTuukCoWaxkP4oj5XmC9EGwNgPFmEuRB1UKa6ckeboE6DD8Gr6wlsWkaELrz5AzUHS2
dEhTns3QaTW1mPfWlu0cq+/lW4P2RfgOgPCX7rdXtsGapIuOz82sZfkS1X6hHbS2HIKjA+dQgCa/
Q9KU6VXypFBzRTUU1/oT6ipHmyvvy6tG0VeACo1QL6HzA3vZ3f6kq1zdLZWkqZrMCqQPUcprVjxx
cho7dqyNTaLPR14tBfvZKilfxGVBkq4qLouBi4/2xiwepf/O6l9CbxKSNm5IljGtTQuAIC4DYmhV
gKSJ60BicJUyTTcbNduelkzjS3P9mY2eaoqqPDuJC7WptNS+GHSAL/FuoCpfqWs6Q2bY08HQsmL0
2GDO2LlRNpHdh4UVVhsGGS0KGXtoPOkjjrKBCtbDf0F/WGXeOL1V4oO9C5H0cEeyimltO2qNiGfF
mtWmuUhVZ7I5SWGFgZ+haO3hYD1MF78d3BGmo92XECKDOV8Vy/VftzURdRSwq7YYzTjXBvlRdDRO
CwA2eQ7S1bzH1bXUjSmiPuGGjRtPHjt2/dq1bTnfVByb4TDYXgjxqpMYkA772ihgxsaJCMr8pV/t
lVFM7AGEIAGKkbcCCgwbTIGVKfBPtTtASz2kFd5gM5uWqz36KtMedJGLFKwvPST/gl2iiqONGhLW
FjIZftlR8W5DH6mbkwdDUECJlt7Jke7OaOzm8SIjIiIiI583NOjnsavlAlJJ1C7bsZd3Wo/Wf71p
Y7V2KZIWWCQtTHMUWIsEImQfpaJ1ChN4ViWNAVFMqno/+3lCXCAUAXaJLuQR+VzwdFRnpqYkaWIV
93GxlKdkM5cxGWSWuiyqKlT4xCtFUfS5h+SqSJ1WAbC+LFA5CrvZvZfJlCyGB6BrYkLzSl9jdeXZ
VyuQdHBG0sG0DmoJn/s8gRXcppvD0J7oU/BvhaD27qdfDFW3n9aQfFco/Rh9MVCZ7/vLUjVzIlz7
evi3RXQ4gvFbAFYGivbEU964q3ZDWnF2OpreLNWyJYLwq7Xnp9nY7N69m9fT09jQkBvSlDXeyl6r
A5N3zYyPLntPP3/TsW1tAZIiOCRFnE1SZIjPfZhHZGdFyVaI14fW+3ASrWyaiF/A+NQVozeIGE7L
IM7h2g3sAHRrFn25oocPx1sRXbVCU5MEb3d8HpHQIvntRZtmvxeLmQ/+u79h76hRo2JjY6dOnerk
5DR+6pwI1RAPjlZ2a8sW2z6wmFdq4Zq9ej+SEi5vrARF3iWqdOAerykJbZdu3gvOUPCsEgnLv1iu
C+s84XUvjes+QL9+V3K9PWvWV0nEQZqqqy+PmETU9hcrsMqnIcWZtSfyWIs9NPTyy+h1B9qYrtSw
Q4dyc3JykpP9qVSNDtTAPqEScYmx3pj3xmGH7+ihrwSRlEDI7abNVRgoy5loMX+yRSlqy9HcsKWn
bG6tHveF3Zqbz+aOmTR79k8zayQv2jmFjenpjlc2P7p0G0gNtQ863+Kedqfy8Y+2q8ScZXyLeZWf
f7bgVqM6lZ+XBXvuwrVLEV6KELCI6do0WCQA1BfOelTLIrB1O6KeLOzhWR39mijjQAdr2tEhKNqS
FQDnIFxLTPEK9WKxpZ2an0QMeLtxYGMwFJO9Bb88kQS5DPUmuyaUpDBk+3jpz+vq6vz8/FpbWxMT
E6tOzqWCajmLAdm+gmWZ0yrEIIqQp027ZdHjUO+mf//7ZkzM6j17eq9+lfzs2bM5c+fSoqLCBtsi
YVQHBw8QicSAgAA7Ozt7e/uwsDA8Hj9//nwbG5vZs5OzsvROidEH+W+Hg/yzR7OakNaHmHlNg3lI
DsDRnDa16HQAoG8Vjd1t5YL3zPSA6IJ6Mo7MmOqpXL8LnFFjY5UZ7smMkkrhGoKr0xYK+/K6Z5Dv
4Ik8P9WmcOntniXMmmJVWE/nlfT0j4OCgry9vUNCBNd90jyjlGLYIydf3jlz8jf6kaGYK8RYJCUQ
0q5p46RgmKdYfDrG4tMTjmenOy05X7GUcmPvj9yurqz0HydYtNEoj7/cisMtOG83bc1/CsNn1ahq
4PISUE1BaDojOCPlS6xp5aUK4B7LI0pri+pbtGeDKlbDW+nm63moGTyoEKLhIhNNhDg7BTh4KyN9
V8ABcF/XGTKZrisGVeH85wn4ZaQJWZTfCzp/7Ts5q57MuKfqB+/uZy9YuJDX3f3hokV5B9rVg+3L
hoMCQR8UKiJXkJE0QMiVria9CYDrY9K+fR/rbxoZvRr2Ex+fMxcvXiwpKUlJSTl79mxaGr/u8rrh
yHpV7ywi3WSkPOeMlOewpnWNQlIRXGqDViWnd0j1TVp1rgm/JZRwlN3s/nWkhQlF52BGyc/Lv4/J
1rczK+C0jWY5MCMybkkmSofGt2XY3xukFnd25GUkpNZedK2uqTkZF7fO2zvnl19etN0LJTJ03+pL
jafDpcZPdR6BSMtHyG4mzqoBBlNiYkYvWbJk9OjRM2b4hIaGUigFubm5339vYWWVcPz48bS0NCaT
mZW1dNaspOjo+9FjJ9EhHa3nsR0ajV67tjI6OtohgTns7i7D7n7w+vvrkZaIlLswpq1RIaztTmY6
hS/n+6lOwTtcttUqKKGYI9FqigpJlxRF3f7yTXvkl8Xl2UCxVtLNZvIAVoSQ6nhL7S3uaFpG0uZr
ZLyzD31kMtm2bdu2bN0qEAjI7QXyP9JV7AQ9mYvi8D8irRshXbmbFKU8QnviX94GDm+tg4MDvH+X
LrUNtNwebWn52Zo127dvv3D+/EwbG39//4S5y8L6Gxx9fOoVCkUCiphFYnEeP/5yx44iFgti55GH
49BKfRxiVdnlIa0SKWNhTQxEhVPWTLOw2PTDxMnzvCf+vAmTvPnXWSe8XGTTu5pXBVlEhhR1puIq
S21HW1ivamz1C3FcxG+jcqnZdzavx67NdD361LarmJzpznfjn31GFVFFly6f/SZ+4vxVE45aO/Iu
zYjyhIQOpRbWjMUIV2ASnJFOk1iTPP/Vwr0/frCUMmiB995WZT39g5TA0MtnruXirbndmZLj1Jpi
X8c1E0ZZbFrvsz4onqO5JL10u/HjK8trR88/u7nRD+CINM6VmMpLoZmHJ5RRyfE5jR78gzWwWqes
F1RO8GQSFXDc/abYTY60eIQUZtroi4Ihia/4V9/J1fa2ZGqJoq5pkojxwxyKMPTF87omIjWbBiP9
dI9GapNQAmkAcnnslHHjxk2ePPnkyZP+d7+7R9MoniQTiDT1A30Ff2r4uL6565NkpDUiZCgT+ZUr
0gCd/rLlbYMROaqHeZezGbBX2YUp5TlNxH1Li4IDdKVhQLUQTdfpQCqnKPLgwYPwGuGYQafTsVgs
nE3h2qUqARWsD2B7LPUBjFm32BphlTiEDEYwKTh46HrS+CX6VTYPUnLAvjwQzcgfiLSjyeQ/NxHf
qykK8lOU/l9tNS2bHqVRZLJYzLi4uCNHjiQmHu6qPDHsWDS9Y61TLUCYXETAISQmd9NOohKAW8uC
6JAGArgQfO5lUjT1VGgJnGBvhJc0q2VsnS9xB1AS7zGkfpGBUgVzsE6MF7l8XpoXs5XNvpefb2tr
6+bubjXXY9jKT8forbzhE/RHSMt883NaK5yorjpwCStUd1UPgRNeJehI8WFFCvr2YNSFSI30Nyrp
QJSW1leeXRqTbXtuBaZdFwV2kdeRIHEr4Kx8KihGs2al0KqKtEfKU5OoJFA5xKs+brMkOiYG1Gq1
IMjj8exsbceMGXOAU/Tw9dOl8JBVB5EUQTqnmXj7KaQUxFZx8ct1BZKHeYcTSnZfomTcVl0Yik1b
PzvV9gDtbreuiUqiV9lTy3MHRpXfGl/gn+rEEMvva0jz4wKpA9R7UhWg3oDalkTM5ci/EUhRcJ1N
V8haLuCCNzI9aQPN2PHjx8OOuHXrcyuUJ+b1c4zbE5C+RCXgEHKeafFBX5Zl658tgU2hwjPP1A4w
3+JMSkM4WC9AMSbVlHTtkHy6t7y+JdyTqFQ78B74X91t9Un4cq5Y6Q/JvaIz7D/YT73bWeY7nN8+
0ee3a2cwSE8pcEj5zbQDPqgBTi/aACMK2xfOq/fv3y+BA5MIgkJQjOvfRd2/OTAKSo8T2DM0gIjB
uRB+Y4n9xf0MXX8VtxpF3/sd5RHMzLNYBz4HUktFqPLFtmNXD3c4+1sgnspwCDnOxJXKBU23dlcf
/eEH/Uq3b58xffofK5WKGHsPUB7dHDjSfXGdPzMK0ogY7RVW8Er3fUehKNprcSJ6/3eRlfBKO9UO
hUwGJAf+tNLImqUIfTQEHEJSM3GlgIgbZ4XqFwj000iH/V8qlcIY6vhcqAJgrc+MfAAvtrEnTUPS
RWik5Gf62yBRY+ZEyWVs5ldeJQ9v0P7L3JVHNXVtfRCVKlZwAOpzQGVV6EMZRAgIJFZfqxarVqvU
ImDVgnNQJpkSa/VVa1UcCrbKYFXQIkMFRAQSUBQUIUWQMCYQCEnIcDPPw3dusM9q71tfrjxYXYt/
zAJX9tnTb+9z9m/XFPO+0Qns7em67XDcfccYd+2+dUVgysd4ImUw0woHoP1vLCxv5+WBM21ra+vq
6pLzOxXgTBPDDBdDlFVljHnAxdaADLc/0ZvbmAbOLkQtdJEK93LT3Vqx6tiB7gK2Y8GWVNwSmnwf
rdvNGIu94FhMXekei/RlkXqcpoF0ePwa4CrwDVl8fkNVVVVDw2wbm0ilsJdsMIRppOXCLj/9JusZ
qQHbwkRVBOoppjVJr1MYpOWZU1aGei5KBOJcrSWl+WUQcdLBCHYvdWG9A0yqUMp9ZCSoHmrRZlnC
oW1tnB8SRluCWKWZ/PWBWbTmBbMYjAd1dc6OjhdSUiL1WhXOoE8nKFxk/cGgQvspNcAmTOLME8JB
2aDVQCCvmFuGeSxMnFus/qzrNwx8MyDuv1yfkQaMJjI/iU1SMDPs6X90mIe+fibeH2E7BmYJUjvT
w7RUKGFRgLnkrMnYvmtXXU3N9fz80JAQnbD3IUiQ/CRRAPv3mdlM60upAeu7lcVsXnlwJrHSIMM3
XMPLy8MWL0zMuivaXf1TXA5NfyWGVURLhQN6zZzEKKnsLO5lQ3m6GRyIL99eegfpuyOWd6bev8C8
KZNnL/38iy+cFy1qePTo6/37Aw4yagropG6DOKI13W3AL9R9ETjjwXPNGfbTDiQRQFxpoJA1+cTn
HdqLoGABppWuqLgU3dd8NQg3kUKaFiKpO0A9JdibmZEMftdAfFUgV3XisEgSIPYvTY4pQILGK76e
UQNr4uLiADqbNu3C9evXP72MIWvVURoJNC6CVp+XOL9IfvKhwB7kdpDiKXIWbsNaku1W2fo9fMec
brfFa0khhwz191fSj1pXhn+pPwIEa49Zx4utrMPqBFX1ENFgMCK9QmPESbu1HGFjMGbJ2/cw4ZDT
XR4XQcngQ5Cbo+O13NzLFy8Wx/I70vD09ERDbt9Ty2t8yo1W7KEu3S9yhsaxgFihErFqLjssSsOx
8ckLSAMwhfreOYR0IhTIEJVO5Ga4A+coFax+eMP6O+M+DjoICK8asVdPLj+PJATS/aSJ2gC+0Oy0
rnR/Z+qFC9eysrJyc2fa2pZsqz4ahKeHGKSJTd+6zfuO7ow/PHiH9fWL44pamlap1tBvWJPDu1W8
MugGyFSTE0MvZiSWCpqoAK/ZXonPKdZPaL5jeYib0QYRmqKZfTAjud7S3GhW78NmFXt71WwkQRA7
nSbHpIIw8hz/w4Ugl37//URPT8/Zs9Nv3rypsrLzj1cNduTQXRySA7Gi1l0aK2qA2x5Xgo9ETgWJ
zJWgLOmhpdU5FpSU+sfQJPMhafkma3I+UZvX35V4+tN18UHYFpq2JYpen13vsI6k+xNuzN/88TQk
QRDrSNOoOQDWyqOQWTTdlWjtaUlGGgCDpWG6e4xq6oMiqEtOamnXtmzjFj3biA/CakH1c7bkLMku
PRmqNGySnqNeOJC0VDzAulBADNUpy3VGBKnOJ3aIGJofrclAeRLNy654AKyICfdXXkX6/kjdUFQR
Kj+08j5wBQZje3BwcFSUhM1mx0tYuMMyuVYTlutArMdpaPsNuVnfFiTkJycAn38ydIUEZO7OtydY
hr4I0xcONFGBcLYZ8Tklqlsdj3M+cKI9K9cwW1l0Y3Y+AGfnPduWn0GSADE7m9bgATGwmorryE86
ESCH79/UgVAaVnkHaOBMrgM/jlzYrprfq7y8JQ4LJaqSuReg/UHYBZmHLyeru69fXnbOAYPTJej6
INhHaPquaNUKuuxs7hxCgH6glk8h0/RaDRf6U4wtehSIQKeM8UK8djTNGQDEzQ0qODPbzxtPq7h9
e2FERAQeD50/fz6vM66LoNPzysNcHAi3KoTzmC3lT63gK1Q1rzNzZRgx87AkqqnSrT2H/u/ZhPSY
we7i4EwMVn9XSEu70ozPi60o7JTNH2BzP8DgMpM0Ei5ENqpis3GRVfjqLCRBkFK1iVf0GoMBGEtc
hZJGYK54UqYAJ+2aLIwB9pLrQNhPVnsI2mbSLQrOr62Al4tXB+HOkPS/AUXdzXXguiZfSuBKGlmg
dFHrGJpM4OqzEmQ7aN2UjXjCl5GK+rssOoWkiVFIYPmBMJDiZY/9E1iaQc/N9kjSICVv06moKZm4
MDIhmd9RYmE5+RlIgn5+fv9cuhSHI+offJQGYQ8LZRSmNbkVp35OlARSZRQXh6QymUoBTuFAkjqZ
10BRxZFbQtTrD8l1NTMzvXGqu3yO4lYp9kZGEpco3MT7DRNAxc4mApxeQH4lzD8a1u9AEgaxvjWx
3oLozXhiHNaABWd8C4NbVGaIoZyCnOh6f+FgbVd5Zq4bwZksJIgb1gGcStb2Uo8rcKVY3d0eQdoN
BVmQrNIN5NDxRL1OrIHqHYiNFZoyzpNSAHVvxytjoFMQ0FcCOA1Q5gDr1PRR4LrD+IRCaQRXwXFb
CUgiIWV0T9OeUIAcAtHJZIJOrddp7N1Ct1YcPqhTv7sx+9OCW/hdu/Z9WRLe0F1LoSVpQH0DRUGE
fcnqZH4f1JlJJIs4CvCF6Vploq65INmN7EZSxDzmU+odkgLAcdwqxZX6q7xlrayfTzl0FBC2Aujy
41kyyaCqhZNJjwWcTC5u+OI0kkRI6d20UMarrp54dJmN2e96A8M6+llWotJi6helwvNZ+45O7Xc9
IWD/4OnXiY8WBnxW4ow55dRHwTvPKqnqnk85WF6cUpG9gy9x887A5S7xZFmE69SRO/2DJ07/Zc/Y
pj2MvaXXxwvOPD2YGzHHvfDxwwOKWsKYSWYr8UHuSBKgn1NDNTHku+SNOTWUE0M7mYyBr5ivz6LA
s87G0bvvzDlIImFQi4RquMb35XPB/4g08sM1GC+fkVaT77DUhH6wC+PlO8IieY3I+N02GBfMOI80
UYjxdh9pkUZ7/A7j7YFapNGbgVLr9AKVrkuifsJXZfdIv28VHWsWpXdJKZC6V6Z5DqlKmPLjLaJd
T/iHKdCNHlkNV3mfpTjxQvRZNTfgPvvTqsE4CvRzpwT87cV2yeHfoVgKdKlT8lyoURpZQD5MXWOH
dCYjPOnm6/XGSOJIj8JivD3/xlrW6g1shfZ3SHWnX/79C1FkgyCxSVjYr+iVaVtF6rxeWVQjBFQZ
9JD7Q6u4kqMkcZSpHZI1VYOuxQN+ZewtNdyjzcL0bpg05GCDIOQxL7lJWMFRCtV6vZEEhHL9k+VI
Z4J+yB6llj2HoeWI/v+iZnie0TbbHIE7HOPthVqi0WNtkmv1nRJ1OUcBvDjsMW97HQ+oDKiYKlLn
98l3P+X73mP9q5ITQ4GKmPKqQeXZNvGKCvasvH6XIuYqEgdYBdAv+Il4wl9VyfmqlnfV+OdaPcwM
caz/o+NIBzLCvNq+Xv/jkdX/35HRY5/R5F7T98s0FWw58Mf11YOhj2Ed9cu1bWJNDl265RHvgztM
vzIWiMkVHEUVR/EDVex/nz35V4ZDfj/2PntfPR8E5xSqOOQRD/zzsweD59pEVLFmiLEpfNG/kLqI
3qiB0zBp/00Cg2a2ZoOgojGo1Wq5XA5BkFgsViqVOh08eUtXTl+PJMkIc0H6ev1vaEz6bf8Sj+wa
zPUIEmHQw6XRM1adXs+Ua0DKiW6EAsmDIIuAiAOARYNA9XMXTDP0zyImCEDRjYIbdBmcmVpFH5bD
LHL/yINpH/fXC060iE61ikE8wpWzwf+Q1CQEmUmkhlXsuWgFwjo2DAY12AKwHZWKX+d18TQpCRtV
vHz8wtv7bo55xpt1ZWuXf0WS1rh/BC6NJ0ebv4skC2qQhEqUvzqeaY8AJSyKjEuN43eUWI+XC7oT
GTUncUQ9fEXrucW2HUmOEWYP8vXCDM/ttg/8VxgwaC5FkujvTN6o0elpUs2vvXLgYR4lAwDFgZze
KYXh35FmkdMd5j9uMzD3WJHPBADbV7IVALSDD8fl9ILPvUtZ4U/4v9CkWTTpF0YHBSD/eIuwVaRR
G3MEL3B5JNKBoMZFXqgOxNfL5+3cbrn5M9jr5r9yOqPX/QK7nc1kc6RXGhjUkGaYbrfYJLcTMwNX
rz75448/vjupraMjPCLCoJJYzq0yy66wgpCkQA9jFqPTyBvtjrcktUbwuUhzEZJAo09qbbrPqXT6
RoEKVEXAYxYWMXfU8ctYCgDKMmnSZeUw7bFtLmNFBecMVfSEpwLlNfA/y5swi6r9bfjzky9Ed/vl
P7SKvEpZzneYGx9ws7qlbKVuqLo6F/XhGqQDQY1mvFBVnL7e7m9hp2/6XOQcazcj+fq7x8yQngv4
oEYwHsNTq+n77Zqd1r07adJ7KWZ+fokJCWoy0QAPPZX8NhFhhS/GB32XB52/eXu8tb+9zHK9Ro/r
sfuTy8EExVNtzH9FEgj9To/hxUHT3kIlqPmUivKwfbHYtC81deHUUz/Bz/LEiZRTDk0r6Sfy4+En
WR2Pc3Y70QWH9cmyawUky1BRQUJdIc98a1LzBbzLnCRZm+KTaJmjbhFFTKnwU6trS3FG1SZXBSBs
Kcb4oMYvXihV+3qzyrT7Nli1H5v/B1LWbXU9AD8FsZGaIc2s+qBGLMNMaqbdGQIs2XRt5bixY4GX
YTAKKacZ3ix4kmv5JZIMI0xx6Ov99u2kly721ZCP2eyc8oaPbTDPQZIINdQYpo95uJsUxM2CzG4a
xBp9MVMB4KP1r72LigeOPBd2SDSNkOrAM2hWfj/IXda5jEAyp6BPTh5URjzlz8yDPwQ/U3IZH1Vy
0ruloKbbVssDsBJkuVUkDsh7HAVM8k7k+v+EdBqoIYs3Sj97WzLZj+HSjffs5pFvL1itOiQRikXf
3ttqBJJzb2iNWHKuuTlSOeqDHrSgNNm37zi8brLbvp7yKi+MByY7Jdoc6eGGD/oeyujBMICYqgcV
nz/gTvmVMa+gH5QyTwWqZqH6MAWaazTZCTd7sffZV2nSR1xlHAUCvzNksmNzepbcZf3cJakeVMZS
oPkF/eNu9rgWDyT9DrWJ1UMdUNdKrAHhQHxRAxi0Vvt6x8HLVBi2ffwYu83O24CSx27YunDuZwcW
pNjYn3jysL7Wbe47RhAwjjtlGoy4P3jfvAhJshGHNG/U7eghzR/G+9Ur44WvgK3bEL3RF/2t06iW
7TU8FQiTE2/1Ts9lbHgwWM5WtgjVSU2iuUYztcjpWVwycK5NXMdTgmDsWPhy0YZFdg8o88/Dn6uO
t4hA/TAmpwf8CShCnvJVQ/Td1uOwQUgHghrZoLXd18t208Z1gYbHjAm32+wd694DdNw30DvAtJgg
sXpHLIy0+uYSqN63M6ae37Bs7iJHF8up54NsYBv+cM4YLpKEI8zz7Ov99mXw29nw3/kGSqM33OqV
gyJ23M1eYMbAmAsY8qH465D/MtSCCvnfL4TAhodsFVj10OcuRczvW0X1fNVZqti9ZGBcDuwFoY95
IFIPcZP37gzIQzoQ1BgKpQ1jXi+DQR2GIv56x0626dnJYoRHRET09Y6bIBFZmbUfnZudUnjC+ex7
Z+8dO3bv+sXiSatWbZ4M0wtUjbmCJOJI93Iww64tURrx6PdyTNJagoELXfHLjCn13xGqT9nxyIKb
TrHv0iUNdFMYUdDX1IDt8LLtFm9sHknZy+Y6JFNx8EjTWLux8+eWi55/14wnNpZJHu3sjGplWn9E
9Z/oo9zDbcZnDm0ou/eLvxbpMFAjKo/hXbCZxs8MTwCQkjXTbW1nwLVZaV7e/k2bNsXHx8+YdDE1
dXNQEL6jeAKw2cJjUz/+q1Q+7qhh0WgUnAkKQUhgoJXF1G07d7a0tpIOMSfCvamoOkuE9OjjjhoA
LR6eZjCmVc2ivtrHp2e2t7fPWG/u4pJbXAyTw6SlBYWHD1x8snFt+lIZi5JJ3CYE1fVHp+w8PDzm
7Z1iZ4eN7Bl6Wjp7FoJP+rijB0cog8wbT3JGOMj4uKO/dhqNHdkJCsm6h8yzYuM4jBm8vLMgXiqT
doYRLMMO5iW9M+XzrYbrsqe1VhDxRZjWbOeKsd+sin94IWNvZj5R7cUciGj4lHJk/hUXhwReYhmf
U4on6s3Hvmd2UuTvh3QIqPHPcIOLSYeg1qokV3yj2oAJp5g5Ojo6OeWkpNjgpvb09W3cvFnA4cBN
E/PsdxA4xX3cUSOgUYks6v7da9ZMApElIiIuJkanVXnCzrZLaYmwodPHHTVoGaZaPE0bb9EooJK9
1B9On54RabF27VoQ8N3cCvR6vQKiWwAjw7VYIXAz+LxGU/i30YhaLdu7evUEoJHt25+/eJGsEr9v
5ExZa3kMSQb0kARl+HujuWh6+Asf2jcSPrRwZEf4H8vJQACE3zFNnm6O8N7Zx320GzWmTV3f16ni
2nqpSblzFi9MrKrQfqMhpX0XZrhEhIoaU3PW1M9xP3LucXaOREDwVQiCnosw83MdPKpqZHf9g9U9
9Q3ryPWNxJRgxVjnB2Xir6quBi2bRtCr4C3rm5z8EHZ1+3igv18anqctNgldJcilW3bv/sDi4LIt
W+I5z2/APcSGeeN3I0mAGoWM2g3Z6ZmYhQsXvpdy5MiRZaGhNDqZCLfvS3wmIlQxPh7oL5RQrSH5
ixwmklqBVNS/+oLt9OnvCccsWLAgJkbWXhQBPy0DAFggENTd2bdvX3V1NVGvhZMSIW4KAneJjwdq
sOExTOFMKmjUEohOSsN9jsF+DSqXo5fScJE0ibiRRY+g6VvaxZNcXSvlTalO9P9j7trjYkz/tppq
ouiowmpiWZRKpZoOmlArxygkW00lK0qHDZVqpiyiUFZHh2bX2g2hg6hQI+QU2oToYFJIjWlMU03N
M4ffc0+877v7u/94HvN557P+wz/PNd/7vu7re7ivG3S/JkSQILeoyFa4FYSc+wfTSXU8tjt9oGWJ
Zr2xa+btPsMKpiw4B2+M94VBwK0Y5DxsMW2glqqYwrS0cTLPqp9TUmrf1edKJWINlMqW/qIOsRci
W+GftbWSj9ExTdkAA9WHqVSQNI9eVL+UraXxpMaJ37ekNj/2lzBjJXeT+1sF9YuL6eG0/sc7kJjv
8kz4ZcTXCLUgkd/ViVCVgPKNU9fX9xPP49xpZZPoUkRAQnNL6+kuurAfArfeUAinX4vn/xgYaIJy
urc3/6/fFgNOL+tRg7SUyVa41YZCFNMgu7lgQcKdurpJmcmHDj360o7dR0yBYcAtMKxxXRL7Wj5H
NSya+BauKOjs7TWdMeNO8pSSkpKXLS0uCcKPtT8T09LS7nv5+fnt3LkTBEgwVzsRAs4a/2AtTjn4
914kNn3+f+TgmEYw0OZ6PDeD6rraY8MGN310v2hkK0Fu9ZKt8Tdy5JSC2KptfH5ky4MKIPBAJtw7
hRERNzDYUU86khBQcilOXedtwEhJx8frGlyawckkyyq187oHVHwoF64PvHnTTNGLTPRqH1aZPrui
bynyPKOBKQUnwPJvHLNgvwBu7YHuULnSYGusa/Wcd+HA4CCaBqM58LlzW9evX/+dWmhoaJzw7RyQ
rnT+phcGA4Rbb8hJINg0IcoY5Vub8vLyjAKTjx5ds27d4GcejD8ErbBZ4xYX1vLFxR5zXFK1SAUu
8UJNdYZzdYKgD+XGsG3bOru6Ll64ELJ5cz4KcV7ymTNvX6P/yWU13L27f+6Te/cqfnw8GUzhlN6d
qg+Di1uIKEYlirks4T2Wmw8F1Lf3bMihHHLsf99VzEQCaLkBiIqFxZWhxqPNFKASx6aTIK6oZGvc
2kQRJ7KpI1Kw9RVBzeinNnGnuJgOVuKeQ+OhocGtKeTUiNh89iqjfktGF5TRhw8f2qpiwHMLAAOF
r/4tDIOi2yrYeL5l+O0JSc4WkNujKX+ZaGHvwYpmF8m2mv41QWI9tRIT7XMRiWWi2uapljWtnN21
N0TT/NqiWi+bezJPJQiapB1mRyauju7a3vDCWSgcFFDBBtNxdYS8rUe2xt9LUQjPS8RIy5WwfXv3
orlyefkOd/c6NLnkBiUXehZIRse495GMIUZmZJt/ZxuF1+m+atUEgm5gUFBpWRn6V1VwVm2fSoQY
TpNt8LdR5CR5bB4fw7yurDnewZs26enq6urpeXt5PW1qam1pAe4+SchQvs2W9+/fb9u2zfpX5TVr
Gp8X+XjmO6v6ZqLnWkCA5O7hKWAn5hEmQ4bVyTb/782Uv899fbV8zB/Vjx4bVIB8VFFSgYFReCMF
2yLkd0U+a2y+YUayBvJxGZtxIe7Tu5cnGKtQ+Tg3dZy1eULm7n5OnRbT1DIx01egMl3d7RszY/2T
SbHspuIaNmOtnWvdKx9nD/LQ+957VBDN+fscqmE/AP4miiJYZbdYuDMszExPT4+gu3rdOv/KqDcs
Jp25KZlEoYmEgxpoRLOOmTyDAcKvQxRVUuS0VkydOhWVw1panomJIgaFDlRHhcc4WNHeBv/8rHyB
scM2oz7Yu87P7xvg8q5ZUlbW0tJSg/6TVCpl0sTXYrpXRURYEEwzc3JeX93+Q3Dw9DITDY307Ozn
uZZUgDVWzSgIhhV/0UNRFUY0G/uj2eWLdvxEGe5t4tK3vJZk/SBQsXhyQ1R70okBCgla+0m2MGQK
vmCMzWbMlMw/EvSKQH76un9gqJsC6CHFSLMR9v24RYdCpOOVbdky6aiuoQFe6fosHV1UiLDi/Hz8
9Q75GIGMiRGORyOXe+8WgjLv6rbS5lyK6Hz1wMJd7XqVv/blbLkOHGKFhbf7DOfWk27Vjb/q0jo0
gFTFUqoFzBB/pYk+GwQhvY8bSDQJGL+RNDgUwJDjb6/ISe6Y9hXgibVr9VGeyMo6dOjQhbNnZy9U
dXd3X7duXcLQR1DqOFagOxOGR9G3hrGVFlG9++Z2KuiyZCZnZa2l0ylAMR7eS8yBYcCtOOTldUyV
7t3I0HbQtAPTQ1lHj/b09FShvI6eWFrGzkY6OikXkvftq2trE719cEwoFN7vDA8PP3r0qFQiBlZb
PY8NzGFQ8VdAcN0Q+G9ax+YWx+umotIJ3Xg3dbrTUvncpBGxgHp7pn60ZJ1WZKJw8AOblD3eM7NO
o6EajN/q5ZvVw9DhFhryxRGjzhAjsaGhs4FwAnbaN+hSCSqcADtG/zkO4pRPno+/8yInO2LrpQ+8
yW2/ZPio/n8UcHicaHtzOvd9K8MmxT35QNi725fCSCSa2DtxqPrt8Vma86KfTNRyKqYlDnE8H9dp
WYfpdNYQA07FI3qoWCQddoiBgccvPOQMIqYV6pgkLD93bg7BFN2MIffU0DjqT5y45fFxVe3AMcWr
VVtgSBTddcG2Gj/PQr18OVo0dXffLOhrB6sx0ZIYCIOBv/Ein+Cww4ZDOMh++sfyqqoqVL2jinb/
/u9DQ0PXrs0qLCw8c2ZG2VxU0cfHj6CnQFVlZWZdSlta2jhQyjndNAFil0y2xa1IrOfLhxKzjWYq
lX5KcCNE1lHPWZDpL3jbl8tiSUQxLXxl37ZA9mUuXWJeLc2e9J262wUz4wi6hIBurxcGFndhOHHr
D0Wo32sJgkunT08naJ7580/JaC75vRPRCPb9+EsdVgrgRuFQN/UWryKxyFjWXHpUb/zMXxjV1cQ9
+22xg4/LXnXlNS/fNPu4iPxGPhVJcrZELTRZ5sh7f7eQWmRMs32Zpp3ri4QOnWrQYkqA2OKsd4a8
BUO2xT/2IR83Yqt7t5RvPVZZSSY0uq5cuZ3//rGs7n1epRuG4F95MRhk0NHRVrICo5WNTcLwp2lA
LkbaEWETUra4VYachIjt5ijoIh2eYu/n7z/pAGHFihWOjo6zPAtO2oYZHNcnkVg34vkg3d/iM14N
hgn/hKh86f58bMMeCFfabsl892JB0OeBonmtPFEzU6pVI8nxFaj7Ovd/CJM91HuCNAYGS8FtFmxs
t4wymANyfa+N0rcjAlmeTBdq3oN9/7+yVrGxNFjVycmJoFl+9apEIp6CsrVdqhrEOZ78FZax8ilZ
bC+Lbbvev4Ym1tu/WctkdkdHUT2JZhsgmV0xYdrZinevanJZaMbBKRXM5PcTo6JT2y2PVI9ED7V7
Fi6wzAvc4/r9i3MV6dwkQNNDb8jtENT4XWXlpWlMqHvZ7E3BwcEmE+ZZW/f29Jyi0I3RyAWRVYpg
GHDrBIUQ9aeOlIwMLYJuR2fnuPHjxSP8WYCoQ/KIELNvMn7bV3lHQLHVMIc4rQ+zzQYHBozUlQwM
DMzNLx7Um0VDDx1z8/G+aagm37gRjDYAXnDrn+AHQ6bo+U+Ml7j4XFatD2VDLiVwg5r73HrS8NQ4
sYAlrbZkfptuY0lfHdtDAPFSYxjDGh/4DVwVwXZlL0dOArb+qR3pbWZJQVQS/tJsgn2/ggc/MVaW
zc03o9s+OWWE3/3ZxMvMRM0e9v2KrjtgY+uNP0mLXrzfIhu+7cvZsiRAvGGoo+iJwV4T6fklGtyk
eAEY7LJHtfetumw751efhtnpJPoiLeaPvke0Y1kCa2TgB6ARVBhkyIs/ZDtFFxwwigRPzy0mk0E/
59Wr6sQRXTRsS5kq12AA/p3TnagcRVec7fz5RpnJZ8+Grlw5Hmz9X+hEiM8HGb9XqpxUDW5lY0y/
tUgGczd09PTMMTV9mDx+npXVgwcPVNXUnpxyEogRQQODUlFe7rb+5q1bwSEhKrIrgr8umwhTQ/jt
U+UtvmJ8Q1HA6keok3IWJH/74p2W7hGmWMyVtjkxjtb55lDykhA+SnshL1wWGXhSxEAyaHHMYEOC
+M1QrazwveNg/w9vEszOVbIxhN+NA2VGgDL7TaKXzFDHdePaFX6LdD2WLwUXzhj6hKswYIoe58So
5z58OID+mTHhzp07O3buFI/WTWZPm/gXDIOiJzgxO3Jlm/no6upOP+q6bNnDvvbroHPbwp4wGYYB
f/NCvhFwMjYQAi6rIpI1Yarjs8ZGnalTOZ2dwUFBQYGBgeHh4WFhbDb7RH6+w+aHWd6Fq9AgsVlM
umXAjfv37x9wU16zZg2Hw6FLZS1D5OAsIQw2/nqDQmhjRMAq/4HxhTZiPJmIWEBtfp5xvxNVfuFx
Io4kl+VnZmyS3kwdUdEOHEM0M/OCwcNfesBLG1+j0r/YwvQq2e2asMoiIsI4wIWmFBERsXBakI5J
3UzT7yymzZk5x5yAIjugTqDDkOFXFnIKQkxFlWsx3U/+WJ5roUe85FfV/7HHBoijZUdN/WEQFK0t
sGVQ6I67l0Eq9qv6adJYv+u7OE2FnrLnWTUM98NA4B/TlK9mjK24NWbamNdSiUQyODj44sWLmpqa
0tLSc+fOXbx4sbKyEqWHN2/eIAiC0uEjy8lMCCz8XqYKiQ0qmVA2vDQam2s7enqOFYLYeH5nGAID
gX9aU1HkdmYKw+gzuaU/qZYOCqjtf2jJyO3jbp647Trjkcce12dJYj2gawluZrCbV/htTXGT21c+
13XaLnDUGrkDaCIlL2BW7Zq2eLXHBjdUErkpo1JikYPyHBgm3FKCjBPSP0yuMMq8GQbzxijtua2i
/Ehz7gXXm3ef1I49XVUZH7dwvswRWC9gDKxLi9+qFG+EyP941mo+1ghZf47Q27fgKr6qF/Dwd03z
BhHSVAHFfDeqsjsMEv4xCJyI/m7ghPlAXaT6yCT5VsrYkhLXfckzzKY4OTkRZxnaa2l/6udpJIei
J+tCbXNl9EC1jFP6CAOGXyrMw6XEHcjWX7ebgv+cHAge+fniNN4FvMaVvYB5nGuapx/YTd7ayrAi
JX4bUrzB+rsThC1WJ4jRYC00GKNhZVVaUlZ6+XJM1E/R/E/9/f2feBpj5gQAIaRtPg6EK1VpGAYN
t3jAHa5/WKxifdjvtLFsa30xhpc5w3e+ezfRQGciwetGpy44sBbcV7aEgcItJvDG6x8eqxg31wzi
PKvLJWVlZaVomJS2Arkaoc2gump7lI4Djj2TrijBBsLw+4nK20/H1swUcKlLlx48c2YGwSgvL+8b
Ck2Epk1LWKJ57RJQjVXv3MiLeiC29KwR8xZ8Sts8QqiMEz6oiHWRgus/PLu9wSYPHcRDr7tZIJQe
DXYvYdgV/VSePbamZz8S2ZcfC+qd2k1lxKdhpHahiC0upgt/YEy7k0v5q0000FVMFzAlOX58dd+2
BGk9iy516otXMlSZXlFtSReLtdBN+SHRCXY9Br8rqSIMFsCMXHDwdBKJRDDau29fe2U0mGHZeJr4
AAYB/7ymfJoR26zORmT4RF/OaJ1adG2JE4POFPJyuwoMV9STbtYVWdbQhzgC0XVqud23+jbmCasT
eOL0SNl9A+7wXFiX5yvcRBWyPlFt/AtC9c2RdXlERcYR8UJOK5feuIR1UzXFI2rwd3R10qRIw65u
jUoTdAWfn1KQOCIu/ihKCKk7P4VRI+EZosFVOuQES9bwO44qwj1jt/j94dxcQzMzM3DNQs/b3789
3dASxM67kwh505aM3ydUIWu0t5q3dOttWef7/u5uvnck/WPSSPsOJKbSpPshsSmSLhlgR9ZnZ/Sz
ddLifVxO7mLzu6kym53u3+ZCHqIgf4VZqJxrFKO1GFd62JM5326BzImmcr1LeLWI18yiN0Uk/bhn
rLIOkpbK8XGRSJBikShBbUb0r8J6Em07XXIqyWFR5qa627eLaeCNKbOrTrCWy1c4isqHGtsdNcek
94fO5U8a9XgpLx84bhtWQ6hl0bcWvh53iXan5KOSysyp9BiEX/wq1iUsfPc4w7XtwyGtTVwSTbzS
WbI/9vniykrhn4UnChIRhCsbmV9hb/8E9gMofLADW9qOHp21rypkRye7P7UACaCJBgW9hSzTKYxb
dfm5lKg2cf/jDGZqgFjbX6zum9hysYFLk9i8HvrGQt1tZS4FxHz1M4fF/w3ZAb/FqLxT2disiWzD
cs6fNyUYxcXH+1/b0SOVSg1dRGUs8Z7NI4vRfZ7sETr4+6QKCnNYYs995NRom2Gyx1U/6tPzOgEF
VU9bKxBV2ZwLV2zZcAMZiwqHU9G2kMvODvjtSeVVitjmgPlcFs+ekmXvDEbEDoAJWV8klFtPokhE
9Q7iCdPVF+4pMr6YJOLUc5lKRGqtakpvtYApGuqmNl/JWOGRtn2XCx3hW4LF7vjcOQ+GXNEzpw7Y
NPIwb9OiRcoUCgU9k0gk1p2DeqyaJETAki61p5hFxj0E+93hIy26l5PB59IdOPG1ZaJpbplgTL+I
RKVJm2LEx57unxVVt6LeWJ+RJPjAjgSl4HwbMsSywOErDE7ljD+2LS9EIhurYmVWfoDVJ81iSYb5
3PtsUhm7YN7NO76jVwRRScI2TuqiDmpbWJQJG1N8KH2JIxcvj8zxy0x4d3u7J1OKSIEHlF6KMwsG
XtFSDJu9oWNUR/LBg2PB1RLCz6dOtT84NksKDOZaGZmLi9FDDwyNH6j0cQmvEb1B97t3ZJJX+7D+
dHW3jScYfXESzlA3qzY1IPpSnLph7kYkRNJuSaVLwfWhnUlkiBWWA34zVMVkiygHVMVSxl912TTK
AZTVrOGBt61UlkS0fAHPYLq6LnXIdcfj33dm1CQNDzZzO8xCeHmbImkicXMCR+9eGjGK98g7UipC
QOLkFbDAG4Yd/3SMNb7E/+/dbaxlz/994q5TVnoiPgWdbde05W5rNdEFrf1UaQMMjaJ1G7bTTMjr
ZmWdYLg1O8u8z1/6OK9w4A3dLmbeC5D+9XIALN1H9aRKTtIIusb9G5hmF+jKYOmGCtK5DUzpztd8
ZYuzV3p62i3pEqkURNP+8IIXMPwKV3DYNnTicMl/eDvzqKau54EDLqjUggUERYvWfqt2kSVkUyS2
bnUFsYqyRa2CShGFVvbk51KXSouImrpGqRUpCAgiiyQBEVGpoAVEEBIgkAAJBMi+vXzfC9T+yntf
eUHF4/GPnDPHzMzn3pk7uXcmJwerP2ccSk0VdFQlgws6TCSgPy3JABNy/YJWeC3szFP11sSzzLop
z+r1VpkgoP/JUrdp1PSty9l7S6xGJVSfX24ZEhOl5upD208qgh2SGQzP497QDE6oMJDrdGDISopn
vgrqfvLtbSAHACDIUyWE1Cw+RrDYlxbxgiIFd3ZdeSUrkNxrlM4O1KXacHTCCMAvmLv+RlOfabAX
CQD03f2iH7ohtKwmGt6x1dBlPei3QefhLWt+ywdQH17j0KWl9/8DHTwnRRgjvJ8jGt6/9U09ikoh
qOlTcy3pNp7Uv0XTSLdfSlvuqclgDnqc0DcVRBgM4TeCYwr4pfK7dGp0V/R4G/6m3ky5KpmkA8LJ
6jlM3qQlHkHibEvwlNofrP20bhQkE7zrdigEwhu6tH8CcBOP1z8Y6a9t/SXnD8YYRyHpM9IdUVBG
XegCyEt6Tv8Z+9gmGimOBPB4yeTZbE1mQ+80vUvtCaLIfbLGjFEO6+5jcQsblS3qo2SquKLQ2k88
7iPbyFYpw0FfAzslQjppEw3vB2uoL994sOzAFHXeZKhLNhf0Ke3kaGgIX5zxMSSFRjqFQjcnANpx
aSTddY5qe2HXlJIs00X373ZulXWE15KAeoXiQvHGGzMsnByoFqEKaUouCb8QCLg9ceaeXEEpk8ax
j1X7RXVfaihYvmhShbW5WSWTKpGaQ2EnOcJNi2QEw3MpwwbVEYf5m+u/vNoELVH9Cm0DvWrZ71bL
jUiD6oiGN4kdkfEP+rudpuTPw10DvWVQt1yZtXmVO5Oh7KhNUpPfAxNmIzOTSVV9poCp/6VoeZCy
JKPAx6JFdpc8jSrmaitZ1jbsE2mU0VbN3spMWctRMJqajLY1Omfq+imSEd51V3vi8CcHDW+xjnhX
e3Re1co5vNkcXxmzaVPvyX6viteyGLq22qRo8upckulPiyxAp249SiarFUHFDIdPXl4uLmXIWfOV
Mr44hNq3lpXopx4356N83jp+TXwGRQPdP8ymuaYhGGEYzWnfbMdCOT6pYB93ma/vxZMnLSwtExMS
ngnrsjksqq6zjJ6Sy9wZTHlQqDEGN7LddvTnvpq9IrFoAZ1Ku0R1yO0e72Fx7PtcVwED6Gi/YH/G
xm1O+tEJJtAggJ9pbq4aFfSijf8HkYlkjJFubotyhqpKLeI8w5OSfilM8FYfA5FgbjAvdyhkqXrl
BWWci7LC7eReizn6iPzxdGoYuM6x8cz5XZHFzBbjJQ38otTEEApT05sL/GV66Yn7OTDh9lffEHeW
JXMAqCbaJVt4G8ka7zrTIg5/ig/S2HerybzmM/p5o1ZJxkjphuGNbt/YvSjvGOt0jeBx16GwltMX
F6nvep74C4vYpyq76kUCz0kJvmLI6zO2bQZmqNoFv2VQp8WKMZ0Pg+b+micCvJLZgEbG5zTcJYMo
NPkrLW78LmtRX6BToGvvcze4ITxnIhreLddQ5w57Rsn/cO7ZU2cToI3MeoIxwlUvouH9cN90N0dX
8+hPvSY3qlsK5GNqHx+FKhzdsfmyZ7XgGbjGV7MlUzrF4zDo3es7ZvQ+cWf6KRWpshbTxb9GFB3w
ukuO0an4nGIvDsjDhkbF6ZCaEkliiDtDC9Xyvw0kvUSyxLuuZRFdRti1I13O0t9UGlolIz+jJJ1W
p3skVGwpE36a1TY6uenjzNZDVT3lXcprHKlHcadNWkv/SMo5WW1xtb3VParkJqlncee0m9Dn+Dz+
pUZJq0zTIdeeqhMvLmz/ILUFlLrbLu9TaQFABx6dLI0X/4Fkk3c9DZo4/GnQSE4+fYqXkHAmEerv
ZDPbGOnYYHi/XUOxxb1VbE+D0PYrZL3XGKFxK9HwfruGugj/ll10tvnMgIsWGANIGr3rKc5Ewgi7
yPAUx0AXEd+Oi1omD9Zo8h1jhAmgxGE02B25vVKk1KY1S7c97AI3vrlZbd9XiDK5spst0vBK0eLC
jhkZ0BRqxxxeYl3f4y5lYYf8h4ruL++2T7/ZsoLZcb5B/LxXJVMD+e2K3eXQ51vLhFfYkkqRSqIG
N2ForzwWv+wWkk0Mz3UMu67j6PjGFQkEbr2giWw2B0wmIak00oUmQ9wsVgO5fPmOR0JiHh9zhwe6
ObVZBv6l/NWzitXxaXabWUrzSmbnhQbJ424ls10e86zna2bHF7d5YBTN5ko5ErVcC7A6FBGVIq8S
Qcif3dc4kspu5auQ+GDL15ZINnnHdSfQzU5v1c2tZ16tZptJyBuu4ZmPQRsuqNLbPYMNveO+47wF
1Agz0mvxHScuoEpvNeFuStDrBN0EsDYyZiNoNIwOvoY66W1nl0M5yfDWvGDUMEylQekl6tclAVu3
DaXTAxOkDc/w9rwG64Qftk6vUckDKspOyTZxRtLJ8PzFsF4Rjo6DckxUzW/+h07c/pNN4iutpi8x
WYukleEZiGGP2x0dByWaaB/LvNZTNhv0StlxTZYjKWV4DmLgLuH05mnVDuixVqv1/1PLGqoQWp9C
rDQMoznvyKVVSqWSz+dXV1ffu3cvKSnp+PHjaZm3n71o7OqTKjXaPrW2QawuFSofdSmbJGqpBgCT
JfDfNpnmqUiV3SoDU7JKkZIt0bTLtbV96gyu9GKD+HarDPwETKzAtCov3tMcySZ/5yA+oC4r9mzf
EbFj+z+KOGOxkKP6E6OJfv9IEVBIOcOkiCikMIOlXrV3fZ2UC0zKCYUUFibljEIKB5PCoJDCw6Rc
UEgRYFJYFFJEmBRuaClnR5gUCjacYWxgUbDhDGMDi4INZxgbOBRsOMPYwKFgwxnGBg4FG84wNnAo
2HCGsYFDwYYzjA0cCjacYWzgULCBgbGBQ8EGBsYGDgUbGBgbOBRsYGBs4FGwgYGxgUfBBgbGBh4F
GxgYG3gUbGBgbOBRsIGBsYFHwQYGxgYeBRsuMDZeNU95nRSMDTwKNlxgbOBRsOECY4OAgg0XGBsE
FGy4wNggoGDDBcYGAQUbLjA2CCjYcIGxQUDBhguMDQIKNrAwNl69mX+dFIwNAgo2sDA2CCjYwMLY
IKJgAwtjg4iCDSyMDSIKNrAwNogo2MDC2CCiYAMLY4OIgg0sjA0iCjZwMDZePUh8nRSMDSIKNnAw
Nogo2MANZmOgFDyU2GA4BkqLQ4kNpmOgfDeU2GA8BmpkQ4kN5mOgDjWU2GBABoo9Q4kNJmSgoDKE
GH4wIgM1i6HEBjMyUBYYSmwwJAPn7qHE4JQ4oaAED6fkX/e//z5CYlAdi4XF5RMOLrIyegqQT/rb
z7AOTirC3RMe3rg1eOxPJrM+y7sat60iOKBaILH7wrXMIzzl/IaD3Uruxcdt08PP/RJqeT1KW6Rc
o6oUueHH31na+OiIc+OHJ+YblbI7Z1SnOnuspPyMB/a7nisoScD7OD4g8I1mHF605KOs5+9HMXRi
yy1Gnhzv2fDD5cAZcLBGziibkOp0NI6OrdWoW9ScC3QKPVIeJj8hCrKP9dG2C67P5pABhRjgs5I5
lJBoVXBNSYadPXUBwOOfMWetZWrzWwHanc/s7ebF/holFqvKOL8wlftapZVd7qybkZIuVTI0h8PU
5Mg6xwlj8VAZbvG3nr8h6oBB8gqqa25Raq7ogBfpkwbF6dC+Na0Jtb/zOQ7RPTtANVLtKV35slua
e2pZqr2XqyKqs6vyLpnCUivlpXLSAjqVvp9ffv8CncbWRalqan1ELHs3auS9a3OXlpb+uLS0q6vr
M68MN4rm/pMLeDKLouWWxVN1gFPcwXWOc4yh67uU6HXfI6rjguQSdN0DdDpdBkvnpgNAl9Ch7xgt
D1KLRWai2HP7BeJTavJaplIpeUk3Jet8I3RhJdwQy5CY3Yy+rbwuBzWZQgKd07mcHORAOebaN1/S
I0jKFgWygcLeR7k1oM9Y0nxRffKYcNZlilwsFlHf+22L1XsbjSy2GNlc/YaEqAsWyTUo50ZwK2V8
jk96zDhXxePQsrBchsNnDoVkZZOgYDn5ZXrMalfgkw7Fywer7HGuQFS3NiOQA8SopOGVJ+zX0Ny2
X6R4hfVyC9T27gxtpKq4XHmC1srjLV22LGD79tV0t1gdoPXK8I9VdzfSSVRAqy5znLCs+Mpo6KmA
ccnaKYja4JA8g+4lpVikazNnXW9QTYtS5HTI+CvtLud1x9b9IK06UsY5u1DhGdPN4DNpTFN/rB+Q
KVbK7eiUWK1WDtA4YlHsivm9z+VNF1qyRXpdGzMWHo3H4rBjxo6tr6v7/dq1z/0LFZKOqhB2oVIt
dyiZYzvmkDV0tRC352sBoiZ4JE3QdWvQiUXPkznlFaxwtvirYO565hlzhpx1PkogjvOhc+MZtxqV
DREvxUlhov0MBQDCZk/V2VPFvyn7lotiHdbsL4wjqgKkv4XY+FPr8nasolCYhw4dOn58RUAAr6+t
3MGvQNL1MvfvpXJMv1Q+DV+C0F9noPoyPIdE9WpFf5mSLX9hOL0EfGOezDqyw1y4n/FrjLiKN5sz
u1FhtV+RU/w8EPTTNXrM3ebe3KNkKhWQhstP2I8JZNeJKFezlJFNzXgzETW/B6g927XA03P9kydP
cnJyMBhMbdrmMLWsC1r4Oh19q1XcweIJ0EuMFJOl8xE1ISJp4oxGkwJJs5dcGt98lCwIiXyQ0zez
qs+0Ipq831dL4FfQjpTbHzRnPK/XfLNLmyhJDKG5KaLAHSGXpEunSGp2882UEyu/ii+8HCao6sjl
4EM46zy9d+/atWvnzl9ptNzdNX8sCO/WgMsD3Fn0y30btNzv2H/lgaTFv24zD2iB8qWxVi0X8yvj
7UkU4Ytbq2jzGLFqWXXKen7FJTX4v3NYVGgebmDlZTabnZSU1Nra2t7enpeXJ5FI6uvrfzSzYeft
OwSZ+ep7kJnNVJ8jPDYfKIYNj3uVQsA5GE12lTO+qe85/INyFAjMNzjXFJakuSjVvmpPrIzY81Ok
clQtw8GGowsViEUiKtBFARZyqxdwgysjvBa61PVua3nizufo5ocBX+3alXLmzJnMzL07d7YfmWjX
zWHpBLUZoJkx/3DPrf8S4ZLJQHVuWHaOknc3pm3OnjZtmq+fn9mECXe+q2sB/wiFF8+elamkAr+7
+39PTvbx8fls7tzxZmZhoaFZt27t27dvxapVgs7OsWPHdtdlH4XsPNMMsnM11RZxp3RGCsnocJ4P
8AJ5KeEFPpedHKhFmULjqixTNzU5OEITXHlCBC69Kd/FPsjSHHjYuTw/mTM9WixW06nhLM2eAk1x
QK0Zc4M50cs1zk0VwD8hciBRzpGoB2g02o0bN+LiVlMoQF12ILi3gIuSqk8snKDEYv1y0nVELRAi
MQ5VtlcQLvKPiXEdNerQjRs7Q0NDvbxsZs2aZWNDY7F0wrrsmzdvKhWKFy9eNDQ0pPvm34NCT48J
FHq2Pp2I0E1roNo52KBOqAyq0qg5cS/pl2SFTWQp9KAhoSZ+ZQWDJJXxIZ5lTCtfqceexkS2gN5N
UWoFItbP7swfP6Q8uS00lnfOJgay/VQ9ArZWDeIaFRW1evXqZcuWrU9ey+iftThlWfEc2wlGM4qM
aiqImYjfHSFsYlGZEepFC67ttLQ0W1tbKysrb2/vrKysvPz86dOnr1mzJjIiYurUqbbQF7gOfYHz
pe/tRvwCSNEOpfHkIt2lStaJSkZtg+S0/pqweTXe7RJFIC6VszodYp829q3ep00cj3djgJmhNJ41
3Yt0XhRRwWw58KcqeY2XGxvQqBXHE52cnDw9PePi4tLT0+3wezRgtAbX+j/G+8tyvj/id0cIceie
EAqLvxy/aOZ7Rk/n2gW82HTgPz28FZ9vmb9m22jL40JJWEzPwnByUMqnRoct/vwubl3Q0iUBnySd
9qzIl7O9LRM8HxP57AX8OKduRnMkRQAeIKZrJiPM6xooVw+2rSPqPkKPckmz4gsn++kv2IO2PY13
3fy9qFwpZ3m6M8/4q78O5lZNyXVjaZXy+mRyXTJ77k1q0p2OutM+dPB0EdZZvcvd3X3evHljxx65
cuXKIVNzANzE/o5Vk6BYleZCmIn0xTEIsYqILhL0NJeAoWnz5s1TbKEGemAYUiiVXULh2S98rl+9
Wvzo0aOHDx8+eBAQFHQ3qDY9O7DyQ8LeK3l5mzZvVoKxDMwJwDQB6+gYoZZ9AaVqiy2gVG1vvB3C
A6GBGj3MwOiCqlynA2gkVxmj1Vf/lAk0sAtu4SWqqBy0e8n7LJ6/0iOypIoYzooBtCJVGRlMIszS
o64xlHWF0WSSRhXNE9YVFS3auHEjaODMzEyoy7pSrA8AV0dBAcD0DxeEa0YDvxHAAgCqxF9YfGvi
mElGRh4T5/OedqYTRtkuqh77tH5xy9r77+Oe/eQJTNxilODDtZGzxdFpOUZG42byG6LpngWiBQ82
rexgHLVIF4RWrFs5fubKlIvZTmO//fz3ad8KGbXeOc+5BNtv+ZF3nvMufjXu8MnnU2PcdJ3WW4wC
S+ftQ9QBKYihtDyI9nE86aK8cLs/8H/9lv8eT/IL1ZX/7M4CiQ8g9y7aVZLYkQudPUSPj5L3lXH2
pkfcyJXWtYCEaJThvD/PXbkyox/toqIikCLgX5anVGERmg4M/GIC2+xQnYYhyy8FLb/o2boU6202
PjuDk3IPeF+9gjkw5uPnHivGfQlMZUWEixjeqRYmRv8t7U3gudrW/3FRyJAiVDKUShE+8yBDpZIy
lAzJlHmeyUwaKIWSkrlSCaHMMickGcpYQsg8zzO/tXXOved+1uf7/fa///O69xze9t5rrWc9w/tZ
61l7H2U8f2amvfmS4V3gKpaiugvkGNHlUY5zupaiN+45ir1ouNQXJQugUBXL5NDjh8p28BgW9011
eIOuL6Tiaal2nVqQ+3OBA6fhOVv0t8B72KazJbWW+oeAT+YIKurUWTjnPhJnni3tMz8z9yMv1pdB
byLZHfkoWaK/XtHqgsvitLmtre2/BP5ASBkYa9i/Be6IwVN5dc9f20b/rYGOrT2w9TEIKtDX+VtN
fjVJabqOVVV0IAe5uy8t3HNbuD45NSazuuoyVhVbJ5uq+UjmnuacUU2bOMA8JuflT5zYyMzMDLjG
u3eLT2X9V1dXqhBCUbcBIRQvz+DKqPaaSkz8wyM1C3N6Uz3By0n86MMexe+W9XtusvH7rER7L6X/
ipBTqOLLGfFyG6saEy9a44zyqsjtQhISY27p/LWZORDPQX60vLzMwsLS09ODvFJpbU1m3QmyIk7w
Ch7jS7W31KLgn/UWBIO8WJ/3bEUmF2evmn+jq8QHN0ktznbXFjU8sOUILloAqpMZXBSYLd2tNWPX
U5rqA7jhVG9gaqr4+qt/ZDU0mlP1itZZRhoSqUeLRKnUafy1OUfZxz/20/F6a++3/N3HCXzwFem1
VUDFbnTbXttSsLja13FzToazWWYgb3VhbG1trL3A0dkZ+fTU5csHxcRWZ4a414W4ExFiwVPhL9Q6
iKMS8f40VM+NxRYVyay//K409NAFm7Z3zlO91UTb9uWFKdPaO/zlrTHYwx4CaYtfyuX02ApWzd92
kwFxVwyTyV+ciB/5JHdzRjlHXfrxlaF6kEdjlQp7QOixrbrQJyW+Ltm9iGTtQoizVDtOLQT+IX9b
Xcnz9d0AjCMuzhBQV1XVhk8PRWQ85+1WV8STomvDH0ldBjJ3XriumS2jtzhe5Tx2FriONOWigrme
uXzkhaIySUXznT1zMo3cMgdTfPZmLN4HqUdEZEyElU8NYmfnaBA728KEH6TadyqB8M/szB0oYUYG
DmjghQv1SRqpNl6r1kXrL5RjqeJz0lkCTmLs6vVUTXUk21n8XqHHE+uJbZ+VnJvO84j1GfOZMXwf
qKyjIeOst9TgNtMdGhm7zjYtEEkfScLtpdpbKiGP8Gefp1uY6wguWltdXVob61hLyJbG/nYOq9/m
AJqUN33feOH6SG1RrPvSA+DRQLKxPu+6SG/OnRCk8vmCvzZ4/yuK5j4//hT5au76+0T19DryXMZG
fRa6M/r2/xZfhs7CPEiL3gimampIskhPL37111vSXX3TMiE5MN8aGesNgslac4ePzNqq4Y5NcZfN
aJGXtylbiH2l2k8qcYv0Rwu23xenl8qFOghSC4UDldnVyoWpPsvWNdHi6aOe4W5LU34VHd4rK9n9
7dx+xmwXw2ROSy3MznX4RGvIpB32edNV0nx2zMdZd+3DuhrSI2oo8ApDNbTiqAQp8h910X112U1V
NTQ2FjgAn6NHrwYFbUG+T0pHJyTUd20Tc6HngsNYFX+8lHg48mXC2ScrnyrCOtb8+N2q33Xp1z3V
CGtfk1xejG+s6ZuoaNdem7+zHlHpkYhqWSF8m2pnqcWmP2Iw35enl95V6BElV7M6J5pBHiv6bq3M
oMKxh1X5IVFy4sfcZHPHWp6ep6kmEm6v1yHefklmrsa0t4ftQNv89HArf8pDNksxLyNk1j+uz3qt
DYq6V6ISk/4wgk50V+Q69inFSnsBltfQoHr+/Hl6enpz84FkrWwkgQGpzpU8XZTo+vrHVBoD8q6p
hRXl/s7m1yJ8p3jdvEa6U73EfS4Ou8Y4LVcHBv+OTuuWfYMPReUkw1/lAZQ6+kcyBZa9Vlu05r2y
tLbcyu/fJr4D+Ezd1aNe9fXKRWtAaFpmM4KPeth2XylanhpbG+XuuFNTuDS7FLv8Ti5BqAODLGdN
ry9nyU2IPKPWNzy1VOzP3PvijKWbW+66m7x+7945F5c5ZBFtZa3oZzt3oKLyzkdSb9oXluuS+NkK
l7fITEZ49JT2x9mm+Czj+0a5kxWVC2aLJFZm+4p8fqfiEYgI3VVEjal2k0oY+mNXrqikFLTuka5f
vVqMvE2ywGMOuMPCodjfb9cstp+remDr/WN1WWh43LL9IRtZQ1pBZmF20l8PmLtwss/7tOVj853N
3B1ri/9Bmdq2oMSo9va/DjxAAZvf32TG4/E7d+4Mf/yYlpZWTDtnHHA3oHMtI+4lhV17StMYzgzF
KuQuDKyGdYxoSAtbuxrkTZWByWcrXO3M6NtUNenvpxWb7D7fM/TXRhEeycbFaMRHqPaWaq71Zzqw
NDcGaK+2jk5uTg5Ixz9//kyw+TEPBjEU612x20ckY3Eb6G6aZWxotA9IfceAm9Ucdq15t/y06WV8
uo2P9NKo6Wi4i4ol/yFb16/Atu6M+awblAqiDakj6DGqPaaWZ/15j7/EyZW+f79x48YdO3Z8rq7m
Fr00DdINrVifvmgv8YJZpMdMQ7Hbo718Zttqn8imzqtLNbQvZ8x9r4hL9VHVcU3NWb09WB7vHCYt
Ob/Y11H0e8XjECJjizQMlW9x/lXd8l/2GLDogfp4WVnZhYWFnTt2APrOJaY931nq3yyz2qS9eDBv
dDPoccDQ3zJujfUxjnYXypy9D2S80iwT4zqVvrzscdNZWZUgaZ2/3PmluePfPXbcgumh2mOqqdUf
Li7NjfVUhTk6OOzbv19TUzM5OZkb9BjI2LRjTSlnQt506gJwWiCZQrUsvp4arADwj8XpvK73HoCq
Ii5Ob6LYoGJqZ7YMoFJx/T88FmaU3VN93Gdn2NaNbyNifAP7iPuodpzqiuMffh1pqu+tYQU7B8fJ
kyeBtKWkpIhWLeNA+kCmRJ2FV1kThwCJ8UziI4+5oddGwzRkVnU910TWPmt9ywwGHf+ps1Bn2VHF
yVY06rkquvBBKwEf3KIhCbiN52x0ra33sj4S2+rokNiWsVGigWr/qW2sof9ozRb4uurvmZYFBQUL
8/PPX7zgYGcP4pNaHGidw455c0UtCaSPbl7/8kLsCX639LGyOaBBfK4z2NkWHpD2gP7f02LY7lMw
MZHNyVboPuZTlj34dPq7XCGDbornfM9KatG62rgjajNyV2Kcau//+800ZB+qMUnDw90dqHhObi7I
Vs+eOWPTUbjSNZQK+AQDv7tozuK25k/+5a2xYXrzdjPdqQx6q4cBzQCZQ7saW66GNK51NX+xaylZ
udBFe+VV0czOoUl/wDl32HqoXxlty50r8l5dWN9tFlinbJ8VZAypjYJALV37w70qkFAm8fuYti+w
O/VnfmkyXU7io9/tmQkYI2twUU+sW19O382G73KgV3bJnjtchqtfCnXMFi3rOk4UdI9yh1jyVSZ7
qFxZXYnh7tDzWnNcrg5+nz424lJg933K4f2Mspze2vz00NjfC9gfED8ZSZYzoDoMqltufzYZwIdX
RxKbU3R4+PnFRUSSEhJ2bt+O85gdzlPWjQIeZWRQKM669kWzNKZtVXK1JRIfXAhSob6WSH48t4yZ
tbdwYe/9b7N9aLkOhcIF85m4VHJ8BxjZ+zfDvv2DcvYV7a89x3vaaov+vbNZkHWUieooqK5n/tlk
ADHF2fqoSy8/cl0OBJMxORR7g9dbamy0zzm4UF3Pc+zN0s1fEchkvLJyDfFaHGmK73Apmtd1nrje
lsL9LIk/3Man3WmgtDK7SBr40F+NwcMXxqxcCsbJ4xZfA5VNO1YWZ5EI8I/J6FU7TeV0118Fc//d
MNxXFmd6qyPrv35taGxUU1NbWVmJV4p2H6ppi+T3/pw39c2wQyTXWVkhS6ZWesVmpTs1uHA1d3Ki
+W5rrM5cIQ5M0FRDq5uLjHjh2ovx4SNg3kga0tt1pj56VkwtY8cI0quzXRUdMv+x73/q/LFSqsOg
WiLzR7si7murK7c5hL5//w4MvKGhQVJKCqQztu3vnNfqg5Nri0xj3eLzenJ7gvrC49ttXJdnZoKL
XGTWdKf6td5PEBN5kLQ/5srkSH5eLMgymjwXrn8L6tMW4Q9IdTPKWnFbDXcBbnptfGjsb0r5GpmP
x4dPUvne0V8lhf+lcQC1Alw3mF+mvaNjbHQ05cWLnp6exm/f3HoGM4/wF455ThR0LXvktYlbuxR8
lJyxaa0fA9llwdTCHEgrJ2vysa0Tn02a79zotjVpX81fncjOEuE/2Syp8m38g/7cnWeOY9mSK6ud
zXr/3idtrzqhTHUUVOti/myHD3CXmLAOEbF8l465rzbNd65hx7g61t7NfsketeS/zlYALFtbv40j
2Es8vn3Zc7wxWDDVZ1p3bbvd+MPW9jA17nZbt8WRxQo9PZ+1vPnV5hs8sY61+Um58/qNpanx7aue
0zNzwUCp1tZq/+1xD8YpnKI6DqpVMX/2vk7gqq4zsM2OtrW2t4/29BhbWAx2d9d/+WI/sFhtOYbM
RtzEpNyarG3+XFGi5Jp+bdWYuPdyATCQ73IdAbUFjq1L7w07qq6lj3H9WEoDs9FbxW91RVqjdb7B
qmLqo2DqUoqX5MxsX7PM2o5/qZXzTznqZk61LuaPsr13Sz1z1/L0MMoFzJLTwsBkv7lI27pPWjdF
iy+YtruNepjnj4QvFYYla0jb+Kyu9A/xp9v6VErMiI22RL67g5RigbCRGtaxlr88YTpTOiYaJvO5
YMmto2pMQ3rZe3WkNlsG2X5fn42f67PBc/qsKdVBUI3if8ahpgfqX5wNa0rW0tDRGQH/9PY+CglJ
s+t8JuLCr+u9Ztg6ZQuSFuMobz272ZX8PD0bz8WZ4dZY5jEfYPLJg++X+gVtQ4KKRgpn7YEeVfF7
JhfOl3iNnY2MrgU6aVG4bI9UF/gsr0yN8f+72krFUT6N2kiIVCP5n1X0rYx1vGArMvmxqu00q/Nt
YQ54l47V6aXPrYiez0iNC4//TBpkHsuWXrky25bKq1yknD+R2/V+qSaJX0NqGSmL89db81yemQOJ
JBhH9O8yrWbJRffp6mCQIMkszfZNjRWBSQGEWebfY7klcCGJ6liolsD+WcEo4Fb+bPyj7QUegw0J
nCLqoWFhFR8+PH/+cnZGmXSld7mNrcPGe7FgaSF7wKXQSXtJcm40DJDGwvnVvtG+jr72Fe2Vca2l
xuAXfe3O2is5kyXZI8pF4jlzL/qHl+pKUwWD81MK5vVb621BjFlZmfs9M+zIaKY7zlFN6YnUwjr2
z/zvxFzHgIsMd9sSZqI8PjxbxtZ7cmQ+kj++Y/XH+LzW0EO2TabtmdoLOV2dzelj3m3L00s/k/jP
jvqEu/RVAbpVU7S2sLzUIV605rU44wLmQITPW3P1Z1VWfIdS4crEYkUHW9Gq9+IKMuNIfeLc76T/
93h8QzW7qI7nvy+FHS4pYbqG2kFzOfbIsEGnLAlT4D5el9xI7mc/HoDy27rt0OFWg6HYUn6PwC3e
/Htpr6qcYSzZERda3rrvoj+zz85tKqFqc2jeu5lOFVyTSy5zV6s8+hlCt/BIxdyotjnQJWH9edW8
VtzDTL/U2U4tSYU9xcOfpNhuNRuGbAjGl6mNUh0O1b3MP3IBwyVvt1xDbaU5t+pjd9nJZB/LgS0o
9JvSfYQD7PJ0Jxney3tkSqWs0tON5QaO/fyqG8vfod3pOHP9adjL4/qHfza8V+uynhBUkVoT+xpq
K1JsabDFl3TwucP751rp7ar8rZ9TNomz7rF3Ig236wGeIuZ1np9q//8R3ln/OtB8ytbGCfzyr+PM
qg7Oxut/YQWjcnB0kjXTd0BOarOKK+j/87f1886OAloCyFfmdABwXN/ReP1h4mdk5ZUUjotomNuY
GoH/O2KQZ4G/nDB2NHQwt3OydUDK2f86GICI6d8dJFDv4D/uZBU/5mi4fpaavH6aWt/ur/PWKPAb
ch3yN1EMGvkVTIepowDur+aPH7d1Bf1FIX9FAzUEaRnybSOdv/6spG9tjPT99LmT/+i7qIqxqbOV
PtKuvJO+lbnhMRtTK+P1xi44GVurr/+E3A5UwBiDjItIbVz/jOTUlOVvbSKikVPtv39BIzESR6JQ
pB/qzKocGrsK3Wjl3cKfaHFP0L5g2qdPS7/J8+ZWFBfjgT0qrYnyO07jKm98plFRFbi0MflRVoCy
sMWdrrhngcEjNjqSV04mnPNUM0p+p5J9ib+Rq+NJAV3Sq+S8vmFynmltTRQ5fKkD2dJbDV6m20FD
w3+O6eJl9xD1hxh0/JJEiPamo/3xTadOnmXzzt5a4CIY3m6EJaU0sZI3XTXD0bBEJ1y9FnuqsZlu
6xO6qxyx3R8zvb49rKMp/ilM01LvkHySHFE03Ldh6xW65L5Ie9nZzk1kRp6b08de79xMz+h6lobx
+NJPzvTAiBdntC9uLj63h+Y1k4g+Zrh9bFWQZtv2SZc6k8c9lwdyt52W2dr5tO1yadwug4c0t+4r
+zUeu7ddguHdB7XpwtLbRxoUS19u2JpG/03We0Pc3Esf3598i5zX2s/acThuTrEv2PtJKLRjwsQV
ZalzLf10Q4kR6rl0y1nt2kLeA/50bwa0dfeFlZjknMLsHL7E+sj3dkzIxhQ2YdaNcR62eBQt+9Zi
JrujT00PexmOa3pYyTRXRWrZ+IUFc9zOD2NT9qpWHZrk9c99HNi/2ZRp08PROGZx6+VJZs36wTLO
atnIzMU59JiQ9k6rEwnDggPnrBjDHlb2bqYftI8/aVmZKRuNjX1+WUKJk70m/OuxizSsP5k9+ehO
nDMmyj/fe/iZrWCGXr1B6dNHmJbdXB5iDV01tHc2+++69uS54Jt+aSejd7teJv66naj6cNT5oMbB
0J0SxiGMW4g3KwJv1C4WX6N3qwj8YPTVzGqfX8ohs51CgUH3Vw0XinyupmUqV0SVbHidVnZw9OHn
NIydNq3tY9M7H0LSinl/RPMseCwXCLmYtU4dYas4MSxp3zoUuE1GL8W9f0alVc9HpodNtKMjpeV8
fY7A8KeowzIO5a9TJ2ndt5i0bekIwWdGtAkSFk0fbiL0iUrtDOF0nrx1DyszO/Uiss2cQ1xPmfHb
Sz0y0TUwM9/e4NPkztF3LQ/adLu6R3MaFbiEB/vOXLvpWraU6uaPnW3p+cpQJjSUl8Xl7PguLLCS
OTl4t/eozgbdhXMZVyfaQ9XKTdYCX+h4zG6e292YGjVgrsqnvSbv//oGh0PTIZMwR0LN7K75p+fs
u2uKM2wlH72eTTeR+lX5iKiRIlVx5fXtx4YX09bYZWwbX77cbdj12Pis7DONG6pi+bEjC5+SDefO
r2Q9EXq0k6ZwXK/xaQ7XsgDZ0tvY0eGkWotz5/Ra0d52YV6/mzM7tyz24fhiQ9feP1jV2s5f4T+X
ND9vWDjt5198wTjeLp43/k1ahN7D6b2hNzc5yduitR1ttbQfqjiXj8g0OvhpGLzuOqN1iV8tP9bz
DGfR9OTm0ZwI6yFTxVz31NbnqmM9rW/5mytstnlE58mztHZJmUvIvRQzb0xonb3F3rpgfWdOySsj
LyM5/bsO+7Mz0+l8el+K62xJ45lG1p4alS9fv7uwZ77MJfvzpan4+kO3e4kfHN2voHe+7jho1jrN
IBLvZbUw7PpW8OuOXaEbhazZWM2ePZ5TlWHlWe5tmpQMN/01MlcT06HmZf6lvFmiUpYj32KXBJfz
Rs+6z+/6OV/2eceu2n8SkhMSit3xoojzh8PPxo32F52GBpl9+GInZfNEX/w0EMwqyc7IfC6lbzNS
YLzt68erS/43mgutc6IOuey7c9IRHabB6+5pqalA/2BAI/SCdWxzXVYkuli3vr98Ksbk84lN1vOB
r4pIsujHGeKd25SFjx9rscqpN0JffPro41MmVqXdJr94krm+3j0i/+re3KNfB61u4LhKY0L3FdwN
ul9W2fXysli51po9+1ejwwnK5gr6+k+f0xwKOX3eYK/VeTNajuc390adPB/AIjpy3U5iX93FjXjX
oBMnmjP3qYWdaHZ47XSY8K426HBliOXTe7Jq7KoXWfdtNnyy46WmgtK1E9sX3fpZ1c9m+aZtvXJx
q2iPoW6GtEbx54Yzmx7LFIxvHz/AcxprIRXw5uwKKrbwnKvZuBWPfu0jen3fjBv7WfqJqUd3bzZN
/VaxtMw9HEdT2pf3sWyc/vRopRN6R7GO83Cj4jefIna7n/eTL6b0tgnunby0v6i+6WRFjIz+auRr
OfyTgnc8a5dEbiy1+HcUOrfoa7nPfDRtFXyj9kUz3aW5lqVK55vr03GGmjL+I0ljVt1F2nMD/QtB
zC63iY2OjHqBDvrFh5YVaH85BWma6vCNlbJxaDOvMond9mglBTuSnOyyX5pYKlrMJHwZ0DTULmsu
MFrU6S0/0bO4ccCPYaSKz4hwm2BN2ppiM7I4Tm9pNlF9dX4xLxLba29VznNnI2eckgv94r2l3G4Z
fu+fZ6oY3BSXHK6k1N/0LK2N9nI5dr6naXd7r/ycR1RJW48t73BEvyO+amtEU5ag9FL+z7gE//a3
L7b8kC6nw0/Sc/dpfS4jt0VG76ElcNDtiPWeMU4H4hdVVz+WumM4TcXKJkHPfsZFjlOql1MmWMJA
ef722CXTRXFcyJ1Sp7jU44cfm7w3QfG9ZdA/fnd1cmgtjeejgXsobaj1xs63uTv21vIG57a8VdZ3
zUi8wxvwQday9Kx/+KFPx8rlTq7cKb/YZzAi6vj2h0T6zRsHfshrOhw+QHdT9qxtaV2Z3wOnZtLE
7h+3WxVzGHcNf6s7fh8VewLFHhJab/Ds9UlJTAeJjnj+3t4T9zDdb2QYlYe/roR04h4fdBd49uVE
J+GHUknnLXkS25d95ldVr+0R2kR/p/FyxleFmMwmHxqzJ11u4hJmtNWXDmXtwTIy3Gd4y1FbVSEf
sHvtcJDd5NZp9Pi3qIDLGYfF6F98uXrgeT6N3DXc3g6lnVtFCjaJb3+6/X3OtpZbO3RfqgfZBe2N
39+s8EVWZRc391IUmbFHXaShjpF9Zdt9swPd39hfnbNwclCTsE3TjrsfP6R6RlRBxZwzwUEtArP5
U/2DmIjShEQc565Sdr5AJY0X8R9k2zbu/9wg/FRiZ0FiRkGvaqXwTe34G2YJjeaqTDqDQ+ciw0nn
E+qORUeodw483NUo/lnD46JqBWds+NI14805tHt3FRw/qnrRhfNE3F6tK/fxVY7Hjl4XqzoikMQ8
efvSO4FjG4+dzHi46xgHa+FeLvxpxQtvBU5xvKAXLFRJXslQf0UQvoSf/qHjdnpwbiY1ay7bpa8d
a1oT5dgbFe7YWSritLVI4nAoW7DqxlMJdGqoLRtvvDoed9RanylTnYd1aiKg/9XPN6frTjbEP8+q
pdXlZU85X/RVk5OHL+GrxcKGpOLNT30jzF4IGF8Vpi2QVb3vWzL+3dT44j7+50FMnH4MJenX2DSu
Bvl+2XVyHz8f706+l2pu4UK3z1viPM0uhvabCqc/wAlPXS1+cy5ZeO+uUA0RnC5qnyrvi5g1C4XY
NP3LavtSVW8c7E3MUNFNUrm98cjNqeP3nqpuCDvFHLMFd3TUtCRkp4pfuYGFO8GKuVLe89Ges4xJ
odO/9iXv37adfG/nYs+9o89+caLad//I3Rxe9WBhOGPjreuHZbekKvdysNY9NOIKuVcttO+AGPES
BlV2WdugZuf5lJ6cDVtuqR6jyzwuvOgaUdknIz8l7f5yT6OAoqLyfc7d7FfYY8TmVU1Cwi/y6Nij
xLwT3+8uPzpulHxZQ39Hy7HoU0XnpUnyL8f69qUtYOTi9yw9ZQngHMbkBZOkW4e/Tfs+yPFR7sTW
c0yrSGMZHDpnBtnDxcPrn0TbbLfeb6iffb3j3ju5Vw1ZZld6TupVuhV9LnBjWxNIf6uvVpfIixeJ
fPS2JCjkl+MER8ypz9rZw+OC/gMiKVbzn8tx1oae4+JadU73Z6toitq/dnaHPcmVlirZlTDBn8w9
pSfMmsLzXcRyVbvROZ472nyUEDT6Q8mY90h4jsUnpp7PvPyPpMWFZ6dC279h22qLBsrYbtpMHndn
GS4Ru/zOasGnc3meWPbkcWYa6SaKJVH01YPA4bkQ/H5+zzd15wxZ8r999N99JO0tHZ157o0s5Zhf
oWsjz8qe8ih7PdSzcel8rIC9pXM49Hwm+wOpgGMDB5lfPNt3Nq++dDpoq1zqezN5PbJhUFxU/gs/
VcP3XzPyn/aw6Ny6r1gsOaNof8d8hVVkAGWYMur6Szx0rsZDPVlKwuX4zOuG12LyPQ/6ol+eyp64
YIGdFnTZNd0o2EeMXXW6pmxX1rnNgyDaVleY1XNvcHBJdzG5oGa1NSHiJH+GkcYbH+X8NZX3uNzB
O467HGy/0Ws49R9R0VJu2z3l/45bZOw7Obt6NLpf5/6dbMmpAd1s4+4DRXf1FGfrovVUc1/+rEqP
EStfzrF33t9ayPPlp/fE5w1F6at3uAtzctZCUnrLW6Jkgj4eiSwiJr8ZqMjOKQiMXbvCqYptlhNb
vfDl9b1Nc8q2jKmSiyvaSclZmm95C5oHQuYkE8WW5NtHZi+5m1x6be1WWRkQNCja46ZzfrFqi298
4BHmiU2v+mtYX9OJiH/QoxnI2Xp5U+DaXEfKh21e6NeLZy435/Qde3tyqJBJ+Ft/+8gTHvbn9pi+
ErRF/dp7fcYvq3ynbExXh8cfVP0qLLzgGS8+L39L/WV+6PfIMx4mJ7Ky2/N7cs3MznE+Luc9HORq
ImXeymyzvKfU5ZmtbW5Y9kp6dYyX90AquuJ9Y3RossdcsKkVv8TQBz1xl8cF8hfqntzLdNMbzH2j
+vz1Y7RgbpzQjKb5KiphqLWZMGZoUlMtGBht9M0mSTCYz3s41dbOczjFxTqjiJiagG/PNbt07pVK
30S+g8ZRw0x/V/9ujlMtdSgive2J8dM+sj7Xt/Y0ND/bF8AtSF8wcC3ukdwGtnmGguF9y5tDHB20
bd0F59aWLXwMg3ffu2Uov0GTRrnolPt8qt+RzaPWr5jU7tMzs0UwuUhJVsu6PCbgNu2snk4wwy+L
fLmg7R9QHap5mm3F/aeNbxP/IvvTMpOdaq4FuStkYdpvbPJ05geqe9vJAi4xxfobzC9/vyr2Ueu6
tCxxfMzXlPM7i1fF+TwU0z6Np9dfMXjQfhrXs+PezCDM1ctA3lmss2lxdYvzM/43dLMVL+Y3jp8+
7avJXWV14Kf5hozIF4yMJeEtVwNdeT/mKx7sYlZhfX6jIcT9q0LZl1UFHhH9lRyFe9e2Hdu+i56L
6evx+1wmTXHGKyqiOVc3BxWfJ7HalmU+kWUepZXc2260xVWnmOuM3J2BPAX6dOa68lOO/JpvBSKP
HXY4JukgJ335IVPvLZroB3UMZi92JtEklYTdfEXf+CzaTFzibkSdvL6SE2fbUamfvEeuXg7jj/E1
pLGnEaypOPkzOO3YwYpWezob2pWari0YrtdZAhyvs81y/VQfCP46TJYrFMqulJq8dzwUn/n464Vv
DTYW/M4xEsoM9ZnTSou7vAJLFAq+XWBv8g00raIZIluKXRfpItjz21ecUMHRDk/S5vWWkB/emiwO
aXy18WGExgjqJ6MEk5ns3MYjNAWph7eh6ETstwbRf+jcdNE/7KdV/rOOZ8rjfNr+wVdFea9WzQsX
3l7zy6vu33PYfu+DxRFmoUvsspiP6mmBVkJLe/byfNzsEP6Dhsf2QcXlONb9T3cnoEMDmGhPnGdO
4GzYNSjQqKDz4t3ltg/TVt9jg152l8yqLxK8uNVDUNu7a+YxY7RfHx8+EHvI8MrREy5ondctw5yb
j0RFV6YYW7bQZz3wqiQ7KEWJHP1USRYNq+xxWMpp/cGbRNfENORkGfeReUQWM71wb1iK6YtXwIf0
B/eZC5m+vLmbRiem+1Fqby8muV7++hPe+LKYNyrN59mMA9vjtM6zZG41xrh/8ssLHrQj6Fydu3Cs
n+Z7dU8XR2jQ4LMr2NFhhTsy8vjM4Kpupx+8ddPbMsPlu59fLAntlMAwYL7fEqzjWN4hei3c8eOJ
hoCmp+xRd16fe9i4wYo5t+l4eRfGhHuG590jFfSCK+3rnwdfBi5uXdgrt+9UzEdOg+hjW9778fwk
ttWaDm7PtUpraLX8+mFzTLfUjw57R96KYN6p2f7zYoLRciSyBEsYS3q2R5W6lWBaVtdFPz8mbreE
H9ecPAv8U2Jm7Zi3zHK1t7FfvYe69SSpz3f7tISyVCo2fSLVkZ7G9NPWGhpm06MyQll9pk8123Xz
PwWmrl0aKCd2bdr2dlw7xelO91Deapl7Ln2mvY798o9GC5dtlzeeEtDKGU6jz+O6+NifdR+9L9/V
7XddN549+mbrz+9Kg64SF7KDWlnMLew23uYMe17vNCjXte+KxSDn86xb9RHhfk3YaIUKbMIQ4XY9
w4S/woBQPNaZviHdY9OGiJyVOp2V0bUfjjXtBXOjOiMpJkRzgtYTNZW3e+Vdb/RjxhwDmDYHiJV5
ueq1cDoZeHwxui57hWVHANMei9OnsDtFy0T5A9hd8F9YykcSAzACzw1StwcPOx0KTLswcu1ZlcvM
rEghV1GV+f3nR88/Pb7by+H0hlwl+XSLQz/rlOLsttxsVhIc1fCnEzTIsJOQ3IU9ftBMcSBsySNv
JSCF+CRGsC2xoUrpxeptTcfz+nfzm0Y1QnajaUdWD41/YIgLvK5kelRKy69U5vULU0P3WY50Lp0W
43bxxEY714uqNRnzYXL7M1k2vvny7Lhtkt573aqU8+d5TyXp8WwgnPlMGH4+eMFfnkFSIE9Vefzq
q32VzpOF474Cuq9n9DddCj7NMSQ1mzAfW9LNXjriralicdjhSXM4R/UNu6H7lafyWnIwKqo78C/r
w4NS5M/uOJRQFej74rGJ+UDizQLdKItns6dtPux/dstr7+wHcREF75uXWFSP5qTS1tsxb436skLy
KXnz9kzB1kXPuMN+Mpu0GSd/dGi4u3PwiXXMH3r18p32o0e7y7mtyyzUsqzOazCNFZ+9I5XUNNhz
8qY/Z6rnx4PCulGY8YWJJ0cfssZrhzQkSbKnyzKKfLp8J7bpJKPmgWKbdPrtB16deskt+NK/8eNP
A6OB8Sd3qxYUPXfTPt7+9PJAmMnnS0PfNV7ce710g8Fsty1/2A7jmQX92KInREmDQ4x+cnSu5j9c
RfxKbTSd/K93tl/0RO27c4q8e8a91F+7pGxPWVe9IFeZ9K4WOTuVhyoSPJ8u+euZ6tM2GBx+d3Tb
q5Wf2aLzNCFyG7qKsJ7PZ6wWZjW4xncG8fgzCjf+lP/OYui38hHnOk+746w7T7mzbfFdu23lC5I7
lM+cfeMfInn37vscFF23nyUqZW3PyWpjfjmbyywdl+e5iwWjSghFwVknuncl6gR734i+YV8TXMF2
bt70oJXMyeq+lGMVe993oFI3eBWVOWqX52ySP6W3czHmOL5kRzOj4Z2+r2siJc4blz47P+0I7a/g
+h6270jWzZXet1L6TJwVFT7MbnxDL14xDFy8aei6rNRQgDJ/896eq0/JeEKbFBujpgqcRe9uHTz3
muk4r522i2+Q5pFaC6ULq1p8Sb3VYrV7yk8M038312vJot+cPMnq4za65rf10qbCVmanFZs8fvot
zUJyqblX2jSylvz3L5lcOxEtond768vDZTJalSFrR1Bxz3QNq1NO6viNevXXhz9RfuXv7cGU00by
u+tU0i5Q/niEg3X/QWXL42IqC4ceMqvWXHCL/iSiWqNCVnxx/wzdQ3dhZ9Vh1cQEydMvQpjkbr54
Fnd8uPoVv8CYoM9xm71Fx8UEZeTE9nR/PPlLclLCYRf55vLGnSdjTi3ek7oUGWZW363a/mRy10ON
hKg4h4CAB2dEH0arCr8aV51W3SF8OTtudduClAPvAuukpRF97rX82wp7ZWRrBITuCwIqIm+iYvI1
6PTd3VnEyfvpnr8YPH9pSk+S+N3uBg/3CNJ5Po8Mdpq8T8M/McVzU/LY9sK9vxiHNqXf22/EtPPa
+YuCzxnpj20l+XLu2ND8Kk29zzjf2vlDksKcL3Gf8JrVA8MPdV8T+nsknhm5lrTqmqoLv2Zy1PaY
unXfNfReX5BmQ1jQIYF93sOaZ4/TbfiYttpnont+ajEonzXXiGH84iOlydyx8cRs1oJt1Tznwb8s
D3BIH5yYDdpILObGLS+cGuXRuT/wPXVLc18w0zluO6cL0UYhrKSYJyeZGox3sqlZXvc4ipExd7uz
yYEvZOJb5DVxx4Rbu4QTRRPVZOc/qMhaNszln/i4/IsupEfUQXob5tkR3nj2IpGJby95Pqy5825R
yYqfGNs2KzXJRMPD4KVNPClN/0b0886+J738F21ExBTDvk69cDI/xzB1neXw1dXFgoBjsxJHhe8m
raEWycsRD0ror9gdp5PcKG3GIOMku3Wx0ve70+XHFii6O8Z8dhcD7l3rOXXxeo86CtM4K3pzeFd6
zts3J/QuaOtkZWZ96fk8kcOryJY9H3HkkovznDR7vxXfYDt++8eSRp/9qTavKtG/kpIVD/C9Ohb1
a7u3j9WBvjcFShjstsGBgPvhlYkspwPQPVeuH6pr+9UaofE50kAh0cuD8/kv7JuUkCpRS+e57cQj
7ySmLiRi76o1tbUXchg/zG5Sa0tr8vgu0SIldDxvUEJZdS6qX7i86HbloItsq6qoR7bI3K7cLUOP
o7fuZa27aZHZFl10xDSq2TtHQ31XX5pIYHpOXHSM774bzwKq6fEWIY+0NcmmkenVtUnGBnqPCgOs
JJtc+6a8tNCVn3p/5Sv2GIeYYRKaZnlbiY8evfkQejvz2uTk668hyz1ZqroWezU1DzxQ1c26Hho2
qPCi/2l/0Yde5SyrcZcoybxz6eeWv97Z4KPUKl4ZLLP8OGqPnrX3dFlf7JFmx7G4+/y8VnxmXrc/
36vOvn0ucyImNRaVXeTiRByd8tEUW/w5cccyUsHQ8KXSRM+DGZu540/mtzX7Xj/JljtZtDJTXqBu
3jbeeDNl1JZeZuHXTeyv4cabWrzfCVnHx3ltWKTrK8jbivZOpT7fRsCLyrKhDziFMzyqvVy5vZ4+
gRBlfo6ZR0mdwCAR081MsBY+2JJRkLHvyBG6af6PxL4xP6k2FQv9mut66TJN3xoeePhW/vwQkj71
9Cbb2eHcLDlLOf+0QvtSRQJqaMLm/ZGjPvJ5kaT+x3WO2nd3psVj3in4Ge7krejqSxhEcxx4sNVv
vwTXymDblWtfBshcLz9eOGrlkiYy4Z0XN2N1sahR2LN5vubNm0arxrg9+9EhJ6bDRkX7w2/OLmzv
FR7QNwn/trD7pRCf3uAxqeVrQ/SPy1u39tEVLFtPM73xuKbhMfO5qK+4sngP7edUhc+ft/LFMZ7e
w9DN93ILvUk54+WmYbufXZcvb5SIjL4e6Cz0AEdHytgx7CuvUsfehblXenWUVuX93YC7xQa+5+1F
69DuPvxpLSvSH/atzbG3mLOtPVzx+khjz9vCO8piSn73NMXw8rlS+p3p5oxhwcdRniXzO/mNMKYO
e7dcWzqjUNf+gBG1QrchbvvWdPRW+qWcWk32p1YfabnsMH20vdIH6F+yBfCHSh/0Obehl55+o9Zl
sbWzvo20z8xWlE2umTiinh+bQdFZqtEfjNz08dHVtG9XD9Pdkz9crLDltbXUE6sD9NJ+LAcjd756
xvLJZENa2LFvVkdn8eKmwTQaQiPjn/OntwuINbGeURSvlj+8Vy2q5E7JTjMPmusi1zmuE2RJsgdk
+WQlZJlCxUwYDU5v+vqChcxym+WG2tBXTamDOH70JI0WoaD4nqHBVpq0q5WPJljPSp4L2na4tqFY
4HuBqkxMR6+IP46BNB+WEr3MdsJWstr7pm+nHk2z1xVZgTAGrnoavrscXFQ3b0n/H/ZGcdj/X3uj
yAFd5BmUe6Pwvu4fboqSqW2Kkv9wUxSL9Phfm6IE5DD3f+6Jvn7EfE61j7Oidq7Nw4X7mOY53Weu
YSLbje8HZLGrpr0LHr8lenAw5aZ9mH8XXdtB53ORARz89ugLzo/NLcq59BTj70+ImTHwJzdxleNm
vtx9qWRoHb8fG3Q7qPtEtJHBwFp7nsBlg6/h7d1jMVPRYz+moqe8XCbYBZ/db1Cgfejlc8xG99PN
YLb3jhyHE80ZN45pjGvcKt8taJBuQcB9quLHFWz2kLjvaqpp51bKLxOdwB5udDdMTK/AfucL58e3
ulAmGkNDtJmmiaOqW/e73R/Lm7H7wJepsG/Xl7sTHxb9yl9yBM/ylexgLGm0tKQtZPPk31rWUTEV
z0OrWPIqQUUwplYuP/9A3TniWOV89InbXJ/76JtTbE+05bDbWE6VODsfq+Wt2vnsvOE98YjHA4yt
suyB7OJ3wjrlh5tVRT6i99mXhxuVnyxNcWO2c/wRNuZj8slEzixxYPeFSH+GgTC83mKYzQ/BibN0
hb2DSwFDkdIJkaneaiwdZy4M0GZ26dIl7hGzeCg2yW/QwNphb6aoPb1j7vjAXgdFY81l2sPzM0sm
QSyH5dI1uRRLLyRPO86f/aic7Emf+hU7N4E5gfp0vWjXNqnDHy7dMlzeFf3hUtv0pioDn+7o+5xT
Zu90a5W3tp6JR4WVHXGLjzFkFy37bPLdN9zG/XTwxV1VpqL5d8e4z8c51W5nM/+iESlflsH40CyX
8EVMSiupUJcoVfyA8KiyFxOszvrrcF7N6PHRCZxq4UPb7rwF79dLJw7fUD0d+PXkrxU+/NGmJ9eq
ne7VfBH9VWkw83qzJou5vvUwaol1ciVIp9sxJzj1aBZv1/G3KgYhAopfsD0ReqU2qgYVEdPakeYi
1vHRr8ZMna56Hxs7xx39Euv0yDv4wldh7+AUg0yfnzi+dDMuBnl/o7fajypevj3ee0Lo5Ou7oper
WpiyQpINhlrcGxrZ7xNb0A3TDFc0x1TGtk/ekzIIztkcQh9O83bqkCQ/xr+2NEX92aLaspwnW0dV
h9+Pq9PHR5nSLvt/3qbOrPherDPETjEq0OuSSJb8pq/alSIrO3TKI3VRS9Uadrvufg49UXnvx8dD
3HWHh49uLlC4Yy6FN+DP6vzA9lWfKW4u3b1WalrM61bKWL9OxVH2i2mz0m92Zz1eaAm5tfHL0LuP
o5YOjA47HHbxxhr3Ccy50iofM02VlWA4MfSLw/fGRh32PRw3nPZojcfFc3WKdsrev402ePb4RnvW
rWqDSNfTw1weH1q7rG/Llv/EMT8v679yJ0PuuxDvvaCzwu/4rBOvZfQ7tOUX53/PL82vXbZkZmUX
4i2x7el/E9tjn6g/1eIc8bogqXdTQ83o+UA3fHt1+vTFrf0ZKH9dtNptlsZvokrmwQkBVyacHlR5
njxshHU7tP+thLC+8bTWAYM1FTOxh4YvIlv6+E6TMyq3i6vXiTJvbr5xdmWG8fawWGzJo3GltyoK
oVyWttfbp/ZMf/hws//N1eTuAive6GfBG4mrjDUfY9Fel9obbPuUKt+aKseEziR/vnv7zDvFmHsE
b+3BltBfzz/cQMd1d79+G3eq/ETwrbTHiiEH7U5dye6aqLJ4qceJffjs2W7r1xt/MrI4zKvtFKut
26E2O6Q/WXeaYW8Y6x2nHfeDfE+bPDT98np33rC60UzI2ft5LSEO4sNE7QBl9bHBWck2LuxMyWkW
K4LknrwHQzppn5bTtGasXrHlroj9YpYLthOuebeNfIUp+JbfTtazMwdLUFPbMW0/+VyOPX5gvC9R
5ez2MC1Rde1LmxPvdW5pSDTu0c0WaTSZ6mlR6319PlFNpTfx7Td3RvKMseqDC/ihqo8iGVdendzS
Wut/xUUz4Xss74WkBnrhgsSt4+aWH4yTxA+JzbxQLKgkz4rNVjGl7uoZNlDtlDq536u6s8skrCo+
mWtserSh9MHWmIwEohpj7gONj99R278fSrLuaS9JJ4yMTu0xDypwKmz2S+Scs9G0NCzUGKOR13QQ
C2jwvBR5qtQ5QGtqXuOTRShGI4Etebr7TbmfakTRlyZ01gf7xLFY1a5Hspy6ZS8LHyfO06bYd6K3
RxS9TW/Zw80WXfnWP9m+XMlfruzU3cf3rwe+8yW3fS3FM6vN2eLrhVUCJgJeOQTePZMf8Ak7maml
I33TYnKbX1XFmziRNz6r9zKPHmE8VJr48an/De5juUuV55QFutDGF/lDTCxSq4pF/Be8tapr1IWU
m9q3p3PI3fnENDPh4jDM06Cy3+xho4rVzoduE/dSBbi1bNLN43987XliwdLQ65CKfpQgkXl9d+43
6YdLmeFTK9jNzJnhvavhvhUrTLp9HM+9Wva/evTZ1+dt04cvo4u0D/dLm76reVxRWyHqf/KQoGpv
NcuNSyrYladt0rsDGWTKzn2M+xhzT2Z7/6BlirpREjtT2CO/azY+Pmd1vPq0VNQqbPSkSl8m1t9t
Oyd3pOC48NxOLmVOT/LzRn2JuVjMs1eHPeu13y5rpVqNO3Pwq1dH7ClUnuehZ0r4gNn5/KqCcMmD
5F6hBgvyqZH3HQlai4cyLR/Xs65IHvl0ZuQRX2lz8GjrjR9HE2V3o8Z4yodktz145cG41Mlzo7B3
n0VZmMPQz0wnq217Dc8yZIbXnM865Jeo8E31wI8nJw1w1VzLocKeSuKX2VT8zhMem06uFV00Fsjk
eXzlmHLwcMKIj6yM3AgzPvC7m/is2chUd5H5j6OeWz195/SFBo9s1htL7ydnS1eLeJkI1BBcI4Kt
g1t8bj9ZeF3H7+Ul+npX6HXuku0ovtXaEr2STXa7nK66FOvXMfFdDy4RHZfuXwj5URHT9LT561hw
w0cD1piEikWczbikh9o7/ZagHZOudoQJey65basMUg3nQxke6h8sOzfgl7bzDEE14mn5TuHGc5VB
/EdlaNlK6Ox25jMrXVN6UnazJLV42xvuYdrWEq43215vyLx86BXt2asatT51F19Wn2NgmXn0tJzH
4vVTFZaHv1x3Ll6w49TeEFYcW+LxU/nnXtKGdnq5ksjLbC30WddMzmmGhu2c6ZhNImYkCwfELrWf
bbdWj8zvVZatf+0hThgJaWrOz9CRbcSnvk4rzC1v1BQZVMl+nfFxa3OX09ONTwVCKzm2+/MbGd5q
vRyC52/iuu+VMHxnuH7r8tTJpacHt8m8+mwtLzXXYy0gzLv31s9cct9qu1SRywPHjiqpvlNDV8Jj
79W+GcVX8lVNXpd9lrsnIvZOb96zhQizwr0R5C9R26vtv0gelD7N+e66TbxoRji9+dVFM8GZOvpL
yjqhKkKcByuYMp+FEUmGCkKnJgb1Ubot55eND6cpaCtLXnA64aRihSt2VWFLodmWKhbFtH2p++Qo
a9LGiwciwza7Oe75kCazWNn7PuFem7LC0eVg9uW2h/fd8CN+6g5b4szLmB58e2wc98h609tyHkPJ
+q5wrtoM15dl2LGJa0aH6CLQuY9Z176FNd9YftEnpl+L07r7uT7sUD+HbG3TInt29c3zJrKTN/jG
86dfcU5e3R3Flsx0tKaUoBA4c9FS6uonbZ2BFJyj/nH9FHp1v28pP5ev7r60v886jMF/v7bZjycX
RzuZXcV60Ckfn2gd3vr0qPR7J1Vaudt6e/RoXjWmxbPk+RyN7Fc6k9Zw4KyDr/8Z3+vCpJS2QXHG
ZpqxohvfbLb0TXaRE3i7XJXOXNtgmuLUmycxeYTfzSpcMiN08NvN1MEnj77cbo9Wnne11bX59OCy
bhiHzhHeX0ZSTh+ONPre9+WK2VAyxuObFerzSO+AEIOOVKGmWaRz9uevaikcIb8WVYhOqQJOSUOH
lHuElgMtyGqH4p+fWsa9VcrceCUsUgVve0Y0qVY/u4bG7wTq+XOu8bPSpifUnxWoKOthbu+ZTGvy
5z6/2+kZ9qi7cVGp+tfmsIaWAYFnGdlyggEHJQRdLdlyS2JdPQ687AWc3sLKJJDtx4KNIumB+vvS
7PRS/Zv5NdapnoaWa1N6tRrS0uMNZRJB7fmHHFKYJ0gaXSsuhcHVqn0OiRGCd7Bom5UmjzMRh7f4
l5Y25mbsjVLcJ92YkXnimXuG1OL87S/th8b6X7kIN0gGtF6ats0IXGstan9sd8W5v9RHkMn8lPP7
pq+e/FFraYx1+pq+ybXBk70m1e98CjQUp7RqjnW+qu49Rvvm7dWLaW857r83YR+0O1FSkORHNrt6
ndBrv/wmcNMHZsKVvat2RmZjq17unp6LLQ3bGrq/N9GhaGXfcM+WStfZl+72NyfRX7D7MBp8nZ5B
wN9si+4NedcF6fm1jaWX7qf+9LKT5YrrK74+ZsSUPc/aubX8zGEZC4HVngHZUX8fv62Zj8avixSy
D4kXpM9zHcXLFpWd4X+yOuq4yJrLE3GcWtZGQv1hkgMu/f0W6v9MbW6EKdr+OMXiN7bIKZHCbCQZ
NZZLOPSVq3/PR1qp7VIZfjzPPzIYcH/sECeH7A8QHC2+WmAp+ex04T7/KetrC92SC2YBkXcU069b
WYXrvTCLiozli+/weVykMGfbUbrc6bZIWLD6ZDXBwEgX26/8toRkubI87vZurSc9+Ir3lLO7nCvm
G7qQxKFTe73cw/TM0XYeu7suiStmDoNuqRMpu95Hv/Xt1C8t2Cz5g4leaT5n4svz4mqh7tvZLw+U
xwey0Rehlkpu8NUmuil0R1niX6DyX7Wbuud3J1nEvD9R+Pj9hzPqmcF+Hp71BH4D0RiV8C/xn0PP
KDnSfxyKmQvA1tAeeNtHNI/DPlS7lsocM57M0hGa7P/uWFKK/4PBI+QvU5ozUpcXZpcPWLEUdG9L
r2pxr58QjEpWD773KGCb5Ksgoe4ztbbPyk9f7DuiLiXyMd+c6REbj4JcVcCT64OSvlJFxCSs75Ku
AqNU4e1dHJzDox6ag9uwxYlSpvvHksauiSWOMc66Nmqn4tT26xI0LzyTdEk50q1puf1c9J43fdHq
mw5qDdrLjNPfNSzTbdjJsnHWU7VgwwOl4XjfI1yNJjlNSTRXwg2viQeoHrTaLKWLt+3PqX7R1Red
Mrgxa+OspFnNxghf3sLNzDeDxAcU0I/UNGf6OGO1eXhD2o3KHoRlXwhSxYY0ndjk0XX66zNJdJSt
/629b74m91y5dS0lYAT/gS5wJZHlbkuNrrzlAxf5W1dn6KUmSjtqGMVu+X7p9Dwh9KTyy5fIuym7
e32UkvH7YxoE6lVSr2nUfjEOG5l3ONJwVWRf3MMH0/sbBFkjo8Tm7JnUubFZe/a4xXO6mgue7sp7
9lApS+pzFp2pdrGKvmsOb/yTuZoMXNDcOa8jJ/ennH3nJ+yq8xWvXhJ27HVLwqNOOsXgjPTrFzel
VJ2hnckXtrRmiP4gl2bA8jo1uikhS1QuhK9S2E6nCa9aYrpf1bTVb8/E/cQddEOW8Qnv/Nyfr5xW
82VT48x/OXj2FS3/qwgRJWE/y+p3N4QHvFYDZF02q3W9SyysRlcmVb8rF17wfZ37c/+1zmxjTqc3
600C0FVNHSXUJJfYZX0388qOV8JmM6qsIwSBiaeJ1zQ8nG+r1gkqDqyW2p2svxg5Irh7ROCcr21I
SnOztMpE8dELx4JxL8oCOwNeWj6nbd/f0yrbyrM/wu98AAO9O9OltvtNB6V0L+zw1qoVjBoelWjL
nD3qGPmc3d+x1fWpiNSwn/k2tvlW823T3hFf6b/Gl+kfZQnODmSWYL1rWPy65+uBV8wZss5Nm3Tp
m0RX9V15L8p0uRWV0+hh1bsTnnHdbd8nyhC4m2uj+T57l1bu2x7GX9UGjT4w27ixdOCqM1Zmahgl
t0RtyyFc0YuqnNfz6/PF0orTmW7UZajZx3GxcvsRu1M/IxPFvkolt9LtS/3cFiDH/H5brP4b/vm9
408OmMycHD9f9blLoZjz/hd5x/Kvrx45NU2m2cyHiJ/RNcs9+r1bt7Rfp95u8PO2VHVmp8zRcebS
Y7cbmq7MnvEca/gspSlmza5+yvaF8zbz5feJL+hFa7g1NqYKv3tcEZeQRvsq4nlWRsH5rgXJuvzd
LbTqGzdZcrduOhvamfdsgsRnrastM/7lUrVkxocTEuo7U1j1Ii9tOv0joTHS/SJPQaS460Hucobq
MDOl/vqZj8cEiiRI5pqas1dv5Way1EYIPQ08dZsbLxLTq1ihUR3ZM7vD/GGb/RuLt6mjjHy4KfuJ
8qlWk43x6jt+FtZPnYmnfaRwtqCbO5/xGN7WvHPI1VjxWtPZ4lTVbSEGPG9Sle2MhzbtDkr2Fi0q
P9FyBM/7SLHYUeBmTPMW1WLD26c8Xi1PXg1JmDXM65bXLYgxCL+/8D57tj/KQjqq0yL7+PPEqj0T
I8R3TyJczmZcaz6F+hn1PBN1opBGLt7ijr82g+mLkzTKasJpW+dXeXTOB8Y3CYY016jZFWZeHvek
C2pPnJXlIYUwiIaTzpttYajI/t6vZn3HOv7aLxf7qs5Hm1Iyzu++Kp74ZazLpLBEVukiToov004q
4zbXYT2puObZn9WFPzXcOhRldOOXhhqrUXpr4ZdZf1Rv8T9tHWzsPhwQXOAdNFXqSDe8vIxqK/Ji
m/Lvq6xpZlic8Xr32aXZp1L7UnVnnsadEY4tKhySfMU7U9EE0Stve+xV85eVjBYevtARvN9WVau3
5rE8vWxAeu03YpLj9Z7OMLeTq7vU4MrbbR9PLfVHXC8KTwrXW5uZHugW1FweOMOdBWKKNdf3xKAS
w+y6e/ZT9d3TS8s3JxsKOGs/uHuKVJXVL15zMQ3ukvJvP3rE45C421GfoV5xrh2XFrqP+5d2845u
CfOvqHUhHRD36dBPE6taixl9syiOW2hri23WE9pezfBYz3fDpWcptlzpNsp0JjNLyAd+ezydT7JS
i61/n/1Ck1CYfywskjB/HnOx/1PMJWz1G1sScbJivtHLIuOXTxC9xud+Ov1ojW83vVjI9tt002Mu
p81ffDmXfm2Dh7XMrmqinnde8bSkzt53EfFdUzfu6dTUJ0Xt7ppeGZhcDRsY6umsPvJYukC7UIc2
F+O2SttXtRGds3uhpL9uCSXlnSu5PLH/psTK7FiPdWm64HbPmZGKYu47we34qZINNq7TLxd+0gZJ
XpSUoxO1cZJm4tOQzjlYmvxCSmZcv+fCWf83/NrW+X3TTNK7Zr+UajOUCdVLkz5xNA6e2eap6+Z0
PqLvWRBOs+ntO5P8nL0WnHeMo7RJxc3qAmGTfmHf208+JD3lic4fYM51Lb7eo+C8Wc5T1Oq9+uOH
wW5ZNQXigxFN75q8Wu18ejBdX5xipryLhUrdrspOWapd2C2lHKVT8vV2H1OHxS4XNdq7BYbbdUUr
rovEYd1ELc6w8ngGS26k1bNk8s62dB2cPB034M7z9X6HCef3lK01/Dv0RCIctLZH9pmPOvPpfRki
a2rGSmk4ZX3f9P1qkGR4zIUl9LjleUcbLWM7vm8BxUkDW5Snrz7Idn9C2pHMEUWi23Iy9YGmmhmH
1GTJ5EsMsWviA08tmlEyvP2X251D7d+L+rU66aMO2xro8eQLF5idwfhzfv8RmI9PZlxOell1SUPM
iGT3kiQe8brYvqrvk9D46VTjnriTNRdK2kt2sZk8t1aSk750v2tPjNLxHotbXGIL3q8CDpTOi6re
5LZ0PirzEadbi0nvS8In7+h9dJ4UZXRgIoabxGc7rL1I3zR9Se1wXveTG4VkXCHXQzn+Hrfi+Grf
mcxXHgX2D87sqqVvv9l31Fbk4uZsLT5OPaXJHd+EfDXiSh9JjvYPN0fsDZRXPfx45ZrXfnO+ZO/b
Xp3mnqKHxloPNsqbTT7FfdnT7yqjcNK2qjlbp7BLNfIGz7hVVhV7QlflIHfHw5DyOzebZYd6RxVX
dlwgzS+5Ge3s3GQ90r4/OKD8gaTwj/aCumDV6sg8l9uqnQPez62HNkvwML+MDaNTFLovnP+YN/1E
omv3qXTtsO2B7RaPHYx2JzOz9h54jwucS/945DDT95yaH2mv+l1DTt5M3dTDeb7rGBdn0aOMVyKi
1cwKnU4y4gFiLlPvt218W1B3Kc9RdztvVmZeM+qsLhBDKMMxXfIGTzbVKbMZZt6u1seDHAlCp7on
vA1yhMokmMq9eh/tONn34MPBqM9vtdjjXC2n0gJOM/QmHyrosQ+WuyBwvuiO+e7RvvuC7FViXSuS
wt8b5FBpWaRLIa9cz/K2hbyy+/1vx9Nh+4SXjc5ghyyOaV2IMGn1kFjwQOSZZCn/rCs7uYrt4/0t
uXN5vWNJgmc8tZm/q8idjQpob0rZ7jvFK5u+cFiprF4zKoDYOLrb9KcN9zTIpJ3aQ7dlrNk+Lfd+
Z/bj3qlMp7Zkc8mzd7tKNQ22Fz3c/txTc/La7ntX68Pty/ryyhdsDX5Nqqt8HPyh8zqJ4ZPOUEy6
yE93C681mgWPJuzQoS+6GfKCzg0TFzP56iR3SbpaHQ80dmA/+cwuf0h9iCn4VO2PR9G99beJH3w4
c966adhuVzJtP1gY5fpAZ7vO0ZnDMx6FO+IPzdeJq0l2H8s49vbEWPW79yPvxXpblbbmJ9x3Vc6c
aPLEjWRbik/58nPkq31vLOyaCl/JKtxUxJt0Hk83k/A1X+dHQ8R1zNqBJGMNl7dFfUkyb2MjfnJI
Pl7t25Z1JzLvrsLNjj2uQzEBW9ncumOYROtORPmUHKi/8phOLV+nxSRK49krlbbEiCt57Bs8uM0K
dwSJm6oaiKSdbpzmXbw37DbZ9FGsOXt7T/WD/IK73FMBclWSk1ZYvl+bgvI11fTyzjXmq6mJqTry
9YjeytfU0Is4yjNvpRkseuWMgDjDr2q3mQanL8WRUxKxz0LzG6p/JTWSJX1IP3+yulytiGSTD1D7
pEaLqmZo8hAMfrnyvTbm4nOFfYwvvfrn9lRHDu1wSyWspatqbax8w/ZwZae9oxna+e2OBw1aG5t+
HK8WXfYVV3efN7Op5opT1d6o7vz0FLHLTJ04L33r9Ysbv/ZmJDJzLj2x9E6yaZc3/6lpdgT1TFXn
RkkX84zX64Xkd8ZCw7Yh6GsN529oOcufOXXw6WZuRVOR7+eW2m/rDu49nhahj04df5FlK16kK87W
LKKE0lkz6ZSWucUxOfCor/mcx+in2gJv+frus0LL05Oubq5TW14qi3PL6PC3Zq+JySjK6K2Zz04a
BGPfPh6OPd5T3tfwxmzWLeuTYG2g51JMZJtGjLI1X69JZnTH28jVoYGehe76Zv5afmllfmkpLy9P
b/fcAjGx1KmhocX4j471ZUc6BruW32kQ71RZvmldrddpm14snautVa7uGmu+wvE4Jr7KYk+2b8/I
J2fzPialjlixsfhUUa/F5EMORcMdwphpL7eS1lI5us8SQrUPSDKflL2Wx+PcZoto6GhK6+5uoxqM
sf8KxhjiP4Mx7s+DMZ5KMO76im/CYnFvztXhG7C4tzgNRvtOTB0WhUKpMMr3ft2EDvy8/finDYAm
hCUzDFLt2d+nXnGkf/aL8Of9IlIlCUfSdu9hOTmlWfaaRnBCWUdpd6HwWPHbqp4VIa5phq1e/u6V
Qwn1Fjpi7F0zI3383B0yq4WFumu6QYE+WguChlORXpigjoR7+rZtS3OxGi/qT1aYnRl2nTyg+n1X
QHSNi5Wp5yhu4fLkce5Q+UdymzzusN8X3xx9R9Ip4vLe9n26dqfCQxezXradvEAY3fPQ6vVIRlG/
SpFn6X6eGubdYo/vvOKffGlRdU3uYH14TtfmjyxNN3Lq3AQveP5UCqvFCJEubl18RO6e3h0Zhbdn
rck7GW7vz3UzxqxIc/u3vgL399ZCmlgjlZDOmwUFv7TD9RVzOF++51Ct9A/HBglPgRuNBS8kvmo2
ySheku393K7r4F5HSm+Rlxh0KH/6wLNhWcFF6Gxjw34Htag0q0e6U2jPUFJ6gbB1W7WUtdZ3hu1B
0ZJqNa6nhKM1O9O2VR6YDVCO9YrS/H47yt7qRXK17pe6StlulrG7+8gJEoFnMLu6NrVLkLtbKmV/
KcgKFlRaDkc/mLypW7ST7JYY1Zn8EFuY7vDy6cP4T+GFBUZafXdSQr6jQwJujeCEP8m+uObhoyY3
lKDSWXdW41KSCmk01V/pZlhgjbtFu9PC8Mtr5vGO5U8jw2p2+l/xk3ho7m4aj3uk+9HYsI+luzut
JpC5MNOxXN86BmPq3mfCaVdvdD+65GLR1wyOxPnWcyEDjYsMCYObsisLX+J/msVIpWs48ZvFd6/u
mMLtzk5I4ma3CDAdVPqxa3yZ7HxyLuhs5g3/4WhNe9oU9ngCxjwq61Ijc3aqgvl3xrCLjw4zeL/J
1C50aEUL2e6v9R0rnNw398HwPtm+mM7CtU9KZWo8set0OaYz/W4ynY9W5CApz09j3lr0bJHXq4vV
YToSXd/fRFgRBw5GXRk4yOfSiY02y+d1zdbyKlvq8z41eXDgxY5fyRvYnqzofOEMKpAq9Tg05ytX
/djLyuvY1BOeB/m6FhJKWTNXBW3HxrFjhxXW7tZO4sa9dCctsDfU9SJMQ723qq/y3nVoacFmdUl9
1rnmj2nXGVI+aN8hrDO1bT8fm2SwyymHzX4uIixSioqmp7uNFd333lWsFizzGB7YKRM0ty/Xos3z
XiG+PNua2ZLP3R1ne2iqM+B4+9Ppm6kzyW6qqRW3RLE9dngBNo8JTp2Jj81T7w9lv9Y/IMTm9TDz
rkhQ1Ix2h5JvhfxFJZkdUk2GZ6dKno2n7AqjDeQ4uOnia4MMn5/336r4OJsPk+bP25m13uJYLi51
eNikmroZw3w3XZMRJZ359OLUGw5+2VOTbrueHL82MSIYnEJWDTs/Tqo+/PTJOGY7PhfLr9/4iS8p
+4fF+8vqN9REKmzaWCJM3+w0etqq+0D6MUPe3oywXLWAXqm7sVp7PvHxmqYwjjw8n5+1rdrFo1vS
6FTruyehLSSnso2uKaLnSttaJWvzHHYTY15uE77iWPYZTZBP0h438lVPTL/380rELfanMVduaiyb
jzQPLaUiac5YKdssVf/19+FxNPKS4X/gpD/3YGQqHszq3jHLUhTLzbFFzrEc3penUwyPND9Mq98S
dy36bP+pMxoXMS0dqSPPXxjLCkihFtvTX6GZz7UwJFz/9an0xY3+m4YhnMN3ImYansUOpl8eTHD7
JiwtxH5R77u41M8vW577Gj9V7TH8eavl0NnH598r0YlJbW958ObW8wDhMyK2BTzoUWWZPMP9fY+9
bx/SCE70bLZvD0JPfKo9gP3CbfAwhV3v246dHrtnb+agFw+U0bxjp+2rzQ7SKbyV5kimKeg+UTtb
kTlzP8+jOdLw7p2SVpkk0w30NE95FT9Tld/fdSYYNO4f4iP/+cosmdrKrAoKT2hIR51HEbH16W9Q
KHXGyh7MOcZDfV9Pyx+Wb2SpBJHrCxaHx2v8I3J9xa+HLlVGeT9U4N1jEs/wTOz1FzhZ8Iozd5FX
0EqycOyjNoZ/fS0U/PAP9B+JLqv4OQdbI2dDMIqDxwwdbA30nQROmDs6mVtZAQgvhhLDC2gf1DAH
97o4ah86xCp+zNnJzBZcvbpGo0ijT+NAY07jRGNGM0AjQCO7/rsVQIxpHMClirZGJ4BgBA6ekMCg
UBg0Bo1FPmOCJYqg0EIolNCh9RdIWBgbOgkclFVWUDgpqyqvflJA4aSq6kkV8EdZMBonc1sbKg/B
okj/foiquZMVuOC0rZOxlaOogKG+g6OAo7HDFXNDY8e/H2P7jwGeO3FKUd/y9/gETMBfNGwdjA79
Z5kR+Z/vIPldNqVo7KRvpO+kL/Dv115cVFT45zuWiP8x2ZIyrnb6hpbGTgIGxqbmNlJCQgLmRlJC
GnhFlKKdrLGZ+Wl3B+ML7kqqhu6WhmQjIQEDNydjRykh8CCCkIy0pIORiYTKiVMCrtZWNo4S4Dcp
ITMnJzsJcXEXFxcxF6yYrYOpOJpMJoujMOIYjCi4QtTRzcZJ31XUxlFQ6K/7zC/+6zYbRzF9MDxj
MUNba3Hzi+JoMZS40O92/i4HA9IW0DewdXZCerv+AOp32xmZgNux4n+3YveP3v0PF4KfJP45o1JC
yHyKosH/sKoosgQGK4EiXfp93V+a879d8rfeSgn9T3r7t9oe+n3Db8WVElLUdzB3MitNEJDVd7Ay
N3b4R89s//E0qkry+9p1fZMSoqpvv6/4S62lhCC1FhKXZvqvJO6qb/d7wv6SOPj9/7xQ3+73uIz/
N2EiVwF5m5u4/V9X/c8SXH/GX+bxvzxFWhK5cF18v9XumJXT7x+szJFhSVjp25hKCbmKGhmb6Dtb
OQlJU5WxpPjvW6R//7D+EPF/PBn58R/i/cOmoKn6H5v5j2eLU0zmn0+vnbOD1boNGxmKG1sZWxvb
ODmCmUP/a4qNDP/kWiNDCcO/lReeGfBXp/9VXcEFRv/u6/+kseJ/OSPpfzs14CqlhByAo6K2gUnG
/TPG/Paf5/RNjR3Bb2fNjZA3AKHRqN/f3f0dJtGk31+qxaB+L65i0L9f9YPB/v05W/Rf//0L//uz
yZi/PhaMVJ3K2jrbOAmsV6qe03cwXv+Z/NcHj//TvVN5pxFl/34PQgX5gfD3D0SKppCk9T8fTOVd
RBQPxvz1TV4MCfXXf38/HvMXYcD81RwWhf7rv3/9jv7rd/Rf32LGYtD/xcj/8VKh/6GDWMxfDWIx
f/3397CxuL9+/+uL8Ni/voWOxVOKhfh/dMPVwdiEFYX8DSTXqH/9I0DA47F4ARNWpvVfyWgCMgXr
f7H5F0ZCSpr/E8Osv8eaAsMgvafAcMiXlv8Tw5PxFNchLz5GPuJDgZFxEEZAU7aLvJwUUUwKDE+E
MSIJwojrryymwDDICx0pMDwO6jORiBjIf2Kk9U8YUmCQXJC1DhQ0DhIRBY2XREZD14EJIUAYlkSG
MDwJGhuZSKYcG/LFbsp7EdJI2WfkYxDwdQQi/DwyDroOjYbmEo3G4ijHhkbjId1Ao0kYSjmjMesf
1aXAMCjK8aIxOCrXEUjw80gwhl1/zRkFhiFBfcbi8fB1REj/0DgUpENoHBaaXyApLCQ/HAnSFzQe
BbeBX3dhFBieAMkFT4J0Ek1Y/4wLBYbBQvcScHhoLgkE5GMMFBiZ0vbRaCIa7gtIT2AMtl80kUjl
OjJ8HbA3SFYkHBnqC4lAhmRAIpEh+ZHXM3sKDAPZIJqMh3WcTIJ0EoP8C8LQZMrnYVCw7mKAvVHK
GQO8LHQdYlwQhoXmHIPGw89bXximwDDrBVIUGAbyLxgMDvKxGOBKoHYx8LwBL4mBnofFYaGxAXdP
KWegpViof1TsDYPDUMY3gOFx0HzgiDhIBjgy/Dw8mgg9D4QKGCMQKfUP0CpYpgQUpOOAdqEgGYCw
DfWPQEXXiCApgDCglRCGQ0N9IRKg2IghkqEYhSGhYX0mYaA4gyHh0dCck4hwG2QU3AaZSp/JWHgu
yQQMfC+JQDk2LAoF+WwsCgPFHiwKB8UAMBtUMDI0NiwSMSEMA/khLBoPxQAscJSUMsWiyThoHMBY
oeswIDBAGBHyJVgwRdC92PUkgALDwf3DEiBfhwUUBMJwKGiOgElD/gqLg/0QFgf7ISweBfcZT+V5
wDxgjATFMiwBBfkwxL1AbRAIkE5iAY2AriOuv/GfAsNC/gAL1B7qH5EIy4qEgvtCwuAhHQK2BT2P
RIRsAUwRGZIzIPMwhiNA7ZLh2IMlk6E4g0OtJ5QUGA6aNxyKAPk/oC546F6EhUAYDgs9DxAT6Hlo
2C5xGDTE0XEYLGSXOOCMYYxEopQpDouC9B4HEjiof0ABYYwE+XEcDgXlHzgcBtJnHA4H6RAOUHSo
LzjYZ+PwaEhfAO2E7A0wPVimeCLkJ3F4MjxHVLgjjoCHZU8gQNwHRyBB/ABHREE+B0fEoKE+E7EQ
r8MR8QT4XiIU93FEMmTTgHpD/A+4JnjeSDBXATMExVUcCc5DcSQygfJePAislLYFMCj/BRiUg+GB
XCh1Fw8oDaVcgJeEeDueCHMpPAkFjQNoM5lyHMDFQnqAJ+EhH4EHuS6lbgA6BPliPBnOwfCA7lLO
EQGLhmwVYFAeCjBIBkD9oPESgPwo9YUA9Apql4peEajoFWB/8PNIKMgXE0gYAqWsCCQc/DygV/Dz
iJDtE0gwzyaArlDqCxABFr4O5mvAUiH/RwQBmPI6gEHtAgyyc0AnoZyTSIbzChAZIZ9IJBOg9QMi
mQTlECQUzCeBOkM8m4TCQnktCL9QnCGhiJBPJFFZ8yDh4LUWEkiPqGAQPyWRcJBfI5FgDkICvoRS
n0EKC9kg0HAo/yBj0ZCsyAgZpcRAPgNjeCh2kwGdpJxLgMF9IRMpdQhDZa0PpLoQf8agAUyEMUou
j2CU48UgSRMJwiBOiEESATQlBoYGPY+IhtsgYijzLQyygUrZZ9AIpW4ADJIpBkQZSpkiGCVHQjBK
PwlSbAJl3oik3ZScAWBkynU9kHajoXEgaQAVjNL/YbAgpkDXESGujMEhiygwRrk+hGCUfhek7FhK
HwYwiAODlJ1AaZcIRrlWCjAimrLPoAlKOwcYgZInAtGTIFkBDJIVwCBZ4clkaM4JKFjXCID0U9oC
wCC5ELDQejHQejIl58KAdIbSb2AIwFYpZUogkyhjN4JBsidiobwbqTqgXCvFgNAI6RoR0EnoeUQ8
JS8BBo2BdIhIxlLmJMCiUZR+HGBoyI4ARsnXMCQCmXLdB7ArNGRHgJZQci6AkSjzUASD9A+EWgxl
n8kgsYUxAiUnRFbNKOMHgkE2TSZC+y6ImUN6ivhnCpliUUiCDmOUuQvAoD0MLArEMjIlhkdR2jkW
RYLsCGBEHHwdkTKPwiLf/cVDGIGSN2GRJAy6DiRc8HU4ypiCRcPrAgDDUOoGFrgmSAYAo/TP2PVA
SIFhgPekbAMDr91gAduFxoYhYCj1GcEo9RkLFJpyrQBgJEr/ggWKSsnvgZZC+yQAI1JyZQSDxgtU
iFInAYan9C8AI1DaAoJRckeAESltC8Eo4y/AoH0NBKPkGwAjU8Z9BKP0p1hExSllDzDK2A0wNKW/
Ahi0DoJglFwFYFhKW0UwSt4EMBwl50cwyngJMDwlf0EwynVqgBEo/S6CUcYjLELl4XFAPAKLrK/B
4yBR5uIAg7geglGu72KxBGjtC2AQJ0QwyngEMAyszwQM5T4xwLCUnAHBIB+GJeAo9zAQjAiNA1Af
eBzQug/ACJRxFcEo1xkABuUaCEaZdwOMhIPHQYJ8LBgZJTcDAQXKjxCMkisjK1qU8RfBIN+Ehddk
EIwyTgMMjimAO8L6RyTBukZCUXI4gGEo82mA4WCbhvf9AEaCZUqG1q4BhoF1Eqgz9DwQa+HngUwU
wsiQv8Ih22MQBreLQ0HrAgDDQz4RRDdKHoEsy0O2j0NTaRcN7U8DDA/5TpCtQvMLeDs0vyCThHQS
hyQ0EEaEYhkOA88RDouCx4bFQH4IB+9hAAwP6QEOSV4gjEzJJ7E4OBcCGAijEIaH4hYOxDJIVkBN
ofnAoyn3YgCGpVzXQyqXqVxHpHIdGb6OgIavI2BhPQB+DZIfgcocEaA9UhCm0bC+ELFQvETWaCF9
ATQbfh6Zcv0UYaeQreJIOFgnSbB/AfQA8iU4YPswhoX1lIyHuAWOTILGAdg9FQwDcVvAbCGOCRgh
xK8ABYF4BLKkD2M4aD5AlgzFCqBBUEzGwzVeAMNC/A9QGijmgYyOCkamzF2QrTsoTuOBd4L6h4Vy
F4BBawpIxk6ZlwEMA80vHhgc1D9kQwDCYE4I6BXEI/AAhNrAQ3vbgF6hIH8AaBjkh/DA3iC5IIvI
lBiI09B4AVWG+gLybmh+gcuGryNDOo6H62kAhoN8LJ4E1WUAjATxZzxImaCxkaEaB4DhYX0GaRR8
LxnCCChoXxxgOEjHCSgi1C5I/SDbJ6ChPT6AwdwRoaKU4yWgSZRrI4CKoiCZEkBCCI0DA+3ZAIxI
uSYNMDKU1wJqC8VLAhaqE0ToLvw8QIig5+GgmiKAYSE9IMD1awhVhuySgEdBeQVQeyhPJuBxcF+o
5Ckg04XnA+TOUF+QgUAYtJ+C0HH4OiKcDxKIGMiXEIiwH0f2haA+AyoP9ZmEhu8FqRXUBrA3GIPz
XwIZXn8BDBgeBxnmygQykcrzoHozkC7A3JGIwkK8GLgrKA4SUdD6KcDIkA0S0VANEBb5DCvlvIGU
BOJrgA1BeSNgYZT7UQDDQDZDxOAp9yrX0xmoDQxU74glIitJEAbVOwKMALcBkhdIViA0QuPAwfpH
xEFrqgCD+RoRkBpoHHg0tGYE1BmK04CuwTKA60oBo0ZB9kskYCD7RbaioT4DQ4LaQDYmKTEiGuKE
wNwgv0YEDUMyIJKgOI1sV0B9JmFhGZDwlPuXAIP2YbFEMoqyRg5gUB0PwHBwX8gEKK8lkqF1apAS
oyGeSEJBe3cAg9fcQDoNtQtEAN+LFEBDGB6KKSRkF5cSw6AgnSRhYO5DwuAg+ZFAzKOcD5DuQz4C
aB/kS0hY2EeQsDD3AS4Wyo+ABUJrDwj1gTECFGdIOBKUi5OAbUH9o7LWR8LDXArMEMTbQaYB+V0Q
FqC4SiJAtUwAI8F6QIR9IomIhewSKduE2iDC61IkEgqeDxKGcq8NYRuwrpFgXkIiQftqgNCgYL0H
IQoaBzAZaH7JBGidH7A/yMci5kspA4BB+SUZBdWWIRjEacjItiuMUe7JAQzewyAjYoAweC0IYFBO
TKaSX5JRBBQ8DgIkUzIVrgwwyIeRUSRofgEG5R9kFGxvAINyYjIaBa09kNFwnkdGTmzAGKSnZDS8
TwIwyIeR0VhI1wAG+SYy4CDQONB4yN8DDMqnAWOFbAtgEGcgo6E6AASDdBxIFFrPQc5vweMgQzkJ
wCD7IIM8BRoHBo7nZAwayu0BBsUtMgYDxUsyBgP5HDJIOaFxYHCQLyFjoLMoyBItxKUABvFOpIwM
HgcB2qMiI0XqlBhcTwMwDLQWRMbiqGBwPCdjodo3LBlHRc44Km0A9YPkgoPOGwAM9p1kkINB1+Hh
NVoyHo55ZDwetjc8EbZVPAmKeWT4rBHAMLB/IWBhWRGg81ZIaTLs/+C6PiyZCK/pk4kY2N6IcI5I
JkL1OQAjQusMZCIZ4gxkErw/SCZBdQAAw8HjJVHxByDPg/pHpuInyVAdI8Bw0N4EmYyH9jTJyEAg
jEzp/3Ao+OwSbl0MEAbxRIBBtbAAI1P6dhxy0osEYdBePg4Fc1HcegUgJYaB9rsBhqHMEXFI9RE0
Xgy0b4pDwXVkOKQaAuoLFtI13PrqJoQRKbkebr2HEAadLQUYVB+xXn4PY2RKn4ND4SGfDTAcLD88
tEcPMKgOGWSrUJwGGIZynxNgeFguBCIlDwMYVNuIQxHRlJwBYDjK9Q1kG4zS/wEM8onA60L7zgDD
UvI/gEH1sTjkDC805yQyZUzGIdQHxqjImQzVjwOMBNkMGgWdwQIYlK8CDOLtOOTQMmVf0OBxlLqB
RmMo14cABu09AYwI2QcahBRKfQaZC9w/DLT2DzACZazAIYfJKOcNDdd44ZADTZR6gMZCa+sAg+pL
cMjBGKgNpBUIg86hAQw6ew0wIozhUbDs8RhYfnio/gBgBMqcCYcU0UPjIEBnNwEGrbMix2cgn40m
ECk5Fw4pAoeeR4TWWQGGpaxNARjEdwEGrY/jkAJt6F4ShpKv4ZAia6h/JKhuCYcUSkPtAtIPjQOQ
OKgvgMBAbZChvRikTBXCMCh4LjHwPgTACJT8GWBQjAdJMgqyXwwVu8Qgp0wgDDqHi2zHQ34SmCVk
bxgMxP8AhqfkBwCDat5BhILWfZCoRZk3AgwH+V0MlgjFZAzI0KF24XOGAIP2lAAG1UYBDMqtAAad
mcJh8FBtPMCwlPk0wKA1QaTEgTL/ABi014ZDav2g5xGwsKzg84gAg/gawMiwXIAaQP0D8RKSFUgv
4etIcF9IUL0tDinChXQNuGz4OiIsKxJUm4cDGk65DoJbL5qFMGh9A2BQbQrAyJBNY5GjExAGnQtE
tIpynwlg0LkTHIi+UF+waJj/YdHQ2RYccv4XahcNrUvhsBhorX69/IVS1wDthDgmSFchmWKx0NlD
gGEh+0AKAKFxYKH9MhyylQ/1DwfVsAAMqpHDIbWc0Hjh2kscUjAAPQ+Ph3QSOX4JtQHCEdQGAXpP
Ag7ZhITGC+wNapeIguIbsoEEXwfVbQKMSLkmCDAyZX6OQxbSob6QoHpvpAIXniMSleeRMfC9ZBwU
f0EEgLgFSEShfBAkXJCvQxIayr4gW1mUz0NINYQhb/OBMAzkO3FoaJ8Yh4PfZ4RDgjfUF/gcPQ4J
FpRziTheSrkgTgzCsFB94np5GIzhIQ6MKAyl/uGw0Dlr3PqAIQwLyx4MA3oeEBV8Lxny2QCD5wMP
584Ag3wTlfo1BIP7Avgu3Aa0PwgwLCwDPLQWDjCo5gnBIP6Cw0NnTABGgPgGwCj3xhCRUq5xIxjl
eizAoD0WBIN8Dg4PnYVCMChG4QgoyI8DDMrZcQQ0xOsABvEDHAF65wXAYN4EMChu4QhQTSWCwfZB
wMP6TIDezwAwAuV6HYLBNk0gQvwAWe6E24D2y5Dj8Si4DTLlujwOB/w41Ab8bgeAQefoEQz2L8Ck
4TYwsN8gwrEHB5/vARgOikcAg30dEQ/bORGqpUMw2M6JRNjOiVB9LMCo6DgRWjMHGLQei2CU69k4
5FVX0HUkqP4KYNCaKrISDvFigMG6S8JC62E4KvwUZFFQvoAjUbFVwE8hmZKxsJ6SYR4Bsm4oJuMA
badsFw+fCwQYFkX5PDwKetcV4p4hGeDhPX+AkSF+hbhxSrng4bpwHHIEhlIGeDQBshmk1hRqA4OC
5gNkanBfALel5Jh4uH4cqX6B28XAuS4eIeQQRkWmWBwU3/DwmUckHEE2g8dCZ1uQN05BcRAPvwsO
CWVQDMDjoHfvAIwExVoQ8iDfiQeTBF2Hp9IuHjqbATCorgpgJIizghAKcWA8gYoOwe9tREIt5K/w
8BkYgMG+BAnJ0L1E6J0m668vgfpChPatAAadm0WyFPg6ElQvj0O2vGCMSOV5ZMh34slQTQfAoHcc
AQwP+Rw8mYqs4FohHJUzxgi1QFHeixzBomyXQITe/4KEX4h3gumAbJCIJLswBsVLIh7aXwUYmnLf
CmAYaI0MmV7K+SUScFCOCDBoD4NIIEL5KpEKtwBXQXEQYNCaG1AriMcSSQRID4jwO2GQ1WLIRxDJ
/1Ez6+Sgb25l7MAqKckqfsHc3Xj99a6s4vIntCRBlDLBko0wWALZiKxvjCGDrBaHMsCSDYlkA2N9
kvT/fYUOq7Q0q6OTvoPT+stj0UQs6/79J5VPsf4/UEsBAhQAFAAAAAgATn6lLoSLU3vqSAMADKYH
AA8AAAAAAAAAAAAgALaBAAAAAFRyYXZlbCBJbmZvLnBkZlBLBQYAAAAAAQABAD0AAAAXSQMAAAA=

------_=_NextPart_001_01C32FF0.E5BEB845--
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Wed Jun 11 16:21:44 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09420
	for <sigtran-archive@odin.ietf.org>; Wed, 11 Jun 2003 16:21:44 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5BKLG032489
	for sigtran-archive@odin.ietf.org; Wed, 11 Jun 2003 16:21:16 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5BKKom32316;
	Wed, 11 Jun 2003 16:20:52 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5BKDKm31931
	for <sigtran@optimus.ietf.org>; Wed, 11 Jun 2003 16:13:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00482
	for <sigtran@ietf.org>; Wed, 11 Jun 2003 16:13:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QBw9-0003JB-00
	for sigtran@ietf.org; Wed, 11 Jun 2003 16:11:13 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QBw9-0003Iv-00
	for sigtran@ietf.org; Wed, 11 Jun 2003 16:11:13 -0400
Received: from alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h5BKClB3027364;
	Wed, 11 Jun 2003 15:12:47 -0500 (CDT)
Message-ID: <3EE78D3F.40004@alcatel.com>
Date: Wed, 11 Jun 2003 15:12:47 -0500
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
CC: sigtran@ietf.org
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
References: <20030604175601.74616.qmail@web12804.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

I think this problem can be avoided. Suppose that messages are
transmitted in this order:

Type       FSN   stream
---------  ---   ------
User Data   1      1
User Data   2      1
LS PO       2      0
LS PR       2      0
User Data   3      1

The User Data messages arrive in order and the LS messages arrive in
order on their respective streams. But there are no guarantees about
their order relative to each other.

Tolga is concerned about the situation when the LS PR arrives after
the new User Data message. For example, say they arrive like this:

User Data   1      1
LS PO       2      0
User Data   2      1
User Data   3      1
LS PR       2      0

Does UD message 3 get unacked and thereby cause link failure?

Here is what happens:

User Data   1      1

    Message is passed to MTP3.

LS PO       2      0

    Mark RPO and notify MTP3. Buffer but do not ack incoming messages.

User Data   2      1

    This message goes into the buffer-but-do-not-ack queue. The T7
    timer is _not_ running at the other end.

User Data   3      1

    This message goes into the buffer-but-do-not-ack queue. The T7
    timer _is_ running at the other end.

LS PR       2      0

    Notify MTP3 that the RPO has ended.

    If MTP3 wants to Continue, then start processing the queued
    messages.

    If MTP3 wants to Flush, then M2PA should not delete all messages
    willy-nilly. It should note that in the LS PR message, FSN =
    2. Therefore:

       UD message 2 was sent before the PO, so flush it.

       UD message 3 was sent after the PO, so process and ack it.

tomG.

Tolga Asveren wrote:
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> 
>>Tolga,
>>
>>Yes.
> 
> [TOLGA]But why? They are sent after local processor
> outage has ended. The sending side will keep timeout
> information for such a message (T7) and because it
> won't be acknowledged, link will be dropped.
> 
>>--brian
>>
>>Tolga Asveren wrote:                                
>>                                (Wed, 04 Jun 2003
>>03:51:49)
>>
>>>Brian,
>>>--- "Brian F. G. Bidulock" <bidulock@openss7.org>
>>>wrote:
>>>
>>>>Tolga,
>>>>
>>>>In SS7 flushed messages are never retransmitted.
>>>
>>>>This
>>>>is because they are old and stagnant by the time
>>>
>>the
>>
>>>>Flush_buffers is issued and must be dicareded.
>>>
>>>[TOLGA] Yes, but should we qualify also messages
>>
>>sent
>>
>>>after local processor outage ended but received on
>>
>>the
>>
>>>other side before LSPR (because they are sent on
>>>different streams) as "old"?
>>>
>>>>--brian
>>>>
>>>>Tolga Asveren wrote:                            
>>>
>>   
>>
>>>>                                (Tue, 03 Jun
>>>
>>2003
>>
>>>>13:18:29)
>>>>
>>>>>Tom,
>>>>>
>>>>>[..snip..]
>>>>>
>>>>>>If M2PA receives a Flush command from MTP3,
>>>>>
>>M2PA
>>
>>>>>>SHALL discard the
>>>>>>incoming messages that were queued and
>>>>>>unacknowledged during the
>>>>>>processor outage condition. Furthermore,
>>>>>
>>M2PA
>>
>>>>SHALL
>>>>
>>>>>>discard messages
>>>>>>in the transmit and retransmit queues as
>>>>>
>>>>required by
>>>>
>>>>>>MTP2. 
>>>>>
>>>>>[TOLGA]So also messages sent after local
>>>>
>>processor
>>
>>>>>outage ended but received before LSPR will be
>>>>>discarded(?). How are they going to be
>>>>
>>>>retransmitted?
>>>>
>>>>>
>>>>>__________________________________
>>>>>Do you Yahoo!?
>>>>>Yahoo! Calendar - Free online calendar with
>>>>
>>sync
>>
>>>>to Outlook(TM).
>>>>
>>>>>http://calendar.yahoo.com
>>>>>
>>>>
>>_______________________________________________
>>
>>>>>Sigtran mailing list
>>>>>Sigtran@ietf.org
>>>>>https://www1.ietf.org/mailman/listinfo/sigtran
>>>>
>>>>-- 
>>>>Brian F. G. Bidulock
>>>>bidulock@openss7.org
>>>>http://www.openss7.org/
>>>>_______________________________________________
>>>>Sigtran mailing list
>>>>Sigtran@ietf.org
>>>>https://www1.ietf.org/mailman/listinfo/sigtran
>>>
>>>
>>>__________________________________
>>>Do you Yahoo!?
>>>Yahoo! Calendar - Free online calendar with sync
>>
>>to Outlook(TM).
>>
>>>http://calendar.yahoo.com
>>>_______________________________________________
>>>Sigtran mailing list
>>>Sigtran@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/sigtran
>>
>>-- 
>>Brian F. G. Bidulock
>>bidulock@openss7.org
>>http://www.openss7.org/
>>_______________________________________________
>>Sigtran mailing list
>>Sigtran@ietf.org
>>https://www1.ietf.org/mailman/listinfo/sigtran
> 
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
> http://calendar.yahoo.com
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 


-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
* I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
* to advertise or represent its position,  operations, or activities. *

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



From mailnull@www1.ietf.org  Wed Jun 11 18:08:05 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05745
	for <sigtran-archive@odin.ietf.org>; Wed, 11 Jun 2003 18:08:05 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5BM7dI10613
	for sigtran-archive@odin.ietf.org; Wed, 11 Jun 2003 18:07:39 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5BM7Jm10236;
	Wed, 11 Jun 2003 18:07:19 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5BM4vm09635
	for <sigtran@optimus.ietf.org>; Wed, 11 Jun 2003 18:04:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05399
	for <sigtran@ietf.org>; Wed, 11 Jun 2003 18:04:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QDg9-0004RS-00
	for sigtran@ietf.org; Wed, 11 Jun 2003 18:02:49 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[RbtiY2gD2ysEQ+k47TDWgPDZ+LmVTaB4])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QDg8-0004RP-00
	for sigtran@ietf.org; Wed, 11 Jun 2003 18:02:48 -0400
Received: from ns.pigworks.openss7.net (IDENT:GocH4Yz4jYRtoDpYtW9BoCercCFGzMmf@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5BM4qX07321;
	Wed, 11 Jun 2003 16:04:52 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5BM4pD07619;
	Wed, 11 Jun 2003 16:04:51 -0600
Date: Wed, 11 Jun 2003 16:04:51 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tom George <Tom.George@alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
Message-ID: <20030611160451.A7104@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tom George <Tom.George@alcatel.com>, sigtran@ietf.org
References: <20030604175601.74616.qmail@web12804.mail.yahoo.com> <3EE78D3F.40004@alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <3EE78D3F.40004@alcatel.com>; from Tom.George@alcatel.com on Wed, Jun 11, 2003 at 03:12:47PM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tom,

Send LSPR ordered on stream 1 and there is no problem,
because then the race condition between LS PR and DATA
is removed.

That is a simpler and more direct solution than expecting
the receiver to resolve races.  It seems rather pointless
to intentionally introduce races when SCTP provides an
ordered delivery service.

--brian

Tom George wrote:                                                                      (Wed, 11 Jun 2003 15:12:47)
> I think this problem can be avoided. Suppose that messages are
> transmitted in this order:
> 
> Type       FSN   stream
> ---------  ---   ------
> User Data   1      1
> User Data   2      1
> LS PO       2      0
> LS PR       2      0
> User Data   3      1
> 
> The User Data messages arrive in order and the LS messages arrive in
> order on their respective streams. But there are no guarantees about
> their order relative to each other.
> 
> Tolga is concerned about the situation when the LS PR arrives after
> the new User Data message. For example, say they arrive like this:
> 
> User Data   1      1
> LS PO       2      0
> User Data   2      1
> User Data   3      1
> LS PR       2      0
> 
> Does UD message 3 get unacked and thereby cause link failure?
> 
> Here is what happens:
> 
> User Data   1      1
> 
>     Message is passed to MTP3.
> 
> LS PO       2      0
> 
>     Mark RPO and notify MTP3. Buffer but do not ack incoming messages.
> 
> User Data   2      1
> 
>     This message goes into the buffer-but-do-not-ack queue. The T7
>     timer is _not_ running at the other end.
> 
> User Data   3      1
> 
>     This message goes into the buffer-but-do-not-ack queue. The T7
>     timer _is_ running at the other end.
> 
> LS PR       2      0
> 
>     Notify MTP3 that the RPO has ended.
> 
>     If MTP3 wants to Continue, then start processing the queued
>     messages.
> 
>     If MTP3 wants to Flush, then M2PA should not delete all messages
>     willy-nilly. It should note that in the LS PR message, FSN =
>     2. Therefore:
> 
>        UD message 2 was sent before the PO, so flush it.
> 
>        UD message 3 was sent after the PO, so process and ack it.
> 
> tomG.
> 
> Tolga Asveren wrote:
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > 
> >>Tolga,
> >>
> >>Yes.
> > 
> > [TOLGA]But why? They are sent after local processor
> > outage has ended. The sending side will keep timeout
> > information for such a message (T7) and because it
> > won't be acknowledged, link will be dropped.
> > 
> >>--brian
> >>
> >>Tolga Asveren wrote:                                
> >>                                (Wed, 04 Jun 2003
> >>03:51:49)
> >>
> >>>Brian,
> >>>--- "Brian F. G. Bidulock" <bidulock@openss7.org>
> >>>wrote:
> >>>
> >>>>Tolga,
> >>>>
> >>>>In SS7 flushed messages are never retransmitted.
> >>>
> >>>>This
> >>>>is because they are old and stagnant by the time
> >>>
> >>the
> >>
> >>>>Flush_buffers is issued and must be dicareded.
> >>>
> >>>[TOLGA] Yes, but should we qualify also messages
> >>
> >>sent
> >>
> >>>after local processor outage ended but received on
> >>
> >>the
> >>
> >>>other side before LSPR (because they are sent on
> >>>different streams) as "old"?
> >>>
> >>>>--brian
> >>>>
> >>>>Tolga Asveren wrote:                            
> >>>
> >>   
> >>
> >>>>                                (Tue, 03 Jun
> >>>
> >>2003
> >>
> >>>>13:18:29)
> >>>>
> >>>>>Tom,
> >>>>>
> >>>>>[..snip..]
> >>>>>
> >>>>>>If M2PA receives a Flush command from MTP3,
> >>>>>
> >>M2PA
> >>
> >>>>>>SHALL discard the
> >>>>>>incoming messages that were queued and
> >>>>>>unacknowledged during the
> >>>>>>processor outage condition. Furthermore,
> >>>>>
> >>M2PA
> >>
> >>>>SHALL
> >>>>
> >>>>>>discard messages
> >>>>>>in the transmit and retransmit queues as
> >>>>>
> >>>>required by
> >>>>
> >>>>>>MTP2. 
> >>>>>
> >>>>>[TOLGA]So also messages sent after local
> >>>>
> >>processor
> >>
> >>>>>outage ended but received before LSPR will be
> >>>>>discarded(?). How are they going to be
> >>>>
> >>>>retransmitted?
> >>>>
> >>>>>
> >>>>>__________________________________
> >>>>>Do you Yahoo!?
> >>>>>Yahoo! Calendar - Free online calendar with
> >>>>
> >>sync
> >>
> >>>>to Outlook(TM).
> >>>>
> >>>>>http://calendar.yahoo.com
> >>>>>
> >>>>
> >>_______________________________________________
> >>
> >>>>>Sigtran mailing list
> >>>>>Sigtran@ietf.org
> >>>>>https://www1.ietf.org/mailman/listinfo/sigtran
> >>>>
> >>>>-- 
> >>>>Brian F. G. Bidulock
> >>>>bidulock@openss7.org
> >>>>http://www.openss7.org/
> >>>>_______________________________________________
> >>>>Sigtran mailing list
> >>>>Sigtran@ietf.org
> >>>>https://www1.ietf.org/mailman/listinfo/sigtran
> >>>
> >>>
> >>>__________________________________
> >>>Do you Yahoo!?
> >>>Yahoo! Calendar - Free online calendar with sync
> >>
> >>to Outlook(TM).
> >>
> >>>http://calendar.yahoo.com
> >>>_______________________________________________
> >>>Sigtran mailing list
> >>>Sigtran@ietf.org
> >>>https://www1.ietf.org/mailman/listinfo/sigtran
> >>
> >>-- 
> >>Brian F. G. Bidulock
> >>bidulock@openss7.org
> >>http://www.openss7.org/
> >>_______________________________________________
> >>Sigtran mailing list
> >>Sigtran@ietf.org
> >>https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> > 
> > 
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
> > http://calendar.yahoo.com
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> 
> 
> -- 
> * Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
> * 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
> * Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
> * I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
> * to advertise or represent its position,  operations, or activities. *
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Wed Jun 11 18:41:21 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07779
	for <sigtran-archive@odin.ietf.org>; Wed, 11 Jun 2003 18:41:21 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5BMetQ13798
	for sigtran-archive@odin.ietf.org; Wed, 11 Jun 2003 18:40:55 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5BMeZm13770;
	Wed, 11 Jun 2003 18:40:35 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5BMaRm12664
	for <sigtran@optimus.ietf.org>; Wed, 11 Jun 2003 18:36:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07617
	for <sigtran@ietf.org>; Wed, 11 Jun 2003 18:36:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QEAd-0004ob-00
	for sigtran@ietf.org; Wed, 11 Jun 2003 18:34:19 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QEAc-0004oE-00
	for sigtran@ietf.org; Wed, 11 Jun 2003 18:34:18 -0400
Received: from alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h5BMZrB3023500;
	Wed, 11 Jun 2003 17:35:53 -0500 (CDT)
Message-ID: <3EE7AEC9.4070403@alcatel.com>
Date: Wed, 11 Jun 2003 17:35:53 -0500
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
CC: sigtran@ietf.org
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
References: <20030604175601.74616.qmail@web12804.mail.yahoo.com> <3EE78D3F.40004@alcatel.com> <20030611160451.A7104@openss7.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

But now you have a race condition between LS PO and LS PR.

Brian F. G. Bidulock wrote:
> Tom,
> 
> Send LSPR ordered on stream 1 and there is no problem,
> because then the race condition between LS PR and DATA
> is removed.
> 
> That is a simpler and more direct solution than expecting
> the receiver to resolve races.  It seems rather pointless
> to intentionally introduce races when SCTP provides an
> ordered delivery service.
> 
> --brian
> 
> Tom George wrote:                                                                      (Wed, 11 Jun 2003 15:12:47)
> 
>>I think this problem can be avoided. Suppose that messages are
>>transmitted in this order:
>>
>>Type       FSN   stream
>>---------  ---   ------
>>User Data   1      1
>>User Data   2      1
>>LS PO       2      0
>>LS PR       2      0
>>User Data   3      1
>>
>>The User Data messages arrive in order and the LS messages arrive in
>>order on their respective streams. But there are no guarantees about
>>their order relative to each other.
>>
>>Tolga is concerned about the situation when the LS PR arrives after
>>the new User Data message. For example, say they arrive like this:
>>
>>User Data   1      1
>>LS PO       2      0
>>User Data   2      1
>>User Data   3      1
>>LS PR       2      0
>>
>>Does UD message 3 get unacked and thereby cause link failure?
>>
>>Here is what happens:
>>
>>User Data   1      1
>>
>>    Message is passed to MTP3.
>>
>>LS PO       2      0
>>
>>    Mark RPO and notify MTP3. Buffer but do not ack incoming messages.
>>
>>User Data   2      1
>>
>>    This message goes into the buffer-but-do-not-ack queue. The T7
>>    timer is _not_ running at the other end.
>>
>>User Data   3      1
>>
>>    This message goes into the buffer-but-do-not-ack queue. The T7
>>    timer _is_ running at the other end.
>>
>>LS PR       2      0
>>
>>    Notify MTP3 that the RPO has ended.
>>
>>    If MTP3 wants to Continue, then start processing the queued
>>    messages.
>>
>>    If MTP3 wants to Flush, then M2PA should not delete all messages
>>    willy-nilly. It should note that in the LS PR message, FSN =
>>    2. Therefore:
>>
>>       UD message 2 was sent before the PO, so flush it.
>>
>>       UD message 3 was sent after the PO, so process and ack it.
>>
>>tomG.
>>
>>Tolga Asveren wrote:
>>
>>>Brian,
>>>--- "Brian F. G. Bidulock" <bidulock@openss7.org>
>>>wrote:
>>>
>>>
>>>>Tolga,
>>>>
>>>>Yes.
>>>
>>>[TOLGA]But why? They are sent after local processor
>>>outage has ended. The sending side will keep timeout
>>>information for such a message (T7) and because it
>>>won't be acknowledged, link will be dropped.
>>>
>>>
>>>>--brian
>>>>
>>>>Tolga Asveren wrote:                                
>>>>                               (Wed, 04 Jun 2003
>>>>03:51:49)
>>>>
>>>>
>>>>>Brian,
>>>>>--- "Brian F. G. Bidulock" <bidulock@openss7.org>
>>>>>wrote:
>>>>>
>>>>>
>>>>>>Tolga,
>>>>>>
>>>>>>In SS7 flushed messages are never retransmitted.
>>>>>
>>>>>>This
>>>>>>is because they are old and stagnant by the time
>>>>>
>>>>the
>>>>
>>>>
>>>>>>Flush_buffers is issued and must be dicareded.
>>>>>
>>>>>[TOLGA] Yes, but should we qualify also messages
>>>>
>>>>sent
>>>>
>>>>
>>>>>after local processor outage ended but received on
>>>>
>>>>the
>>>>
>>>>
>>>>>other side before LSPR (because they are sent on
>>>>>different streams) as "old"?
>>>>>
>>>>>
>>>>>>--brian
>>>>>>
>>>>>>Tolga Asveren wrote:                            
>>>>>
>>>>  
>>>>
>>>>
>>>>>>                               (Tue, 03 Jun
>>>>>
>>>>2003
>>>>
>>>>
>>>>>>13:18:29)
>>>>>>
>>>>>>
>>>>>>>Tom,
>>>>>>>
>>>>>>>[..snip..]
>>>>>>>
>>>>>>>
>>>>>>>>If M2PA receives a Flush command from MTP3,
>>>>>>>
>>>>M2PA
>>>>
>>>>
>>>>>>>>SHALL discard the
>>>>>>>>incoming messages that were queued and
>>>>>>>>unacknowledged during the
>>>>>>>>processor outage condition. Furthermore,
>>>>>>>
>>>>M2PA
>>>>
>>>>
>>>>>>SHALL
>>>>>>
>>>>>>
>>>>>>>>discard messages
>>>>>>>>in the transmit and retransmit queues as
>>>>>>>
>>>>>>required by
>>>>>>
>>>>>>
>>>>>>>>MTP2. 
>>>>>>>
>>>>>>>[TOLGA]So also messages sent after local
>>>>>>
>>>>processor
>>>>
>>>>
>>>>>>>outage ended but received before LSPR will be
>>>>>>>discarded(?). How are they going to be
>>>>>>
>>>>>>retransmitted?
>>>>>>
>>>>>>
>>>>>>>__________________________________
>>>>>>>Do you Yahoo!?
>>>>>>>Yahoo! Calendar - Free online calendar with
>>>>>>
>>>>sync
>>>>
>>>>
>>>>>>to Outlook(TM).
>>>>>>
>>>>>>
>>>>>>>http://calendar.yahoo.com
>>>>>>>
>>>>>>
>>>>_______________________________________________
>>>>
>>>>
>>>>>>>Sigtran mailing list
>>>>>>>Sigtran@ietf.org
>>>>>>>https://www1.ietf.org/mailman/listinfo/sigtran
>>>>>>
>>>>>>-- 
>>>>>>Brian F. G. Bidulock
>>>>>>bidulock@openss7.org
>>>>>>http://www.openss7.org/
>>>>>>_______________________________________________
>>>>>>Sigtran mailing list
>>>>>>Sigtran@ietf.org
>>>>>>https://www1.ietf.org/mailman/listinfo/sigtran
>>>>>
>>>>>
>>>>>__________________________________
>>>>>Do you Yahoo!?
>>>>>Yahoo! Calendar - Free online calendar with sync
>>>>
>>>>to Outlook(TM).
>>>>
>>>>
>>>>>http://calendar.yahoo.com
>>>>>_______________________________________________
>>>>>Sigtran mailing list
>>>>>Sigtran@ietf.org
>>>>>https://www1.ietf.org/mailman/listinfo/sigtran
>>>>
>>>>-- 
>>>>Brian F. G. Bidulock
>>>>bidulock@openss7.org
>>>>http://www.openss7.org/
>>>>_______________________________________________
>>>>Sigtran mailing list
>>>>Sigtran@ietf.org
>>>>https://www1.ietf.org/mailman/listinfo/sigtran
>>>
>>>
>>>
>>>__________________________________
>>>Do you Yahoo!?
>>>Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
>>>http://calendar.yahoo.com
>>>_______________________________________________
>>>Sigtran mailing list
>>>Sigtran@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/sigtran
>>>
>>
>>
>>-- 
>>* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
>>* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
>>* Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
>>* I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
>>* to advertise or represent its position,  operations, or activities. *
>>
>>_______________________________________________
>>Sigtran mailing list
>>Sigtran@ietf.org
>>https://www1.ietf.org/mailman/listinfo/sigtran
> 
> 


-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
* I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
* to advertise or represent its position,  operations, or activities. *

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



From mailnull@www1.ietf.org  Wed Jun 11 22:07:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11975
	for <sigtran-archive@odin.ietf.org>; Wed, 11 Jun 2003 22:07:29 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5C272P26616
	for sigtran-archive@odin.ietf.org; Wed, 11 Jun 2003 22:07:02 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5C26Zm26525;
	Wed, 11 Jun 2003 22:06:36 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5C23Zm26435
	for <sigtran@optimus.ietf.org>; Wed, 11 Jun 2003 22:03:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11915
	for <sigtran@ietf.org>; Wed, 11 Jun 2003 22:03:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QHP5-0005xh-00
	for sigtran@ietf.org; Wed, 11 Jun 2003 22:01:27 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[rCzvrT1LGJSyXleg0OIy9ezZLu+dr6FN])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QHP4-0005xe-00
	for sigtran@ietf.org; Wed, 11 Jun 2003 22:01:26 -0400
Received: from ns.pigworks.openss7.net (IDENT:SJmZKmtljizocu9DT7OrBzcBHvT2ZGt4@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5C23VX10898;
	Wed, 11 Jun 2003 20:03:31 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5C23VI10846;
	Wed, 11 Jun 2003 20:03:31 -0600
Date: Wed, 11 Jun 2003 20:03:31 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tom George <Tom.George@alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
Message-ID: <20030611200331.B10555@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tom George <Tom.George@alcatel.com>, sigtran@ietf.org
References: <20030604175601.74616.qmail@web12804.mail.yahoo.com> <3EE78D3F.40004@alcatel.com> <20030611160451.A7104@openss7.org> <3EE7AEC9.4070403@alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <3EE7AEC9.4070403@alcatel.com>; from Tom.George@alcatel.com on Wed, Jun 11, 2003 at 05:35:53PM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tom,

Although it is hightly unlikely that a real network work
place them close enough together for there to be a race,
sending everything ordered on one stream would solve all
racees.

If one wants to use Q.703 state machines for the most part
then it appears that one should meet the same ordering
characteristics as an Q.703 link.

--brian

Tom George wrote:                                                                      (Wed, 11 Jun 2003 17:35:53)
> But now you have a race condition between LS PO and LS PR.
> 
> Brian F. G. Bidulock wrote:
> > Tom,
> > 
> > Send LSPR ordered on stream 1 and there is no problem,
> > because then the race condition between LS PR and DATA
> > is removed.
> > 
> > That is a simpler and more direct solution than expecting
> > the receiver to resolve races.  It seems rather pointless
> > to intentionally introduce races when SCTP provides an
> > ordered delivery service.
> > 
> > --brian
> > 
> > Tom George wrote:                                                                      (Wed, 11 Jun 2003 15:12:47)
> > 
> >>I think this problem can be avoided. Suppose that messages are
> >>transmitted in this order:
> >>
> >>Type       FSN   stream
> >>---------  ---   ------
> >>User Data   1      1
> >>User Data   2      1
> >>LS PO       2      0
> >>LS PR       2      0
> >>User Data   3      1
> >>
> >>The User Data messages arrive in order and the LS messages arrive in
> >>order on their respective streams. But there are no guarantees about
> >>their order relative to each other.
> >>
> >>Tolga is concerned about the situation when the LS PR arrives after
> >>the new User Data message. For example, say they arrive like this:
> >>
> >>User Data   1      1
> >>LS PO       2      0
> >>User Data   2      1
> >>User Data   3      1
> >>LS PR       2      0
> >>
> >>Does UD message 3 get unacked and thereby cause link failure?
> >>
> >>Here is what happens:
> >>
> >>User Data   1      1
> >>
> >>    Message is passed to MTP3.
> >>
> >>LS PO       2      0
> >>
> >>    Mark RPO and notify MTP3. Buffer but do not ack incoming messages.
> >>
> >>User Data   2      1
> >>
> >>    This message goes into the buffer-but-do-not-ack queue. The T7
> >>    timer is _not_ running at the other end.
> >>
> >>User Data   3      1
> >>
> >>    This message goes into the buffer-but-do-not-ack queue. The T7
> >>    timer _is_ running at the other end.
> >>
> >>LS PR       2      0
> >>
> >>    Notify MTP3 that the RPO has ended.
> >>
> >>    If MTP3 wants to Continue, then start processing the queued
> >>    messages.
> >>
> >>    If MTP3 wants to Flush, then M2PA should not delete all messages
> >>    willy-nilly. It should note that in the LS PR message, FSN =
> >>    2. Therefore:
> >>
> >>       UD message 2 was sent before the PO, so flush it.
> >>
> >>       UD message 3 was sent after the PO, so process and ack it.
> >>
> >>tomG.
> >>
> >>Tolga Asveren wrote:
> >>
> >>>Brian,
> >>>--- "Brian F. G. Bidulock" <bidulock@openss7.org>
> >>>wrote:
> >>>
> >>>
> >>>>Tolga,
> >>>>
> >>>>Yes.
> >>>
> >>>[TOLGA]But why? They are sent after local processor
> >>>outage has ended. The sending side will keep timeout
> >>>information for such a message (T7) and because it
> >>>won't be acknowledged, link will be dropped.
> >>>
> >>>
> >>>>--brian
> >>>>
> >>>>Tolga Asveren wrote:                                
> >>>>                               (Wed, 04 Jun 2003
> >>>>03:51:49)
> >>>>
> >>>>
> >>>>>Brian,
> >>>>>--- "Brian F. G. Bidulock" <bidulock@openss7.org>
> >>>>>wrote:
> >>>>>
> >>>>>
> >>>>>>Tolga,
> >>>>>>
> >>>>>>In SS7 flushed messages are never retransmitted.
> >>>>>
> >>>>>>This
> >>>>>>is because they are old and stagnant by the time
> >>>>>
> >>>>the
> >>>>
> >>>>
> >>>>>>Flush_buffers is issued and must be dicareded.
> >>>>>
> >>>>>[TOLGA] Yes, but should we qualify also messages
> >>>>
> >>>>sent
> >>>>
> >>>>
> >>>>>after local processor outage ended but received on
> >>>>
> >>>>the
> >>>>
> >>>>
> >>>>>other side before LSPR (because they are sent on
> >>>>>different streams) as "old"?
> >>>>>
> >>>>>
> >>>>>>--brian
> >>>>>>
> >>>>>>Tolga Asveren wrote:                            
> >>>>>
> >>>>  
> >>>>
> >>>>
> >>>>>>                               (Tue, 03 Jun
> >>>>>
> >>>>2003
> >>>>
> >>>>
> >>>>>>13:18:29)
> >>>>>>
> >>>>>>
> >>>>>>>Tom,
> >>>>>>>
> >>>>>>>[..snip..]
> >>>>>>>
> >>>>>>>
> >>>>>>>>If M2PA receives a Flush command from MTP3,
> >>>>>>>
> >>>>M2PA
> >>>>
> >>>>
> >>>>>>>>SHALL discard the
> >>>>>>>>incoming messages that were queued and
> >>>>>>>>unacknowledged during the
> >>>>>>>>processor outage condition. Furthermore,
> >>>>>>>
> >>>>M2PA
> >>>>
> >>>>
> >>>>>>SHALL
> >>>>>>
> >>>>>>
> >>>>>>>>discard messages
> >>>>>>>>in the transmit and retransmit queues as
> >>>>>>>
> >>>>>>required by
> >>>>>>
> >>>>>>
> >>>>>>>>MTP2. 
> >>>>>>>
> >>>>>>>[TOLGA]So also messages sent after local
> >>>>>>
> >>>>processor
> >>>>
> >>>>
> >>>>>>>outage ended but received before LSPR will be
> >>>>>>>discarded(?). How are they going to be
> >>>>>>
> >>>>>>retransmitted?
> >>>>>>
> >>>>>>
> >>>>>>>__________________________________
> >>>>>>>Do you Yahoo!?
> >>>>>>>Yahoo! Calendar - Free online calendar with
> >>>>>>
> >>>>sync
> >>>>
> >>>>
> >>>>>>to Outlook(TM).
> >>>>>>
> >>>>>>
> >>>>>>>http://calendar.yahoo.com
> >>>>>>>
> >>>>>>
> >>>>_______________________________________________
> >>>>
> >>>>
> >>>>>>>Sigtran mailing list
> >>>>>>>Sigtran@ietf.org
> >>>>>>>https://www1.ietf.org/mailman/listinfo/sigtran
> >>>>>>
> >>>>>>-- 
> >>>>>>Brian F. G. Bidulock
> >>>>>>bidulock@openss7.org
> >>>>>>http://www.openss7.org/
> >>>>>>_______________________________________________
> >>>>>>Sigtran mailing list
> >>>>>>Sigtran@ietf.org
> >>>>>>https://www1.ietf.org/mailman/listinfo/sigtran
> >>>>>
> >>>>>
> >>>>>__________________________________
> >>>>>Do you Yahoo!?
> >>>>>Yahoo! Calendar - Free online calendar with sync
> >>>>
> >>>>to Outlook(TM).
> >>>>
> >>>>
> >>>>>http://calendar.yahoo.com
> >>>>>_______________________________________________
> >>>>>Sigtran mailing list
> >>>>>Sigtran@ietf.org
> >>>>>https://www1.ietf.org/mailman/listinfo/sigtran
> >>>>
> >>>>-- 
> >>>>Brian F. G. Bidulock
> >>>>bidulock@openss7.org
> >>>>http://www.openss7.org/
> >>>>_______________________________________________
> >>>>Sigtran mailing list
> >>>>Sigtran@ietf.org
> >>>>https://www1.ietf.org/mailman/listinfo/sigtran
> >>>
> >>>
> >>>
> >>>__________________________________
> >>>Do you Yahoo!?
> >>>Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
> >>>http://calendar.yahoo.com
> >>>_______________________________________________
> >>>Sigtran mailing list
> >>>Sigtran@ietf.org
> >>>https://www1.ietf.org/mailman/listinfo/sigtran
> >>>
> >>
> >>
> >>-- 
> >>* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
> >>* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
> >>* Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
> >>* I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
> >>* to advertise or represent its position,  operations, or activities. *
> >>
> >>_______________________________________________
> >>Sigtran mailing list
> >>Sigtran@ietf.org
> >>https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> > 
> 
> 
> -- 
> * Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
> * 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
> * Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
> * I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
> * to advertise or represent its position,  operations, or activities. *
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jun 12 08:31:01 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07197
	for <sigtran-archive@odin.ietf.org>; Thu, 12 Jun 2003 08:31:01 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5CCUXe15660
	for sigtran-archive@odin.ietf.org; Thu, 12 Jun 2003 08:30:33 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CCUDm15617;
	Thu, 12 Jun 2003 08:30:15 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CCR6m15490
	for <sigtran@optimus.ietf.org>; Thu, 12 Jun 2003 08:27:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07057
	for <sigtran@ietf.org>; Thu, 12 Jun 2003 08:27:04 -0400 (EDT)
From: kakaul@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QR8U-0001dy-00
	for sigtran@ietf.org; Thu, 12 Jun 2003 08:24:58 -0400
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QR8S-0001dc-00
	for sigtran@ietf.org; Thu, 12 Jun 2003 08:24:56 -0400
Received: from hindon.hss.co.in (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h5CCNwb05004
	for <sigtran@ietf.org>; Thu, 12 Jun 2003 17:53:58 +0530 (IST)
Received: from ultra.hss.co.in (ultra [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h5CCNv904992
	for <sigtran@ietf.org>; Thu, 12 Jun 2003 17:53:57 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h5CCROJ14328
	for <sigtran@ietf.org>; Thu, 12 Jun 2003 17:57:24 +0530 (IST)
To: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF85129ACE.0BAF3C8D-ON65256D43.0043E377@hss.hns.com>
Date: Thu, 12 Jun 2003 17:52:18 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 12/06/2003
 05:51:27 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Subject: [Sigtran] Minor Corrections required in M3UA RFC 3332
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>






Hi
      Some minor corrections required in RFC 3332

Section 1.3.2.3 :
old text  - Providing an indication to the M3UA layer
at an ASP that the routes to a destination in the SS7 network
are restricted.

New text  - Providing an indication to MTP3-Users at an ASP
that the routes to a destination in the SS7 network are restricted.

Sections 5.1.1.2, 5.1.1.3, 5.1.1.4 :
Local Routing Context (LRC)should be replaced with
Local Routing Key identifier (LRK)

Section 5.1.2:
NOTIFY (AS-ACTIVE) missing in the message sequence

Section 5.1.4:
NOTIFY (AS-ACTIVE) missing in the message sequence
from SGP to ASP1

Section 5.3:
LRCn is not required in DEREGISTER RESPONSE message

Regards
Kamesh
Hughes Software Systems



"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
(HSS) and is intended solely for the use of the individual to whom it is
addressed. It may contain  privileged or confidential information and
should not be circulated or used for any purpose other than for what it is
intended. If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient, you are
notified that you are strictly prohibited from using, copying, altering, or
disclosing the contents of this message. HSS accepts no responsibility for
loss or damage arising from the use of the information transmitted by this
email including damage from virus."

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



From mailnull@www1.ietf.org  Thu Jun 12 08:49:45 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08517
	for <sigtran-archive@odin.ietf.org>; Thu, 12 Jun 2003 08:49:45 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5CCnHR17507
	for sigtran-archive@odin.ietf.org; Thu, 12 Jun 2003 08:49:17 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CClbm17429;
	Thu, 12 Jun 2003 08:47:37 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CCh8m17193
	for <sigtran@optimus.ietf.org>; Thu, 12 Jun 2003 08:43:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07750
	for <sigtran@ietf.org>; Thu, 12 Jun 2003 08:43:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QRO0-0001pE-00
	for sigtran@ietf.org; Thu, 12 Jun 2003 08:41:00 -0400
Received: from web12807.mail.yahoo.com ([216.136.174.42])
	by ietf-mx with smtp (Exim 4.12)
	id 19QRNs-0001oY-00
	for sigtran@ietf.org; Thu, 12 Jun 2003 08:40:56 -0400
Message-ID: <20030612124237.15967.qmail@web12807.mail.yahoo.com>
Received: from [208.255.120.2] by web12807.mail.yahoo.com via HTTP; Thu, 12 Jun 2003 05:42:37 PDT
Date: Thu, 12 Jun 2003 05:42:37 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] Minor Corrections required in M3UA RFC 3332
To: sigtran@ietf.org
In-Reply-To: <OF85129ACE.0BAF3C8D-ON65256D43.0043E377@hss.hns.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Hi Kamesh,
--- kakaul@hss.hns.com wrote:
> 
> 
> 
> 
> 
> Hi
>       Some minor corrections required in RFC 3332
> 
> Section 1.3.2.3 :
> old text  - Providing an indication to the M3UA
> layer
> at an ASP that the routes to a destination in the
> SS7 network
> are restricted.
> 
> New text  - Providing an indication to MTP3-Users at
> an ASP
> that the routes to a destination in the SS7 network
> are restricted.
[TOLGA]There is no defined indication to MTP3-Users
for restricted case(and it is also not necessary, they
don't care how a message is routed -via this or that
SG-, what they care is whether the destination is
reachable or not)
> 
> Sections 5.1.1.2, 5.1.1.3, 5.1.1.4 :
> Local Routing Context (LRC)should be replaced with
> Local Routing Key identifier (LRK)
> 
> Section 5.1.2:
> NOTIFY (AS-ACTIVE) missing in the message sequence
> 
> Section 5.1.4:
> NOTIFY (AS-ACTIVE) missing in the message sequence
> from SGP to ASP1
[TOLGA]Those are not the only missing NTFYs in this
section but we have at he beginning of section5:
"NOTE: Not all the Notify messages that are
appropriate per the Notify procedures are shown in
these examples."
I don't know whether the whole section 5 should be
revised to include necessary NTFYs(?).

> 
> Section 5.3:
> LRCn is not required in DEREGISTER RESPONSE message
> 
> Regards
> Kamesh
> Hughes Software Systems
> 
> 
> 
> "DISCLAIMER: This message is proprietary to Hughes
> Software Systems Limited
> (HSS) and is intended solely for the use of the
> individual to whom it is
> addressed. It may contain  privileged or
> confidential information and
> should not be circulated or used for any purpose
> other than for what it is
> intended. If you have received this message in
> error, please notify the
> originator immediately. If you are not the intended
> recipient, you are
> notified that you are strictly prohibited from
> using, copying, altering, or
> disclosing the contents of this message. HSS accepts
> no responsibility for
> loss or damage arising from the use of the
> information transmitted by this
> email including damage from virus."
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jun 12 08:59:45 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08973
	for <sigtran-archive@odin.ietf.org>; Thu, 12 Jun 2003 08:59:45 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5CCxHm18103
	for sigtran-archive@odin.ietf.org; Thu, 12 Jun 2003 08:59:17 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CCwxm18066;
	Thu, 12 Jun 2003 08:58:59 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CCu6m17963
	for <sigtran@optimus.ietf.org>; Thu, 12 Jun 2003 08:56:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08846
	for <sigtran@ietf.org>; Thu, 12 Jun 2003 08:56:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QRaY-0002B5-00
	for sigtran@ietf.org; Thu, 12 Jun 2003 08:53:58 -0400
Received: from web12802.mail.yahoo.com ([216.136.174.37])
	by ietf-mx with smtp (Exim 4.12)
	id 19QRaX-0002B2-00
	for sigtran@ietf.org; Thu, 12 Jun 2003 08:53:57 -0400
Message-ID: <20030612125603.45486.qmail@web12802.mail.yahoo.com>
Received: from [208.255.120.2] by web12802.mail.yahoo.com via HTTP; Thu, 12 Jun 2003 05:56:03 PDT
Date: Thu, 12 Jun 2003 05:56:03 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
To: sigtran@ietf.org
In-Reply-To: <20030611200331.B10555@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

I also think like Brian. IMO Tom's solution is a nice
one, but isn't it just to use a second level of global
sequencing on top of stream based SCTP sequencing, to
prevent side effects of multiple streams? As far as I
understand, if this is the way to go, there will be
cases where one needs to look to FSN for sequencing
information and cases, where one does not need this.
IMO, this will complicate the protocol.

   Tolga 
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Tom,
> 
> Although it is hightly unlikely that a real network
> work
> place them close enough together for there to be a
> race,
> sending everything ordered on one stream would solve
> all
> racees.
> 
> If one wants to use Q.703 state machines for the
> most part
> then it appears that one should meet the same
> ordering
> characteristics as an Q.703 link.
> 
> --brian
> 
> Tom George wrote:                                   
>                                   (Wed, 11 Jun 2003
> 17:35:53)
> > But now you have a race condition between LS PO
> and LS PR.
> > 
> > Brian F. G. Bidulock wrote:
> > > Tom,
> > > 
> > > Send LSPR ordered on stream 1 and there is no
> problem,
> > > because then the race condition between LS PR
> and DATA
> > > is removed.
> > > 
> > > That is a simpler and more direct solution than
> expecting
> > > the receiver to resolve races.  It seems rather
> pointless
> > > to intentionally introduce races when SCTP
> provides an
> > > ordered delivery service.
> > > 
> > > --brian
> > > 
> > > Tom George wrote:                               
>                                       (Wed, 11 Jun
> 2003 15:12:47)
> > > 
> > >>I think this problem can be avoided. Suppose
> that messages are
> > >>transmitted in this order:
> > >>
> > >>Type       FSN   stream
> > >>---------  ---   ------
> > >>User Data   1      1
> > >>User Data   2      1
> > >>LS PO       2      0
> > >>LS PR       2      0
> > >>User Data   3      1
> > >>
> > >>The User Data messages arrive in order and the
> LS messages arrive in
> > >>order on their respective streams. But there are
> no guarantees about
> > >>their order relative to each other.
> > >>
> > >>Tolga is concerned about the situation when the
> LS PR arrives after
> > >>the new User Data message. For example, say they
> arrive like this:
> > >>
> > >>User Data   1      1
> > >>LS PO       2      0
> > >>User Data   2      1
> > >>User Data   3      1
> > >>LS PR       2      0
> > >>
> > >>Does UD message 3 get unacked and thereby cause
> link failure?
> > >>
> > >>Here is what happens:
> > >>
> > >>User Data   1      1
> > >>
> > >>    Message is passed to MTP3.
> > >>
> > >>LS PO       2      0
> > >>
> > >>    Mark RPO and notify MTP3. Buffer but do not
> ack incoming messages.
> > >>
> > >>User Data   2      1
> > >>
> > >>    This message goes into the
> buffer-but-do-not-ack queue. The T7
> > >>    timer is _not_ running at the other end.
> > >>
> > >>User Data   3      1
> > >>
> > >>    This message goes into the
> buffer-but-do-not-ack queue. The T7
> > >>    timer _is_ running at the other end.
> > >>
> > >>LS PR       2      0
> > >>
> > >>    Notify MTP3 that the RPO has ended.
> > >>
> > >>    If MTP3 wants to Continue, then start
> processing the queued
> > >>    messages.
> > >>
> > >>    If MTP3 wants to Flush, then M2PA should not
> delete all messages
> > >>    willy-nilly. It should note that in the LS
> PR message, FSN =
> > >>    2. Therefore:
> > >>
> > >>       UD message 2 was sent before the PO, so
> flush it.
> > >>
> > >>       UD message 3 was sent after the PO, so
> process and ack it.
> > >>
> > >>tomG.
> > >>
> > >>Tolga Asveren wrote:
> > >>
> > >>>Brian,
> > >>>--- "Brian F. G. Bidulock"
> <bidulock@openss7.org>
> > >>>wrote:
> > >>>
> > >>>
> > >>>>Tolga,
> > >>>>
> > >>>>Yes.
> > >>>
> > >>>[TOLGA]But why? They are sent after local
> processor
> > >>>outage has ended. The sending side will keep
> timeout
> > >>>information for such a message (T7) and because
> it
> > >>>won't be acknowledged, link will be dropped.
> > >>>
> > >>>
> > >>>>--brian
> > >>>>
> > >>>>Tolga Asveren wrote:                          
>      
> > >>>>                               (Wed, 04 Jun
> 2003
> > >>>>03:51:49)
> > >>>>
> > >>>>
> > >>>>>Brian,
> > >>>>>--- "Brian F. G. Bidulock"
> <bidulock@openss7.org>
> > >>>>>wrote:
> > >>>>>
> > >>>>>
> > >>>>>>Tolga,
> > >>>>>>
> > >>>>>>In SS7 flushed messages are never
> retransmitted.
> > >>>>>
> > >>>>>>This
> > >>>>>>is because they are old and stagnant by the
> time
> > >>>>>
> > >>>>the
> > >>>>
> > >>>>
> > >>>>>>Flush_buffers is issued and must be
> dicareded.
> > >>>>>
> > >>>>>[TOLGA] Yes, but should we qualify also
> messages
> > >>>>
> > >>>>sent
> > >>>>
> > >>>>
> > >>>>>after local processor outage ended but
> received on
> > >>>>
> > >>>>the
> > >>>>
> > >>>>
> > >>>>>other side before LSPR (because they are sent
> on
> > >>>>>different streams) as "old"?
> > >>>>>
> > >>>>>
> > >>>>>>--brian
> > >>>>>>
> > >>>>>>Tolga Asveren wrote:                        
>    
> > >>>>>
> > >>>>  
> > >>>>
> > >>>>
> > >>>>>>                               (Tue, 03 Jun
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Thu Jun 12 11:12:04 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15311
	for <sigtran-archive@odin.ietf.org>; Thu, 12 Jun 2003 11:12:04 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5CFBcL30988
	for sigtran-archive@odin.ietf.org; Thu, 12 Jun 2003 11:11:38 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CFB9m30930;
	Thu, 12 Jun 2003 11:11:09 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CF8Pm30697
	for <sigtran@optimus.ietf.org>; Thu, 12 Jun 2003 11:08:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15007
	for <sigtran@ietf.org>; Thu, 12 Jun 2003 11:08:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QTeZ-0003J7-00
	for sigtran@ietf.org; Thu, 12 Jun 2003 11:06:15 -0400
Received: from email10.etsi.org ([212.234.161.112] helo=email10.etsihq.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19QTeY-0003Ip-00
	for sigtran@ietf.org; Thu, 12 Jun 2003 11:06:14 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Date: Thu, 12 Jun 2003 17:07:50 +0200
Message-ID: <4091553999CBE4409CC2B562152B5A3301EBC919@email10.etsihq.org>
Thread-Topic: SIGTRAN Bake-off at ETSI on September
Thread-Index: AcMOTaeTixv0FXxzTZyrK5aW9olehwipFvyAAACNkVA=
From: =?us-ascii?Q?Sebastien_Flaux?= <Sebastien.Flaux@etsi.org>
To: <sigtran@ietf.org>
Cc: "Philippe Cousin" <Philippe.Cousin@etsi.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h5CF8Pm30698
Subject: [Sigtran] FW: Registration now open for the SIGTRAN Bake-off at ETSI on 1-5 September 2003 !
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

On behalf of Philippe Cousin:


Dear all,

ETSI is pleased to invite you for a SIGTRAN bake-off to be held on 1-5
September at ETSI premises Sophia-Antipolis (Nice airport).

Registration is now open at
http://www.etsi.org/plugtests/02UpcomingEvents/SIGTRAN/SIGTRAN_home.htm
where you will find all necessary information including technical and
logistics.

Look forward having a succesfull event like the previous ones.

Kind regards
Philippe

Philippe COUSIN
Interoperability Service Manager
Tel: + 33 (0)4 92 94 4306
Fax: +33 (0)4 92 38 5248
http://www.etsi.org/plugtests/


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



From mailnull@www1.ietf.org  Thu Jun 12 11:23:44 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15669
	for <sigtran-archive@odin.ietf.org>; Thu, 12 Jun 2003 11:23:44 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5CFNGV31603
	for sigtran-archive@odin.ietf.org; Thu, 12 Jun 2003 11:23:16 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CFMtm31540;
	Thu, 12 Jun 2003 11:22:55 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CF13m29348
	for <sigtran@optimus.ietf.org>; Thu, 12 Jun 2003 11:01:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14700
	for <sigtran@ietf.org>; Thu, 12 Jun 2003 11:00:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QTXR-0003EZ-00
	for sigtran@ietf.org; Thu, 12 Jun 2003 10:58:53 -0400
Received: from email10.etsi.org ([212.234.161.112] helo=email10.etsihq.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19QTXQ-0003E5-00
	for sigtran@ietf.org; Thu, 12 Jun 2003 10:58:52 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Date: Thu, 12 Jun 2003 17:00:26 +0200
Message-ID: <4091553999CBE4409CC2B562152B5A3301CFE6DC@email10.etsihq.org>
Thread-Topic: SIGTRAN Bake-off at ETSI on September
Thread-Index: AcMOTaeTixv0FXxzTZyrK5aW9olehwipFvyA
From: "Philippe Cousin" <Philippe.Cousin@etsi.org>
To: "MTS-IPT-SIGTRAN" <MTS-IPT-SIGTRAN@list.etsi.org>, <sigtran@ietf.org>
Cc: "Anthony Wiles" <Anthony.Wiles@etsi.org>,
        =?us-ascii?Q?Patrick_Rene_Guillemin?= <Patrick.Guillemin@etsi.org>,
        "Ken Morneault" <kmorneau@cisco.com>,
        "Garnero, Pierre" <Pierre.Garnero@hp.com>, <LyOng@ciena.com>,
        "Christian Julien" <Christian.Julien@etsi.org>,
        <tuexen@fh-muenster.de>,
        =?us-ascii?Q?Sebastien_Flaux?= <Sebastien.Flaux@etsi.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h5CF14m29349
Subject: [Sigtran] Registration now open for the SIGTRAN Bake-off at ETSI on 1-5 September 2003 !
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Dear all,

ETSI is pleased to invite you for a SIGTRAN bake-off to be held on 1-5
September at ETSI premises Sophia-Antipolis (Nice airport).

Registration is now open at
http://www.etsi.org/plugtests/02UpcomingEvents/SIGTRAN/SIGTRAN_home.htm
where you will find all necessary information including technical and
logistics.

Look forward having a succesfull event like the previous ones.

Kind regards
Philippe

Philippe COUSIN
Interoperability Service Manager
Tel: + 33 (0)4 92 94 4306
Fax: +33 (0)4 92 38 5248
http://www.etsi.org/plugtests/


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



From mailnull@www1.ietf.org  Fri Jun 13 06:34:42 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27667
	for <sigtran-archive@odin.ietf.org>; Fri, 13 Jun 2003 06:34:41 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5DAYFQ28620
	for sigtran-archive@odin.ietf.org; Fri, 13 Jun 2003 06:34:15 -0400
Received: from optimus.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5D3qJa19199;
	Thu, 12 Jun 2003 23:52:19 -0400
Received: from ietf.org (lists.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5D3pOm19153
	for <sigtran@optimus.ietf.org>; Thu, 12 Jun 2003 23:51:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07113
	for <sigtran@ietf.org>; Thu, 12 Jun 2003 23:51:19 -0400 (EDT)
From: kakaul@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QfYv-0000jZ-00
	for sigtran@ietf.org; Thu, 12 Jun 2003 23:49:13 -0400
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QfYu-0000j5-00
	for sigtran@ietf.org; Thu, 12 Jun 2003 23:49:12 -0400
Received: from hindon.hss.co.in (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h5D3mEM25515
	for <sigtran@ietf.org>; Fri, 13 Jun 2003 09:18:14 +0530 (IST)
Received: from ultra.hss.co.in (ultra [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h5D3mC925509;
	Fri, 13 Jun 2003 09:18:12 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h5D3pfb09686;
	Fri, 13 Jun 2003 09:21:41 +0530 (IST)
Subject: Re: [Sigtran] Minor Corrections required in M3UA RFC 3332
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OFC2FCA507.875CE97D-ON65256D44.00138A36@hss.hns.com>
Date: Fri, 13 Jun 2003 09:16:36 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 13/06/2003
 09:15:44 AM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>





Hi Tolga,
   You are right correction in Section 1.3.2.3 is not required,
    I misunderstood restricted to unavailable
   Thanks for correction. Notify messages are the part of
   protocol operations, i believe these should be shown
   in message flow examples completely to avoid any
   confusions.

Regards
Kamesh




Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org on 06/12/2003 06:12:37 PM

Sent by:    sigtran-admin@ietf.org


To:    sigtran@ietf.org
cc:

Subject:    Re: [Sigtran] Minor Corrections required in M3UA RFC 3332


Hi Kamesh,
--- kakaul@hss.hns.com wrote:
>
>
>
>
>
> Hi
>       Some minor corrections required in RFC 3332
>
> Section 1.3.2.3 :
> old text  - Providing an indication to the M3UA
> layer
> at an ASP that the routes to a destination in the
> SS7 network
> are restricted.
>
> New text  - Providing an indication to MTP3-Users at
> an ASP
> that the routes to a destination in the SS7 network
> are restricted.
[TOLGA]There is no defined indication to MTP3-Users
for restricted case(and it is also not necessary, they
don't care how a message is routed -via this or that
SG-, what they care is whether the destination is
reachable or not)
>
> Sections 5.1.1.2, 5.1.1.3, 5.1.1.4 :
> Local Routing Context (LRC)should be replaced with
> Local Routing Key identifier (LRK)
>
> Section 5.1.2:
> NOTIFY (AS-ACTIVE) missing in the message sequence
>
> Section 5.1.4:
> NOTIFY (AS-ACTIVE) missing in the message sequence
> from SGP to ASP1
[TOLGA]Those are not the only missing NTFYs in this
section but we have at he beginning of section5:
"NOTE: Not all the Notify messages that are
appropriate per the Notify procedures are shown in
these examples."
I don't know whether the whole section 5 should be
revised to include necessary NTFYs(?).

>
> Section 5.3:
> LRCn is not required in DEREGISTER RESPONSE message
>
> Regards
> Kamesh
> Hughes Software Systems
>
>
>
> "DISCLAIMER: This message is proprietary to Hughes
> Software Systems Limited
> (HSS) and is intended solely for the use of the
> individual to whom it is
> addressed. It may contain  privileged or
> confidential information and
> should not be circulated or used for any purpose
> other than for what it is
> intended. If you have received this message in
> error, please notify the
> originator immediately. If you are not the intended
> recipient, you are
> notified that you are strictly prohibited from
> using, copying, altering, or
> disclosing the contents of this message. HSS accepts
> no responsibility for
> loss or damage arising from the use of the
> information transmitted by this
> email including damage from virus."
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
 https://www1.ietf.org/mailman/listinfo/sigtran


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



From mailnull@www1.ietf.org  Fri Jun 13 09:40:06 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04774
	for <sigtran-archive@odin.ietf.org>; Fri, 13 Jun 2003 09:40:06 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5DDdcS11657
	for sigtran-archive@odin.ietf.org; Fri, 13 Jun 2003 09:39:38 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CL72a24528;
	Thu, 12 Jun 2003 17:07:02 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CL6Wm24444
	for <sigtran@optimus.ietf.org>; Thu, 12 Jun 2003 17:06:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26951
	for <SIGTRAN@IETF.org>; Thu, 12 Jun 2003 17:06:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QZF9-0005zO-00
	for SIGTRAN@IETF.org; Thu, 12 Jun 2003 17:04:23 -0400
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QZF9-0005zC-00
	for SIGTRAN@IETF.org; Thu, 12 Jun 2003 17:04:23 -0400
Received: from alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h5CL5xwA023354;
	Thu, 12 Jun 2003 16:05:59 -0500 (CDT)
Message-ID: <3EE8EB37.6020706@alcatel.com>
Date: Thu, 12 Jun 2003 16:05:59 -0500
From: Tom George <Tom.George@alcatel.com>
Organization: Alcatel
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: SIGTRAN e-mail list <SIGTRAN@ietf.org>
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
References: <20030604175601.74616.qmail@web12804.mail.yahoo.com> <3EE78D3F.40004@alcatel.com> <20030611160451.A7104@openss7.org> <3EE7AEC9.4070403@alcatel.com> <20030611200331.B10555@openss7.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Likewise, I think the probability of the User Data with FSN=3 arriving 
ahead of the LS PR is very small, too. The LS PR is sent first and in 
all likelihood the UD message will follow the LS message along the same 
path through the network.

The idea of the separate stream for LS is to expedite some of the LS 
messages (Busy, Busy Ended, PO, PR, OOS) past any queued messages at the 
receiving end.

For example: If node "A" is suffering from receive congestion (in SCTP 
or M2PA), and its peer "B" sends LS OOS (or LS PO), the message could 
get stuck for a relatively long time behind the data messages. In the 
meantime, A continues to send User Data messages to B. A does keep the 
messages in its retransmit queue, so they are available for 
changeover,so the messages are not lost. But it seems like this is not 
ideal. A might keep sending until its T7 timer expires, or until its 
MTP3 receives an XCO from B.

IMHO we should do what we can to expedite the LS messages. It would be 
even better to have some kind of prioritized stream scheme in SCTP, but 
you have to get by with what is available.

To me it looks like a tradeoff. The data stream makes the protocol 
complicated in places. But going to one stream means losing some ability 
to notify the other end of status changes in a timely manner.

tomG.

Brian F. G. Bidulock wrote:
> Tom,
> 
> Although it is hightly unlikely that a real network work
> place them close enough together for there to be a race,
> sending everything ordered on one stream would solve all
> racees.
> 
> If one wants to use Q.703 state machines for the most part
> then it appears that one should meet the same ordering
> characteristics as an Q.703 link.
> 
> --brian
> 
> Tom George wrote:   (Wed, 11 Jun 2003 17:35:53)
> 
>>But now you have a race condition between LS PO and LS PR.
>>
>>Brian F. G. Bidulock wrote:
>>
>>>Tom,
>>>
>>>Send LSPR ordered on stream 1 and there is no problem,
>>>because then the race condition between LS PR and DATA
>>>is removed.
>>>
>>>That is a simpler and more direct solution than expecting
>>>the receiver to resolve races.  It seems rather pointless
>>>to intentionally introduce races when SCTP provides an
>>>ordered delivery service.
>>>
>>>--brian
>>>
>>>Tom George wrote:  (Wed, 11 Jun 2003 15:12:47)
>>>
>>>
>>>>I think this problem can be avoided. Suppose that messages are
>>>>transmitted in this order:
>>>>
>>>>Type       FSN   stream
>>>>---------  ---   ------
>>>>User Data   1      1
>>>>User Data   2      1
>>>>LS PO       2      0
>>>>LS PR       2      0
>>>>User Data   3      1
>>>>
>>>>The User Data messages arrive in order and the LS messages arrive in
>>>>order on their respective streams. But there are no guarantees about
>>>>their order relative to each other.
>>>>
>>>>Tolga is concerned about the situation when the LS PR arrives after
>>>>the new User Data message. For example, say they arrive like this:
>>>>
>>>>User Data   1      1
>>>>LS PO       2      0
>>>>User Data   2      1
>>>>User Data   3      1
>>>>LS PR       2      0
>>>>
>>>>Does UD message 3 get unacked and thereby cause link failure?
>>>>
>>>>Here is what happens:
>>>>
>>>>User Data   1      1
>>>>
>>>>   Message is passed to MTP3.
>>>>
>>>>LS PO       2      0
>>>>
>>>>   Mark RPO and notify MTP3. Buffer but do not ack incoming messages.
>>>>
>>>>User Data   2      1
>>>>
>>>>   This message goes into the buffer-but-do-not-ack queue. The T7
>>>>   timer is _not_ running at the other end.
>>>>
>>>>User Data   3      1
>>>>
>>>>   This message goes into the buffer-but-do-not-ack queue. The T7
>>>>   timer _is_ running at the other end.
>>>>
>>>>LS PR       2      0
>>>>
>>>>   Notify MTP3 that the RPO has ended.
>>>>
>>>>   If MTP3 wants to Continue, then start processing the queued
>>>>   messages.
>>>>
>>>>   If MTP3 wants to Flush, then M2PA should not delete all messages
>>>>   willy-nilly. It should note that in the LS PR message, FSN =
>>>>   2. Therefore:
>>>>
>>>>      UD message 2 was sent before the PO, so flush it.
>>>>
>>>>      UD message 3 was sent after the PO, so process and ack it.
>>>>
>>>>tomG.
>>>>
>>>>Tolga Asveren wrote:
>>>>
>>>>
>>>>>Brian,
>>>>>--- "Brian F. G. Bidulock" <bidulock@openss7.org>
>>>>>wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Tolga,
>>>>>>
>>>>>>Yes.
>>>>>
>>>>>[TOLGA]But why? They are sent after local processor
>>>>>outage has ended. The sending side will keep timeout
>>>>>information for such a message (T7) and because it
>>>>>won't be acknowledged, link will be dropped.
>>>>>
>>>>>
>>>>>
>>>>>>--brian
>>>>>>
>>>>>>Tolga Asveren wrote:                                
>>>>>>                              (Wed, 04 Jun 2003
>>>>>>03:51:49)
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Brian,
>>>>>>>--- "Brian F. G. Bidulock" <bidulock@openss7.org>
>>>>>>>wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>Tolga,
>>>>>>>>
>>>>>>>>In SS7 flushed messages are never retransmitted.
>>>>>>>
>>>>>>>>This
>>>>>>>>is because they are old and stagnant by the time
>>>>>>>
>>>>>>the
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>Flush_buffers is issued and must be dicareded.
>>>>>>>
>>>>>>>[TOLGA] Yes, but should we qualify also messages
>>>>>>
>>>>>>sent
>>>>>>
>>>>>>
>>>>>>
>>>>>>>after local processor outage ended but received on
>>>>>>
>>>>>>the
>>>>>>
>>>>>>
>>>>>>
>>>>>>>other side before LSPR (because they are sent on
>>>>>>>different streams) as "old"?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>--brian
>>>>>>>>
>>>>>>>>Tolga Asveren wrote:                            
>>>>>>>
>>>>>> 
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>                              (Tue, 03 Jun
>>>>>>>
>>>>>>2003
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>13:18:29)
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>Tom,
>>>>>>>>>
>>>>>>>>>[..snip..]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>If M2PA receives a Flush command from MTP3,
>>>>>>>>>
>>>>>>M2PA
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>>>SHALL discard the
>>>>>>>>>>incoming messages that were queued and
>>>>>>>>>>unacknowledged during the
>>>>>>>>>>processor outage condition. Furthermore,
>>>>>>>>>
>>>>>>M2PA
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>SHALL
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>>discard messages
>>>>>>>>>>in the transmit and retransmit queues as
>>>>>>>>>
>>>>>>>>required by
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>>MTP2. 
>>>>>>>>>
>>>>>>>>>[TOLGA]So also messages sent after local
>>>>>>>>
>>>>>>processor
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>>outage ended but received before LSPR will be
>>>>>>>>>discarded(?). How are they going to be
>>>>>>>>
>>>>>>>>retransmitted?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>__________________________________
>>>>>>>>>Do you Yahoo!?
>>>>>>>>>Yahoo! Calendar - Free online calendar with
>>>>>>>>
>>>>>>sync
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>to Outlook(TM).
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>http://calendar.yahoo.com
>>>>>>>>>
>>>>>>>>
>>>>>>_______________________________________________
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>>Sigtran mailing list
>>>>>>>>>Sigtran@ietf.org
>>>>>>>>>https://www1.ietf.org/mailman/listinfo/sigtran
>>>>>>>>
>>>>>>>>-- 
>>>>>>>>Brian F. G. Bidulock
>>>>>>>>bidulock@openss7.org
>>>>>>>>http://www.openss7.org/
>>>>>>>>_______________________________________________
>>>>>>>>Sigtran mailing list
>>>>>>>>Sigtran@ietf.org
>>>>>>>>https://www1.ietf.org/mailman/listinfo/sigtran
>>>>>>>
>>>>>>>
>>>>>>>__________________________________
>>>>>>>Do you Yahoo!?
>>>>>>>Yahoo! Calendar - Free online calendar with sync
>>>>>>
>>>>>>to Outlook(TM).
>>>>>>
>>>>>>
>>>>>>
>>>>>>>http://calendar.yahoo.com
>>>>>>>_______________________________________________
>>>>>>>Sigtran mailing list
>>>>>>>Sigtran@ietf.org
>>>>>>>https://www1.ietf.org/mailman/listinfo/sigtran
>>>>>>
>>>>>>-- 
>>>>>>Brian F. G. Bidulock
>>>>>>bidulock@openss7.org
>>>>>>http://www.openss7.org/
>>>>>>_______________________________________________
>>>>>>Sigtran mailing list
>>>>>>Sigtran@ietf.org
>>>>>>https://www1.ietf.org/mailman/listinfo/sigtran
>>>>>
>>>>>
>>>>>
>>>>>__________________________________
>>>>>Do you Yahoo!?
>>>>>Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
>>>>>http://calendar.yahoo.com
>>>>>_______________________________________________
>>>>>Sigtran mailing list
>>>>>Sigtran@ietf.org
>>>>>https://www1.ietf.org/mailman/listinfo/sigtran
>>>>>
>>>>
>>>>
>>>>-- 
>>>>* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
>>>>* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
>>>>* Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
>>>>* I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
>>>>* to advertise or represent its position,  operations, or activities. *
>>>>
>>>>_______________________________________________
>>>>Sigtran mailing list
>>>>Sigtran@ietf.org
>>>>https://www1.ietf.org/mailman/listinfo/sigtran
>>>
>>>
>>
>>-- 
>>* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
>>* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
>>* Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
>>* I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
>>* to advertise or represent its position,  operations, or activities. *
>>
>>_______________________________________________
>>Sigtran mailing list
>>Sigtran@ietf.org
>>https://www1.ietf.org/mailman/listinfo/sigtran
> 
> 


-- 
* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
* Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
* I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
* to advertise or represent its position,  operations, or activities. *

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



From mailnull@www1.ietf.org  Fri Jun 13 13:17:12 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13661
	for <sigtran-archive@odin.ietf.org>; Fri, 13 Jun 2003 13:17:12 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5DHGjP25900
	for sigtran-archive@odin.ietf.org; Fri, 13 Jun 2003 13:16:45 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5DAX2a28578;
	Fri, 13 Jun 2003 06:33:02 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5DAWbm28549
	for <sigtran@optimus.ietf.org>; Fri, 13 Jun 2003 06:32:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27627
	for <sigtran@ietf.org>; Fri, 13 Jun 2003 06:32:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QlpC-0003UK-00
	for sigtran@ietf.org; Fri, 13 Jun 2003 06:30:26 -0400
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49] helo=albatross.tn.sw.ericsson.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19QlpB-0003UH-00
	for sigtran@ietf.org; Fri, 13 Jun 2003 06:30:26 -0400
Received: from esealnt612.al.sw.ericsson.se (alteon-nat1.sw.ericsson.se [153.88.254.118])
	by albatross.tn.sw.ericsson.se (8.12.9/8.12.9/WIREfire-1.6b) with ESMTP id h5DAWQG5023691;
	Fri, 13 Jun 2003 12:32:26 +0200 (MEST)
Received: from ESEALNT744.al.sw.ericsson.se ([153.88.251.4]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id LYGKXXVD; Fri, 13 Jun 2003 12:32:16 +0200
Received: by ESEALNT744.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <JNZ534Q1>; Fri, 13 Jun 2003 12:32:26 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C36@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
To: "'kakaul@hss.hns.com'" <kakaul@hss.hns.com>,
        Tolga Asveren
	 <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] Minor Corrections required in M3UA RFC 3332
Date: Fri, 13 Jun 2003 12:31:57 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Thanks guys, 

We'll include it for the next version we are baking...
We'll also send you the new proposal for the section 15 according to the consensus.

Cheers // Javier.

> -----Original Message-----
> From: kakaul@hss.hns.com [mailto:kakaul@hss.hns.com]
> Sent: viernes, 13 de junio de 2003 5:47
> To: Tolga Asveren
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] Minor Corrections required in M3UA RFC 3332
> 
> 
> 
> 
> 
> 
> Hi Tolga,
>    You are right correction in Section 1.3.2.3 is not required,
>     I misunderstood restricted to unavailable
>    Thanks for correction. Notify messages are the part of
>    protocol operations, i believe these should be shown
>    in message flow examples completely to avoid any
>    confusions.
> 
> Regards
> Kamesh
> 
> 
> 
> 
> Tolga Asveren <tolga_asveren@yahoo.com>@ietf.org on 
> 06/12/2003 06:12:37 PM
> 
> Sent by:    sigtran-admin@ietf.org
> 
> 
> To:    sigtran@ietf.org
> cc:
> 
> Subject:    Re: [Sigtran] Minor Corrections required in M3UA RFC 3332
> 
> 
> Hi Kamesh,
> --- kakaul@hss.hns.com wrote:
> >
> >
> >
> >
> >
> > Hi
> >       Some minor corrections required in RFC 3332
> >
> > Section 1.3.2.3 :
> > old text  - Providing an indication to the M3UA
> > layer
> > at an ASP that the routes to a destination in the
> > SS7 network
> > are restricted.
> >
> > New text  - Providing an indication to MTP3-Users at
> > an ASP
> > that the routes to a destination in the SS7 network
> > are restricted.
> [TOLGA]There is no defined indication to MTP3-Users
> for restricted case(and it is also not necessary, they
> don't care how a message is routed -via this or that
> SG-, what they care is whether the destination is
> reachable or not)
> >
> > Sections 5.1.1.2, 5.1.1.3, 5.1.1.4 :
> > Local Routing Context (LRC)should be replaced with
> > Local Routing Key identifier (LRK)
> >
> > Section 5.1.2:
> > NOTIFY (AS-ACTIVE) missing in the message sequence
> >
> > Section 5.1.4:
> > NOTIFY (AS-ACTIVE) missing in the message sequence
> > from SGP to ASP1
> [TOLGA]Those are not the only missing NTFYs in this
> section but we have at he beginning of section5:
> "NOTE: Not all the Notify messages that are
> appropriate per the Notify procedures are shown in
> these examples."
> I don't know whether the whole section 5 should be
> revised to include necessary NTFYs(?).
> 
> >
> > Section 5.3:
> > LRCn is not required in DEREGISTER RESPONSE message
> >
> > Regards
> > Kamesh
> > Hughes Software Systems
> >
> >
> >
> > "DISCLAIMER: This message is proprietary to Hughes
> > Software Systems Limited
> > (HSS) and is intended solely for the use of the
> > individual to whom it is
> > addressed. It may contain  privileged or
> > confidential information and
> > should not be circulated or used for any purpose
> > other than for what it is
> > intended. If you have received this message in
> > error, please notify the
> > originator immediately. If you are not the intended
> > recipient, you are
> > notified that you are strictly prohibited from
> > using, copying, altering, or
> > disclosing the contents of this message. HSS accepts
> > no responsibility for
> > loss or damage arising from the use of the
> > information transmitted by this
> > email including damage from virus."
> >
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
> http://calendar.yahoo.com
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
>  https://www1.ietf.org/mailman/listinfo/sigtran
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Fri Jun 13 14:37:33 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17469
	for <sigtran-archive@odin.ietf.org>; Fri, 13 Jun 2003 14:37:33 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5DHNTw21864
	for sigtran-archive@odin.ietf.org; Fri, 13 Jun 2003 13:23:29 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5DEW4a15686;
	Fri, 13 Jun 2003 10:32:04 -0400
Received: from ietf.org (lists.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5DEVfm15666
	for <sigtran@optimus.ietf.org>; Fri, 13 Jun 2003 10:31:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08093
	for <SIGTRAN@ietf.org>; Fri, 13 Jun 2003 10:31:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QpYX-0005qM-00
	for SIGTRAN@ietf.org; Fri, 13 Jun 2003 10:29:29 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[FQZnWQH9pkRk7iKldq3z0fqm2ZRE8CZJ])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QpYU-0005qD-00
	for SIGTRAN@ietf.org; Fri, 13 Jun 2003 10:29:27 -0400
Received: from ns.pigworks.openss7.net (IDENT:mLCHVMaXpCsrQd7hoDLgtgscLCZprUY4@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5DEVQX14547;
	Fri, 13 Jun 2003 08:31:26 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5DEVQh07783;
	Fri, 13 Jun 2003 08:31:26 -0600
Date: Fri, 13 Jun 2003 08:31:26 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tom George <Tom.George@alcatel.com>
Cc: SIGTRAN e-mail list <SIGTRAN@ietf.org>
Subject: Re: [Sigtran] (M2PA) Comments on M2PA v8
Message-ID: <20030613083125.A7599@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tom George <Tom.George@alcatel.com>,
	SIGTRAN e-mail list <SIGTRAN@ietf.org>
References: <20030604175601.74616.qmail@web12804.mail.yahoo.com> <3EE78D3F.40004@alcatel.com> <20030611160451.A7104@openss7.org> <3EE7AEC9.4070403@alcatel.com> <20030611200331.B10555@openss7.org> <3EE8EB37.6020706@alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <3EE8EB37.6020706@alcatel.com>; from Tom.George@alcatel.com on Thu, Jun 12, 2003 at 04:05:59PM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id h5DEVQX14547
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h5DEVfm15667
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Tom,

On Thu, 12 Jun 2003, Tom George wrote:

> Likewise, I think the probability of the User Data with FSN=3 arriving 
> ahead of the LS PR is very small, too. The LS PR is sent first and in 
> all likelihood the UD message will follow the LS message along the same 
> path through the network.
> 
> The idea of the separate stream for LS is to expedite some of the LS 
> messages (Busy, Busy Ended, PO, PR, OOS) past any queued messages at the 
> receiving end.
> 
> For example: If node "A" is suffering from receive congestion (in SCTP 
> or M2PA), and its peer "B" sends LS OOS (or LS PO), the message could 
> get stuck for a relatively long time behind the data messages. In the 
> meantime, A continues to send User Data messages to B. A does keep the 
> messages in its retransmit queue, so they are available for 
> changeover,so the messages are not lost. But it seems like this is not 
> ideal. A might keep sending until its T7 timer expires, or until its 
> MTP3 receives an XCO from B.

XCO must arrive within 0.5 seconds (1/2 T7) for Q.704 if this is not the
last link.  If it is the last link the point is moot.

Besides that, LS OOS does not have to be sent on another stream to be
expedited.  It could be sent unordered.

There is no similar argument for any other LS message.  It is the other
LS messages that have the race conditions.

So, send them all on one stream and send LS OOS unordered (and periodic).

> 
> IMHO we should do what we can to expedite the LS messages. It would be 
> even better to have some kind of prioritized stream scheme in SCTP, but 
> you have to get by with what is available.
> 
> To me it looks like a tradeoff. The data stream makes the protocol 
> complicated in places. But going to one stream means losing some ability 
> to notify the other end of status changes in a timely manner.

See different solution above.

--brian

> 
> tomG.
> 
> Brian F. G. Bidulock wrote:
> > Tom,
> > 
> > Although it is hightly unlikely that a real network work
> > place them close enough together for there to be a race,
> > sending everything ordered on one stream would solve all
> > racees.
> > 
> > If one wants to use Q.703 state machines for the most part
> > then it appears that one should meet the same ordering
> > characteristics as an Q.703 link.
> > 
> > --brian
> > 
> > Tom George wrote:   (Wed, 11 Jun 2003 17:35:53)
> > 
> >>But now you have a race condition between LS PO and LS PR.
> >>
> >>Brian F. G. Bidulock wrote:
> >>
> >>>Tom,
> >>>
> >>>Send LSPR ordered on stream 1 and there is no problem,
> >>>because then the race condition between LS PR and DATA
> >>>is removed.
> >>>
> >>>That is a simpler and more direct solution than expecting
> >>>the receiver to resolve races.  It seems rather pointless
> >>>to intentionally introduce races when SCTP provides an
> >>>ordered delivery service.
> >>>
> >>>--brian
> >>>
> >>>Tom George wrote:  (Wed, 11 Jun 2003 15:12:47)
> >>>
> >>>
> >>>>I think this problem can be avoided. Suppose that messages are
> >>>>transmitted in this order:
> >>>>
> >>>>Type       FSN   stream
> >>>>---------  ---   ------
> >>>>User Data   1      1
> >>>>User Data   2      1
> >>>>LS PO       2      0
> >>>>LS PR       2      0
> >>>>User Data   3      1
> >>>>
> >>>>The User Data messages arrive in order and the LS messages arrive in
> >>>>order on their respective streams. But there are no guarantees about
> >>>>their order relative to each other.
> >>>>
> >>>>Tolga is concerned about the situation when the LS PR arrives after
> >>>>the new User Data message. For example, say they arrive like this:
> >>>>
> >>>>User Data   1      1
> >>>>LS PO       2      0
> >>>>User Data   2      1
> >>>>User Data   3      1
> >>>>LS PR       2      0
> >>>>
> >>>>Does UD message 3 get unacked and thereby cause link failure?
> >>>>
> >>>>Here is what happens:
> >>>>
> >>>>User Data   1      1
> >>>>
> >>>>   Message is passed to MTP3.
> >>>>
> >>>>LS PO       2      0
> >>>>
> >>>>   Mark RPO and notify MTP3. Buffer but do not ack incoming messages.
> >>>>
> >>>>User Data   2      1
> >>>>
> >>>>   This message goes into the buffer-but-do-not-ack queue. The T7
> >>>>   timer is _not_ running at the other end.
> >>>>
> >>>>User Data   3      1
> >>>>
> >>>>   This message goes into the buffer-but-do-not-ack queue. The T7
> >>>>   timer _is_ running at the other end.
> >>>>
> >>>>LS PR       2      0
> >>>>
> >>>>   Notify MTP3 that the RPO has ended.
> >>>>
> >>>>   If MTP3 wants to Continue, then start processing the queued
> >>>>   messages.
> >>>>
> >>>>   If MTP3 wants to Flush, then M2PA should not delete all messages
> >>>>   willy-nilly. It should note that in the LS PR message, FSN =
> >>>>   2. Therefore:
> >>>>
> >>>>      UD message 2 was sent before the PO, so flush it.
> >>>>
> >>>>      UD message 3 was sent after the PO, so process and ack it.
> >>>>
> >>>>tomG.
> >>>>
> >>>>Tolga Asveren wrote:
> >>>>
> >>>>
> >>>>>Brian,
> >>>>>--- "Brian F. G. Bidulock" <bidulock@openss7.org>
> >>>>>wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>>Tolga,
> >>>>>>
> >>>>>>Yes.
> >>>>>
> >>>>>[TOLGA]But why? They are sent after local processor
> >>>>>outage has ended. The sending side will keep timeout
> >>>>>information for such a message (T7) and because it
> >>>>>won't be acknowledged, link will be dropped.
> >>>>>
> >>>>>
> >>>>>
> >>>>>>--brian
> >>>>>>
> >>>>>>Tolga Asveren wrote:                                
> >>>>>>                              (Wed, 04 Jun 2003
> >>>>>>03:51:49)
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>Brian,
> >>>>>>>--- "Brian F. G. Bidulock" <bidulock@openss7.org>
> >>>>>>>wrote:
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>>Tolga,
> >>>>>>>>
> >>>>>>>>In SS7 flushed messages are never retransmitted.
> >>>>>>>
> >>>>>>>>This
> >>>>>>>>is because they are old and stagnant by the time
> >>>>>>>
> >>>>>>the
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>>Flush_buffers is issued and must be dicareded.
> >>>>>>>
> >>>>>>>[TOLGA] Yes, but should we qualify also messages
> >>>>>>
> >>>>>>sent
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>after local processor outage ended but received on
> >>>>>>
> >>>>>>the
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>other side before LSPR (because they are sent on
> >>>>>>>different streams) as "old"?
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>>--brian
> >>>>>>>>
> >>>>>>>>Tolga Asveren wrote:                            
> >>>>>>>
> >>>>>> 
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>>                              (Tue, 03 Jun
> >>>>>>>
> >>>>>>2003
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>>13:18:29)
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>>Tom,
> >>>>>>>>>
> >>>>>>>>>[..snip..]
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>>If M2PA receives a Flush command from MTP3,
> >>>>>>>>>
> >>>>>>M2PA
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>>>>SHALL discard the
> >>>>>>>>>>incoming messages that were queued and
> >>>>>>>>>>unacknowledged during the
> >>>>>>>>>>processor outage condition. Furthermore,
> >>>>>>>>>
> >>>>>>M2PA
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>>SHALL
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>>>discard messages
> >>>>>>>>>>in the transmit and retransmit queues as
> >>>>>>>>>
> >>>>>>>>required by
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>>>MTP2. 
> >>>>>>>>>
> >>>>>>>>>[TOLGA]So also messages sent after local
> >>>>>>>>
> >>>>>>processor
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>>>outage ended but received before LSPR will be
> >>>>>>>>>discarded(?). How are they going to be
> >>>>>>>>
> >>>>>>>>retransmitted?
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>>__________________________________
> >>>>>>>>>Do you Yahoo!?
> >>>>>>>>>Yahoo! Calendar - Free online calendar with
> >>>>>>>>
> >>>>>>sync
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>>to Outlook(TM).
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>>http://calendar.yahoo.com
> >>>>>>>>>
> >>>>>>>>
> >>>>>>_______________________________________________
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>>>Sigtran mailing list
> >>>>>>>>>Sigtran@ietf.org
> >>>>>>>>>https://www1.ietf.org/mailman/listinfo/sigtran
> >>>>>>>>
> >>>>>>>>-- 
> >>>>>>>>Brian F. G. Bidulock
> >>>>>>>>bidulock@openss7.org
> >>>>>>>>http://www.openss7.org/
> >>>>>>>>_______________________________________________
> >>>>>>>>Sigtran mailing list
> >>>>>>>>Sigtran@ietf.org
> >>>>>>>>https://www1.ietf.org/mailman/listinfo/sigtran
> >>>>>>>
> >>>>>>>
> >>>>>>>__________________________________
> >>>>>>>Do you Yahoo!?
> >>>>>>>Yahoo! Calendar - Free online calendar with sync
> >>>>>>
> >>>>>>to Outlook(TM).
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>http://calendar.yahoo.com
> >>>>>>>_______________________________________________
> >>>>>>>Sigtran mailing list
> >>>>>>>Sigtran@ietf.org
> >>>>>>>https://www1.ietf.org/mailman/listinfo/sigtran
> >>>>>>
> >>>>>>-- 
> >>>>>>Brian F. G. Bidulock
> >>>>>>bidulock@openss7.org
> >>>>>>http://www.openss7.org/
> >>>>>>_______________________________________________
> >>>>>>Sigtran mailing list
> >>>>>>Sigtran@ietf.org
> >>>>>>https://www1.ietf.org/mailman/listinfo/sigtran
> >>>>>
> >>>>>
> >>>>>
> >>>>>__________________________________
> >>>>>Do you Yahoo!?
> >>>>>Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
> >>>>>http://calendar.yahoo.com
> >>>>>_______________________________________________
> >>>>>Sigtran mailing list
> >>>>>Sigtran@ietf.org
> >>>>>https://www1.ietf.org/mailman/listinfo/sigtran
> >>>>>
> >>>>
> >>>>
> >>>>-- 
> >>>>* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
> >>>>* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
> >>>>* Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
> >>>>* I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
> >>>>* to advertise or represent its position,  operations, or activities. *
> >>>>
> >>>>_______________________________________________
> >>>>Sigtran mailing list
> >>>>Sigtran@ietf.org
> >>>>https://www1.ietf.org/mailman/listinfo/sigtran
> >>>
> >>>
> >>
> >>-- 
> >>* Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
> >>* 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
> >>* Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
> >>* I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
> >>* to advertise or represent its position,  operations, or activities. *
> >>
> >>_______________________________________________
> >>Sigtran mailing list
> >>Sigtran@ietf.org
> >>https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> > 
> 
> 
> -- 
> * Tom George       PB7-24001 (near B-21)      Tom.George@alcatel.com  *
> * 972-519-3168   Intranet:  http://www.ssd.usa.alcatel.com/~tgeorge/  *
> * Alcatel;  3400 West Plano Pkwy,  MS PB7-SWPRO;  Plano, Texas 75075  *
> * I actively disclaim speaking for Alcatel USA, Inc. I do not purport *
> * to advertise or represent its position,  operations, or activities. *
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

-- 
Brian F. G. Bidulock    ¦ The reasonable man adapts himself to the ¦
bidulock@openss7.org    ¦ world; the unreasonable one persists in  ¦
http://www.openss7.org/ ¦ trying  to adapt the  world  to himself. ¦
                        ¦ Therefore  all  progress  depends on the ¦
                        ¦ unreasonable man. -- George Bernard Shaw ¦
_______________________________________________
Sigtran mailing list
Sigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/sigtran



From mailnull@www1.ietf.org  Mon Jun 16 14:14:24 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23867
	for <sigtran-archive@odin.ietf.org>; Mon, 16 Jun 2003 14:14:24 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5GIDug23840
	for sigtran-archive@odin.ietf.org; Mon, 16 Jun 2003 14:13:56 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GBv2a28217;
	Mon, 16 Jun 2003 07:57:02 -0400
Received: from ietf.org (lists.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GBu9m28178
	for <sigtran@optimus.ietf.org>; Mon, 16 Jun 2003 07:56:09 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09140;
	Mon, 16 Jun 2003 07:56:07 -0400 (EDT)
Message-Id: <200306161156.HAA09140@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sigtran@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Mon, 16 Jun 2003 07:56:07 -0400
Subject: [Sigtran] I-D ACTION:draft-ietf-sigtran-m3ua-mib-05.txt
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Signaling Transport Working Group of the IETF.

	Title		: SS7 MTP3-User Adaptation Layer (M3UA)Management 
                          Information Base using SMIv2
	Author(s)	: A. Roque et al.
	Filename	: draft-ietf-sigtran-m3ua-mib-05.txt
	Pages		: 65
	Date		: 2003-6-13
	
The MTP3-User Adaptation Layer is a protocol for the transport of any SS7 TP3-User signalling (e.g., ISUP and SCCP messages) over IP using the
services of the Stream Control Transmission Protocol. Also, provision is
made for protocol elements that enable a seamless operation of the MTP3-
User peers in the SS7 and IP domains. This protocol would be used between a Signalling Gateway (SG) and a Media Gateway Controller (MGC) or IP-resident Database. It is assumed that the SG receives SS7 signaling over a standard SS7 interface using the SS7 Message Transfer Part (MTP) to provide transport.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-mib-05.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-sigtran-m3ua-mib-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sigtran-m3ua-mib-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-6-16080901.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sigtran-m3ua-mib-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sigtran-m3ua-mib-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-6-16080901.I-D@ietf.org>

--OtherAccess--

--NextPart--


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



From mailnull@www1.ietf.org  Tue Jun 17 01:12:13 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17165
	for <sigtran-archive@odin.ietf.org>; Tue, 17 Jun 2003 01:12:13 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5H5BiW07099
	for sigtran-archive@odin.ietf.org; Tue, 17 Jun 2003 01:11:44 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5H3STa31570;
	Mon, 16 Jun 2003 23:28:29 -0400
Received: from ietf.org (lists.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5H3Q4m31420
	for <sigtran@optimus.ietf.org>; Mon, 16 Jun 2003 23:26:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14795
	for <sigtran@ietf.org>; Mon, 16 Jun 2003 23:25:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S74M-00025g-00
	for sigtran@ietf.org; Mon, 16 Jun 2003 23:23:38 -0400
Received: from [203.196.162.59] (helo=india.mercurykr.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19S74L-00025Z-00
	for sigtran@ietf.org; Mon, 16 Jun 2003 23:23:37 -0400
Received: from srivatsp (mercury-33-162-del.mercurykr.com [203.196.162.33] (may be forged))
	by india.mercurykr.com (8.12.5/8.11.2) with SMTP id h5H3LXdd009260
	for <sigtran@ietf.org>; Tue, 17 Jun 2003 08:51:34 +0530
Message-Id: <200306170321.h5H3LXdd009260@india.mercurykr.com>
Date: Tue, 17 Jun 2003 8:51:56 +0500
From: "Srivats P." <srivats@india.mercurykr.com>
To: sigtran <sigtran@ietf.org>
Subject: Re: [Sigtran] I-D ACTION:draft-ietf-sigtran-m3ua-mib-05.txt
Organization: Mercury Corporation, India
X-mailer: FoxMail 2.1 [en]
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,

Just glanced over the latest M3UA MIB draft. Seems to be a
complete overhaul. Looks good. Will check in detail and get
back with issues/nits asap.

Regards,
Srivats P.

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



From mailnull@www1.ietf.org  Tue Jun 17 14:45:49 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02265
	for <sigtran-archive@odin.ietf.org>; Tue, 17 Jun 2003 14:45:49 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5HIjMT21966
	for sigtran-archive@odin.ietf.org; Tue, 17 Jun 2003 14:45:22 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5HEJ4a32161;
	Tue, 17 Jun 2003 10:19:04 -0400
Received: from ietf.org (lists.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5HEIxm32132
	for <sigtran@optimus.ietf.org>; Tue, 17 Jun 2003 10:18:59 -0400
Received: from albatross.tn.sw.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18440
	for <sigtran@ietf.org>; Tue, 17 Jun 2003 10:18:55 -0400 (EDT)
Received: from esealnt610.al.sw.ericsson.se (alteon-nat3.sw.ericsson.se [153.88.254.120])
	by albatross.tn.sw.ericsson.se (8.12.9/8.12.9/WIREfire-1.6b) with ESMTP id h5HEItG5006033
	for <sigtran@ietf.org>; Tue, 17 Jun 2003 16:18:55 +0200 (MEST)
Received: from ESEALNT744.al.sw.ericsson.se ([153.88.251.4]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id LYG2GQ9V; Tue, 17 Jun 2003 16:20:44 +0200
Received: by ESEALNT744.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NBCQ8FM3>; Tue, 17 Jun 2003 16:18:56 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C5E@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>
Cc: =?iso-8859-1?Q?Antonio_Ca=F1ete_=28ECE=29?=
	 <antonio.canete-martinez@ece.ericsson.se>
Date: Tue, 17 Jun 2003 16:17:17 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sigtran] M3UA IG: section 3.15 reworked
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


Hi guys, 

Here is the proposed rework for section 3.15 of the IG. We have included 

This proposal includes the latest agreements: arrive to AS-ACTIVE only after n ASPs are in ASP-ACTIVE state but moving to AS-PENDING only when all the ASPs have failed (state != ASP-ACTIVE). Changes with the previous version are therefore concentrated on AS-ACTIVE and AS-PENDING states and their transitions.

Cheers // Javier.



--------- 
Old text: (Section 4.3.2) 
---------

AS-DOWN: The Application Server is unavailable.  This state implies 
that all related ASPs are in the ASP-DOWN state for this AS. Initially the AS will be in this state. An Application Server is in the AS-DOWN state when it is removed from a configuration.

AS-INACTIVE: The Application Server is available but no application 
traffic is active (i.e., one or more related ASPs are in the ASP-
INACTIVE state, but none in the ASP-ACTIVE state).  The recovery 
timer T(r) is not running or has expired. 

AS-ACTIVE: The Application Server is available and application traffic is active.  This state implies that at least one ASP is in the ASP-ACTIVE state.

AS-PENDING: An active ASP has transitioned to ASP-INACTIVE or ASP-DOWN  and it was the last remaining active ASP in the AS.  A recovery timer T(r) SHOULD be started and all incoming signalling messages SHOULD be queued by the SGP. If an ASP becomes ASP-ACTIVE before T(r) expires, the AS is moved to the AS-ACTIVE state and all the queued messages will be sent to the ASP. 

If T(r) expires before an ASP becomes ASP-ACTIVE, and the SGP has no 
alternative, the SGP may stops queuing messages and discards all 
previously queued messages. The AS will move to the AS-INACTIVE state 
if at least one ASP is in ASP-INACTIVE state, otherwise it will move 
to AS-DOWN state. 

Figure 5 shows an example AS state machine for the case where the 
AS/ASP data is preconfigured.  For other cases where the AS/ASP 
configuration data is created dynamically, there would be differences 
in the state machine, especially at creation of the AS.  

                 Figure 5: AS State Transition Diagram

     +----------+   one ASP trans to ACTIVE   +-------------+
     |    AS-   |---------------------------->|     AS-     |      
     | INACTIVE |                             |   ACTIVE    |
     |          |<---                         |             |
     +----------+    \                        +-------------+
        ^   |         \ Tr Expiry,                ^    |
        |   |          \ at least one             |    |
        |   |           \ ASP in ASP-INACTIVE     |    |
        |   |            \                        |    |
        |   |             \                       |    |
        |   |              \                      |    |
one ASP |   | all ASP       \            one ASP  |    | Last ACTIVE
trans   |   | trans to       \           trans to |    | ASP trans to
to      |   | ASP-DOWN        -------\   ASP-     |    | ASP-INACTIVE
ASP-    |   |                         \  ACTIVE   |    | or ASP-DOWN
INACTIVE|   |                          \          |    |  (start Tr)
        |   |                           \         |    |
        |   |                            \        |    |
        |   v                             \       |    v         
     +----------+                          \  +-------------+
     |          |                           --|             |      
     | AS-DOWN  |                             | AS-PENDING  |
     |          |                             |  (queueing) |
     |          |<----------------------------|             |
     +----------+    Tr Expiry and no ASP     +-------------+
                     in ASP-INACTIVE state)   

 Tr = Recovery Timer



For example, where the AS/ASP configuration data is not created until 
Registration of the first ASP, the AS-INACTIVE state is entered 
directly upon the first successful REG REQ from an ASP.  Another 
example is where the AS/ASP configuration data is not created until the first ASP successfully enters the ASP-ACTIVE state.  In this case the AS-ACTIVE state is entered directly.


--------- 
New text: (Section 4.3.2) 
---------

AS-DOWN: The Application Server is unavailable.  This state implies that the number of ASPs being in ASP-INACTIVE or ASP-ACTIVE is less than "n". Initially the AS will be in this state. An Application Server is in the AS-DOWN state when it is removed from a configuration.

AS-INACTIVE: The Application Server is available but no application traffic is active. This implies that there are at least n ASPs in either ASP-INACTIVE or ASP-ACTIVE but the total number of ASPs in ASP-ACTIVE state has not reach n.  The recovery timer T(r) is not running or has expired. 

AS-ACTIVE: The Application Server is available and application traffic is active. The AS moves to this state after being in AS-INACTIVE and getting n ASPs in ASP-ACTIVE state or, after reaching AS-ACTIVE and keeping one or more ASPs in ASP-ACTIVE state. 

AS-PENDING: The last active ASP has transitioned from ASP-ACTIVE to ASP-INACTIVE or ASP-DOWN.  A recovery timer T(r) SHOULD be started and all incoming signalling messages SHOULD be queued by the SGP. If an ASP becomes ASP-ACTIVE before T(r) expires, the AS is moved to the AS-ACTIVE state and all the queued messages will be sent to the ASP. 

If T(r) expires before an ASP becomes ASP-ACTIVE, the SGP MAY stops queuing messages and discards all 
previously queued messages. The AS will move to the AS-INACTIVE state 
if at least the number of ASPs in either ASP-INACTIVE or ASP-ACTIVE sum n, otherwise it will move to AS-DOWN state. 

Figure 5 shows an example AS state machine for the case where the 
AS/ASP data is preconfigured and an n+k redundancy model. 


             Figure 5: AS State Transition Diagram

                   
     +----------+          IA2AC              +-------------+
     |    AS-   |---------------------------->|     AS-     |
     | INACTIVE |                             |   ACTIVE    |
     |          |<-----------                 |             |
     +----------+            \                +-------------+
        ^   |                 \                    ^   |
        |   | IA2DN            \ PN2IA             |   | AC2PN
        |   |                   \                  |   | 
  DN2IA |   |                    \          PN2AC  |   | 
        |   v                     \                |   v
     +----------+                  \          +-------------+
     |          |                   ----------|             |
     | AS-DOWN  |                             | AS-PENDING  |
     |          |                  PN2DN      |  (queueing) |
     |          |<----------------------------|             |
     +----------+                             +-------------+



DN2IA: One ASP moves to ASP-INACTIVE causing that n ASPs are in either ASP-ACTIVE or ASP-INACTIVE states.

IA2DN: One ASP moves to ASP-DOWN causing that the number of ASPs in either ASP-ACTIVE or ASP-INACTIVE drops below n.

IA2AC: one ASP moves to ASP-ACTIVE, causing number of ASPs in the ASP-ACTIVE state to be n.

AC2PN: the last ASP in ASP-ACTIVE state moves to ASP-INACTIVE or ASP-DOWN states, causing the number of ASPs in ASP-ACTIVE drop below 1.

PN2AC: One ASP moves to ASP-ACTIVE.

PN2IA: T(r) Expiry, n or more ASPs are in either ASP-INACTIVE.

PN2DN: T(r) Expiry, the number of ASPs in either ASP-INACTIVE state is less than n.

As a general rule, an AS becomes AS-ACTIVE right after n ASPs reach the ASP-ACTIVE state during the start-up phase. Once the traffic is flowing, an AS keeps the AS-ACTIVE state till the last ASP turns to another state different to ASP-ACTIVE. As "n" is considered to be the maximum engineered load, this will avoid


There are other cases where the AS/ASP configuration data is created dynamically. In those cases there would be differences in the state machine, especially at creation of the AS. For example, where the AS/ASP configuration data is not created until Registration of the first ASP, the AS-INACTIVE state is entered directly upon the nth successful REG REQ from an ASP belonging to that AS.  Another example is where the AS/ASP configuration data is not created until the nth ASP successfully enters the ASP-ACTIVE state.  In this latter case the AS-ACTIVE state is entered directly.

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



From mailnull@www1.ietf.org  Tue Jun 17 14:46:40 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02298
	for <sigtran-archive@odin.ietf.org>; Tue, 17 Jun 2003 14:46:40 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5HIkD922142
	for sigtran-archive@odin.ietf.org; Tue, 17 Jun 2003 14:46:13 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5HEq5a02496;
	Tue, 17 Jun 2003 10:52:05 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5HEpim02471
	for <sigtran@optimus.ietf.org>; Tue, 17 Jun 2003 10:51:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20583
	for <sigtran@ietf.org>; Tue, 17 Jun 2003 10:51:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SHm0-0000ET-00
	for sigtran@ietf.org; Tue, 17 Jun 2003 10:49:24 -0400
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49] helo=albatross.tn.sw.ericsson.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SHm0-0000EQ-00
	for sigtran@ietf.org; Tue, 17 Jun 2003 10:49:24 -0400
Received: from esealnt611.al.sw.ericsson.se (alteon-nat4.sw.ericsson.se [153.88.254.121])
	by albatross.tn.sw.ericsson.se (8.12.9/8.12.9/WIREfire-1.6b) with ESMTP id h5HEpaG5012211;
	Tue, 17 Jun 2003 16:51:36 +0200 (MEST)
Received: from ESEALNT744.al.sw.ericsson.se ([153.88.251.4]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id LVYQ1XK6; Tue, 17 Jun 2003 16:53:04 +0200
Received: by ESEALNT744.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NBCQ8F0G>; Tue, 17 Jun 2003 16:51:37 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C61@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>,
        "'sigtran@ietf.org'" <sigtran@ietf.org>
Cc: "Ken Morneault (E-mail)" <kmorneau@cisco.com>,
        =?iso-8859-1?Q?Anton?=
	=?iso-8859-1?Q?io_Ca=F1ete_=28ECE=29?=
	 <antonio.canete-martinez@ece.ericsson.se>
Date: Tue, 17 Jun 2003 16:51:16 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sigtran] RE: M3UA IG: section 3.15 reworked
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

This is the last version. There were still some unfinished sentences and inconsistences in the first text I sent. Now, they are fixed.

Cheers // Javier.


--------- 
Old text: (Section 4.3.2) 
---------

AS-DOWN: The Application Server is unavailable.  This state implies 
that all related ASPs are in the ASP-DOWN state for this AS. Initially the AS will be in this state. An Application Server is in the AS-DOWN state when it is removed from a configuration.

AS-INACTIVE: The Application Server is available but no application 
traffic is active (i.e., one or more related ASPs are in the ASP-
INACTIVE state, but none in the ASP-ACTIVE state).  The recovery 
timer T(r) is not running or has expired. 

AS-ACTIVE: The Application Server is available and application traffic is active.  This state implies that at least one ASP is in the ASP-ACTIVE state.

AS-PENDING: An active ASP has transitioned to ASP-INACTIVE or ASP-DOWN  and it was the last remaining active ASP in the AS.  A recovery timer T(r) SHOULD be started and all incoming signalling messages SHOULD be queued by the SGP. If an ASP becomes ASP-ACTIVE before T(r) expires, the AS is moved to the AS-ACTIVE state and all the queued messages will be sent to the ASP. 

If T(r) expires before an ASP becomes ASP-ACTIVE, and the SGP has no 
alternative, the SGP may stops queuing messages and discards all 
previously queued messages. The AS will move to the AS-INACTIVE state 
if at least one ASP is in ASP-INACTIVE state, otherwise it will move 
to AS-DOWN state. 

Figure 5 shows an example AS state machine for the case where the 
AS/ASP data is preconfigured.  For other cases where the AS/ASP 
configuration data is created dynamically, there would be differences 
in the state machine, especially at creation of the AS.  

                 Figure 5: AS State Transition Diagram

     +----------+   one ASP trans to ACTIVE   +-------------+
     |    AS-   |---------------------------->|     AS-     |      
     | INACTIVE |                             |   ACTIVE    |
     |          |<---                         |             |
     +----------+    \                        +-------------+
        ^   |         \ Tr Expiry,                ^    |
        |   |          \ at least one             |    |
        |   |           \ ASP in ASP-INACTIVE     |    |
        |   |            \                        |    |
        |   |             \                       |    |
        |   |              \                      |    |
one ASP |   | all ASP       \            one ASP  |    | Last ACTIVE
trans   |   | trans to       \           trans to |    | ASP trans to
to      |   | ASP-DOWN        -------\   ASP-     |    | ASP-INACTIVE
ASP-    |   |                         \  ACTIVE   |    | or ASP-DOWN
INACTIVE|   |                          \          |    |  (start Tr)
        |   |                           \         |    |
        |   |                            \        |    |
        |   v                             \       |    v         
     +----------+                          \  +-------------+
     |          |                           --|             |      
     | AS-DOWN  |                             | AS-PENDING  |
     |          |                             |  (queueing) |
     |          |<----------------------------|             |
     +----------+    Tr Expiry and no ASP     +-------------+
                     in ASP-INACTIVE state)   

 Tr = Recovery Timer



For example, where the AS/ASP configuration data is not created until 
Registration of the first ASP, the AS-INACTIVE state is entered 
directly upon the first successful REG REQ from an ASP.  Another 
example is where the AS/ASP configuration data is not created until the first ASP successfully enters the ASP-ACTIVE state.  In this case the AS-ACTIVE state is entered directly.


--------- 
New text: (Section 4.3.2) 
---------

AS-DOWN: The Application Server is unavailable.  This state implies that the number of ASPs being in ASP-INACTIVE or ASP-ACTIVE is less than "n". Initially the AS will be in this state. An Application Server is in the AS-DOWN state when it is removed from a configuration.

AS-INACTIVE: The Application Server is available but no application traffic is active. This implies that there are at least n ASPs in either ASP-INACTIVE or ASP-ACTIVE but the total number of ASPs in ASP-ACTIVE state has not reach n.  The recovery timer T(r) is not running or has expired. 

AS-ACTIVE: The Application Server is available and application traffic is active. The AS moves to this state after being in AS-INACTIVE and getting n ASPs in ASP-ACTIVE state or, after reaching AS-ACTIVE and keeping one or more ASPs in ASP-ACTIVE state. 

AS-PENDING: The last active ASP has transitioned from ASP-ACTIVE to ASP-INACTIVE or ASP-DOWN.  A recovery timer T(r) SHOULD be started and all incoming signalling messages SHOULD be queued by the SGP. If an ASP becomes ASP-ACTIVE before T(r) expires, the AS is moved to the AS-ACTIVE state and all the queued messages will be sent to the ASP. 

If T(r) expires before an ASP becomes ASP-ACTIVE, the SGP MAY stops queuing messages and discards all 
previously queued messages. The AS will move to the AS-INACTIVE state 
if at least the number of ASPs in ASP-INACTIVE sum n, otherwise it will move to AS-DOWN state. 

Figure 5 shows an example AS state machine for the case where the 
AS/ASP data is preconfigured and an n+k redundancy model. 


             Figure 5: AS State Transition Diagram

                   
     +----------+          IA2AC              +-------------+
     |    AS-   |---------------------------->|     AS-     |
     | INACTIVE |                             |   ACTIVE    |
     |          |<-----------                 |             |
     +----------+            \                +-------------+
        ^   |                 \                    ^   |
        |   | IA2DN            \ PN2IA             |   | AC2PN
        |   |                   \                  |   | 
  DN2IA |   |                    \          PN2AC  |   | 
        |   v                     \                |   v
     +----------+                  \          +-------------+
     |          |                   ----------|             |
     | AS-DOWN  |                             | AS-PENDING  |
     |          |                  PN2DN      |  (queueing) |
     |          |<----------------------------|             |
     +----------+                             +-------------+



DN2IA: One ASP moves to ASP-INACTIVE causing that n ASPs are in either ASP-ACTIVE or ASP-INACTIVE states.

IA2DN: One ASP moves to ASP-DOWN causing that the number of ASPs in either ASP-ACTIVE or ASP-INACTIVE drops below n.

IA2AC: one ASP moves to ASP-ACTIVE, causing number of ASPs in the ASP-ACTIVE state to be n.

AC2PN: the last ASP in ASP-ACTIVE state moves to ASP-INACTIVE or ASP-DOWN states, causing the number of ASPs in ASP-ACTIVE drop below 1.

PN2AC: One ASP moves to ASP-ACTIVE.

PN2IA: T(r) Expiry, n or more ASPs are in ASP-INACTIVE.

PN2DN: T(r) Expiry, the number of ASPs in ASP-INACTIVE state is less than n.

As "n" ASPs are needed to handle the maximum engineered load of the AS, an AS becomes AS-ACTIVE right after n ASPs reach the ASP-ACTIVE state during the start-up phase. Once the traffic is flowing, an AS keeps the AS-ACTIVE state till the last ASP turns to another state different to ASP-ACTIVE, avoiding unnecessary traffic disturbances as long as there are ASPs available, in the assumption that the AS will not always be exposed to the maximum load. 

There are other cases where the AS/ASP configuration data is created dynamically. In those cases there would be differences in the state machine, especially at creation of the AS. For example, where the AS/ASP configuration data is not created until Registration of the first ASP, the AS-INACTIVE state is entered directly upon the nth successful REG REQ from an ASP belonging to that AS.  Another example is where the AS/ASP configuration data is not created until the nth ASP successfully enters the ASP-ACTIVE state.  In this latter case the AS-ACTIVE state is entered directly.

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



From exim@www1.ietf.org  Tue Jun 17 15:46:20 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07616
	for <sigtran-archive@odin.ietf.org>; Tue, 17 Jun 2003 15:46:20 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5HJjq722588
	for sigtran-archive@odin.ietf.org; Tue, 17 Jun 2003 15:45:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SM3r-00038U-JC; Tue, 17 Jun 2003 15:24:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SLo4-0007kF-2N
	for sigtran@optimus.ietf.org; Tue, 17 Jun 2003 15:07:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03995
	for <sigtran@ietf.org>; Tue, 17 Jun 2003 15:07:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SLln-0003Vk-00
	for sigtran@ietf.org; Tue, 17 Jun 2003 15:05:27 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[M2RsICnHeSwx+kNUQOdXLushZJHCvFkd])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SLlm-0003VZ-00
	for sigtran@ietf.org; Tue, 17 Jun 2003 15:05:27 -0400
Received: from ns.pigworks.openss7.net (IDENT:YqbW+xv0WjSEJnyEjWbxoaHNcmTKByPA@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5HJ7WX08865;
	Tue, 17 Jun 2003 13:07:32 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5HJ7WH11842;
	Tue, 17 Jun 2003 13:07:32 -0600
Date: Tue, 17 Jun 2003 13:07:32 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>,
        "Ken Morneault (E-mail)" <kmorneau@cisco.com>,
        =?iso-8859-1?Q?Antonio_Ca=F1ete_=28ECE=29?= <antonio.canete-martinez@ece.ericsson.se>
Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
Message-ID: <20030617130732.A11785@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>,
	"Ken Morneault (E-mail)" <kmorneau@cisco.com>,
	=?iso-8859-1?Q?Antonio_Ca=F1ete_=28ECE=29?= <antonio.canete-martinez@ece.ericsson.se>
References: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C61@eestqnt105.es.eu.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C61@eestqnt105.es.eu.ericsson.se>; from javier.pastor-balbas@ece.ericsson.se on Tue, Jun 17, 2003 at 04:51:16PM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Javier,

I believe the concensus from the last long discussions was to
remove section 3.15.

--brian

Javier Pastor-Balbas (ECE) wrote:                                                   (Tue, 17 Jun 2003 16:51:16)
> This is the last version. There were still some unfinished sentences and inconsistences in the first text I sent. Now, they are fixed.
> 
> Cheers // Javier.
> 
> 
> --------- 
> Old text: (Section 4.3.2) 
> ---------
> 
> AS-DOWN: The Application Server is unavailable.  This state implies 
> that all related ASPs are in the ASP-DOWN state for this AS. Initially the AS will be in this state. An Application Server is in the AS-DOWN state when it is removed from a configuration.
> 
> AS-INACTIVE: The Application Server is available but no application 
> traffic is active (i.e., one or more related ASPs are in the ASP-
> INACTIVE state, but none in the ASP-ACTIVE state).  The recovery 
> timer T(r) is not running or has expired. 
> 
> AS-ACTIVE: The Application Server is available and application traffic is active.  This state implies that at least one ASP is in the ASP-ACTIVE state.
> 
> AS-PENDING: An active ASP has transitioned to ASP-INACTIVE or ASP-DOWN  and it was the last remaining active ASP in the AS.  A recovery timer T(r) SHOULD be started and all incoming signalling messages SHOULD be queued by the SGP. If an ASP becomes ASP-ACTIVE before T(r) expires, the AS is moved to the AS-ACTIVE state and all the queued messages will be sent to the ASP. 
> 
> If T(r) expires before an ASP becomes ASP-ACTIVE, and the SGP has no 
> alternative, the SGP may stops queuing messages and discards all 
> previously queued messages. The AS will move to the AS-INACTIVE state 
> if at least one ASP is in ASP-INACTIVE state, otherwise it will move 
> to AS-DOWN state. 
> 
> Figure 5 shows an example AS state machine for the case where the 
> AS/ASP data is preconfigured.  For other cases where the AS/ASP 
> configuration data is created dynamically, there would be differences 
> in the state machine, especially at creation of the AS.  
> 
>                  Figure 5: AS State Transition Diagram
> 
>      +----------+   one ASP trans to ACTIVE   +-------------+
>      |    AS-   |---------------------------->|     AS-     |      
>      | INACTIVE |                             |   ACTIVE    |
>      |          |<---                         |             |
>      +----------+    \                        +-------------+
>         ^   |         \ Tr Expiry,                ^    |
>         |   |          \ at least one             |    |
>         |   |           \ ASP in ASP-INACTIVE     |    |
>         |   |            \                        |    |
>         |   |             \                       |    |
>         |   |              \                      |    |
> one ASP |   | all ASP       \            one ASP  |    | Last ACTIVE
> trans   |   | trans to       \           trans to |    | ASP trans to
> to      |   | ASP-DOWN        -------\   ASP-     |    | ASP-INACTIVE
> ASP-    |   |                         \  ACTIVE   |    | or ASP-DOWN
> INACTIVE|   |                          \          |    |  (start Tr)
>         |   |                           \         |    |
>         |   |                            \        |    |
>         |   v                             \       |    v         
>      +----------+                          \  +-------------+
>      |          |                           --|             |      
>      | AS-DOWN  |                             | AS-PENDING  |
>      |          |                             |  (queueing) |
>      |          |<----------------------------|             |
>      +----------+    Tr Expiry and no ASP     +-------------+
>                      in ASP-INACTIVE state)   
> 
>  Tr = Recovery Timer
> 
> 
> 
> For example, where the AS/ASP configuration data is not created until 
> Registration of the first ASP, the AS-INACTIVE state is entered 
> directly upon the first successful REG REQ from an ASP.  Another 
> example is where the AS/ASP configuration data is not created until the first ASP successfully enters the ASP-ACTIVE state.  In this case the AS-ACTIVE state is entered directly.
> 
> 
> --------- 
> New text: (Section 4.3.2) 
> ---------
> 
> AS-DOWN: The Application Server is unavailable.  This state implies that the number of ASPs being in ASP-INACTIVE or ASP-ACTIVE is less than "n". Initially the AS will be in this state. An Application Server is in the AS-DOWN state when it is removed from a configuration.
> 
> AS-INACTIVE: The Application Server is available but no application traffic is active. This implies that there are at least n ASPs in either ASP-INACTIVE or ASP-ACTIVE but the total number of ASPs in ASP-ACTIVE state has not reach n.  The recovery timer T(r) is not running or has expired. 
> 
> AS-ACTIVE: The Application Server is available and application traffic is active. The AS moves to this state after being in AS-INACTIVE and getting n ASPs in ASP-ACTIVE state or, after reaching AS-ACTIVE and keeping one or more ASPs in ASP-ACTIVE state. 
> 
> AS-PENDING: The last active ASP has transitioned from ASP-ACTIVE to ASP-INACTIVE or ASP-DOWN.  A recovery timer T(r) SHOULD be started and all incoming signalling messages SHOULD be queued by the SGP. If an ASP becomes ASP-ACTIVE before T(r) expires, the AS is moved to the AS-ACTIVE state and all the queued messages will be sent to the ASP. 
> 
> If T(r) expires before an ASP becomes ASP-ACTIVE, the SGP MAY stops queuing messages and discards all 
> previously queued messages. The AS will move to the AS-INACTIVE state 
> if at least the number of ASPs in ASP-INACTIVE sum n, otherwise it will move to AS-DOWN state. 
> 
> Figure 5 shows an example AS state machine for the case where the 
> AS/ASP data is preconfigured and an n+k redundancy model. 
> 
> 
>              Figure 5: AS State Transition Diagram
> 
>                    
>      +----------+          IA2AC              +-------------+
>      |    AS-   |---------------------------->|     AS-     |
>      | INACTIVE |                             |   ACTIVE    |
>      |          |<-----------                 |             |
>      +----------+            \                +-------------+
>         ^   |                 \                    ^   |
>         |   | IA2DN            \ PN2IA             |   | AC2PN
>         |   |                   \                  |   | 
>   DN2IA |   |                    \          PN2AC  |   | 
>         |   v                     \                |   v
>      +----------+                  \          +-------------+
>      |          |                   ----------|             |
>      | AS-DOWN  |                             | AS-PENDING  |
>      |          |                  PN2DN      |  (queueing) |
>      |          |<----------------------------|             |
>      +----------+                             +-------------+
> 
> 
> 
> DN2IA: One ASP moves to ASP-INACTIVE causing that n ASPs are in either ASP-ACTIVE or ASP-INACTIVE states.
> 
> IA2DN: One ASP moves to ASP-DOWN causing that the number of ASPs in either ASP-ACTIVE or ASP-INACTIVE drops below n.
> 
> IA2AC: one ASP moves to ASP-ACTIVE, causing number of ASPs in the ASP-ACTIVE state to be n.
> 
> AC2PN: the last ASP in ASP-ACTIVE state moves to ASP-INACTIVE or ASP-DOWN states, causing the number of ASPs in ASP-ACTIVE drop below 1.
> 
> PN2AC: One ASP moves to ASP-ACTIVE.
> 
> PN2IA: T(r) Expiry, n or more ASPs are in ASP-INACTIVE.
> 
> PN2DN: T(r) Expiry, the number of ASPs in ASP-INACTIVE state is less than n.
> 
> As "n" ASPs are needed to handle the maximum engineered load of the AS, an AS becomes AS-ACTIVE right after n ASPs reach the ASP-ACTIVE state during the start-up phase. Once the traffic is flowing, an AS keeps the AS-ACTIVE state till the last ASP turns to another state different to ASP-ACTIVE, avoiding unnecessary traffic disturbances as long as there are ASPs available, in the assumption that the AS will not always be exposed to the maximum load. 
> 
> There are other cases where the AS/ASP configuration data is created dynamically. In those cases there would be differences in the state machine, especially at creation of the AS. For example, where the AS/ASP configuration data is not created until Registration of the first ASP, the AS-INACTIVE state is entered directly upon the nth successful REG REQ from an ASP belonging to that AS.  Another example is where the AS/ASP configuration data is not created until the nth ASP successfully enters the ASP-ACTIVE state.  In this latter case the AS-ACTIVE state is entered directly.
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Tue Jun 17 15:51:42 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07839
	for <sigtran-archive@odin.ietf.org>; Tue, 17 Jun 2003 15:51:42 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5HJpEe24521
	for sigtran-archive@odin.ietf.org; Tue, 17 Jun 2003 15:51:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SMQ1-00063d-Le; Tue, 17 Jun 2003 15:47:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SM6w-0003MD-JB
	for sigtran@optimus.ietf.org; Tue, 17 Jun 2003 15:27:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06262
	for <sigtran@ietf.org>; Tue, 17 Jun 2003 15:27:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SM4i-0003tx-00
	for sigtran@ietf.org; Tue, 17 Jun 2003 15:25:00 -0400
Received: from web12810.mail.yahoo.com ([216.136.174.137])
	by ietf-mx with smtp (Exim 4.12)
	id 19SM4h-0003tu-00
	for sigtran@ietf.org; Tue, 17 Jun 2003 15:24:59 -0400
Message-ID: <20030617192715.51994.qmail@web12810.mail.yahoo.com>
Received: from [208.255.120.2] by web12810.mail.yahoo.com via HTTP; Tue, 17 Jun 2003 12:27:15 PDT
Date: Tue, 17 Jun 2003 12:27:15 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
To: sigtran@ietf.org
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C61@eestqnt105.es.eu.ericsson.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Hi Javier,

IMO the changes in general are nice, I have one
question/comment though:
For PN2AC transition, unless ASPs have knowledge of
T(r), they can't decide whether the first ACTIVE ASP
will make AS to switch to ACTIVE or not -because they
can't know whether AS has already switched to INACTIVE
after T(r) expiry or not- (AS state machine is
described from SG point of view but I believe we
should make it possible that ASPs and SGPs can have
the same AS state view) -in fact I am not sure,
whether to favor PN2AC transition by allowing it to
happen with only one ACTIVE ASP is the best solution
or not-.
Furthermore, if the proposed PN2AC is going to be kept
I would think PN2IA should be somethink like "T(r)
expiry, no ACTIVE ASPs"

    Tolga
--- "Javier Pastor-Balbas (ECE)"
<javier.pastor-balbas@ece.ericsson.se> wrote:
> This is the last version. There were still some
> unfinished sentences and inconsistences in the first
> text I sent. Now, they are fixed.
> 
> Cheers // Javier.
> 
> 
> --------- 
> Old text: (Section 4.3.2) 
> ---------
> 
> AS-DOWN: The Application Server is unavailable. 
> This state implies 
> that all related ASPs are in the ASP-DOWN state for
> this AS. Initially the AS will be in this state. An
> Application Server is in the AS-DOWN state when it
> is removed from a configuration.
> 
> AS-INACTIVE: The Application Server is available but
> no application 
> traffic is active (i.e., one or more related ASPs
> are in the ASP-
> INACTIVE state, but none in the ASP-ACTIVE state). 
> The recovery 
> timer T(r) is not running or has expired. 
> 
> AS-ACTIVE: The Application Server is available and
> application traffic is active.  This state implies
> that at least one ASP is in the ASP-ACTIVE state.
> 
> AS-PENDING: An active ASP has transitioned to
> ASP-INACTIVE or ASP-DOWN  and it was the last
> remaining active ASP in the AS.  A recovery timer
> T(r) SHOULD be started and all incoming signalling
> messages SHOULD be queued by the SGP. If an ASP
> becomes ASP-ACTIVE before T(r) expires, the AS is
> moved to the AS-ACTIVE state and all the queued
> messages will be sent to the ASP. 
> 
> If T(r) expires before an ASP becomes ASP-ACTIVE,
> and the SGP has no 
> alternative, the SGP may stops queuing messages and
> discards all 
> previously queued messages. The AS will move to the
> AS-INACTIVE state 
> if at least one ASP is in ASP-INACTIVE state,
> otherwise it will move 
> to AS-DOWN state. 
> 
> Figure 5 shows an example AS state machine for the
> case where the 
> AS/ASP data is preconfigured.  For other cases where
> the AS/ASP 
> configuration data is created dynamically, there
> would be differences 
> in the state machine, especially at creation of the
> AS.  
> 
>                  Figure 5: AS State Transition
> Diagram
> 
>      +----------+   one ASP trans to ACTIVE  
> +-------------+
>      |    AS-   |---------------------------->|    
> AS-     |      
>      | INACTIVE |                             |  
> ACTIVE    |
>      |          |<---                         |     
>        |
>      +----------+    \                       
> +-------------+
>         ^   |         \ Tr Expiry,                ^ 
>   |
>         |   |          \ at least one             | 
>   |
>         |   |           \ ASP in ASP-INACTIVE     | 
>   |
>         |   |            \                        | 
>   |
>         |   |             \                       | 
>   |
>         |   |              \                      | 
>   |
> one ASP |   | all ASP       \            one ASP  | 
>   | Last ACTIVE
> trans   |   | trans to       \           trans to | 
>   | ASP trans to
> to      |   | ASP-DOWN        -------\   ASP-     | 
>   | ASP-INACTIVE
> ASP-    |   |                         \  ACTIVE   | 
>   | or ASP-DOWN
> INACTIVE|   |                          \          | 
>   |  (start Tr)
>         |   |                           \         | 
>   |
>         |   |                            \        | 
>   |
>         |   v                             \       | 
>   v         
>      +----------+                          \ 
> +-------------+
>      |          |                           --|     
>        |      
>      | AS-DOWN  |                             |
> AS-PENDING  |
>      |          |                             | 
> (queueing) |
>      |          |<----------------------------|     
>        |
>      +----------+    Tr Expiry and no ASP    
> +-------------+
>                      in ASP-INACTIVE state)   
> 
>  Tr = Recovery Timer
> 
> 
> 
> For example, where the AS/ASP configuration data is
> not created until 
> Registration of the first ASP, the AS-INACTIVE state
> is entered 
> directly upon the first successful REG REQ from an
> ASP.  Another 
> example is where the AS/ASP configuration data is
> not created until the first ASP successfully enters
> the ASP-ACTIVE state.  In this case the AS-ACTIVE
> state is entered directly.
> 
> 
> --------- 
> New text: (Section 4.3.2) 
> ---------
> 
> AS-DOWN: The Application Server is unavailable. 
> This state implies that the number of ASPs being in
> ASP-INACTIVE or ASP-ACTIVE is less than "n".
> Initially the AS will be in this state. An
> Application Server is in the AS-DOWN state when it
> is removed from a configuration.
> 
> AS-INACTIVE: The Application Server is available but
> no application traffic is active. This implies that
> there are at least n ASPs in either ASP-INACTIVE or
> ASP-ACTIVE but the total number of ASPs in
> ASP-ACTIVE state has not reach n.  The recovery
> timer T(r) is not running or has expired. 
> 
> AS-ACTIVE: The Application Server is available and
> application traffic is active. The AS moves to this
> state after being in AS-INACTIVE and getting n ASPs
> in ASP-ACTIVE state or, after reaching AS-ACTIVE and
> keeping one or more ASPs in ASP-ACTIVE state. 
> 
> AS-PENDING: The last active ASP has transitioned
> from ASP-ACTIVE to ASP-INACTIVE or ASP-DOWN.  A
> recovery timer T(r) SHOULD be started and all
> incoming signalling messages SHOULD be queued by the
> SGP. If an ASP becomes ASP-ACTIVE before T(r)
> expires, the AS is moved to the AS-ACTIVE state and
> all the queued messages will be sent to the ASP. 
> 
> If T(r) expires before an ASP becomes ASP-ACTIVE,
> the SGP MAY stops queuing messages and discards all 
> previously queued messages. The AS will move to the
> AS-INACTIVE state 
> if at least the number of ASPs in ASP-INACTIVE sum
> n, otherwise it will move to AS-DOWN state. 
> 
> Figure 5 shows an example AS state machine for the
> case where the 
> AS/ASP data is preconfigured and an n+k redundancy
> model. 
> 
> 
>              Figure 5: AS State Transition Diagram
> 
>                    
>      +----------+          IA2AC             
> +-------------+
>      |    AS-   |---------------------------->|    
> AS-     |
>      | INACTIVE |                             |  
> ACTIVE    |
>      |          |<-----------                 |     
>        |
>      +----------+            \               
> +-------------+
>         ^   |                 \                    ^
>   |
>         |   | IA2DN            \ PN2IA             |
>   | AC2PN
>         |   |                   \                  |
>   | 
>   DN2IA |   |                    \          PN2AC  |
>   | 
>         |   v                     \                |
>   v
>      +----------+                  \         
> +-------------+
>      |          |                   ----------|     
>        |
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

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



From exim@www1.ietf.org  Wed Jun 18 00:46:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23026
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 00:46:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5I4k2p21307
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 00:46:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SUpd-0005XQ-0c; Wed, 18 Jun 2003 00:46:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SUp7-0005Vi-0H
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 00:45:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23015
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 00:45:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SUmr-0007bf-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 00:43:09 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SUmq-0007bb-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 00:43:08 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h5I4i0BZ028172;
	Tue, 17 Jun 2003 23:44:41 -0500 (CDT)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h5I4hp1C005941;
	Tue, 17 Jun 2003 23:43:51 -0500 (CDT)
Date: Tue, 17 Jun 2003 23:43:50 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>,
        "'sigtran@ietf.org'" <sigtran@ietf.org>,
        "Ken Morneault (E-mail)" <kmorneau@cisco.com>,
        =?iso-8859-1?Q?Antonio_Ca=F1ete_=28ECE=29?= <antonio.canete-martinez@ece.ericsson.se>
Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
In-Reply-To: <20030617130732.A11785@openss7.org>
Message-ID: <Pine.SOL.4.10.10306172340590.6574-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


Pastor,

 I too believe that concensus was made to delete section 3.15 from IG 
 as RFC is sufficient to explain n+k case.

--Samuel

  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******

On Tue, 17 Jun 2003, Brian F. G. Bidulock wrote:

> Javier,
> 
> I believe the concensus from the last long discussions was to
> remove section 3.15.
> 
> --brian
> 
> Javier Pastor-Balbas (ECE) wrote:                                                   (Tue, 17 Jun 2003 16:51:16)
> > This is the last version. There were still some unfinished sentences and inconsistences in the first text I sent. Now, they are fixed.
> > 
> > Cheers // Javier.
> > 
> > 
> > --------- 
> > Old text: (Section 4.3.2) 
> > ---------
> > 
> > AS-DOWN: The Application Server is unavailable.  This state implies 
> > that all related ASPs are in the ASP-DOWN state for this AS. Initially the AS will be in this state. An Application Server is in the AS-DOWN state when it is removed from a configuration.
> > 
> > AS-INACTIVE: The Application Server is available but no application 
> > traffic is active (i.e., one or more related ASPs are in the ASP-
> > INACTIVE state, but none in the ASP-ACTIVE state).  The recovery 
> > timer T(r) is not running or has expired. 
> > 
> > AS-ACTIVE: The Application Server is available and application traffic is active.  This state implies that at least one ASP is in the ASP-ACTIVE state.
> > 
> > AS-PENDING: An active ASP has transitioned to ASP-INACTIVE or ASP-DOWN  and it was the last remaining active ASP in the AS.  A recovery timer T(r) SHOULD be started and all incoming signalling messages SHOULD be queued by the SGP. If an ASP becomes ASP-ACTIVE before T(r) expires, the AS is moved to the AS-ACTIVE state and all the queued messages will be sent to the ASP. 
> > 
> > If T(r) expires before an ASP becomes ASP-ACTIVE, and the SGP has no 
> > alternative, the SGP may stops queuing messages and discards all 
> > previously queued messages. The AS will move to the AS-INACTIVE state 
> > if at least one ASP is in ASP-INACTIVE state, otherwise it will move 
> > to AS-DOWN state. 
> > 
> > Figure 5 shows an example AS state machine for the case where the 
> > AS/ASP data is preconfigured.  For other cases where the AS/ASP 
> > configuration data is created dynamically, there would be differences 
> > in the state machine, especially at creation of the AS.  
> > 
> >                  Figure 5: AS State Transition Diagram
> > 
> >      +----------+   one ASP trans to ACTIVE   +-------------+
> >      |    AS-   |---------------------------->|     AS-     |      
> >      | INACTIVE |                             |   ACTIVE    |
> >      |          |<---                         |             |
> >      +----------+    \                        +-------------+
> >         ^   |         \ Tr Expiry,                ^    |
> >         |   |          \ at least one             |    |
> >         |   |           \ ASP in ASP-INACTIVE     |    |
> >         |   |            \                        |    |
> >         |   |             \                       |    |
> >         |   |              \                      |    |
> > one ASP |   | all ASP       \            one ASP  |    | Last ACTIVE
> > trans   |   | trans to       \           trans to |    | ASP trans to
> > to      |   | ASP-DOWN        -------\   ASP-     |    | ASP-INACTIVE
> > ASP-    |   |                         \  ACTIVE   |    | or ASP-DOWN
> > INACTIVE|   |                          \          |    |  (start Tr)
> >         |   |                           \         |    |
> >         |   |                            \        |    |
> >         |   v                             \       |    v         
> >      +----------+                          \  +-------------+
> >      |          |                           --|             |      
> >      | AS-DOWN  |                             | AS-PENDING  |
> >      |          |                             |  (queueing) |
> >      |          |<----------------------------|             |
> >      +----------+    Tr Expiry and no ASP     +-------------+
> >                      in ASP-INACTIVE state)   
> > 
> >  Tr = Recovery Timer
> > 
> > 
> > 
> > For example, where the AS/ASP configuration data is not created until 
> > Registration of the first ASP, the AS-INACTIVE state is entered 
> > directly upon the first successful REG REQ from an ASP.  Another 
> > example is where the AS/ASP configuration data is not created until the first ASP successfully enters the ASP-ACTIVE state.  In this case the AS-ACTIVE state is entered directly.
> > 
> > 
> > --------- 
> > New text: (Section 4.3.2) 
> > ---------
> > 
> > AS-DOWN: The Application Server is unavailable.  This state implies that the number of ASPs being in ASP-INACTIVE or ASP-ACTIVE is less than "n". Initially the AS will be in this state. An Application Server is in the AS-DOWN state when it is removed from a configuration.
> > 
> > AS-INACTIVE: The Application Server is available but no application traffic is active. This implies that there are at least n ASPs in either ASP-INACTIVE or ASP-ACTIVE but the total number of ASPs in ASP-ACTIVE state has not reach n.  The recovery timer T(r) is not running or has expired. 
> > 
> > AS-ACTIVE: The Application Server is available and application traffic is active. The AS moves to this state after being in AS-INACTIVE and getting n ASPs in ASP-ACTIVE state or, after reaching AS-ACTIVE and keeping one or more ASPs in ASP-ACTIVE state. 
> > 
> > AS-PENDING: The last active ASP has transitioned from ASP-ACTIVE to ASP-INACTIVE or ASP-DOWN.  A recovery timer T(r) SHOULD be started and all incoming signalling messages SHOULD be queued by the SGP. If an ASP becomes ASP-ACTIVE before T(r) expires, the AS is moved to the AS-ACTIVE state and all the queued messages will be sent to the ASP. 
> > 
> > If T(r) expires before an ASP becomes ASP-ACTIVE, the SGP MAY stops queuing messages and discards all 
> > previously queued messages. The AS will move to the AS-INACTIVE state 
> > if at least the number of ASPs in ASP-INACTIVE sum n, otherwise it will move to AS-DOWN state. 
> > 
> > Figure 5 shows an example AS state machine for the case where the 
> > AS/ASP data is preconfigured and an n+k redundancy model. 
> > 
> > 
> >              Figure 5: AS State Transition Diagram
> > 
> >                    
> >      +----------+          IA2AC              +-------------+
> >      |    AS-   |---------------------------->|     AS-     |
> >      | INACTIVE |                             |   ACTIVE    |
> >      |          |<-----------                 |             |
> >      +----------+            \                +-------------+
> >         ^   |                 \                    ^   |
> >         |   | IA2DN            \ PN2IA             |   | AC2PN
> >         |   |                   \                  |   | 
> >   DN2IA |   |                    \          PN2AC  |   | 
> >         |   v                     \                |   v
> >      +----------+                  \          +-------------+
> >      |          |                   ----------|             |
> >      | AS-DOWN  |                             | AS-PENDING  |
> >      |          |                  PN2DN      |  (queueing) |
> >      |          |<----------------------------|             |
> >      +----------+                             +-------------+
> > 
> > 
> > 
> > DN2IA: One ASP moves to ASP-INACTIVE causing that n ASPs are in either ASP-ACTIVE or ASP-INACTIVE states.
> > 
> > IA2DN: One ASP moves to ASP-DOWN causing that the number of ASPs in either ASP-ACTIVE or ASP-INACTIVE drops below n.
> > 
> > IA2AC: one ASP moves to ASP-ACTIVE, causing number of ASPs in the ASP-ACTIVE state to be n.
> > 
> > AC2PN: the last ASP in ASP-ACTIVE state moves to ASP-INACTIVE or ASP-DOWN states, causing the number of ASPs in ASP-ACTIVE drop below 1.
> > 
> > PN2AC: One ASP moves to ASP-ACTIVE.
> > 
> > PN2IA: T(r) Expiry, n or more ASPs are in ASP-INACTIVE.
> > 
> > PN2DN: T(r) Expiry, the number of ASPs in ASP-INACTIVE state is less than n.
> > 
> > As "n" ASPs are needed to handle the maximum engineered load of the AS, an AS becomes AS-ACTIVE right after n ASPs reach the ASP-ACTIVE state during the start-up phase. Once the traffic is flowing, an AS keeps the AS-ACTIVE state till the last ASP turns to another state different to ASP-ACTIVE, avoiding unnecessary traffic disturbances as long as there are ASPs available, in the assumption that the AS will not always be exposed to the maximum load. 
> > 
> > There are other cases where the AS/ASP configuration data is created dynamically. In those cases there would be differences in the state machine, especially at creation of the AS. For example, where the AS/ASP configuration data is not created until Registration of the first ASP, the AS-INACTIVE state is entered directly upon the nth successful REG REQ from an ASP belonging to that AS.  Another example is where the AS/ASP configuration data is not created until the nth ASP successfully enters the ASP-ACTIVE state.  In this latter case the AS-ACTIVE state is entered directly.
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 


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



From exim@www1.ietf.org  Wed Jun 18 00:51:28 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23246
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 00:51:28 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5I4p1j21864
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 00:51:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SUuT-0005gP-C1; Wed, 18 Jun 2003 00:51:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SUtr-0005g7-A3
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 00:50:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23207
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 00:50:19 -0400 (EDT)
From: kakaul@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SUrb-0007du-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 00:48:03 -0400
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SUrZ-0007dd-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 00:48:02 -0400
Received: from hindon.hss.co.in (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h5I4l2323276
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 10:17:02 +0530 (IST)
Received: from ultra.hss.co.in (ultra [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h5I4l0923266;
	Wed, 18 Jun 2003 10:17:01 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h5I4oWi02364;
	Wed, 18 Jun 2003 10:20:32 +0530 (IST)
Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
Cc: sigtran@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF3BF6336A.7A515B00-ON65256D49.0016BFB3@hss.hns.com>
Date: Wed, 18 Jun 2003 10:15:23 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 18/06/2003
 10:14:27 AM
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id AAA23246





Hi Javier
  If AS has transitioned to AS-PENDING as a result of ASP inactive being
received
  from last ASP.Now  during T(r) if one of the ASP becomes active.According
to the changed
  text AS transitions  to AS - ACTIVE even though total number of active
ASP's is 1 and n is greater than 1.
  So if configuration of active ASP's remain same there after AS will have
insufficient active
  ASP's to handle the engineered application server traffic. IMO it is not
a fear assumtion to follow
  1 + k redundancy after AS state transitions from AS - ACTIVE state to any
other state.

Regards
Kamesh
Hughes Software Systems




"Javier Pastor-Balbas (ECE)"
<javier.pastor-balbas@ece.ericsson.se>@ietf.org on 06/17/2003 08:21:16 PM

Sent by:    sigtran-admin@ietf.org


To:    "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>,
       "'sigtran@ietf.org'" <sigtran@ietf.org>
cc:    "Ken Morneault (E-mail)" <kmorneau@cisco.com>, Antonio Cañete (ECE)
       <antonio.canete-martinez@ece.ericsson.se>

Subject:    [Sigtran] RE: M3UA IG: section 3.15 reworked


This is the last version. There were still some unfinished sentences and
inconsistences in the first text I sent. Now, they are fixed.

Cheers // Javier.


---------
Old text: (Section 4.3.2)
---------

AS-DOWN: The Application Server is unavailable.  This state implies
that all related ASPs are in the ASP-DOWN state for this AS. Initially the
AS will be in this state. An Application Server is in the AS-DOWN state
when it is removed from a configuration.

AS-INACTIVE: The Application Server is available but no application
traffic is active (i.e., one or more related ASPs are in the ASP-
INACTIVE state, but none in the ASP-ACTIVE state).  The recovery
timer T(r) is not running or has expired.

AS-ACTIVE: The Application Server is available and application traffic is
active.  This state implies that at least one ASP is in the ASP-ACTIVE
state.

AS-PENDING: An active ASP has transitioned to ASP-INACTIVE or ASP-DOWN  and
it was the last remaining active ASP in the AS.  A recovery timer T(r)
SHOULD be started and all incoming signalling messages SHOULD be queued by
the SGP. If an ASP becomes ASP-ACTIVE before T(r) expires, the AS is moved
to the AS-ACTIVE state and all the queued messages will be sent to the ASP.

If T(r) expires before an ASP becomes ASP-ACTIVE, and the SGP has no
alternative, the SGP may stops queuing messages and discards all
previously queued messages. The AS will move to the AS-INACTIVE state
if at least one ASP is in ASP-INACTIVE state, otherwise it will move
to AS-DOWN state.

Figure 5 shows an example AS state machine for the case where the
AS/ASP data is preconfigured.  For other cases where the AS/ASP
configuration data is created dynamically, there would be differences
in the state machine, especially at creation of the AS.

                 Figure 5: AS State Transition Diagram

     +----------+   one ASP trans to ACTIVE   +-------------+
     |    AS-   |---------------------------->|     AS-     |
     | INACTIVE |                             |   ACTIVE    |
     |          |<---                         |             |
     +----------+    \                        +-------------+
        ^   |         \ Tr Expiry,                ^    |
        |   |          \ at least one             |    |
        |   |           \ ASP in ASP-INACTIVE     |    |
        |   |            \                        |    |
        |   |             \                       |    |
        |   |              \                      |    |
one ASP |   | all ASP       \            one ASP  |    | Last ACTIVE
trans   |   | trans to       \           trans to |    | ASP trans to
to      |   | ASP-DOWN        -------\   ASP-     |    | ASP-INACTIVE
ASP-    |   |                         \  ACTIVE   |    | or ASP-DOWN
INACTIVE|   |                          \          |    |  (start Tr)
        |   |                           \         |    |
        |   |                            \        |    |
        |   v                             \       |    v
     +----------+                          \  +-------------+
     |          |                           --|             |
     | AS-DOWN  |                             | AS-PENDING  |
     |          |                             |  (queueing) |
     |          |<----------------------------|             |
     +----------+    Tr Expiry and no ASP     +-------------+
                     in ASP-INACTIVE state)

 Tr = Recovery Timer



For example, where the AS/ASP configuration data is not created until
Registration of the first ASP, the AS-INACTIVE state is entered
directly upon the first successful REG REQ from an ASP.  Another
example is where the AS/ASP configuration data is not created until the
first ASP successfully enters the ASP-ACTIVE state.  In this case the
AS-ACTIVE state is entered directly.


---------
New text: (Section 4.3.2)
---------

AS-DOWN: The Application Server is unavailable.  This state implies that
the number of ASPs being in ASP-INACTIVE or ASP-ACTIVE is less than "n".
Initially the AS will be in this state. An Application Server is in the
AS-DOWN state when it is removed from a configuration.

AS-INACTIVE: The Application Server is available but no application traffic
is active. This implies that there are at least n ASPs in either
ASP-INACTIVE or ASP-ACTIVE but the total number of ASPs in ASP-ACTIVE state
has not reach n.  The recovery timer T(r) is not running or has expired.

AS-ACTIVE: The Application Server is available and application traffic is
active. The AS moves to this state after being in AS-INACTIVE and getting n
ASPs in ASP-ACTIVE state or, after reaching AS-ACTIVE and keeping one or
more ASPs in ASP-ACTIVE state.

AS-PENDING: The last active ASP has transitioned from ASP-ACTIVE to
ASP-INACTIVE or ASP-DOWN.  A recovery timer T(r) SHOULD be started and all
incoming signalling messages SHOULD be queued by the SGP. If an ASP becomes
ASP-ACTIVE before T(r) expires, the AS is moved to the AS-ACTIVE state and
all the queued messages will be sent to the ASP.

If T(r) expires before an ASP becomes ASP-ACTIVE, the SGP MAY stops queuing
messages and discards all
previously queued messages. The AS will move to the AS-INACTIVE state
if at least the number of ASPs in ASP-INACTIVE sum n, otherwise it will
move to AS-DOWN state.

Figure 5 shows an example AS state machine for the case where the
AS/ASP data is preconfigured and an n+k redundancy model.


             Figure 5: AS State Transition Diagram


     +----------+          IA2AC              +-------------+
     |    AS-   |---------------------------->|     AS-     |
     | INACTIVE |                             |   ACTIVE    |
     |          |<-----------                 |             |
     +----------+            \                +-------------+
        ^   |                 \                    ^   |
        |   | IA2DN            \ PN2IA             |   | AC2PN
        |   |                   \                  |   |
  DN2IA |   |                    \          PN2AC  |   |
        |   v                     \                |   v
     +----------+                  \          +-------------+
     |          |                   ----------|             |
     | AS-DOWN  |                             | AS-PENDING  |
     |          |                  PN2DN      |  (queueing) |
     |          |<----------------------------|             |
     +----------+                             +-------------+



DN2IA: One ASP moves to ASP-INACTIVE causing that n ASPs are in either
ASP-ACTIVE or ASP-INACTIVE states.

IA2DN: One ASP moves to ASP-DOWN causing that the number of ASPs in either
ASP-ACTIVE or ASP-INACTIVE drops below n.

IA2AC: one ASP moves to ASP-ACTIVE, causing number of ASPs in the
ASP-ACTIVE state to be n.

AC2PN: the last ASP in ASP-ACTIVE state moves to ASP-INACTIVE or ASP-DOWN
states, causing the number of ASPs in ASP-ACTIVE drop below 1.

PN2AC: One ASP moves to ASP-ACTIVE.

PN2IA: T(r) Expiry, n or more ASPs are in ASP-INACTIVE.

PN2DN: T(r) Expiry, the number of ASPs in ASP-INACTIVE state is less than
n.

As "n" ASPs are needed to handle the maximum engineered load of the AS, an
AS becomes AS-ACTIVE right after n ASPs reach the ASP-ACTIVE state during
the start-up phase. Once the traffic is flowing, an AS keeps the AS-ACTIVE
state till the last ASP turns to another state different to ASP-ACTIVE,
avoiding unnecessary traffic disturbances as long as there are ASPs
available, in the assumption that the AS will not always be exposed to the
maximum load.

There are other cases where the AS/ASP configuration data is created
dynamically. In those cases there would be differences in the state
machine, especially at creation of the AS. For example, where the AS/ASP
configuration data is not created until Registration of the first ASP, the
AS-INACTIVE state is entered directly upon the nth successful REG REQ from
an ASP belonging to that AS.  Another example is where the AS/ASP
configuration data is not created until the nth ASP successfully enters the
ASP-ACTIVE state.  In this latter case the AS-ACTIVE state is entered
directly.

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



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



From exim@www1.ietf.org  Wed Jun 18 05:48:30 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25374
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 05:48:30 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5I9m3p01520
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 05:48:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SZXt-0000O7-1w; Wed, 18 Jun 2003 05:48:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SZXI-0000Mp-5X
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 05:47:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25356
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 05:47:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SZV1-0001jh-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 05:45:03 -0400
Received: from falcon.ericsson.se ([193.180.251.52] helo=falcon.al.sw.ericsson.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SZV0-0001je-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 05:45:02 -0400
Received: from esealnt613.al.sw.ericsson.se (alteon-nat8.sw.ericsson.se [153.88.254.125])
	by falcon.al.sw.ericsson.se (8.12.9/8.12.9/WIREfire-1.6b) with ESMTP id h5I9mBcv024821;
	Wed, 18 Jun 2003 11:48:11 +0200
Received: from ESEALNT745.al.sw.ericsson.se ([153.88.251.5]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id MVP85K78; Wed, 18 Jun 2003 11:47:43 +0200
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <HT92BWYL>; Wed, 18 Jun 2003 11:46:22 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C63@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
To: "'Samuel Dur D. Jeyaseelan'" <sjeyasee@ssd.usa.alcatel.com>,
        "Brian F. G. Bidulock" <bidulock@openss7.org>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: RE: [Sigtran] RE: M3UA IG: section 3.15 reworked
Date: Wed, 18 Jun 2003 11:47:02 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA25374


Samuel and Brian, 

As the archives say, the agreements were:
- Move from AS-INACTIVE to AS-ACTIVE after n ASPs get the ASP-ACTIVE state.
- Stay in AS-ACTIVE even though the number of ASPs that are in ASP-ACTIVE state is below n.

Apart from that I've not seen any consensus on removing it. Although I can find several mails from Brian saying "strike section 3.15"... But I may be wrong. In that case I would appreciate you point me to the exact item where this consensus were made.

Inside the current RFC there are clear divergences: While section 1.4.4.1 says that "n" is the minimum number of redundant ASPs to handle traffic, section 4.3.2 says that an AS can handle traffic with only one ASP in ASP-ACTIVE. These two views MUST be aligned...


Since the relation between n+k and the AS states is not included in the RFC, I would recommend to maintain this text (with the final agreement). 


Cheers // Javier.



> -----Original Message-----
> From: Samuel Dur D. Jeyaseelan [mailto:sjeyasee@ssd.usa.alcatel.com]
> Sent: miércoles, 18 de junio de 2003 6:44
> To: Brian F. G. Bidulock
> Cc: Javier Pastor-Balbas (ECE); 'sigtran@ietf.org'; Ken Morneault
> (E-mail); Antonio Cañete (ECE)
> Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
> 
> 
> 
> Pastor,
> 
>  I too believe that concensus was made to delete section 3.15 from IG 
>  as RFC is sufficient to explain n+k case.
> 
> --Samuel
> 
>   Alcatel USA, Inc.                  Internet: 
> <userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel 
> USA, Inc. *******
> 
> On Tue, 17 Jun 2003, Brian F. G. Bidulock wrote:
> 
> > Javier,
> > 
> > I believe the concensus from the last long discussions was to
> > remove section 3.15.
> > 
> > --brian
> > 
> > Javier Pastor-Balbas (ECE) wrote:                           
>                         (Tue, 17 Jun 2003 16:51:16)
> > > This is the last version. There were still some 
> unfinished sentences and inconsistences in the first text I 
> sent. Now, they are fixed.
> > > 
> > > Cheers // Javier.
> > > 
> > > 
> > > --------- 
> > > Old text: (Section 4.3.2) 
> > > ---------
> > > 
> > > AS-DOWN: The Application Server is unavailable.  This 
> state implies 
> > > that all related ASPs are in the ASP-DOWN state for this 
> AS. Initially the AS will be in this state. An Application 
> Server is in the AS-DOWN state when it is removed from a 
> configuration.
> > > 
> > > AS-INACTIVE: The Application Server is available but no 
> application 
> > > traffic is active (i.e., one or more related ASPs are in the ASP-
> > > INACTIVE state, but none in the ASP-ACTIVE state).  The recovery 
> > > timer T(r) is not running or has expired. 
> > > 
> > > AS-ACTIVE: The Application Server is available and 
> application traffic is active.  This state implies that at 
> least one ASP is in the ASP-ACTIVE state.
> > > 
> > > AS-PENDING: An active ASP has transitioned to 
> ASP-INACTIVE or ASP-DOWN  and it was the last remaining 
> active ASP in the AS.  A recovery timer T(r) SHOULD be 
> started and all incoming signalling messages SHOULD be queued 
> by the SGP. If an ASP becomes ASP-ACTIVE before T(r) expires, 
> the AS is moved to the AS-ACTIVE state and all the queued 
> messages will be sent to the ASP. 
> > > 
> > > If T(r) expires before an ASP becomes ASP-ACTIVE, and the 
> SGP has no 
> > > alternative, the SGP may stops queuing messages and discards all 
> > > previously queued messages. The AS will move to the 
> AS-INACTIVE state 
> > > if at least one ASP is in ASP-INACTIVE state, otherwise 
> it will move 
> > > to AS-DOWN state. 
> > > 
> > > Figure 5 shows an example AS state machine for the case where the 
> > > AS/ASP data is preconfigured.  For other cases where the AS/ASP 
> > > configuration data is created dynamically, there would be 
> differences 
> > > in the state machine, especially at creation of the AS.  
> > > 
> > >                  Figure 5: AS State Transition Diagram
> > > 
> > >      +----------+   one ASP trans to ACTIVE   +-------------+
> > >      |    AS-   |---------------------------->|     AS-   
>   |      
> > >      | INACTIVE |                             |   ACTIVE    |
> > >      |          |<---                         |             |
> > >      +----------+    \                        +-------------+
> > >         ^   |         \ Tr Expiry,                ^    |
> > >         |   |          \ at least one             |    |
> > >         |   |           \ ASP in ASP-INACTIVE     |    |
> > >         |   |            \                        |    |
> > >         |   |             \                       |    |
> > >         |   |              \                      |    |
> > > one ASP |   | all ASP       \            one ASP  |    | 
> Last ACTIVE
> > > trans   |   | trans to       \           trans to |    | 
> ASP trans to
> > > to      |   | ASP-DOWN        -------\   ASP-     |    | 
> ASP-INACTIVE
> > > ASP-    |   |                         \  ACTIVE   |    | 
> or ASP-DOWN
> > > INACTIVE|   |                          \          |    |  
> (start Tr)
> > >         |   |                           \         |    |
> > >         |   |                            \        |    |
> > >         |   v                             \       |    v         
> > >      +----------+                          \  +-------------+
> > >      |          |                           --|           
>   |      
> > >      | AS-DOWN  |                             | AS-PENDING  |
> > >      |          |                             |  (queueing) |
> > >      |          |<----------------------------|             |
> > >      +----------+    Tr Expiry and no ASP     +-------------+
> > >                      in ASP-INACTIVE state)   
> > > 
> > >  Tr = Recovery Timer
> > > 
> > > 
> > > 
> > > For example, where the AS/ASP configuration data is not 
> created until 
> > > Registration of the first ASP, the AS-INACTIVE state is entered 
> > > directly upon the first successful REG REQ from an ASP.  Another 
> > > example is where the AS/ASP configuration data is not 
> created until the first ASP successfully enters the 
> ASP-ACTIVE state.  In this case the AS-ACTIVE state is 
> entered directly.
> > > 
> > > 
> > > --------- 
> > > New text: (Section 4.3.2) 
> > > ---------
> > > 
> > > AS-DOWN: The Application Server is unavailable.  This 
> state implies that the number of ASPs being in ASP-INACTIVE 
> or ASP-ACTIVE is less than "n". Initially the AS will be in 
> this state. An Application Server is in the AS-DOWN state 
> when it is removed from a configuration.
> > > 
> > > AS-INACTIVE: The Application Server is available but no 
> application traffic is active. This implies that there are at 
> least n ASPs in either ASP-INACTIVE or ASP-ACTIVE but the 
> total number of ASPs in ASP-ACTIVE state has not reach n.  
> The recovery timer T(r) is not running or has expired. 
> > > 
> > > AS-ACTIVE: The Application Server is available and 
> application traffic is active. The AS moves to this state 
> after being in AS-INACTIVE and getting n ASPs in ASP-ACTIVE 
> state or, after reaching AS-ACTIVE and keeping one or more 
> ASPs in ASP-ACTIVE state. 
> > > 
> > > AS-PENDING: The last active ASP has transitioned from 
> ASP-ACTIVE to ASP-INACTIVE or ASP-DOWN.  A recovery timer 
> T(r) SHOULD be started and all incoming signalling messages 
> SHOULD be queued by the SGP. If an ASP becomes ASP-ACTIVE 
> before T(r) expires, the AS is moved to the AS-ACTIVE state 
> and all the queued messages will be sent to the ASP. 
> > > 
> > > If T(r) expires before an ASP becomes ASP-ACTIVE, the SGP 
> MAY stops queuing messages and discards all 
> > > previously queued messages. The AS will move to the 
> AS-INACTIVE state 
> > > if at least the number of ASPs in ASP-INACTIVE sum n, 
> otherwise it will move to AS-DOWN state. 
> > > 
> > > Figure 5 shows an example AS state machine for the case where the 
> > > AS/ASP data is preconfigured and an n+k redundancy model. 
> > > 
> > > 
> > >              Figure 5: AS State Transition Diagram
> > > 
> > >                    
> > >      +----------+          IA2AC              +-------------+
> > >      |    AS-   |---------------------------->|     AS-     |
> > >      | INACTIVE |                             |   ACTIVE    |
> > >      |          |<-----------                 |             |
> > >      +----------+            \                +-------------+
> > >         ^   |                 \                    ^   |
> > >         |   | IA2DN            \ PN2IA             |   | AC2PN
> > >         |   |                   \                  |   | 
> > >   DN2IA |   |                    \          PN2AC  |   | 
> > >         |   v                     \                |   v
> > >      +----------+                  \          +-------------+
> > >      |          |                   ----------|             |
> > >      | AS-DOWN  |                             | AS-PENDING  |
> > >      |          |                  PN2DN      |  (queueing) |
> > >      |          |<----------------------------|             |
> > >      +----------+                             +-------------+
> > > 
> > > 
> > > 
> > > DN2IA: One ASP moves to ASP-INACTIVE causing that n ASPs 
> are in either ASP-ACTIVE or ASP-INACTIVE states.
> > > 
> > > IA2DN: One ASP moves to ASP-DOWN causing that the number 
> of ASPs in either ASP-ACTIVE or ASP-INACTIVE drops below n.
> > > 
> > > IA2AC: one ASP moves to ASP-ACTIVE, causing number of 
> ASPs in the ASP-ACTIVE state to be n.
> > > 
> > > AC2PN: the last ASP in ASP-ACTIVE state moves to 
> ASP-INACTIVE or ASP-DOWN states, causing the number of ASPs 
> in ASP-ACTIVE drop below 1.
> > > 
> > > PN2AC: One ASP moves to ASP-ACTIVE.
> > > 
> > > PN2IA: T(r) Expiry, n or more ASPs are in ASP-INACTIVE.
> > > 
> > > PN2DN: T(r) Expiry, the number of ASPs in ASP-INACTIVE 
> state is less than n.
> > > 
> > > As "n" ASPs are needed to handle the maximum engineered 
> load of the AS, an AS becomes AS-ACTIVE right after n ASPs 
> reach the ASP-ACTIVE state during the start-up phase. Once 
> the traffic is flowing, an AS keeps the AS-ACTIVE state till 
> the last ASP turns to another state different to ASP-ACTIVE, 
> avoiding unnecessary traffic disturbances as long as there 
> are ASPs available, in the assumption that the AS will not 
> always be exposed to the maximum load. 
> > > 
> > > There are other cases where the AS/ASP configuration data 
> is created dynamically. In those cases there would be 
> differences in the state machine, especially at creation of 
> the AS. For example, where the AS/ASP configuration data is 
> not created until Registration of the first ASP, the 
> AS-INACTIVE state is entered directly upon the nth successful 
> REG REQ from an ASP belonging to that AS.  Another example is 
> where the AS/ASP configuration data is not created until the 
> nth ASP successfully enters the ASP-ACTIVE state.  In this 
> latter case the AS-ACTIVE state is entered directly.
> > > 
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> 

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



From exim@www1.ietf.org  Wed Jun 18 05:57:28 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25542
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 05:57:28 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5I9v1L02410
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 05:57:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SZga-0000cd-TY; Wed, 18 Jun 2003 05:57:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SZfc-0000ZA-Hv
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 05:56:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25492
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 05:55:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SZdM-0001ls-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 05:53:40 -0400
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47] helo=penguin.al.sw.ericsson.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SZdL-0001lp-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 05:53:39 -0400
Received: from esealnt613.al.sw.ericsson.se (alteon-nat8.sw.ericsson.se [153.88.254.125])
	by penguin.al.sw.ericsson.se (8.12.9/8.12.9/WIREfire-1.6b) with ESMTP id h5I9tuw2012229;
	Wed, 18 Jun 2003 11:55:57 +0200 (MEST)
Received: from ESEALNT745.al.sw.ericsson.se ([153.88.251.5]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id MVP85NPV; Wed, 18 Jun 2003 11:56:20 +0200
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <HT92BW8V>; Wed, 18 Jun 2003 11:54:59 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C64@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
To: "'Tolga Asveren'" <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: RE: [Sigtran] RE: M3UA IG: section 3.15 reworked
Date: Wed, 18 Jun 2003 11:55:39 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


Hi Tolga, 

I think I understand your concern. If we want that both ASPs and SGPs have the same AS state view, one option is to configure T(r) in both machines with the same value. But even then there is a network delay that you may not control. In that case the ASPs will realize of their new state with the help of NTFY message.

Another different point is the transition PN2AC. It follows the philosophy of having the AS-ACTIVE state even when only one ASP is in ASP-ACTIVE state. It's a result of adapting the model to the max-engineered-load "n" view.

Cheers // Javier.



> -----Original Message-----
> From: Tolga Asveren [mailto:tolga_asveren@yahoo.com]
> Sent: martes, 17 de junio de 2003 21:27
> To: sigtran@ietf.org
> Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
> 
> 
> Hi Javier,
> 
> IMO the changes in general are nice, I have one
> question/comment though:
> For PN2AC transition, unless ASPs have knowledge of
> T(r), they can't decide whether the first ACTIVE ASP
> will make AS to switch to ACTIVE or not -because they
> can't know whether AS has already switched to INACTIVE
> after T(r) expiry or not- (AS state machine is
> described from SG point of view but I believe we
> should make it possible that ASPs and SGPs can have
> the same AS state view) -in fact I am not sure,
> whether to favor PN2AC transition by allowing it to
> happen with only one ACTIVE ASP is the best solution
> or not-.
> Furthermore, if the proposed PN2AC is going to be kept
> I would think PN2IA should be somethink like "T(r)
> expiry, no ACTIVE ASPs"
> 
>     Tolga
> --- "Javier Pastor-Balbas (ECE)"
> <javier.pastor-balbas@ece.ericsson.se> wrote:
> > This is the last version. There were still some
> > unfinished sentences and inconsistences in the first
> > text I sent. Now, they are fixed.
> > 
> > Cheers // Javier.
> > 
> > 
> > --------- 
> > Old text: (Section 4.3.2) 
> > ---------
> > 
> > AS-DOWN: The Application Server is unavailable. 
> > This state implies 
> > that all related ASPs are in the ASP-DOWN state for
> > this AS. Initially the AS will be in this state. An
> > Application Server is in the AS-DOWN state when it
> > is removed from a configuration.
> > 
> > AS-INACTIVE: The Application Server is available but
> > no application 
> > traffic is active (i.e., one or more related ASPs
> > are in the ASP-
> > INACTIVE state, but none in the ASP-ACTIVE state). 
> > The recovery 
> > timer T(r) is not running or has expired. 
> > 
> > AS-ACTIVE: The Application Server is available and
> > application traffic is active.  This state implies
> > that at least one ASP is in the ASP-ACTIVE state.
> > 
> > AS-PENDING: An active ASP has transitioned to
> > ASP-INACTIVE or ASP-DOWN  and it was the last
> > remaining active ASP in the AS.  A recovery timer
> > T(r) SHOULD be started and all incoming signalling
> > messages SHOULD be queued by the SGP. If an ASP
> > becomes ASP-ACTIVE before T(r) expires, the AS is
> > moved to the AS-ACTIVE state and all the queued
> > messages will be sent to the ASP. 
> > 
> > If T(r) expires before an ASP becomes ASP-ACTIVE,
> > and the SGP has no 
> > alternative, the SGP may stops queuing messages and
> > discards all 
> > previously queued messages. The AS will move to the
> > AS-INACTIVE state 
> > if at least one ASP is in ASP-INACTIVE state,
> > otherwise it will move 
> > to AS-DOWN state. 
> > 
> > Figure 5 shows an example AS state machine for the
> > case where the 
> > AS/ASP data is preconfigured.  For other cases where
> > the AS/ASP 
> > configuration data is created dynamically, there
> > would be differences 
> > in the state machine, especially at creation of the
> > AS.  
> > 
> >                  Figure 5: AS State Transition
> > Diagram
> > 
> >      +----------+   one ASP trans to ACTIVE  
> > +-------------+
> >      |    AS-   |---------------------------->|    
> > AS-     |      
> >      | INACTIVE |                             |  
> > ACTIVE    |
> >      |          |<---                         |     
> >        |
> >      +----------+    \                       
> > +-------------+
> >         ^   |         \ Tr Expiry,                ^ 
> >   |
> >         |   |          \ at least one             | 
> >   |
> >         |   |           \ ASP in ASP-INACTIVE     | 
> >   |
> >         |   |            \                        | 
> >   |
> >         |   |             \                       | 
> >   |
> >         |   |              \                      | 
> >   |
> > one ASP |   | all ASP       \            one ASP  | 
> >   | Last ACTIVE
> > trans   |   | trans to       \           trans to | 
> >   | ASP trans to
> > to      |   | ASP-DOWN        -------\   ASP-     | 
> >   | ASP-INACTIVE
> > ASP-    |   |                         \  ACTIVE   | 
> >   | or ASP-DOWN
> > INACTIVE|   |                          \          | 
> >   |  (start Tr)
> >         |   |                           \         | 
> >   |
> >         |   |                            \        | 
> >   |
> >         |   v                             \       | 
> >   v         
> >      +----------+                          \ 
> > +-------------+
> >      |          |                           --|     
> >        |      
> >      | AS-DOWN  |                             |
> > AS-PENDING  |
> >      |          |                             | 
> > (queueing) |
> >      |          |<----------------------------|     
> >        |
> >      +----------+    Tr Expiry and no ASP    
> > +-------------+
> >                      in ASP-INACTIVE state)   
> > 
> >  Tr = Recovery Timer
> > 
> > 
> > 
> > For example, where the AS/ASP configuration data is
> > not created until 
> > Registration of the first ASP, the AS-INACTIVE state
> > is entered 
> > directly upon the first successful REG REQ from an
> > ASP.  Another 
> > example is where the AS/ASP configuration data is
> > not created until the first ASP successfully enters
> > the ASP-ACTIVE state.  In this case the AS-ACTIVE
> > state is entered directly.
> > 
> > 
> > --------- 
> > New text: (Section 4.3.2) 
> > ---------
> > 
> > AS-DOWN: The Application Server is unavailable. 
> > This state implies that the number of ASPs being in
> > ASP-INACTIVE or ASP-ACTIVE is less than "n".
> > Initially the AS will be in this state. An
> > Application Server is in the AS-DOWN state when it
> > is removed from a configuration.
> > 
> > AS-INACTIVE: The Application Server is available but
> > no application traffic is active. This implies that
> > there are at least n ASPs in either ASP-INACTIVE or
> > ASP-ACTIVE but the total number of ASPs in
> > ASP-ACTIVE state has not reach n.  The recovery
> > timer T(r) is not running or has expired. 
> > 
> > AS-ACTIVE: The Application Server is available and
> > application traffic is active. The AS moves to this
> > state after being in AS-INACTIVE and getting n ASPs
> > in ASP-ACTIVE state or, after reaching AS-ACTIVE and
> > keeping one or more ASPs in ASP-ACTIVE state. 
> > 
> > AS-PENDING: The last active ASP has transitioned
> > from ASP-ACTIVE to ASP-INACTIVE or ASP-DOWN.  A
> > recovery timer T(r) SHOULD be started and all
> > incoming signalling messages SHOULD be queued by the
> > SGP. If an ASP becomes ASP-ACTIVE before T(r)
> > expires, the AS is moved to the AS-ACTIVE state and
> > all the queued messages will be sent to the ASP. 
> > 
> > If T(r) expires before an ASP becomes ASP-ACTIVE,
> > the SGP MAY stops queuing messages and discards all 
> > previously queued messages. The AS will move to the
> > AS-INACTIVE state 
> > if at least the number of ASPs in ASP-INACTIVE sum
> > n, otherwise it will move to AS-DOWN state. 
> > 
> > Figure 5 shows an example AS state machine for the
> > case where the 
> > AS/ASP data is preconfigured and an n+k redundancy
> > model. 
> > 
> > 
> >              Figure 5: AS State Transition Diagram
> > 
> >                    
> >      +----------+          IA2AC             
> > +-------------+
> >      |    AS-   |---------------------------->|    
> > AS-     |
> >      | INACTIVE |                             |  
> > ACTIVE    |
> >      |          |<-----------                 |     
> >        |
> >      +----------+            \               
> > +-------------+
> >         ^   |                 \                    ^
> >   |
> >         |   | IA2DN            \ PN2IA             |
> >   | AC2PN
> >         |   |                   \                  |
> >   | 
> >   DN2IA |   |                    \          PN2AC  |
> >   | 
> >         |   v                     \                |
> >   v
> >      +----------+                  \         
> > +-------------+
> >      |          |                   ----------|     
> >        |
> > 
> === message truncated ===
> 
> 
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 

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



From exim@www1.ietf.org  Wed Jun 18 06:03:28 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25771
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 06:03:28 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5IA31903594
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 06:03:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SZmO-0000vk-Mx; Wed, 18 Jun 2003 06:03:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SZla-0000vB-FC
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 06:02:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25747
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 06:02:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SZjJ-0001o4-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 05:59:49 -0400
Received: from falcon.ericsson.se ([193.180.251.52] helo=falcon.al.sw.ericsson.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SZjI-0001o1-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 05:59:49 -0400
Received: from esealnt613.al.sw.ericsson.se (alteon-nat8.sw.ericsson.se [153.88.254.125])
	by falcon.al.sw.ericsson.se (8.12.9/8.12.9/WIREfire-1.6b) with ESMTP id h5IA2lcv026620;
	Wed, 18 Jun 2003 12:02:47 +0200
Received: from ESEALNT744.al.sw.ericsson.se ([153.88.251.4]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id MVP85PFS; Wed, 18 Jun 2003 12:02:19 +0200
Received: by ESEALNT744.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NBCQ8NTL>; Wed, 18 Jun 2003 12:01:55 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C65@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
To: "'kakaul@hss.hns.com'" <kakaul@hss.hns.com>
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] RE: M3UA IG: section 3.15 reworked
Date: Wed, 18 Jun 2003 12:01:05 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id GAA25771


Hi Kamesh, 

The main objective is keeping the system working as long as possible. NTFY messages give the AS the clue that the system is not working fine and operator will have to decide whether stop traffic or not. When the number of ASPs is below "n", AS side should take steps ASAP to activate new ASPs. 

Cheers // Javier.

> -----Original Message-----
> From: kakaul@hss.hns.com [mailto:kakaul@hss.hns.com]
> Sent: miércoles, 18 de junio de 2003 6:45
> To: Javier Pastor-Balbas (ECE)
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
> 
> 
> 
> 
> 
> 
> Hi Javier
>   If AS has transitioned to AS-PENDING as a result of ASP 
> inactive being
> received
>   from last ASP.Now  during T(r) if one of the ASP becomes 
> active.According
> to the changed
>   text AS transitions  to AS - ACTIVE even though total 
> number of active
> ASP's is 1 and n is greater than 1.
>   So if configuration of active ASP's remain same there after 
> AS will have
> insufficient active
>   ASP's to handle the engineered application server traffic. 
> IMO it is not
> a fear assumtion to follow
>   1 + k redundancy after AS state transitions from AS - 
> ACTIVE state to any
> other state.
> 
> Regards
> Kamesh
> Hughes Software Systems
> 
> 
> 
> 
> "Javier Pastor-Balbas (ECE)"
> <javier.pastor-balbas@ece.ericsson.se>@ietf.org on 06/17/2003 
> 08:21:16 PM
> 
> Sent by:    sigtran-admin@ietf.org
> 
> 
> To:    "Javier Pastor-Balbas (ECE)" 
> <javier.pastor-balbas@ece.ericsson.se>,
>        "'sigtran@ietf.org'" <sigtran@ietf.org>
> cc:    "Ken Morneault (E-mail)" <kmorneau@cisco.com>, Antonio 
> Cañete (ECE)
>        <antonio.canete-martinez@ece.ericsson.se>
> 
> Subject:    [Sigtran] RE: M3UA IG: section 3.15 reworked
> 
> 
> This is the last version. There were still some unfinished 
> sentences and
> inconsistences in the first text I sent. Now, they are fixed.
> 
> Cheers // Javier.
> 
> 
> ---------
> Old text: (Section 4.3.2)
> ---------
> 
> AS-DOWN: The Application Server is unavailable.  This state implies
> that all related ASPs are in the ASP-DOWN state for this AS. 
> Initially the
> AS will be in this state. An Application Server is in the 
> AS-DOWN state
> when it is removed from a configuration.
> 
> AS-INACTIVE: The Application Server is available but no application
> traffic is active (i.e., one or more related ASPs are in the ASP-
> INACTIVE state, but none in the ASP-ACTIVE state).  The recovery
> timer T(r) is not running or has expired.
> 
> AS-ACTIVE: The Application Server is available and 
> application traffic is
> active.  This state implies that at least one ASP is in the ASP-ACTIVE
> state.
> 
> AS-PENDING: An active ASP has transitioned to ASP-INACTIVE or 
> ASP-DOWN  and
> it was the last remaining active ASP in the AS.  A recovery timer T(r)
> SHOULD be started and all incoming signalling messages SHOULD 
> be queued by
> the SGP. If an ASP becomes ASP-ACTIVE before T(r) expires, 
> the AS is moved
> to the AS-ACTIVE state and all the queued messages will be 
> sent to the ASP.
> 
> If T(r) expires before an ASP becomes ASP-ACTIVE, and the SGP has no
> alternative, the SGP may stops queuing messages and discards all
> previously queued messages. The AS will move to the AS-INACTIVE state
> if at least one ASP is in ASP-INACTIVE state, otherwise it will move
> to AS-DOWN state.
> 
> Figure 5 shows an example AS state machine for the case where the
> AS/ASP data is preconfigured.  For other cases where the AS/ASP
> configuration data is created dynamically, there would be differences
> in the state machine, especially at creation of the AS.
> 
>                  Figure 5: AS State Transition Diagram
> 
>      +----------+   one ASP trans to ACTIVE   +-------------+
>      |    AS-   |---------------------------->|     AS-     |
>      | INACTIVE |                             |   ACTIVE    |
>      |          |<---                         |             |
>      +----------+    \                        +-------------+
>         ^   |         \ Tr Expiry,                ^    |
>         |   |          \ at least one             |    |
>         |   |           \ ASP in ASP-INACTIVE     |    |
>         |   |            \                        |    |
>         |   |             \                       |    |
>         |   |              \                      |    |
> one ASP |   | all ASP       \            one ASP  |    | Last ACTIVE
> trans   |   | trans to       \           trans to |    | ASP trans to
> to      |   | ASP-DOWN        -------\   ASP-     |    | ASP-INACTIVE
> ASP-    |   |                         \  ACTIVE   |    | or ASP-DOWN
> INACTIVE|   |                          \          |    |  (start Tr)
>         |   |                           \         |    |
>         |   |                            \        |    |
>         |   v                             \       |    v
>      +----------+                          \  +-------------+
>      |          |                           --|             |
>      | AS-DOWN  |                             | AS-PENDING  |
>      |          |                             |  (queueing) |
>      |          |<----------------------------|             |
>      +----------+    Tr Expiry and no ASP     +-------------+
>                      in ASP-INACTIVE state)
> 
>  Tr = Recovery Timer
> 
> 
> 
> For example, where the AS/ASP configuration data is not created until
> Registration of the first ASP, the AS-INACTIVE state is entered
> directly upon the first successful REG REQ from an ASP.  Another
> example is where the AS/ASP configuration data is not created 
> until the
> first ASP successfully enters the ASP-ACTIVE state.  In this case the
> AS-ACTIVE state is entered directly.
> 
> 
> ---------
> New text: (Section 4.3.2)
> ---------
> 
> AS-DOWN: The Application Server is unavailable.  This state 
> implies that
> the number of ASPs being in ASP-INACTIVE or ASP-ACTIVE is 
> less than "n".
> Initially the AS will be in this state. An Application Server 
> is in the
> AS-DOWN state when it is removed from a configuration.
> 
> AS-INACTIVE: The Application Server is available but no 
> application traffic
> is active. This implies that there are at least n ASPs in either
> ASP-INACTIVE or ASP-ACTIVE but the total number of ASPs in 
> ASP-ACTIVE state
> has not reach n.  The recovery timer T(r) is not running or 
> has expired.
> 
> AS-ACTIVE: The Application Server is available and 
> application traffic is
> active. The AS moves to this state after being in AS-INACTIVE 
> and getting n
> ASPs in ASP-ACTIVE state or, after reaching AS-ACTIVE and 
> keeping one or
> more ASPs in ASP-ACTIVE state.
> 
> AS-PENDING: The last active ASP has transitioned from ASP-ACTIVE to
> ASP-INACTIVE or ASP-DOWN.  A recovery timer T(r) SHOULD be 
> started and all
> incoming signalling messages SHOULD be queued by the SGP. If 
> an ASP becomes
> ASP-ACTIVE before T(r) expires, the AS is moved to the 
> AS-ACTIVE state and
> all the queued messages will be sent to the ASP.
> 
> If T(r) expires before an ASP becomes ASP-ACTIVE, the SGP MAY 
> stops queuing
> messages and discards all
> previously queued messages. The AS will move to the AS-INACTIVE state
> if at least the number of ASPs in ASP-INACTIVE sum n, 
> otherwise it will
> move to AS-DOWN state.
> 
> Figure 5 shows an example AS state machine for the case where the
> AS/ASP data is preconfigured and an n+k redundancy model.
> 
> 
>              Figure 5: AS State Transition Diagram
> 
> 
>      +----------+          IA2AC              +-------------+
>      |    AS-   |---------------------------->|     AS-     |
>      | INACTIVE |                             |   ACTIVE    |
>      |          |<-----------                 |             |
>      +----------+            \                +-------------+
>         ^   |                 \                    ^   |
>         |   | IA2DN            \ PN2IA             |   | AC2PN
>         |   |                   \                  |   |
>   DN2IA |   |                    \          PN2AC  |   |
>         |   v                     \                |   v
>      +----------+                  \          +-------------+
>      |          |                   ----------|             |
>      | AS-DOWN  |                             | AS-PENDING  |
>      |          |                  PN2DN      |  (queueing) |
>      |          |<----------------------------|             |
>      +----------+                             +-------------+
> 
> 
> 
> DN2IA: One ASP moves to ASP-INACTIVE causing that n ASPs are in either
> ASP-ACTIVE or ASP-INACTIVE states.
> 
> IA2DN: One ASP moves to ASP-DOWN causing that the number of 
> ASPs in either
> ASP-ACTIVE or ASP-INACTIVE drops below n.
> 
> IA2AC: one ASP moves to ASP-ACTIVE, causing number of ASPs in the
> ASP-ACTIVE state to be n.
> 
> AC2PN: the last ASP in ASP-ACTIVE state moves to ASP-INACTIVE 
> or ASP-DOWN
> states, causing the number of ASPs in ASP-ACTIVE drop below 1.
> 
> PN2AC: One ASP moves to ASP-ACTIVE.
> 
> PN2IA: T(r) Expiry, n or more ASPs are in ASP-INACTIVE.
> 
> PN2DN: T(r) Expiry, the number of ASPs in ASP-INACTIVE state 
> is less than
> n.
> 
> As "n" ASPs are needed to handle the maximum engineered load 
> of the AS, an
> AS becomes AS-ACTIVE right after n ASPs reach the ASP-ACTIVE 
> state during
> the start-up phase. Once the traffic is flowing, an AS keeps 
> the AS-ACTIVE
> state till the last ASP turns to another state different to 
> ASP-ACTIVE,
> avoiding unnecessary traffic disturbances as long as there are ASPs
> available, in the assumption that the AS will not always be 
> exposed to the
> maximum load.
> 
> There are other cases where the AS/ASP configuration data is created
> dynamically. In those cases there would be differences in the state
> machine, especially at creation of the AS. For example, where 
> the AS/ASP
> configuration data is not created until Registration of the 
> first ASP, the
> AS-INACTIVE state is entered directly upon the nth successful 
> REG REQ from
> an ASP belonging to that AS.  Another example is where the AS/ASP
> configuration data is not created until the nth ASP 
> successfully enters the
> ASP-ACTIVE state.  In this latter case the AS-ACTIVE state is entered
> directly.
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
>  https://www1.ietf.org/mailman/listinfo/sigtran
> 
> 

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



From exim@www1.ietf.org  Wed Jun 18 06:27:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26136
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 06:27:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5IAR2006633
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 06:27:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Sa9d-0001hs-Eg; Wed, 18 Jun 2003 06:27:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Sa9M-0001hJ-Dq
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 06:26:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26132
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 06:26:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sa75-0001vW-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 06:24:23 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[C6DhKTkcaTsQrbvPXH/wiZ8vkTUMsKg4])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sa74-0001vT-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 06:24:22 -0400
Received: from ns.pigworks.openss7.net (IDENT:rG/nFmdfqRY+wRYA//B3wlJR5HIduAXu@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5IAQeX20484;
	Wed, 18 Jun 2003 04:26:40 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5IAQe124974;
	Wed, 18 Jun 2003 04:26:40 -0600
Date: Wed, 18 Jun 2003 04:26:39 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
Cc: "'Samuel Dur D. Jeyaseelan'" <sjeyasee@ssd.usa.alcatel.com>,
        "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
Message-ID: <20030618042639.A24847@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>,
	"'Samuel Dur D. Jeyaseelan'" <sjeyasee@ssd.usa.alcatel.com>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>
References: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C63@eestqnt105.es.eu.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C63@eestqnt105.es.eu.ericsson.se>; from javier.pastor-balbas@ece.ericsson.se on Wed, Jun 18, 2003 at 11:47:02AM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Javier,

Javier Pastor-Balbas (ECE) wrote:                                                   (Wed, 18 Jun 2003 11:47:02)
> 
> Samuel and Brian, 
> 
> As the archives say, the agreements were:
> - Move from AS-INACTIVE to AS-ACTIVE after n ASPs get the ASP-ACTIVE state.
> - Stay in AS-ACTIVE even though the number of ASPs that are in ASP-ACTIVE state is below n.
> 
> Apart from that I've not seen any consensus on removing it. Although I can
> find several mails from Brian saying "strike section 3.15"... But I may be
> wrong. In that case I would appreciate you point me to the exact item where
> this consensus were made.

Everyone agreed except for Tolga.

> 
> Inside the current RFC there are clear divergences: While section 1.4.4.1
> says that "n" is the minimum number of redundant ASPs to handle traffic,
> section 4.3.2 says that an AS can handle traffic with only one ASP in
> ASP-ACTIVE. These two views MUST be aligned...

This was already described repeatedly in the previous mails and is clear
in the RFC.

Where is the need for text changes?

> 
> Since the relation between n+k and the AS states is not included in the RFC,
> I would recommend to maintain this text (with the final agreement). 

I disagree with alterations to the text in the RFC.  No need has been
demonstrated for any alteration.

--brian

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

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



From exim@www1.ietf.org  Wed Jun 18 06:39:28 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26350
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 06:39:28 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5IAd1V08738
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 06:39:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SaLF-0002Gh-6n; Wed, 18 Jun 2003 06:39:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SaKk-0002GT-I1
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 06:38:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26321
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 06:38:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SaIT-0001yp-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 06:36:09 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[1Tot5pxJ2CnXUQXqDO30sOSxRxziY2Jo])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SaIS-0001ym-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 06:36:08 -0400
Received: from ns.pigworks.openss7.net (IDENT:kTdv+tEN5y/JHjP/hctpXxaEUdGBEECe@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5IAcIX20771;
	Wed, 18 Jun 2003 04:38:18 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5IAcHN25127;
	Wed, 18 Jun 2003 04:38:17 -0600
Date: Wed, 18 Jun 2003 04:38:17 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>,
        "Ken Morneault (E-mail)" <kmorneau@cisco.com>,
        =?iso-8859-1?Q?Antonio_Ca=F1ete_=28ECE=29?= <antonio.canete-martinez@ece.ericsson.se>
Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
Message-ID: <20030618043817.B24847@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>,
	"Ken Morneault (E-mail)" <kmorneau@cisco.com>,
	=?iso-8859-1?Q?Antonio_Ca=F1ete_=28ECE=29?= <antonio.canete-martinez@ece.ericsson.se>
References: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C61@eestqnt105.es.eu.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C61@eestqnt105.es.eu.ericsson.se>; from javier.pastor-balbas@ece.ericsson.se on Tue, Jun 17, 2003 at 04:51:16PM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Javier,

Please see comments below...

Javier Pastor-Balbas (ECE) wrote:                                                   (Tue, 17 Jun 2003 16:51:16)
> --------- 
> New text: (Section 4.3.2) 
> ---------
> 
> AS-DOWN: The Application Server is unavailable.  This state implies that the
> number of ASPs being in ASP-INACTIVE or ASP-ACTIVE is less than "n".
> Initially the AS will be in this state. An Application Server is in the
> AS-DOWN state when it is removed from a configuration.
> 
> AS-INACTIVE: The Application Server is available but no application traffic
> is active. This implies that there are at least n ASPs in either
> ASP-INACTIVE or ASP-ACTIVE but the total number of ASPs in ASP-ACTIVE state
> has not reach n.  The recovery timer T(r) is not running or has expired. 
> 
> AS-ACTIVE: The Application Server is available and application traffic is
> active. The AS moves to this state after being in AS-INACTIVE and getting n
> ASPs in ASP-ACTIVE state or, after reaching AS-ACTIVE and keeping one or
> more ASPs in ASP-ACTIVE state. 

I strongly disagree with the above.  The SG can move to the AS-ACTIVE state
with one ASP in the ASP-ACTIVE state: it need not wait until 'n'.  You are
still interpreting 'n' as some sort of absolute minimum number of ASPs,
when it was agreed that 'n' is the number of ASPs required to handle the
maximum engineered load.  As such, there is no reason why the SG cannot
place the AS AS-ACTIVE when one ASP is in the ASP-ACTIVE state for the AS.

The Old text is correct.  The above is incorrect.

> 
> AS-PENDING: The last active ASP has transitioned from ASP-ACTIVE to
> ASP-INACTIVE or ASP-DOWN.  A recovery timer T(r) SHOULD be started and all
> incoming signalling messages SHOULD be queued by the SGP. If an ASP becomes
> ASP-ACTIVE before T(r) expires, the AS is moved to the AS-ACTIVE state and
> all the queued messages will be sent to the ASP. 
> 
> If T(r) expires before an ASP becomes ASP-ACTIVE, the SGP MAY stops queuing
> messages and discards all previously queued messages. The AS will move to
> the AS-INACTIVE state if at least the number of ASPs in ASP-INACTIVE sum n,
> otherwise it will move to AS-DOWN state. 
> 
> Figure 5 shows an example AS state machine for the case where the 
> AS/ASP data is preconfigured and an n+k redundancy model. 
> 
> 
>              Figure 5: AS State Transition Diagram
> 
>                    
>      +----------+          IA2AC              +-------------+
>      |    AS-   |---------------------------->|     AS-     |
>      | INACTIVE |                             |   ACTIVE    |
>      |          |<-----------                 |             |
>      +----------+            \                +-------------+
>         ^   |                 \                    ^   |
>         |   | IA2DN            \ PN2IA             |   | AC2PN
>         |   |                   \                  |   | 
>   DN2IA |   |                    \          PN2AC  |   | 
>         |   v                     \                |   v
>      +----------+                  \          +-------------+
>      |          |                   ----------|             |
>      | AS-DOWN  |                             | AS-PENDING  |
>      |          |                  PN2DN      |  (queueing) |
>      |          |<----------------------------|             |
>      +----------+                             +-------------+
> 
> 
> 
> DN2IA: One ASP moves to ASP-INACTIVE causing that n ASPs are in either
> ASP-ACTIVE or ASP-INACTIVE states.
> 
> IA2DN: One ASP moves to ASP-DOWN causing that the number of ASPs in either
> ASP-ACTIVE or ASP-INACTIVE drops below n.

Wrong, as per above.  If one ASP is in the ASP-ACTIVE state for the AS,
the AS is AS-ACTIVE.

> 
> IA2AC: one ASP moves to ASP-ACTIVE, causing number of ASPs in the ASP-ACTIVE
> state to be n.

Wrong, as per above.  If one ASP moves to the ASP-ACTIVE state for the AS,
the AS is AS-ACTIVE.

> 
> AC2PN: the last ASP in ASP-ACTIVE state moves to ASP-INACTIVE or ASP-DOWN
> states, causing the number of ASPs in ASP-ACTIVE drop below 1.
> 
> PN2AC: One ASP moves to ASP-ACTIVE.
> 
> PN2IA: T(r) Expiry, n or more ASPs are in ASP-INACTIVE.
> 
> PN2DN: T(r) Expiry, the number of ASPs in ASP-INACTIVE state is less than n.
> 
> As "n" ASPs are needed to handle the maximum engineered load of the AS, an
> AS becomes AS-ACTIVE right after n ASPs reach the ASP-ACTIVE state during
> the start-up phase.

The above is incorrect per concensus.  For the start-up decision, the SG
can choose to either wait for 'n' or start traffic on the first active ASP.
What it MUST do not send NTFY(AS-ACTIVE) until it considers the AS in the
AS-ACTIVE state.

> Once the traffic is flowing, an AS keeps the AS-ACTIVE
> state till the last ASP turns to another state different to ASP-ACTIVE,
> avoiding unnecessary traffic disturbances as long as there are ASPs
> available, in the assumption that the AS will not always be exposed to the
> maximum load. 

It won't necessarily be exposed to maximum load on startup either.

Text below covers things internal to the SG only, and is unnecessary:

> 
> There are other cases where the AS/ASP configuration data is created
> dynamically. In those cases there would be differences in the state machine,
> especially at creation of the AS. For example, where the AS/ASP
> configuration data is not created until Registration of the first ASP, the
> AS-INACTIVE state is entered directly upon the nth successful REG REQ from
> an ASP belonging to that AS.  Another example is where the AS/ASP
> configuration data is not created until the nth ASP successfully enters the
> ASP-ACTIVE state.  In this latter case the AS-ACTIVE state is entered
> directly.

Stick with the old text.

--brian

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

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



From exim@www1.ietf.org  Wed Jun 18 06:59:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26757
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 06:59:30 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5IAx4X10525
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 06:59:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Saea-0002ii-NU; Wed, 18 Jun 2003 06:59:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Sae7-0002iF-6x
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 06:58:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26713
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 06:58:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sabq-000258-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 06:56:10 -0400
Received: from web12806.mail.yahoo.com ([216.136.174.41])
	by ietf-mx with smtp (Exim 4.12)
	id 19Sabp-000255-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 06:56:09 -0400
Message-ID: <20030618105827.77289.qmail@web12806.mail.yahoo.com>
Received: from [208.255.120.2] by web12806.mail.yahoo.com via HTTP; Wed, 18 Jun 2003 03:58:27 PDT
Date: Wed, 18 Jun 2003 03:58:27 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
To: sigtran@ietf.org
In-Reply-To: <20030618042639.A24847@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Please see comments below....
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Javier,
> 
> Javier Pastor-Balbas (ECE) wrote:                   
>                                (Wed, 18 Jun 2003
> 11:47:02)
> > 
> > Samuel and Brian, 
> > 
> > As the archives say, the agreements were:
> > - Move from AS-INACTIVE to AS-ACTIVE after n ASPs
> get the ASP-ACTIVE state.
> > - Stay in AS-ACTIVE even though the number of ASPs
> that are in ASP-ACTIVE state is below n.
> > 
> > Apart from that I've not seen any consensus on
> removing it. Although I can
> > find several mails from Brian saying "strike
> section 3.15"... But I may be
> > wrong. In that case I would appreciate you point
> me to the exact item where
> > this consensus were made.
> 
> Everyone agreed except for Tolga.
[TOLGA]It is clear that an AS, which is not ACTIVE,
SHOULD NOT send/receive application traffic. The only
way to achieve this is to harmonize state change of AS
on ASPs/SGPs. RFC fails to address this for n>1
because it is written always as n=1 in mind. IG
corrects this. 


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

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



From exim@www1.ietf.org  Wed Jun 18 07:12:28 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26969
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 07:12:28 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5IBC0l12502
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 07:12:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Sar9-0003Ej-Mv; Wed, 18 Jun 2003 07:11:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Saqu-0003EE-OV
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 07:11:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26962
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 07:11:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Saod-00028a-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 07:09:23 -0400
Received: from auds953.usa.alcatel.com ([143.209.238.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Saoc-00028X-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 07:09:22 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h5IBB3LX002111;
	Wed, 18 Jun 2003 06:11:04 -0500 (CDT)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h5IBAj1C007643;
	Wed, 18 Jun 2003 06:10:45 -0500 (CDT)
Date: Wed, 18 Jun 2003 06:10:45 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
cc: "Brian F. G. Bidulock" <bidulock@openss7.org>,
        "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: RE: [Sigtran] RE: M3UA IG: section 3.15 reworked
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C63@eestqnt105.es.eu.ericsson.se>
Message-ID: <Pine.SOL.4.10.10306180554570.6574-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by ietf.org id HAA26969


Pastor,
 
 I could not exactly locate the email referring to remove section
3.15 from IG.But following things i could recollect

1. 'n' is mantatory at start case
2. 'n' is # of ASPs to handle the maximum engineered load
3. When # of ASPs < n (where n > 0),AS state will be still AS-ACTIV
   but SGP will direct all traffic to the ACTIVE ASP(this is not a
   start case).All that SGP needs
   is change in the following internal table

   When Both ASPs-ACTIVE
   ---------------------
   ASP1 -- SLS1
   ASP2 -- SLS2


   When ASP1 goes DOWN
   -------------------
   ASP2 -- SLS1 + SLS2

   
--Samuel

  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******

On Wed, 18 Jun 2003, Javier Pastor-Balbas (ECE) wrote:

> 
> Samuel and Brian, 
> 
> As the archives say, the agreements were:
> - Move from AS-INACTIVE to AS-ACTIVE after n ASPs get the ASP-ACTIVE state.
> - Stay in AS-ACTIVE even though the number of ASPs that are in ASP-ACTIVE state is below n.
> 
> Apart from that I've not seen any consensus on removing it. Although I can find several mails from Brian saying "strike section 3.15"... But I may be wrong. In that case I would appreciate you point me to the exact item where this consensus were made.
> 
> Inside the current RFC there are clear divergences: While section 1.4.4.1 says that "n" is the minimum number of redundant ASPs to handle traffic, section 4.3.2 says that an AS can handle traffic with only one ASP in ASP-ACTIVE. These two views MUST be aligned...
> 
> 
> Since the relation between n+k and the AS states is not included in the RFC, I would recommend to maintain this text (with the final agreement). 
> 
> 
> Cheers // Javier.
> 
> 
> 
> > -----Original Message-----
> > From: Samuel Dur D. Jeyaseelan [mailto:sjeyasee@ssd.usa.alcatel.com]
> > Sent: miércoles, 18 de junio de 2003 6:44
> > To: Brian F. G. Bidulock
> > Cc: Javier Pastor-Balbas (ECE); 'sigtran@ietf.org'; Ken Morneault
> > (E-mail); Antonio Cañete (ECE)
> > Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
> > 
> > 
> > 
> > Pastor,
> > 
> >  I too believe that concensus was made to delete section 3.15 from IG 
> >  as RFC is sufficient to explain n+k case.
> > 
> > --Samuel
> > 
> >   Alcatel USA, Inc.                  Internet: 
> > <userid>@ssd.usa.alcatel.com
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel 
> > USA, Inc. *******
> > 
> > On Tue, 17 Jun 2003, Brian F. G. Bidulock wrote:
> > 
> > > Javier,
> > > 
> > > I believe the concensus from the last long discussions was to
> > > remove section 3.15.
> > > 
> > > --brian
> > > 
> > > Javier Pastor-Balbas (ECE) wrote:                           
> >                         (Tue, 17 Jun 2003 16:51:16)
> > > > This is the last version. There were still some 
> > unfinished sentences and inconsistences in the first text I 
> > sent. Now, they are fixed.
> > > > 
> > > > Cheers // Javier.
> > > > 
> > > > 
> > > > --------- 
> > > > Old text: (Section 4.3.2) 
> > > > ---------
> > > > 
> > > > AS-DOWN: The Application Server is unavailable.  This 
> > state implies 
> > > > that all related ASPs are in the ASP-DOWN state for this 
> > AS. Initially the AS will be in this state. An Application 
> > Server is in the AS-DOWN state when it is removed from a 
> > configuration.
> > > > 
> > > > AS-INACTIVE: The Application Server is available but no 
> > application 
> > > > traffic is active (i.e., one or more related ASPs are in the ASP-
> > > > INACTIVE state, but none in the ASP-ACTIVE state).  The recovery 
> > > > timer T(r) is not running or has expired. 
> > > > 
> > > > AS-ACTIVE: The Application Server is available and 
> > application traffic is active.  This state implies that at 
> > least one ASP is in the ASP-ACTIVE state.
> > > > 
> > > > AS-PENDING: An active ASP has transitioned to 
> > ASP-INACTIVE or ASP-DOWN  and it was the last remaining 
> > active ASP in the AS.  A recovery timer T(r) SHOULD be 
> > started and all incoming signalling messages SHOULD be queued 
> > by the SGP. If an ASP becomes ASP-ACTIVE before T(r) expires, 
> > the AS is moved to the AS-ACTIVE state and all the queued 
> > messages will be sent to the ASP. 
> > > > 
> > > > If T(r) expires before an ASP becomes ASP-ACTIVE, and the 
> > SGP has no 
> > > > alternative, the SGP may stops queuing messages and discards all 
> > > > previously queued messages. The AS will move to the 
> > AS-INACTIVE state 
> > > > if at least one ASP is in ASP-INACTIVE state, otherwise 
> > it will move 
> > > > to AS-DOWN state. 
> > > > 
> > > > Figure 5 shows an example AS state machine for the case where the 
> > > > AS/ASP data is preconfigured.  For other cases where the AS/ASP 
> > > > configuration data is created dynamically, there would be 
> > differences 
> > > > in the state machine, especially at creation of the AS.  
> > > > 
> > > >                  Figure 5: AS State Transition Diagram
> > > > 
> > > >      +----------+   one ASP trans to ACTIVE   +-------------+
> > > >      |    AS-   |---------------------------->|     AS-   
> >   |      
> > > >      | INACTIVE |                             |   ACTIVE    |
> > > >      |          |<---                         |             |
> > > >      +----------+    \                        +-------------+
> > > >         ^   |         \ Tr Expiry,                ^    |
> > > >         |   |          \ at least one             |    |
> > > >         |   |           \ ASP in ASP-INACTIVE     |    |
> > > >         |   |            \                        |    |
> > > >         |   |             \                       |    |
> > > >         |   |              \                      |    |
> > > > one ASP |   | all ASP       \            one ASP  |    | 
> > Last ACTIVE
> > > > trans   |   | trans to       \           trans to |    | 
> > ASP trans to
> > > > to      |   | ASP-DOWN        -------\   ASP-     |    | 
> > ASP-INACTIVE
> > > > ASP-    |   |                         \  ACTIVE   |    | 
> > or ASP-DOWN
> > > > INACTIVE|   |                          \          |    |  
> > (start Tr)
> > > >         |   |                           \         |    |
> > > >         |   |                            \        |    |
> > > >         |   v                             \       |    v         
> > > >      +----------+                          \  +-------------+
> > > >      |          |                           --|           
> >   |      
> > > >      | AS-DOWN  |                             | AS-PENDING  |
> > > >      |          |                             |  (queueing) |
> > > >      |          |<----------------------------|             |
> > > >      +----------+    Tr Expiry and no ASP     +-------------+
> > > >                      in ASP-INACTIVE state)   
> > > > 
> > > >  Tr = Recovery Timer
> > > > 
> > > > 
> > > > 
> > > > For example, where the AS/ASP configuration data is not 
> > created until 
> > > > Registration of the first ASP, the AS-INACTIVE state is entered 
> > > > directly upon the first successful REG REQ from an ASP.  Another 
> > > > example is where the AS/ASP configuration data is not 
> > created until the first ASP successfully enters the 
> > ASP-ACTIVE state.  In this case the AS-ACTIVE state is 
> > entered directly.
> > > > 
> > > > 
> > > > --------- 
> > > > New text: (Section 4.3.2) 
> > > > ---------
> > > > 
> > > > AS-DOWN: The Application Server is unavailable.  This 
> > state implies that the number of ASPs being in ASP-INACTIVE 
> > or ASP-ACTIVE is less than "n". Initially the AS will be in 
> > this state. An Application Server is in the AS-DOWN state 
> > when it is removed from a configuration.
> > > > 
> > > > AS-INACTIVE: The Application Server is available but no 
> > application traffic is active. This implies that there are at 
> > least n ASPs in either ASP-INACTIVE or ASP-ACTIVE but the 
> > total number of ASPs in ASP-ACTIVE state has not reach n.  
> > The recovery timer T(r) is not running or has expired. 
> > > > 
> > > > AS-ACTIVE: The Application Server is available and 
> > application traffic is active. The AS moves to this state 
> > after being in AS-INACTIVE and getting n ASPs in ASP-ACTIVE 
> > state or, after reaching AS-ACTIVE and keeping one or more 
> > ASPs in ASP-ACTIVE state. 
> > > > 
> > > > AS-PENDING: The last active ASP has transitioned from 
> > ASP-ACTIVE to ASP-INACTIVE or ASP-DOWN.  A recovery timer 
> > T(r) SHOULD be started and all incoming signalling messages 
> > SHOULD be queued by the SGP. If an ASP becomes ASP-ACTIVE 
> > before T(r) expires, the AS is moved to the AS-ACTIVE state 
> > and all the queued messages will be sent to the ASP. 
> > > > 
> > > > If T(r) expires before an ASP becomes ASP-ACTIVE, the SGP 
> > MAY stops queuing messages and discards all 
> > > > previously queued messages. The AS will move to the 
> > AS-INACTIVE state 
> > > > if at least the number of ASPs in ASP-INACTIVE sum n, 
> > otherwise it will move to AS-DOWN state. 
> > > > 
> > > > Figure 5 shows an example AS state machine for the case where the 
> > > > AS/ASP data is preconfigured and an n+k redundancy model. 
> > > > 
> > > > 
> > > >              Figure 5: AS State Transition Diagram
> > > > 
> > > >                    
> > > >      +----------+          IA2AC              +-------------+
> > > >      |    AS-   |---------------------------->|     AS-     |
> > > >      | INACTIVE |                             |   ACTIVE    |
> > > >      |          |<-----------                 |             |
> > > >      +----------+            \                +-------------+
> > > >         ^   |                 \                    ^   |
> > > >         |   | IA2DN            \ PN2IA             |   | AC2PN
> > > >         |   |                   \                  |   | 
> > > >   DN2IA |   |                    \          PN2AC  |   | 
> > > >         |   v                     \                |   v
> > > >      +----------+                  \          +-------------+
> > > >      |          |                   ----------|             |
> > > >      | AS-DOWN  |                             | AS-PENDING  |
> > > >      |          |                  PN2DN      |  (queueing) |
> > > >      |          |<----------------------------|             |
> > > >      +----------+                             +-------------+
> > > > 
> > > > 
> > > > 
> > > > DN2IA: One ASP moves to ASP-INACTIVE causing that n ASPs 
> > are in either ASP-ACTIVE or ASP-INACTIVE states.
> > > > 
> > > > IA2DN: One ASP moves to ASP-DOWN causing that the number 
> > of ASPs in either ASP-ACTIVE or ASP-INACTIVE drops below n.
> > > > 
> > > > IA2AC: one ASP moves to ASP-ACTIVE, causing number of 
> > ASPs in the ASP-ACTIVE state to be n.
> > > > 
> > > > AC2PN: the last ASP in ASP-ACTIVE state moves to 
> > ASP-INACTIVE or ASP-DOWN states, causing the number of ASPs 
> > in ASP-ACTIVE drop below 1.
> > > > 
> > > > PN2AC: One ASP moves to ASP-ACTIVE.
> > > > 
> > > > PN2IA: T(r) Expiry, n or more ASPs are in ASP-INACTIVE.
> > > > 
> > > > PN2DN: T(r) Expiry, the number of ASPs in ASP-INACTIVE 
> > state is less than n.
> > > > 
> > > > As "n" ASPs are needed to handle the maximum engineered 
> > load of the AS, an AS becomes AS-ACTIVE right after n ASPs 
> > reach the ASP-ACTIVE state during the start-up phase. Once 
> > the traffic is flowing, an AS keeps the AS-ACTIVE state till 
> > the last ASP turns to another state different to ASP-ACTIVE, 
> > avoiding unnecessary traffic disturbances as long as there 
> > are ASPs available, in the assumption that the AS will not 
> > always be exposed to the maximum load. 
> > > > 
> > > > There are other cases where the AS/ASP configuration data 
> > is created dynamically. In those cases there would be 
> > differences in the state machine, especially at creation of 
> > the AS. For example, where the AS/ASP configuration data is 
> > not created until Registration of the first ASP, the 
> > AS-INACTIVE state is entered directly upon the nth successful 
> > REG REQ from an ASP belonging to that AS.  Another example is 
> > where the AS/ASP configuration data is not created until the 
> > nth ASP successfully enters the ASP-ACTIVE state.  In this 
> > latter case the AS-ACTIVE state is entered directly.
> > > > 
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > 
> > > -- 
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > > 
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > 
> > 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 
> 


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



From exim@www1.ietf.org  Wed Jun 18 07:23:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27142
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 07:23:31 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5IBN2j13974
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 07:23:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Sb1p-0003cx-HM; Wed, 18 Jun 2003 07:23:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Sb0v-0003bD-Nv
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 07:22:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27106
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 07:22:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sayg-0002BM-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 07:19:46 -0400
Received: from web12810.mail.yahoo.com ([216.136.174.137])
	by ietf-mx with smtp (Exim 4.12)
	id 19Sayf-0002BJ-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 07:19:45 -0400
Message-ID: <20030618112200.44728.qmail@web12810.mail.yahoo.com>
Received: from [208.255.120.2] by web12810.mail.yahoo.com via HTTP; Wed, 18 Jun 2003 04:22:00 PDT
Date: Wed, 18 Jun 2003 04:22:00 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: RE: [Sigtran] RE: M3UA IG: section 3.15 reworked
To: sigtran@ietf.org
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C64@eestqnt105.es.eu.ericsson.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Hi Javier,
--- "Javier Pastor-Balbas (ECE)"
<javier.pastor-balbas@ece.ericsson.se> wrote:
> 
> Hi Tolga, 
> 
> I think I understand your concern. If we want that
> both ASPs and SGPs have the same AS state view, one
> option is to configure T(r) in both machines with
> the same value. But even then there is a network
> delay that you may not control. In that case the
> ASPs will realize of their new state with the help
> of NTFY message.
[TOLGA]Maybe a few sentences about use of NTFY for
such cases can be added(?). Till now -and according to
RFC- it had only advisory meaning, now it is a bit
more than this.
> 
> Another different point is the transition PN2AC. It
> follows the philosophy of having the AS-ACTIVE state
> even when only one ASP is in ASP-ACTIVE state. It's
> a result of adapting the model to the
> max-engineered-load "n" view.
> 
> Cheers // Javier.
> 


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

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



From exim@www1.ietf.org  Wed Jun 18 09:20:49 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05476
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 09:20:48 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5IDKKD01112
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 09:20:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SciK-0008RK-QT; Wed, 18 Jun 2003 09:11:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ScUq-0007uc-5z
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 08:57:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02582
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 08:57:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ScSZ-0003WB-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 08:54:43 -0400
Received: from falcon.ericsson.se ([193.180.251.52] helo=falcon.al.sw.ericsson.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ScSY-0003Vt-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 08:54:42 -0400
Received: from esealnt612.al.sw.ericsson.se (alteon-nat1.sw.ericsson.se [153.88.254.118])
	by falcon.al.sw.ericsson.se (8.12.9/8.12.9/WIREfire-1.6b) with ESMTP id h5ICvpcv024631;
	Wed, 18 Jun 2003 14:57:51 +0200
Received: from ESEALNT745.al.sw.ericsson.se ([153.88.251.5]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id LYGLQ5C2; Wed, 18 Jun 2003 14:56:54 +0200
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <HT92BZ49>; Wed, 18 Jun 2003 14:56:01 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C68@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
To: "'Samuel Dur D. Jeyaseelan'" <sjeyasee@ssd.usa.alcatel.com>
Cc: "Brian F. G. Bidulock" <bidulock@openss7.org>,
        "'sigtran@ietf.org'"
	 <sigtran@ietf.org>
Subject: RE: [Sigtran] RE: M3UA IG: section 3.15 reworked
Date: Wed, 18 Jun 2003 14:56:41 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA05476

Hi Samuel, 

This is the consensus I was referring to. And it is what the new text try to state. 
As far as I've seen Brian also disagrees now with this consensus since he states that n is not mandatory at the start up....

The consensus you mention would imply changes in the two sections I referred to in my previous mail.

Cheers // Javier.

> -----Original Message-----
> From: Samuel Dur D. Jeyaseelan [mailto:sjeyasee@ssd.usa.alcatel.com]
> Sent: miércoles, 18 de junio de 2003 13:11
> To: Javier Pastor-Balbas (ECE)
> Cc: Brian F. G. Bidulock; 'sigtran@ietf.org'
> Subject: RE: [Sigtran] RE: M3UA IG: section 3.15 reworked
> 
> 
> This message uses a character set that is not supported by 
> the Internet Service.  To view the original message content,  
> open the attached message. If the text doesn't display 
> correctly, save the attachment to disk, and then open it 
> using a viewer that can display the original character set. 
> 

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



From exim@www1.ietf.org  Wed Jun 18 10:38:05 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10075
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 10:38:05 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5IEbch16618
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 10:37:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SdeQ-00035A-5r; Wed, 18 Jun 2003 10:11:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SdDv-0001Ot-65
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 09:43:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06705
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 09:43:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SdBe-0004kg-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 09:41:18 -0400
Received: from auds953.usa.alcatel.com ([143.209.238.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SdBd-0004ka-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 09:41:17 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h5IDh5LX002588
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 08:43:05 -0500 (CDT)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h5IDh01C022983
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 08:43:00 -0500 (CDT)
Date: Wed, 18 Jun 2003 08:43:00 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
In-Reply-To: <20030225031747.B13055@openss7.org>
Message-ID: <Pine.SOL.4.10.10306180837480.6574-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


Brian,

 Just going back to 25-Feb-2003 ....



On Tue, 25 Feb 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> Samuel Dur D. Jeyaseelan wrote:                                                     (Tue, 25 Feb 2003 03:56:07)
> > 
> > Brian,
> > 
> >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> > 
> > On Tue, 25 Feb 2003, Brian F. G. Bidulock wrote:
> > 
> > > TOLGA,
> > > 
> > > TOLGA ASVEREN wrote:                                                                 (Tue, 25 Feb 2003 08:39:11)
> > > > 
> > > > Not necessarily because I disagree with some change, but just to clarify
> > > > where the changes might take us:
> > > 
> > > If we cannot agree, we let the RFC stand.
> > > 
> > > > NTFY was used till now only as an advisory message, this will be changed.
> > > 
> > > No it will not.  An ASP is not forbidden from acting on any Notify message.
> > > All Notify messages are still advisory.  The ASP can take into consideration
> > > Notify messages, information that it has about other ASPs, the time of day,
> > > direction of the wind, etc.
> > > 
> > > > Starting/stopping(till now we focused more on starting but why not stopping
> > > > also? So SG can decide based on load/other dynamic conditions when to stop
> > > > traffic to/from AS) traffic will be controlled by SGP with NTFY.
> > > 
> > > The SG has always been permitted to start or stop traffic when it considers
> > > it necessary and has always been permitted to perform its necessary functions
> > > with the SS7 network.  The SGP can send ASPIA Ack or drop associations any
> > > time it wishes to stop traffic.
> > 
> > Please let me know what are we achieving by stopping the traffic in the
> > following case(n+k - reduntancy)
> > 
> > When 'n' ASPs are active
> > ------------------------
> > SLS-X  ---->ASP1
> > SLS-Y  ---->ASP2
> > 
> > When ASP1 goes down
> > -------------------
> > SLS-(Y,X)  ----->ASP2
> > 
> > Here 3 cases can be dealt
> > 
> > case 1) If SG receives  message with SLS Y - this traffic can be
> >         successfully (100%) handled by ASP2 according to the configured
> >         databse.
> >  
> > case 2) If SG receives messages with SLS X and Y - this traffic can be
> >         successfully (100%) handled by ASP2, provided congestion has not
> >         occured(according to q.704 section 3.8.2)
> > 
> > case 3) Don't allow SG to process the traffic when n<2 ?????????.
> >         SG disallows traffic when n=0.
> > 
> > IMO, SG has capability to reroute the traffic to ASP1 and there is no
> > meaning if SG stops traffic when n < 2.
> > 
> > This is just like a MTP3 link failure concept when link1 goes down ,
> > traffic carried by link1 will be rerouted to available link. 
> > All we need to do at SG is just change the SLS-ASP dynamic table to carry
> > SLS X.
> > 
> > 
> > --Samuel
> 
> I agree.   That is what is provided for in the RFC.  However, section 3.15 of
> the IG would require the SG to stop traffic when n < 2.  So, it must be
> struck.
> 
> --brian
[Samuel] Does new IG stop the traffic when n < 2 ?

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


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



From exim@www1.ietf.org  Wed Jun 18 10:41:20 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10172
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 10:41:20 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5IEerf17953
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 10:40:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SdeS-00035s-8E; Wed, 18 Jun 2003 10:11:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SdHs-0001YS-AR
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 09:47:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06856
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 09:47:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SdFb-0004mr-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 09:45:23 -0400
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SdFa-0004mS-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 09:45:22 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h5IDl6wC017745;
	Wed, 18 Jun 2003 08:47:08 -0500 (CDT)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h5IDl11C024215;
	Wed, 18 Jun 2003 08:47:01 -0500 (CDT)
Date: Wed, 18 Jun 2003 08:47:01 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
cc: "Brian F. G. Bidulock" <bidulock@openss7.org>,
        "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: RE: [Sigtran] RE: M3UA IG: section 3.15 reworked
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C68@eestqnt105.es.eu.ericsson.se>
Message-ID: <Pine.SOL.4.10.10306180844470.6574-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by ietf.org id KAA10172


Javier,
 Sorry for the confusion created.I would agree with you to include
 "section 3.15 reworked".

--Samuel 

  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******

On Wed, 18 Jun 2003, Javier Pastor-Balbas (ECE) wrote:

> Hi Samuel, 
> 
> This is the consensus I was referring to. And it is what the new text try to state. 
> As far as I've seen Brian also disagrees now with this consensus since he states that n is not mandatory at the start up....
> 
> The consensus you mention would imply changes in the two sections I referred to in my previous mail.
> 
> Cheers // Javier.
> 
> > -----Original Message-----
> > From: Samuel Dur D. Jeyaseelan [mailto:sjeyasee@ssd.usa.alcatel.com]
> > Sent: miércoles, 18 de junio de 2003 13:11
> > To: Javier Pastor-Balbas (ECE)
> > Cc: Brian F. G. Bidulock; 'sigtran@ietf.org'
> > Subject: RE: [Sigtran] RE: M3UA IG: section 3.15 reworked
> > 
> > 
> > This message uses a character set that is not supported by 
> > the Internet Service.  To view the original message content,  
> > open the attached message. If the text doesn't display 
> > correctly, save the attachment to disk, and then open it 
> > using a viewer that can display the original character set. 
> > 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 
> 


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



From exim@www1.ietf.org  Wed Jun 18 11:24:20 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12374
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 11:24:20 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5IFNqZ26808
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 11:23:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Se3a-00047H-21; Wed, 18 Jun 2003 10:37:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Sddk-0002ze-J3
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 10:10:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08608
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 10:10:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SdbT-00054V-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 10:07:59 -0400
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49] helo=albatross.tn.sw.ericsson.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SdbS-00054S-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 10:07:58 -0400
Received: from esealnt610.al.sw.ericsson.se (alteon-nat3.sw.ericsson.se [153.88.254.120])
	by albatross.tn.sw.ericsson.se (8.12.9/8.12.9/WIREfire-1.6b) with ESMTP id h5IEABG5018392;
	Wed, 18 Jun 2003 16:10:12 +0200 (MEST)
Received: from ESEALNT745.al.sw.ericsson.se ([153.88.251.5]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id LYG2NA1H; Wed, 18 Jun 2003 16:12:04 +0200
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <HT92B5ZJ>; Wed, 18 Jun 2003 16:09:14 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C6A@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>,
        "Ken Morneault (E-mail)"
	 <kmorneau@cisco.com>,
        =?iso-8859-1?Q?Antonio_Ca=F1ete_=28ECE=29?=
	 <antonio.canete-martinez@ece.ericsson.se>
Subject: RE: [Sigtran] RE: M3UA IG: section 3.15 reworked
Date: Wed, 18 Jun 2003 16:09:52 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA12374

Brian, 

Using n=1 it will work as you desire...

Cheers // Javier.

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: miércoles, 18 de junio de 2003 12:38
> To: Javier Pastor-Balbas (ECE)
> Cc: 'sigtran@ietf.org'; Ken Morneault (E-mail); Antonio Cañete (ECE)
> Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
> 
> 
> Javier,
> 
> Please see comments below...
> 
> Javier Pastor-Balbas (ECE) wrote:                             
>                       (Tue, 17 Jun 2003 16:51:16)
> > --------- 
> > New text: (Section 4.3.2) 
> > ---------
> > 
> > AS-DOWN: The Application Server is unavailable.  This state 
> implies that the
> > number of ASPs being in ASP-INACTIVE or ASP-ACTIVE is less than "n".
> > Initially the AS will be in this state. An Application 
> Server is in the
> > AS-DOWN state when it is removed from a configuration.
> > 
> > AS-INACTIVE: The Application Server is available but no 
> application traffic
> > is active. This implies that there are at least n ASPs in either
> > ASP-INACTIVE or ASP-ACTIVE but the total number of ASPs in 
> ASP-ACTIVE state
> > has not reach n.  The recovery timer T(r) is not running or 
> has expired. 
> > 
> > AS-ACTIVE: The Application Server is available and 
> application traffic is
> > active. The AS moves to this state after being in 
> AS-INACTIVE and getting n
> > ASPs in ASP-ACTIVE state or, after reaching AS-ACTIVE and 
> keeping one or
> > more ASPs in ASP-ACTIVE state. 
> 
> I strongly disagree with the above.  The SG can move to the 
> AS-ACTIVE state
> with one ASP in the ASP-ACTIVE state: it need not wait until 
> 'n'.  You are
> still interpreting 'n' as some sort of absolute minimum 
> number of ASPs,
> when it was agreed that 'n' is the number of ASPs required to 
> handle the
> maximum engineered load.  As such, there is no reason why the 
> SG cannot
> place the AS AS-ACTIVE when one ASP is in the ASP-ACTIVE 
> state for the AS.
> 
> The Old text is correct.  The above is incorrect.
> 
> > 
> > AS-PENDING: The last active ASP has transitioned from ASP-ACTIVE to
> > ASP-INACTIVE or ASP-DOWN.  A recovery timer T(r) SHOULD be 
> started and all
> > incoming signalling messages SHOULD be queued by the SGP. 
> If an ASP becomes
> > ASP-ACTIVE before T(r) expires, the AS is moved to the 
> AS-ACTIVE state and
> > all the queued messages will be sent to the ASP. 
> > 
> > If T(r) expires before an ASP becomes ASP-ACTIVE, the SGP 
> MAY stops queuing
> > messages and discards all previously queued messages. The 
> AS will move to
> > the AS-INACTIVE state if at least the number of ASPs in 
> ASP-INACTIVE sum n,
> > otherwise it will move to AS-DOWN state. 
> > 
> > Figure 5 shows an example AS state machine for the case where the 
> > AS/ASP data is preconfigured and an n+k redundancy model. 
> > 
> > 
> >              Figure 5: AS State Transition Diagram
> > 
> >                    
> >      +----------+          IA2AC              +-------------+
> >      |    AS-   |---------------------------->|     AS-     |
> >      | INACTIVE |                             |   ACTIVE    |
> >      |          |<-----------                 |             |
> >      +----------+            \                +-------------+
> >         ^   |                 \                    ^   |
> >         |   | IA2DN            \ PN2IA             |   | AC2PN
> >         |   |                   \                  |   | 
> >   DN2IA |   |                    \          PN2AC  |   | 
> >         |   v                     \                |   v
> >      +----------+                  \          +-------------+
> >      |          |                   ----------|             |
> >      | AS-DOWN  |                             | AS-PENDING  |
> >      |          |                  PN2DN      |  (queueing) |
> >      |          |<----------------------------|             |
> >      +----------+                             +-------------+
> > 
> > 
> > 
> > DN2IA: One ASP moves to ASP-INACTIVE causing that n ASPs 
> are in either
> > ASP-ACTIVE or ASP-INACTIVE states.
> > 
> > IA2DN: One ASP moves to ASP-DOWN causing that the number of 
> ASPs in either
> > ASP-ACTIVE or ASP-INACTIVE drops below n.
> 
> Wrong, as per above.  If one ASP is in the ASP-ACTIVE state 
> for the AS,
> the AS is AS-ACTIVE.
> 
> > 
> > IA2AC: one ASP moves to ASP-ACTIVE, causing number of ASPs 
> in the ASP-ACTIVE
> > state to be n.
> 
> Wrong, as per above.  If one ASP moves to the ASP-ACTIVE 
> state for the AS,
> the AS is AS-ACTIVE.
> 
> > 
> > AC2PN: the last ASP in ASP-ACTIVE state moves to 
> ASP-INACTIVE or ASP-DOWN
> > states, causing the number of ASPs in ASP-ACTIVE drop below 1.
> > 
> > PN2AC: One ASP moves to ASP-ACTIVE.
> > 
> > PN2IA: T(r) Expiry, n or more ASPs are in ASP-INACTIVE.
> > 
> > PN2DN: T(r) Expiry, the number of ASPs in ASP-INACTIVE 
> state is less than n.
> > 
> > As "n" ASPs are needed to handle the maximum engineered 
> load of the AS, an
> > AS becomes AS-ACTIVE right after n ASPs reach the 
> ASP-ACTIVE state during
> > the start-up phase.
> 
> The above is incorrect per concensus.  For the start-up 
> decision, the SG
> can choose to either wait for 'n' or start traffic on the 
> first active ASP.
> What it MUST do not send NTFY(AS-ACTIVE) until it considers 
> the AS in the
> AS-ACTIVE state.
> 
> > Once the traffic is flowing, an AS keeps the AS-ACTIVE
> > state till the last ASP turns to another state different to 
> ASP-ACTIVE,
> > avoiding unnecessary traffic disturbances as long as there are ASPs
> > available, in the assumption that the AS will not always be 
> exposed to the
> > maximum load. 
> 
> It won't necessarily be exposed to maximum load on startup either.
> 
> Text below covers things internal to the SG only, and is unnecessary:
> 
> > 
> > There are other cases where the AS/ASP configuration data is created
> > dynamically. In those cases there would be differences in 
> the state machine,
> > especially at creation of the AS. For example, where the AS/ASP
> > configuration data is not created until Registration of the 
> first ASP, the
> > AS-INACTIVE state is entered directly upon the nth 
> successful REG REQ from
> > an ASP belonging to that AS.  Another example is where the AS/ASP
> > configuration data is not created until the nth ASP 
> successfully enters the
> > ASP-ACTIVE state.  In this latter case the AS-ACTIVE state 
> is entered
> > directly.
> 
> Stick with the old text.
> 
> --brian
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 

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



From exim@www1.ietf.org  Wed Jun 18 13:12:18 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16685
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 13:12:18 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5IHBp913386
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 13:11:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SfgC-0001NR-PK; Wed, 18 Jun 2003 12:21:00 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5FFO4m06128
	for <sigtran@optimus.ietf.org>; Sun, 15 Jun 2003 11:24:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04444
	for <sigtran@ietf.org>; Sun, 15 Jun 2003 11:24:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RZKI-00042u-00
	for sigtran@ietf.org; Sun, 15 Jun 2003 11:21:50 -0400
Received: from bay0-smtp08.bay0.hotmail.com ([65.54.241.115] helo=BAY0-SMTP08.adinternal.hotmail.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19RZKH-00042l-00
	for sigtran@ietf.org; Sun, 15 Jun 2003 11:21:49 -0400
X-Originating-IP: [163.179.141.52]
X-Originating-Email: [leobloom1@msn.com]
Received: from hppav ([163.179.141.52]) by BAY0-SMTP08.adinternal.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600);
	 Sun, 15 Jun 2003 08:23:30 -0700
Message-ID: <003901c33352$58f08b40$348db3a3@hppav>
From: "LeoBloom1" <LeoBloom1@msn.com>
To: <sigtran@ietf.org>
Date: Sun, 15 Jun 2003 10:25:24 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0036_01C33328.6E99FDC0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-OriginalArrivalTime: 15 Jun 2003 15:23:30.0907 (UTC) FILETIME=[13CD6AB0:01C33352]
Subject: [Sigtran] M3UA: Question about ITU Point Code Format
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0036_01C33328.6E99FDC0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello,

I have a question about the Point Code representation for ITU in M3UA.=20
I've looked through the mailing list threads and have not seen a =
reference so I wanted to pose the question - though I suspect it may be =
a simple one, I cannot quite get clarity from RFC 3332/IG based on my =
analysis:

In the Affected Point Code, etc., parameters in M3UA messages, do the =
six bits in the Most Significant Byte of the ITU Point Code correspond =
to the same six bits in the Most Significant Byte of the M3UA Point =
Code, and the eight bits in the Least Significant Byte correspond to the =
Least Significant Byte in M3UA?

If we have the ITU Point Code 7-255-7 represented in hex (order of =
transmission is displayed left to right) it will appear as FF 3F since =
the Least Significant Byte is transmitted first (reference section =
3.4.2.1 of ITU-T Q.713).  {The binary representation is 11111111 =
00111111.}

-In M3UA the Most Significant Byte is transmitted first so would the =
Point Code example above (7-255-7) appear as 3F FF if represented as =
hex? {The binary representation might be 00111111 11111111.}

Thanks in advance for any feedback.
Regards,
Charles Hastings

------=_NextPart_000_0036_01C33328.6E99FDC0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hello,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I have a question about the Point Code=20
representation for ITU in M3UA. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I've looked through the mailing list =
threads and=20
have not seen a reference so I wanted to pose the question - though I =
suspect it=20
may be a simple one, I cannot quite get clarity from RFC 3332/IG based =
on my=20
analysis:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#3333ff>In the Affected Point Code, etc., parameters =
in M3UA=20
messages, do the six bits in the Most Significant Byte of the ITU Point =
Code=20
correspond to the same six bits in the Most Significant Byte of the M3UA =
Point=20
Code, and the eight bits in the Least Significant Byte correspond to the =
Least=20
Significant Byte in M3UA?<BR><BR>If we have the ITU Point Code 7-255-7=20
represented in hex (order of transmission is displayed left to right) it =
will=20
appear as FF 3F since the Least Significant Byte is transmitted first =
(reference=20
section 3.4.2.1 of ITU-T Q.713). &nbsp;{The binary representation is =
11111111=20
00111111.}<BR></FONT></DIV>
<DIV><FONT color=3D#3333ff>-In M3UA the Most Significant Byte is =
transmitted first=20
so would the Point Code example above (7-255-7)&nbsp;appear as 3F FF if=20
represented as hex? {The binary representation might be 00111111=20
11111111.}</FONT></DIV>
<DIV><FONT color=3D#3333ff></FONT>&nbsp;</DIV>
<DIV>Thanks in advance for any feedback.</DIV>
<DIV>Regards,</DIV>
<DIV>Charles Hastings</DIV>
<DIV><FONT color=3D#3333ff></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0036_01C33328.6E99FDC0--

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



From exim@www1.ietf.org  Wed Jun 18 14:55:58 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21498
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 14:55:58 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5IItVc32574
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 14:55:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Shsf-0007v7-Is; Wed, 18 Jun 2003 14:42:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ShMv-0006NN-AI
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 14:09:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19091
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 14:09:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShKd-0007VV-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 14:06:51 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[TBf0gHe1aUS7Js3qcrZZ5caGhalmP37h])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShKc-0007VS-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 14:06:51 -0400
Received: from ns.pigworks.openss7.net (IDENT:PR4le1tviBZnzn0XDZ/XnBGZGpOLV7XV@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5II97X27476;
	Wed, 18 Jun 2003 12:09:07 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5II96K31465;
	Wed, 18 Jun 2003 12:09:06 -0600
Date: Wed, 18 Jun 2003 12:09:06 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
Message-ID: <20030618120906.A31402@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030618042639.A24847@openss7.org> <20030618105827.77289.qmail@web12806.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030618105827.77289.qmail@web12806.mail.yahoo.com>; from tolga_asveren@yahoo.com on Wed, Jun 18, 2003 at 03:58:27AM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

Tolga Asveren wrote:                                                                 (Wed, 18 Jun 2003 03:58:27)
> Please see comments below....
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Javier,
> > 
> > Javier Pastor-Balbas (ECE) wrote:                   
> >                                (Wed, 18 Jun 2003
> > 11:47:02)
> > > 
> > > Samuel and Brian, 
> > > 
> > > As the archives say, the agreements were:
> > > - Move from AS-INACTIVE to AS-ACTIVE after n ASPs
> > get the ASP-ACTIVE state.
> > > - Stay in AS-ACTIVE even though the number of ASPs
> > that are in ASP-ACTIVE state is below n.
> > > 
> > > Apart from that I've not seen any consensus on
> > removing it. Although I can
> > > find several mails from Brian saying "strike
> > section 3.15"... But I may be
> > > wrong. In that case I would appreciate you point
> > me to the exact item where
> > > this consensus were made.
> > 
> > Everyone agreed except for Tolga.
> [TOLGA]It is clear that an AS, which is not ACTIVE,
> SHOULD NOT send/receive application traffic. The only
> way to achieve this is to harmonize state change of AS
> on ASPs/SGPs. RFC fails to address this for n>1
> because it is written always as n=1 in mind. IG
> corrects this. 

I disagree, the wording "at least one" has 'n' in mind.

It's just not the 'n' you wanted.


--brian


> 
> 
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Wed Jun 18 14:59:11 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21815
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 14:59:11 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5IIwho00963
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 14:58:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Shsg-0007vV-Ss; Wed, 18 Jun 2003 14:42:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ShPl-0006W7-I9
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 14:12:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19169
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 14:12:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShNU-0007Wl-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 14:09:48 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[hILlo5aSNIWzAPANTZG4yefFITyOgIZs])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShNS-0007Wi-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 14:09:47 -0400
Received: from ns.pigworks.openss7.net (IDENT:KLGLJbBmj+Rmy5OCe4OOuOdeNBArsEpM@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5IIC4X27520;
	Wed, 18 Jun 2003 12:12:04 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5IIC3O31531;
	Wed, 18 Jun 2003 12:12:03 -0600
Date: Wed, 18 Jun 2003 12:12:03 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>,
        "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
Message-ID: <20030618121203.B31402@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	"Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>
References: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C63@eestqnt105.es.eu.ericsson.se> <Pine.SOL.4.10.10306180554570.6574-100000@sun2594.ssd.usa.alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.4.10.10306180554570.6574-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Wed, Jun 18, 2003 at 06:10:45AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id h5IIC4X27520
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA21815

Samuel,

Samuel Dur D. Jeyaseelan wrote:                                                     (Wed, 18 Jun 2003 06:10:45)
> 
> Pastor,
>  
>  I could not exactly locate the email referring to remove section
> 3.15 from IG.But following things i could recollect
> 
> 1. 'n' is mantatory at start case

'n' is not mandatory in the start case.  The ASPs must coordinate 'n'
amoungst themselves.  The SGP can start traffic when the first ASP starts
or wait until 'n', however, it withholds NTFT(AS-ACTIVE) until 'n' in
that case.  This is what the RFC already says.  There is no problem with
it.  Can you see any problem?  (Tolga could not point to one.)

--brian


> 2. 'n' is # of ASPs to handle the maximum engineered load
> 3. When # of ASPs < n (where n > 0),AS state will be still AS-ACTIV
>    but SGP will direct all traffic to the ACTIVE ASP(this is not a
>    start case).All that SGP needs
>    is change in the following internal table
> 
>    When Both ASPs-ACTIVE
>    ---------------------
>    ASP1 -- SLS1
>    ASP2 -- SLS2
> 
> 
>    When ASP1 goes DOWN
>    -------------------
>    ASP2 -- SLS1 + SLS2
> 
>    
> --Samuel
> 
>   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> 
> On Wed, 18 Jun 2003, Javier Pastor-Balbas (ECE) wrote:
> 
> > 
> > Samuel and Brian, 
> > 
> > As the archives say, the agreements were:
> > - Move from AS-INACTIVE to AS-ACTIVE after n ASPs get the ASP-ACTIVE state.
> > - Stay in AS-ACTIVE even though the number of ASPs that are in ASP-ACTIVE state is below n.
> > 
> > Apart from that I've not seen any consensus on removing it. Although I can find several mails from Brian saying "strike section 3.15"... But I may be wrong. In that case I would appreciate you point me to the exact item where this consensus were made.
> > 
> > Inside the current RFC there are clear divergences: While section 1.4.4.1 says that "n" is the minimum number of redundant ASPs to handle traffic, section 4.3.2 says that an AS can handle traffic with only one ASP in ASP-ACTIVE. These two views MUST be aligned...
> > 
> > 
> > Since the relation between n+k and the AS states is not included in the RFC, I would recommend to maintain this text (with the final agreement). 
> > 
> > 
> > Cheers // Javier.
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: Samuel Dur D. Jeyaseelan [mailto:sjeyasee@ssd.usa.alcatel.com]
> > > Sent: miércoles, 18 de junio de 2003 6:44
> > > To: Brian F. G. Bidulock
> > > Cc: Javier Pastor-Balbas (ECE); 'sigtran@ietf.org'; Ken Morneault
> > > (E-mail); Antonio Cañete (ECE)
> > > Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
> > > 
> > > 
> > > 
> > > Pastor,
> > > 
> > >  I too believe that concensus was made to delete section 3.15 from IG 
> > >  as RFC is sufficient to explain n+k case.
> > > 
> > > --Samuel
> > > 
> > >   Alcatel USA, Inc.                  Internet: 
> > > <userid>@ssd.usa.alcatel.com
> > >   1000 Coit Road, Plano, Texas 75075
> > >   ******* The opinions expressed are not those of Alcatel 
> > > USA, Inc. *******
> > > 
> > > On Tue, 17 Jun 2003, Brian F. G. Bidulock wrote:
> > > 
> > > > Javier,
> > > > 
> > > > I believe the concensus from the last long discussions was to
> > > > remove section 3.15.
> > > > 
> > > > --brian
> > > > 
> > > > Javier Pastor-Balbas (ECE) wrote:                           
> > >                         (Tue, 17 Jun 2003 16:51:16)
> > > > > This is the last version. There were still some 
> > > unfinished sentences and inconsistences in the first text I 
> > > sent. Now, they are fixed.
> > > > > 
> > > > > Cheers // Javier.
> > > > > 
> > > > > 
> > > > > --------- 
> > > > > Old text: (Section 4.3.2) 
> > > > > ---------
> > > > > 
> > > > > AS-DOWN: The Application Server is unavailable.  This 
> > > state implies 
> > > > > that all related ASPs are in the ASP-DOWN state for this 
> > > AS. Initially the AS will be in this state. An Application 
> > > Server is in the AS-DOWN state when it is removed from a 
> > > configuration.
> > > > > 
> > > > > AS-INACTIVE: The Application Server is available but no 
> > > application 
> > > > > traffic is active (i.e., one or more related ASPs are in the ASP-
> > > > > INACTIVE state, but none in the ASP-ACTIVE state).  The recovery 
> > > > > timer T(r) is not running or has expired. 
> > > > > 
> > > > > AS-ACTIVE: The Application Server is available and 
> > > application traffic is active.  This state implies that at 
> > > least one ASP is in the ASP-ACTIVE state.
> > > > > 
> > > > > AS-PENDING: An active ASP has transitioned to 
> > > ASP-INACTIVE or ASP-DOWN  and it was the last remaining 
> > > active ASP in the AS.  A recovery timer T(r) SHOULD be 
> > > started and all incoming signalling messages SHOULD be queued 
> > > by the SGP. If an ASP becomes ASP-ACTIVE before T(r) expires, 
> > > the AS is moved to the AS-ACTIVE state and all the queued 
> > > messages will be sent to the ASP. 
> > > > > 
> > > > > If T(r) expires before an ASP becomes ASP-ACTIVE, and the 
> > > SGP has no 
> > > > > alternative, the SGP may stops queuing messages and discards all 
> > > > > previously queued messages. The AS will move to the 
> > > AS-INACTIVE state 
> > > > > if at least one ASP is in ASP-INACTIVE state, otherwise 
> > > it will move 
> > > > > to AS-DOWN state. 
> > > > > 
> > > > > Figure 5 shows an example AS state machine for the case where the 
> > > > > AS/ASP data is preconfigured.  For other cases where the AS/ASP 
> > > > > configuration data is created dynamically, there would be 
> > > differences 
> > > > > in the state machine, especially at creation of the AS.  
> > > > > 
> > > > >                  Figure 5: AS State Transition Diagram
> > > > > 
> > > > >      +----------+   one ASP trans to ACTIVE   +-------------+
> > > > >      |    AS-   |---------------------------->|     AS-   
> > >   |      
> > > > >      | INACTIVE |                             |   ACTIVE    |
> > > > >      |          |<---                         |             |
> > > > >      +----------+    \                        +-------------+
> > > > >         ^   |         \ Tr Expiry,                ^    |
> > > > >         |   |          \ at least one             |    |
> > > > >         |   |           \ ASP in ASP-INACTIVE     |    |
> > > > >         |   |            \                        |    |
> > > > >         |   |             \                       |    |
> > > > >         |   |              \                      |    |
> > > > > one ASP |   | all ASP       \            one ASP  |    | 
> > > Last ACTIVE
> > > > > trans   |   | trans to       \           trans to |    | 
> > > ASP trans to
> > > > > to      |   | ASP-DOWN        -------\   ASP-     |    | 
> > > ASP-INACTIVE
> > > > > ASP-    |   |                         \  ACTIVE   |    | 
> > > or ASP-DOWN
> > > > > INACTIVE|   |                          \          |    |  
> > > (start Tr)
> > > > >         |   |                           \         |    |
> > > > >         |   |                            \        |    |
> > > > >         |   v                             \       |    v         
> > > > >      +----------+                          \  +-------------+
> > > > >      |          |                           --|           
> > >   |      
> > > > >      | AS-DOWN  |                             | AS-PENDING  |
> > > > >      |          |                             |  (queueing) |
> > > > >      |          |<----------------------------|             |
> > > > >      +----------+    Tr Expiry and no ASP     +-------------+
> > > > >                      in ASP-INACTIVE state)   
> > > > > 
> > > > >  Tr = Recovery Timer
> > > > > 
> > > > > 
> > > > > 
> > > > > For example, where the AS/ASP configuration data is not 
> > > created until 
> > > > > Registration of the first ASP, the AS-INACTIVE state is entered 
> > > > > directly upon the first successful REG REQ from an ASP.  Another 
> > > > > example is where the AS/ASP configuration data is not 
> > > created until the first ASP successfully enters the 
> > > ASP-ACTIVE state.  In this case the AS-ACTIVE state is 
> > > entered directly.
> > > > > 
> > > > > 
> > > > > --------- 
> > > > > New text: (Section 4.3.2) 
> > > > > ---------
> > > > > 
> > > > > AS-DOWN: The Application Server is unavailable.  This 
> > > state implies that the number of ASPs being in ASP-INACTIVE 
> > > or ASP-ACTIVE is less than "n". Initially the AS will be in 
> > > this state. An Application Server is in the AS-DOWN state 
> > > when it is removed from a configuration.
> > > > > 
> > > > > AS-INACTIVE: The Application Server is available but no 
> > > application traffic is active. This implies that there are at 
> > > least n ASPs in either ASP-INACTIVE or ASP-ACTIVE but the 
> > > total number of ASPs in ASP-ACTIVE state has not reach n.  
> > > The recovery timer T(r) is not running or has expired. 
> > > > > 
> > > > > AS-ACTIVE: The Application Server is available and 
> > > application traffic is active. The AS moves to this state 
> > > after being in AS-INACTIVE and getting n ASPs in ASP-ACTIVE 
> > > state or, after reaching AS-ACTIVE and keeping one or more 
> > > ASPs in ASP-ACTIVE state. 
> > > > > 
> > > > > AS-PENDING: The last active ASP has transitioned from 
> > > ASP-ACTIVE to ASP-INACTIVE or ASP-DOWN.  A recovery timer 
> > > T(r) SHOULD be started and all incoming signalling messages 
> > > SHOULD be queued by the SGP. If an ASP becomes ASP-ACTIVE 
> > > before T(r) expires, the AS is moved to the AS-ACTIVE state 
> > > and all the queued messages will be sent to the ASP. 
> > > > > 
> > > > > If T(r) expires before an ASP becomes ASP-ACTIVE, the SGP 
> > > MAY stops queuing messages and discards all 
> > > > > previously queued messages. The AS will move to the 
> > > AS-INACTIVE state 
> > > > > if at least the number of ASPs in ASP-INACTIVE sum n, 
> > > otherwise it will move to AS-DOWN state. 
> > > > > 
> > > > > Figure 5 shows an example AS state machine for the case where the 
> > > > > AS/ASP data is preconfigured and an n+k redundancy model. 
> > > > > 
> > > > > 
> > > > >              Figure 5: AS State Transition Diagram
> > > > > 
> > > > >                    
> > > > >      +----------+          IA2AC              +-------------+
> > > > >      |    AS-   |---------------------------->|     AS-     |
> > > > >      | INACTIVE |                             |   ACTIVE    |
> > > > >      |          |<-----------                 |             |
> > > > >      +----------+            \                +-------------+
> > > > >         ^   |                 \                    ^   |
> > > > >         |   | IA2DN            \ PN2IA             |   | AC2PN
> > > > >         |   |                   \                  |   | 
> > > > >   DN2IA |   |                    \          PN2AC  |   | 
> > > > >         |   v                     \                |   v
> > > > >      +----------+                  \          +-------------+
> > > > >      |          |                   ----------|             |
> > > > >      | AS-DOWN  |                             | AS-PENDING  |
> > > > >      |          |                  PN2DN      |  (queueing) |
> > > > >      |          |<----------------------------|             |
> > > > >      +----------+                             +-------------+
> > > > > 
> > > > > 
> > > > > 
> > > > > DN2IA: One ASP moves to ASP-INACTIVE causing that n ASPs 
> > > are in either ASP-ACTIVE or ASP-INACTIVE states.
> > > > > 
> > > > > IA2DN: One ASP moves to ASP-DOWN causing that the number 
> > > of ASPs in either ASP-ACTIVE or ASP-INACTIVE drops below n.
> > > > > 
> > > > > IA2AC: one ASP moves to ASP-ACTIVE, causing number of 
> > > ASPs in the ASP-ACTIVE state to be n.
> > > > > 
> > > > > AC2PN: the last ASP in ASP-ACTIVE state moves to 
> > > ASP-INACTIVE or ASP-DOWN states, causing the number of ASPs 
> > > in ASP-ACTIVE drop below 1.
> > > > > 
> > > > > PN2AC: One ASP moves to ASP-ACTIVE.
> > > > > 
> > > > > PN2IA: T(r) Expiry, n or more ASPs are in ASP-INACTIVE.
> > > > > 
> > > > > PN2DN: T(r) Expiry, the number of ASPs in ASP-INACTIVE 
> > > state is less than n.
> > > > > 
> > > > > As "n" ASPs are needed to handle the maximum engineered 
> > > load of the AS, an AS becomes AS-ACTIVE right after n ASPs 
> > > reach the ASP-ACTIVE state during the start-up phase. Once 
> > > the traffic is flowing, an AS keeps the AS-ACTIVE state till 
> > > the last ASP turns to another state different to ASP-ACTIVE, 
> > > avoiding unnecessary traffic disturbances as long as there 
> > > are ASPs available, in the assumption that the AS will not 
> > > always be exposed to the maximum load. 
> > > > > 
> > > > > There are other cases where the AS/ASP configuration data 
> > > is created dynamically. In those cases there would be 
> > > differences in the state machine, especially at creation of 
> > > the AS. For example, where the AS/ASP configuration data is 
> > > not created until Registration of the first ASP, the 
> > > AS-INACTIVE state is entered directly upon the nth successful 
> > > REG REQ from an ASP belonging to that AS.  Another example is 
> > > where the AS/ASP configuration data is not created until the 
> > > nth ASP successfully enters the ASP-ACTIVE state.  In this 
> > > latter case the AS-ACTIVE state is entered directly.
> > > > > 
> > > > > _______________________________________________
> > > > > Sigtran mailing list
> > > > > Sigtran@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > 
> > > > -- 
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > > 
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > 
> > > 
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> > 

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

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



From exim@www1.ietf.org  Wed Jun 18 15:01:10 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21977
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 15:01:10 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5IJ0ho01355
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 15:00:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Shsi-0007vz-LU; Wed, 18 Jun 2003 14:42:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ShRN-0006aR-CC
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 14:13:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19217
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 14:13:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShP6-0007Xs-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 14:11:28 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[b275yxXlTHQ4f0/pobxaZDlkNKgaubOw])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShP5-0007Xp-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 14:11:27 -0400
Received: from ns.pigworks.openss7.net (IDENT:6vdPZyaNKLBuUVty3hjOkNM1b2fles98@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5IIDbX27531;
	Wed, 18 Jun 2003 12:13:37 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5IIDat31538;
	Wed, 18 Jun 2003 12:13:36 -0600
Date: Wed, 18 Jun 2003 12:13:36 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>,
        "Ken Morneault (E-mail)" <kmorneau@cisco.com>,
        =?iso-8859-1?Q?Antonio_Ca=F1ete_=28ECE=29?= <antonio.canete-martinez@ece.ericsson.se>
Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
Message-ID: <20030618121336.C31402@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>,
	"Ken Morneault (E-mail)" <kmorneau@cisco.com>,
	=?iso-8859-1?Q?Antonio_Ca=F1ete_=28ECE=29?= <antonio.canete-martinez@ece.ericsson.se>
References: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C6A@eestqnt105.es.eu.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C6A@eestqnt105.es.eu.ericsson.se>; from javier.pastor-balbas@ece.ericsson.se on Wed, Jun 18, 2003 at 04:09:52PM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id h5IIDbX27531
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA21977

Javier,

Don't be absurd.  n<>1 is the case we speak of.

--brian

Javier Pastor-Balbas (ECE) wrote:                                                   (Wed, 18 Jun 2003 16:09:52)
> Brian, 
> 
> Using n=1 it will work as you desire...
> 
> Cheers // Javier.
> 
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: miércoles, 18 de junio de 2003 12:38
> > To: Javier Pastor-Balbas (ECE)
> > Cc: 'sigtran@ietf.org'; Ken Morneault (E-mail); Antonio Cañete (ECE)
> > Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
> > 
> > 
> > Javier,
> > 
> > Please see comments below...
> > 
> > Javier Pastor-Balbas (ECE) wrote:                             
> >                       (Tue, 17 Jun 2003 16:51:16)
> > > --------- 
> > > New text: (Section 4.3.2) 
> > > ---------
> > > 
> > > AS-DOWN: The Application Server is unavailable.  This state 
> > implies that the
> > > number of ASPs being in ASP-INACTIVE or ASP-ACTIVE is less than "n".
> > > Initially the AS will be in this state. An Application 
> > Server is in the
> > > AS-DOWN state when it is removed from a configuration.
> > > 
> > > AS-INACTIVE: The Application Server is available but no 
> > application traffic
> > > is active. This implies that there are at least n ASPs in either
> > > ASP-INACTIVE or ASP-ACTIVE but the total number of ASPs in 
> > ASP-ACTIVE state
> > > has not reach n.  The recovery timer T(r) is not running or 
> > has expired. 
> > > 
> > > AS-ACTIVE: The Application Server is available and 
> > application traffic is
> > > active. The AS moves to this state after being in 
> > AS-INACTIVE and getting n
> > > ASPs in ASP-ACTIVE state or, after reaching AS-ACTIVE and 
> > keeping one or
> > > more ASPs in ASP-ACTIVE state. 
> > 
> > I strongly disagree with the above.  The SG can move to the 
> > AS-ACTIVE state
> > with one ASP in the ASP-ACTIVE state: it need not wait until 
> > 'n'.  You are
> > still interpreting 'n' as some sort of absolute minimum 
> > number of ASPs,
> > when it was agreed that 'n' is the number of ASPs required to 
> > handle the
> > maximum engineered load.  As such, there is no reason why the 
> > SG cannot
> > place the AS AS-ACTIVE when one ASP is in the ASP-ACTIVE 
> > state for the AS.
> > 
> > The Old text is correct.  The above is incorrect.
> > 
> > > 
> > > AS-PENDING: The last active ASP has transitioned from ASP-ACTIVE to
> > > ASP-INACTIVE or ASP-DOWN.  A recovery timer T(r) SHOULD be 
> > started and all
> > > incoming signalling messages SHOULD be queued by the SGP. 
> > If an ASP becomes
> > > ASP-ACTIVE before T(r) expires, the AS is moved to the 
> > AS-ACTIVE state and
> > > all the queued messages will be sent to the ASP. 
> > > 
> > > If T(r) expires before an ASP becomes ASP-ACTIVE, the SGP 
> > MAY stops queuing
> > > messages and discards all previously queued messages. The 
> > AS will move to
> > > the AS-INACTIVE state if at least the number of ASPs in 
> > ASP-INACTIVE sum n,
> > > otherwise it will move to AS-DOWN state. 
> > > 
> > > Figure 5 shows an example AS state machine for the case where the 
> > > AS/ASP data is preconfigured and an n+k redundancy model. 
> > > 
> > > 
> > >              Figure 5: AS State Transition Diagram
> > > 
> > >                    
> > >      +----------+          IA2AC              +-------------+
> > >      |    AS-   |---------------------------->|     AS-     |
> > >      | INACTIVE |                             |   ACTIVE    |
> > >      |          |<-----------                 |             |
> > >      +----------+            \                +-------------+
> > >         ^   |                 \                    ^   |
> > >         |   | IA2DN            \ PN2IA             |   | AC2PN
> > >         |   |                   \                  |   | 
> > >   DN2IA |   |                    \          PN2AC  |   | 
> > >         |   v                     \                |   v
> > >      +----------+                  \          +-------------+
> > >      |          |                   ----------|             |
> > >      | AS-DOWN  |                             | AS-PENDING  |
> > >      |          |                  PN2DN      |  (queueing) |
> > >      |          |<----------------------------|             |
> > >      +----------+                             +-------------+
> > > 
> > > 
> > > 
> > > DN2IA: One ASP moves to ASP-INACTIVE causing that n ASPs 
> > are in either
> > > ASP-ACTIVE or ASP-INACTIVE states.
> > > 
> > > IA2DN: One ASP moves to ASP-DOWN causing that the number of 
> > ASPs in either
> > > ASP-ACTIVE or ASP-INACTIVE drops below n.
> > 
> > Wrong, as per above.  If one ASP is in the ASP-ACTIVE state 
> > for the AS,
> > the AS is AS-ACTIVE.
> > 
> > > 
> > > IA2AC: one ASP moves to ASP-ACTIVE, causing number of ASPs 
> > in the ASP-ACTIVE
> > > state to be n.
> > 
> > Wrong, as per above.  If one ASP moves to the ASP-ACTIVE 
> > state for the AS,
> > the AS is AS-ACTIVE.
> > 
> > > 
> > > AC2PN: the last ASP in ASP-ACTIVE state moves to 
> > ASP-INACTIVE or ASP-DOWN
> > > states, causing the number of ASPs in ASP-ACTIVE drop below 1.
> > > 
> > > PN2AC: One ASP moves to ASP-ACTIVE.
> > > 
> > > PN2IA: T(r) Expiry, n or more ASPs are in ASP-INACTIVE.
> > > 
> > > PN2DN: T(r) Expiry, the number of ASPs in ASP-INACTIVE 
> > state is less than n.
> > > 
> > > As "n" ASPs are needed to handle the maximum engineered 
> > load of the AS, an
> > > AS becomes AS-ACTIVE right after n ASPs reach the 
> > ASP-ACTIVE state during
> > > the start-up phase.
> > 
> > The above is incorrect per concensus.  For the start-up 
> > decision, the SG
> > can choose to either wait for 'n' or start traffic on the 
> > first active ASP.
> > What it MUST do not send NTFY(AS-ACTIVE) until it considers 
> > the AS in the
> > AS-ACTIVE state.
> > 
> > > Once the traffic is flowing, an AS keeps the AS-ACTIVE
> > > state till the last ASP turns to another state different to 
> > ASP-ACTIVE,
> > > avoiding unnecessary traffic disturbances as long as there are ASPs
> > > available, in the assumption that the AS will not always be 
> > exposed to the
> > > maximum load. 
> > 
> > It won't necessarily be exposed to maximum load on startup either.
> > 
> > Text below covers things internal to the SG only, and is unnecessary:
> > 
> > > 
> > > There are other cases where the AS/ASP configuration data is created
> > > dynamically. In those cases there would be differences in 
> > the state machine,
> > > especially at creation of the AS. For example, where the AS/ASP
> > > configuration data is not created until Registration of the 
> > first ASP, the
> > > AS-INACTIVE state is entered directly upon the nth 
> > successful REG REQ from
> > > an ASP belonging to that AS.  Another example is where the AS/ASP
> > > configuration data is not created until the nth ASP 
> > successfully enters the
> > > ASP-ACTIVE state.  In this latter case the AS-ACTIVE state 
> > is entered
> > > directly.
> > 
> > Stick with the old text.
> > 
> > --brian
> > 
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> > 

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

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



From exim@www1.ietf.org  Wed Jun 18 15:03:14 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22096
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 15:03:13 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5IJ2kq02235
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 15:02:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ShzQ-0008Gu-Uo; Wed, 18 Jun 2003 14:49:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Shk7-000793-1s
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 14:33:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20152
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 14:33:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Shhp-0007kG-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 14:30:49 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[8dm+ZFpqF4yXtSb88b/XWCQ3bJ4LeOhc])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Shho-0007kD-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 14:30:48 -0400
Received: from ns.pigworks.openss7.net (IDENT:3W/76210T8egm52RGZ4D6cktU6ijf3ru@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5IIX7X27836;
	Wed, 18 Jun 2003 12:33:07 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5IIX6D31925;
	Wed, 18 Jun 2003 12:33:06 -0600
Date: Wed, 18 Jun 2003 12:33:06 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
Cc: "'Samuel Dur D. Jeyaseelan'" <sjeyasee@ssd.usa.alcatel.com>,
        "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
Message-ID: <20030618123306.D31402@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>,
	"'Samuel Dur D. Jeyaseelan'" <sjeyasee@ssd.usa.alcatel.com>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>
References: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C68@eestqnt105.es.eu.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C68@eestqnt105.es.eu.ericsson.se>; from javier.pastor-balbas@ece.ericsson.se on Wed, Jun 18, 2003 at 02:56:41PM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id h5IIX7X27836
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA22096

Javier,

Your attachment didn't come through....

--brian

Javier Pastor-Balbas (ECE) wrote:                                                   (Wed, 18 Jun 2003 14:56:41)
> Hi Samuel, 
> 
> This is the consensus I was referring to. And it is what the new text try to state. 
> As far as I've seen Brian also disagrees now with this consensus since he
> states that n is not mandatory at the start up....
> 
> The consensus you mention would imply changes in the two sections I referred
> to in my previous mail.
> 
> Cheers // Javier.
> 
> > -----Original Message-----
> > From: Samuel Dur D. Jeyaseelan [mailto:sjeyasee@ssd.usa.alcatel.com]
> > Sent: miércoles, 18 de junio de 2003 13:11
> > To: Javier Pastor-Balbas (ECE)
> > Cc: Brian F. G. Bidulock; 'sigtran@ietf.org'
> > Subject: RE: [Sigtran] RE: M3UA IG: section 3.15 reworked
> > 
> > 
> > This message uses a character set that is not supported by 
> > the Internet Service.  To view the original message content,  
> > open the attached message. If the text doesn't display 
> > correctly, save the attachment to disk, and then open it 
> > using a viewer that can display the original character set. 
> > 

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

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



From exim@www1.ietf.org  Wed Jun 18 15:07:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22640
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 15:07:31 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5IJ74P03026
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 15:07:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ShzS-0008HI-5s; Wed, 18 Jun 2003 14:49:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ShqS-0007bu-7c
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 14:39:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20368
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 14:39:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShoA-0007nG-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 14:37:22 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[ixNc07Mzgc9vjW3ekzGOjWurPtTrLqXO])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sho9-0007nD-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 14:37:22 -0400
Received: from ns.pigworks.openss7.net (IDENT:ffaPnqbZ9PZQCiJoRWkW84J7ChK2KnW3@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5IIdeX27912;
	Wed, 18 Jun 2003 12:39:40 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5IIdd632037;
	Wed, 18 Jun 2003 12:39:39 -0600
Date: Wed, 18 Jun 2003 12:39:39 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030618123939.E31402@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030225031747.B13055@openss7.org> <Pine.SOL.4.10.10306180837480.6574-100000@sun2594.ssd.usa.alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.4.10.10306180837480.6574-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Wed, Jun 18, 2003 at 08:43:00AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Samuel,

Samuel Dur D. Jeyaseelan wrote:                                                     (Wed, 18 Jun 2003 08:43:00)
> 
> Brian,
> 
>  Just going back to 25-Feb-2003 ....
> 
> 
> 
> On Tue, 25 Feb 2003, Brian F. G. Bidulock wrote:
> 
> > Samuel,
> > 
> > Samuel Dur D. Jeyaseelan wrote:                                                     (Tue, 25 Feb 2003 03:56:07)
> > > 
> > > Brian,
> > > 
> > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
> > >   1000 Coit Road, Plano, Texas 75075
> > >   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> > > 
> > > On Tue, 25 Feb 2003, Brian F. G. Bidulock wrote:
> > > 
> > > > TOLGA,
> > > > 
> > > > TOLGA ASVEREN wrote:                                                                 (Tue, 25 Feb 2003 08:39:11)
> > > > > 
> > > > > Not necessarily because I disagree with some change, but just to clarify
> > > > > where the changes might take us:
> > > > 
> > > > If we cannot agree, we let the RFC stand.
> > > > 
> > > > > NTFY was used till now only as an advisory message, this will be changed.
> > > > 
> > > > No it will not.  An ASP is not forbidden from acting on any Notify message.
> > > > All Notify messages are still advisory.  The ASP can take into consideration
> > > > Notify messages, information that it has about other ASPs, the time of day,
> > > > direction of the wind, etc.
> > > > 
> > > > > Starting/stopping(till now we focused more on starting but why not stopping
> > > > > also? So SG can decide based on load/other dynamic conditions when to stop
> > > > > traffic to/from AS) traffic will be controlled by SGP with NTFY.
> > > > 
> > > > The SG has always been permitted to start or stop traffic when it considers
> > > > it necessary and has always been permitted to perform its necessary functions
> > > > with the SS7 network.  The SGP can send ASPIA Ack or drop associations any
> > > > time it wishes to stop traffic.
> > > 
> > > Please let me know what are we achieving by stopping the traffic in the
> > > following case(n+k - reduntancy)
> > > 
> > > When 'n' ASPs are active
> > > ------------------------
> > > SLS-X  ---->ASP1
> > > SLS-Y  ---->ASP2
> > > 
> > > When ASP1 goes down
> > > -------------------
> > > SLS-(Y,X)  ----->ASP2
> > > 
> > > Here 3 cases can be dealt
> > > 
> > > case 1) If SG receives  message with SLS Y - this traffic can be
> > >         successfully (100%) handled by ASP2 according to the configured
> > >         databse.
> > >  
> > > case 2) If SG receives messages with SLS X and Y - this traffic can be
> > >         successfully (100%) handled by ASP2, provided congestion has not
> > >         occured(according to q.704 section 3.8.2)
> > > 
> > > case 3) Don't allow SG to process the traffic when n<2 ?????????.
> > >         SG disallows traffic when n=0.
> > > 
> > > IMO, SG has capability to reroute the traffic to ASP1 and there is no
> > > meaning if SG stops traffic when n < 2.
> > > 
> > > This is just like a MTP3 link failure concept when link1 goes down ,
> > > traffic carried by link1 will be rerouted to available link. 
> > > All we need to do at SG is just change the SLS-ASP dynamic table to carry
> > > SLS X.
> > > 
> > > 
> > > --Samuel
> > 
> > I agree.   That is what is provided for in the RFC.  However, section 3.15 of
> > the IG would require the SG to stop traffic when n < 2.  So, it must be
> > struck.
> > 
> > --brian
> [Samuel] Does new IG stop the traffic when n < 2 ?

Yes, it does.  On restart.

--brian

> 
> > 
> > 
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> > 
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Wed Jun 18 16:08:55 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26805
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 16:08:55 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5IK8Qc14075
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 16:08:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Sj2H-0002zL-8s; Wed, 18 Jun 2003 15:56:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SipC-0002Xj-3t
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 15:42:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25291
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 15:42:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Simv-0000ys-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 15:40:09 -0400
Received: from web41801.mail.yahoo.com ([66.218.93.135])
	by ietf-mx with smtp (Exim 4.12)
	id 19Simv-0000yY-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 15:40:09 -0400
Message-ID: <20030618194157.16164.qmail@web41801.mail.yahoo.com>
Received: from [65.198.40.51] by web41801.mail.yahoo.com via HTTP; Wed, 18 Jun 2003 14:41:57 CDT
Date: Wed, 18 Jun 2003 14:41:57 -0500 (CDT)
From: =?iso-8859-1?q?Pablo=20Salinas?= <pablopesb@yahoo.com>
To: sigtran@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id PAA25292
Subject: [Sigtran] Interface Identifier parameter in M2UA DEREG REQ
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA26805

Hi there,
         In a DEREG REQ message in M2UA, could it have
a mix of Interface identifiers in integer type and
string type.
         Or should it be like an ASP Active message
where it cannot have string and integer Interface
Identifiers together?

         thanks,
                Pablo Salinas

_________________________________________________________
Do You Yahoo!?
Información de Estados Unidos y América Latina, en Yahoo! Noticias.
Visítanos en http://noticias.espanol.yahoo.com

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



From exim@www1.ietf.org  Wed Jun 18 23:59:18 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13890
	for <sigtran-archive@odin.ietf.org>; Wed, 18 Jun 2003 23:59:18 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5J3woQ17147
	for sigtran-archive@odin.ietf.org; Wed, 18 Jun 2003 23:58:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Sq5h-0003SP-2K; Wed, 18 Jun 2003 23:28:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SpnR-0002t6-Ca
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 23:09:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA12927
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 23:09:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Spl8-0005di-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 23:06:47 -0400
Received: from sj-core-4.cisco.com ([171.68.223.138])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Spl8-0005dL-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 23:06:46 -0400
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com [64.102.16.27])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id h5J38XaZ026250;
	Wed, 18 Jun 2003 20:08:34 -0700 (PDT)
Received: from kmorneau-w2k01.cisco.com (rtp-vpn1-28.cisco.com [10.82.224.28])
	by fruitpie.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AEI84689;
	Wed, 18 Jun 2003 20:08:32 -0700 (PDT)
Message-Id: <4.3.2.7.2.20030618230802.0ed30e80@cia.cisco.com>
X-Sender: kmorneau@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 18 Jun 2003 23:08:30 -0400
To: Pablo Salinas <pablopesb@yahoo.com>, sigtran@ietf.org
From: Ken Morneault <kmorneau@cisco.com>
Subject: Re: [Sigtran] Interface Identifier parameter in M2UA DEREG REQ
In-Reply-To: <20030618194157.16164.qmail@web41801.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id XAA13890


Pablo,

It should behave like the other messages which do not
allow a mix of string and integer types.

Regards,

Ken

At 02:41 PM 6/18/2003 -0500, Pablo Salinas wrote:
>Hi there,
>         In a DEREG REQ message in M2UA, could it have
>a mix of Interface identifiers in integer type and
>string type.
>         Or should it be like an ASP Active message
>where it cannot have string and integer Interface
>Identifiers together?
>
>         thanks,
>                Pablo Salinas
>
>_________________________________________________________
>Do You Yahoo!?
>Información de Estados Unidos y América Latina, en Yahoo! Noticias.
>Visítanos en http://noticias.espanol.yahoo.com
>
>_______________________________________________
>Sigtran mailing list
>Sigtran@ietf.org
>https://www1.ietf.org/mailman/listinfo/sigtran 


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



From exim@www1.ietf.org  Thu Jun 19 00:26:35 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15090
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Jun 2003 00:26:35 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5J4Q6N21259
	for sigtran-archive@odin.ietf.org; Thu, 19 Jun 2003 00:26:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SqmG-00054i-P1; Thu, 19 Jun 2003 00:12:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SqQo-00045f-Jh
	for sigtran@optimus.ietf.org; Wed, 18 Jun 2003 23:49:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13748
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 23:49:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SqOX-0005s6-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 23:47:29 -0400
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SqOW-0005rm-00
	for sigtran@ietf.org; Wed, 18 Jun 2003 23:47:28 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h5J3nGwC001508
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 22:49:17 -0500 (CDT)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h5J3mN1C028253
	for <sigtran@ietf.org>; Wed, 18 Jun 2003 22:48:23 -0500 (CDT)
Date: Wed, 18 Jun 2003 22:48:23 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
In-Reply-To: <20030618123939.E31402@openss7.org>
Message-ID: <Pine.SOL.4.10.10306182245090.9866-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


Brian,

  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******

On Wed, 18 Jun 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> Samuel Dur D. Jeyaseelan wrote:                                                     (Wed, 18 Jun 2003 08:43:00)
> > 
> > Brian,
> > 
> >  Just going back to 25-Feb-2003 ....
> > 
> > 
> > 
> > On Tue, 25 Feb 2003, Brian F. G. Bidulock wrote:
> > 
> > > Samuel,
> > > 
> > > Samuel Dur D. Jeyaseelan wrote:                                                     (Tue, 25 Feb 2003 03:56:07)
> > > > 
> > > > Brian,
> > > > 
> > > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
> > > >   1000 Coit Road, Plano, Texas 75075
> > > >   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> > > > 
> > > > On Tue, 25 Feb 2003, Brian F. G. Bidulock wrote:
> > > > 
> > > > > TOLGA,
> > > > > 
> > > > > TOLGA ASVEREN wrote:                                                                 (Tue, 25 Feb 2003 08:39:11)
> > > > > > 
> > > > > > Not necessarily because I disagree with some change, but just to clarify
> > > > > > where the changes might take us:
> > > > > 
> > > > > If we cannot agree, we let the RFC stand.
> > > > > 
> > > > > > NTFY was used till now only as an advisory message, this will be changed.
> > > > > 
> > > > > No it will not.  An ASP is not forbidden from acting on any Notify message.
> > > > > All Notify messages are still advisory.  The ASP can take into consideration
> > > > > Notify messages, information that it has about other ASPs, the time of day,
> > > > > direction of the wind, etc.
> > > > > 
> > > > > > Starting/stopping(till now we focused more on starting but why not stopping
> > > > > > also? So SG can decide based on load/other dynamic conditions when to stop
> > > > > > traffic to/from AS) traffic will be controlled by SGP with NTFY.
> > > > > 
> > > > > The SG has always been permitted to start or stop traffic when it considers
> > > > > it necessary and has always been permitted to perform its necessary functions
> > > > > with the SS7 network.  The SGP can send ASPIA Ack or drop associations any
> > > > > time it wishes to stop traffic.
> > > > 
> > > > Please let me know what are we achieving by stopping the traffic in the
> > > > following case(n+k - reduntancy)
> > > > 
> > > > When 'n' ASPs are active
> > > > ------------------------
> > > > SLS-X  ---->ASP1
> > > > SLS-Y  ---->ASP2
> > > > 
> > > > When ASP1 goes down
> > > > -------------------
> > > > SLS-(Y,X)  ----->ASP2
> > > > 
> > > > Here 3 cases can be dealt
> > > > 
> > > > case 1) If SG receives  message with SLS Y - this traffic can be
> > > >         successfully (100%) handled by ASP2 according to the configured
> > > >         databse.
> > > >  
> > > > case 2) If SG receives messages with SLS X and Y - this traffic can be
> > > >         successfully (100%) handled by ASP2, provided congestion has not
> > > >         occured(according to q.704 section 3.8.2)
> > > > 
> > > > case 3) Don't allow SG to process the traffic when n<2 ?????????.
> > > >         SG disallows traffic when n=0.
> > > > 
> > > > IMO, SG has capability to reroute the traffic to ASP1 and there is no
> > > > meaning if SG stops traffic when n < 2.
> > > > 
> > > > This is just like a MTP3 link failure concept when link1 goes down ,
> > > > traffic carried by link1 will be rerouted to available link. 
> > > > All we need to do at SG is just change the SLS-ASP dynamic table to carry
> > > > SLS X.
> > > > 
> > > > 
> > > > --Samuel
> > > 
> > > I agree.   That is what is provided for in the RFC.  However, section 3.15 of
> > > the IG would require the SG to stop traffic when n < 2.  So, it must be
> > > struck.
> > > 
> > > --brian
> > [Samuel] Does new IG stop the traffic when n < 2 ?
> 
> Yes, it does.  On restart.
> 
Yes thats what everybody agrees that on start and restart case 'n' number
of ASPs to be in ACTIVE state.

--Samuel
> --brian
> 
> > 
> > > 
> > > 
> > > -- 
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > > 
> > 
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 


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



From exim@www1.ietf.org  Thu Jun 19 01:29:24 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16564
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Jun 2003 01:29:23 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5J5StK30329
	for sigtran-archive@odin.ietf.org; Thu, 19 Jun 2003 01:28:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SrdV-00077n-LT; Thu, 19 Jun 2003 01:07:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SrRs-0006iu-CB
	for sigtran@optimus.ietf.org; Thu, 19 Jun 2003 00:55:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15747
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 00:54:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SrPa-0006KO-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 00:52:38 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[udF+hl84Y/MC27UXLqj2WDS0lSMMOCdf])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SrPZ-0006K9-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 00:52:37 -0400
Received: from ns.pigworks.openss7.net (IDENT:6+C2GGISt7s0wASqqPAUoqbTgz+nDKS0@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5J4sfX03679;
	Wed, 18 Jun 2003 22:54:41 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5J4seZ08865;
	Wed, 18 Jun 2003 22:54:40 -0600
Date: Wed, 18 Jun 2003 22:54:40 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030618225440.A8726@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030618123939.E31402@openss7.org> <Pine.SOL.4.10.10306182245090.9866-100000@sun2594.ssd.usa.alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.4.10.10306182245090.9866-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Wed, Jun 18, 2003 at 10:48:23PM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Samuel,

Samuel Dur D. Jeyaseelan wrote:                                                     (Wed, 18 Jun 2003 22:48:23)
> > > > 
> > > > I agree.   That is what is provided for in the RFC.  However, section 3.15 of
> > > > the IG would require the SG to stop traffic when n < 2.  So, it must be
> > > > struck.
> > > > 
> > > > --brian
> > > [Samuel] Does new IG stop the traffic when n < 2 ?
> > 
> > Yes, it does.  On restart.
> > 
> Yes thats what everybody agrees that on start and restart case 'n' number
> of ASPs to be in ACTIVE state.

Disagree wholeheartedly.  And this was never agreed.

What was agreed (except for Tolga) was that the RFC allowed the SG to either
activate on one ASP or wait for 'n' and withhold NTFY(AS-ACTIVE) which was
sufficient for both start and restart cases.

If an outage has been for a brief period and was not congestion related, there
is no reason why traffic cannot be started on the first active ASP, or under
emergency conditions for that matter.

The start, restart and shutdown decisions were discussed in detail on the
list.  Whether the SG waits for 1 or 'n' is an IMPLEMENTATION and OPERATIONAL
decision.  The existing RFC provides for this in saying that the AS-ACTIVE
state implies that "at least one" ASP is in the ASP-ACTIVE state for the AS.
Also the RFC states that the SGP should withhold the NTFY(AS-ACTIVE) until 'n'
ASPs are active if it is going to wait for 'n' ASPs (as it MAY do).  And it
also says that the ASPs should coordinate amoungst themselves to ensure that
'n' are active.

Let me give you an example of the negative effect of this change:  An SG is
configured with n=256.  There are 257 ASPs.  2 are dead.  The AS will never
activate.  Some carrier class system...

Contrast this where, soley at the SG implementer's discretion, the SG
implementor sets a timer when the first ASP goes ASP-ACTIVE for the AS.  If
the other 255 are not active by the time this timer expires, it sends
NTFY(AS-ACTIVE) and starts traffic.  This system will always come up in
contrast to the above that will not.  The RFC allows for this system, the
new IG text does not.

The new IG text would have you implement the system that will never come up
with 2 ASPs out of service.  The RFC does not.

I you wan to explain things in the IG, go ahead, but the proposed text does
not do that.  The proposed text makes changes to the normal and correct
operation as laid out in the RFC and starts making implementation and
operational decisions for the SG designer that it must not.

--brian

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

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



From exim@www1.ietf.org  Thu Jun 19 02:14:53 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29839
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Jun 2003 02:14:53 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5J6EPA15674
	for sigtran-archive@odin.ietf.org; Thu, 19 Jun 2003 02:14:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SsM1-0000Vm-9F; Thu, 19 Jun 2003 01:53:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SsCH-0000Ba-Mk
	for sigtran@optimus.ietf.org; Thu, 19 Jun 2003 01:42:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17238
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 01:42:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ss9z-0006kF-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 01:40:35 -0400
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ss9u-0006kB-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 01:40:30 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h5J5gJwA008533
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 00:42:19 -0500 (CDT)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h5J5g51C010266
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 00:42:06 -0500 (CDT)
Date: Thu, 19 Jun 2003 00:42:05 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
In-Reply-To: <20030618225440.A8726@openss7.org>
Message-ID: <Pine.SOL.4.10.10306190008150.9866-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


Brian,


On Wed, 18 Jun 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> Samuel Dur D. Jeyaseelan wrote:                                                     (Wed, 18 Jun 2003 22:48:23)
> > > > > 
> > > > > I agree.   That is what is provided for in the RFC.  However, section 3.15 of
> > > > > the IG would require the SG to stop traffic when n < 2.  So, it must be
> > > > > struck.
> > > > > 
> > > > > --brian
> > > > [Samuel] Does new IG stop the traffic when n < 2 ?
> > > 
> > > Yes, it does.  On restart.
> > > 
> > Yes thats what everybody agrees that on start and restart case 'n' number
> > of ASPs to be in ACTIVE state.
> 
> Disagree wholeheartedly.  And this was never agreed.
> 
> What was agreed (except for Tolga) was that the RFC allowed the SG to either
> activate on one ASP or wait for 'n' and withhold NTFY(AS-ACTIVE) which was
> sufficient for both start and restart cases.
> 
section 5.4.1 says that minimum 'n' number of ASPs are required to handle 
total traffic load.Here my understanding is, craft person knows the
incoming traffic capacity based on some kind of 'traffic measurement
analysis',
and the same time craft person knows, to handle this incoming traffic an
SGP requires 'n' ASPs.Here the point is craft person can not maintain 'n'
ASPs to be in ACTIVE state throughout the traffic period but at least he
can make sure 'n' ASPs are ACTIVE when (initally) SG comes up.

> If an outage has been for a brief period and was not congestion related, there
> is no reason why traffic cannot be started on the first active ASP, or under
> emergency conditions for that matter.
This may happen while SGP is processing the load but it may not happen in
the beginning and a good network configuration should not allow these
kinds of problems to happen in the beginning.

> The start, restart and shutdown decisions were discussed in detail on the
> list.  Whether the SG waits for 1 or 'n' is an IMPLEMENTATION and OPERATIONAL
> decision.  The existing RFC provides for this in saying that the AS-ACTIVE
> state implies that "at least one" ASP is in the ASP-ACTIVE state for the AS.
> Also the RFC states that the SGP should withhold the NTFY(AS-ACTIVE) until 'n'
> ASPs are active if it is going to wait for 'n' ASPs (as it MAY do).  And it
> also says that the ASPs should coordinate amoungst themselves to ensure that
> 'n' are active.
This is left to the decision of the craft person, this case he can
configure n=1.
> 
> Let me give you an example of the negative effect of this change:  An SG is
> configured with n=256.  There are 257 ASPs.  2 are dead.  The AS will never
> activate.  Some carrier class system...
> 
If n=256, it is the responsibility of the operator to make sure and bring
up 256 ASPs to ACTIVE state at least in the beginning.

> Contrast this where, soley at the SG implementer's discretion, the SG
> implementor sets a timer when the first ASP goes ASP-ACTIVE for the AS.  If
> the other 255 are not active by the time this timer expires, it sends
> NTFY(AS-ACTIVE) and starts traffic.  This system will always come up in
> contrast to the above that will not.  The RFC allows for this system, the
> new IG text does not.
> 
> The new IG text would have you implement the system that will never come up
> with 2 ASPs out of service.  The RFC does not.

section 5.1.4
   n+k case
   --------
   This scenario shows the example M3UA message flows for the
   establishment of traffic between an SGP and three ASPs in the same
   Application Server, where two of the ASPs are brought to the state
   ASP-ACTIVE and subsequently share the load.  In this case, a minimum
   of two ASPs are required to handle the total traffic load (2+1
   sparing).

still RFC says '... a minimum of two ASPs are required to handle the total
traffic load ....'

> 
> I you wan to explain things in the IG, go ahead, but the proposed text does
> not do that.  The proposed text makes changes to the normal and correct
> operation as laid out in the RFC and starts making implementation and
> operational decisions for the SG designer that it must not.
> 
> --brian
> 

I have conveyed my understanding to all. Otherwise in order to conclude 
this issue we can go for polling.

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


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



From exim@www1.ietf.org  Thu Jun 19 02:44:36 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01809
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Jun 2003 02:44:36 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5J6i8T21741
	for sigtran-archive@odin.ietf.org; Thu, 19 Jun 2003 02:44:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Sswo-0004nF-4b; Thu, 19 Jun 2003 02:31:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Ssnd-0004Lo-KR
	for sigtran@optimus.ietf.org; Thu, 19 Jun 2003 02:21:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00641
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 02:21:30 -0400 (EDT)
From: joyce_archibald@agilent.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SslL-0007Dm-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 02:19:11 -0400
Received: from msgbas1x.net.europe.agilent.com ([192.25.19.109])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SslK-0007Dj-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 02:19:10 -0400
Received: from msgrel1.germany.agilent.com (msgrel1.germany.agilent.com [134.40.2.57])
	by msgbas1x.net.europe.agilent.com (Postfix) with ESMTP
	id 08560BC1; Thu, 19 Jun 2003 08:21:30 +0200 (METDST)
Received: from wbbnbh01.germany.agilent.com (wbbnbh01b.germany.agilent.com [134.40.35.102])
	by msgrel1.germany.agilent.com (Postfix) with ESMTP
	id DFA765C9; Thu, 19 Jun 2003 08:21:29 +0200 (METDST)
content-class: urn:content-classes:message
Subject: RE: [Sigtran] M3UA: Question about ITU Point Code Format
Date: Thu, 19 Jun 2003 08:21:29 +0200
Message-ID: <C12D24916888D311BC790090275414BB0F32BA9F@oberon.britain.agilent.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [Sigtran] M3UA: Question about ITU Point Code Format
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Thread-Index: AcM1vJrUaPmNyVLOSo2DaWnquYGofgAbO+Xg
To: <LeoBloom1@msn.com>, <sigtran@ietf.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id CAA01809

Hi Leo
 
The PointCodes in M3UA occupy 4 bytes, the MSB is a mask and the next 3 bytes contain the point code, right justified. Thus the ITU point code of 7-255-7 would be transmitted as 00 00 3F FF. As you say the same pointcode on SS7 would be transmitted as FF 3F.
 
Cheers,
Joyce

==================================================================
Joyce Archibald, TSD R&D     | Phone:    +44 (0) 131 3317521
Agilent Technologies UK Ltd  | Telnet:   313 2521
South Queensferry,           | Mailstop: SQFRD3A
EH30 9TG, Scotland.          | E-mail: joyce_archibald@agilent.com
================================================================== 

 

-----Original Message-----
From: LeoBloom1 [mailto:LeoBloom1@msn.com]
Sent: 15 June 2003 16:25
To: sigtran@ietf.org
Subject: [Sigtran] M3UA: Question about ITU Point Code Format


Hello,
 
I have a question about the Point Code representation for ITU in M3UA. 
I've looked through the mailing list threads and have not seen a reference so I wanted to pose the question - though I suspect it may be a simple one, I cannot quite get clarity from RFC 3332/IG based on my analysis:
 
In the Affected Point Code, etc., parameters in M3UA messages, do the six bits in the Most Significant Byte of the ITU Point Code correspond to the same six bits in the Most Significant Byte of the M3UA Point Code, and the eight bits in the Least Significant Byte correspond to the Least Significant Byte in M3UA?

If we have the ITU Point Code 7-255-7 represented in hex (order of transmission is displayed left to right) it will appear as FF 3F since the Least Significant Byte is transmitted first (reference section 3.4.2.1 of ITU-T Q.713).  {The binary representation is 11111111 00111111.}

-In M3UA the Most Significant Byte is transmitted first so would the Point Code example above (7-255-7) appear as 3F FF if represented as hex? {The binary representation might be 00111111 11111111.}
 
Thanks in advance for any feedback.
Regards,
Charles Hastings
 


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



From exim@www1.ietf.org  Thu Jun 19 04:06:13 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04152
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Jun 2003 04:06:13 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5J85jG01515
	for sigtran-archive@odin.ietf.org; Thu, 19 Jun 2003 04:05:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SuBF-0008KR-Fe; Thu, 19 Jun 2003 03:50:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Stzx-0007uy-My
	for sigtran@optimus.ietf.org; Thu, 19 Jun 2003 03:38:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03497
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 03:38:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Stxg-0000SH-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 03:36:00 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[jF6dfD0+wmgEA93nrXkj7RfuB2TEQpdy])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Stxf-0000SE-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 03:35:59 -0400
Received: from ns.pigworks.openss7.net (IDENT:9Jx5JFw2D6Hye2OgpGkOOKoakPc6EvD+@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5J7cIX05940;
	Thu, 19 Jun 2003 01:38:18 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5J7cIt10582;
	Thu, 19 Jun 2003 01:38:18 -0600
Date: Thu, 19 Jun 2003 01:38:18 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030619013818.A10362@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030618225440.A8726@openss7.org> <Pine.SOL.4.10.10306190008150.9866-100000@sun2594.ssd.usa.alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.4.10.10306190008150.9866-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Thu, Jun 19, 2003 at 12:42:05AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Samuel,

'n' (as agreed by concensus, and included in the new IG text as well) is the
number of ASP required to handle the "maximum engineered load", not the normal
load, or event the expected load.  So, for an ISUP bearing system, if it is
not Christmas or Mother's day, and there is not a significant backlog of
reattempt traffic (extended outage), the system can come up with less than 'n'
processors, as 'n' is defined.  Therefore, refusing to start or restart an
AS with less than 'n' active ASPs is foolish.

Setting n to 1, as you suggest, would be incorrect.  1 ASP cannot handle the
"maximum engineered load".  In the example, it takes 256 ASPs to handle the
"maximum engineered load" (e.g. busy-hour on Mother's Day).  But for the other
340 some days of the year, some lesser number of ASPs is sufficient, and 255
ASPs is surely sufficient.

Not permitting the SG to start or restart with less than 'n' ASPs active
is a bad thing for carrier class systems.

I cannot agree with the change on these grounds.

--brian


Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 19 Jun 2003 00:42:05)
> 
> Brian,
> 
> 
> On Wed, 18 Jun 2003, Brian F. G. Bidulock wrote:
> 
> > Samuel,
> > 
> > Samuel Dur D. Jeyaseelan wrote:                                                     (Wed, 18 Jun 2003 22:48:23)
> > > > > > 
> > > > > > I agree.   That is what is provided for in the RFC.  However, section 3.15 of
> > > > > > the IG would require the SG to stop traffic when n < 2.  So, it must be
> > > > > > struck.
> > > > > > 
> > > > > > --brian
> > > > > [Samuel] Does new IG stop the traffic when n < 2 ?
> > > > 
> > > > Yes, it does.  On restart.
> > > > 
> > > Yes thats what everybody agrees that on start and restart case 'n' number
> > > of ASPs to be in ACTIVE state.
> > 
> > Disagree wholeheartedly.  And this was never agreed.
> > 
> > What was agreed (except for Tolga) was that the RFC allowed the SG to either
> > activate on one ASP or wait for 'n' and withhold NTFY(AS-ACTIVE) which was
> > sufficient for both start and restart cases.
> > 
> section 5.4.1 says that minimum 'n' number of ASPs are required to handle 
> total traffic load.Here my understanding is, craft person knows the
> incoming traffic capacity based on some kind of 'traffic measurement
> analysis',
> and the same time craft person knows, to handle this incoming traffic an
> SGP requires 'n' ASPs.Here the point is craft person can not maintain 'n'
> ASPs to be in ACTIVE state throughout the traffic period but at least he
> can make sure 'n' ASPs are ACTIVE when (initally) SG comes up.
> 
> > If an outage has been for a brief period and was not congestion related, there
> > is no reason why traffic cannot be started on the first active ASP, or under
> > emergency conditions for that matter.
> This may happen while SGP is processing the load but it may not happen in
> the beginning and a good network configuration should not allow these
> kinds of problems to happen in the beginning.
> 
> > The start, restart and shutdown decisions were discussed in detail on the
> > list.  Whether the SG waits for 1 or 'n' is an IMPLEMENTATION and OPERATIONAL
> > decision.  The existing RFC provides for this in saying that the AS-ACTIVE
> > state implies that "at least one" ASP is in the ASP-ACTIVE state for the AS.
> > Also the RFC states that the SGP should withhold the NTFY(AS-ACTIVE) until 'n'
> > ASPs are active if it is going to wait for 'n' ASPs (as it MAY do).  And it
> > also says that the ASPs should coordinate amoungst themselves to ensure that
> > 'n' are active.
> This is left to the decision of the craft person, this case he can
> configure n=1.
> > 
> > Let me give you an example of the negative effect of this change:  An SG is
> > configured with n=256.  There are 257 ASPs.  2 are dead.  The AS will never
> > activate.  Some carrier class system...
> > 
> If n=256, it is the responsibility of the operator to make sure and bring
> up 256 ASPs to ACTIVE state at least in the beginning.
> 
> > Contrast this where, soley at the SG implementer's discretion, the SG
> > implementor sets a timer when the first ASP goes ASP-ACTIVE for the AS.  If
> > the other 255 are not active by the time this timer expires, it sends
> > NTFY(AS-ACTIVE) and starts traffic.  This system will always come up in
> > contrast to the above that will not.  The RFC allows for this system, the
> > new IG text does not.
> > 
> > The new IG text would have you implement the system that will never come up
> > with 2 ASPs out of service.  The RFC does not.
> 
> section 5.1.4
>    n+k case
>    --------
>    This scenario shows the example M3UA message flows for the
>    establishment of traffic between an SGP and three ASPs in the same
>    Application Server, where two of the ASPs are brought to the state
>    ASP-ACTIVE and subsequently share the load.  In this case, a minimum
>    of two ASPs are required to handle the total traffic load (2+1
>    sparing).
> 
> still RFC says '... a minimum of two ASPs are required to handle the total
> traffic load ....'
> 
> > 
> > I you wan to explain things in the IG, go ahead, but the proposed text does
> > not do that.  The proposed text makes changes to the normal and correct
> > operation as laid out in the RFC and starts making implementation and
> > operational decisions for the SG designer that it must not.
> > 
> > --brian
> > 
> 
> I have conveyed my understanding to all. Otherwise in order to conclude 
> this issue we can go for polling.
> 
> --Samuel
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> > 
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Thu Jun 19 04:08:26 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04248
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Jun 2003 04:08:26 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5J87vE03239
	for sigtran-archive@odin.ietf.org; Thu, 19 Jun 2003 04:07:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SuCD-0008MI-Qa; Thu, 19 Jun 2003 03:51:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Su3x-00082j-5v
	for sigtran@optimus.ietf.org; Thu, 19 Jun 2003 03:42:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03529
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 03:42:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Su1f-0000Sp-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 03:40:08 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[JEu7fmVgxa5CVlEXd1A5NOmV1sGzac3+])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Su1f-0000Sm-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 03:40:07 -0400
Received: from ns.pigworks.openss7.net (IDENT:HrQdPki4Lq6oNgNaBzHfUoKynVbT7Iaf@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5J7gQX05984;
	Thu, 19 Jun 2003 01:42:26 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5J7gQY10607;
	Thu, 19 Jun 2003 01:42:26 -0600
Date: Thu, 19 Jun 2003 01:42:26 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: joyce_archibald@agilent.com
Cc: LeoBloom1@msn.com, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA: Question about ITU Point Code Format
Message-ID: <20030619014226.B10362@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: joyce_archibald@agilent.com, LeoBloom1@msn.com,
	sigtran@ietf.org
References: <C12D24916888D311BC790090275414BB0F32BA9F@oberon.britain.agilent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <C12D24916888D311BC790090275414BB0F32BA9F@oberon.britain.agilent.com>; from joyce_archibald@agilent.com on Thu, Jun 19, 2003 at 08:21:29AM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

joyce_archibald,

joyce_archibald@agilent.com wrote:                                         (Thu, 19 Jun 2003 08:21:29)
> Hi Leo
>  
> The PointCodes in M3UA occupy 4 bytes, the MSB is a mask and the next 3
> bytes contain the point code, right justified. Thus the ITU point code of
> 7-255-7 would be transmitted as 00 00 3F FF. As you say the same pointcode
> on SS7 would be transmitted as
> FF 3F.
  ^^^^^

Only if you like to read from left to right and lsbit to msbit!  It is custom
in SS7 to read from rigth to left and lsbit to msbit, in which case it would
be:  3F FF as well.

--brian



>  
> Cheers,
> Joyce
> 
> ==================================================================
> Joyce Archibald, TSD R&D     | Phone:    +44 (0) 131 3317521
> Agilent Technologies UK Ltd  | Telnet:   313 2521
> South Queensferry,           | Mailstop: SQFRD3A
> EH30 9TG, Scotland.          | E-mail: joyce_archibald@agilent.com
> ================================================================== 
> 
>  
> 
> -----Original Message-----
> From: LeoBloom1 [mailto:LeoBloom1@msn.com]
> Sent: 15 June 2003 16:25
> To: sigtran@ietf.org
> Subject: [Sigtran] M3UA: Question about ITU Point Code Format
> 
> 
> Hello,
>  
> I have a question about the Point Code representation for ITU in M3UA. 
> I've looked through the mailing list threads and have not seen a reference so I wanted to pose the question - though I suspect it may be a simple one, I cannot quite get clarity from RFC 3332/IG based on my analysis:
>  
> In the Affected Point Code, etc., parameters in M3UA messages, do the six bits in the Most Significant Byte of the ITU Point Code correspond to the same six bits in the Most Significant Byte of the M3UA Point Code, and the eight bits in the Least Significant Byte correspond to the Least Significant Byte in M3UA?
> 
> If we have the ITU Point Code 7-255-7 represented in hex (order of transmission is displayed left to right) it will appear as FF 3F since the Least Significant Byte is transmitted first (reference section 3.4.2.1 of ITU-T Q.713).  {The binary representation is 11111111 00111111.}
> 
> -In M3UA the Most Significant Byte is transmitted first so would the Point Code example above (7-255-7) appear as 3F FF if represented as hex? {The binary representation might be 00111111 11111111.}
>  
> Thanks in advance for any feedback.
> Regards,
> Charles Hastings
>  
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Thu Jun 19 04:30:38 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05085
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Jun 2003 04:30:37 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5J8UAn06801
	for sigtran-archive@odin.ietf.org; Thu, 19 Jun 2003 04:30:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SuTd-0000xS-Rm; Thu, 19 Jun 2003 04:09:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SuL7-00009I-Bc
	for sigtran@optimus.ietf.org; Thu, 19 Jun 2003 04:00:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04080
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 04:00:11 -0400 (EDT)
From: joyce_archibald@agilent.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SuIp-0000aw-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 03:57:52 -0400
Received: from msgbas1x.net.europe.agilent.com ([192.25.19.109])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SuIp-0000at-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 03:57:51 -0400
Received: from msgrel1.germany.agilent.com (msgrel1.germany.agilent.com [134.40.2.57])
	by msgbas1x.net.europe.agilent.com (Postfix) with ESMTP
	id AE5F0C9C; Thu, 19 Jun 2003 10:00:10 +0200 (METDST)
Received: from denep.germany.agilent.com (denep.germany.agilent.com [134.40.35.17])
	by msgrel1.germany.agilent.com (Postfix) with SMTP
	id 55628539; Thu, 19 Jun 2003 10:00:10 +0200 (METDST)
Received: from 134.40.35.17 by denep.germany.agilent.com (InterScan E-Mail VirusWall NT); Thu, 19 Jun 2003 10:00:09 +0200
Received: by denep.germany.agilent.com with Internet Mail Service (5.5.2653.19)
	id <LYCWL3LS>; Thu, 19 Jun 2003 10:00:09 +0200
Message-ID: <C12D24916888D311BC790090275414BB0F32BAA0@oberon.britain.agilent.com>
To: bidulock@openss7.org
Cc: LeoBloom1@msn.com, sigtran@ietf.org
Subject: RE: [Sigtran] M3UA: Question about ITU Point Code Format
Date: Thu, 19 Jun 2003 10:00:05 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,

Leo asked about byte transmission order and the order of bytes transmitted is still 00 00 3F FF for M3UA and FF 3F for SS7, regardless of how you read it.

Joyce

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: 19 June 2003 08:42
> To: joyce_archibald@agilent.com
> Cc: LeoBloom1@msn.com; sigtran@ietf.org
> Subject: Re: [Sigtran] M3UA: Question about ITU Point Code Format
> 
> 
> joyce_archibald,
> 
> joyce_archibald@agilent.com wrote:                            
>              (Thu, 19 Jun 2003 08:21:29)
> > Hi Leo
> >  
> > The PointCodes in M3UA occupy 4 bytes, the MSB is a mask 
> and the next 3
> > bytes contain the point code, right justified. Thus the ITU 
> point code of
> > 7-255-7 would be transmitted as 00 00 3F FF. As you say the 
> same pointcode
> > on SS7 would be transmitted as
> > FF 3F.
>   ^^^^^
> 
> Only if you like to read from left to right and lsbit to 
> msbit!  It is custom
> in SS7 to read from rigth to left and lsbit to msbit, in 
> which case it would
> be:  3F FF as well.
> 
> --brian
> 
> 
> 
> >  
> > Cheers,
> > Joyce
> > 
> > ==================================================================
> > Joyce Archibald, TSD R&D     | Phone:    +44 (0) 131 3317521
> > Agilent Technologies UK Ltd  | Telnet:   313 2521
> > South Queensferry,           | Mailstop: SQFRD3A
> > EH30 9TG, Scotland.          | E-mail: joyce_archibald@agilent.com
> > ================================================================== 
> > 
> >  
> > 
> > -----Original Message-----
> > From: LeoBloom1 [mailto:LeoBloom1@msn.com]
> > Sent: 15 June 2003 16:25
> > To: sigtran@ietf.org
> > Subject: [Sigtran] M3UA: Question about ITU Point Code Format
> > 
> > 
> > Hello,
> >  
> > I have a question about the Point Code representation for 
> ITU in M3UA. 
> > I've looked through the mailing list threads and have not 
> seen a reference so I wanted to pose the question - though I 
> suspect it may be a simple one, I cannot quite get clarity 
> from RFC 3332/IG based on my analysis:
> >  
> > In the Affected Point Code, etc., parameters in M3UA 
> messages, do the six bits in the Most Significant Byte of the 
> ITU Point Code correspond to the same six bits in the Most 
> Significant Byte of the M3UA Point Code, and the eight bits 
> in the Least Significant Byte correspond to the Least 
> Significant Byte in M3UA?
> > 
> > If we have the ITU Point Code 7-255-7 represented in hex 
> (order of transmission is displayed left to right) it will 
> appear as FF 3F since the Least Significant Byte is 
> transmitted first (reference section 3.4.2.1 of ITU-T Q.713). 
>  {The binary representation is 11111111 00111111.}
> > 
> > -In M3UA the Most Significant Byte is transmitted first so 
> would the Point Code example above (7-255-7) appear as 3F FF 
> if represented as hex? {The binary representation might be 
> 00111111 11111111.}
> >  
> > Thanks in advance for any feedback.
> > Regards,
> > Charles Hastings
> >  
> > 
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 

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



From exim@www1.ietf.org  Thu Jun 19 06:07:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06915
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Jun 2003 06:07:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5JA72f25266
	for sigtran-archive@odin.ietf.org; Thu, 19 Jun 2003 06:07:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SvyX-0005kc-V9; Thu, 19 Jun 2003 05:45:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Svjh-0004s4-7a
	for sigtran@optimus.ietf.org; Thu, 19 Jun 2003 05:29:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05954
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 05:29:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SvhO-00016z-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 05:27:18 -0400
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47] helo=penguin.al.sw.ericsson.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SvhO-00016w-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 05:27:18 -0400
Received: from esealnt613.al.sw.ericsson.se (alteon-nat8.sw.ericsson.se [153.88.254.125])
	by penguin.al.sw.ericsson.se (8.12.9/8.12.9/WIREfire-1.6b) with ESMTP id h5J9TNw2024005;
	Thu, 19 Jun 2003 11:29:25 +0200 (MEST)
Received: from ESEALNT744.al.sw.ericsson.se ([153.88.251.4]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id MVP9CC3G; Thu, 19 Jun 2003 11:29:51 +0200
Received: by ESEALNT744.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NBCQ8WM1>; Thu, 19 Jun 2003 11:29:23 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C6D@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
To: "'kakaul@hss.hns.com'" <kakaul@hss.hns.com>,
        Tolga Asveren
	 <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] M3UA IG: NTFY & Examples Section proposal
Date: Thu, 19 Jun 2003 11:29:05 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Hi guys, 

Here I include a proposed text for the Examples section where all the NTFY are included. Check I didn't miss any. I've also changed LRC meaning explanation to "Local RK Id".

Thanks // Javier.


---------------------------oOo--------------------------


---------
Old text: (Section 5)
---------

NOTE: Not all the Notify messages that are appropriate per the Notify procedures are shown in these examples.


---------
New text: (Section 5)
---------

-	


---------
Old text: (Section 5.1.1.1)
---------

              SGP                             ASP1
               |                               |
               |<-------------ASP Up-----------|
               |-----------ASP Up Ack--------->|
               |                               |
               |<------- ASP Active(RCn)-------|  RC: Routing Context
               |-----ASP Active Ack (RCn)----->|      (optional)
               |                               |
               |-----NTFY(AS-ACTIVE)(RCn)----->|
               |                               |


---------
New text: (Section 5.1.1.1)
---------


              SGP                             ASP1
               |                               |
               |<-------------ASP Up-----------|
               |-----------ASP Up Ack--------->|
               |                               |
               |-----NTFY(AS-INACTIVE)(RCn)--->|
               |                               |
               |<------- ASP Active(RCn)-------|  RC: Routing Context
               |-----ASP Active Ack (RCn)----->|      (optional)
               |                               |
               |-----NTFY(AS-ACTIVE)(RCn)----->|
               |                               |
---------
Old text: (Section 5.1.1.2)
---------


             SGP                             ASP1
              |                               |
              |<------------ASP Up------------|
              |----------ASP Up Ack---------->|
              |                               |
              |<----REGISTER REQ(LRCn,RKn)----|  LRC: Local Routing
              |                               |       Context
              |----REGISTER RESP(LRCn,RCn)--->|   RK: Routing Key
              |                               |   RC: Routing Context
              |                               |
              |<------- ASP Active(RCn)-------|
              |-----ASP Active Ack (RCn)----->|
              |                               |
              |-----NTFY(AS-ACTIVE)(RCn)----->|
              |                               |


---------
New text: (Section 5.1.1.2)
---------

             SGP                             ASP1
              |                               |
              |<------------ASP Up------------|
              |----------ASP Up Ack---------->|
              |                               |
              |----NTFY(AS-INACTIVE)(RCn)---->|
              |                               |
              |<----REGISTER REQ(LRCn,RKn)----|  LRC: Local Routing
              |                               |       Key Id
              |----REGISTER RESP(LRCn,RCn)--->|   RK: Routing Key
              |                               |   RC: Routing Context
              |                               |
              |<------- ASP Active(RCn)-------|
              |-----ASP Active Ack (RCn)----->|
              |                               |
              |-----NTFY(AS-ACTIVE)(RCn)----->|
              |                               |



---------
Old text: (Section 5.1.1.3)
---------


	
             SGP                             ASP1
              |                               |
              |<------------ASP Up------------|
              |----------ASP Up Ack---------->|
              |                               |
              |<----REGISTER REQ(LRC1,RK1)----|  LRC: Local Routing
              |                               |       Context
              |----REGISTER RESP(LRC1,RC1)--->|   RK: Routing Key
              |                               |   RC: Routing Context
              |                               |
              |<------- ASP Active(RC1)-------|
              |-----ASP Active Ack (RC1)----->|
              |                               |
              |                               |
              |<----REGISTER REQ(LRCn,RKn)----|
              |                               |
              |----REGISTER RESP(LRCn,RCn)--->|
              |                               |
              |                               |
              |<------- ASP Active(RCn)-------|
              |-----ASP Active Ack (RCn)----->|
              |                               |


---------
New text: (Section 5.1.1.3)
---------


	
             SGP                             ASP1
              |                               |
              |<------------ASP Up------------|
              |----------ASP Up Ack---------->|
              |                               |
              |------NOTIFY(AS-INACTIVE)----->|
              |                               |
              |<----REGISTER REQ(LRC1,RK1)----|  LRC: Local Routing
              |                               |       Key Id
              |----REGISTER RESP(LRC1,RC1)--->|   RK: Routing Key
              |                               |   RC: Routing Context
              |                               |
              |<------- ASP Active(RC1)-------|
              |-----ASP Active Ack (RC1)----->|
              |                               |
              |----NOTIFY(AS-ACTIVE)(RC1)---->|
              |                               |
              ~                               ~
              |                               |
              |<----REGISTER REQ(LRCn,RKn)----|
              |                               |
              |----REGISTER RESP(LRCn,RCn)--->|
              |                               |
              |                               |
              |<------- ASP Active(RCn)-------|
              |-----ASP Active Ack (RCn)----->|
              |                               |
              |----NOTIFY(AS-ACTIVE)(RCn)---->|
              |                               |


---------
Old text: (Section 5.1.1.4)
---------



               SGP                             ASP1
                |                               |
                |<------------ASP Up------------|
                |----------ASP Up Ack---------->|
                |                               |
                |<---REGISTER REQ({LRC1,RK1},---|
                |                   ...,        |
                |                 {LRCn,RKn}),--|
                |                               |
                |---REGISTER RESP({LRC1,RC1},-->|
                |                  ...,         |
                |                 (LRCn,RCn})   |
                |                               |
                |<------- ASP Active(RC1)-------|
                |-----ASP Active Ack (RC1)----->|
                |                               |
                :                               :
                :                               :
                |                               |
                |<------- ASP Active(RCn)-------|
                |-----ASP Active Ack (RCn)----->|
                |                               |

---------
New text: (Section 5.1.1.4)
---------


               SGP                             ASP1
                |                               |
                |<------------ASP Up------------|
                |----------ASP Up Ack---------->|
                |                               |
                |------NOTIFY(AS-INACTIVE)----->|
                |                               |
                |                               |
                |<---REGISTER REQ({LRC1,RK1},   |
                |                   ...,        |
                |                 {LRCn,RKn}),--|
                |                               |
                |---REGISTER RESP({LRC1,RC1},-->|
                |                  ...,         |
                |                 (LRCn,RCn})   |
                |                               |
                |<------- ASP Active(RC1)-------|
                |-----ASP Active Ack (RC1)----->|
                |                               |
                |----NOTIFY(AS-ACTIVE)(RC1)---->|
                |                               |
                :                               :
                :                               :
                |                               |
                |<------- ASP Active(RCn)-------|
                |-----ASP Active Ack (RCn)----->|
                |                               |
                |----NOTIFY(AS-ACTIVE)(RCn)---->|
                |                               |







---------
Old text: (Section 5.1.2)
---------

      SGP                      ASP1                       ASP2
       |                        |                          |
       |<--------ASP Up---------|                          |
       |-------ASP Up Ack------>|                          |
       |                        |                          |
       |<----------------------------ASP Up----------------|
       |----------------------------ASP Up Ack------------>|
       |                        |                          |
       |                        |                          |
       |<-------ASP Active------|                          |
       |------ASP Active Ack--->|                          |
       |                        |                          |

---------
New text: (Section 5.1.2)
---------


      SGP                      ASP1                       ASP2
       |                        |                          |
       |<--------ASP Up---------|                          |
       |-------ASP Up Ack------>|                          |
       |                        |                          |
       |--NOTIFY(AS-INACTIVE)-->|                          |
       |                        |                          |
       |<----------------------------ASP Up----------------|
       |----------------------------ASP Up Ack------------>|
       |                        |                          |
       |                        |                          |
       |<-------ASP Active------|                          |
       |------ASP Active Ack--->|                          |
       |                        |                          |
       |---NOTIFY(AS-ACTIVE)--->|                          |
       |--------------------------NOTIFY(AS-ACTIVE)------->|
       |                        |                          |






---------
Old text: (Section 5.1.3)
---------

     OLD:
      SGP                      ASP1                       ASP2
       |                        |                          |
       |<---------ASP Up--------|                          |
       |--------ASP Up Ack----->|                          |
       |                        |                          |
       |<-----------------------------ASP Up---------------|
       |----------------------------ASP Up Ack------------>|
       |                        |                          |
       |                        |                          |
       |<--ASP Active (Ldshr)---|                          |
       |-----ASP-Active Ack---->|                          |
       |                        |                          |
       |---------------------------NOTIFY (AS-ACTIVE------>|
       |                        |                          |
       |<---------------------------ASP Active (Ldshr)-----|
       |------------------------------ASP Active Ack------>|
       |                        |                          |


---------
New text: (Section 5.1.3)
---------



      SGP                      ASP1                       ASP2
       |                        |                          |
       |<---------ASP Up--------|                          |
       |--------ASP Up Ack----->|                          |
       |                        |                          |
       |--NOTIFY(AS-INACTIVE)-->|                          |
       |                        |                          |
       |<-----------------------------ASP Up---------------|
       |----------------------------ASP Up Ack------------>|
       |                        |                          |
       |<--ASP Active (Ldshr)---|                          |
       |-----ASP-Active Ack---->|                          |
       |                        |                          |
       |---NOTIFY (AS-ACTIVE)-->|                          |
       |-----------------------------NOTIFY(AS-ACTIVE)---->|
       |                        |                          |
       |<---------------------------ASP Active (Ldshr)-----|
       |------------------------------ASP Active Ack------>|
       |                        |                          |


---------
Old text: (Section 5.1.4)
---------


     SGP                 ASP1                ASP2                ASP3
       |                   |                   |                   |
       |<------ASP Up------|                   |                   |
       |-----ASP Up Ack--->|                   |                   |
       |                   |                   |                   |
       |<-------------------------ASP Up-------|                   |
       |------------------------ASP Up Ack---->|                   |
       |                   |                   |                   |
       |<--------------------------------------------ASP Up--------|
       |--------------------------------------------ASP Up Ack---->|
       |                   |                   |                   |
       |                   |                   |                   |
       |<--ASP Act (Ldshr)-|                   |                   |
       |----ASP Act Ack--->|                   |                   |
       |                   |                   |                   |
       |                   |                   |                   |
       |<-------------------ASP Act. (Ldshr)---|                   |
       |----------------------ASP Act Ack----->|                   |
       |                   |                   |                   |
       |---------Notify (AS-ACTIVE)----------->|                   |
       |----------------------Notify (AS-ACTIVE)------------------>|


---------
New text: (Section 5.1.4)
---------	



     SGP                 ASP1                ASP2                ASP3
       |                   |                   |                   |
       |<------ASP Up------|                   |                   |
       |-----ASP Up Ack--->|                   |                   |
       |                   |                   |                   |
       |<-------------------------ASP Up-------|                   |
       |------------------------ASP Up Ack---->|                   |
       |                   |                   |                   |
       |NTFY(AS-INACTIVE)->|                   |                   |
       |------------------NOTIFY(AS-INACTIVE)->|                   |
       |                   |                   |                   |
       |<--------------------------------------------ASP Up--------|
       |--------------------------------------------ASP Up Ack---->|
       |                   |                   |                   |
       |                   |                   |                   |
       |<--ASP Act (Ldshr)-|                   |                   |
       |----ASP Act Ack--->|                   |                   |
       |                   |                   |                   |
       |                   |                   |                   |
       |<-------------------ASP Act. (Ldshr)---|                   |
       |----------------------ASP Act Ack----->|                   |
       |                   |                   |                   |
       |--NTFY(AS-ACTIVE)->|                   |                   |
       |--------------------NOTIFY(AS-ACTIVE)->|                   |
       |----------------------------------------NOTIFY(AS-ACTIVE)->|
       |                   |                   |                   |
       |                   |                   |                   |

---------
Old text: (Section 5.2.3)
---------	


     SGP                 ASP1                ASP2                ASP3
       |                   |                   |                   |
       |<----ASP Inact.----|                   |                   |
       |---ASP Inact Ack-->|                   |                   |
       |                   |                   |                   |
       |--------------------------------NTFY(Ins. ASPs)----------->|
       |                   |                   |                   |
       |<----------------------------------------ASP Act (Ldshr)---|
       |------------------------------------------ASP Act (Ack)--->|
       |                   |                   |                   |


---------
New text: (Section 5.2.3)
---------	


     SGP                 ASP1                ASP2                ASP3
       |                   |                   |                   |
       |<----ASP Inact.----|                   |                   |
       |---ASP Inact Ack-->|                   |                   |
       |                   |                   |                   |
       |-NTFY(AS-PENDING)->|                   |                   |
       |-------------------NOTIFY(AS-PENDING)->|                   |
       |---------------------------------------NOTIFY(AS-PENDING)->|
       |---------------------------------------NOTIFY(Ins. ASPs)-->|
       |                   |                   |                   |
       |                   |                   |                   |
       |<----------------------------------------ASP Act (Ldshr)---|
       |------------------------------------------ASP Act (Ack)--->|
       |                   |                   |                   |
       |-NTFY(AS-ACTIVE)-->|                   |                   |
       |-------------------NOTIFY(AS-ACTIVE)-->|                   |
       |---------------------------------------NOTIFY(AS-ACTIVE)-->|
       |                   |                   |                   |
       |                   |                   |                   |


 

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



From exim@www1.ietf.org  Thu Jun 19 07:41:07 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09845
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Jun 2003 07:41:07 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5JBeci09176
	for sigtran-archive@odin.ietf.org; Thu, 19 Jun 2003 07:40:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Sxd7-0001if-Br; Thu, 19 Jun 2003 07:31:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SxLm-00011G-NL
	for sigtran@optimus.ietf.org; Thu, 19 Jun 2003 07:13:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08641
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 07:13:03 -0400 (EDT)
From: kakaul@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SxJV-0001jX-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 07:10:45 -0400
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SxJQ-0001jP-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 07:10:40 -0400
Received: from hindon.hss.co.in (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h5JB9fY14416
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 16:39:42 +0530 (IST)
Received: from ultra.hss.co.in (ultra [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h5JB9Z914389;
	Thu, 19 Jun 2003 16:39:35 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h5JBD4L01916;
	Thu, 19 Jun 2003 16:43:04 +0530 (IST)
Subject: RE: [Sigtran] M3UA IG: NTFY & Examples Section proposal
To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
Cc: sigtran@ietf.org, Tolga Asveren <tolga_asveren@yahoo.com>
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OFDD4A77DC.88E83FCC-ON65256D4A.003C8CE8@hss.hns.com>
Date: Thu, 19 Jun 2003 16:37:55 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 19/06/2003
 04:37:00 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>





Hi Javier,
  Changes are fine but there is one minor comment that notification of AS
(INACTIVE) should be send after REGISTER RESP message, because AS at SG is
created after successful registration procedure of the routing key, so AS
state change notification message should be sent when AS is actually
created at SG and moves directly into INACTIVE state after successful
registration procedure.
Regards
Kamesh




"Javier Pastor-Balbas (ECE)"
<javier.pastor-balbas@ece.ericsson.se>@ietf.org on 06/19/2003 02:59:05 PM

Sent by:    sigtran-admin@ietf.org


To:    Kamesh Kaul/HSS@HSS, Tolga Asveren <tolga_asveren@yahoo.com>
cc:    sigtran@ietf.org

Subject:    RE: [Sigtran] M3UA IG: NTFY & Examples Section proposal


Hi guys,

Here I include a proposed text for the Examples section where all the NTFY
are included. Check I didn't miss any. I've also changed LRC meaning
explanation to "Local RK Id".

Thanks // Javier.


---------------------------oOo--------------------------


---------
Old text: (Section 5)
---------

NOTE: Not all the Notify messages that are appropriate per the Notify
procedures are shown in these examples.


---------
New text: (Section 5)
---------

-


---------
Old text: (Section 5.1.1.1)
---------

              SGP                             ASP1
               |                               |
               |<-------------ASP Up-----------|
               |-----------ASP Up Ack--------->|
               |                               |
               |<------- ASP Active(RCn)-------|  RC: Routing Context
               |-----ASP Active Ack (RCn)----->|      (optional)
               |                               |
               |-----NTFY(AS-ACTIVE)(RCn)----->|
               |                               |


---------
New text: (Section 5.1.1.1)
---------


              SGP                             ASP1
               |                               |
               |<-------------ASP Up-----------|
               |-----------ASP Up Ack--------->|
               |                               |
               |-----NTFY(AS-INACTIVE)(RCn)--->|
               |                               |
               |<------- ASP Active(RCn)-------|  RC: Routing Context
               |-----ASP Active Ack (RCn)----->|      (optional)
               |                               |
               |-----NTFY(AS-ACTIVE)(RCn)----->|
               |                               |
---------
Old text: (Section 5.1.1.2)
---------


             SGP                             ASP1
              |                               |
              |<------------ASP Up------------|
              |----------ASP Up Ack---------->|
              |                               |
              |<----REGISTER REQ(LRCn,RKn)----|  LRC: Local Routing
              |                               |       Context
              |----REGISTER RESP(LRCn,RCn)--->|   RK: Routing Key
              |                               |   RC: Routing Context
              |                               |
              |<------- ASP Active(RCn)-------|
              |-----ASP Active Ack (RCn)----->|
              |                               |
              |-----NTFY(AS-ACTIVE)(RCn)----->|
              |                               |


---------
New text: (Section 5.1.1.2)
---------

             SGP                             ASP1
              |                               |
              |<------------ASP Up------------|
              |----------ASP Up Ack---------->|
              |                               |
              |----NTFY(AS-INACTIVE)(RCn)---->|
              |                               |
              |<----REGISTER REQ(LRCn,RKn)----|  LRC: Local Routing
              |                               |       Key Id
              |----REGISTER RESP(LRCn,RCn)--->|   RK: Routing Key
              |                               |   RC: Routing Context
              |                               |
              |<------- ASP Active(RCn)-------|
              |-----ASP Active Ack (RCn)----->|
              |                               |
              |-----NTFY(AS-ACTIVE)(RCn)----->|
              |                               |



---------
Old text: (Section 5.1.1.3)
---------



             SGP                             ASP1
              |                               |
              |<------------ASP Up------------|
              |----------ASP Up Ack---------->|
              |                               |
              |<----REGISTER REQ(LRC1,RK1)----|  LRC: Local Routing
              |                               |       Context
              |----REGISTER RESP(LRC1,RC1)--->|   RK: Routing Key
              |                               |   RC: Routing Context
              |                               |
              |<------- ASP Active(RC1)-------|
              |-----ASP Active Ack (RC1)----->|
              |                               |
              |                               |
              |<----REGISTER REQ(LRCn,RKn)----|
              |                               |
              |----REGISTER RESP(LRCn,RCn)--->|
              |                               |
              |                               |
              |<------- ASP Active(RCn)-------|
              |-----ASP Active Ack (RCn)----->|
              |                               |


---------
New text: (Section 5.1.1.3)
---------



             SGP                             ASP1
              |                               |
              |<------------ASP Up------------|
              |----------ASP Up Ack---------->|
              |                               |
              |------NOTIFY(AS-INACTIVE)----->|
              |                               |
              |<----REGISTER REQ(LRC1,RK1)----|  LRC: Local Routing
              |                               |       Key Id
              |----REGISTER RESP(LRC1,RC1)--->|   RK: Routing Key
              |                               |   RC: Routing Context
              |                               |
              |<------- ASP Active(RC1)-------|
              |-----ASP Active Ack (RC1)----->|
              |                               |
              |----NOTIFY(AS-ACTIVE)(RC1)---->|
              |                               |
              ~                               ~
              |                               |
              |<----REGISTER REQ(LRCn,RKn)----|
              |                               |
              |----REGISTER RESP(LRCn,RCn)--->|
              |                               |
              |                               |
              |<------- ASP Active(RCn)-------|
              |-----ASP Active Ack (RCn)----->|
              |                               |
              |----NOTIFY(AS-ACTIVE)(RCn)---->|
              |                               |


---------
Old text: (Section 5.1.1.4)
---------



               SGP                             ASP1
                |                               |
                |<------------ASP Up------------|
                |----------ASP Up Ack---------->|
                |                               |
                |<---REGISTER REQ({LRC1,RK1},---|
                |                   ...,        |
                |                 {LRCn,RKn}),--|
                |                               |
                |---REGISTER RESP({LRC1,RC1},-->|
                |                  ...,         |
                |                 (LRCn,RCn})   |
                |                               |
                |<------- ASP Active(RC1)-------|
                |-----ASP Active Ack (RC1)----->|
                |                               |
                :                               :
                :                               :
                |                               |
                |<------- ASP Active(RCn)-------|
                |-----ASP Active Ack (RCn)----->|
                |                               |

---------
New text: (Section 5.1.1.4)
---------


               SGP                             ASP1
                |                               |
                |<------------ASP Up------------|
                |----------ASP Up Ack---------->|
                |                               |
                |------NOTIFY(AS-INACTIVE)----->|
                |                               |
                |                               |
                |<---REGISTER REQ({LRC1,RK1},   |
                |                   ...,        |
                |                 {LRCn,RKn}),--|
                |                               |
                |---REGISTER RESP({LRC1,RC1},-->|
                |                  ...,         |
                |                 (LRCn,RCn})   |
                |                               |
                |<------- ASP Active(RC1)-------|
                |-----ASP Active Ack (RC1)----->|
                |                               |
                |----NOTIFY(AS-ACTIVE)(RC1)---->|
                |                               |
                :                               :
                :                               :
                |                               |
                |<------- ASP Active(RCn)-------|
                |-----ASP Active Ack (RCn)----->|
                |                               |
                |----NOTIFY(AS-ACTIVE)(RCn)---->|
                |                               |







---------
Old text: (Section 5.1.2)
---------

      SGP                      ASP1                       ASP2
       |                        |                          |
       |<--------ASP Up---------|                          |
       |-------ASP Up Ack------>|                          |
       |                        |                          |
       |<----------------------------ASP Up----------------|
       |----------------------------ASP Up Ack------------>|
       |                        |                          |
       |                        |                          |
       |<-------ASP Active------|                          |
       |------ASP Active Ack--->|                          |
       |                        |                          |

---------
New text: (Section 5.1.2)
---------


      SGP                      ASP1                       ASP2
       |                        |                          |
       |<--------ASP Up---------|                          |
       |-------ASP Up Ack------>|                          |
       |                        |                          |
       |--NOTIFY(AS-INACTIVE)-->|                          |
       |                        |                          |
       |<----------------------------ASP Up----------------|
       |----------------------------ASP Up Ack------------>|
       |                        |                          |
       |                        |                          |
       |<-------ASP Active------|                          |
       |------ASP Active Ack--->|                          |
       |                        |                          |
       |---NOTIFY(AS-ACTIVE)--->|                          |
       |--------------------------NOTIFY(AS-ACTIVE)------->|
       |                        |                          |






---------
Old text: (Section 5.1.3)
---------

     OLD:
      SGP                      ASP1                       ASP2
       |                        |                          |
       |<---------ASP Up--------|                          |
       |--------ASP Up Ack----->|                          |
       |                        |                          |
       |<-----------------------------ASP Up---------------|
       |----------------------------ASP Up Ack------------>|
       |                        |                          |
       |                        |                          |
       |<--ASP Active (Ldshr)---|                          |
       |-----ASP-Active Ack---->|                          |
       |                        |                          |
       |---------------------------NOTIFY (AS-ACTIVE------>|
       |                        |                          |
       |<---------------------------ASP Active (Ldshr)-----|
       |------------------------------ASP Active Ack------>|
       |                        |                          |


---------
New text: (Section 5.1.3)
---------



      SGP                      ASP1                       ASP2
       |                        |                          |
       |<---------ASP Up--------|                          |
       |--------ASP Up Ack----->|                          |
       |                        |                          |
       |--NOTIFY(AS-INACTIVE)-->|                          |
       |                        |                          |
       |<-----------------------------ASP Up---------------|
       |----------------------------ASP Up Ack------------>|
       |                        |                          |
       |<--ASP Active (Ldshr)---|                          |
       |-----ASP-Active Ack---->|                          |
       |                        |                          |
       |---NOTIFY (AS-ACTIVE)-->|                          |
       |-----------------------------NOTIFY(AS-ACTIVE)---->|
       |                        |                          |
       |<---------------------------ASP Active (Ldshr)-----|
       |------------------------------ASP Active Ack------>|
       |                        |                          |


---------
Old text: (Section 5.1.4)
---------


     SGP                 ASP1                ASP2                ASP3
       |                   |                   |                   |
       |<------ASP Up------|                   |                   |
       |-----ASP Up Ack--->|                   |                   |
       |                   |                   |                   |
       |<-------------------------ASP Up-------|                   |
       |------------------------ASP Up Ack---->|                   |
       |                   |                   |                   |
       |<--------------------------------------------ASP Up--------|
       |--------------------------------------------ASP Up Ack---->|
       |                   |                   |                   |
       |                   |                   |                   |
       |<--ASP Act (Ldshr)-|                   |                   |
       |----ASP Act Ack--->|                   |                   |
       |                   |                   |                   |
       |                   |                   |                   |
       |<-------------------ASP Act. (Ldshr)---|                   |
       |----------------------ASP Act Ack----->|                   |
       |                   |                   |                   |
       |---------Notify (AS-ACTIVE)----------->|                   |
       |----------------------Notify (AS-ACTIVE)------------------>|


---------
New text: (Section 5.1.4)
---------



     SGP                 ASP1                ASP2                ASP3
       |                   |                   |                   |
       |<------ASP Up------|                   |                   |
       |-----ASP Up Ack--->|                   |                   |
        |                   |                   |                   |
       |<-------------------------ASP Up-------|                   |
       |------------------------ASP Up Ack---->|                   |
       |                   |                   |                   |
       |NTFY(AS-INACTIVE)->|                   |                   |
       |------------------NOTIFY(AS-INACTIVE)->|                   |
       |                   |                   |                   |
       |<--------------------------------------------ASP Up--------|
       |--------------------------------------------ASP Up Ack---->|
       |                   |                   |                   |
       |                   |                   |                   |
       |<--ASP Act (Ldshr)-|                   |                   |
       |----ASP Act Ack--->|                   |                   |
       |                   |                   |                   |
       |                   |                   |                   |
       |<-------------------ASP Act. (Ldshr)---|                   |
       |----------------------ASP Act Ack----->|                   |
       |                   |                   |                   |
       |--NTFY(AS-ACTIVE)->|                   |                   |
       |--------------------NOTIFY(AS-ACTIVE)->|                   |
       |----------------------------------------NOTIFY(AS-ACTIVE)->|
       |                   |                   |                   |
       |                   |                   |                   |

---------
Old text: (Section 5.2.3)
---------


     SGP                 ASP1                ASP2                ASP3
       |                   |                   |                   |
       |<----ASP Inact.----|                   |                   |
       |---ASP Inact Ack-->|                   |                   |
       |                   |                   |                   |
       |--------------------------------NTFY(Ins. ASPs)----------->|
       |                   |                   |                   |
       |<----------------------------------------ASP Act (Ldshr)---|
       |------------------------------------------ASP Act (Ack)--->|
       |                   |                   |                   |


---------
New text: (Section 5.2.3)
---------


     SGP                 ASP1                ASP2                ASP3
       |                   |                   |                   |
       |<----ASP Inact.----|                   |                   |
       |---ASP Inact Ack-->|                   |                   |
       |                   |                   |                   |
       |-NTFY(AS-PENDING)->|                   |                   |
       |-------------------NOTIFY(AS-PENDING)->|                   |
       |---------------------------------------NOTIFY(AS-PENDING)->|
       |---------------------------------------NOTIFY(Ins. ASPs)-->|
       |                   |                   |                   |
       |                   |                   |                   |
       |<----------------------------------------ASP Act (Ldshr)---|
       |------------------------------------------ASP Act (Ack)--->|
       |                   |                   |                   |
       |-NTFY(AS-ACTIVE)-->|                   |                   |
       |-------------------NOTIFY(AS-ACTIVE)-->|                   |
       |---------------------------------------NOTIFY(AS-ACTIVE)-->|
       |                   |                   |                   |
       |                   |                   |                   |




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



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



From exim@www1.ietf.org  Thu Jun 19 07:47:03 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10335
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Jun 2003 07:47:03 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5JBkYQ10070
	for sigtran-archive@odin.ietf.org; Thu, 19 Jun 2003 07:46:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Sxd7-0001in-PC; Thu, 19 Jun 2003 07:31:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SxNY-00011g-4y
	for sigtran@optimus.ietf.org; Thu, 19 Jun 2003 07:14:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08673
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 07:14:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SxLG-0001jm-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 07:12:34 -0400
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SxLG-0001ji-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 07:12:34 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h5JBEOwA026408
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 06:14:24 -0500 (CDT)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h5JBDf1C022048
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 06:13:41 -0500 (CDT)
Date: Thu, 19 Jun 2003 06:13:41 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
In-Reply-To: <20030618123306.D31402@openss7.org>
Message-ID: <Pine.SOL.4.10.10306190609190.9866-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


Brian,
 
I remeber the following topics were discussged a few
months back.
 
1.'n' is mantatory at start case.
2. 'n' # of ASPs sufficient to handle maximum engineered load.
3.When # of ASPs < n (where n > 0) , ASP state should be ACTIVE(not
pending)
 
I dont know whether consensus is made or not.
 
My support is to make 'n' as mandatory at start case as section
5.1.4 of RFC, where it says
 
if n=2
 
...............................................a minimum
of two ASPs are required to handle the total traffic load (2+1
sparing).
 
Once again i am not saying that we should make this as a consensus, i just
conveyed my idea thats all.
 
--Samuel


  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******



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



From exim@www1.ietf.org  Thu Jun 19 08:59:51 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16073
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Jun 2003 08:59:50 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5JCxM524820
	for sigtran-archive@odin.ietf.org; Thu, 19 Jun 2003 08:59:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Sygv-0005YW-U7; Thu, 19 Jun 2003 08:39:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Sy2G-00037Z-0D
	for sigtran@optimus.ietf.org; Thu, 19 Jun 2003 07:57:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10723
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 07:56:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sxzy-00026H-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 07:54:38 -0400
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sxzx-00024i-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 07:54:37 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h5JBuOwA029052;
	Thu, 19 Jun 2003 06:56:24 -0500 (CDT)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h5JBuA1C004783;
	Thu, 19 Jun 2003 06:56:10 -0500 (CDT)
Date: Thu, 19 Jun 2003 06:56:10 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
In-Reply-To: <20030619013818.A10362@openss7.org>
Message-ID: <Pine.SOL.4.10.10306190614240.9866-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


Brian,


                        +----+                  +-----+
                        |STP-|------------------| ASP1| SCP (1-1-1)
     +------------------| SG |------+           +-----+
     |                  +----+      |  
     |                              |           +-----+
     |                              +-----------| ASP2| MGC(2-2-2)
     |                                          +-----+
     |                      
 Conventional SS7



Consider a call which needs to access database (ASP1) and then
to be routed to ASP2.
In this case if we configure n=2 and 'n' as a mandatory,then
the call will pass. This same will fail if n is not a mandatory
as SG started processing the traffic as soon as one of the ASPs
becomes available.The unavailability of another ASP will
fail the call.

So we need to have certain restrictions to make 'n' as mandatory
to process the call successfully.

--Samuel


On Thu, 19 Jun 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> 'n' (as agreed by concensus, and included in the new IG text as well) is the
> number of ASP required to handle the "maximum engineered load", not the normal
> load, or event the expected load.  So, for an ISUP bearing system, if it is
> not Christmas or Mother's day, and there is not a significant backlog of
> reattempt traffic (extended outage), the system can come up with less than 'n'
> processors, as 'n' is defined.  Therefore, refusing to start or restart an
> AS with less than 'n' active ASPs is foolish.
> 
> Setting n to 1, as you suggest, would be incorrect.  1 ASP cannot handle the
> "maximum engineered load".  In the example, it takes 256 ASPs to handle the
> "maximum engineered load" (e.g. busy-hour on Mother's Day).  But for the other
> 340 some days of the year, some lesser number of ASPs is sufficient, and 255
> ASPs is surely sufficient.
> 
> Not permitting the SG to start or restart with less than 'n' ASPs active
> is a bad thing for carrier class systems.
> 
> I cannot agree with the change on these grounds.
> 
> --brian
> 
> 
> Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 19 Jun 2003 00:42:05)
> > 
> > Brian,
> > 
> > 
> > On Wed, 18 Jun 2003, Brian F. G. Bidulock wrote:
> > 
> > > Samuel,
> > > 
> > > Samuel Dur D. Jeyaseelan wrote:                                                     (Wed, 18 Jun 2003 22:48:23)
> > > > > > > 
> > > > > > > I agree.   That is what is provided for in the RFC.  However, section 3.15 of
> > > > > > > the IG would require the SG to stop traffic when n < 2.  So, it must be
> > > > > > > struck.
> > > > > > > 
> > > > > > > --brian
> > > > > > [Samuel] Does new IG stop the traffic when n < 2 ?
> > > > > 
> > > > > Yes, it does.  On restart.
> > > > > 
> > > > Yes thats what everybody agrees that on start and restart case 'n' number
> > > > of ASPs to be in ACTIVE state.
> > > 
> > > Disagree wholeheartedly.  And this was never agreed.
> > > 
> > > What was agreed (except for Tolga) was that the RFC allowed the SG to either
> > > activate on one ASP or wait for 'n' and withhold NTFY(AS-ACTIVE) which was
> > > sufficient for both start and restart cases.
> > > 
> > section 5.4.1 says that minimum 'n' number of ASPs are required to handle 
> > total traffic load.Here my understanding is, craft person knows the
> > incoming traffic capacity based on some kind of 'traffic measurement
> > analysis',
> > and the same time craft person knows, to handle this incoming traffic an
> > SGP requires 'n' ASPs.Here the point is craft person can not maintain 'n'
> > ASPs to be in ACTIVE state throughout the traffic period but at least he
> > can make sure 'n' ASPs are ACTIVE when (initally) SG comes up.
> > 
> > > If an outage has been for a brief period and was not congestion related, there
> > > is no reason why traffic cannot be started on the first active ASP, or under
> > > emergency conditions for that matter.
> > This may happen while SGP is processing the load but it may not happen in
> > the beginning and a good network configuration should not allow these
> > kinds of problems to happen in the beginning.
> > 
> > > The start, restart and shutdown decisions were discussed in detail on the
> > > list.  Whether the SG waits for 1 or 'n' is an IMPLEMENTATION and OPERATIONAL
> > > decision.  The existing RFC provides for this in saying that the AS-ACTIVE
> > > state implies that "at least one" ASP is in the ASP-ACTIVE state for the AS.
> > > Also the RFC states that the SGP should withhold the NTFY(AS-ACTIVE) until 'n'
> > > ASPs are active if it is going to wait for 'n' ASPs (as it MAY do).  And it
> > > also says that the ASPs should coordinate amoungst themselves to ensure that
> > > 'n' are active.
> > This is left to the decision of the craft person, this case he can
> > configure n=1.
> > > 
> > > Let me give you an example of the negative effect of this change:  An SG is
> > > configured with n=256.  There are 257 ASPs.  2 are dead.  The AS will never
> > > activate.  Some carrier class system...
> > > 
> > If n=256, it is the responsibility of the operator to make sure and bring
> > up 256 ASPs to ACTIVE state at least in the beginning.
> > 
> > > Contrast this where, soley at the SG implementer's discretion, the SG
> > > implementor sets a timer when the first ASP goes ASP-ACTIVE for the AS.  If
> > > the other 255 are not active by the time this timer expires, it sends
> > > NTFY(AS-ACTIVE) and starts traffic.  This system will always come up in
> > > contrast to the above that will not.  The RFC allows for this system, the
> > > new IG text does not.
> > > 
> > > The new IG text would have you implement the system that will never come up
> > > with 2 ASPs out of service.  The RFC does not.
> > 
> > section 5.1.4
> >    n+k case
> >    --------
> >    This scenario shows the example M3UA message flows for the
> >    establishment of traffic between an SGP and three ASPs in the same
> >    Application Server, where two of the ASPs are brought to the state
> >    ASP-ACTIVE and subsequently share the load.  In this case, a minimum
> >    of two ASPs are required to handle the total traffic load (2+1
> >    sparing).
> > 
> > still RFC says '... a minimum of two ASPs are required to handle the total
> > traffic load ....'
> > 
> > > 
> > > I you wan to explain things in the IG, go ahead, but the proposed text does
> > > not do that.  The proposed text makes changes to the normal and correct
> > > operation as laid out in the RFC and starts making implementation and
> > > operational decisions for the SG designer that it must not.
> > > 
> > > --brian
> > > 
> > 
> > I have conveyed my understanding to all. Otherwise in order to conclude 
> > this issue we can go for polling.
> > 
> > --Samuel
> > > -- 
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > > 
> > 
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 


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



From exim@www1.ietf.org  Thu Jun 19 09:22:21 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16978
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Jun 2003 09:22:21 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5JDLrd31052
	for sigtran-archive@odin.ietf.org; Thu, 19 Jun 2003 09:21:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SyzJ-0006N3-Rq; Thu, 19 Jun 2003 08:58:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SyVP-0004cI-6t
	for sigtran@optimus.ietf.org; Thu, 19 Jun 2003 08:27:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12641
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 08:27:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SyT7-0002hP-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 08:24:45 -0400
Received: from web12808.mail.yahoo.com ([216.136.174.43])
	by ietf-mx with smtp (Exim 4.12)
	id 19SyT2-0002gf-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 08:24:44 -0400
Message-ID: <20030619122646.20025.qmail@web12808.mail.yahoo.com>
Received: from [208.255.120.2] by web12808.mail.yahoo.com via HTTP; Thu, 19 Jun 2003 05:26:46 PDT
Date: Thu, 19 Jun 2003 05:26:46 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] Re: M3UA Notify message
To: sigtran@ietf.org
In-Reply-To: <20030619013818.A10362@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Samuel,
> 
> 'n' (as agreed by concensus, and included in the new
> IG text as well) is the
> number of ASP required to handle the "maximum
> engineered load", not the normal
> load, or event the expected load.  So, for an ISUP
> bearing system, if it is
> not Christmas or Mother's day, and there is not a
> significant backlog of
> reattempt traffic (extended outage), the system can
> come up with less than 'n'
> processors, as 'n' is defined.  Therefore, refusing
> to start or restart an
> AS with less than 'n' active ASPs is foolish.
> 
> Setting n to 1, as you suggest, would be incorrect. 
> 1 ASP cannot handle the
> "maximum engineered load".  In the example, it takes
> 256 ASPs to handle the
> "maximum engineered load" (e.g. busy-hour on
> Mother's Day).  But for the other
> 340 some days of the year, some lesser number of
> ASPs is sufficient, and 255
> ASPs is surely sufficient.
[TOLGA]For this case, IMO n=1 (or whatever is the
number of ASPs, which should be ACTIVE at minimum)is
correct. I don't interprete n as number of maximum
ASPs, which can be ACTIVE at any given time. n is the
number of ASPs, which should be ACTIVE, so that AS
switches to ACTIVE state. For example, if n=3, this
IMO does not mean that I can't have 256 ASPs ACTIVE at
any given time. So, for your example, you set
n=sufficient number of ASPs(something less than 256). 
Maybe using the term n+k for this kind of operation is
what you don't like?
> 
> Not permitting the SG to start or restart with less
> than 'n' ASPs active
> is a bad thing for carrier class systems.
> 
> I cannot agree with the change on these grounds.
> 
> --brian
> 
> 
> Samuel Dur D. Jeyaseelan wrote:                     
>                                (Thu, 19 Jun 2003
> 00:42:05)
> > 
> > Brian,
> > 
> > 
> > On Wed, 18 Jun 2003, Brian F. G. Bidulock wrote:
> > 
> > > Samuel,
> > > 
> > > Samuel Dur D. Jeyaseelan wrote:                 
>                                    (Wed, 18 Jun 2003
> 22:48:23)
> > > > > > > 
> > > > > > > I agree.   That is what is provided for
> in the RFC.  However, section 3.15 of
> > > > > > > the IG would require the SG to stop
> traffic when n < 2.  So, it must be
> > > > > > > struck.
> > > > > > > 
> > > > > > > --brian
> > > > > > [Samuel] Does new IG stop the traffic when
> n < 2 ?
> > > > > 
> > > > > Yes, it does.  On restart.
> > > > > 
> > > > Yes thats what everybody agrees that on start
> and restart case 'n' number
> > > > of ASPs to be in ACTIVE state.
> > > 
> > > Disagree wholeheartedly.  And this was never
> agreed.
> > > 
> > > What was agreed (except for Tolga) was that the
> RFC allowed the SG to either
> > > activate on one ASP or wait for 'n' and withhold
> NTFY(AS-ACTIVE) which was
> > > sufficient for both start and restart cases.
> > > 
> > section 5.4.1 says that minimum 'n' number of ASPs
> are required to handle 
> > total traffic load.Here my understanding is, craft
> person knows the
> > incoming traffic capacity based on some kind of
> 'traffic measurement
> > analysis',
> > and the same time craft person knows, to handle
> this incoming traffic an
> > SGP requires 'n' ASPs.Here the point is craft
> person can not maintain 'n'
> > ASPs to be in ACTIVE state throughout the traffic
> period but at least he
> > can make sure 'n' ASPs are ACTIVE when (initally)
> SG comes up.
> > 
> > > If an outage has been for a brief period and was
> not congestion related, there
> > > is no reason why traffic cannot be started on
> the first active ASP, or under
> > > emergency conditions for that matter.
> > This may happen while SGP is processing the load
> but it may not happen in
> > the beginning and a good network configuration
> should not allow these
> > kinds of problems to happen in the beginning.
> > 
> > > The start, restart and shutdown decisions were
> discussed in detail on the
> > > list.  Whether the SG waits for 1 or 'n' is an
> IMPLEMENTATION and OPERATIONAL
> > > decision.  The existing RFC provides for this in
> saying that the AS-ACTIVE
> > > state implies that "at least one" ASP is in the
> ASP-ACTIVE state for the AS.
> > > Also the RFC states that the SGP should withhold
> the NTFY(AS-ACTIVE) until 'n'
> > > ASPs are active if it is going to wait for 'n'
> ASPs (as it MAY do).  And it
> > > also says that the ASPs should coordinate
> amoungst themselves to ensure that
> > > 'n' are active.
> > This is left to the decision of the craft person,
> this case he can
> > configure n=1.
> > > 
> > > Let me give you an example of the negative
> effect of this change:  An SG is
> > > configured with n=256.  There are 257 ASPs.  2
> are dead.  The AS will never
> > > activate.  Some carrier class system...
> > > 
> > If n=256, it is the responsibility of the operator
> to make sure and bring
> > up 256 ASPs to ACTIVE state at least in the
> beginning.
> > 
> > > Contrast this where, soley at the SG
> implementer's discretion, the SG
> > > implementor sets a timer when the first ASP goes
> ASP-ACTIVE for the AS.  If
> > > the other 255 are not active by the time this
> timer expires, it sends
> > > NTFY(AS-ACTIVE) and starts traffic.  This system
> will always come up in
> > > contrast to the above that will not.  The RFC
> allows for this system, the
> > > new IG text does not.
> > > 
> > > The new IG text would have you implement the
> system that will never come up
> > > with 2 ASPs out of service.  The RFC does not.
> > 
> > section 5.1.4
> >    n+k case
> >    --------
> >    This scenario shows the example M3UA message
> flows for the
> >    establishment of traffic between an SGP and
> three ASPs in the same
> >    Application Server, where two of the ASPs are
> brought to the state
> >    ASP-ACTIVE and subsequently share the load.  In
> this case, a minimum
> >    of two ASPs are required to handle the total
> traffic load (2+1
> >    sparing).
> > 
> > still RFC says '... a minimum of two ASPs are
> required to handle the total
> > traffic load ....'
> > 
> > > 
> > > I you wan to explain things in the IG, go ahead,
> but the proposed text does
> > > not do that.  The proposed text makes changes to
> the normal and correct
> > > operation as laid out in the RFC and starts
> making implementation and
> > > operational decisions for the SG designer that
> it must not.
> > > 
> > > --brian
> > > 
> > 
> > I have conveyed my understanding to all. Otherwise
> in order to conclude 
> > this issue we can go for polling.
> > 
> > --Samuel
> > > -- 
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > > 
> > 
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

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



From exim@www1.ietf.org  Thu Jun 19 09:25:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17135
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Jun 2003 09:25:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5JDP2831930
	for sigtran-archive@odin.ietf.org; Thu, 19 Jun 2003 09:25:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SzPR-0008Il-Jj; Thu, 19 Jun 2003 09:25:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SzPN-0008II-CJ
	for sigtran@optimus.ietf.org; Thu, 19 Jun 2003 09:24:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17126
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 09:24:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SzN4-0004Ak-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 09:22:34 -0400
Received: from falcon.ericsson.se ([193.180.251.52] helo=falcon.al.sw.ericsson.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SzN3-0004Ah-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 09:22:33 -0400
Received: from esealnt610.al.sw.ericsson.se (alteon-nat3.sw.ericsson.se [153.88.254.120])
	by falcon.al.sw.ericsson.se (8.12.9/8.12.9/WIREfire-1.6b) with ESMTP id h5JDPccv028289;
	Thu, 19 Jun 2003 15:25:38 +0200
Received: from ESEALNT745.al.sw.ericsson.se ([153.88.251.5]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id LYG2SKY5; Thu, 19 Jun 2003 15:26:41 +0200
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <HT92CC47>; Thu, 19 Jun 2003 15:23:46 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C72@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
To: "'kakaul@hss.hns.com'" <kakaul@hss.hns.com>
Cc: sigtran@ietf.org, Tolga Asveren <tolga_asveren@yahoo.com>
Subject: RE: [Sigtran] M3UA IG: NTFY & Examples Section proposal
Date: Thu, 19 Jun 2003 15:24:27 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Thanks Kamesh, 

Your statements are right when dynamic registering. I'll fixed it. 

Cheers // Javier.

> -----Original Message-----
> From: kakaul@hss.hns.com [mailto:kakaul@hss.hns.com]
> Sent: jueves, 19 de junio de 2003 13:08
> To: Javier Pastor-Balbas (ECE)
> Cc: sigtran@ietf.org; Tolga Asveren
> Subject: RE: [Sigtran] M3UA IG: NTFY & Examples Section proposal
> 
> 
> 
> 
> 
> 
> Hi Javier,
>   Changes are fine but there is one minor comment that 
> notification of AS
> (INACTIVE) should be send after REGISTER RESP message, 
> because AS at SG is
> created after successful registration procedure of the 
> routing key, so AS
> state change notification message should be sent when AS is actually
> created at SG and moves directly into INACTIVE state after successful
> registration procedure.
> Regards
> Kamesh
> 
> 
> 
> 
> "Javier Pastor-Balbas (ECE)"
> <javier.pastor-balbas@ece.ericsson.se>@ietf.org on 06/19/2003 
> 02:59:05 PM
> 
> Sent by:    sigtran-admin@ietf.org
> 
> 
> To:    Kamesh Kaul/HSS@HSS, Tolga Asveren <tolga_asveren@yahoo.com>
> cc:    sigtran@ietf.org
> 
> Subject:    RE: [Sigtran] M3UA IG: NTFY & Examples Section proposal
> 
> 
> Hi guys,
> 
> Here I include a proposed text for the Examples section where 
> all the NTFY
> are included. Check I didn't miss any. I've also changed LRC meaning
> explanation to "Local RK Id".
> 
> Thanks // Javier.
> 
> 
> ---------------------------oOo--------------------------
> 
> 
> ---------
> Old text: (Section 5)
> ---------
> 
> NOTE: Not all the Notify messages that are appropriate per the Notify
> procedures are shown in these examples.
> 
> 
> ---------
> New text: (Section 5)
> ---------
> 
> -
> 
> 
> ---------
> Old text: (Section 5.1.1.1)
> ---------
> 
>               SGP                             ASP1
>                |                               |
>                |<-------------ASP Up-----------|
>                |-----------ASP Up Ack--------->|
>                |                               |
>                |<------- ASP Active(RCn)-------|  RC: Routing Context
>                |-----ASP Active Ack (RCn)----->|      (optional)
>                |                               |
>                |-----NTFY(AS-ACTIVE)(RCn)----->|
>                |                               |
> 
> 
> ---------
> New text: (Section 5.1.1.1)
> ---------
> 
> 
>               SGP                             ASP1
>                |                               |
>                |<-------------ASP Up-----------|
>                |-----------ASP Up Ack--------->|
>                |                               |
>                |-----NTFY(AS-INACTIVE)(RCn)--->|
>                |                               |
>                |<------- ASP Active(RCn)-------|  RC: Routing Context
>                |-----ASP Active Ack (RCn)----->|      (optional)
>                |                               |
>                |-----NTFY(AS-ACTIVE)(RCn)----->|
>                |                               |
> ---------
> Old text: (Section 5.1.1.2)
> ---------
> 
> 
>              SGP                             ASP1
>               |                               |
>               |<------------ASP Up------------|
>               |----------ASP Up Ack---------->|
>               |                               |
>               |<----REGISTER REQ(LRCn,RKn)----|  LRC: Local Routing
>               |                               |       Context
>               |----REGISTER RESP(LRCn,RCn)--->|   RK: Routing Key
>               |                               |   RC: Routing Context
>               |                               |
>               |<------- ASP Active(RCn)-------|
>               |-----ASP Active Ack (RCn)----->|
>               |                               |
>               |-----NTFY(AS-ACTIVE)(RCn)----->|
>               |                               |
> 
> 
> ---------
> New text: (Section 5.1.1.2)
> ---------
> 
>              SGP                             ASP1
>               |                               |
>               |<------------ASP Up------------|
>               |----------ASP Up Ack---------->|
>               |                               |
>               |----NTFY(AS-INACTIVE)(RCn)---->|
>               |                               |
>               |<----REGISTER REQ(LRCn,RKn)----|  LRC: Local Routing
>               |                               |       Key Id
>               |----REGISTER RESP(LRCn,RCn)--->|   RK: Routing Key
>               |                               |   RC: Routing Context
>               |                               |
>               |<------- ASP Active(RCn)-------|
>               |-----ASP Active Ack (RCn)----->|
>               |                               |
>               |-----NTFY(AS-ACTIVE)(RCn)----->|
>               |                               |
> 
> 
> 
> ---------
> Old text: (Section 5.1.1.3)
> ---------
> 
> 
> 
>              SGP                             ASP1
>               |                               |
>               |<------------ASP Up------------|
>               |----------ASP Up Ack---------->|
>               |                               |
>               |<----REGISTER REQ(LRC1,RK1)----|  LRC: Local Routing
>               |                               |       Context
>               |----REGISTER RESP(LRC1,RC1)--->|   RK: Routing Key
>               |                               |   RC: Routing Context
>               |                               |
>               |<------- ASP Active(RC1)-------|
>               |-----ASP Active Ack (RC1)----->|
>               |                               |
>               |                               |
>               |<----REGISTER REQ(LRCn,RKn)----|
>               |                               |
>               |----REGISTER RESP(LRCn,RCn)--->|
>               |                               |
>               |                               |
>               |<------- ASP Active(RCn)-------|
>               |-----ASP Active Ack (RCn)----->|
>               |                               |
> 
> 
> ---------
> New text: (Section 5.1.1.3)
> ---------
> 
> 
> 
>              SGP                             ASP1
>               |                               |
>               |<------------ASP Up------------|
>               |----------ASP Up Ack---------->|
>               |                               |
>               |------NOTIFY(AS-INACTIVE)----->|
>               |                               |
>               |<----REGISTER REQ(LRC1,RK1)----|  LRC: Local Routing
>               |                               |       Key Id
>               |----REGISTER RESP(LRC1,RC1)--->|   RK: Routing Key
>               |                               |   RC: Routing Context
>               |                               |
>               |<------- ASP Active(RC1)-------|
>               |-----ASP Active Ack (RC1)----->|
>               |                               |
>               |----NOTIFY(AS-ACTIVE)(RC1)---->|
>               |                               |
>               ~                               ~
>               |                               |
>               |<----REGISTER REQ(LRCn,RKn)----|
>               |                               |
>               |----REGISTER RESP(LRCn,RCn)--->|
>               |                               |
>               |                               |
>               |<------- ASP Active(RCn)-------|
>               |-----ASP Active Ack (RCn)----->|
>               |                               |
>               |----NOTIFY(AS-ACTIVE)(RCn)---->|
>               |                               |
> 
> 
> ---------
> Old text: (Section 5.1.1.4)
> ---------
> 
> 
> 
>                SGP                             ASP1
>                 |                               |
>                 |<------------ASP Up------------|
>                 |----------ASP Up Ack---------->|
>                 |                               |
>                 |<---REGISTER REQ({LRC1,RK1},---|
>                 |                   ...,        |
>                 |                 {LRCn,RKn}),--|
>                 |                               |
>                 |---REGISTER RESP({LRC1,RC1},-->|
>                 |                  ...,         |
>                 |                 (LRCn,RCn})   |
>                 |                               |
>                 |<------- ASP Active(RC1)-------|
>                 |-----ASP Active Ack (RC1)----->|
>                 |                               |
>                 :                               :
>                 :                               :
>                 |                               |
>                 |<------- ASP Active(RCn)-------|
>                 |-----ASP Active Ack (RCn)----->|
>                 |                               |
> 
> ---------
> New text: (Section 5.1.1.4)
> ---------
> 
> 
>                SGP                             ASP1
>                 |                               |
>                 |<------------ASP Up------------|
>                 |----------ASP Up Ack---------->|
>                 |                               |
>                 |------NOTIFY(AS-INACTIVE)----->|
>                 |                               |
>                 |                               |
>                 |<---REGISTER REQ({LRC1,RK1},   |
>                 |                   ...,        |
>                 |                 {LRCn,RKn}),--|
>                 |                               |
>                 |---REGISTER RESP({LRC1,RC1},-->|
>                 |                  ...,         |
>                 |                 (LRCn,RCn})   |
>                 |                               |
>                 |<------- ASP Active(RC1)-------|
>                 |-----ASP Active Ack (RC1)----->|
>                 |                               |
>                 |----NOTIFY(AS-ACTIVE)(RC1)---->|
>                 |                               |
>                 :                               :
>                 :                               :
>                 |                               |
>                 |<------- ASP Active(RCn)-------|
>                 |-----ASP Active Ack (RCn)----->|
>                 |                               |
>                 |----NOTIFY(AS-ACTIVE)(RCn)---->|
>                 |                               |
> 
> 
> 
> 
> 
> 
> 
> ---------
> Old text: (Section 5.1.2)
> ---------
> 
>       SGP                      ASP1                       ASP2
>        |                        |                          |
>        |<--------ASP Up---------|                          |
>        |-------ASP Up Ack------>|                          |
>        |                        |                          |
>        |<----------------------------ASP Up----------------|
>        |----------------------------ASP Up Ack------------>|
>        |                        |                          |
>        |                        |                          |
>        |<-------ASP Active------|                          |
>        |------ASP Active Ack--->|                          |
>        |                        |                          |
> 
> ---------
> New text: (Section 5.1.2)
> ---------
> 
> 
>       SGP                      ASP1                       ASP2
>        |                        |                          |
>        |<--------ASP Up---------|                          |
>        |-------ASP Up Ack------>|                          |
>        |                        |                          |
>        |--NOTIFY(AS-INACTIVE)-->|                          |
>        |                        |                          |
>        |<----------------------------ASP Up----------------|
>        |----------------------------ASP Up Ack------------>|
>        |                        |                          |
>        |                        |                          |
>        |<-------ASP Active------|                          |
>        |------ASP Active Ack--->|                          |
>        |                        |                          |
>        |---NOTIFY(AS-ACTIVE)--->|                          |
>        |--------------------------NOTIFY(AS-ACTIVE)------->|
>        |                        |                          |
> 
> 
> 
> 
> 
> 
> ---------
> Old text: (Section 5.1.3)
> ---------
> 
>      OLD:
>       SGP                      ASP1                       ASP2
>        |                        |                          |
>        |<---------ASP Up--------|                          |
>        |--------ASP Up Ack----->|                          |
>        |                        |                          |
>        |<-----------------------------ASP Up---------------|
>        |----------------------------ASP Up Ack------------>|
>        |                        |                          |
>        |                        |                          |
>        |<--ASP Active (Ldshr)---|                          |
>        |-----ASP-Active Ack---->|                          |
>        |                        |                          |
>        |---------------------------NOTIFY (AS-ACTIVE------>|
>        |                        |                          |
>        |<---------------------------ASP Active (Ldshr)-----|
>        |------------------------------ASP Active Ack------>|
>        |                        |                          |
> 
> 
> ---------
> New text: (Section 5.1.3)
> ---------
> 
> 
> 
>       SGP                      ASP1                       ASP2
>        |                        |                          |
>        |<---------ASP Up--------|                          |
>        |--------ASP Up Ack----->|                          |
>        |                        |                          |
>        |--NOTIFY(AS-INACTIVE)-->|                          |
>        |                        |                          |
>        |<-----------------------------ASP Up---------------|
>        |----------------------------ASP Up Ack------------>|
>        |                        |                          |
>        |<--ASP Active (Ldshr)---|                          |
>        |-----ASP-Active Ack---->|                          |
>        |                        |                          |
>        |---NOTIFY (AS-ACTIVE)-->|                          |
>        |-----------------------------NOTIFY(AS-ACTIVE)---->|
>        |                        |                          |
>        |<---------------------------ASP Active (Ldshr)-----|
>        |------------------------------ASP Active Ack------>|
>        |                        |                          |
> 
> 
> ---------
> Old text: (Section 5.1.4)
> ---------
> 
> 
>      SGP                 ASP1                ASP2                ASP3
>        |                   |                   |                   |
>        |<------ASP Up------|                   |                   |
>        |-----ASP Up Ack--->|                   |                   |
>        |                   |                   |                   |
>        |<-------------------------ASP Up-------|                   |
>        |------------------------ASP Up Ack---->|                   |
>        |                   |                   |                   |
>        |<--------------------------------------------ASP Up--------|
>        |--------------------------------------------ASP Up Ack---->|
>        |                   |                   |                   |
>        |                   |                   |                   |
>        |<--ASP Act (Ldshr)-|                   |                   |
>        |----ASP Act Ack--->|                   |                   |
>        |                   |                   |                   |
>        |                   |                   |                   |
>        |<-------------------ASP Act. (Ldshr)---|                   |
>        |----------------------ASP Act Ack----->|                   |
>        |                   |                   |                   |
>        |---------Notify (AS-ACTIVE)----------->|                   |
>        |----------------------Notify (AS-ACTIVE)------------------>|
> 
> 
> ---------
> New text: (Section 5.1.4)
> ---------
> 
> 
> 
>      SGP                 ASP1                ASP2                ASP3
>        |                   |                   |                   |
>        |<------ASP Up------|                   |                   |
>        |-----ASP Up Ack--->|                   |                   |
>         |                   |                   |                   |
>        |<-------------------------ASP Up-------|                   |
>        |------------------------ASP Up Ack---->|                   |
>        |                   |                   |                   |
>        |NTFY(AS-INACTIVE)->|                   |                   |
>        |------------------NOTIFY(AS-INACTIVE)->|                   |
>        |                   |                   |                   |
>        |<--------------------------------------------ASP Up--------|
>        |--------------------------------------------ASP Up Ack---->|
>        |                   |                   |                   |
>        |                   |                   |                   |
>        |<--ASP Act (Ldshr)-|                   |                   |
>        |----ASP Act Ack--->|                   |                   |
>        |                   |                   |                   |
>        |                   |                   |                   |
>        |<-------------------ASP Act. (Ldshr)---|                   |
>        |----------------------ASP Act Ack----->|                   |
>        |                   |                   |                   |
>        |--NTFY(AS-ACTIVE)->|                   |                   |
>        |--------------------NOTIFY(AS-ACTIVE)->|                   |
>        |----------------------------------------NOTIFY(AS-ACTIVE)->|
>        |                   |                   |                   |
>        |                   |                   |                   |
> 
> ---------
> Old text: (Section 5.2.3)
> ---------
> 
> 
>      SGP                 ASP1                ASP2                ASP3
>        |                   |                   |                   |
>        |<----ASP Inact.----|                   |                   |
>        |---ASP Inact Ack-->|                   |                   |
>        |                   |                   |                   |
>        |--------------------------------NTFY(Ins. ASPs)----------->|
>        |                   |                   |                   |
>        |<----------------------------------------ASP Act (Ldshr)---|
>        |------------------------------------------ASP Act (Ack)--->|
>        |                   |                   |                   |
> 
> 
> ---------
> New text: (Section 5.2.3)
> ---------
> 
> 
>      SGP                 ASP1                ASP2                ASP3
>        |                   |                   |                   |
>        |<----ASP Inact.----|                   |                   |
>        |---ASP Inact Ack-->|                   |                   |
>        |                   |                   |                   |
>        |-NTFY(AS-PENDING)->|                   |                   |
>        |-------------------NOTIFY(AS-PENDING)->|                   |
>        |---------------------------------------NOTIFY(AS-PENDING)->|
>        |---------------------------------------NOTIFY(Ins. ASPs)-->|
>        |                   |                   |                   |
>        |                   |                   |                   |
>        |<----------------------------------------ASP Act (Ldshr)---|
>        |------------------------------------------ASP Act (Ack)--->|
>        |                   |                   |                   |
>        |-NTFY(AS-ACTIVE)-->|                   |                   |
>        |-------------------NOTIFY(AS-ACTIVE)-->|                   |
>        |---------------------------------------NOTIFY(AS-ACTIVE)-->|
>        |                   |                   |                   |
>        |                   |                   |                   |
> 
> 
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
>  https://www1.ietf.org/mailman/listinfo/sigtran
> 
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 

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



From exim@www1.ietf.org  Thu Jun 19 09:31:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17233
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Jun 2003 09:31:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5JDV2O00476
	for sigtran-archive@odin.ietf.org; Thu, 19 Jun 2003 09:31:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SzVF-00007R-Gt; Thu, 19 Jun 2003 09:31:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SzUN-000061-6W
	for sigtran@optimus.ietf.org; Thu, 19 Jun 2003 09:30:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17213
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 09:30:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SzS4-0004CH-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 09:27:44 -0400
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49] helo=albatross.tn.sw.ericsson.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SzS3-0004CE-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 09:27:43 -0400
Received: from esealnt611.al.sw.ericsson.se (alteon-nat4.sw.ericsson.se [153.88.254.121])
	by albatross.tn.sw.ericsson.se (8.12.9/8.12.9/WIREfire-1.6b) with ESMTP id h5JDU3G5023949;
	Thu, 19 Jun 2003 15:30:03 +0200 (MEST)
Received: from ESEALNT744.al.sw.ericsson.se ([153.88.251.4]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id LVYQSC09; Thu, 19 Jun 2003 15:31:36 +0200
Received: by ESEALNT744.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NBCQ8ZAR>; Thu, 19 Jun 2003 15:30:03 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C73@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
To: sigtran@ietf.org
Cc: "'Tolga Asveren'" <tolga_asveren@yahoo.com>
Subject: RE: [Sigtran] Re: M3UA Notify message
Date: Thu, 19 Jun 2003 15:29:42 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Hi Brian, 

I think Tolga had a good point. Maybe it is important to note the difference between max engineered load and peak load. I would leave to the operator how to solve the peak load. They may decide to turn to active more than "n" ASPs to solve this isolated cases.

Cheers // Javier.

> -----Original Message-----
> From: Tolga Asveren [mailto:tolga_asveren@yahoo.com]
> Sent: jueves, 19 de junio de 2003 14:27
> To: sigtran@ietf.org
> Subject: Re: [Sigtran] Re: M3UA Notify message
> 
> 
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Samuel,
> > 
> > 'n' (as agreed by concensus, and included in the new
> > IG text as well) is the
> > number of ASP required to handle the "maximum
> > engineered load", not the normal
> > load, or event the expected load.  So, for an ISUP
> > bearing system, if it is
> > not Christmas or Mother's day, and there is not a
> > significant backlog of
> > reattempt traffic (extended outage), the system can
> > come up with less than 'n'
> > processors, as 'n' is defined.  Therefore, refusing
> > to start or restart an
> > AS with less than 'n' active ASPs is foolish.
> > 
> > Setting n to 1, as you suggest, would be incorrect. 
> > 1 ASP cannot handle the
> > "maximum engineered load".  In the example, it takes
> > 256 ASPs to handle the
> > "maximum engineered load" (e.g. busy-hour on
> > Mother's Day).  But for the other
> > 340 some days of the year, some lesser number of
> > ASPs is sufficient, and 255
> > ASPs is surely sufficient.
> [TOLGA]For this case, IMO n=1 (or whatever is the
> number of ASPs, which should be ACTIVE at minimum)is
> correct. I don't interprete n as number of maximum
> ASPs, which can be ACTIVE at any given time. n is the
> number of ASPs, which should be ACTIVE, so that AS
> switches to ACTIVE state. For example, if n=3, this
> IMO does not mean that I can't have 256 ASPs ACTIVE at
> any given time. So, for your example, you set
> n=sufficient number of ASPs(something less than 256). 
> Maybe using the term n+k for this kind of operation is
> what you don't like?
> > 
> > Not permitting the SG to start or restart with less
> > than 'n' ASPs active
> > is a bad thing for carrier class systems.
> > 
> > I cannot agree with the change on these grounds.
> > 
> > --brian
> > 
> > 
> > Samuel Dur D. Jeyaseelan wrote:                     
> >                                (Thu, 19 Jun 2003
> > 00:42:05)
> > > 
> > > Brian,
> > > 
> > > 
> > > On Wed, 18 Jun 2003, Brian F. G. Bidulock wrote:
> > > 
> > > > Samuel,
> > > > 
> > > > Samuel Dur D. Jeyaseelan wrote:                 
> >                                    (Wed, 18 Jun 2003
> > 22:48:23)
> > > > > > > > 
> > > > > > > > I agree.   That is what is provided for
> > in the RFC.  However, section 3.15 of
> > > > > > > > the IG would require the SG to stop
> > traffic when n < 2.  So, it must be
> > > > > > > > struck.
> > > > > > > > 
> > > > > > > > --brian
> > > > > > > [Samuel] Does new IG stop the traffic when
> > n < 2 ?
> > > > > > 
> > > > > > Yes, it does.  On restart.
> > > > > > 
> > > > > Yes thats what everybody agrees that on start
> > and restart case 'n' number
> > > > > of ASPs to be in ACTIVE state.
> > > > 
> > > > Disagree wholeheartedly.  And this was never
> > agreed.
> > > > 
> > > > What was agreed (except for Tolga) was that the
> > RFC allowed the SG to either
> > > > activate on one ASP or wait for 'n' and withhold
> > NTFY(AS-ACTIVE) which was
> > > > sufficient for both start and restart cases.
> > > > 
> > > section 5.4.1 says that minimum 'n' number of ASPs
> > are required to handle 
> > > total traffic load.Here my understanding is, craft
> > person knows the
> > > incoming traffic capacity based on some kind of
> > 'traffic measurement
> > > analysis',
> > > and the same time craft person knows, to handle
> > this incoming traffic an
> > > SGP requires 'n' ASPs.Here the point is craft
> > person can not maintain 'n'
> > > ASPs to be in ACTIVE state throughout the traffic
> > period but at least he
> > > can make sure 'n' ASPs are ACTIVE when (initally)
> > SG comes up.
> > > 
> > > > If an outage has been for a brief period and was
> > not congestion related, there
> > > > is no reason why traffic cannot be started on
> > the first active ASP, or under
> > > > emergency conditions for that matter.
> > > This may happen while SGP is processing the load
> > but it may not happen in
> > > the beginning and a good network configuration
> > should not allow these
> > > kinds of problems to happen in the beginning.
> > > 
> > > > The start, restart and shutdown decisions were
> > discussed in detail on the
> > > > list.  Whether the SG waits for 1 or 'n' is an
> > IMPLEMENTATION and OPERATIONAL
> > > > decision.  The existing RFC provides for this in
> > saying that the AS-ACTIVE
> > > > state implies that "at least one" ASP is in the
> > ASP-ACTIVE state for the AS.
> > > > Also the RFC states that the SGP should withhold
> > the NTFY(AS-ACTIVE) until 'n'
> > > > ASPs are active if it is going to wait for 'n'
> > ASPs (as it MAY do).  And it
> > > > also says that the ASPs should coordinate
> > amoungst themselves to ensure that
> > > > 'n' are active.
> > > This is left to the decision of the craft person,
> > this case he can
> > > configure n=1.
> > > > 
> > > > Let me give you an example of the negative
> > effect of this change:  An SG is
> > > > configured with n=256.  There are 257 ASPs.  2
> > are dead.  The AS will never
> > > > activate.  Some carrier class system...
> > > > 
> > > If n=256, it is the responsibility of the operator
> > to make sure and bring
> > > up 256 ASPs to ACTIVE state at least in the
> > beginning.
> > > 
> > > > Contrast this where, soley at the SG
> > implementer's discretion, the SG
> > > > implementor sets a timer when the first ASP goes
> > ASP-ACTIVE for the AS.  If
> > > > the other 255 are not active by the time this
> > timer expires, it sends
> > > > NTFY(AS-ACTIVE) and starts traffic.  This system
> > will always come up in
> > > > contrast to the above that will not.  The RFC
> > allows for this system, the
> > > > new IG text does not.
> > > > 
> > > > The new IG text would have you implement the
> > system that will never come up
> > > > with 2 ASPs out of service.  The RFC does not.
> > > 
> > > section 5.1.4
> > >    n+k case
> > >    --------
> > >    This scenario shows the example M3UA message
> > flows for the
> > >    establishment of traffic between an SGP and
> > three ASPs in the same
> > >    Application Server, where two of the ASPs are
> > brought to the state
> > >    ASP-ACTIVE and subsequently share the load.  In
> > this case, a minimum
> > >    of two ASPs are required to handle the total
> > traffic load (2+1
> > >    sparing).
> > > 
> > > still RFC says '... a minimum of two ASPs are
> > required to handle the total
> > > traffic load ....'
> > > 
> > > > 
> > > > I you wan to explain things in the IG, go ahead,
> > but the proposed text does
> > > > not do that.  The proposed text makes changes to
> > the normal and correct
> > > > operation as laid out in the RFC and starts
> > making implementation and
> > > > operational decisions for the SG designer that
> > it must not.
> > > > 
> > > > --brian
> > > > 
> > > 
> > > I have conveyed my understanding to all. Otherwise
> > in order to conclude 
> > > this issue we can go for polling.
> > > 
> > > --Samuel
> > > > -- 
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > > 
> > > 
> > > 
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> > 
> === message truncated ===
> 
> 
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 

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



From exim@www1.ietf.org  Thu Jun 19 09:33:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17281
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Jun 2003 09:33:28 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5JDX1j01155
	for sigtran-archive@odin.ietf.org; Thu, 19 Jun 2003 09:33:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SzXB-0000IW-8C; Thu, 19 Jun 2003 09:33:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SzWE-0000Hn-Oe
	for sigtran@optimus.ietf.org; Thu, 19 Jun 2003 09:32:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17255
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 09:32:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SzTw-0004Ci-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 09:29:40 -0400
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47] helo=penguin.al.sw.ericsson.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SzTv-0004Ce-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 09:29:39 -0400
Received: from esealnt613.al.sw.ericsson.se (alteon-nat8.sw.ericsson.se [153.88.254.125])
	by penguin.al.sw.ericsson.se (8.12.9/8.12.9/WIREfire-1.6b) with ESMTP id h5JDVvw2008608;
	Thu, 19 Jun 2003 15:31:58 +0200 (MEST)
Received: from ESEALNT745.al.sw.ericsson.se ([153.88.251.5]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id MVP9D87Z; Thu, 19 Jun 2003 15:32:25 +0200
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <HT92CCX3>; Thu, 19 Jun 2003 15:30:58 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C74@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
To: "'sigtran@ietf.org'" <sigtran@ietf.org>
Cc: "Lyndon Ong (E-mail)" <lyong@ciena.com>
Subject: RE: [Sigtran] RE: M3UA IG: section 3.15 reworked
Date: Thu, 19 Jun 2003 15:31:37 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Folks, 

I think we must try to conclude this discussion. 

As a summary:
- It seems to me that we have full consensus in saying that "n" is the maximum engineered load. - And it also seems to me that most of the folks support to wait to "n" ASPs in start/restart situations. 

If this is true, I would appeal for the rough consensus law, unless the chairman says anything else...

Then, we'll include the reworked 3.15 section into the IG. And also a modification in section 1.4.4.1 to state that "n" is the maximum engineered load.


Thanks // Javier.


> -----Original Message-----
> From: Samuel Dur D. Jeyaseelan [mailto:sjeyasee@ssd.usa.alcatel.com]
> Sent: jueves, 19 de junio de 2003 13:14
> To: 'sigtran@ietf.org'
> Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
> 
> 
> 
> Brian,
>  
> I remeber the following topics were discussged a few
> months back.
>  
> 1.'n' is mantatory at start case.
> 2. 'n' # of ASPs sufficient to handle maximum engineered load.
> 3.When # of ASPs < n (where n > 0) , ASP state should be ACTIVE(not
> pending)
>  
> I dont know whether consensus is made or not.
>  
> My support is to make 'n' as mandatory at start case as section
> 5.1.4 of RFC, where it says
>  
> if n=2
>  
> ..............................................a minimum
> of two ASPs are required to handle the total traffic load (2+1
> sparing).
>  
> Once again i am not saying that we should make this as a 
> consensus, i just
> conveyed my idea thats all.
>  
> --Samuel
> 
> 
>   Alcatel USA, Inc.                  Internet: 
> <userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel 
> USA, Inc. *******
> 
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 

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



From exim@www1.ietf.org  Thu Jun 19 15:18:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12958
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Jun 2003 15:18:31 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5JJI3m32715
	for sigtran-archive@odin.ietf.org; Thu, 19 Jun 2003 15:18:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19T4v3-0008VX-I9; Thu, 19 Jun 2003 15:18:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19T4uC-0008Uz-Mi
	for sigtran@optimus.ietf.org; Thu, 19 Jun 2003 15:17:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12783
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 15:17:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T4ru-00021U-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 15:14:46 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[8zdrnkWJNUGkSqB5ew1f4s+tHDnExO1/])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T4rt-00021R-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 15:14:45 -0400
Received: from ns.pigworks.openss7.net (IDENT:v9ZxGgK1oNhVBag/wqKLUBpNGU5d1fSf@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5JJH5X16259;
	Thu, 19 Jun 2003 13:17:05 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5JJH4X21344;
	Thu, 19 Jun 2003 13:17:04 -0600
Date: Thu, 19 Jun 2003 13:17:04 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030619131704.A21325@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030619013818.A10362@openss7.org> <20030619122646.20025.qmail@web12808.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030619122646.20025.qmail@web12808.mail.yahoo.com>; from tolga_asveren@yahoo.com on Thu, Jun 19, 2003 at 05:26:46AM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

Tolga Asveren wrote:                                                                 (Thu, 19 Jun 2003 05:26:46)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Samuel,
> > 
> > 'n' (as agreed by concensus, and included in the new
> > IG text as well) is the
> > number of ASP required to handle the "maximum
> > engineered load", not the normal
> > load, or event the expected load.  So, for an ISUP
> > bearing system, if it is
> > not Christmas or Mother's day, and there is not a
> > significant backlog of
> > reattempt traffic (extended outage), the system can
> > come up with less than 'n'
> > processors, as 'n' is defined.  Therefore, refusing
> > to start or restart an
> > AS with less than 'n' active ASPs is foolish.
> > 
> > Setting n to 1, as you suggest, would be incorrect. 
> > 1 ASP cannot handle the
> > "maximum engineered load".  In the example, it takes
> > 256 ASPs to handle the
> > "maximum engineered load" (e.g. busy-hour on
> > Mother's Day).  But for the other
> > 340 some days of the year, some lesser number of
> > ASPs is sufficient, and 255
> > ASPs is surely sufficient.
> [TOLGA]For this case, IMO n=1 (or whatever is the
> number of ASPs, which should be ACTIVE at minimum)is
> correct. I don't interprete n as number of maximum
> ASPs, which can be ACTIVE at any given time. n is the
> number of ASPs, which should be ACTIVE, so that AS
> switches to ACTIVE state. For example, if n=3, this
> IMO does not mean that I can't have 256 ASPs ACTIVE at
> any given time. So, for your example, you set
> n=sufficient number of ASPs(something less than 256). 
> Maybe using the term n+k for this kind of operation is
> what you don't like?

But that would change the meaning of 'n' from the agreed
"maximum engineered load".

--brian

> > 
> > Not permitting the SG to start or restart with less
> > than 'n' ASPs active
> > is a bad thing for carrier class systems.
> > 
> > I cannot agree with the change on these grounds.
> > 
> > --brian
> > 
> > 
> > Samuel Dur D. Jeyaseelan wrote:                     
> >                                (Thu, 19 Jun 2003
> > 00:42:05)
> > > 
> > > Brian,
> > > 
> > > 
> > > On Wed, 18 Jun 2003, Brian F. G. Bidulock wrote:
> > > 
> > > > Samuel,
> > > > 
> > > > Samuel Dur D. Jeyaseelan wrote:                 
> >                                    (Wed, 18 Jun 2003
> > 22:48:23)
> > > > > > > > 
> > > > > > > > I agree.   That is what is provided for
> > in the RFC.  However, section 3.15 of
> > > > > > > > the IG would require the SG to stop
> > traffic when n < 2.  So, it must be
> > > > > > > > struck.
> > > > > > > > 
> > > > > > > > --brian
> > > > > > > [Samuel] Does new IG stop the traffic when
> > n < 2 ?
> > > > > > 
> > > > > > Yes, it does.  On restart.
> > > > > > 
> > > > > Yes thats what everybody agrees that on start
> > and restart case 'n' number
> > > > > of ASPs to be in ACTIVE state.
> > > > 
> > > > Disagree wholeheartedly.  And this was never
> > agreed.
> > > > 
> > > > What was agreed (except for Tolga) was that the
> > RFC allowed the SG to either
> > > > activate on one ASP or wait for 'n' and withhold
> > NTFY(AS-ACTIVE) which was
> > > > sufficient for both start and restart cases.
> > > > 
> > > section 5.4.1 says that minimum 'n' number of ASPs
> > are required to handle 
> > > total traffic load.Here my understanding is, craft
> > person knows the
> > > incoming traffic capacity based on some kind of
> > 'traffic measurement
> > > analysis',
> > > and the same time craft person knows, to handle
> > this incoming traffic an
> > > SGP requires 'n' ASPs.Here the point is craft
> > person can not maintain 'n'
> > > ASPs to be in ACTIVE state throughout the traffic
> > period but at least he
> > > can make sure 'n' ASPs are ACTIVE when (initally)
> > SG comes up.
> > > 
> > > > If an outage has been for a brief period and was
> > not congestion related, there
> > > > is no reason why traffic cannot be started on
> > the first active ASP, or under
> > > > emergency conditions for that matter.
> > > This may happen while SGP is processing the load
> > but it may not happen in
> > > the beginning and a good network configuration
> > should not allow these
> > > kinds of problems to happen in the beginning.
> > > 
> > > > The start, restart and shutdown decisions were
> > discussed in detail on the
> > > > list.  Whether the SG waits for 1 or 'n' is an
> > IMPLEMENTATION and OPERATIONAL
> > > > decision.  The existing RFC provides for this in
> > saying that the AS-ACTIVE
> > > > state implies that "at least one" ASP is in the
> > ASP-ACTIVE state for the AS.
> > > > Also the RFC states that the SGP should withhold
> > the NTFY(AS-ACTIVE) until 'n'
> > > > ASPs are active if it is going to wait for 'n'
> > ASPs (as it MAY do).  And it
> > > > also says that the ASPs should coordinate
> > amoungst themselves to ensure that
> > > > 'n' are active.
> > > This is left to the decision of the craft person,
> > this case he can
> > > configure n=1.
> > > > 
> > > > Let me give you an example of the negative
> > effect of this change:  An SG is
> > > > configured with n=256.  There are 257 ASPs.  2
> > are dead.  The AS will never
> > > > activate.  Some carrier class system...
> > > > 
> > > If n=256, it is the responsibility of the operator
> > to make sure and bring
> > > up 256 ASPs to ACTIVE state at least in the
> > beginning.
> > > 
> > > > Contrast this where, soley at the SG
> > implementer's discretion, the SG
> > > > implementor sets a timer when the first ASP goes
> > ASP-ACTIVE for the AS.  If
> > > > the other 255 are not active by the time this
> > timer expires, it sends
> > > > NTFY(AS-ACTIVE) and starts traffic.  This system
> > will always come up in
> > > > contrast to the above that will not.  The RFC
> > allows for this system, the
> > > > new IG text does not.
> > > > 
> > > > The new IG text would have you implement the
> > system that will never come up
> > > > with 2 ASPs out of service.  The RFC does not.
> > > 
> > > section 5.1.4
> > >    n+k case
> > >    --------
> > >    This scenario shows the example M3UA message
> > flows for the
> > >    establishment of traffic between an SGP and
> > three ASPs in the same
> > >    Application Server, where two of the ASPs are
> > brought to the state
> > >    ASP-ACTIVE and subsequently share the load.  In
> > this case, a minimum
> > >    of two ASPs are required to handle the total
> > traffic load (2+1
> > >    sparing).
> > > 
> > > still RFC says '... a minimum of two ASPs are
> > required to handle the total
> > > traffic load ....'
> > > 
> > > > 
> > > > I you wan to explain things in the IG, go ahead,
> > but the proposed text does
> > > > not do that.  The proposed text makes changes to
> > the normal and correct
> > > > operation as laid out in the RFC and starts
> > making implementation and
> > > > operational decisions for the SG designer that
> > it must not.
> > > > 
> > > > --brian
> > > > 
> > > 
> > > I have conveyed my understanding to all. Otherwise
> > in order to conclude 
> > > this issue we can go for polling.
> > > 
> > > --Samuel
> > > > -- 
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > > 
> > > 
> > > 
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> > 
> === message truncated ===
> 
> 
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Thu Jun 19 15:20:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13144
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Jun 2003 15:20:30 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5JJK2t00723
	for sigtran-archive@odin.ietf.org; Thu, 19 Jun 2003 15:20:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19T4x0-0000BZ-44; Thu, 19 Jun 2003 15:20:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19T4wH-00006t-4T
	for sigtran@optimus.ietf.org; Thu, 19 Jun 2003 15:19:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13080
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 15:19:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T4ty-00024m-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 15:16:54 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[HiETgfbXjz8dxDX+/QAz2r86HYPQ3dJp])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T4tx-00024Z-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 15:16:53 -0400
Received: from ns.pigworks.openss7.net (IDENT:DZxweU2RM+iGHU8ylkrLxFg3u16BFPyN@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5JJJDX16289;
	Thu, 19 Jun 2003 13:19:13 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5JJJCZ21413;
	Thu, 19 Jun 2003 13:19:12 -0600
Date: Thu, 19 Jun 2003 13:19:12 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
Cc: sigtran@ietf.org, "'Tolga Asveren'" <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030619131912.B21325@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>,
	sigtran@ietf.org, 'Tolga Asveren' <tolga_asveren@yahoo.com>
References: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C73@eestqnt105.es.eu.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C73@eestqnt105.es.eu.ericsson.se>; from javier.pastor-balbas@ece.ericsson.se on Thu, Jun 19, 2003 at 03:29:42PM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Javier,

Telephone networks are engineered to meet high day busy hour peak load.  What
else did you think that "maximum engineered load" means?

--brian

Javier Pastor-Balbas (ECE) wrote:                                                   (Thu, 19 Jun 2003 15:29:42)
> Hi Brian, 
> 
> I think Tolga had a good point. Maybe it is important to note the difference
> between max engineered load and peak load. I would leave to the operator how
> to solve the peak load. They may decide to turn to active more than "n" ASPs
> to solve this isolated cases.
> 
> Cheers // Javier.
> 
> > -----Original Message-----
> > From: Tolga Asveren [mailto:tolga_asveren@yahoo.com]
> > Sent: jueves, 19 de junio de 2003 14:27
> > To: sigtran@ietf.org
> > Subject: Re: [Sigtran] Re: M3UA Notify message
> > 
> > 
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > Samuel,
> > > 
> > > 'n' (as agreed by concensus, and included in the new
> > > IG text as well) is the
> > > number of ASP required to handle the "maximum
> > > engineered load", not the normal
> > > load, or event the expected load.  So, for an ISUP
> > > bearing system, if it is
> > > not Christmas or Mother's day, and there is not a
> > > significant backlog of
> > > reattempt traffic (extended outage), the system can
> > > come up with less than 'n'
> > > processors, as 'n' is defined.  Therefore, refusing
> > > to start or restart an
> > > AS with less than 'n' active ASPs is foolish.
> > > 
> > > Setting n to 1, as you suggest, would be incorrect. 
> > > 1 ASP cannot handle the
> > > "maximum engineered load".  In the example, it takes
> > > 256 ASPs to handle the
> > > "maximum engineered load" (e.g. busy-hour on
> > > Mother's Day).  But for the other
> > > 340 some days of the year, some lesser number of
> > > ASPs is sufficient, and 255
> > > ASPs is surely sufficient.
> > [TOLGA]For this case, IMO n=1 (or whatever is the
> > number of ASPs, which should be ACTIVE at minimum)is
> > correct. I don't interprete n as number of maximum
> > ASPs, which can be ACTIVE at any given time. n is the
> > number of ASPs, which should be ACTIVE, so that AS
> > switches to ACTIVE state. For example, if n=3, this
> > IMO does not mean that I can't have 256 ASPs ACTIVE at
> > any given time. So, for your example, you set
> > n=sufficient number of ASPs(something less than 256). 
> > Maybe using the term n+k for this kind of operation is
> > what you don't like?
> > > 
> > > Not permitting the SG to start or restart with less
> > > than 'n' ASPs active
> > > is a bad thing for carrier class systems.
> > > 
> > > I cannot agree with the change on these grounds.
> > > 
> > > --brian
> > > 
> > > 
> > > Samuel Dur D. Jeyaseelan wrote:                     
> > >                                (Thu, 19 Jun 2003
> > > 00:42:05)
> > > > 
> > > > Brian,
> > > > 
> > > > 
> > > > On Wed, 18 Jun 2003, Brian F. G. Bidulock wrote:
> > > > 
> > > > > Samuel,
> > > > > 
> > > > > Samuel Dur D. Jeyaseelan wrote:                 
> > >                                    (Wed, 18 Jun 2003
> > > 22:48:23)
> > > > > > > > > 
> > > > > > > > > I agree.   That is what is provided for
> > > in the RFC.  However, section 3.15 of
> > > > > > > > > the IG would require the SG to stop
> > > traffic when n < 2.  So, it must be
> > > > > > > > > struck.
> > > > > > > > > 
> > > > > > > > > --brian
> > > > > > > > [Samuel] Does new IG stop the traffic when
> > > n < 2 ?
> > > > > > > 
> > > > > > > Yes, it does.  On restart.
> > > > > > > 
> > > > > > Yes thats what everybody agrees that on start
> > > and restart case 'n' number
> > > > > > of ASPs to be in ACTIVE state.
> > > > > 
> > > > > Disagree wholeheartedly.  And this was never
> > > agreed.
> > > > > 
> > > > > What was agreed (except for Tolga) was that the
> > > RFC allowed the SG to either
> > > > > activate on one ASP or wait for 'n' and withhold
> > > NTFY(AS-ACTIVE) which was
> > > > > sufficient for both start and restart cases.
> > > > > 
> > > > section 5.4.1 says that minimum 'n' number of ASPs
> > > are required to handle 
> > > > total traffic load.Here my understanding is, craft
> > > person knows the
> > > > incoming traffic capacity based on some kind of
> > > 'traffic measurement
> > > > analysis',
> > > > and the same time craft person knows, to handle
> > > this incoming traffic an
> > > > SGP requires 'n' ASPs.Here the point is craft
> > > person can not maintain 'n'
> > > > ASPs to be in ACTIVE state throughout the traffic
> > > period but at least he
> > > > can make sure 'n' ASPs are ACTIVE when (initally)
> > > SG comes up.
> > > > 
> > > > > If an outage has been for a brief period and was
> > > not congestion related, there
> > > > > is no reason why traffic cannot be started on
> > > the first active ASP, or under
> > > > > emergency conditions for that matter.
> > > > This may happen while SGP is processing the load
> > > but it may not happen in
> > > > the beginning and a good network configuration
> > > should not allow these
> > > > kinds of problems to happen in the beginning.
> > > > 
> > > > > The start, restart and shutdown decisions were
> > > discussed in detail on the
> > > > > list.  Whether the SG waits for 1 or 'n' is an
> > > IMPLEMENTATION and OPERATIONAL
> > > > > decision.  The existing RFC provides for this in
> > > saying that the AS-ACTIVE
> > > > > state implies that "at least one" ASP is in the
> > > ASP-ACTIVE state for the AS.
> > > > > Also the RFC states that the SGP should withhold
> > > the NTFY(AS-ACTIVE) until 'n'
> > > > > ASPs are active if it is going to wait for 'n'
> > > ASPs (as it MAY do).  And it
> > > > > also says that the ASPs should coordinate
> > > amoungst themselves to ensure that
> > > > > 'n' are active.
> > > > This is left to the decision of the craft person,
> > > this case he can
> > > > configure n=1.
> > > > > 
> > > > > Let me give you an example of the negative
> > > effect of this change:  An SG is
> > > > > configured with n=256.  There are 257 ASPs.  2
> > > are dead.  The AS will never
> > > > > activate.  Some carrier class system...
> > > > > 
> > > > If n=256, it is the responsibility of the operator
> > > to make sure and bring
> > > > up 256 ASPs to ACTIVE state at least in the
> > > beginning.
> > > > 
> > > > > Contrast this where, soley at the SG
> > > implementer's discretion, the SG
> > > > > implementor sets a timer when the first ASP goes
> > > ASP-ACTIVE for the AS.  If
> > > > > the other 255 are not active by the time this
> > > timer expires, it sends
> > > > > NTFY(AS-ACTIVE) and starts traffic.  This system
> > > will always come up in
> > > > > contrast to the above that will not.  The RFC
> > > allows for this system, the
> > > > > new IG text does not.
> > > > > 
> > > > > The new IG text would have you implement the
> > > system that will never come up
> > > > > with 2 ASPs out of service.  The RFC does not.
> > > > 
> > > > section 5.1.4
> > > >    n+k case
> > > >    --------
> > > >    This scenario shows the example M3UA message
> > > flows for the
> > > >    establishment of traffic between an SGP and
> > > three ASPs in the same
> > > >    Application Server, where two of the ASPs are
> > > brought to the state
> > > >    ASP-ACTIVE and subsequently share the load.  In
> > > this case, a minimum
> > > >    of two ASPs are required to handle the total
> > > traffic load (2+1
> > > >    sparing).
> > > > 
> > > > still RFC says '... a minimum of two ASPs are
> > > required to handle the total
> > > > traffic load ....'
> > > > 
> > > > > 
> > > > > I you wan to explain things in the IG, go ahead,
> > > but the proposed text does
> > > > > not do that.  The proposed text makes changes to
> > > the normal and correct
> > > > > operation as laid out in the RFC and starts
> > > making implementation and
> > > > > operational decisions for the SG designer that
> > > it must not.
> > > > > 
> > > > > --brian
> > > > > 
> > > > 
> > > > I have conveyed my understanding to all. Otherwise
> > > in order to conclude 
> > > > this issue we can go for polling.
> > > > 
> > > > --Samuel
> > > > > -- 
> > > > > Brian F. G. Bidulock
> > > > > bidulock@openss7.org
> > > > > http://www.openss7.org/
> > > > > 
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > 
> > > -- 
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > > 
> > === message truncated ===
> > 
> > 
> > __________________________________
> > Do you Yahoo!?
> > SBC Yahoo! DSL - Now only $29.95 per month!
> > http://sbc.yahoo.com
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Thu Jun 19 15:22:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13302
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Jun 2003 15:22:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5JJM1c01621
	for sigtran-archive@odin.ietf.org; Thu, 19 Jun 2003 15:22:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19T4yu-0000Ou-Pi; Thu, 19 Jun 2003 15:22:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19T4yJ-0000Ko-NM
	for sigtran@optimus.ietf.org; Thu, 19 Jun 2003 15:21:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13225
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 15:21:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T4w1-00027N-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 15:19:01 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[7Fc7tlY473hiDww2PgipMqJJJoMiR88m])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T4w0-00027F-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 15:19:01 -0400
Received: from ns.pigworks.openss7.net (IDENT:ZfFmNm6pTEEo7VRTOzMkmoEy71/0IKLR@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5JJLKX16320;
	Thu, 19 Jun 2003 13:21:20 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5JJLKF21467;
	Thu, 19 Jun 2003 13:21:20 -0600
Date: Thu, 19 Jun 2003 13:21:19 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>,
        "Lyndon Ong (E-mail)" <lyong@ciena.com>
Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
Message-ID: <20030619132119.C21325@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>,
	"Lyndon Ong (E-mail)" <lyong@ciena.com>
References: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C74@eestqnt105.es.eu.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C74@eestqnt105.es.eu.ericsson.se>; from javier.pastor-balbas@ece.ericsson.se on Thu, Jun 19, 2003 at 03:31:37PM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Javier,

Javier Pastor-Balbas (ECE) wrote:                                                   (Thu, 19 Jun 2003 15:31:37)
> Folks, 
> 
> I think we must try to conclude this discussion. 
> 
> As a summary:
> - It seems to me that we have full consensus in saying that "n" is the
> maximum engineered load. - And it also seems to me that most of the folks
> support to wait to "n" ASPs in start/restart situations. 
> 
> If this is true, I would appeal for the rough consensus law, unless the
> chairman says anything else...
> 
> Then, we'll include the reworked 3.15 section into the IG. And also a
> modification in section 1.4.4.1 to state that "n" is the maximum engineered
> load.

I disagree with this, both on technical grounds, and on the grounds that
the RFC cannot place requirements on purely load and related operational
characteristics.

--brian

> 
> 
> Thanks // Javier.
> 
> 
> > -----Original Message-----
> > From: Samuel Dur D. Jeyaseelan [mailto:sjeyasee@ssd.usa.alcatel.com]
> > Sent: jueves, 19 de junio de 2003 13:14
> > To: 'sigtran@ietf.org'
> > Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
> > 
> > 
> > 
> > Brian,
> >  
> > I remeber the following topics were discussged a few
> > months back.
> >  
> > 1.'n' is mantatory at start case.
> > 2. 'n' # of ASPs sufficient to handle maximum engineered load.
> > 3.When # of ASPs < n (where n > 0) , ASP state should be ACTIVE(not
> > pending)
> >  
> > I dont know whether consensus is made or not.
> >  
> > My support is to make 'n' as mandatory at start case as section
> > 5.1.4 of RFC, where it says
> >  
> > if n=2
> >  
> > ..............................................a minimum
> > of two ASPs are required to handle the total traffic load (2+1
> > sparing).
> >  
> > Once again i am not saying that we should make this as a 
> > consensus, i just
> > conveyed my idea thats all.
> >  
> > --Samuel
> > 
> > 
> >   Alcatel USA, Inc.                  Internet: 
> > <userid>@ssd.usa.alcatel.com
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel 
> > USA, Inc. *******
> > 
> > 
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Thu Jun 19 15:23:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13363
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Jun 2003 15:23:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5JJN0002865
	for sigtran-archive@odin.ietf.org; Thu, 19 Jun 2003 15:23:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19T4zs-0000k6-No; Thu, 19 Jun 2003 15:23:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19T4zd-0000jk-VC
	for sigtran@optimus.ietf.org; Thu, 19 Jun 2003 15:22:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13327
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 15:22:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T4xL-00028k-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 15:20:23 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[QyfH/0GfPT/SIOYrYqAD8VXyD3/ee0A3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T4xK-00028f-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 15:20:23 -0400
Received: from ns.pigworks.openss7.net (IDENT:y5FmlMUawXusFFVpSFduyyYdQm7qaTQx@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5JJMgX16340;
	Thu, 19 Jun 2003 13:22:42 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5JJMfN21507;
	Thu, 19 Jun 2003 13:22:41 -0600
Date: Thu, 19 Jun 2003 13:22:41 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] RE: M3UA IG: section 3.15 reworked
Message-ID: <20030619132241.D21325@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	"'sigtran@ietf.org'" <sigtran@ietf.org>
References: <20030618123306.D31402@openss7.org> <Pine.SOL.4.10.10306190609190.9866-100000@sun2594.ssd.usa.alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.4.10.10306190609190.9866-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Thu, Jun 19, 2003 at 06:13:41AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Samuel,

Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 19 Jun 2003 06:13:41)
> 
> Brian,
>  
> I remeber the following topics were discussged a few
> months back.
>  
> 1.'n' is mantatory at start case.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

This was not agreed.


> 2. 'n' # of ASPs sufficient to handle maximum engineered load.
> 3.When # of ASPs < n (where n > 0) , ASP state should be ACTIVE(not
> pending)
>  
> I dont know whether consensus is made or not.
>  
> My support is to make 'n' as mandatory at start case as section
> 5.1.4 of RFC, where it says
>  
> if n=2
>  
> ...............................................a minimum
> of two ASPs are required to handle the total traffic load (2+1
> sparing).
>  
> Once again i am not saying that we should make this as a consensus, i just
> conveyed my idea thats all.
>  
> --Samuel
> 
> 
>   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> 
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Thu Jun 19 15:45:32 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15001
	for <sigtran-archive@odin.ietf.org>; Thu, 19 Jun 2003 15:45:32 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5JJj4209936
	for sigtran-archive@odin.ietf.org; Thu, 19 Jun 2003 15:45:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19T5LB-0002a1-Sh; Thu, 19 Jun 2003 15:45:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19T5Kl-0002Z5-1e
	for sigtran@optimus.ietf.org; Thu, 19 Jun 2003 15:44:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14959
	for <sigtran@ietf.org>; Thu, 19 Jun 2003 15:44:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T5IS-0002YI-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 15:42:12 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[YLRM8MX2H8BNf9ik3r9EtMG/qZrMIZRN])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T5IR-0002YF-00
	for sigtran@ietf.org; Thu, 19 Jun 2003 15:42:12 -0400
Received: from ns.pigworks.openss7.net (IDENT:s9EuyuIuA/A4DcfmRk8IODuTCSInw6Fb@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5JJiWX16694;
	Thu, 19 Jun 2003 13:44:32 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5JJiWX21879;
	Thu, 19 Jun 2003 13:44:32 -0600
Date: Thu, 19 Jun 2003 13:44:32 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030619134432.A21852@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030619013818.A10362@openss7.org> <Pine.SOL.4.10.10306190614240.9866-100000@sun2594.ssd.usa.alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.4.10.10306190614240.9866-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Thu, Jun 19, 2003 at 06:56:10AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Samuel,

These are two different AS.  'n' is an AS specific number.

--brian

Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 19 Jun 2003 06:56:10)
> 
> Brian,
> 
> 
>                         +----+                  +-----+
>                         |STP-|------------------| ASP1| SCP (1-1-1)
>      +------------------| SG |------+           +-----+
>      |                  +----+      |  
>      |                              |           +-----+
>      |                              +-----------| ASP2| MGC(2-2-2)
>      |                                          +-----+
>      |                      
>  Conventional SS7
> 
> 
> 
> Consider a call which needs to access database (ASP1) and then
> to be routed to ASP2.
> In this case if we configure n=2 and 'n' as a mandatory,then
> the call will pass. This same will fail if n is not a mandatory
> as SG started processing the traffic as soon as one of the ASPs
> becomes available.The unavailability of another ASP will
> fail the call.
> 
> So we need to have certain restrictions to make 'n' as mandatory
> to process the call successfully.
> 
> --Samuel
> 
> 
> On Thu, 19 Jun 2003, Brian F. G. Bidulock wrote:
> 
> > Samuel,
> > 
> > 'n' (as agreed by concensus, and included in the new IG text as well) is the
> > number of ASP required to handle the "maximum engineered load", not the normal
> > load, or event the expected load.  So, for an ISUP bearing system, if it is
> > not Christmas or Mother's day, and there is not a significant backlog of
> > reattempt traffic (extended outage), the system can come up with less than 'n'
> > processors, as 'n' is defined.  Therefore, refusing to start or restart an
> > AS with less than 'n' active ASPs is foolish.
> > 
> > Setting n to 1, as you suggest, would be incorrect.  1 ASP cannot handle the
> > "maximum engineered load".  In the example, it takes 256 ASPs to handle the
> > "maximum engineered load" (e.g. busy-hour on Mother's Day).  But for the other
> > 340 some days of the year, some lesser number of ASPs is sufficient, and 255
> > ASPs is surely sufficient.
> > 
> > Not permitting the SG to start or restart with less than 'n' ASPs active
> > is a bad thing for carrier class systems.
> > 
> > I cannot agree with the change on these grounds.
> > 
> > --brian
> > 
> > 
> > Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 19 Jun 2003 00:42:05)
> > > 
> > > Brian,
> > > 
> > > 
> > > On Wed, 18 Jun 2003, Brian F. G. Bidulock wrote:
> > > 
> > > > Samuel,
> > > > 
> > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Wed, 18 Jun 2003 22:48:23)
> > > > > > > > 
> > > > > > > > I agree.   That is what is provided for in the RFC.  However, section 3.15 of
> > > > > > > > the IG would require the SG to stop traffic when n < 2.  So, it must be
> > > > > > > > struck.
> > > > > > > > 
> > > > > > > > --brian
> > > > > > > [Samuel] Does new IG stop the traffic when n < 2 ?
> > > > > > 
> > > > > > Yes, it does.  On restart.
> > > > > > 
> > > > > Yes thats what everybody agrees that on start and restart case 'n' number
> > > > > of ASPs to be in ACTIVE state.
> > > > 
> > > > Disagree wholeheartedly.  And this was never agreed.
> > > > 
> > > > What was agreed (except for Tolga) was that the RFC allowed the SG to either
> > > > activate on one ASP or wait for 'n' and withhold NTFY(AS-ACTIVE) which was
> > > > sufficient for both start and restart cases.
> > > > 
> > > section 5.4.1 says that minimum 'n' number of ASPs are required to handle 
> > > total traffic load.Here my understanding is, craft person knows the
> > > incoming traffic capacity based on some kind of 'traffic measurement
> > > analysis',
> > > and the same time craft person knows, to handle this incoming traffic an
> > > SGP requires 'n' ASPs.Here the point is craft person can not maintain 'n'
> > > ASPs to be in ACTIVE state throughout the traffic period but at least he
> > > can make sure 'n' ASPs are ACTIVE when (initally) SG comes up.
> > > 
> > > > If an outage has been for a brief period and was not congestion related, there
> > > > is no reason why traffic cannot be started on the first active ASP, or under
> > > > emergency conditions for that matter.
> > > This may happen while SGP is processing the load but it may not happen in
> > > the beginning and a good network configuration should not allow these
> > > kinds of problems to happen in the beginning.
> > > 
> > > > The start, restart and shutdown decisions were discussed in detail on the
> > > > list.  Whether the SG waits for 1 or 'n' is an IMPLEMENTATION and OPERATIONAL
> > > > decision.  The existing RFC provides for this in saying that the AS-ACTIVE
> > > > state implies that "at least one" ASP is in the ASP-ACTIVE state for the AS.
> > > > Also the RFC states that the SGP should withhold the NTFY(AS-ACTIVE) until 'n'
> > > > ASPs are active if it is going to wait for 'n' ASPs (as it MAY do).  And it
> > > > also says that the ASPs should coordinate amoungst themselves to ensure that
> > > > 'n' are active.
> > > This is left to the decision of the craft person, this case he can
> > > configure n=1.
> > > > 
> > > > Let me give you an example of the negative effect of this change:  An SG is
> > > > configured with n=256.  There are 257 ASPs.  2 are dead.  The AS will never
> > > > activate.  Some carrier class system...
> > > > 
> > > If n=256, it is the responsibility of the operator to make sure and bring
> > > up 256 ASPs to ACTIVE state at least in the beginning.
> > > 
> > > > Contrast this where, soley at the SG implementer's discretion, the SG
> > > > implementor sets a timer when the first ASP goes ASP-ACTIVE for the AS.  If
> > > > the other 255 are not active by the time this timer expires, it sends
> > > > NTFY(AS-ACTIVE) and starts traffic.  This system will always come up in
> > > > contrast to the above that will not.  The RFC allows for this system, the
> > > > new IG text does not.
> > > > 
> > > > The new IG text would have you implement the system that will never come up
> > > > with 2 ASPs out of service.  The RFC does not.
> > > 
> > > section 5.1.4
> > >    n+k case
> > >    --------
> > >    This scenario shows the example M3UA message flows for the
> > >    establishment of traffic between an SGP and three ASPs in the same
> > >    Application Server, where two of the ASPs are brought to the state
> > >    ASP-ACTIVE and subsequently share the load.  In this case, a minimum
> > >    of two ASPs are required to handle the total traffic load (2+1
> > >    sparing).
> > > 
> > > still RFC says '... a minimum of two ASPs are required to handle the total
> > > traffic load ....'
> > > 
> > > > 
> > > > I you wan to explain things in the IG, go ahead, but the proposed text does
> > > > not do that.  The proposed text makes changes to the normal and correct
> > > > operation as laid out in the RFC and starts making implementation and
> > > > operational decisions for the SG designer that it must not.
> > > > 
> > > > --brian
> > > > 
> > > 
> > > I have conveyed my understanding to all. Otherwise in order to conclude 
> > > this issue we can go for polling.
> > > 
> > > --Samuel
> > > > -- 
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > > 
> > > 
> > > 
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > 

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

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



From exim@www1.ietf.org  Fri Jun 20 02:25:33 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18999
	for <sigtran-archive@odin.ietf.org>; Fri, 20 Jun 2003 02:25:33 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5K6P5X14594
	for sigtran-archive@odin.ietf.org; Fri, 20 Jun 2003 02:25:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19TFKY-0003n6-CM; Fri, 20 Jun 2003 02:25:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19TFJp-0003mk-Pb
	for sigtran@optimus.ietf.org; Fri, 20 Jun 2003 02:24:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18957
	for <sigtran@ietf.org>; Fri, 20 Jun 2003 02:24:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TFHV-0007ar-00
	for sigtran@ietf.org; Fri, 20 Jun 2003 02:21:53 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TFHP-0007ac-00
	for sigtran@ietf.org; Fri, 20 Jun 2003 02:21:47 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h5K6NcB3002678
	for <sigtran@ietf.org>; Fri, 20 Jun 2003 01:23:38 -0500 (CDT)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h5K6NK1C006456
	for <sigtran@ietf.org>; Fri, 20 Jun 2003 01:23:20 -0500 (CDT)
Date: Fri, 20 Jun 2003 01:23:19 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
In-Reply-To: <20030619134432.A21852@openss7.org>
Message-ID: <Pine.SOL.4.10.10306200114410.9866-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


Brian,
 Yes i understood 'n' is an AS specific number. But i have a freedom to
comprise ASP1 and ASP2 in one AS having a single point code.It is just a
matter of configuration.Ultimately i want to say SGP needs both ASPs to be
be in ACTIVE state to process a given explained call.


--Samuel

  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******

On Thu, 19 Jun 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> These are two different AS.  'n' is an AS specific number.
> 
> --brian
> 
> Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 19 Jun 2003 06:56:10)
> > 
> > Brian,
> > 
> > 
> >                         +----+                  +-----+
> >                         |STP-|------------------| ASP1| SCP (1-1-1)
> >      +------------------| SG |------+           +-----+
> >      |                  +----+      |  
> >      |                              |           +-----+
> >      |                              +-----------| ASP2| MGC(2-2-2)
> >      |                                          +-----+
> >      |                      
> >  Conventional SS7
> > 
> > 
> > 
> > Consider a call which needs to access database (ASP1) and then
> > to be routed to ASP2.
> > In this case if we configure n=2 and 'n' as a mandatory,then
> > the call will pass. This same will fail if n is not a mandatory
> > as SG started processing the traffic as soon as one of the ASPs
> > becomes available.The unavailability of another ASP will
> > fail the call.
> > 
> > So we need to have certain restrictions to make 'n' as mandatory
> > to process the call successfully.
> > 
> > --Samuel
> > 
> > 
> > On Thu, 19 Jun 2003, Brian F. G. Bidulock wrote:
> > 
> > > Samuel,
> > > 
> > > 'n' (as agreed by concensus, and included in the new IG text as well) is the
> > > number of ASP required to handle the "maximum engineered load", not the normal
> > > load, or event the expected load.  So, for an ISUP bearing system, if it is
> > > not Christmas or Mother's day, and there is not a significant backlog of
> > > reattempt traffic (extended outage), the system can come up with less than 'n'
> > > processors, as 'n' is defined.  Therefore, refusing to start or restart an
> > > AS with less than 'n' active ASPs is foolish.
> > > 
> > > Setting n to 1, as you suggest, would be incorrect.  1 ASP cannot handle the
> > > "maximum engineered load".  In the example, it takes 256 ASPs to handle the
> > > "maximum engineered load" (e.g. busy-hour on Mother's Day).  But for the other
> > > 340 some days of the year, some lesser number of ASPs is sufficient, and 255
> > > ASPs is surely sufficient.
> > > 
> > > Not permitting the SG to start or restart with less than 'n' ASPs active
> > > is a bad thing for carrier class systems.
> > > 
> > > I cannot agree with the change on these grounds.
> > > 
> > > --brian
> > > 
> > > 
> > > Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 19 Jun 2003 00:42:05)
> > > > 
> > > > Brian,
> > > > 
> > > > 
> > > > On Wed, 18 Jun 2003, Brian F. G. Bidulock wrote:
> > > > 
> > > > > Samuel,
> > > > > 
> > > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Wed, 18 Jun 2003 22:48:23)
> > > > > > > > > 
> > > > > > > > > I agree.   That is what is provided for in the RFC.  However, section 3.15 of
> > > > > > > > > the IG would require the SG to stop traffic when n < 2.  So, it must be
> > > > > > > > > struck.
> > > > > > > > > 
> > > > > > > > > --brian
> > > > > > > > [Samuel] Does new IG stop the traffic when n < 2 ?
> > > > > > > 
> > > > > > > Yes, it does.  On restart.
> > > > > > > 
> > > > > > Yes thats what everybody agrees that on start and restart case 'n' number
> > > > > > of ASPs to be in ACTIVE state.
> > > > > 
> > > > > Disagree wholeheartedly.  And this was never agreed.
> > > > > 
> > > > > What was agreed (except for Tolga) was that the RFC allowed the SG to either
> > > > > activate on one ASP or wait for 'n' and withhold NTFY(AS-ACTIVE) which was
> > > > > sufficient for both start and restart cases.
> > > > > 
> > > > section 5.4.1 says that minimum 'n' number of ASPs are required to handle 
> > > > total traffic load.Here my understanding is, craft person knows the
> > > > incoming traffic capacity based on some kind of 'traffic measurement
> > > > analysis',
> > > > and the same time craft person knows, to handle this incoming traffic an
> > > > SGP requires 'n' ASPs.Here the point is craft person can not maintain 'n'
> > > > ASPs to be in ACTIVE state throughout the traffic period but at least he
> > > > can make sure 'n' ASPs are ACTIVE when (initally) SG comes up.
> > > > 
> > > > > If an outage has been for a brief period and was not congestion related, there
> > > > > is no reason why traffic cannot be started on the first active ASP, or under
> > > > > emergency conditions for that matter.
> > > > This may happen while SGP is processing the load but it may not happen in
> > > > the beginning and a good network configuration should not allow these
> > > > kinds of problems to happen in the beginning.
> > > > 
> > > > > The start, restart and shutdown decisions were discussed in detail on the
> > > > > list.  Whether the SG waits for 1 or 'n' is an IMPLEMENTATION and OPERATIONAL
> > > > > decision.  The existing RFC provides for this in saying that the AS-ACTIVE
> > > > > state implies that "at least one" ASP is in the ASP-ACTIVE state for the AS.
> > > > > Also the RFC states that the SGP should withhold the NTFY(AS-ACTIVE) until 'n'
> > > > > ASPs are active if it is going to wait for 'n' ASPs (as it MAY do).  And it
> > > > > also says that the ASPs should coordinate amoungst themselves to ensure that
> > > > > 'n' are active.
> > > > This is left to the decision of the craft person, this case he can
> > > > configure n=1.
> > > > > 
> > > > > Let me give you an example of the negative effect of this change:  An SG is
> > > > > configured with n=256.  There are 257 ASPs.  2 are dead.  The AS will never
> > > > > activate.  Some carrier class system...
> > > > > 
> > > > If n=256, it is the responsibility of the operator to make sure and bring
> > > > up 256 ASPs to ACTIVE state at least in the beginning.
> > > > 
> > > > > Contrast this where, soley at the SG implementer's discretion, the SG
> > > > > implementor sets a timer when the first ASP goes ASP-ACTIVE for the AS.  If
> > > > > the other 255 are not active by the time this timer expires, it sends
> > > > > NTFY(AS-ACTIVE) and starts traffic.  This system will always come up in
> > > > > contrast to the above that will not.  The RFC allows for this system, the
> > > > > new IG text does not.
> > > > > 
> > > > > The new IG text would have you implement the system that will never come up
> > > > > with 2 ASPs out of service.  The RFC does not.
> > > > 
> > > > section 5.1.4
> > > >    n+k case
> > > >    --------
> > > >    This scenario shows the example M3UA message flows for the
> > > >    establishment of traffic between an SGP and three ASPs in the same
> > > >    Application Server, where two of the ASPs are brought to the state
> > > >    ASP-ACTIVE and subsequently share the load.  In this case, a minimum
> > > >    of two ASPs are required to handle the total traffic load (2+1
> > > >    sparing).
> > > > 
> > > > still RFC says '... a minimum of two ASPs are required to handle the total
> > > > traffic load ....'
> > > > 
> > > > > 
> > > > > I you wan to explain things in the IG, go ahead, but the proposed text does
> > > > > not do that.  The proposed text makes changes to the normal and correct
> > > > > operation as laid out in the RFC and starts making implementation and
> > > > > operational decisions for the SG designer that it must not.
> > > > > 
> > > > > --brian
> > > > > 
> > > > 
> > > > I have conveyed my understanding to all. Otherwise in order to conclude 
> > > > this issue we can go for polling.
> > > > 
> > > > --Samuel
> > > > > -- 
> > > > > Brian F. G. Bidulock
> > > > > bidulock@openss7.org
> > > > > http://www.openss7.org/
> > > > > 
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > 
> > > -- 
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > > 
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > 
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 


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



From exim@www1.ietf.org  Fri Jun 20 04:11:33 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20819
	for <sigtran-archive@odin.ietf.org>; Fri, 20 Jun 2003 04:11:32 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5K8B4B05155
	for sigtran-archive@odin.ietf.org; Fri, 20 Jun 2003 04:11:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19TGz7-0001Ku-FG; Fri, 20 Jun 2003 04:11:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19TGyu-0001Kj-Sp
	for sigtran@optimus.ietf.org; Fri, 20 Jun 2003 04:10:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20803
	for <sigtran@ietf.org>; Fri, 20 Jun 2003 04:10:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TGwb-0000TW-00
	for sigtran@ietf.org; Fri, 20 Jun 2003 04:08:25 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[YQVgavkWDzmK1RenvUwN+Zov7F/WqSZU])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TGwa-0000TT-00
	for sigtran@ietf.org; Fri, 20 Jun 2003 04:08:24 -0400
Received: from ns.pigworks.openss7.net (IDENT:nVMPcjwPUsVH46QQVE+bGJjysYD4s/Ix@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5K8AjX26706;
	Fri, 20 Jun 2003 02:10:45 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5K8Aiv31048;
	Fri, 20 Jun 2003 02:10:44 -0600
Date: Fri, 20 Jun 2003 02:10:44 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030620021044.A31022@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030619134432.A21852@openss7.org> <Pine.SOL.4.10.10306200114410.9866-100000@sun2594.ssd.usa.alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.4.10.10306200114410.9866-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Fri, Jun 20, 2003 at 01:23:19AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Samuel,

So, why do your ASPs have different point codes in the diagram?

--brian

Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 20 Jun 2003 01:23:19)
> 
> Brian,
>  Yes i understood 'n' is an AS specific number. But i have a freedom to
> comprise ASP1 and ASP2 in one AS having a single point code.It is just a
> matter of configuration.Ultimately i want to say SGP needs both ASPs to be
> be in ACTIVE state to process a given explained call.
> 
> 
> --Samuel
> 
>   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> 
> On Thu, 19 Jun 2003, Brian F. G. Bidulock wrote:
> 
> > Samuel,
> > 
> > These are two different AS.  'n' is an AS specific number.
> > 
> > --brian
> > 
> > Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 19 Jun 2003 06:56:10)
> > > 
> > > Brian,
> > > 
> > > 
> > >                         +----+                  +-----+
> > >                         |STP-|------------------| ASP1| SCP (1-1-1)
> > >      +------------------| SG |------+           +-----+
> > >      |                  +----+      |  
> > >      |                              |           +-----+
> > >      |                              +-----------| ASP2| MGC(2-2-2)
> > >      |                                          +-----+
> > >      |                      
> > >  Conventional SS7
> > > 
> > > 
> > > 
> > > Consider a call which needs to access database (ASP1) and then
> > > to be routed to ASP2.
> > > In this case if we configure n=2 and 'n' as a mandatory,then
> > > the call will pass. This same will fail if n is not a mandatory
> > > as SG started processing the traffic as soon as one of the ASPs
> > > becomes available.The unavailability of another ASP will
> > > fail the call.
> > > 
> > > So we need to have certain restrictions to make 'n' as mandatory
> > > to process the call successfully.
> > > 
> > > --Samuel
> > > 
> > > 
> > > On Thu, 19 Jun 2003, Brian F. G. Bidulock wrote:
> > > 
> > > > Samuel,
> > > > 
> > > > 'n' (as agreed by concensus, and included in the new IG text as well) is the
> > > > number of ASP required to handle the "maximum engineered load", not the normal
> > > > load, or event the expected load.  So, for an ISUP bearing system, if it is
> > > > not Christmas or Mother's day, and there is not a significant backlog of
> > > > reattempt traffic (extended outage), the system can come up with less than 'n'
> > > > processors, as 'n' is defined.  Therefore, refusing to start or restart an
> > > > AS with less than 'n' active ASPs is foolish.
> > > > 
> > > > Setting n to 1, as you suggest, would be incorrect.  1 ASP cannot handle the
> > > > "maximum engineered load".  In the example, it takes 256 ASPs to handle the
> > > > "maximum engineered load" (e.g. busy-hour on Mother's Day).  But for the other
> > > > 340 some days of the year, some lesser number of ASPs is sufficient, and 255
> > > > ASPs is surely sufficient.
> > > > 
> > > > Not permitting the SG to start or restart with less than 'n' ASPs active
> > > > is a bad thing for carrier class systems.
> > > > 
> > > > I cannot agree with the change on these grounds.
> > > > 
> > > > --brian
> > > > 
> > > > 
> > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 19 Jun 2003 00:42:05)
> > > > > 
> > > > > Brian,
> > > > > 
> > > > > 
> > > > > On Wed, 18 Jun 2003, Brian F. G. Bidulock wrote:
> > > > > 
> > > > > > Samuel,
> > > > > > 
> > > > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Wed, 18 Jun 2003 22:48:23)
> > > > > > > > > > 
> > > > > > > > > > I agree.   That is what is provided for in the RFC.  However, section 3.15 of
> > > > > > > > > > the IG would require the SG to stop traffic when n < 2.  So, it must be
> > > > > > > > > > struck.
> > > > > > > > > > 
> > > > > > > > > > --brian
> > > > > > > > > [Samuel] Does new IG stop the traffic when n < 2 ?
> > > > > > > > 
> > > > > > > > Yes, it does.  On restart.
> > > > > > > > 
> > > > > > > Yes thats what everybody agrees that on start and restart case 'n' number
> > > > > > > of ASPs to be in ACTIVE state.
> > > > > > 
> > > > > > Disagree wholeheartedly.  And this was never agreed.
> > > > > > 
> > > > > > What was agreed (except for Tolga) was that the RFC allowed the SG to either
> > > > > > activate on one ASP or wait for 'n' and withhold NTFY(AS-ACTIVE) which was
> > > > > > sufficient for both start and restart cases.
> > > > > > 
> > > > > section 5.4.1 says that minimum 'n' number of ASPs are required to handle 
> > > > > total traffic load.Here my understanding is, craft person knows the
> > > > > incoming traffic capacity based on some kind of 'traffic measurement
> > > > > analysis',
> > > > > and the same time craft person knows, to handle this incoming traffic an
> > > > > SGP requires 'n' ASPs.Here the point is craft person can not maintain 'n'
> > > > > ASPs to be in ACTIVE state throughout the traffic period but at least he
> > > > > can make sure 'n' ASPs are ACTIVE when (initally) SG comes up.
> > > > > 
> > > > > > If an outage has been for a brief period and was not congestion related, there
> > > > > > is no reason why traffic cannot be started on the first active ASP, or under
> > > > > > emergency conditions for that matter.
> > > > > This may happen while SGP is processing the load but it may not happen in
> > > > > the beginning and a good network configuration should not allow these
> > > > > kinds of problems to happen in the beginning.
> > > > > 
> > > > > > The start, restart and shutdown decisions were discussed in detail on the
> > > > > > list.  Whether the SG waits for 1 or 'n' is an IMPLEMENTATION and OPERATIONAL
> > > > > > decision.  The existing RFC provides for this in saying that the AS-ACTIVE
> > > > > > state implies that "at least one" ASP is in the ASP-ACTIVE state for the AS.
> > > > > > Also the RFC states that the SGP should withhold the NTFY(AS-ACTIVE) until 'n'
> > > > > > ASPs are active if it is going to wait for 'n' ASPs (as it MAY do).  And it
> > > > > > also says that the ASPs should coordinate amoungst themselves to ensure that
> > > > > > 'n' are active.
> > > > > This is left to the decision of the craft person, this case he can
> > > > > configure n=1.
> > > > > > 
> > > > > > Let me give you an example of the negative effect of this change:  An SG is
> > > > > > configured with n=256.  There are 257 ASPs.  2 are dead.  The AS will never
> > > > > > activate.  Some carrier class system...
> > > > > > 
> > > > > If n=256, it is the responsibility of the operator to make sure and bring
> > > > > up 256 ASPs to ACTIVE state at least in the beginning.
> > > > > 
> > > > > > Contrast this where, soley at the SG implementer's discretion, the SG
> > > > > > implementor sets a timer when the first ASP goes ASP-ACTIVE for the AS.  If
> > > > > > the other 255 are not active by the time this timer expires, it sends
> > > > > > NTFY(AS-ACTIVE) and starts traffic.  This system will always come up in
> > > > > > contrast to the above that will not.  The RFC allows for this system, the
> > > > > > new IG text does not.
> > > > > > 
> > > > > > The new IG text would have you implement the system that will never come up
> > > > > > with 2 ASPs out of service.  The RFC does not.
> > > > > 
> > > > > section 5.1.4
> > > > >    n+k case
> > > > >    --------
> > > > >    This scenario shows the example M3UA message flows for the
> > > > >    establishment of traffic between an SGP and three ASPs in the same
> > > > >    Application Server, where two of the ASPs are brought to the state
> > > > >    ASP-ACTIVE and subsequently share the load.  In this case, a minimum
> > > > >    of two ASPs are required to handle the total traffic load (2+1
> > > > >    sparing).
> > > > > 
> > > > > still RFC says '... a minimum of two ASPs are required to handle the total
> > > > > traffic load ....'
> > > > > 
> > > > > > 
> > > > > > I you wan to explain things in the IG, go ahead, but the proposed text does
> > > > > > not do that.  The proposed text makes changes to the normal and correct
> > > > > > operation as laid out in the RFC and starts making implementation and
> > > > > > operational decisions for the SG designer that it must not.
> > > > > > 
> > > > > > --brian
> > > > > > 
> > > > > 
> > > > > I have conveyed my understanding to all. Otherwise in order to conclude 
> > > > > this issue we can go for polling.
> > > > > 
> > > > > --Samuel
> > > > > > -- 
> > > > > > Brian F. G. Bidulock
> > > > > > bidulock@openss7.org
> > > > > > http://www.openss7.org/
> > > > > > 
> > > > > 
> > > > > 
> > > > > _______________________________________________
> > > > > Sigtran mailing list
> > > > > Sigtran@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > 
> > > > -- 
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > > 
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > 
> > 
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Fri Jun 20 05:28:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22954
	for <sigtran-archive@odin.ietf.org>; Fri, 20 Jun 2003 05:28:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5K9S1V23200
	for sigtran-archive@odin.ietf.org; Fri, 20 Jun 2003 05:28:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19TIBd-00061x-1I; Fri, 20 Jun 2003 05:28:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19TIAs-00061e-7P
	for sigtran@optimus.ietf.org; Fri, 20 Jun 2003 05:27:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22936
	for <sigtran@ietf.org>; Fri, 20 Jun 2003 05:27:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TI8W-00013n-00
	for sigtran@ietf.org; Fri, 20 Jun 2003 05:24:48 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TI8V-00013a-00
	for sigtran@ietf.org; Fri, 20 Jun 2003 05:24:47 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h5K9QeB3012864;
	Fri, 20 Jun 2003 04:26:40 -0500 (CDT)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h5K9QP1C029155;
	Fri, 20 Jun 2003 04:26:25 -0500 (CDT)
Date: Fri, 20 Jun 2003 04:26:25 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
In-Reply-To: <20030620021044.A31022@openss7.org>
Message-ID: <Pine.SOL.4.10.10306200424440.9866-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


Brian,
I meant to say ASP1 and ASP2 are in a single SPMC which has a single point
code.

--Samuel

  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******

On Fri, 20 Jun 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> So, why do your ASPs have different point codes in the diagram?
> 
> --brian
> 
> Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 20 Jun 2003 01:23:19)
> > 
> > Brian,
> >  Yes i understood 'n' is an AS specific number. But i have a freedom to
> > comprise ASP1 and ASP2 in one AS having a single point code.It is just a
> > matter of configuration.Ultimately i want to say SGP needs both ASPs to be
> > be in ACTIVE state to process a given explained call.
> > 
> > 
> > --Samuel
> > 
> >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> > 
> > On Thu, 19 Jun 2003, Brian F. G. Bidulock wrote:
> > 
> > > Samuel,
> > > 
> > > These are two different AS.  'n' is an AS specific number.
> > > 
> > > --brian
> > > 
> > > Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 19 Jun 2003 06:56:10)
> > > > 
> > > > Brian,
> > > > 
> > > > 
> > > >                         +----+                  +-----+
> > > >                         |STP-|------------------| ASP1| SCP (1-1-1)
> > > >      +------------------| SG |------+           +-----+
> > > >      |                  +----+      |  
> > > >      |                              |           +-----+
> > > >      |                              +-----------| ASP2| MGC(2-2-2)
> > > >      |                                          +-----+
> > > >      |                      
> > > >  Conventional SS7
> > > > 
> > > > 
> > > > 
> > > > Consider a call which needs to access database (ASP1) and then
> > > > to be routed to ASP2.
> > > > In this case if we configure n=2 and 'n' as a mandatory,then
> > > > the call will pass. This same will fail if n is not a mandatory
> > > > as SG started processing the traffic as soon as one of the ASPs
> > > > becomes available.The unavailability of another ASP will
> > > > fail the call.
> > > > 
> > > > So we need to have certain restrictions to make 'n' as mandatory
> > > > to process the call successfully.
> > > > 
> > > > --Samuel
> > > > 
> > > > 
> > > > On Thu, 19 Jun 2003, Brian F. G. Bidulock wrote:
> > > > 
> > > > > Samuel,
> > > > > 
> > > > > 'n' (as agreed by concensus, and included in the new IG text as well) is the
> > > > > number of ASP required to handle the "maximum engineered load", not the normal
> > > > > load, or event the expected load.  So, for an ISUP bearing system, if it is
> > > > > not Christmas or Mother's day, and there is not a significant backlog of
> > > > > reattempt traffic (extended outage), the system can come up with less than 'n'
> > > > > processors, as 'n' is defined.  Therefore, refusing to start or restart an
> > > > > AS with less than 'n' active ASPs is foolish.
> > > > > 
> > > > > Setting n to 1, as you suggest, would be incorrect.  1 ASP cannot handle the
> > > > > "maximum engineered load".  In the example, it takes 256 ASPs to handle the
> > > > > "maximum engineered load" (e.g. busy-hour on Mother's Day).  But for the other
> > > > > 340 some days of the year, some lesser number of ASPs is sufficient, and 255
> > > > > ASPs is surely sufficient.
> > > > > 
> > > > > Not permitting the SG to start or restart with less than 'n' ASPs active
> > > > > is a bad thing for carrier class systems.
> > > > > 
> > > > > I cannot agree with the change on these grounds.
> > > > > 
> > > > > --brian
> > > > > 
> > > > > 
> > > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 19 Jun 2003 00:42:05)
> > > > > > 
> > > > > > Brian,
> > > > > > 
> > > > > > 
> > > > > > On Wed, 18 Jun 2003, Brian F. G. Bidulock wrote:
> > > > > > 
> > > > > > > Samuel,
> > > > > > > 
> > > > > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Wed, 18 Jun 2003 22:48:23)
> > > > > > > > > > > 
> > > > > > > > > > > I agree.   That is what is provided for in the RFC.  However, section 3.15 of
> > > > > > > > > > > the IG would require the SG to stop traffic when n < 2.  So, it must be
> > > > > > > > > > > struck.
> > > > > > > > > > > 
> > > > > > > > > > > --brian
> > > > > > > > > > [Samuel] Does new IG stop the traffic when n < 2 ?
> > > > > > > > > 
> > > > > > > > > Yes, it does.  On restart.
> > > > > > > > > 
> > > > > > > > Yes thats what everybody agrees that on start and restart case 'n' number
> > > > > > > > of ASPs to be in ACTIVE state.
> > > > > > > 
> > > > > > > Disagree wholeheartedly.  And this was never agreed.
> > > > > > > 
> > > > > > > What was agreed (except for Tolga) was that the RFC allowed the SG to either
> > > > > > > activate on one ASP or wait for 'n' and withhold NTFY(AS-ACTIVE) which was
> > > > > > > sufficient for both start and restart cases.
> > > > > > > 
> > > > > > section 5.4.1 says that minimum 'n' number of ASPs are required to handle 
> > > > > > total traffic load.Here my understanding is, craft person knows the
> > > > > > incoming traffic capacity based on some kind of 'traffic measurement
> > > > > > analysis',
> > > > > > and the same time craft person knows, to handle this incoming traffic an
> > > > > > SGP requires 'n' ASPs.Here the point is craft person can not maintain 'n'
> > > > > > ASPs to be in ACTIVE state throughout the traffic period but at least he
> > > > > > can make sure 'n' ASPs are ACTIVE when (initally) SG comes up.
> > > > > > 
> > > > > > > If an outage has been for a brief period and was not congestion related, there
> > > > > > > is no reason why traffic cannot be started on the first active ASP, or under
> > > > > > > emergency conditions for that matter.
> > > > > > This may happen while SGP is processing the load but it may not happen in
> > > > > > the beginning and a good network configuration should not allow these
> > > > > > kinds of problems to happen in the beginning.
> > > > > > 
> > > > > > > The start, restart and shutdown decisions were discussed in detail on the
> > > > > > > list.  Whether the SG waits for 1 or 'n' is an IMPLEMENTATION and OPERATIONAL
> > > > > > > decision.  The existing RFC provides for this in saying that the AS-ACTIVE
> > > > > > > state implies that "at least one" ASP is in the ASP-ACTIVE state for the AS.
> > > > > > > Also the RFC states that the SGP should withhold the NTFY(AS-ACTIVE) until 'n'
> > > > > > > ASPs are active if it is going to wait for 'n' ASPs (as it MAY do).  And it
> > > > > > > also says that the ASPs should coordinate amoungst themselves to ensure that
> > > > > > > 'n' are active.
> > > > > > This is left to the decision of the craft person, this case he can
> > > > > > configure n=1.
> > > > > > > 
> > > > > > > Let me give you an example of the negative effect of this change:  An SG is
> > > > > > > configured with n=256.  There are 257 ASPs.  2 are dead.  The AS will never
> > > > > > > activate.  Some carrier class system...
> > > > > > > 
> > > > > > If n=256, it is the responsibility of the operator to make sure and bring
> > > > > > up 256 ASPs to ACTIVE state at least in the beginning.
> > > > > > 
> > > > > > > Contrast this where, soley at the SG implementer's discretion, the SG
> > > > > > > implementor sets a timer when the first ASP goes ASP-ACTIVE for the AS.  If
> > > > > > > the other 255 are not active by the time this timer expires, it sends
> > > > > > > NTFY(AS-ACTIVE) and starts traffic.  This system will always come up in
> > > > > > > contrast to the above that will not.  The RFC allows for this system, the
> > > > > > > new IG text does not.
> > > > > > > 
> > > > > > > The new IG text would have you implement the system that will never come up
> > > > > > > with 2 ASPs out of service.  The RFC does not.
> > > > > > 
> > > > > > section 5.1.4
> > > > > >    n+k case
> > > > > >    --------
> > > > > >    This scenario shows the example M3UA message flows for the
> > > > > >    establishment of traffic between an SGP and three ASPs in the same
> > > > > >    Application Server, where two of the ASPs are brought to the state
> > > > > >    ASP-ACTIVE and subsequently share the load.  In this case, a minimum
> > > > > >    of two ASPs are required to handle the total traffic load (2+1
> > > > > >    sparing).
> > > > > > 
> > > > > > still RFC says '... a minimum of two ASPs are required to handle the total
> > > > > > traffic load ....'
> > > > > > 
> > > > > > > 
> > > > > > > I you wan to explain things in the IG, go ahead, but the proposed text does
> > > > > > > not do that.  The proposed text makes changes to the normal and correct
> > > > > > > operation as laid out in the RFC and starts making implementation and
> > > > > > > operational decisions for the SG designer that it must not.
> > > > > > > 
> > > > > > > --brian
> > > > > > > 
> > > > > > 
> > > > > > I have conveyed my understanding to all. Otherwise in order to conclude 
> > > > > > this issue we can go for polling.
> > > > > > 
> > > > > > --Samuel
> > > > > > > -- 
> > > > > > > Brian F. G. Bidulock
> > > > > > > bidulock@openss7.org
> > > > > > > http://www.openss7.org/
> > > > > > > 
> > > > > > 
> > > > > > 
> > > > > > _______________________________________________
> > > > > > Sigtran mailing list
> > > > > > Sigtran@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > 
> > > > > -- 
> > > > > Brian F. G. Bidulock
> > > > > bidulock@openss7.org
> > > > > http://www.openss7.org/
> > > > > 
> > > > > _______________________________________________
> > > > > Sigtran mailing list
> > > > > Sigtran@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > 
> > > 
> > > -- 
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > > 
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > 
> > 
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 


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



From exim@www1.ietf.org  Fri Jun 20 07:32:32 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25601
	for <sigtran-archive@odin.ietf.org>; Fri, 20 Jun 2003 07:32:32 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5KBW3215960
	for sigtran-archive@odin.ietf.org; Fri, 20 Jun 2003 07:32:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19TK7d-000498-IV; Fri, 20 Jun 2003 07:32:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19TK6f-00047F-UH
	for sigtran@optimus.ietf.org; Fri, 20 Jun 2003 07:31:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25546
	for <sigtran@ietf.org>; Fri, 20 Jun 2003 07:31:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TK4K-0001cA-00
	for sigtran@ietf.org; Fri, 20 Jun 2003 07:28:36 -0400
Received: from web12803.mail.yahoo.com ([216.136.174.38])
	by ietf-mx with smtp (Exim 4.12)
	id 19TK4J-0001c7-00
	for sigtran@ietf.org; Fri, 20 Jun 2003 07:28:35 -0400
Message-ID: <20030620113059.3861.qmail@web12803.mail.yahoo.com>
Received: from [208.255.120.2] by web12803.mail.yahoo.com via HTTP; Fri, 20 Jun 2003 04:30:59 PDT
Date: Fri, 20 Jun 2003 04:30:59 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] Re: M3UA Notify message
To: sigtran@ietf.org
In-Reply-To: <20030619131704.A21325@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,

[..snip..]
> > [TOLGA]For this case, IMO n=1 (or whatever is the
> > number of ASPs, which should be ACTIVE at
> minimum)is
> > correct. I don't interprete n as number of maximum
> > ASPs, which can be ACTIVE at any given time. n is
> the
> > number of ASPs, which should be ACTIVE, so that AS
> > switches to ACTIVE state. For example, if n=3,
> this
> > IMO does not mean that I can't have 256 ASPs
> ACTIVE at
> > any given time. So, for your example, you set
> > n=sufficient number of ASPs(something less than
> 256). 
> > Maybe using the term n+k for this kind of
> operation is
> > what you don't like?
> 
> But that would change the meaning of 'n' from the
> agreed
> "maximum engineered load".
[TOLGA]To be honest, if the agreement is to interprete
n as the maximum number of ASPs, which can be ACTIVE
at any time, I disagree with this -and yes IMO
"maximum engineered load" might be a misleading term
for n-. But I think, the way of operation explained
above is reasonable, and probably what people would
agree in general(?). IMO, the importance of n from
M3UA point of view is, that based on n, AS state
change to ACTIVE happens -so it is more "minimum
number of required ASPs". 
> 
> --brian
> 


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

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



From exim@www1.ietf.org  Fri Jun 20 08:50:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04470
	for <sigtran-archive@odin.ietf.org>; Fri, 20 Jun 2003 08:50:31 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5KCo3O09369
	for sigtran-archive@odin.ietf.org; Fri, 20 Jun 2003 08:50:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19TLL7-0002Qk-Jq; Fri, 20 Jun 2003 08:50:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19TLKN-0002Cx-NI
	for sigtran@optimus.ietf.org; Fri, 20 Jun 2003 08:49:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04352
	for <sigtran@ietf.org>; Fri, 20 Jun 2003 08:49:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TLI1-0003gf-00
	for sigtran@ietf.org; Fri, 20 Jun 2003 08:46:49 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[2fZtbpjuaWDx7Oz37REEOcen03wOzIPS])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TLI0-0003gX-00
	for sigtran@ietf.org; Fri, 20 Jun 2003 08:46:48 -0400
Received: from ns.pigworks.openss7.net (IDENT:eWy4dL+XaSuJ2ZGKFCnqsJKTqIkp9YN6@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5KCnBX31000;
	Fri, 20 Jun 2003 06:49:11 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5KCnA602264;
	Fri, 20 Jun 2003 06:49:10 -0600
Date: Fri, 20 Jun 2003 06:49:10 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030620064910.A2194@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030620021044.A31022@openss7.org> <Pine.SOL.4.10.10306200424440.9866-100000@sun2594.ssd.usa.alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.4.10.10306200424440.9866-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Fri, Jun 20, 2003 at 04:26:25AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Samuel,

Could you, then, please explain how your example has anything to do with 'n'?

--brian


Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 20 Jun 2003 04:26:25)
> 
> Brian,
> I meant to say ASP1 and ASP2 are in a single SPMC which has a single point
> code.
> 
> --Samuel
> 
>   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> 
> On Fri, 20 Jun 2003, Brian F. G. Bidulock wrote:
> 
> > Samuel,
> > 
> > So, why do your ASPs have different point codes in the diagram?
> > 
> > --brian
> > 
> > Samuel Dur D. Jeyaseelan wrote:                                                     (Fri, 20 Jun 2003 01:23:19)
> > > 
> > > Brian,
> > >  Yes i understood 'n' is an AS specific number. But i have a freedom to
> > > comprise ASP1 and ASP2 in one AS having a single point code.It is just a
> > > matter of configuration.Ultimately i want to say SGP needs both ASPs to be
> > > be in ACTIVE state to process a given explained call.
> > > 
> > > 
> > > --Samuel
> > > 
> > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
> > >   1000 Coit Road, Plano, Texas 75075
> > >   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> > > 
> > > On Thu, 19 Jun 2003, Brian F. G. Bidulock wrote:
> > > 
> > > > Samuel,
> > > > 
> > > > These are two different AS.  'n' is an AS specific number.
> > > > 
> > > > --brian
> > > > 
> > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 19 Jun 2003 06:56:10)
> > > > > 
> > > > > Brian,
> > > > > 
> > > > > 
> > > > >                         +----+                  +-----+
> > > > >                         |STP-|------------------| ASP1| SCP (1-1-1)
> > > > >      +------------------| SG |------+           +-----+
> > > > >      |                  +----+      |  
> > > > >      |                              |           +-----+
> > > > >      |                              +-----------| ASP2| MGC(2-2-2)
> > > > >      |                                          +-----+
> > > > >      |                      
> > > > >  Conventional SS7
> > > > > 
> > > > > 
> > > > > 
> > > > > Consider a call which needs to access database (ASP1) and then
> > > > > to be routed to ASP2.
> > > > > In this case if we configure n=2 and 'n' as a mandatory,then
> > > > > the call will pass. This same will fail if n is not a mandatory
> > > > > as SG started processing the traffic as soon as one of the ASPs
> > > > > becomes available.The unavailability of another ASP will
> > > > > fail the call.
> > > > > 
> > > > > So we need to have certain restrictions to make 'n' as mandatory
> > > > > to process the call successfully.
> > > > > 
> > > > > --Samuel
> > > > > 
> > > > > 
> > > > > On Thu, 19 Jun 2003, Brian F. G. Bidulock wrote:
> > > > > 
> > > > > > Samuel,
> > > > > > 
> > > > > > 'n' (as agreed by concensus, and included in the new IG text as well) is the
> > > > > > number of ASP required to handle the "maximum engineered load", not the normal
> > > > > > load, or event the expected load.  So, for an ISUP bearing system, if it is
> > > > > > not Christmas or Mother's day, and there is not a significant backlog of
> > > > > > reattempt traffic (extended outage), the system can come up with less than 'n'
> > > > > > processors, as 'n' is defined.  Therefore, refusing to start or restart an
> > > > > > AS with less than 'n' active ASPs is foolish.
> > > > > > 
> > > > > > Setting n to 1, as you suggest, would be incorrect.  1 ASP cannot handle the
> > > > > > "maximum engineered load".  In the example, it takes 256 ASPs to handle the
> > > > > > "maximum engineered load" (e.g. busy-hour on Mother's Day).  But for the other
> > > > > > 340 some days of the year, some lesser number of ASPs is sufficient, and 255
> > > > > > ASPs is surely sufficient.
> > > > > > 
> > > > > > Not permitting the SG to start or restart with less than 'n' ASPs active
> > > > > > is a bad thing for carrier class systems.
> > > > > > 
> > > > > > I cannot agree with the change on these grounds.
> > > > > > 
> > > > > > --brian
> > > > > > 
> > > > > > 
> > > > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 19 Jun 2003 00:42:05)
> > > > > > > 
> > > > > > > Brian,
> > > > > > > 
> > > > > > > 
> > > > > > > On Wed, 18 Jun 2003, Brian F. G. Bidulock wrote:
> > > > > > > 
> > > > > > > > Samuel,
> > > > > > > > 
> > > > > > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Wed, 18 Jun 2003 22:48:23)
> > > > > > > > > > > > 
> > > > > > > > > > > > I agree.   That is what is provided for in the RFC.  However, section 3.15 of
> > > > > > > > > > > > the IG would require the SG to stop traffic when n < 2.  So, it must be
> > > > > > > > > > > > struck.
> > > > > > > > > > > > 
> > > > > > > > > > > > --brian
> > > > > > > > > > > [Samuel] Does new IG stop the traffic when n < 2 ?
> > > > > > > > > > 
> > > > > > > > > > Yes, it does.  On restart.
> > > > > > > > > > 
> > > > > > > > > Yes thats what everybody agrees that on start and restart case 'n' number
> > > > > > > > > of ASPs to be in ACTIVE state.
> > > > > > > > 
> > > > > > > > Disagree wholeheartedly.  And this was never agreed.
> > > > > > > > 
> > > > > > > > What was agreed (except for Tolga) was that the RFC allowed the SG to either
> > > > > > > > activate on one ASP or wait for 'n' and withhold NTFY(AS-ACTIVE) which was
> > > > > > > > sufficient for both start and restart cases.
> > > > > > > > 
> > > > > > > section 5.4.1 says that minimum 'n' number of ASPs are required to handle 
> > > > > > > total traffic load.Here my understanding is, craft person knows the
> > > > > > > incoming traffic capacity based on some kind of 'traffic measurement
> > > > > > > analysis',
> > > > > > > and the same time craft person knows, to handle this incoming traffic an
> > > > > > > SGP requires 'n' ASPs.Here the point is craft person can not maintain 'n'
> > > > > > > ASPs to be in ACTIVE state throughout the traffic period but at least he
> > > > > > > can make sure 'n' ASPs are ACTIVE when (initally) SG comes up.
> > > > > > > 
> > > > > > > > If an outage has been for a brief period and was not congestion related, there
> > > > > > > > is no reason why traffic cannot be started on the first active ASP, or under
> > > > > > > > emergency conditions for that matter.
> > > > > > > This may happen while SGP is processing the load but it may not happen in
> > > > > > > the beginning and a good network configuration should not allow these
> > > > > > > kinds of problems to happen in the beginning.
> > > > > > > 
> > > > > > > > The start, restart and shutdown decisions were discussed in detail on the
> > > > > > > > list.  Whether the SG waits for 1 or 'n' is an IMPLEMENTATION and OPERATIONAL
> > > > > > > > decision.  The existing RFC provides for this in saying that the AS-ACTIVE
> > > > > > > > state implies that "at least one" ASP is in the ASP-ACTIVE state for the AS.
> > > > > > > > Also the RFC states that the SGP should withhold the NTFY(AS-ACTIVE) until 'n'
> > > > > > > > ASPs are active if it is going to wait for 'n' ASPs (as it MAY do).  And it
> > > > > > > > also says that the ASPs should coordinate amoungst themselves to ensure that
> > > > > > > > 'n' are active.
> > > > > > > This is left to the decision of the craft person, this case he can
> > > > > > > configure n=1.
> > > > > > > > 
> > > > > > > > Let me give you an example of the negative effect of this change:  An SG is
> > > > > > > > configured with n=256.  There are 257 ASPs.  2 are dead.  The AS will never
> > > > > > > > activate.  Some carrier class system...
> > > > > > > > 
> > > > > > > If n=256, it is the responsibility of the operator to make sure and bring
> > > > > > > up 256 ASPs to ACTIVE state at least in the beginning.
> > > > > > > 
> > > > > > > > Contrast this where, soley at the SG implementer's discretion, the SG
> > > > > > > > implementor sets a timer when the first ASP goes ASP-ACTIVE for the AS.  If
> > > > > > > > the other 255 are not active by the time this timer expires, it sends
> > > > > > > > NTFY(AS-ACTIVE) and starts traffic.  This system will always come up in
> > > > > > > > contrast to the above that will not.  The RFC allows for this system, the
> > > > > > > > new IG text does not.
> > > > > > > > 
> > > > > > > > The new IG text would have you implement the system that will never come up
> > > > > > > > with 2 ASPs out of service.  The RFC does not.
> > > > > > > 
> > > > > > > section 5.1.4
> > > > > > >    n+k case
> > > > > > >    --------
> > > > > > >    This scenario shows the example M3UA message flows for the
> > > > > > >    establishment of traffic between an SGP and three ASPs in the same
> > > > > > >    Application Server, where two of the ASPs are brought to the state
> > > > > > >    ASP-ACTIVE and subsequently share the load.  In this case, a minimum
> > > > > > >    of two ASPs are required to handle the total traffic load (2+1
> > > > > > >    sparing).
> > > > > > > 
> > > > > > > still RFC says '... a minimum of two ASPs are required to handle the total
> > > > > > > traffic load ....'
> > > > > > > 
> > > > > > > > 
> > > > > > > > I you wan to explain things in the IG, go ahead, but the proposed text does
> > > > > > > > not do that.  The proposed text makes changes to the normal and correct
> > > > > > > > operation as laid out in the RFC and starts making implementation and
> > > > > > > > operational decisions for the SG designer that it must not.
> > > > > > > > 
> > > > > > > > --brian
> > > > > > > > 
> > > > > > > 
> > > > > > > I have conveyed my understanding to all. Otherwise in order to conclude 
> > > > > > > this issue we can go for polling.
> > > > > > > 
> > > > > > > --Samuel
> > > > > > > > -- 
> > > > > > > > Brian F. G. Bidulock
> > > > > > > > bidulock@openss7.org
> > > > > > > > http://www.openss7.org/
> > > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > > _______________________________________________
> > > > > > > Sigtran mailing list
> > > > > > > Sigtran@ietf.org
> > > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > 
> > > > > > -- 
> > > > > > Brian F. G. Bidulock
> > > > > > bidulock@openss7.org
> > > > > > http://www.openss7.org/
> > > > > > 
> > > > > > _______________________________________________
> > > > > > Sigtran mailing list
> > > > > > Sigtran@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > > > 
> > > > 
> > > > -- 
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > > 
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > 
> > > 
> > > 
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> > 

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

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



From exim@www1.ietf.org  Fri Jun 20 08:55:30 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04647
	for <sigtran-archive@odin.ietf.org>; Fri, 20 Jun 2003 08:55:30 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5KCt2d11044
	for sigtran-archive@odin.ietf.org; Fri, 20 Jun 2003 08:55:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19TLPx-0002rt-N2; Fri, 20 Jun 2003 08:55:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19TLPq-0002rb-Qi
	for sigtran@optimus.ietf.org; Fri, 20 Jun 2003 08:54:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04641
	for <sigtran@ietf.org>; Fri, 20 Jun 2003 08:54:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TLNV-0003lH-00
	for sigtran@ietf.org; Fri, 20 Jun 2003 08:52:29 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[HEEmuKxWzHao/aA6+DnJWRNghn3Pxd6Q])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TLNU-0003lE-00
	for sigtran@ietf.org; Fri, 20 Jun 2003 08:52:28 -0400
Received: from ns.pigworks.openss7.net (IDENT:0HrhuqRjSVyW95bauiKnV/xdO1NYdA6s@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5KCspX31058;
	Fri, 20 Jun 2003 06:54:52 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5KCspg02332;
	Fri, 20 Jun 2003 06:54:51 -0600
Date: Fri, 20 Jun 2003 06:54:51 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030620065451.B2194@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030619131704.A21325@openss7.org> <20030620113059.3861.qmail@web12803.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030620113059.3861.qmail@web12803.mail.yahoo.com>; from tolga_asveren@yahoo.com on Fri, Jun 20, 2003 at 04:30:59AM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

Tolga Asveren wrote:                                                                 (Fri, 20 Jun 2003 04:30:59)
> Brian,
> 
> [..snip..]
> > > [TOLGA]For this case, IMO n=1 (or whatever is the
> > > number of ASPs, which should be ACTIVE at
> > minimum)is
> > > correct. I don't interprete n as number of maximum
> > > ASPs, which can be ACTIVE at any given time. n is
> > the
> > > number of ASPs, which should be ACTIVE, so that AS
> > > switches to ACTIVE state. For example, if n=3,
> > this
> > > IMO does not mean that I can't have 256 ASPs
> > ACTIVE at
> > > any given time. So, for your example, you set
> > > n=sufficient number of ASPs(something less than
> > 256). 
> > > Maybe using the term n+k for this kind of
> > operation is
> > > what you don't like?
> > 
> > But that would change the meaning of 'n' from the
> > agreed
> > "maximum engineered load".
> [TOLGA]To be honest, if the agreement is to interprete
> n as the maximum number of ASPs, which can be ACTIVE
> at any time, I disagree with this -and yes IMO
> "maximum engineered load" might be a misleading term
> for n-. But I think, the way of operation explained
> above is reasonable, and probably what people would
> agree in general(?). IMO, the importance of n from
> M3UA point of view is, that based on n, AS state
> change to ACTIVE happens -so it is more "minimum
> number of required ASPs". 

No such thing as "minimum number of required ASPs"
in carrier class systems.  Such an 'n' could not be
anything other than 1.

There is such thing as the minimum number of ASPs
required to handle the "maximum engineered load".
Such an 'n' can be greater than 1, and an SG cannot
be required to remain inactive when so much as 1 ASP
is active.

The latter is what the RFC already provides.  The IG
attempts to deviate from that without apparent cause
or purpose.

Please tell me: what bad thing do you think will
happen if the RFC is followed as it stands?

--brian

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

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



From exim@www1.ietf.org  Fri Jun 20 09:14:30 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05360
	for <sigtran-archive@odin.ietf.org>; Fri, 20 Jun 2003 09:14:30 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5KDE2G15793
	for sigtran-archive@odin.ietf.org; Fri, 20 Jun 2003 09:14:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19TLiL-00046c-Fn; Fri, 20 Jun 2003 09:14:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19TLhb-00044L-V2
	for sigtran@optimus.ietf.org; Fri, 20 Jun 2003 09:13:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05292
	for <sigtran@ietf.org>; Fri, 20 Jun 2003 09:13:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TLha-0003ut-00
	for sigtran@ietf.org; Fri, 20 Jun 2003 09:13:14 -0400
Received: from web12807.mail.yahoo.com ([216.136.174.42])
	by ietf-mx with smtp (Exim 4.12)
	id 19TLhZ-0003uq-00
	for sigtran@ietf.org; Fri, 20 Jun 2003 09:13:13 -0400
Message-ID: <20030620131311.51918.qmail@web12807.mail.yahoo.com>
Received: from [208.255.120.2] by web12807.mail.yahoo.com via HTTP; Fri, 20 Jun 2003 06:13:11 PDT
Date: Fri, 20 Jun 2003 06:13:11 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] Re: M3UA Notify message
To: sigtran@ietf.org
In-Reply-To: <20030620065451.B2194@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Tolga,
> 
> Tolga Asveren wrote:                                
>                                 (Fri, 20 Jun 2003
> 04:30:59)
> > Brian,
> > 
> > [..snip..]
> > > > [TOLGA]For this case, IMO n=1 (or whatever is
> the
> > > > number of ASPs, which should be ACTIVE at
> > > minimum)is
> > > > correct. I don't interprete n as number of
> maximum
> > > > ASPs, which can be ACTIVE at any given time. n
> is
> > > the
> > > > number of ASPs, which should be ACTIVE, so
> that AS
> > > > switches to ACTIVE state. For example, if n=3,
> > > this
> > > > IMO does not mean that I can't have 256 ASPs
> > > ACTIVE at
> > > > any given time. So, for your example, you set
> > > > n=sufficient number of ASPs(something less
> than
> > > 256). 
> > > > Maybe using the term n+k for this kind of
> > > operation is
> > > > what you don't like?
> > > 
> > > But that would change the meaning of 'n' from
> the
> > > agreed
> > > "maximum engineered load".
> > [TOLGA]To be honest, if the agreement is to
> interprete
> > n as the maximum number of ASPs, which can be
> ACTIVE
> > at any time, I disagree with this -and yes IMO
> > "maximum engineered load" might be a misleading
> term
> > for n-. But I think, the way of operation
> explained
> > above is reasonable, and probably what people
> would
> > agree in general(?). IMO, the importance of n from
> > M3UA point of view is, that based on n, AS state
> > change to ACTIVE happens -so it is more "minimum
> > number of required ASPs". 
> 
> No such thing as "minimum number of required ASPs"
> in carrier class systems.  Such an 'n' could not be
> anything other than 1.
> 
> There is such thing as the minimum number of ASPs
> required to handle the "maximum engineered load".
> Such an 'n' can be greater than 1, and an SG cannot
> be required to remain inactive when so much as 1 ASP
> is active.
> 
> The latter is what the RFC already provides.  The IG
> attempts to deviate from that without apparent cause
> or purpose.
> 
> Please tell me: what bad thing do you think will
> happen if the RFC is followed as it stands?
[TOLGA]It is obvious that RFC as it stands now is
WRONG, regarding n+k mode. Parts of it are written
without considering n>1 case. Now, if one thinks that
always n=1 (n being used as I refer above, i.e.
minimum number of ACTIVE ASPs to declare AS as
ACTIVE-)
then this is easy to achieve with IG, just use always
n=1. If one interpretes n as you describe -the value
to be used during mother's day-, IMO n has nothing to
do with M3UA AS state machine -so no need to mention
anything about it in M3UA documents-, something
totally different. 
The important thing IMO is that ASPs and SGPs have the
same AS state view. And to achieve this, when staet
change to ACTIVE for AS  happens, should be clearly
defined. RFC fails on this. Now, about the bad thing,
which can happen if this view is not the same, -as I
stated several times- SG might expose AS as available
to SS7 network, whereas in fact in wasn't available.
Nodes in SS7 domain will send traffic to AS but can't
get replies. This, IMO should be avoided.
Basically, I could understand if somebody advocates
the idea that n+k mode is useless (because n is going
to be always 1), but this would require striking out
everything related with n+k in both IG and RFC, not
just IG (and IMO because n+k mode includes n=1, there
is no need to put restrictions. For example, it migth
be usefull for a case, where the operator does not
want AS to be ACTIVE, unless two ASPs are ACTIVE, to
ensure redundancy at the startup. IMO, the value of n
is an operation issue)
IMO, the only thing, which could be modified in the
proposed text is not to use the term "maximum
engineered load", and explain maybe more openly, what
is meant with n.
> 
> --brian
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

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



From exim@www1.ietf.org  Fri Jun 20 16:34:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06849
	for <sigtran-archive@odin.ietf.org>; Fri, 20 Jun 2003 16:34:30 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5KKY3l01843
	for sigtran-archive@odin.ietf.org; Fri, 20 Jun 2003 16:34:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19TSa9-0000TR-IV; Fri, 20 Jun 2003 16:34:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19TSZo-0000T9-1c
	for sigtran@optimus.ietf.org; Fri, 20 Jun 2003 16:33:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06818
	for <sigtran@ietf.org>; Fri, 20 Jun 2003 16:33:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TSZm-0002rS-00
	for sigtran@ietf.org; Fri, 20 Jun 2003 16:33:38 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[kJnS6PQxAWvM71XLoOQysAQFSBdts03A])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TSZl-0002rO-00
	for sigtran@ietf.org; Fri, 20 Jun 2003 16:33:37 -0400
Received: from ns.pigworks.openss7.net (IDENT:gP8164tjA5hngPgmaylINssMpLQ1WTbU@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5KKXaX04835;
	Fri, 20 Jun 2003 14:33:36 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5KKXZR09403;
	Fri, 20 Jun 2003 14:33:35 -0600
Date: Fri, 20 Jun 2003 14:33:35 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030620143335.A9154@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030620065451.B2194@openss7.org> <20030620131311.51918.qmail@web12807.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030620131311.51918.qmail@web12807.mail.yahoo.com>; from tolga_asveren@yahoo.com on Fri, Jun 20, 2003 at 06:13:11AM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

Tolga Asveren wrote:                                                                 (Fri, 20 Jun 2003 06:13:11)
> > 
> > No such thing as "minimum number of required ASPs"
> > in carrier class systems.  Such an 'n' could not be
> > anything other than 1.
> > 
> > There is such thing as the minimum number of ASPs
> > required to handle the "maximum engineered load".
> > Such an 'n' can be greater than 1, and an SG cannot
> > be required to remain inactive when so much as 1 ASP
> > is active.
> > 
> > The latter is what the RFC already provides.  The IG
> > attempts to deviate from that without apparent cause
> > or purpose.
> > 
> > Please tell me: what bad thing do you think will
> > happen if the RFC is followed as it stands?
> [TOLGA]It is obvious that RFC as it stands now is
> WRONG, regarding n+k mode.

Where is it WRONG?

> Parts of it are written
> without considering n>1 case.

Which parts?

> Now, if one thinks that
> always n=1 (n being used as I refer above, i.e.
> minimum number of ACTIVE ASPs to declare AS as
> ACTIVE-)
> then this is easy to achieve with IG, just use always
> n=1.

Even the IG defines 'n' as the mininum number of ASPs
for "maximum engineered load".  So you would further
change the definition of 'n' again?  We already agreed
by concensus that 'n' was the minimum numebr of ASPs
for "maximum engineered load".

> If one interpretes n as you describe -the value
> to be used during mother's day-, IMO n has nothing to
> do with M3UA AS state machine -so no need to mention
> anything about it in M3UA documents-, something
> totally different. 

This was the concensus reached from the last discusssion.
If you don't care about such a definition of 'n' then
you shouldn't need to get further involved in these
dicussions.

> The important thing IMO is that ASPs and SGPs have the
> same AS state view. And to achieve this, when staet
> change to ACTIVE for AS  happens, should be clearly
> defined.

It is: SGP MUST send NTFY(AS-ACTIVE) when it moves the
AS to the AS-ACTIVE state.  This is provided for in the
RFC.  The ASP ALWAYS knows when the SGP determines that
an as is active from its view.

> RFC fails on this.

Simply wrong.  The SGP sending NTFY(AS-ACTIVE) ensures
that the SGP and ASP have the same view of AS state,
and not just for the AS-ACTIVE state.

> Now, about the bad thing,
> which can happen if this view is not the same,

Because of NTFY(AS-ACTIVE) the view cannot differ, so
no bad thing can happen based on mis-match of state.

> -as I
> stated several times- SG might expose AS as available
> to SS7 network, whereas in fact in wasn't available.

Can't happen.  Please try to describe an example message
flow in terms of M3UA messages.

> Nodes in SS7 domain will send traffic to AS but can't
> get replies.

Can't happen.  Please try to describe an example message
flow in terms of M3UA messages.

> This, IMO should be avoided.

It can't happen under exisint RFC.  This is precisely
why the NTFY(AS-ACTIVE) is withheld if the SG is going
to wait for 'n' ASPs to activate.  So that this can
never happen.

> Basically, I could understand if somebody advocates
> the idea that n+k mode is useless (because n is going
> to be always 1), but this would require striking out
> everything related with n+k in both IG and RFC, not
> just IG (and IMO because n+k mode includes n=1, there
> is no need to put restrictions. For example, it migth
> be usefull for a case, where the operator does not
> want AS to be ACTIVE, unless two ASPs are ACTIVE, to
> ensure redundancy at the startup. IMO, the value of n
> is an operation issue)

The existing RFC has the ability for the SGP to wait
for 'n' where n>1 and withhold NTFY)(AS-ACTIVE).  You
will not be removing this option either.

> IMO, the only thing, which could be modified in the
> proposed text is not to use the term "maximum
> engineered load", and explain maybe more openly, what
> is meant with n.

The only thing to do is scrap the proposed text.  The
SGP must be permitted to activate the AS with the first
ASP (and send NTFY(AS-ACTIVE) immediately) or activate
the AS with the 'n'th ASP (sending NTFY(AS-ACTIVE) only
after the 'n' ASP) or at some 'm' value or time expiration
somewhere in between.  It is the ASPss responsibility to
coordinate amongst themselves and get 'n' 0f them up.
If the APS needs 'n' or nothing, it should not activate
until it can be sure that n-1 other ASPs are also
activating.

This is what is already provided for in the RFC, regardless
of what one's view of 'n' is, the SGP is provided the option
to do the right thing, and the requirement to notify the
ASP of its decision (with NTFY(AS-ACTIVE)).

The only thing left to do is strike 3.15.

--brian


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

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



From exim@www1.ietf.org  Fri Jun 20 16:51:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07941
	for <sigtran-archive@odin.ietf.org>; Fri, 20 Jun 2003 16:51:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5KKp2a05269
	for sigtran-archive@odin.ietf.org; Fri, 20 Jun 2003 16:51:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19TSqb-0001Ms-Ry; Fri, 20 Jun 2003 16:51:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19TSpp-0001MG-2Q
	for sigtran@optimus.ietf.org; Fri, 20 Jun 2003 16:50:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07914
	for <sigtran@ietf.org>; Fri, 20 Jun 2003 16:50:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TSpn-00037Y-00
	for sigtran@ietf.org; Fri, 20 Jun 2003 16:50:11 -0400
Received: from web12801.mail.yahoo.com ([216.136.174.36])
	by ietf-mx with smtp (Exim 4.12)
	id 19TSpm-00037V-00
	for sigtran@ietf.org; Fri, 20 Jun 2003 16:50:10 -0400
Message-ID: <20030620205008.98400.qmail@web12801.mail.yahoo.com>
Received: from [208.255.120.2] by web12801.mail.yahoo.com via HTTP; Fri, 20 Jun 2003 13:50:08 PDT
Date: Fri, 20 Jun 2003 13:50:08 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] Re: M3UA Notify message
To: sigtran@ietf.org
In-Reply-To: <20030620143335.A9154@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,

1- NTFY has only advisory meaning, there is no
"SHOULD" action, which is to be taken after NTFY, so
your argument that ASPs can rely on NTFY is not valid
-you know it was proposed to make ASPs decide for the
AS state change by NTFY but it was not accepted,
because it was considered as a too radical change-.
Nowhere it is stated in RFC nor in IG, that ASPs
decide to accept/receive application traffic based on
NTFY.

2- RFC tells that ASPs SHOULD arrange number of ACTIVE
ASPs among themselves, but allows SG to start routing
traffic even with less than n ACTIVE ASP. Just look to
the definition of INACTIVE AS in RFC, an AS whith no
application traffic flowing to/from it. So, they might
have inconsistent views of AS state.

3- If n is to be seen as the mother day's value, IMO
it really has nothing to do with M3UA, because it
won't change AS state at all (or maybe you can give an
example about its relation to M3UA)

    Regards,
     Tolga  
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Tolga,
> 
> Tolga Asveren wrote:                                
>                                 (Fri, 20 Jun 2003
> 06:13:11)
> > > 
> > > No such thing as "minimum number of required
> ASPs"
> > > in carrier class systems.  Such an 'n' could not
> be
> > > anything other than 1.
> > > 
> > > There is such thing as the minimum number of
> ASPs
> > > required to handle the "maximum engineered
> load".
> > > Such an 'n' can be greater than 1, and an SG
> cannot
> > > be required to remain inactive when so much as 1
> ASP
> > > is active.
> > > 
> > > The latter is what the RFC already provides. 
> The IG
> > > attempts to deviate from that without apparent
> cause
> > > or purpose.
> > > 
> > > Please tell me: what bad thing do you think will
> > > happen if the RFC is followed as it stands?
> > [TOLGA]It is obvious that RFC as it stands now is
> > WRONG, regarding n+k mode.
> 
> Where is it WRONG?
> 
> > Parts of it are written
> > without considering n>1 case.
> 
> Which parts?
> 
> > Now, if one thinks that
> > always n=1 (n being used as I refer above, i.e.
> > minimum number of ACTIVE ASPs to declare AS as
> > ACTIVE-)
> > then this is easy to achieve with IG, just use
> always
> > n=1.
> 
> Even the IG defines 'n' as the mininum number of
> ASPs
> for "maximum engineered load".  So you would further
> change the definition of 'n' again?  We already
> agreed
> by concensus that 'n' was the minimum numebr of ASPs
> for "maximum engineered load".
> 
> > If one interpretes n as you describe -the value
> > to be used during mother's day-, IMO n has nothing
> to
> > do with M3UA AS state machine -so no need to
> mention
> > anything about it in M3UA documents-, something
> > totally different. 
> 
> This was the concensus reached from the last
> discusssion.
> If you don't care about such a definition of 'n'
> then
> you shouldn't need to get further involved in these
> dicussions.
> 
> > The important thing IMO is that ASPs and SGPs have
> the
> > same AS state view. And to achieve this, when
> staet
> > change to ACTIVE for AS  happens, should be
> clearly
> > defined.
> 
> It is: SGP MUST send NTFY(AS-ACTIVE) when it moves
> the
> AS to the AS-ACTIVE state.  This is provided for in
> the
> RFC.  The ASP ALWAYS knows when the SGP determines
> that
> an as is active from its view.
> 
> > RFC fails on this.
> 
> Simply wrong.  The SGP sending NTFY(AS-ACTIVE)
> ensures
> that the SGP and ASP have the same view of AS state,
> and not just for the AS-ACTIVE state.
> 
> > Now, about the bad thing,
> > which can happen if this view is not the same,
> 
> Because of NTFY(AS-ACTIVE) the view cannot differ,
> so
> no bad thing can happen based on mis-match of state.
> 
> > -as I
> > stated several times- SG might expose AS as
> available
> > to SS7 network, whereas in fact in wasn't
> available.
> 
> Can't happen.  Please try to describe an example
> message
> flow in terms of M3UA messages.
> 
> > Nodes in SS7 domain will send traffic to AS but
> can't
> > get replies.
> 
> Can't happen.  Please try to describe an example
> message
> flow in terms of M3UA messages.
> 
> > This, IMO should be avoided.
> 
> It can't happen under exisint RFC.  This is
> precisely
> why the NTFY(AS-ACTIVE) is withheld if the SG is
> going
> to wait for 'n' ASPs to activate.  So that this can
> never happen.
> 
> > Basically, I could understand if somebody
> advocates
> > the idea that n+k mode is useless (because n is
> going
> > to be always 1), but this would require striking
> out
> > everything related with n+k in both IG and RFC,
> not
> > just IG (and IMO because n+k mode includes n=1,
> there
> > is no need to put restrictions. For example, it
> migth
> > be usefull for a case, where the operator does not
> > want AS to be ACTIVE, unless two ASPs are ACTIVE,
> to
> > ensure redundancy at the startup. IMO, the value
> of n
> > is an operation issue)
> 
> The existing RFC has the ability for the SGP to wait
> for 'n' where n>1 and withhold NTFY)(AS-ACTIVE). 
> You
> will not be removing this option either.
> 
> > IMO, the only thing, which could be modified in
> the
> > proposed text is not to use the term "maximum
> > engineered load", and explain maybe more openly,
> what
> > is meant with n.
> 
> The only thing to do is scrap the proposed text. 
> The
> SGP must be permitted to activate the AS with the
> first
> ASP (and send NTFY(AS-ACTIVE) immediately) or
> activate
> the AS with the 'n'th ASP (sending NTFY(AS-ACTIVE)
> only
> after the 'n' ASP) or at some 'm' value or time
> expiration
> somewhere in between.  It is the ASPss
> responsibility to
> coordinate amongst themselves and get 'n' 0f them
> up.
> If the APS needs 'n' or nothing, it should not
> activate
> until it can be sure that n-1 other ASPs are also
> activating.
> 
> This is what is already provided for in the RFC,
> regardless
> of what one's view of 'n' is, the SGP is provided
> the option
> to do the right thing, and the requirement to notify
> the
> ASP of its decision (with NTFY(AS-ACTIVE)).
> 
> The only thing left to do is strike 3.15.
> 
> --brian
> 
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

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



From exim@www1.ietf.org  Fri Jun 20 18:15:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12560
	for <sigtran-archive@odin.ietf.org>; Fri, 20 Jun 2003 18:15:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5KMF3q26515
	for sigtran-archive@odin.ietf.org; Fri, 20 Jun 2003 18:15:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19TU9t-0006sw-Rf; Fri, 20 Jun 2003 18:15:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19TU9B-0006sA-UC
	for sigtran@optimus.ietf.org; Fri, 20 Jun 2003 18:14:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12404
	for <sigtran@ietf.org>; Fri, 20 Jun 2003 18:14:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TU99-0003uv-00
	for sigtran@ietf.org; Fri, 20 Jun 2003 18:14:15 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[Zsau20QzwyiFGOe5jwaLc5F2wqvJ7Zye])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TU98-0003us-00
	for sigtran@ietf.org; Fri, 20 Jun 2003 18:14:14 -0400
Received: from ns.pigworks.openss7.net (IDENT:Mxb0UymHrXJGF061PauIfsNooh5iVutA@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5KMEEX06121;
	Fri, 20 Jun 2003 16:14:14 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5KMEDB10948;
	Fri, 20 Jun 2003 16:14:13 -0600
Date: Fri, 20 Jun 2003 16:14:13 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030620161413.B9154@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030620143335.A9154@openss7.org> <20030620205008.98400.qmail@web12801.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030620205008.98400.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Fri, Jun 20, 2003 at 01:50:08PM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

Tolga Asveren wrote:                                                                 (Fri, 20 Jun 2003 13:50:08)
> Brian,
> 
> 1- NTFY has only advisory meaning, there is no
> "SHOULD" action, which is to be taken after NTFY, so
> your argument that ASPs can rely on NTFY is not valid

The RFC does not say that.  It says:

  An SGP or IPSP, upon reception of an ASP Active
  message for the first ASP in a Loadshare AS, MAY
  choose not to direct traffic to a newly active ASP
  until it determines that there are sufficient
  resources to handle the expected load (e.g., until
  there are "n" ASPs in state ASP-ACTIVE in the AS).
  In this case, the SGP or IPSP SHOULD withhold the
  Notify (AS-ACTIVE) until there are sufficient
  resources.

And the ASP can rely on it.  The Notify is advisory.
The ASP can ignore it if it likes.  It does not
compel the ASP to do anything.  The ASP can ignore
the notification of AS state change at its own peril.

The argument that an ASP can rely on this notify is
ensured by the SHOULD in the passage above.

> -you know it was proposed to make ASPs decide for the
> AS state change by NTFY but it was not accepted,

That was an observation in an old thread, not a
rejection.

The ASP is welcome to use whatever information it
has at its disposal, INCLUDING Notify, which it can
rely upon because of the requirement (MUST) for the
SGP to send it.

> because it was considered as a too radical change-.

What change?  It is already there in the RFC in
section 4.3.4.3.  This is also true for M2UA and
SUA.

> Nowhere it is stated in RFC nor in IG, that ASPs
> decide to accept/receive application traffic based on
> NTFY.

There is no requirement for them to do so.  There
is, however, a requirement placed on ASPs in thes
same section (4.3.4.3) that reads;

  For the n+k redundancy case, ASPs which are in the
  AS SHOULD coordinate amoung themselves the number
  of active ASPs in the AS, and should start sending
  traffic only after 'n' ASPs are active.

It does not require the ASP to use Notify, but it
does not keep the ASP from using whatever means it
has at its disposal for coordinating that 'n' ASPs
become active.
> 
> 2- RFC tells that ASPs SHOULD arrange number of ACTIVE
> ASPs among themselves, but allows SG to start routing
> traffic even with less than n ACTIVE ASP.

As it should.

> Just look to
> the definition of INACTIVE AS in RFC, an AS whith no
> application traffic flowing to/from it. So, they might
> have inconsistent views of AS state.

No, because the ASP will coordinate that 'n' are
active.

> 
> 3- If n is to be seen as the mother day's value, IMO
> it really has nothing to do with M3UA, because it
> won't change AS state at all (or maybe you can give an
> example about its relation to M3UA)

I think you misread the first quote from 4.3.4.3.
The ASP has little idea what load it will be offered
when it activates.  This is why it should coordinate
that 'n' are active.  It might be Mother's Day, it
might not.  The SG, on the other hand, has a better
idea of what load will be offered and will activate
when the number of ASPs is sufficient to handle the
load.  That is not necessariliy 'n'.  'n' is just an
example in the quote: "(e.g., until thare are "n"
ASPs in state ASP-ACTIVE in the AS)".  The SG
normally activates the AS with the first active ASP
(as indicated and completely consistent with the
state diagram and descriptions in the RFC), but it
MAY wait until 'n' are active.  In any case it sends
Notify to indicate that th AS is active as it MUST
(see the MUSTs in section 4.3.4.5).

It is not a question that the SGP MUST send Notify.
It MAY wait until sufficient ASPs are active to
handle the load (and not necessarily "n", but it may
be "n") and it SHOULD withhold the Notify until
sufficient ASPs are active to handle the load.

This provide the SG designer with the freedom to
meet dynamic load and redundancy needs at the same
time as ensuring interoperability through the Notify
and ASP-Active procedures.

You seem to want to restrict this further, taking
the necessary flexibility away from the SG designer
with no resulting benefit.  I cannot agree with the
proposal.  The RFC is both sufficient and necessary
in this regard.

Strike 3.15.

--brian

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

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



From exim@www1.ietf.org  Tue Jun 24 12:03:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21632
	for <sigtran-archive@odin.ietf.org>; Tue, 24 Jun 2003 12:03:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5OG04J31956
	for sigtran-archive@odin.ietf.org; Tue, 24 Jun 2003 12:00:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19UqDB-0008JA-Jy; Tue, 24 Jun 2003 12:00:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19UqC6-0008IO-13
	for sigtran@optimus.ietf.org; Tue, 24 Jun 2003 11:59:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21479
	for <sigtran@ietf.org>; Tue, 24 Jun 2003 11:58:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UqC4-0003sh-00
	for sigtran@ietf.org; Tue, 24 Jun 2003 11:58:52 -0400
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47] helo=penguin.al.sw.ericsson.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19UqBt-0003rR-00
	for sigtran@ietf.org; Tue, 24 Jun 2003 11:58:41 -0400
Received: from esealnt613.al.sw.ericsson.se (alteon-nat8.sw.ericsson.se [153.88.254.125])
	by penguin.al.sw.ericsson.se (8.12.9/8.12.9/WIREfire-1.6b) with ESMTP id h5OFtKw2023261;
	Tue, 24 Jun 2003 17:55:30 +0200 (MEST)
Received: from ESEALNT744.al.sw.ericsson.se ([153.88.251.4]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id MVP98H99; Tue, 24 Jun 2003 17:55:07 +0200
Received: by ESEALNT744.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NRQH0SQS>; Tue, 24 Jun 2003 17:55:21 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C90@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>,
        Tolga Asveren
	 <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] Re: M3UA Notify message
Date: Tue, 24 Jun 2003 17:53:40 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hi Brian,

The text you show below together with section 1.4.4.1 does not say that =
you may send NTFY before "n" ASPs are ACTIVE per section 1.4.4.1. Then =
you can conclude that you MAY wait till n+m ASPs till you send the =
NTFY. M

>   An SGP or IPSP, upon reception of an ASP Active
>   message for the first ASP in a Loadshare AS, MAY
>   choose not to direct traffic to a newly active ASP
>   until it determines that there are sufficient
>   resources to handle the expected load (e.g., until
>   there are "n" ASPs in state ASP-ACTIVE in the AS).
>   In this case, the SGP or IPSP SHOULD withhold the
>   Notify (AS-ACTIVE) until there are sufficient
>   resources.

It seems that your statements are not aligned with section 1.4.4.1, 3rd =
paragraph... This section clearly says that n ASPs are needed.=20

But also section 4.3.2 does not say a word about withholding the =
NTFY(AS-ACTIVE) as it is explained in other sections. What means that =
the text needs some fixings...

I would recommend to fixed the text to clearly specify the behavior we =
want.


Cheers // Javier.

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: s=E1bado, 21 de junio de 2003 0:14
> To: Tolga Asveren
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] Re: M3UA Notify message
>=20
>=20
> Tolga,
>=20
> Tolga Asveren wrote:                                         =20
>                        (Fri, 20 Jun 2003 13:50:08)
> > Brian,
> >=20
> > 1- NTFY has only advisory meaning, there is no
> > "SHOULD" action, which is to be taken after NTFY, so
> > your argument that ASPs can rely on NTFY is not valid
>=20
> The RFC does not say that.  It says:
>=20
>   An SGP or IPSP, upon reception of an ASP Active
>   message for the first ASP in a Loadshare AS, MAY
>   choose not to direct traffic to a newly active ASP
>   until it determines that there are sufficient
>   resources to handle the expected load (e.g., until
>   there are "n" ASPs in state ASP-ACTIVE in the AS).
>   In this case, the SGP or IPSP SHOULD withhold the
>   Notify (AS-ACTIVE) until there are sufficient
>   resources.
>=20
> And the ASP can rely on it.  The Notify is advisory.
> The ASP can ignore it if it likes.  It does not
> compel the ASP to do anything.  The ASP can ignore
> the notification of AS state change at its own peril.
>=20
> The argument that an ASP can rely on this notify is
> ensured by the SHOULD in the passage above.
>=20
> > -you know it was proposed to make ASPs decide for the
> > AS state change by NTFY but it was not accepted,
>=20
> That was an observation in an old thread, not a
> rejection.
>=20
> The ASP is welcome to use whatever information it
> has at its disposal, INCLUDING Notify, which it can
> rely upon because of the requirement (MUST) for the
> SGP to send it.
>=20
> > because it was considered as a too radical change-.
>=20
> What change?  It is already there in the RFC in
> section 4.3.4.3.  This is also true for M2UA and
> SUA.
>=20
> > Nowhere it is stated in RFC nor in IG, that ASPs
> > decide to accept/receive application traffic based on
> > NTFY.
>=20
> There is no requirement for them to do so.  There
> is, however, a requirement placed on ASPs in thes
> same section (4.3.4.3) that reads;
>=20
>   For the n+k redundancy case, ASPs which are in the
>   AS SHOULD coordinate amoung themselves the number
>   of active ASPs in the AS, and should start sending
>   traffic only after 'n' ASPs are active.
>=20
> It does not require the ASP to use Notify, but it
> does not keep the ASP from using whatever means it
> has at its disposal for coordinating that 'n' ASPs
> become active.
> >=20
> > 2- RFC tells that ASPs SHOULD arrange number of ACTIVE
> > ASPs among themselves, but allows SG to start routing
> > traffic even with less than n ACTIVE ASP.
>=20
> As it should.
>=20
> > Just look to
> > the definition of INACTIVE AS in RFC, an AS whith no
> > application traffic flowing to/from it. So, they might
> > have inconsistent views of AS state.
>=20
> No, because the ASP will coordinate that 'n' are
> active.
>=20
> >=20
> > 3- If n is to be seen as the mother day's value, IMO
> > it really has nothing to do with M3UA, because it
> > won't change AS state at all (or maybe you can give an
> > example about its relation to M3UA)
>=20
> I think you misread the first quote from 4.3.4.3.
> The ASP has little idea what load it will be offered
> when it activates.  This is why it should coordinate
> that 'n' are active.  It might be Mother's Day, it
> might not.  The SG, on the other hand, has a better
> idea of what load will be offered and will activate
> when the number of ASPs is sufficient to handle the
> load.  That is not necessariliy 'n'.  'n' is just an
> example in the quote: "(e.g., until thare are "n"
> ASPs in state ASP-ACTIVE in the AS)".  The SG
> normally activates the AS with the first active ASP
> (as indicated and completely consistent with the
> state diagram and descriptions in the RFC), but it
> MAY wait until 'n' are active.  In any case it sends
> Notify to indicate that th AS is active as it MUST
> (see the MUSTs in section 4.3.4.5).
>=20
> It is not a question that the SGP MUST send Notify.
> It MAY wait until sufficient ASPs are active to
> handle the load (and not necessarily "n", but it may
> be "n") and it SHOULD withhold the Notify until
> sufficient ASPs are active to handle the load.
>=20
> This provide the SG designer with the freedom to
> meet dynamic load and redundancy needs at the same
> time as ensuring interoperability through the Notify
> and ASP-Active procedures.
>=20
> You seem to want to restrict this further, taking
> the necessary flexibility away from the SG designer
> with no resulting benefit.  I cannot agree with the
> proposal.  The RFC is both sufficient and necessary
> in this regard.
>=20
> Strike 3.15.
>=20
> --brian
>=20
> --=20
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
>=20

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



From exim@www1.ietf.org  Tue Jun 24 12:15:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22186
	for <sigtran-archive@odin.ietf.org>; Tue, 24 Jun 2003 12:15:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5OGF2n05607
	for sigtran-archive@odin.ietf.org; Tue, 24 Jun 2003 12:15:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19UqRi-0001SK-0R; Tue, 24 Jun 2003 12:15:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19UqRE-0001QE-JN
	for sigtran@optimus.ietf.org; Tue, 24 Jun 2003 12:14:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22129
	for <sigtran@ietf.org>; Tue, 24 Jun 2003 12:14:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UqRD-00040z-00
	for sigtran@ietf.org; Tue, 24 Jun 2003 12:14:31 -0400
Received: from web12802.mail.yahoo.com ([216.136.174.37])
	by ietf-mx with smtp (Exim 4.12)
	id 19UqR2-00040Y-00
	for sigtran@ietf.org; Tue, 24 Jun 2003 12:14:20 -0400
Message-ID: <20030624161339.28083.qmail@web12802.mail.yahoo.com>
Received: from [208.255.120.2] by web12802.mail.yahoo.com via HTTP; Tue, 24 Jun 2003 09:13:39 PDT
Date: Tue, 24 Jun 2003 09:13:39 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: RE: [Sigtran] Re: M3UA Notify message
To: sigtran@ietf.org
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C90@eestqnt105.es.eu.ericsson.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id MAA22130
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hi Javier,

My opinion is, when AS state change happens should be
clearly defined and M3UA documents are not the place
to discuss traffic engineering issues other than that.
So, IMO, the text you proposed is fine -maybe just
renaming max engineered load, or clearly explaining
what is meant with that-.=20

      Tolga
--- "Javier Pastor-Balbas (ECE)"
<javier.pastor-balbas@ece.ericsson.se> wrote:
> Hi Brian,
>=20
> The text you show below together with section
> 1.4.4.1 does not say that you may send NTFY before
> "n" ASPs are ACTIVE per section 1.4.4.1. Then you
> can conclude that you MAY wait till n+m ASPs till
> you send the NTFY. M
>=20
> >   An SGP or IPSP, upon reception of an ASP Active
> >   message for the first ASP in a Loadshare AS, MAY
> >   choose not to direct traffic to a newly active
> ASP
> >   until it determines that there are sufficient
> >   resources to handle the expected load (e.g.,
> until
> >   there are "n" ASPs in state ASP-ACTIVE in the
> AS).
> >   In this case, the SGP or IPSP SHOULD withhold
> the
> >   Notify (AS-ACTIVE) until there are sufficient
> >   resources.
>=20
> It seems that your statements are not aligned with
> section 1.4.4.1, 3rd paragraph... This section
> clearly says that n ASPs are needed.=20
>=20
> But also section 4.3.2 does not say a word about
> withholding the NTFY(AS-ACTIVE) as it is explained
> in other sections. What means that the text needs
> some fixings...
>=20
> I would recommend to fixed the text to clearly
> specify the behavior we want.
>=20
>=20
> Cheers // Javier.
>=20
> > -----Original Message-----
> > From: Brian F. G. Bidulock
> [mailto:bidulock@openss7.org]
> > Sent: s=E1bado, 21 de junio de 2003 0:14
> > To: Tolga Asveren
> > Cc: sigtran@ietf.org
> > Subject: Re: [Sigtran] Re: M3UA Notify message
> >=20
> >=20
> > Tolga,
> >=20
> > Tolga Asveren wrote:                             =20
>           =20
> >                        (Fri, 20 Jun 2003 13:50:08)
> > > Brian,
> > >=20
> > > 1- NTFY has only advisory meaning, there is no
> > > "SHOULD" action, which is to be taken after
> NTFY, so
> > > your argument that ASPs can rely on NTFY is not
> valid
> >=20
> > The RFC does not say that.  It says:
> >=20
> >   An SGP or IPSP, upon reception of an ASP Active
> >   message for the first ASP in a Loadshare AS, MAY
> >   choose not to direct traffic to a newly active
> ASP
> >   until it determines that there are sufficient
> >   resources to handle the expected load (e.g.,
> until
> >   there are "n" ASPs in state ASP-ACTIVE in the
> AS).
> >   In this case, the SGP or IPSP SHOULD withhold
> the
> >   Notify (AS-ACTIVE) until there are sufficient
> >   resources.
> >=20
> > And the ASP can rely on it.  The Notify is
> advisory.
> > The ASP can ignore it if it likes.  It does not
> > compel the ASP to do anything.  The ASP can ignore
> > the notification of AS state change at its own
> peril.
> >=20
> > The argument that an ASP can rely on this notify
> is
> > ensured by the SHOULD in the passage above.
> >=20
> > > -you know it was proposed to make ASPs decide
> for the
> > > AS state change by NTFY but it was not accepted,
> >=20
> > That was an observation in an old thread, not a
> > rejection.
> >=20
> > The ASP is welcome to use whatever information it
> > has at its disposal, INCLUDING Notify, which it
> can
> > rely upon because of the requirement (MUST) for
> the
> > SGP to send it.
> >=20
> > > because it was considered as a too radical
> change-.
> >=20
> > What change?  It is already there in the RFC in
> > section 4.3.4.3.  This is also true for M2UA and
> > SUA.
> >=20
> > > Nowhere it is stated in RFC nor in IG, that ASPs
> > > decide to accept/receive application traffic
> based on
> > > NTFY.
> >=20
> > There is no requirement for them to do so.  There
> > is, however, a requirement placed on ASPs in thes
> > same section (4.3.4.3) that reads;
> >=20
> >   For the n+k redundancy case, ASPs which are in
> the
> >   AS SHOULD coordinate amoung themselves the
> number
> >   of active ASPs in the AS, and should start
> sending
> >   traffic only after 'n' ASPs are active.
> >=20
> > It does not require the ASP to use Notify, but it
> > does not keep the ASP from using whatever means it
> > has at its disposal for coordinating that 'n' ASPs
> > become active.
> > >=20
> > > 2- RFC tells that ASPs SHOULD arrange number of
> ACTIVE
> > > ASPs among themselves, but allows SG to start
> routing
> > > traffic even with less than n ACTIVE ASP.
> >=20
> > As it should.
> >=20
> > > Just look to
> > > the definition of INACTIVE AS in RFC, an AS
> whith no
> > > application traffic flowing to/from it. So, they
> might
> > > have inconsistent views of AS state.
> >=20
> > No, because the ASP will coordinate that 'n' are
> > active.
> >=20
> > >=20
> > > 3- If n is to be seen as the mother day's value,
> IMO
> > > it really has nothing to do with M3UA, because
> it
> > > won't change AS state at all (or maybe you can
> give an
> > > example about its relation to M3UA)
> >=20
> > I think you misread the first quote from 4.3.4.3.
> > The ASP has little idea what load it will be
> offered
> > when it activates.  This is why it should
> coordinate
> > that 'n' are active.  It might be Mother's Day, it
> > might not.  The SG, on the other hand, has a
> better
> > idea of what load will be offered and will
> activate
> > when the number of ASPs is sufficient to handle
> the
> > load.  That is not necessariliy 'n'.  'n' is just
> an
> > example in the quote: "(e.g., until thare are "n"
> > ASPs in state ASP-ACTIVE in the AS)".  The SG
> > normally activates the AS with the first active
> ASP
> > (as indicated and completely consistent with the
> > state diagram and descriptions in the RFC), but it
> > MAY wait until 'n' are active.  In any case it
> sends
> > Notify to indicate that th AS is active as it MUST
> > (see the MUSTs in section 4.3.4.5).
> >=20
> > It is not a question that the SGP MUST send
> Notify.
> > It MAY wait until sufficient ASPs are active to
> > handle the load (and not necessarily "n", but it
> may
> > be "n") and it SHOULD withhold the Notify until
> > sufficient ASPs are active to handle the load.
> >=20
> > This provide the SG designer with the freedom to
> > meet dynamic load and redundancy needs at the same
> > time as ensuring interoperability through the
> Notify
> > and ASP-Active procedures.
> >=20
> > You seem to want to restrict this further, taking
> > the necessary flexibility away from the SG
> designer
> > with no resulting benefit.  I cannot agree with
> the
> > proposal.  The RFC is both sufficient and
> necessary


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

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



From exim@www1.ietf.org  Tue Jun 24 13:27:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25703
	for <sigtran-archive@odin.ietf.org>; Tue, 24 Jun 2003 13:27:28 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5OHR2G18028
	for sigtran-archive@odin.ietf.org; Tue, 24 Jun 2003 13:27:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19UrZN-0004gW-6l; Tue, 24 Jun 2003 13:27:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19UrZB-0004gH-8D
	for sigtran@optimus.ietf.org; Tue, 24 Jun 2003 13:26:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25683
	for <sigtran@ietf.org>; Tue, 24 Jun 2003 13:26:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UrYu-0004cB-00
	for sigtran@ietf.org; Tue, 24 Jun 2003 13:26:32 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[jubQ7UZtiqrpVXwaIShlLsEu/pGRhHiY])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UrYe-0004c3-00
	for sigtran@ietf.org; Tue, 24 Jun 2003 13:26:16 -0400
Received: from ns.pigworks.openss7.net (IDENT:6GHBhRxlEKy2SP6qHokMtbhv+xlimKIb@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5OHPfX22600;
	Tue, 24 Jun 2003 11:25:41 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5OHPfM24495;
	Tue, 24 Jun 2003 11:25:41 -0600
Date: Tue, 24 Jun 2003 11:25:41 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
Cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030624112541.A24293@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>,
	Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C90@eestqnt105.es.eu.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C90@eestqnt105.es.eu.ericsson.se>; from javier.pastor-balbas@ece.ericsson.se on Tue, Jun 24, 2003 at 05:53:40PM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id h5OHPfX22600
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Javier,

Javier Pastor-Balbas (ECE) wrote:                                        =
           (Tue, 24 Jun 2003 17:53:40)
> Hi Brian,
>=20
> The text you show below together with section 1.4.4.1 does not say that=
 you
> may send NTFY before "n" ASPs are ACTIVE per section 1.4.4.1. Then you =
can
> conclude that you MAY wait till n+m ASPs till you send the NTFY. M

Read: (Section 4.3.4.5:)

  A Notify message reflecting a change in the AS state MUST be
  sent to all ASPs in the AS, except thos in the ASP-DOWN state,
  with apporpriate Status Information and any ASP Identifier of
  the failed ASP.  ...  The Notify message must be sent whether
  the AS state change was a result of an ASP failure or
  reception of an ASP State management (ASPSM) / ASP Traffic
  Management (ASPTM) message.  In the second case, the Notify
  message MUST be sent after any related acknowledgement message
  (e.g., ASP Up Ack, ASP Down Ack, ASP Active Ack, or ASP
  Inactive Ack).

Read: (Section 4.3.2:)

  AS-ACTIVE: The Application Server is available and application
  traffic is active.  This state implies that at least one ASP
  is in the ASP-ACTIVE state.

Read: (Section 4.3.4.3:)

  An SGP or IPSP, upon reception of an ASP Active message for
  the first ASP in a Loadshare AS, MAY choose not to direct
  traffic to a newly active ASP until it determines that there
  are sufficient resources to handle the expected load (e.g.,
  until there are "n" ASPs in state ASP-ACTIVE in the AS).  In
  this case, the SGP or IPSP SHOULD withhold the Notify
  (AS-ACTIVE) until there are sufficient resources.
 =20
The first passage says that I must send Notify(AS Actve), the
second passages says that I can send it when the first ASP is
Active for the AS, the third passage says that I may withhold it
until sufficient resources are active (regardless of 'n').

> >   An SGP or IPSP, upon reception of an ASP Active
> >   message for the first ASP in a Loadshare AS, MAY
> >   choose not to direct traffic to a newly active ASP
> >   until it determines that there are sufficient
> >   resources to handle the expected load (e.g., until
> >   there are "n" ASPs in state ASP-ACTIVE in the AS).
> >   In this case, the SGP or IPSP SHOULD withhold the
> >   Notify (AS-ACTIVE) until there are sufficient
> >   resources.
>=20
> It seems that your statements are not aligned with section 1.4.4.1, 3rd
> paragraph... This section clearly says that n ASPs are needed.=20

1.4.4.1 says nothing about when to send messages.

>=20
> But also section 4.3.2 does not say a word about withholding the
> NTFY(AS-ACTIVE) as it is explained in other sections. What means that t=
he
> text needs some fixings...

No.  It is stated in section 4.3.4.3, the ASP Active procedures.
There are a lot of things stated in the 4.3.4.3 procedures that
are not stated in section 4.3.2, because 4.3.2 is an OVERVIEW.

>=20
> I would recommend to fixed the text to clearly specify the
> behavior we want.

IMO nothing needs changing.  But, if you have another text
proposal, please don't hesitate to suggest it.


--brian

>=20
>=20
> Cheers // Javier.
>=20
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: s=E1bado, 21 de junio de 2003 0:14
> > To: Tolga Asveren
> > Cc: sigtran@ietf.org
> > Subject: Re: [Sigtran] Re: M3UA Notify message
> >=20
> >=20
> > Tolga,
> >=20
> > Tolga Asveren wrote:                                         =20
> >                        (Fri, 20 Jun 2003 13:50:08)
> > > Brian,
> > >=20
> > > 1- NTFY has only advisory meaning, there is no
> > > "SHOULD" action, which is to be taken after NTFY, so
> > > your argument that ASPs can rely on NTFY is not valid
> >=20
> > The RFC does not say that.  It says:
> >=20
> >   An SGP or IPSP, upon reception of an ASP Active
> >   message for the first ASP in a Loadshare AS, MAY
> >   choose not to direct traffic to a newly active ASP
> >   until it determines that there are sufficient
> >   resources to handle the expected load (e.g., until
> >   there are "n" ASPs in state ASP-ACTIVE in the AS).
> >   In this case, the SGP or IPSP SHOULD withhold the
> >   Notify (AS-ACTIVE) until there are sufficient
> >   resources.
> >=20
> > And the ASP can rely on it.  The Notify is advisory.
> > The ASP can ignore it if it likes.  It does not
> > compel the ASP to do anything.  The ASP can ignore
> > the notification of AS state change at its own peril.
> >=20
> > The argument that an ASP can rely on this notify is
> > ensured by the SHOULD in the passage above.
> >=20
> > > -you know it was proposed to make ASPs decide for the
> > > AS state change by NTFY but it was not accepted,
> >=20
> > That was an observation in an old thread, not a
> > rejection.
> >=20
> > The ASP is welcome to use whatever information it
> > has at its disposal, INCLUDING Notify, which it can
> > rely upon because of the requirement (MUST) for the
> > SGP to send it.
> >=20
> > > because it was considered as a too radical change-.
> >=20
> > What change?  It is already there in the RFC in
> > section 4.3.4.3.  This is also true for M2UA and
> > SUA.
> >=20
> > > Nowhere it is stated in RFC nor in IG, that ASPs
> > > decide to accept/receive application traffic based on
> > > NTFY.
> >=20
> > There is no requirement for them to do so.  There
> > is, however, a requirement placed on ASPs in thes
> > same section (4.3.4.3) that reads;
> >=20
> >   For the n+k redundancy case, ASPs which are in the
> >   AS SHOULD coordinate amoung themselves the number
> >   of active ASPs in the AS, and should start sending
> >   traffic only after 'n' ASPs are active.
> >=20
> > It does not require the ASP to use Notify, but it
> > does not keep the ASP from using whatever means it
> > has at its disposal for coordinating that 'n' ASPs
> > become active.
> > >=20
> > > 2- RFC tells that ASPs SHOULD arrange number of ACTIVE
> > > ASPs among themselves, but allows SG to start routing
> > > traffic even with less than n ACTIVE ASP.
> >=20
> > As it should.
> >=20
> > > Just look to
> > > the definition of INACTIVE AS in RFC, an AS whith no
> > > application traffic flowing to/from it. So, they might
> > > have inconsistent views of AS state.
> >=20
> > No, because the ASP will coordinate that 'n' are
> > active.
> >=20
> > >=20
> > > 3- If n is to be seen as the mother day's value, IMO
> > > it really has nothing to do with M3UA, because it
> > > won't change AS state at all (or maybe you can give an
> > > example about its relation to M3UA)
> >=20
> > I think you misread the first quote from 4.3.4.3.
> > The ASP has little idea what load it will be offered
> > when it activates.  This is why it should coordinate
> > that 'n' are active.  It might be Mother's Day, it
> > might not.  The SG, on the other hand, has a better
> > idea of what load will be offered and will activate
> > when the number of ASPs is sufficient to handle the
> > load.  That is not necessariliy 'n'.  'n' is just an
> > example in the quote: "(e.g., until thare are "n"
> > ASPs in state ASP-ACTIVE in the AS)".  The SG
> > normally activates the AS with the first active ASP
> > (as indicated and completely consistent with the
> > state diagram and descriptions in the RFC), but it
> > MAY wait until 'n' are active.  In any case it sends
> > Notify to indicate that th AS is active as it MUST
> > (see the MUSTs in section 4.3.4.5).
> >=20
> > It is not a question that the SGP MUST send Notify.
> > It MAY wait until sufficient ASPs are active to
> > handle the load (and not necessarily "n", but it may
> > be "n") and it SHOULD withhold the Notify until
> > sufficient ASPs are active to handle the load.
> >=20
> > This provide the SG designer with the freedom to
> > meet dynamic load and redundancy needs at the same
> > time as ensuring interoperability through the Notify
> > and ASP-Active procedures.
> >=20
> > You seem to want to restrict this further, taking
> > the necessary flexibility away from the SG designer
> > with no resulting benefit.  I cannot agree with the
> > proposal.  The RFC is both sufficient and necessary
> > in this regard.
> >=20
> > Strike 3.15.
> >=20
> > --brian
> >=20
> > --=20
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> >=20
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> >=20

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

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



From exim@www1.ietf.org  Tue Jun 24 13:28:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25773
	for <sigtran-archive@odin.ietf.org>; Tue, 24 Jun 2003 13:28:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5OHS1R18362
	for sigtran-archive@odin.ietf.org; Tue, 24 Jun 2003 13:28:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19UraL-0004m0-2a; Tue, 24 Jun 2003 13:28:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Ura1-0004kJ-JF
	for sigtran@optimus.ietf.org; Tue, 24 Jun 2003 13:27:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25719
	for <sigtran@ietf.org>; Tue, 24 Jun 2003 13:27:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UrZz-0004cW-00
	for sigtran@ietf.org; Tue, 24 Jun 2003 13:27:39 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[zdSKgeFBW5c/NTwQzXayOU0Cf39MRr14])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UrZj-0004cN-00
	for sigtran@ietf.org; Tue, 24 Jun 2003 13:27:23 -0400
Received: from ns.pigworks.openss7.net (IDENT:CAF6Q98frSw3g54TzsWTetCp8EO0MpSe@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5OHRCX22627;
	Tue, 24 Jun 2003 11:27:13 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5OHRCm24558;
	Tue, 24 Jun 2003 11:27:12 -0600
Date: Tue, 24 Jun 2003 11:27:12 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030624112712.B24293@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C90@eestqnt105.es.eu.ericsson.se> <20030624161339.28083.qmail@web12802.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030624161339.28083.qmail@web12802.mail.yahoo.com>; from tolga_asveren@yahoo.com on Tue, Jun 24, 2003 at 09:13:39AM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id h5OHRCX22627
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Tolga,

You have no response to my last message of June 20th?

--brian

Tolga Asveren wrote:                                                     =
            (Tue, 24 Jun 2003 09:13:39)
> Hi Javier,
>=20
> My opinion is, when AS state change happens should be
> clearly defined and M3UA documents are not the place
> to discuss traffic engineering issues other than that.
> So, IMO, the text you proposed is fine -maybe just
> renaming max engineered load, or clearly explaining
> what is meant with that-.=20
>=20
>       Tolga
> --- "Javier Pastor-Balbas (ECE)"
> <javier.pastor-balbas@ece.ericsson.se> wrote:
> > Hi Brian,
> >=20
> > The text you show below together with section
> > 1.4.4.1 does not say that you may send NTFY before
> > "n" ASPs are ACTIVE per section 1.4.4.1. Then you
> > can conclude that you MAY wait till n+m ASPs till
> > you send the NTFY. M
> >=20
> > >   An SGP or IPSP, upon reception of an ASP Active
> > >   message for the first ASP in a Loadshare AS, MAY
> > >   choose not to direct traffic to a newly active
> > ASP
> > >   until it determines that there are sufficient
> > >   resources to handle the expected load (e.g.,
> > until
> > >   there are "n" ASPs in state ASP-ACTIVE in the
> > AS).
> > >   In this case, the SGP or IPSP SHOULD withhold
> > the
> > >   Notify (AS-ACTIVE) until there are sufficient
> > >   resources.
> >=20
> > It seems that your statements are not aligned with
> > section 1.4.4.1, 3rd paragraph... This section
> > clearly says that n ASPs are needed.=20
> >=20
> > But also section 4.3.2 does not say a word about
> > withholding the NTFY(AS-ACTIVE) as it is explained
> > in other sections. What means that the text needs
> > some fixings...
> >=20
> > I would recommend to fixed the text to clearly
> > specify the behavior we want.
> >=20
> >=20
> > Cheers // Javier.
> >=20
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock
> > [mailto:bidulock@openss7.org]
> > > Sent: s=E1bado, 21 de junio de 2003 0:14
> > > To: Tolga Asveren
> > > Cc: sigtran@ietf.org
> > > Subject: Re: [Sigtran] Re: M3UA Notify message
> > >=20
> > >=20
> > > Tolga,
> > >=20
> > > Tolga Asveren wrote:                             =20
> >           =20
> > >                        (Fri, 20 Jun 2003 13:50:08)
> > > > Brian,
> > > >=20
> > > > 1- NTFY has only advisory meaning, there is no
> > > > "SHOULD" action, which is to be taken after
> > NTFY, so
> > > > your argument that ASPs can rely on NTFY is not
> > valid
> > >=20
> > > The RFC does not say that.  It says:
> > >=20
> > >   An SGP or IPSP, upon reception of an ASP Active
> > >   message for the first ASP in a Loadshare AS, MAY
> > >   choose not to direct traffic to a newly active
> > ASP
> > >   until it determines that there are sufficient
> > >   resources to handle the expected load (e.g.,
> > until
> > >   there are "n" ASPs in state ASP-ACTIVE in the
> > AS).
> > >   In this case, the SGP or IPSP SHOULD withhold
> > the
> > >   Notify (AS-ACTIVE) until there are sufficient
> > >   resources.
> > >=20
> > > And the ASP can rely on it.  The Notify is
> > advisory.
> > > The ASP can ignore it if it likes.  It does not
> > > compel the ASP to do anything.  The ASP can ignore
> > > the notification of AS state change at its own
> > peril.
> > >=20
> > > The argument that an ASP can rely on this notify
> > is
> > > ensured by the SHOULD in the passage above.
> > >=20
> > > > -you know it was proposed to make ASPs decide
> > for the
> > > > AS state change by NTFY but it was not accepted,
> > >=20
> > > That was an observation in an old thread, not a
> > > rejection.
> > >=20
> > > The ASP is welcome to use whatever information it
> > > has at its disposal, INCLUDING Notify, which it
> > can
> > > rely upon because of the requirement (MUST) for
> > the
> > > SGP to send it.
> > >=20
> > > > because it was considered as a too radical
> > change-.
> > >=20
> > > What change?  It is already there in the RFC in
> > > section 4.3.4.3.  This is also true for M2UA and
> > > SUA.
> > >=20
> > > > Nowhere it is stated in RFC nor in IG, that ASPs
> > > > decide to accept/receive application traffic
> > based on
> > > > NTFY.
> > >=20
> > > There is no requirement for them to do so.  There
> > > is, however, a requirement placed on ASPs in thes
> > > same section (4.3.4.3) that reads;
> > >=20
> > >   For the n+k redundancy case, ASPs which are in
> > the
> > >   AS SHOULD coordinate amoung themselves the
> > number
> > >   of active ASPs in the AS, and should start
> > sending
> > >   traffic only after 'n' ASPs are active.
> > >=20
> > > It does not require the ASP to use Notify, but it
> > > does not keep the ASP from using whatever means it
> > > has at its disposal for coordinating that 'n' ASPs
> > > become active.
> > > >=20
> > > > 2- RFC tells that ASPs SHOULD arrange number of
> > ACTIVE
> > > > ASPs among themselves, but allows SG to start
> > routing
> > > > traffic even with less than n ACTIVE ASP.
> > >=20
> > > As it should.
> > >=20
> > > > Just look to
> > > > the definition of INACTIVE AS in RFC, an AS
> > whith no
> > > > application traffic flowing to/from it. So, they
> > might
> > > > have inconsistent views of AS state.
> > >=20
> > > No, because the ASP will coordinate that 'n' are
> > > active.
> > >=20
> > > >=20
> > > > 3- If n is to be seen as the mother day's value,
> > IMO
> > > > it really has nothing to do with M3UA, because
> > it
> > > > won't change AS state at all (or maybe you can
> > give an
> > > > example about its relation to M3UA)
> > >=20
> > > I think you misread the first quote from 4.3.4.3.
> > > The ASP has little idea what load it will be
> > offered
> > > when it activates.  This is why it should
> > coordinate
> > > that 'n' are active.  It might be Mother's Day, it
> > > might not.  The SG, on the other hand, has a
> > better
> > > idea of what load will be offered and will
> > activate
> > > when the number of ASPs is sufficient to handle
> > the
> > > load.  That is not necessariliy 'n'.  'n' is just
> > an
> > > example in the quote: "(e.g., until thare are "n"
> > > ASPs in state ASP-ACTIVE in the AS)".  The SG
> > > normally activates the AS with the first active
> > ASP
> > > (as indicated and completely consistent with the
> > > state diagram and descriptions in the RFC), but it
> > > MAY wait until 'n' are active.  In any case it
> > sends
> > > Notify to indicate that th AS is active as it MUST
> > > (see the MUSTs in section 4.3.4.5).
> > >=20
> > > It is not a question that the SGP MUST send
> > Notify.
> > > It MAY wait until sufficient ASPs are active to
> > > handle the load (and not necessarily "n", but it
> > may
> > > be "n") and it SHOULD withhold the Notify until
> > > sufficient ASPs are active to handle the load.
> > >=20
> > > This provide the SG designer with the freedom to
> > > meet dynamic load and redundancy needs at the same
> > > time as ensuring interoperability through the
> > Notify
> > > and ASP-Active procedures.
> > >=20
> > > You seem to want to restrict this further, taking
> > > the necessary flexibility away from the SG
> > designer
> > > with no resulting benefit.  I cannot agree with
> > the
> > > proposal.  The RFC is both sufficient and
> > necessary
>=20
>=20
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com
>=20
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Tue Jun 24 14:01:34 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27938
	for <sigtran-archive@odin.ietf.org>; Tue, 24 Jun 2003 14:01:33 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5OI15824941
	for sigtran-archive@odin.ietf.org; Tue, 24 Jun 2003 14:01:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Us6I-0006Tb-2Q; Tue, 24 Jun 2003 14:01:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Us5o-0006QD-LY
	for sigtran@optimus.ietf.org; Tue, 24 Jun 2003 14:00:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27819
	for <sigtran@ietf.org>; Tue, 24 Jun 2003 14:00:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Us5m-00059B-00
	for sigtran@ietf.org; Tue, 24 Jun 2003 14:00:30 -0400
Received: from web12808.mail.yahoo.com ([216.136.174.43])
	by ietf-mx with smtp (Exim 4.12)
	id 19Us5a-00058p-00
	for sigtran@ietf.org; Tue, 24 Jun 2003 14:00:19 -0400
Message-ID: <20030624175953.73705.qmail@web12808.mail.yahoo.com>
Received: from [208.255.120.2] by web12808.mail.yahoo.com via HTTP; Tue, 24 Jun 2003 10:59:53 PDT
Date: Tue, 24 Jun 2003 10:59:53 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] Re: M3UA Notify message
To: sigtran@ietf.org
In-Reply-To: <20030620161413.B9154@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,

Although I do not believe that it will help us to
reach a consensus , still I will try to summarize my
opinions about this topic -otherwise I think we just
have different opinions/interpretations about text and
in the last messages I am just repeating the same
things again and again and wasting bandwith-

1- My interpretation of "ASPs coordinating n ACTIVE
ASPs among themselves" is not that they rely on NTFY,
but they do this via some communication inside ASP
cluster. And even if one could argue that NTFY might
be used for this, unless it is mandated in the
document, it has little value IMO (in fact this is the
key point, you assume that NTFY is going to be used
for this purpose). I can have a RFC compliant ASP,
which does not coordinate n based on NTFY. So, based
on that, I think the only way to synchronize AS staet
changes on ASP and SGPs is a)either using NTFY -this
is not mandated in RFC- b)or to rely on a
preconfigured number n . Relying on n requires, that
both sides know this number and activate AS only after
n ASPs are ACTIVE.

2- In my opinion it questionable, whether SG or ASPs
have a better view about current load/load to be
offered on ASPs -especially considering that ASPs
might serve multiple AS and can be connected to
multiple SG-. When the AS is not ACTIVE, SG also won't
receive traffic for it, so it seems to me that it
can't decide based on traffic dynamics to activate an
AS or not. Furthermore, as I said above, SG is even
not aware of the current load on ASPs. Yes, n is
static, but IMO it is operators responsibility to
activate more ASPs when needed -manually or via a
monitoring program etc...- . So for me, using n=1 (or
whatever is the needed minimum number of ASPs) and
activating new ASPs during mother's day is a valid
solution -and I think those new ASPs activated for
mother's day have nothing to do with M3UA itself, just
an operational issue-  

    Tolga 
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Tolga,
> 
> Tolga Asveren wrote:                                
>                                 (Fri, 20 Jun 2003
> 13:50:08)
> > Brian,
> > 
> > 1- NTFY has only advisory meaning, there is no
> > "SHOULD" action, which is to be taken after NTFY,
> so
> > your argument that ASPs can rely on NTFY is not
> valid
> 
> The RFC does not say that.  It says:
> 
>   An SGP or IPSP, upon reception of an ASP Active
>   message for the first ASP in a Loadshare AS, MAY
>   choose not to direct traffic to a newly active ASP
>   until it determines that there are sufficient
>   resources to handle the expected load (e.g., until
>   there are "n" ASPs in state ASP-ACTIVE in the AS).
>   In this case, the SGP or IPSP SHOULD withhold the
>   Notify (AS-ACTIVE) until there are sufficient
>   resources.
> 
> And the ASP can rely on it.  The Notify is advisory.
> The ASP can ignore it if it likes.  It does not
> compel the ASP to do anything.  The ASP can ignore
> the notification of AS state change at its own
> peril.
> 
> The argument that an ASP can rely on this notify is
> ensured by the SHOULD in the passage above.
> 
> > -you know it was proposed to make ASPs decide for
> the
> > AS state change by NTFY but it was not accepted,
> 
> That was an observation in an old thread, not a
> rejection.
> 
> The ASP is welcome to use whatever information it
> has at its disposal, INCLUDING Notify, which it can
> rely upon because of the requirement (MUST) for the
> SGP to send it.
> 
> > because it was considered as a too radical
> change-.
> 
> What change?  It is already there in the RFC in
> section 4.3.4.3.  This is also true for M2UA and
> SUA.
> 
> > Nowhere it is stated in RFC nor in IG, that ASPs
> > decide to accept/receive application traffic based
> on
> > NTFY.
> 
> There is no requirement for them to do so.  There
> is, however, a requirement placed on ASPs in thes
> same section (4.3.4.3) that reads;
> 
>   For the n+k redundancy case, ASPs which are in the
>   AS SHOULD coordinate amoung themselves the number
>   of active ASPs in the AS, and should start sending
>   traffic only after 'n' ASPs are active.
> 
> It does not require the ASP to use Notify, but it
> does not keep the ASP from using whatever means it
> has at its disposal for coordinating that 'n' ASPs
> become active.
> > 
> > 2- RFC tells that ASPs SHOULD arrange number of
> ACTIVE
> > ASPs among themselves, but allows SG to start
> routing
> > traffic even with less than n ACTIVE ASP.
> 
> As it should.
> 
> > Just look to
> > the definition of INACTIVE AS in RFC, an AS whith
> no
> > application traffic flowing to/from it. So, they
> might
> > have inconsistent views of AS state.
> 
> No, because the ASP will coordinate that 'n' are
> active.
> 
> > 
> > 3- If n is to be seen as the mother day's value,
> IMO
> > it really has nothing to do with M3UA, because it
> > won't change AS state at all (or maybe you can
> give an
> > example about its relation to M3UA)
> 
> I think you misread the first quote from 4.3.4.3.
> The ASP has little idea what load it will be offered
> when it activates.  This is why it should coordinate
> that 'n' are active.  It might be Mother's Day, it
> might not.  The SG, on the other hand, has a better
> idea of what load will be offered and will activate
> when the number of ASPs is sufficient to handle the
> load.  That is not necessariliy 'n'.  'n' is just an
> example in the quote: "(e.g., until thare are "n"
> ASPs in state ASP-ACTIVE in the AS)".  The SG
> normally activates the AS with the first active ASP
> (as indicated and completely consistent with the
> state diagram and descriptions in the RFC), but it
> MAY wait until 'n' are active.  In any case it sends
> Notify to indicate that th AS is active as it MUST
> (see the MUSTs in section 4.3.4.5).
> 
> It is not a question that the SGP MUST send Notify.
> It MAY wait until sufficient ASPs are active to
> handle the load (and not necessarily "n", but it may
> be "n") and it SHOULD withhold the Notify until
> sufficient ASPs are active to handle the load.
> 
> This provide the SG designer with the freedom to
> meet dynamic load and redundancy needs at the same
> time as ensuring interoperability through the Notify
> and ASP-Active procedures.
> 
> You seem to want to restrict this further, taking
> the necessary flexibility away from the SG designer
> with no resulting benefit.  I cannot agree with the
> proposal.  The RFC is both sufficient and necessary
> in this regard.
> 
> Strike 3.15.
> 
> --brian
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

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



From exim@www1.ietf.org  Tue Jun 24 14:19:30 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29445
	for <sigtran-archive@odin.ietf.org>; Tue, 24 Jun 2003 14:19:30 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5OIJ2v27689
	for sigtran-archive@odin.ietf.org; Tue, 24 Jun 2003 14:19:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19UsNh-0007C6-7C; Tue, 24 Jun 2003 14:19:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19UsN3-0007BX-7w
	for sigtran@optimus.ietf.org; Tue, 24 Jun 2003 14:18:21 -0400
Received: from gw.openss7.com (IDENT:yT6TVjjIxSPs7jm28PlI3vPnNDV9hIqP@gw.openss7.com [142.179.199.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29375
	for <sigtran@ietf.org>; Tue, 24 Jun 2003 14:18:17 -0400 (EDT)
Received: from ns.pigworks.openss7.net (IDENT:z4zWFuqGDuhFU202zHaDqjFMoSFDzFJN@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5OIHkX23377;
	Tue, 24 Jun 2003 12:17:46 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5OIHkJ25609;
	Tue, 24 Jun 2003 12:17:46 -0600
Date: Tue, 24 Jun 2003 12:17:45 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030624121745.A25318@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030620161413.B9154@openss7.org> <20030624175953.73705.qmail@web12808.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030624175953.73705.qmail@web12808.mail.yahoo.com>; from tolga_asveren@yahoo.com on Tue, Jun 24, 2003 at 10:59:53AM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

The RFC permits an SG to wait until sufficient
resources are active before directing traffic to
the ASP as you describe.

There is no reason, however, to require the SG
to wait.

It appears to me that the RFC accomodates your
view, but also accomodates other views (AS
active on first ASP).  If your ASPs can indeed
coordinate 'n' amoung themselves, then it is
moot what the SG does.

IG 3.15 attempts to force the optional procedure
in the SG, of waiting until sufficient resources
are active, to be a mandatory procedure.  (The
changing of MAY to MUST that I have always
disagreed with.)

What need is there to force your view on others
when, as you say, your ASPs can coordinate that
'n' of them are active, anyway?

--brian

Tolga Asveren wrote:                                                                 (Tue, 24 Jun 2003 10:59:53)
> Brian,
> 
> Although I do not believe that it will help us to
> reach a consensus , still I will try to summarize my
> opinions about this topic -otherwise I think we just
> have different opinions/interpretations about text and
> in the last messages I am just repeating the same
> things again and again and wasting bandwith-
> 
> 1- My interpretation of "ASPs coordinating n ACTIVE
> ASPs among themselves" is not that they rely on NTFY,
> but they do this via some communication inside ASP
> cluster. And even if one could argue that NTFY might
> be used for this, unless it is mandated in the
> document, it has little value IMO (in fact this is the
> key point, you assume that NTFY is going to be used
> for this purpose). I can have a RFC compliant ASP,
> which does not coordinate n based on NTFY. So, based
> on that, I think the only way to synchronize AS staet
> changes on ASP and SGPs is a)either using NTFY -this
> is not mandated in RFC- b)or to rely on a
> preconfigured number n . Relying on n requires, that
> both sides know this number and activate AS only after
> n ASPs are ACTIVE.
> 
> 2- In my opinion it questionable, whether SG or ASPs
> have a better view about current load/load to be
> offered on ASPs -especially considering that ASPs
> might serve multiple AS and can be connected to
> multiple SG-. When the AS is not ACTIVE, SG also won't
> receive traffic for it, so it seems to me that it
> can't decide based on traffic dynamics to activate an
> AS or not. Furthermore, as I said above, SG is even
> not aware of the current load on ASPs. Yes, n is
> static, but IMO it is operators responsibility to
> activate more ASPs when needed -manually or via a
> monitoring program etc...- . So for me, using n=1 (or
> whatever is the needed minimum number of ASPs) and
> activating new ASPs during mother's day is a valid
> solution -and I think those new ASPs activated for
> mother's day have nothing to do with M3UA itself, just
> an operational issue-  
> 
>     Tolga 
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                                
> >                                 (Fri, 20 Jun 2003
> > 13:50:08)
> > > Brian,
> > > 
> > > 1- NTFY has only advisory meaning, there is no
> > > "SHOULD" action, which is to be taken after NTFY,
> > so
> > > your argument that ASPs can rely on NTFY is not
> > valid
> > 
> > The RFC does not say that.  It says:
> > 
> >   An SGP or IPSP, upon reception of an ASP Active
> >   message for the first ASP in a Loadshare AS, MAY
> >   choose not to direct traffic to a newly active ASP
> >   until it determines that there are sufficient
> >   resources to handle the expected load (e.g., until
> >   there are "n" ASPs in state ASP-ACTIVE in the AS).
> >   In this case, the SGP or IPSP SHOULD withhold the
> >   Notify (AS-ACTIVE) until there are sufficient
> >   resources.
> > 
> > And the ASP can rely on it.  The Notify is advisory.
> > The ASP can ignore it if it likes.  It does not
> > compel the ASP to do anything.  The ASP can ignore
> > the notification of AS state change at its own
> > peril.
> > 
> > The argument that an ASP can rely on this notify is
> > ensured by the SHOULD in the passage above.
> > 
> > > -you know it was proposed to make ASPs decide for
> > the
> > > AS state change by NTFY but it was not accepted,
> > 
> > That was an observation in an old thread, not a
> > rejection.
> > 
> > The ASP is welcome to use whatever information it
> > has at its disposal, INCLUDING Notify, which it can
> > rely upon because of the requirement (MUST) for the
> > SGP to send it.
> > 
> > > because it was considered as a too radical
> > change-.
> > 
> > What change?  It is already there in the RFC in
> > section 4.3.4.3.  This is also true for M2UA and
> > SUA.
> > 
> > > Nowhere it is stated in RFC nor in IG, that ASPs
> > > decide to accept/receive application traffic based
> > on
> > > NTFY.
> > 
> > There is no requirement for them to do so.  There
> > is, however, a requirement placed on ASPs in thes
> > same section (4.3.4.3) that reads;
> > 
> >   For the n+k redundancy case, ASPs which are in the
> >   AS SHOULD coordinate amoung themselves the number
> >   of active ASPs in the AS, and should start sending
> >   traffic only after 'n' ASPs are active.
> > 
> > It does not require the ASP to use Notify, but it
> > does not keep the ASP from using whatever means it
> > has at its disposal for coordinating that 'n' ASPs
> > become active.
> > > 
> > > 2- RFC tells that ASPs SHOULD arrange number of
> > ACTIVE
> > > ASPs among themselves, but allows SG to start
> > routing
> > > traffic even with less than n ACTIVE ASP.
> > 
> > As it should.
> > 
> > > Just look to
> > > the definition of INACTIVE AS in RFC, an AS whith
> > no
> > > application traffic flowing to/from it. So, they
> > might
> > > have inconsistent views of AS state.
> > 
> > No, because the ASP will coordinate that 'n' are
> > active.
> > 
> > > 
> > > 3- If n is to be seen as the mother day's value,
> > IMO
> > > it really has nothing to do with M3UA, because it
> > > won't change AS state at all (or maybe you can
> > give an
> > > example about its relation to M3UA)
> > 
> > I think you misread the first quote from 4.3.4.3.
> > The ASP has little idea what load it will be offered
> > when it activates.  This is why it should coordinate
> > that 'n' are active.  It might be Mother's Day, it
> > might not.  The SG, on the other hand, has a better
> > idea of what load will be offered and will activate
> > when the number of ASPs is sufficient to handle the
> > load.  That is not necessariliy 'n'.  'n' is just an
> > example in the quote: "(e.g., until thare are "n"
> > ASPs in state ASP-ACTIVE in the AS)".  The SG
> > normally activates the AS with the first active ASP
> > (as indicated and completely consistent with the
> > state diagram and descriptions in the RFC), but it
> > MAY wait until 'n' are active.  In any case it sends
> > Notify to indicate that th AS is active as it MUST
> > (see the MUSTs in section 4.3.4.5).
> > 
> > It is not a question that the SGP MUST send Notify.
> > It MAY wait until sufficient ASPs are active to
> > handle the load (and not necessarily "n", but it may
> > be "n") and it SHOULD withhold the Notify until
> > sufficient ASPs are active to handle the load.
> > 
> > This provide the SG designer with the freedom to
> > meet dynamic load and redundancy needs at the same
> > time as ensuring interoperability through the Notify
> > and ASP-Active procedures.
> > 
> > You seem to want to restrict this further, taking
> > the necessary flexibility away from the SG designer
> > with no resulting benefit.  I cannot agree with the
> > proposal.  The RFC is both sufficient and necessary
> > in this regard.
> > 
> > Strike 3.15.
> > 
> > --brian
> > 
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> 
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Tue Jun 24 16:57:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10807
	for <sigtran-archive@odin.ietf.org>; Tue, 24 Jun 2003 16:57:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5OKv2f22682
	for sigtran-archive@odin.ietf.org; Tue, 24 Jun 2003 16:57:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Uuqb-0005tb-2k; Tue, 24 Jun 2003 16:57:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Uupm-0005t3-Ab
	for sigtran@optimus.ietf.org; Tue, 24 Jun 2003 16:56:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10751
	for <sigtran@ietf.org>; Tue, 24 Jun 2003 16:56:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Uuoz-0007Eg-00
	for sigtran@ietf.org; Tue, 24 Jun 2003 16:55:21 -0400
Received: from web12809.mail.yahoo.com ([216.136.174.136])
	by ietf-mx with smtp (Exim 4.12)
	id 19Uuoo-0007ET-00
	for sigtran@ietf.org; Tue, 24 Jun 2003 16:55:10 -0400
Message-ID: <20030624205450.71566.qmail@web12809.mail.yahoo.com>
Received: from [208.255.120.2] by web12809.mail.yahoo.com via HTTP; Tue, 24 Jun 2003 13:54:50 PDT
Date: Tue, 24 Jun 2003 13:54:50 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] Re: M3UA Notify message
To: sigtran@ietf.org
In-Reply-To: <20030624121745.A25318@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,
(some more repeating of my ideas about this topic ;-)
)
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Tolga,
> 
> The RFC permits an SG to wait until sufficient
> resources are active before directing traffic to
> the ASP as you describe.
> 
> There is no reason, however, to require the SG
> to wait.
[TOLGA]Basically, what you are describing is "Let SG
decide by itself, when to activate AS". In such a
case, there should be a mechanism for SG to tell about
this state change, which will make the ASPs to change
their AS state accordingly -IMO, NTFY, as decribed in
RFC can't be seen as serving this purpose, as it is
not mandatory that ASPs update AS state based on
that-. I also doubt, whether SG can dynamically decide
when to activate AS, while it does not receive traffic
for AS.
> 
> It appears to me that the RFC accomodates your
> view, but also accomodates other views (AS
> active on first ASP).  If your ASPs can indeed
> coordinate 'n' amoung themselves, then it is
> moot what the SG does.
[TOLGA] IMO it is not irrelevant what SG does, if ASPs
coordinate 'n' among themselves -not based on NTFY-.
In such a case, it might happen that SG switches AS
state to ACTIVE with less than n ACTIVE ASPs but ASPs
will still wait for n ASPs to become ACTIVE and will
have AS state INACTIVE. The result will be SG exposing
AS as available to SS7 network, while in fact it was
not ready on ASP side, this IMO shouldn't happen. 
> 
> IG 3.15 attempts to force the optional procedure
> in the SG, of waiting until sufficient resources
> are active, to be a mandatory procedure.  (The
> changing of MAY to MUST that I have always
> disagreed with.)
> 
> What need is there to force your view on others
> when, as you say, your ASPs can coordinate that
> 'n' of them are active, anyway?
[TOLGA]IMO, it is important that AS states are
consistent on both sides(so the goal is not to put
restrictions).
Secondly, if SG does not see AS as ACTIVE, there
shouldn't be traffic directed for this AS to this SG.
So, which traffic is SG supposed to withhold?
Initially SG should see AS as ACTIVE -before there was
any traffic-, and this IMO can be decided only based
on number of ACTIVE ASPs -where this number can be
also 1 of course-.
> 
> --brian
> 
> Tolga Asveren wrote:                                
>                                 (Tue, 24 Jun 2003
> 10:59:53)
> > Brian,
> > 
> > Although I do not believe that it will help us to
> > reach a consensus , still I will try to summarize
> my
> > opinions about this topic -otherwise I think we
> just
> > have different opinions/interpretations about text
> and
> > in the last messages I am just repeating the same
> > things again and again and wasting bandwith-
> > 
> > 1- My interpretation of "ASPs coordinating n
> ACTIVE
> > ASPs among themselves" is not that they rely on
> NTFY,
> > but they do this via some communication inside ASP
> > cluster. And even if one could argue that NTFY
> might
> > be used for this, unless it is mandated in the
> > document, it has little value IMO (in fact this is
> the
> > key point, you assume that NTFY is going to be
> used
> > for this purpose). I can have a RFC compliant ASP,
> > which does not coordinate n based on NTFY. So,
> based
> > on that, I think the only way to synchronize AS
> staet
> > changes on ASP and SGPs is a)either using NTFY
> -this
> > is not mandated in RFC- b)or to rely on a
> > preconfigured number n . Relying on n requires,
> that
> > both sides know this number and activate AS only
> after
> > n ASPs are ACTIVE.
> > 
> > 2- In my opinion it questionable, whether SG or
> ASPs
> > have a better view about current load/load to be
> > offered on ASPs -especially considering that ASPs
> > might serve multiple AS and can be connected to
> > multiple SG-. When the AS is not ACTIVE, SG also
> won't
> > receive traffic for it, so it seems to me that it
> > can't decide based on traffic dynamics to activate
> an
> > AS or not. Furthermore, as I said above, SG is
> even
> > not aware of the current load on ASPs. Yes, n is
> > static, but IMO it is operators responsibility to
> > activate more ASPs when needed -manually or via a
> > monitoring program etc...- . So for me, using n=1
> (or
> > whatever is the needed minimum number of ASPs) and
> > activating new ASPs during mother's day is a valid
> > solution -and I think those new ASPs activated for
> > mother's day have nothing to do with M3UA itself,
> just
> > an operational issue-  
> > 
> >     Tolga 
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > Tolga,
> > > 
> > > Tolga Asveren wrote:                            
>    
> > >                                 (Fri, 20 Jun
> 2003
> > > 13:50:08)
> > > > Brian,
> > > > 
> > > > 1- NTFY has only advisory meaning, there is no
> > > > "SHOULD" action, which is to be taken after
> NTFY,
> > > so
> > > > your argument that ASPs can rely on NTFY is
> not
> > > valid
> > > 
> > > The RFC does not say that.  It says:
> > > 
> > >   An SGP or IPSP, upon reception of an ASP
> Active
> > >   message for the first ASP in a Loadshare AS,
> MAY
> > >   choose not to direct traffic to a newly active
> ASP
> > >   until it determines that there are sufficient
> > >   resources to handle the expected load (e.g.,
> until
> > >   there are "n" ASPs in state ASP-ACTIVE in the
> AS).
> > >   In this case, the SGP or IPSP SHOULD withhold
> the
> > >   Notify (AS-ACTIVE) until there are sufficient
> > >   resources.
> > > 
> > > And the ASP can rely on it.  The Notify is
> advisory.
> > > The ASP can ignore it if it likes.  It does not
> > > compel the ASP to do anything.  The ASP can
> ignore
> > > the notification of AS state change at its own
> > > peril.
> > > 
> > > The argument that an ASP can rely on this notify
> is
> > > ensured by the SHOULD in the passage above.
> > > 
> > > > -you know it was proposed to make ASPs decide
> for
> > > the
> > > > AS state change by NTFY but it was not
> accepted,
> > > 
> > > That was an observation in an old thread, not a
> > > rejection.
> > > 


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

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



From exim@www1.ietf.org  Tue Jun 24 17:26:28 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11803
	for <sigtran-archive@odin.ietf.org>; Tue, 24 Jun 2003 17:26:28 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5OLQ1G27387
	for sigtran-archive@odin.ietf.org; Tue, 24 Jun 2003 17:26:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19UvIf-00077O-2P; Tue, 24 Jun 2003 17:26:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19UvI4-00075K-J2
	for sigtran@optimus.ietf.org; Tue, 24 Jun 2003 17:25:24 -0400
Received: from gw.openss7.com (IDENT:jANQshXjVM3qFq/KswJ5bJNBlNi5mcVX@gw.openss7.com [142.179.199.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11733
	for <sigtran@ietf.org>; Tue, 24 Jun 2003 17:25:05 -0400 (EDT)
Received: from ns.pigworks.openss7.net (IDENT:3Z6ejpGUr73nVvfap1SVXvhT7BbE43Rw@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5OLOoX25895;
	Tue, 24 Jun 2003 15:24:50 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5OLOoT28544;
	Tue, 24 Jun 2003 15:24:50 -0600
Date: Tue, 24 Jun 2003 15:24:49 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030624152449.A28080@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030624121745.A25318@openss7.org> <20030624205450.71566.qmail@web12809.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030624205450.71566.qmail@web12809.mail.yahoo.com>; from tolga_asveren@yahoo.com on Tue, Jun 24, 2003 at 01:54:50PM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

Tolga Asveren wrote:                                                                 (Tue, 24 Jun 2003 13:54:50)
> Brian,
> (some more repeating of my ideas about this topic ;-)
> )
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > The RFC permits an SG to wait until sufficient
> > resources are active before directing traffic to
> > the ASP as you describe.
> > 
> > There is no reason, however, to require the SG
> > to wait.
> [TOLGA]Basically, what you are describing is "Let SG
> decide by itself, when to activate AS". In such a
> case, there should be a mechanism for SG to tell about
> this state change, which will make the ASPs to change
> their AS state accordingly -IMO, NTFY, as decribed in
> RFC can't be seen as serving this purpose, as it is
> not mandatory that ASPs update AS state based on
> that-. I also doubt, whether SG can dynamically decide
> when to activate AS, while it does not receive traffic
> for AS.

NTFY serves this purpose.  Whether your ASP
relies on it or not is up to the ASP designer.
You say your ASPs can coordinate 'n' without
relying on NTFY, so there is obviously no need
for any extra protocol to signal this.

> > 
> > It appears to me that the RFC accomodates your
> > view, but also accomodates other views (AS
> > active on first ASP).  If your ASPs can indeed
> > coordinate 'n' amoung themselves, then it is
> > moot what the SG does.
> [TOLGA] IMO it is not irrelevant what SG does, if ASPs
> coordinate 'n' among themselves -not based on NTFY-.
> In such a case, it might happen that SG switches AS
> state to ACTIVE with less than n ACTIVE ASPs but ASPs
> will still wait for n ASPs to become ACTIVE and will
> have AS state INACTIVE. The result will be SG exposing
> AS as available to SS7 network, while in fact it was
> not ready on ASP side, this IMO shouldn't happen. 

Here's where your wrong.  Activating an AS and
traffic from the SS7 network are not correlated.
There is no requirement to direct traffic after
AS-ACTIVE.  When the SG indicates SS7 network
availability is a function of the NIF and there
are no requirements in the RFC in this regard.
Also, even after the NIF decides to place the PC
or UP as available, there will be some
considerable time before traffic will start.
Distant signalling points and user parts will
have to time out on procedures before they will
restart traffic.  If an SG chooses to do this on
the first active ASP (getting a jump on restart
and knowing that it will take some time for
traffic to resume, and knowing that the APSs
will coordinate 'n' amoungst themselves anyway)
the is is allowed to do so by the RFC, but not
by the IG 3.15 proposal.

> > 
> > IG 3.15 attempts to force the optional procedure
> > in the SG, of waiting until sufficient resources
> > are active, to be a mandatory procedure.  (The
> > changing of MAY to MUST that I have always
> > disagreed with.)
> > 
> > What need is there to force your view on others
> > when, as you say, your ASPs can coordinate that
> > 'n' of them are active, anyway?
> [TOLGA]IMO, it is important that AS states are
> consistent on both sides(so the goal is not to put
> restrictions).

It is not so important.  Procedures are in place
to resynchronize state.  One of the most
important ones is the Notify procedure.  The SG
MUST notify ASPs of its perceived state for the
AS.  It is not an option.  The ASP can rely on
this because it is an absolute requirement.  (MUST)

> Secondly, if SG does not see AS as ACTIVE, there
> shouldn't be traffic directed for this AS to this SG.

The timing of traffic and AS activity is not
correlated or specified.  This is an NIF
function.  The SG cannot decide WHEN to resume
traffic, it is the remote signalling point that
decides WHEN to resume traffic.

By "direct traffic" the RFC means: do that NIF
thing to allow remote signalling points to
resume traffic at some time in the future.

> So, which traffic is SG supposed to withhold?

The SG does not withhold traffic, it withholds
the NTFY)(AS Active) if it waits to do that NIF
thing until it is confident that there are
sufficient ASP resources active to handle some
future load.  But this must remain optional.
The SG must be permitted to do that NIF thing on
the first active ASP (or 'm'th" or after a timeout) or
whenever it deems necessary after the first
active ASP.  And this cannot be mandated as 'n'.

> Initially SG should see AS as ACTIVE -before there was
> any traffic-, and this IMO can be decided only based
> on number of ACTIVE ASPs -where this number can be
> also 1 of course-.

No. The SG can do that NIF thing in anticipation
of 'n' ASPs being active because it has the
knowledge that 'n' will become active because
the ASPs SHOULD coordinate that 'n' are active.

There is no problem with the existing RFC.

Mandating 'n' is unacceptable.

I will ask you once more the question that you
have neglected to answer:

What bad thing will happen if the SG activates
(does that NIF thing) on the first ASP and the ASPs
wait until 'n'?

Quite frankly there is no bad thing that will
happen and therefore all interoperability needs
are met by the existing RFC.

--brian

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

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



From exim@www1.ietf.org  Thu Jun 26 04:24:47 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12032
	for <sigtran-archive@odin.ietf.org>; Thu, 26 Jun 2003 04:24:47 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5Q8OJR22798
	for sigtran-archive@odin.ietf.org; Thu, 26 Jun 2003 04:24:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VS3H-0005vb-IV; Thu, 26 Jun 2003 04:24:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VRqY-00056d-SQ
	for sigtran@optimus.ietf.org; Thu, 26 Jun 2003 04:11:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11719
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 04:11:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VRqW-0006Wv-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 04:11:08 -0400
Received: from falcon.ericsson.se ([193.180.251.52] helo=falcon.al.sw.ericsson.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19VRqL-0006Ws-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 04:10:57 -0400
Received: from esealnt610.al.sw.ericsson.se (alteon-nat3.sw.ericsson.se [153.88.254.120])
	by falcon.al.sw.ericsson.se (8.12.9/8.12.9/WIREfire-1.6b) with ESMTP id h5Q8Bqcv020866;
	Thu, 26 Jun 2003 10:11:52 +0200
Received: from ESEALNT745.al.sw.ericsson.se ([153.88.251.5]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id N4L8MMVN; Thu, 26 Jun 2003 10:10:54 +0200
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NSLY00K4>; Thu, 26 Jun 2003 10:10:50 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C9D@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>
Cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: RE: [Sigtran] Re: M3UA Notify message
Date: Thu, 26 Jun 2003 10:10:30 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


Brian, 

More comments on yours....

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: jueves, 26 de junio de 2003 9:44
> To: Javier Pastor-Balbas (ECE)
> Cc: Tolga Asveren; sigtran@ietf.org
> Subject: Re: [Sigtran] Re: M3UA Notify message
> 
> 
> Javier,
> 
> Your proposal for 3.15 is still unacceptable.
> 
> Please see comments below...
> 
> Javier Pastor-Balbas (ECE) wrote:                             
>                       (Thu, 26 Jun 2003 09:12:20)
> > Brian, 
> > 
> > See my comments inline...
> > 
> > Cheers // Javier.
> > 
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > Sent: martes, 24 de junio de 2003 23:25
> > > To: Tolga Asveren
> > > Cc: sigtran@ietf.org
> > > Subject: Re: [Sigtran] Re: M3UA Notify message
> > > 
> > > 
> > > Tolga,
> > > 
> > > Tolga Asveren wrote:                                          
> > >                        (Tue, 24 Jun 2003 13:54:50)
> > > > Brian,
> > > > (some more repeating of my ideas about this topic ;-)
> > > > )
> > > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > wrote:
> > > > > Tolga,
> > > > > 
> > > > > The RFC permits an SG to wait until sufficient
> > > > > resources are active before directing traffic to
> > > > > the ASP as you describe.
> > > > > 
> > > > > There is no reason, however, to require the SG
> > > > > to wait.
> > > > [TOLGA]Basically, what you are describing is "Let SG
> > > > decide by itself, when to activate AS". In such a
> > > > case, there should be a mechanism for SG to tell about
> > > > this state change, which will make the ASPs to change
> > > > their AS state accordingly -IMO, NTFY, as decribed in
> > > > RFC can't be seen as serving this purpose, as it is
> > > > not mandatory that ASPs update AS state based on
> > > > that-. I also doubt, whether SG can dynamically decide
> > > > when to activate AS, while it does not receive traffic
> > > > for AS.
> > > 
> > > NTFY serves this purpose.  Whether your ASP
> > > relies on it or not is up to the ASP designer.
> > > You say your ASPs can coordinate 'n' without
> > > relying on NTFY, so there is obviously no need
> > > for any extra protocol to signal this.
> > > 
> > 
> > It can not be up to the ASP designer !! Upon the activation 
> of the first ASP the following scenario will happen:
> > - SG thinks that AS is in AS-ACTIVE when the first ASP gets 
> the ASP-ACTIVE state
> > - ASP in ASP-ACTIVE state remains itself in an AS with 
> AS-INACTIVE (less than n ASPs are ASP-ACTIVE and there is 
> ASP-coordination)
> > 
> > There is not a common network view !! This MUST be fixed.
> 
> The RFC does not say that the ASP considers itself in the
> AS-INACTIVE state until n ASPs are active.  Read again:
> 
>    For the n+k redundancy case, ASPs which are in that AS should
>    coordinate among themselves the number of active ASPs in 
> the AS, and
>    should start sending traffic only after n ASPs are active.
> 
> The ASP considers itself in the ASP-ACTIVE state for the AS
> (and may consider the AS active) as soon as it receives the
> ASP Active Ack.
> 
> The ASP may consider the AS active as soon as it receives an
> NTFY(AS-Active) regardless of whether it is ASP-INACTIVE for
> the AS.
> 
> What the ASPs do is not start sending traffic until 'n' are
> active.
> 
> > 
> > 
> > 
> > > > > 
> > > > > It appears to me that the RFC accomodates your
> > > > > view, but also accomodates other views (AS
> > > > > active on first ASP).  If your ASPs can indeed
> > > > > coordinate 'n' amoung themselves, then it is
> > > > > moot what the SG does.
> > > > [TOLGA] IMO it is not irrelevant what SG does, if ASPs
> > > > coordinate 'n' among themselves -not based on NTFY-.
> > > > In such a case, it might happen that SG switches AS
> > > > state to ACTIVE with less than n ACTIVE ASPs but ASPs
> > > > will still wait for n ASPs to become ACTIVE and will
> > > > have AS state INACTIVE. The result will be SG exposing
> > > > AS as available to SS7 network, while in fact it was
> > > > not ready on ASP side, this IMO shouldn't happen. 
> > > 
> > > Here's where your wrong.  Activating an AS and
> > > traffic from the SS7 network are not correlated.
> > > There is no requirement to direct traffic after
> > > AS-ACTIVE.  When the SG indicates SS7 network
> > > availability is a function of the NIF and there
> > > are no requirements in the RFC in this regard.
> > 
> > Read the description of the AS-INACTIVE state. No traffic 
> processing for the
> > ASPs belonging to that AS.
> 
> Read the AS-ACTIVE state description.  It does not
> say that the SG must direct any traffic.
> 
It says "no application traffic is active". So there must not be any application traffic with the AS, which correponds with AS-INACTIVE.

> DUNA(*) is a particular case in point.  Because an
> AS is AS-ACTIVE does not mean that traffic is
> directed at the ASPs.  So, I stand by my statement:
> "Activating an AS and traffic from the SS7 network
> are not correlated."
> 
> Also, the AS state at ASP and SG is not synchronized.  See
> the warnings regarding message loss in Section 4.3.4.3.


These are regarding the delay on reception of the ASPAC-ACK, that will be added to the total traffic loss in there exists a different perception of the AS state in the network. 
> 
> > 
> > > Also, even after the NIF decides to place the PC
> > > or UP as available, there will be some
> > > considerable time before traffic will start.
> > > Distant signalling points and user parts will
> > > have to time out on procedures before they will
> > > restart traffic.  If an SG chooses to do this on
> > > the first active ASP (getting a jump on restart
> > > and knowing that it will take some time for
> > > traffic to resume, and knowing that the APSs
> > > will coordinate 'n' amoungst themselves anyway)
> > > the is is allowed to do so by the RFC, but not
> > > by the IG 3.15 proposal.
> > > 
> > So you'll be happy if we include a SHOULD instead of MUST 
> for n ASPs in the
> > transition form AS-INACTIVE to AS-ACTIVE...
> 
> It has to stay as MAY, as indicated in the current RFC.
> SHOULD is unacceptable.
> 
There is no explicit "MAY" in the current RFC...

> > 
> > 
> > > > > 
> > > > > IG 3.15 attempts to force the optional procedure
> > > > > in the SG, of waiting until sufficient resources
> > > > > are active, to be a mandatory procedure.  (The
> > > > > changing of MAY to MUST that I have always
> > > > > disagreed with.)
> > > > > 
> > > > > What need is there to force your view on others
> > > > > when, as you say, your ASPs can coordinate that
> > > > > 'n' of them are active, anyway?
> > > > [TOLGA]IMO, it is important that AS states are
> > > > consistent on both sides(so the goal is not to put
> > > > restrictions).
> > > 
> > > It is not so important.  Procedures are in place
> > > to resynchronize state.  One of the most
> > > important ones is the Notify procedure.  The SG
> > > MUST notify ASPs of its perceived state for the
> > > AS.  It is not an option.  The ASP can rely on
> > > this because it is an absolute requirement.  (MUST)
> > > 
> > 
> > But also the ASP will syncronize with the rest and wait for 
> n ASPs in ASP-ACTIVE...
> > The ASP can and cannot rely on it. This is only advisory. 
> It is NOT either a MUST or a SHOULD to rely on NTFY.
> 
> It is a MUST that the SG sends Notify.  Therefore the ASP
> can rely on it.  If the ASP cannot rely on it, why else
> would it be a MUST to send it?

I meant "may or may not". There is nothing in the RFC saying that the ASP MUST take into account the NTFY or trigger any action from its reception. Although it is a good test that both network nodes have the same state understanding.
> 
> The MUST keyword is used where an action is required for
> interoperability.  The SG MUST send Notify, so the ASP
> can rely on it.  It is that simple.
> 
As I said it can rely, but it may not...

> If the ASP desginer chooses to ignore the Notifications
> that the SG is required to send, she does so at her own
> peril.
> 
> > 
> > > > Secondly, if SG does not see AS as ACTIVE, there
> > > > shouldn't be traffic directed for this AS to this SG.
> > > 
> > > The timing of traffic and AS activity is not
> > > correlated or specified.  This is an NIF
> > > function.  The SG cannot decide WHEN to resume
> > > traffic, it is the remote signalling point that
> > > decides WHEN to resume traffic.
> > > 
> > > By "direct traffic" the RFC means: do that NIF
> > > thing to allow remote signalling points to
> > > resume traffic at some time in the future.
> > > 
> > > > So, which traffic is SG supposed to withhold?
> > > 
> > > The SG does not withhold traffic, it withholds
> > > the NTFY)(AS Active) if it waits to do that NIF
> > > thing until it is confident that there are
> > > sufficient ASP resources active to handle some
> > > future load.  But this must remain optional.
> > > The SG must be permitted to do that NIF thing on
> > > the first active ASP (or 'm'th" or after a timeout) or
> > > whenever it deems necessary after the first
> > > active ASP.  And this cannot be mandated as 'n'.
> > > 
> > > > Initially SG should see AS as ACTIVE -before there was
> > > > any traffic-, and this IMO can be decided only based
> > > > on number of ACTIVE ASPs -where this number can be
> > > > also 1 of course-.
> > > 
> > > No. The SG can do that NIF thing in anticipation
> > > of 'n' ASPs being active because it has the
> > > knowledge that 'n' will become active because
> > > the ASPs SHOULD coordinate that 'n' are active.
> > > 
> > This is not stated in the RFC. 
> 
> That is why the SG is allowed to do so.  Because the
> RFC neither forbids nor recommends against it.
> 
Since the RFC does not state a word about it. It is an implementation choice and not a standard way of working.

> > 
> > > There is no problem with the existing RFC.
> > > 
> > > Mandating 'n' is unacceptable.
> > > 
> > RFC does it as per section 1.4.4.1
> 
> There are no requirements in section 1.4.4.1.
> 
There are not requirements, there are DEFINITIONS: what things are. These are the basis for the protocol explanation.

> > 
> > > I will ask you once more the question that you
> > > have neglected to answer:
> > > 
> > > What bad thing will happen if the SG activates
> > > (does that NIF thing) on the first ASP and the ASPs
> > > wait until 'n'?
> > > 
> > 
> > Answer:
> > - Lack of synchronization among the two parts: ASPs and SGPs
> 
> Lack of synchronization already (intentionally) exists in
> the protocol.  See the comments regarding message loss in
> 4.3.4.3, and particularly:
> 
>    At the ASP, the ASP Active Ack message received is not 
> acknowledged.
>    Layer Management is informed with an M-ASP_ACTIVE confirm 
> primitive.
>    It is possible for the ASP to receive Data message(s) 
> before the ASP
>    Active Ack message as the ASP Active Ack and Data messages 
> from an SG
>    or IPSP may be sent on different SCTP streams.  Message loss is
>    possible as the ASP does not consider itself in the 
> ASP-ACTIVE state
>    until reception of the ASP Active Ack message.
> 

This is due to the network latency, what is unavoidable. But not due to different state view !! The latter should be avoided.
> 
> > - Traffic Loss if the SS7 network start sending traffic 
> before "n" ASPs know the AS is ACTIVE
> 
> What traffic loss?  Give an example.

SS7 nodes start sending traffic to the AS and both the AS has not still "n" ASPs in ASP-ACTIVE and the SG buffer is full.

> 
> > 
> > Which is not tolerable in carrier-grade networks with 
> availability requirements of 99.9999%
> 
> Performance requirements are outside the scope of the RFC.
> 
> (M3UA cannot even meet MTP3 performance requirements with
> IETF recommended SCTP parameters, not M3UA proceedures.)

As you probably know although SCTP was first thought for signaling traffic, in its later steps it was consider to be general purpose. Hope you don't use such parameters for signaling traffic....  

> 
> > 
> > > Quite frankly there is no bad thing that will
> > > happen and therefore all interoperability needs
> > > are met by the existing RFC.
> > 
> > 
> > Your interpretation of the RFC seems to be biased since the RFC also
> > includes statements as 1.4.4.1, the AS-INACTIVE definition 
> or examples for
> > n>1. 
> 
> Section 1.4.4.1, quoted here for others, says:
> 
>    The failover model supports an "n+k" redundancy model, 
> where "n" ASPs
>    is the minimum number of redundant ASPs required to handle traffic
>    and "k" ASPs are available to take over for a failed or unavailable
>    ASP.
> 
> There are no requirements in this section whatsoever.  It is 
> introductory.

As I said before, they are definitions that set up the basis for the protocol.

> Also, we agreed by concensus that the "traffic" referred to here is
> "maximum engineered load".

Maximum engineered load is not peak load, it is the load you are expected to be able to offer 99.9999% of the time... And at least at the beginning you should get it before activate traffic.



Cheers // Javier.

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

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



From exim@www1.ietf.org  Thu Jun 26 04:24:35 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11943
	for <sigtran-archive@odin.ietf.org>; Thu, 26 Jun 2003 04:24:35 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5Q8O7n21642
	for sigtran-archive@odin.ietf.org; Thu, 26 Jun 2003 04:24:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VS32-0005cL-91; Thu, 26 Jun 2003 04:24:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VQxI-00018q-Iz
	for sigtran@optimus.ietf.org; Thu, 26 Jun 2003 03:15:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10889
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 03:13:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VQx1-0006JF-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 03:13:47 -0400
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47] helo=penguin.al.sw.ericsson.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19VQwq-0006If-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 03:13:36 -0400
Received: from esealnt613.al.sw.ericsson.se (alteon-nat8.sw.ericsson.se [153.88.254.125])
	by penguin.al.sw.ericsson.se (8.12.9/8.12.9/WIREfire-1.6b) with ESMTP id h5Q7Cew2019983;
	Thu, 26 Jun 2003 09:12:41 +0200 (MEST)
Received: from ESEALNT745.al.sw.ericsson.se ([153.88.251.5]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id MVP0L97T; Thu, 26 Jun 2003 09:12:33 +0200
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NSLY09HF>; Thu, 26 Jun 2003 09:12:38 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C9C@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>,
        Tolga Asveren
	 <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] Re: M3UA Notify message
Date: Thu, 26 Jun 2003 09:12:20 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian, 

See my comments inline...

Cheers // Javier.

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: martes, 24 de junio de 2003 23:25
> To: Tolga Asveren
> Cc: sigtran@ietf.org
> Subject: Re: [Sigtran] Re: M3UA Notify message
> 
> 
> Tolga,
> 
> Tolga Asveren wrote:                                          
>                        (Tue, 24 Jun 2003 13:54:50)
> > Brian,
> > (some more repeating of my ideas about this topic ;-)
> > )
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > Tolga,
> > > 
> > > The RFC permits an SG to wait until sufficient
> > > resources are active before directing traffic to
> > > the ASP as you describe.
> > > 
> > > There is no reason, however, to require the SG
> > > to wait.
> > [TOLGA]Basically, what you are describing is "Let SG
> > decide by itself, when to activate AS". In such a
> > case, there should be a mechanism for SG to tell about
> > this state change, which will make the ASPs to change
> > their AS state accordingly -IMO, NTFY, as decribed in
> > RFC can't be seen as serving this purpose, as it is
> > not mandatory that ASPs update AS state based on
> > that-. I also doubt, whether SG can dynamically decide
> > when to activate AS, while it does not receive traffic
> > for AS.
> 
> NTFY serves this purpose.  Whether your ASP
> relies on it or not is up to the ASP designer.
> You say your ASPs can coordinate 'n' without
> relying on NTFY, so there is obviously no need
> for any extra protocol to signal this.
> 

It can not be up to the ASP designer !! Upon the activation of the first ASP the following scenario will happen:
- SG thinks that AS is in AS-ACTIVE when the first ASP gets the ASP-ACTIVE state
- ASP in ASP-ACTIVE state remains itself in an AS with AS-INACTIVE (less than n ASPs are ASP-ACTIVE and there is ASP-coordination)

There is not a common network view !! This MUST be fixed.



> > > 
> > > It appears to me that the RFC accomodates your
> > > view, but also accomodates other views (AS
> > > active on first ASP).  If your ASPs can indeed
> > > coordinate 'n' amoung themselves, then it is
> > > moot what the SG does.
> > [TOLGA] IMO it is not irrelevant what SG does, if ASPs
> > coordinate 'n' among themselves -not based on NTFY-.
> > In such a case, it might happen that SG switches AS
> > state to ACTIVE with less than n ACTIVE ASPs but ASPs
> > will still wait for n ASPs to become ACTIVE and will
> > have AS state INACTIVE. The result will be SG exposing
> > AS as available to SS7 network, while in fact it was
> > not ready on ASP side, this IMO shouldn't happen. 
> 
> Here's where your wrong.  Activating an AS and
> traffic from the SS7 network are not correlated.
> There is no requirement to direct traffic after
> AS-ACTIVE.  When the SG indicates SS7 network
> availability is a function of the NIF and there
> are no requirements in the RFC in this regard.

Read the description of the AS-INACTIVE state. No traffic processing for the ASPs belonging to that AS.

> Also, even after the NIF decides to place the PC
> or UP as available, there will be some
> considerable time before traffic will start.
> Distant signalling points and user parts will
> have to time out on procedures before they will
> restart traffic.  If an SG chooses to do this on
> the first active ASP (getting a jump on restart
> and knowing that it will take some time for
> traffic to resume, and knowing that the APSs
> will coordinate 'n' amoungst themselves anyway)
> the is is allowed to do so by the RFC, but not
> by the IG 3.15 proposal.
> 
So you'll be happy if we include a SHOULD instead of MUST for n ASPs in the transition form AS-INACTIVE to AS-ACTIVE...


> > > 
> > > IG 3.15 attempts to force the optional procedure
> > > in the SG, of waiting until sufficient resources
> > > are active, to be a mandatory procedure.  (The
> > > changing of MAY to MUST that I have always
> > > disagreed with.)
> > > 
> > > What need is there to force your view on others
> > > when, as you say, your ASPs can coordinate that
> > > 'n' of them are active, anyway?
> > [TOLGA]IMO, it is important that AS states are
> > consistent on both sides(so the goal is not to put
> > restrictions).
> 
> It is not so important.  Procedures are in place
> to resynchronize state.  One of the most
> important ones is the Notify procedure.  The SG
> MUST notify ASPs of its perceived state for the
> AS.  It is not an option.  The ASP can rely on
> this because it is an absolute requirement.  (MUST)
> 

But also the ASP will syncronize with the rest and wait for n ASPs in ASP-ACTIVE...
The ASP can and cannot rely on it. This is only advisory. It is NOT either a MUST or a SHOULD to rely on NTFY.

> > Secondly, if SG does not see AS as ACTIVE, there
> > shouldn't be traffic directed for this AS to this SG.
> 
> The timing of traffic and AS activity is not
> correlated or specified.  This is an NIF
> function.  The SG cannot decide WHEN to resume
> traffic, it is the remote signalling point that
> decides WHEN to resume traffic.
> 
> By "direct traffic" the RFC means: do that NIF
> thing to allow remote signalling points to
> resume traffic at some time in the future.
> 
> > So, which traffic is SG supposed to withhold?
> 
> The SG does not withhold traffic, it withholds
> the NTFY)(AS Active) if it waits to do that NIF
> thing until it is confident that there are
> sufficient ASP resources active to handle some
> future load.  But this must remain optional.
> The SG must be permitted to do that NIF thing on
> the first active ASP (or 'm'th" or after a timeout) or
> whenever it deems necessary after the first
> active ASP.  And this cannot be mandated as 'n'.
> 
> > Initially SG should see AS as ACTIVE -before there was
> > any traffic-, and this IMO can be decided only based
> > on number of ACTIVE ASPs -where this number can be
> > also 1 of course-.
> 
> No. The SG can do that NIF thing in anticipation
> of 'n' ASPs being active because it has the
> knowledge that 'n' will become active because
> the ASPs SHOULD coordinate that 'n' are active.
> 
This is not stated in the RFC. 

> There is no problem with the existing RFC.
> 
> Mandating 'n' is unacceptable.
> 
RFC does it as per section 1.4.4.1

> I will ask you once more the question that you
> have neglected to answer:
> 
> What bad thing will happen if the SG activates
> (does that NIF thing) on the first ASP and the ASPs
> wait until 'n'?
> 

Answer:
- Lack of synchronization among the two parts: ASPs and SGPs
- Traffic Loss if the SS7 network start sending traffic before "n" ASPs know the AS is ACTIVE

Which is not tolerable in carrier-grade networks with availability requirements of 99.9999%

> Quite frankly there is no bad thing that will
> happen and therefore all interoperability needs
> are met by the existing RFC.


Your interpretation of the RFC seems to be biased since the RFC also includes statements as 1.4.4.1, the AS-INACTIVE definition or examples for n>1. 


> 
> --brian
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 

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



From exim@www1.ietf.org  Thu Jun 26 04:24:51 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12080
	for <sigtran-archive@odin.ietf.org>; Thu, 26 Jun 2003 04:24:51 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5Q8OOg22913
	for sigtran-archive@odin.ietf.org; Thu, 26 Jun 2003 04:24:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VS3L-0005xT-VC; Thu, 26 Jun 2003 04:24:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VS2L-0005Yj-9C
	for sigtran@optimus.ietf.org; Thu, 26 Jun 2003 04:23:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11865
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 04:23:18 -0400 (EDT)
From: agurmukhani@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VS2I-0006ZH-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 04:23:18 -0400
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VS26-0006Z6-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 04:23:06 -0400
Received: from hindon.hss.co.in (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h5Q8IsO25613
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 13:48:54 +0530 (IST)
Received: from ultra.hss.co.in (ultra [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h5Q8IqO25605
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 13:48:52 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h5Q8MQO21135
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 13:52:26 +0530 (IST)
To: sigtran@ietf.org
Date: Thu, 26 Jun 2003 13:45:52 +0530
Message-ID: <OF68EE9297.B8EE6E76-ON65256D51.002D4D3D@hss.hns.com>
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 26/06/2003
 01:46:13 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Subject: [Sigtran] M3UA MIB Draft05: Loadsharing on CIC ,SSN
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>





Hi....

I had a query related to the M3UA MIB draft 05.
Both m3uaSpLshMethod OBJECT-TYPE and  m3uaStreamLshMethod OBJECT-TYPE
mention CIC and SSN as basis of loadsharing
In my opinion, there is no point keeping CIC and SSN  as loadsharing basis
since this  would require  parsing  the data coming from the M3UA user.
Also references to these as loadsharing basis have been removed from RFC as
per Implementors guide 03.
So IMO these should be removed from the MIB also.


Thanks
Anjali
Hughes Software Systems



"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
(HSS) and is intended solely for the use of the individual to whom it is
addressed. It may contain  privileged or confidential information and
should not be circulated or used for any purpose other than for what it is
intended. If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient, you are
notified that you are strictly prohibited from using, copying, altering, or
disclosing the contents of this message. HSS accepts no responsibility for
loss or damage arising from the use of the information transmitted by this
email including damage from virus."


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



From exim@www1.ietf.org  Thu Jun 26 04:24:41 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11980
	for <sigtran-archive@odin.ietf.org>; Thu, 26 Jun 2003 04:24:40 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5Q8OC022203
	for sigtran-archive@odin.ietf.org; Thu, 26 Jun 2003 04:24:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VS3A-0005m1-68; Thu, 26 Jun 2003 04:24:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VRQg-0003Mj-Dv
	for sigtran@optimus.ietf.org; Thu, 26 Jun 2003 03:44:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11303
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 03:44:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VRQd-0006Q1-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 03:44:23 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[ZzyNz8DfGT5QSnIzrFz+fLh6aWSVrUfx])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VRQN-0006Pp-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 03:44:08 -0400
Received: from ns.pigworks.openss7.net (IDENT:THw+G2sZK3yhcMlepzRt6pUUpOnNwrMS@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5Q7hhX21525;
	Thu, 26 Jun 2003 01:43:43 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5Q7hgY27452;
	Thu, 26 Jun 2003 01:43:42 -0600
Date: Thu, 26 Jun 2003 01:43:42 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
Cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030626014342.A27236@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>,
	Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C9C@eestqnt105.es.eu.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C9C@eestqnt105.es.eu.ericsson.se>; from javier.pastor-balbas@ece.ericsson.se on Thu, Jun 26, 2003 at 09:12:20AM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Javier,

Your proposal for 3.15 is still unacceptable.

Please see comments below...

Javier Pastor-Balbas (ECE) wrote:                                                   (Thu, 26 Jun 2003 09:12:20)
> Brian, 
> 
> See my comments inline...
> 
> Cheers // Javier.
> 
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: martes, 24 de junio de 2003 23:25
> > To: Tolga Asveren
> > Cc: sigtran@ietf.org
> > Subject: Re: [Sigtran] Re: M3UA Notify message
> > 
> > 
> > Tolga,
> > 
> > Tolga Asveren wrote:                                          
> >                        (Tue, 24 Jun 2003 13:54:50)
> > > Brian,
> > > (some more repeating of my ideas about this topic ;-)
> > > )
> > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > wrote:
> > > > Tolga,
> > > > 
> > > > The RFC permits an SG to wait until sufficient
> > > > resources are active before directing traffic to
> > > > the ASP as you describe.
> > > > 
> > > > There is no reason, however, to require the SG
> > > > to wait.
> > > [TOLGA]Basically, what you are describing is "Let SG
> > > decide by itself, when to activate AS". In such a
> > > case, there should be a mechanism for SG to tell about
> > > this state change, which will make the ASPs to change
> > > their AS state accordingly -IMO, NTFY, as decribed in
> > > RFC can't be seen as serving this purpose, as it is
> > > not mandatory that ASPs update AS state based on
> > > that-. I also doubt, whether SG can dynamically decide
> > > when to activate AS, while it does not receive traffic
> > > for AS.
> > 
> > NTFY serves this purpose.  Whether your ASP
> > relies on it or not is up to the ASP designer.
> > You say your ASPs can coordinate 'n' without
> > relying on NTFY, so there is obviously no need
> > for any extra protocol to signal this.
> > 
> 
> It can not be up to the ASP designer !! Upon the activation of the first ASP the following scenario will happen:
> - SG thinks that AS is in AS-ACTIVE when the first ASP gets the ASP-ACTIVE state
> - ASP in ASP-ACTIVE state remains itself in an AS with AS-INACTIVE (less than n ASPs are ASP-ACTIVE and there is ASP-coordination)
> 
> There is not a common network view !! This MUST be fixed.

The RFC does not say that the ASP considers itself in the
AS-INACTIVE state until n ASPs are active.  Read again:

   For the n+k redundancy case, ASPs which are in that AS should
   coordinate among themselves the number of active ASPs in the AS, and
   should start sending traffic only after n ASPs are active.

The ASP considers itself in the ASP-ACTIVE state for the AS
(and may consider the AS active) as soon as it receives the
ASP Active Ack.

The ASP may consider the AS active as soon as it receives an
NTFY(AS-Active) regardless of whether it is ASP-INACTIVE for
the AS.

What the ASPs do is not start sending traffic until 'n' are
active.

> 
> 
> 
> > > > 
> > > > It appears to me that the RFC accomodates your
> > > > view, but also accomodates other views (AS
> > > > active on first ASP).  If your ASPs can indeed
> > > > coordinate 'n' amoung themselves, then it is
> > > > moot what the SG does.
> > > [TOLGA] IMO it is not irrelevant what SG does, if ASPs
> > > coordinate 'n' among themselves -not based on NTFY-.
> > > In such a case, it might happen that SG switches AS
> > > state to ACTIVE with less than n ACTIVE ASPs but ASPs
> > > will still wait for n ASPs to become ACTIVE and will
> > > have AS state INACTIVE. The result will be SG exposing
> > > AS as available to SS7 network, while in fact it was
> > > not ready on ASP side, this IMO shouldn't happen. 
> > 
> > Here's where your wrong.  Activating an AS and
> > traffic from the SS7 network are not correlated.
> > There is no requirement to direct traffic after
> > AS-ACTIVE.  When the SG indicates SS7 network
> > availability is a function of the NIF and there
> > are no requirements in the RFC in this regard.
> 
> Read the description of the AS-INACTIVE state. No traffic processing for the
> ASPs belonging to that AS.

Read the AS-ACTIVE state description.  It does not
say that the SG must direct any traffic.

DUNA(*) is a particular case in point.  Because an
AS is AS-ACTIVE does not mean that traffic is
directed at the ASPs.  So, I stand by my statement:
"Activating an AS and traffic from the SS7 network
are not correlated."

Also, the AS state at ASP and SG is not synchronized.  See
the warnings regarding message loss in Section 4.3.4.3.

> 
> > Also, even after the NIF decides to place the PC
> > or UP as available, there will be some
> > considerable time before traffic will start.
> > Distant signalling points and user parts will
> > have to time out on procedures before they will
> > restart traffic.  If an SG chooses to do this on
> > the first active ASP (getting a jump on restart
> > and knowing that it will take some time for
> > traffic to resume, and knowing that the APSs
> > will coordinate 'n' amoungst themselves anyway)
> > the is is allowed to do so by the RFC, but not
> > by the IG 3.15 proposal.
> > 
> So you'll be happy if we include a SHOULD instead of MUST for n ASPs in the
> transition form AS-INACTIVE to AS-ACTIVE...

It has to stay as MAY, as indicated in the current RFC.
SHOULD is unacceptable.

> 
> 
> > > > 
> > > > IG 3.15 attempts to force the optional procedure
> > > > in the SG, of waiting until sufficient resources
> > > > are active, to be a mandatory procedure.  (The
> > > > changing of MAY to MUST that I have always
> > > > disagreed with.)
> > > > 
> > > > What need is there to force your view on others
> > > > when, as you say, your ASPs can coordinate that
> > > > 'n' of them are active, anyway?
> > > [TOLGA]IMO, it is important that AS states are
> > > consistent on both sides(so the goal is not to put
> > > restrictions).
> > 
> > It is not so important.  Procedures are in place
> > to resynchronize state.  One of the most
> > important ones is the Notify procedure.  The SG
> > MUST notify ASPs of its perceived state for the
> > AS.  It is not an option.  The ASP can rely on
> > this because it is an absolute requirement.  (MUST)
> > 
> 
> But also the ASP will syncronize with the rest and wait for n ASPs in ASP-ACTIVE...
> The ASP can and cannot rely on it. This is only advisory. It is NOT either a MUST or a SHOULD to rely on NTFY.

It is a MUST that the SG sends Notify.  Therefore the ASP
can rely on it.  If the ASP cannot rely on it, why else
would it be a MUST to send it?

The MUST keyword is used where an action is required for
interoperability.  The SG MUST send Notify, so the ASP
can rely on it.  It is that simple.

If the ASP desginer chooses to ignore the Notifications
that the SG is required to send, she does so at her own
peril.

> 
> > > Secondly, if SG does not see AS as ACTIVE, there
> > > shouldn't be traffic directed for this AS to this SG.
> > 
> > The timing of traffic and AS activity is not
> > correlated or specified.  This is an NIF
> > function.  The SG cannot decide WHEN to resume
> > traffic, it is the remote signalling point that
> > decides WHEN to resume traffic.
> > 
> > By "direct traffic" the RFC means: do that NIF
> > thing to allow remote signalling points to
> > resume traffic at some time in the future.
> > 
> > > So, which traffic is SG supposed to withhold?
> > 
> > The SG does not withhold traffic, it withholds
> > the NTFY)(AS Active) if it waits to do that NIF
> > thing until it is confident that there are
> > sufficient ASP resources active to handle some
> > future load.  But this must remain optional.
> > The SG must be permitted to do that NIF thing on
> > the first active ASP (or 'm'th" or after a timeout) or
> > whenever it deems necessary after the first
> > active ASP.  And this cannot be mandated as 'n'.
> > 
> > > Initially SG should see AS as ACTIVE -before there was
> > > any traffic-, and this IMO can be decided only based
> > > on number of ACTIVE ASPs -where this number can be
> > > also 1 of course-.
> > 
> > No. The SG can do that NIF thing in anticipation
> > of 'n' ASPs being active because it has the
> > knowledge that 'n' will become active because
> > the ASPs SHOULD coordinate that 'n' are active.
> > 
> This is not stated in the RFC. 

That is why the SG is allowed to do so.  Because the
RFC neither forbids nor recommends against it.

> 
> > There is no problem with the existing RFC.
> > 
> > Mandating 'n' is unacceptable.
> > 
> RFC does it as per section 1.4.4.1

There are no requirements in section 1.4.4.1.

> 
> > I will ask you once more the question that you
> > have neglected to answer:
> > 
> > What bad thing will happen if the SG activates
> > (does that NIF thing) on the first ASP and the ASPs
> > wait until 'n'?
> > 
> 
> Answer:
> - Lack of synchronization among the two parts: ASPs and SGPs

Lack of synchronization already (intentionally) exists in
the protocol.  See the comments regarding message loss in
4.3.4.3, and particularly:

   At the ASP, the ASP Active Ack message received is not acknowledged.
   Layer Management is informed with an M-ASP_ACTIVE confirm primitive.
   It is possible for the ASP to receive Data message(s) before the ASP
   Active Ack message as the ASP Active Ack and Data messages from an SG
   or IPSP may be sent on different SCTP streams.  Message loss is
   possible as the ASP does not consider itself in the ASP-ACTIVE state
   until reception of the ASP Active Ack message.


> - Traffic Loss if the SS7 network start sending traffic before "n" ASPs know the AS is ACTIVE

What traffic loss?  Give an example.

> 
> Which is not tolerable in carrier-grade networks with availability requirements of 99.9999%

Performance requirements are outside the scope of the RFC.

(M3UA cannot even meet MTP3 performance requirements with
IETF recommended SCTP parameters, not M3UA proceedures.)

> 
> > Quite frankly there is no bad thing that will
> > happen and therefore all interoperability needs
> > are met by the existing RFC.
> 
> 
> Your interpretation of the RFC seems to be biased since the RFC also
> includes statements as 1.4.4.1, the AS-INACTIVE definition or examples for
> n>1. 

Section 1.4.4.1, quoted here for others, says:

   The failover model supports an "n+k" redundancy model, where "n" ASPs
   is the minimum number of redundant ASPs required to handle traffic
   and "k" ASPs are available to take over for a failed or unavailable
   ASP.

There are no requirements in this section whatsoever.  It is introductory.
Also, we agreed by concensus that the "traffic" referred to here is
"maximum engineered load".

--brian

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

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



From exim@www1.ietf.org  Thu Jun 26 05:40:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13696
	for <sigtran-archive@odin.ietf.org>; Thu, 26 Jun 2003 05:40:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5Q9e2q18123
	for sigtran-archive@odin.ietf.org; Thu, 26 Jun 2003 05:40:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VTEW-0004iC-Tf; Thu, 26 Jun 2003 05:40:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VTED-0004hb-Gr
	for sigtran@optimus.ietf.org; Thu, 26 Jun 2003 05:39:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13673
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 05:39:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VTDv-0006z2-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 05:39:23 -0400
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VTDk-0006yx-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 05:39:12 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h5Q9cMwA002238
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 04:38:23 -0500 (CDT)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h5Q9bc1C023222
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 04:37:38 -0500 (CDT)
Date: Thu, 26 Jun 2003 04:37:38 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
In-Reply-To: <20030626014342.A27236@openss7.org>
Message-ID: <Pine.SOL.4.10.10306260420160.15012-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


My understanding is, 'n' is just an operator configurable parameter.
When n=1, it sounds to activate an AS as soon as at least one ASP goes
to ACTIVE state, when n=2 , it sounds to activate an AS as soon as 
minimum two ASPs go to ACTIVE state.I think the concept is followed in
the conventional SS7 network, in order to make a particular route as 
unrestricted the operator has an option to describe 'how many links
to be in active state', this is absolutely a configurable parameter,
in order to make a particular route as unrestricted if '# of links
to be in active state' says 3, it is a wise idea to make that route as
unrestricted after 3 links go to active state.  In some very rare 
cases originating node may be sending a warning ss7 message to 
destination node with single active link to make that route as 
unrestricted.

Keeping section 3.15 holds good.

--Samuel

  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******



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



From exim@www1.ietf.org  Thu Jun 26 07:08:27 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15307
	for <sigtran-archive@odin.ietf.org>; Thu, 26 Jun 2003 07:08:27 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5QB82Y13416
	for sigtran-archive@odin.ietf.org; Thu, 26 Jun 2003 07:08:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VUbh-0003U9-3l; Thu, 26 Jun 2003 07:08:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VUat-0003ES-GR
	for sigtran@optimus.ietf.org; Thu, 26 Jun 2003 07:07:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15189
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 07:06:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VUZm-0007RU-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 07:06:02 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[13jZTS9nthM9n3PmG+0L7RDO8xuGU9YT])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VUZW-0007RF-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 07:05:46 -0400
Received: from ns.pigworks.openss7.net (IDENT:ZgXMKZnrXhUOzQiqoXe99ZJnRzDHQBRZ@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5QB5LX24372;
	Thu, 26 Jun 2003 05:05:21 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5QB5LH00353;
	Thu, 26 Jun 2003 05:05:21 -0600
Date: Thu, 26 Jun 2003 05:05:20 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030626050520.A32756@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030626014342.A27236@openss7.org> <Pine.SOL.4.10.10306260420160.15012-100000@sun2594.ssd.usa.alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.4.10.10306260420160.15012-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Thu, Jun 26, 2003 at 04:37:38AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Samuel,

The SS7 network does not work the way you describe.  There is no concept
in SS7 of the "minimum number of links" before a route goes active.
A route is active with the first signalling link.

--brian

Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 26 Jun 2003 04:37:38)
> 
> My understanding is, 'n' is just an operator configurable parameter.
> When n=1, it sounds to activate an AS as soon as at least one ASP goes
> to ACTIVE state, when n=2 , it sounds to activate an AS as soon as 
> minimum two ASPs go to ACTIVE state.I think the concept is followed in
> the conventional SS7 network, in order to make a particular route as 
> unrestricted the operator has an option to describe 'how many links
> to be in active state', this is absolutely a configurable parameter,
> in order to make a particular route as unrestricted if '# of links
> to be in active state' says 3, it is a wise idea to make that route as
> unrestricted after 3 links go to active state.  In some very rare 
> cases originating node may be sending a warning ss7 message to 
> destination node with single active link to make that route as 
> unrestricted.
> 
> Keeping section 3.15 holds good.
> 
> --Samuel
> 
>   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> 
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Thu Jun 26 07:20:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15532
	for <sigtran-archive@odin.ietf.org>; Thu, 26 Jun 2003 07:20:31 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5QBK2S17047
	for sigtran-archive@odin.ietf.org; Thu, 26 Jun 2003 07:20:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VUnJ-0004Qq-R7; Thu, 26 Jun 2003 07:20:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VUmp-0004Pu-Gu
	for sigtran@optimus.ietf.org; Thu, 26 Jun 2003 07:19:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15512
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 07:19:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VUmo-0007WM-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 07:19:30 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[4Ye7I3JcyV7CjtX3LkKX4lrQTB6ouFFs])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VUmY-0007WJ-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 07:19:14 -0400
Received: from ns.pigworks.openss7.net (IDENT:qQiRXAiPemNV9Y2JVPRwADfQ3fJrZND8@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5QBJ3X24523;
	Thu, 26 Jun 2003 05:19:03 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5QBJ2F00513;
	Thu, 26 Jun 2003 05:19:02 -0600
Date: Thu, 26 Jun 2003 05:19:02 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
Cc: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030626051902.B32756@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>,
	Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C9D@eestqnt105.es.eu.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C01B65C9D@eestqnt105.es.eu.ericsson.se>; from javier.pastor-balbas@ece.ericsson.se on Thu, Jun 26, 2003 at 10:10:30AM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Javier,

Javier Pastor-Balbas (ECE) wrote:                                                   (Thu, 26 Jun 2003 10:10:30)
> 
> Brian, 
> 
> More comments on yours....
> 
> > -----Original Message-----
> > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > Sent: jueves, 26 de junio de 2003 9:44
> > To: Javier Pastor-Balbas (ECE)
> > Cc: Tolga Asveren; sigtran@ietf.org
> > Subject: Re: [Sigtran] Re: M3UA Notify message
> > 
> > 
> > Javier,
> > 
> > Your proposal for 3.15 is still unacceptable.
> > 
> > Please see comments below...
> > 
> > Javier Pastor-Balbas (ECE) wrote:                             
> >                       (Thu, 26 Jun 2003 09:12:20)
> > > Brian, 
> > > 
> > > See my comments inline...
> > > 
> > > Cheers // Javier.
> > > 
> > > > -----Original Message-----
> > > > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> > > > Sent: martes, 24 de junio de 2003 23:25
> > > > To: Tolga Asveren
> > > > Cc: sigtran@ietf.org
> > > > Subject: Re: [Sigtran] Re: M3UA Notify message
> > > > 
> > > > 
> > > > Tolga,
> > > > 
> > > > Tolga Asveren wrote:                                          
> > > >                        (Tue, 24 Jun 2003 13:54:50)
> > > > > Brian,
> > > > > (some more repeating of my ideas about this topic ;-)
> > > > > )
> > > > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > > > wrote:
> > > > > > Tolga,
> > > > > > 
> > > > > > The RFC permits an SG to wait until sufficient
> > > > > > resources are active before directing traffic to
> > > > > > the ASP as you describe.
> > > > > > 
> > > > > > There is no reason, however, to require the SG
> > > > > > to wait.
> > > > > [TOLGA]Basically, what you are describing is "Let SG
> > > > > decide by itself, when to activate AS". In such a
> > > > > case, there should be a mechanism for SG to tell about
> > > > > this state change, which will make the ASPs to change
> > > > > their AS state accordingly -IMO, NTFY, as decribed in
> > > > > RFC can't be seen as serving this purpose, as it is
> > > > > not mandatory that ASPs update AS state based on
> > > > > that-. I also doubt, whether SG can dynamically decide
> > > > > when to activate AS, while it does not receive traffic
> > > > > for AS.
> > > > 
> > > > NTFY serves this purpose.  Whether your ASP
> > > > relies on it or not is up to the ASP designer.
> > > > You say your ASPs can coordinate 'n' without
> > > > relying on NTFY, so there is obviously no need
> > > > for any extra protocol to signal this.
> > > > 
> > > 
> > > It can not be up to the ASP designer !! Upon the activation 
> > of the first ASP the following scenario will happen:
> > > - SG thinks that AS is in AS-ACTIVE when the first ASP gets 
> > the ASP-ACTIVE state
> > > - ASP in ASP-ACTIVE state remains itself in an AS with 
> > AS-INACTIVE (less than n ASPs are ASP-ACTIVE and there is 
> > ASP-coordination)
> > > 
> > > There is not a common network view !! This MUST be fixed.
> > 
> > The RFC does not say that the ASP considers itself in the
> > AS-INACTIVE state until n ASPs are active.  Read again:
> > 
> >    For the n+k redundancy case, ASPs which are in that AS should
> >    coordinate among themselves the number of active ASPs in 
> > the AS, and
> >    should start sending traffic only after n ASPs are active.
> > 
> > The ASP considers itself in the ASP-ACTIVE state for the AS
> > (and may consider the AS active) as soon as it receives the
> > ASP Active Ack.
> > 
> > The ASP may consider the AS active as soon as it receives an
> > NTFY(AS-Active) regardless of whether it is ASP-INACTIVE for
> > the AS.
> > 
> > What the ASPs do is not start sending traffic until 'n' are
> > active.
> > 
> > > 
> > > 
> > > 
> > > > > > 
> > > > > > It appears to me that the RFC accomodates your
> > > > > > view, but also accomodates other views (AS
> > > > > > active on first ASP).  If your ASPs can indeed
> > > > > > coordinate 'n' amoung themselves, then it is
> > > > > > moot what the SG does.
> > > > > [TOLGA] IMO it is not irrelevant what SG does, if ASPs
> > > > > coordinate 'n' among themselves -not based on NTFY-.
> > > > > In such a case, it might happen that SG switches AS
> > > > > state to ACTIVE with less than n ACTIVE ASPs but ASPs
> > > > > will still wait for n ASPs to become ACTIVE and will
> > > > > have AS state INACTIVE. The result will be SG exposing
> > > > > AS as available to SS7 network, while in fact it was
> > > > > not ready on ASP side, this IMO shouldn't happen. 
> > > > 
> > > > Here's where your wrong.  Activating an AS and
> > > > traffic from the SS7 network are not correlated.
> > > > There is no requirement to direct traffic after
> > > > AS-ACTIVE.  When the SG indicates SS7 network
> > > > availability is a function of the NIF and there
> > > > are no requirements in the RFC in this regard.
> > > 
> > > Read the description of the AS-INACTIVE state. No traffic 
> > processing for the
> > > ASPs belonging to that AS.
> > 
> > Read the AS-ACTIVE state description.  It does not
> > say that the SG must direct any traffic.
> > 
> It says "no application traffic is active". So there must not be any
> application traffic with the AS, which correponds with AS-INACTIVE.
> 
> > DUNA(*) is a particular case in point.  Because an
> > AS is AS-ACTIVE does not mean that traffic is
> > directed at the ASPs.  So, I stand by my statement:
> > "Activating an AS and traffic from the SS7 network
> > are not correlated."
> > 
> > Also, the AS state at ASP and SG is not synchronized.  See
> > the warnings regarding message loss in Section 4.3.4.3.
> 
> 
> These are regarding the delay on reception of the ASPAC-ACK, that will be
> added to the total traffic loss in there exists a different perception of
> the AS state in the network. 

I still stand by my statement.

> > 
> > > 
> > > > Also, even after the NIF decides to place the PC
> > > > or UP as available, there will be some
> > > > considerable time before traffic will start.
> > > > Distant signalling points and user parts will
> > > > have to time out on procedures before they will
> > > > restart traffic.  If an SG chooses to do this on
> > > > the first active ASP (getting a jump on restart
> > > > and knowing that it will take some time for
> > > > traffic to resume, and knowing that the APSs
> > > > will coordinate 'n' amoungst themselves anyway)
> > > > the is is allowed to do so by the RFC, but not
> > > > by the IG 3.15 proposal.
> > > > 
> > > So you'll be happy if we include a SHOULD instead of MUST 
> > for n ASPs in the
> > > transition form AS-INACTIVE to AS-ACTIVE...
> > 
> > It has to stay as MAY, as indicated in the current RFC.
> > SHOULD is unacceptable.
> > 
> There is no explicit "MAY" in the current RFC...

This MAY:

   An SGP or IPSP, upon reception of an ASP Active message for the first
   ASP in a Loadshare AS, MAY choose not to direct traffic to a newly
   active ASP until it determines that there are sufficient resources to
   handle the expected load (e.g., until there are "n" ASPs in state
   ASP-ACTIVE in the AS).  In this case, the SGP or IPSP SHOULD withhold
   the Notify (AS-ACTIVE) until there are sufficient resources.

And this MAY:

   An SGP or IPSP, upon reception of an ASP Active message for the first
   ASP in a Broadcast AS, MAY choose not to direct traffic to a newly
   active ASP until it determines that there are sufficient resources to
   handle the expected load (e.g., until there are "n" ASPs in state
   ASP-ACTIVE in the AS).  In this case, the SGP or IPSP SHOULD withhold
   the Notify (AS-ACTIVE) until there are sufficient resources.

> 
> > > 
> > > 
> > > > > > 
> > > > > > IG 3.15 attempts to force the optional procedure
> > > > > > in the SG, of waiting until sufficient resources
> > > > > > are active, to be a mandatory procedure.  (The
> > > > > > changing of MAY to MUST that I have always
> > > > > > disagreed with.)
> > > > > > 
> > > > > > What need is there to force your view on others
> > > > > > when, as you say, your ASPs can coordinate that
> > > > > > 'n' of them are active, anyway?
> > > > > [TOLGA]IMO, it is important that AS states are
> > > > > consistent on both sides(so the goal is not to put
> > > > > restrictions).
> > > > 
> > > > It is not so important.  Procedures are in place
> > > > to resynchronize state.  One of the most
> > > > important ones is the Notify procedure.  The SG
> > > > MUST notify ASPs of its perceived state for the
> > > > AS.  It is not an option.  The ASP can rely on
> > > > this because it is an absolute requirement.  (MUST)
> > > > 
> > > 
> > > But also the ASP will syncronize with the rest and wait for 
> > n ASPs in ASP-ACTIVE...
> > > The ASP can and cannot rely on it. This is only advisory. 
> > It is NOT either a MUST or a SHOULD to rely on NTFY.
> > 
> > It is a MUST that the SG sends Notify.  Therefore the ASP
> > can rely on it.  If the ASP cannot rely on it, why else
> > would it be a MUST to send it?
> 
> I meant "may or may not". There is nothing in the RFC saying that the ASP
> MUST take into account the NTFY or trigger any action from its reception.
> Although it is a good test that both network nodes have the same state
> understanding.

So the ASP can rely on it.

> > 
> > The MUST keyword is used where an action is required for
> > interoperability.  The SG MUST send Notify, so the ASP
> > can rely on it.  It is that simple.
> > 
> As I said it can rely, but it may not...

And ignore it at its own peril...

> 
> > If the ASP desginer chooses to ignore the Notifications
> > that the SG is required to send, she does so at her own
> > peril.
> > 
> > > 
> > > > > Secondly, if SG does not see AS as ACTIVE, there
> > > > > shouldn't be traffic directed for this AS to this SG.
> > > > 
> > > > The timing of traffic and AS activity is not
> > > > correlated or specified.  This is an NIF
> > > > function.  The SG cannot decide WHEN to resume
> > > > traffic, it is the remote signalling point that
> > > > decides WHEN to resume traffic.
> > > > 
> > > > By "direct traffic" the RFC means: do that NIF
> > > > thing to allow remote signalling points to
> > > > resume traffic at some time in the future.
> > > > 
> > > > > So, which traffic is SG supposed to withhold?
> > > > 
> > > > The SG does not withhold traffic, it withholds
> > > > the NTFY)(AS Active) if it waits to do that NIF
> > > > thing until it is confident that there are
> > > > sufficient ASP resources active to handle some
> > > > future load.  But this must remain optional.
> > > > The SG must be permitted to do that NIF thing on
> > > > the first active ASP (or 'm'th" or after a timeout) or
> > > > whenever it deems necessary after the first
> > > > active ASP.  And this cannot be mandated as 'n'.
> > > > 
> > > > > Initially SG should see AS as ACTIVE -before there was
> > > > > any traffic-, and this IMO can be decided only based
> > > > > on number of ACTIVE ASPs -where this number can be
> > > > > also 1 of course-.
> > > > 
> > > > No. The SG can do that NIF thing in anticipation
> > > > of 'n' ASPs being active because it has the
> > > > knowledge that 'n' will become active because
> > > > the ASPs SHOULD coordinate that 'n' are active.
> > > > 
> > > This is not stated in the RFC. 
> > 
> > That is why the SG is allowed to do so.  Because the
> > RFC neither forbids nor recommends against it.
> > 
> Since the RFC does not state a word about it. It is an implementation choice
> and not a standard way of working.

But currently permitted.  Your proposal would remove this.
It is unacceptable for that and other reasons.

> 
> > > 
> > > > There is no problem with the existing RFC.
> > > > 
> > > > Mandating 'n' is unacceptable.
> > > > 
> > > RFC does it as per section 1.4.4.1
> > 
> > There are no requirements in section 1.4.4.1.
> > 
> There are not requirements, there are DEFINITIONS: what things are. These
> are the basis for the protocol explanation.

These are nor definitions.  They are simple statements.
Read 1.4.4.1 again.  Where is there a definition?

> 
> > > 
> > > > I will ask you once more the question that you
> > > > have neglected to answer:
> > > > 
> > > > What bad thing will happen if the SG activates
> > > > (does that NIF thing) on the first ASP and the ASPs
> > > > wait until 'n'?
> > > > 
> > > 
> > > Answer:
> > > - Lack of synchronization among the two parts: ASPs and SGPs
> > 
> > Lack of synchronization already (intentionally) exists in
> > the protocol.  See the comments regarding message loss in
> > 4.3.4.3, and particularly:
> > 
> >    At the ASP, the ASP Active Ack message received is not 
> > acknowledged.
> >    Layer Management is informed with an M-ASP_ACTIVE confirm 
> > primitive.
> >    It is possible for the ASP to receive Data message(s) 
> > before the ASP
> >    Active Ack message as the ASP Active Ack and Data messages 
> > from an SG
> >    or IPSP may be sent on different SCTP streams.  Message loss is
> >    possible as the ASP does not consider itself in the 
> > ASP-ACTIVE state
> >    until reception of the ASP Active Ack message.
> > 
> 
> This is due to the network latency, what is unavoidable. But not due to
> different state view !! The latter should be avoided.

It is a difference in state view: the SG views the ASP as
active for the AS because it has send ASP Active Ack, the
ASP does not view itself as active yet because it has not
yet received ASP Active Ack.

I don't see much difference between this and ASPs coordinating
that 'n' of them go active within a short interval.

> > 
> > > - Traffic Loss if the SS7 network start sending traffic 
> > before "n" ASPs know the AS is ACTIVE
> > 
> > What traffic loss?  Give an example.
> 
> SS7 nodes start sending traffic to the AS and both the AS has not still "n"
> ASPs in ASP-ACTIVE and the SG buffer is full.

Where does it say that the ASP does not receive traffic when
it is active for the AS?  It says in the RFC that the ASP
will not send traffic, not that it will not receive it.

> 
> > 
> > > 
> > > Which is not tolerable in carrier-grade networks with 
> > availability requirements of 99.9999%
> > 
> > Performance requirements are outside the scope of the RFC.
> > 
> > (M3UA cannot even meet MTP3 performance requirements with
> > IETF recommended SCTP parameters, not M3UA proceedures.)
> 
> As you probably know although SCTP was first thought for signaling traffic,
> in its later steps it was consider to be general purpose. Hope you don't use
> such parameters for signaling traffic....  

But that is what the SCTP applicability statement says, particularly
with regards to SIGTRAN, that the SCTP [RFC 2960] recommended
parameters are to be followed.  In particular, RTOs max's of 60 seconds
and RTO mins of 1 second.

Are you recommending that the RFC recommendations be violated?

> 
> > 
> > > 
> > > > Quite frankly there is no bad thing that will
> > > > happen and therefore all interoperability needs
> > > > are met by the existing RFC.
> > > 
> > > 
> > > Your interpretation of the RFC seems to be biased since the RFC also
> > > includes statements as 1.4.4.1, the AS-INACTIVE definition 
> > or examples for
> > > n>1. 
> > 
> > Section 1.4.4.1, quoted here for others, says:
> > 
> >    The failover model supports an "n+k" redundancy model, 
> > where "n" ASPs
> >    is the minimum number of redundant ASPs required to handle traffic
> >    and "k" ASPs are available to take over for a failed or unavailable
> >    ASP.
> > 
> > There are no requirements in this section whatsoever.  It is 
> > introductory.
> 
> As I said before, they are definitions that set up the basis for the
> protocol.

> 
> > Also, we agreed by concensus that the "traffic" referred to here is
> > "maximum engineered load".
> 
> Maximum engineered load is not peak load, it is the load you are expected to
> be able to offer 99.9999% of the time... And at least at the beginning you
> should get it before activate traffic.

So wrong: we should be glad you have not engineered any networks.

--brian

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

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



From exim@www1.ietf.org  Thu Jun 26 07:26:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15642
	for <sigtran-archive@odin.ietf.org>; Thu, 26 Jun 2003 07:26:31 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5QBQ2718209
	for sigtran-archive@odin.ietf.org; Thu, 26 Jun 2003 07:26:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VUt7-0004jE-4u; Thu, 26 Jun 2003 07:26:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VUsn-0004ii-RM
	for sigtran@optimus.ietf.org; Thu, 26 Jun 2003 07:25:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15620
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 07:25:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VUsn-0007Xo-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 07:25:41 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VUsc-0007X7-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 07:25:30 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h5QBOOB3008349
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 06:24:24 -0500 (CDT)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h5QBNe1C019354
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 06:23:40 -0500 (CDT)
Date: Thu, 26 Jun 2003 06:23:40 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
In-Reply-To: <20030626050520.A32756@openss7.org>
Message-ID: <Pine.SOL.4.10.10306260612510.15012-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


Brian,
  Again i am saying it is left to the decision of operator.

  When node A is sending messages to node B, in this case, if operator 
  decides one link is not sufficient to carry messages from node A to
  node B, operator can say 'min 2 links' are required between node
  A and node B.Logically it sounds good also.
 
 --Sam  
 
  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******

On Thu, 26 Jun 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> The SS7 network does not work the way you describe.  There is no concept
> in SS7 of the "minimum number of links" before a route goes active.
> A route is active with the first signalling link.
> 
> --brian
> 
> Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 26 Jun 2003 04:37:38)
> > 
> > My understanding is, 'n' is just an operator configurable parameter.
> > When n=1, it sounds to activate an AS as soon as at least one ASP goes
> > to ACTIVE state, when n=2 , it sounds to activate an AS as soon as 
> > minimum two ASPs go to ACTIVE state.I think the concept is followed in
> > the conventional SS7 network, in order to make a particular route as 
> > unrestricted the operator has an option to describe 'how many links
> > to be in active state', this is absolutely a configurable parameter,
> > in order to make a particular route as unrestricted if '# of links
> > to be in active state' says 3, it is a wise idea to make that route as
> > unrestricted after 3 links go to active state.  In some very rare 
> > cases originating node may be sending a warning ss7 message to 
> > destination node with single active link to make that route as 
> > unrestricted.
> > 
> > Keeping section 3.15 holds good.
> > 
> > --Samuel
> > 
> >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> > 
> > 
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 


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



From exim@www1.ietf.org  Thu Jun 26 07:47:32 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15992
	for <sigtran-archive@odin.ietf.org>; Thu, 26 Jun 2003 07:47:32 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5QBl3x24673
	for sigtran-archive@odin.ietf.org; Thu, 26 Jun 2003 07:47:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VVDQ-0006Pf-OY; Thu, 26 Jun 2003 07:47:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VVCc-0006PA-Bp
	for sigtran@optimus.ietf.org; Thu, 26 Jun 2003 07:46:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15938
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 07:45:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VVBY-0007cj-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 07:45:04 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[OV50LowajGW9kjMR4g27NGHgEkE1AqSg])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VVBI-0007cg-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 07:44:48 -0400
Received: from ns.pigworks.openss7.net (IDENT:xYiXSI4T4DU42A3//FgYETDUjr9kpvIh@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5QBibX24891;
	Thu, 26 Jun 2003 05:44:37 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5QBibn00925;
	Thu, 26 Jun 2003 05:44:37 -0600
Date: Thu, 26 Jun 2003 05:44:37 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030626054437.A827@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030626050520.A32756@openss7.org> <Pine.SOL.4.10.10306260612510.15012-100000@sun2594.ssd.usa.alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.4.10.10306260612510.15012-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Thu, Jun 26, 2003 at 06:23:40AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Samuel,

What you describe is not provided for in the standards and is
thus, forbidden.

Point to where you believe that this is explicitly permitted
in the MTP standards.

--brian

Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 26 Jun 2003 06:23:40)
> 
> Brian,
>   Again i am saying it is left to the decision of operator.
> 
>   When node A is sending messages to node B, in this case, if operator 
>   decides one link is not sufficient to carry messages from node A to
>   node B, operator can say 'min 2 links' are required between node
>   A and node B.Logically it sounds good also.
>  
>  --Sam  
>  
>   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> 
> On Thu, 26 Jun 2003, Brian F. G. Bidulock wrote:
> 
> > Samuel,
> > 
> > The SS7 network does not work the way you describe.  There is no concept
> > in SS7 of the "minimum number of links" before a route goes active.
> > A route is active with the first signalling link.
> > 
> > --brian
> > 
> > Samuel Dur D. Jeyaseelan wrote:                                                     (Thu, 26 Jun 2003 04:37:38)
> > > 
> > > My understanding is, 'n' is just an operator configurable parameter.
> > > When n=1, it sounds to activate an AS as soon as at least one ASP goes
> > > to ACTIVE state, when n=2 , it sounds to activate an AS as soon as 
> > > minimum two ASPs go to ACTIVE state.I think the concept is followed in
> > > the conventional SS7 network, in order to make a particular route as 
> > > unrestricted the operator has an option to describe 'how many links
> > > to be in active state', this is absolutely a configurable parameter,
> > > in order to make a particular route as unrestricted if '# of links
> > > to be in active state' says 3, it is a wise idea to make that route as
> > > unrestricted after 3 links go to active state.  In some very rare 
> > > cases originating node may be sending a warning ss7 message to 
> > > destination node with single active link to make that route as 
> > > unrestricted.
> > > 
> > > Keeping section 3.15 holds good.
> > > 
> > > --Samuel
> > > 
> > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
> > >   1000 Coit Road, Plano, Texas 75075
> > >   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> > 
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Thu Jun 26 07:50:30 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16049
	for <sigtran-archive@odin.ietf.org>; Thu, 26 Jun 2003 07:50:30 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5QBo1625642
	for sigtran-archive@odin.ietf.org; Thu, 26 Jun 2003 07:50:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VVGL-0006fT-FL; Thu, 26 Jun 2003 07:50:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VVFs-0006f3-9s
	for sigtran@optimus.ietf.org; Thu, 26 Jun 2003 07:49:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16029
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 07:49:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VVFr-0007dQ-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 07:49:31 -0400
Received: from web12801.mail.yahoo.com ([216.136.174.36])
	by ietf-mx with smtp (Exim 4.12)
	id 19VVFg-0007dL-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 07:49:20 -0400
Message-ID: <20030626114859.52034.qmail@web12801.mail.yahoo.com>
Received: from [208.255.120.2] by web12801.mail.yahoo.com via HTTP; Thu, 26 Jun 2003 04:48:59 PDT
Date: Thu, 26 Jun 2003 04:48:59 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] Re: M3UA Notify message
To: sigtran@ietf.org
In-Reply-To: <20030626051902.B32756@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,

IMO, one of the key points is that assuming that an
ASP SHOULD rely on NTFY from SGP or not. If there is
such a need, this has to be in RFC/IG with a "SHOULD"
-like everything else necessary is there with a
"SHOULD" or "MUST". Otherwise one can fill the RFC
with "MAY"s and can argue "Well, it is implementors
responsibility to be clever enough to decide which of
those MAY should have been in fact a SHOULD".

I also don't see waiting for n ACTIVE ASPs as a
restriction. It is the same like not putting AS to
ACTIVE without an ACTIVE ASP for n=1 case. In my
opinion based on definition of AS-ACTIVE and
AS-INACTIVE states it is clear that if AS is not
ACTIVE, no application traffic should run to/from it.

IMO, there is also a correlation between AS state and
traffic destined to this AS from SS7 nodes. Without AS
is exposed as available, there won't be traffic for
this AS -or better said should not be-. The view of AS
as seen from SS7 nodes (PC reachability or user part
availability) should reflect the real situation IMO.

If your view is that the first ASPAC is the sign that
ASPs have coordinated n among themselves and in a very
short time, necessary number of ASPs is going to be
ACTIVE, then IMO there is no need to care about n on
SGP side. Just always switch to AS-ACTIVE with the
first ASPAC and leave the coordination totally to
ASPs.
I also don't think it is a good idea to give the
responsibility of a dynamic decision to activate AS to
SG, which is not aware of the load on ASPs and which
even does not receive traffic from SS7 nodes for it.

     Tolga
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Javier,
> 
> Javier Pastor-Balbas (ECE) wrote:                   
>                                (Thu, 26 Jun 2003
> 10:10:30)
> > 
> > Brian, 
> > 
> > More comments on yours....
> > 
> > > -----Original Message-----
> > > From: Brian F. G. Bidulock
> [mailto:bidulock@openss7.org]
> > > Sent: jueves, 26 de junio de 2003 9:44
> > > To: Javier Pastor-Balbas (ECE)
> > > Cc: Tolga Asveren; sigtran@ietf.org
> > > Subject: Re: [Sigtran] Re: M3UA Notify message
> > > 
> > > 
> > > Javier,
> > > 
> > > Your proposal for 3.15 is still unacceptable.
> > > 
> > > Please see comments below...
> > > 
> > > Javier Pastor-Balbas (ECE) wrote:               
>              
> > >                       (Thu, 26 Jun 2003
> 09:12:20)
> > > > Brian, 
> > > > 
> > > > See my comments inline...
> > > > 
> > > > Cheers // Javier.
> > > > 
> > > > > -----Original Message-----
> > > > > From: Brian F. G. Bidulock
> [mailto:bidulock@openss7.org]
> > > > > Sent: martes, 24 de junio de 2003 23:25
> > > > > To: Tolga Asveren
> > > > > Cc: sigtran@ietf.org
> > > > > Subject: Re: [Sigtran] Re: M3UA Notify
> message
> > > > > 
> > > > > 
> > > > > Tolga,
> > > > > 
> > > > > Tolga Asveren wrote:                        
>                  
> > > > >                        (Tue, 24 Jun 2003
> 13:54:50)
> > > > > > Brian,
> > > > > > (some more repeating of my ideas about
> this topic ;-)
> > > > > > )
> > > > > > --- "Brian F. G. Bidulock"
> <bidulock@openss7.org>
> > > > > > wrote:
> > > > > > > Tolga,
> > > > > > > 
> > > > > > > The RFC permits an SG to wait until
> sufficient
> > > > > > > resources are active before directing
> traffic to
> > > > > > > the ASP as you describe.
> > > > > > > 
> > > > > > > There is no reason, however, to require
> the SG
> > > > > > > to wait.
> > > > > > [TOLGA]Basically, what you are describing
> is "Let SG
> > > > > > decide by itself, when to activate AS". In
> such a
> > > > > > case, there should be a mechanism for SG
> to tell about
> > > > > > this state change, which will make the
> ASPs to change
> > > > > > their AS state accordingly -IMO, NTFY, as
> decribed in
> > > > > > RFC can't be seen as serving this purpose,
> as it is
> > > > > > not mandatory that ASPs update AS state
> based on
> > > > > > that-. I also doubt, whether SG can
> dynamically decide
> > > > > > when to activate AS, while it does not
> receive traffic
> > > > > > for AS.
> > > > > 
> > > > > NTFY serves this purpose.  Whether your ASP
> > > > > relies on it or not is up to the ASP
> designer.
> > > > > You say your ASPs can coordinate 'n' without
> > > > > relying on NTFY, so there is obviously no
> need
> > > > > for any extra protocol to signal this.
> > > > > 
> > > > 
> > > > It can not be up to the ASP designer !! Upon
> the activation 
> > > of the first ASP the following scenario will
> happen:
> > > > - SG thinks that AS is in AS-ACTIVE when the
> first ASP gets 
> > > the ASP-ACTIVE state
> > > > - ASP in ASP-ACTIVE state remains itself in an
> AS with 
> > > AS-INACTIVE (less than n ASPs are ASP-ACTIVE and
> there is 
> > > ASP-coordination)
> > > > 
> > > > There is not a common network view !! This
> MUST be fixed.
> > > 
> > > The RFC does not say that the ASP considers
> itself in the
> > > AS-INACTIVE state until n ASPs are active.  Read
> again:
> > > 
> > >    For the n+k redundancy case, ASPs which are
> in that AS should
> > >    coordinate among themselves the number of
> active ASPs in 
> > > the AS, and
> > >    should start sending traffic only after n
> ASPs are active.
> > > 
> > > The ASP considers itself in the ASP-ACTIVE state
> for the AS
> > > (and may consider the AS active) as soon as it
> receives the
> > > ASP Active Ack.
> > > 
> > > The ASP may consider the AS active as soon as it
> receives an
> > > NTFY(AS-Active) regardless of whether it is
> ASP-INACTIVE for
> > > the AS.
> > > 
> > > What the ASPs do is not start sending traffic
> until 'n' are
> > > active.


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

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



From exim@www1.ietf.org  Thu Jun 26 11:20:35 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01780
	for <sigtran-archive@odin.ietf.org>; Thu, 26 Jun 2003 11:20:35 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5QFK7x05203
	for sigtran-archive@odin.ietf.org; Thu, 26 Jun 2003 11:20:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VYXZ-0001K8-ID; Thu, 26 Jun 2003 11:20:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VYXE-0001Gj-RV
	for sigtran@optimus.ietf.org; Thu, 26 Jun 2003 11:19:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01504
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 11:19:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VYXD-0002ZF-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 11:19:39 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[o5msrTuqudNWkc0PzOxHbS3x5oMBfcbZ])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VYWp-0002Z2-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 11:19:17 -0400
Received: from ns.pigworks.openss7.net (IDENT:C9HixNACiEBXs4lUStxYa55R86xuG1Dz@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5QFIjX27708;
	Thu, 26 Jun 2003 09:18:45 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5QFIjb04529;
	Thu, 26 Jun 2003 09:18:45 -0600
Date: Thu, 26 Jun 2003 09:18:45 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030626091845.A939@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030626051902.B32756@openss7.org> <20030626114859.52034.qmail@web12801.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030626114859.52034.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Thu, Jun 26, 2003 at 04:48:59AM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

Tolga Asveren wrote:                                                                 (Thu, 26 Jun 2003 04:48:59)
> Brian,
> 
> IMO, one of the key points is that assuming that an
> ASP SHOULD rely on NTFY from SGP or not. If there is
> such a need, this has to be in RFC/IG with a "SHOULD"
> -like everything else necessary is there with a
> "SHOULD" or "MUST". Otherwise one can fill the RFC
> with "MAY"s and can argue "Well, it is implementors
> responsibility to be clever enough to decide which of
> those MAY should have been in fact a SHOULD".

I am not saying that an ASP should rely on Notify.
I am saying that it can.  That is, the ASP can meet
the requirement that it SHOULD coordinate that 'n'
ASPs are active regardles of what the SG does, and
that the ASP can know when the SG activates the AS
to synchronize state as much as it cares to.

> 
> I also don't see waiting for n ACTIVE ASPs as a
> restriction.

I do.

> It is the same like not putting AS to
> ACTIVE without an ACTIVE ASP for n=1 case. In my
> opinion based on definition of AS-ACTIVE and
> AS-INACTIVE states it is clear that if AS is not
> ACTIVE, no application traffic should run to/from it.
> 
> IMO, there is also a correlation between AS state and
> traffic destined to this AS from SS7 nodes. Without AS
> is exposed as available, there won't be traffic for
> this AS -or better said should not be-. The view of AS
> as seen from SS7 nodes (PC reachability or user part
> availability) should reflect the real situation IMO.

There is no mechanism in SS7 to inform the SS7 network
that an AS (MTP-User) is active.  There is no UPA or UPT
message in MTP, just a UPU.

In the SS7 network every MTP-User can be exposed to
200-300% of its rated load.  The MTP-User is responsible
for user-part congestion avoidance and flow control.

> 
> If your view is that the first ASPAC is the sign that
> ASPs have coordinated n among themselves and in a very
> short time, necessary number of ASPs is going to be
> ACTIVE, then IMO there is no need to care about n on
> SGP side. Just always switch to AS-ACTIVE with the
> first ASPAC and leave the coordination totally to
> ASPs.
> I also don't think it is a good idea to give the
> responsibility of a dynamic decision to activate AS to
> SG, which is not aware of the load on ASPs and which
> even does not receive traffic from SS7 nodes for it.

For startup of an MTP-User, the only traffic that can
be received is user part test traffic: e.g. UPT or CVT
for ISUP, or SST for SCCP.  If the ASP does not respond
to these messages, no user-part traffic will flow.

In addition, the MTP-User has congestion avoidance
procedures at its disposal: e.g. ACL in REL for ISUP and
SSC for SCCP.  Because an ASP can always be exposed to
200-300% of its rated load, the ASP had better appropriately
use these procedures.

Therefore, is is the AS that is responsible for starting
traffic flow from the SS7 network to the AS (by responding
to UPT/CVT or SST) and not the responsibility of the SG
at all.  The SG merely starts passing messages to and from
the AS so that the AS can determine respond to these user
part flow control and test messages of its own accord.

No bad thing can happen from the SG starting traffic on
the first active ASP because the only traffic started is
user-part test traffic.  It is the responsibility of the
ASP to respond to test traffic (after 'n' are active) and
restart the user part traffic flow from other users in
the SS7 network.

Therefore, the SG can always start traffic on the first ASP
as provided for in the RFC.

The proposal to require the SG to wait remains unacceptable.

--brian

> 
>      Tolga
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Javier,
> > 
> > Javier Pastor-Balbas (ECE) wrote:                   
> >                                (Thu, 26 Jun 2003
> > 10:10:30)
> > > 
> > > Brian, 
> > > 
> > > More comments on yours....
> > > 
> > > > -----Original Message-----
> > > > From: Brian F. G. Bidulock
> > [mailto:bidulock@openss7.org]
> > > > Sent: jueves, 26 de junio de 2003 9:44
> > > > To: Javier Pastor-Balbas (ECE)
> > > > Cc: Tolga Asveren; sigtran@ietf.org
> > > > Subject: Re: [Sigtran] Re: M3UA Notify message
> > > > 
> > > > 
> > > > Javier,
> > > > 
> > > > Your proposal for 3.15 is still unacceptable.
> > > > 
> > > > Please see comments below...
> > > > 
> > > > Javier Pastor-Balbas (ECE) wrote:               
> >              
> > > >                       (Thu, 26 Jun 2003
> > 09:12:20)
> > > > > Brian, 
> > > > > 
> > > > > See my comments inline...
> > > > > 
> > > > > Cheers // Javier.
> > > > > 
> > > > > > -----Original Message-----
> > > > > > From: Brian F. G. Bidulock
> > [mailto:bidulock@openss7.org]
> > > > > > Sent: martes, 24 de junio de 2003 23:25
> > > > > > To: Tolga Asveren
> > > > > > Cc: sigtran@ietf.org
> > > > > > Subject: Re: [Sigtran] Re: M3UA Notify
> > message
> > > > > > 
> > > > > > 
> > > > > > Tolga,
> > > > > > 
> > > > > > Tolga Asveren wrote:                        
> >                  
> > > > > >                        (Tue, 24 Jun 2003
> > 13:54:50)
> > > > > > > Brian,
> > > > > > > (some more repeating of my ideas about
> > this topic ;-)
> > > > > > > )
> > > > > > > --- "Brian F. G. Bidulock"
> > <bidulock@openss7.org>
> > > > > > > wrote:
> > > > > > > > Tolga,
> > > > > > > > 
> > > > > > > > The RFC permits an SG to wait until
> > sufficient
> > > > > > > > resources are active before directing
> > traffic to
> > > > > > > > the ASP as you describe.
> > > > > > > > 
> > > > > > > > There is no reason, however, to require
> > the SG
> > > > > > > > to wait.
> > > > > > > [TOLGA]Basically, what you are describing
> > is "Let SG
> > > > > > > decide by itself, when to activate AS". In
> > such a
> > > > > > > case, there should be a mechanism for SG
> > to tell about
> > > > > > > this state change, which will make the
> > ASPs to change
> > > > > > > their AS state accordingly -IMO, NTFY, as
> > decribed in
> > > > > > > RFC can't be seen as serving this purpose,
> > as it is
> > > > > > > not mandatory that ASPs update AS state
> > based on
> > > > > > > that-. I also doubt, whether SG can
> > dynamically decide
> > > > > > > when to activate AS, while it does not
> > receive traffic
> > > > > > > for AS.
> > > > > > 
> > > > > > NTFY serves this purpose.  Whether your ASP
> > > > > > relies on it or not is up to the ASP
> > designer.
> > > > > > You say your ASPs can coordinate 'n' without
> > > > > > relying on NTFY, so there is obviously no
> > need
> > > > > > for any extra protocol to signal this.
> > > > > > 
> > > > > 
> > > > > It can not be up to the ASP designer !! Upon
> > the activation 
> > > > of the first ASP the following scenario will
> > happen:
> > > > > - SG thinks that AS is in AS-ACTIVE when the
> > first ASP gets 
> > > > the ASP-ACTIVE state
> > > > > - ASP in ASP-ACTIVE state remains itself in an
> > AS with 
> > > > AS-INACTIVE (less than n ASPs are ASP-ACTIVE and
> > there is 
> > > > ASP-coordination)
> > > > > 
> > > > > There is not a common network view !! This
> > MUST be fixed.
> > > > 
> > > > The RFC does not say that the ASP considers
> > itself in the
> > > > AS-INACTIVE state until n ASPs are active.  Read
> > again:
> > > > 
> > > >    For the n+k redundancy case, ASPs which are
> > in that AS should
> > > >    coordinate among themselves the number of
> > active ASPs in 
> > > > the AS, and
> > > >    should start sending traffic only after n
> > ASPs are active.
> > > > 
> > > > The ASP considers itself in the ASP-ACTIVE state
> > for the AS
> > > > (and may consider the AS active) as soon as it
> > receives the
> > > > ASP Active Ack.
> > > > 
> > > > The ASP may consider the AS active as soon as it
> > receives an
> > > > NTFY(AS-Active) regardless of whether it is
> > ASP-INACTIVE for
> > > > the AS.
> > > > 
> > > > What the ASPs do is not start sending traffic
> > until 'n' are
> > > > active.
> 
> 
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Thu Jun 26 12:27:30 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07385
	for <sigtran-archive@odin.ietf.org>; Thu, 26 Jun 2003 12:27:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5QGR3Q22206
	for sigtran-archive@odin.ietf.org; Thu, 26 Jun 2003 12:27:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VZaP-0005lv-G4; Thu, 26 Jun 2003 12:27:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VZaH-0005lj-2J
	for sigtran@optimus.ietf.org; Thu, 26 Jun 2003 12:26:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07344
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 12:26:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VZaF-0003Uy-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 12:26:51 -0400
Received: from web12803.mail.yahoo.com ([216.136.174.38])
	by ietf-mx with smtp (Exim 4.12)
	id 19VZa4-0003UN-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 12:26:40 -0400
Message-ID: <20030626155913.23670.qmail@web12803.mail.yahoo.com>
Received: from [208.255.120.2] by web12803.mail.yahoo.com via HTTP; Thu, 26 Jun 2003 08:59:13 PDT
Date: Thu, 26 Jun 2003 08:59:13 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] Re: M3UA Notify message
To: sigtran@ietf.org
In-Reply-To: <20030626091845.A939@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Tolga,
> 
> Tolga Asveren wrote:                                
>                                 (Thu, 26 Jun 2003
> 04:48:59)
> > Brian,
> > 
> > IMO, one of the key points is that assuming that
> an
> > ASP SHOULD rely on NTFY from SGP or not. If there
> is
> > such a need, this has to be in RFC/IG with a
> "SHOULD"
> > -like everything else necessary is there with a
> > "SHOULD" or "MUST". Otherwise one can fill the RFC
> > with "MAY"s and can argue "Well, it is
> implementors
> > responsibility to be clever enough to decide which
> of
> > those MAY should have been in fact a SHOULD".
> 
> I am not saying that an ASP should rely on Notify.
> I am saying that it can.  That is, the ASP can meet
> the requirement that it SHOULD coordinate that 'n'
> ASPs are active regardles of what the SG does, and
> that the ASP can know when the SG activates the AS
> to synchronize state as much as it cares to.
[TOLGA]What is the reason to allow SG to decide
dynamically, when AS should be ACTIVE? And based on
which criteria -apart from number of ACTIVE ASPs-? In
fact, based on your arguments, I would expect that you
propose getting rid of concept of n and just saying
that it is ASPs responsibility when to send ASPAC,
based on current load and expected load and that to
decide for this is outside of the scope of M3UA.

[..snip..]
> There is no mechanism in SS7 to inform the SS7
> network
> that an AS (MTP-User) is active.  There is no UPA or
> UPT
> message in MTP, just a UPU.
[TOLGA]I think it will be SG, which responds with a
UPU or not for received traffic (including UPT). So,
it might not respond with UPU, if it has AS state
ACTIVE, even if ASP has AS state INACTIVE.
IMO, each layer should do, what it is supposed to do,
without relying to some other mechanisms on upper
layers-for example generating or not generating is
MTP3 responsibility, so SG should do this correctly-.
Personally I prefer to reflect the state of AS
properly to SS7 nodes. For example, with the same
logic, one could argue that UPU is not necessary at
all, because we have SST and CVT. 

[..snip..] 
> Therefore, the SG can always start traffic on the
> first ASP
> as provided for in the RFC.
[TOLGA]What stands in IG does not disallow this, just
using n=1 will achieve this.
> 
> The proposal to require the SG to wait remains
> unacceptable.
> 
> --brian
> 
> > 
> >      Tolga
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > Javier,
> > > 
> > > Javier Pastor-Balbas (ECE) wrote:               
>    
> > >                                (Thu, 26 Jun 2003
> > > 10:10:30)
> > > > 
> > > > Brian, 
> > > > 
> > > > More comments on yours....
> > > > 
> > > > > -----Original Message-----
> > > > > From: Brian F. G. Bidulock
> > > [mailto:bidulock@openss7.org]
> > > > > Sent: jueves, 26 de junio de 2003 9:44
> > > > > To: Javier Pastor-Balbas (ECE)
> > > > > Cc: Tolga Asveren; sigtran@ietf.org
> > > > > Subject: Re: [Sigtran] Re: M3UA Notify
> message
> > > > > 
> > > > > 
> > > > > Javier,
> > > > > 
> > > > > Your proposal for 3.15 is still
> unacceptable.
> > > > > 
> > > > > Please see comments below...
> > > > > 
> > > > > Javier Pastor-Balbas (ECE) wrote:           
>    
> > >              
> > > > >                       (Thu, 26 Jun 2003
> > > 09:12:20)
> > > > > > Brian, 
> > > > > > 
> > > > > > See my comments inline...
> > > > > > 
> > > > > > Cheers // Javier.
> > > > > > 
> > > > > > > -----Original Message-----
> > > > > > > From: Brian F. G. Bidulock
> > > [mailto:bidulock@openss7.org]
> > > > > > > Sent: martes, 24 de junio de 2003 23:25
> > > > > > > To: Tolga Asveren
> > > > > > > Cc: sigtran@ietf.org
> > > > > > > Subject: Re: [Sigtran] Re: M3UA Notify
> > > message
> > > > > > > 
> > > > > > > 
> > > > > > > Tolga,
> > > > > > > 
> > > > > > > Tolga Asveren wrote:                    
>    
> > >                  
> > > > > > >                        (Tue, 24 Jun 2003
> > > 13:54:50)
> > > > > > > > Brian,
> > > > > > > > (some more repeating of my ideas about
> > > this topic ;-)
> > > > > > > > )
> > > > > > > > --- "Brian F. G. Bidulock"
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

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



From exim@www1.ietf.org  Thu Jun 26 14:02:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11799
	for <sigtran-archive@odin.ietf.org>; Thu, 26 Jun 2003 14:02:30 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5QI23816141
	for sigtran-archive@odin.ietf.org; Thu, 26 Jun 2003 14:02:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Vb4L-0004Bz-Cz; Thu, 26 Jun 2003 14:02:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Vb3T-00040H-AA
	for sigtran@optimus.ietf.org; Thu, 26 Jun 2003 14:01:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11698
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 14:00:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vb3B-0004Mb-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 14:00:49 -0400
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vb30-0004L9-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 14:00:39 -0400
Received: from [172.16.1.204] (helo=CCPU00198)
	by smtp.ccpu.com with smtp (Exim 4.20 #1 (Debian))
	id 19Vb15-0006DA-Vl
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 10:58:39 -0700
From: "Nitin Tomar" <nitty@ccpu.com>
To: <sigtran@ietf.org>
Date: Thu, 26 Jun 2003 11:01:39 -0700
Message-ID: <EPEMKGELBFBBOPEEIJNBAEBPCCAA.nitty@ccpu.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0006_01C33BD2.515DD260"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Subject: [Sigtran] AS Override question
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0006_01C33BD2.515DD260
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Hi All,
One basic question related to AS state in Override mode.
Scenario is:
An SG is served by two SGPs (SGP-1 and SGP-2) and AS is served by two ASPs
(ASP-1 and ASP-2),
let's say ASP-1 is initially active for AS and it has sent ASP-ACTIVE
message only towards
SGP-1, and now the SGP-2 receives this ASP-ACTIVE from ASP-2 for the same
AS.

What shall be the behavior at SG in response to ASP-ACTIVE from ASP-2,
I can see three possibilities:
a) SG (SGP-2) shall reject ASP-ACTIVE from ASP-2 as ASP-1 is already active
towards SGP1,
    if yes then what shall be the errorcode used in rejection message?

b) SG shall mark the ASP-2 as active for AS and mark the ASP-1 as INACTIVE
(and send the NTFY
    message (ALT-ASP-ACTIVE) to ASP-1 but in this case SG will not know from
which SGP
    it shall send the NTFY message?).

c) SG shall accept the ASP-2's request as well but in this case for a single
AS in OVERRIDE mode there
    will be two ASPs which are ACTIVE (each from different SGPs).

It will be interesting to know that what other M3UA implementers think about
handling above scenario.

Thanks
Nitin


------=_NextPart_000_0006_01C33BD2.515DD260
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D046263617-26062003>Hi=20
All,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D046263617-26062003>One =
basic question=20
related to AS state in Override mode.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D046263617-26062003>Scenario=20
is:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D046263617-26062003>An SG =
is served by=20
two SGPs (SGP-1 and SGP-2) and AS is&nbsp;served by&nbsp;two ASPs (ASP-1 =
and=20
ASP-2),</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D046263617-26062003>let's =
say ASP-1 is=20
initially active for AS and it has sent ASP-ACTIVE message only=20
towards</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D046263617-26062003>SGP-1, =
and now the=20
SGP-2 receives this ASP-ACTIVE from ASP-2 for the same AS. =
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D046263617-26062003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D046263617-26062003>What =
shall be the=20
behavior at SG in response to ASP-ACTIVE from ASP-2, =
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D046263617-26062003>I can =
see three=20
possibilities:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D046263617-26062003>a) SG=20
(SGP-2)&nbsp;shall reject ASP-ACTIVE from ASP-2 as ASP-1 is already =
active=20
towards SGP1,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D046263617-26062003>&nbsp;&nbsp;&nbsp;=20
if yes then what shall be the errorcode used in rejection=20
message?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D046263617-26062003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D046263617-26062003>b) SG =
shall mark the=20
ASP-2 as active for AS and mark the ASP-1 as INACTIVE (and send the=20
NTFY</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D046263617-26062003>&nbsp;&nbsp;&nbsp;=20
message (ALT-ASP-ACTIVE) to ASP-1 but in this case SG will not know from =
which=20
SGP&nbsp;</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D046263617-26062003>&nbsp;&nbsp;&nbsp;=20
it shall send the&nbsp;NTFY message?).</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D046263617-26062003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D046263617-26062003>c) SG =
shall accept=20
the ASP-2's request as well but in this case for a single AS in OVERRIDE =
mode=20
there</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D046263617-26062003>&nbsp;&nbsp;&nbsp;=20
will be two ASPs which are ACTIVE (each from different=20
SGPs).</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D046263617-26062003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D046263617-26062003>It =
will be=20
interesting to know that what other M3UA implementers think&nbsp;about=20
handling&nbsp;above scenario.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D046263617-26062003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D046263617-26062003>Thanks</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D046263617-26062003>Nitin</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D046263617-26062003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D046263617-26062003></SPAN></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0006_01C33BD2.515DD260--


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



From exim@www1.ietf.org  Thu Jun 26 14:04:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11943
	for <sigtran-archive@odin.ietf.org>; Thu, 26 Jun 2003 14:04:28 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5QI41T17186
	for sigtran-archive@odin.ietf.org; Thu, 26 Jun 2003 14:04:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Vb6H-0004T6-ET; Thu, 26 Jun 2003 14:04:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Vb69-0004QP-Bu
	for sigtran@optimus.ietf.org; Thu, 26 Jun 2003 14:03:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11823
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 14:02:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vb54-0004NV-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 14:02:46 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[8VYT9tD0qZk6KhhgGVOC2E8QncPgznkq])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vb4o-0004LU-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 14:02:30 -0400
Received: from ns.pigworks.openss7.net (IDENT:MpXkEC41SlmVP3smAQAEFbhGuWRb2P0k@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5QHwsX30196;
	Thu, 26 Jun 2003 11:58:54 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5QHwrI07025;
	Thu, 26 Jun 2003 11:58:53 -0600
Date: Thu, 26 Jun 2003 11:58:53 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030626115853.A5811@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030626091845.A939@openss7.org> <20030626155913.23670.qmail@web12803.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030626155913.23670.qmail@web12803.mail.yahoo.com>; from tolga_asveren@yahoo.com on Thu, Jun 26, 2003 at 08:59:13AM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

Tolga Asveren wrote:                                                                 (Thu, 26 Jun 2003 08:59:13)
> Brian,
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                                
> >                                 (Thu, 26 Jun 2003
> > 04:48:59)
> > > Brian,
> > > 
> > > IMO, one of the key points is that assuming that
> > an
> > > ASP SHOULD rely on NTFY from SGP or not. If there
> > is
> > > such a need, this has to be in RFC/IG with a
> > "SHOULD"
> > > -like everything else necessary is there with a
> > > "SHOULD" or "MUST". Otherwise one can fill the RFC
> > > with "MAY"s and can argue "Well, it is
> > implementors
> > > responsibility to be clever enough to decide which
> > of
> > > those MAY should have been in fact a SHOULD".
> > 
> > I am not saying that an ASP should rely on Notify.
> > I am saying that it can.  That is, the ASP can meet
> > the requirement that it SHOULD coordinate that 'n'
> > ASPs are active regardles of what the SG does, and
> > that the ASP can know when the SG activates the AS
> > to synchronize state as much as it cares to.
> [TOLGA]What is the reason to allow SG to decide
> dynamically, when AS should be ACTIVE? And based on
> which criteria -apart from number of ACTIVE ASPs-? In
> fact, based on your arguments, I would expect that you
> propose getting rid of concept of n and just saying
> that it is ASPs responsibility when to send ASPAC,
> based on current load and expected load and that to
> decide for this is outside of the scope of M3UA.
> 
> [..snip..]
> > There is no mechanism in SS7 to inform the SS7
> > network
> > that an AS (MTP-User) is active.  There is no UPA or
> > UPT
> > message in MTP, just a UPU.
> [TOLGA]I think it will be SG, which responds with a
> UPU or not for received traffic (including UPT). So,
> it might not respond with UPU, if it has AS state
> ACTIVE, even if ASP has AS state INACTIVE.

Not responding with UPU does not activate traffic at
the remote peer.  For ISUP, a message must be received
from the ASP (UPA or CNF(97)) before traffic will be
started.  For, SCCP a message must be received from
the ASP (SSA) before traffic will be started.

So, you see, the ASP is responsible for starting
traffic from remote peers, other than UP test messages,
which, if not responded to, will NOT start user traffic.

There is still the concept of 'n', it is just that
the ASP is responsible for it, not the SG, as in the
RFC...


> IMO, each layer should do, what it is supposed to do,
> without relying to some other mechanisms on upper
> layers-for example generating or not generating is
> MTP3 responsibility, so SG should do this correctly-.

User flow control and congestion control is explicitly
a responsibility of the MTP-User in the MTP specifications.
It is MTP that we are transporting with M3UA, and flow
control (starting user traffic) and congestion control
(throttling excess user traffic) is explicitly the
responsibility of the ASP.  As in the RFC...

> Personally I prefer to reflect the state of AS
> properly to SS7 nodes. For example, with the same
> logic, one could argue that UPU is not necessary at
> all, because we have SST and CVT. 

UPU is necessary for distinguishing between an
unequipped user (for which traffic must cease and
management be notified) and an unavailable user (for
which user test procedures begin).  To distinguish,
this message is issued by MTP.  Aside from that, 
UPT/UPA (and restarting user traffic) is the
responsibility of ISUP and  SST/SSA to SSN 0 (and
restarting subsystem traffic) is the responsibility
of SCCP.  These are the responsibilities of the MTP-User
in the MTP specifications.  They are the responsibility
of the ASP in the M3UA RFC, and a responsibility that
the ASP cannot avoid.  The MTP cannot send UPA/SSA for
the user part, even if it wanted to.

So, at the SG, there is no correlation between AS-ACTIVE
and the restart of the user traffic.  User traffic will
only restart some time after AS-ACTIVE, when the ASPs
decide amoungst themselves (E.G. WHEN 'N' OF THEM ARE
ACTIVE) that they should send UPA/SSA and restart
user traffic.

> 
> [..snip..] 
> > Therefore, the SG can always start traffic on the
> > first ASP
> > as provided for in the RFC.
> [TOLGA]What stands in IG does not disallow this, just
> using n=1 will achieve this.

The RFC permits it when 'n' is not one.

You can see from the above that AS-ACTIVE and 'n' has
no bearing on when the "traffic" mentioned in 1.4.4.1
is directed to the ASP.  The ASP decides this for itself
when it coordinates that 'n' are active.

No changes are needed to the AS state machin or the
RFC.  Nothing bad will happen.  IG. 3.15 is a waste of
time.  Stike it.

--brian


> > 
> > The proposal to require the SG to wait remains
> > unacceptable.
> > 
> > --brian
> > 
> > > 
> > >      Tolga
> > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > wrote:
> > > > Javier,
> > > > 
> > > > Javier Pastor-Balbas (ECE) wrote:               
> >    
> > > >                                (Thu, 26 Jun 2003
> > > > 10:10:30)
> > > > > 
> > > > > Brian, 
> > > > > 
> > > > > More comments on yours....
> > > > > 
> > > > > > -----Original Message-----
> > > > > > From: Brian F. G. Bidulock
> > > > [mailto:bidulock@openss7.org]
> > > > > > Sent: jueves, 26 de junio de 2003 9:44
> > > > > > To: Javier Pastor-Balbas (ECE)
> > > > > > Cc: Tolga Asveren; sigtran@ietf.org
> > > > > > Subject: Re: [Sigtran] Re: M3UA Notify
> > message
> > > > > > 
> > > > > > 
> > > > > > Javier,
> > > > > > 
> > > > > > Your proposal for 3.15 is still
> > unacceptable.
> > > > > > 
> > > > > > Please see comments below...
> > > > > > 
> > > > > > Javier Pastor-Balbas (ECE) wrote:           
> >    
> > > >              
> > > > > >                       (Thu, 26 Jun 2003
> > > > 09:12:20)
> > > > > > > Brian, 
> > > > > > > 
> > > > > > > See my comments inline...
> > > > > > > 
> > > > > > > Cheers // Javier.
> > > > > > > 
> > > > > > > > -----Original Message-----
> > > > > > > > From: Brian F. G. Bidulock
> > > > [mailto:bidulock@openss7.org]
> > > > > > > > Sent: martes, 24 de junio de 2003 23:25
> > > > > > > > To: Tolga Asveren
> > > > > > > > Cc: sigtran@ietf.org
> > > > > > > > Subject: Re: [Sigtran] Re: M3UA Notify
> > > > message
> > > > > > > > 
> > > > > > > > 
> > > > > > > > Tolga,
> > > > > > > > 
> > > > > > > > Tolga Asveren wrote:                    
> >    
> > > >                  
> > > > > > > >                        (Tue, 24 Jun 2003
> > > > 13:54:50)
> > > > > > > > > Brian,
> > > > > > > > > (some more repeating of my ideas about
> > > > this topic ;-)
> > > > > > > > > )
> > > > > > > > > --- "Brian F. G. Bidulock"
> > 
> === message truncated ===
> 
> 
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Thu Jun 26 14:09:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12312
	for <sigtran-archive@odin.ietf.org>; Thu, 26 Jun 2003 14:09:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5QI92r20121
	for sigtran-archive@odin.ietf.org; Thu, 26 Jun 2003 14:09:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VbB7-0005EI-DH; Thu, 26 Jun 2003 14:09:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VbAX-0005Dm-2R
	for sigtran@optimus.ietf.org; Thu, 26 Jun 2003 14:08:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12243
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 14:08:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VbAU-0004R0-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 14:08:22 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[UqznAlaqsIYWLRvFpupnoMenwaW6seQL])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VbAE-0004Qr-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 14:08:06 -0400
Received: from ns.pigworks.openss7.net (IDENT:nfH9DAClQbLRzKNvC+3Dz9DnqOdD7H9b@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5QI7uX30420;
	Thu, 26 Jun 2003 12:07:56 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5QI7tA07437;
	Thu, 26 Jun 2003 12:07:55 -0600
Date: Thu, 26 Jun 2003 12:07:55 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Nitin Tomar <nitty@ccpu.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] AS Override question
Message-ID: <20030626120755.A7389@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Nitin Tomar <nitty@ccpu.com>, sigtran@ietf.org
References: <EPEMKGELBFBBOPEEIJNBAEBPCCAA.nitty@ccpu.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <EPEMKGELBFBBOPEEIJNBAEBPCCAA.nitty@ccpu.com>; from nitty@ccpu.com on Thu, Jun 26, 2003 at 11:01:39AM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Nitin,

ASPTM/SM message and ASP state in the AS are per-SGP.

--brian

Nitin Tomar wrote:                                                                   (Thu, 26 Jun 2003 11:01:39)
> 
>    Hi All,
> 
>    One basic question related to AS state in Override mode.
> 
>    Scenario is:
> 
>    An  SG is served by two SGPs (SGP-1 and SGP-2) and AS is served by two
>    ASPs (ASP-1 and ASP-2),
> 
>    let's  say ASP-1 is initially active for AS and it has sent ASP-ACTIVE
>    message only towards
> 
>    SGP-1,  and  now the SGP-2 receives this ASP-ACTIVE from ASP-2 for the
>    same AS.
> 
> 
> 
>    What shall be the behavior at SG in response to ASP-ACTIVE from ASP-2,
> 
>    I can see three possibilities:
> 
>    a)  SG  (SGP-2) shall reject ASP-ACTIVE from ASP-2 as ASP-1 is already
>    active towards SGP1,
> 
>        if yes then what shall be the errorcode used in rejection message?
> 
> 
> 
>    b)  SG  shall  mark  the  ASP-2 as active for AS and mark the ASP-1 as
>    INACTIVE (and send the NTFY
> 
>         message  (ALT-ASP-ACTIVE)  to  ASP-1 but in this case SG will not
>    know from which SGP
> 
>        it shall send the NTFY message?).
> 
> 
> 
>    c)  SG shall accept the ASP-2's request as well but in this case for a
>    single AS in OVERRIDE mode there
> 
>        will be two ASPs which are ACTIVE (each from different SGPs).
> 
> 
> 
>    It  will  be  interesting  to  know  that what other M3UA implementers
>    think about handling above scenario.
> 
> 
> 
>    Thanks
> 
>    Nitin

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

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



From exim@www1.ietf.org  Thu Jun 26 14:59:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15077
	for <sigtran-archive@odin.ietf.org>; Thu, 26 Jun 2003 14:59:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5QIx2G06958
	for sigtran-archive@odin.ietf.org; Thu, 26 Jun 2003 14:59:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VbxV-0001k6-1Q; Thu, 26 Jun 2003 14:59:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Vbx3-0001eG-HG
	for sigtran@optimus.ietf.org; Thu, 26 Jun 2003 14:58:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15028
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 14:58:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vbx0-0004uK-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 14:58:30 -0400
Received: from web12806.mail.yahoo.com ([216.136.174.41])
	by ietf-mx with smtp (Exim 4.12)
	id 19Vbwp-0004rc-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 14:58:19 -0400
Message-ID: <20030626185454.46249.qmail@web12806.mail.yahoo.com>
Received: from [208.255.120.2] by web12806.mail.yahoo.com via HTTP; Thu, 26 Jun 2003 11:54:54 PDT
Date: Thu, 26 Jun 2003 11:54:54 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] Re: M3UA Notify message
To: sigtran@ietf.org
In-Reply-To: <20030626115853.A5811@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,

To me any user part message (including ISUP/SCCP
management messages) is the same. So, that SG causes
SST to be sent by a peer, in fact where AS was not
ACTIVE on ASP side is also bad.

IMO, user part procedures should be irrelevant for
M3UA. We should try to mimic MTP3 as much as possible,
and when a user part is not avialable, MTP3 replies
with UPU for messages received for that user part.
There is a way to achieve consistency of AS states at
ASP and SGP sides and my personal opinion is to move
in that direction. Personally I fail to see a benefit
of not doing so -especially when n=1 is always
possible, for the behaviour you describe below n=1
should work fine as far as I can see (that ASPs reply
with SSA/UPA only after n of them are ACTIVE-).

In fact, as far as I can understand, you are proposing
to get rid of n, althoug you say it is still there but
just for ASP. I think, M3UA document should not speak
about procedures/requirements of user parts on ASP
side but just of M3UA stack on ASP side. In your way
of operation, you shift the concept of n up to the
user parts -so IMO this makes it disappear in the
context of M3UA-.

     Tolga

--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Tolga,
> 
> Tolga Asveren wrote:                                
>                                 (Thu, 26 Jun 2003
> 08:59:13)
> > Brian,
> > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > wrote:
> > > Tolga,
> > > 
> > > Tolga Asveren wrote:                            
>    
> > >                                 (Thu, 26 Jun
> 2003
> > > 04:48:59)
> > > > Brian,
> > > > 
> > > > IMO, one of the key points is that assuming
> that
> > > an
> > > > ASP SHOULD rely on NTFY from SGP or not. If
> there
> > > is
> > > > such a need, this has to be in RFC/IG with a
> > > "SHOULD"
> > > > -like everything else necessary is there with
> a
> > > > "SHOULD" or "MUST". Otherwise one can fill the
> RFC
> > > > with "MAY"s and can argue "Well, it is
> > > implementors
> > > > responsibility to be clever enough to decide
> which
> > > of
> > > > those MAY should have been in fact a SHOULD".
> > > 
> > > I am not saying that an ASP should rely on
> Notify.
> > > I am saying that it can.  That is, the ASP can
> meet
> > > the requirement that it SHOULD coordinate that
> 'n'
> > > ASPs are active regardles of what the SG does,
> and
> > > that the ASP can know when the SG activates the
> AS
> > > to synchronize state as much as it cares to.
> > [TOLGA]What is the reason to allow SG to decide
> > dynamically, when AS should be ACTIVE? And based
> on
> > which criteria -apart from number of ACTIVE ASPs-?
> In
> > fact, based on your arguments, I would expect that
> you
> > propose getting rid of concept of n and just
> saying
> > that it is ASPs responsibility when to send ASPAC,
> > based on current load and expected load and that
> to
> > decide for this is outside of the scope of M3UA.
> > 
> > [..snip..]
> > > There is no mechanism in SS7 to inform the SS7
> > > network
> > > that an AS (MTP-User) is active.  There is no
> UPA or
> > > UPT
> > > message in MTP, just a UPU.
> > [TOLGA]I think it will be SG, which responds with
> a
> > UPU or not for received traffic (including UPT).
> So,
> > it might not respond with UPU, if it has AS state
> > ACTIVE, even if ASP has AS state INACTIVE.
> 
> Not responding with UPU does not activate traffic at
> the remote peer.  For ISUP, a message must be
> received
> from the ASP (UPA or CNF(97)) before traffic will be
> started.  For, SCCP a message must be received from
> the ASP (SSA) before traffic will be started.
> 
> So, you see, the ASP is responsible for starting
> traffic from remote peers, other than UP test
> messages,
> which, if not responded to, will NOT start user
> traffic.
> 
> There is still the concept of 'n', it is just that
> the ASP is responsible for it, not the SG, as in the
> RFC...
> 
> 
> > IMO, each layer should do, what it is supposed to
> do,
> > without relying to some other mechanisms on upper
> > layers-for example generating or not generating is
> > MTP3 responsibility, so SG should do this
> correctly-.
> 
> User flow control and congestion control is
> explicitly
> a responsibility of the MTP-User in the MTP
> specifications.
> It is MTP that we are transporting with M3UA, and
> flow
> control (starting user traffic) and congestion
> control
> (throttling excess user traffic) is explicitly the
> responsibility of the ASP.  As in the RFC...
> 
> > Personally I prefer to reflect the state of AS
> > properly to SS7 nodes. For example, with the same
> > logic, one could argue that UPU is not necessary
> at
> > all, because we have SST and CVT. 
> 
> UPU is necessary for distinguishing between an
> unequipped user (for which traffic must cease and
> management be notified) and an unavailable user (for
> which user test procedures begin).  To distinguish,
> this message is issued by MTP.  Aside from that, 
> UPT/UPA (and restarting user traffic) is the
> responsibility of ISUP and  SST/SSA to SSN 0 (and
> restarting subsystem traffic) is the responsibility
> of SCCP.  These are the responsibilities of the
> MTP-User
> in the MTP specifications.  They are the
> responsibility
> of the ASP in the M3UA RFC, and a responsibility
> that
> the ASP cannot avoid.  The MTP cannot send UPA/SSA
> for
> the user part, even if it wanted to.
> 
> So, at the SG, there is no correlation between
> AS-ACTIVE
> and the restart of the user traffic.  User traffic
> will
> only restart some time after AS-ACTIVE, when the
> ASPs
> decide amoungst themselves (E.G. WHEN 'N' OF THEM
> ARE
> ACTIVE) that they should send UPA/SSA and restart
> user traffic.
> 
> > 
> > [..snip..] 
> > > Therefore, the SG can always start traffic on
> the
> > > first ASP
> > > as provided for in the RFC.
> > [TOLGA]What stands in IG does not disallow this,
> just
> > using n=1 will achieve this.
> 
> The RFC permits it when 'n' is not one.
> 
> You can see from the above that AS-ACTIVE and 'n'
> has
> no bearing on when the "traffic" mentioned in
> 1.4.4.1
> is directed to the ASP.  The ASP decides this for
> itself
> when it coordinates that 'n' are active.
> 
> No changes are needed to the AS state machin or the
> RFC.  Nothing bad will happen.  IG. 3.15 is a waste
> of
> time.  Stike it.
> 
> --brian
> 
> 
> > > 
> > > The proposal to require the SG to wait remains
> > > unacceptable.
> > > 
> > > --brian
> > > 
> > > > 
> > > >      Tolga
> > > > --- "Brian F. G. Bidulock"
> <bidulock@openss7.org>
> > > > wrote:
> > > > > Javier,
> > > > > 
> > > > > Javier Pastor-Balbas (ECE) wrote:           
>    
> > >    
> > > > >                                (Thu, 26 Jun


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

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



From exim@www1.ietf.org  Thu Jun 26 15:04:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15335
	for <sigtran-archive@odin.ietf.org>; Thu, 26 Jun 2003 15:04:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5QJ42n09824
	for sigtran-archive@odin.ietf.org; Thu, 26 Jun 2003 15:04:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Vc2L-0002Xq-2z; Thu, 26 Jun 2003 15:04:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Vc1V-0002SH-5x
	for sigtran@optimus.ietf.org; Thu, 26 Jun 2003 15:03:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15199
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 15:02:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vc0P-0004wD-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 15:02:01 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[tdo3WyMp/nd4XEhk6kMsFaxpu7ycjicJ])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vc08-0004w0-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 15:01:45 -0400
Received: from ns.pigworks.openss7.net (IDENT:IgyMRs7qEGoquPk0HRSMz5v4d5xEcyp9@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5QJ1NX31223;
	Thu, 26 Jun 2003 13:01:23 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5QJ1No08624;
	Thu, 26 Jun 2003 13:01:23 -0600
Date: Thu, 26 Jun 2003 13:01:23 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re: M3UA Notify message
Message-ID: <20030626130123.A8284@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030626115853.A5811@openss7.org> <20030626185454.46249.qmail@web12806.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030626185454.46249.qmail@web12806.mail.yahoo.com>; from tolga_asveren@yahoo.com on Thu, Jun 26, 2003 at 11:54:54AM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

I am not proposing anything.  I wish to stick with
the RFC as it stands.  You and Javier are prosposing
a change.  One that is unnecessary and one that I
disagree with.

--brian


Tolga Asveren wrote:                                                                 (Thu, 26 Jun 2003 11:54:54)
> Brian,
> 
> To me any user part message (including ISUP/SCCP
> management messages) is the same. So, that SG causes
> SST to be sent by a peer, in fact where AS was not
> ACTIVE on ASP side is also bad.
> 
> IMO, user part procedures should be irrelevant for
> M3UA. We should try to mimic MTP3 as much as possible,
> and when a user part is not avialable, MTP3 replies
> with UPU for messages received for that user part.
> There is a way to achieve consistency of AS states at
> ASP and SGP sides and my personal opinion is to move
> in that direction. Personally I fail to see a benefit
> of not doing so -especially when n=1 is always
> possible, for the behaviour you describe below n=1
> should work fine as far as I can see (that ASPs reply
> with SSA/UPA only after n of them are ACTIVE-).
> 
> In fact, as far as I can understand, you are proposing
> to get rid of n, althoug you say it is still there but
> just for ASP. I think, M3UA document should not speak
> about procedures/requirements of user parts on ASP
> side but just of M3UA stack on ASP side. In your way
> of operation, you shift the concept of n up to the
> user parts -so IMO this makes it disappear in the
> context of M3UA-.
> 
>      Tolga
> 
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Tolga,
> > 
> > Tolga Asveren wrote:                                
> >                                 (Thu, 26 Jun 2003
> > 08:59:13)
> > > Brian,
> > > --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> > > wrote:
> > > > Tolga,
> > > > 
> > > > Tolga Asveren wrote:                            
> >    
> > > >                                 (Thu, 26 Jun
> > 2003
> > > > 04:48:59)
> > > > > Brian,
> > > > > 
> > > > > IMO, one of the key points is that assuming
> > that
> > > > an
> > > > > ASP SHOULD rely on NTFY from SGP or not. If
> > there
> > > > is
> > > > > such a need, this has to be in RFC/IG with a
> > > > "SHOULD"
> > > > > -like everything else necessary is there with
> > a
> > > > > "SHOULD" or "MUST". Otherwise one can fill the
> > RFC
> > > > > with "MAY"s and can argue "Well, it is
> > > > implementors
> > > > > responsibility to be clever enough to decide
> > which
> > > > of
> > > > > those MAY should have been in fact a SHOULD".
> > > > 
> > > > I am not saying that an ASP should rely on
> > Notify.
> > > > I am saying that it can.  That is, the ASP can
> > meet
> > > > the requirement that it SHOULD coordinate that
> > 'n'
> > > > ASPs are active regardles of what the SG does,
> > and
> > > > that the ASP can know when the SG activates the
> > AS
> > > > to synchronize state as much as it cares to.
> > > [TOLGA]What is the reason to allow SG to decide
> > > dynamically, when AS should be ACTIVE? And based
> > on
> > > which criteria -apart from number of ACTIVE ASPs-?
> > In
> > > fact, based on your arguments, I would expect that
> > you
> > > propose getting rid of concept of n and just
> > saying
> > > that it is ASPs responsibility when to send ASPAC,
> > > based on current load and expected load and that
> > to
> > > decide for this is outside of the scope of M3UA.
> > > 
> > > [..snip..]
> > > > There is no mechanism in SS7 to inform the SS7
> > > > network
> > > > that an AS (MTP-User) is active.  There is no
> > UPA or
> > > > UPT
> > > > message in MTP, just a UPU.
> > > [TOLGA]I think it will be SG, which responds with
> > a
> > > UPU or not for received traffic (including UPT).
> > So,
> > > it might not respond with UPU, if it has AS state
> > > ACTIVE, even if ASP has AS state INACTIVE.
> > 
> > Not responding with UPU does not activate traffic at
> > the remote peer.  For ISUP, a message must be
> > received
> > from the ASP (UPA or CNF(97)) before traffic will be
> > started.  For, SCCP a message must be received from
> > the ASP (SSA) before traffic will be started.
> > 
> > So, you see, the ASP is responsible for starting
> > traffic from remote peers, other than UP test
> > messages,
> > which, if not responded to, will NOT start user
> > traffic.
> > 
> > There is still the concept of 'n', it is just that
> > the ASP is responsible for it, not the SG, as in the
> > RFC...
> > 
> > 
> > > IMO, each layer should do, what it is supposed to
> > do,
> > > without relying to some other mechanisms on upper
> > > layers-for example generating or not generating is
> > > MTP3 responsibility, so SG should do this
> > correctly-.
> > 
> > User flow control and congestion control is
> > explicitly
> > a responsibility of the MTP-User in the MTP
> > specifications.
> > It is MTP that we are transporting with M3UA, and
> > flow
> > control (starting user traffic) and congestion
> > control
> > (throttling excess user traffic) is explicitly the
> > responsibility of the ASP.  As in the RFC...
> > 
> > > Personally I prefer to reflect the state of AS
> > > properly to SS7 nodes. For example, with the same
> > > logic, one could argue that UPU is not necessary
> > at
> > > all, because we have SST and CVT. 
> > 
> > UPU is necessary for distinguishing between an
> > unequipped user (for which traffic must cease and
> > management be notified) and an unavailable user (for
> > which user test procedures begin).  To distinguish,
> > this message is issued by MTP.  Aside from that, 
> > UPT/UPA (and restarting user traffic) is the
> > responsibility of ISUP and  SST/SSA to SSN 0 (and
> > restarting subsystem traffic) is the responsibility
> > of SCCP.  These are the responsibilities of the
> > MTP-User
> > in the MTP specifications.  They are the
> > responsibility
> > of the ASP in the M3UA RFC, and a responsibility
> > that
> > the ASP cannot avoid.  The MTP cannot send UPA/SSA
> > for
> > the user part, even if it wanted to.
> > 
> > So, at the SG, there is no correlation between
> > AS-ACTIVE
> > and the restart of the user traffic.  User traffic
> > will
> > only restart some time after AS-ACTIVE, when the
> > ASPs
> > decide amoungst themselves (E.G. WHEN 'N' OF THEM
> > ARE
> > ACTIVE) that they should send UPA/SSA and restart
> > user traffic.
> > 
> > > 
> > > [..snip..] 
> > > > Therefore, the SG can always start traffic on
> > the
> > > > first ASP
> > > > as provided for in the RFC.
> > > [TOLGA]What stands in IG does not disallow this,
> > just
> > > using n=1 will achieve this.
> > 
> > The RFC permits it when 'n' is not one.
> > 
> > You can see from the above that AS-ACTIVE and 'n'
> > has
> > no bearing on when the "traffic" mentioned in
> > 1.4.4.1
> > is directed to the ASP.  The ASP decides this for
> > itself
> > when it coordinates that 'n' are active.
> > 
> > No changes are needed to the AS state machin or the
> > RFC.  Nothing bad will happen.  IG. 3.15 is a waste
> > of
> > time.  Stike it.
> > 
> > --brian
> > 
> > 
> > > > 
> > > > The proposal to require the SG to wait remains
> > > > unacceptable.
> > > > 
> > > > --brian
> > > > 
> > > > > 
> > > > >      Tolga
> > > > > --- "Brian F. G. Bidulock"
> > <bidulock@openss7.org>
> > > > > wrote:
> > > > > > Javier,
> > > > > > 
> > > > > > Javier Pastor-Balbas (ECE) wrote:           
> >    
> > > >    
> > > > > >                                (Thu, 26 Jun
> 
> 
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Thu Jun 26 21:15:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29872
	for <sigtran-archive@odin.ietf.org>; Thu, 26 Jun 2003 21:15:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5R1F2S01446
	for sigtran-archive@odin.ietf.org; Thu, 26 Jun 2003 21:15:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VhpM-0000N6-Nd; Thu, 26 Jun 2003 21:15:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Vhnw-0000CH-CE
	for sigtran@optimus.ietf.org; Thu, 26 Jun 2003 21:14:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29811
	for <sigtran@ietf.org>; Thu, 26 Jun 2003 21:13:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vhne-0007kT-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 21:13:14 -0400
Received: from sjmail.ciena.com ([12.7.169.25] helo=w2ksjexg01.ciena.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19VhnU-0007k3-00
	for sigtran@ietf.org; Thu, 26 Jun 2003 21:13:04 -0400
Received: by w2ksjexg01.ciena.com with Internet Mail Service (5.5.2653.19)
	id <NS8BHGN6>; Thu, 26 Jun 2003 18:12:36 -0700
Message-ID: <829F074A10F98943A218DC363D09C92A250208@w2ksjexg06.oni.com>
From: "Ong, Lyndon" <LyOng@Ciena.com>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>,
        Tolga Asveren
	 <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] Re:n+k issue
Date: Thu, 26 Jun 2003 18:16:18 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Hi Folks,

At the risk of blowing up the issue (although I think we
are there already), I would like to make the following
points:

-- the issue of n+k is in fact confusing in the RFC text
  - n+k as defined in the introduction is subject to multiple
    interpretations
  - n+k has the following procedure defined in 4.3.4.3 -
  "For the n+k redundancy case, ASPs which are in that AS should
   coordinate among themselves the number of active ASPs in the AS, and
   should start sending traffic only after n ASPs are active."
    This seems to imply that traffic should only be resumed after
    n ASPs are active, even if traffic is sent from the SG the ASPs
    should not reply.
  - the examples in 5.1.4 and 5.2.3 also appear to reflect this usage.
  - n+k is not clearly reflected in the current state diagrams

Given that this appears to be a valid issue with the RFC and
there seems to be a greater weight of opinion on the side of
the proposed text I believe that the rough consensus exists
supporting the proposed text in the M3UA implementor's guide draft.

However, I understand the concern on the part of some folks
that have interpreted n+k differently.  As a result I think
we also should add clarifying text to the n+k definition in
1.4.4.1 stating that in this definition, traffic is not sent
until "n" ASPs are active, and that the "k" ASPs may be either 
active at the same time as "n" or kept inactive until needed
due to a failed or unavailable ASP.  Hopefully that will 
cover other situations acceptably.

Cheers,

L. Ong

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



From exim@www1.ietf.org  Fri Jun 27 12:32:36 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06736
	for <sigtran-archive@odin.ietf.org>; Fri, 27 Jun 2003 12:32:36 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5RGW9x32020
	for sigtran-archive@odin.ietf.org; Fri, 27 Jun 2003 12:32:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Vw8q-0008JI-Ad; Fri, 27 Jun 2003 12:32:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Vn1r-00062X-7B
	for sigtran@optimus.ietf.org; Fri, 27 Jun 2003 02:48:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19347
	for <sigtran@ietf.org>; Fri, 27 Jun 2003 02:47:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vn1Y-0001q7-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 02:47:56 -0400
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49] helo=albatross.tn.sw.ericsson.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vn1N-0001pT-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 02:47:45 -0400
Received: from esealnt611.al.sw.ericsson.se (alteon-nat4.sw.ericsson.se [153.88.254.121])
	by albatross.tn.sw.ericsson.se (8.12.9/8.12.9/WIREfire-1.6b) with ESMTP id h5R6jNG5007793;
	Fri, 27 Jun 2003 08:45:23 +0200 (MEST)
Received: from ESEALNT745.al.sw.ericsson.se ([153.88.251.5]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id NW47Q5L4; Fri, 27 Jun 2003 08:47:18 +0200
Received: by ESEALNT745.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NSLZAL41>; Fri, 27 Jun 2003 08:45:19 +0200
Message-ID: <1AB3D30B989BF141BBD5C70057B2EF7C01B65CA2@eestqnt105.es.eu.ericsson.se>
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
To: "'agurmukhani@hss.hns.com'" <agurmukhani@hss.hns.com>, sigtran@ietf.org
Subject: RE: [Sigtran] M3UA MIB Draft05: Loadsharing on CIC ,SSN
Date: Fri, 27 Jun 2003 08:45:02 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Hi Anjali, 

Thanks for your comment.

You are right saying that all CIC and SSN references were removed from the draft in  M3UA IG v03. Anyhow, I don't see any damage in keeping this CIC and SSN based loadsharing as another option. In fact it seems to me that this change was a bug during the process of removing all the SSN and CIC reference for the RK. But in any case both documents should be aligned. 

What do you and others think? Do we remove CIC and SSN based loadsharing from both documents? or do we allow it?

Thanks // Javier.


> -----Original Message-----
> From: agurmukhani@hss.hns.com [mailto:agurmukhani@hss.hns.com]
> Sent: jueves, 26 de junio de 2003 10:16
> To: sigtran@ietf.org
> Subject: [Sigtran] M3UA MIB Draft05: Loadsharing on CIC ,SSN
> 
> 
> 
> 
> 
> 
> Hi....
> 
> I had a query related to the M3UA MIB draft 05.
> Both m3uaSpLshMethod OBJECT-TYPE and  m3uaStreamLshMethod OBJECT-TYPE
> mention CIC and SSN as basis of loadsharing
> In my opinion, there is no point keeping CIC and SSN  as 
> loadsharing basis
> since this  would require  parsing  the data coming from the 
> M3UA user.
> Also references to these as loadsharing basis have been 
> removed from RFC as
> per Implementors guide 03.
> So IMO these should be removed from the MIB also.
> 
> 
> Thanks
> Anjali
> Hughes Software Systems
> 
> 
> 
> "DISCLAIMER: This message is proprietary to Hughes Software 
> Systems Limited
> (HSS) and is intended solely for the use of the individual to 
> whom it is
> addressed. It may contain  privileged or confidential information and
> should not be circulated or used for any purpose other than 
> for what it is
> intended. If you have received this message in error, please 
> notify the
> originator immediately. If you are not the intended recipient, you are
> notified that you are strictly prohibited from using, 
> copying, altering, or
> disclosing the contents of this message. HSS accepts no 
> responsibility for
> loss or damage arising from the use of the information 
> transmitted by this
> email including damage from virus."
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 

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



From exim@www1.ietf.org  Fri Jun 27 14:22:59 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09414
	for <sigtran-archive@odin.ietf.org>; Fri, 27 Jun 2003 14:22:59 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5RIMU520091
	for sigtran-archive@odin.ietf.org; Fri, 27 Jun 2003 14:22:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Vxri-0005Dv-9L; Fri, 27 Jun 2003 14:22:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VuPY-0002NW-Cb
	for sigtran@optimus.ietf.org; Fri, 27 Jun 2003 10:41:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27359
	for <sigtran@ietf.org>; Fri, 27 Jun 2003 09:22:24 -0400 (EDT)
From: agurmukhani@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VtBJ-0002cJ-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 09:22:25 -0400
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VtB7-0002bO-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 09:22:13 -0400
Received: from hindon.hss.co.in (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h5RCBtm09913
	for <sigtran@ietf.org>; Fri, 27 Jun 2003 17:41:55 +0530 (IST)
Received: from ultra.hss.co.in (ultra [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h5RCBnO09890;
	Fri, 27 Jun 2003 17:41:49 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h5RCFQ309693;
	Fri, 27 Jun 2003 17:45:26 +0530 (IST)
Subject: RE: [Sigtran] M3UA MIB Draft05: Loadsharing on CIC ,SSN
To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
Cc: sigtran@ietf.org
Date: Fri, 27 Jun 2003 17:38:51 +0530
Message-ID: <OF0B5DD3F3.CDBBADA5-ON65256D52.004227ED@hss.hns.com>
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 27/06/2003
 05:39:12 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>





Hi Javier


I agree with you that the two documents should be aligned .
But  what I wanted to emphasize upon  is that  CIC and SSN should not be
part of loadsharing criteria because these are ISUP and SCCP specific
parameters and M3UA should not parse and process MTP3-user specific data
for traffic distribution.
Even MTP3 does not loadshare user data on the basis of  any user specific
info(i.e CIC and SSN) but only on SLS which is the part of Routing lable.

Hence IMO these two should be removed from both the documents.

Regards
Anjali
www.hssworld.com
Hughes Software Systems.







"Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se> on
06/27/2003 12:15:02 PM

To:    Anjali Gurmukhani/HSS@HSS, sigtran@ietf.org
cc:

Subject:    RE: [Sigtran] M3UA MIB Draft05: Loadsharing on CIC ,SSN


Hi Anjali,

Thanks for your comment.

You are right saying that all CIC and SSN references were removed from the
draft in  M3UA IG v03. Anyhow, I don't see any damage in keeping this CIC
and SSN based loadsharing as another option. In fact it seems to me that
this change was a bug during the process of removing all the SSN and CIC
reference for the RK. But in any case both documents should be aligned.

What do you and others think? Do we remove CIC and SSN based loadsharing
from both documents? or do we allow it?

Thanks // Javier.


> -----Original Message-----
> From: agurmukhani@hss.hns.com [mailto:agurmukhani@hss.hns.com]
> Sent: jueves, 26 de junio de 2003 10:16
> To: sigtran@ietf.org
> Subject: [Sigtran] M3UA MIB Draft05: Loadsharing on CIC ,SSN
>
>
>
>
>
>
> Hi....
>
> I had a query related to the M3UA MIB draft 05.
> Both m3uaSpLshMethod OBJECT-TYPE and  m3uaStreamLshMethod OBJECT-TYPE
> mention CIC and SSN as basis of loadsharing
> In my opinion, there is no point keeping CIC and SSN  as
> loadsharing basis
> since this  would require  parsing  the data coming from the
> M3UA user.
> Also references to these as loadsharing basis have been
> removed from RFC as
> per Implementors guide 03.
> So IMO these should be removed from the MIB also.
>
>
> Thanks
> Anjali
> Hughes Software Systems
>
>
>
> "DISCLAIMER: This message is proprietary to Hughes Software
> Systems Limited
> (HSS) and is intended solely for the use of the individual to
> whom it is
> addressed. It may contain  privileged or confidential information and
> should not be circulated or used for any purpose other than
> for what it is
> intended. If you have received this message in error, please
> notify the
> originator immediately. If you are not the intended recipient, you are
> notified that you are strictly prohibited from using,
> copying, altering, or
> disclosing the contents of this message. HSS accepts no
> responsibility for
> loss or damage arising from the use of the information
> transmitted by this
> email including damage from virus."
>
>
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
 >




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



From exim@www1.ietf.org  Fri Jun 27 14:22:55 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09272
	for <sigtran-archive@odin.ietf.org>; Fri, 27 Jun 2003 14:22:37 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5RIM9t18342
	for sigtran-archive@odin.ietf.org; Fri, 27 Jun 2003 14:22:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VxrL-0004j3-L6; Fri, 27 Jun 2003 14:22:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VnPt-0000HR-U1
	for sigtran@optimus.ietf.org; Fri, 27 Jun 2003 03:13:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19784
	for <sigtran@ietf.org>; Fri, 27 Jun 2003 03:12:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VnPc-0001x9-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 03:12:48 -0400
Received: from auds953.usa.alcatel.com ([143.209.238.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VnPS-0001wx-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 03:12:38 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h5R7BdLZ013122;
	Fri, 27 Jun 2003 02:11:40 -0500 (CDT)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h5R7BH1C003857;
	Fri, 27 Jun 2003 02:11:17 -0500 (CDT)
Date: Fri, 27 Jun 2003 02:11:16 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: Nitin Tomar <nitty@ccpu.com>
cc: sigtran@ietf.org
Subject: Re: [Sigtran] AS Override question
In-Reply-To: <EPEMKGELBFBBOPEEIJNBAEBPCCAA.nitty@ccpu.com>
Message-ID: <Pine.SOL.4.10.10306270048070.15012-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


Nitin,

 This is just for your information.

 Basically state of an AS is determined with respect to an SGP.

  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******

On Thu, 26 Jun 2003, Nitin Tomar wrote:

> Hi All,
> One basic question related to AS state in Override mode.
> Scenario is:
> An SG is served by two SGPs (SGP-1 and SGP-2) and AS is served by two ASPs
> (ASP-1 and ASP-2),
> let's say ASP-1 is initially active for AS and it has sent ASP-ACTIVE
> message only towards
> SGP-1, and now the SGP-2 receives this ASP-ACTIVE from ASP-2 for the same
> AS.
> 
> What shall be the behavior at SG in response to ASP-ACTIVE from ASP-2,
> I can see three possibilities:
> a) SG (SGP-2) shall reject ASP-ACTIVE from ASP-2 as ASP-1 is already active
> towards SGP1,
>     if yes then what shall be the errorcode used in rejection message?
> 
How does SGP-2 know that AS is already ACTIVE for SGP1?
You mean to say SGP2 interacts with SGP1 as soon as it receives ASP ACTIV
message.If this is your answer then the AS state is determined with
respect to (SGP1+SGP2), this case SGP2 should send a NTFY message to ASP1
or SGP2 can instruct SGP1 to send a NTFY message to ASP1 to go down.

> b) SG shall mark the ASP-2 as active for AS and mark the ASP-1 as INACTIVE
> (and send the NTFY
>     message (ALT-ASP-ACTIVE) to ASP-1 but in this case SG will not know from
> which SGP
>     it shall send the NTFY message?).
refer above ans.
> 
> c) SG shall accept the ASP-2's request as well but in this case for a single
> AS in OVERRIDE mode there
>     will be two ASPs which are ACTIVE (each from different SGPs).
> 
refer above ans.

> It will be interesting to know that what other M3UA implementers think about
> handling above scenario.
Note: REG message is being sent by ASP before ASP ACTIVE message.
If AS state is determined with respect to (SGP1+SGP2), see the following
case
 1.ASP1 sends RK1 to SGP1
 2. SGP1 interacts with SGP2 and returns a unique RC1
 .
 .
 .

 1.ASP2 sends RK1 to SGP2
 2.SGP2 interacts with SGP1 and finds RK1 is already existing in SGP1 so
   SGP2 will send a REG RESP with error code to ASP2.

 3.By seening REG RESP with error code ASP2 should not be sending ASP
 ACTIV message to SGP2.


 like this, so many cases can be dealt.

 
> 
> Thanks
> Nitin
> 
> 


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



From exim@www1.ietf.org  Fri Jun 27 15:00:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13517
	for <sigtran-archive@odin.ietf.org>; Fri, 27 Jun 2003 15:00:31 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5RJ02331935
	for sigtran-archive@odin.ietf.org; Fri, 27 Jun 2003 15:00:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VyS1-0008Is-HM; Fri, 27 Jun 2003 15:00:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VyRB-0008HR-Bh
	for sigtran@optimus.ietf.org; Fri, 27 Jun 2003 14:59:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13448
	for <sigtran@ietf.org>; Fri, 27 Jun 2003 14:59:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VyRB-0005Me-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 14:59:09 -0400
Received: from web12803.mail.yahoo.com ([216.136.174.38])
	by ietf-mx with smtp (Exim 4.12)
	id 19VyQz-0005Le-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 14:58:58 -0400
Message-ID: <20030627185728.49154.qmail@web12803.mail.yahoo.com>
Received: from [208.255.120.2] by web12803.mail.yahoo.com via HTTP; Fri, 27 Jun 2003 11:57:28 PDT
Date: Fri, 27 Jun 2003 11:57:28 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA RFC 3332 default treatment of unallocated data
To: sigtran@ietf.org
In-Reply-To: <OF103D9B85.761870E4-ON65256D52.004F32F2@hss.hns.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Hi Kamesh,

I believe it is there because of CIC/SSN based RKs,
which could create cases, where SPMC/user part is
available even when an AS is not ACTIVE(for example
AS1=1-1-1 CIC=0-100 and AS2=1-1-1 CIC=101-200).
Probably the idea was, when AS2 is down, 1-1-1 ISUP is
still available -so no UPU for received traffic- but
traffic for AS2 should also be answered somehow.

In fact, because now CIC/SSN RKs are no more popular
-and if there are no other reason to have default
treatment-, maybe default treatment is also no more
necessary(?).

   Tolga 
--- kakaul@hss.hns.com wrote:
> 
> 
> 
> 
> Hi all,
>  Can some one share thoughts about what is the usage
> in practical sense of
> data routed through default AS from SG side.As M3UA
> RFC 3332 mentions about
> default treatment of unallocated data(data for which
> no routing key is
> configured) at SG side. What can ASP do with that
> data which has been
> routed to it by SG for default AS. I am sure while
> adding default treatment
> text in the RFC, usage of that in practical sense
> must be thought about. I
> want to know in what network scenario SG will
> receive unallocated data and
> after routing it to default AS what is the usage of
> that data at AS. Please
> comment.
> 
> Regards
> Kamesh Kaul
> www.hssworld.com
> Hughes Software Systems
> 
> "DISCLAIMER: This message is proprietary to Hughes
> Software Systems Limited
> (HSS) and is intended solely for the use of the
> individual to whom it is
> addressed. It may contain  privileged or
> confidential information and
> should not be circulated or used for any purpose
> other than for what it is
> intended. If you have received this message in
> error, please notify the
> originator immediately. If you are not the intended
> recipient, you are
> notified that you are strictly prohibited from
> using, copying, altering, or
> disclosing the contents of this message. HSS accepts
> no responsibility for
> loss or damage arising from the use of the
> information transmitted by this
> email including damage from virus."
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

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



From exim@www1.ietf.org  Fri Jun 27 15:29:30 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16906
	for <sigtran-archive@odin.ietf.org>; Fri, 27 Jun 2003 15:29:30 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5RJT1r11110
	for sigtran-archive@odin.ietf.org; Fri, 27 Jun 2003 15:29:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Vyu4-0002ss-H4; Fri, 27 Jun 2003 15:29:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VytQ-0002s8-8M
	for sigtran@optimus.ietf.org; Fri, 27 Jun 2003 15:28:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16833
	for <sigtran@ietf.org>; Fri, 27 Jun 2003 15:28:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VytO-0005d7-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 15:28:18 -0400
Received: from web12805.mail.yahoo.com ([216.136.174.40])
	by ietf-mx with smtp (Exim 4.12)
	id 19VytD-0005cd-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 15:28:07 -0400
Message-ID: <20030627190008.92479.qmail@web12805.mail.yahoo.com>
Received: from [208.255.120.2] by web12805.mail.yahoo.com via HTTP; Fri, 27 Jun 2003 12:00:08 PDT
Date: Fri, 27 Jun 2003 12:00:08 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] AS Override question
To: sigtran@ietf.org
In-Reply-To: <Pine.SOL.4.10.10306270048070.15012-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Samuel,

IMO, that you interprete SG as peer -instead of SGP-
for ASPTM procedures is not inline with RFC.

    Tolga
--- "Samuel Dur D. Jeyaseelan"
<sjeyasee@ssd.usa.alcatel.com> wrote:
> 
> Nitin,
> 
>  This is just for your information.
> 
>  Basically state of an AS is determined with respect
> to an SGP.
> 
>   Alcatel USA, Inc.                  Internet:
> <userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of
> Alcatel USA, Inc. *******
> 
> On Thu, 26 Jun 2003, Nitin Tomar wrote:
> 
> > Hi All,
> > One basic question related to AS state in Override
> mode.
> > Scenario is:
> > An SG is served by two SGPs (SGP-1 and SGP-2) and
> AS is served by two ASPs
> > (ASP-1 and ASP-2),
> > let's say ASP-1 is initially active for AS and it
> has sent ASP-ACTIVE
> > message only towards
> > SGP-1, and now the SGP-2 receives this ASP-ACTIVE
> from ASP-2 for the same
> > AS.
> > 
> > What shall be the behavior at SG in response to
> ASP-ACTIVE from ASP-2,
> > I can see three possibilities:
> > a) SG (SGP-2) shall reject ASP-ACTIVE from ASP-2
> as ASP-1 is already active
> > towards SGP1,
> >     if yes then what shall be the errorcode used
> in rejection message?
> > 
> How does SGP-2 know that AS is already ACTIVE for
> SGP1?
> You mean to say SGP2 interacts with SGP1 as soon as
> it receives ASP ACTIV
> message.If this is your answer then the AS state is
> determined with
> respect to (SGP1+SGP2), this case SGP2 should send a
> NTFY message to ASP1
> or SGP2 can instruct SGP1 to send a NTFY message to
> ASP1 to go down.
> 
> > b) SG shall mark the ASP-2 as active for AS and
> mark the ASP-1 as INACTIVE
> > (and send the NTFY
> >     message (ALT-ASP-ACTIVE) to ASP-1 but in this
> case SG will not know from
> > which SGP
> >     it shall send the NTFY message?).
> refer above ans.
> > 
> > c) SG shall accept the ASP-2's request as well but
> in this case for a single
> > AS in OVERRIDE mode there
> >     will be two ASPs which are ACTIVE (each from
> different SGPs).
> > 
> refer above ans.
> 
> > It will be interesting to know that what other
> M3UA implementers think about
> > handling above scenario.
> Note: REG message is being sent by ASP before ASP
> ACTIVE message.
> If AS state is determined with respect to
> (SGP1+SGP2), see the following
> case
>  1.ASP1 sends RK1 to SGP1
>  2. SGP1 interacts with SGP2 and returns a unique
> RC1
>  .
>  .
>  .
> 
>  1.ASP2 sends RK1 to SGP2
>  2.SGP2 interacts with SGP1 and finds RK1 is already
> existing in SGP1 so
>    SGP2 will send a REG RESP with error code to
> ASP2.
> 
>  3.By seening REG RESP with error code ASP2 should
> not be sending ASP
>  ACTIV message to SGP2.
> 
> 
>  like this, so many cases can be dealt.
> 
>  
> > 
> > Thanks
> > Nitin
> > 
> > 
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

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



From exim@www1.ietf.org  Fri Jun 27 15:37:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17355
	for <sigtran-archive@odin.ietf.org>; Fri, 27 Jun 2003 15:37:31 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5RJb3u12479
	for sigtran-archive@odin.ietf.org; Fri, 27 Jun 2003 15:37:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Vz1r-0003F4-0D; Fri, 27 Jun 2003 15:37:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Vz1p-0003E8-HI
	for sigtran@optimus.ietf.org; Fri, 27 Jun 2003 15:37:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17314
	for <sigtran@ietf.org>; Fri, 27 Jun 2003 15:36:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vz1o-0005h6-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 15:37:00 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[de4/hyrwnrNrK2Cdfp0fJQ4qJiUmUK7W])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vz1Y-0005h2-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 15:36:44 -0400
Received: from ns.pigworks.openss7.net (IDENT:WplXnt7trU2yypF/a4rrj+3G46brsDtB@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5RJaXX21492;
	Fri, 27 Jun 2003 13:36:33 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5RJaWE27219;
	Fri, 27 Jun 2003 13:36:32 -0600
Date: Fri, 27 Jun 2003 13:36:32 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: kakaul@hss.hns.com
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA RFC 3332 default treatment of unallocated data
Message-ID: <20030627133632.B24607@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: kakaul@hss.hns.com, sigtran@ietf.org
References: <OF103D9B85.761870E4-ON65256D52.004F32F2@hss.hns.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <OF103D9B85.761870E4-ON65256D52.004F32F2@hss.hns.com>; from kakaul@hss.hns.com on Fri, Jun 27, 2003 at 08:11:06PM +0530
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

kakaul,

Is is an OPTION.  If you cannot see a use for it, you do
not have to implement it.

--brian

kakaul@hss.hns.com wrote:                                                           (Fri, 27 Jun 2003 20:11:06)
> 
> 
> 
> 
> Hi all,
>  Can some one share thoughts about what is the usage in practical sense of
> data routed through default AS from SG side.As M3UA RFC 3332 mentions about
> default treatment of unallocated data(data for which no routing key is
> configured) at SG side. What can ASP do with that data which has been
> routed to it by SG for default AS. I am sure while adding default treatment
> text in the RFC, usage of that in practical sense must be thought about. I
> want to know in what network scenario SG will receive unallocated data and
> after routing it to default AS what is the usage of that data at AS. Please
> comment.
> 
> Regards
> Kamesh Kaul
> www.hssworld.com
> Hughes Software Systems
> 
> "DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
> (HSS) and is intended solely for the use of the individual to whom it is
> addressed. It may contain  privileged or confidential information and
> should not be circulated or used for any purpose other than for what it is
> intended. If you have received this message in error, please notify the
> originator immediately. If you are not the intended recipient, you are
> notified that you are strictly prohibited from using, copying, altering, or
> disclosing the contents of this message. HSS accepts no responsibility for
> loss or damage arising from the use of the information transmitted by this
> email including damage from virus."
> 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Fri Jun 27 15:38:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17462
	for <sigtran-archive@odin.ietf.org>; Fri, 27 Jun 2003 15:38:28 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5RJc0p15023
	for sigtran-archive@odin.ietf.org; Fri, 27 Jun 2003 15:38:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Vz2m-0003uC-Bx; Fri, 27 Jun 2003 15:38:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Vz1v-0003Jy-Ei
	for sigtran@optimus.ietf.org; Fri, 27 Jun 2003 15:37:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17262
	for <sigtran@ietf.org>; Fri, 27 Jun 2003 15:36:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vz0r-0005go-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 15:36:01 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[yVaBwz4fX8LaHVLeBnfL0+Heg5LNI202])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vz0b-0005fp-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 15:35:45 -0400
Received: from ns.pigworks.openss7.net (IDENT:pwf0shOh6ncjW3Khrj0vIwBfFhWyuQ9r@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5RJYDX21467;
	Fri, 27 Jun 2003 13:34:13 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5RJYDl27206;
	Fri, 27 Jun 2003 13:34:13 -0600
Date: Fri, 27 Jun 2003 13:34:13 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
Cc: "'agurmukhani@hss.hns.com'" <agurmukhani@hss.hns.com>, sigtran@ietf.org
Subject: Re: [Sigtran] M3UA MIB Draft05: Loadsharing on CIC ,SSN
Message-ID: <20030627133413.A24607@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>,
	"'agurmukhani@hss.hns.com'" <agurmukhani@hss.hns.com>,
	sigtran@ietf.org
References: <1AB3D30B989BF141BBD5C70057B2EF7C01B65CA2@eestqnt105.es.eu.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <1AB3D30B989BF141BBD5C70057B2EF7C01B65CA2@eestqnt105.es.eu.ericsson.se>; from javier.pastor-balbas@ece.ericsson.se on Fri, Jun 27, 2003 at 08:45:02AM +0200
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Javier,

CIC and SSN were removed from M3UA in the IG by concensus after
long discussion.

IMO the MIB should not extend the protocol it represents and
CIC and SSN should be removed from the MIB as well.

--brian

Javier Pastor-Balbas (ECE) wrote:                                                   (Fri, 27 Jun 2003 08:45:02)
> Hi Anjali, 
> 
> Thanks for your comment.
> 
> You are right saying that all CIC and SSN references were removed from the draft in  M3UA IG v03. Anyhow, I don't see any damage in keeping this CIC and SSN based loadsharing as another option. In fact it seems to me that this change was a bug during the process of removing all the SSN and CIC reference for the RK. But in any case both documents should be aligned. 
> 
> What do you and others think? Do we remove CIC and SSN based loadsharing from both documents? or do we allow it?
> 
> Thanks // Javier.
> 
> 
> > -----Original Message-----
> > From: agurmukhani@hss.hns.com [mailto:agurmukhani@hss.hns.com]
> > Sent: jueves, 26 de junio de 2003 10:16
> > To: sigtran@ietf.org
> > Subject: [Sigtran] M3UA MIB Draft05: Loadsharing on CIC ,SSN
> > 
> > 
> > 
> > 
> > 
> > 
> > Hi....
> > 
> > I had a query related to the M3UA MIB draft 05.
> > Both m3uaSpLshMethod OBJECT-TYPE and  m3uaStreamLshMethod OBJECT-TYPE
> > mention CIC and SSN as basis of loadsharing
> > In my opinion, there is no point keeping CIC and SSN  as 
> > loadsharing basis
> > since this  would require  parsing  the data coming from the 
> > M3UA user.
> > Also references to these as loadsharing basis have been 
> > removed from RFC as
> > per Implementors guide 03.
> > So IMO these should be removed from the MIB also.
> > 
> > 
> > Thanks
> > Anjali
> > Hughes Software Systems
> > 
> > 
> > 
> > "DISCLAIMER: This message is proprietary to Hughes Software 
> > Systems Limited
> > (HSS) and is intended solely for the use of the individual to 
> > whom it is
> > addressed. It may contain  privileged or confidential information and
> > should not be circulated or used for any purpose other than 
> > for what it is
> > intended. If you have received this message in error, please 
> > notify the
> > originator immediately. If you are not the intended recipient, you are
> > notified that you are strictly prohibited from using, 
> > copying, altering, or
> > disclosing the contents of this message. HSS accepts no 
> > responsibility for
> > loss or damage arising from the use of the information 
> > transmitted by this
> > email including damage from virus."
> > 
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Fri Jun 27 16:16:30 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18519
	for <sigtran-archive@odin.ietf.org>; Fri, 27 Jun 2003 16:16:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5RKG1E24639
	for sigtran-archive@odin.ietf.org; Fri, 27 Jun 2003 16:16:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VzdY-0006On-Sw; Fri, 27 Jun 2003 16:16:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VzAk-0004dC-9q
	for sigtran@optimus.ietf.org; Fri, 27 Jun 2003 15:46:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17908
	for <sigtran@ietf.org>; Fri, 27 Jun 2003 15:46:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VzAi-0005nP-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 15:46:12 -0400
Received: from web12801.mail.yahoo.com ([216.136.174.36])
	by ietf-mx with smtp (Exim 4.12)
	id 19VzAX-0005k2-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 15:46:01 -0400
Message-ID: <20030627194019.31393.qmail@web12801.mail.yahoo.com>
Received: from [208.255.120.2] by web12801.mail.yahoo.com via HTTP; Fri, 27 Jun 2003 12:40:19 PDT
Date: Fri, 27 Jun 2003 12:40:19 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] M3UA MIB Draft05: Loadsharing on CIC ,SSN
To: sigtran@ietf.org
In-Reply-To: <20030627133413.A24607@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,

I believe removing CIC/SSN was in the context using
them for RKs. Also for loadsharing?

    Tolga
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Javier,
> 
> CIC and SSN were removed from M3UA in the IG by
> concensus after
> long discussion.
> 
> IMO the MIB should not extend the protocol it
> represents and
> CIC and SSN should be removed from the MIB as well.
> 
> --brian
> 
> Javier Pastor-Balbas (ECE) wrote:                   
>                                (Fri, 27 Jun 2003
> 08:45:02)
> > Hi Anjali, 
> > 
> > Thanks for your comment.
> > 
> > You are right saying that all CIC and SSN
> references were removed from the draft in  M3UA IG
> v03. Anyhow, I don't see any damage in keeping this
> CIC and SSN based loadsharing as another option. In
> fact it seems to me that this change was a bug
> during the process of removing all the SSN and CIC
> reference for the RK. But in any case both documents
> should be aligned. 
> > 
> > What do you and others think? Do we remove CIC and
> SSN based loadsharing from both documents? or do we
> allow it?
> > 
> > Thanks // Javier.
> > 
> > 
> > > -----Original Message-----
> > > From: agurmukhani@hss.hns.com
> [mailto:agurmukhani@hss.hns.com]
> > > Sent: jueves, 26 de junio de 2003 10:16
> > > To: sigtran@ietf.org
> > > Subject: [Sigtran] M3UA MIB Draft05: Loadsharing
> on CIC ,SSN
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > Hi....
> > > 
> > > I had a query related to the M3UA MIB draft 05.
> > > Both m3uaSpLshMethod OBJECT-TYPE and 
> m3uaStreamLshMethod OBJECT-TYPE
> > > mention CIC and SSN as basis of loadsharing
> > > In my opinion, there is no point keeping CIC and
> SSN  as 
> > > loadsharing basis
> > > since this  would require  parsing  the data
> coming from the 
> > > M3UA user.
> > > Also references to these as loadsharing basis
> have been 
> > > removed from RFC as
> > > per Implementors guide 03.
> > > So IMO these should be removed from the MIB
> also.
> > > 
> > > 
> > > Thanks
> > > Anjali
> > > Hughes Software Systems
> > > 
> > > 
> > > 
> > > "DISCLAIMER: This message is proprietary to
> Hughes Software 
> > > Systems Limited
> > > (HSS) and is intended solely for the use of the
> individual to 
> > > whom it is
> > > addressed. It may contain  privileged or
> confidential information and
> > > should not be circulated or used for any purpose
> other than 
> > > for what it is
> > > intended. If you have received this message in
> error, please 
> > > notify the
> > > originator immediately. If you are not the
> intended recipient, you are
> > > notified that you are strictly prohibited from
> using, 
> > > copying, altering, or
> > > disclosing the contents of this message. HSS
> accepts no 
> > > responsibility for
> > > loss or damage arising from the use of the
> information 
> > > transmitted by this
> > > email including damage from virus."
> > > 
> > > 
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > 
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

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



From exim@www1.ietf.org  Fri Jun 27 18:30:41 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23560
	for <sigtran-archive@odin.ietf.org>; Fri, 27 Jun 2003 18:30:41 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5RMUFc28599
	for sigtran-archive@odin.ietf.org; Fri, 27 Jun 2003 18:30:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19W1jP-0007NP-7x; Fri, 27 Jun 2003 18:30:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19W0Tr-0002ij-5K
	for sigtran@optimus.ietf.org; Fri, 27 Jun 2003 17:10:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20788
	for <sigtran@ietf.org>; Fri, 27 Jun 2003 17:08:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19W0Sm-0006SO-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 17:08:56 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[zbtPSUAd6uHFrv716wUpBQvB4Rb3MgiR])
	by ietf-mx with esmtp (Exim 4.12)
	id 19W0SW-0006SH-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 17:08:40 -0400
Received: from ns.pigworks.openss7.net (IDENT:rGX2xJL+3O7opXf942J7QcnSKpzH9jPO@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5RL85X22917;
	Fri, 27 Jun 2003 15:08:05 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5RL84o28450;
	Fri, 27 Jun 2003 15:08:04 -0600
Date: Fri, 27 Jun 2003 15:08:04 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] M3UA MIB Draft05: Loadsharing on CIC ,SSN
Message-ID: <20030627150804.A28023@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030627133413.A24607@openss7.org> <20030627194019.31393.qmail@web12801.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030627194019.31393.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Fri, Jun 27, 2003 at 12:40:19PM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

M3UA does not specify loadsharing keys.  Neither should
the MIB.

--brian

Tolga Asveren wrote:                                                                 (Fri, 27 Jun 2003 12:40:19)
> Brian,
> 
> I believe removing CIC/SSN was in the context using
> them for RKs. Also for loadsharing?
> 
>     Tolga
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Javier,
> > 
> > CIC and SSN were removed from M3UA in the IG by
> > concensus after
> > long discussion.
> > 
> > IMO the MIB should not extend the protocol it
> > represents and
> > CIC and SSN should be removed from the MIB as well.
> > 
> > --brian
> > 
> > Javier Pastor-Balbas (ECE) wrote:                   
> >                                (Fri, 27 Jun 2003
> > 08:45:02)
> > > Hi Anjali, 
> > > 
> > > Thanks for your comment.
> > > 
> > > You are right saying that all CIC and SSN
> > references were removed from the draft in  M3UA IG
> > v03. Anyhow, I don't see any damage in keeping this
> > CIC and SSN based loadsharing as another option. In
> > fact it seems to me that this change was a bug
> > during the process of removing all the SSN and CIC
> > reference for the RK. But in any case both documents
> > should be aligned. 
> > > 
> > > What do you and others think? Do we remove CIC and
> > SSN based loadsharing from both documents? or do we
> > allow it?
> > > 
> > > Thanks // Javier.
> > > 
> > > 
> > > > -----Original Message-----
> > > > From: agurmukhani@hss.hns.com
> > [mailto:agurmukhani@hss.hns.com]
> > > > Sent: jueves, 26 de junio de 2003 10:16
> > > > To: sigtran@ietf.org
> > > > Subject: [Sigtran] M3UA MIB Draft05: Loadsharing
> > on CIC ,SSN
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > Hi....
> > > > 
> > > > I had a query related to the M3UA MIB draft 05.
> > > > Both m3uaSpLshMethod OBJECT-TYPE and 
> > m3uaStreamLshMethod OBJECT-TYPE
> > > > mention CIC and SSN as basis of loadsharing
> > > > In my opinion, there is no point keeping CIC and
> > SSN  as 
> > > > loadsharing basis
> > > > since this  would require  parsing  the data
> > coming from the 
> > > > M3UA user.
> > > > Also references to these as loadsharing basis
> > have been 
> > > > removed from RFC as
> > > > per Implementors guide 03.
> > > > So IMO these should be removed from the MIB
> > also.
> > > > 
> > > > 
> > > > Thanks
> > > > Anjali
> > > > Hughes Software Systems
> > > > 
> > > > 
> > > > 
> > > > "DISCLAIMER: This message is proprietary to
> > Hughes Software 
> > > > Systems Limited
> > > > (HSS) and is intended solely for the use of the
> > individual to 
> > > > whom it is
> > > > addressed. It may contain  privileged or
> > confidential information and
> > > > should not be circulated or used for any purpose
> > other than 
> > > > for what it is
> > > > intended. If you have received this message in
> > error, please 
> > > > notify the
> > > > originator immediately. If you are not the
> > intended recipient, you are
> > > > notified that you are strictly prohibited from
> > using, 
> > > > copying, altering, or
> > > > disclosing the contents of this message. HSS
> > accepts no 
> > > > responsibility for
> > > > loss or damage arising from the use of the
> > information 
> > > > transmitted by this
> > > > email including damage from virus."
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > 
> > > 
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > 
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> 
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Fri Jun 27 18:30:47 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23651
	for <sigtran-archive@odin.ietf.org>; Fri, 27 Jun 2003 18:30:47 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5RMULl29002
	for sigtran-archive@odin.ietf.org; Fri, 27 Jun 2003 18:30:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19W1jZ-0007Xf-J7; Fri, 27 Jun 2003 18:30:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19W1cp-0006ug-QJ
	for sigtran@optimus.ietf.org; Fri, 27 Jun 2003 18:23:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23110
	for <sigtran@ietf.org>; Fri, 27 Jun 2003 18:23:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19W1cm-0006jB-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 18:23:21 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[SH50Bao7ZjvGxyPowxw7ccua+Y1Ppbro])
	by ietf-mx with esmtp (Exim 4.12)
	id 19W1cX-0006j1-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 18:23:05 -0400
Received: from ns.pigworks.openss7.net (IDENT:KDuwNQBMQOLrwL9MLnkTipWPqM3OOZkl@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5RMMQX24113;
	Fri, 27 Jun 2003 16:22:26 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5RMMP229339;
	Fri, 27 Jun 2003 16:22:25 -0600
Date: Fri, 27 Jun 2003 16:22:25 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Ong, Lyndon" <LyOng@Ciena.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re:n+k issue
Message-ID: <20030627162225.B28023@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Ong, Lyndon" <LyOng@Ciena.com>, sigtran@ietf.org
References: <829F074A10F98943A218DC363D09C92A25020B@w2ksjexg06.oni.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <829F074A10F98943A218DC363D09C92A25020B@w2ksjexg06.oni.com>; from LyOng@Ciena.com on Fri, Jun 27, 2003 at 02:28:35PM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Lyndon,

Lyndon Ong wrote:                                                                   (Fri, 27 Jun 2003 14:28:35)
> Hi Brian,
> 
> I did not mean to imply that you had misinterpreted anything
> (and my email says "interpreted n+k differently").  No one is
> at fault, however the definition of n+k appears to be causing
> confusion.
> 
> Right now the behavior of the SG depends on the individual
> implementation depending interpretation of the RFC.

The RFC is not open to interpretation.  The behavior is specified.
The SG activates on the first ASP, but MAY, as an OPTION, choose
to withhold until it determines that sufficient ASPs are active.
In the case that it waits, it SHOULD withhold the NTFY(AS-Active)
until such a determination is made.  There is no room for
interpretation.  We agreed on several occasions the text is clear.

> If we tighten up the definition of n+k, this should allow
> both behaviors (send on 1 active or send on N active)
> but they would be identified as different cases.

Activating on the 1st ASP is not optional.  That the SG MAY wait
for sufficient ASPs active is the OPTIONAL behavior.

If someone wants to describe this OPTIONAL behavior in the IG,
please do.  However, the current proposal and Section 3.15
presumes to make the behavior MANDATORY rather than OPTIONAL.
That is against the long line of consensus.

Please start by striking the current proposal and section 3.15 and
follow with a new proposal that clarifies, rather than changes, the
requirements.

--brian

> 
> This seems to fit at least the latest rough consensus, but
> please chime in people if you disagree.
> 
> Cheers,
> 
> Lyndon
> 

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

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



From exim@www1.ietf.org  Fri Jun 27 19:17:46 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23561
	for <sigtran-archive@odin.ietf.org>; Fri, 27 Jun 2003 18:30:41 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5RMUFl28598
	for sigtran-archive@odin.ietf.org; Fri, 27 Jun 2003 18:30:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19W1jQ-0007Pd-Uk; Fri, 27 Jun 2003 18:30:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19W0jO-0003Yv-45
	for sigtran@optimus.ietf.org; Fri, 27 Jun 2003 17:26:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21065
	for <sigtran@ietf.org>; Fri, 27 Jun 2003 17:25:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19W0j6-0006WO-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 17:25:48 -0400
Received: from sjmail.ciena.com ([12.7.169.25] helo=w2ksjexg01.ciena.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19W0iw-0006W7-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 17:25:38 -0400
Received: by w2ksjexg01.ciena.com with Internet Mail Service (5.5.2653.19)
	id <NS8BH067>; Fri, 27 Jun 2003 14:25:00 -0700
Message-ID: <829F074A10F98943A218DC363D09C92A25020B@w2ksjexg06.oni.com>
From: "Ong, Lyndon" <LyOng@Ciena.com>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] Re:n+k issue
Date: Fri, 27 Jun 2003 14:28:35 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Hi Brian,

I did not mean to imply that you had misinterpreted anything
(and my email says "interpreted n+k differently").  No one is
at fault, however the definition of n+k appears to be causing
confusion.

Right now the behavior of the SG depends on the individual
implementation depending interpretation of the RFC.
If we tighten up the definition of n+k, this should allow
both behaviors (send on 1 active or send on N active)
but they would be identified as different cases.

This seems to fit at least the latest rough consensus, but
please chime in people if you disagree.

Cheers,

Lyndon

-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
Sent: Friday, June 27, 2003 12:45 AM
To: Ong, Lyndon
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re:n+k issue


Lyndon,

I don't think that I have misinterpreted anything as I authored half the text
in question and helped with the other half.  Consider the history of consensus
on this issue:

This began with the thread that I initiated entitled

  "M3UA-10: Example 5.1.4" that extended from Jan 2, 2002 to Jan 7, 2002.

This was a LC issue on M3UA.  The example showed in the "n+k" case the SG
sending NTFY(AS-Active) after this first (yes, the first) ASP activated for
the AS even thought "n=2" in the example.  I asked why the SG did not withhold
NTFY(AS-Active) until after "n=2" ASPs were active for the AS.

Greg proposed the text:

  An SGP or IPSP, upon reception of an ASP Active message for the first ASP in
  a Load-share AS, MAY choose not to direct traffic to a newly active ASP
  until it determines that there are sufficient resources to handle the
  expected load (e.g., until there are "n" ASPs in state ASP-ACTIVE in the
  AS)."

The MAY was intentional to permit the SG to activate on the first ASP.

I proposed that the SG then withhold the NTFY(AS-Active) until after it
directs traffic if the SG follows the MAY and waits for sufficient ASPs.  (The
point of the original issue.)

It was agreed on this thread that some implementations would want to wait for
'n' and some would want to activate immediately, relying on the congestion and
flow controls of the ASP and MTP-User parts to handle any potential traffic
overloads.

Consensus was reached in the LC process and the text was adopted in M3UA-11.

On the thread:

  "n+k redundancy + NTFY  changes" from Jan 30, 2002 to Feb 1, 2002.

Tolga (surprising now) asks John Loughney to echo the changes of these two
passages into SUA and the same procedures are incorporated into SUA by
consensus.

On the thread:

  "m3ua-implementors-guidev00,  OPC list + missing issues" from March 31, 2002
  through April 10, 2002.

The discussion of "n+k" is brought up again by Tolga.  In this thread, Vikas,
Ken Morneault, and I agree that the text is clear.  Vikas and I also defend
the text.  Tolga is the only dissenter.  Umesh asks for clarification in the
IG, but it is agreed that the text in the RFC is clear.

On the thread:

  "m3ua: IG : n+k redundancy" from Jun 21, 2002 to Jun 26, 2002
  and
  "m2ua: IG : n+k redundancy - AS state machine"

Tolga brings up the same arguments again.  Javier's conclusion from previous
discussion initially was that no change was necessary.  Javier and Tolga then
go on to have a discussion between the two of them.  (I would have disagreed
in the middle of this, as consensus was already reached twice, but I was in a
U-haul between Texas and Alberta for the remainder of their exchange).  No one
else commented on the matter.

On the next thread:

  "I-D ACTION:draft-ietf-sigtran-m3ua-implementors-guide-02.txt"

I initiated a number of issued on the new release of the IG including the
section 3.15 which was not included by consensus, but only on the basis of
this brief discussion between Javier and Tolga.   I pointed out to Ken the
previous consensus points on this matter and he agreed to review the mail
threads.  Ken did not comment further.

Next on the thread:

  "M3UA Notify message" from Feb 12, 2003 to Feb 26, 2003
  (rejoined recently and extending from Jun 18, 2003 to Jun 26, 2003)

Srini asks some questions about Notify messages and n+k comes up again.  Srini
agrees that active ASPs < n corresponds to the AS-ACTIVE state as in the RFC
and that the ASP should use congestion and flow control procedures to limit
traffic if it is presented with too much traffic.  Bijoy agrees as well.
Srivats agrees as well with not stopping traffic #ASPs < n.  Samuel also
agrees with not stopping traffic #ASPs < n.  Javier agrees to the MAY.

The thread is rejoined recently.  The only dissenting voice on the thread is
Tolga (and most recently Javier).

Now, it appears to me that Tolga has brought this up on 4 or 5 separate
occasions, on each occasion (except when I was in the U-Haul) consensus was
that the existing RFC text stands and that the SG can activate with the first
ASP active in the AS regardless of 'n' or MAY wait for 'n' and SHOULD withhold
then NTFY(AS-Active) is reiterated.

10 separate individuals have come to consensus 4 times on this issue,
including last call, and the result was always that the RFC stands.  This text
also appears by consensus (as proposed by Tolga!) in SUA.  In subsequent
discussions Tolga was the only dissenting voice.  It appears Tolga wants 'n'
to be required (only) and never preferred.

The existing text allows it to be preferred or required depending on SG
implementation or configuration.  Although Tolga states that "1+k" required is
the same as preferred, the Notify(Insufficient ASPs Active in AS) behavior is
different for "1+k" required than it is for "n+k" preferred.

10 separate individual disagree with Tolga's proposals over the cited threads
(he disagrees with himself on a couple of occasions too).

Section 3.15 was NOT included on the consensus of the WG and stands against
the consensus of the WG.  There is no rough consensus to adopt the proposal as
evidenced by the archive.

As the WG has consistently spoken against these changes over the last 18
months, please do the right thing and strike Section 3.15 from the IG.

Thank you.

--brian


Lyndon Ong wrote:                                                                   (Thu, 26 Jun 2003 18:16:18)
> Hi Folks,
> 
> At the risk of blowing up the issue (although I think we
> are there already), I would like to make the following
> points:
> 
> -- the issue of n+k is in fact confusing in the RFC text
>   - n+k as defined in the introduction is subject to multiple
>     interpretations
>   - n+k has the following procedure defined in 4.3.4.3 -
>   "For the n+k redundancy case, ASPs which are in that AS should
>    coordinate among themselves the number of active ASPs in the AS, and
>    should start sending traffic only after n ASPs are active."
>     This seems to imply that traffic should only be resumed after
>     n ASPs are active, even if traffic is sent from the SG the ASPs
>     should not reply.
>   - the examples in 5.1.4 and 5.2.3 also appear to reflect this usage.
>   - n+k is not clearly reflected in the current state diagrams
> 
> Given that this appears to be a valid issue with the RFC and
> there seems to be a greater weight of opinion on the side of
> the proposed text I believe that the rough consensus exists
> supporting the proposed text in the M3UA implementor's guide draft.
> 
> However, I understand the concern on the part of some folks
> that have interpreted n+k differently.  As a result I think
> we also should add clarifying text to the n+k definition in
> 1.4.4.1 stating that in this definition, traffic is not sent
> until "n" ASPs are active, and that the "k" ASPs may be either 
> active at the same time as "n" or kept inactive until needed
> due to a failed or unavailable ASP.  Hopefully that will 
> cover other situations acceptably.
> 
> Cheers,
> 
> L. Ong

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

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



From exim@www1.ietf.org  Fri Jun 27 20:10:32 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27329
	for <sigtran-archive@odin.ietf.org>; Fri, 27 Jun 2003 20:10:32 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5S0A3U07430
	for sigtran-archive@odin.ietf.org; Fri, 27 Jun 2003 20:10:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19W3I2-0001vE-8R; Fri, 27 Jun 2003 20:10:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19W3Ho-0001um-04
	for sigtran@optimus.ietf.org; Fri, 27 Jun 2003 20:09:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27309
	for <sigtran@ietf.org>; Fri, 27 Jun 2003 20:09:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19W3HX-0007eY-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 20:09:31 -0400
Received: from sjmail.ciena.com ([12.7.169.25] helo=w2ksjexg01.ciena.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19W3HM-0007eQ-00
	for sigtran@ietf.org; Fri, 27 Jun 2003 20:09:20 -0400
Received: by w2ksjexg01.ciena.com with Internet Mail Service (5.5.2653.19)
	id <NS8B2B9Q>; Fri, 27 Jun 2003 16:08:30 -0700
Message-ID: <829F074A10F98943A218DC363D09C92A25020D@w2ksjexg06.oni.com>
From: "Ong, Lyndon" <LyOng@Ciena.com>
To: "'bidulock@openss7.org'" <bidulock@openss7.org>
Cc: sigtran@ietf.org
Subject: RE: [Sigtran] Re:n+k issue
Date: Fri, 27 Jun 2003 16:12:06 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Hi Brian,

Hmm, I suppose you could argue that the RFC wording is not open
to interpretation, however the conditions under which
the "MAY" is exercised are at the moment not clearly 
defined.  Also the definition of "n+k" appears to be
inconsistent, in that even if the SG sends messages on the 
first active ASP, the ASP "should" start sending messages
only after "n" ASPs are active.

I read your concern, however, as to the capability at the
SG to restrict traffic to the ASPs as being OPTIONAL in the
original RFC and becoming more a "mandatory" function
in the proposed IG text.  Perhaps we can work on the text
to address that after the next issue.

Cheers,

Lyndon

-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
Sent: Friday, June 27, 2003 3:22 PM
To: Ong, Lyndon
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re:n+k issue


Lyndon,

Lyndon Ong wrote:                                                                   (Fri, 27 Jun 2003 14:28:35)
> Hi Brian,
> 
> I did not mean to imply that you had misinterpreted anything
> (and my email says "interpreted n+k differently").  No one is
> at fault, however the definition of n+k appears to be causing
> confusion.
> 
> Right now the behavior of the SG depends on the individual
> implementation depending interpretation of the RFC.

The RFC is not open to interpretation.  The behavior is specified.
The SG activates on the first ASP, but MAY, as an OPTION, choose
to withhold until it determines that sufficient ASPs are active.
In the case that it waits, it SHOULD withhold the NTFY(AS-Active)
until such a determination is made.  There is no room for
interpretation.  We agreed on several occasions the text is clear.

> If we tighten up the definition of n+k, this should allow
> both behaviors (send on 1 active or send on N active)
> but they would be identified as different cases.

Activating on the 1st ASP is not optional.  That the SG MAY wait
for sufficient ASPs active is the OPTIONAL behavior.

If someone wants to describe this OPTIONAL behavior in the IG,
please do.  However, the current proposal and Section 3.15
presumes to make the behavior MANDATORY rather than OPTIONAL.
That is against the long line of consensus.

Please start by striking the current proposal and section 3.15 and
follow with a new proposal that clarifies, rather than changes, the
requirements.

--brian

> 
> This seems to fit at least the latest rough consensus, but
> please chime in people if you disagree.
> 
> Cheers,
> 
> Lyndon
> 

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

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



From exim@www1.ietf.org  Sat Jun 28 02:36:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16625
	for <sigtran-archive@odin.ietf.org>; Sat, 28 Jun 2003 02:36:30 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5S6Z6x02866
	for sigtran-archive@odin.ietf.org; Sat, 28 Jun 2003 02:35:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19W9Id-0000j0-Nh; Sat, 28 Jun 2003 02:35:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19W9IK-0000iM-Qg
	for sigtran@optimus.ietf.org; Sat, 28 Jun 2003 02:34:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16547
	for <sigtran@ietf.org>; Sat, 28 Jun 2003 02:34:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19W9I2-0001f2-00
	for sigtran@ietf.org; Sat, 28 Jun 2003 02:34:26 -0400
Received: from auds953.usa.alcatel.com ([143.209.238.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 19W9Hr-0001eV-00
	for sigtran@ietf.org; Sat, 28 Jun 2003 02:34:15 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h5S6WvLX023428
	for <sigtran@ietf.org>; Sat, 28 Jun 2003 01:32:58 -0500 (CDT)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h5S6W71C026421
	for <sigtran@ietf.org>; Sat, 28 Jun 2003 01:32:07 -0500 (CDT)
Date: Sat, 28 Jun 2003 01:32:07 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: sigtran@ietf.org
In-Reply-To: <20030627133413.A24607@openss7.org>
Message-ID: <Pine.SOL.4.10.10306280123510.24516-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Sigtran] [m3ua] MIB CIC+SSN+DPC - REMOVE
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


Pastor,

  References to CIC and SSN were removed from RFC after a long discussion.
  I agree to remove CIC and SSN from MIB.

  Load sharing on DPC also can be removed from MIB as nobody is able
  to expain the prior mail below.

----  
Date: Sun, 13 Apr 2003 22:50:12 -0500 (CDT)
From: Samuel Dur D. Jeyaseelan <sjeyasee@ssd.usa.alcatel.com>
To: sigtran@ietf.org
Subject: Re: [Sigtran] [m3ua]-ldshar basing on dpc
----

--Samuel
 


  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******



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



From exim@www1.ietf.org  Sat Jun 28 02:40:30 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16756
	for <sigtran-archive@odin.ietf.org>; Sat, 28 Jun 2003 02:40:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5S6e1804916
	for sigtran-archive@odin.ietf.org; Sat, 28 Jun 2003 02:40:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19W9NQ-0001H3-W9; Sat, 28 Jun 2003 02:40:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19W9LH-0001DI-Ku
	for sigtran@optimus.ietf.org; Sat, 28 Jun 2003 02:39:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16669
	for <sigtran@ietf.org>; Sat, 28 Jun 2003 02:37:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19W9LE-0001gR-00
	for sigtran@ietf.org; Sat, 28 Jun 2003 02:37:44 -0400
Received: from auds953.usa.alcatel.com ([143.209.238.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 19W9L3-0001gJ-00
	for sigtran@ietf.org; Sat, 28 Jun 2003 02:37:33 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h5S6avLX023562;
	Sat, 28 Jun 2003 01:36:57 -0500 (CDT)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h5S6aA1C026878;
	Sat, 28 Jun 2003 01:36:11 -0500 (CDT)
Date: Sat, 28 Jun 2003 01:36:10 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: "Ong, Lyndon" <LyOng@Ciena.com>, sigtran@ietf.org
Subject: Re: [Sigtran] Re:n+k issue
In-Reply-To: <20030627014505.A14028@openss7.org>
Message-ID: <Pine.SOL.4.10.10306280133100.24516-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


Brian,

question in-line.
 
  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******

On Fri, 27 Jun 2003, Brian F. G. Bidulock wrote:

> Lyndon,
> 
> I don't think that I have misinterpreted anything as I authored half the text
> in question and helped with the other half.  Consider the history of consensus
> on this issue:
> 
> This began with the thread that I initiated entitled
> 
>   "M3UA-10: Example 5.1.4" that extended from Jan 2, 2002 to Jan 7, 2002.
> 
> This was a LC issue on M3UA.  The example showed in the "n+k" case the SG
> sending NTFY(AS-Active) after this first (yes, the first) ASP activated for
> the AS even thought "n=2" in the example.  I asked why the SG did not withhold
> NTFY(AS-Active) until after "n=2" ASPs were active for the AS.
> 
> Greg proposed the text:
> 
>   An SGP or IPSP, upon reception of an ASP Active message for the first ASP in
>   a Load-share AS, MAY choose not to direct traffic to a newly active ASP
>   until it determines that there are sufficient resources to handle the
>   expected load (e.g., until there are "n" ASPs in state ASP-ACTIVE in the
>   AS)."
> 
> The MAY was intentional to permit the SG to activate on the first ASP.
> 
> I proposed that the SG then withhold the NTFY(AS-Active) until after it
> directs traffic if the SG follows the MAY and waits for sufficient ASPs.  (The
> point of the original issue.)
> 
> It was agreed on this thread that some implementations would want to wait for
> 'n' and some would want to activate immediately, relying on the congestion and
> flow controls of the ASP and MTP-User parts to handle any potential traffic
> overloads.
> 
> Consensus was reached in the LC process and the text was adopted in M3UA-11.
> 
> On the thread:
> 
>   "n+k redundancy + NTFY  changes" from Jan 30, 2002 to Feb 1, 2002.
> 
> Tolga (surprising now) asks John Loughney to echo the changes of these two
> passages into SUA and the same procedures are incorporated into SUA by
> consensus.
> 
> On the thread:
> 
>   "m3ua-implementors-guidev00,  OPC list + missing issues" from March 31, 2002
>   through April 10, 2002.
> 
> The discussion of "n+k" is brought up again by Tolga.  In this thread, Vikas,
> Ken Morneault, and I agree that the text is clear.  Vikas and I also defend
> the text.  Tolga is the only dissenter.  Umesh asks for clarification in the
> IG, but it is agreed that the text in the RFC is clear.
> 
> On the thread:
> 
>   "m3ua: IG : n+k redundancy" from Jun 21, 2002 to Jun 26, 2002
>   and
>   "m2ua: IG : n+k redundancy - AS state machine"
> 
> Tolga brings up the same arguments again.  Javier's conclusion from previous
> discussion initially was that no change was necessary.  Javier and Tolga then
> go on to have a discussion between the two of them.  (I would have disagreed
> in the middle of this, as consensus was already reached twice, but I was in a
> U-haul between Texas and Alberta for the remainder of their exchange).  No one
> else commented on the matter.
> 
> On the next thread:
> 
>   "I-D ACTION:draft-ietf-sigtran-m3ua-implementors-guide-02.txt"
> 
> I initiated a number of issued on the new release of the IG including the
> section 3.15 which was not included by consensus, but only on the basis of
> this brief discussion between Javier and Tolga.   I pointed out to Ken the
> previous consensus points on this matter and he agreed to review the mail
> threads.  Ken did not comment further.
> 
> Next on the thread:
> 
>   "M3UA Notify message" from Feb 12, 2003 to Feb 26, 2003
>   (rejoined recently and extending from Jun 18, 2003 to Jun 26, 2003)
> 
> Srini asks some questions about Notify messages and n+k comes up again.  Srini
> agrees that active ASPs < n corresponds to the AS-ACTIVE state as in the RFC
> and that the ASP should use congestion and flow control procedures to limit
> traffic if it is presented with too much traffic.  Bijoy agrees as well.
> Srivats agrees as well with not stopping traffic #ASPs < n.  Samuel also
> agrees with not stopping traffic #ASPs < n.  Javier agrees to the MAY.

Could you please give me a pointer where i agreed?

--Samuel

> 
> The thread is rejoined recently.  The only dissenting voice on the thread is
> Tolga (and most recently Javier).
> 
> Now, it appears to me that Tolga has brought this up on 4 or 5 separate
> occasions, on each occasion (except when I was in the U-Haul) consensus was
> that the existing RFC text stands and that the SG can activate with the first
> ASP active in the AS regardless of 'n' or MAY wait for 'n' and SHOULD withhold
> then NTFY(AS-Active) is reiterated.
> 
> 10 separate individuals have come to consensus 4 times on this issue,
> including last call, and the result was always that the RFC stands.  This text
> also appears by consensus (as proposed by Tolga!) in SUA.  In subsequent
> discussions Tolga was the only dissenting voice.  It appears Tolga wants 'n'
> to be required (only) and never preferred.
> 
> The existing text allows it to be preferred or required depending on SG
> implementation or configuration.  Although Tolga states that "1+k" required is
> the same as preferred, the Notify(Insufficient ASPs Active in AS) behavior is
> different for "1+k" required than it is for "n+k" preferred.
> 
> 10 separate individual disagree with Tolga's proposals over the cited threads
> (he disagrees with himself on a couple of occasions too).
> 
> Section 3.15 was NOT included on the consensus of the WG and stands against
> the consensus of the WG.  There is no rough consensus to adopt the proposal as
> evidenced by the archive.
> 
> As the WG has consistently spoken against these changes over the last 18
> months, please do the right thing and strike Section 3.15 from the IG.
> 
> Thank you.
> 
> --brian
> 
> 
> Lyndon Ong wrote:                                                                   (Thu, 26 Jun 2003 18:16:18)
> > Hi Folks,
> > 
> > At the risk of blowing up the issue (although I think we
> > are there already), I would like to make the following
> > points:
> > 
> > -- the issue of n+k is in fact confusing in the RFC text
> >   - n+k as defined in the introduction is subject to multiple
> >     interpretations
> >   - n+k has the following procedure defined in 4.3.4.3 -
> >   "For the n+k redundancy case, ASPs which are in that AS should
> >    coordinate among themselves the number of active ASPs in the AS, and
> >    should start sending traffic only after n ASPs are active."
> >     This seems to imply that traffic should only be resumed after
> >     n ASPs are active, even if traffic is sent from the SG the ASPs
> >     should not reply.
> >   - the examples in 5.1.4 and 5.2.3 also appear to reflect this usage.
> >   - n+k is not clearly reflected in the current state diagrams
> > 
> > Given that this appears to be a valid issue with the RFC and
> > there seems to be a greater weight of opinion on the side of
> > the proposed text I believe that the rough consensus exists
> > supporting the proposed text in the M3UA implementor's guide draft.
> > 
> > However, I understand the concern on the part of some folks
> > that have interpreted n+k differently.  As a result I think
> > we also should add clarifying text to the n+k definition in
> > 1.4.4.1 stating that in this definition, traffic is not sent
> > until "n" ASPs are active, and that the "k" ASPs may be either 
> > active at the same time as "n" or kept inactive until needed
> > due to a failed or unavailable ASP.  Hopefully that will 
> > cover other situations acceptably.
> > 
> > Cheers,
> > 
> > L. Ong
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 


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



From exim@www1.ietf.org  Sat Jun 28 03:30:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17737
	for <sigtran-archive@odin.ietf.org>; Sat, 28 Jun 2003 03:30:31 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5S7U2X18021
	for sigtran-archive@odin.ietf.org; Sat, 28 Jun 2003 03:30:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19WA9p-0004gQ-FV; Sat, 28 Jun 2003 03:30:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19WA9n-0004g5-FO
	for sigtran@optimus.ietf.org; Sat, 28 Jun 2003 03:29:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17726
	for <sigtran@ietf.org>; Sat, 28 Jun 2003 03:29:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WA9l-0001yx-00
	for sigtran@ietf.org; Sat, 28 Jun 2003 03:29:57 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[c60crx95kf0e+zT3q93Hyegm/VmiyVKw])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WA9V-0001yt-00
	for sigtran@ietf.org; Sat, 28 Jun 2003 03:29:41 -0400
Received: from ns.pigworks.openss7.net (IDENT:ByGnmx9wrcduSZbU9/mZqA+1+e8J5l7F@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5S7THX32303
	for <sigtran@ietf.org>; Sat, 28 Jun 2003 01:29:17 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5S7TGG03973
	for sigtran@ietf.org; Sat, 28 Jun 2003 01:29:16 -0600
Date: Sat, 28 Jun 2003 01:29:16 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: sigtran@ietf.org
Subject: Re: [Sigtran] Re:n+k issue
Message-ID: <20030628012916.A3873@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: sigtran@ietf.org
References: <20030627014505.A14028@openss7.org> <Pine.SOL.4.10.10306280133100.24516-100000@sun2594.ssd.usa.alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.4.10.10306280133100.24516-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Sat, Jun 28, 2003 at 01:36:10AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Samuel,

Samuel Dur D. Jeyaseelan wrote:                                                     (Sat, 28 Jun 2003 01:36:10)

> > 
> > Next on the thread:
> > 
> >   "M3UA Notify message" from Feb 12, 2003 to Feb 26, 2003
> >   (rejoined recently and extending from Jun 18, 2003 to Jun 26, 2003)
> > 
> > Srini asks some questions about Notify messages and n+k comes up again.  Srini
> > agrees that active ASPs < n corresponds to the AS-ACTIVE state as in the RFC
> > and that the ASP should use congestion and flow control procedures to limit
> > traffic if it is presented with too much traffic.  Bijoy agrees as well.
> > Srivats agrees as well with not stopping traffic #ASPs < n.  Samuel also
> > agrees with not stopping traffic #ASPs < n.  Javier agrees to the MAY.
> 
> Could you please give me a pointer where i agreed?
> 
> --Samuel
> 

Correct me if I'm wrong but it appears in the following two statements that
you agreed to not stopping traffic for #ASPs < n.

> Date: Tue, 25 Feb 2003 08:11:31 -0600 (CST)
> From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
> cc: "Brian F. G. Bidulock" <bidulock@openss7.org>,
>    TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
> Subject: RE: [Sigtran] Re: M3UA Notify message
> 
> Javier,
> 
>   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> 
> On Tue, 25 Feb 2003, Javier Pastor-Balbas (ECE) wrote:
> 
> > Hi Samuel et al., 
> > 
> > Take into account that if you define two ASes:
> > - AS1 DPC+SLS1  with two ASPs (ASP1 and ASP2) and redundancy: n=1 k=1
> > - AS2 DPC+SLS2  with two ASPs (ASP1 and ASP2) and redundancy: n=1 k=1
> > 
> > And 
> > - ASP1 active for AS1 and backup for AS2
> > - ASP2 active for AS2 and backup for AS1
> > 
> > You get the desired behaviour. This case can be solved with a right 
>   network configuration without changing the current "required"
>   qualification for "n".
> > 
> > 
> > 
> > Apart from this, 
> > 
> > I would say that a compromise option would consist of considering "n" as 
>   the normal working case, but make it implementation dependent (maybe
> configurable) whether an implementation may have more than "n" ASPs 
>  working at the same time for an AS, and whether the SG keeps working when
> the number of ASP is under "n". We could make a recommendation with "MAY" 
> allowing both options.
> >
> [Samuel] Yes .SG keeps working when n=1 or n >=2.
> but current RFC says that SG NOTIFIES 'k' ASP to become active only
> when n<2 and it does not say what will happen when SG requires more than
> 'n' ASP to handle the traffic 't+1'.
>  
> > But now, the problem comes with the AS state machine. If we agree upon here,
>  we could say the AS is ACTIVE in the range n_min to n_max, where these two
>  values are configurable.
> > 
> [Samuel] To handle the 'normal(best) traffic T' SG requires 'n=2' ASPs.
> In the course of traffic if 'n became 1'(means ASP1 failed), here SG can
> handle the traffic with 'n=1' ASP. 
> So only intially SG requires 'n=2' ASPs to make the AS state as ACTIVE
> and 'n=2' is fed during configuration.But while handling traffic due to 
> failure of ASP1 'n' becomes '1', here still AS is ACTIVE with single ASP.
> 
> --Samuel

[snip]

> Date: Tue, 25 Feb 2003 06:08:39 -0600 (CST)
> From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
> cc: sigtran@ietf.org
> Subject: Re: [Sigtran] Re: M3UA Notify message
> 
> 
> Tolga,
> 
> From this thread we can end up with two kinds of SGs.
> 
> The SG which decides to stop taking the traffic when 'n' changed
> from '2' to '1'.
> 
> The other SG which decides to continue the traffic  when 'n' 
> changed from '2' to '1'.
> 
> When performance is considered, i think everyone will prefer second case.
> Second case follows the existing network standards.But first case does
> not follow any standards.

[snip]


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

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



From exim@www1.ietf.org  Sat Jun 28 04:27:33 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18650
	for <sigtran-archive@odin.ietf.org>; Sat, 28 Jun 2003 04:27:32 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5S8R3901926
	for sigtran-archive@odin.ietf.org; Sat, 28 Jun 2003 04:27:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19WB2z-0000Ug-CX; Sat, 28 Jun 2003 04:27:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19WB2P-0000UJ-0K
	for sigtran@optimus.ietf.org; Sat, 28 Jun 2003 04:26:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18643
	for <sigtran@ietf.org>; Sat, 28 Jun 2003 04:26:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WB27-0002A9-00
	for sigtran@ietf.org; Sat, 28 Jun 2003 04:26:07 -0400
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WB1w-0002A1-00
	for sigtran@ietf.org; Sat, 28 Jun 2003 04:25:56 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h5S8OxB3018304;
	Sat, 28 Jun 2003 03:24:59 -0500 (CDT)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h5S8Ok1C009620;
	Sat, 28 Jun 2003 03:24:46 -0500 (CDT)
Date: Sat, 28 Jun 2003 03:24:46 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: "Brian F. G. Bidulock" <bidulock@openss7.org>
cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re:n+k issue
In-Reply-To: <20030628012916.A3873@openss7.org>
Message-ID: <Pine.SOL.4.10.10306280313030.24516-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


Brian,

In this attached mail i have said that 'n=2'(example) is mandatory at
start case.
This is what Javier,Tolga are also proposing to make 'n=2' as mandatory
at start case.

SGP will stop taking traffic when # ASPS < n at start case.

But while handling the traffic if # ASPs < n , this will not stop the
traffic.This is what i comprised in this mail.

So from the beginning i disagree to make an AS as active as soon as a
single ASP goes to ACTIVE state in n+k reduntancy case.

--Samuel

  Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
  1000 Coit Road, Plano, Texas 75075
  ******* The opinions expressed are not those of Alcatel USA, Inc. *******

On Sat, 28 Jun 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> Samuel Dur D. Jeyaseelan wrote:                                                     (Sat, 28 Jun 2003 01:36:10)
> 
> > > 
> > > Next on the thread:
> > > 
> > >   "M3UA Notify message" from Feb 12, 2003 to Feb 26, 2003
> > >   (rejoined recently and extending from Jun 18, 2003 to Jun 26, 2003)
> > > 
> > > Srini asks some questions about Notify messages and n+k comes up again.  Srini
> > > agrees that active ASPs < n corresponds to the AS-ACTIVE state as in the RFC
> > > and that the ASP should use congestion and flow control procedures to limit
> > > traffic if it is presented with too much traffic.  Bijoy agrees as well.
> > > Srivats agrees as well with not stopping traffic #ASPs < n.  Samuel also
> > > agrees with not stopping traffic #ASPs < n.  Javier agrees to the MAY.
> > 
> > Could you please give me a pointer where i agreed?
> > 
> > --Samuel
> > 
> 
> Correct me if I'm wrong but it appears in the following two statements that
> you agreed to not stopping traffic for #ASPs < n.
> 
> > Date: Tue, 25 Feb 2003 08:11:31 -0600 (CST)
> > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
> > cc: "Brian F. G. Bidulock" <bidulock@openss7.org>,
> >    TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
> > Subject: RE: [Sigtran] Re: M3UA Notify message
> > 
> > Javier,
> > 
> >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> > 
> > On Tue, 25 Feb 2003, Javier Pastor-Balbas (ECE) wrote:
> > 
> > > Hi Samuel et al., 
> > > 
> > > Take into account that if you define two ASes:
> > > - AS1 DPC+SLS1  with two ASPs (ASP1 and ASP2) and redundancy: n=1 k=1
> > > - AS2 DPC+SLS2  with two ASPs (ASP1 and ASP2) and redundancy: n=1 k=1
> > > 
> > > And 
> > > - ASP1 active for AS1 and backup for AS2
> > > - ASP2 active for AS2 and backup for AS1
> > > 
> > > You get the desired behaviour. This case can be solved with a right 
> >   network configuration without changing the current "required"
> >   qualification for "n".
> > > 
> > > 
> > > 
> > > Apart from this, 
> > > 
> > > I would say that a compromise option would consist of considering "n" as 
> >   the normal working case, but make it implementation dependent (maybe
> > configurable) whether an implementation may have more than "n" ASPs 
> >  working at the same time for an AS, and whether the SG keeps working when
> > the number of ASP is under "n". We could make a recommendation with "MAY" 
> > allowing both options.
> > >
> > [Samuel] Yes .SG keeps working when n=1 or n >=2.
> > but current RFC says that SG NOTIFIES 'k' ASP to become active only
> > when n<2 and it does not say what will happen when SG requires more than
> > 'n' ASP to handle the traffic 't+1'.
> >  
> > > But now, the problem comes with the AS state machine. If we agree upon here,
> >  we could say the AS is ACTIVE in the range n_min to n_max, where these two
> >  values are configurable.
> > > 
> > [Samuel] To handle the 'normal(best) traffic T' SG requires 'n=2' ASPs.
> > In the course of traffic if 'n became 1'(means ASP1 failed), here SG can
> > handle the traffic with 'n=1' ASP. 
> > So only intially SG requires 'n=2' ASPs to make the AS state as ACTIVE
> > and 'n=2' is fed during configuration.But while handling traffic due to 
> > failure of ASP1 'n' becomes '1', here still AS is ACTIVE with single ASP.
> > 
> > --Samuel
> 
> [snip]
> 
> > Date: Tue, 25 Feb 2003 06:08:39 -0600 (CST)
> > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
> > cc: sigtran@ietf.org
> > Subject: Re: [Sigtran] Re: M3UA Notify message
> > 
> > 
> > Tolga,
> > 
> > From this thread we can end up with two kinds of SGs.
> > 
> > The SG which decides to stop taking the traffic when 'n' changed
> > from '2' to '1'.
> > 
> > The other SG which decides to continue the traffic  when 'n' 
> > changed from '2' to '1'.
> > 
> > When performance is considered, i think everyone will prefer second case.
> > Second case follows the existing network standards.But first case does
> > not follow any standards.
> 
> [snip]
> 
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 


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



From exim@www1.ietf.org  Sat Jun 28 04:45:09 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19001
	for <sigtran-archive@odin.ietf.org>; Sat, 28 Jun 2003 04:45:09 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5S8i2406220
	for sigtran-archive@odin.ietf.org; Sat, 28 Jun 2003 04:44:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19WBJR-0001c5-1U; Sat, 28 Jun 2003 04:44:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19WBIX-0001ZP-9w
	for sigtran@optimus.ietf.org; Sat, 28 Jun 2003 04:43:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18986
	for <sigtran@ietf.org>; Sat, 28 Jun 2003 04:42:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WBIF-0002Gk-00
	for sigtran@ietf.org; Sat, 28 Jun 2003 04:42:47 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[zb4EkJsTUQB7O6yjXWV78XCvIQVYAnn7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WBHz-0002GW-00
	for sigtran@ietf.org; Sat, 28 Jun 2003 04:42:31 -0400
Received: from ns.pigworks.openss7.net (IDENT:LFsLz+9+rWyUfcqUqNSD7Up7tVV8mfLn@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5S8g3X00766;
	Sat, 28 Jun 2003 02:42:03 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5S8g3j05071;
	Sat, 28 Jun 2003 02:42:03 -0600
Date: Sat, 28 Jun 2003 02:42:03 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re:n+k issue
Message-ID: <20030628024203.A5019@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030628012916.A3873@openss7.org> <Pine.SOL.4.10.10306280313030.24516-100000@sun2594.ssd.usa.alcatel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.4.10.10306280313030.24516-100000@sun2594.ssd.usa.alcatel.com>; from sjeyasee@ssd.usa.alcatel.com on Sat, Jun 28, 2003 at 03:24:46AM -0500
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Samuel,

In the note I only said that you and Srivats agreed to not
stopping traffic #APSs < n.  I didn't say that you agreed
to starting traffic on the first ASP.  The others in this
and previous disccusions did, however.

--brian

Samuel Dur D. Jeyaseelan wrote:                                                     (Sat, 28 Jun 2003 03:24:46)
> 
> Brian,
> 
> In this attached mail i have said that 'n=2'(example) is mandatory at
> start case.
> This is what Javier,Tolga are also proposing to make 'n=2' as mandatory
> at start case.
> 
> SGP will stop taking traffic when # ASPS < n at start case.
> 
> But while handling the traffic if # ASPs < n , this will not stop the
> traffic.This is what i comprised in this mail.
> 
> So from the beginning i disagree to make an AS as active as soon as a
> single ASP goes to ACTIVE state in n+k reduntancy case.
> 
> --Samuel
> 
>   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
>   1000 Coit Road, Plano, Texas 75075
>   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> 
> On Sat, 28 Jun 2003, Brian F. G. Bidulock wrote:
> 
> > Samuel,
> > 
> > Samuel Dur D. Jeyaseelan wrote:                                                     (Sat, 28 Jun 2003 01:36:10)
> > 
> > > > 
> > > > Next on the thread:
> > > > 
> > > >   "M3UA Notify message" from Feb 12, 2003 to Feb 26, 2003
> > > >   (rejoined recently and extending from Jun 18, 2003 to Jun 26, 2003)
> > > > 
> > > > Srini asks some questions about Notify messages and n+k comes up again.  Srini
> > > > agrees that active ASPs < n corresponds to the AS-ACTIVE state as in the RFC
> > > > and that the ASP should use congestion and flow control procedures to limit
> > > > traffic if it is presented with too much traffic.  Bijoy agrees as well.
> > > > Srivats agrees as well with not stopping traffic #ASPs < n.  Samuel also
> > > > agrees with not stopping traffic #ASPs < n.  Javier agrees to the MAY.
> > > 
> > > Could you please give me a pointer where i agreed?
> > > 
> > > --Samuel
> > > 
> > 
> > Correct me if I'm wrong but it appears in the following two statements that
> > you agreed to not stopping traffic for #ASPs < n.
> > 
> > > Date: Tue, 25 Feb 2003 08:11:31 -0600 (CST)
> > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
> > > cc: "Brian F. G. Bidulock" <bidulock@openss7.org>,
> > >    TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
> > > Subject: RE: [Sigtran] Re: M3UA Notify message
> > > 
> > > Javier,
> > > 
> > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
> > >   1000 Coit Road, Plano, Texas 75075
> > >   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> > > 
> > > On Tue, 25 Feb 2003, Javier Pastor-Balbas (ECE) wrote:
> > > 
> > > > Hi Samuel et al., 
> > > > 
> > > > Take into account that if you define two ASes:
> > > > - AS1 DPC+SLS1  with two ASPs (ASP1 and ASP2) and redundancy: n=1 k=1
> > > > - AS2 DPC+SLS2  with two ASPs (ASP1 and ASP2) and redundancy: n=1 k=1
> > > > 
> > > > And 
> > > > - ASP1 active for AS1 and backup for AS2
> > > > - ASP2 active for AS2 and backup for AS1
> > > > 
> > > > You get the desired behaviour. This case can be solved with a right 
> > >   network configuration without changing the current "required"
> > >   qualification for "n".
> > > > 
> > > > 
> > > > 
> > > > Apart from this, 
> > > > 
> > > > I would say that a compromise option would consist of considering "n" as 
> > >   the normal working case, but make it implementation dependent (maybe
> > > configurable) whether an implementation may have more than "n" ASPs 
> > >  working at the same time for an AS, and whether the SG keeps working when
> > > the number of ASP is under "n". We could make a recommendation with "MAY" 
> > > allowing both options.
> > > >
> > > [Samuel] Yes .SG keeps working when n=1 or n >=2.
> > > but current RFC says that SG NOTIFIES 'k' ASP to become active only
> > > when n<2 and it does not say what will happen when SG requires more than
> > > 'n' ASP to handle the traffic 't+1'.
> > >  
> > > > But now, the problem comes with the AS state machine. If we agree upon here,
> > >  we could say the AS is ACTIVE in the range n_min to n_max, where these two
> > >  values are configurable.
> > > > 
> > > [Samuel] To handle the 'normal(best) traffic T' SG requires 'n=2' ASPs.
> > > In the course of traffic if 'n became 1'(means ASP1 failed), here SG can
> > > handle the traffic with 'n=1' ASP. 
> > > So only intially SG requires 'n=2' ASPs to make the AS state as ACTIVE
> > > and 'n=2' is fed during configuration.But while handling traffic due to 
> > > failure of ASP1 'n' becomes '1', here still AS is ACTIVE with single ASP.
> > > 
> > > --Samuel
> > 
> > [snip]
> > 
> > > Date: Tue, 25 Feb 2003 06:08:39 -0600 (CST)
> > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
> > > cc: sigtran@ietf.org
> > > Subject: Re: [Sigtran] Re: M3UA Notify message
> > > 
> > > 
> > > Tolga,
> > > 
> > > From this thread we can end up with two kinds of SGs.
> > > 
> > > The SG which decides to stop taking the traffic when 'n' changed
> > > from '2' to '1'.
> > > 
> > > The other SG which decides to continue the traffic  when 'n' 
> > > changed from '2' to '1'.
> > > 
> > > When performance is considered, i think everyone will prefer second case.
> > > Second case follows the existing network standards.But first case does
> > > not follow any standards.
> > 
> > [snip]
> > 
> > 
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> > 

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

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



From exim@www1.ietf.org  Sat Jun 28 06:19:41 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20080
	for <sigtran-archive@odin.ietf.org>; Sat, 28 Jun 2003 06:19:40 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5SAJDN25381
	for sigtran-archive@odin.ietf.org; Sat, 28 Jun 2003 06:19:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19WCnN-0006b8-Du; Sat, 28 Jun 2003 06:19:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19WCmw-0006au-IU
	for sigtran@optimus.ietf.org; Sat, 28 Jun 2003 06:18:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20077
	for <sigtran@ietf.org>; Sat, 28 Jun 2003 06:18:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WCms-0002Yt-00
	for sigtran@ietf.org; Sat, 28 Jun 2003 06:18:30 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[bM8/4tbtgVgRIJTWMMRc86DM85zoblul])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WCmc-0002Yd-00
	for sigtran@ietf.org; Sat, 28 Jun 2003 06:18:14 -0400
Received: from ns.pigworks.openss7.net (IDENT:sdwiKpwTyeqHtEYb1xfYKeSTZmekX0lY@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5SAHsX02252;
	Sat, 28 Jun 2003 04:17:54 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5SAHrD06485;
	Sat, 28 Jun 2003 04:17:53 -0600
Date: Sat, 28 Jun 2003 04:17:53 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
        sigtran@ietf.org
Subject: Re: [Sigtran] Re:n+k issue
Message-ID: <20030628041753.B5019@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>,
	sigtran@ietf.org
References: <20030628012916.A3873@openss7.org> <Pine.SOL.4.10.10306280313030.24516-100000@sun2594.ssd.usa.alcatel.com> <20030628024203.A5019@openss7.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030628024203.A5019@openss7.org>; from bidulock@openss7.org on Sat, Jun 28, 2003 at 02:42:03AM -0600
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Samuel,

I should point out that the proposal to require that the SG wait for 'n' to
start traffic does not have much merit.

Example: n=256, k=1

2 ASPs fail, permanently and need to be manually replaced.

A temporary network failure causes SCTP associations to be lost to the
remaining 255 ASPs.  They move to the ASP down state and immediately
re-establish SCTP associations and move to the ASP-Active state.  Because the
number of ASPs is < n, the SG will not restart traffic for some time.

Consider the same example with: n=2, k=1, two ASPs failed.

Any system that introduces hysteresis to aggravate and perpetuate an outage in
this fashion is not very useful.

In the examples, what would have been a brief AS-PENDING situation has been
turned into a prolonged and complete system failure.  It is certainly not good
practice to design redundant systems in that fashion and recommending or
requiring such a design would be a bad thing.

To further the example, consider the multiple SG as STP situation.  One SG
cannot know the state of ASPs for the its mated SG and therefore cannot
distinguish between the restart scenario and the start scenario as far as the
AS state is concerned because the SG does not know the state of the AS itself:
the AS could be active with other SGs.

This is the same case for SGP.  Unless AS state is synchronized across SGPs,
one SGP cannot know the total state of the AS (only its partition).  There is
no requirement to synchronize AS state across SGP (on the SGP side, AS-state
is per-SGP), and there is certainly no requirement to synchronize AS-state
across SGs.

So, take the (n=2, k=0) example where there are two SGs.  Due to a network
partitioning at startup, one ASP can communicate only with one SG, and the
other ASP can communicate only with the other SG.  Because n=2, neither SG
will start traffic and the system suffers 100% failure until the network
partitioning ceases.

Consider the same example where there are two SGPs (instead of SGs) and the
two ASPs normally only form one association (e.g., ASP1-SGP1, ASP2-SGP2).
Note that there is no requirement in the RFC to form full-mesh associations.
Because the number of active ASPs with each SGP is < 2, the system will never
start.

These are not strange scenarios.  These situations are all permitted by the
RFC.  Yet, in each situation it is clear that one cannot recommend that the SG
wait.  The result would be a non-functional system.  There are many more
examples.

n+k is a model for redundancy (not for congestion and flow control).  A system
with an SG that waits for n is, in general, not a fully redundant system at
all, but is, rather, prone to these failure syndromes.

When you look at the situation and apply the experience of reliability
engineering, the recommendation is that the SG SHOULD start traffic when the
first ASP goes active.

Why wait for 'n' anyway?  Because the ASP cannot handle some level of traffic?
Any ASP that conforms to MTP-User standards, must have the standardized
MTP-User (ISUP/SCCP) congestion and flow controls and must have the SCTP
congestion controls and is therefore able to accept any amount of traffic
overload.

So there is no real reason for the SG to wait for 'n'.  Nevertheless, the RFC
allows this as an OPTION.  Requiring (MUST) or recommending it (SHOULD)
regardless of whether the number of active processors is rising or falling,
whether start, restart or failure, is unacceptable.

On the other side, at the ASPs, the ASPs have a requirement to share state
between them.  They must share circuit state and transaction state in all
configurations to meet carrier grade.  This is stated in the RFC.  It is
implicit that the ASPs are capable of knowing with which SGs, and which SGPs
for which they are active.  They have access to the total state of the AS that
they collectively represent, that the SG/SGP does not.  Therefore is it
reasonable for the ASPs to coordinate among themselves the number of active
ASPs and to ensure that there are sufficient ASPs active to handle the
expected load before starting traffic.  Because the ASPs need not respond to
user test traffic (UPT/SST), the ASPs are also in control of when remote SS7
MTP-User restart traffic toward them.

Therefore, the recommendation that the ASPs SHOULD coordinate among
themselves the number of active ASPs and not start traffic until a sufficient
number of them are active is sound.  This is not a MUST, permitting ASPs
that know that they are capable of handling any overload, to start traffic
immediately, or at some earlier point.

Back to the RFC, the RFC sets the normal case where the SG starts traffic on
the first active ASP but explicitly permits as an OPTION to wait until it
considers that there are sufficient ASPs active to handle the offered load.
The RFC also RECOMMENDS that the ASPs coordinate among themselves the number
of active ASPs so that there are sufficient ASPs to handle the expected load.

The provisions in the RFC are both sound, where the proposal and section 3.15
is clearly not.

Remember when looking at the AS state diagram in the RFC that this is the
SGP's view of the AS state and not the total state of the AS, that can only
known to the ASPs for all configurations.  'n' as defined has no meaning to
the state machine at the SGP because is not required to know, and often cannot
know, how many ASPs are active for the AS via other SGPs and SGs, or even via
direct connection to the SS7 network.

Some SGs might have special knowledge, or sophisticated algorithms that allow
it to determine whether a congestive failure will be the immediate result of
starting or restarting traffic.  These SGs are permitted as an OPTION to wait.

The ASPs SHOULD have the knowledge of how many are required to handle the
expected load, because they must share circuit/transaction state and they must
have congestion and flow controls as required by the standards.

So again, the RFC is adequate in this regard.  The current proposal and
section 3.15 are not.

--brian


Brian F. G. Bidulock wrote:                                                         (Sat, 28 Jun 2003 02:42:03)
> Samuel,
> 
> In the note I only said that you and Srivats agreed to not
> stopping traffic #APSs < n.  I didn't say that you agreed
> to starting traffic on the first ASP.  The others in this
> and previous disccusions did, however.
> 
> --brian
> 
> Samuel Dur D. Jeyaseelan wrote:                                                     (Sat, 28 Jun 2003 03:24:46)
> > 
> > Brian,
> > 
> > In this attached mail i have said that 'n=2'(example) is mandatory at
> > start case.
> > This is what Javier,Tolga are also proposing to make 'n=2' as mandatory
> > at start case.
> > 
> > SGP will stop taking traffic when # ASPS < n at start case.
> > 
> > But while handling the traffic if # ASPs < n , this will not stop the
> > traffic.This is what i comprised in this mail.
> > 
> > So from the beginning i disagree to make an AS as active as soon as a
> > single ASP goes to ACTIVE state in n+k reduntancy case.
> > 
> > --Samuel
> > 
> >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
> >   1000 Coit Road, Plano, Texas 75075
> >   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> > 
> > On Sat, 28 Jun 2003, Brian F. G. Bidulock wrote:
> > 
> > > Samuel,
> > > 
> > > Samuel Dur D. Jeyaseelan wrote:                                                     (Sat, 28 Jun 2003 01:36:10)
> > > 
> > > > > 
> > > > > Next on the thread:
> > > > > 
> > > > >   "M3UA Notify message" from Feb 12, 2003 to Feb 26, 2003
> > > > >   (rejoined recently and extending from Jun 18, 2003 to Jun 26, 2003)
> > > > > 
> > > > > Srini asks some questions about Notify messages and n+k comes up again.  Srini
> > > > > agrees that active ASPs < n corresponds to the AS-ACTIVE state as in the RFC
> > > > > and that the ASP should use congestion and flow control procedures to limit
> > > > > traffic if it is presented with too much traffic.  Bijoy agrees as well.
> > > > > Srivats agrees as well with not stopping traffic #ASPs < n.  Samuel also
> > > > > agrees with not stopping traffic #ASPs < n.  Javier agrees to the MAY.
> > > > 
> > > > Could you please give me a pointer where i agreed?
> > > > 
> > > > --Samuel
> > > > 
> > > 
> > > Correct me if I'm wrong but it appears in the following two statements that
> > > you agreed to not stopping traffic for #ASPs < n.
> > > 
> > > > Date: Tue, 25 Feb 2003 08:11:31 -0600 (CST)
> > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > > To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
> > > > cc: "Brian F. G. Bidulock" <bidulock@openss7.org>,
> > > >    TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
> > > > Subject: RE: [Sigtran] Re: M3UA Notify message
> > > > 
> > > > Javier,
> > > > 
> > > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
> > > >   1000 Coit Road, Plano, Texas 75075
> > > >   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> > > > 
> > > > On Tue, 25 Feb 2003, Javier Pastor-Balbas (ECE) wrote:
> > > > 
> > > > > Hi Samuel et al., 
> > > > > 
> > > > > Take into account that if you define two ASes:
> > > > > - AS1 DPC+SLS1  with two ASPs (ASP1 and ASP2) and redundancy: n=1 k=1
> > > > > - AS2 DPC+SLS2  with two ASPs (ASP1 and ASP2) and redundancy: n=1 k=1
> > > > > 
> > > > > And 
> > > > > - ASP1 active for AS1 and backup for AS2
> > > > > - ASP2 active for AS2 and backup for AS1
> > > > > 
> > > > > You get the desired behaviour. This case can be solved with a right 
> > > >   network configuration without changing the current "required"
> > > >   qualification for "n".
> > > > > 
> > > > > 
> > > > > 
> > > > > Apart from this, 
> > > > > 
> > > > > I would say that a compromise option would consist of considering "n" as 
> > > >   the normal working case, but make it implementation dependent (maybe
> > > > configurable) whether an implementation may have more than "n" ASPs 
> > > >  working at the same time for an AS, and whether the SG keeps working when
> > > > the number of ASP is under "n". We could make a recommendation with "MAY" 
> > > > allowing both options.
> > > > >
> > > > [Samuel] Yes .SG keeps working when n=1 or n >=2.
> > > > but current RFC says that SG NOTIFIES 'k' ASP to become active only
> > > > when n<2 and it does not say what will happen when SG requires more than
> > > > 'n' ASP to handle the traffic 't+1'.
> > > >  
> > > > > But now, the problem comes with the AS state machine. If we agree upon here,
> > > >  we could say the AS is ACTIVE in the range n_min to n_max, where these two
> > > >  values are configurable.
> > > > > 
> > > > [Samuel] To handle the 'normal(best) traffic T' SG requires 'n=2' ASPs.
> > > > In the course of traffic if 'n became 1'(means ASP1 failed), here SG can
> > > > handle the traffic with 'n=1' ASP. 
> > > > So only intially SG requires 'n=2' ASPs to make the AS state as ACTIVE
> > > > and 'n=2' is fed during configuration.But while handling traffic due to 
> > > > failure of ASP1 'n' becomes '1', here still AS is ACTIVE with single ASP.
> > > > 
> > > > --Samuel
> > > 
> > > [snip]
> > > 
> > > > Date: Tue, 25 Feb 2003 06:08:39 -0600 (CST)
> > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > > To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
> > > > cc: sigtran@ietf.org
> > > > Subject: Re: [Sigtran] Re: M3UA Notify message
> > > > 
> > > > 
> > > > Tolga,
> > > > 
> > > > From this thread we can end up with two kinds of SGs.
> > > > 
> > > > The SG which decides to stop taking the traffic when 'n' changed
> > > > from '2' to '1'.
> > > > 
> > > > The other SG which decides to continue the traffic  when 'n' 
> > > > changed from '2' to '1'.
> > > > 
> > > > When performance is considered, i think everyone will prefer second case.
> > > > Second case follows the existing network standards.But first case does
> > > > not follow any standards.
> > > 
> > > [snip]
> > > 
> > > 
> > > -- 
> > > Brian F. G. Bidulock
> > > bidulock@openss7.org
> > > http://www.openss7.org/
> > > 
> > > _______________________________________________
> > > Sigtran mailing list
> > > Sigtran@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > 
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Sat Jun 28 10:38:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24354
	for <sigtran-archive@odin.ietf.org>; Sat, 28 Jun 2003 10:38:31 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5SEc3j02986
	for sigtran-archive@odin.ietf.org; Sat, 28 Jun 2003 10:38:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19WGq1-0000lu-KC; Sat, 28 Jun 2003 10:38:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19WGpF-0000aj-6d
	for sigtran@optimus.ietf.org; Sat, 28 Jun 2003 10:37:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24337
	for <sigtran@ietf.org>; Sat, 28 Jun 2003 10:37:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WGpC-0003RB-00
	for sigtran@ietf.org; Sat, 28 Jun 2003 10:37:10 -0400
Received: from web12801.mail.yahoo.com ([216.136.174.36])
	by ietf-mx with smtp (Exim 4.12)
	id 19WGp2-0003R7-00
	for sigtran@ietf.org; Sat, 28 Jun 2003 10:37:00 -0400
Message-ID: <20030628143629.57533.qmail@web12801.mail.yahoo.com>
Received: from [68.44.141.139] by web12801.mail.yahoo.com via HTTP; Sat, 28 Jun 2003 07:36:29 PDT
Date: Sat, 28 Jun 2003 07:36:29 -0700 (PDT)
From: Tolga Asveren <tolga_asveren@yahoo.com>
Subject: Re: [Sigtran] Re:n+k issue
To: sigtran@ietf.org
In-Reply-To: <20030628041753.B5019@openss7.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Brian,

IMO -although you disagree-, your arguments should
lead to discarding n+k concept from SG side, and
always activating with the first ACTIVE ASP, because I
don't see how SG can dynamically decide to activate or
not an AS. (BTW, getting rid of n+k was also proposed
as one of the options at one of the n+k discussions,
basically there were three options 
1) If there is no use for n+k, no need to define it
2) Making AS state changes based on NTFY on ASP side
3) Using n as a static value at both SGP and ASP so
that their AS state views are the same.)
So, I think n+k case -as in IG- with n=1 should give
the operation characteristics you want.
Please see also some other comments/questions below.

     Tolga
--- "Brian F. G. Bidulock" <bidulock@openss7.org>
wrote:
> Samuel,
> 
> I should point out that the proposal to require that
> the SG wait for 'n' to
> start traffic does not have much merit.
> 
> Example: n=256, k=1
> 
> 2 ASPs fail, permanently and need to be manually
> replaced.
> 
> A temporary network failure causes SCTP associations
> to be lost to the
> remaining 255 ASPs.  They move to the ASP down state
> and immediately
> re-establish SCTP associations and move to the
> ASP-Active state.  Because the
> number of ASPs is < n, the SG will not restart
> traffic for some time.
[TOLGA] So, maybe you should have n=254, k=2, or n
=200 k=56 (IMO your example is very extreme -a low k
value, 2 systems going down and global network
failure)
> 
> Consider the same example with: n=2, k=1, two ASPs
> failed.
> 
> Any system that introduces hysteresis to aggravate
> and perpetuate an outage in
> this fashion is not very useful.
> 
> In the examples, what would have been a brief
> AS-PENDING situation has been
> turned into a prolonged and complete system failure
>  It is certainly not good
> practice to design redundant systems in that fashion
> and recommending or
> requiring such a design would be a bad thing.
> 
> To further the example, consider the multiple SG as
> STP situation.  One SG
> cannot know the state of ASPs for the its mated SG
> and therefore cannot
> distinguish between the restart scenario and the
> start scenario as far as the
> AS state is concerned because the SG does not know
> the state of the AS itself:
> the AS could be active with other SGs.
[TOLGA]So? This is always possible. What is wrong that
SGs have different view of AS state? (Although I don't
believe multiple SG scenario is well supported with
M3UA, I believe n+k does not bring any disadvantage)
> 
> This is the same case for SGP.  Unless AS state is
> synchronized across SGPs,
> one SGP cannot know the total state of the AS (only
> its partition).  There is
> no requirement to synchronize AS state across SGP
> (on the SGP side, AS-state
> is per-SGP), and there is certainly no requirement
> to synchronize AS-state
> across SGs.
> 
> So, take the (n=2, k=0) example where there are two
> SGs.  Due to a network
> partitioning at startup, one ASP can communicate
> only with one SG, and the
> other ASP can communicate only with the other SG. 
> Because n=2, neither SG
> will start traffic and the system suffers 100%
> failure until the network
> partitioning ceases.
[TOLGA]For n=2 -I speak from IG 3.15 point view-, this
is the expected and desired behaviour. Nothing wrong
with this. This can be avoided with n=1. And from your
point of view, there is no way SG can know anything
about the situation either. In fact this is an example
for my point at the beginning of the message: SG can
only statically decide to activate AS (and this might
be forced always to happen with the first ACTIVE ASP
or with a configurable number of ACTIVE ASPs, which
certainly allows that number also to be 1)
BTW, it is also very unlikely that two ASPs have
different IP connectivity to the network and that a
network isolation happens. 
> 
> Consider the same example where there are two SGPs
> (instead of SGs) and the
> two ASPs normally only form one association (e.g.,
> ASP1-SGP1, ASP2-SGP2).
> Note that there is no requirement in the RFC to form
> full-mesh associations.
> Because the number of active ASPs with each SGP is <
> 2, the system will never
> start.
[TOLGA] IMO, this is definitly a configuration
problem. Either let both ASPs form association to both
SGPs, or use n=1.
> 
> These are not strange scenarios.  These situations
> are all permitted by the
> RFC.  Yet, in each situation it is clear that one
> cannot recommend that the SG
> wait.  The result would be a non-functional system. 
> There are many more
> examples.
> 
> n+k is a model for redundancy (not for congestion
> and flow control).  A system
> with an SG that waits for n is, in general, not a
> fully redundant system at
> all, but is, rather, prone to these failure
> syndromes.
[TOLGA]Because transition from AS-ACTIVE to AS-PENDING
has been changed, I think n+k increases redundancy of
the system. 
> 
> When you look at the situation and apply the
> experience of reliability
> engineering, the recommendation is that the SG
> SHOULD start traffic when the
> first ASP goes active.
[TOLGA] Then just using n=1 should be fine.
> 
> Why wait for 'n' anyway?  Because the ASP cannot
> handle some level of traffic?
> Any ASP that conforms to MTP-User standards, must
> have the standardized
> MTP-User (ISUP/SCCP) congestion and flow controls
> and must have the SCTP
> congestion controls and is therefore able to accept
> any amount of traffic
> overload.
[TOLGA]This is just another level of operation. If the
operator knows that n ASPs are required for a healthy
operation, what is wrong by giving the operator the
choice of configuring n, where n=1 is also possible?
> 
> So there is no real reason for the SG to wait for
> 'n'.  Nevertheless, the RFC
> allows this as an OPTION.  Requiring (MUST) or
> recommending it (SHOULD)
> regardless of whether the number of active
> processors is rising or falling,
> whether start, restart or failure, is unacceptable.
> 
> On the other side, at the ASPs, the ASPs have a
> requirement to share state
> between them.  They must share circuit state and
> transaction state in all
> configurations to meet carrier grade.  This is
> stated in the RFC.  It is
> implicit that the ASPs are capable of knowing with
> which SGs, and which SGPs
> for which they are active.  They have access to the
> total state of the AS that
> they collectively represent, that the SG/SGP does
> not.  Therefore is it
> reasonable for the ASPs to coordinate among
> themselves the number of active
> ASPs and to ensure that there are sufficient ASPs
> active to handle the
> expected load before starting traffic.  Because the
> ASPs need not respond to
> user test traffic (UPT/SST), the ASPs are also in
> control of when remote SS7
> MTP-User restart traffic toward them.
> 
> Therefore, the recommendation that the ASPs SHOULD
> coordinate among
> themselves the number of active ASPs and not start
> traffic until a sufficient
> number of them are active is sound.  This is not a
> MUST, permitting ASPs
> that know that they are capable of handling any
> overload, to start traffic
> immediately, or at some earlier point.
> 
> Back to the RFC, the RFC sets the normal case where
> the SG starts traffic on
> the first active ASP but explicitly permits as an
> OPTION to wait until it
> considers that there are sufficient ASPs active to
> handle the offered load.
> The RFC also RECOMMENDS that the ASPs coordinate
> among themselves the number
> of active ASPs so that there are sufficient ASPs to
> handle the expected load.
> 
> The provisions in the RFC are both sound, where the
> proposal and section 3.15
> is clearly not.
> 
> Remember when looking at the AS state diagram in the
> RFC that this is the
> SGP's view of the AS state and not the total state
> of the AS, that can only
> known to the ASPs for all configurations.  'n' as
> defined has no meaning to
> the state machine at the SGP because is not required
> to know, and often cannot
> know, how many ASPs are active for the AS via other
> SGPs and SGs, or even via
> direct connection to the SS7 network.
> 
> Some SGs might have special knowledge, or
> sophisticated algorithms that allow
> it to determine whether a congestive failure will be
> the immediate result of
> starting or restarting traffic.  These SGs are
> permitted as an OPTION to wait.
> 
> The ASPs SHOULD have the knowledge of how many are
> required to handle the
> expected load, because they must share
> circuit/transaction state and they must
> have congestion and flow controls as required by the
> standards.
> 
> So again, the RFC is adequate in this regard.  The
> current proposal and
> section 3.15 are not.
> 
> --brian
> 


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

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



From exim@www1.ietf.org  Sun Jun 29 02:37:33 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23503
	for <sigtran-archive@odin.ietf.org>; Sun, 29 Jun 2003 02:37:33 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5T6b4q12051
	for sigtran-archive@odin.ietf.org; Sun, 29 Jun 2003 02:37:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19WVo6-00037M-3Y; Sun, 29 Jun 2003 02:37:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19WVnL-00034C-LE
	for sigtran@optimus.ietf.org; Sun, 29 Jun 2003 02:36:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23500
	for <sigtran@ietf.org>; Sun, 29 Jun 2003 02:35:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WVn3-0007a2-00
	for sigtran@ietf.org; Sun, 29 Jun 2003 02:35:57 -0400
Received: from gw.openss7.com ([142.179.199.224] ident=[LXMaF9Vtsh0C0Ue+0aiEfSpMf4xvCDE1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WVmm-0007Zr-00
	for sigtran@ietf.org; Sun, 29 Jun 2003 02:35:41 -0400
Received: from ns.pigworks.openss7.net (IDENT:NdWoOYw6tiSCtk79bCY/8nGBelBhlDvE@ns1.evil.openss7.net [192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id h5T6Z6X17029;
	Sun, 29 Jun 2003 00:35:06 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id h5T6Z5E19410;
	Sun, 29 Jun 2003 00:35:05 -0600
Date: Sun, 29 Jun 2003 00:35:04 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Tolga Asveren <tolga_asveren@yahoo.com>
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Re:n+k issue
Message-ID: <20030629003504.A19393@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: Tolga Asveren <tolga_asveren@yahoo.com>, sigtran@ietf.org
References: <20030628041753.B5019@openss7.org> <20030628143629.57533.qmail@web12801.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030628143629.57533.qmail@web12801.mail.yahoo.com>; from tolga_asveren@yahoo.com on Sat, Jun 28, 2003 at 07:36:29AM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

Tolga,

Tolga Asveren wrote:                                                                 (Sat, 28 Jun 2003 07:36:29)
> Brian,
> 
> IMO -although you disagree-, your arguments should lead to discarding n+k
> concept from SG side, and always activating with the first ACTIVE ASP, because
> I don't see how SG can dynamically decide to activate or not an AS.  (BTW,
> getting rid of n+k was also proposed as one of the options at one of the n+k
> discussions, basically there were three options 1) If there is no use for n+k,
> no need to define it

The SG MAY withhold traffic in the RFC.  This is an OPTIONAL feature.  OPTIONAL
features that are not implemented between "Proposed Standard" and "Standard"
will be automatically dropped.  Therefore, if we choose 1), no change is
necessary and we can strike 3.15 and wait for the OPTIONAL feature to drop
between "Proposed Standard" and "Standard".

OTOH, others could find it useful, even if you do not and implement the option,
in which case it would remain an option when the protocol moves to "Standard".
I described a number of ways in which the option can be used.  I have considered
implementing a procedure similar to the link oscillation procedures in ANSI/2000
MTP, where the SG would withhold traffic and NTFY(AS Active) for a probation
period on restart to avoid failure oscillation.  Under such a scheme, if the ASP
is restarting within a suspension interval from the last restart, the SG would
withhold traffic until a probation interval expired.  This makes sense because
SCTP has no proving period for M3UA.

> 2) Making AS state changes based on NTFY on ASP side

The ASP is already permitted to do this now.  If we choose 2), no change is
necessary and we can strike 3.15.

> 3) Using n as a static value at both SGP and ASP so that their AS state views
> are the same.)

The AS state view at the SGP and ASP are not the same.  One SGP can view the AS
state as AS-DOWN while another SGP and the ASP view the AS state as AS-ACTIVE.
Therefore you cannot make the AS state view the same unless protocol is added to
have the ASP notify the SGP what the total ASP state is with regard to the AS.

Your proposal does not make this view the same, because each SGP already has an
independent state view of the AS.  The SGP's view of the AS-state is its own.
So, for example, ASP1 has an association with SGP1 and SGP2.  The ASP has
executed ASP-UP on the association to SGP1, and has executed ASP-Active/Ack for
AS1 with SGP1.  The ASP has not executed ASP-UP with SGP2 yet.  SGP1's view is
that ASP1 is ASP-ACTIVE for AS1 and that AS1 is in the AS-ACTIVE state.  SGP2's
view is that ASP1 is ASP-DOWN and that AS1 is in the AS-DOWN state.  The ASPs
view is that it is AS-ACTIVE for AS1.  SGP2 and ASP1 have a different view of AS
state.  This inherent to the protocol.  Neither the current section 3.15 nor
your proposal can achieve this.

> So, I think n+k case -as in IG- with n=1 should give the operation
> characteristics you want.

No.  Because the SG will not send Notify(Insufficient ASPs active in AS) for
n=1.  That is an operational characteristic that is not achieved by setting n to
1.  Also, if n is set to 1, the ASPs are not expected to wait until the true 'n'
of them are active before starting traffic themselves.  Also, the SG can no
longer wait for the true 'n' ASPs to become active before starting traffic is
its its prerogative in the current RFC.

Setting n to one changes both points in the RFC: that the SG MAY wait for 'n'
and that the ASP SHOULD wait for 'n'.  These are the fundamental operating
characteristics as I have already described below.

The option you missed:

4) Leave the RFC as it is, because there is nothing the matter with it.

> Please see also some other comments/questions below.
> 
>      Tolga
> --- "Brian F. G. Bidulock" <bidulock@openss7.org>
> wrote:
> > Samuel,
> > 
> > I should point out that the proposal to require that the SG wait for 'n' to
> > start traffic does not have much merit.
> > 
> > Example: n=256, k=1
> > 
> > 2 ASPs fail, permanently and need to be manually replaced.
> > 
> > A temporary network failure causes SCTP associations to be lost to the
> > remaining 255 ASPs.  They move to the ASP down state and immediately
> > re-establish SCTP associations and move to the ASP-Active state.  Because
> > the number of ASPs is < n, the SG will not restart traffic for some time.
> [TOLGA] So, maybe you should have n=254, k=2, or n =200 k=56 (IMO your example
> is very extreme -a low k value, 2 systems going down and global network
> failure)

There are no restrictions on n or k.  However, the same example was repeated
with n=2 and k=1.  Pick a number.  It appears that if n=7 and k=1, you will tell
me that I should have made n=6 and k=2 and then if 3 ASPs fail, you will tell me
I should have set n=5 and k=3 and so on, until you tell me finally as you have
above that I should set n=1 and k=6.

Well, n is not some arbitrary value.  It is the number of processors necessary
to handle the engineered load with the engineered level of reliability,
considering k.  When n=6 and the number of active ASPs drops to 5, the SG sends
notification to all the active and inactive ASPs (i.e. the k ASPs) that there
are insufficient ASP resources active in the AS.  Arbitrarily setting n=1 does
not accomplish this.

> > 
> > Consider the same example with: n=2, k=1, two ASPs failed.
> > 
> > Any system that introduces hysteresis to aggravate and perpetuate an outage
> > in this fashion is not very useful.
> > 
> > In the examples, what would have been a brief AS-PENDING situation has been
> > turned into a prolonged and complete system failure It is certainly not good
> > practice to design redundant systems in that fashion and recommending or
> > requiring such a design would be a bad thing.
> > 
> > To further the example, consider the multiple SG as STP situation.  One SG
> > cannot know the state of ASPs for the its mated SG and therefore cannot
> > distinguish between the restart scenario and the start scenario as far as
> > the AS state is concerned because the SG does not know the state of the AS
> > itself: the AS could be active with other SGs.
> [TOLGA]So? This is always possible. What is wrong that SGs have different view
> of AS state? (Although I don't believe multiple SG scenario is well supported
> with M3UA, I believe n+k does not bring any disadvantage)

Yes, what is wrong with this?  You are the one that said that the reason for
your proposal was so that the SGP and the ASP will have the same view of the
AS-state.  Well they cannot.  What other reason do you have for your proposal?

> > 
> > This is the same case for SGP.  Unless AS state is synchronized across SGPs,
> > one SGP cannot know the total state of the AS (only its partition).  There
> > is no requirement to synchronize AS state across SGP (on the SGP side,
> > AS-state is per-SGP), and there is certainly no requirement to synchronize
> > AS-state across SGs.
> > 
> > So, take the (n=2, k=0) example where there are two SGs.  Due to a network
> > partitioning at startup, one ASP can communicate only with one SG, and the
> > other ASP can communicate only with the other SG.  Because n=2, neither SG
> > will start traffic and the system suffers 100% failure until the network
> > partitioning ceases.
> [TOLGA]For n=2 -I speak from IG 3.15 point view-, this is the expected and
> desired behaviour. Nothing wrong with this.

Err, there is plenty wrong with requiring or recommending such an unnecessary and
prolonged 100% failure.

> This can be avoided with n=1.

With n=1 the k'th ASP is not notified when one of the two 'n' ASPs fails.  Also,
the SG is then unaware that the number of active ASPs is beneath the engineered
capacity.

> And from your point of view, there is no way SG can know anything about the
> situation either. In fact this is an example for my point at the beginning of
> the message: SG can only statically decide to activate AS (and this might be
> forced always to happen with the first ACTIVE ASP or with a configurable
> number of ACTIVE ASPs, which certainly allows that number also to be 1) BTW,
> it is also very unlikely that two ASPs have different IP connectivity to the
> network and that a network isolation happens. 
> > 
> > Consider the same example where there are two SGPs (instead of SGs) and the
> > two ASPs normally only form one association (e.g., ASP1-SGP1, ASP2-SGP2).
> > Note that there is no requirement in the RFC to form full-mesh associations.
> > Because the number of active ASPs with each SGP is < 2, the system will
> > never start.
> [TOLGA] IMO, this is definitly a configuration problem. Either let both ASPs
> form association to both SGPs, or use n=1.

n=1 does not function correctly.  There is no requirement in the RFC to form
full mess associations.

> > 
> > These are not strange scenarios.  These situations are all permitted by the
> > RFC.  Yet, in each situation it is clear that one cannot recommend that the
> > SG wait.  The result would be a non-functional system.  There are many more
> > examples.
> > 
> > n+k is a model for redundancy (not for congestion and flow control).  A
> > system with an SG that waits for n is, in general, not a fully redundant
> > system at all, but is, rather, prone to these failure syndromes.
> [TOLGA]Because transition from AS-ACTIVE to AS-PENDING has been changed, I
> think n+k increases redundancy of the system. 

But because transition from AS-INACTIVE to AS-ACTIVE has not in your proposal,
the reliability of the system is reduced from that of the RFC.  That is what
is unacceptable about both section 3.15 and your proposal.

> > 
> > When you look at the situation and apply the experience of reliability
> > engineering, the recommendation is that the SG SHOULD start traffic when the
> > first ASP goes active.
> [TOLGA] Then just using n=1 should be fine.

No, because n is not chose arbitrarily.  Setting n=1 arbitrarily does no have
the same dynamics with respect to the detection at the SGP and notification
from the SGP of insufficient ASPs active in the AS.

Perhaps the reason that you think that n can be set arbitrarily in this fashion
is because you do not understand the relationship of 'n' to 'k' in the n+k
redundancy model as it is normally applied in telecommunications engineering
practice.   Otherwise, I cannot see why you would think so falsely that n
can be set arbitrarily.  'n' and 'k' are engineered figures considering traffic
loading and reliability requirements.  They are outside the M3UA protocol.
They are not numbers that can be set willy nilly to extreme values such as 1
in an attempt to fudge one's way around the unreasonable requirement in your
proposal.

> > 
> > Why wait for 'n' anyway?  Because the ASP cannot handle some level of
> > traffic?  Any ASP that conforms to MTP-User standards, must have the
> > standardized MTP-User (ISUP/SCCP) congestion and flow controls and must have
> > the SCTP congestion controls and is therefore able to accept any amount of
> > traffic overload.
> [TOLGA]This is just another level of operation. If the operator knows that n
> ASPs are required for a healthy operation, what is wrong by giving the
> operator the choice of configuring n, where n=1 is also possible?

Because n is not 1.

What is the problem with the operator configuring the SG to wait for 'n' when
they known that the ASPs are so poorly designed that they do not conform to the
flow and congestion control requirements of the SS7 standards?  Nothing.  And
that is what the RFC permits.

But it also permits the SG to function without lost reliability with ASPs that
correctly conform to SS7 flow and congestion controls, without the poor hack
of setting n to 1.

The RFC already provides for both behaviors, and accommodates your broken ASPs,
without requiring properly functioning ASPs to behave like they are one big
broken ASP.

Who is there that has implemented an ASP with complete neglect for ISUP/SCCP
congestion and flow controls that needs the SG to wait?  Are you speaking of
your ASPs?

Comments please: Who is it that has an ASP that does not conform to SS7
ISUP and SCCP specifications and is so brittle that it needs the SG to wait?

(Nobody I think.)

But the option is there in the RFC in case some SG finds itself faced with
malfunctioning ASPs in the field.

--brian

> > 
> > So there is no real reason for the SG to wait for 'n'.  Nevertheless, the
> > RFC allows this as an OPTION.  Requiring (MUST) or recommending it (SHOULD)
> > regardless of whether the number of active processors is rising or falling,
> > whether start, restart or failure, is unacceptable.
> > 
> > On the other side, at the ASPs, the ASPs have a requirement to share state
> > between them.  They must share circuit state and transaction state in all
> > configurations to meet carrier grade.  This is stated in the RFC.  It is
> > implicit that the ASPs are capable of knowing with which SGs, and which SGPs
> > for which they are active.  They have access to the total state of the AS
> > that they collectively represent, that the SG/SGP does not.  Therefore is it
> > reasonable for the ASPs to coordinate among themselves the number of active
> > ASPs and to ensure that there are sufficient ASPs active to handle the
> > expected load before starting traffic.  Because the ASPs need not respond to
> > user test traffic (UPT/SST), the ASPs are also in control of when remote SS7
> > MTP-User restart traffic toward them.
> > 
> > Therefore, the recommendation that the ASPs SHOULD coordinate among
> > themselves the number of active ASPs and not start traffic until a
> > sufficient number of them are active is sound.  This is not a MUST,
> > permitting ASPs that know that they are capable of handling any overload, to
> > start traffic immediately, or at some earlier point.
> > 
> > Back to the RFC, the RFC sets the normal case where the SG starts traffic on
> > the first active ASP but explicitly permits as an OPTION to wait until it
> > considers that there are sufficient ASPs active to handle the offered load.
> > The RFC also RECOMMENDS that the ASPs coordinate among themselves the number
> > of active ASPs so that there are sufficient ASPs to handle the expected
> > load.
> > 
> > The provisions in the RFC are both sound, where the proposal and section
> > 3.15 is clearly not.
> > 
> > Remember when looking at the AS state diagram in the RFC that this is the
> > SGP's view of the AS state and not the total state of the AS, that can only
> > known to the ASPs for all configurations.  'n' as defined has no meaning to
> > the state machine at the SGP because is not required to know, and often
> > cannot know, how many ASPs are active for the AS via other SGPs and SGs, or
> > even via direct connection to the SS7 network.
> > 
> > Some SGs might have special knowledge, or sophisticated algorithms that
> > allow it to determine whether a congestive failure will be the immediate
> > result of starting or restarting traffic.  These SGs are permitted as an
> > OPTION to wait.
> > 
> > The ASPs SHOULD have the knowledge of how many are required to handle the
> > expected load, because they must share circuit/transaction state and they
> > must have congestion and flow controls as required by the standards.
> > 
> > So again, the RFC is adequate in this regard.  The current proposal and
> > section 3.15 are not.
> > 
> > --brian
> > 
> 
> 
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran

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

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



From exim@www1.ietf.org  Sun Jun 29 07:40:33 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26595
	for <sigtran-archive@odin.ietf.org>; Sun, 29 Jun 2003 07:40:33 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5TBe3k04201
	for sigtran-archive@odin.ietf.org; Sun, 29 Jun 2003 07:40:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19WaXJ-00015W-KS; Sun, 29 Jun 2003 07:40:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19WaWi-000120-1x
	for sigtran@optimus.ietf.org; Sun, 29 Jun 2003 07:39:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26587
	for <sigtran@ietf.org>; Sun, 29 Jun 2003 07:39:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WaWh-0000Zw-00
	for sigtran@ietf.org; Sun, 29 Jun 2003 07:39:23 -0400
Received: from mail-n.franken.de ([193.175.24.27] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 19WaWW-0000Zt-00
	for sigtran@ietf.org; Sun, 29 Jun 2003 07:39:12 -0400
Received: from lurchi.franken.de (dialin-145-254-162-199.arcor-ip.net [145.254.162.199])
	by mail-n.franken.de (Postfix) with ESMTP id 2549A2480B
	for <sigtran@ietf.org>; Sun, 29 Jun 2003 13:30:57 +0200 (CEST)
Date: Sun, 29 Jun 2003 13:29:20 +0200
Mime-Version: 1.0 (Apple Message framework v552)
Content-Type: text/plain; charset=US-ASCII; format=flowed
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
To: sigtran@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <ECF7D787-AA24-11D7-8921-0030654C1AB6@lurchi.franken.de>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Subject: [Sigtran] draft-ietf-sigtran-security-03.txt
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Dear all,

a new version of draft-ietf-sigtran-security-03.txt has been
submitted to the IETF.

What is new?

- Editorial changes have been made to reflect the comments during IETS 
review.
- A TLS session upgrade procedure is described now.

The document is also available at
http://www.sctp.de/internet-drafts/draft-ietf-sigtran-security-03.txt

Best regards
Michael


---------------------
tuexen@fh-muenster.de


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



From exim@www1.ietf.org  Mon Jun 30 10:35:33 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27743
	for <sigtran-archive@odin.ietf.org>; Mon, 30 Jun 2003 10:35:33 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5UEZ5Z07241
	for sigtran-archive@odin.ietf.org; Mon, 30 Jun 2003 10:35:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19WzkE-0001qx-MY; Mon, 30 Jun 2003 10:35:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Wzk7-0001oZ-1T
	for sigtran@optimus.ietf.org; Mon, 30 Jun 2003 10:34:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27572
	for <sigtran@ietf.org>; Mon, 30 Jun 2003 10:34:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WzXn-00015Z-00
	for sigtran@ietf.org; Mon, 30 Jun 2003 10:22:11 -0400
Received: from web41813.mail.yahoo.com ([66.218.93.147])
	by ietf-mx with smtp (Exim 4.12)
	id 19WzXQ-00014K-00
	for sigtran@ietf.org; Mon, 30 Jun 2003 10:21:48 -0400
Message-ID: <20030630141913.28823.qmail@web41813.mail.yahoo.com>
Received: from [65.198.40.51] by web41813.mail.yahoo.com via HTTP; Mon, 30 Jun 2003 09:19:13 CDT
Date: Mon, 30 Jun 2003 09:19:13 -0500 (CDT)
From: =?iso-8859-1?q?Pablo=20Salinas?= <pablopesb@yahoo.com>
To: sigtran@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-328760516-1056982753=:27893"
Subject: [Sigtran] Signaling Gateway Doubts
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>

--0-328760516-1056982753=:27893
Content-Type: text/plain; charset=iso-8859-1
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id KAA27575
Content-Transfer-Encoding: quoted-printable

Hi there,
            I am having a hard time to understand one thing in a VoIP Net=
work that uses a softswitch.
Supose, we have the following situation:
There is a softswitch installed in location A. And this softswitch must c=
ommunicate with the PTT in localtion A. Should it have a Signaling Gatewa=
y between the softswitch and the PTT?
If the answer is yes, why use the SCTP, M2UA, M2PA or whatever other sigt=
ran protocol, if it is possible to connect the softswitch directly to the=
 PTT via the MTP2 protocol.
If the answer is no, why in every network scheme I saw until now, there i=
s always a SG between the PTT and the softswitch, when the sofswitch comm=
unicates with the media gateways via H.248?
=20
                         thanks,
                                      Pablo Salinas



---------------------------------
Do You Yahoo!?
Todo lo que quieres saber de Estados Unidos, Am=E9rica Latina y el resto =
del Mundo.
Vis=EDta Yahoo! Noticias.

--0-328760516-1056982753=:27893
Content-Type: text/html; charset=iso-8859-1
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id KAA27575
Content-Transfer-Encoding: quoted-printable

<DIV>Hi there,</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I=
 am having a hard time to understand one thing in a VoIP Network that&nbs=
p;uses a softswitch.</DIV>
<DIV>Supose, we have the following situation:</DIV>
<DIV>There is a softswitch installed in location A. And this softswitch m=
ust communicate with the PTT in localtion A. Should it have a Signaling G=
ateway between the softswitch and the PTT?</DIV>
<DIV>If the answer is yes, why use the SCTP, M2UA, M2PA or whatever other=
 sigtran protocol, if it is possible to connect the softswitch directly t=
o the PTT via the MTP2 protocol.</DIV>
<DIV>If the answer is no, why in every network scheme I saw until now, th=
ere is always a SG between the PTT and the softswitch,&nbsp;when the sofs=
witch communicates with the media gateways via H.248?</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; thanks,</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; Pablo Salinas</DIV><p><br><hr size=3D1 noshade><b>Do You Yahoo!?=
</b><br>
<a href=3Dhttp://espanol.yahoo.com/mail_tagline/*http://espanol.news.yaho=
o.com><img src=3D"http://us.i1.yimg.com/us.yimg.com/i/not/dailynews.gif" =
width=3D30 height=3D26 border=3D0 align=3Dleft></a>
Todo lo que quieres saber de Estados Unidos, Am=E9rica Latina y el resto =
del Mundo.<br>
Vis=EDta <a href=3Dhttp://espanol.yahoo.com/mail_tagline/*http://espanol.=
news.yahoo.com>Yahoo! Noticias</a>.<br>
--0-328760516-1056982753=:27893--

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



From exim@www1.ietf.org  Mon Jun 30 10:49:29 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28572
	for <sigtran-archive@odin.ietf.org>; Mon, 30 Jun 2003 10:49:29 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5UEn1111223
	for sigtran-archive@odin.ietf.org; Mon, 30 Jun 2003 10:49:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Wzxk-0002uo-EY; Mon, 30 Jun 2003 10:49:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Wzx5-0002t0-Do
	for sigtran@optimus.ietf.org; Mon, 30 Jun 2003 10:48:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28497
	for <sigtran@ietf.org>; Mon, 30 Jun 2003 10:48:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Wzwn-0001Rv-00
	for sigtran@ietf.org; Mon, 30 Jun 2003 10:48:01 -0400
Received: from auds953.usa.alcatel.com ([143.209.238.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Wzwa-0001Qm-00
	for sigtran@ietf.org; Mon, 30 Jun 2003 10:47:48 -0400
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.8p1/8.12.8) with ESMTP id h5UEioLX026742
	for <sigtran@ietf.org>; Mon, 30 Jun 2003 09:44:50 -0500 (CDT)
Received: from sun2594.ssd.usa.alcatel.com (sun2594.ssd.usa.alcatel.com [143.209.250.252])
	by ssd.usa.alcatel.com (8.12.8/8.12.8) with ESMTP id h5UEi11C002634
	for <sigtran@ietf.org>; Mon, 30 Jun 2003 09:44:01 -0500 (CDT)
Date: Mon, 30 Jun 2003 09:44:01 -0500 (CDT)
From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
To: sigtran@ietf.org
Subject: Re: [Sigtran] Re:n+k issue
In-Reply-To: <20030628041753.B5019@openss7.org>
Message-ID: <Pine.SOL.4.10.10306300837510.24913-100000@sun2594.ssd.usa.alcatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>,
	<mailto:sigtran-request@ietf.org?subject=subscribe>


Brian,



On Sat, 28 Jun 2003, Brian F. G. Bidulock wrote:

> Samuel,
> 
> I should point out that the proposal to require that the SG wait for 'n' to
> start traffic does not have much merit.
> 
> Example: n=256, k=1
> 
> 2 ASPs fail, permanently and need to be manually replaced.
> 
> A temporary network failure causes SCTP associations to be lost to the
> remaining 255 ASPs.  They move to the ASP down state and immediately
> re-establish SCTP associations and move to the ASP-Active state.  Because the
> number of ASPs is < n, the SG will not restart traffic for some time.

Your example leads to the following figure.

         SG1                            AS1
     
 SS7 MSG +------+----------------------- ASP (1)
---------| SGP1 |----------------------- ASP (2)
         |      |----------------------- ....
         +------+----------------------- ASP (256)
            |
            | 
            +---------------------------ASP(k)

1. First of all craft will not configure 1 ASP as backup for 256 Active
   ASPs, if he does, it means to be a poor network configuration.

2. Consider ASP as an MGC, your example leads to 256 MGCs and they are 
   controlled by a single SGP.A good network will have multiple SGPs to
   share the POTENTIAL traffic across ASPs.

3. BASIC INTENTION OF 'n+k' is,just to make sure that incoming messages
   ARE EFFICIENTLY TRANSMITTED TO DESTINATION ASPs WITH THE HELP OF
   MINIMUM NUMBER OF ASSOCIATIONS.

   Say for example

   Inefficient configuration -just an example
   ------------------------------------------
  
            SLS         DEST
            =================
             0           ASP1
             1           ASP1
             2           ASP1
             3           ASP1
             4           ASP1
             5           ASP1
             6           ASP1
             .            .
             .            .
             15          ASP1
             
             
               SG                            AS1
sls(0,1..15 )+----+  sls(0,1..15)         +------+
-------------|SGP1|-----------------------| ASP1 |
             |    |              ASSOC-1  +------+
             +----+                     

                      Fig - 1

In this figure, all incoming messages are transmitted over ASSOC-1 towards
ASP1.Here there are two potential problems 

       1. Total incoming traffic is dependent on a single ASP
       2. ASP1 is always overloaded, messages are processed one by one
          from the transmission buffer which ultimately introduces time
          delay(example last arrived msg will be processed at the end).


Efficient configuration
-----------------------  

             SLS         DEST
            =================
             0           ASP1
             1           ASP1
             2           ASP1
             3           ASP1
             4           ASP1
             5           ASP1
             6           ASP1
             7           ASP1
             8           ASP2
             9           ASP2
             .            .
             .            .
             15          ASP2

               
                       
                       
              SG                             AS1
sls(0,1..15 )+----+   sls(0,1,..7)ASSOC-1 +------+
-------------|SGP1|-----------------------| ASP1 |
             |    |--------+              +------+
             +----+        | sls(8,9..15) +------+
                           +--------------| ASP2 |
                                 ASSOC-2  +------+
                        
                   fig - 2

In this example incoming traffic is distributed between ASP1 and ASP2.

IN ORDER TO HANDLE THE HEAVY INCOMING TRAFFIC, SGP1 NEEDS MINIMUM OF
2 ACTIVE ASPs BY SETTING n=2.


Your example with n=256 is completely a wrong interpretaion of 'n+k'
redundancy case.


> 
> Consider the same example with: n=2, k=1, two ASPs failed.
> 
> Any system that introduces hysteresis to aggravate and perpetuate an outage in
> this fashion is not very useful.
> 
> In the examples, what would have been a brief AS-PENDING situation has been
> turned into a prolonged and complete system failure.  It is certainly not good
> practice to design redundant systems in that fashion and recommending or
> requiring such a design would be a bad thing.
> 
> To further the example, consider the multiple SG as STP situation.  One SG
> cannot know the state of ASPs for the its mated SG and therefore cannot
> distinguish between the restart scenario and the start scenario as far as the
> AS state is concerned because the SG does not know the state of the AS itself:
> the AS could be active with other SGs.
> 
> This is the same case for SGP.  Unless AS state is synchronized across SGPs,
> one SGP cannot know the total state of the AS (only its partition).  There is
> no requirement to synchronize AS state across SGP (on the SGP side, AS-state
> is per-SGP), and there is certainly no requirement to synchronize AS-state
> across SGs.
> 
> So, take the (n=2, k=0) example where there are two SGs.  Due to a network
> partitioning at startup, one ASP can communicate only with one SG, and the
> other ASP can communicate only with the other SG.  Because n=2, neither SG
> will start traffic and the system suffers 100% failure until the network
> partitioning ceases.
> 
> Consider the same example where there are two SGPs (instead of SGs) and the
> two ASPs normally only form one association (e.g., ASP1-SGP1, ASP2-SGP2).
> Note that there is no requirement in the RFC to form full-mesh associations.
> Because the number of active ASPs with each SGP is < 2, the system will never
> start.
> 
> These are not strange scenarios.  These situations are all permitted by the
> RFC.  Yet, in each situation it is clear that one cannot recommend that the SG
> wait.  The result would be a non-functional system.  There are many more
> examples.
> 
> n+k is a model for redundancy (not for congestion and flow control).  A system
> with an SG that waits for n is, in general, not a fully redundant system at
> all, but is, rather, prone to these failure syndromes.
> 
> When you look at the situation and apply the experience of reliability
> engineering, the recommendation is that the SG SHOULD start traffic when the
> first ASP goes active.
> 
> Why wait for 'n' anyway?  Because the ASP cannot handle some level of traffic?
> Any ASP that conforms to MTP-User standards, must have the standardized
> MTP-User (ISUP/SCCP) congestion and flow controls and must have the SCTP
> congestion controls and is therefore able to accept any amount of traffic
> overload.
> 
> So there is no real reason for the SG to wait for 'n'.  Nevertheless, the RFC
> allows this as an OPTION.  Requiring (MUST) or recommending it (SHOULD)
> regardless of whether the number of active processors is rising or falling,
> whether start, restart or failure, is unacceptable.
> 
> On the other side, at the ASPs, the ASPs have a requirement to share state
> between them.  They must share circuit state and transaction state in all
> configurations to meet carrier grade.  This is stated in the RFC.  It is
> implicit that the ASPs are capable of knowing with which SGs, and which SGPs
> for which they are active.  They have access to the total state of the AS that
> they collectively represent, that the SG/SGP does not.  Therefore is it
> reasonable for the ASPs to coordinate among themselves the number of active
> ASPs and to ensure that there are sufficient ASPs active to handle the
> expected load before starting traffic.  Because the ASPs need not respond to
> user test traffic (UPT/SST), the ASPs are also in control of when remote SS7
> MTP-User restart traffic toward them.
> 
> Therefore, the recommendation that the ASPs SHOULD coordinate among
> themselves the number of active ASPs and not start traffic until a sufficient
> number of them are active is sound.  This is not a MUST, permitting ASPs
> that know that they are capable of handling any overload, to start traffic
> immediately, or at some earlier point.
> 
> Back to the RFC, the RFC sets the normal case where the SG starts traffic on
> the first active ASP but explicitly permits as an OPTION to wait until it
> considers that there are sufficient ASPs active to handle the offered load.
> The RFC also RECOMMENDS that the ASPs coordinate among themselves the number
> of active ASPs so that there are sufficient ASPs to handle the expected load.
> 
> The provisions in the RFC are both sound, where the proposal and section 3.15
> is clearly not.
> 
> Remember when looking at the AS state diagram in the RFC that this is the
> SGP's view of the AS state and not the total state of the AS, that can only
> known to the ASPs for all configurations.  'n' as defined has no meaning to
> the state machine at the SGP because is not required to know, and often cannot
> know, how many ASPs are active for the AS via other SGPs and SGs, or even via
> direct connection to the SS7 network.
> 
> Some SGs might have special knowledge, or sophisticated algorithms that allow
> it to determine whether a congestive failure will be the immediate result of
> starting or restarting traffic.  These SGs are permitted as an OPTION to wait.
> 
> The ASPs SHOULD have the knowledge of how many are required to handle the
> expected load, because they must share circuit/transaction state and they must
> have congestion and flow controls as required by the standards.
> 
> So again, the RFC is adequate in this regard.  The current proposal and
> section 3.15 are not.
RFC is inadequate so we need section 3.15 to explain 'n+k' case.

--Samuel
> 
> --brian
> 
> 
> Brian F. G. Bidulock wrote:                                                         (Sat, 28 Jun 2003 02:42:03)
> > Samuel,
> > 
> > In the note I only said that you and Srivats agreed to not
> > stopping traffic #APSs < n.  I didn't say that you agreed
> > to starting traffic on the first ASP.  The others in this
> > and previous disccusions did, however.
> > 
> > --brian
> > 
> > Samuel Dur D. Jeyaseelan wrote:                                                     (Sat, 28 Jun 2003 03:24:46)
> > > 
> > > Brian,
> > > 
> > > In this attached mail i have said that 'n=2'(example) is mandatory at
> > > start case.
> > > This is what Javier,Tolga are also proposing to make 'n=2' as mandatory
> > > at start case.
> > > 
> > > SGP will stop taking traffic when # ASPS < n at start case.
> > > 
> > > But while handling the traffic if # ASPs < n , this will not stop the
> > > traffic.This is what i comprised in this mail.
> > > 
> > > So from the beginning i disagree to make an AS as active as soon as a
> > > single ASP goes to ACTIVE state in n+k reduntancy case.
> > > 
> > > --Samuel
> > > 
> > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
> > >   1000 Coit Road, Plano, Texas 75075
> > >   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> > > 
> > > On Sat, 28 Jun 2003, Brian F. G. Bidulock wrote:
> > > 
> > > > Samuel,
> > > > 
> > > > Samuel Dur D. Jeyaseelan wrote:                                                     (Sat, 28 Jun 2003 01:36:10)
> > > > 
> > > > > > 
> > > > > > Next on the thread:
> > > > > > 
> > > > > >   "M3UA Notify message" from Feb 12, 2003 to Feb 26, 2003
> > > > > >   (rejoined recently and extending from Jun 18, 2003 to Jun 26, 2003)
> > > > > > 
> > > > > > Srini asks some questions about Notify messages and n+k comes up again.  Srini
> > > > > > agrees that active ASPs < n corresponds to the AS-ACTIVE state as in the RFC
> > > > > > and that the ASP should use congestion and flow control procedures to limit
> > > > > > traffic if it is presented with too much traffic.  Bijoy agrees as well.
> > > > > > Srivats agrees as well with not stopping traffic #ASPs < n.  Samuel also
> > > > > > agrees with not stopping traffic #ASPs < n.  Javier agrees to the MAY.
> > > > > 
> > > > > Could you please give me a pointer where i agreed?
> > > > > 
> > > > > --Samuel
> > > > > 
> > > > 
> > > > Correct me if I'm wrong but it appears in the following two statements that
> > > > you agreed to not stopping traffic for #ASPs < n.
> > > > 
> > > > > Date: Tue, 25 Feb 2003 08:11:31 -0600 (CST)
> > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > > > To: "Javier Pastor-Balbas (ECE)" <javier.pastor-balbas@ece.ericsson.se>
> > > > > cc: "Brian F. G. Bidulock" <bidulock@openss7.org>,
> > > > >    TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>, sigtran@ietf.org
> > > > > Subject: RE: [Sigtran] Re: M3UA Notify message
> > > > > 
> > > > > Javier,
> > > > > 
> > > > >   Alcatel USA, Inc.                  Internet: <userid>@ssd.usa.alcatel.com
> > > > >   1000 Coit Road, Plano, Texas 75075
> > > > >   ******* The opinions expressed are not those of Alcatel USA, Inc. *******
> > > > > 
> > > > > On Tue, 25 Feb 2003, Javier Pastor-Balbas (ECE) wrote:
> > > > > 
> > > > > > Hi Samuel et al., 
> > > > > > 
> > > > > > Take into account that if you define two ASes:
> > > > > > - AS1 DPC+SLS1  with two ASPs (ASP1 and ASP2) and redundancy: n=1 k=1
> > > > > > - AS2 DPC+SLS2  with two ASPs (ASP1 and ASP2) and redundancy: n=1 k=1
> > > > > > 
> > > > > > And 
> > > > > > - ASP1 active for AS1 and backup for AS2
> > > > > > - ASP2 active for AS2 and backup for AS1
> > > > > > 
> > > > > > You get the desired behaviour. This case can be solved with a right 
> > > > >   network configuration without changing the current "required"
> > > > >   qualification for "n".
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > Apart from this, 
> > > > > > 
> > > > > > I would say that a compromise option would consist of considering "n" as 
> > > > >   the normal working case, but make it implementation dependent (maybe
> > > > > configurable) whether an implementation may have more than "n" ASPs 
> > > > >  working at the same time for an AS, and whether the SG keeps working when
> > > > > the number of ASP is under "n". We could make a recommendation with "MAY" 
> > > > > allowing both options.
> > > > > >
> > > > > [Samuel] Yes .SG keeps working when n=1 or n >=2.
> > > > > but current RFC says that SG NOTIFIES 'k' ASP to become active only
> > > > > when n<2 and it does not say what will happen when SG requires more than
> > > > > 'n' ASP to handle the traffic 't+1'.
> > > > >  
> > > > > > But now, the problem comes with the AS state machine. If we agree upon here,
> > > > >  we could say the AS is ACTIVE in the range n_min to n_max, where these two
> > > > >  values are configurable.
> > > > > > 
> > > > > [Samuel] To handle the 'normal(best) traffic T' SG requires 'n=2' ASPs.
> > > > > In the course of traffic if 'n became 1'(means ASP1 failed), here SG can
> > > > > handle the traffic with 'n=1' ASP. 
> > > > > So only intially SG requires 'n=2' ASPs to make the AS state as ACTIVE
> > > > > and 'n=2' is fed during configuration.But while handling traffic due to 
> > > > > failure of ASP1 'n' becomes '1', here still AS is ACTIVE with single ASP.
> > > > > 
> > > > > --Samuel
> > > > 
> > > > [snip]
> > > > 
> > > > > Date: Tue, 25 Feb 2003 06:08:39 -0600 (CST)
> > > > > From: "Samuel Dur D. Jeyaseelan" <sjeyasee@ssd.usa.alcatel.com>
> > > > > To: TOLGA ASVEREN <TOLGA.ASVEREN@o2.com.tr>
> > > > > cc: sigtran@ietf.org
> > > > > Subject: Re: [Sigtran] Re: M3UA Notify message
> > > > > 
> > > > > 
> > > > > Tolga,
> > > > > 
> > > > > From this thread we can end up with two kinds of SGs.
> > > > > 
> > > > > The SG which decides to stop taking the traffic when 'n' changed
> > > > > from '2' to '1'.
> > > > > 
> > > > > The other SG which decides to continue the traffic  when 'n' 
> > > > > changed from '2' to '1'.
> > > > > 
> > > > > When performance is considered, i think everyone will prefer second case.
> > > > > Second case follows the existing network standards.But first case does
> > > > > not follow any standards.
> > > > 
> > > > [snip]
> > > > 
> > > > 
> > > > -- 
> > > > Brian F. G. Bidulock
> > > > bidulock@openss7.org
> > > > http://www.openss7.org/
> > > > 
> > > > _______________________________________________
> > > > Sigtran mailing list
> > > > Sigtran@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/sigtran
> > > > 
> > 
> > -- 
> > Brian F. G. Bidulock
> > bidulock@openss7.org
> > http://www.openss7.org/
> > 
> > _______________________________________________
> > Sigtran mailing list
> > Sigtran@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sigtran
> 
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
> 
> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/sigtran
> 


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



